M20T10 40e 01 PRT

FOUNDATION fieldbus
Reference
IM 33M20T10-40E
IM 33M20T10-40E
1st Edition

Introduction
This manual contains important information for using the FOUNDATION fieldbus together with
the KFCS, KFCS2, FFCS, RFCS2 or RFCS5 in CENTUM VP. Please be sure to read this manual
before using the product.
A Fieldbus is a fully digital bidirectional communication link that connects a control system with
field devices, such as transmitters, flowmeters, and analyzers.
This manual explains the Control Function, Operation and Monitoring Functions, and System
Builder Function of the CENTUM VP system to which the Fieldbus is connected.
This manual consists of the following parts:
In this manual the KFCS, KFCS2, FFCS, RFCS2 and RFCS5 are all referred to as FCS in
regarding to installation of ALE111, a communication module for connecting to fieldbus devices
with FOUNDATION fieldbus (FF-H1).
• Part A Fieldbus Overview

This part explains the system configuration for connecting the Fieldbus with the CENTUM VP
as well as the FOUNDATION fieldbus faceplate blocks, and it also provides an overview of
the CENTUM VP engineering procedures related to the Fieldbus. Please be sure to read this
part before starting to engineer the Fieldbus system.
• Part B FCS Fieldbus Support

This part explains the functions of the FCS that support the Fieldbus. It explains how the
basic FCS functions support the Fieldbus system, and it also explains the detailed functions
of the FOUNDATION fieldbus faceplate blocks. Please refer to this part to obtain information
on these subjects.
• Part C System Fieldbus Support

This part explains how the Fieldbus is supported in the CENTUM VP system. Specifically,
it provides detailed descriptions of the Operation and Monitoring Functions that support the
Fieldbus. Please refer to this part to obtain information on these subjects.
• Part D Fieldbus Engineering

This part explains the Fieldbus engineering on the CENTUM VP in detail. Specifically, it
provides detailed descriptions of system engineering using System View and Function
Block Builder as well as Fieldbus engineering using Fieldbus Builder. It also explains how
to perform debug tests using wiring, and explains about the Fieldbus support tools. Please
refer to this part to obtain information on these subjects.
• Part E Variety Fieldbus Device Engineering

Variety fieldbus engineering including filedbus block instantiation, various types of fieldbus
device specifications and the engineering methods are explained in the sections divided in
accordance with the respective installation points. User can read only the needed section
of the interested point. However, to fully understand the contents in the chapter, the overall
engineering knowledge maybe required. For this purpose, user may need to read the
related items in Part D too.
Media No. IM 33M20T10-40E (DVD) 1st Edition : Mar. 2008(YK) IM 33M20T10-40E 1st Edition : Mar.23,2008-00
All Rights Reserved Copyright © 2001, Yokogawa Electric Corporation
ii
CENTUM VP Document Map

 Engineering
CENTUM VP
Engineering
Guidance
Engineering Engineering Reference

Test Guide Tutorial IM 33M01A30-40E
IM 33M10D20-40E IM 33M10D10-40E
CENTUM Data
Fieldbus APCS
Access Library
Documentation Documentation
IM 33M05F10-40E
 Operation and Operating

Monitoring HIS Operation
Messages
IM 33M05D10-40E
IM 33M05D20-40E
 Hardware
Peripherals Input & Output
Migrated-FCS (FIO)
Modules
IM 33M50C10-40E IM 33M50W10-40E
IM 33M50G10-40E
Communication Field Control

Vnet/IP
Devices Stations
IM 33L01A10-40E
IM 33M50D10-40E IM 33M50E40-40E
Turbomachinery
I/O Modules
IM 33M10U10-40E
User's manual
 Installation CENTUM VP Installation Only available in electronic document
IM 33M01A20-40E Relationship between manuals
that must be read in order
Relationship to a referred manual
Reference manual
IM 33M20T10-40E 1st Edition : Mar.23,2008-00

iii
Safety Precautions
n Safety, Protection, and Modification of the Product
• In order to protect the system controlled by the product and the product itself and ensure
safe operation, observe the safety precautions described in this user’s manual. We assume
no liability for safety if users fail to observe these instructions when operating the product.
• If this instrument is used in a manner not specified in this user’s manual, the protection
provided by this instrument may be impaired.
• If any protection or safety circuit is required for the system controlled by the product or for
the product itself, prepare it separately.
• Be sure to use the spare parts approved by Yokogawa Electric Corporation (hereafter
simply referred to as YOKOGAWA) when replacing parts or consumables.
• Modification of the product is strictly prohibited.
• The following symbols are used in the product and user’s manual to indicate that there are
precautions for safety:
Indicates that caution is required for operation. This symbol is placed on the product to refer
the user to the user’s manual in order to protect the operator and the equipment. In the
user’s manuals you will find precautions to avoid physical injury or death of the operator,
including electrical shocks.
Identifies a protective grounding terminal. Before using the product, ground the terminal.
Identifies a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates that the main switch is ON.
Indicates that the main switch is OFF.

iv
n Notes on Handling User’s Manuals

• Please hand over the user’s manuals to your end users so that they can keep the user’s
manuals on hand for convenient reference.
• Please read the information thoroughly before using the product.
• The purpose of these user’s manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
• YOKOGAWA reserves the right to make improvements in the user’s manuals and product at
any time, without notice or obligation.
• If you have any questions, or you find mistakes or omissions in the user’s manuals, please
contact our sales representative or your local distributor.
n Warning and Disclaimer

The product is provided on an “as is” basis. YOKOGAWA shall have neither liability nor
responsibility to any person or entity with respect to any direct or indirect loss or damage arising
from using the product or any defect of the product that YOKOGAWA can not predict in advance.
n Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the
software’s merchantability or suitability for any particular purpose, except as specified in the
terms of warranty.
• This product may be used on a machine only. If you need to use the product on another
machine, you must purchase another product.
• It is strictly prohibited to reproduce the product except for the purpose of backup.
• Store the DVD-ROM (the original medium) in a safe place.
• It is strictly prohibited to perform any reverse-engineering operation, such as reverse
compilation or reverse assembling on the product.
• No part of the product may be transferred, converted or sublet for use by any third party,
without prior written consent from YOKOGAWA.

Documentation Conventions
n Typographical Conventions
The following typographical conventions are used throughout the user’s manuals:
l Commonly used conventions throughout user’s manuals:
Character string to be entered:

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

Indicates an option that can be omitted.
Example:
. PRΔTAG{Δ.sheet name}

vi
l Conventions used to show key or button operations:
Characters enclosed by brackets ([ ]):

Characters enclosed by brackets within any description on a key or button operation, indicate
either a key on the HIS (Human Interface Station) keyboard, a key on the operation keyboard, a
button name on a window, or an item displayed on a window.
Example:
To alter the function, press the [ESC] key.
l Conventions used in command syntax or program statements:

The following conventions are used within a command syntax or program statement format:
Characters enclosed by angle-brackets:

Indicate character strings that user can specify freely according to certain guidelines.
Example:
#define <Identifier><Character string>
“...” Mark
Indicates that the previous command or argument may be repeated.
Example:
Imax (arg1, arg2, ...)
Characters enclosed by brackets ([ ]):

Indicate those character strings that can be omitted.
Example:
sysalarm format_string [output_value ...]
Characters enclosed by separators (| |):

Indicate those character strings that can be selected from more than one option.
Example:
opeguide <format_character_string> [, <output_value> ...]
OG,<element number>

vii
n Symbol Marks
Throughout this user’s manual, you will find several different types of symbols are used to identify
different sections of text. This section describes these icons.
CAUTION
Identifies instructions that must be observed in order to avoid physical injury and electric
shock or death of the operator.
WARNING
Identifies instructions that must be observed in order to prevent the software or hardware
from being damaged or the system from becoming faulty.
IMPORTANT
Identifies important information required to understand operations or functions.
TIP
Identifies additional information.
SEE
ALSO
Identifies a source to be referred to.

Clicking a reference displayed in green can call up its source, while clicking a reference
displayed in black cannot.
n Drawing Conventions
Some drawings may be partially emphasized, simplified, or omitted, for the convenience of
description.
Some screen images depicted in the user’s manual may have different display positions or
character types (e.g., the upper / lower case). Also note that some of the images contained in this
user’s manual are display examples.

viii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the DVD-ROM or CD-ROM shall
remain in Yokogawa.
You are allowed to print out the required pages of the online manuals for using the product,
however, you are not allowed to print out the entire document. You can purchase the printed
manual from Yokogawa.
Except as stated above, no part of the online manual may be reproduced, either in electronic
or written form, registered, recorded, transferred, sold or distributed (in any manner including
without limitation, in the forms of paper documents, electronic media, films or transmission via the
network).
n Trademark Acknowledgments
• CENTUM and Vnet/IP are registered trademarks of YOKOGAWA.
• Microsoft, Windows, Windows Vista, Visual Basic, Visual C++ and Visual Studio are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
• Adobe, Acrobat and Acrobat Reader are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
• Ethernet is a registered trademark of XEROX Corporation.
• Java is a registered trademark of Sun Microsystems,Inc.
• MELSEC is a registered trademark of Mitsubishi Electric Corporation.
• Modicon and Modbus are registered trademarks of Schneider Electric SA.
• Memocon-SC is a registered trademark of Yaskawa Electric Corporation.
• PLC is a registered trademark of Rockwell Automation, Inc.
• SYSMAC is a registered trademark of OMRON Corporation.
• SIEMENS and SIMATIC are registered trademarks of Siemens Industrial Automation Ltd.
• “FOUNDATION” in “FOUNDATION fieldbus” is a registered trademark of Fieldbus
Foundation.
• SmartPlant is a registered trademark of Intergraph Corporation.
• “HART” is a registered trademark of the HART Communication Foundation.
• All other company and product names mentioned in this user’s manual are trademarks or
registered trademarks of their respective companies.
• We do not use TM or ® mark to indicate those trademarks or registered trademarks in this
user’s manual.

TocA-1
CENTUM VP
FOUNDATION fieldbus Reference
IM 33M20T10-40E 1st Edition
CONTENTS
PART-A Fieldbus Overview
A1. What is a Fieldbus?.................................................................................A1-1
A1.1 Glossary........................................................................................................... A1-2
A1.2 Fieldbus Systems........................................................................................... A1-5
A1.3 Configuration of Fieldbus Systems.............................................................. A1-6
A1.4 Fieldbus System Hardware............................................................................ A1-8
A1.5 Software for Configuring a Fieldbus System............................................ A1-10
A2. Overview of FF Faceplate Blocks..........................................................A2-1
A2.1 What is an FF Faceplate Block?.................................................................... A2-2
A2.2 Control Loop and Data Flow.......................................................................... A2-8
A2.3 Tuning Parameters........................................................................................ A2-16
A3. Overview of Simplified Universal Block...............................................A3-1
A3.1 What Is a Simplified Universal Block? ........................................................ A3-2
A3.2 Control Loop and Data Flow.......................................................................... A3-4
A3.3 Definition of the Simplified Universal Block ............................................... A3-8
A3.3.1 Assigning a Custom Block ...............................................................A3-9
A3.3.2 Correspondence of Connection Terminals, Data Items and
Parameters.....................................................................................A3-10
A3.3.3 Definition of I/O Parameter Names . ..............................................A3-11
A3.3.4 Builder Definition Items for the Simplified Universal Block ............A3-12
A4. Overview of Engineering........................................................................A4-1
A4.1 Flow of Engineering........................................................................................ A4-2
A4.2 State Transition of FF Faceplate Blocks...................................................... A4-9
A4.3 Software Download to Fieldbus Devices................................................... A4-12
A4.4 Template......................................................................................................... A4-13

Blank Page
<A1. What is a Fieldbus?> A1-1
A1. What is a Fieldbus?

A Fieldbus is a communication method that allows bidirectional communication via digital
signals. This communication method replaces the conventional standard communication,
i.e., 4 to 20 mA analog communication. The following eight types of definitions are made
in the IEC Fieldbus Communication Standard:
• Current IEC TS 61158
• FOUNDATION fieldbus
• FOUNDATION fieldbus High Speed Ethernet
• PROFIBUS
• Control Net
• P-Net
• Swift Net
• World FIP
• Interbus
• Profi Net
CENTUM VP support the FOUNDATION fieldbus and PROFIBUS-DP communication

standards.
FOUNDATION fieldbus is called the Fieldbus in this manual.
Sophisticated communication of the Fieldbus allows distributed control via Fieldbus
devices and optimal control by interfacing with a field control station (FCS).

A1.1 Glossary
This manual uses the terms listed below in addition to the basic terminology. Refer to this
list as necessary.
n Alert
Alert is a generic term for alarms and events that Fieldbus devices detect and notify to the upper-
level system (CENTUM VP).
n ALF111
ALF111 is a communication module compatible with the Fieldbus. The ALF111 module is
installed on a control station, KFCS, KFCS2, FFCS, RFCS2 or RFCS5, where it will handle
communication via the FOUNDATION fieldbus H1.
n Capabilities File
A capabilities file is a text file provided by the Fieldbus Foundation or device vendors. It contains
the information on resources and capabilities, default values, and index information of a Fieldbus
device. One capabilities file is generally provided for one device model.
n Configuration Data File (Value File)

This is the text file that describes the information for downloading to Fieldbus devices or link
master devices. Downloader reads the configuration data file and executes downloading. The
configuration data file is described according to the Common File Format.
n DD File
A DD file is a binary file provided by the Fieldbus Foundation or device vendors. It contains
information on how to handle block parameters used by function blocks mounted on the Fieldbus
devices.
n Extended Parameters
These parameters are the block parameters of the Fieldbus block added by the Fieldbus device
vendors independently.
n FF
This is the abbreviation for the Fieldbus Foundation.
n FF-H1
FF-H1 stands for FOUNDATION Fieldbus H1. Hereinafter FOUNDATION Fieldbus H1 will be
referred to as FF-H1 in the text as well as in the engineering builders.
n Fieldbus Block
Function blocks to be executed in field devices are generically referred to as Fieldbus blocks in
this manual.

n Fieldbus Block Instantiation

Fieldbus block instantiation instantiates the Fieldbus function blocks such as PID and AI blocks
which are implemented as classes in the Fieldbus devices. The user can define the number
of blocks for each block type according to the purpose within the range of blocks that can be
instantiated. The Fieldbus devices that allow block instantiation are required.
n Fieldbus Device
Field devices to be connected to the Fieldbus are generically referred to as Fieldbus devices in
this manual.
n FOUNDATION fieldbus Faceplate Block

This function block is operated as a representation of a Fieldbus block in the CENTUM VP. It
is included in the regulatory control category. The FOUNDATION fieldbus faceplate block is
referred to as the FF faceplate block throughout this manual. The abbreviation “FF” is different
from the abbreviation of Fieldbus Foundation (FF).
n Function Block
This is the section that achieves control algorithms such as PID and AI inside the Fieldbus
device. The function block is called the “Fieldbus block” in the descriptions of this manual.
n Host File
This file contains the configuration information of the Fieldbus required by Fieldbus Builder and
other builders of the CENTUM VP for engineering the Fieldbus system.
n LAS (Link Active Scheduler)

LAS (Link Active Scheduler) controls the communication schedule of the Fieldbus. A single
segment network must always contain only one device having the role of LAS.
n Macrocycle
A macrocycle refers to a reference scheduling cycle in which cyclic communication equivalent to
the minimum control cycle is repeated. Cyclic and noncyclic communications are scheduled by
LAS according to this macrocyle.
n Multiple Levels Compliant Devices

The fieldbus devices that support multiple capability levels are referred to as Multiple Levels
Compliant Devices. For each capability level, the number of function blocks in the fieldbus
devices are regulated. The capability level of the fieldbus devices can be determined according
to the actual applications.
n Segment
A segment is an engineering unit consisting of several Fieldbus devices and ALF111 ports to be
connected to one H1 Fieldbus.

n Standard Block Parameter

This is the type of a block parameter of the Fieldbus block that was designated by the Fieldbus
Foundation.
n Trend Object
This is a feature that stores short-term trend data locally within the Fieldbus block.
n VCR (Virtual Communication Relationship)

This is a communication channel among Fieldbus devices.
n View Object
This is a feature that manages and stores static and dynamic parameters such as PV to be used
for monitoring and control and scale upper/lower limit values within the Fieldbus device.

A1.2 Fieldbus Systems

A Fieldbus system refers to a control system that uses a Fieldbus. With the CENTUM VP, it
is possible to build a Fieldbus system according to the CENTUM VP engineering standard
and to operate and monitor the Fieldbus blocks of the Fieldbus devices in the same
manner as for the function blocks of the FCS.
n CENTUM VP System and Fieldbus

By mounting an ALF111 module to the field control station KFCS, KFCS2, FFCS, RFCS2 or
RFCS5, it is possible to integrate a Fieldbus system with the CENTUM VP in the following
manner:
l Integration of Control Function

• The FF faceplate block is one of FCS function blocks that represents a Fieldbus block of a
Fieldbus device. The Fieldbus block can be handled by control drawing in the same manner
as for the FCS function block. A control loop can be configured with FF faceplate blocks and
FCS function blocks in order to utilize the FCS control and computation features.
l Integration of Operation and Monitoring

• Alarms sent out from Fieldbus blocks of Fieldbus devices are handed in the same way as
alarms of FCS function blocks (such as process alarms and system alarms) through FF
faceplate blocks.
• Fieldbus blocks of Fieldbus devices can be operated and monitored in the same way as
FCS function blocks through FF faceplate blocks.
l Integration of Engineering
The engineering function of the CENTUM VP is used for engineering. Create FF faceplate
blocks using Function Block Builder, and make definitions unique to the Fieldbus using Fieldbus
Builder. These builders can be called up from System View in order to perform the same type of
engineering as for other FCS function blocks.

A1.3 Configuration of Fieldbus Systems

A Fieldbus system consists of a CENTUM VP system, a Fieldbus connected through
an ALF111 module mounted on a KFCS, KFCS2, FFCS, RFCS2 or RFCS5 station in
the system, and Fieldbus devices. FOUNDATION fieldbus is in accordance with the
Fieldbus standard called H1. The H1 standard is capable of supporting intrinsically safe
explosion-proof.
n Overall Configuration of the Fieldbus System

The overall configuration of the Fieldbus system is shown in the figure below. It shows
an example of a system where the engineering function and the Foundation Fieldbus
Communication Package (for ALF111) are installed in an HIS. As for the FCS, a KFCS that can
mount an ALF111 is used as an example.
Ethernet
HIS
• System Builders Device Management

Tools
• Operation and Monitoring
Master PC
Vnet
KFCS
FCU
ESBbus
SB401
Fieldbus Support
Tool
ALF111
Slave PC
H1 Fieldbus
Fieldbus external
power supply Fieldbus device Fieldbus device
A010301E.ai
HIS: Human Interface Station

KFCS: Control station
FCU: Field control unit
ESB bus: Extended SB bus
SB401: ESB bus interface (I/O nest side)
ALF111: Foundation Fieldbus communication module
Device Management Tool: Can be used for the purpose of supplementing operation and monitoring.
Fieldbus support tool: Cannot be used for the Fieldbus devices that are operating on the H1 Fieldbus, but can be used for the
purpose of performing Fieldbus device engineering prior to installation.
Figure Example of Fieldbus System Configuration
SEE
ALSO For more details on the device management tool and the Fieldbus support tool, refer to the FOUNDATION
fieldbus Tools (IM 33S05P10-01E).

n Fieldbus System Configuration and Data Flow

The following figure shows the Fieldbus system configuration and data flow:
HIS
System Builders
System View
Function Block Builder
Operation and
Monitoring Fieldbus Builder
Vnet
FCS
Schedule
FCU downloading
FF faceplate block Parameter uploading

and downloading
Fieldbus
communication
Messages
Process I/O data V net communication
Block parameters transmission/reception
Status
monitoring Schedule
Fieldbus data access downloading
ALF111 status Parameter

uploading and
Process I/O data Alert field downloading
device status
Block parameters
I/O image
Process I/O data
ESB bus
ALF111
H1 Fieldbus
Fieldbus device
Communication interface
Function block
Resource block
Physical information
Transducer block Status information
Signal conversion between Legend
hardware and function block
Actual hardware : Data flow
(sensor/actuator) : Connection line
A010302E.ai
Figure Fieldbus System Configuration and Data Flow

A1.4 Fieldbus System Hardware

This section explains each of the hardware to construct the Fieldbus system.
n Fieldbus System Hardware Configuration

The Fieldbus is connected to the Foundation Fieldbus communication module (ALF111).
Communication modules of this type are mounted on the ESB bus node units (ANB10S,
ANB10D) and the ER bus node units (ANR10S, ANR10D); and directly inserted in a slot of
FFCS FCU. Moreover, various other types of hardware can be connected to the Fieldbus. The
hardware configuration is explained in the following:
FCS: Field control station
FCU: Field control unit
SB401: ESB bus interface (I/O nest side)
EB401: ER bus interface (FCS side) FCS
EB501: ER bus interface (remote node side)
ALF111: Foundation Fieldbus communication module FCU
ACB41: Input/output extension cabinet
ESBbus
ALF111 ALF111 EB401 SB401

Intrinsic safety barrier/arrester (Control) (Standby) (Duplexed)(Duplexed)
(optional)
H1 Fieldbus Local node
Terminator
Terminator
(optional) Fieldbus power
ERbus
supply (Option)
ACB41
ALF111 ALF111 EB501
Intrinsic safety barrier/arrester (Control) (Standby) (Duplexed)
(optional)
H1 Fieldbus Remote node
Terminator
Terminator
(optional) Fieldbus power
supply (Option)
A010401E.ai
Figure Hardware Configuration on Fieldbus Side
l Fieldbus Communication Module (ALF111)

The ALF111 operates as a link active scheduler (LAS), and manages the communication
schedule of the Fieldbus. In addition, the ALF111 transfers data between the FCS and the
Fieldbus devices.
l Cable
Select the cable from the following wire material types according to the cable installation
environment:
• Type A (twisted pair wire with individual shield)
• Type B (twisted pair wire with bundle shield)
• Type D (twisted non-pair wire with bundle shield)

l Barrier
The barrier is installed when intrinsically safe explosion-proof is required. The barrier is a unit
that suppresses the power supply to the electrical circuit of a Fieldbus or Fieldbus device when
the circuit is short-circuited, in order to prevent ignition and explosion of flammable gas due to
electrical sparks. Using the barrier as a boundary, the bus power supply side of the Fieldbus is
called the safe side, and the opposite side is called the dangerous side.
The number of Fieldbus devices that can be connected when the barrier is installed is about up
to four units in the dangerous side, and up to two units in the safe side. However, the number
of Fieldbus devices that can be connected to each side will vary slightly depending on the
consumption current of the Fieldbus devices to be connected to the dangerous side and the
specifications of the barrier to be installed.
l Arrester
The arrester is an device that discharges overvoltage shock waves to the ground if overvoltage
shock waves are generated by lightning, etc.
l Fieldbus Power Supply

This power supply is used exclusively for the Fieldbus that supplies power to Fieldbus devices.
l Terminator
The terminator is a device that is installed to adjust the network.
l Fieldbus Device
This is a Fieldbus device such as a transmitter or positioning unit. A device from any
manufacturer can be connected as long as it is compatible with the Fieldbus and conforms to the
FOUNDATION fieldbus specifications.

A1.5 Software for Configuring a Fieldbus System

This section provides an overview of the software necessary for engineering, controlling,
and operating and monitoring a Fieldbus system.
n Software for Configuring a Fieldbus System

In order to configure a Fieldbus system, each of operation and monitoring, system builders and
FCS control software is required. The Foundation Fieldbus communication package (for ALF111)
is also required.

<A2. Overview of FF Faceplate Blocks> A2-1
A2. Overview of FF Faceplate Blocks

The Fieldbus device is logically structured with an internal resource block, function
blocks and transducer blocks, etc. One resource block is always mounted to the Fieldbus
device. Function blocks and transducer blocks are mounted as necessary.
FF faceplate blocks are function blocks representing Fieldbus blocks to be executed in an
FCS. By using FF faceplate blocks, it becomes possible to operate and monitor Fieldbus
blocks on an HIS in the same manner as for FCS function blocks. In addition, the internal
parameters of the Fieldbus blocks can be referenced/set by the HIS or other function
blocks. This enables to build cascade loops from other function blocks in the FCS to
Fieldbus blocks, thereby configuring control loops that integrate the Fieldbus system
with the FCS.
This chapter describes the types and operations of FF faceplate blocks, and the function
block diagram and data flow of FF faceplate blocks.

A2.1 What is an FF Faceplate Block?

This section provides an overview of the FF faceplate blocks. It explains their roles in the
system and the different types of FF faceplate blocks.
n Roles in the System

The FF faceplate blocks play the following roles in the CENTUM VP system.
• The FF faceplate block is a “window” through which the function blocks of the HIS or FCS
can access the Fieldbus side.
• The FF faceplate block provides a means to perform HIS or FCS engineering and Fieldbus
engineering in the same environment.
Because of the above roles the FF faceplate block plays, the CENTUM VP specifications are
used if the CENTUM VP specifications and the Fieldbus Foundation specifications are different.
Consequently, parts of the Fieldbus Foundation specifications may not be used in some of
the CENTUM VP systems. The differences between the CENTUM VP specifications and the
Fieldbus Foundation specifications are described below.
l Comparison between the CENTUM VP Specifications and the Fieldbus

Foundation Specifications
The following explains the specifications of the FF faceplate blocks, along with a description of
how the Fieldbus Foundation specifications differ from the CENTUM VP specifications.
• Block Type
In the FF faceplate block, the block type of the Fieldbus block predetermined by Fieldbus
Foundation is prefixed by “FF-.”
(Example) The block type of the FF faceplate block for the AI block is FF-AI.
• Tag Name
Up to 32 characters are allowed in the Fieldbus Foundation specifications, whereas up to
16 single-byte characters are allowed in the CENTUM VP specifications. The CENTUM VP
specifications are used for the FF faceplate block.
• Tag Comment
Up to 32 single-byte characters or 16 double-byte characters are allowed in the Fieldbus
Foundation specifications, whereas up to 24 single-byte characters or 12 double-byte
characters are allowed in the CENTUM VP specifications. The CENTUM VP specifications
are used for the FF faceplate blocks; i.e., up to 24 single-byte characters or 12 double-byte
characters.
• Parameter Name
Up to 32 characters are allowed in the Fieldbus Foundation specifications, whereas up
to 8 single-byte characters are allowed for data items in the CENTUM VP specifications.
Because of this difference, parameter names may be abbreviated.
Since the FF faceplate block is a representation of the Fieldbus block, most of the
parameters of the FF faceplate block are the same as those of the Fieldbus block. The
following table lists the parameters that are different between these two blocks.
Table Correspondence of Parameters
Fieldbus FF faceplate
block block Description
parameter name parameter name
MODE_BLK MODE Replaced with a common data item name of an FCS function block.
HI_HI_LIM HH Same as above.
STATUS_OPT STS_OPT Abbreviated, as the maximum number of characters is limited to 8.
A020101E.ai

• Parameter Type
The Fieldbus Foundation specifications support parameter structures, but the CENTUM VP
specifications do not support them. The structure is a collection of multiple sets of data. For
example, in the Fieldbus Foundation specifications, block modes are grouped as the structure
named MODE_BLK, and target mode and actual mode are defined as structure members
such as MODE_BLK.Target and MODE_BLK.Actual. Because structures are not supported
in the CENTUM VP specifications, in the FF faceplate block, each member of a structure
becomes a separate data item named TMOD and AMOD, for example.
• Block Mode
In the Fieldbus Foundation specifications, all block modes have compound modes, whereas
MAN, AUT and CAS are all independent in the CENTUM VP specifications and there are no
compound modes.
• Process Alarm
In the Fieldbus Foundation specifications, the process alarm detection designation and
priority can be set in detail. In the CENTUM VP specifications, only the process alarm
detection designation and alarm off designation can be set. As for the priority, the alarm
severity of the FF faceplate block is defined. An alarm priority that may exceed the definable
alarm severity range cannot be set.
• Terminal
In the Fieldbus Foundation specifications, the terminal itself has a value because it is
defined as a parameter that can be connected. On the other hand, in the CENTUM VP
specifications, the terminal and the data item are clearly different; the terminal does not
have a value. In the FF faceplate block, a name defined as a terminal in the Fieldbus
Foundation specifications becomes a terminal, but the terminal itself does not have a value.
Instead, a data item called “TerminalName_V” is defined. It is possible to read the value of
the Fieldbus block terminal through this data item.
• Wiring
In the Fieldbus Foundation specifications, wiring must be laid out from an output terminal
to an input terminal. Even when readback is performed, wiring is also required. However,
the FF faceplate block follows the CENTUM VP specifications; readback is automatically
connected internally.
• Builder Items that can be Changed
There are differences between the builder elements that can be designated among the
static parameters in the Fieldbus Foundation specifications and the builder elements
that can be designated in the CENTUM VP specifications. Data items that must remain
unchanged according to the Fieldbus Foundation specifications will have a write-protect
attribute in a builder.

l Difference in Block Mode between the Fieldbus Foundation Specifications and
the CENTUM VP Specifications
In the CENTUM VP specifications, the MAN, AUT and CAS block modes cannot be used
together in a function block at the same time. However, a compound block mode can be used
for other block modes. In the Fieldbus Foundation specifications, there are two types of modes,
actual mode and target mode, each of which represents a compound block mode. As a result,
compound MAN/AUT/CAS modes also exist. The FF faceplate block follows the CENTUM VP
specifications; the MAN, AUT and CAS block modes do not coexist in a function block at the
same time. The following table lists the correspondence of block mode actions between the FF
faceplate block and the Fieldbus block.
Table Correspondence of Block Modes
Prior FF faceplate
Fieldbus mode Remarks
Level block mode
High O/S O/S
IMAN IMAN The block mode becomes a compound block
mode with a higher priority mode of the target
TRK LO mode.
MAN MAN
MAN, AUT, and CAS can be compound
AUT AUT modes in the Fieldbus, but are incompatible
block modes in CENTUM.
CAS CAS
RCAS RCAS
Low ROUT ROUT
A020102E.ai
• Relationship between MODE_BLK of the Fieldbus block and the Block Mode of the FF
Faceplate Block
The actual and target modes in MODE_BLK of the Fieldbus block are combined to make up
the block mode of the FF faceplate block. When these two modes are not identical, they are
displayed as a compound block mode.
• Display of a Compound Block Mode on HIS
In the Operation and Monitoring, the block mode with the lowest priority and the block mode
with the highest priority among the basic block modes that came into existence at the same
time, are combined and displayed.
Examples:
AUT O/S
RCAS IMAN
ROUT TRK
• Data Items Related to Block Mode
The block mode of the FF faceplate block is created by combining the actual and target
modes of the Fieldbus block. However, considering the situation where the target and
actual modes are monitored separately, data items related to the block mode are provided
for monitoring both these modes independently. These data items are displayed as the
same data type as that of the CENTUM VP block mode of U32, not as a mode string. The
following table lists the data items related to the block mode.
Table Data Items Related to Block Mode
Data item name Description
AMOD Displays the actual mode of MODE_BLK.
TMOD Displays the target mode of MODE_BLK.
NMOD Displays the normal mode of MODE_BLK.
PMOD Displays the permitted mode of MODE_BLK.
A020103E.ai

n Function Block Category

FF faceplate blocks are classified into the category of regulatory control blocks. The maximum
number of FF faceplate blocks that can be defined in one FCS varies depending on the FCS
database type. Moreover, the maximum number of FF faceplate blocks that can be defined is
restricted to 100 per ALF111 module.
SEE
ALSO For more explanation of the FCS database type, see the following:
F2.4.1, “Creating a New FCS” in CENTUM VP Reference, Engineering (IM 33M01A30-40E)
n Types of FF Faceplate Blocks

Those of the Fieldbus blocks prescribed in the FF specification, for which corresponding FF
faceplate blocks are provided, are shown in the following table. The FF specification furthermore
defines resource blocks and transducer blocks. Use normal faceplate blocks in order to monitor
these blocks with the HIS.
Table FF Faceplate Blocks
Type Name Corresponding Fieldbus block
FF-AI Foundation Fieldbus Analog Input Block AI (Analog Input Block)
FF-DI Foundation Fieldbus Discrete Input Block DI (Discrete Input Block)
FF-CS Foundation Fieldbus Control Selector Block CS (Control Selector Block)
FF-PID Foundation Fieldbus PID Control Block PID (PID, PI, I Controller Block)
FF-RA Foundation Fieldbus Ratio Block RA (Ratio Station Block)
FF-AO Foundation Fieldbus Analog Output Block AO (Analog Output Block)
FF-DO Foundation Fieldbus Discrete Output Block DO (Discrete Output Block)
FF-OS Foundation Fieldbus Output Splitter Block OS (Output Splitter)
FF-SC Foundation Fieldbus Signal Characterizer Block SC (Signal Characterizer)
FF-IT Foundation Fieldbus Integrator (Totalizer) Block IT (Integrator)
FF-IS Foundation Fieldbus Input Selector Block IS (Input Selector)
FF-MDI Foundation Fieldbus Multiple Discrete Input Block MDI (Multiple Discrete Input)
FF-MDO Foundation Fieldbus Multiple Discrete Output Block MDO (Multiple Discrete Output)
FF-MAI Foundation Fieldbus Multiple Analog Input Block MAI (Multiple Analog Input)
FF-MAO Foundation Fieldbus Multiple Analog Output Block MAO (Multiple Analog Output)
A020104E.ai
To support Fieldbus blocks in other than the above 15 types of Fieldbus blocks as well as custom
blocks, an FF faceplate block called “simplified universal block” is provided for engineering
purposes.
(The functions and operations of simplified universal block vary from those of the above 15
types of FF faceplate blocks. Hereinafter, this document describes the simplified universal block
independently, without including it in the FF faceplate blocks.)
SEE
ALSO For an overview of simplified universal block, see the following:
A3, “Overview of Simplified Universal Block”

n Operation of FF Faceplate Blocks

FF faceplate blocks are function blocks that are executed in an FCS as representations of
Fieldbus blocks. The connection specifications and data item specifications of the Fieldbus
blocks are different from those of the general FCS function blocks. However, they are adjusted
to the specifications of the standard FCS function blocks so that unified engineering can be
performed. The main functions common to the FF faceplate blocks are shown below.
ZRSV SET ZSET
ZP01
P01 RSV
(RCAS_IN) CSV
(RCAS_OUT) (CAS_IN)
RMV
ZRMV
(ROUT_IN)
(ROUT_OUT)
SV
ZP04
P04 (SP)
MV
OUT
(OUT)
IN_V
IN
TRK_VAL TRK_IN_D FF_VAL

ZIN
TIN ZTIN TSI ZTSI BIN ZBIN

A020105E.ai
Figure Function Block Diagram of FF Faceplate Block (Example of FF-PID)
l Block Mode Equalization

Block mode equalization matches the block modes of the Fieldbus block and FF faceplate block.
It transmits mode change commands from the FF faceplate block to the Fieldbus block, and
updates the FF faceplate block side whenever a state transition occurs on the Fieldbus block
side.
l Data Equalization
Data equalization matches an internal parameter of the Fieldbus block and the corresponding to
the item of the FF faceplate block. The internal parameters of the Fieldbus block are managed by
the view object feature available within the Fieldbus device.
l Input Signal Processing

In the input signal processing, data for FCS function blocks other than the FF faceplate blocks
as well as process input data can be referenced via the terminals of an FF faceplate block. If a
connection from a block other than an FF faceplate block is connected to a given input terminal,
the data equalization function dealing with the data item corresponding to that terminal stops and
the result of the input signal processing from the terminal is reflected.
l Alarm Processing
In alarm processing, after receiving an alarm detected by the Fieldbus block, it is converted into
either a process alarm of the FF faceplate block or a system alarm originally sent by the FCS,
and then notifies the HIS of the alarm. In addition, the FF faceplate block itself detects output
open detection processing and communication errors, and notifies the HIS of these detected
items.

l Processing of FF Faceplate Blocks and Fieldbus Blocks
The following table shows a comparison of the processing that takes place in FF faceplate blocks
and Fieldbus blocks.
Table Processing of FF Faceplate Block and Fieldbus Block
FF
Fieldbus
Processing faceplate Specification overview
block
block
Displays the block mode of a Fieldbus
Block mode equalization Y N
Equalization function block.
processing Displays the parameters of a Fieldbus
Data equalization Y N
function block.
Input signal conversion N Y
Input signal The filter in a Fieldbus block can be used
processing Digital filter N Y for a connection between FF faceplate
blocks.
Output velocity limiter N N
Output limiter N Y
Output clamp N Y
Preset manipulated output N N
Output signal
Output value tracking N Y
processing
Output range tracking N N
Manipulated output index Y N
Output signal conversion N N
Auxiliary output N N
Input open check Y Y Converts a Block Alarm in case of an input

from an FF faceplate block. The FF
faceplate block itself detects for input from
Input error alarm check Y Y blocks other than an FF faceplate block.
Input high-high and low-low
N Y
limit check
Input high and low limit check N Y
Input velocity check N N
Alarm Deviation check N Y
processing Output open check N Y Converts a Block Alarm into OOP.
Output high and low limit check N N
Output fail check Y N Detects error and long term power fail of IOM.
Alarm priority Y Y
Alarm detection designation Y Y
Alarm inhibition designation Y N
Checks the status of communication with
Communication error check Y N
devices.
Simulation A simulation mode for setting values of field
Simulation operation N Y
processing devices from the device management tool.
A020106E.ai
Y: Processed
N: Not processed

A2.2 Control Loop and Data Flow

This section explains how the signals of the actual control loop designed by Control
Drawing Builder flow between FF faceplate blocks and Fieldbus blocks.
n Control Loop in Fieldbus

The following figure shows an example where a control loop is closed in a connection between
two Fieldbus blocks.
IN OUT
FF-PID
OUT SET
FF-AI FF-AO
A020201E.ai
Figure Example of Control Loop Closed Only within the Fieldbus

l Signal Flow
The following shows the data flow based on the connection explained above. The types of
communication performed between the FF faceplate blocks and the Fieldbus blocks include only
update by View Object and one-shot writing from the host.
TIP
Note that there will be a slight time difference between the referenced OUT_V value of the FF-AI block or MV
value of the FF-PID block and the actual change of the parameter values in the Fieldbus block in this kind of
connection.
SEE
ALSO For the information about View Object, see the following:
“ View Object” in A1.1, “Glossary”
FF-PID
FF-AI FF-AO
Update by View Object

/one-shot writing
FCS side
Fieldbus side
Update by View Object Update by View Object

IN OUT
/one-shot writing PID /one-shot writing
BKCAL_IN
BKCAL_OUT
CAS_IN
OUT
AI AO
A020202E.ai
Figure Signal Flow when a Control Loop is Closed Only within the Fieldbus

n Control Loop for Performing Cascade Control by FCS

The following explains an example of a control loop where Fieldbus blocks are used for input/
output and the control loop is implemented on an FCS. In this connection, the process input is
obtained via an FF faceplate block, the control computation is performed by a regulatory control
block in FCS, in this example a PID controller, and the result is output to a Fieldbus block via a
second FF faceplate block.
IN OUT
PID
OUT SET
FF-AI FF-AO
A020203E.ai
Figure Control Loop for Performing Cascade Control in the FCS
l Signal Flow
If it is defined to connect a block other than an FF faceplate block to a connection terminal of
an FF faceplate block, Fieldbus input/output (%Z) is automatically assigned to a terminal for
performing input/output at corresponding high speed. Using this connection with %Z, the FF
faceplate block exchanges the process data used for control with the Fieldbus block at high
speed. When such connection is used, the OUT_V terminal of FF-AI will have the same value as
the internal parameter of the actual Fieldbus block, so OUT_V can be used for control.
IN OUT
PID
OUT SET
OUT_V CSV
FF-AI FF-AO
ZOUT ZSET
FCS side
%Z %Z
Fieldbus side
Update through %Z Update through %Z

BKCAL_OUT
/one-shot writing /one-shot writing

CAS_IN
AI AO
A020204E.ai
Figure Signal Flow when Performing Cascade Control in the FCS

n Control Loop with Process Input

If the IN terminal of an FF faceplate block is connected to a function block other than an FF
faceplate block, the FF faceplate block forwards the input processing result to the Fieldbus block.
The Fieldbus block can then execute the control computation using the input signal. Specifically,
this can be used when the Fieldbus performs the control using I/O signals unsupported by the
Fieldbus. In this case, make sure to obtain the I/O signal with the PVI block in order to convert the
input signal correctly.
IN PV IN OUT
%Z PVI FF-PID
SET
FF-AO
A020205E.ai
Figure Control Loop with Process Input
l Signal Flow
The following shows the data flows using the connection example explained above.
IN PV IN
IN_V
%Z PVI FF-PID
ZIN
FF-AO
FCS side
%Z
Fieldbus side
Update by %Z
/one-shot writing
/one-shot writing Receives the input signal of
the FF faceplate block,
executes control computation,
and outputs the result to the AO.
IN OUT CAS_IN
PID AO
BKCAL_IN BKCAL_OUT
A020206E.ai
Figure Signal Flow in a Control Loop with Process Input

n Remote Cascade Control Loop

If an FF faceplate block is to be operated in the RCAS mode, the data for the remote setting
value should be specified in RSV in the same way as for FCS standard function blocks. Within
the FF faceplate block, %Z is connected to the ZRSV terminal of the FF faceplate block for high-
speed data transfer. The RSV data is set to the RCAS_IN terminal of the Fieldbus block via this
ZRSV terminal.
n Remote Output Control Loop

If an FF faceplate block is to be operated in the ROUT mode, the data for the remote setting
value should be specified in RMV in the same way as for FCS standard function blocks. Within
the FF faceplate block, %Z is connected to the ZRMV terminal of the FF faceplate block for high-
speed data transfer. The RMV data is set to the ROUT_IN terminal of the Fieldbus block via this
ZRMV terminal.
n Faceplate Block Monitoring Loop

The output of a faceplate block can be connected to external indicator and trend recorder. The
output signals can be monitored using FF-MAO, FF-MDO and FF-AO blocks.
FF-AI OUT IN FF-PID
Monitoring settings are IN1 FF-MAO

performed on FF-MAO
function block builder.
A020210E.ai
Figure Faceplate Block Monitoring Loop
SEE
ALSO For more information about monitoring settings, see the following:
D1.3, “Modifying an FF Faceplate Block”

n Fieldbus Connection of Enhanced MC/Swicth Instruments

Enhanced MC/Swicth Instruments can be connected to the fieldbus devices via the FF-DI and
FF-DO faceplate blocks for operating and monitoring the fieldbus devices.
l The Enhanced MC/Switch Instrument Blocks for Connecting FF-Blocks

The Enhanced MC/Switch Instrument blocks that can be connected to fieldbus faceplate blocks
are listed in the following table. To apply the enhanced MC/Switch Instrument blocks to the
FCS, it is necessary to register [DIOENH] to [Options] field by choosing [Constant] tab of [FCS
Properties] sheet on System View.
Table Enhanced MC/Switch Instrument Blocks
Type Name
ONOFF-E Enhanced two-position ON/OFF controller block

ONOFF-GE Enhanced three-position ON/OFF controller block
MC-2E Enhanced two-position motor control block
MC-3E Enhanced three-position motor control block
SI-1E Enhanced switch instrument block with 1 input
SI-2E Enhanced switch instrument block with 2 inputs
SO-1E Enhanced switch instrument block with 1 output
SO-2E Enhanced switch instrument block with 2 outputs
SIO-11E Enhanced switch instrument block with 1 input, 1 output
SIO-12E Enhanced switch instrument block with 1 input, 2 outputs
SIO-21E Enhanced switch instrument block with 2 inputs, 1 output
SIO-22E Enhanced switch instrument block with 2 inputs, 2 outputs
SIO-12PE Enhanced switch instrument block with 1 input, 2 one-shot outputs
SIO-22PE Enhanced switch instrument block with 2 inputs, 2 one-shot outputs
A020211E.ai
IN2
OUT
SIO-21E
IN1
OUT OUT SET
FCS
FF-DI FF-DI FF-DO
Fieldbus
Open limit switch
Valve Open/Close
Close limit switch

A020212E.ai
Figure Fieldbus Connection of Enhanced MC/Switch Instrument Blocks

n Examples of Illegal Connection

The following kinds of connections are illegal. They may cause errors during generation, or they
may perform unintended control actions without causing errors; care must be taken to use proper
connections.
l Output from FF Faceplate Blocks

FF faceplate blocks do not perform any output signal processing. An output terminal of an FF
faceplate block must be connected to another FF faceplate block.
IN OUT
FF-PID %Z
OUT
FF-AI
A020207E.ai
Figure Example of Illegal Connection (Where an FF Faceplate Performs Output Directly)
l Non-Terminal Connection between FF faceplate Blocks

A connection between two FF faceplate blocks must be a terminal connection. Other types of
connection are not allowed.
Example: Referencing the PV data of the FF-AI block via the IN terminal of the FF-PID block
FF-AI
PV
IN
FF-PID
A020208E.ai
Figure Example of Illegal Connection (Non-Terminal Connection between FF Faceplate Blocks)
In the connection between the two FF faceplate blocks shown above, the processing is supposed
to be completed by the Fieldbus blocks only. However, in this connection, the PV data of the FF-
AI block is first referenced in the IN terminal processing of the FF-PID block, and then the FF-PID
block sends the value to the PID of the Fieldbus block. The intended control cannot be performed
in such a connection.

l Terminal Connection via a Selector Switch from Output Terminals of FF
Faceplate Blocks
When connecting from output terminals of FF faceplate blocks to a terminal of a function block
other than FF faceplate blocks, a selector switch cannot be used in between. If a selector switch
must be used, reference data from the input terminal side of a function block other than FF
faceplate blocks at the connection destination. When referencing data, auto assignment of %Z is
not performed. Therefore, designate a high-speed update with %Z in Drawing Builder details.
OUT S11 PV S11

S10 IN S10 IN
FF-AI SW-33 PID FF-AI SW-33 PID
S21 S21
OUT PV
FF-AI Connection between FF-AI Can be substituted by
terminals via a selector data reference
switch is not allowed
Check “high-speed update with %Z” in
OUT terminal details
A020209E.ai
Figure Terminal Connection via a Selector Switch is not Allowed
l Connection between Areas of Output Terminals of FF Faceplate Blocks

Areas of output terminals of FF faceplate blocks cannot be connected.

A2.3 Tuning Parameters

This section explains the tuning parameters of FF faceplate blocks.
n Saving Tuning Parameters

Data items in FF faceplate blocks are always overwritten by the internal parameters of the
corresponding Fieldbus blocks. Therefore, when saving the tuning parameters of FF faceplate
blocks, it is only possible to save certain data items dedicated to FCS function blocks, which are
listed in the table below. In order to save internal parameters of Fieldbus blocks, a parameter
upload must be performed by Fieldbus Builder.
SEE
ALSO For more details on uploading parameters by Fieldbus Builder, see the following:
D2.3.6, “Uploading the Block Parameters”
The following table lists the kinds of data that can be saved in each operation.
Table Operation and Data Saved
User operation Data saved
Data items dedicated to FCS function blocks only. For example:
• UAID/SAID
Saving tuning parameter
• Operation mark
• MV index
Internal parameters of Fieldbus devices/Fieldbus blocks can be saved.
Uploading by Fieldbus Builder
Data saved in this way is effective even after replacing Fieldbus devices.
A020301E.ai

<A3. Overview of Simplified Universal Block> A3-1
A3. Overview of Simplified Universal

Block
The simplified universal block is a general-purpose FF faceplate block that only has a
connection function.
Using simplified universal blocks, a control loop containing Fieldbus blocks for which
there are no dedicated FF faceplate blocks corresponding to each type of standard
Fieldbus blocks, or a control loop containing custom blocks can be built using the
Control Drawing Builder in the same manner as a control loop containing other function
blocks.

A3.1 What Is a Simplified Universal Block?

This section describes an overview of simplified universal block.
n Positioning
The positioning of the simplified universal block is described below:
• The simplified universal block is an FF faceplate block that has only the connection function.
• Simplified Universal Blocks can be used to build a control loop containing Fieldbus blocks
for which there are no dedicated FF faceplate blocks corresponding to each type of
standard Fieldbus blocks, or a control loop containing custom blocks created arbitrarily
by a device vendor, in the Control Drawing Builder in the same manner as a control loop
containing other function blocks.
The simplified universal blocks are used only in engineering, and cannot be used for the purpose
of operation and monitoring.
n Function Block Category

The simplified universal block is classified as an FF faceplate block of the regulatory control
blocks. There is no limit to the number of simplified universal blocks that can be defined for one
FCS. The simplified universal blocks, which provide only a connection function, do not use up the
function block resource of the associated FCS.
The model name of the simplified universal block is as follows:
• Model name: FF-SUNV
(The term “FF faceplate block(s)” used in this document will hereinafter refer individually or
collectively to the 15 types of FF faceplate blocks corresponding to the respective standard
Fieldbus block types. The term “custom block(s)” will be used as a general term for Fieldbus
blocks not handled by these 15 types of FF faceplate blocks, as well as for custom blocks created
arbitrarily by a device vendor.)

n Operation of the Simplified Universal Block

Connection between an FF faceplate block and a simplified universal block to which a custom
block is assigned, or between a simplified universal block and an FCS function block, is
implemented by way of connecting the I/O terminals of the respective blocks.
An example of control loop using a simplified universal block is shown below:
IN PV IN OUT
%Z PVI FF-SUNV
SET
FF-AO
A030101E.ai
Figure Example of Control Loop Using a Simplified Universal Block
Engineering data created with each simplified universal block is set in the applicable Fieldbus
device. Only when a simplified universal block is connected to an FCS function block, Fieldbus
I/O (%Z) information is set for use by the control function of the FCS.
Unlike the FF faceplate blocks, the simplified universal blocks cannot operate or monitor the
custom blocks assigned to them.
To operate and monitor a custom block, a desired parameter of the custom block must be
manually and individually assigned to a %Z. This way, the custom block can be operated and
monitored via the FCS function block (PVI, etc.) connected to that %Z.
TIP
• To constantly monitor the I/Os of a simplified universal block, monitor the I/Os of the FF faceplate block or
FCS function block connected to the target simplified universal block.
• The parameters of the Fieldbus block being assigned to a simplified universal block are set using the Edit
Block Parameter dialog box of the Fieldbus Builder.
The simplified universal blocks can be used for the following purposes:
• Register Fieldbus blocks, which need not be operated or monitored but are required in order
to achieve control purposes, using the Control Drawing Builder.
• Build control loops using custom blocks.
The Fieldbus blocks handled by FF faceplate blocks cannot be assigned to simplified universal
blocks. Only custom blocks can be assigned to simplified universal blocks.
IMPORTANT
The simplified universal blocks are not operated or monitored. Exercise caution, because this not
only means that operation and monitoring cannot be performed using simplified universal blocks,
but it also means that process alarms are not displayed as part of the operation and monitoring
function. For reference purposes, messages from Fieldbus devices are stored as historical
messages.

A3.2 Control Loop and Data Flow

In this section, how the control signal of the control loops in the control drawing is passed
among the simplified universal blocks, the FF faceplate blocks and the Fieldbus blocks.
n Foundation Fieldbus Control Loops

For a control loop formed with the Foundation Fieldbus function blocks and a simplified universal
block, the simplified universal block does not communicate with its corresponding fieldbus block,
due to the simplified universal block is not registered in FCS.

n Control Loop Controlled by an FCS with Fieldbus Blocks Used for

Input and Output
The following shows an example of control loop that uses Fieldbus blocks AI and AR (Arithmetic
Blocks) for input and arithmetic processing of input, function block PID of an FCS for control
operation, and Fieldbus block AO for output. The AR block is assigned to simplified universal
block FF-SUNV.
IN OUT IN OUT
FF-SUNV PID
(Act as AR)
OUT SET
FF-AI FF-AO
A030102E.ai
Figure Control Loop Controlled by an FCS with Fieldbus Blocks Used for Input and Output
l Signal Flow
When a connection with an FCS function block is defined in the connection terminal of
a simplified universal block, a Fieldbus I/O (%Z) will be automatically assigned to the
corresponding high-speed transmission I/O terminal. The simplified universal block functions as
the %Z itself.
IN OUT
PID
SET
CSV
FF-AI FF-AO
ZSET
FCS side
%Z %Z
Fieldbus side
Update through %Z Update through %Z

BKCAL_OUT
CAS_IN
OUT
OUT
AI AR AO
IN
(Block assigned to FF-SUNV)

A030103E.ai
Figure Signal Flow in a Control Loop Controlled by an FCS with Fieldbus Blocks Used for Input and
Output

n Control Loop Directly Receiving an Input Signal by a Simplified

Universal Block
To connect an input signal (%Z) of an FCS to a custom block using a simplified universal block,
the input signal must first be received by a PVI block for conversion of the input signal, and then
connect the PVI to the simplified universal block.
An example of this control loop is shown below:
IN PV IN OUT IN
%Z PVI FF-SUNV FF-PID
(Act as AR) OUT
SET
FF-AO
A030104E.ai
Figure Control Loop Directly Receiving an Input Signal by a Simplified Universal Block
l Signal Flow
IN PV
%Z PVI
FF-PID FF-AO
FCS side
%Z
Fieldbus side
Update through %Z
IN
(Block assigned Update by View Object Update by View Object

to FF-SUNV) AR
OUT
IN
OUT CAS_IN
PID AO
BKCAL_IN BKCAL_OUT
A030105E.ai
Figure Signal Flow in a Control Loop Directly Receiving an Input Signal by a Simplified Universal Block

n Control Loop in the RCAS/ROUT Mode

To connect a custom block controlled in the RCAS/ROUT mode to a host block using a simplified
universal block, set parameters RCAS_IN (back-calculation parameter: RCAS_OUT) and
ROUT_IN (back-calculation parameter: ROUT_OUT) as the terminal names of the simplified
universal block, just like other parameters. In addition, a remote mode must be set using the
Function Block Detail Builder in the same manner as with any FF faceplate block.
n Incorrect Connections
The simplified universal blocks are not permitted for use in the connections listed below. They
may cause errors during generation. However, in some cases, the error will not be generated and
a control different from the intended function will be performed without warning.
• Direct output from a simplified universal block to a %Z
• Non-terminal connection between simplified universal blocks
• Terminal connection with an output terminal of a simplified universal block via a selector
switch (SW-33/SW-91)
• Connection between Areas of Terminals of simplified universal blocks

A3.3 Definition of the Simplified Universal Block

This section describes the items to be defined when assigning individual custom blocks
to simplified universal blocks.

A3.3.1 Assigning a Custom Block

The following describes the methods for assigning a custom block to a simplified
universal block.
n Block Assignment
A custom block mounted in a Fieldbus device can be assigned to a simplified universal block in
the following two ways:
• Manual assignment: A control loop is created first, and then a Fieldbus device is registered
and assigned.
• Automatic assignment: A control loop is created after registering a Fieldbus device.
l Manual Assignment
Register a simplified universal block using the Control Drawing Builder. Next, register a Fieldbus
device using the Fieldbus Builder, and then associate the registered simplified universal block
with a custom block using the Control Drawing Builder. The following methods can be used to
associate a custom block:
• Assign a desired custom block by selecting it in the Fieldbus Block List dialog box.
• Directly specify the device tag name and block ID in the Properties of the simplified
universal block.
l Automatic Assignment
If a Fieldbus device is already registered using the Fieldbus Builder, dragging and dropping
a custom block from the Fieldbus Block List dialog box in the Control Drawing Builder will
automatically register a simplified universal block and associate it with the selected custom block.
n Setting Up a Block Tag Name

The simplified universal blocks use a user-defined label. A block tag name cannot be defined for
a simplified universal block.
A user-defined label must be prefixed with a “%%.” A tag without “%%” will generate an error.
Example)
%%FI1001AI

A3.3.2 Correspondence of Connection Terminals, Data Items

and Parameters
The following describes the data items directly connected to the connection terminals of
a simplified universal block, as well as the custom block parameters corresponding to
these terminals.
n Data Items and I/O Parameters Corresponding to the Connection

Terminals
A maximum of 12 connection terminals including input and output terminals can be defined for a
simplified universal block.
l Input Terminals
The following describes the relationship of the input connection terminal name and the custom-
block input parameter connected to that terminal:
• Connection terminal name:
Manually enter a desired custom-block input parameter name.
• Custom-block input parameter to be connected:
This is the terminal name manually entered.
• Data item name:
There are no data items that can be connected directly to the connection terminals of a
simplified universal block. (Input parameter names are directly assigned to Fieldbus I/Os
(%Zs).)
l Output Terminals
The following describes the relationship of the output connection terminal name and the custom-
block output parameter connected to that terminal:
• Connection terminal name:
Manually enter a desired custom-block output parameter name.
• Custom-block output parameter to be connected:
This is the terminal name manually entered.
• Data item name:
There are no data items that can be connected directly to the connection terminals of a
simplified universal block. (Output parameter names are directly assigned to Fieldbus I/Os
(%Zs).)
TIP
To implement data connection between a custom block and an FCS function block, do not use a simplified
universal block. Instead, manually assign the I/O parameters of a custom block to the Fieldbus I/Os (%Zs) using
the Fieldbus Builder and implement data connection between the assigned %Zs and the function block using the
Control Drawing Builder.

A3.3.3 Definition of I/O Parameter Names

The following describes the definition of I/O parameters when making a connection using
n I/O Parameter Names

When a simplified universal block is registered using the Control Drawing Builder, IN and OUT
will be displayed as the default I/O terminal names of the simplified universal block. Change
these default I/O terminal names to the custom-block terminal names (I/O parameter names)
to be assigned. If the I/O parameter names exceed 18 characters, use abbreviations consisting
of 18 or fewer characters. The correspondences between these abbreviations and the formal
parameter names are defined in the Function Block Detail Builder.
If the tentative terminal name such as OUT or IN is not changed, saving or downloading a builder
file in the Control Drawing Builder may result in a generation error.

A3.3.4 Builder Definition Items for the Simplified Universal

Block
The following describes the builder definition items for the simplified universal block.
n Definition Items in the Function Block Detail Builder

The definition items for the simplified universal block in the Function Block Detail Builder are as
follows:
l Basic Tab
• Tag name/model name (display only)
• Tag comment: 24-byte characters
l Fieldbus Tab
• Device tag name (selection only)
• Block ID (selection only)
• Subschedule number: Select from 0 to 4. The default is 1.
l Control Calculation Tab

Remote mode: Select RCAS, ROUT, RCAS+ROUT or No. The Default is “No.”
l Connection Tab
▼ Connection
Specify each I/O terminal (terminal name defined in the Control Drawing Builder) and the name
of the connection destination terminal (tag. parameter (abbreviation)).
l Terminal Name Tab

▼ Terminal name
Specify the correspondence of the abbreviation set up for each I/O parameter exceeding 18
characters, and the formal name of that parameter. The abbreviation will be displayed in the

<A4. Overview of Engineering> A4-1
A4. Overview of Engineering

This chapter describes an overview of Fieldbus engineering.
SEE
ALSO For more details on actual engineering of the Fieldbus, see the following:
Part D, “Fieldbus Engineering”

A4.1 Flow of Engineering

This section explains the flow of Fieldbus engineering.
Fieldbus engineering operation can largely be divided into two types of operations: the
operation that registers devices using Fieldbus Builder, and the operation that registers
control loops using Control Drawing Builder. The order of these two types of operations is
not specifically set. Start either one of these two types of operations first, according to the
convenience of the intended engineering operation.
n Creating Control Loops after Registering Fieldbus Devices

In this procedure, the Fieldbus devices are registered with Fieldbus Builder first, after which the
control loops are created with Control Drawing Builder.
The flow of the engineering is as follows in this procedure:
Start
Creation of ALF111
Operation in
System View
Instantiates the function blocks if required
Download
and determine the capability levels for the
device that supports multiple levels of
capabilites.
For resistering the device, a template or a tool Registration of a device
for copying device definitions can be used. (manual registration
Operation in
or auto registration)
Fieldbus Builder
(device registration)
Initial download is internally performed.
Download (*1)
There are the following two methods for Creation of

creating FF faceplate blocks. an FF faceplate block
• Drag and drop from the Fieldbus Block List
Dialog.
Operation in
• Specify a type in order to create an FF
Connection and Control Drawing Builder
faceplate block, and then specify the
Detailed definition (control loop registration)
Fieldbus block to be connected to it.
The communication can be established Download

after downloading to ALF111, fieldbus devices
and the FCS.
End
A040101E.ai
*1: If the fieldbus device parameters need to be equalized using the Device panel at the later stage, the block parameters should not
be downloaded at this stage. The option [Block parameters are scope of the loading] on the downloading confirmation dialog box
should be unchecked.
IMPORTANT
Close Fieldbus Builder when saving with overwrite or downloading using Control Drawing
Builder. A generation error occurs if related segments are open.
SEE
ALSO For more information about Device Panel, see the following:
D5, “Device Panel”

n Registering Fieldbus Devices after Creating Control Loops

In this procedure, the control loops are created with Control Drawing Builder first, after which the
Fieldbus devices are registered by Fieldbus Builder.
The flow of the engineering is as follows in this procedure:
Start
Creation of ALF111
Operation on
System View
Download
Specify a type in order to create an FF faceplate

block, and then specify the connection Creation of
destination if the Fieldbus block to be connected an FF faceplate block
to is already determined.
Operation on
Connection and
Control Drawing
Detailed definition
Builder
The FF faceplate block becomes an invalid
element if it is not connected to a Fieldbus
block. Download
Instantiates the function blocks if required

and determine the capability levels for the
device that supports multiple levels of Registration of a device
capabilites. (manual registration
For resistering the device, a template or a tool or auto registration)
for copying device definitions can be used. Operation on
Fieldbus Builder
Initial download is internally performed.

Download (*1)
A drawing that includes the FF faceplate block

in the invalid element status is generated and
downloaded, and the FF faceplate block and
Resolve Operation on
the Fieldbus device are connected.
Invalid element System View
The same result can be obtained by
downloading a drawing that includes an invalid
element using Control Drawing Builder.
End
A040102E.ai
*1: If the fieldbus device parameters need to be equalized using the Device panel at the later stage, the block parameters should not
be downloaded at this stage. The option [Block parameters are scope of the loading] on the downloading confirmation dialog box
should be unchecked.
IMPORTANT
Close Fieldbus Builder when resolving an invalid element. A generation error occurs if related
segments are open.
SEE

n Flow of Fieldbus Block Engineering

The following explains the flow of the basic engineering using Fieldbus Builder. The flow of
procedures such as registration and deletion of devices are mainly explained.
l Registering Fieldbus Devices

The following flowchart shows the flow of operation for registering Fieldbus devices.
Start
Start up Fieldbus Builder

from System View.
Are the Fieldbus

Yes devices to be registered conncted No
to the Fieldbus via
the ALF111?
Automatic resistration(*1) Manual resistration(*2)
Download(*3)
End
A040103E.ai
*1: For the fieldbus devices that support block instantiation, after downloading, the block instantiation needs to be performed. While
for the fieldbus devices that support multiple capability levels, the capability levels needs to be selected.
*2: The engineering works for block instantiation and capability level selection of the fieldbus devices may be performed accordingly.
*3: During manual registration, if the fieldbus device is not connected on the fieldbus network, a warning message will occur. In this
case, it is necessary to connect the fieldbus device to the fieldbus network and run initial download to the device again. If the
fieldbus device corresponds to the function block instantiation, the instantiation needs to be performed.
Figure Flow of Operation for Registering Fieldbus Devices
SEE
ALSO • For the detailed explanation on Fieldbus device registration, see the following:
D2.3.3, “Configuring a New Fieldbus System”
• For more information about block instantiation, see the following:
E1, “Fieldbus Block Instantiation”
• For more information about the devices of multiple levels, see the following:
E3, “Devices of Multiple Levels”

l Deleting Fieldbus Devices
The following flowchart shows the flow of operation for deleting a Fieldbus device.
Start
Start up Fieldbus Builder

from System View.
Select a Fieldbus device

to be deleted.
Delete the device.
Updates to the configuration are detected and

Download
only the updated information is downloaded.
Has
a control loop
been created that uses the block Yes
corresponding to the deleted
Fieldbus device?
Do you Yes
No want to delete the
block?
No
Delete the block that became
an invalid element by Control
Drawing Builder.
Register Fieldbus devices
Execute the download

on Control Drawing Builder.
End
A040104E.ai
Figure Flow of Operation for Deleting Fieldbus Devices
SEE
ALSO For the detailed explanation on deleting Fieldbus devices, see the following:
D2.3.4, “Modifying Fieldbus Devices”

l Replacing Fieldbus Devices
The following flowchart shows the flow of operation for replacing a Fieldbus device.
Start
Start up Fieldbus
Builder from System View.
Replace
No
with the same type of
Fieldbus device?
Equalize the replaced

Yes fieldbus devices using
Specify a device tag for Device Panel.
Replace with the correct
the Fieldbus device to replace
Fieldbus device. (*1)
the previous one in advance.
Run [Offline Load] -

[Master Data Download]
End
A040105E.ai
*1: When a device is replaced, if the fieldbus device corresponds to the block instantiation, the instantiation needs to be performed.
Figure Procedure for Replacing Fieldbus Devices
SEE
ALSO • For the detailed explanation on replacing Fieldbus devices, see the following:
D2.4.4, “Replacing Fieldbus Devices”
• For more information about using Device Panel when replacing the fieldbus devices, see the following:
D5.4.5, “Replacing Devices”

l Manual Setting of Fieldbus Input/Output Terminals
The following flowchart shows the procedure for setting the Fieldbus input/output terminal
(%Z) manually. Perform this operation, for instance, when it is desired to access data items in a
Fieldbus at high speed.
Start
Start up Fieldbus
Builder from
System View.
Select a segment
to display the Fieldbus
input/output terminal list.
Define an appropriate
Fieldbus input/output
terminal within the
manual setting range.
Set high-speed designation

for all Fieldbus input/output
terminals.
Updates to the configuration are detected and

Download
only the updated information is downloaded.
End
A040106E.ai
Figure Flow of Operation for Setting Fieldbus Input/Output Terminal Manually
SEE
ALSO For the detailed explanation on manual setting of Fieldbus input/output terminals, see the following:
D2.4.1, “Data Access through Input/Output Terminals”

l Tuning Block Parameters
The following flowchart shows the flow of operation for tuning block parameters. Because the
default values are generally used for the block parameters, this operation is not required.
Start
Start up Fieldbus
Builder from
System View.
Start the block The block parameter edit function

parameter edit function. can be used to edit segments,
Fieldbus devices, or blocks.
Edit the parameter

values.
Updates to the configuration are detected

Download
and only the updated information is
downloaded.
End
A040107E.ai
Figure Flow of Operation for Tuning Block Parameters
SEE
ALSO For the detailed explanation on block parameter tuning, see the following:
D2.4.2, “Tuning Block Parameter Values”

A4.2 State Transition of FF Faceplate Blocks

This section explains the states of FF faceplate blocks and the transitions between them.
An FF faceplate block may be in several states during the engineering process. In the
following, the engineering operation and the block states are explained in detail.
n States of FF Faceplate Blocks

FF faceplate blocks and Fieldbus blocks are connected by “device tag name” and “block ID.” The
operation where an FF faceplate block is connected to a Fieldbus block on a drawing is referred
to as “assigning an FF faceplate block to a Fieldbus block.”
l Assignment States of FF Faceplate Blocks

FF faceplate blocks can be in three states of assignment: “unassigned state,” “assigned state,”
and “assignment invalid state.” FF faceplate blocks become invalid elements if they are in the
unassigned state or in the assignment invalid state.
Drawing
Unassigned state
FF-PID
Assigned state Assignment invalid state
FF-AI FF-AO
Connected by:
(DeviceTagName + BlockID) An assignment destination
has not been registered.
Fieldbus device A040201E.ai
Figure Assignment States of FF Faceplate Blocks
• Assigned state
This is a state where the device tag name and block ID are already defined and the FF
faceplate block is connected to a Fieldbus block. In this state it is possible to communicate
with the FCS and Fieldbus devices.
• Unassigned state
This is a state where the device tag name and block ID are not defined and the FF faceplate
block is not connected to a Fieldbus block. In the engineering, the FF faceplate block
becomes an invalid element and it will not be possible to communicate with the FCS and
Fieldbus devices.
• Assignment invalid state
This is a state where the device tag name and block ID are already defined but the FF
faceplate block is not connected to a Fieldbus block. This status occurs, for instance,
when the Fieldbus block definition is changed by Fieldbus Builder. In this state it will not be
possible to communicate with the FCS and Fieldbus devices.

n Automatic Assignment of FF Faceplate Blocks

Automatic assignment is performed if there are FF faceplate blocks in the unassigned or the
assignment invalid states when the drawing file is downloaded and the following conditions are
met. All automatic assignment are performed in a batch for each FCS when invalid elements are
resolved.
• If the device tag name and block ID have been set for an FF faceplate block, it is connected
with a Fieldbus block with a matching device tag name and block ID at download, and its
state is changed to assigned state.
• If the device tag name and block ID have not been set for an FF faceplate block, it is
connected with a Fieldbus block of the same type, with the same block tag name as the tag
name assigned to the FF faceplate at download, and its state is changed to assigned state.
n Confirmation of Unassigned State and Assignment Invalid State

It can be confirmed whether FF faceplate blocks are in the unassigned or assignment invalid
states by performing the following operation. Warning messages are displayed for all invalid
elements included in the target FCS.
• Select [Error Check] menu from the [FCS] drop-down menu of System View.
• Perform a save with overwrite or download operation using an FCS related builder.
n Transition of Assignment State

The following figure shows how the assignment state of an FF faceplate block can make
transitions. Each of the states in the figure is explained using the corresponding numbers.
4
1 3
5 Assigned
Unassigned
state state
7 8
6
Assigned 9
invalid
state
A040202E.ai
Figure State Transitions of FF Faceplate Blocks
• State 1 is the state where an FF faceplate block is created without designating an

assignment destination. In Function Block Detail Builder, [Device tag name] and [Block ID]
are undefined.
• State 2 is the state where an FF faceplate block is created by designating a nonexistent
assignment destination. In Function Block Detail Builder, [Device tag name] and [Block ID]
are defined to the contents other than the selections displayed during the definition.

• State 3 is the state where an FF faceplate block is created by designating an existing
assignment destination. In Function Block Detail Builder, one of the [Device tag name] and
[Block ID] selections displayed during the definition is selected.
• State 4 represents a transition to an “assigned state.” This state transition is performed
automatically if the tag name matches with the block tag name of an Fieldbus block when
invalid elements are resolved or when the drawing file defining the FF faceplate block is
downloaded.
The state can also be changed to an “assigned state” by defining [Device tag name] and
[Block ID] to existing contents using Function Block Detail Builder and then downloading.
• State 5 is the state where an FF faceplate block in an assigned state is downloaded by
leaving [Device tag name] and [Block ID] blank using Function Block Detail Builder.
• State 6 is the state where an FF faceplate block in an assignment invalid state is
downloaded by leaving [Device tag name] and [Block ID] blank using Function Block Detail
Builder.
• State 7 is the state where an FF faceplate block is downloaded after defining [Device tag
name] and [Block ID] to contents other than listed in the selections using Function Block
Detail Builder.
• State 8 represents a transition to an “assigned state.” This state transition is performed
automatically if [Device tag name] and [Block ID] match with the definitions in the Fieldbus
block when invalid elements are resolved or the drawing file defining the FF faceplate block
is downloaded.
The state can also be changed to an “assigned state” by defining [Device tag name] and
[Block ID] to available selections using Function Block Detail Builder and then downloading.
Alternatively, the state can be changed by matching the device tag name and block ID of the
Fieldbus block with the definitions made with Function Block Detail Builder, and by resolving
invalid elements or downloading the drawing file defining the FF faceplate block.
• State 9 is the state where a Fieldbus device that includes an already assigned Fieldbus
block has been deleted, or the device tag name has been changed. A warning will be
generated if the drawing file defining the FF faceplate block is downloaded in this state.
Or, this state represents the state where the node address of a Fieldbus device that includes
an assigned Fieldbus block has been changed.

A4.3 Software Download to Fieldbus Devices

This section introduces the software download function and describes its positioning.
SEE
ALSO For more information about software download, see the following:
E2, “Software Download”
n What Is Software Download?

Downloading software to the fieldbus device means to use a new software to partially or entirely
replace the existing software (including the communication stack and firmware) in the fieldbus.
The new software can be downloaded form the HIS installed with engineering builders or ENG
station to the fieldbus devices through control bus, FCS and the FF-H1 fieldbus network to
replace the existing software in the fieldbus devices.
Software can be replaced simultaneously on multiple Fieldbus devices. This software download
function can be used when upgrading the software version of Fieldbus devices.
n Positioning of Software Download

The software download function is started in the System View or Device Panel of the engineering
function. When the software replacement is complete on the target device, the information
required for reengineering will be notified to the Fieldbus Builder of the engineering function.
Start
Engineering function
Result is reflected (System View/Device Panel)
Software download
function
Software Data download

download
FF-H1 Fieldbus
Fieldbus device A040301E.ai
Figure Positioning of Software Download

A4.4 Template
When perform fieldbus engineering works, the prepared templates can be used for
registering the fieldbus devices and then initially downloading the devices. How to use
the templates will be explained as follows.
n Template
A template is a file that holds the user-specified block parameter values and the information
about the equalized parameters of all the blocks. A file likes is referred to as a template file.
Multiple devices can use the contents kept in a template file. Since the user-specified parameters
can be reutilized, registration of the devices and initial downloading to the devices can be
performed more efficiently.
n Template File
A template file can be created by users if required for the engineering works. What components
in a template file and how to create a template file will be explained as follows:
l Creating Template File

A template file is created in accordance with the Vendor ID, Device Type and Device Revision
Number of the fieldbus device. Moreover, for the same fieldbus device, multiple templates can be
created.
l File Name
A template file is identified by the file name. The file name can be automatically assigned,
however, a part of the file name is user-definable. Moreover, the location for holding the template
file is also user-definable.
l Information Held in a Template

A template file contains equalization directions for all block parameters. Moreover, the user
default values are also saved in the template file.
l Equalization Direction
Equalizing the block parameters in the project database and the block parameters in the fieldbus
devices is referred to as equalization.
When running equalization, to use the block parameters in the project database to overwrite the
block parameter in the fieldbus device or vise versa need to be determined. This is referred to as
equalization direction.
SEE
ALSO • For more information about the template files, see the followings:
“n Create Template File Dialog Box” in D2.4.9, “Create and Use Template on Fieldbus Builder”
“n Create Template File Dialog Box” in D5.4.8, “Create or Open Template File on Device Panel”
• For more information about the location of the template files, see the followings:
“l Destination Directory of Template File” in “n Project Common” of D2.3.1, “Environment Settings”

n Fieldbus Device Engineering with Templates
l For Registering Devices

For applying the same model of field device with the same vendor ID, device type and device
revision number to different process measurements of pressure, flow and level, multiple
templates can be created. One of the prepared templates can be used for registering the field
device.
l For Equalization and Initial Downloading

The initial downloading will be performed based on the selected template.
Moreover, equalization with the project database will also be performed according to the selected
template, since what to be downloaded to the fieldbus device and what to be uploaded from the
fieldbus device are all scripted in the template.
n Using Templates
In this section, how to use the templates will be explained.
l How to Use a Template

Creating or reading a template file can be performed on either the fieldbus builder or on Device
Panel. The figure below illustrates the relationship between the templates and fieldbus builder
and the Device Panel.
Template File :
Created for the devices
with same Vendor ID, Device Type,
and revision number
Device Panel Fieldbus Builders
Apply Apply
Equalization
Create Directions Create
Block
Parameter
Values : Operation
: Data Flow
A040401E.ai
Figure Relationship of Fieldbus Builder, Device Panel and Templates
l Using Template on Fieldbus Builder

A template can be read or created on the fieldbus builder. When registering a field device or
initially downloading to the field device, the information kept in the template will be applied.
l Using Template on Device Panel

A template can be read or created on Device Panel. When the Device addition is performed, the
information kept in the template will be applied.
l Template Applicable Devices

A template can be applied to the devices with the same vendor ID, device type and revision
number. Moreover, for one device, multiple templates can be created to handle different
implementations.

l Specify Default Template
A default template can be specified for a fieldbus device so that when registering the fieldbus
device on the fieldbus builder or initially downloading to the fieldbus device, the information kept
in the default template will be read. Also when registering a new fieldbus device on Device Panel,
the Device panel will use the default template for reading and keeping the information of the new
fieldbus device.
Creating and designating a default template can be performed on the dialog box used for
creating the template. Moreover, when reading a template, the template can be selected on the
dialog box for selecting the template.
SEE
ALSO For more information about designating the default templates, see the followings:
“n Creating Template on Fieldbus Builder” in D2.4.9, “Create and Use Template on Fieldbus Builder”
“n Create Template File Dialog Box” in D5.4.8, “Create or Open Template File on Device Panel”
l Procedure of Creating Template

The procedure for creating a template on fieldbus builder or on Device Panel is as follows:
Procedure on fieldbus builder Procedure on Device Panel
Start the fieldbus builder Start Device Panel and

and open the window open the dialog box for
for editing the template. displaying the information.
Edit the user default Edit the user default

values. values.
Decide the equalization Decide the equalization

directions. directions.
Create a Template Create a Template
End End
A040402E.ai
Figure Flow Chart for Creating Template
SEE
ALSO • For more information about creating a template on the fieldbus builder, see the following:
D2.4.9, “Create and Use Template on Fieldbus Builder”
• For more information about creating a template on Device Panel, see the following:
D5.4.8, “Create or Open Template File on Device Panel”

Blank Page
TocB-1
CENTUM VP
CONTENTS
PART-B FCS Fieldbus Support
B1. FCS Fieldbus Compatibility...................................................................B1-1
B1.1 Fieldbus Data Access..................................................................................... B1-2
B1.2 Operations at the Occurrence of an Abnormality and at Recovery ........ B1-6
B1.2.1 Overall System Operations at the Occurrence of an Abnormality
and at Recovery................................................................................B1-7
B1.2.2 FCU Operations at the Occurrence of an Abnormality and
at Recovery.....................................................................................B1-11
B1.2.3 ALF111 Operations at the Occurrence of an Abnormality and
at Recovery.....................................................................................B1-13
B1.2.4 Fieldbus Device Operations at the Occurrence of an Abnormality
and at Recovery..............................................................................B1-15
B1.3 Making FCSs Redundant............................................................................. B1-17
B1.4 Download Operations................................................................................... B1-22
B2. FF Faceplate Block Common Operations............................................B2-1
B2.1 Data Equalization Processing....................................................................... B2-2
B2.1.1 Referencing the Standard Block Parameters...................................B2-4
B2.1.2 Update Using Fieldbus I/O (%Z).......................................................B2-5
B2.1.3 Reflecting the Data Value Change...................................................B2-8
B2.2 Block Mode Processing................................................................................. B2-9
B2.3 Abnormality Detection Operations at FF Faceplate Block....................... B2-12
B2.4 Input Signal Processing............................................................................... B2-13
B2.5 Output Signal Processing............................................................................ B2-14
B2.6 Alarm Processing......................................................................................... B2-15
B2.7 Operation during I/O Simulation................................................................. B2-19
B2.8 Correspondence among Connecting Terminals, Data Items, and
Parameters.................................................................................................... B2-20
B2.9 Builder Definition Items of FF Faceplate Blocks....................................... B2-26

TocB-2
B3. Individual FF Faceplate Block Operation.............................................B3-1
B3.1 FF AI Block (FF-AI).......................................................................................... B3-2
B3.2 FF DI Block (FF-DI).......................................................................................... B3-6
B3.3 FF Control Selector Block (FF-CS).............................................................. B3-10
B3.4 FF PID Controller Block (FF-PID)................................................................ B3-14
B3.5 FF Ratio Set Block (FF-RA).......................................................................... B3-20
B3.6 FF AO Block (FF-AO).................................................................................... B3-25
B3.7 FF DO Block (FF-DO).................................................................................... B3-29
B3.8 FF Splitter Block (FF-OS)............................................................................. B3-33
B3.9 FF Signal Characterizer Block (FF-SC)....................................................... B3-37
B3.10 FF Integrator Block (FF-IT)........................................................................... B3-41
B3.11 FF Input Selector Block (FF-IS)................................................................... B3-46
B3.12 FF Multiple DI Block (FF-MDI)...................................................................... B3-51
B3.13 FF Multiple DO Block (FF-MDO).................................................................. B3-55
B3.14 FF Multiple AI Block (FF-MAI)...................................................................... B3-60
B3.15 FF Multiple AO Block (FF-MAO).................................................................. B3-65

<B1. FCS Fieldbus Compatibility> B1-1
B1. FCS Fieldbus Compatibility

The Fieldbus system performs data communication between the Fieldbus device and the
FCS.
The FCS reads data on the Fieldbus device as Fieldbus input (%Z), and writes it onto the
Fieldbus device as Fieldbus output (%Z) after processing it with the FCS block.
This chapter explains the FCS operations in the Fieldbus system.

B1.1 Fieldbus Data Access

The Fieldbus data access function references and sets data on the Fieldbus device via the
FOUNDATION fieldbus (FF-H1) communication module (ALF111).
This section explains the data access method, the data access communication methods,
and the communication timing of each communication method in Fieldbus data access.
n Data Access Method

With the Fieldbus data access function, FCS Fieldbus I/O (%Z) is assigned to the I/O terminals
and the block parameters that are contained in the Fieldbus block within the Fieldbus device.
Then, this function accesses the data on the Fieldbus via the assigned Fieldbus I/O. The
following figure shows a mechanism of data access on the Fieldbus device from the FCS:
FCS
FCU
IN OUT
PID
SET
FF-AI FF-AO
Tracking
Reading data I/O image Writing data
Input Readback Writing

data data data
ALF111 Instantaneous
ESB bus type data area
Input Readback Writing

data data data
Fieldbus
AI AO
Fieldbus device
B010101E.ai
Figure Mechanism of Fieldbus Data Access

n Communication Methods
The communication methods for accessing data on the Fieldbus are classified into two main
categories: publisher/subscriber type communication and client/server type communication.
l Publisher/Subscriber Type Communication

On Fieldbus Builder, the communication period of periodically communicated Fieldbus blocks
and the execution time schedule of Fieldbus blocks can be defined.
This method is used to perform communication according to a Fieldbus schedule created with
builder.
l Client/Server Type Communication

This method is used to perform communication using the background communication time that is
a spare time on a Fieldbus schedule.
l Details on Each Communication Method

The above communication methods are further classified into the following classification shown
in the table below. The accessible data and the communication timing on the Fieldbus vary
depending on the communication method.
Table Classification of Communication Methods
Example of Communication method

Classification Description data Input or output Remark
(parameters) Output
readback
Publisher/Subscriber Reads the output terminal data of the OUT of AI
P/S - (*1)
type input Fieldbus block into the FCU. block, etc.
Publisher/Subscriber Sets the FCU’s output data to the
CAS_IN, etc. P/S P/S (*1)
type cascade output cascade input of the Fieldbus block.
Sets the FCU’s output data to the input
terminal of the Fieldbus block.
Publisher/Subscriber TRK_IN_D,
Reads the Fieldbus device value via C/S P/S (*1)
type output etc.
Client/Server type communication before
starting output for output value tracking.
Client/Server type remote Sets the FCU’s output data to the remote
RCAS_IN, etc. C/S C/S (*1)
cascade output cascade input of the Fieldbus block.
Reads the block parameter values of the ALARM_SUM,
Client/Server type input C/S - (*2)
Fieldbus block into the FCU. etc.
Sets the FCU’s output data to the block MODE_BLK,
Client/Server type output C/S C/S (*2)
parameters of the Fieldbus block. etc.
B010102E.ai
*1: This is used when connection has been performed with Control Drawing Builder.
*2: This is used when the extended parameters have been defined with Function Block Detail Builder, or when %Z has been
manually set with Fieldbus Builder.
P/S: Publisher/Subscriber type communication
C/S: Client/Server type communication

n Communication Timing
The communication timing when accessing data on the Fieldbus varies depending on the
communication method as follows:
l Communication Timing of Publisher/Subscriber Type Communication

The Publisher/Subscriber type communication is executed by synchronizing with the execution
timing of the Fieldbus block according to the Fieldbus schedule. Since this communication
method has a high priority on the Fieldbus, a periodic characteristic of the communication timing
is guaranteed.
l Communication Timing of Client/Server Type Communication

The Client/Server type communication normally allows one communication per second for one
Fieldbus device. This communication method features the following characteristics:
• In addition to a Client/Server type communication, another communication is also performed
in order to control the Fieldbus communication line in the background communication
time in which the Client/Server type communication is performed. As a result, it has a low
communication priority.
• The time it takes the server (Fieldbus device) to return a response for a request made from
a client (ALF111) depends on the performance of the Fieldbus device.
• The greater the number of requested data for one Fieldbus device, the longer the update
cycle per data becomes.
Based on the above reasons, this communication method does not guarantee a periodic
characteristic of the communication timing.
The following shows a Fieldbus schedule for a structure as indicated by the previous figure of
“Mechanism of Fieldbus Data Access.” The following AI block and AO block represent the AI
block and AO block in the Fieldbus device.
Publisher/Subscriber type communication
Macrocycle
Execution of AI block
Communication (AI → ALF111)
Communication (ALF111 → AO)
Execution of AO block
Communication (AO → ALF111)
Background communication time

B010103E.ai
Figure Example of Fieldbus Schedule
SEE
ALSO For more explanation on the macrocycle, see the following:
“n Macrocycle” in A1.1, “Glossary”

n Data Type
Fieldbus block data is processed in the FCS via the ALF111. The following table lists the
correspondence between the data types defined by the Fieldbus Foundation specifications and
the corresponding data types of the ALF111.
Table Correspondence between Data Types
Data type of ALF111 Data type of Fieldbus Foundation specifications
I8 Integer8
U8 Unsigned8
I16 Integer16
U16 Unsigned16
I32 Integer32
U32 Unsigned32
F32 Floating Point
F32S, F32SR Value & Status-Floating Point Structure
DS Value & Status-Discrete Structure
B010104E.ai

B1.2 Operations at the Occurrence of an

Abnormality and at Recovery
When an abnormality occurs in the Fieldbus system, each device in the Fieldbus system
performs various operations for recovery according to the type and location of an
abnormality.
This section explains the following operations at the occurrence of an abnormality and at
recovery.
• Overall system operations at the occurrence of an abnormality and at recovery
• FCU operations at the occurrence of an abnormality and at recovery
• ALF111 operations at the occurrence of an abnormality and at recovery
• Fieldbus device operations at the occurrence of an abnormality and at recovery

B1.2.1 Overall System Operations at the Occurrence of an

The following explains the overall system operations to handle abnormalities such as
power failure and breakdown and to perform recovery.
n Overall System Operations

The following table lists the operations that are performed when an abnormality occurs as well as
the recovery operations of each of the FCU, the ALF111 and the Fieldbus device.
Table Overall System Operations at the Occurrence of an Abnormality and at Recovery
Power Operation when an abnormality occurs Recovery operation

failure/breakdown Fieldbus Fieldbus
mode FCU ALF111 FCU ALF111
device device
Follows the Follows the fault Performs fallback Performs fault
Both CPU Starts
- fallback operation state operation recovery state recovery
operations stop initialization.
specification. specification. operation. operation.
Starts Fieldbus
System power Starts ALF111
- - - Starts FCS device
failure initialization.
initialization initialization.
Follows the Follows the fault /resumes FCS Performs fallback Performs fault
FCU power failure
- fallback operation state operation operation. recovery state recovery
(*1)
specification. specification. operation. operation.
CPU control Continues Continues Continues Continues Continues Continues
privilege change operation. operation. operation. operation. operation. operation.
Performs node Follows the Performs node Performs fallback
Both SB301
long stop fallback operation long stop recovery
operations stop(*2)
operation. specification. operation. operation.
Local node power Starts ALF111
Performs node - Performs node
failure initialization.
long stop/node long stop/node
Communication instantaneous instantaneous
error with direct stop operation. stop operation.
coupled node Follows the Performs fallback
fallback operation Follows the fault recovery Performs fault
Performs node specification. Performs node operation.
Both EB401 state operation state recovery
long stop long stop
operations stop specification. operation.
operation. operation.
Remote node Starts ALF111
Performs node - Performs node
power failure initialization.
long stop/node long stop/node
Communication instantaneous Follows the instantaneous Performs fallback
error with remote stop operation. fallback operation stop operation. recovery
node specification. operation.
ALF111 operation Performs IO error Performs IO error Starts ALF111
-
stop(*3) handling operation. recovery operation. initialization.
Starts Fieldbus
Fieldbus power
- device
failure
initialization.
Performs Performs Performs Performs
Communication Follows the fault Performs fault
Fieldbus device Fieldbus device Fieldbus device Fieldbus device
error with Fieldbus state operation state recovery
error handling error handling error recovery error recovery
device specification. operation.
operation. operation. operation. operation.
Fieldbus device Starts Fieldbus
breakdown/ - device
maintenance initialization.
B010201E.ai
*1: In the case of the ALF111 installed to the FCU of the FFCS, power failure/breakdown mode “FCU power failure” does not exist.
The FCU power failure in this case is equivalent to power failure/breakdown mode “System power failure.”
*2: This mode is not available in FFCS.
*3: In a duplex configuration, the operations of the both ALF111 modules stop.
-: No operation

The meanings of various operations in the previous table are as follows:
l Following the Fallback Operation Specification

The output operation is determined by the specification of the operation when an abnormality
occurs and also by the time when an abnormality occurs. The input operation continues.
SEE
ALSO For more details on the fallback operation, see the following:
B1.2.3, “ALF111 Operations at the Occurrence of an Abnormality and at Recovery”
l Continuing Operation
Continues I/O operation.
l Performing when I/O Error Occurs/ I/O Error Recovered

Follows the FCU or FF faceplate block operations at the occurrence of an I/O error and at
recovery.
SEE
ALSO For more details on the operations performed at the occurrence of an I/O abnormality and at recovery, see the
following:
“n Operations at the Occurrence of an ALF111 Abnormality and at Recovery” in B1.2.2, “FCU Operations
at the Occurrence of an Abnormality and at Recovery”
l Starting ALF111 Initialization

Reads new data of the Fieldbus device in input operation, and tracks the Fieldbus device values
in output operation.
l Performing Fieldbus Device Error Handling Operation/Error Recovery

Operation
Performs operations when a power failure occurs in the Fieldbus device. Follows the FCU or FF
faceplate block operations at the occurrence of a Fieldbus device abnormality and at recovery.
l Following the Fault State Operation Specification

Follows the Fieldbus block operation when a communication error is detected. However, if the
ALF111 does not fall back, the operation will continue.
SEE
ALSO For more details on the fault state operation of the Fieldbus devices, see the following:
“n Operation in the Fault State” in B1.2.4, “Fieldbus Device Operations at the Occurrence of an
Abnormality and at Recovery”

l Starting Fieldbus Device Initialization
This refers to an operation when the Fieldbus device is started by powering ON.
SEE
ALSO For more details on the operation when starting the Fieldbus devices, refer to the Fieldbus device manual.
l Starting FCS Initialization/Resuming FCS Operation
SEE
ALSO For more details on staring the FCS initialization and resuming the FCS operation, see the following:
B2, “Start Operations” in CENTUM VP Reference, FCS Basics (IM 33M01A30-40E)
l Performs Node Long Stop/Node Instantaneous Stop Operation
SEE
ALSO For more details on performing the node long stop/node instantaneous stop operation, see the following:
B3, “Operation at Error Occurrence” in CENTUM VP Reference, FCS Basics (IM 33M01A30-40E)

n Devices Affected by Abnormalities

The following table shows the devices, located below the SB301, which are affected by
abnormalities such as a power failure or a breakdown occurring in the FCS.
Table Devices Affected by Abnormalities
Power failure/breakdown mode Affected devices
Both CPU operations stop All IOMs (ALF111s) and all Fieldbus devices under the FCU
System power failure All IOMs (ALF111s) and all Fieldbus devices under the FCU
FCU power failure(*1) All IOMs (ALF111s) and all Fieldbus devices under the FCU
CPU control privilege change Not affected.
Both SB301 operations stop(*2) All IOMs (ALF111s) and all Fieldbus devices under the FCU
The IOM (ALF111) of the applicable node, and the IOM (ALF111) and Fieldbus
Local node standalone power failure
device of the remote node under the EB401 mounted in the applicable node
The IOM (ALF111) of the applicable node, and the IOM (ALF111) and Fieldbus
Communication error with local node
device of the remote node under the EB401 mounted in the applicable node
Both EB401 operations stop The IOMs (ALF111s) and Fieldbus devices of all nodes under the applicable EB401
Remote node power failure All IOMs (ALF111s) and Fieldbus devices under the applicable node
Communication error with remote node All IOMs (ALF111s) and Fieldbus devices under the applicable node
ALF111 operation stop All Fieldbus devices under the applicable ALF111
Fieldbus power failure All Fieldbus devices of the applicable segment
Communication error with Fieldbus
All Fieldbus devices of the applicable segment
device
Fieldbus device Fieldbus devices that have the blocks of control loop related to the applicable
breakdown/maintenance Fieldbus device
B010202E.ai
*1: In the case of the ALF111 installed to the FCU of the FFCS, power failure/breakdown mode “FCU power failure” does not exist.
The FCU power failure in this case is equivalent to power failure/breakdown mode “System power failure.”
*2: This mode is not available in FFCS.

B1.2.2 FCU Operations at the Occurrence of an Abnormality

and at Recovery
This section explains the operations of the Field Control Unit (FCU) to handle
abnormalities such as power failure and breakdown and to perform recovery.
n FCU Process I/O when Starting the FCS

SEE
ALSO For more details on the FCU process I/O when starting the FCS, see the following:
B2.1.4, “Status of FCS at Start Operation” in CENTUM VP Reference, FCS Basics (IM 33M01A30-40E)
n Operations at the Occurrence of a Node Abnormality and at Recovery,

and Process I/O
The following table shows the operations of the FCU when an node (remote node or local node)
abnormality such as power failure or breakdown occurs as well as the recovery operations.
Table FCU Operations at the Occurrence of a Node Abnormality and at Recovery
When abnormal When recovering
Judgment
of node FF faceplate
Fieldbus I/O Fieldbus I/O FF faceplate
abnormality block operation
data status data status block operation
(*1)
Reads a new input
Node long
value, and tracks Tracks the Fieldbus
stop Data status is BAD. CNF
the Fieldbus device device value.
operation
value for output.
Node Retains the previous
Retains the previous Retains the previous
instantaneous input value, and Resumes output and
value, and the data PV value, and
stop outputs the previous continues operation.
status is NRDY. continues operation.
operation output value again.
B010203E.ai
*1: The operation of the FCS function block that is connected with the FF faceplate block is as follows:
. • Detects an IOP and performs MAN fallback if the FCS function block is connected with the input side.
. • Sets IMAN if the FCS function block is connected with the output side.
The following table lists the ALF111 Fieldbus I/O when recovering from a node (direct coupled
node or remote node) abnormality.
Table ALF111 Fieldbus I/O when Recovering from a Node Abnormality
Input/Output Node long stop operation Node instantaneous stop operation
Retains the previous value until FF-H1 Retains the previous value until FF-H1
Fieldbus input
communication of the ALF111 resumes. communication of the ALF111 resumes.
Resumes output after tracking the Resumes output after tracking the
Fieldbus output
Fieldbus device value. Fieldbus device value.
B010204E.ai

n Operations at the Occurrence of an ALF111 Abnormality and at

Recovery
The following table lists the FCU operations that are performed when an abnormality such as
power failure or breakdown occurs in the ALF111, as well as the recovery operations.
Table FCU Operations at the Occurrence of an ALF111 Abnormality and At Recovery
Description
of FF faceplate
(*1)
Reads a new input
I/O value, and tracks Tracks the Fieldbus
Data status is BAD. CNF
abnormality the Fieldbus device device value.
value for output.
B010205E.ai
n Operations at the Occurrence of a Fieldbus Device Abnormality and at

Recovery
The following table lists the FCU operations that are performed when an abnormality such as
power failure or breakdown occurs in a Fieldbus device, as well as the recovery operations.
Table FCU Operations at the Occurrence of a Fieldbus Device Abnormality and at Recovery
Description
of FF faceplate
(*1)
Reads a new input
Fieldbus
value, and tracks Tracks the Fieldbus
device Data status is BAD. CNF
the Fieldbus device device value.
abnormality
value for output.
B010206E.ai
n Recovery Operation from Remote Node Power Failure

SEE
ALSO For the recovery startup time from a power failure of the ER bus slave interface module (EB501) of a remote
node, see the following:
B2.3, “Start Operation of KFCS2, KFCS and FFCS Nodes” in CENTUM VP Reference, FCS
Basics (IM 33M01A30-40E)

B1.2.3 ALF111 Operations at the Occurrence of an

This section explains the operations of the FOUNDATION fieldbus (FF-H1) communication
module (ALF111) to handle abnormalities such as power failure and breakdown and to
perform recovery.
n Operation at ALF111 Restart

The following operation will immediately be performed after the ALF111 recovers from the power
failure status:
• Input operation: Reads new data of the Fieldbus device.
• Output operation: Starts output after tracking the Fieldbus device data.
n ALF111 Fallback Operation when an Abnormality Occurs in a Higher

System
When an abnormality occurs in a system higher than the ALF111, such as the CPU or the FCU in
the FCS, the ALF111 operates according to the fallback specification.
l With Fallback
If an access from the FCU becomes shorter than the “line loss setting time (4 seconds)” because
the FCU’s CPU operation has stopped or because of node abnormality, the ALF111 performs a
fallback operation.
The fallback operations that are performed by the ALF111 are as follows:
• Stops output communication and continues input communication.
• Continues LAS.
When the Fieldbus device receives the output data for which update has been stopped for
the number of times exceeding the count specified with “High-Limit Counts to ignore BNU
Communication Error,” it will be placed in the fault state.
SEE
ALSO • For more details on the fault state, see the following:
• For information about LAS, see the following:
“n LAS (Link Active Scheduler)” in A1.1, “Glossary”
l Without Fallback
The ALF111 performs the same operation as when normal. However, the output value set by the
FCU before the occurrence of an abnormality in the CPU or the FCU will be used as the output
value of the ALF111.

n Operation when the ALF111 Breaks Down

When a breakdown occurs in the ALF111, the ALF111 stops all communications including input
and output.
In this case, the Fieldbus device will be placed in the fault state.
SEE
ALSO For more details on the fault state, see the following:
n Operations at the Occurrence of a Fieldbus Device Abnormality and at

Recovery
ALF111 Operations at the Occurrence of a Fieldbus Device Abnormality and at Recovery
Table FCU Operations at the Occurrence of an ALF111 Abnormality and At Recovery
Description When abnormal Immediately after recovery

of Operation for Operation for
abnormality Operation for FCU Fieldbus device Operation for FCU
Fieldbus device
Reads new data for
Reads a new value
Fieldbus input values, and
Stops I/O for input, and tracks
device Data status is BAD. tracks the Fieldbus
communication. the Fieldbus device
abnormality device values for
value for output.
output values.
B010207E.ai

B1.2.4 Fieldbus Device Operations at the Occurrence of an

This section explains the operations of the Fieldbus device to handle abnormalities such
as power failure and breakdown and to perform recovery.
The Fieldbus device generally operates in accordance with the Fieldbus Foundation
specifications. This section explains the operations of the Fieldbus device at the
occurrence of an abnormality and at recovery that are in accordance with the Fieldbus
Foundation specifications.
SEE
ALSO Some Fieldbus devices may contain device vendor specific functions. In this case, these Fieldbus devices may
not entirely operate according to the FF specifications.
For more details on the Fieldbus device operation, refer to the Manual of each Fieldbus device used.
n Operations when Restarting the Fieldbus Device

The following table lists the Fieldbus device restart operations such as when the Fieldbus power
recovers from a power failure.
Table Operations of Fieldbus Device when Restarting
Operation Description
Sets to either AUTO or MAN. If the mode set in MODE_BLK.Target is
Fieldbus block mode CAS, RCAS, or ROUT, it transits to the applicable mode after cascade
initialization with the higher system is completed.
Input value Reads a new value.
Output value Uses the previously set value or the FSTATE_VAL value. (*1)
B010208E.ai
*1: For the output value of an output block such as the AO block, either the previous value or FSTATE_VAL can be selected by
setting when restarting the Fieldbus device.
It may take about 10 to 30 seconds until the restart operation of a Fieldbus device is completed.
For more details, refer to the Manual of each Fieldbus device used.

n Operation in the Fault State

When the Fieldbus block detects an abnormality in an input terminal (IN or CAS_IN), it uses one
of the following AO block output values according to the setting of the Fieldbus device:
• Retains the output value.
• Changes the output value to the set value (FSTATE_VAL).
The following figure shows an example of Fieldbus device operation within the Fieldbus device in
the fault state:
Type A Type B
ALF111 output or ALF111 output or

upstream Fieldbus upstream Fieldbus
block block
Notifies
A communication "Initiate Fault State." A communication
error has occurred. error has occurred.
BKCAL_OUT CAS_IN BKCAL_OUT CAS_IN
OUT OUT
AI PID AO AO
IN CAS_IN
BKCAL_IN BKCAL_OUT
Transits to the fault state by Transits to the fault state

notification from the higher block by communication timeout.
B010209E.ai
Figure Example of Fault State Operation
In the above type A example, because an input to CAS_IN of the PID block resulted in an error,
“Initiate Fault State” (instruction to transit to the fault state) was notified to the AO block. Upon
receiving this notification, the AO block transited to the fault state.
Whether or not “Initiate Fault State” is notified is determined by the STATUS_OPTS setting
the PID block. If this setting has been made to not notify “Initiate Fault State,” control can be of
continued with the AI, PID and AO blocks.
In the above type B example, because the communication to CAS_IN of the AO block timed out,
the AO block transited to the fault state.

B1.3 Making FCSs Redundant

The FCS adopts a redundant method that makes each section duplex in order to achieve
high reliability of the system. This section explains the duplexed FOUNDATION fieldbus
(FF-H1) communication modules (ALF111s), which is one of FCS redundancy features
compatible with Fieldbus.
SEE
ALSO For other redundancy methods of the FCS, see the following:
B4.2, “Dual-Redundant Architecture of KFCS2, KFCS and FFCS” in CENTUM VP Reference, FCS Basics
(IM 33M01A30-40E)
n Duplexing ALF111s
Two neighboring ALF111s can be made duplex. In the duplexed ALF111s, one in the odd slot is
called master and the other in the even slot is called slave. Mount the two ALF111s so that the
slot number on the master side becomes smaller than the slot number on the slave side.
KFCS
ALF111 ALF111
(master) (slave)
Segment 1
Segment 2
Segment 3
Segment 4
External Fieldbus
power supply
B010301E.ai
Figure Image Diagram of Duplexed ALF111s
Dual-redundantly configured ALF111 modules switch the communication from one to the other.

l Control Privilege in ALF111 Duplexing
The control privilege in ALF111 duplexing signifies the right to execute I/O data communication
for Fieldbus devices. The ALF111 with the control privilege and the ALF111 without the control
privilege are called control side and standby side, respectively.
l Switching Mechanism of the Control Privilege

Duplexing control privilege can be switched when the FCU issues a switch instruction to the
ALF111. The FCU always monitors the status of the ALF111, and issues a switching instruction
based on the switching standard of the control privilege shown in the table below.
Table Switching Standard of the Control Privilege
Description of breakdown Switching Remark
Abnormality on the field side Does not switch.
Switches according to the settings
Front connector disconnection Switches by default.
of the ALF111 properties. (*1)
Configuration error (*2) Switches.
Hardware breakdown Switches.
B010303E.ai
*1: Only setting on KFCS, FFCS, RFCS5.

*2: When the load data from a builder is abnormal from System View.
l Detection of Front Connector Disconnection

If the front connector of the ALF111 is disconnected, the control privilege switches by the default
setting for ALF111 duplexing.
When ALF111 duplexing is specified and “Front connector disconnection check” is set to “No” in a
command line of ALF111 Properties in System View, the front connector disconnection will not be
detected and the control privilege of the ALF111 will not switch.
IMPORTANT
The ALF111 judges the presence of the front connector from the external Fieldbus power supply
status. If the external Fieldbus power supply is not used, the specification of “Front connector
disconnection check” will be invalid. Therefore, the control privilege will not switch even if the front
connector is disconnected.

l Detecting Abnormalities in the Communication Route between ALF111 and
Fieldbus Devices
▼ Switch ALF111 modules upon Communication errors
For KFCS2, FFCS and RFCS5 types of FCSs, switching the fieldbus communication from one
module to the other when an error is detected in the communication route to the fieldbus devices
can be specified.
With this specification, the control right switching between the ALF111 modules will be triggered
by the communication route abnormalities.
On the FCS Constant Builder and ALF111 Properties Sheet of System View, this setting needs to
be specified.
• On FCS Constant Builder
The action for switching the ALF111 module needs to be specified on FCS Constant Builder.
Find the setting item of [Switch the dual-redundant ALF111 upon communication errors] in
the Detailed Settings area.
[Valid]: Switches to another ALF111 module when fieldbus communication error is detected
on the communication route to the fieldbus device. This is the default setting when the FCS
is newly created.
[Invalid]: Does not check the communication error on the communication route to the
fieldbus device.
If the FCS is created by CENTUM CS 3000 R3.07 or an earlier version and to be upgraded
to CENTUM VP, this is default setting.
• On ALF111 Properties Sheet
On ALF111 properties sheet, the command line for the module can be specified. The
command line is valid for the whole module.
The time unit of command parameter for the detection interval is minute. The module will
probe the error on the communication route to the fieldbus devices at this interval. For
dual-redundantly configured modules, when one module is set not to detect the error on the
communication route, this setting will be applied to both the modules.
IMPORTANT
The communication errors occurred on the route between the fieldbus devices and the ALF111
modules are referred to as the fieldbus communication abnormalities. The occurrences of the
fieldbus communication abnormalities can be confirmed by the system alarms. When the fieldbus
communication abnormality occurs, it should be recovered as soon as possible, no matter what
type of FCS as long as it is supporting ALF111. If the abnormality on the communication route for
the standing-by side is not recovered, the following phenomena may occur:
• When next fieldbus communication error occurs, since the standby module is still in the
erroneous state, the communication cannot be switched to the redundant route.
• When the ALF111 module on control side suffers a diagnostic error and fails, or when
IOM downloading is performed to the ALF111 module on control side, the control right
may be forced to switch to the standby ALF111 module which is not recovered from the
communication abnormality, the potential communication error will become an obvious
error.
• Therefore, before IOM downloading to an ALF111 module, it is necessary to check the
standby ALF111 module communication status on the HIS status display window.

SEE
ALSO • For more information about the command line, see the following:
“ Details of Contents that can be Specified in the Command Line” in “ Properties of the Module” of D1.1,
“Engineering of the ALF111 Module”
• For more information on dealing with the system alarms caused by the fieldbus communication
abnormalities, see the following:
“No. 4023 Communication Error with Duplicate ALF111” in 2.11, “Control Station Related Messages” in
Operating Messages (IM 33M05D20-40E)
l LAS (Link Active Scheduler) Function in Duplexing

The LAS in Fieldbus communication switches independent of the switching instruction from the
FCU. When the ALF111 on the control side fails, the LAS quickly switches to the ALF111 on the
standby side. As a result, the communication stop time on the Fieldbus can be minimized.
l Operation when the ALF111 on the Master Side is Normally Recovered

After an error has occurred in the ALF111 on the master side and the control privilege has been
transferred to the ALF111 on the slave side, the control privilege will not return to the ALF111 on
the master side even if the ALF111 on the master side is normally recovered. The ALF111 on the
slave side will continue to operate as the control side.

l Data Delay Time at Duplex Switching
The following table lists the data delay time at duplex switching. The FCS block retains the
previous value during delay.
Table Delay Time at Duplex Switching
Service Delay time Remark
Publisher/Subscriber type input None
Publisher/Subscriber type
None
cascade output
Publisher/Subscriber type output About 5 seconds
Client/Server type input About 5 seconds
Client/Server type output About 5 seconds
Client/Server type remote
About 5 seconds
cascade output
Block parameter reference
About 5 seconds
(auto update of View Object)
When the setting from the FF Faceplate Block
Block parameter setting None occurs at the timing of switching the ALF111
modules, the setting signal may be lost.
B010304E.ai
SEE
ALSO For more information about the communications of publisher/subscribe and server/client, see the following:
“n Communication Methods” in B1.1, “Fieldbus Data Access”
TIP
The following shows examples of data that has no delay time at duplex switching. In addition to the examples
below, there is no delay time for I/O data that is used by a normal control loop.
• Output from the OUT terminal of the FF-AI block to the ALF111
• Output from the ALF111 to the CAS_IN terminal of either the FF-AO or FF-PID block
The following shows examples of data that has a delay of one to five seconds at duplex switching.
• Output from the ALF111 to the RCAS_IN or TRK_IN_D terminal of the FF-PID block
• Output from the ALF111 to the IN1 through IN8 terminals of the FF-MAO block
• Referencing or setting via the faceplate block for the resource block that is not supported by the FF
faceplate block

B1.4 Download Operations

Accompanied with various user operations performed via Fieldbus Builder and Function
Block Builder, engineering data is downloaded to FCSs, ALF111s and Fieldbus devices
during the engineering of the Fieldbus system.
This section explains the download operations that are executed during engineering and
the effects of such download operations.
SEE
ALSO For more information on various download operations, see the following:
“n Download Operation” in D2.3.5, “Downloading to Fieldbus Devices”
n Engineering for which IOM Initialization Downloading is Performed

Two types of download method, IOM initialization download method and IOM continuous
download method, are available for the online download to the ALF111. If a change is made in the
setting of ALF111 duplexing, IOM downloading will be performed.
SEE
ALSO • For more information on IOM initialization downloading and IOM continuous downloading, see the
following:
“n Operation of the I/O Module when Online Download to the I/O Module is Executed: KFCS2/KFCS/
FFCS” in B3.5, “Operation of I/O Module when Downloading is Performed” in CENTUM VP Reference,
FCS Basics (IM 33M01A30-40E)
• For details on the engineering of ALF111 duplexing, see the following:
D1.1, “Engineering of the ALF111 Module”

n Download that Occurs during Engineering

The following shows the targets of downloading that occurs during engineering and the FF
faceplate block operation during downloading:
l Download Operations to be Performed during Regular Engineering

The following table shows the download operations to be performed during regular engineering:
Table Download Operations to be Performed during Regular Engineering
NO. Operation Download target Block operation and precaution
Blocks included in the Fieldbus device: Not affected.
Added Fieldbus device
(There is no FF faceplate block during addition.)
Newly adding Fieldbus (*1)
Other blocks: Not operated as O/S. However, all Fieldbus
1 device in Fieldbus Other Fieldbus devices
devices in the applicable segment look as if they change
Builder (*2)
from Fail to Recover only when a Fieldbus device with
ALF111
degraded communication performance is added. (*3)
Blocks included in the Fieldbus device: A communication
Other Fieldbus devices error occurs.
Deleting Fieldbus device
2 (*2) Other blocks: Blocks connected with a block that is included
in Fieldbus Builder
ALF111 in the Fieldbus device detect IOP/OOP. Others are not
affected.
Block to be changed: Block mode O/S → Recovers after
Adding FF faceplate downloading is completed.
Block to be changed
3 block in Function Block Other blocks: Blocks connected with the block to be
(Fieldbus device/FCS)
Builder changed detect IOP/OOP. The update cycle of the block
parameters may be delayed.
Block to be changed: Deleted from the schedule.
Deleting FF faceplate
Block to be changed Other blocks: Blocks connected with the block to be
4 block in Function Block
(Fieldbus device/FCS) changed detect IOP/OOP. The update cycle period of the
Builder
block parameters may be delayed.
Changing tag name of Block to be changed: Block mode O/S → Recovers after
Block to be changed
assigned FF faceplate downloading is completed.
5 (Fieldbus device/FCS)
block in Function Block Other blocks: Blocks connected with the block to be
Fieldbus I/O (%Z) (*4)
Builder downloaded detect IOP/OOP. Others are not affected.
Changing block detailed
Block to be changed downloading is completed. (*5)
6 definition in Function
(Fieldbus device/FCS) Other blocks: Blocks connected with the block to be
Block Builder
downloaded detect IOP/OOP. Others are not affected.
Fieldbus device including
the block to be changed Block to be changed: Detects IOP/OOP.
Changing loop structure
7 Other Fieldbus devices (*6) Other blocks: Blocks connected with the block to be
in Function Block Builder
ALF111 changed detect IOP/OOP. Others are not affected.
FCS I/O detailed definitions
B010401E.ai
*1: The initial downloading will be performed to the newly added fieldbus device. If the block parameter downloading is not required
right now and the equalization of the new fieldbus device parameters may be performed on Device Panel later, it is necessary to
uncheck [Block parameters are the scope of the loading] checkbox on the downloading confirmation dialog box.
*2: If a Fieldbus device is added or deleted, schedule information may be changed. The Fieldbus device of which the schedule
information has been changed becomes the target for downloading.
*3: The only time all Fieldbus devices in the applicable segment fail is limited to the cases when a Fieldbus device with inferior
communication performance than an already registered Fieldbus devices is added and the NMIB (Network Management
Information Base) parameters (SlotTime, etc.) are changed. When this happens, a warning message is displayed when a
Fieldbus device is added with Fieldbus Builder.
*4: Only the Fieldbus I/O (%Z) list display of Fieldbus Builder will be changed.
*5: In downloading from Control Drawing Builder, the block mode will be changed to O/S (Out of Service) only when the block
parameters that cannot be changed unless the block mode is changed to O/S have been changed. These block parameters
include the following:
CHANNEL, CONTROL_OPTS, IO_OPTS, OUT_SCALE, PV_SCALE, STATUS_OPTS, XD_SCALE, FF_SCALE, L_TYPE,
SEL_TYPE, TRK_SCALE
*6: Schedule information may be changed if a block is added, deleted or connected. The Fieldbus device of which the schedule
information has been changed will be the target for downloading.

l Operation when a Fieldbus Device is Changed
This type of download operation is performed when a Fieldbus device is changed.
Table Download Operation when a Fieldbus Device is Changed
NO. Operation Download target Block operation and precaution
Blocks included in Fieldbus devices: A communication error
Run [Offline Load] -
occurs (block mode O/S) → Recover after downloading is
1 [Master Data Download]
Applicable Fieldbus device completed.
menu in Fieldbus Builder
Other blocks: Blocks connected with the block included in the
(*1)
Fieldbus device detect IOP/OOP. Others are not affected.
B010402E.ai
*1: Master data downloading may be performed when the same type of fieldbus device is replaced. If a different type fieldbus is
replaced, Device Panel should be used.
l Special Download Operations

The following table lists the download operations that are performed from Fieldbus Builder
only if necessary, because normal engineering uses the default setting values or automatically
determined values.
Table Special Download Operations
Operation in
NO. Download target Block operation and precaution
Fieldbus Builder
Applicable Fieldbus device Blocks included in the Fieldbus device: A communication
Changing node address
Other Fieldbus devices error occurs. (*2)
1 of Fieldbus device in
(*1) Other blocks: Blocks connected with a block included in the
operation
ALF111 Fieldbus devices detect IOP/OOP. Others are not affected.
All Fieldbus devices in Not affected. (However, if a macrocycle is changed,
Changing SMIB
2 a segment the schedule is also affected. Thus, the block execution
parameters (*3)
ALF111 sequence may be affected.) (*4)
All Fieldbus devices in
Changing NMIB All Fieldbus devices in the applicable segment look as if they
3 a segment
parameters (*5) change from Fail to Recover with the changed parameters.
ALF111
All Fieldbus devices
Not affected. (However, if a macrocycle is changed, the
that are link master in
4 Changing schedule schedule is also affected. Thus, the block execution
a segment
sequence may be affected.) (*4)
ALF111
The tag name of the Fieldbus device that includes a block to
Changing tag name of Applicable Fieldbus device which the FF faceplate block has been assigned cannot be
5
Fieldbus device ALF111 changed.
Other blocks: Not affected.
The tag name of the Fieldbus device that includes a block to
which the FF faceplate block has been assigned cannot be
Block to be changed
Changing tag name of changed.
6 (Fieldbus device)
block Block to be changed: Block mode O/S → Recovers after
Fieldbus I/O (%Z) (*6)
downloading is completed.
Other blocks: Not affected.
Changing block Block to be changed downloading is completed.
7
parameters (Fieldbus device) Other blocks: Blocks connected with the block to be
downloaded detect IOP/OOP. Others are not affected.
B010403E.ai
*1: The communication information of the Fieldbus device that is connected with the Fieldbus block in the changed Fieldbus device
may be changed. The changed Fieldbus device becomes the target for downloading.
*2: The FF faceplate block of which node address has been changed becomes an invalid element of the FCS. A communication
error will be recovered when the invalid element is resolved.
*3: Changing the SMIB (System Management Information Base) parameters includes the change via the “Segment Common” tab
(schedule adjustment, sub-schedule) in addition to the change in the parameter edit dialog.
*4: Generally, the user does not make changes.
*5: The NMIB (Network Management Information Base) parameters can be changed in the Edit Parameter dialog box. The
parameters that fail all Fieldbus devices include the following:
SlotTime, PerDlpduPhlOverhead, MaxresponseDelay, ThisLink, MinInterPduDelay, PreambleExtension,
PostTransGapExtension, MaxInterChanSignalSkew, TimeSyncClass
*6: Only the Fieldbus I/O (%Z) list display of Fieldbus Builder will be changed.

n Timing of Block Mode Change

The following figure shows the download sequence of Fieldbus devices, an ALF111, an FCS (I/O
definitions) and an FCS (blocks), and the timing of block mode change for the Fieldbus devices
when downloading is executed with a builder. Downloading will be executed only to the devices
that have become the targets for downloading in the previous tables.
Repeats for the number of ALF111 modules.
Timing of Fieldbus Fieldbus … Fieldbus

download Device 1 Device 2 Device n ALF111 FCS/(I/O definitions) FCS(Function blocks)
Timing of Fieldbus Fieldbus … Fieldbus

block mode Communication information block 1 block 2 block n
change
Sets the block Returns the block mode

mode to O/S. to the original setting. B010404E.ai
Figure Download Sequence and Timing of Block Mode Change

Blank Page
<B2. FF Faceplate Block Common Operations> B2-1
B2. FF Faceplate Block Common

Operations
The FF faceplate block contains the functions and processing that are performed
commonly among blocks. This chapter explains the components of the FF faceplate
block.
• Data equalization function
• Block mode processing
• Operations at FCS start
• Input signal processing
• Output signal processing
• Alarm processing
• Operation during I/O simulation
• Correspondence among connecting terminals, data items, and parameters
• Builder definition items

B2.1 Data Equalization Processing

Data equalization processing matches the standard block parameters of the Fieldbus
block with the corresponding data items of the FF faceplate block.
SEE
ALSO • For more information on the Standard Block Parameter and Extended Parameters, see the following:
A1.1, “Glossary”
• For the method to handle the Extended Parameters with the FF faceplate block, see the following:
“n Extended Parameters” in B2.1.2, “Update Using Fieldbus I/O (%Z)”
Change of data values

Reflection of data
value change GAIN OUT
Reference to standard
SP
block parameters
PV
FF faceplate block
%Z FCU
Fieldbus device
GAIN
View Object
(*1)
PV
Update using %Z Fieldbus block

B020101E.ai
Figure Data Equalization Processing
*1: View Object is a feature that manages and stores the internal block parameters of the Fieldbus device.

n List of Data Equalization Processing

The following describes the contents of data equalization processing:
• Referencing the standard block parameters
Updates the standard block parameters of the FF faceplate block via View Object of the
Fieldbus block.
• Update using %Z (Fieldbus I/O)
Updates the data items using %Z.
• Reflecting data item value change
Reflects the changed data items of the FF faceplate block in the Fieldbus block.
Table List of Data Equalization Processing
Referencing standard block parameters Update using %Z Reflecting data value change
• Accesses data items
Uses the data setting for the
directly connected with
Updates the standard data items of the data items of the FF faceplate
Application the terminal.
FF faceplate block. block, and the entry for the
• Accesses the extended
Fieldbus block.
parameters. (*1)
Transmission For direct coupled node: About 2 seconds
1 second About 2 seconds (*2)
time For remote node: About 4 seconds (*2)
For dynamic parameters(*3): Updates data
items using the timing of specified by the
Detects a change in data
update coefficient and the phase.
Updates data items using values using periodic
Update For static parameters(*3): The ALF111
periodic processing of the FF processing of the FF faceplate
timing detects a change of View Object and
faceplate block. block, and writes for one shot
updates the View Object image of the FCS.
to the Fieldbus block.
Then, updates data items using periodic
processing of the FF faceplate block.
B020102E.ai
*1: Since only the standard block parameters in View Object can be accessed when referencing View Object, %Z is used for
accessing the extended parameters.
*2: If multiple Fieldbus blocks exist in the same Fieldbus device, the required transmission time will be prolonged for the number of
such blocks.
*3: The dynamic parameters are a set of parameters such as PV and SP that are required for operations performed by the operator.
The static parameters are a set of parameters such as I/O scale and upper/lower limit values that must be displayed for the
operator.
IMPORTANT
The IEEE infinite value is used in the Fieldbus Foundation specifications, and infinite values
occasionally appear in the block parameters of the Fieldbus block. However, the CENTUM
system does not handle values such as IEEE infinite value and NaN (Not a Number). Therefore,
the following precautions must be exercised:
• Do not assign a block parameter that may take an infinite value to %Z. If an infinite value is
entered during update using %Z, the data status will become BAD and the previous value
will be retained.
• When referencing via View object, if an infinite value is entered in View object and it is
a positive infinite value, it will be replaced with the maximum value of data type. If it is a
negative infinite value, it will be replaced with the minimum value of data type.
• In either case, as for NaN, the data status will become BAD and the previous value will be
retained.

B2.1.1 Referencing the Standard Block Parameters

The standard block parameters are referenced by using View Object of the Fieldbus block.
View Object is an interface of the Fieldbus block that is used to reference several block
parameters by one or more communications.
n Transmission Time
If the ALF111 is mounted to a local node, data exchange between the ALF111 and the FCU
can be performed at high speed. If the ALF111 is mounted to a remote node, it takes more time
to exchange data as compared to the case of the local node because communication is done
via the EB401. The transmission time of the standard block parameters is approximately one
second when mounted to a direct coupled node, and approximately four seconds when mounted
to a remote node for both the dynamic parameters and the static parameters. However, the
transmission time is affected by the Fieldbus communication schedule as well as by the Fieldbus
device performance. In actuality, this transmission time includes errors.
IMPORTANT
If multiple Fieldbus blocks exist in the same Fieldbus device, the required transmission time will
be prolonged for the number of such blocks.
n Update Timing
▼ Update Timing
When updating the standard internal parameters using View Object, the update cycle fluctuates
depending on the Fieldbus device on the Fieldbus, the dispersion condition of the Fieldbus
blocks, and the load. Furthermore, the greater the number of Fieldbus blocks becomes, the
slower all standard internal parameters are updated.
As a result, a perfect periodicity cannot be guaranteed for the update cycle of the standard
internal parameters.
l Changing the Update Cycle

The CENTUM VP enables the change of the update cycle for each block using View Object. By
this, the load on the Fieldbus can be reduced by making the update cycle longer and reducing
the number of updates for the block to be monitored. It is also possible to set a shorter update
cycle for only the desired Fieldbus block. This setting can be performed using the Basics tab of
Function Block Detail Builder.
• Update coefficient: 4 (default), 1, 2, 8, 16, 32, 64
• Phase: 0 to (update coefficient - 1)
An appropriate value is assigned by the system as the default phase.
l Update Interval Display: DTUP (Update Interval)

The update interval can be checked by DTUP, which is one of the data items of the FF faceplate
block.
The DTUP is the count of the update timing that has been skipped from the previous update to
the current update.

B2.1.2 Update Using Fieldbus I/O (%Z)

▼ %Z Assignment
The process data and extended parameters that are used for control are updated via the
Fieldbus I/O (%Z). This chapter explains the mechanism of data equalization using %Z.
n Process Data Used for Control

The process data of the Fieldbus block is used for control by loading it into the FCS function
block via the FF faceplate block. If the update time of the process data in the FF faceplate block
is delayed, control is adversely affected. To avoid this, if a definition is made to connect the FCS
function block (other than the FF faceplate block) to the connecting terminal of the FF faceplate
block, %Z is automatically assigned, and as a result, process data will be updated at high speed.
l Mechanism of %Z Auto Assignment

High-speed transmission terminals (ZIN, ZOUT, etc.) corresponding to IN, OUT and other
connecting terminals for updating data at high speed are provided in the FF faceplate block.
If a definition is made using Control Drawing Builder to connect a block other than the FF
faceplate block to the connecting terminal of the FF faceplate block, the data items directly
connected with that connecting terminal are automatically assigned to %Z. Then, this connection
with %Z is set in the corresponding high-speed transmission terminal (Zxxx). As a result, process
data to be directly connected with the FF faceplate block terminal can be updated at high speed
using %Z.
Connection by the user
Data item directly FCS

IN PID
connected with function block
the OUT terminal
FF faceplate block OUT

OUT_V
Auto connection
with %Z with a builder FF-AI
AI OUT is assigned to ZOUT

%Z with a builder
FCS
%Z(OUT)
Fieldbus
OUT
AI
B020103E.ai
Figure Auto Assignment of %Z

n Extended Parameters
▼ Extended Parameter
Fieldbus device vendors are differentiating their products by adding original parameters to the
standard block parameters of the Fieldbus block. These added parameters are called extended
parameters. Because only the standard View Object can be supported with “Reference with View
Object,” the user cannot access the parameters that are extended by the vendors. To reference
and set the proprietary extended parameters of each vendor, assign those parameters to the
extended parameters (P01 to P04) of the FF faceplate block using Function Block Detail Builder.
By doing this, the extended parameters of the Fieldbus block can be referenced and set from the
HIS.
The data type of the extended parameters (P01 to P04) is fixed at F32S. The data type of the
Fieldbus block extended parameters is displayed after converting it into F32S.
SEE
ALSO For more details on the data type, see the following:
“n Data Type” in B1.1, “Fieldbus Data Access”
l High-Speed Transmission Terminals ZP01 to ZP04 for the Extended

Parameters
Assign the parameters that are extended by the vendors from P01 to P04 on the Extended
Parameter tab of Function Block Detail Builder. The assigned extended parameters are then
assigned to %Z, and that %Z is connected with high-speed transmission terminals ZP01 to ZP04
of the FF faceplate block. The FF faceplate block references and sets the data of the parameters
assigned from the high-speed transmission terminals via %Z.
FF faceplate block
Creation of connection information
extended parameter
P01
Function Block Detail Builder
ZPO1 FF faceplate block PO1 AUX_IN

High-speed PO2
transmission terminal PO3
PO4
%Zxxxx
Fieldbus block
View Object
IN OK
PV
Extended parameter SP %Z assignment
that is not included OUT
in View Object AUX_IN
B020104E.ai
Figure Referencing the Extended Parameters Using %Z

l Extended Parameter Attributes
An extended parameter is a data item, not a terminal. Among the extended parameters of the
Fieldbus block, it is possible to assign I/O parameters. However, connection between terminals
that use the extended parameters is not allowed.
IMPORTANT
The extended parameters should be used only when necessary. If multiple extended parameters
are assigned, the data update cycle for the applicable FF faceplate block will slow down. It affects
not only the update using View Object but also the update of Fieldbus I/O data using %Z used for
control.

B2.1.3 Reflecting the Data Value Change

If data setting or data entry is performed for a data item of the FF faceplate block from
the HIS, one-shot writing is performed to the corresponding internal parameter of the
Fieldbus block, and change in the data value is reflected.
n Stopping the Data Equalization

Data equalization to the applicable data item is not performed for a certain period of time after
one-shot writing is performed. This is to avoid an internal conflict of data update between the FF
faceplate block and the Fieldbus block.
The stop time of data equalization is automatically determined based on the update coefficient,
which is an item for the block specified by Function Block Builder.

B2.2 Block Mode Processing

The FF faceplate block notifies the Fieldbus block of the block mode change in the FF
faceplate block from the user operation on the HIS or the sequence control of the FCS.
Conversely, it detects the mode transition on the Fieldbus block side, and changes the
block mode of the FF faceplate block.
The modes of both the FF faceplate block and the Fieldbus block match based on this
mechanism.
n Mechanism of the Block Mode Equalization
HIS
Mode change
MODE Reflection of
mode transition
FF faceplate block
Reflection of mode
change specification
MODE_BLK Target
View
Object
Fieldbus block
B020201E.ai
Figure Block Mode Equalization
Table Timing and Transmission Method of the Block Mode Equalization

FF faceplate block → Fieldbus block Fieldbus block → FF faceplate block
Periodic processing of the FF faceplate Approximately 2 to 3 seconds after mode
Update timing
block after mode change specification transition
Detects mode change specification by
Updates the View Object image of the FCS by
the differential from the previous mode in
Transmission periodic collection processing of the ALF111,
block periodic processing, and writes into
method then reads the View Object by periodic
the target mode (MODE_BLK.Target) of
processing of the FF faceplate block.
the Fieldbus block.
B020202E.ai

n Operation while in the O/S Mode

Generally, if the block mode of the FF faceplate block is changed by user operation on the HIS
or by the sequence control on the FCS, the block mode of the Fieldbus block that corresponds to
that FF faceplate block will be changed almost at the same time.
However, if the block mode of the FF faceplate block is changed to O/S (Out of Service), the
block mode of the Fieldbus block will not be changed. This is because when the mode of the
FF faceplate block is placed in O/S, communication with the Fieldbus is not performed for that
particular block.
n Operations when Changing the Local Mode

If the block mode of the Fieldbus block is changed directly with the Device Management tool or
other means rather than via the FF faceplate block, and as a result it becomes different from the
block mode of the FF faceplate block, the following operations will be performed depending on
the block mode of the FF faceplate block.
Table Operations when the Local Mode of the Fieldbus Block is Changed
Block mode of FF faceplate block
When O/S Other than O/S
• The FF faceplate block is placed in the O/S
• Since the FF faceplate block has been stopped,
compound mode by block mode equalization
communication with the Fieldbus block is cut off.
When processing.
• The data status of other function blocks that are
Fieldbus • The data status of the data item becomes BAD
referencing data in the FF faceplate block is set to
block is (BAD value) + CND (CoNDitional), so other
IOP (Input OPen high: Upper limit input is open).
O/S function blocks that are referencing this data item
• O/S is not notified to the Fieldbus block even if
is set to IOP, and the mode of the setting block
the FF faceplate block becomes O/S.
becomes IMAN (Initialization MANual).
• Since the FF faceplate block has been stopped,
communication with the Fieldbus block is cut off.
When • O/S is not notified to the Fieldbus block even if
Fieldbus the FF faceplate block becomes O/S. The block mode of the FF faceplate block becomes
block is • Other function blocks that are referencing data the same as that of the Fieldbus block by block
other than in the FF faceplate block remain as IOP. mode equalization processing.
O/S It is necessary to set the block mode of the FF
faceplate block to other than O/S in order to
operate the FF faceplate block.
B020203E.ai

The following table summarizes the operations in various block modes of the FF faceplate block:
Table Data Update in Various Block Modes of the FF Faceplate Block
Communication Data Mode of referencing or Mode of
Block mode
with Fieldbus equalization setting block Fieldbus block
• Block that is referencing is IOP.
O/S - - No mode change
• Block that is setting is IMAN.
Dead mode in the case of the
O/S transient state.
One of the following three modes
O/S compound when the Fieldbus block is O/S:
mode • IOP if data with data status is O/S, or state during
x x
O/S (MAN) being referenced recovery from O/S
O/S (AUT), etc. • IMAN if data with data status
is being set
• Dead mode if other than the
above
Same mode as the FF
Normal mode x x Normal operation
faceplate block
B020204E.ai
x: Executed.
–: Not executed.
SEE
ALSO For more details on the O/S transient state, see the following:
“n Over Transition Mode” in C6.1.3, “Block Mode Transition” in CENTUM VP Reference, Function Block
Details (IM 33M01A30-40E)
n Prohibiting MAN Entry

▼ Prohibit the Entry of MAN
MAN entry for a block of the FF faceplate blocks can be prohibited. This is the MODE_BLK.
permitted (permitted mode) function originally possessed by the Fieldbus block. Although entries
in all modes can be prohibited in the Fieldbus Foundation specifications, only “Prohibit MAN
Entry,” the prohibition of MAN entry, can be defined for practical purposes using Function Block
Detail Builder in the CENTUM VP system.
Nevertheless, a block itself may transit its mode to MAN during fallback operation even if MAN
entry is prohibited. This means that prohibiting MAN entry does not completely remove the MAN
entry feature from the block operation specifications.

B2.3 Abnormality Detection Operations at FF

Faceplate Block
The following shows the operations of the FF faceplate block when the FCS and ALF111
are started, instantaneously stopped, and stopped for a long period of time.
n Operations when Initializing the FCS and during Power Failure of

Nodes (Direct Coupled Node and Remote Node)
The following table lists the operations performed by the FF faceplate block when Initializing the
FCS and when recovering from instantaneous or long-term power failure of a direct coupled or
remote node.
Table Operations when Initializing the FCS and during Power Failure of Nodes
Item Data value Data status Alarm
The previous values are QST + CND The previous values are
retained. retained.
The previous values are QST and CND are set to Alarm being generated is
FCS initialization
retained until the latest ON until the latest values not reset. It is updated
start
values are received from are received from the when the latest alarm
the ALF111 after ALF111 after information is received
communication is established. communication is established. from the ALF111.
The previous values are The previous values are
retained. retained. The previous values are
Recovery from
The previous values are The previous values are retained.
node (local or
retained until the latest retained until the latest It is updated when the
remote node)
values are received from values are received from latest alarm information is
instantaneous stop
the ALF111 after the ALF111 after received from the ALF111.
communication is established. communication is established.
The previous values are
Recovery from BAD
retained. The previous values are
long-term power
The previous values are BAD is set to ON until the retained.
failure of node
retained until the latest latest values are received It is updated when the
(direct coupled
values are received from from the ALF111 after latest alarm information is
node and remote
the ALF111 after communication is established. received from the ALF111.
node)
communication is established.
B020301E.ai

B2.4 Input Signal Processing

When a loop is formed between Fieldbus blocks, the input terminal of the FF faceplate
block is connected with the output terminal of the FF faceplate block. In this case, the data
items of the FF faceplate block are equalized with the data items of the Fieldbus block
using View Object.
Furthermore, when a loop is formed by combining an FF faceplate block and an FCS
function block, the input terminal of the FF faceplate block can reference the data items of
the FCS function block.
n Non-Conversion Processing
Only non-conversion is supported for the input signal processing of the FF faceplate block. If the
connection type of the input terminal is data connection, the data of the connection destination is
referenced according to the connection information, and then stored in the data items of the FF
faceplate block upon the completion of data status processing.
SEE
ALSO For the correspondence of the data items between each connecting terminal and the storage destination, see the
following:
B2.8, “Correspondence among Connecting Terminals, Data Items, and Parameters”
If functions such as signal conversion and digital filtering are required, use the FCS function block
that processes input signals such as PVI first, and then reference the PV data of that PVI.
PV
Signal IN
%Z FF-PID
conversion
Input indicator
block (PVI)
B020401E.ai
Figure Example of Connection when Signal Conversion is Required
n Calibration
No calibration function for the IN terminal and PV is available.

B2.5 Output Signal Processing

Output signal processing is not available in the FF faceplate block. The output terminal of
the FF faceplate block can only be connected with the input terminal of the FF faceplate
block. If an attempt is made to define data connection or terminal connection with other
than the FF faceplate block is defined for the output terminal, an error will be generated by
a builder.
n Output Range Setting

The output range of the Fieldbus block cannot be determined automatically by Function Block
Builder. When connecting two FF faceplate blocks, perform engineering so that the scale
upper limit values and lower limit values of both blocks match. However, in a cascade loop that
connects an output terminal of an FCS function block such as PID with the SET terminal of an FF
faceplate block, the output range can be determined automatically in relation to the range change
of the FF faceplate block.
It is necessary to manually
adjust the range to the
secondary side range
OUT
FF faceplate block
SET Secondary side

range change
SH
SL
FF faceplate block
B020501E.ai
Figure When Connecting Two FF Faceplate Blocks (It is necessary to adjust the range manually)
OUT
FCS function block
SET
SH
SL
FF faceplate block
B020502E.ai
Figure When Connecting an FCS Function Block to an FF Faceplate Block (Output range can be
determined automatically)

B2.6 Alarm Processing

Alarm processing is performed based on the following two types of alarms in the FF
faceplate block.
• Alarms to be detected by the Fieldbus block (ALARM_SUM, BLOCK_ERR)
• Alarms to be detected by the alarm detection processing (communication error
detection processing) that is performed by the FF faceplate block itself
This section explains an overview of the alarm processing of the FF faceplate block,
ALARM_SUM, BLOCK_ERR, and communication error detection processing.
n Alarm Processing of the FF Faceplate Block

The Fieldbus block detects two alarms, ALARM_SUM and BLOCK_ALM. This alarm is conveyed
to the FF faceplate block via the ALF111. The FF faceplate block converts ALARM_SUM and
BLOCK_ALM into an alarm status, and then notifies it to the HIS as a process alarm, a recording
message, or a system alarm in which the sender is the FCS.
The FF faceplate block itself performs two types of alarm detection processing; output open
detection processing and communication error detection processing. The alarm detection
processing detects an output readback value error from the Fieldbus block or a communication
error with the Fieldbus block. When an error is detected, the FF faceplate block notifies a process
alarm to the HIS.
TIP
A system alarm is also notified when a Fieldbus device abnormality or ALF111 self diagnosis abnormality occurs.
However, this alarm is related to the ALF111 of the FCS, and is generated regardless of the FF faceplate block
operation.

n Process Alarm Processing

The ALARM_SUM status of the Fieldbus block is converted into the alarm status of the FF
faceplate block, and is notified as a process alarm. The user can perform an acknowledgement
operation for this alarm.
l Alarm ACK Operation

If an acknowledgement operation is performed for a process alarm in the FF faceplate block,
flashing of the alarm in the FF faceplate block stops.
Because the acknowledgement operation is effective only for the FF faceplate block, an
acknowledgement is not sent from the FF faceplate block to the Fieldbus block. Set the alarm
confirmation specification to “Auto ACK Enable” in the Fieldbus block. This is the default setting in
the definition of Function Block Detail Builder.
The Fieldbus block can make an alarm acknowledgment for each alarm, whereas the FCS
function block make a batch alarm acknowledgment for the entire block. Therefore, the alarm
acknowledgement of the FF faceplate block is also made for the entire block in a batch.
Table Process Alarm List of the FF Faceplate Block
Alarm status Fieldbus alarm
High-high limit alarm (HH) Hi Hi Alarm
High limit alarm (HI) Hi Alarm
Low-low limit alarm (LL) Lo Lo Alarm
Low limit alarm (LO) Lo Alarm
Positive direction deviation alarm (DV+) DevHi Alarm
Negative direction deviation alarm (DV-) DevLo Alarm
Connection status failure alarm (CNF)
Input open alarm (IOP) Block Alarm
Output open alarm (OOP)
Discrete alarm (INT) Discrete Alarm
B020601E.ai
IMPORTANT
• The FF faceplate block converts the status of the ALARM_SUM parameter into a process
alarm. The alert object sent from the Fieldbus device will not be directly referenced.
• The mapping of process alarms in the FF faceplate block is as shown in the table above. If
alarms of the Fieldbus block are to be monitored using the conventional faceplate block, the
conventional alarm mapping will be used.

n Block Alarm Processing

The Fieldbus block itself detects hardware and software abnormalities that affect the Fieldbus
block operation during block alarm processing. When the FF faceplate block detects a block
alarm, it sends a process alarm, a recording message or a system alarm according to the
contents of the block alarm. The information on block alarm generation is stored in the data called
BLOCK_ERR.
The following table lists the alarms that correspond to the contents of BLOCK_ERR:
Table FF Faceplate Block Operation Corresponding to the Contents of BLOCK_ERR
Process System Recording Block
Content of BLOCK_ERR Remarks
alarm alarm message status
Other x x
Block Configuration Error IOP x x
Link Configuration Error IOP x x
Simulate Active x SIM
Local Override x MODE is set to TRK.
Device Fault State Set x
Device Needs Maintenance Soon x x
Input Failure/process variable x
has BAD status
Output Failure OOP x
Memory Failure IOP x x
Lost IOP x x
Lost NV Data IOP x x
Readback Check Failed IOP x x
Device Needs Maintenance Now IOP x x
Power-up x
x MODE becomes O/S

Out-of-Service
compound mode.
B020602E.ai
x: A message or alarm will be generated.

n Communication Error Detection Processing

When the FF faceplate block detects an abnormality in the communication with the Fieldbus
block, it notifies process alarm CNF.
n Alarm Detection Stop Processing

Alarm detection stop processing stops alarm detection of individual process alarm, which is the
same processing as the alarm detection processing of general FCS function blocks.
If the alarm detection is set to “No detection” using Function Block Detail Builder, alarm dispatch
by the FF faceplate block stops, the alarm bit that corresponds to ALARM_SUM.disabled of the
Fieldbus block is set to ON, and then alarm detection of the Fieldbus block stops.
n Alarm Off Processing

Alarm Off processing temporarily suppresses the process alarm message operation while
making the alarm detection function active. This processing is the same as the alarm off
processing of general FCS function blocks.
SEE
ALSO For the alarm inhibition processing of general FCS function blocks, see the following:
C5.14, “Alarm Inhibition (Alarm Off) ” in CENTUM VP Reference, Function Block Details (IM 33M01A30-
40E)

B2.7 Operation during I/O Simulation

The actual connection between the Fieldbus device I/O and the Fieldbus block can be
disconnected to manually enter I/O values in order to perform a control loop test.
n Fieldbus Block Simulation Procedure

The following shows the procedure for placing the Fieldbus block in the simulation state:
1. Turn ON the simulation switch (hardware switch) on the Fieldbus device.
2. Set Simulate Enable/Disable of the SIMULATE parameter of the target Fieldbus block to
“Enable” using the Device Management tool.
3. Set the SIMULATE parameter values and status using the Device Management tool.
n Block Status
When the Fieldbus block is placed in the simulation state, the simulation state is notified to the
FF faceplate block by block alarm. The FF faceplate block that received the notification sets the
block status of the simulation state to SIM. The SIM block status indicates that the block is in the
simulation state.
n Operation of Connected Blocks

A function block that is referencing block data in the simulation state performs normal operation
regardless of whether or not the connection destination block is in the simulation state.

B2.8 Correspondence among Connecting

Terminals, Data Items, and Parameters
This section describes the correspondence among the connecting terminals of the
FF faceplate blocks, data items that are directly connected to these terminals, and the
parameters (terminals) of the Fieldbus block.
n FF-AI Block
Table Correspondence among the Connecting Terminals of the FF-AI Block, Data Items, and
Parameters
Connecting terminal Data item Fieldbus block terminal parameter
OUT OUT_V OUT
B020801E.ai
n FF-DI Block
Table Correspondence among the Connecting Terminals of the FF-DI Block, Data Items, and
Parameters
OUT OUT_V OUT_D
B020802E.ai
n FF-CS Block
Table Correspondence among the Connecting Terminals of the FF-CS Block, Data Items, and
Parameters
SEL_1
IN1 SEL1
BKCAL_SEL1
SEL_2
IN2 SEL2
BKCAL_SEL2
SEL_3
IN3 SEL3
BKCAL_SEL3
OUT
OUT MV
BKCAL_IN
B020803E.ai

n FF-PID Block
Table Correspondence among the Connecting Terminals of the FF-PID Block, Data Items, and
Parameters
IN IN_V IN
OUT
OUT MV
BKCAL_IN
CAS_IN
SET CSV
BKCAL_OUT
TIN TRK_VAL TRK_VAL
TSI TRK_IN_D TRK_IN_D
BIN FF_VAL FF_VAL
RCAS_IN
– RSV
RCAS_OUT
ROUT_IN
– RMV
ROUT_OUT
B020804E.ai
n FF-RA Block
Table Correspondence among the Connecting Terminals of the FF-RA Block, Data Items, and
Parameters

IN IN_V IN
IN1 IN1_V IN_1
OUT
OUT MV
BKCAL_IN
CAS_IN
SET CSV
BKCAL_OUT
TIN TRK_VAL TRK_VAL
TSI TRK_IN_D TRK_IN_D
RCAS_IN
– RSV
RCAS_OUT
B020805E.ai

n FF-AO Block
Table Correspondence among the Connecting Terminals of the FF-AO Block, Data Items, and
Parameters
OUT
OUT MV
BKCAL_IN
CAS_IN
SET CSV
BKCAL_OUT
RCAS_IN
– RSV
RCAS_OUT
B020806E.ai
n FF-DO Block
Table Correspondence among the Connecting Terminals of the FF-DO Block, Data Items, and
Parameters
OUT_D
OUT MV
BKCAL_IN_D
CAS_IN_D
SET CSV
BKCAL_OUT_D
RCAS_IN_D
– RSV
RCAS_OUT_D
B020807E.ai
n FF-OS Block
Table Correspondence among the Connecting Terminals of the FF-OS Block, Data Items, and
Parameters
Connecting terminal Data item FB terminal parameter
CAS_IN
SET CSV
BKCAL_OUT
OUT1 OUT1_V OUT_1
OUT2 OUT2_V OUT_2
C020808E.ai

n FF-SC Block
Table Correspondence among the Connecting Terminals of the FF-SC Block, Data Items, and
Parameters
IN IN1_V IN_1
IN2 IN2_V IN_2
OUT1 OUT1_V OUT_1
OUT2 OUT2_V OUT_2
B020809E.ai
n FF-IT Block
Table Correspondence among the Connecting Terminals of the FF-IT Block, Data Items, and
Parameters
OUT CPV OUT
IN1 IN1_V IN_1
IN2 IN2_V IN_2
RFW1 RFW1_V REV_FLOW1
RFW2 RFW2_V REV_FLOW2
RSTI RSTI_V RESET_IN
OPTR OPTR_V OUT_PTRIP
OTR OTR_V OUT_TRIP
RESET_CONF
RSTC RSTC_V
IRM
B020810E.ai
n FF-IS Block
Table Correspondence among the Connecting Terminals of the FF-IS Block, Data Items, and
Parameters
OUT CPV OUT
SEL SEL_V SELECTED
IN1 IN1_V IN_1
IN2 IN2_V IN_2
IN3 IN3_V IN_3
IN4 IN4_V IN_4
DIS1 DIS1_V DISABLE_1
OSEL OSEL_V OP_SELECT
B020811E.ai

n FF-MDI Block
Table Correspondence among the Connecting Terminals of the FF-MDI Block, Data Items, and
Parameters
OUT1 OUT1_V OUT_D1
OUT2 OUT2_V OUT_D2
OUT3 OUT3_V OUT_D3
OUT4 OUT4_V OUT_D4
OUT5 OUT5_V OUT_D5
OUT6 OUT6_V OUT_D6
OUT7 OUT7_V OUT_D7
OUT8 OUT8_V OUT_D8
B020812E.ai
n FF-MDO Block
Table Correspondence among the Connecting Terminals of the FF-MDO Block, Data Items, and
Parameters
IN1 IN1_V IN_D1
IN2 IN2_V IN_D2
IN3 IN3_V IN_D3
IN4 IN4_V IN_D4
IN5 IN5_V IN_D5
IN6 IN6_V IN_D6
IN7 IN7_V IN_D7
IN8 IN8_V IN_D8
B020813E.ai

n FF-MAI Block
Table Correspondence among the Connecting Terminals of the FF-MAI Block, Data Items, and
Parameters
OUT1 OUT1_V OUT_1
OUT2 OUT2_V OUT_2
OUT3 OUT3_V OUT_3
OUT4 OUT4_V OUT_4
OUT5 OUT5_V OUT_5
OUT6 OUT6_V OUT_6
OUT7 OUT7_V OUT_7
OUT8 OUT8_V OUT_8
B020814E.ai
n FF-MAO Block
Table Correspondence among the Connecting Terminals of the FF-MAO Block, Data Items, and
Parameters
IN1 IN1_V IN1
IN2 IN2_V IN2
IN3 IN3_V IN3
IN4 IN4_V IN4
IN5 IN5_V IN5
IN6 IN6_V IN6
IN7 IN7_V IN7
IN8 IN8_V IN8
B020815E.ai

B2.9 Builder Definition Items of FF Faceplate

Blocks
The builder definition items to be specified by each function block vary in the FF faceplate
blocks. This section presents a list of the builder definition items to be specified by each
function block and explains the details of the builder definition items.

n Builder Definition Items to be Specified by Each Function Block

The following tables list the builder definition items to be specified by each function block of the
FF faceplate blocks:
Table List of Builder Definition Items to be Specified by Each Function Block (1/4)
F F F F F
F F F F F F F F F F F F F F F
F F F F F F F F F F
Specification item
-
-
-
-
P M M M M
-
-
-
-
-
-
-
-
-
-
A D C I R A D O S I I D D A A
I I S D A O O S C T S I O I O
Basic
Tag name x x x x x x x x x x x x x x x
Tag comment (TAG_DESC) x x x x x x x x x x x x x x x
Scan period x x x x x x x x x x x x x x x
Lvl x x x x x x x x x x x x x x x
Open/close mark – – x x x x – – – – – – – – –
Switch Position Label – x – – – – x – – – – – – – –
Label Format – x – – – – x – – – – – – – –
Strategy (STRATEGY) x x x x x x x x x x x x x x x
Prohibit the entry of MAN x x x x x x x x x x x x – x –
Update coefficient x x x x x x x x x x x x x x x
Phase x x x x x x x x x x x x x x x
Tag
Tag mark x x x x x x x x x x x x x x x
Status Change Message Bypass x x x x x x x x x x x x x x x
Upper window x x x x x x x x x x x x x x x
Upper equipment name x x x x x x x x x x x x x x x
Help x x x x x x x x x x x x x x x
MV Display on Faceplate – – x x x x – – – – – – – – –
CAS mark – – – x x x x x – – – – – – –
Kind of CAS mark – – – x x x x x – – – – – – –
Scale Reverse Display x – – x x – – – x x x – – – –
MV Reverse Display – – x x x x – – – – – – – – –
Index – – x x x x – – – – – – – – –
Scale - division x – x x x x – – x x x – – – –
Button Color – x – – – – – – – – – – – – –
F F F F F
F F F F F F F F F F
Specification item
-
-
-
-
-
P M M M M
-
-
-
-
-
-
-
-
-
-
A D C R A D O S I I
I I S I A O O S C T S D D A A
D I O I O
B020901E.ai
x: Available
–: Not available

F F F F F F
F F F F F F F F F
F F F F F F
F F F F F F F F F
Specification item
-
-
-
-
P M M M M
-
-
-
-
-
-
-
-
-
-
A D C I R A D O S I I D D A A
I I S D A O O S C T S I O I O
Input
Process value range (PV_SCALE) – – – x x x – – – – – – – – –
Output value range (OUT_SCALE) x – – – – – – – – – – – – – –
Input filter time constant (PV_FTIME) x x – x x – – – – – – – – – –
Ratio input filter time constant (RA_FTIME) – – – – x – – – – – – – – – –
Transducer range (XD_SCALE) x – – – – x – – – – – – – – –
Input signal conversion (L_TYPE) x – – – – – – – – – – – – – –
Input 1 Time unit (TIME_UNIT1) – – – – – – – – – x – – – – –
Input 2 Time unit (TIME_UNIT2) – – – – – – – – – x – – – – –
Input 1 pulse rate (PULSE_VAL1) – – – – – – – – – x – – – – –
Input 2 pulse rate (PULSE_VAL2) – – – – – – – – – x – – – – –
I/O option(IO_OPTS) x x – – – x x – – – – – – – –
Multiple input/output options specification
– – – – – – – – – – – – x – x
(MO_OPTS)
Action at communication timeout (SHED_OPT) – – – x x x x – – – – – – – –
Status option (STATUS_OPTS) x x x x x x x x – x x – – – –
Line-segment input value range (X_RANGE) – – – – – – – – x – – – – – –
Line-segment output value range (Y_RANGE) – – – – – – – – x – – – – – –
Low cutoff value (LOW_CUT) x – – – – – – – – – – – – – –
B020902E.ai
x: Available
–: Not available

Specification item
-
-
-
-
P I M M M M
-
-
-
-
-
-
-
-
-
-
A D C I R A D O S I D D A A
I I S A O O S C T S
D I O I O
Control calculation
Control option (CONTROL_OPTS) – – – x x – – – – – – – – – –
Feedforward range (FF_SCALE) – – – x – – – – – – – – – – –
Selection operation specification (SEL_TYPE) – – x – – – – – – – – – – – –
Selection operation specification (SELECT_TYPE) – – – – – – – – – – x – – – –
Swap Calculation Action (SWAP_2) – – – – – – – – x – – – – – –
Engineering unit conversion coefficient (UNIT_CONV) – – – – – – – – – x – – – – –
Integration action (INTEG_TYPE) – – – – – – – – – x – – – – –
Integration option (INTEG_OPTS) – – – – – – – – – x – – – – –
Integration period (CLOCK_PER) – – – – – – – – – x – – – – –
Pre-trip value (PRE_TRIP) – – – – – – – – – x – – – – –
Output GOOD threshold (GOOD_LIM) – – – – – – – – – x – – – – –
Output BAD threshold e (UNCERT_LIM) – – – – – – – – – x – – – – –
Momentary power failure Dead Time (OUTAGE_LIM) – – – – – – – – – x – – – – –
Input value bad threshold value (MIN_GOOD) – – – – – – – – – – x – – – –
Remote mode – – – x x x x – – – – – – – –
Input line-segment values 1 to 4 (IN_ARRAY) – – – – – – – x – – – – – – –
Output line-segment values 1 to 4 (OUT_ARRAY) – – – – – – – x – – – – – – –
Lock action – – – – – – – x – – – – – – –
B020903E.ai
x: Available
–: Not available

Specification item
-
-
-
-
P I M M M M
-
-
-
-
-
-
-
-
-
-
A D C I R A D O S I D D A A
I I S A O O S C T S
D I O I O
Output
Output limit hysteresis (BKCAL_HYS) – – – x – – – – – – – – – – –
Operation output range (OUT_SCALE) – – x x x – – – – – – – – – –
Setpoint Value Downward Change Rate Limiter
– – – x x x – – – – – – – – –
(SP_RATE_DN)
Setpoint Value Upward Change Rate Limiter
– – – x x x – – – – – – – – –
(SP_RATE_UP)
Tracking input value range high/low limits (TRK_SCALE) – – – x x – – – – – – – – – –
Operation output range (OUT_RANGE) – – – – – – – – – x x – – – –
Fault state transition detection time (FSTATE_TIME) – – – – – x x – – – – – – – –
Output 1 range (OUT_1_RANGE) – – – – – – – x – – – – – – –
Output 2 range (OUT_2_RANGE) – – – – – – – x – – – – – – –
Alarm
Alarm level x x x x x x x x x x x x x x x
Input open alarm x x x x x x x x x x x x x x x
PV high-high and low-low limit alarm x – – x x – – – – – – – – – –
PV high/low limit alarm x – – x x – – – – – – – – – –
Deviation alarm – – – x x – – – – – – – – – –
Output open alarm x x x x x x x x x x x x x x x
Bad Connection Alarm x x x x x x x x x x x x x x x
DISC alarm – x – – – – – – – – – – – – –
Alarm ack (ACK_OPTION) x – – x x – – – – – – – – – –
Input alarm hysteresis (ALARM_HYS) x – – x x – – – – – – – – – –
Alert key (ALERT_KEY) x x x x x x x x x x x x x x x
Line segment
X-axis line-segment data 1 to 21 (CURVE_X) – – – – – – – – x – – – – – –
Y-axis line-segment data 1 to 21 (CURVE_Y) – – – – – – – – x – – – – – –
B020904E.ai
x: Available
–: Not available

n Details of Builder Definition Items

The following tables list the details of the builder definition items:
▼ Tag Comment (TAG-DESC), Strategy (STRATEGY)
Table Details of Builder Definition Items (Basic)

Detailed setting
Specification item Specification range Default Remarks
items
Basic
Tag name 16 alphanumeric characters
Tag comment
24 byte characters
(TAG_DESC)
Scan period High speed/Medium speed/Basic Basic
Lvl 1 to 8 4
OC/CO/OCO/COC/OCC/OOC
Open/close mark None
/COO/CCO/none
Switch position label 1 to 64 2
0: Direct
Label format 0: Direct
1: Reverse
Strategy x
1 to 65535 1
(STRATEGY)
Only MAN entry cannot
Prohibit the entry of be made. If a block falls x
Yes/No No (*1)
MAN back, it operates in the
MAN mode.
Update Timing 1/2/4/8/16/32/64 4 x
Unspecified
Phase 0 to (update coefficient - 1) x
value
B020905E.ai
*1 : The default setting on FF-OS and FF-SC blocks is “Yes.”
Table Details of Builder Definition Items (Tag)
Detailed setting
items
Tag
Tag mark 1 to 8 2 x
Status Change x
Yes/No No
Message bypass
Upper window x
Upper equipment name x
Help HW0000 x
MV display on Actual quantity x
Actual quantity display/% display
Faceplate display
Type of CAS mark x
Automatic x
CAS mark Yes/No/ Automatic determination
determination
Scale Reverse display Yes/No No x
MV Reverse display Yes/No No x
Index Yes/No No x
1/2/3/4/5/6/7/ Automatic x
Scale - division
Automatic determination determination
N/R/G/Y/B/M/C/W/SB/ Specify each color of x
Button Color R(Red)
PK/SG/OR/YG/VO/DB/GR upper and lower side.
B020918E.ai

▼ Process Value Range (PV_SCALE), Output Value Range (OUT_SCALE), Transducer Range (XD_SCALE),
Input Signal Conversion (L_Type), Line-Segment Input Value Range (X_RANGE), Line-Segment Output
Value Range (Y_RANGE), Input Filter Time Constant (PV_FTIME), Ratio Input Filter Time Constant
(RA_FTIME), Action at Communication Time-Out (SHED_OPT), Input 1 Time Unit (TIME_UNIT1), Input
1-Pulse Rate (PULSE_VAL1), Input 2 Time Unit (TIME_UNIT2), Input 2-Pulse Rate (PULSE_VAL2), Low
cutoff value (LOW_CUT).
Table Details of Builder Definition Items (Input)
Detailed setting
items
Input
Process value range 7 digits including a
Engineering unit actual quantity 100.0/0.0/%
(PV_SCALE) decimal point
Output value range 7 digits including a
(OUT_SCALE) decimal point
Input filter time 32-bit floating decimal point data
0 second
constant (PV_FTIME) of 0 or more
Ratio input filter time 32-bit floating decimal point data
0 second
constant (RA_FTIME) of 0 or more
Transducer range 7 digits including a
(XD_SCALE) decimal point
Input signal 1: Direct 2: Indirect
1: Direct
conversion (L_TYPE) 3: Ind Sqr Root
Input 1 Time Unit
1: Second/2: Minute/3: Hour/4: Day 1: Second
(TIME_UNIT1)
Input 2 Time unit
1: Second/2: Minute/3: Hour/4: Day 1: Second
(TIME_UNIT2)
Input 1-pulse rate 32-bit floating decimal point data
1
(PULSE_VAL1) of 0 or more
Input 2-pulse rate 32-bit floating decimal point data
1
(PULSE_VAL2) of 0 or more
I/O option Described x
Described separately.
(IO_OPTS) separately.
Multiple I/O options Described x
(MO_OPTS) separately.
Action at
communication Described x
time-out separately.
(SHED_OPT)
Status option Described x
(STATUS_OPTS) separately.
Line-segment input
7 digits including a
value range Engineering unit actual quantity 100.0/0.0/%
decimal point
(X_RANGE)
Line-segment output
7 digits including a
value range Engineering unit actual quantity 100.0/0.0/%
decimal point
(Y_RANGE)
Low cutoff value 7 digits including a
A value within the scale 0.0
(LOW_CUT) decimal point
B020906E.ai
SEE
ALSO For the specification ranges and default settings of IO_OPTS, MO_OPTS, SHED_OPT, STATUS_OPTS, see the
following:
“n Details of Optional Definition Items”

▼ Selector Action (SEL_TYPE), Selector Action (SELECT_TYPE), Remote Mode, Feedforward Range (FF_
SCALE), Input Line-Segment Value (IN_ARRAY), Output Line-Segment Value (OUT_ARRAY), Lock Action
(LOCKVAL), Swap Calculation Action (SWAP_2), Engineering Unit Conversion Coefficient (UNIT_CONV),
Integration Action (INTEG_TYPE), Integration Period (CLOCK_PER), Pre-Trip Value (PRE_TRIP), Output
GOOD Threshold (GOOD_LIM), Output BAD Threshold (UNCERT_LIM), Input Value Invalid Threshold
(MIN_GOOD), Momentary Power Failure Dead Time (OUTAGE_LIM)
Table Details of Builder Definition Items (Control Calculation) (1/2)

Detailed setting
items
Control Calculation
Control option Described
(CONTROL_OPTS) separately.
Feedforward Range 7 digits including a
(FF_SCALE) decimal point
1: High/
Selector Action
2: Low/ 1: High
(SEL_TYPE)
3: Middle
1: First good/2: Minimum
Selector Action
/3: Maximum/4: Middle 3: Maximum
(SELECT_TYPE)
/5: Average
Swap Calculation 1: No swap
1: No swap
Action (SWAP_2) 2: Swap
Engineering unit
32-bit floating decimal point data
conversion coefficient 1.0
of 0 or more
(UNIT_CONV)
1: UP_AUTO
2: UP_DEM
3: DN_AUTO
Integration action
4: DN_DEM 1: UP_AUTO
(INTEG_TYPE)
5: PERIODIC
6: DEMAND
7: PER&DEM
Integration option Described
(INTEG_OPTS) separately.
Integration period 32-bit floating decimal point data
0 second
(CLOCK_PER) of 0 or more (second)
Pre-trip value 32-bit floating decimal point data
0.0
(PRE_TRIP) of 0 or more
Output GOOD
0.0 to 100.0 (%) 0.0%
threshold (GOOD_LIM)
B020907E.ai

Table Details of Builder Definition Items (Control Calculation) (2/2)
Detailed setting
items
Output BAD threshold
0.0 to 100.0 (%) 0.0%
(UNCERT_LIM)
Momentary power
32-bit floating decimal point data
failure dead time 0 second
of 0 or more (second)
(OUTAGE_LIM)
Input value invalid
threshold 0/1/2/3/4 0
(MIN_GOOD)
Remote mode RCAS/ROUT/RCAS+ROUT/None None x
Input line-segment
values X11, X12, X21, 0 to 100% 0.0
X22 (IN_ARRAY)
Output line-segment
values Y11, Y12, Y21, 0 to 100% 0.0
Y22(OUT_AR_RAY)
Lock action 1: No-lock
1: No-lock
(LOCKVAL) 2: Lock
B020923E.ai
SEE
ALSO For the specification ranges and the default settings of CONTROL_OPTS, INTEG_OPTS, see the following:
“n Details of Optional Definition Items”
▼ Operation Output Range (OUT_SCALE), Operation Output Range (OUT_RANGE), Output 1 Range (OUT_
1_RANGE), Output 2 Range (OUT_2_RANGE), Tracking Input Value Range (TRK_SCALE), Setpoint Value
Downward Change Rate Limiter (SP_RATE_DN), Setpoint Value Upward Change Rate Limiter (SP_RATE_
UP), Output Limit Hysterisis (BKCAL_HYS), Fault State Transition Detection Time (FSTATE_TIME)
Table Details of Builder Definition Items (Output)

Detailed setting
items
Output
Output limit hysteresis
0.0 to 50.0 (5%) 0.5 (%)
(BKCAL_HYS)
Operation output range Engineering unit actual 7 digits including a
100.0/0.0/%
(OUT_SCALE) quantity decimal point
Setpoint Value Downward Change 32-bit floating decimal
0.0
Rate Limiter (SP_RATE_DN) point data of 0 or more
Setpoint Value Upward Change 32-bit floating decimal
0.0
Rate Limiter (SP_RATE_UP) point data of 0 or more
Tracking input value range Engineering unit actual 7 digits including a
100.0/0.0/%
(TRK_SCALE) quantity decimal point
Operation output range Engineering unit actual 7 digits including a
100.0/0.0/%
(OUT_RANGE) quantity decimal point
Fault state transition detection time 32-bit floating decimal point
0 (second)
(FSTATE_TIME) data of 0 or more (second)
Output 1 range (OUT_1_RANGE)
Output 2 range (OUT_2_RANGE)
B020908E.ai

▼ PV High/Low Limit Alarm, PV High-High/Low-Low Limit Alarm, Deviation Alarm-FF-PID/FF-RA, Discrete
Alarm, Alarm Ack (ACK_OPTION), Alert Key (ALERT_KEY)
Table Details of Builder Definition Items (Alarm)
Detailed setting
items
Alarm
Alarm level 1 to 4 2 (Medium) x
Input open alarm HL/H/L/None HL x
PV high-high and low-low limit alarm HHLL/HH/LL/None HHLL x
PV high-low limit alarm HL/H/L/None HL x
Both directions/Positive
Both x
Deviation alarm direction/Negative direction
directions
/None
Output open alarm Yes/No Yes x
Bad Connection Alarm Yes/No Yes x
Discrete alarm Yes/No Yes x
0: Auto ACK Disabled/ x
Alarm ack (ACK_OPTION) 1: Auto ACK
1: Auto ACK Enabled
Input alarm hysteresis x
0.0 to 50.0 (%) 0.5 %
(ALARM_HYS)
Alert key (ALERT_KEY) 1 to 255 1 x
B020919E.ai
▼ X-Axis Line-Segment Data (CURVE_X), Y-Axis Line-Segment Data (CURVE_Y)
Table Details of Builder Definition Items (Line-Segment Data)
Detailed setting
items
Line-segment Data
See X_RANGE for
X-axis line-segment data 1 to 21 32-bit floating decimal 0 the display decimal
(CURVE_X) point data
point.
See Y_RANGE for
Y-axis line-segment data 1 to 21 32-bit floating decimal 0 the display decimal
(CURVE_Y) point data
point.
B020920E.ai

n Details of Optional Definition Items

The following shows the detailed listings of the optional definition items that have different initial
values in each function block, and the builder definition items consisting of bit information:
l IO_OPTS
▼ Low Cutoff, Invert, SP-PV Track in MAN, SP-PV Track in LO, SP Track Retained Target, Increase to Close,
Fault State to Value, Use Fault State Value on Restart, Target to MAN if Fault State Activated, Use PV for
BKCAL_OUT
Table Details of IO-OPTS Definition Items

Specification item Default FF-AI FF-DI FF-AO FF-DO
Invert No – Selectable – Selectable
SP-PV Track in MAN Yes – – Selectable Selectable
SP-PV Track in LO Yes – – Selectable Selectable
SP Track retained target No – – Selectable Selectable
Increase to close No – – Selectable –
Fault State to value No – – Selectable Selectable
Use Fault state value on restart No – – Selectable Selectable
Target to MAN if Fault State activated No – – Selectable Selectable
Use PV for BKCAL_OUT No – – Selectable Selectable
Low cutoff No Selectable – – –
B020909E.ai
Selectable: Either “Yes” or “No” can be selected.

–: Nothing Definition Items
l MO_OPTS
▼ Fault State to Value n, Use Fault State on Restart n
Table Details of MO_OPTS Definition Items

Specification item Default FF-MDO FF-MAO
Fault state to value 1 No Selectable Selectable
Use Fault state value on restart 1 No Selectable Selectable
B020910E.ai

l SHED_OPTS
The following shows the specification items of the option menu that is displayed in a valid FF
faceplate block:
Table Details of SHED_OPTS Definition Items
Specification item
Normal shed, normal return (default)
Normal shed, no return
Shed to Auto, normal return
Shed to Auto, no return
Shed to Manual, normal return
Shed to Manual, no return
Shed to Retained target, normal return
Shed to Retained target, no return
B020911E.ai
l INTEG_OPTS
▼ Input 1 Accumulate, Input 2 Accumulate, Flow Forward, Flow Reverse, Use Uncertain, Use Bad, Carry,
Add Zero if Bad, Confirm Reset, Generate Reset Event
Table Details of INTEG_OPTS Definition Items

Description Default FF-IT
Input 1 accumulate Yes Selectable
Input 2 accumulate No Selectable
Flow forward Yes Selectable
Flow reverse No Selectable
Use Uncertain No Selectable
Use Bad No Selectable
Carry No Selectable
Add zero if bad No Selectable
Confirm reset No Selectable
Generate reset event No Selectable
B020912E.ai

l CONTROL_OPTS
▼ SP-PV Track in MAN, SP-PV Track in LO or IMAN, SP-PV Track in ROUT, SP Track Retained Target, Track
Enable, Track in Manual, Bypass Enable, Use PV for BKCAL_OUT, Use BKCAL_OUT with IN_1, Act on IR,
Obey SP Limits if CAS or RCAS, No OUT Limits in Manual, Direct Acting
Table Details of CONTROL_OPTS Definition Items
Specification item Default FF-PID FF-RA
Bypass Enable No Selectable –

SP-PV Track in MAN Yes Selectable Selectable
SP-PV Track in ROUT Yes Selectable –
SP-PV Track in LO or IMAN Yes Selectable Selectable
SP Track retained target No Selectable Selectable
Direct Acting No Selectable –
Track Enable No Selectable Selectable
Track in Manual No Selectable Selectable
Use PV for BKCAL_OUT No Selectable Selectable
Act on IR No – Selectable
Use BKCAL_OUT with IN_1 No – Selectable
Obey SP limits if Cas or RCas No Selectable Selectable
No OUT limits in Manual Yes Selectable Selectable
B020913E.ai
l STATUS_OPTS
▼ Propagate Fault Forward, Propagate Fault Backward, Initiate Fault Status (IFS) if BAD IN, Initiate Fault
Status (IFS) if BAD CAS_IN, Use Uncertain as Good, Uncertain if MAN Mode, Uncertain if Limited, Bad if
Limited, Target to Next Permitted Mode if BAD CAS_IN, Target to Manual If BAD IN
Table Details of STATUS_OPTS Definition Items
F F F F F F F F F F F
F F F F F F F F F F F
-
Specification item Default

A D C PI R A
-
-
-
-
-
-
-
-
-
-
D O S I I
I I S D A O O S C T S
Initiate Fault Status (IFS) if BAD IN No (*1) – – S S S – – – – – –

Initiate Fault Status (IFS) if BAD CAS_IN No – – – S S – – S – – –
Use Uncertain as Good No – – S S S – – – – – S
Propagate Fault Forward No S S – – – – – – – – –
Propagate Fault Backward No – – – – – S S – – – –
Target to Manual if BAD IN Yes – – – S – – – – – – –
Uncertain if Limited No S – – – – – – – – – –
BAD if Limited No S – – – – – – – – – –
Uncertain if MAN mode No S S – – – – – – – S S
Target to next permitted mode if BAD CAS_IN Yes – – – S S – – S – – –
B020914E.ai
S: Either “Yes” or “No” can be selected.

*1: Yes on FF-CS block only.

l MODE_BLK
The following shows the setting contents of the permitted mode (MODE_BLK.permitted) in the
Fieldbus block:
Table Block Modes Set by MODE_BLK.permitted
F F F F F
F F F F F F F F F F
F F F F F
MODE_BLK. F F F F F F F F F F
-
-
-
-
P M M M M Condition
-
-
-
-
-
-
-
-
-
-
permitted A D C R A D O S I I
I D D A A
I I S A O O S C T S
D I O I O
O/S x x x x x x x x x x x x x x x
IMAN – – x x x x x x – – – – – – –
TRK mode is valid for
LO – – – xx x x x – – – – – x – x
CONTROL_OPTS.
xx xx xx xx xx xx xx xx xx xx xx xx xx Prohibition of MAN Entry is

MAN – –
specified as “No.”
AUT x x x x x x x x x x x x x x x
CAS – – – xx xx xx xx x – – – – – – – CAS mark is ON.
RCAS – – – xx xx xx xx – – – – – – – – Remote mode is RCAS.
ROUT – – – xx – – – – – – – – – – – Remote mode is ROUT.
B020915E.ai
x: Indicates an item whose default setting is ON.

xx: Indicates an item whose default setting changes depending on the condition.
l ALARM_SUM
Each alarm detection specification is reflected on ALARM_SUM.disabled and AF.

n Setting Destinations of Builder Definition Items

Some builder definition items of the FF faceplate block are set for the FF faceplate block as their
setting destinations. In addition, some items that are set for the Fieldbus block are set to special
setting destinations.
The setting destinations of builder definition items are listed below.
Table Setting Destinations of Builder Definition Items (1/2)
Setting destination
Specification item Specification range Default FF faceplate
Fieldbus block
block
Tag name 16 alphanumeric characters x –
24 alphanumeric characters, x
Tag comment –
12 double-byte characters
Tag mark 1 to 8 2 x –
Lvl 1 to 8 4 x –
High speed/ Medium speed/
Scan period Basic – –
Basic
Processing timing (Fixed) Periodic fixed x –
Status Change Message x
Yes/No No –
bypass
Engineering unit actual quantity x PV_SCALE OUT_
Output value range 100.0/0.0
effective 5-digit number SCALE only for FF-AI
Engineering unit actual quantity x
Operation output range 100.0/0.0 OUT_SCALE
effective 5-digit number
2 (all medium x
Alarm level 1 to 16 –
alarm)
B020916E.ai
x: Is set.
–: Is not set.

Table Setting Destinations of Builder Definition Items (2/2)
Setting destination
Specification item Specification range Default
FF faceplate block Fieldbus block
Input open alarm HL/H/L/None HL x –
PV high-high and x ALARM_SUM
HL/H/L/None HL
low-low limit alarm Disabled
x ALARM_SUM
PV high /low limit alarm HL/H/L/None HL
Disabled
x ALARM_SUM
Deviation alarm Both/PLUS/MINUS/No Both
Disabled
ALARM_HYS
Input alarm hysteresis 0.0 to 50.0 0.5 – (HH/HI/LO/LL are
shared with DV)
Output open alarm Yes/No Yes x –
Output limit hysteresis 0.0 to 50.0 0.5 – BKCAL_HYS
Bad Connection alarm Yes/No Yes x –
Error detection
specification during online Yes/No Yes x –
maintenance
Status option
– STATUS_OPTS
(STATUS_OPTS)
I/O option (IO_OPTS) – IO_OPTS
Action at communication
– CONTROL_OPTS
time-out (SHED_OPT)
B020917E.ai
x: Is set.
–: Is not set.
n Constant
The following data items of FF Faceplate Blocks can be defined with constants:
• AOFS
• SAID
• UAID
• OPMK
• MODE
n Manipulating FF Faceplate Blocks from Sequence Table

The data items of FF Faceplate Blocks can be used as condition signals in a sequence table. The
data can also be manipulated from the sequence table.
The data items for condition signals and the data items can be manipulated are listed in the
following table.

l Condition Signals
The description format and condition rules of the condition signals when referencing the block
mode, block status, alarm status and data status are the same as those for other regulatory
control blocks. The following table lists the data items that can be referenced for each block:
Table Data Items that can be Referenced
Block type name Data item Setting range
PV(RO) 0,1
FF-DI
OUT_V 0,1
TRK_IN_D 0,1
FF-PID
BYPASS 1,2
FF-RA TRK_IN_D 0,1
PV(RO) 0,1
FF-DO SV 0,1
MV 0,1
OTR_V 0,1
OPTR_V 0,1
RFW1_V 0,1
FF-IT
RFW2_V 0,1
RSTI_V 0,1
RSTC_V 0,1
DIS1_V 0,1
DIS2_V 0,1
DIS3_V 0,1
FF-IS
DIS4_V 0,1
SEL_V(RO) 0,1,2,3,4
OSEL_V 0,1,2,3,4
OUT1_V 0,1
OUT2_V 0,1
OUT3_V 0,1
OUT4_V 0,1
FF-MDI
OUT5_V 0,1
OUT6_V 0,1
OUT7_V 0,1
OUT8_V 0,1
IN1_V 0,1
IN2_V 0,1
IN3_V 0,1
IN4_V 0,1
FF-MDO
IN5_V 0,1
IN6_V 0,1
IN7_V 0,1
IN8_V 0,1
B020921E.ai
Note: (RO) is a data item that can only be described for the condition signals. Other data items can be described even for the operation
signals.

l Operation Signals
The description format and condition rules of the condition signals when operating the block
mode, block status, alarm status and data status are the same as those for other regulatory
control blocks. The following table lists the data items that can be operated for each block:
Table Data Items that can be Operated
FF-DI OUT_V 0,1
TRK_IN_D 0,1
FF-PID
BYPASS 1,2
FF-RA TRK_IN_D 0,1
SV 0,1
FF-DO
MV 0,1
OTR_V 0,1
OPTR_V 0,1
RFW1_V 0,1
FF-IT
RFW2_V 0,1
RSTI_V 0,1
RSTC_V 0,1
DIS1_V 0,1
DIS2_V 0,1
FF-IS DIS3_V 0,1
DIS4_V 0,1
OSEL_V 0,1,2,3,4
OUT1_V 0,1
OUT2_V 0,1
OUT3_V 0,1
OUT4_V 0,1
FF-MDI
OUT5_V 0,1
OUT6_V 0,1
OUT7_V 0,1
OUT8_V 0,1
IN1_V 0,1
IN2_V 0,1
IN3_V 0,1
IN4_V 0,1
FF-MDO
IN5_V 0,1
IN6_V 0,1
IN7_V 0,1
IN8_V 0,1
B020922E.ai

Blank Page
<B3. Individual FF Faceplate Block Operation> B3-1
B3. Individual FF Faceplate Block

Operation
This chapter describes the details of the connecting terminals, processing timings,
modes, statuses, and data items of individual FF faceplate blocks.

B3.1 FF AI Block (FF-AI)

The FF-AI block connects with the AI (Analog Input) block in a Fieldbus device to enable
operation and monitoring from the DCS.
n FF-AI Block
The FF-AI block connects with the AI block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-AI block:
P01
PV OUT_V
OUT
(OUT)
P04
B030101E.ai
Figure FF-AI Block
n Connecting Terminals of the FF-AI Block

▼ Connection
The following table lists the connection methods and connection destinations of the I/O terminals
of the FF-AI block:
Table Connecting Terminals of the FF-AI Block
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function Function
reference setting connection I/O I/O block(*1) block(*2)
OUT Manipulated output – – x(*3) – – x x
B030102E.ai
x: Can be connected.
–: Cannot be connected.
*1: Other than FF faceplate block
*2: FF faceplate block
*3: Cannot be connected with selector switch block (SW-33, SW-91)

n Processing Timing of the FF-AI Block
l One-Shot Processing
This cannot be executed.
l Periodic Processing
This is executed according to the scan period. A high-speed scan can be specified.
n Modes and Statuses of the FF-AI Block

The following shows the block modes, alarm statuses, and block statuses of the FF-AI block:
l Block Mode
Table Block Modes of the FF-AI Block
O/S IMAN TRK MAN AUT CAS PRD RCAS ROUT
x x x
B030103E.ai
x: Has the indicated block mode.

–: Does not have the indicated block mode.
l Alarm Status
Table Alarm Statuses of the FF-AI Block
IOP IOP- OOP CNF HH LL HI LO DV+ DV-
x x x x x x x
VEL+ VEL- MHI MLO INT
B030104E.ai

l Block Statuses
Table Block Statuses of the FF-AI Block
SIM
x
B030105E.ai

n Data Items of the FF-AI Block

Table Data Items of the FF-AI Block (1/2)
Fieldbus Fieldbus Entry
Fieldbus
Data item Data name Type parameter element enabled/ Range Default
data type
name name disabled
O/S
MODE Block mode U32 MODE_BLK DS-69 x
(AUT)
ALRM Alarm status U32 – NR
AFLS Alarm flashing U32 –
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
OPMK Operation mark I16 x 0
SAID System APID I16 x 0
UAID User APID I16 x 0
Function block
TYPE U16 –
type
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
BSTS Block status U32 –
ERRC Error code U32 –
DTUP Update cycle I32 –
Extended
P01 to P04 F32S x
parameters
Static data revision
ST_REV U16 ST_REV Unsigned16 –
number
STRATEGY Strategy U16 STRATEGY Unsigned16 –
ALRT_KEY Alert key U16 ALERT_KEY Unsigned8 –
TMOD Target mode U32 MODE_BLK Target Bit String –
AMOD Actual mode U32 MODE_BLK Actual Bit String –
PMOD Permitted mode U32 MODE_BLK Permitted Bit String –
NMOD Normal mode U32 MODE_BLK Normal Bit String –

BLK_ERR Block error U16 BLOCK_ERR Bit String –
Measurement
PV F32S PV DS-65 – SL <= n <= SH
input value
OUT_V Output value F32S OUT DS-65 x(*1) SL <= n <= SH
XD scale high limit
XDSC_100 F32 XD_SCALE EU at 100% Float –
value
XD scale low limit
XDSC_0 F32 XD_SCALE EU at 0% Float –
value
Fieldbus
data type
name name disabled
B030106E.ai
x: Entry is always enabled.

–: Entry is disabled.
*1: Entry enable when the MAN mode only.

Table Data Items of the FF-AI Block (2/2)
Fieldbus
data type
name name disabled
XD engineering
XDSC_UNT U16 XD_SCALE Units Index Unsigned16 –
unit
XD decimal point Decimal
XDSC_DP I16 XD_SCALE Integer8 –
position Point
PV scale high limit
SH F32 OUT_SCALE EU at 100% Float –
value
PV scale low limit
SL F32 OUT_SCALE EU at 0% Float –
value
PV scale
OTSC_UNT U16 OUT_SCALE Units Index Unsigned16 –
engineering unit
PV scale decimal Decimal
OTSC_DP I16 OUT_SCALE Integer8 –
point position Point
IO_OPTS Input option U16 IO_OPTS Bit String –
STS_OPTS Status option U16 STATUS_OPTS Bit String –
CHANNEL Channel U16 CHANNEL Unsigned16 –
Input signal
L_TYPE U16 L_TYPE Unsigned8 –
conversion
Low input cutoff
LOW_CUT F32 LOW_CUT Float –
value
PV filter time
PV_FTIME F32 PV_FTIME Float –
constant
FILD_VAL Field value F32S FILD_VAL DS-65 –
ACK_OPT ACK option U16 ACK_OPTION Bit String –
Input alarm
ALRM_HYS F32 ALARM_HYS Float
hysteresis
Input high-high
HH_PRI U16 HI_HI_PRI Unsigned8 3
limit alarm priority
Input high-high limit
HH F32 HI_HI_LIM Float x SL <= n <= SH SH
alarm set value
Input high limit
HI_PRI U16 HI_PRI Unsigned8 – 3
alarm priority
Input high limit
PH F32 HI_LIM Float x SL <= n <= SH SH
alarm set value
Input low limit
LO_PRI U16 LO_PRI Unsigned8 – 3
alarm priority
Input low limit
PL F32 LO_LIM Float x SL <= n <= SH SL
alarm set value
Input low-low limit
LL_PRI U16 LO_LO_PRI Unsigned8 – 3
alarm priority
Input low-low limit
LL F32 LO_LO_LIM Float x SL <= n <= SH SL
alarm set value
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B030107E.ai
x: Entry is always possible.

–: Entry is not possible.
*1: System reserved.

B3.2 FF DI Block (FF-DI)

The FF-DI block connects with the DI (Discrete Input) block in a Fieldbus device to enable
n FF-DI Block
The FF-DI block connects with the DI block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-DI block:
P01
PV OUT_V
OUT
(OUT_D)
P04
B030201E.ai
Figure FF-DI Block
n Connecting Terminals of the FF-DI Block

▼ Connection
of the FF-DI block:
Table Connecting Terminals of the FF-DI Block
B030202E.ai
*3: Cannot be connected with selector switch block (SW-33, SW-91)
n Processing Timing of the FF-DI Block

n Modes and Statuses of the FF-DI Block

The following shows the block modes, alarm statuses, and block statuses of the FF-DI block:
l Block Mode
Table Block Modes of the FF-DI Block
x x x
B030203E.ai

l Alarm Status
Table Alarm Statuses of the FF-DI Block
x x x
x
B030204E.ai

l Block Statuses
Table Block Statuses of the FF-DI Block
SIM
x
B030205E.ai

n Data Items of the FF-DI Block

Table Data Items of the FF-DI Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Function block
TYPE U16 –
type
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
Extended
P01 to P04 F32S x
parameters
number

Measurement
PV F32S PV_D DS-66 –
input value
OUT_V Output value F32S OUT_D DS-66 x(*1) 0/1
Fieldbus
data type
name name disabled
B030206E.ai

*1: Entry enabled when the MAN mode only.

Table Data Items of the FF-DI Block (2/2)
Fieldbus
data type
name name disabled
Status XD input
XD_STATE U16 XD_STATE Unsigned16 x
value
OUT_ST Status output value U16 OUT_STATE Unsigned16 x 0 <= n
PV filter time
constant
FILD_VAL Field value F32S FILD_VAL_D DS-66 –
Discrete alarm
DISC_PRI U16 DISC_PRI Unsigned8 – 3
priority
DISC_LIM Discrete limit U16 DISC_LIM Unsigned8 x 0/1 1
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
B030207E.ai
x: Entry is always possible.

–: Entry is not possible.

B3.3 FF Control Selector Block (FF-CS)

The FF-CS block connects with the CS (Control Selector) block in a Fieldbus device to
enable operation and monitoring from the DCS.
n FF-CS Block
The FF-CS block connects with the CS block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-CS
block:
IN SEL1
SEL_TYPE
MV
IN2 SEL2 (OUT) OUT
IN3 SEL3
P01 P04
B030301E.ai
Figure FF-CS Block
n Connecting Terminals of the FF-CS Block

▼ Connection
of the FF-CS block:
Table Connecting Terminals of the FF-CS Block
IN1 Selection input 1 x – x x x x x
OUT Manipulated output – – x – – – x
B030302E.ai

n Processing Timing of the FF-CS Block
n Modes and Statuses of the FF-CS Block

The following shows the block modes, alarm statuses, and block statuses of the FF-CS block:
l Block Mode
Table Block Modes of the FF-CS Block
x x x x
B030303E.ai

l Alarm Status
Table Alarm Statuses of the FF-CS Block
x x x
B030304E.ai

l Block Statuses
Table Block Statuses of the FF-CS Block
SIM
x
B030305E.ai

n Data Items of the FF-CS Block

Table Data Items of the FF-CS Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Function block
TYPE U16 –
type
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
Extended
P01 to P04 F32S x
parameters
number

Output high-limit MSL <= n <=
OPHI F32 x MSH
index MSH
Output low-limit MSL <= n <=
OPLO F32 x MSL
index MSH
Fieldbus
data type
name name disabled
B030306E.ai


Table Data Items of the FF-CS Block (2/2)
Fieldbus
data type
name name disabled
Manipulated output MSL <= n <=
MV F32S OUT DS-65 x
value MSH
MV scale high limit
MSH F32 OUT_SCALE EU at 100% Float x
value
MV scale low limit
MSL F32 OUT_SCALE EU at 0% Float x
value
MV scale
OTSC_UNT U16 OUT_SCALE Units Index Unsigned16 x
engineering unit
MV scale decimal Decimal
OTSC_DP I16 OUT_SCALE Integer8 x
Selection input MSL <= n <=
SEL1 F32S SEL_1 DS-65 x
value 1 MSH
value 2 MSH
value 3 MSH
SEL_TYPE Selection operation U16 SEL_TYPE Unsigned8 –
Readback input
BKCL_IN F32S BKCAL_IN DS-65 –
value
MH F32 OUT_HI_LIM Float x MSH
high limit value MSH
ML F32 OUT_LO_LIM Float x MSL
low limit value MSH
SEL1 Readback
BKCL_SL1 F32S BKCAL_SEL_1 DS-65 –
output value
SEL2 Readback
output value
SEL3 Readback
output value
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B030307E.ai


B3.4 FF PID Controller Block (FF-PID)

The FF-PID block connects with the PID (PID, PI, I controller) block in a Fieldbus device to
n FF-PID Block
The FF-PID block connects with the PID block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-PID
block:
SET
P01 RMV
(ROUT_IN)
CSV (ROUT_OUT)
(CAS_IN)
SV
(SP)
P04
RSV
(RCAS_IN)
(RCAS_OUT)
Input MV
IN IN_V (OUT) OUT
processing
TRK_VAL TRK_IN_D FF-VAL
TIN TSI BIN

B030401E.ai
Figure FF-PID Block
n Connecting Terminals of the FF-PID Block

▼ Connection
of the FF-PID block:
Table Connecting Terminals of the FF-PID Block
IN Measurement input x – xx x x x x
SET Setting input – – x – – x x
TIN Tracking input x – xx x x x x
TSI Tracking SW input x – xx x x x x
BIN Compensation input x – xx x x x x
B030402E.ai
xx: Can be connected only when connecting to Switch block (SW-33, SW-91) or FF faceplate block.

n Processing Timing of the FF-PID Block
n Modes and Statuses of the FF-PID Block

The following shows the block modes, alarm statuses, and block statuses of the FF-PID block:
l Block Mode
Table Block Modes of the FF-PID Block
x x x x x x x x
B030403E.ai

l Alarm Status
Table Alarm Statuses of the FF-PID Block
x x x x x x x x x
B030404E.ai

l Block Statuses
Table Block Statuses of the FF-PID Block
SIM
x
B030405E.ai

n Data Items of the FF-PID Block

Table Data Items of the FF-PID Block (1/4)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Function block
TYPE U16 –
type
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
Extended
P01 to P04 F32S x
parameters
number
Output high-limit MSL <= n <=
OPHI F32 x MSH
index MSH
Output low-limit MSL <= n <=
OPLO F32 x MSL
index MSH
Measurement
PV F32S PV DS-65 –
input value
SV Set value F32S SP DS-65 x(*1) SL <= n <= SH
Fieldbus
data type
name name disabled
B030406E.ai

*1: Not allowed for CAS/RCAS

Fieldbus
data type
name name disabled
MV F32S OUT DS-65 x(*1)
value MSH
PV scale high limit
SH F32 PV_SCALE EU at 100% Float –
value
PV scale low limit
SL F32 PV_SCALE EU at 0% Float –
value
PV scale
PVSC_UNT U16 PV_SCALE Units Index Unsigned16 –
engineering unit
PVSC_DP I16 PV_SCALE Integer8 –
MV scale high limit
value
MV scale low limit
value
MV scale
engineering unit
CONTROL_
CTL_OPTS Control option U16 Bit String –
OPTS
IN_V Raw input value F32S IN DS-65 x
PV filter time
constant
BYPASS Bypass SW U16 BYPASS Unsigned8 x(*1) 1: Off, 2: On 1
F32
CSV Cascade set value CAS_IN DS-65 x
SR
Negative direction
SV_RDN set value rate limit F32 SP_RATE_DN Float –
value
Positive direction
SV_RUP set value rate limit F32 SP_RATE_UP Float –
value
SVH Set value high limit F32 SP_HI_LIM Float x SL <= n <= SH SH
SVL Set value low limit F32 SP_LO_LIM Target Float x SL <= n <= SH SL
GAIN(*2) Gain F32 GAIN Actual Float x 1
RESET(*3) Integral time F32 RESET Permitted Float x 0 <= n
BAL_TIME Balance time F32 BAL_TIME Normal Float x 0 <= n 0
RATE(*4) Differential time F32 RATE Float x 0 <= n
Readback input
BKCL_IN F32S BKCAL_IN DS-65 –
value
Fieldbus
data type
name name disabled
B030407E.ai

*1: Entry is enabled when the MAN mode only.
*2: If the data item display is set to the CENTUM mode, this data item will change to P. In this case, the value of P will become 100/
GAIN.
*3: If the data item display is set to the CENTUM mode, this data item will change to I. The value will not change.
*4: If the data item display is set to the CENTUM mode, this data item will change to D. The value will not change.

Fieldbus
data type
name name disabled
MH F32 OUT_HI_LIM Float x MSH
high limit value MSH
ML F32 OUT_LO_LIM Float x MSL
low limit value MSH
Output limit
BKCL_HYS F32 BKCAL_HYS Float –
hysteresis
Readback output
BKCL_OUT F32S BKCAL_OUT DS-65 –
value
RSV Remote set value F32S RCAS_IN DS-65 x SL <= n <= SH
Remote operation MSL <= n <=
RMV F32S ROUT_IN DS-65 x
output value MSH
Communication
SHED_OPT U16 SHED_OPT Unsigned8 –
timeout operation
RCAS readback
RCAS_OUT F32S RCAS_OUT DS-65 –
output value
ROUT readback
ROUT_OUT F32S ROUT_OUT DS-65 –
value
TRK scale high
TKSC_100 F32 TRK_SCALE EU at 100% Float –
limit value
TRK scale low limit
value
TRK engineering
TKSC_UNT U16 TRK_SCALE Units Index Unsigned16 –
unit
TRK decimal point Decimal
TKSC_DP I16 TRK_SCALE Integer8 –
position Point
TRK_IN_D Tracking SW U32S TRK_IN_D DS-66 x 0/1
Tracking input TKSC_0 <= n
TRK_VAL F32S TRK_VAL DS-65 x
value <= TKSC_100
Compensation FFSC_0 <= n
FF_VAL F32S FF_VAL DS-65 x 0
input value <= FFSC_100
FF_VAL scale high
FFSC_100 F32 FF_SCALE EU at 100% Float –
limit value
FF_VAL scale low
FFSC_0 F32 FF_SCALE EU at 0% Float –
limit value
FF_VAL scale
FFSC_UNT U16 FF_SCALE Units Index Unsigned16 –
engineering unit
FF_VAL scale
Decimal
FFSC_DP decimal point I16 FF_SCALE Integer8 –
Point
position
Compensation None: maximum/
FF_GAIN F32 FF_GAIN Float x(*1)
gain minimum of type
Fieldbus
data type
name name disabled
B030408E.ai


Fieldbus
data type
name name disabled
Input alarm
ALRM_HYS F32 ALARM_HYS Float –
hysteresis
Input high-high
HH_PRI U16 HI_HI_PRI Unsigned8 – 3
limit alarm priority
Input high-high
HH limit alarm set F32 HI_HI_LIM Float x SL <= n <= SH SH
value
Input high limit
alarm priority
Input high limit
PH F32 HI_LIM Float x(*1) SL <= n <= SH SH
alarm set value
Input low limit
alarm priority
Input low limit
alarm set value
Input low-low limit
alarm priority
Input low-low limit
alarm set value
Positive direction
DVHI_PRI deviation alarm U16 DV_HI_PRI Unsigned8 –
priority
Positive direction
PV
DH deviation alarm set F32 DV_HI_LIM Float x 0 to PV span
span
value
Negative direction
DVLO_PRI deviation alarm U16 DV_LO_PRI Unsigned8 –
priority
Negative direction
–PV
DL deviation alarm set F32 DV_LO_LIM Float x –PV span to 0
span
value
Alarm status
FREQ_ALM U32 –
change (*2)
Block mode
FREQ_MOD U32 –
change (*2)
Fieldbus
data type
name name disabled
B030409E.ai

PV span: SH-SL

B3.5 FF Ratio Set Block (FF-RA)

The FF-RA block connects with the RA (Ratio Station) block in a Fieldbus device to enable
n FF-RA Block
The FF-RA block connects with the RA block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-RA
block:
SET
P01
CSV
(CAS_IN)
SV
(SP)
P04
RSV
(RCAS_IN)
(RCAS_OUT)
MV
IN IN_V (OUT) OUT
IN1 IN1_V
TRK_VAL TRK_IN_D
TIN TSI
B030501E.ai
Figure FF-RA Block
n Connecting Terminals of the FF-RA Block

▼ Connection
of the FF-RA block:
Table Connecting Terminals of the FF-RA Block
SET Set value input – – x – – x x
IN Measurement input x – xx x x x x
IN1 Measurement input x – xx x x x x
TIN Tracking input x – xx x x x x
TSI Tracking SW input x – xx x x x x
B030502E.ai
xx: Switch block (SW-33, SW-91) or FF faceplate block

n Processing Timing of the FF-RA Block
n Modes and Statuses of the FF-RA Block

The following shows the block modes, alarm statuses, and block statuses of the FF-RA block:
l Block Mode
Table Block Modes of the FF-RA Block
x x x x x x x
B030503E.ai

l Alarm Status
Table Alarm Statuses of the FF-RA Block
x x x
B030504E.ai

l Block Statuses
Table Block Statuses of the FF-RA Block
SIM
x
B030505E.ai

n Data Items of the FF-RA Block

Table Data Items of the FF-RA Block (1/3)
Fieldbus
data type
name name disabled
O/S
MODE Block mode U32 MODE_BLK DS- 69 x
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
TYPE Function block type U16 –
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
P01 to P04 Extended parameters F32S x
number
Output high-limit MSH
OPHI F32 x MSL <= n <= MSH
index
Output low-limit MSL
OPLO F32 x MSL <= n <= MSH
index
Measurement input
value
Manipulated output
MV F32S OUT DS-65 x(*2) MSL <= n <= MSH
value
Fieldbus
data type
name name disabled
B030506E.ai

*1: Entry is not allowed for CAS/RCAS.

Fieldbus
data type
name name disabled
PV scale high limit
value
PV scale low limit
value
PV scale
engineering unit
PV scale decimal
PVSC_DP I16 PV_SCALE Decimal Point Integer8 –
point position
MV scale high limit
value
MV scale low limit
value
MV scale
engineering unit
CTL_OPTS Control option U16 CONTROL_OPTS Bit String –
IN_V Raw input value F32S IN DS-65 x
PV_FTIME PV filter time constant F32 PV_FTIME Float –
IN1_V Raw input value 1 F32S IN_1 DS-65 x
Ratio input filter
RA_FTIME F32 RA_FTIME Float – 0 <= n
time constant
CSV Cascade set value F32SR CAS_IN DS-65 –
Negative direction set
SV_RDN F32 SP_RATE_DN Float –
value rate limit value
Positive direction set
SV_RUP F32 SP_RATE_UP Float –
SVL Set value low limit F32 SP_LO_LIM Target Float x SL <= n <= SH SL
GAIN Gain F32 GAIN Float x
BKCL_IN Readback input value F32S BKCAL_IN DS-65 –
Manipulated output
MH F32 OUT_HI_LIM Float x MSL <=n <= MSH MSH
high limit value
Manipulated output
ML F32 OUT_LO_LIM Float x MSL <=n <= MSH MSL
low limit value
Readback output
value
BAL_TIME Balance time F32 BAL_TIME Float x 0 <= n 0
Communication
timeout operation
RCAS readback
output value
Fieldbus
data type
name name disabled
B030507E.ai


Fieldbus
data type
name name disabled
TRK scale high limit
value
TRK scale low limit
value
TKSC_UNT TRK engineering unit U16 TRK_SCALE Units Index Unsigned16 –
TRK decimal point Decimal
TKSC_DP I16 TRK_SCALE Integer8 –
position Point
TRK_IN_D Tracking SW U32S TRK_IN_D DS- 66 x 0/1
TKSC_0 <= n <=
TRK_VAL Tracking input value F32S TRK_VAL DS- 65 x
TKSC_100
Input alarm
ALRM_HYS F32 ALARM_HYS Float –
hysteresis
HH_PRI U16 HI_HI_PRI Unsigned8 – 3
alarm priority
HH F32 HI_HI_LIM Float x SL <= n <= SH SH
alarm set value
Input high limit
alarm priority
Input high limit
PH F32 HI_LIM Float x SL <= n <= SH SH
alarm set value
Input low limit alarm
priority
Input low limit alarm
set value
Input low-low limit
alarm priority
Input low-low limit
alarm set value
Positive direction
DVHI_PRI deviation alarm U16 DV_HI_PRI Unsigned8 – 3
priority
Positive direction
DH deviation alarm set F32 DV_HI_LIM Float x 0 to PV span PV
value span
Negative direction
DVLO_PRI deviation alarm U16 DV_LO_PRI Unsigned8 – 3
priority
Negative direction
DL deviation alarm set F32 DV_LO_LIM Float x -PV span to 0 -PV
value span
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B030508E.ai

PV span: SH – SL

B3.6 FF AO Block (FF-AO)

The FF-AO block connects with the AO (Analog Output) block in a Fieldbus device to
n FF-AO Block
The FF-AO block connects with the AO block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-AO
block:
SET
P01
CSV
(CAS_IN) SV MV
(OUT) OUT
(SP)
P04
RSV
(RCAS_IN)
(RCAS_OUT)
B030601E.ai
Figure FF-AO Block
n Connecting Terminals of the FF-AO Block

▼ Connection
of the FF-AO block:
Table Connecting Terminals of the FF-AO Block
B030602E.ai
n Processing Timing of the FF-AO Block

n Modes and Statuses of the FF-AO Block

The following shows the block modes, alarm statuses, and block statuses of the FF-AO block:
l Block Mode
Table Block Modes of the FF-AO Block
x x x x x x x
B030603E.ai

l Alarm Status
Table Alarm Statuses of the FF-AO Block
x x x
B030604E.ai

l Block Statuses
Table Block Statuses of the FF-AO Block
SIM
x
B030605E.ai

n Data Items of the FF-AO Block

Table Data Items of the FF-AO Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Output high-limit
OPHI F32 x MSL <= n <= MSH MSH
index
Output low-limit
OPLO F32 x MSL <= n <= MSH MSL
index
Measurement
input value
Fieldbus
data type
name name disabled
B030606E.ai


Table Data Items of the FF-AO Block (2/2)
Fieldbus
data type
name name disabled
Manipulated output
MV F32S OUT DS-65 x(*2) MSL <= n <= MSH
value
PV scale high limit
value
PV scale low limit
value
PV scale
engineering unit
PVSC_DP I16 PV_SCALE Integer8 –
MV scale high limit
MSH F32 XD_SCALE EU at 100% Float x
value
MV scale low limit
MSL F32 XD_SCALE EU at 0% Float x
value
XDSC_UNT XD engineering unit U16 XD_SCALE Units Index Unsigned16 x
XD decimal point Decimal
XDSC_DP I16 XD_SCALE Integer8 x
position Point
READBACK Readback value F32S READBACK DS-65 x
CSV Cascade set value F32SR CAS_IN DS-65 x
Negative direction set
SV_RDN F32 SP_RATE_DN Float –
Positive direction set
SV_RUP F32 SP_RATE_UP Float –
SVL Set value low limit F32 SP_LO_LIM Float x SL <= n <= SH SL
Fault state transition
FST_TIM F32 FSTATE_TIME Float –
detection time
FST_VAL Fault state value F32 FSTATE_VAL Float x PV_SCALE 0
Readback output
value
Communication
timeout operation
RCAS readback
output value
Alarm status
FREQ_ALM U32
change (*3)
Block mode
FREQ_MOD U32
change (*3)
B030607E.ai

*1: Entry is not allowed for CAS/RCAS.

B3.7 FF DO Block (FF-DO)

The FF-DO block connects with the DO (Discrete Output) block in a Fieldbus device to
n FF-DO Block
The FF-DO block connects with the DO block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-DO
block:
SET
P01
CSV
(CAS_IN) SV MV
AUT (OUT_D) OUT
(SP_D)
P04 MAN
RSV
(RCAS_IN)
(RCAS_OUT)
B030701E.ai
Figure FF-DO Block
n Connecting Terminals of the FF-DO Block

▼ Connection
of the FF-DO block:
Table Connecting Terminals of the FF-DO Block
B030702E.ai

n Processing Timing of the FF-DO Block
n Modes and Statuses of the FF-DO Block

The following shows the block modes, alarm statuses, and block statuses of the FF-DO block:
l Block Mode
Table Block Modes of the FF-DO Block
x x x x x x x
B030703E.ai

l Alarm Status
Table Alarm Statuses of the FF-DO Block
x x x
B030704E.ai

l Block Statuses
Table Block Statuses of the FF-DO Block
SIM
x
B030705E.ai

n Data Items of the FF-DO Block

Table Data Items of the FF-DO Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Measurement
PV U32S PV_D DS-66 –
input value
SV Set value U32S SP_D DS-65 x(*1) 0 <= n <= PV_ST
MV Output value U32S OUT_D DS-66 x(*2) 0/1
Fieldbus
data type
name name disabled
B030706E.ai

*1: Entry is not allowed for CAS/RCAS

Table Data Items of the FF-DO Block (2/2)
Fieldbus
data type
name name disabled
PV_ST Status input value U16 PV_STATE Unsigned16 x 0 <= n
XD_STATE Status XD input value U16 XD_STATE Unsigned16 x
READBACK Readback value U32S READBACK_D DS-66 –
CSV Cascade set value U32S CAS_IN_D DS-66 –
detection time
FST_VAL Fault state value U16 FSTATE_VAL_D Unsigned8 x
Readback output
BKCL_OUT U32S BKCAL_OUT_D DS-66 –
value
RSV Remote set value U32S RCAS_IN_D DS-66 x 0 <= n <= PV_ST
Communication
SHED_OPT timeout operation U16 SHED_OPT Unsigned8 –
RCAS readback
RCAS_OUT U32S RCAS_OUT_D DS-66 –
output value
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
B030707E.ai


B3.8 FF Splitter Block (FF-OS)

The FF-OS block connects with the OS (Output Splitter) block in a Fieldbus device to
n FF-OS Block
The FF-OS block connects with the OS block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-OS
block:
SET
CSV OUT1_V
P01 (CAS_IN) OUT1
(OUT_1)
SV
(sp)
OUT2_V
P04 OUT2
(OUT_2)
B030801E.ai
Figure FF-OS Block
n Connecting Terminals of the FF-OS Block

▼ Connection
of the FF-OS block:
Table Connecting Terminals of the FF-OS Block
OUT1 Manipulated output – – x – – – x
OUT2 Manipulated output – – x – – – x
B030802E.ai

n Processing Timing of the FF-OS Block
n Modes and Statuses of the FF-OS Block

The following shows the block modes, alarm statuses, and block statuses of the FF-OS block:
l Block Mode
Table Block Modes of the FF-OS Block
x x x x x
B030803E.ai

l Alarm Status
Table Alarm Statuses of the FF-OS Block
x x x
B030804E.ai

l Block Statuses
Table Block Statuses of the FF-OS Block
SIM
x
B030805E.ai

n Data Items of the FF-OS Block

Table Data Items of the FF-OS Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
SV Set value F32S SP DS-65 x(*1) 0-100
Fieldbus
data type
name name disabled
B030806E.ai

*1: Entry is not allowed for CAS.

Table Data Items of the FF-OS Block (2/2)
Fieldbus
data type
name name disabled
OUT1_V Output value 1 F32S OUT_1 DS-65 x
Output 1 scale high
O1SC_100 F32 OUT_1_RANGE EU at 100% Float –
limit value
Output 1 scale low
limit value
Output 1
O1SC_UNT U16 OUT_1_RANGE Units Index Unsigned16 –
engineering unit
Output 1 decimal Decimal
O1SC_DP I16 OUT_1_RANGE Integer8 –
Output 2 scale high
limit value
Output 2 scale low
limit value
Output 2
O2SC_UNT U16 OUT_2_RANGE Units Index Unsigned16 –
engineering unit
Output 2 decimal Decimal
O2SC_DP I16 OUT_2_RANGE Integer8 –
CSV Cascade set value F32SR CAS_IN DS-65 –
Readback output
value
IN_ARRAY Input line-segment
F32 IN_ARRAY Float –
[4] value
OT_ARRAY Output line-segment
F32 OUT_ARRAY Float –
[4] value
LOCKVAL Output lock operation U16 LOCKVAL Unsigned8 – 1:nonlock /2:lock 2:lock
Readback input
BKCL_IN1 F32S BKCAL_IN_1 DS-65 –
value 1
Readback input
BKCL_IN2 F32S BKCAL_IN_2 DS-65 –
value 2
BAL_TIME Balance time F32 BAL_TIME Float x 0 <= n 0
HYSTVAL Hysteresis F32 HYSTVAL Float x 0 <= n 0
SSH SV scale high limit F32 –
SSL SV scale low limit F32 –
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B030807E.ai


B3.9 FF Signal Characterizer Block (FF-SC)

The FF-SC block connects with the SC (Signal Characterizer) block in a Fieldbus device to
n FF-SC Block
The FF-SC block connects with the SC block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-SC
block:
IN1_V OUT1_V
IN1 OUT1
(IN_1) (OUT_1)
IN2_V OUT2_V
IN2 OUT2
(IN_2) (OUT_2)
P01
P04
B030901E.ai
Figure FF-SC Block
n Connecting Terminals of the FF-SC Block

▼ Connection
of the FF-SC block:
Table Connecting Terminals of the FF-SC Block
IN1 Input 1 x – xx x x x x
OUT1 Output 1 – – x(*3) – – x x
OUT2 Output 2 – – x(*3) – – x x
B030902E.ai
*3: Cannot be connected when connecting to a selector switch block (SW-33, SW-91).

n Processing Timing of the FF-SC Block
n Modes and Statuses of the FF-SC Block

The following shows the block modes, alarm statuses, and block statuses of the FF-SC block:
l Block Mode
Table Block Modes of the FF-SC Block
x x x
B030903E.ai

l Alarm Status
Table Alarm Statuses of the FF-SC Block
x x x
B030904E.ai

l Block Statuses
Table Block Statuses of the FF-SC Block
SIM
x
B030905E.ai

n Data Items of the FF-SC Block

Table Data Items of the FF-SC Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
AFLS Alarm flashing U32 x
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 x
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Fieldbus
data type
name name disabled
B030906E.ai


Table Data Items of the FF-SC Block (2/2)
Fieldbus
data type
name name disabled
Line-segment input
XSC_100 value scale high F32 X_RANGE EU at 100% Float –
limit value
Line-segment input
XSC_0 value scale low limit F32 X_RANGE EU at 0% Float –
value
Line-segment input
XSC_UNT value engineering U16 X_RANGE Units Index Unsigned16 –
unit
Line-segment input
XSC_DP value decimal point I16 X_RANGE Decimal Integer8 –
position Point
Line-segment output
SH value scale high F32 Y_RANGE EU at 100% Float –
limit value
Line-segment output
SL value scale low limit F32 Y_RANGE EU at 0% Float –
value
Line-segment output
YSC_UNT value engineering U16 Y_RANGE Units Index Unsigned16 –
unit
Line-segment output
YSC_DP value decimal point I16 Y_RANGE Decimal Integer8 –
position Point
Reverse computation
SWAP_2 U16 SWAP_2 Unsigned8 –
operation
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
B030907E.ai


B3.10 FF Integrator Block (FF-IT)

The FF-IT block connects with the IT (Integrator) block in a Fieldbus device to enable
n FF-IT Block
The FF-IT block connects with the IT block in a Fieldbus device to enable operation and
monitoring from the DCS.
The following figure shows a function block diagram of the FF-IT block:
IN1 OUT
IN1_V CPV
(IN_1) (OUT)
IN2 OPTR
IN2_V OPTR_V
(IN_2) (OUT_PTRIP)
RFW1 OTR
RFW1_V OTR_V
(REV_FROW1) (OUT_TRIP)
RFW2
RFW2_V
(REV_FROW2)
P01
RSTC_V
RSTI_V (RESET_
(RESET_IN) CONFIRM)
P04
RSTI RSTC
B031001E.ai
Figure FF-IT Block

n Connecting Terminals of the FF-IT Block

▼ Connection
of the FF-IT block:
Table Connecting Terminals of the FF-IT Block
RFW1 Reverse flow SW1 input x – xx x x x x
RFW2 Reverse flow SW2 input x – xx x x x x
RSTI Reset input x – xx x x x x
OPTR Pre-trip output – – x(*3) – – x x
OTR Trip output – – x(*3) – – x x
RSTC Reset SW output x – xx x x x x
B031002E.ai
*3: Cannot be connected when connecting to selector switch block (SW-33, SW-91).

n Processing Timing of the FF-IT Block
n Modes and Statuses of the FF-IT Block

The following shows the block modes, alarm statuses, and block statuses of the FF-IT block:
l Block Mode
Table Block Modes of the FF-IT Block
x x x
B031003E.ai

l Alarm Status
Table Alarm Statuses of the FF-IT Block
x x x
B031004E.ai

l Block Statuses
Table Block Statuses of the FF-IT Block
SIM
x
B031005E.ai

n Data Items of the FF-IT Block

Table Data Items of the FF-IT Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Fieldbus
data type
name name disabled
B031006E.ai


Table Data Items of the FF-IT Block (2/2)
Fieldbus
data type
name name disabled
TOTAL_SP Total setpoint F32 TOTAL_SP Float x 0 <= n

Computation
CPV F32S OUT DS-65 x SL <= n <= SH
output value
Scale high limit
SH F32 OUT_RANGE EU at 100% Float –
value
Scale low limit
SL F32 OUT_RANGE EU at 0% Float –
value
Output value
OTSC_UNT U16 OUT_RANGE Units Index Unsigned16 –
engineering unit
Output value
Decimal
OTSC_DP decimal point I16 OUT_RANGE Integer8 –
Point
position
OTR_V Trip U32S OUT_TRIP DS-66 x 0/1
OPTR_V Pre-trip U32S OUT_PTRP DS-66 x 0/1
TIME_UN1 Time unit 1 U16 TIME_UNIT1 Unsigned8 –
TIME_UN2 Time unit 2 U16 TIME_UNIT2 Unsigned8 –
Engineering unit
UNIT_CNV conversion F32 UNIT_CONV Float –
coefficient
PLS_V1 Pulse input value 1 F32 PULSE_VAL1 Float –
PLS_V2 Pulse input value 2 F32 PULSE_VAL2 Float – SH
RFW1_V Reverse flow SW1 U32S REV_FLOW1 DS-66 x
RFW2_V Reverse flow SW2 U32S REV_FLOW2 DS-66 x SH
RSTI_V Reset input U32S RESET_IN DS-66 x
Snap shot total
STOTAL F32 STOTAL Float – SL
value
RTOTAL Bad total value F32 RTOTAL Float x
Snap shot bad
SRTOTAL F32 SRTOTAL Float –
total value
Snap shot total
SSP F32 SSP Float –
setpoint
PRE_TRIP Pre-trip value F32 PRE_TRIP Float –
N_RESET Reset count F32 N_RESET Float –
PCT_INCL Valid data rate F32 PCT_INCL Float –
OC_INT Reset command U16 OP_CMD_INT Unsigned8 x 0/1
RSTC_V Reset SW U32S RESET_CONFIRM DS-66 x 0/1
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B031007E.ai


B3.11 FF Input Selector Block (FF-IS)

The FF-IS block connects with the IS (Input Selector) block in a Fieldbus device to enable
n FF-IS Block
The FF-IS block connects with the IS block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-IS block:
OSEL
IN1 OUT
IN1_V OSEL_V CPV

(IN_1) (OP_ (OUT)
SELECT)
IN2 SEL
IN2_V SEL_V
(IN_2) (SELECTED)
IN3
IN3_V
(IN_3)
IN4
IN4_V
(IN_4)
DIS1_V DIS2_V DIS3_V DIS4_V

(DISABLE_1) (DISABLE_2) (DISABLE_3) (DISABLE_4)
P01 P02
DIS1 DIS2 DIS3 DIS4

B031101E.ai
Figure FF-IS Block

n Connecting Terminals of the FF-IS Block

▼ Connection
of the FF-IS block:
Table Connecting Terminals of the FF-IS Block
IN1 Setting input x – xx x x x x
SEL Selection number input – – x(*3) – – x x
DIS1 Input invalid SW input x – xx x x x x
OSEL Selection command input x – xx x x x x
B031102E.ai
*3: Cannot be connected when connecting to selector switch block (SW-33, SW-91).

n Processing Timing of the FF-IS Block
n Modes and Statuses of the FF-IS Block

The following shows the block modes, alarm statuses, and block statuses of the FF-IS block:
l Block Mode
Table Block Modes of the FF-IS Block
x x x
B031103E.ai

l Alarm Status
Table Alarm Statuses of the FF-IS Block
x x x
B031104E.ai

l Block Statuses
Table Block Statuses of the FF-IS Block
SIM
x
B031105E.ai

n Data Items of the FF-IS Block

Table Data Items of the FF-IS Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Fieldbus
data type
name name disabled
B031106E.ai


Table Data Items of the FF-IS Block (2/2)
Fieldbus
data type
name name disabled
Computation output
CPV F32S OUT DS-65 x SL <= n <= SH
value
SH Scale high limit value F32 OUT_RANGE EU at 100% Float –
SL Scale low limit value F32 OUT_RANGE EU at 0% Float –
Output value
OTSC_UNT U16 OUT_RANGE Units Index Unsigned16 –
engineering unit
Output value Decimal
OTSC_DP I16 OUT_RANGE Integer8 –
decimal point position Point
DIS1_V Input invalid SW1 U32S DISABLE_1 DS-66 x 0/1
SEL_TYPE Selection operation U16 SELECT_TYPE Unsigned8 –
Input value bad
MIN_GOOD U16 MIN_GOOD Unsigned8 –
threshold value
SEL_V Selection number U32S SELECTED DS-66 –
OSEL_V Selection command U32S OP_SELECT DS-66 x 0 to 4
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
B031107E.ai


B3.12 FF Multiple DI Block (FF-MDI)

The FF-MDI block connects with the MDI (Multiple Discrete Input) block in a Fieldbus
device to enable operation and monitoring from the DCS.
n FF-MDI Block
The FF-MDI block connects with the MDI block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-MDI
block:
OUT1
OUT1_V
(OUT_D1)
OUT2
OUT2_V
(OUT_D2)
OUT3
OUT3_V
(OUT_D3)
OUT4
OUT4_V
(OUT_D4)
OUT5
OUT5_V
(OUT_D5)
OUT6
OUT6_V
(OUT_D6)
OUT7
OUT7_V
P01
(OUT_D7)
OUT8
P02
OUT8_V
(OUT_D8)
B031201E.ai
Figure FF-MDI Block

n Connecting Terminals of the FF-MDI Block

▼ Connection
of the FF-MDI block:
Table Connecting Terminals of the FF-MDI Block
OUT1 Output 1 – – x(*3) – – x x
OUT2 Output 2 – – x(*3) – – x x
OUT3 Output 3 – – x(*3) – – x x
OUT4 Output 4 – – x(*3) – – x x
OUT5 Output 5 – – x(*3) – – x x
OUT6 Output 6 – – x(*3) – – x x
OUT7 Output 7 – – x(*3) – – x x
OUT8 Output 8 – – x(*3) – – x x
B031202E.ai

n Processing Timing of the FF-MDI Block
n Modes and Statuses of the FF-MDI Block

The following shows the block modes, alarm statuses, and block statuses of the FF-MDI block:
l Block Mode
Table Block Modes of the FF-MDI Block
x x x
B031203E.ai

l Alarm Status
Table Alarm Statuses of the FF-MDI Block
x x x
B031204E.ai

l Block Statuses
Table Block Statuses of the FF-MDI Block
SIM
x
B031205E.ai

n Data Items of the FF-MDI Block

Table Data Items of the FF-MDI Block
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
OMOD Block mode (lowest) U32 –
CMOD Block mode (highest) U32 –
number
OUT1_V Output value 1 U32S OUT_D1 DS- 66 x 0/1
Alarm status –
FREQ_ALM U32
change (*1)
Block mode –
FREQ_MOD U32
change (*1)
Fieldbus
data type
name name disabled
B031206E.ai


B3.13 FF Multiple DO Block (FF-MDO)

The FF-MDO block connects with the MDO (Multiple Discrete Output) block in a Fieldbus
n FF-MDO Block
The FF-MDO block connects with the MDO block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-MDO
block:
IN1
IN1_V
(IN_D1)
IN2
IN2_V
(IN_D2)
IN3
IN3_V
(IN_D3)
IN4
IN4_V
(IN_D4)
IN5
IN5_V
(IN_D5)
IN6
IN6_V
(IN_D6)
IN7
IN7_V
(IN_D7)
IN8
IN8_V
(IN_D8)
P01
P02
B031301E.ai
Figure FF-MDO Block

n Connecting Terminals of the FF-MDO Block

▼ Connection
of the FF-MDO block:
Table Connecting Terminals of the FF-MDO Block
IN1 Setting input – – x – – x x
B031302E.ai

n Processing Timing of the FF-MDO Block
n Modes and Statuses of the FF-MDO Block

The following shows the block modes, alarm statuses, and block statuses of the FF-MDO block:
l Block Mode
Table Block Modes of the FF-MDO Block
x x x
B031303E.ai

l Alarm Status
Table Alarm Statuses of the FF-MDO Block
x x x
B031304E.ai

l Block Statuses
Table Block Statuses of the FF-MDO Block
SIM
x
B031305E.ai

n Data Items of the FF-MDO Block

Table Data Items of the FF-MDO Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
B031306E.ai


Table Data Items of the FF-MDO Block (2/2)
Fieldbus
data type
name name disabled

detection time
FST_VAL1 Fault state value 1 U16 FSTATE_VAL_D1 Unsigned8 x
FST_STS Fault state U16 FSTATE_STATUS Unsigned8 –
IN1_V Raw input value 1 U32S IN_D1 DS-66 x
MO_OPTS Multiple I/O options U16 MO_OPTS Bit String –
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B031307E.ai


B3.14 FF Multiple AI Block (FF-MAI)

The FF-MAI block connects with the MAI (Multiple Analog Input) block in a Fieldbus device
to enable operation and monitoring from the DCS.
n FF-MAI Block
The FF-MAI block connects with the MAI block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-MAI
block:
OUT1
OUT1_V
(OUT_1)
OUT2
OUT2_V
(OUT_2)
OUT3
OUT3_V
(OUT_3)
OUT4
OUT4_V
(OUT_4)
OUT5
OUT5_V
(OUT_5)
OUT6
OUT6_V
(OUT_6)
OUT7
OUT7_V
P01
(OUT_7)
OUT8
P02
OUT8_V
(OUT_8)
B031401E.ai
Figure FF-MAI Block

n Connecting Terminals of the FF-MAI Block

▼ Connection
of the FF-MAI block:
Table Connecting Terminals of the FF-MAI Block
OUT1 Output 1 – – x(*3) – – x x
OUT2 Output 2 – – x(*3) – – x x
OUT3 Output 3 – – x(*3) – – x x
OUT4 Output 4 – – x(*3) – – x x
OUT5 Output 5 – – x(*3) – – x x
OUT6 Output 6 – – x(*3) – – x x
OUT7 Output 7 – – x(*3) – – x x
OUT8 Output 8 – – x(*3) – – x x
B031402E.ai

n Processing Timing of the FF-MAI Block
n Modes and Statuses of the FF-MAI Block

The following shows the block modes, alarm statuses, and block statuses of the FF-MAI block:
l Block Mode
Table Block Modes of the FF-MAI Block
x x x
B031403E.ai

l Alarm Status
Table Alarm Statuses of the FF-MAI Block
x x x
B031404E.ai

l Block Statuses
Table Block Statuses of the FF-MAI Block
SIM
x
B031405E.ai

n Data Items of the FF-MAI Block

Table Data Items of the FF-MAI Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
OUT1_V Output value 1 U32S OUT_1 DS- 65 x
Fieldbus
data type
name name disabled
B031406E.ai


Table Data Items of the FF-MAI Block (2/2)
Fieldbus
data type
name name disabled
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
B031407E.ai

B3.15 FF Multiple AO Block (FF-MAO)

The FF-MAO block connects with the MAO (Multiple Analog Output) block in a Fieldbus
n FF-MAO Block
The FF-MAO block connects with the MAO block in a Fieldbus device to enable operation and
monitoring from the DCS. The following figure shows a function block diagram of the FF-MAO
block:
IN1
IN1_V
(IN_1)
IN2
IN2_V
(IN_2)
IN3
IN3_V
(IN_3)
IN4
IN4_V
(IN_4)
IN5
IN5_V
(IN_5)
IN6
IN6_V
(IN_6)
IN7
IN7_V
(IN_7)
IN8
IN8_V
(IN_8)
P01
P02
B031501E.ai
Figure FF-MAO Block

n Connecting Terminals of the FF-MAO Block

▼ Connection
of the FF-MAO block:
Table Connecting Terminals of the FF-MAO Block
B031502E.ai

n Processing Timing of the FF-MAO Block
n Modes and Statuses of the FF-MAO Block

The following shows the block modes, alarm statuses, and block statuses of the FF-MAO block:
l Block Mode
Table Block Modes of the FF-MAO Block
x x x
B031503E.ai

l Alarm Status
Table Alarm Statuses of the FF-MAO Block
x x x
B031504E.ai

l Block Statuses
Table Block Statuses of the FF-MAO Block
SIM
x
B031505E.ai

n Data Items of the FF-MAO Block

Table Data Items of the FF-MAO Block (1/2)
Fieldbus
data type
name name disabled
O/S
(AUT)
Alarm detection
AF U32 –
specification
Alarm off
AOFS U32 –
specification
Block mode
OMOD U32 –
(lowest)
Block mode
CMOD U32 –
(highest)
number
Fieldbus
data type
name name disabled
B031506E.ai


Table Data Items of the FF-MAO Block (2/2)
Fieldbus
data type
name name disabled
detection time
FST_VAL1 Fault state value 1 F32 FSTATE_VAL_1 Float x
FSTATE_
FST_STS Fault state U16 Unsigned8 –
STATUS
MO_OPTS Multiple I/O options U16 MO_OPTS Bit String –
Alarm status
FREQ_ALM U32 –
change (*1)
Block mode
FREQ_MOD U32 –
change (*1)
Fieldbus
data type
name name disabled
B031507E.ai


Blank Page
TocC-1
CENTUM VP
CONTENTS
PART-C System Fieldbus Support
C1. Fieldbus Operation and Monitoring .....................................................C1-1
C1.1 Operation and Monitoring of FF Faceplate Blocks..................................... C1-2
C1.2 Messages......................................................................................................... C1-3
C1.3 System Maintenance...................................................................................... C1-5

Blank Page
<C1. Fieldbus Operation and Monitoring> C1-1
C1. Fieldbus Operation and Monitoring

It is possible to operate and monitor a Fieldbus system in the same way as an FCS. This
chapter explains the operation and monitoring of a Fieldbus system, which involves the
operation and monitoring of FF faceplate blocks, messages, and system maintenance.

C1.1 Operation and Monitoring of FF Faceplate

Blocks
A Fieldbus block can be operated and monitored through an FF faceplate block.
An FF faceplate block can be operated and monitored in the same manner as other FCS
function blocks, from the following windows:
• Graphic view
• Trend view
• Tuning view
• Faceplate view
• Control Drawing view
• Process Report view
• System Alarm view
• Process Alarm view
• Historical Message Report window
SEE
ALSO For the detailed information on the operation of each window, see the followings:
E3, “Windows Convenient for Operation and Monitoring” in CENTUM VP Reference, HIS (IM 33M01A30-
40E)
E4, “Windows for System Administration” in CENTUM VP Reference, HIS (IM 33M01A30-40E)
E8, “Window for Process Status and Operation Record Confirmation” in CENTUM VP Reference, HIS (IM
33M01A30-40E)

C1.2 Messages
The messages necessary for operating and monitoring a Fieldbus system are displayed
on an HIS in the same way as messages from an FCS. The various types of messages
displayed are listed in the following, along with brief descriptions of each type of
message.
SEE
ALSO For more details on the Fieldbus system messages, see the following:
2.10, “Fieldbus Messages” in Operating Messages (IM 33M05D20-40E)
n Process Alarm
Process alarms such as HI and LO reported from an FF faceplate block are displayed in the
Process Alarm view.
n System Alarm
Messages related to errors in Fieldbus devices and the ALF111 module are displayed in the
System Alarm view. System alarms include the following:
• Errors generated by input/output modules and messages of input/output modules returning
to normal
• Communication errors generated by input/output modules and messages of input/output
modules returning to normal
l Fieldbus Device Communication Errors

Messages regarding errors in the communication with a Fieldbus device, detected by the ALF111
module, are displayed in the System Alarm view.
l Fieldbus Device Self-Diagnosis Errors

If an error is detected during the self-diagnosis of a Fieldbus device, a message that reports the
error is displayed in the System Alarm view.
l ALF111 System Alarm

A message indicating an error in the ALF111 module itself is displayed in the System Alarm view.
n Status Change Notification

If the status of a Fieldbus block is changed directly from Device Management Tool, etc. to
the operating system, and this change has not been initiated from an HIS, the change to the
operating system is reported as a status change notification.

n Fieldbus Messages
The messages related to the Fieldbus include alerts reported from the Fieldbus devices and
messages of self-diagnosis errors in the ALF111 module itself.
l Fieldbus Device Alerts

Alerts reported from Fieldbus devices are displayed in the Historical Message Report window as
Fieldbus messages. Fieldbus device alerts includes the following:
• Error alarms generated by Fieldbus devices and messages of Fieldbus devices returning to
normal
• Process alarms generated by Fieldbus devices and messages of Fieldbus devices returning
to normal
• Update events of Fieldbus devices
• Changes in the write-protect status of Fieldbus devices
l ALF111 Self-Diagnosis Errors and Updates

Alerts related to self-diagnosis errors and updates of the ALF111 module are displayed in the
Historical Message Report window as Fieldbus messages.

C1.3 System Maintenance

The status of the ALF111 module can be displayed in the system maintenance windows.
SEE
ALSO For the status display of the ALF111 module, see the following:
E4.8, “KFCS Status Display View” in CENTUM VP Reference, HIS (IM 33M01A30-40E)
n ALF111 Module Status Display

If there is an abnormality in the communication with a Fieldbus device, the port corresponding to
the segment to which the Fieldbus device is connected is displayed as nC (n is a port number)
and the module is displayed in red in the ALF111 status display. An error refers to cases where
the ALF111 module cannot identify a Fieldbus device in a communication circuit. The cause can
be one of the following:
• The Fieldbus device is not connected to the Fieldbus.
• The Fieldbus device fails to operate properly.
• The node address of the Fieldbus device is different from the node address specified by
Builder.
• Power is not supplied to Fieldbus devices (for example, the external power supply is out of
service or not connected, or the power switch is OFF when power is supplied to the Fieldbus
device from an external power supply).
If the communication with all Fieldbus devices connected to a segment is normal, no errors
are displayed for the port (nC) connected to that segment. If all ports are normal, the module is
displayed in green.
n ALF111 Module Report

ALF111 module information is displayed in the Report dialog box. The size is equivalent to 1K
bytes of memory.
SEE
ALSO For more details on the Report dialog box of the I/O module, see the following:
E4.8.3, “FCS Report Dialog Box” in CENTUM VP Reference, HIS (IM 33M01A30-40E)

Blank Page
TocD-1
CENTUM VP
CONTENTS
PART-D Fieldbus Engineering
D1. System Engineering................................................................................D1-1
D1.1 Engineering of the ALF111 Module............................................................... D1-2
D1.2 Creating a New FF Faceplate Block.............................................................. D1-8
D1.3 Modifying an FF Faceplate Block................................................................ D1-13
D1.4 Creating a Simplified Universal Block . ..................................................... D1-17
D1.4.1 General Operation Flow . .............................................................. D1-18
D1.4.2 Creating a Simplified Universal Block . ......................................... D1-21
D1.4.3 Assigning a Custom Block to a Simplified Universal Block........... D1-23
D1.4.4 Defining an I/O Parameter Name ................................................. D1-25
D1.4.5 Connecting a Simplified Universal Block in the Function Block
Overview Builder . ......................................................................... D1-27
D1.4.6 Defining Detail Parameters for a Simplified Universal Block . ...... D1-28
D1.5 Starting Up Fieldbus Builder....................................................................... D1-29
D1.6 Other Engineering Items.............................................................................. D1-30
D2. Fieldbus Builder .....................................................................................D2-1
D2.1 Overview of Fieldbus Builder ....................................................................... D2-2
D2.2 Overview of the Window Structure............................................................... D2-5
D2.2.1 Overall Window Structure................................................................ D2-6
D2.2.2 Tree View......................................................................................... D2-7
D2.2.3 Segment Tab.................................................................................... D2-8
D2.2.4 Device Tab..................................................................................... D2-13
D2.3 Standard Engineering.................................................................................. D2-15
D2.3.1 Environment Settings..................................................................... D2-16
D2.3.2 Starting Up and Closing Down....................................................... D2-23
D2.3.3 Configuring a New Fieldbus System............................................. D2-24
D2.3.4 Modifying Fieldbus Devices........................................................... D2-35
D2.3.5 Downloading to Fieldbus Devices................................................. D2-38
D2.3.6 Uploading the Block Parameters................................................... D2-48
D2.3.7 Tag Assignment/Address Assignment/Device Class Setting........ D2-49

TocD-2
D2.4 Advanced Engineering................................................................................. D2-51
D2.4.1 Data Access through Input/Output Terminals................................ D2-52
D2.4.2 Tuning Block Parameter Values.................................................... D2-54
D2.4.3 Updating Capabilities Files and DD Files...................................... D2-57
D2.4.4 Replacing Fieldbus Devices.......................................................... D2-59
D2.4.5 Display and Adjust Schedule ........................................................ D2-63
D2.4.6 Tuning Communication Parameter Values.................................... D2-68
D2.4.7 Setting Trend Objects.................................................................... D2-71
D2.4.8 Manually Copying Device For Registering Device........................ D2-72
D2.4.9 Create and Use Template on Fieldbus Builder.............................. D2-74
D2.5 Other Engineering......................................................................................... D2-80
D2.6 Menu List........................................................................................................ D2-81
D3. Engineering Tests...................................................................................D3-1
D3.1 Operation when I/O is Disconnected............................................................ D3-2
D3.2 Wiring Test....................................................................................................... D3-4
D3.3 Alarm Status and Block Mode Setting Tests............................................... D3-6
D3.4 FF Faceplate Block Input/Output Test.......................................................... D3-8
D3.5 Individual Processing during the FF Faceplate Block Input/Output
Test................................................................................................................. D3-10
D4. Tools Related to Fieldbus Engineering.................................................... D4-1
D4.1 Copy Tool for Fieldbus Associated Files .................................................... D4-2
D5. Device Panel............................................................................................D5-1
D5.1 Device Panel Overview................................................................................... D5-2
D5.2 Menu List.......................................................................................................... D5-5
D5.3 Basic Operation.............................................................................................. D5-9
D5.3.1 Starting and Quitting.......................................................................D5-11
D5.3.2 Environment Settings..................................................................... D5-13
D5.3.3 Device Recognition and Status Display......................................... D5-16
D5.3.4 Device Information Display............................................................ D5-20
D5.3.5 Equalization................................................................................... D5-22
D5.4 Advanced Operations................................................................................... D5-33
D5.4.1 Editing Device Information............................................................. D5-34
D5.4.2 Displaying Block Parameter Values............................................... D5-37
D5.4.3 Adjusting Block Parameter Values................................................ D5-41
D5.4.4 Displaying Detailed Device Information......................................... D5-43
D5.4.5 Replacing Devices......................................................................... D5-45
D5.4.6 Communication.............................................................................. D5-48
D5.4.7 Registering New Device on Device Panel..................................... D5-50
D5.4.8 Create or Open Template File on Device Panel............................ D5-52

<D1. System Engineering> D1-1
D1. System Engineering

This chapter explains the flow of the Fieldbus engineering. It also covers the engineering
of the ALF111 module, engineering using Function Block Builder, and other Fieldbus
engineering.

D1.1 Engineering of the ALF111 Module

This section explains how to engineer the “Fieldbus H1 communication module (ALF111
module),” which acts as an interface between an FCS and Fieldbus devices. In particular,
the operations for creating a new Fieldbus communication module and for modifying and
deleting an existing Fieldbus communication module are explained.
SEE
ALSO For more information on the basic functions and operations of the related IOM Builder, see the following:
F2.5, “Creating a New IOM” in CENTUM VP Reference, Engineering (IM 33M01A30-40E)

n Creating a New Module

The ALF111 module can be defined for the following FCS types: AFG30S, AFG30D, AFG40S,
AFG40D, AFG81S, AFG81D, AFG82S, AFG82D, AFG83S, AFG83D, AFG84S, AFG84D,
AFS30S, AFS30D, AFS40S, AFS40D, AFS81S, AFS81D, AFS82S, AFS82D, AFS83S, AFS83D,
AFS84S, AFS84D, AFF50S and AFF50D.
While the [Node] folder is being selected in System View, select [Create New] - [IOM] from the
[File] menu. A dialog box for creating new IOM is displayed. Specify the following items:
• IOM Type (Category) : Fieldbus communication
• IOM Type (Type) : ALF111 (Foundation Fieldbus (FF-H1) Communication)
• Installation Position (Slot) : 1 to 8
SEE
ALSO For more details on the module properties, see the following:
“n Properties of the Module”
The figure below shows the display image of System View when an ALF111 module is created at
node 1 of FCS0102. When a new ALF111 module is created, the following builder file and folder
are created at the same time.
• A builder file common to all modules
• A builder file for each port and a folder where it is stored
System View – NODE1
File Edit View Tools Load Project FCS HIS Help
a 87
z
All Folders Opened Folder : NODE1
- SYSTEM VIEW Name Type Modified
+ PJT20 1ALF111 ALF111 [Foundation Fieldbus [FF-H1] Com... 2008/03/20 11:33
- PJT25 2AAI841-S AAI841-S [8-Point Current Input 8-Point Cu... 2008/03/20 16:27
+ COMMON 3ADV141-P ADV141-P [16-Point Status Input, 100VAC] 2008/03/20 16:36
+ BATCH
+ FCS0101
- FCS0102
CONFIGURATION
+ SEQ_LIBRARY
- IOM
- NODE1
1ALF111
SWITCH
MESSAGE
+ FUNCTION_BLOCK
+ DISPLAY
+ HIS0163
+ HIS0164
3 Objects
D010101E.ai
Figure Definition of the ALF111 Module in System View

l Builder Files for Each Port
When the folder that stores builder files for each port (sALF111: s indicates a slot number) is
selected in System View, four builder files (sALF111-p: s indicates a slot number and p indicates
a port number), one for each port, are displayed. It is possible to start Fieldbus Builder by double-
clicking one of the builder files corresponding to one of the ports.
System View – NODE1
File Edit View Tools Load Project FCS HIS Help
a 87
z
All Folders Opened Folder : NODE1
- SYSTEM VIEW Name Type Modified Comment
+ PJT20T04 1ALF111-1 Field device 2008/03/20 14:21
- PJT25 1ALF111-2 Field device 2008/03/20 14:35
+ COMMON 1ALF111-3 Field device 2008/03/20 14:35
+ BATCH 1ALF111-4 Field device 14:35
+ FCS0101
- FCS0102
CONFIGURATION
+ SEQ_LIBRARY
- IOM
- NODE1
1ALF111
SWITCH
MESSAGE
+ FUNCTION_BLOCK
+ DISPLAY
+ HIS0163
+ HIS0164
3 Objects
D010102E.ai
Figure Display of Builder Files for Each Port in System View

n Properties of the Module

In order to change the properties of an ALF111 module, select the sALF111(s indicates a slot
number) file in System View, and then select [Properties] in the [File] menu. Alternatively, select
a builder file, right-click the mouse to display a pop-up menu, and then select [Properties] in the
displayed menu. The property sheet will be called up. The following explains the items that can
be set in the property sheet:
l Type and Position Tab

• Duplicate Next Card
Check the [Duplicate Next Card] check box in order to make an ALF111 module duplex.
This designation is allowed only for modules in odd slots. This check box is not checked by
default, i.e., the module is the “not duplex” state.
IMPORTANT
The ALF111 modules will be restarted during the download operation after making changes to the
duplex settings.
SEE
ALSO For the operation when ALF module is restarted, see the following:
B1.2.3, “ALF111 Operations at the Occurrence of an Abnormality and at Recovery”
• High Speed Read

The check box needs to be checked when reading data from ALF111 module at a high
speed.
• IOM Comment
A comment of up to 12 double-byte characters or 24 single-byte characters can be entered.
l Setting Details Tab

▼ Perform Fallback, Command
• Perform Fallback
Check this check box in order to perform fallback operation. This check box is checked by
default, i.e., the module is in the “perform fallback” state.
• Command Line
Whether or not to check the disconnection of the front connector can be designated.

l Details of Contents that can be Specified in the Command Line
Specify whether or not the module will be checked for the disconnection of the front connector. If
a front connector disconnection error is detected when the front connector disconnection check is
enabled, the IOM (Input Output Module) will fail. The format of the command line is as follows:
CNCTCHK = Yes
The parameters are as follows:

Yes:
Performs the front connector disconnection check (default when a module is specified to be
in duplex operation).
No:
Does not perform the front connector disconnection check (default when a module is
specified to be in single operation).
Detection Interval for Abnormalities in the Communication Route to Fieldbus Devices

(CERRDET).
When switching the ALF111 upon communication error is set on the FCS Constant Builder
of KFCS2, FFCS or RFCS5 type FCS, this Command Line can be used for setting a proper
detection interval.
The time unit for the interval of detecting the error on communication route to the fieldbus devices
is minute. By default, the interval is 3 minutes.
It means, if the command line is empty, the detection will be performed each three minutes.
The syntax of the command is as follows:
Example:
When specify a 6-minute interval
CERRDET=6
The parameter can be a number ranged from 3 to 1440. Or can be a string of NO.
CERRDET=NO
Means do not detect the error on the communication route. This will be valid for both the
modules in the dual-redundant configuration.
SEE
ALSO • For more details on the front connector disconnection check, see the following:
“l Detection of Front Connector Disconnection” in “ Duplexing ALF111s” in B1.3, “Making FCSs
Redundant”
• For more details detecting abnormalities communication route between ALF111 and Fieldbus Devices, see
the following:
“l Detecting Abnormalities in the Communication Route between ALF111 and Fieldbus Devices” in “
Duplexing ALF111s” in B1.3, “Making FCSs Redundant”

n Properties for Each Port

In order to change properties for each port, select the builder file for the port whose properties are
to be changed. The file is displayed by selecting the ALF111 module in System View. Then select
[Properties] in the [File] menu. Alternatively, select the builder file, and click the right mouse
button and select [Properties] in the displayed pop-up menu. The property sheet is called up. The
following explains the items that can be set in the sheet.
l Type and Position Tab

• IOM Comment
It is possible to enter a comment of up to12 double-byte characters or 24 single-byte
characters here.
l Setting Details Tab

• High-Limit Counts to ignore BNU Communication Error
This value indicates the maximum allowable number of times errors are detected when an
input data update is interrupted during BNU communication (communication used between
Fieldbus devices or between a Fieldbus device and an ALF111). Designate an integer
from 0 to 255. Error detection is not performed at all if 0 is designated. The initial value is 5.
Normally use the initial value.
• Re-Establish Connection cycle
Designate the time interval between attempting to re-establish connection between the
ALF111 module and a Fieldbus device in units of seconds. An integer from 0 to 120 seconds
should be designated. The connection will not be re-established at all if 0 is designated. The
initial value is 10 seconds. Normally use the initial value.
• RCAS Write Cycle
Designate the write cycle from an FCS function block to a Fieldbus block in the RCAS mode
in units of seconds. Designate an integer from 0 to 120 seconds. The initial value is 10
seconds.
n Deleting a Module
In order to delete an existing ALF111 module definition, select the sALF111 (s indicates a slot
number) file and then [Delete] in the [File] menu. Alternatively, right-click the mouse to display a
pop-up menu, and then select [Delete] in the menu. When the existing ALF111 module definition
is deleted, all the four ports included in the module definition are also deleted. In the case of a
current project, downloading will be performed.
n Downloading
In System View select the folder for the node unit that contains the builder file of the ALF111
module, and then select [Download to IOM] in the [Load] menu to display the IOM Download
dialog box. Select the target ALF111 module in this dialog box, and then click the [OK] button to
start IOM downloading. All four ports will be targets of this downloading operation. However, the
engineering data will not be downloaded to Fieldbus devices.
SEE
ALSO For more information on the downloading operation, see the following:
B1.4, “Download Operations”

D1.2 Creating a New FF Faceplate Block

This section explains the procedure for creating new FF faceplate blocks. FF faceplate
blocks can be created in the same way as regular FCS function blocks. However, if
Fieldbus devices have been registered with Fieldbus Builder, the Fieldbus Block List
dialog box can be used to assign Fieldbus devices to FF faceplate blocks. First, the
Fieldbus Block List dialog box in Control Drawing Builder is explained in order to
describe the procedures when Fieldbus devices are registered using Fieldbus Builder and
when they are not registered.
SEE
ALSO For more details on how to register Fieldbus devices using Fieldbus Builder, see the following:
D2.3.3, “Configuring a New Fieldbus System”
n Fieldbus Block List Dialog Box

▼ Fieldbus Block List
FF faceplate blocks can be created using the same procedure as for regular FCS function blocks.
However, it is possible to call up the “Fieldbus Block List dialog box” from Control Drawing Builder
or Function Block Overview Builder. This dialog box is used to assign Fieldbus devices to FF
faceplate blocks. By using this dialog box, it becomes possible to assign devices to FF faceplate
blocks efficiently. This dialog box can be used effectively when Fieldbus devices are registered
using Fieldbus Builder.
l Calling Up the Dialog Box

The Fieldbus Block List dialog box can be called up by selecting [Fieldbus Block List] in the
[Window] menu of Control Drawing Builder or Function Block Overview Builder. Also can be
called up by right clicking the FF faceplate block and then choose [Fieldbus Block List] from the
pop-up menu.

l Appearance of the Dialog Box
The figure below shows the Fieldbus Block List dialog box.
Fieldbus Block List [pjt:MYPJT Stn:FCS0101]
Pin button Title bar

Device Tag Name Block Tag Name Type Block Label Position
AE100LC1_01 (AI_01) AI Analog Input 1-4-1-3
AE100LC1_01 (PID_01) PID PID Control 1-4-1-3
EJALC1_01 (AI_01) AI Analog Input 1-1-1-1
* EJALC1_01 AI-01 AI Analog Input 1-1-1-1
List EJALC1_01 (PID_01) PID PID Control 1-1-1-1
YF100ELC1_01 (AI_01) AI Analog Input 1-1-1-1
* YF100ELC1_01 PID-01 PID PID Control 1-1-1-1
YVPLC1_01 (AO_01) AO Analog Output 1-1-1-2
YVPLC1_01 (DI_01) DI Discrete Input 1-1-1-2
YVPLC1_01 (DI_02) DI Discrete Input 1-1-1-2
* YVPLC1_01 PID-02 PID PID Control 1-1-1-2
Refresh Close
D010201E.ai
Figure Fieldbus Block List Dialog Box
• Device Tag Name

The device tag name of the selected Fieldbus block is displayed. If the device is already
assigned to an FF faceplate block, an “*” (asterisk) is displayed at the head of the device tag
name. Nothing is displayed if the device has not been assigned.
• Block Tag Name
The block tag name of the selected Fieldbus block included in the Fieldbus device
is displayed. If the block tag name has not been defined, the block ID is displayed in
parentheses.
• Type
The type of the selected Fieldbus block included in the Fieldbus device is displayed.
• Block Label
The block label of the selected Fieldbus block included in the Fieldbus device is displayed. If
the block label is not displayed, click the [Refresh] button. This will display the block label.
• Position
The information of the segment that includes the selected Fieldbus device is displayed in
the form of the position where the card is mounted (node number and slot number) and the
port number on the card.
• Pin Button
This button is used to specify the hierarchical relationship between the Fieldbus Block List
dialog box and other windows. If this pin is up, the Fieldbus Block List dialog box is always
displayed on top of other windows. If this pin is lying sideways, the Fieldbus Block List dialog
box is hidden underneath other active windows.
l Operations Performed from the Dialog Box

It is possible to select any Fieldbus block from the devices listed in the Fieldbus Block List dialog
box. The Fieldbus device selected in this dialog box can be used for the definitions made by
Control Drawing Builder or Function Block Overview Builder. In addition, it is possible to sort the
lists using each item as a key. Moreover, by selecting a block and clicking the right mouse button,
a pop-up menu is displayed where it is possible to call up the copy function as well as Fieldbus
Builder.

n When Fieldbus Devices are Already Registered

If Fieldbus devices are already registered using Fieldbus Builder, it is possible to define FF
faceplate blocks for the registered Fieldbus blocks using the Fieldbus Block List dialog box.
l Creating a New FF Faceplate Block Using Control Drawing Builder

1. Select [Fieldbus Block List] in the [Window] menu to call up the Fieldbus Block List dialog
box.
2. Select a Fieldbus block in the Fieldbus Block List dialog box, and drag and drop it in the
empty area in the Drawing pane of Control Drawing Builder.
Fieldbus Block List
EJA100A-1 [AI_001] AI 1-1-1
EJA100A-1 AI002 AI 1-1-1
Drag & Drop
Control Drawing Builder Control Drawing Builder
AI002 FF-AI
AI002
FF-AI
D010202E.ai
Figure Creating a New FF Faceplate Block Using the Fieldbus Block List Dialog Box
3. Then the FF faceplate block corresponding to the selected Fieldbus block is defined. If
a block tag name is assigned to the Fieldbus block at this point, that tag name is also
assigned to the FF faceplate block.
IMPORTANT
Note the following precautions at the drag and drop operation:
• It is not allowed to drag and drop a block onto a drawing of a different FCS.
• If the number of function blocks defined in a drawing has reached the maximum allowable
number of function blocks, no more Fieldbus blocks can be dragged and dropped onto that
drawing.
4. Perform the download operation to put the FF faceplate block in the assigned state.

l Creating a New FF Faceplate Block Using Function Block Overview Builder
box.
2. Select a Fieldbus block in the Fieldbus Block List dialog box. Click the right mouse button to
display the pop-up menu and select the [Copy] menu to copy and paste the Fieldbus block
to an empty line of the Function Block Overview Builder.
Fieldbus Block List
EJA100A-1 [AI_001] AI 1-1-1
EJA100A-1 AI002 AI 1-1-1
Copy & Paste
Function Block Overview Builder Function Block Overview Builder
AI002 FF-AI
D010203E.ai
Figure Creating a New FF Faceplate Block Using Function Block Overview Builder
3. Then the FF faceplate block corresponding to the selected Fieldbus block is defined. If
a block tag name is assigned to the Fieldbus block at this point, that tag name is also
assigned to the FF faceplate block.
4. Perform the download operation to put the FF faceplate block in the assigned state.

n When Fieldbus Devices are not Registered

If a Fieldbus device has not been registered using Fieldbus Builder, the Fieldbus Block List dialog
box cannot be used. Use the following procedure instead. It is also possible to use this procedure
when a Fieldbus device is already registered.
l Creating a New FF Faceplate Block Using Control Drawing Builder or Function

Block Overview Builder
Use the same procedure as when creating a new function block under normal circumstances. If
a Fieldbus device with the same model name is already registered, the status of the FF faceplate
block becomes assigned by matching the tag name with the block tag name of the Fieldbus
device and performing the download operation. If the Fieldbus device is not registered, the status
of the FF faceplate block becomes unassigned.
IMPORTANT
On Control Drawing Builder, if a FF faceplate block assigned with a physical Fieldbus device is
connected to a FF faceplate block not assigned with a physical Fieldbus device, both blocks are
parsed as invalid elements. This phenomenon can be avoided by assigning physical Fieldbus
devices to both blocks. After completing the assignment of the unassigned faceplate block, it is
necessary to run [Resolve Invalid Elements] on System View.

D1.3 Modifying an FF Faceplate Block

This section explains how to make changes to an already defined FF faceplate block,
in particular, how to set block parameters with Control Drawing Builder, how to change
loops, and how to speed up data access.
n Setting the Block Parameters

The Fieldbus block parameter data related to engineering is defined with Function Block Detail
Builder as detailed parameters for a FF faceplate block. Parameters related to tuning data and
extended parameters can be set only with Fieldbus Builder.
SEE
ALSO • For more information on the parameter setting operation using Fieldbus Builder, see the following:
• For detailed explanations on data items unique to FF faceplate blocks, see the following:
B2.9, “Builder Definition Items of FF Faceplate Blocks”
l Designating the Sub-Schedule Number

Fieldbus blocks have a detailed definition item called a “sub-schedule number.” This value can be
changed in the property sheet of Function Block Detail Builder or Control Drawing Builder.
IMPORTANT
If two FF faceplate blocks are connected, it is necessary to designate the same sub-schedule
number for both blocks. If blocks with different sub-schedule numbers are connected, an error
will occur when downloading.
l Function Block Property Sheet of Control Drawing Builder

When changing FF faceplate block properties on Control Drawing Builder, entering values in the
[Scale Low Limit Value], [Scale High Limit Value], and [Engineering Unit Symbol] settings in the
Function Block tab in the property sheet corresponds to entering values for the following detailed
settings:
• FF-AI:
High limit value, low limit value and engineering unit symbol of [Output Value Range (OUT_
SCALE)]
• FF-PID, FF-RA, FF-AO:
High limit value, low limit value and engineering unit symbol of [Process Value Range
(PV_SCALE)]
• FF-SC:
High limit value, low limit value and engineering unit symbol of [Line-Segment Output Value
Range (Y_RANGE)]
• FF-IT, FF-IS:
High limit value, low limit value and engineering unit symbol of [Operation Output Range
(OUT_RANGE)]
• Other FF faceplate blocks:
It is not permissible to enter values for these blocks.

n Changing Assignments
If it is required to change the assignments of FF faceplate blocks, the definitions of the blocks
must be changed by one of the function block builders, such as Control Drawing Builder. It is
possible to use the Fieldbus Block List dsialog box for this change. In addition, the definition can
be changed in the property sheet of the function block or with Function Block Detail Builder, in the
same way as when changing the properties of normal blocks.
l Using the Fieldbus Block List Dialog Box in Control Drawing Builder
box.
2. Select the Fieldbus block to be modified in the Fieldbus Block List dialog box, and drag and
drop it onto the FF faceplate block whose assignment is to be changed. The FF faceplate.
IMPORTANT
• It is not allowed to drag and drop a block onto a drawing of a different FCS.
• It is only possible to drop a block onto a FF faceplate block of the same type.
3. If either “device tag name” or “block ID” does not match in the definitions of the FF faceplate
blocks for both the dropped block and the drop destination block, a dialog box is displayed
to confirm that it is all right to drop it. Select [OK] to change the assignment and definitions.
Select [Cancel] if the assignments should not be changed. A confirmation dialog box will not
be displayed if the definitions of “device tag name” and “block ID” match, or definitions are
left blank.
4. If a block tag name is assigned to the Fieldbus block, the tag name of the FF faceplate block
is replaced with the new name when the changes to the assignment are complete.
l Using the Property Sheet in Control Drawing Builder

It is possible to change the definitions from the property sheet of the FF faceplate block, in the
same way as for normal function blocks. A [Fieldbus] tab is displayed in the property sheet of the
FF faceplate block. It is possible to change the definitions of [Device Tag Name], [Block ID], and
sub-schedule number from this property sheet.
l Using the Fieldbus Block List Dialog Box in the Function Block Overview
Builder
1. Select [Fieldbus Block List] from the [Window] menu to call up the Fieldbus Block List dialog
box.
2. Select the Fieldbus block from the Fieldbus Block List dialog box and right-click on it
to display the pop-up menu. Select [Copy] from the menu. Paste the block onto the FF
faceplate block whose assignment is to be changed in Function Block Overview Builder.
The pasting conditions and the changes in definitions after pasting are the same as when
performing the change operation using Control Drawing Builder.

l Making Changes in Function Block Detail Builder
In Function Block Detail Builder, open the [Fieldbus] tab and change the entries in [Device Tag
Name] and [Block ID].
l Making Changes by Pasting a Function Block

When a FF faceplate block is copied or cut, and then it is pasted with Control Drawing Builder or
Function Block Overview Builder, the entries in [Device Tag Name] and [Block ID] become the
same as those of the copy source block. Because it is not allowed to have duplicates of these
definition items, they must be redefined correctly.
n Speeding Up Data Access

Through explicitly assigning %Z (Fieldbus input/output terminals) to connecting terminals of an
FF faceplate block that is not used for connection, it is possible to speed up referencing and
setting the data items corresponding to these terminals. If this setting is performed, data will be
updated at a fixed cycle.
SEE
ALSO It is also possible to perform this assignment using Fieldbus Builder. For more information on how to do this using
Fieldbus Builder, see the following:
l Assigning to Connecting Terminals

Fieldbus input/output terminals can be assigned to connecting terminals using the [%Z
Assignment] tab of Function Block Detail Builder.
l %Z Assignment
The [%Z Assignment] check box is displayed in the line corresponding to the connecting terminal
of the FF faceplate block. Enable this check box when the assignment is to be performed
manually. The [%Z Assignment] column is displayed when downloading is completed and a
Function Block Detail Builder is opened.
l Assigning Extended Parameters to Data Items for Extended Parameters

It is possible to assign extended parameters of a Fieldbus block to the data items (P01 to P04)
for extended parameters of an FF faceplate block. Through this assignment, the extended
parameters of the Fieldbus block can be accessed via %Z. In order to assign extended
parameters to data items for extended parameters, use the [Extended Parameter] tab of Function
Block Detail Builder. Designate an extended parameter name for the Fieldbus block in the data
item column for each extended parameter. Up to 32 single-byte characters can be used.
SEE
ALSO For more details on the extended parameters, see the following:
“n Extended Parameters” in B2.1.2, “Update Using Fieldbus I/O (%Z)”

n Monitoring FF Faceplate Blocks

▼ Monitoring
Outputs from FF faceplate blocks can be monitored via FF-MAO, FF-MDO, and FF-AO blocks,
so that they can be used by external indicators and external trend graphs. Define the monitoring
of these outputs for FF faceplate blocks that execute the monitoring, such as an FF-MAO block in
the [Monitoring] tab of Function Block Detail Builder. FF faceplate block output terminals can be
specified as monitoring targets.
Function Block Detail Builder (FF-MAO)
Monitoring
Set Value Input (IN1) FF-AI.OUT
Set Value Input (IN2)
D010301E.ai
Figure Monitoring Tab of Function Block Detail Builder
l Specification of Monitoring
The blocks and terminals that can be specified as monitoring targets are as follows:
• Terminals IN1 to IN8 of FF-MAO and FF-MDO blocks
• The SET terminal of an FF-AO block
TIP
• It is also possible to specify to monitor the output terminals of FF faceplate blocks that have been defined in
separate drawing sheets.
• Information about the connections used in monitoring is not displayed in Control Drawing Builder. This
means that that information is neither displayed in the Control Drawing View of an HIS. Thus, add text
objects to Control Drawing Builder as necessary. Alternatively, graphic objects indicating the connections
can be added by using Status Display Builder.
IMPORTANT
The monitoring definition for an FF-AO block is valid only when the outputs of the FF-AO are
used for the purpose of monitoring, for instance, as outputs to an indicator. Do not use the
outputs in order to control valves and the like. Otherwise, the following problems may occur.
• There is a risk that bumps may occur.
• Errors of AO blocks cannot be detected.

D1.4 Creating a Simplified Universal Block

This section describes the procedure to create a simplified universal block.

D1.4.1 General Operation Flow

The following describes the procedures for creating a simplified universal block using the
Control Drawing Builder and the Function Block Overview Builder.
n Creating in the Control Drawing Builder

The following describes the automatic assignment in which a simplified universal block is created
after registering the applicable Fieldbus device, and the manual assignment in which a simplified
universal block is created before registering the applicable Fieldbus device.
The general operation flow of automatic assignment is shown below:
Control Drawing Builder Fieldbus Builder
Block tag
name entry Sta
rt
Dr Device
ag Fieldbus Block registration
an
dd List dialog box
ro
p
Block registration
D010401E.ai
Figure General Operation Flow (Automatic Assignment)
1. Register the Fieldbus device using the Fieldbus Builder.

2. Select Save As/Download.
3. Open the Fieldbus Block List dialog box in the Control Drawing Builder.
4. Select a custom block, and drag and drop it over a blank area in the drawing pane of the
Control Drawing Builder. This will register a simplified universal block to which the selected
custom block is assigned.
5. Enter a block tag name for the simplified universal block (define the tag name as a user-
defined label).
6. Connect the blocks.

l Manual Assignment
The general operation flow of manual assignment is shown below:
Select Function
Block dialog box
t
ar
St
Control Drawing Builder ct Fieldbus Builder
le
Se
Block tag
name entry Sta
rt
Device
Dr registration
ag Fieldbus Block
an
dd List dialog box
ro
p
Block registration
D010402E.ai
Figure General Operation Flow (Manual Assignment)
1. Open the Select Function Block dialog box in the Control Drawing Builder.
2. Select simplified Universal Block and click the [OK] button.
3. Click on the drawing sheet. A simplified universal block will be registered.
defined label).
6. Register the applicable Fieldbus device using the Fieldbus Builder.
8. Open the Fieldbus Block List dialog box in the Control Drawing Builder.
9. Select a corresponding custom block, and drag and drop it over the registered simplified
universal block. The custom block will be assigned to the simplified universal block.
10. Connect the blocks.

n Creating in the Function Block Overview Builder

The following describes automatic assignment and manual assignment.
3. Open the Fieldbus Block List dialog box in the Function Block Overview Builder and select
a desired custom block. Select [Copy] in the pop-up menu and copy the custom block, and
then paste it into a blank line in the Function Block Overview Builder. This will register a
simplified universal block to which the selected custom block is assigned.
defined label).
5. In the [Connection] tab of the Function Block Detail Builder of the registered simplified
universal block, enter the applicable terminal names and the names of the connection
destination terminals. Also enter the names of the connection source terminals.
l Manual Assignment
1. Register a simplified universal block using the Function Block Overview Builder. Define the
tag name as a user-defined label.
2. Select Save As/Download (this step may be omitted).
5. Open the Fieldbus Block List dialog box in the Function Block Overview Builder and select
a desired custom block. Select [Copy] in the pop-up menu and copy the custom block,
and then select the line of the registered simplified universal block in the Function Block
Overview Builder and paste the custom block into that line. This will assign the selected
custom block to the registered simplified universal block.
6. In the [Connection] tab of the Function Block Detail Builder of the simplified universal block,
enter the applicable terminal names and the names of the connection destination terminals.
Also enter the names of the connection source terminals.
IMPORTANT
Regardless of whether the Control Drawing Builder or the Function Block Overview Builder is
used, the following caution must be exercised when connecting the blocks.
With a simplified universal block, just like with any FF faceplate block, connecting a parameter
that requires back calculation for the function block assigned to the simplified universal block will
automatically create a back-calculation connection via the generation function in the Fieldbus
Builder.
However, back-calculation connection cannot be created automatically if a custom block exists
which is defined under a name different from the parameter requiring back calculation as defined
in a FF standard block. Therefore, pay attention not to create a connection that doesn’t permit
back calculation.
If a connection not permitting back calculation is created, bumpless control (tracking processing)
will not be implemented and therefore a control problem may occur.

D1.4.2 Creating a Simplified Universal Block

The following describes the creation of a simplified universal block using the Control
Drawing Builder and the Function Block Overview Builder.
n Creating in the Control Drawing Builder

The following describes the procedure for creating a simplified universal block before registering
the applicable Fieldbus device, and the procedure for creating a simplified universal block after
registering the applicable Fieldbus device.
l Creating a Simplified Universal Block before Device Registration

the applicable Fieldbus device:
1. Select [Function Block] from the [Insert] menu or corresponding tool button of the Control
Drawing Builder.
2. The Select Function Block dialog box will open.
3. Select [Regulatory Control Blocks/Calculation Blocks] and then [Foundation Fieldbus
Faceplates] in the Select Function Block dialog box.
4. Select [FF-SUNV] from the expanded blocks.
5. A simplified universal block will be registered in the drawing sheet.
6. Enter the block tag name (define the tag name as a user-defined label). It is recommended
that the user-defined label be set using text indicating the block type. In addition, entering a
tag comment consisting of a character string indicating the block type (such as a block label)
will allow the entered tag comment to be displayed as necessary.
l Creating a Simplified Universal Block after Device Registration
SEE
ALSO Registration of a simplified universal block after registering the applicable Fieldbus device corresponds to
automatic assignment. For the automatic assignment procedure, see the following:
“l Automatic Assignment” in “n Control Drawing Builder” of D1.4.3, “Assigning a Custom Block to a
Simplified Universal Block”

n Creating in the Function Block Overview Builder

the applicable Fieldbus device, and the procedure for creating a simplified universal block after
registering the applicable Fieldbus device.
l Creating a Simplified Universal Block before Device Registration

the applicable Fieldbus device:
1. Click the model name entry box in the Function Block Overview Builder.
2. In the model name tree view displayed on the left, select [Regulatory Control Blocks/
Calculation Blocks] and then [Foundation Fieldbus Faceplates].
3. Double-click on [FF-SUNV] among the expanded blocks.
4. A simplified universal block will be registered.
l Creating a Simplified Universal Block after Device Registration
SEE
ALSO Registration of a simplified universal block after registering the applicable Fieldbus device corresponds to
automatic assignment. For the automatic assignment procedure, see the following:
“l Automatic Assignment” in “n Function Block Overview Builder” of D1.4.3, “Assigning a Custom Block to
a Simplified Universal Block”

D1.4.3 Assigning a Custom Block to a Simplified Universal

Block
The following describes the assignment of a custom block to a simplified universal block
using the Control Drawing Builder and the Function Block Overview Builder.
n Control Drawing Builder

The following describes the manual assignment and automatic assignment of a custom block to
l Manual Assignment
If a simplified universal block was created before registering the applicable Fieldbus device,
assign a desired custom block to the simplified universal block according to the following
procedure:
3. In the Control Drawing Builder, select [Fieldbus Block List] from the [Window] menu or from
the pop-up menu displayed by clicking the right mouse button.
4. The Fieldbus Block List dialog box will open.
5. In the Fieldbus Block List dialog box, select (drag) a corresponding custom block and drop it
onto the registered simplified universal block.
6. The custom block selected in the Fieldbus Block List dialog box will be assigned to the
When creating a simplified universal block after registering the applicable Fieldbus device,
register the Fieldbus device, assign a desired custom block to a simplified universal block, and
then register the simplified universal block according to the following procedure:
3. In the Control Drawing Builder, select [Fieldbus Block List] from the [Window] menu or from
the pop-up menu displayed by clicking the right mouse button.
5. In the Fieldbus Block List dialog box, select (drag) a corresponding custom block and drop it
over a blank area in the drawing pane of the Control Drawing Builder.
6. A simplified universal block to which the selected custom block is assigned will be registered
in the drawing sheet.

n Function Block Overview Builder

The following describes the manual assignment and automatic assignment of a custom block to
l Manual Assignment
If a simplified universal block was created before registering the applicable Fieldbus device,
assign a desired custom block to the simplified universal block according to the following
procedure:
3. In the Function Block Overview Builder, open the Fieldbus Block List dialog box and select
a desired custom block. Select [Copy] in the pop-up menu and copy the custom block,
and then select the line of the registered simplified universal block in the Function Block
Overview Builder and paste the custom block into that line.
4. The selected custom block will be assigned to the registered simplified universal block.
When creating a simplified universal block after registering the applicable Fieldbus device,
register the Fieldbus device, assign a desired custom block to a simplified universal block, and
then register the simplified universal block according to the following procedure:
3. Select [Fieldbus Block List] from the [Window] menu of the Function Block Overview Builder.
5. In the Fieldbus Block List dialog box, select a corresponding custom block. In the pop-up
menu displayed by clicking the right mouse button, select [Copy] to copy the custom block.
Then, paste the custom block into a blank line of the Function Block Overview Builder.
6. A simplified universal block to which the selected custom block is assigned will be registered
in the Function Block Overview Builder.

D1.4.4 Defining an I/O Parameter Name

The following describes the definition of an I/O parameter name using the Control
Drawing Builder and the Function Block Overview Builder.
n Control Drawing Builder

The following describes the procedure for defining an I/O parameter name consisting of 18 or
fewer characters and one exceeding 18 characters.
l I/O Parameter Name Consisting of 18 or Fewer Characters

1. Register component blocks of a loop using the Control Drawing Builder.
2. Select [Wiring] from the [Insert] menu or click the corresponding tool button to change the
input mode to [Wiring] and connect the blocks.
3. Click on the output block and double-click on the input block.
4. The wiring will be displayed, together with the I/O terminal names. The terminal names of
each simplified universal block are tentative (example: OUT, IN).
5. Click on a displayed terminal name to change it to an input field.
6. Set the correct terminal name (I/O parameter name) for the corresponding block. The
correct terminal name can be identified by referencing the manual for the applicable
Fieldbus device or the Edit Block Parameter dialog box of the Fieldbus Builder. Note that the
number of characters must not exceed 18.
l I/O Parameter Name Exceeding 18 Characters

1. If an I/O parameter name exceeds 18 characters, abbreviate it to 18 or fewer characters and
set the abbreviated I/O parameter name in the same manner described in “I/O Parameter
Name Consisting of 18 or Fewer Characters.”
2. Open the Function Block Detail Builder.
3. Select the [Terminal name] tab in the Function Block Detail Builder and enter the
abbreviated name and correct terminal name (I/O parameter name).
4. Close the Function Block Detail Builder.
5. Select Save As/Download in the Control Drawing Builder.

n Function Block Overview Builder

The following describes the procedure for defining an I/O parameter name consisting of 18 or
fewer characters and one exceeding 18 characters.
l I/O Parameter Name Consisting of 18 or Fewer Characters

Define I/O connection information in the Function Block Overview Builder. At this time, enter the
correct I/O parameter name as registered in the applicable Fieldbus device as the terminal name.
The correct I/O parameter name can be identified by referencing the manual for the applicable
Fieldbus device or the Edit Block Parameter dialog box of the Fieldbus Builder. Note that the
number of characters must not exceed 18.
l I/O Parameter Name Exceeding 18 Characters

1. If an I/O parameter name exceeds 18 characters, abbreviate it to 18 or fewer characters and
set the abbreviated I/O parameter name in the same manner described in “I/O Parameter
Name Consisting of 18 or Fewer Characters.”
2. Open the Function Block Detail Builder.
3. Select the [Terminal name] tab in the Function Block Detail Builder and enter the
abbreviated name and correct terminal name (I/O parameter name).
4. Close the Function Block Detail Builder.
5. Select Save As/Download in the Function Block Overview Builder.

D1.4.5 Connecting a Simplified Universal Block in the

Function Block Overview Builder
The following describes the connection of a simplified universal block using the Function
Block Overview Builder.
n Connecting a Simplified Universal Block

Connect a simplified universal block according to the following procedure:
1. In the Function Block Overview Builder, select the simplified universal block you want to
connect and open the Function Block Detail Builder.
2. In the [Connection] tab of the Function Block Detail Builder, enter the applicable terminal
names and the names of the connection destination terminals. Also enter the names of the
connection source terminals.

D1.4.6 Defining Detail Parameters for a Simplified Universal

Block
The following describes the setting of detail parameters (builder definition items) for a
n Setting Definition Items in the Function Block Detail Builder

Select a registered simplified universal block in the Control Drawing Builder or the Function Block
Overview Builder, and start the Function Block Detail Builder. Set the necessary parameters
(builder definition items) for the simplified universal block using the Function Block Detail Builder.
SEE
ALSO For the builder definition items of a simplified universal block as set in the Function Block Detail Builder, see the
following:
A3.3.4, “Builder Definition Items for the Simplified Universal Block”

D1.5 Starting Up Fieldbus Builder

This section explains how to start up Fieldbus Builder from Control Drawing Builder or
Function Block Overview Builder.
n Designating an FF Faceplate Block

It is possible to start up Fieldbus Builder by designating an FF faceplate block that has been
defined with Control Drawing Builder or Function Block Overview Builder.
1. Select an FF faceplate block.
2. Select [Fieldbus Builder] in the [Window] menu, or right click the FF faceplate block and
choose [Fieldbus Builder] from the pop-up menu.
n Designating a Fieldbus Block

It is possible to open a screen related to the applicable Fieldbus block in Fieldbus Builder via the
Fieldbus Block List dialog box.
1. Select [Fieldbus Block List] in the [Window] menu of Control Drawing Builder or Function
Block Overview Builder to display the Fieldbus Block List dialog box.
2. Select a Fieldbus block from the Fieldbus Block List dialog box.
3. Click the right mouse button to display the pop-up menu and select [Fieldbus Builder].

D1.6 Other Engineering Items

This section explains other Fieldbus engineering items.
n Resolving Invalid Elements

It is necessary to resolve invalid elements if there are FF faceplate blocks that are not connected
to Fieldbus blocks. Specifically, such FF faceplate blocks are in the unassigned or assignment
invalid state. They are assigned to Fieldbus blocks through this operation.
The operations for resolving invalid elements, the conditions under which FF faceplate blocks
become invalid elements, and the results of resolving invalid elements are explained together.
l FF Faceplate Blocks in the Invalid Element State

FF faceplate blocks in the unassigned or assignment invalid state become invalid elements. This
happened in one of the following conditions:
• When a download operation is performed, a Fieldbus with matching block model name and
block tag name is not registered using Fieldbus Builder, and the device tag name and block
ID of the FF faceplate block are not specified (unassigned state).
• As a result of deleting a registered Fieldbus device or changing the device tag name with
Fieldbus Builder, the Fieldbus block, which is specified by a set of device tag name and
block ID assigned for the FF faceplate block, has ceased to exist (assignment invalid state).
• As a result of changing the block tag name or uploading with Fieldbus Builder, the tag name
of the FF faceplate block and the block tag name of the Fieldbus block do not match any
longer (assignment invalid state).
l How to Resolve Invalid Elements

FF faceplate blocks in the unassigned or assignment invalid state can be put into the assigned
state by resolving the invalid elements. Perform the following operations using Fieldbus Builder,
and then resolve the invalid elements in order to change the unassigned or assignment invalid
state of the FF faceplate blocks to the assigned state.
• Perform the following operations using Fieldbus Builder in such a way that the tag name of
an FF faceplate block in the unassigned state and the block tag name of the Fieldbus block
of the same model type do match.
- Register the device and set the block tag name.
- Change or upload the block tag name.
• Perform the following operations using Fieldbus Builder in such a way that the device tag
name and block ID set for an FF faceplate block in the assignment invalid state and the
device tag name and block ID of the Fieldbus block do match.
- Register the device.
- Change the device tag name.

l Operations
Invalid elements are resolved by the following operations:
• Selecting [Resolve Invalid Element] in the [Project] menu of System View
• Performing an FCS off-line download operation
• Starting up the test function
• Copying an FCS
• Changing FCS properties
IMPORTANT
If invalid elements are resolved after changing the block tag name of a Fieldbus block connected
to an FF faceplate block in the assigned state, the block tag name of the Fieldbus block is
changed back to the one before making the change. If this is not desirable, it is necessary to
change the tag name of the corresponding FF faceplate block with Control Drawing Builder or
Function Block Overview Builder after changing the block tag name of the Fieldbus block with
Fieldbus Builder before resolving invalid elements.
n Switching the Data Item Names of FF-PID Blocks

▼ Display FF-PID in same style as PID. (Use P. I. D instead of GAIN. RESET. RATE)
It is possible to specify for each project that the data item names of FF-PID blocks, namely, GAIN,
RESET and RATE, be switched to P, I and D as used for the CENTUM PID blocks at system
generation.
IMPORTANT
• When switching the data item names of FF-PID blocks, offline load will be required for all
KFCSs, KFCS2s, FFCSs, RFCS2s and RFCS5s defined for the applicable project. To apply
this function to a project currently running, do so when FCS offline load can be executed.
• When switching the data item names of FF-PID blocks in an existing project, any application
using the data item names in the previous mode must be changed.

l Differences between the FF-PID Block and the PID Block
The following describes the differences between a FF-PID block having GAIN, RESET and RATE
as its data item names, and a FF-PID block whose data item names have been switched to P, I
and D as used for the CENTUM PID blocks:
• The value of P takes the value of GAIN after converting it using the following equation:
P = 100/GAIN
• The value of I takes the same value as RESET.
• The value of D takes the same value as RATE.
IMPORTANT
Controllability and sensitivity are different between the FF-PID blocks (PID blocks in a Fieldbus
device) and the CENTUM PID blocks, due mainly to the different algorithms used by the two
types of blocks.
In this document, the display mode using GAIN, RESET and RATE is called “FF mode,” while the
one using P, I and D is called “CENTUM mode.”
Table Data Items in the FF Mode/CENTUM Mode
FF mode CENTUM mode Data value
GAIN P P=100/GAIN
RESET I I=RESET
RATE D D=RATE
D010601E.ai

l FF-PID Display on the HIS
The following shows a FF-PID block in the FF mode and CENTUM mode in the tuning view of the
HIS is shown below:
FIC100FF TUN
FIC100FF
MODE= MAN C/S ALRM:NR
ML = 0 BSTS:
GAIN = 1
RESET = 20
RATE = 0
BAL_TIME = 0
FF_VAL = 0
FF_GAIN = 0
D010602E.ai
Figure FF-PID Tuning View in the FF Mode
FIC100FF TUN
FIC100FF
MODE= MAN C/S ALRM:NR
ML = 0 BSTS:
P = 100.0
I = 20.0
D = 0.0
BAL_TIME = 0
FF_VAL = 0
FF_GAIN = 0
D010603E.ai
Figure FF-PID Tuning View in the CENTUM Mode
l Mode Switching for a New Project

At the start of an engineering session, set the FF mode or CENTUM mode in the Properties of
the new project. Once the mode is set, perform normal engineering using the data item names
corresponding to the specified mode.

l Mode Switching for an Existing Project
The flow of switching the display mode to CENTUM is shown below:
Start The application must be changed if it is using
GAIN, RESET and RATE.
If the mode is switched in the Properties of the
applicable project, you will be prompted to
Specify the CENTUM mode change the application, if necessary.
in the Properties of the applicable project
Need to change [Yes]

the application?
[Yes]
Current project?
[No] Change "current project"

to "user-defined project"
Change the application Change the application
Change "user-defined project"

to "current project"
Execute an FCS offline load
Execute a project common load
End
D010604E.ai
Figure Flow of Switching to the CENTUM Mode
The following describes the procedure for switching the data item names of FF-PID blocks in an
existing project:
1. Set the CENTUM mode or FF mode in the Properties of the applicable project.
2. If the data item names in the previous mode are used in the relevant engineering data
(application), change the applicable referencing blocks (blocks referencing the data item
names in the previous mode).
SEE
ALSO For more information about how to verify the extent of impact on the application, see the following:
“l How to Verify the Extent of Impact of Mode Switching when Changing the Application”
IMPORTANT
If the application must be changed for the current project (step 2 above), tentatively change the
project’s attribute to “user-defined project” and perform step 2 above, and then return it to “current
project” and perform steps 3 and 4 below. Change the project’s attribute using the Project
Attribute Change Tool.

3. Execute an FCS offline load. This will change the data of FF-PIDs in the FCS to the data
item names in the new mode.
4. Execute a project common load. After the load, the data items in the new mode will be
displayed on the HIS.
Basically, this switching operation is the same as the relationship between the definitions in the
Project Common Builder and the FCS.
IMPORTANT
• An attempt to display the FF-PIDs of an FCS, for which no FCS offline load has been
executed, on an HIS will generate a communication error and disable operation and
monitoring.
• The FCSs requiring an FCS offline load include all KFCSs, KFCS2s, FFCSs, RFCS2s and
RFCS5s that are defined in the applicable project and for which FF-PIDs can be created.
When an invalid element resolution is executed in the System View, a message will be
displayed to prompt an FCS offline load.
l FF Mode/CENTUM Mode Specification

Specify the FF mode or CENTUM mode for each project in the project’s Properties in the System
View.
To specify the CENTUM mode, check the [Display FF-PID in same style as PID. (Use P. I. D
instead of GAIN. RESET. RATE)] check box. To specify the FF mode, uncheck this check box.
The default is the FF mode, meaning that the check box is not checked.
Properties
Name and Position Outline Constant Detailed Setting
Manually Resister Engineering Unit Symbol

Manually Resister Switch Position Label
Plant Hierarchy
Start Number 1
Maximum Number of use 32767
Number of in use (Number of Custom facilities) 1262(1000)
Display FF-PID in same style as PID. (Use P.I.D instead of GAIN. RESET. RATE)
OK Cancel
D010605E.ai
Figure Project’s Properties

l How to Verify the Extent of Impact of Mode Switching when Changing the
Application
Switching between the FF mode and CENTUM mode will change the data item names and
values (P = 100/GAIN). Therefore, if the data item names in the previous mode are used in
the relevant engineering data (application), the applicable referencing function blocks (blocks
referencing the data item names in the previous mode) must be changed. The following
describes how to verify the extent of impact (blocks requiring change) in this process.
• Verifying whether or not the application requires a change:
In the Properties of the applicable project, specifying the FF mode or CENTUM mode and
clicking the [OK] button will display a list of FCSs containing the function blocks that require
an application change. Verify the referencing function blocks for the corresponding FCSs
and change the application using the necessary builder.
• How to verify the reference function blocks:
Switching between the FF mode and CENTUM mode in the Properties of the applicable
project will change to invalid elements those blocks that are referencing the data item
names in the previous mode. The blocks that became invalid elements can be displayed in
the message display area by selecting the [Error Check] menu from [FCS] in the System
View.
l Handling the Saved Tuning Parameters

When the mode is switched to CENTUM, the saved tuning parameters created before switching
to the CENTUM mode will be handled as follows. The tuning parameters saved as FF mode
values will be reverted in the FF-PID block. When the FF-PID block is executed again, it reads
relevant data from the Fieldbus device and converts the parameters to CENTUM mode values,
and then overwrites the previously reverted values. It takes about four seconds for a FF-PID
block to read data from the Fieldbus device, convert them into CENTUM mode values and
overwrite the previous values.
n Block Parameter Acquisition

The block parameters defined in the function blocks on the fieldbus builder need to be fetched
and used as the initial parameter values for the FF faceplate blocks defined in the control
drawings. Therefore, the tuned block parameters can be used in the control drawing. However,
for the FF faceplate blocks that do not have corresponding function blocks defined on the
fieldbus builder, there is no need to perform the block parameter acquisition.
The procedure of block parameter acquisition is as follows:
1. Start Control Drawing Builder, and then choose an FF faceplate block on the Control
Drawing Builder. However, you can choose multiple faceplate blocks together.
2. On the [Tools] menu of Control Drawing Builder, choose [Block Parameter Acquisition]
or right click the mouse on an FF faceplate block and then choose [Block Parameter
Acquisition] from the pop-up menu. Then a dialog box for confirming block parameter
acquisition will be displayed.
3. Click [OK] button on the dialog box for confirming block parameter acquisition, then the
block parameters of the function blocks on the fieldbus builder will be fetched. The fetched
block parameters can be displayed on the Function Block Detail Builder.

n Batch Self-Documentation
It is possible to print out the definitions for a Fieldbus block using the batch self-documentation.
SEE
ALSO For more information on the operation of the batch self-document printing, see the following:
F19, “Self-Documentation” in CENTUM VP Reference, Engineering (IM 33M01A30-40E)
l Operation
Select [Self-Document Printing...] in the [Tools] menu of System View to display the following
dialog box:
Self Document
Print Range Header - Footer Print Type Print Order Drawing Select Print
Project Name FIELDBUS
Print All
Print from the list
IOM
Node1
Select All Node Properties
Deselect All IOM Properties
1ALF111
1ALF111-1
1ALF111-2
1ALF111-3
1ALF111-4
XXXX
Print by Date Between 2008/3/31 2008/3/31
Print Close
Ready
D010606E.ai
Figure Self-Document Printing
l Printing the Definition Contents of the ALF111 Module

Checks the IOM properties in the tree in order to print the properties of ALF111 module defined in
System View.
l Printing the Contents Defined with Fieldbus Builder

Checks the builder file for each ALF111 module port in order to print out the contents defined with
Fieldbus Builder.

n Host File Set Generation

The host files set required for Fieldbus system engineering can be generated for each project or
for each FCS.
l Procedure
On System View, select a project that requires the host file set, choose [Fieldbus] and then
[Generate Host File] from [Tools] menu. A dialog box displays for confirmation. When confirmed,
the host file set for the selected project is generated.
On System View, select a FCS that requires the host file set, choose [Fieldbus] and then
[Generate Host File] from [Tools] menu. A dialog box displays for confirmation. When confirmed,
the host file set for the selected FCS is generated.
l Host File Set Information

In host file set generation, the configuration data of a project is output from the project database
to a host file set.
The Host File Set contains the information extracted from project configuration data and in the
file format supported by CENTUM VP builders and the Plant Resource Manager (PRM). The
information in the Host File Set is as follows:
Table Information Output to the Host File Set
No. File name Type of information Description
Correspondence table of device numbers, vendor names,
1 Device.hfs Device configuration list models, device IDs, tag name of the device on FF-H1 bus,
and node addresses
Correspondence table of block tag names and block indexes
2 BlkInfo.hfs Block information (including indexes of view objects for referencing block types
and parameters within a block)
Correspondence table of vendor specific FBAP parameters
3 BlkParam.hfs Block parameter list
added to the standard parameters and parameter indexes
Information about connection terminals and the connection
4 Terminal.hfs Terminal information
between function blocks and objects
List of intended use of VCR (including information regarding
5 VcrUsage.hfs VCR application list
VFD and devices with which the VCR communicates)
6 Alert.hfs Alert information Information for analyzing alert information
7 Trend.hfs Trend information Information about defined trend objects
Correspondence table of the standard FBAP parameters
8 StBlkParam.hfs Standard block parameter list
and the parameter indexes
9 View.hfs View information Information about the defined view objects
10 DataType.hfs Data type list List of data types
11 Reserved.hfs Reserved word list List of reserved words
D010607E.ai
Note: For information from numbers 1 through 7, a file having different contents is output every time configuration is performed. For
information from numbers 8 through 11, a file having the same contents is always output after the first output. Information from
numbers 8 through 11 is called option.
TIP
The host file generation is internally executed even during Fieldbus downloading.

n Fieldbus Overall Upload

In the Fieldbus Overall Upload dialog box, it is possible to specify an ALF111 defined for the FCS
and upload the block parameters from a Fieldbus device in a batch. It is also possible to upload
the block parameters of all the Fieldbus devices connected to the FCS by specifying all the
ALF111 modules defined for the FCS.
l Overall Upload Operation

1. Select an FCS from Tree View in System View, then select [Fieldbus] - [Upload All] from the
[Tools] menu. The Fieldbus Overall Upload dialog box will be displayed.
Fieldbus Overall Upload
File Name Line Node Comment

1ALF111 1 1
Select All Clear All OK Cancel
D010608E.ai
Figure Fieldbus Overall Upload Dialog Box
2. The Fieldbus Overall Upload dialog box displays all the ALF111 modules defined for the
selected FCS. Select the ALF111 for which the upload is to be performed, then click the [OK]
button. The overall upload will start.
3. A dialog box showing the upload progress is displayed while the overall upload is being
performed. Errors and warning messages generated during the upload are displayed in the
message display area of System View.
l Canceling Overall Upload

To cancel the overall upload, click the [Cancel] button in the dialog box indicating the progress
during the overall upload. The upload processing is canceled once the upload of Fieldbus device
block parameters in progress completes.

n Download to All Fieldbus Devices

In the Download to All Fieldbus Devices dialog box, it is possible to specify individual ALF111
modules defined in an FCS and perform off-line download to the connected Fieldbus devices in a
batch. It is also possible to perform off-line download to all the Fieldbus devices connected to the
FCS in a batch by specifying all the ALF111 modules defined in the FCS.
l Operation of Off-Line Download to All Fieldbus Devices

1. Select an FCS in Tree View of System View, and select [Fieldbus] and then [Download All]
from the [Tools] menu. The Download to All Fieldbus Devices dialog box appears.
Download to All Fieldbus Devices
File Nme Line Node Comment

1ALF111 1 1
7ALF111 1 1
Initial Download (Use Block Parameters of Device)
Select All Clear All OK Cancel
D010609E.ai
Figure Download to All Fieldbus Devices Dialog Box
2. All the ALF111 modules defined in the selected FCS are displayed in the Download to All
Fieldbus Devices dialog box. If the option [initial Download (use Block Parameter of Device)]
is checked, the Initial Download will be performed on all the fieldbus devices in the segment.
Select the ALF111 modules for which the download processing is to be executed and click
the [OK] button. The download processing to all the connected Fieldbus devices starts.
While the download processing to all the connected devices is being performed, a dialog
box indicating that the download processing is in progress is displayed. Errors and warning
messages generated during off-line download are displayed in the message display area of
System View. If any ALF111 module is down, the download processing for that ALF111 module is
skipped and the download processing for the next ALF111 module is executed.
SEE
ALSO For more information about initial download, see the following:
“n Initial Downloading” in D2.3.5, “Downloading to Fieldbus Devices”
l Canceling Downloading to All Fieldbus Devices

To stop downloading to all Fieldbus devices, click the [Cancel] button in the dialog box indicating
that downloading to all Fieldbus devices is being performed. The processing is canceled as soon
as the off-line download to the Fieldbus devices currently in process is completed.

n Displaying Device Information

It is possible to call up the Device Panel from System View. First, specify builder files for each
port of the applicable ALF111 module in System View. Next, select [Fieldbus] and then [Display
Device Information] from the [Tools] menu. The device information will be displayed in the window
of Device Panel.
SEE
ALSO For a detailed description of the Device Panel, see the following:
n Start Device Management Tool

▼ Device Management Tool
Starts the Device Management Tool of the fieldbus tools if it is installed in the same PC with the
l Procedure
Choose [Device Management Tool] from the [Windows] menu of the Control Drawing Builder. If
the device management tool is not installed, an error message will be initiated and displayed.

Blank Page
<D2. Fieldbus Builder> D2-1
D2. Fieldbus Builder

This chapter explains Fieldbus Builder, a part of the Fieldbus engineering.
In particular, the structure of the windows, basic engineering, advanced engineering,
other engineering, menus, and messages related to Fieldbus Builder are explained.

D2.1 Overview of Fieldbus Builder

This section explains an overview of Fieldbus Builder. It explains the scope of engineering
for Fieldbus system, relationship with other software, and the structure of Fieldbus
Builder.
n Scope of Engineering with Fieldbus Builder

The following figure shows the scope of engineering that can be performed with Fieldbus Builder
on the Fieldbus engineering.
IOM engineering HIS engineering
Loop configuration ALF111

configuration
Fieldbus I/O Fieldbus I/O Tag list

Assignment Assignment
Scope of engineering
that can be performed
Engineering of Fieldbus devices with Control Drawing
Builder
Configuration of control functions
Configuration of communication functions Scope of engineering

that can be performed
with Fieldbus Builder
D020101E.ai
Figure Scope of Engineering with Fieldbus Builder
n Relationship with Other Software

The figure below shows the relationship among Fieldbus Builder and other software, HIS, and
FCS.
Fieldbus PC Tool
System View Starting up Fieldbus Builder Device
Management Tool
g Creation
cin
en
refer Setting
Starting up ta
Da Starting up Start in the Host file
Starting up
background
Control Drawing
Builder
Start in the
background
Device Panel
Starting up
Starting up
Start menu D020102E.ai
Figure Relationship with Other Software

n Structure of Fieldbus Builder

The following table shows the structure of Fieldbus Builder.
Table Structure of Fieldbus Builder (1/2)
Item Description Usage Remark
This function manages segments, which are
the engineering units of one FF-H1 Fieldbus.
It performs file management (e.g., open,
Fieldbus input/output information
close, save as). It also allows editing
Segment management xx1 (%Z) is automatically determined by
information common to different segments
and Fieldbus input/output information (in
order to designate high-speed data access
and assignment to faceplate blocks).
This function registers Fieldbus devices. Resource/capability information of a
Device Registration Automatic registration and manual device is obtained from a capability
registration are possible. file.
Define and execute the block instantiation
Block Instantiation
to the corresponding devices
Block parameter information is
obtained from a DD file when a
device is registered. Block
This function allows editing of block parameter values are obtained from
Edit Block Parameter... parameter values. It also allows editing of xx2 a capability file at manual
values in link objects and trend objects. registration. They are handled as
initial values and overwritten by the
default values provided by Fieldbus
Builder.
This function allows editing of values for NM
These parameters are automatically
Adjust Communication parameters, SM parameters, LAS
determined. It is possible to modify
Parameter... schedules/FB schedules, and VCR
values manually.
parameters.
This function graphically displays the
schedule result generated by Control
Drawing Builder. The schedule result can be Scheduling or displaying is
modified graphically. performed for blocks whose block
Display and Adjust Schedule It changes the schedule adjustment tag names are set and blocks to
parameters, i.e., the macrocycle, control which Fieldbus I/O (%Z) are
cycle, time resolution, and safety factor, and assigned.
generates the schedule again
(rescheduling function).
This function downloads Fieldbus
information to FCS, IOM (ALF111), and field
devices.
Online downloading generates Fieldbus
information based on the definition For offline downloading to devices,
Downloading information, detects a difference, and the tag assignment and address
Online Load downloads the difference information. assignment can be performed by
Offline Load to Devices With offline downloading to devices, the designating the options. Offline
(Master Data Download / already generated Fieldbus information is downloading to devices can be
Initial Download) downloaded to all Fieldbus devices only. performed for each segment,
The master data downloading needs to be Fieldbus device, and block.
performed when replacing a fieldbus device;
while the initial downloading needs to be
performed when a fieldbus device is
connected to the fieldbus for the first time.
Block parameter values can be
uploaded for each segment, device,
This function uploads block parameter
Upload and block.
values from Fieldbus devices.
This function is used when a Fieldbus
device is automatically registered.
D020103E.ai
: Used in normal cases.

xx1: Used as necessary (as initial setting)
xx2: Used as necessary (others)
No mark: Used when advanced engineering is performed.

Table Structure of Fieldbus Builder (2/2)
Item Description Usage Remark
This function sets the tag name of the
Tag Assign
device on FF-H1 bus and node address
Address Assign xx2
value for Fieldbus devices. It also sets the
Device Class Setting
device class.
It generates trend objects and VCR
This function performs the necessary
when generating Fieldbus
Trend setting designations for sending trends of block xx2
information based on the designated
parameter values.
information.
This function rebuilds segment/device
Import information from files output by the Save As xx2 Common function for builders
function.
This function prints definitions and
Self-document printing generated information in a batch in the xx2 Common function for builders
document format.
Online help This function displays the online manual. xx2 Common function for builders
The initial value is “do not display.”
Transducer Select whether or not to display transducer It is designated for each segment.
xx1
block blocks. The value is initialized when
opening a segment.
Manual The default is [Manual Modification
Designate whether or not to modify NM
modification xx1 Disabled]. The value is designated
parameters manually.
Environment selection for each segment.
settings Designate a directory for storing DD files/
Bus information This variable is designated for each
capability files. xx1
setting CENTUM VP project.
Designate an output directory for host files.
Designation of
Select whether or not to perform tag The default is “do not perform.”
offline
assignment and address assignment at xx1 The variable is designated for each
downloading
offline downloading to devices. segment.
to devices
Utilities Generate Host Files xx2
Update the content of a registered device to
Update Capabilities File/
reflect changes in the device revision, DD xx2
DD File
revision, capabilities file revision and options.
Check the scheduled load when saving or
Scheduled load check xx2
downloading to Fieldbus devices.
xx1: Used as necessary (as initial setting) Template can be used for registering
Template can be created, saved and
Templatexx2: Used as necessary (others) xx2 device and initial downloading to
No mark: Usedopened.
when advanced engineering is performed. device.
D020104E.ai

D2.2 Overview of the Window Structure

This section explains the window structure of Fieldbus Builder. First, the overall structure
of the main window is explained. Next, Tree View, each of the tabs related to segments,
and then the tabs related to devices are explained.

D2.2.1 Overall Window Structure

This section explains an overview of the overall structure of the windows of Fieldbus
Builder, focusing on the characteristics unique to Fieldbus Builder.
SEE
ALSO For more details on other parts constituting the windows, see the following:
D2.6, “Menu List”
n Window Structure
The following figure shows the window structure of Fieldbus Builder.
Fieldbus Builder [Pjt:FIELDBUS Stn:FCS0101 Train]:1 Node:1 File:1ALF111-1.edf]
File Edit View Tools DeviceRegistration Off-lineLoad EnvironmentSettings Window Help
%Z manual decision 0
1ALF111-1 Device List Common Information %Z List

+ YVP_01
+ YF100E_01 Device Tag Address Device Class Device ID Vendor Name Model Name Revision Name
+ EJA_01 YVP_01 0xF7 BASIC 594543000100 Yokogawa Elect YVP R1.01
+ AE100_01 YF100E_01 0xF6 BASIC 594543000200 Yokogawa Elect YF100E R2.00
- YTA320_01 EJA_01 0xF5 BASIC 594543000300 Yokogawa Elect EJA100A R2.00
RESOURCE_R01-05(R AE100_01 0xF4 BASIC 594543000400 Yokogawa Elect AE100 R2.00
YTA_AI(AI_01) YTA320_01 0xF3 BASIC 594543000500 Yokogawa Elect YTA320 R1.01
(AI_02)
(AI_03)
(AI_04)
(DI_01)
(DI_02)
(DI_03)
(DI_04)
Message
Ready Position: Line 1Column 2

D020201E.ai
Figure Window Structure of Fieldbus Builder
n Items Displayed in Tree View

Tree View displays the segments defined in the system, the Fieldbus devices constituting each
segment, and the blocks constituting each of the Fieldbus devices.
n Tabs
The structure of the tabs changes depending on what is selected in Tree View on the left side.
The tabs switch to tabs related to segments if a segment is selected, tabs related to Fieldbus
devices if a Fieldbus device is selected, and tabs related to blocks if a block is selected.

D2.2.2 Tree View

Tree View not only displays the hierarchy in the Fieldbus system, but is also used for
operations such as changing device tag names and block tag names as well as adding
and deleting devices.
Tree View is explained below.
SEE
ALSO For specific operations such as changing device tag names and block tag names, as well as adding and deleting
devices, see the following:
l Hierarchy Display
The folders displayed at the top of the hierarchy in Tree View are segment names. These
folders correspond to ports of the ALF111 module. A device tag name is displayed for a Fieldbus
device, and a block tag name is displayed for a block. A temporary tag name may be displayed
in parentheses at the right side of a block tag name. An “*” (asterisk) is displayed at the left side
of a block tag name for blocks being used by Control Drawing Builder. Transducer blocks are
displayed only if the [Show Transducer Blocks] check box is enabled in the Environment Settings
dialog box.
SEE
ALSO For more details on the Environment Settings dialog box, see the following:
D2.3.1, “Environment Settings”

D2.2.3 Segment Tab

When a segment is selected in Tree View, the Segment tab is displayed in the right pane.
The Segment tab contains the “Device List,” “Common Information,” and “%Z List” tabs.
n Device List
▼ Device List
The Device List tab is explained below.
This tab is used to display the Fieldbus devices registered in a segment in a list format.

+ YVP_01
+ YF100E_01 Device Tag Address Device Class Device ID Vendor Name Model Name Revision Name
+ EJA_01 YVP_01 0xF7 BASIC 594543000100 Yokogawa Elect YVP R1.01
+ AE100_01 YF100E_01 0xF6 BASIC 594543000200 Yokogawa Elect YF100E R2.00
- YTA320_01 EJA_01 0xF5 BASIC 594543000300 Yokogawa Elect EJA100A R2.00
RESOURCE_R01-05(R AE100_01 0xF4 BASIC 594543000400 Yokogawa Elect AE100 R2.00
YTA_AI(AI_01) YTA320_01 0xF3 BASIC 594543000500 Yokogawa Elect YTA320 R1.01
(AI_02)
(AI_03)
(AI_04)
(DI_01)
(DI_02)
(DI_03)
(DI_04)
Message

D020206E.ai
Figure Device List Tab
l Device Tag Name

▼ Device Tag Name
It is possible to display and edit the device tag name of a Fieldbus device. The device tag
name must be unique within an FCS. The device tag name may contain up to 16 single-
byte characters. Only single-byte alphanumeric characters, hyphen (-), underscore (_), and
uppercase alphabetic characters can be used. The string must start with an alphabetic character.
l Address
▼ Address
It is possible to display and edit the value of a node address. The address can be designated
by either a decimal or hexadecimal number. Place “0x” at the head when designating by a
hexadecimal number. The allowable designation range is from 0x16 to 0xF7. The allowable
designation range for decimal numbers is from 22 to 247. The node address must be unique in a
segment.

l Device Class
▼ Device Class
It is possible to display and edit the device class of a Fieldbus device. Select either the link
master or basic device class. The devices that do not execute LAS are of the basic device class,
and the devices that execute LAS are of the link master device class. At least one link master
device is required in one segment.
The fieldbus H1 Communication module (ALF111 Module) acts as the link master. So that device
classes for all the other devices connected on the fieldbus segment with the ALF111 module can
be defined as the basic device class.
l Device ID
▼ Device ID
It is possible to display and edit the device ID of a Fieldbus device. Enter the device ID that is set
for the Fieldbus device.
l Vendor Name
▼ Vendor Name
The vendor name of the selected Fieldbus device is displayed.
l Model Name
▼ Model Name
The model name of the selected Fieldbus device is displayed.
l Revision Name
▼ Revision Name
The revision name (character strings) of the selected Fieldbus device is displayed.
l MANUFAC_ID
▼ MANUFAC_ID
The manufacturer ID number of the Fieldbus device is displayed.
l DEV_TYPE
▼ DEV_TYPE
The device type number of the Fieldbus device is displayed.
l DEV_REV
▼ DEV_REV
The device revision of the Fieldbus device is displayed.
l DD_REV
▼ DD_REV
The DD revision of the Fieldbus device is displayed.
l Software Revision
▼ Software Revision
The software revision of the selected Fieldbus device is displayed.

l Capability Level
When registering a device that supports multiple capability level, the selected capability level will
be displayed. When registering a device that does not support multiple capability level, the folder
name holding the capability file will be displayed.
l Instrument Tag Name

▼ Instrument Tag Name
Smart Plant Instrumentation is an engineering tool provided by Intergraph Corporation used for
the management of plant inputs and outputs as well as the cable wirings.
l Template File Name

▼ Template File Name
The name of template file used by the fieldbus device is displayed.
n Common Information
The figure below shows the Common Information tab.
This tab displays information common to all segments.
Fieldbus Builder – [Pjt:FIELDBUS Stn:FCS0101 Train:1 Node:1 File:1ALF111-1.edf]
%Z manual decision

+ YVP_01 Schedule Adjustment
+ YF100E_01 Version Number: 4
+ EJA_01 Macrocycle Duration: 1000 msec
+ AE100_01
Time Resolution: 1 msec
+ YTA320_01
Safety Factor: 1.000000
Subschedule
Number Control Cycle StaleCountLimit Comment
1 1000 msec 5
2 2000 msec 5
3 500 msec 5
4 250 msec 5
Default Value within the range of Polling Node Address

0x10~ 0x23 ------------------------------------------- 0xE8 ~0xFF
(Range of Unpolled Node Address)
Message
Ready
D020202E.ai
Figure Common Information Tab
l Schedule Adjustment
This tab displays [Version Number], [Macrocycle Duration], [Time Resolution], and [Safety
Factor].

l Subschedule
It is possible to display and edit definitions of subschedules. Up to four subschedules can
be defined. [Control Cycle] is designated by selecting an option from the menu; an arbitrary
value cannot be entered. The content of [Subschedule 1] is fixed to one second and cannot be
changed.
l Default Value within the Range of Polling Node Address

It is possible to display and edit the polling address range.
SEE
ALSO For more details on the common information tab, see the following:
“n Setting the Information Common to Segments” in D2.3.3, “Configuring a New Fieldbus System”
n %Z List
▼ P&ID Tag Name, Tag Name, Tag Comment, Switch Position Label, Label, Btn1, Btn2, Lvl
This tab displays information of all the Fieldbus inputs/outputs (%Z) assigned to the selected
segment. The displayed definition items, [P&ID Tag Name], [Tag Name], and [Tag Comment], are
specified in the same way as IOM Builder.
SEE
ALSO For more information on the definition items of I/O modules, see the following:
A3.4.2, “Parameters for FIO Contact Inputs/Outputs” in CENTUM VP Reference, FCS Basics (IM
33M01A30-40E)
The figure below shows the %Z List tab.

Fieldbus Builder [Pjt:FIELDBUS Stn:FCS0101 Train:1 Node:1 File:1ALF111-1.edf]

- YF100E_01
RESOURCE_RI Terminal Number Block Tag Name Parameter Fast-Scan P&ID Tag Name
*
YF100A(AI_01 %Z011101 AI_1000 OUT
TRANSDUCE_T01-01%Z011102 AI_1100 OUT
- YF100E_02 %Z011103 AO_800-2 CAS_IN
RESOURCE_RI %Z011104 AO_800-2 MODE_BLK
TRANSDUCE_T01-01%Z011105
(AI_01) %Z011106
%Z011107
%Z011108
Message

D020203E.ai
Figure %Z List Tab

l Terminal Number
▼ Terminal Number
The terminal number of the selected Fieldbus inputs/outputs (%Z) is displayed.
l Block Tag Name

▼ Block Tag Name
The block tag name of the Fieldbus block assigned to the terminal is displayed. It is also possible
to change block tag names.
l Parameter
▼ Parameter
The parameter of the Fieldbus block assigned to the terminal is displayed here. It is also possible
to change parameter names.
l Fast-Scan
Check this box when designating that the terminal should be high-speed.
SEE
ALSO For more details on the high-speed designation, see the following:

D2.2.4 Device Tab

The Device tab is displayed in the client area when a Fieldbus device is selected in Tree
View. The Device tag includes the Block List tab.
n Block List
The figure below shows the Block List tab.
This tab lists the Fieldbus blocks included in a Fieldbus device.
1ALF111-1 Block List

- YVP_01 Block ID Block Tag Name Block Label Block Index Profile Profile Revision
RESOURCE_RI
RESOURCE_01 RESOURCE_R01-01 Resource Block 2 1000 0x0108 0x0101
* YVP_AO(AO_01
AO_01 YVP_AO Analog Output 5000 0x0102 0x0001
(DI_01)
DI_01 Discrete Input 6000 0x0103 0x0001
(DI_02)
DI_02 Discrete Input 6100 0x0103 0x0001
+ YF100E_01
+ EJA_01
+ AE100_01
+ YTA320_01
Message
Message Position: Line 1Column 2

D020204E.ai
Figure Block List Tab
l Block ID
▼ Block ID
The block ID of the selected block is displayed. A block ID is an arbitrary name that must be
unique in a Fieldbus device. With Fieldbus Builder and Function Block Builder, Fieldbus blocks
are identified by their block IDs.
l Block Tag Name

▼ Block Tag Name
It is possible to display and edit a block tag name. The block tag name must be unique within
an FCS. The block tag name may contain up to 16 single-byte characters. Only single-byte
alphanumeric characters, hyphen (-), underscore (_), and uppercase alphabetic characters can
be used. The string must start with an alphabetic character.

l Block Label
▼ Block Label
The block type of the selected block is displayed. For a standard block, the block type string
corresponding to the profile number is displayed. For a custom block or transducer block, the
block label in the corresponding DD file is displayed. [CUSTOM] is displayed if the block label
could not be obtained from the DD file.
l Block Index
▼ Block Index
The block index of the Fieldbus block is displayed.
l Profile
▼ Profile
The profile number of the Fieldbus block is displayed.
l Profile Revision
▼ Profile Revision
The profile revision of the Fieldbus block is displayed.
l Maximum Execution Time

▼ Maximum Execution Time
The maximum execution time of the Fieldbus block is displayed.
l Number of Parameters
▼ Number of Parameters
The number of block parameters included in the Fieldbus block is displayed.
l Subschedule Number
▼ Subschedule Number
The subschedule number of the Fieldbus block is displayed. Fieldbus block is executed in the
control cycle defined in the subschedule. Note that only Fieldbus blocks to which FF faceplate
blocks are assigned, Fieldbus blocks for which block tag names are set, or Fieldbus blocks for
which %Zs are defined, are valid.

D2.3 Standard Engineering

This section explains how to perform basic engineering using Fieldbus Builder. In
particular, the operations necessary at the start of the Fieldbus engineering and the basic
engineering operations, are explained.

D2.3.1 Environment Settings

This section explains the environment settings necessary before starting the Fieldbus
engineering.
The environment settings common to CENTUM VP projects are required at the start of the
engineering, while the environment settings common to segments should be specified as
necessary.
n Copying Capabilities Files and DD Files

Capabilities files and DD files are essential in the Fieldbus engineering. The capabilities file and
the DD file are provided from the device vendor. It is necessary to place these files in the right
folders. It is possible to copy these files using the “Copy Tool for Fieldbus associated files”.
l Copy Tool for Fieldbus Associated Files

From the [Start] menu of Windows, select [Program] - [YOKOGAWA CENTUM] - [Copy Tool for
Fieldbus associated files]. This utility allows copying capability files and DD files into the proper
folders.
SEE
ALSO For more information on how to use the Copy Tool for Fieldbus associated files, see the following:
D4.1, “Copy Tool for Fieldbus Associated Files”
n Calling Up the Environment Settings Dialog Box

There are two types of Environment Settings dialog boxes: [Project Common], [Segment
Common] and [Scheduled Load Setting].
l Calling Up the Project Common Dialog Box

When [Project Common] is selected from the [Environment Settings] menu in Fieldbus Builder,
the Environment Settings dialog box common to all segments of the project currently being
selected in Fieldbus Builder will be called up.
l Calling Up the Segment Common Dialog Box

When [Segment Common] is selected from the [Environment Settings] menu in Fieldbus Builder,
the Environment Settings dialog box for the segment currently being selected in Fieldbus Builder
will be called up.
l Calling Up the Scheduled Load Setting Dialog Box

When [Scheduled Load Setting] is selected from the [Environment Settings] menu in Fieldbus
Builder, the Scheduled Load Setting dialog box will be called up. In this dialog box, perform the
settings for checking the scheduled load when saving and downloading to Fieldbus devices.

n Project Common
▼ Project Common
The Project Common Environment Settings dialog box is used to set up the environment
common to projects when engineering the Fieldbus in the CENTUM VP system. These
environment settings must be specified when a new project is created. The figure below shows
the dialog box for performing environment settings common to projects.
Environment Settings
Project Common
Directory Path of Capabilities File/DD File

D:\CENTUMVP\eng\BKProject\MYPJT\Fieldbus\CFDDFILE Refer...
Destination Directory of Host File Set

D:\CENTUMVP\eng\BKProject\MYPJT\Fieldbus\HOSTFILE Refer...
Destination Directory of Template File

D:\CENTUMVP\eng\BKProject\MYPJT\Fieldbus\TEMPLATE Refer...
In Device Recognition Registration, the dialog box confirmed
whether the option for Capabilities file exists is not shown.
The block parameter which includes a block tag name is NOT the
scope of the loading at the time of “File” - “Download”
execution.
OK Cancel
D020301E.ai
Figure Dialog Box for Specifying Environment Settings Common to Projects
l Directory Path of Capabilities File/ DD File

▼ Directory Path of Capabilities File/ DD File
Designate the path to the directory where capability files and DD files are stored. The setting is
retained until a change is made. Designate the absolute path to the directory where capability
files and DD files are stored. If the DD file is shared by multiple PCs of the same project, the UNC
path should be designated for the project directory. This setting will be retained until the path is
changed.
l Destination Directory of Host File Set

▼ Destination Directory of Host File Set
Designate the path to the directory where the host file created at the generation is stored. The
setting is retained until a change is made.
l Destination Directory of Template File

▼ Destination Directory of Template File
Designate the absolute path to the directory where the template files are stored.
The default path is <Project Top>\Fieldbus\TEMPLATE.
If the template files are shared by multiple PCs of the same project, the UNC path should be
designated for the project directory. This setting will be retained until a change is made.
Example: UNC path for the file in PC01
\\PC01\Fieldbus\TEMPLATE

l In Device Recognition Registration, the dialog box confirmed whether the
option for Capabilities file exists is not shown
▼ In Device Recognition Registration, the dialog box confirmed whether the option for Capabilities file
exists is not shown.
When automatically registering a device, if the capability file of the device has options, a dialog
box will be displayed for notification. On this dialog box, user can select the capability file options.
Check this check box will not show this dialog box if this dialog box is not needed. The settings
will be saved until the next time they are changed.
l Do not Download Parameters When Running [Download] From [File] Menu

▼ The block parameter which includes a block tag name is NOT the scope of the loading at the time of
“File” - “Download” execution.
When running [Download] from [File] menu of Fieldbus builder, if you do not want to download
the block parameters and tag names, the following option needs to be checked.
[The block parameter which includes a block tag name is NOT the scope of the loading at the
time of “File” - “Download” execution]. By default, this option is not checked (means the block
parameters will be downloaded).
When this check box is checked, the block parameters will not be downloaded/uploaded to/from
all the fieldbus devices. This setting will be kept unless it is changed.
When choosing [Offline Load to Device] - [Initial Download] from [Offline Load] menu or from
the right-clicked pop-up menu will start initial downloading and the block parameters will be
downloaded regardless the above option setting. [Offline Load to Device] is irrelevant to this
option either.
However, the above option setting will also be valid when running [Download] from [File] menu of
n Segment Common
▼ Segment Common
This is a dialog box for specifying environment settings for each segment. Specify these settings
as necessary. The figure below shows the dialog box for specifying environment settings
common to segments.
Segment Common
Show Transducer Blocks.
The parameter is corrected manuallly.
Make NM Parameter the optimum value.
Modify schedule manually.
Accurately Calculate BNU Communication Time.
Specify the assignment order of multi-task scheduler

Assign blocks in ascending order of control period of scheduler.
Assign blocks in descending order of control period of scheduler.
Offline loading setting to Device

Tag Assignment is executed.
Address Assignment is executed.
OK Cancel
D020302E.ai
Figure Dialog Box for Specifying Environment Settings Common to Segments

l Show Transducer Blocks
▼ Show Transducer Blocks
Designate whether or not to display transducer blocks when displaying Fieldbus block lists,
editing block parameter values, and off-line downloading to Fieldbus devices. If it is desired to
download parameter values of transducer blocks at the download operation, it is necessary to
designate to display and download them. Transducer blocks are only displayed in each dialog
box if this item is checked. The setting is retained until a change is made.
SEE
ALSO • For more details on downloading, see the following:
D2.3.5, “Downloading to Fieldbus Devices”
• For more details on displaying Fieldbus block lists, see the following:
D2.2.4, “Device Tab”
• For more details on editing block parameter values, see the following:
l The Parameter is Corrected Manually

▼ The parameter is corrected manually
Enable this check box when it is desired to set communication parameters manually. This allows
manual modification of manually correctable parameters including parameters other than read-
only parameters. The default setting is [Manual Modification Disabled]. If manual modification
is designated and there is a difference between a parameter value and the parameter value
automatically calculated at the generation, the parameter name and value are displayed as
a generation message. In this case, change the setting to manual modification disabled. The
setting is retained until a change is made.
l Make NM Parameter the Optimum Value

▼ Make NM parameter the optimum value
When adding a new fieldbus device, NM parameter value will be automatically calculated
according to the capabilities after adding the fieldbus device. When a fieldbus device is deleted,
by default, the NM parameter will not be automatically calculated for communication. However,
in order to optimize the communication capability, the NM parameter can also be automatically
calculated after deleting a fieldbus device. For this purpose, this option needs to be checked.
This setting will be kept unless it is changed again.
TIP
When calculating the NM parameter value after adding a new fieldbus device, the polling address range will not
be changed. However, when the above option is checked, the polling addresses of the fieldbus devices will be
optimized during recalculating the NM parameter after deleting a device.
SEE
ALSO For more details on the NM parameter setting, see the following:
D2.4.6, “Tuning Communication Parameter Values”

l Modify Schedule Manually
▼ Modify schedule manually
Check this check box when manually modifying the schedule and communication schedule of a
Fieldbus block. Schedules can be modified manually from the Schedule Display dialog box.
IMPORTANT
Errors will occur at the time of generation if any modification affecting a schedule is made in
Fieldbus Builder or Control Drawing Builder while the [Modify Schedule Manually] check box
is checked. Clear the check box and select [Download] before making any modification that
affects the schedule. However, if the schedule has already been modified manually, the manual
modification made will be lost by the automatic schedule generation during the download.
The following changes affect a schedule.
• Changes made from Control Drawing Builder
- Control loop configuration changes
- Addition and deletion of FF faceplate blocks
- Changes of subschedule numbers of FF faceplate blocks
• Changes made from Fieldbus Builder
- Deletion of Fieldbus devices
- Setting of block tag names
- Changes of subschedule numbers
- Control cycle changes
- Changes in schedule parameters (safety factor, time resolution)
l Accurately Calculate BNU Communication Time

▼ Accurately Calculate BNU Communication Time
When this check box is checked, for the purpose of automatic scheduling, the BNU
communication time will be accurately calculated according to the transmitted data length.

n Specify the assignment order of multi-task scheduler

▼ Specify the assignment order of multi-task scheduler
The scheduler for running the communication and function block tasks can be assigned in
accordance with their control periods. Whether the assignment is in ascending order or in
descending order needs to be specified. By default [Assign blocks in ascending order of control
period of scheduler] is checked.
When changing this setting, the setting will become valid only after rescheduling performed
during saving or downloading.
TIP
For CENTUM CS 3000, the default option for this setting is [Assign blocks in descending order of control period
of scheduler]. When upgrading a project from CENTUM CS 3000 to CENTUM VP, this setting of the segments
created on CENTUM CS 3000 will be kept as [Assign blocks in descending order of control period of scheduler],
and new segments created on CENTUM VP will use [Assign blocks in ascending order of control period of
scheduler].
l Offline Loading Setting to Device

▼ Offline Loading Setting to Device
Check each of these items if it is desired to perform tag assignment and address assignment at
offline downloading to Fieldbus devices. The operation to set the device tag name of the Fieldbus
device is called “tag assignment,” and the operation to set the node address is called “address
assignment.” “Tag assignment” and “address assignment” are not performed during offline
downloading in the default settings.
SEE
ALSO • For more details on offline downloading to devices, see the following:
• For more details on the tag assignment and address assignment, see the following:
D2.3.7, “Tag Assignment/Address Assignment/Device Class Setting”

n Scheduled Load Setting

▼ Scheduled Load Setting
Scheduled load settings can be performed for each project or segment. The following figure
shows the Scheduled Load Setting dialog box.
Scheduled Load Setting
Check with Project Common Settings

Check with Segment Settings
Project Common Settings
Make it error if block or communication process time exceeds the control cycle for [X%] X= 100
Make it error if total communication process time exceeds the macro cycle for [X%] X= 50
Segment Settings
Make it error if block or communication process time exceeds the control cycle for [X%] X=
Make it error if total communication process time exceeds the macro cycle for [X%] X=
OK Cancel
D020308E.ai
Figure Scheduled Load Setting Dialog Box
l Specification of the Setting Range

Scheduled load can be checked either for each segment, or each CENTUM VP project that
includes the segment for which the dialog box was called up. The default is checking for each
project.
• Project Common Settings
To perform a check with the settings common to the project, select [Check with Project
Common Settings]. The items in [Project Common Settings] are then enabled.
• Segment Settings
If it is desirable to check individual segments with different settings, select [Check with
Segment Settings]. The items in [Segment Settings] are then enabled.
l Setting of the Threshold Value Regarding the Process Time

The threshold values for checking scheduled load can be specified both as a percentage of the
process time in a control cycle and as a percentage of the total communication process time in a
macro cycle.
• Make it error if block or communication process time exceeds the control cycle for [X%]
An error is generated if the percentage taken up by the process time of Fieldbus blocks
and communication in the control cycle exceeds the specified threshold value. Specify the
threshold value in percentage at which an error should be generated. The setting range is
from 1 to 100%, and the default value is 100%.
• Make it error if total communication process time exceeds the macro cycle for [X%]
An error is generated if the percentage taken up by the total communication process time
in the macro cycle exceeds the specified threshold value. Specify the threshold value in
percentage at which an error should be generated. The setting range is from 1 to 100%, and
the default value is 50%.
SEE
ALSO For a detailed description of each threshold value, see the following:
“n Scheduled Load” in D2.4.5, “Display and Adjust Schedule”

D2.3.2 Starting Up and Closing Down

This section explains how to start up and close down Fieldbus Builder.
n Starting Up Fieldbus Builder

There are three ways of starting up Fieldbus Builder.
l Starting Up from System View

Select the IOM tree of the desired FCS from System View, and double-click the builder file of the
displayed ALF111 module. Alternatively, select the builder file of the ALF111 module and select
[Open] from the [File] menu. Fieldbus Builder will start up.
l Starting Up from Control Drawing Builder

Select an FF faceplate block by Control Drawing Builder, and then select [Fieldbus Builder] from
the [Window] menu, or right click the FF faceplate block and choose [Fieldbus Builder] from the
pop-up menu. Then the segment in which the selected block exists is opened, the designated
block is expanded, and Fieldbus Builder will start up.
l Builder Quick Start

It is possible to search for specific Fieldbus device tag names or block tag names via the Search
by Name dialog box included in the tools of System View and to launch Fieldbus Builder based
on the search result. Click the right mouse button on the line where the desired tag name is
displayed after the search, and select [Builder] from the pop-up menu displayed.
n Closing Down Fieldbus Builder

Select [Exit] from the [File] menu of Fieldbus Builder. Alternatively, click the [Close] button in the
window of Fieldbus Builder.

D2.3.3 Configuring a New Fieldbus System

This section explains the operations and setting items of Fieldbus Builder when creating
a new segment and registering Fieldbus devices to that segment.
The following shows the procedure. This section covers steps 1 and 2 in detail.
1. Register an ALF111 module in System View and create a segment.
2. Register Fieldbus devices. (Manual or automatic registration)
3. Execute downloading.
SEE
ALSO For more details on downloading, see the following:
n Creating a Segment
A segment can be created by registering an ALF111 module in System View. When a new
ALF111 module is registered in System View, four ports are automatically created.
SEE
ALSO For more information on how to define an ALF111 module in System View, see the following:
D1.1, “Engineering of the ALF111 Module”

n Registering Fieldbus Devices

▼ Add Device, Manual Registration Dialog Box
Manual registration of Fieldbus devices can be carried out even when the Fieldbus devices
are not connected to Fieldbus segments. The following steps explain the sequence of manual
registration by going through each procedure.
l Step 1. Starting Up the Add Device Dialog Box

In Tree View of Fieldbus Builder, select the segment to which a Fieldbus device is to be added
by clicking the right mouse button in order to display the pop-up menu and select [Add Device].
Alternatively, select the segment and then [Add Device] from the [Device Registration] menu. The
“Manual Registration dialog box” is displayed.
l Step 2. Displaying the List of Devices that can Be Registered

Tree View on the left side of the “Manual Registration dialog box” displays folders where
capabilities files are stored along with sub-folders, etc. Select “Manufacturer ID” so that “Device
Type” will be expanded and displayed. Select the “Device Type” to display the list of Fieldbus
devices that can be registered in the list on the right side. The figure below shows the “Manual
Registration dialog box” that displays the Fieldbus device list.
Manual Registration
Name DEV_REV DD_REV CF_REV Date

- CFDDFILE
EJA 0x01 0x01 0x02 2001/09/20
- 594543(Yokogawa Electric)
EJA 0x02 0x01 0x04 2005/11/25
- 0003(EJA100A)
Show all Capabilities File OK Cancel
D020303E.ai
Figure Manual Registration Dialog Box
• Device Name
The device name of the Fieldbus device is displayed.
• Revision Information
The Fieldbus device revision (DEV_REV), DD file revision (DD_REV) and capability file
revision (CF_REV) are displayed.
• File Date
The file date of capabilities file is displayed.
By default only the latest capability file corresponding to each device revision is displayed.
Checking the [Show all Capabilities File] check box will display all capability files.

l Step 3. Registering a Device
Select the device to be registered from the displayed Fieldbus devices and click the [OK] button.
The Enter Device Information dialog box is displayed.
l Step 4. Entering the Device Information

▼ Enter Device Information Dialog Box
The figure below shows the Device Information Input dialog box.
Enter Device Information
Device ID:
Device Tag name: EJA_02
Node Address: 0xF2
Device Class: BASIC

Browse Button
Template File: 594543_0003_02.xml ...
OK Cancel
D020304E.ai
Figure Enter Device Information Dialog Box.
• Device ID
Enter the device ID. This information is required when performing tag assignment. It is also
acceptable to keep the device blank.
• Device Tag Name
Enter the device tag name of the selected device.
• Node Address
The node address of the selected device is displayed. Change this information as
necessary. In normal cases, it is not necessary to change this information.
• Device Class
The device class of the selected device is displayed. This value indicates the
communication ability of the Fieldbus device. Change this value as necessary. In normal
cases, it is not necessary to change this value.
• Template File
The default template file will be displayed.
However, a different template can be selected if required.
When the data entry in the dialog box is completed, click the [OK] button. Processing and checks
corresponding to the input data are performed.
SEE
ALSO • For more information about using the template, see the following:
D2.4.9, “Create and Use Template on Fieldbus Builder”
• For more information about designating the default templates, see the followings:
“l Set the Template as Default Template File” in “n Create Template File Dialog Box” in D2.4.9, “Create
and Use Template on Fieldbus Builder”

n Processing that is Performed during Manual Registration

The following explains the process to be executed when saving the device information by
overwriting after clicking the [OK] button in the Enter Device Information dialog box during
Fieldbus device manual registration.
l NM Parameter Setting
When a device is added, the NM parameter value is recalculated according to the capability
of the device described in the capability file. If the calculation results in a change to a lower
capability (the value becomes larger), a dialog box to confirm the device addition is displayed.
Select [Yes] to add the device, and [No] to cancel the device addition. If the calculation results
in a change to a higher capability, the current value rather than the result of the recalculation, is
used to register the device.
If the capability becomes lower when [Make NM Parameter the optimum value] is designated
in the Environment Settings dialog box, the parameter cannot be automatically changed even
by selecting [Yes]. The registration will be canceled automatically in this case. If the capability
becomes higher, the device is registered.
IMPORTANT
When adding devices in such a way that the capability becomes lower, the segment to which a
device is added will be reset when downloading the change contents, and all inputs/outputs of
the Fieldbus devices that are connected to that segment will be set to IOP/OOP. Afterward, it will
be recovered automatically.
n Displaying Device Information

The device information collected from the fieldbus devices connected on the fieldbus can
be displayed on Device Panel window so as to compare the information with the registered
information.
SEE

n Setting the Information Common to Segments

▼ Common Information
The parameter values necessary to create execution schedules of communication and Fieldbus
blocks are set as follows:
l Opening the Common Information Tab

Select a segment in Tree View of Fieldbus Builder, and then select the displayed Common
Information tab. The figure below shows the Common Information tab.
%Z manual decision

+ YVP_01 Schedule Adjustment
+ YF100E_01 Version Number: 4
+ EJA_01 Macrocycle Duration: 1000 msec
+ AE100_01
Time Resolution: 1 msec
+ YTA320_01
Safety Factor: 1.000000
Subschedule
Number Control Cycle StaleCountLimit Comment
1 1000 msec 5
2 2000 msec 5
3 500 msec 5
4 250 msec 5
Default Value within the range of Polling Node Address

0x10~ 0x23 ------------------------------------------- 0xE8 ~0xFF
(Range of Unpolled Node Address)
Message
Ready
D020305E.ai
Figure Common Information Tab

l Changing the Schedule Adjustment Parameters
▼ Schedule Adjustment
• Version Number
This is the version number of the schedule to be created. The number is automatically
incremented when a schedule is created from scratch or re-scheduled. This value is only
displayed, and cannot be edited.
• Macrocycle Duration
The macrocycle is the execution cycle of a schedule and is the lowest common multiple of
control cycles for each of the subschedules. The value is given in units of msec. This value
is only displayed, and cannot be edited.
• Time Resolution
Designate the time resolution for absorbing variations in communication time as a decimal
number of 1 or greater. Specify the value in units of msec.
• Safety Factor
The communication schedule is created in accordance with the calculated communication
times for all individual devices. The safety factor is an assumption base for calculating the
communication schedule by multiplying all the calculated communication times according to
the actual control communications. For setting the safety factor, use a decimal value greater
than 1.0 as the safety factor. When the value of the safety factor is specified, a schedule
based on the calculated communication times for all the individual devices and the specified
safety factor will be created.
Therefore, the created schedule will guarantee the actual control communications with
sufficient communication times.
Nevertheless, the safety factor can be specified with a value between 0.5 and 1.0 which
may create the schedule according to an assumption of shorter communication times for all
the individual devices. Since the assumption communications may be shorter than actual
control communication times, the communication may not be properly performed according
to the schedule.
l Changing Subschedules
▼ Subschedule
• Control Cycle
The control cycle is the cycle in which one subschedule is executed. The value is given
in units of msec. Select a control cycle from the displayed menu. The control cycle of
subschedule number 1 is fixed to 1000 msec, and cannot be changed.
• Stale Count Limit
The stale count limit is a limit number to ignore the BNU communication error counts.
When the control communication (BNU communication) error occurrence counts reach this
limit, a communication error alarm will be initiated.
This setting can be put into the project database when creating or modifying a control loops
on the Control Drawing Builder for the devices in the corresponding segments.
• Comment
It is possible to enter a comment of up to 255 single-byte characters or 127 double-byte
characters. The comment can be printed out by the self-documentation.

l Default Value within the Range of Polling Node Address
▼ Default Value within the Range of Polling Node Address
Designate the range of node addresses to be checked for whether or not they are actually
connected during the identification of Fieldbus devices connected to the Fieldbus. This range
is referred to as the polling address range. It is necessary that the node addresses of all the
Fieldbus devices are covered in this polling address range. Future Fieldbus device expansions
should therefore be taken into consideration when setting the polling address range.
TIP
The polling address range is automatically calculated based on the node address values of the registered
Fieldbus devices. If the automatically calculated value is within the manual set range, the manually designated
value is kept as the address range.
n Automatic Registration of Fieldbus Devices

▼ Device Recognition Registration
Automatic Registration of an actual Fieldbus device is possible if its device tag name has already
been set, it is connected to a Fieldbus segment and it is ready to communicate. This section
explains how to perform this operation.
l Preparation for Automatic Registration of Fieldbus Devices

• Preparing Capabilities Files and DD Files
In the designated folder for the project, prepare the capabilities files and DD files for the
Fieldbus devices that are to be automatically registered. This engineering task cannot be
performed properly if the folder does not provide the correct capabilities files and DD files
corresponding to the Fieldbus devices.
• Connecting Fieldbus Devices
Connect to a Fieldbus segment the Fieldbus devices for which the device tag names
have been set. Fieldbus devices whose device tag names have not been set will not be
recognized during the automatic registration processing. If there are multiple Fieldbus
devices with the same device tag name, only one of them will be recognized. In this case,
from the Device Panel specify a device tag name that does not overlap with the tag names
of any other devices.
SEE
ALSO For more information on the Device Panel, see the following in this section:

l Starting Automatic Registration of Fieldbus Devices
Select a segment with the right mouse button from Tree View in Fieldbus Builder to display
the pop-up menu, then select [Device Recognition Registration]. Alternatively, select [Device
Recognition Registration] from the Device Registration menu while a segment is selected. The
automatic registration of the Fieldbus devices starts and a dialog box indicating the progress
will be displayed. A consistency check at registration is performed and a message showing
the result will be displayed in the message display area of Fieldbus Builder. This processing is
carried out for all the Fieldbus devices connected to the segment. And the default templates
will automatically referred for getting the equalization directions and the user specified block
parameters.
If there is an option folder for the capability files of the recognized Fieldbus device, the following
confirmation dialog box will be displayed.
Device Recognition Registration
Device registered has an option. Do you select

Capabilities file according to this option?
This dialog box is not shown after that.

(If you check this box, the option is ignored
after that. If you want to uncheck this, you can
change it using the Environment Settings.)
OK Cancel
D020311E.ai
Figure Confirmation Dialog Box
Clicking the [OK] button in this confirmation dialog box will display the Device Recognition
Registration dialog box (the Capability File Selection dialog box) showing the applicable option
folder. Select a desired file from the list of capability files displayed in the Capability File Selection
dialog box.
Name DEV_REV DD_REV CF_REV Date

- CFDDFILE
EJA 0x01 0x01 0x02 2001/09/20
- 594543 (Yokogawa Electric)
EJA 0x02 0x01 0x04 2005/11/22
- 0003 (EJA100A)
+ LC1
+ STD
Show all Capabilities File OK Cancel
D020312E.ai
Figure Capability File Selection Dialog Box
SEE
ALSO For more information on messages displayed during automatic registration of Fieldbus devices, see the following
in this section:
“n Processing Performed during Automatic Registration of Fieldbus Devices”

l Completing Automatic Registration of Fieldbus Devices
The Fieldbus devices automatically registered will be displayed in the Device List tab of the
Segment tab. Modify the displayed device tag names, node addresses and device classes as
necessary. A temporary address will be assigned to a Fieldbus device without a node address.
Assign an address that does not conflict with other devices.
l Canceling Automatic Registration of Fieldbus Devices

To cancel the automatic registration of Fieldbus devices, click the [Cancel] button in the dialog
box indicating the progress during the automatic registration of Fieldbus devices. Fieldbus
devices that have been registered before clicking the [Cancel] button will remain valid.
l Generating Tentative Capabilities Files

Tentative capabilities files are automatically generated during the automatic registration of
Fieldbus devices if the corresponding capabilities files have not been provided in the designated
folder of the project. Fieldbus devices for which tentative capabilities files are created are
displayed with “***” before and after the [Model Name] in the Device List tab, indicating that the
capabilities files are tentative. This “***” indication will be attached when printing, as well.
IMPORTANT
If Fieldbus devices are registered with tentative capabilities files, it will be necessary to obtain
the formal capabilities files promptly and to update the files by performing “Update Capabilities
File/DD File.”
If the tentative capabilities files are kept in use, the results of the engineering tasks and the
operation of the Fieldbus devices cannot be guaranteed.
SEE
ALSO For more information on capabilities files/DD files, see the following:
D2.4.3, “Updating Capabilities Files and DD Files”

n Processing Performed during Automatic Registration of Fieldbus

Devices
The following processing is performed internally during automatic registration of Fieldbus
devices:
• Device Recognition
• Device ID Acquisition
• Consistency Check
• Device Registration
• Device Information Correction
• Setting of Initial Parameter Values
During automatic registration these internal operations are performed as necessary. The same
processing as in manual registration is performed for the setting of the NM parameter values.
SEE
ALSO For the explanation of the processing involved in setting initial parameter values during manual registration, see
the following in this section:
“n Processing that is Performed during Manual Registration”
The following processing is performed for block parameters:

1. Reading from capabilities files
2. Overwriting the initial values provided by Fieldbus Builder
3. Reading the user specified block parameters from the default templates.
The following provides a detailed explanation of the consistency check, which is part of the
internal processing.

l Consistency Check
In the automatic registration of Fieldbus devices, the first step is to carry out device recognition
for all the Fieldbus devices connected to a Fieldbus segment. Next, a consistency check is
carried out using the device tag names of the recognized devices as the key. The consistency
check compares the information of registered Fieldbus devices with the information actually
obtained. If inconsistencies are found during this comparison, the registered information will
be changed. A message will be displayed in Fieldbus Builder when registered information is
changed. The possible results of this comparison using the device tag names as the key, their
display messages and processing performed according to the results are listed below.
• Either MANUFUC_ID, DEV_TYPE or DEV_REV is different (Device Type Inconsistent)
The message “The device is inconsistent with the registered device” is displayed and the
registration task will not be performed.
• MANUFUC_ID, DEV_TYPE, DEV_REV and DD_REV All Match (*1) (Device Type
Consistent)
The following processing is carried out depending on what is different:
Device ID is different: The device ID will be overwritten.
Node address is different: The node address will be overwritten. The same processing is
carried out if the node address of the recognized Fieldbus device conflicts with another
Fieldbus device.
Device class is different: The device class will be overwritten.
*1: DD_REV is upward compatible; it is treated as consistent if compatibility is found.
• MANUFUC_ID, DEV_TYPE, DEV_REV, DD_REV, Node Address, Device ID, and Device
Class All Match (Consistent)
No processing will be carried out.
• The Device In Question Does Not Exist (Unregistered)
Node address is unused: The registration processing will be carried out.
Node address is used: The message “Overwrote node address of the device” is displayed
and registration processing will be carried out.
n Device ID Acquisition
▼ Device ID Acquisition
The device IDs of all the Fieldbus devices connected to a Fieldbus segment are acquired. The
[Device ID] column of the device tags registered in the Device List tab of Fieldbus Builder is
updated if both the device tag names and node addresses match. Select [Device ID Acquisition]
from the [Device Registration] menu of Fieldbus Builder in order to carry out this function.
n Backing Up Segments
▼ Save As
Segment information can be backed up through [Save As] in the [File] menu of Fieldbus Builder.

D2.3.4 Modifying Fieldbus Devices

This section explains the engineering for modifying existing Fieldbus devices.
n Modifying Existing Segments

Existing segments can be opened in the same way as opening a new segment. Fieldbus Builder
can be called up from both the System View and the Control Drawing Builder.
n Modifying Fieldbus Device Data

The following explains the procedure for modifying Fieldbus device data. If a corresponding FF
faceplate block is defined, it may also become necessary to do some engineering using Control
Drawing Builder.
SEE
ALSO For more information on the engineering using Control Drawing Builder, see the following:
D1.3, “Modifying an FF Faceplate Block”
l Changing the Device Tag Name

A device tag name can be directly changed by selecting a device tag name displayed in Tree
View of Fieldbus Builder with the mouse. And also it can be changed on the Device List tab.
When a device tag name is changed, it is checked whether or not an FF faceplate block
corresponding to a block included in the applicable Fieldbus device is defined with Control
Drawing Builder. If it is defined, a message is displayed and changing the device tag name
is prohibited. In order to change device tag names of such Fieldbus devices, it is necessary
to delete the corresponding FF faceplate blocks with Control Drawing Builder or cancel the
association with the Fieldbus blocks in advance.
l Changing the Block Tag Name

A block tag name can be directly changed by selecting a block tag name displayed in Tree View
of Fieldbus Builder with the mouse. And also it can be changed on the Device List tab.
When a block tag name is changed, it is checked whether or not an FF faceplate block
corresponding to the applicable block is defined with Control Drawing Builder. If it is defined,
a message is displayed and changing the block tag name is prohibited. In order to change the
block tag name, it is necessary to change the tag name of the corresponding FF faceplate block
with Control Drawing Builder in advance.
l Changing the Device ID

In order to change a device ID, change the [Device ID] field in the Device List tab displayed by
selecting a segment in Tree View of Fieldbus Builder.

l Changing the Node Address
In order to change a node address, change the [Node Address] field in the Device List tab.
Changing this item has the following effects:
• A difference will be generated between the VCR parameter and the polling address range.
• If an FF faceplate block corresponding to a block included in the applicable Fieldbus device
is defined with Control Drawing Builder, the FF faceplate block becomes an invalid element.
l Changing the Device Class

Perform this operation to the Fieldbus device that is to be used as a link master. Select
[LINKMASTER] or [BASIC] from the [Device Class] combo box in the Device List tab. It is not
possible to select [LINKMASTER] for a Fieldbus device without the [LINKMASTER] ability. If
such selection is made, an error message will be displayed, and the setting will return to the
original setting.
IMPORTANT
After setting the fieldbus device class, restart is required. The fieldbus device can be restarted
from the Device Panel or by directly toggling the ON/OFF power switch on the fieldbus device.
[Offline Load to Device] - [Master Data Download], or if an error has occurred during initial
downloading to the fieldbus device, it is necessary to run the [Offline Load to Device] - [Initial
Download] again.
SEE
l Changing the Software Revision

Enter the software revision in the Device List tab.
When the combo box in the software revision entry area is opened, a list of software revisions
corresponding to the software files stored under MANUFAC_ID and DEV_TYPE of the applicable
device will be displayed. Select and set the corresponding software revision. If the corresponding
revision is not included in the list, manually enter the revision from the keyboard.

n Deleting Fieldbus Devices

It is possible to delete all the Fieldbus devices in a segment as well as any Fieldbus devices.
When a Fieldbus device is deleted, it is checked whether or not an FF faceplate block
corresponding to a block included in the applicable Fieldbus device is defined with Control
Drawing Builder. If it is defined, a warning is displayed and the FF faceplate block becomes an
invalid element.
IMPORTANT
If an FF faceplate block has become an invalid element, it must be resolved, for instance by
deleting it with Control Drawing Builder or associating it with a block of a different Fieldbus
device, etc.
l Processing the NM Parameter Values

If [Make NM Parameter the optimum value] is designated in the Environment Settings dialog box,
the NM parameter value is recalculated when a device is deleted as well. If the calculation results
in a change to a higher capability (the value becomes smaller) as the result of the automatic
calculation, a confirmation dialog box is displayed. Select [Yes] to use the recalculated NM
parameter value. Select [No] to use the previous NM parameter value. In both cases, the device
is deleted.
If [The parameter is corrected manually] is designated in the Environment Settings dialog box,
a message is displayed to indicate that the value is not automatically changed to the result of
recalculation, but the device is deleted.
SEE
ALSO For more information on the Environment Settings dialog box, see the following:
IMPORTANT
If [Yes] is selected in a confirmation dialog box displayed before a change is to be made in such
a way that the NM parameter value will become smaller (the capability becomes higher) by
automatic calculation, the NM parameter value will be changed. Therefore, the segment in which
the deleted device existed will be reset during the download operation.
l Deleting All Fieldbus Devices in a Segment

▼ Delete All Devices in the Segment
Select the segment that contains the devices to be deleted in Tree View of Fieldbus Builder.
Select [Delete All Devices in the Segment] in the pop-up menu displayed by clicking the right
mouse button on Tree View. Alternatively, select [Delete All Devices in the Segment] in the
[Device Registration] menu.
l Deleting Arbitrary Fieldbus Devices

▼ Delete Device
Select the Fieldbus device to be deleted in Tree View of Fieldbus Builder. Select [Delete Device]
from the pop-up menu displayed by clicking the right mouse button on Tree View. Alternatively,
select [Delete Device] in the [Device Registration ] menu.

D2.3.5 Downloading to Fieldbus Devices

Offline download and download to the fieldbus devices have different meanings.
Moreover, offline initial download and offline master data download are also different. The
details as well as the downloading operations are explained as follows.
n Overview
Offline master data download means to download all the configuration data on the fieldbus
builders and function block builders to the fieldbus device.
Offline initial download means to import the local parameters of the fieldbus device first to the
fieldbus builder and then to download the configuration data on the fieldbus builders and function
block builders to the fieldbus device.
Initial download is used for the first time downloading to the fieldbus device after the fieldbus
device is connected. With the template of the fieldbus device, the initial downloading can be
performed according to the equalization directions described in the template.
When changing environment, the tag assignment, address assignment can be performed for
offline download. Thus, the offline download can be performed to a segment, a field device or a
function block.
SEE
ALSO For more information on the environment settings, see the following:
In downloading, the Fieldbus information is generated based on the previously defined

information, any difference in the information is detected, and only the difference information is
downloaded online. Note that, if any items that would normally be included in off-line downloading
are included among the detected difference information, an off-line download operation to the
applicable Fieldbus device is performed instead. It is possible to perform a scheduled load check
when executing a download operation.
SEE
ALSO • For more information about processing of download, see the following:
“n Processing of Download”
• For how to set a scheduled load check, see the following:

n Offline Download Operation

▼ Offline Load to Device, Initial Download, Master Data Download
The following explains steps involved in performing an offline download operation. During the
offline download operation, a dialog box for confirming the downloading of block parameters is
displayed.
l Offline Downloading for an Individual Segment

Select a segment in Tree View of Fieldbus Builder, and then right click the mouse to pop-up a
menu. Choose [Offline Load to Device] - [Initial Download] or [Offline Load to Device] - [Master
Data Download] from this pop-up menu. Or choose [Offline Load to Device] - [Initial Dowmload]
or [Offline Load to Device] - [Master Data Download] from the [Offline Load] menu on the menu
bar.
l Offline Downloading for an Individual Fieldbus Device

Select a fieldbus device in Tree View of Fieldbus Builder, and then right click the mouse to pop-up
a menu. Choose [Offline Load to Device] - [Initial Download] or [Offline Load to Device] - [Master
Data Download] from this pop-up menu. Or choose [Offline Load to Device] - [Initial Download] or
[Offline Load to Device] - [Master Data Download] from the [Offline Load] menu on the menu bar.
l Offline Downloading for an Individual Block

Select a fieldbus function block in Tree View of Fieldbus Builder, and then right click the mouse
to pop-up a menu. Choose [Offline Load to Device] - [Master Data Download] from this pop-up
menu. Or choose [Offline Load to Device] - [Master Data Download] from the [Offline Load] menu
on the menu bar.
l Offline Downloading for Transducer Blocks

Transducer blocks are only displayed in Tree View when the [Show Transducer Blocks] check
box is enabled in the Environment Settings dialog box. In order to perform offline download
operations to transducer blocks, change the environment settings to display transducer blocks.
Then select a displayed transducer block in Tree View of Fieldbus Builder, and then right click
the mouse to pop-up a menu. Choose [Offline Load to Device] - [Master Data Download] from
this pop-up menu, or choose [Offline Load to Device] - [Master Data Download] from the [Offline
Load] menu on the menu bar.
SEE
ALSO For more information on the environment settings, see the following:

l Canceling Offline Downloading
While an off-line download operation is being performed, a dialog box indicating that it is being
performed is displayed. If the [Cancel] button is clicked in the dialog box, a confirmation dialog
box is displayed. If the [Yes] button is selected, the offline downloading is terminated after the
communication currently being processed is over. If the [No] button is clicked, the confirmation
dialog box is closed and the download processing continues.
IMPORTANT
• If a warning is generated during an off-line download operation, remove the cause of the
warning and execute the off-line downloading to Fieldbus devices again.
SEE
ALSO For the operation of downloading to Fieldbus devices, see the following:
B1.4, “Download Operations”
• In the course of offline downloading to the devices, if an inconsistent class error occurs, user
can either redefine the device class or change the device settings on the fieldbus builders.
And then run offline download again.
SEE
ALSO For more information about setting device class, see the following:
“n Device Class Setting Operation” in D2.3.7, “Tag Assignment/Address Assignment/Device Class Setting”

n Download Operation
In order to perform the download operation, select [Download] in the [File] menu of Fieldbus
Builder. Download Confirmation dialog box will be displayed.
Download Confirmation
Download is executed to the following devices.
The check is attached to the device which needs Initial
Download. Moreover, the check of whether to be aimed at
block parameters is displayed.
For outside devices for Initial Download, “Differencial
Load” is executed. Moreover, when “Block parameters are
the scope of the loading” is removed, please execute the
equalization work using Device Panel after that.
Enable/Disab... Device... Block parameters are th...

YVP_01
YVP_02
YVP_03
EJX-01
EJX-02
OK Cancel
D020313E.ai
Figure Download Confirmation Dialog Box
• Initial Download
The checkboxes of the devices for initial downloading need to be checked; otherwise only
the discrepancies will be downloaded.
• Device Tag Name
The device tag names of the devices in the whole segment will be displayed.
• Block parameters are the scope of the loading
Whether to download the block parameters to a device can be decided by checking the
checkbox of the device in this column. If the checkbox is checked, the block parameters
will be downloaded to the corresponding device. The default setting for the checkboxes
are determined by the options of [The block parameter which includes a block tag name is
NOT the scope of the loading at the time of “File” - “Download” execution] on environment
settings.
If the option of [Block parameters are the scope of the loading] is unchecked, equalization of
the devices need to be performed on Device Panel after downloading.
If all the above settings for downloading are confirmed, click [OK] button to start downloading.
IMPORTANT
When downloading to fieldbus device, if the revision number of the designated device on the
fieldbus builder is different from the device on the FF-H1 fieldbus, the communication error will
occur for VCR Clear and Write, and the downloading may fail. Under the circumstance that the
communication error will occur for VCR Clear and Write, it is necessary to check the revision
numbers of the devices on both fieldbus builder and FF-H1 fieldbus using Device Panel. If the
revision numbers are not consistent, the fieldbus device on the FF-H1 fieldbus needs to be
correctly registered again.

n Processing during Downloading

▼ Download
The processing performed when [Download] is selected varies depending on the attribute of the
project and the connection status of the involved Fieldbus devices. The table below summarizes
the processing. This processing is the same as for uploading, tag assignment, address
assignment, and device class setting.
Table Processing During Online Downloading
Status Processing Remark
Actual device Fieldbus difference information is generated, the difference is detected,
exists and only the difference is downloaded.
Current Fieldbus difference information is generated, the difference is detected,
project and only the difference is downloaded. However, a warning is displayed
No actual because there is no actual device.
device The online download operation itself succeeds and the master file is
updated, but [Offline Load] - [Initial Download] must be performed to
the Fieldbus devices after installing the Fieldbus devices.
The menu shows “Save.”
Non-current project and Fieldbus difference information is generated to update the master file. “Download” is
executing Test Functions [Offline Load] - [Initial Download] must be performed after changing displayed in gray.
the applicable project to the current project.
D020306E.ai
SEE
ALSO • For more details on uploading, see the following:
• For more details on tag assignment, address assignment and device class setting, see the following:

n Initial Downloading
Initial downloading is performed after uploading a part of the block parameters from the fieldbus
device and saving them in the project database. All the block parameters will be downloaded to
the fieldbus devices except those uploaded from the fieldbus device.
The block parameters set on the function block details builder and the recommended CENTUM
block parameters are not included in the contents uploaded from the fieldbus device by default.
The option for uploading the parameters can be defined on the Device Panel or specified in a
template file.
The initial downloading in the case that the equalization directions are defined in a template or on
Device Panel, and in the case that the equalization directions are not defined will be explained
below.
l When Equalization Directions Defined in Template or on Device Panel

If the equalization directions are defined in a template or on Device Panel, the initial downloading
to the fieldbus device or getting from the field device will be performed in accordance with the
directions specified in the project database.
IMPORTANT
If the equalization directions for the application setting values (the setting values set on the
function block details builder) specify that the setting values in the fieldbus device will be used,
at the final process of the initial downloading, a message will be displayed in the message area
before getting the fieldbus block parameters to the Control Drawing Builder.
Follow the procedure below to get the block parameters.
1. Start Control Drawing Builder.
2. Select the corresponding FF faceplate block for getting the block parameters.
3. Choose [Block Parameter Acquisition] from [Tools] menu on the Control Drawing Builder.
Or choose [Block Parameter Acquisition] from the pop-up menu after right clicking the FF
faceplate block.
l If Getting Block Parameters from Fieldbus Device is Unspecified ( Equalization

Directions are not Defined)
1. Getting the block parameters from the fieldbus device and then put the parameters in to
the project database. And then download all the data to the fieldbus device. However, the
following block parameters cannot be taken from the fieldbus device.
• Application setting values (the setting values on the function block details builder)
• Recommended CENTUM initial values
2. If the downloaded application setting values are inconsistent with the settings in the fieldbus
device, the discrepancies will be displayed at the end of downloading messages.
3. If you want change the parameters of the fieldbus devices to the original setting values, you
can change the setting values on the function block details builder and run downloading
again to download the new setting values to the fieldbus device.

l Additional Explanations Regarding Initial Downloading
• When initial downloading is performed for a specified segment, the initial downloading will
be performed sequentially to all the devices in the segment.
• The parameters of the unscheduled fieldbus blocks cannot be downloaded.
• Initial downloading cannot be performed for a single block.
• If the node address set on the fieldbus device and the node address set on the fieldbus
builder are different, a new address will be assigned during initial downloading regardless
whether the environment setting of [Address Assignment is executed] is enabled or
disabled.
TIP
The [Address Assignment is executed] option on environment setting is valid only for master data download. The
[Tag Assignment is executed] option on environment setting is valid for both master data download and initial
download.
SEE
ALSO For more information about using the template files, see the followings:
A4.4, “Template”
n Types of Block Parameters

For engineering works on the fieldbus devices, the following three types of block parameters
need to be handled:
• Block parameters on function block details builder
• CENTUM recommended initial block parameters
• Other block parameters
l Block Parameters on Function Block Details Builder

These parameters are the block parameters defined on the function block details builder for FF
faceplate blocks.
SEE
ALSO For more information about block parameters on function block details builder, see the following:
B2.9, “Builder Definition Items of FF Faceplate Blocks”
l CENTUM Recommended Initial Block Parameters

These parameters are CENTUM recommended initial parameters for the block. These
parameters can be edited on the parameter editing dialog box of the fieldbus builder. However, in
most of cases, the initial parameters are used without modification.

The types of parameters are listed as follows:
Table CENTUM Recommended Initial Block Parameters (1/2)
Block Parameter Element Initial Value Block Type
STRATEGY 1 Resource, CUSTOM, Transducer
ALERT_KEY 1 Resource, CUSTOM, Transducer
FEATURE_SEL 0x7e00 (*1) Resource
CYCLE_SEL 0x8000 Resource
SHED_RCAS 640000 Resource
SHED_ROUT 640000 Resource
LIM_NOTIFY 1 (*1) Resource
CONFIRM_TIME 640000 Resource
WRITE_LOCK 1 Resource
ACK_OPTION 0x8100 Resource
WRITE_PRI 3 Resource
MODE_BLK TARGET 0x10 Auto Resource, SC, MDO, MAO,
PERMITTED 0x11 Auto+O/S Transducer, CUSTOM
NORMAL 0x10 Auto
TARGET 0x10 Auto AI, DI, MDI, MAI
PERMITTED 0x19 Auto+Man+O/S
NORMAL 0x10 Auto
TARGET 0x08 Man CS, PID, RA, IT, IS
PERMITTED 0x19 Auto+Man+O/S
NORMAL 0x10 Auto
TARGET 0x30 Cas+Auto AO
PERMITTED 0x39 Cas+Auto+Man+O/S DO
NORMAL 0x30 Cas+Auto
TARGET 0x10 Auto OS
PERMITTED 0x31 Cas+Auto+O/S
NORMAL 0x30 Cas+Auto
ALARM_SUM DISABLED 0 Resource, AI, DI, PID, RA
HI_HI_PRI 3 AI, PID, RA
HI_PRI 3
LO_PRI 3
LO_LO_PRI 3
HI_HI_LIM INF (*2)
HI_LIM INF (*2)
LO_LIM -INF (*2)
LO_LO_LIM -INF (*2)
DISC_PRI 3 DI
DISC_LIM 0
OUT_STATE 0
DV_HI_PRI 3 PID, RA
DV_LO_PRI 3
DV_HI_LIM INF (*2)
DV_LO_LIM -INF (*2)
OUT_HI_LIM INF (*2) PID, CS, RA
OUT_LO_LIM INF (*2)
SP_HI_LIM -INF (*2) PID, AO, RA
SP_LO_LIM -INF (*2)
XD_STATE 0 DO, DI
FSTATE_VAL 0 AO
D020309E.ai
*1: This initial value varies with device functionality.

*2: INF stands for infinite.

Table CENTUM Recommended Initial Block Parameters (2/2)
Block Parameter Element Initial Value Block Type
FSTATE_VAL_D 0 DO
PV_STATE 0
BYPASS 1 PID(*1)
GAIN 1
FF_GAIN 0
RESET 20
BAL_TIME 0
RATE 0
D020310E.ai
*1: These parameter values in the fieldbus devices will be used as the initial values during initial downloading. And the initial values
of these parameters will be used during the master data downloading.
l Other Block Parameters

The parameters excluded from the above-described two types of parameters are all referred
to as other block parameters. These parameters can be modified on fieldbus builder for
engineering. Uploading these parameters from the fieldbus devices to engineering builders is the
first task performed when running Initial Download to fieldbus devices.
n Master Data Download

All the configuration data completed on the engineering builders can be downloaded to the
fieldbus devices. However, a dialog box to query whether to download the block parameters to
the fieldbus devices will be displayed and confirmation is required.
If the master data download is performed to a segment, all the devices connected in the segment
will be downloaded one by one, but the block parameters will be downloaded only to the fieldbus
blocks defined in the scheduler. Once user confirms on the dialog box to download the block
parameters to the fieldbus devices, downloading will be performed for all the devices.
n Processing of Download
When [Download] is selected, the following processing is performed.
1. Generating the modified data and extracting the modified data
2. Downloading the modified data to the Fieldbus devices
3. Downloading the modified data to the ALF111 module
4. Downloading the modified data to the FCS
5. Updating the master file
The detail of each process is as follows:
l Generating the Modified Data

After comparison with the master data, the modified data will be generated.
l Downloading the Modified Data to the Fieldbus Devices

If the uploaded parameters are modified, the parameters need to be downloaded to the original
fieldbus devices. However, if the items that only allow offline modification were modified, offline
download and initial download become necessary. When running offline download under this
circumstance, the confirmation dialog box for downloading block parameters will not display. The
detailed actions during Download can be summarized according to the following circumstances:

l Cases when Off-Line Downloading is Performed in “Download”
• When a new Fieldbus device is added
• When a device tag name is changed
• When a node address is changed
l Downloading the Modified Data to the ALF111 Module

Fieldbus input/output (%Z) information, the modified data for the module and other information is
downloaded online.
l Downloading the Modified Data to the FCS

The modified information of Fieldbus input/output (%Z) is downloaded online.
l Updating the Master File

If the downloading succeeds, the master file is updated.

D2.3.6 Uploading the Block Parameters

This section explains the upload operation of the block parameters and how to cancel the
upload operation.
n Upload Operation
▼ Upload
It is possible to perform manual upload for each segment, Fieldbus device, and Fieldbus block.
What is being processed is displayed in the dialog box that indicates the execution of the upload
operation. Warnings generated during the execution of the upload operation are displayed in
the message display area of Fieldbus Builder. Perform the following operations when uploading
information:
l Upload for an Individual Segment

Select a segment in Tree View of Fieldbus Builder, and select [Upload] in the pop-up menu
displayed by clicking the right mouse button. Or select [Upload] - [Offline Load] menu.
l Upload for an Individual Fieldbus Device

Select a Fieldbus device in Tree View of Fieldbus Builder, and select [Upload] in the pop-up
menu displayed by clicking the right mouse button. Or select [Upload] - [Offline Load] menu.
l Upload for an Individual Fieldbus Block

Select a Fieldbus block in Tree View of Fieldbus Builder, and select [Upload] in the pop-up menu
displayed by clicking the right mouse button. Or select [Upload] - [Offline Load] menu.
All the static parameters are uploaded. Uploaded parameter values that must be engineered with
Control Drawing Builder are not reflected in Fieldbus Builder.
n Canceling Upload Operation

A dialog box with a [Cancel] button is displayed during the execution of the upload operation to
indicate that information is being uploaded. If the [Cancel] button in the dialog box is clicked, a
confirmation dialog box is displayed. If [Yes] is selected in the confirmation dialog box, the upload
processing is canceled at the stage where current communication processing is completed. If
[No] is selected, the confirmation dialog box is closed and the upload processing continues.

D2.3.7 Tag Assignment/Address Assignment/Device Class

Setting
This section explains the tag assignment, address assignment, and the setting of the
device class. The tag assignment and address assignment are necessary for Fieldbus
devices to operate. They can be executed at the same time as the off-line download
processing by specifying the environment settings accordingly.
SEE
ALSO For more information on how to specify environment settings, see the following:
n Tag Assignment
▼ Tag Assignment
Fieldbus devices cannot be identified simply by connecting them to a network. In order to
be identified on the network, they must have device tag names. This is prescribed in the FF
communication protocol specifications. By performing a tag assignment, device tag names are
set for actual Fieldbus devices. In order to perform a tag asLQgnment, device IDs are required.
IMPORTANT
An address assignment is performed automatically after performing a tag assignment.
n Tag Assignment Operation

Select a Fieldbus device in Tree View of Fieldbus Builder, and select [Tag Assignment] in the
pop-up menu displayed by clicking the right mouse button. Alternatively, select a Fieldbus device
and then [Tag Assignment] in the [Offline Load] menu.
n Address Assignment
▼ Address Assignment
Through the address assignment operation, node addresses are set for Fieldbus devices for
which device tags are assigned. They have been assigned temporary addresses before the
actual address assignment is performed.
IMPORTANT
It is necessary to perform off-line downloading to Fieldbus devices after performing an address
assignment.

n Address Assignment Operation

Select a Fieldbus device in Tree View of Fieldbus Builder, and select [Address Assignment] in the
pop-up menu displayed by clicking the right mouse button. Alternatively, select a Fieldbus device
and then [Address Assignment] in the [Offline Load] menu.
n Setting the Device Class

▼ Device Class Setting
When setting the device class, it is possible to set device classes for Fieldbus devices for which
device tags and node addresses are already set. The values designated at the registration of
devices are used for device classes. This function is used when making Fieldbus devices with
the Link Master capability operate as Link Master devices.
n Device Class Setting Operation

Select a Fieldbus device in Tree View of Fieldbus Builder and select [Device Class Setting] from
the pop-up menu displayed by clicking the right mouse button. Alternatively, select a Fieldbus
device and select [Device Class Setting] in the [Offline Load] menu. Or open Device Panel
and choose a fieldbus device in the device status area, then choose [Set Device Class] from
[Communication] menu.
IMPORTANT
After setting the fieldbus device class, restart is required. The device can be restarted on the
Device Panel, or by directly switching OFF/ON the power switch of the device, and then offline
downloading the settings to the fieldbus device.
SEE

D2.4 Advanced Engineering

This section explains engineering using Fieldbus Builder, focusing on the advanced
engineering.
• Data access method using %Z
• Engineering method when changing Fieldbus devices
• Adjustment method of block parameter values
• Adjustment method of schedules
• Adjustment method of communication parameter values

D2.4.1 Data Access through Input/Output Terminals

When an FF faceplate block and a function block in an FCS are connected with Control
Drawing Builder, a %Z element (Fieldbus input/output terminal) is automatically assigned.
48 points of %Z elements are reserved for one segment and it is possible to view the list
of all the definitions with Fieldbus Builder. All the %Z elements are automatically assigned
by default. However, it is also possible to reserve some of them for manual assignment to
be used by Control Drawing Builder for referencing block parameters of resource blocks
and transducer blocks.
l Designation of the Manual Determination Range

▼ %Z Manual Decision
Select the %Z List tab to enable the input field on the tool bar. Specify “% manual decision” with a
decimal number between 0 and 48, where 0 indicates that no manual determination will be made.

l Operation for Setting the Fieldbus Input/Output Terminal (%Z) Information
▼ Fast-Scan
Select a segment in Tree View of Fieldbus Builder, and select “%Z List” in the Segment tab.
File Edit View Tools DeviceRegistration OfflineLoad EnvironmentSettings Window Help

+ YVP_01
+ Terminal Number Block Tag Name Parameter Fast-Scan P&ID Tag Name Tag name Tag Comment
YF100E_01
+ EJA_01 %Z011101 YVP_AO CAS_IN
+ AE100_01 %Z011102 YF100AI OUT
+ YTA320_01 %Z011103
%Z011104
%Z011105
%Z011106
%Z011107
%Z011108
%Z011109
%Z011110
%Z011111
%Z011112
%Z011113
%Z011114
%Z011115
%Z011116
%Z011117
%Z011118
%Z011119
Message
Ready Position: Line19Column 7

D020401E.ai
Figure %Z List Tab
• Designation of Fieldbus Input/Output Terminals (%Z)

Designate desired block tag names and parameters for Fieldbus input/output terminals (%Z)
in the manual setting range.
• Fast-Scan
Enable the [Fast-Scan] check box for Fieldbus input/output terminals (%Z) that correspond
to parameters to be accessed at high speed. Up to 6 points can be designated per segment.

D2.4.2 Tuning Block Parameter Values

It is possible to tune block parameters of Fieldbus devices as necessary. This section
explains the operation.
n Edit Block Parameter Dialog Box

▼ Edit Block Parameter, Parameter, Element, Value, Type, Limit String
l Calling Up
Select a segment, Fieldbus device, or Fieldbus block in Tree View of Fieldbus Builder, and select
[Edit Block Parameter...] from the pop-up menu displayed by clicking the right mouse button.
Alternatively, select [Edit Block Parameter...] from the [Tools] menu. Then the Parameter Edit
dialog box is displayed.
l Operation of Edit Block Parameter Dialog Box

The figure below shows the Edit Block Parameter dialog box.
Parameter Edit
Device List
- 1ALF111-1 Parameter Element Value Type Limit String Trend Specification
+ YVP_01 ST_REV 0 Unsigned16
- YF100E_01 TAG_DESC 0 OctetString
RESOURCE_R01-02(RE STRATEGY 1 Unsigned16
YF100AI(AI_01) ALERT_KEY 1 Unsigned8 1~
+ Link Object MODE_BLK TARGET Auto BitString
+ Trend Object
MODE_BLK PERMITTED Auto+Man+O/S BitString
+ EJA_01 MODE_BLK NORMAL Auto BitString
+ AE100_01 OUT STATUS Bad NonSpecific NotLimitec Unsigned8
+ YTA320_01 OUT VALUE 0 Floating Point
XD_SCALE EU_100 100.0 Floating Point
XD_SCALE UNITS_INDEX 1342 Unsigned16
XD_SCALE DECIMAL 1 Integer8
OUT_SCALE EU_100 100.0 Floating Point
OUT_SCALE UNITS_INDEX % Unsigned16
OUT_SCALE DECIMAL 1 Integer8
GRANT_DENY GRANT 0 BitString
GRANT_DENY DENY 0 BitString
IO OPTS Low Cutoff BitString
OK Cancel Print
D020402E.ai
Figure Edit Block Parameter Dialog Box

• Tree View
Tree View is displayed on the left side of the Block Parameter dialog box. Tree View is a
hierarchical representation of Fieldbus devices and Fieldbus blocks, as well as link objects,
trend objects, and the elements. As many elements are displayed as there are resources of
link objects and trend objects. Device tag names are displayed for Fieldbus devices, block
tag names with temporary tag names are displayed for Fieldbus blocks, and element names
or numbers are displayed for elements. It is not possible to change the displayed names.
Transducer blocks are displayed only when the [Show Transducer Blocks] check box is
enabled in the Environment Settings dialog box.
SEE
ALSO For more information on the Environment Settings dialog box, see the following:
• Parameter
The block parameter name of the corresponding block is displayed.
• Element
The element name of the selected block parameter is displayed.
• Value
It is possible to enter a value in the edit box directly from the keyboard. If the element type
is BitString and selection type, it is possible to select one from among the listed keywords
using radio buttons. If the element type is BitString and connection type, it is possible to
select more than one of the listed values from among the listed keywords using check
boxes.
• Type
The data types of the selected block parameter and element are displayed.
• Limit String
The limit strings of the selected block parameter and element are displayed.
• Trend Specification
It is possible to set the selected block parameters as the target of trend object data
acquisition.
l Operation of Trend Specification/Link Object

The parameter value of each object is displayed by selecting a link object or trend object and
expanding each element.

l Displaying Help
Click the right mouse button in the area where the parameter name and element name are
displayed to display the pop-up menu. A dialog box that explains the parameter and element is
displayed by selecting [Parameter Explanation...] from the pop-up menu.
Parameter Edit
Device List
- 1ALF111-1 Parameter Element Value Type Limit String Trend Specification
+ YVP_01 ST_REV 0 Unsigned16
- YF100E_01 TAG_DESC 0 OctetString
RESOURCE_R01-02(RE STRATEGY 1 Unsigned16
YF100AI(AI_01) ALERT_KEY 1 Unsigned8 1~
+ Link Object MODE_BLK TARGET Auto BitString
+ Trend Object
MODE_BLK PERMITTED Auto+Man+O/S BitString
+ EJA_01 MODE_BLK NORMAL Auto BitString
+ Describe
AE100_01 OUT STATUS Bad NonSpecific NotLimitecUnsigned8
+ YTA320_01
MODE_BLK OUT VALUE 0 Floating Point
Unit: XD_SCALE EU_100 100.0 Floating Point
Used to select the block execution method for this resource.
XD_SCALE UNITS_INDEX 1342 Unsigned16
XD_SCALE DECIMAL 1 Integer8
OUT_SCALE EU_100 OK
100.0 Floating Point
OUT_SCALE UNITS_INDEX % Unsigned16
OUT_SCALE DECIMAL 1 Integer8
GRANT_DENY GRANT 0 BitString
GRANT_DENY DENY 0 BitString
IO OPTS Low Cutoff BitString
OK Cancel Print
D020403E.ai
Figure Describe Dialog Box

D2.4.3 Updating Capabilities Files and DD Files

With this command, it is possible to update capabilities files and DD files without
changing the block parameter values and block tag names when the device revision
(DEV_REV), DD revision (DD_REV), or capabilities file revision is changed after installing
a Fieldbus device, or when a device is replaced. This command can be used for both
current and non-current projects.
n Procedure for Updating Capabilities Files and DD Files

▼ Update Capabilities File/DD File
1. Obtain updated capabilities files and DD files from the Fieldbus Foundation or a Fieldbus
device vendor and copy them to the folder for storing capabilities files and DD files
designated by the project, using “Copy Tool for Fieldbus associated files”
SEE
ALSO For more information on the Copy Tool for Fieldbus associated files, see the following:
2. In Fieldbus Builder, select the device for which the capabilities file and DD file are updated,
then select [Update Capabilities File/DD File] from the [Device Registration] menu. The
Update Capabilities File/DD File dialog box will be displayed.
Updating Capabilities File/DD Files
- CFDDFILE Name DEV_REV DD_REV CF_REV
- 594543 (Yokogawa Electric) EJA 0x01 0x01 0x02
- 0003 (EJA100A) EJA 0x02 0x01 0x04
OK Cancel
D020404E.ai
Figure Update Capabilities File/DD File Dialog Box
This dialog box displays a list of capabilities files for which both the manufacturer ID
(MANUFUC_ID) and device type number (DEV_TYPE) of the selected device match.
If there is a subfolder in which option capabilities files are stored, the subfolder and
capabilities files stored there will also be displayed.

3. Select the files that suit the purpose in the Update Capabilities File/DD File dialog box, then
click the [OK] button to update the capabilities files and DD files. A confirmation dialog box is
displayed if the device revision differs from the Fieldbus device or is an earlier revision than
the current one. It is possible to cancel the updating by clicking [Cancel] in the confirmation
dialog box.
SEE
ALSO For the explanation of storage folders for option capabilities files, see the following:
“l How to Handle Option Capabilities Files” in D4.1, “Copy Tool for Fieldbus Associated Files”
IMPORTANT
• If the device revision number is changed due to modification of capability file and DD file,
or if the fieldbus block configuration is modified, when running [Download], initial offline
download will be performed to the fieldbus device.
• If the number block parameters is changed, either increased or decreased, due to
modification of capability file and DD file, when running [Download], initial offline download
will be performed to the fieldbus device.
• If any FF faceplate block becomes invalid element due to updating of DD file, all FF
faceplate blocks correspond to the fieldbus device will become invalid elements.

D2.4.4 Replacing Fieldbus Devices

This section explains the procedure and operation for replacing Fieldbus devices.
When replacing a fieldbus device, Device Panel should be used. The explanations below
are for using fieldbus builder, a legacy method.
SEE
ALSO For more information about using Device Panel when replacing the fieldbus devices, see the following:
D5.4.5, “Replacing of Devices”
n Replacing with a Fieldbus Device of the Identical Type

The following describes the procedure to replace a Fieldbus device with a Fieldbus device of the
same type having a different device ID.
l Uploading the Block Parameter Values

Upload the block parameter values of the Fieldbus device before replacing it.
SEE
ALSO For more information on how to upload block parameter values, see the following:
l Setting the Device Tag Name

Set a device tag name for the newly installed Fieldbus device using the Fieldbus Builder.
l Connecting the Fieldbus Device

Connect the newly installed Fieldbus device to the Fieldbus.
l Checking the Environment Settings

Call up the Environment Settings dialog box to check that the environment settings have been
properly specified, so that address assignment is executed at the same time as the off-line
download processing.
SEE
ALSO • For more information on the environment settings, see the following:
• For more information on the address assignment, see the following:
l Device ID acquisition
Run [Device ID aquisition] from the menu of [Device Registration] to get the device ID of the
newly installed fieldbus device.

l Downloading
Select the replacing Fieldbus device and execute, [Offline Load] - [Offline Load to Device] -
[Master Data Download]. An master data download operation to the Fieldbus device is executed.
SEE
ALSO For more information on the download procedure, see the following:
n Replacing with a Fieldbus Device of Different Device Revision

The following describes the procedure to replace a Fieldbus device with a Fieldbus device of
different device revision:
l Uploading Block Parameter Values

Upload the block parameter values to the Fieldbus device before replacing the device (perform
this operation if the Fieldbus device to be replaced is not broken).
l Updating Capabilities File/DD File

Select a Fieldbus device from Tree View in Fieldbus Builder and then select [Update Capabilities
File/DD File] from the [Device Registration] menu in order to update the capabilities file and DD
file.

Before connecting to a segment of Fieldbus device, set a device tag name for the newly installed
Fieldbus device using the Fieldbus Builder.

l Downloading
Select the newly connected Fieldbus device and execute [Download] from selecting [File] menu.
An initial download operation to the Fieldbus device is executed.
SEE
ALSO For more information on the download procedure, see the following:
l Resolving Invalid Elements

Resolve invalid elements in System View. It is not necessary to change control loops defined on
control drawings.
SEE
ALSO For more information on how to resolve invalid elements, see the following:
D1.6, “Other Engineering Items”

n Replacing with a Fieldbus Device of the Same Type Made by Other

Manufacturers
Fieldbus devices of the same type refer to devices of the same transmitter types, such as
pressure gauges, thermometers, and flowmeters, etc.
When replacing an existing feildbus device with a same type device made by different
manufacturers, the existing fieldbus device needs to be removed and the new device needs to be
registered.

Before connecting the Feildbus device to a segment of Fieldbus, set a device tag name for the
newly installed Fieldbus device.
l Removing the Existing Device

Removing the existing fieldbus device is performed on the fieldbus builder.
Select the device that needs to be replaced on the tree view of fieldbus builder, and then choose
[Delete] from [Device Registration] menu, or right click the mouse, choose [Delete] from the pop-up
menu.

l Registering the Fieldbus Device

Register the newly installed Fieldbus device using Automatic Registration.
SEE
ALSO For more information about automatically resgistration of fieldbus devices, see the following:
“n Automatic Registration of Fieldbus Devices” in D2.3.3, “Configuring a New Fieldbus System”
l Changing the Block Tag Name

If the block tag name of the automatically registered Fieldbus device is different from the block
tag name of the replaced fieldbus device, the block tag name needs to be changed on Tree View
or the Block List tab.
l Tuning Block Parameters

The block parameters of the newly connected Fieldbus device need to be adjusted accordingly.
On the tree view of the fieldbus builder, select the fieldbus device, and then choose [Editing Block
Parameter] from [Tool] menu.
A dialog box for editing the block parameter displays. The parameters of the newly registered
block can be edited on this dialog box according to the parameters of the replaced device.
SEE
ALSO For more information on the procedure for tuning block parameters, see the following:

l Downloading
On the tree view of the fieldbus builder, select a fieldbus device, and then choose [Download]
from [File] menu.
An initial download starts for the selected Fieldbus device.
l Resolving Invalid Elements

Run resolve invalid elements on System View. There is no need to change the control loops
defined in control drawings.
SEE
ALSO For more information about how to resolve invalid elements, see the following:
D1.6, “Other Engineering Items”

D2.4.5 Display and Adjust Schedule

This section explains how to display and adjust the result of scheduling communication
and block execution of each Fieldbus device, as well as the scheduled load.
n Schedule Display Dialog Box

▼ Display Schedule
l Calling Up
Select a segment in Tree View of Fieldbus Builder, and then [Display Schedule..] from the menu
displayed by clicking the right mouse button. Alternatively, select a segment and then [Display
Schedule..] from the [Tools] menu. Then the Schedule Display dialog box is displayed.
Schedule
Display Schedule
Auto Schedule Re-Schedule 100 % Undo
Version: 4 Macrocycle: 1000 msec Time Resolution: 1 msec Safety Factor: 1

Change
msec
0 200 400 600 800 1000
SCHED1
TERMO_1
TERMO_1.OUT
YVP_AO
YVP_AO.BKCAL_OUT
TERMI_2
YF100AI
YF100AIOUT
TERMI_3
EJA_AI
Print Help OK Close
D020405E.ai
Figure Schedule Display Dialog Box
l List of Block Names

Block tag names and parameter names are listed in the left side of the dialog box.
l Result of Scheduling
In the right side of the dialog box, the execution of blocks and communications is displayed
in Gantt chart format for each sub-schedule. Both executions of block and executions of
communication are displayed in one line for each item.
The result of the scheduling of execution of blocks is displayed in “Block Execution bar” and the
execution time of communication in the “Communication Execution bar.”

n Operations in the Schedule Display Dialog Box

It is possible to change the schedule result of a Fieldbus block from the Schedule Display dialog
box.
l Manual Modification of Execution Schedule

▼ Re-Schedule
The Block Execution bar and Communication Execution bar in the Gantt chart can be dragged
using the mouse and placed in any position. Terminals of Fieldbus blocks cannot be moved. The
positions of the Block Execution bar and Communication Execution bar will be adjusted to the
closest grid positions specified by the time resolution. Click the [Re-Schedule] button to adjust the
schedules of the related elements as well, which will be reflected in the Schedule Display dialog
box. Schedules in fixed status are not rescheduled.
IMPORTANT
Manual modification of an execution schedule is only possible when [Modify Schedule Manually]
is checked in the Environment Settings dialog box. If a download is carried out after clearing
[Modify Schedule Manually], the schedule will be automatically generated and the contents of
manual modification will be lost.
l Freeing Fixed Elements

Select [Fix Free] from the pop-up menu displayed by clicking the right mouse button on the
manually modified Block Execution bar or the Communication Execution bar. The fixed status of
the scheduling, in which the bar has been placed via manual modification, will be canceled.
l Displaying Properties
Select [Properties] from the pop-up menu displayed by clicking the right mouse button on the
Block Execution bar or the Communication Execution bar. The Properties dialog box that shows
the start time and the execution or communication time will be displayed.
l Canceling Re-Scheduling
▼ Undo
Click the [Undo] button. It is possible to cancel the rescheduling operation and undo the operation
only once.
l Creating New Schedules

▼ Auto Schedule
Click the [Auto Schedule] button. The execution and communication timing chart for the Fieldbus
block will be created according to the control loop configuration created in Control Drawing
Builder. If this operation is performed, the information changed by manual modification will be
lost.

l Changing Default Values
▼ Change
It is possible to change the default values for [Time Resolution] and [Safety Factor]. Click the
[Change] button to display the Change Default Value dialog box. Change the values of [Time
Resolution] and [Safety Factor] in the Change Default Value dialog box, then click the [OK]
button. Rescheduling will be carried out and the result will be reflected in the Schedule Display
dialog box. If the entered values are invalid, an error message will be displayed, the entered
value will be canceled, and the Change Default Value dialog box will await new input.
l Cancel
Click the [Cancel] button. All the changes made in the dialog box will be canceled and the dialog
box will close.
l Saving the Result of Scheduling and Exiting the Dialog Box

Click the [OK] button. The FB schedule, LAS schedule, part of the block parameter values and
communication parameter values will be generated and saved, and the dialog box will close. If
any manual modifications have been made in the Schedule Display dialog box, click the [Re-
Schedule] button, then click the [OK] button.
l Print
▼ Print
Click the [Print] button to print a schedule in Gantt chart format.
l Displaying Properties
▼ Properties
Click the right mouse button on the Block Execution bar or Communication Execution bar to
display the pop-up menu. Select [Properties] from the pop-up menu. Then the Properties dialog
box appears to display the start time and communication or block execution time.

n Scheduled Load
It is possible to check the set schedules when saving or downloading to Fieldbus devices and
stop the processing if the scheduled load exceeds the specified threshold values. The threshold
values used in the scheduled load check can be specified both as a percentage of the process
time of Fieldbus blocks and communication in a control cycle and as a percentage of the total
communication process time in a macro cycle.
SEE
ALSO For a detailed description of how to perform scheduled load check settings, see the following:
l Checking the Percentage of the Block and Communication Process Time in a

Control Cycle
The figure below shows examples of schedules where the process time of Fieldbus blocks and
communication exceeds the threshold value, which has been set to 75% of the control cycle. In
this case, because 75 has been entered in the [Make it error if block or communication process
time exceeds the control cycle for [X%]] field in the Scheduled Load Setting dialog box, an error
occurs when downloading and the processing is halted.
Control cycle 1000 msec
Threshold value = 75%
SCHED2
FF-AI
FF-AI.OUT
FF-PID
FF-PID.OUT
SCHED3
FF-AI2
FF-AI2.OUT

An error occurs if the end time of the block and/or
Control cycle 500 msec communication processing exceeds the threshold
value.
D020407E.ai
Figure Method of Checking the Percentage of the Fieldbus Block and Communication Process Time

l Communication Load Check
The figure below shows examples of schedules where the total communication process time
exceeds the threshold value, which has been set to 60% of the macro cycle. In this case,
because 60 has been entered in the [Make it error if total communication process time exceeds
the macro cycle for [X%]] field in the Scheduled Load Setting dialog box, an error occurs when
downloading and the processing is halted.
SCHED2
FF-AI
FF-AI.OUT A
FF-PID
FF-PID.OUT B
SCHED3
FF-AI2
FF-AI2.OUT C
Macro cycle 1000 msec
A B C C
An error occurs if the total communication

process time exceeds the threshold value.
D020408E.ai
Figure Method of Checking the Communication Load
The total communication process time is calculated according to the following method:
Total communication process time
= communication process time x number of times the communication processing is
performed within the macro cycle
In the example above where the macro cycle is 1000 msec and the threshold value is 60%, the
error handling is performed if the following condition is satisfied:
(Process time A + process time B + process time C x 2) / 1000 > 0.60

D2.4.6 Tuning Communication Parameter Values

This section explains how to change communication parameters. In normal engineering,
it is not necessary to change communication parameters. Change them when advanced
engineering is required.
n Edit Communication Parameters Dialog Box

▼ Adjust Communication Parameter
l Calling Up the Edit Communication Parameters Dialog Box

Select a segment in Tree View of Fieldbus Builder and then [Edit Communication Parameters]
from the pop-up menu displayed by clicking the right mouse button. Alternatively, select [Adjust
Communication Parameters] from the [Tools] menu. Then the Parameter Edit dialog box is
displayed.
Parameter Edit
Device List
- 1ALF111-1 Parameter Element Value Type Limit String

- Common FasArTypeAndRole SERVER+QUB Unsigned32 0~0xff.0
FasDllLocalAddr INITIATOR Unsigned32 0~0xff.0
NM
SM FasDllSDAP RESPONDER OctatString
+ LAS FasDllMaxConfirmDelayOnConnect CLIENT Unsigned16
+ ALF111-14 FasDllMaxConfirmDelayonData SERVER Unsigned16
+ EJA3K-1 FasDllMaxDlsduSize SOURCE Unsigned16 1~256
FasDllResidualActivitySupported SINK Boolean 0x00, 0x
+ YEWFL3K
FasDlltTimelinessClass PUBLISHER OctetString
- F01001
FasDllPublisherTimeWindowSize Unsigned16
- VCR
FasDllPublisherSynchronizingDlcep Unsigned32
VCR1 FasDllSubscriberTimeWindowSize Unsigned16
VCR2 FasDllSubscriberSynchronizingDlcep Unsigned32
VCR3 FmsVfdld Unsigned32 0~
VCR4 FmsMaxOutstanding ServicesCalling Unsigned8 0~
VCR5 FmsMaxOutstanding ServicesCalled Unsigned8 0~
VCR6 FmsFeaturesSupported NON,GET_00+READ+WRIT BitString
VCR7
VCR8
VCR9
OK Cancel Print
D020406E.ai
Figure Parameter Edit Dialog Box
l Edit Communication Parameters Dialog Box

Tree View is displayed in the left side of the dialog box. Tree View is a hierarchical representation
of common part, Fieldbus devices, groups, and items. It is not possible to change these names.
• Common
The common part is a collection of parameters common in a segment.
• Fieldbus Device
The device tag names of the segment are displayed.
• Group
A group is a group of parameters that have the same meaning. Group names are displayed
for groups.
• Item
An item is displayed when there are multiple parameter groups belonging to a group. Item
names are displayed for items (number).
• Data Display
Data corresponding to the selection in Tree View is displayed in the right side of the dialog
box.

n Tuning the Parameters Common in a Segment

The tuning made here will be reflected in all the Fieldbus devices of the segment.
l NM/SM Parameters
The NMIB and SMIB parameters are displayed by expanding the common part in Tree View
on the left side of the dialog box. NMIB parameters are related to the network management
and SMIB parameters are related to the system management. If NMIB or SMIB is selected, the
parameter list is displayed in the area on the right side. The parameter name, parameter member
name, value, type and range are displayed in the parameter list. It is only [Value] that can be
changed.
IMPORTANT
If the download processing is executed after making changes to the NM parameters, the
communication currently being executed is temporarily disconnected and the segment to which
changes are made is reset. Since changing the NM parameters affect the basic network control,
it should be performed by an expert who is familiar with the Fieldbus specifications.
l LAS Schedule Parameters

The LAS schedule is displayed by expanding the common part in Tree View on the left side of
the dialog box. LAS schedule parameters are related to the Schedule Domain. LAS schedule
parameters are further classified into the following sub-groups:
• Schedule Version Number
The version of the schedule to be executed.
• Summary
A summary of the schedule.
• Subschedule
The subschedule is expanded into four items.
• Sequence
The sequence shows the communication execution start time and the interval at which the
sequence is repeated. The sequence is expanded into multiple items.
• Element
An element is equivalent to a DLCEP address to which data is to be sent. An element is
expanded to multiple items.
n Tuning the Parameters Unique to a Device
l VCR/FB Schedule Parameters

The VCR parameters and FB schedule are displayed by selecting and expanding the
Fieldbus device in Tree View on the left side of the dialog box. VCR parameters are related to
VcrStaticEntry and FB schedule are related to FbStartEntry. Each of them is expanded into
multiple elements.

n Entering Parameter Values

There are parameters whose values can be entered in the normal way and parameters whose
values must be entered in a special way.
l Normal Entry
An edit box is displayed by clicking the area where the parameter values are displayed using
the mouse. Change the values directly via the keyboard. Alternatively, select a value from
the keyword list displayed in the combo box. Input operation can be performed only for the
parameters that can be changed.
l Special Entry
The following expression format is used in the keyword selection list for VCR parameters.
• FmsFeaturesSupported
FmsFeaturesSupported is divided into client and server lists. Unnecessary features for
a particular parameter are displayed in gray and cannot be selected. Check [NONE] to
disable all other check boxes. Check [ALL_FMS] to enable all the check boxes that are not
displayed in gray, except for [NONE]. At this point, [NONE] is disabled.
• FasArTypeAndRole
Only keywords related to the FAS Role are displayed.
• FasDllDAP
FasDllDAP is divided into S (Scheduled), D (Delivery), A (Authentication), and P (Priority).
Keywords belonging to each of them are displayed.
• FasDllTimeLinessClass
FasDllTimeLinessClass is divided into three categories and keywords belonging to each of
them are displayed.

D2.4.7 Setting Trend Objects

A trend object that manages local trend data exists within a Fieldbus device.
The block parameter within the Fieldbus device can be set the target of data collection by
the trend object. This section explains the operation of data collection by the trend objest.
n Operation of Setting Trends

▼ Trend Specification
Select a block in Tree View of Fieldbus Builder, and then the [Parameter] tab in the displayed
Block tab. The Block Parameter Value tab is displayed.
l Trend Specification
When this check box is checked, the corresponding parameter can be Specified to be collected
by a trend object. The setting for an element is recognized as the setting of a trend for the
parameter containing that element, and the parameter is set as the taeget of data collection by
the trend object.
TIP
Trend objects, VCR, and link objects within a Fieldbus device are created based on this setting at the generation
of defference information duning the online download operaton. The assigned trend objects and link objects are
displayed in Tree View after the generation is completed.

D2.4.8 Manually Copying Device For Registering Device

A new device can be registered by copying and pasting the information of a registered
device. Therefore, all the devices in the segment can be registered by repeatedly pasting
the same device information for a number of times. Moreover, by copying and pasting
the device information across different segments, the new devices can be registered for
another segment.
n Copying Device For Manually Registering Device

On [Device] tab, choose the device
to be copied and right click on it.
FieldBus Builder - [Pjt:MYPJT Stn:FCS0101Train:1 Node:1 File:1ALF111-1.edf]


+ DYF_01
Device Tag Address Device Class Device ID
DYF_01 0xF7 BASIC 0001 Yokogawa Electric
Cut 0xF6 Ctrl+X
BASIC
Copy 0xF5 Ctrl+C
BASIC
Paste Ctrl+V
Clear
Detailed Setting Items
Message
Cut selected range and save to clipboard Position: Line 1 Column 1

D020409E.ai
Figure Window for Registering Device by Copying and Pasting
1. On the fieldbus builder, choose a registered device and then choose [Copy] from the pop-
up menu after right clicking the device. Multiple devices can be chosen for copying.
2. On [Device] tab, choose a blank for pasting the device and then choose [Paste] from the
pop-up menu after right clicking the blank.
3. Copying and pasting will be complete.

n Duplicable Items
The following items can be copied and pasted.
Table Duplicable Items
Items Duplicable
Device Tag xx(*1)
Node Address xx(*2)
Device Class x
Device ID –(*3)
Software Revision Number x
Capability File x
Template File x
Block Tag Name xx(*4)
Sub Schedule Number –
Block Parameter Values x
Equalization Directions x
Links to Control Drawing Builder –
VCR –
FB Schedule –
D020410E.ai
x: Duplicable, xx: Conditionally Duplicable, –: Not Duplicable

*1: At the timing to paste, if the device tag name is identical in the segment will be checked. If an identical device tag name exists, a
two-digit number will be automatically affixed to the device tag name in the format of (<device tag name>_nn) where nn stands
for 01,02,03,04 and so on.
If the length of the device tag name exceeds 13 characters, the device tag name only takes the first 13 characters and discards
the rest from the 14th.
*2: At the timing to paste, if the node address is identical in the segment will be checked. If an identical node address exists, the first
vacant node address searched in descending order from 0xF7 will be used.
*3: Device ID will be absent.
*4: At the timing to paste, if the block tag name of resource block or tag name of transducer block is identical in the segment will be
checked. If an identical block tag name exists, a two-digit number will be automatically affixed to the block tag name in the format
of (<block tag name>_nn) where nn stands for 01,02,03,04 and so on.
If the length of the block tag name exceeds 13 characters, the block tag name only takes the first 13 characters and discards the
rest from the 14th.
Moreover, the fieldbus block tag name is always absent.

D2.4.9 Create and Use Template on Fieldbus Builder

In this section, how to create and read the template will be explained.
n Creating Template on Fieldbus Builder

▼ Create Template, Edit Template
The procedure for creating template will be explained as follows.
Set Equalization direction
Device Block Parameter Property
+ RESOURCE BLO Basic Observation Basic Config Observation Other Config Other
+ TRANSDUCER B
- FUNCTION BLOC
Prameter Name. Element Name Devices in Pt... Devices on FF... Manufacturer ... User de
(AI_01)
(AI_02) Block Tag Name FI1001
ST_REV 120 0 (No

MODE_BLK.TARGET Auto 0 (No
MODE_BLK.ACTUAL O/S 0 (No
MODE_BLK.PEMITED Auto+Man+O/S 0 (No
MODE_BLK.NORMAL Auto 0 (No
BLOCK_ERP 0 0 0(No
PV.STATUS Bad :: NonSpeci Bad :: NonSpeci (No
PV.VALUE 0 0 (No
OUT.STATUS Bad :: NonSpeci Bad :: NonSpeci (No
OUT.VALUE 3 3 (No
FIELD_VAL.STATUS Bad :: NonSpeci Bad :: NonSpeci (No
FIELD_VAL.VALUE 0 0 (No
Back to default Create Template Open Template
User default value

D020411E.ai
Figure Editing a Template on Fieldbus Builder
1. Choose a device on tree view for saving information in a template.

2. On the fieldbus builder, choose [Edit Template File] from [DeviceRegistration] menu.
3. A window for editing template will be displayed.
4. Open [Block Parameter] tab.
5. Set the user default values. Double click User default column so as to open a dialog box for
entering the user default setting values.
6. Click the check box of [It is the user default value].
7. Enter the user default values. The settings might be chosen from the keywords in the combo
box.
8. Set the equalization directions.
9. Click [Create Template] button on the window for creating the template. Then a dialog box
for creating the template will be displayed.
10. On the dialog box for creating the template, enter the template file name, comment and so
on.
11. To set the created template as a default template file, check the check box of [This template
file is the default].
12. Click [OK] button to finish.

SEE
ALSO For more information about template, see the following:
n Create Template File Dialog Box

After clicking the [Create Template] button, the Create Template File dialog box will be
displayed. On this dialog box, the file name and comment for the template file need to be
entered. Moreover, the template file can also be specified as the default template.
Create Template File
Template File 594543_0004_01_ 01 .xml

Name
Comment transmitter
This template file is the default.
Save Cancel
D020412E.ai
Figure Create Template File Dialog Box
l Template File Comment

A comment text with up to 48 alphanumeric characters or 24 double-byte characters can be
entered.

The format of the template file name is as follows:
<MANUFAC_ID>_<DEV_TYPE>_<DEV_REV>_<***>.XML
Where the *** stands for a user-defined string contains up to 8 alphanumeric characters. If this
string is not specified by user, the file name will be automatically affixed with a number and the
file name becomes follows:
<MANUFAC_ID>_<DEV_TYPE>_<DEV_REV>_nn.XML
Where nn=01,02,03,04,05, and so on. This number nn will make the template file has a unique
file name from the existing files.
l Set the Template as Default Template File

A created template file can be set as the default template file.
If a template file is set as the default template file, when recognizing and registering a device, the
information in the default template file will be automatically used. When manually registering a
device, the default template file name will be displayed on the Device Information dialog box.
On the Create Template File dialog box, checking the option of [This template file is the default],
the template file will be set as a default template file. In general, this option is checked.

IMPORTANT
When opening a template file on the Create Template File dialog box, if the option of [This
template file is the default] is not checked, there is a possibility that the device does not have a
default template or another template of the same type (with the same vendor ID, device type and
revision number) is set as the default template file.
Checking the option of [This template file is the default] will set the created template as the
default template file.
SEE
ALSO For more information about setting a template as a default template file, see the following:
“n Read Template File on Fieldbus Builder”
n Read Template File on Fieldbus Builder

▼ Open Template
The fieldbus builder will read the template file for the device with the same vendor ID, device type
and revision number. When manually registering a device, a template file list will be displayed for
selecting the required template to use. When recognizing and registering a device, the template
file list will not be displayed and the default template file for the recognized device will be used.
If the default template file is not available, the recognition and registration of the device will be
performed without using the template file.
l Action of Reading Template File on Fieldbus Builder

When the fieldbus builder reads the template file, the user specified parameters would be applied
to the block parameters in the project database.
IMPORTANT
If the proper template file for the device with the same vendor ID, device type and revision
number (MANUFAC_ID, DEV_TYPE, DEV_REV) cannot be found, the fieldbus builder will not
able to read the template file.

l Open Template File on Fieldbus Builder
The procedure to read a template file on the fieldbus builder is as follows:
1. Choose a device on tree view, choose [Open Template] from [Device Registration] menu.
FieldBus Builder - [Pjt:MYPJT Stn:FCS0101Train:1 Node:1 File:1ALF111-1.edf]
%Z manual decision
Device ID acquisition 0
Add Device
1ALF111-1 Block List Common
Delete Device Information %Z List
+ EJA_02 Delete All Devices in the Segment
Update Capabilities File/DD File
Device Tag Address Device Class Block Label Block Index
Edit Template 0xF7 BASIC
RESOURCE Resource Block 2 1000
Open Template
AI_01 Analog Input 4000
AI_02 Analog Input 4100
Message
Position: Line 1 Column 1

D020413E.ai
Figure Read Template File on Fieldbus Builder
Choose Template File
0x594543 (Yokogawa Ele Default Name Comment Date

- 0x0003 (EJA100A) 594543_0003_02_01.xml pressure 2008/03/01
02 594543_0003_02_02.xml temperature 2008/03/03
OK Cancel
D020414E.ai
Figure Choose Template File Dialog Box

2. Display of Choose Template File Dialog Box
On the Choose Template File dialog box, only the template files correspond the device
are displayed in a list. The displayed template files are the template files correspond to the
device with the same vendor ID, device type and revision number.
If a template file has been used for handling the device before, this template file will be
selected on the Choose Template File dialog box. If no template file is appreciated for the
selected device, a message will be displayed to indicate that no appreciated template file in
the list.
3. Open the required template file.
4. Checking and unchecking the option of [This template file is the default] on the template
files can change the device’s default template file.
5. Click [OK] button.
6. The template files will be accessed.
7. The template file names will be displayed on the device list of Fieldbus Builder.
IMPORTANT
When opening a template file on the fieldbus builder, choose [Download] from the [File] menu
may save the template file to overwrite the existing template file. On the dialog box for download
confirmation, the option of [Block Parameters are the scope of loading] needs to be checked and
then click [OK] button to continue.
SEE
ALSO For more information about using the block parameters in the fieldbus device during initial downloading, see the
following:
“l When Equalization Directions Defined in Template or on Device Panel” in “ Initial Downloading” in

l Read Template File for Recognizing and Registering Device
When recognizing and registering a device, the list of template files for selection will not be
displayed. The default template file for the device will be accessed directly. If the device is not
specified with a default template, the device recognition and registration will be performed.
l Read Template File for Manually Registering a Device

How to read a template file for manually registering a device on the fieldbus builder will be
explained as follows:
1. Click [Add Device] on [Device Registration] menu.
2. A list of devices will be displayed for registration.
3. Choose a device for registration and then click [OK] button.
4. The Device information dialog box will be displayed for registering the device.
5. If a template file is already specified as the default template file for this device, the default
template file name will be displayed in the dialog box. To use this default file for this device,
click [OK] and continue. To use a different template file other than the default template file,
click the [...] button next to the [Template File] blank to browse the template file. And then
click [OK] button.
Enter Device Information
Device ID: Default Tag name
Device Tag name: DYFLC1_01
Node Address: 0xF7
Device Class: BASIC
Template File: 594543_0007_01_01.xml ...
OK Cancel
D020415E.ai
Figure Specifying Template File on Dialog Box for Entering Device Information
6. Choosing and reading the template file finishes.

7. On the Device List tab of fieldbus builder, the file name of the selected template will be
displayed.
SEE
ALSO For more information about starting the fieldbus builder, see the following:
“n Starting Up Fieldbus Builder” in D2.3.2, “Starting Up and Closing Down”
For more information about manually registering devices, see the following:
“n Registering Fieldbus Devices” in D2.3.3, “Configuring a New Fieldbus System”

D2.5 Other Engineering

This section explains engineering issues that have not been covered previously.
n Self-Documentation
In self-documentation, the contents of definitions and generated contents are printed in a batch
document format in the same way as for other self-documentation in CENTUM VP.
SEE
ALSO For more information on the self-document printing operation, see the following:
F19, “Self-Documentation” in CENTUM VP Reference, Engineering (IM 33M01A30-40E)
l Calling Up the Self-Documentation Function

Select [Print] from the [File] menu to print individually.
n Import
▼ Import
By using the import processing, SVA files saved using [Save As] can be read in the same way as
other builders of the CENTUM VP.
l Operation
Select [External File] - [Import] from the [File] menu of Fieldbus Builder.
n Utility
▼ Generate Host Files
The utility includes a function to generate a host file. Note also that a host file is generated
internally as necessary at the time when the information stored in the file is updated, for example
when device tag names or block tag names are changed.
l Operation
Select [Utility] - [Generate Host Files] from the [Tools] menu of Fieldbus Builder.
n Start Device Management Tool

▼ Start Device Management Tool
Starts the Device Management Tool of the fieldbus tools if it is installed in the same PC with the
fieldbus builder.
l Procedure
Choose [Start Device Management Tool] from the [Tools] menu of the fieldbus builder. If the
device management tool is not installed, an error message will be initiated and displayed.

D2.6 Menu List

▼ Menu Bar List
This section lists the menus of Fieldbus Builder.
n Menu Bar
Table Menu Bar
Title Description
File Operations on files and the document as a whole.
Edit Edits the selected object.
Menu for changing views during editing and displaying, as well as for displaying each part of
View
the builder.
Tools Calls up options and other programs.
Device Registration Menu related to registration and deletion of devices.
Offline Load Menu related to offline download.
Environment Settings Set up environment settings of Fieldbus Builder.
Window Menu for manipulating document windows.
Help Calls up the Help.
D020601E.ai

n Drop-Down Menu
l File
▼ Print Preview, Print
Table “File” Menu

Menu title Description
Open... (*1) Opens an SVA file (for any port of ALF111).
Close Closes the active document window.
Save (*2) Saves the contents being edited to the current editor file (for ALF111 and all field devices).
Save As... Saves the contents being edited under a different file name (for ALF111 and all field devices).
External File →
Import... Imports external files. Only SVA formatted files can be imported.
Export... Outputs CSV formatted files.
Properties Displays a property sheet of a file.
Print Preview → Displays the print preview window.
Common... Executes the common print preview.
Device... Executes the device related printing.
Individual... Prints the contents that are displayed in a builder window individually.
Print → Executes printing (self-documentation).
Common... Executes the printing of the common section.
Device... Executes device related printing.
Individual... Prints the contents that are displayed in a builder window individually.
Executes online download.
Download (*2) When the settings are updated, download only the difference information to FCS, ALF111, and
to each field device.
Exit Fieldbus Builder Exits the builder.
D020602E.ai
*1: If an SVA file is opened, the operations will be limited to the following because the DD file will not be referenced.
• It is not possible to enter or edit using keywords in the Edit Block Parameter dialog box or the Communication Parameters
Tuning dialog box.
• It is not possible to invoke the block parameter explanations in the Edit Block Parameter dialog box.
*2: The “Save” and “Download” menu items do not exist at the same time. In case of the current project, the “Download” menu
becomes valid. When opening a user-defined project and files saved by “Save As,” the “Save As” menu becomes valid. When
importing files saved by “Save As,” the “Download” menu becomes valid.
l Edit
Table “Edit” Menu
Cut Deletes a selected object and stores it on the clipboard.
Copy Stores a selected object on the clipboard.
Paste Pastes data stored on the clipboard at the current position.
Clear Clears the selected data.
Select All Selects all the selectable data.
Deselect All Cancels the selection of all selected data.
Find... Searches for a specified data string.
Replace... Replaces the specified data string with any data string.
D020603E.ai

l View
Table “View” Menu
Tool bar Designates whether or not to show the tool bar.
Status bar Designates whether or not to show the status bar.
Message Display Area Designates whether or not to show the message display area.
Detailed Setting Items Designates whether or not to show the detailed setting items.
D020604E.ai
l Tools
▼ Start Control Drawing Builder
Table “Tools” Menu

Tag/Window Name
(Function common to the builders)
List...
Display Schedule ... Starts up the Schedule Display dialog box. Used to check/modify the result of scheduling.
Adjust Communication
Starts up the Edit Communication Parameters dialog box.
Parameter ...
Edit Block Parameter... Starts up the Edit Block Parameter dialog box.
Display Device
Gets and displays the information about the Fieldbus device that is connected to the Fieldbus.
Information
Start Control Starts up the Control Drawing Builder. Opens the drawing file that contains the configuration
Drawing Builder data of the selected fieldbus device and assigned FF faceplate block.
Start Device Starts the Device Management Tool of the fieldbus tools if it is installed in the same PC with
Management Tool the fieldbus builder.
Option... Start up the Operation Environment Settings sheet.
Utilities →
Generates a host file.
Generate Host Files
D020605E.ai
l Device Registration
Table “Device Registration” Menu
Device Recognition
Registration Performs automatic registration of Fieldbus devices.
Device ID acquisition Executes the device ID acquisition function.

Add Device... Starts up the Add Device dialog box. Used at manual registration.
Deletes devices. This menu becomes enabled when a device is selected, otherwise it is
Delete Device
grayed out.
Delete All Devices in Deletes all devices in a segment in a batch mode. This menu becomes enabled when a
the Segment segment is selected, otherwise it is displayed in gray.
Update Capabilities
Updates the revisions of capabilities files and DD files.
File/DD File
Edit Template File When a template file is created, sets or edits block parameters and/or equalization direction.
Open Template Reads a template file.
D020606E.ai

l Offline Load
Table “Offline Load” Menu
Executes offline download to the devices. Master data download will be performed if a device
is replaced with new device of the identical type. The initial download will be performed at the
Offline Load to Device
first time the device is connected. Initial download cannot be performed to an individual block.
→ Master Data Download
Downloading is executed for segment, device, or fieldbus block depending on the selected
Initial Download
item in Tree View. Multiple devices or Fieldbus blocks can be selected together in the Device
List or Block List display tab.
Executes the upload function. The upload processing is executed for each segment, device, or
Upload fieldbus block depending on the element selected in Tree View. In order to select more than
one devices or blocks, make multiple selections in the Device List or Block List display tab.
Executes tag assignment. This menu becomes enabled when a device is selected, otherwise
Tag Assignment
it is displayed in gray.
Executes address assignment. This menu becomes enabled when a device is selected,
Address Assignment
otherwise it is displayed in gray.
Sets the device class. This menu becomes enabled when a device is selected, otherwise it is
displayed in gray.
D020607E.ai
l Environment Settings
Table “Environment Settings” Menu
Project Common Performs environment settings common to each project, such as host file storage directory.
Segment Common Performs environment settings common to segments, such as offline download settings.
Scheduled Load Setting Performs load check settings of Fieldbus schedules.
D020611E.ai
l Window
Table “Window” Menu
Cascade Displays all the currently open document windows on top of one another in a “pile.”
Adjusts the size of each document window and aligns them the side by side so that all the
Tile Vertically
currently open document windows can be viewed.
Adjusts the size of each document window and aligns each window above the next so that all
Tile Horizontally
the currently open document windows can be viewed.
Arrange Icons Arranges icon-use document windows.
D020608E.ai
l Help
Table “Help” Menu
Using the Online
Display the online manual.
Manual...
Builder Definition Item
Displays the list of builder items.
List...
Reference Index... Displays the index of references.
Version Information Displays version information.
D020609E.ai

n Pop-Up Menus
Different pop-up menus are displayed when right mouse button is clicked depending on whether
a segment, Fieldbus device, or Fieldbus block is selected in Tree View. The table lists the
different pop-up menus that can be displayed.
Table Right-Button Menu
Selected
Pop-up menu Description Remarks
position
Device Recognition
Registers Fieldbus devices automaticaly.
Registration
Add Device Calls up the Add Device dialog box.
Adjust Communication Calls up the Edit Communication Opened in a state where devices
Parameter Parameters dialog box. are expanded.
Opened in a state where devices
Edit Block Parameter Calls up the Parameter Edit dialog box.
are expanded.
Segment Display Schedule... Calls up the Schedule Display dialog box.
Executes offline download to all devices
in a segment in a batch mode.
Initial Download
Executes upload of all devices in a
Upload
segment in a batch mode.
Delete All Devices in Deletes all devices in a segment in a
the Segment batch mode.
Opened in a state where blocks up
to the selected one are expanded.
Executes offline download to a selected
device.
Initial Download
Upload Executes upload of a selected device.
Executes tag assignment for a selected
Tag Assignment
device.
Device
Executes address assignment for a
Address Assignment
selected device.
Sets the device class for a selected
device.
Delete Device Deletes a selected device.
Updates the revisions of the Capabilities
Update Capabilities
file and DD file of the selected Fieldbus
File/DD File
device.
Opened in a state where a selected
block’s parameters are displayed.
Executes master data download to a
Master Data Download
selected block.
Block Upload Executes upload of a selected block.
Opens the drawing file that contains
the configuration data of the
Start Drawing Builder Starts up the Control Drawing Builder.
selected fieldbus device and
assigned FF faceplate block.
D020610E.ai

Blank Page
<D3. Engineering Tests> D3-1
D3. Engineering Tests

Using Test Function, it is possible to start the system and test the operations of FF
faceplate blocks and FCS function blocks even when Fieldbus devices are not connected.
Note, however, that the Fieldbus blocks in the Fieldbus devices cannot be tested.
n Tests Using Test Function

Using Test Function, the following tests can be performed even when Fieldbus devices are not
connected.
• Wiring of FF faceplate blocks
• Test of alarm status change
• Test of block mode change
• Test of input/output processing
l Software/Hardware Environment
The FF faceplate block test functions are included in the Test Function package.
TIP
Tests of alarm status change, block mode change, and input/output processing will only work for FCSs newly
created in a system running CENTUM CS 3000 software revision R3.03 or later.

D3.1 Operation when I/O is Disconnected

This section explains the operations of FF faceplate blocks and ALF111 modules when
input/output is disconnected.
n FF Faceplate Blocks
When I/O is disconnected, FF faceplate blocks and Fieldbus devices cannot communicate. In
this state, IOP/OOPs that have already been generated will recover, and new IOP/OOPs will not
be generated.
l Operation when I/O is Disconnected

The table below lists the operations of FF faceplate blocks when I/O is disconnected.
Table Operation of FF Faceplate Blocks when I/O is Disconnected
Mode/data
Item Reflection of entry in FF faceplate block Alarm
equalization
Alarms being generated
When I/O is Entries are not reflected. Entries can be only
Equalization is stopped. are recovered and
disabled made for data items of FF faceplate blocks.
become NR.
The values while the The entered values are retained until the latest
Updated when the latest
I/O is disabled are values are sent from the ALF111 module. After
When I/O is alarm information is
retained until the latest that, the values return to the device's values.
enabled again obtained from the
values are sent from Entries made while the I/O was disabled are
ALF111 module.
the ALF111 module. discarded.
D030101E.ai

n ALF111 Modules
When all inputs/outputs are disconnected or all units are disconnected, the data status of
the ALF111 module returns to the normal status. The ALF111 module operates according to
the fallback designation made in I/O Builder while I/O is disconnected. However, necessary
communication such as download communication is performed independently from the fallback
designation.
l Process Input/Output Data

Fieldbus input/output terminals (%Z) are treated in the same way as in other I/O modules while
I/O is disconnected.
IMPORTANT
• It is necessary to disconnect inputs and outputs in order to perform alarm status change,
block mode change, and input/output tests. If inputs and outputs are disconnected during
the target test, simulated input/output values of FF faceplate blocks and the input/output
values of the actual process (Fieldbus blocks) will not match. If the disconnected inputs
and outputs are connected in this status, the values output to the actual process may
change suddenly and may induce disturbances to the actual process. The test function
does not support tracking inputs and outputs of the actual process. Therefore, care must be
exercised when changing the status of inputs/outputs from disconnected to connected.
• When the I/O is disconnected by Test Functions, if the settings of the Control
Drawing Builder are modified and the modified contents are online-downloaded, the
CONFIGURATION ERROR may occur and ALF111 may fail when the I/O is reconnected
due to the discrepancies from the actual I/O settings. In order to recover the failed ALF111,
it is necessary to perform IOM download to ALF111 and offline-download to the fieldbus
devices.

D3.2 Wiring Test

The FF faceplate blocks connected with FCS function blocks can be tested just like other
function blocks by virtually wiring the block parameters.
l Wiring of FF Faceplate Blocks

It is possible to wire to parameters of FF faceplate blocks that are connected to function blocks of
an FCS. Check the Fieldbus input/output terminals (%Z) to be wired using Fieldbus Builder. The
table below shows the wiring types that can be used. Wire connections between FF faceplate
blocks cannot be made because they do not use Fieldbus input/output terminals (%Z).
Table Wiring Types that can be Used
Data type Wiring types that can be used
AI8
AU8
AI16
AU16 Wiring types where wiring connection destination is an analog input.
AI32 Wiring types where wiring connection destination is an analog output.
AU32
AF32
AF32S
D Wiring types where wiring connection destination is contact input.
DS Wiring types where wiring connection destination is contact output.
D030102E.ai
SEE
ALSO For more information on the wiring types, see the following:
C1, “Wiring Type Details” in Engineering Test Guide (IM 33M10D20-40E)

l Wiring of FF-DI Block and Enhanced Switch Instruments
When FF-DI block is connected to the input terminals of three-position input enhanced switch
instruments (SIO-21E, SIO-22E, SIO-22PE) or enhanced MC instruments (MC-2E, MC-3E), the
wiring needs to be performed manually. Automatic wiring cannot run properly. In more details,
the wiring types maybe applied to IN1 and IN2 terminals of three-position input enhanced switch
instruments or enhanced MC instruments with %Z elements can also be applied to IN1 and IN2
terminals of three-position input enhanced switch instruments or enhanced MC instruments with
ZOUT terminal of FF-DI block.
A loop diagram of FF-DI and SIO-22E is illustrated as follows:
IN1 OUT1
SIO-22E MV
IN2 OUT2
OUT OUT
FF-DI FF-DI
ZOUT ZOUT
Input Input Output Output

Terminal Terminal Terminal Terminal
Ind3Ind2+
or
Ind3Ind2-
Ind3Ind1+
or
Ind3Ind1- D030202E.ai
Figure Wiring of FF-DI Block and Enhanced Switch Instruments
When wiring a loop with a SIO-22E block only, the IN1 terminal can be applied with Ind3Ind1+
(Direct) or Ind3Ind1- (Reverse) and IN2 terminal can be applied with Ind3Ind2+ (Direct) or
Ind3Ind2- (Reverse). When wiring a loop with FF-DI blocks and SIO-22E block, and the terminals
IN1 and IN2 are connected to FF-DI blocks, the ZOUT terminal of the FF-DI block connected
to IN1 of SIO-22E block can be applied with Ind3Ind1+ (Direct) or Ind3Ind1- (Reverse) and the
ZOUT terminal of the FF-DI block connected to IN2 terminal can be applied with Ind3Ind2+
(Direct) or Ind3Ind2- (Reverse).

D3.3 Alarm Status and Block Mode Setting Tests

Test Function allows to perform the following tests without communicating with Fieldbus
devices.
• Generation of or recovery from required alarms in FF faceplate blocks.
• Setting of modes that are normally set internally by Fieldbus devices and compound
modes.
It is necessary to disconnect inputs and outputs in order to perform these tests.
n Changing Alarm Status from Test Function

If Test Function has requested to generate/recover from an alarm, the applicable FF faceplate
block performs the notification processing of the specified alarm and changes the alarm status. It
is only possible to test the generation and recovery of the alarm status (including NR) that the FF
faceplate block has.
l Operation of the Alarm Status Change Test

• Only the notification processing of the specified alarm is performed. Alarm detection is not
performed.
• The generation/recovery of the specified alarm is notified even if the status is different from
the internal status of the FF faceplate block.
Example:
HI alarm is generated if the HI alarm is specified even in the condition of PV < HI.
• Block mode and operation are not affected by alarm generation.
• Cancellation of alarm detection and suppression of alarms are performed in the same way
as for other function blocks in the FCS.
n Changing the Block Mode from Test Function

If Test Function has requested to change the block mode, the applicable FF faceplate block
switches to the specified block mode.
l Operation of the Block Mode Change Test

• In order for the specified block mode to be set, the FF faceplate block must have that block
mode.
• The block mode of the connecting FF faceplate block will never be changed when the block
mode of a connected function block changes.
• The block mode is not changed unless it is specified to change the block mode.
• The FF faceplate block switches to the specified block mode even if it is different from the
internal status.
Example 1:
The FF faceplate block mode may be switched to the TRK mode even if there is no tracking
signal.
Example 2:
The FF faceplate block mode may be switched to the CAS mode even if it is not connected
in cascade.

n Operation of the Alarm Status and Block Mode Setting Test

The alarm status and block mode setting test is executed from Test Function.
1. Select [Change FF Faceplate Block Alarm Status/Block Mode] from the [Tools] menu of the
Test Function main window.
2. The FF Faceplate Block Alarm Status/Block Mode dialog box appears.
FF Faceplate Block Alarm Status/Block Mode
Tag Name
... Update
Alarm Status
IOP IOP- OOP CNF
HH LL HI LO
DV+ DV- VEL+ VEL-
MHI MLO INT
Settings
Block Mode
O/S
IMAN
TRK
MAN AUT CAS PRD
RCAS ROUT
Settings
Close
D030301E.ai
Figure FF Faceplate Block Alarm Status/Block Mode Dialog Box
3. Enter the tag name of the FF faceplate block in [Tag Name] and click the [Update] button.
The current alarm status and block mode appear.
4. Specify the alarm status or block mode you want to set, and click the [Settings] button.
5. Click the [Update] to confirm that the setting has been performed correctly.

D3.4 FF Faceplate Block Input/Output Test

This test function allows to perform the following tests without communicating with
Fieldbus devices.
• Data exchange between an FF faceplate block and connected function blocks (input/
output connection processing)
• Creation of output data from input data (output data creation processing)
It is necessary to disconnect inputs and outputs in order to perform these tests.
n Input/Output Test from Test Function

When the input/output test is executed from Test Function, data is exchanged between the FF
faceplate block and the connection destinations according to the connection method.
In this test, the following processing is performed depending on the block mode of the FF
faceplate block.
Table Block Modes and Processing
Mode Name Description of processing
O/S Out of Service All the functions are halted.
Initialization Output data creation processing is halted and the manipulated output value
IMAN
Manual is output.
Output data creation processing is halted and the specified value is forcibly
TRK Tracking
output.
Output data creation processing is halted and the manipulated output value
MAN Manual
is output.
AUT Auto Output data creation processing is performed and the result is output.
CAS Cascade Output data creation processing is performed and the result is output.
Remote
RCAS Output data creation processing is performed and the result is output.
Cascade
Remote
ROUT Output data creation processing is performed and the result is output.
Output
D030401E.ai
l Input Connection Processing

Data of the connection destinations is referenced according to the connection information,
and the data is stored in the data items in the FF faceplate block. The input signal conversion
processing is set to “non-conversion.”
l Output Processing
After the output data creation processing is executed, the data is transferred from the output
terminals to the connection destination data “without converting” the output signals.
l Operation of Input/Output Processing

• The block mode will neither be changed automatically nor a process alarm is generated
even if an error occurs during the input/output processing.
• The states of input data, output data, and set value data are set in the same way as for FCS
function blocks via the input/output processing.
• Complicated calculations are not performed in the output data creation processing. Only PV,
SV, and MV are set based on the input signals.
• Data status is not changed in the output data creation processing.

n Operation of Input/Output Test

The input/output tests are executed from Test Function.
1. Select [Set FF Faceplate Block I/O Action] from the [Tools] menu in the Test Function main
window.
2. The FF Faceplate Block I/O Action dialog box appears.
FF Faceplate Block I/O Action
I/O Action
Current State Stop Start
End
Close
D030402E.ai
Figure FF Faceplate Block I/O Action Dialog Box
The current input/output status is displayed in [Current State].

3. Click the [Start] button to start the input/output test. The input/output processing of the FF
faceplate block that was connected to the ALF111 module, which is currently disconnected,
is started by Test Function.
4. Click the [End] button to end the input/output test. The input/output processing also ends if
you close this dialog box or exit Test Function.

D3.5 Individual Processing during the FF

Faceplate Block Input/Output Test
This section explains the processing performed during the input/output test of each FF
faceplate block.
n Input/Output Test Processing of FF AI Blocks

The following processing is performed during the input/output test of an FF-AI block.

Not performed.
l Output Data Creation Processing

The value of OUT_V is set equal to PV when the block mode is AUT.
l Output Connection Processing

OUT_V is set as the connection destination of the OUT terminal.
n Input/Output Test Processing of FF DI Blocks

The following processing is performed during the input/output test of an FF-DI block.

Not performed.

The value of OUT_V is set equal to PV when the block mode is AUT.

OUT_V is set as the connection destination of the OUT terminal.

n Input/Output Test Processing of FF Control Selector Blocks

The following processing is performed during the input/output test of an FF-CS block.

Data is acquired from the blocks connected to the IN1, IN2, and IN3 terminals, and then stored in
SEL1, SEL2, and SEL3, respectively.

Depending on SEL_TYPE, MV is set to the following value.
Table Value Assigned to MV
SEL_TYPE 1 2 3
The maximum value The minimum value
The mean value of
MV among SEL1, SEL2, among SEL1, SEL2,
SEL1, SEL2, and SEL3
and SEL3 and SEL3
D030501E.ai

MV is set as the connection destination of the OUT terminal.

n Input/Output Test Processing of FF PID Controller Blocks

The following processing is performed during the input/output test of an FF-PID block.

• IN Terminal Processing
Data is acquired from the block connected to the IN terminal, and then stored in IN_V.
• SET Terminal Processing
Data is acquired from the block connected to the SET terminal, and then stored in CSV.
• TIN Terminal Processing
Data is acquired from the block connected to the TIN terminal, and then stored in TRK_VAL.
• TSI Terminal Processing
Data is acquired from the block connected to the TSI terminal, and then stored in TRK_IN_D.
• BIN Terminal Processing
Data is acquired from the block connected to the BIN terminal, and then stored in FF_VAL.

Depending on MODE, SV, MV and PV are set to the following values.
Table Values Set According to MODE
MODE
CAS RCAS TRK ROUT AUT
Data item
PV IN_V IN_V IN_V IN_V IN_V
MV IN_V IN_V TRK_VAL RMV IN_V
SV CSV RSV – – –
D030502E.ai


n Input/Output Test Processing of FF Ratio Blocks

The following processing is performed during the input/output test of an FF-RA block.

• IN and IN1 Terminal Processing
Data is acquired from the blocks connected to the IN and IN1 terminals, and then stored in
IN_V and IN1_V, respectively.
• SET Terminal Processing
• TIN Terminal Processing
Data is acquired from the block connected to the TIN terminal, and then stored in TRK_VAL.
• TSI Terminal Processing
Data is acquired from the block connected to the TSI terminal, and then stored in TRK_IN_D.

MODE
CAS RCAS TRK AUT
Data item
PV IN_V IN_V IN_V IN_V
MV IN_V IN_V TRK_VAL IN_V
SV CSV RSV – –
D030503E.ai


n Input/Output Test Processing of FF AO Blocks

The following processing is performed during the input/output test of an FF-AO block.


MODE
CAS RCAS TRK AUT
Data item
PV CSV RSV – SV
MV CSV RSV – SV
SV CSV RSV – –
D030504E.ai

n Input/Output Test Processing of FF DO Blocks

The following processing is performed during the input/output test of an FF-DO block.


MODE
CAS RCAS TRK AUT
Data item
PV CSV RSV – SV
MV CSV RSV – SV
SV CSV RSV – –
D030505E.ai


n Input/Output Test Processing of FF Output Splitter Blocks

The following processing is performed during the input/output test of an FF-OS block.


Depending on MODE, SV, OUT1_V, and OUT2_V are set to the following values.
MODE
CAS AUT
Data item
SV CSV –
OUT1_V CSV SV
OUT2_V CSV SV
D030506E.ai

OUT1_V and OUT2_V are set as the connection destinations of the OUT1 and OUT2 terminals,
respectively.
n Input/Output Test Processing of FF Signal Characterizer Blocks

The following processing is performed during the input/output test of an FF-SC block.

Data is acquired from the blocks connected to the IN1 and IN2 terminals, and then stored in
IN1_V and IN2_V, respectively.

OUT1_V and OUT2_V are set to the following values.
Table Values Assigned to OUT1_V and OUT2_V
OUT1_V IN1_V
OUT2_V IN2_V
D030507E.ai

OUT1_V and OUT2_V are set as the connection destinations of the OUT1 and OUT2 terminals,
respectively.

n Input/Output Test Processing of FF Integrator Blocks

The following processing is performed during the input/output test of an FF-IT block.

• IN1 and IN2 Terminal Processing
Data is acquired from the blocks connected to the IN1 and IN2 terminals, and then stored in
IN1_V and IN2_V, respectively.
• RFW1 and RFW2 Terminal Processing
Data is acquired from the blocks connected to the RFW1 and RFW2 terminals, and then
stored in RFW1_V and RFW2_V, respectively.
• RSTI Terminal Processing
Data is acquired from the block connected to the RSTI terminal, and then stored in RSTI_V.
• RSTC Terminal Processing
Data is acquired from the block connected to the RTSC terminal, and then stored in RSTC_V.

CPV is set to the value of IN1_V.

• OUT Terminal Processing
CPV is set as the connection destination of the OUT terminal.
• OPTR Terminal Processing
OPTR_V is set as the connection destination of the OPTR terminal.
• OTR Terminal Processing
OTR_V is set as the connection destination of the OTR terminal.

n Input/Output Test Processing of FF Input Selector Blocks

The following processing is performed during the input/output test of an FF-IS block.

• IN1, IN2, IN3, and IN4 Terminal Processing
Data is acquired from the blocks connected to the IN1, IN2, IN3, and IN4 terminals, and then
stored in IN1_V, IN2_V, IN3_V, and IN4_V, respectively.
• DIS1, DIS2, SID3, and DIS4 Terminal Processing
Data is acquired from the blocks connected to the DIS1, DIS2, DIS3, and DIS4 terminals,
and then stored in DIS1_V, DIS2_V, DIS3_V, and DIS4_V, respectively.
• OSEL Terminal Processing
Data is acquired from the block connected to the OSEL terminal, and then stored in OSEL_V.

Depending on the value of OSEL_V, SEL_V and CPV are set to the following values.
• If OSEL_V is different from 0
Table Values Assigned to SEL_V and CPV when OSEL_V is Different from 0
OSEL_V 1 2 3 4
SEL_V 1 2 3 4
CPV IN1_V IN2_V IN3_V IN4_V
D030508E.ai
• If OSEL_V is 0
Table Values Assigned to SEL_V and CPV According to the Value of SEL_TYPE
SEL_TYPE 1 2 3 4 5
The terminal The terminal
number of the number of the
SEL_V 1 minimum value maximum value 0 4
among IN1_V to among IN1_V
IN4_V to IN4_V
The average of the
data values of
The minimum The maximum (IN1_V+IN2_V
IN1_V to IN4_V,
CPV IN1_V value among value among +IN3_V+IN4_V)
excluding the
IN1_V to IN4_V IN1_V to IN4_V /4
maximum and
minimum values
D030509E.ai

• OUT Terminal Processing
CPV is set as the connection destination of the OUT terminal.
• SEL Terminal Processing
SEL_V is set as the connection destination of the SEL terminal.

n Input/Output Test Processing of FF Multiple Discrete Input Blocks

The following processing is performed during the input/output test of an FF-MDI block.

Not performed.

Not performed.

OUT1_V to OUT8_V are set as the connection destinations of the OUT1 to OUT8 terminals,
respectively.
n Input/Output Test Processing of FF Multiple Discrete Output Blocks

The following processing is performed during the input/output test of an FF-MDO block.

Data is acquired from the block connected to the IN1 to IN8 terminals, and then stored in IN1_V
to IN8_V, respectively.

Not performed.

Not performed.
n Input/Output Test Processing of FF Multiple Analog Input Blocks

The following processing is performed during the input/output test of an FF-MAI block.

Not performed.

Not performed.

OUT1_V to OUT8_V are set as the connection destinations of the OUT1 to OUT8 terminals,
respectively.

n Input/Output Test Processing of FF Multiple Analog Output Blocks

The following processing is performed during the input/output test of an FF-MAO block.

Data is acquired from the blocks connected to the IN1 to IN8 terminals, and then stored in IN1_V
to IN8_V, respectively.

Not performed.

Not performed.

Blank Page
<D4. Tools Related to Fieldbus Engineering> D4-1
D4. Tools Related to Fieldbus Engineering

This chapter explains required tools and utilities when engineering the Fieldbus.

<D4. Tools Related to Fieldbus Engineering> D4-2
D4.1 Copy Tool for Fieldbus Associated Files

The Copy Tool for Fieldbus associated files is a utility used for copying the DD files and
capability files as well as Fieldbus device software files to the machine on which the
engineering is performed.
l Operation of the Copy Tool for Fieldbus Associated Files

From the [Start] menu of [Windows], select [YOKOGAWA CENTUM] - [Copy Tool for Fieldbus
associated files]. Then the Copy Tool for Fieldbus associated files is displayed. Designate the
following items in the displayed window:
• Copy source folder/file
Specify the DD files, capability files and Fieldbus device software files you want to copy,
either as folders or individual files. You can select folders also from the dialog box.
TIP
The DD files and capabilities files of Fieldbus devices made by Yokogawa Electric Corporation are stored in the
following folder on the CENTUM VP software medium. This folder can be specified as the [Copy source folder].
DVD-ROM drive: \CENTUM\YOKOGAWA_DD\594543
• Copy destination folder

Designate the folder to be copied to. It is also possible to select a folder from the dialog box.
If a file already exists, it will be overwritten.
The following example for project name MYPJT shows how the copy destination can be
specified.
C:\CENTUMVP\eng\BKProject\MYPJT\Fieldbus\CDDFILE
l How to Handle Option Capabilities Files

Option capabilities files of Fieldbus devices should be stored in a folder under the device type
folder, where the option capabilities files’ relationships with the rest of the project data is clear.
In this case, DD files should also be stored in the device type folder. An example of a folder
configuration for project name MYPJT is shown below.
C:\CENTUMVP\eng\BKProject\MYPJT\Fieldbus\CDDFILE\594543\0001
Vendor ID Device type

folder folder
D040101E.ai
TIP
A subfolder for option capabilities files will be displayed in the Add Device dialog box during manual registration of
Fieldbus devices and the Update Capabilities File/DD File dialog box.

<D5. Device Panel> D5-1
D5. Device Panel

This chapter describes Device Panel. Device Panel supports the equalization between
Fieldbus devices in the project database and Fieldbus devices on the FF-H1 bus.
The following explains a menu list, basic operation and advanced operation.

D5.1 Device Panel Overview

This section describes an overview of Device Panel, including the positioning of Device
Panel, relationships with other software, and the overall configuration of Device Panel.
n Positioning of Device Panel

Device Panel is assumed to be used in the following cases in the construction and operation
procedures of a Fieldbus system.
• Device Panel is used by startup work in the construction of a Fieldbus system. The “connection”
work at startup is performed to incorporate Fieldbus devices into the CENTUM VP system so
that they can be used.
• It is used to replace Fieldbus devices during the maintenance work.
Conventional (4 to 20 mA Analog Communication) System Construction/Operation Procedure
Order/adjustment/
installation of device
Connect Test run/actual run Device/system maintenance
System (DCS) design/ Startup

offline engineering
Fieldbus System Construction/Operation Procedure
Order/adjustment/ Startup
installation of device
Adjust
Connect Test run/actual run System maintenance
device
System (DCS) design/

offline engineering
Replace
Device maintenance
device
Main target operations

of Device Panel
D050101E.ai
Figure Positioning of Device Panel in System Construction/Operation

n Relationships with Other Software

Device Panel has the following relationships with other software.
l Relationship with System View

Device Panel can be started from System View. Device Panel can individually be started from the
Start menu.
l Relationship with Fieldbus Builder

Device Panel can be started from Fieldbus Builder.

n Configurations of Device Panel

Device Panel consists of the following configurations:
• Environment setting
This configures the operating environment of Device Panel.
• Device status display
This configures the Fieldbus device status display.
• Equalization
This configures the equalization of the devices in the project database and the devices on
the FF-H1 bus as well as the relevant device information.
• Communication
This configures the communication of the Fieldbus devices connected to a segment.
• Creating Template Files
The template files used for fieldbus device engineering can be created.
The created template files can also be edited and saved.
• Registering Device
On the Device Panel, all the recognized FF-H1 devices can be registered to the project
database.
Device Panel
Environment setting
Device status display
Equalization
Communication
Template
Device Registration
FF-H1 Fieldbus
Fieldbus device
D050102E.ai
Figure Configurations of Device Panel

D5.2 Menu List

This section describes the menu of Device Panel.
n Menu Bar
The following table lists the menu titles displayed on the menu bar of Device Panel.
Table Menu Bar
Title Description
Project Menu for performing file operation and operation of project
Edit Menu for editing a selected object
Menu for changing the view while editing or displaying, and for changing the display of each part of
View
Device Panel
Tool Menu for calling an option or another program
Communication Menu pertaining to communication with Fieldbus devices
Option Menu for setting the operating environment of Device Panel
Window Menu for operating windows
Help Menu for calling Help
D050201E.ai
n Drop-Down Menu
The following table shows the details of the menu titles displayed on the menu bar of Device
Panel.
l Project
Table [Project] Menu
Menu Title Description
Open Opens the reference of a folder dialog box.
Close Closes an active window.
Displays up to four projects used recently.
(Recent Project)
By selecting a project being displayed, that project can be opened.
Exit Device Panel Quits Device Panel.
D050202E.ai
l Edit
Table [Edit] Menu
Select All Select all selectable data. (Enabled only in the device status display area (*1))
D050203E.ai
*1: The device status display area is a configuration element of Device Panel’s main window. The information pertaining to Fieldbus
devices is displayed in the device status display area.

l View
Table [View] Menu
Toolbar Specifies whether or not to display the toolbar.
Status Bar Specifies whether or not to display the status bar.
Project Bar Specifies whether or not to display the project bar.
Message Bar Specifies whether or not to display the message bar.
Switches the positions of the FCS name and ALF111 name displays and the comment
Switch Show Comment
display.
Display Device Detail Info Specifies whether or not to display the device information.
Display Block Info Specifies whether or not to display the block information.
Device Info Display Settings Specifies the content of the device information to be displayed.
Sorting Sorts and displays the display items based on the specified key.
Node Address
Device Tag Name
Device ID
Device Class
Update Time
MANUFAC_ID
DEV_TYPE
DEV_REV
Property Displays the property sheet. (Enable only in the project/plant configuration display area)
D050204E.ai
l Tool
Table [Tool] Menu
Re-acquires the display target information of all devices being connected to the segment
(excluding information to be acquired by constant cycle update). If a device is being selected
Update
in the device status display area (*1), the selected device is subject to update.
At that time, all contents in the project/plant configuration display area are also updated.
Commission Places the selected device in the commission state.
Decommission Places the selected device in the decommission state.
Detects the difference from the device in the project database whose device tag matches for
a device(s) selected in the device status display area (*1), opens the Device Information Display
Display Device Info... dialog box, and then displays the result. Values can be edited and equalized in the Device
Information Display dialog box.
Address Reassign Calls the dialog box for reassigning the node address of the device.
D050205E.ai
SEE
ALSO For more information about commission and decommission, see the following:
“l Connection Status of the CENTUM VP System and Fieldbus Devices” in “n Device Status Display” in
D5.3.3, “Device Recognition and Status Display”

l Communication
Table [Communication] Menu
Master Data Download Executes master data download in the device status display area (*1) for the selected device.
This menu is enabled when a device is selected. Otherwise, this menu is grayed out.
Tag Assignment Executes tag assignment in the device status display area (*1) for the selected device.
Address Assignment Executes address assignment in the device status display area (*1) for the selected device.
Executes tag clear in the device status display area (*1) for the selected device.
Tag Clear This menu is enabled when the device status is “decommission” and a device is selected.
Otherwise, this menu is grayed out.
Executes address clear in the device status display area (*1) for the selected device.
Address Clear This menu is enabled when the device status is “decommission” and a device is selected.
Otherwise, this menu is grayed out.
Executes device class setting in the device status display area (*1) for the selected device.
Set Device Class Then, device restart is executed.
Device Restart Executes device restart in the device status display area (*1) for the selected device.
Starts the Device Settings dialog box for the selected device(s) in the device status display
Software Download area (*1).
Starts only the Device Settings dialog box if no device is being selected.
Block Instantiation Executes block instantiation for the selected device in the device status display area (*1).
D050206E.ai
l Option
Table [Option] Menu
Environment Settings Starts the Environment Settings dialog box.
Specifies whether or not to match the display style in each device status display area (*1) or
Display style its matching method.
Same style for all Makes all display styles in the device status display area (*1) identical.
Inherits the display style only if a segment is newly opened. If a correction is made after a
Previous style for
segment has been opened, that display style is used as the display style in individual device
new segment
status display areas (*1).
Individual style Displays each device status display area (*1) in an independent display style.
Restart Starts the constant cycle renewal of the device panel.
Stop Stops the constant cycle renewal of the device panel.
(Toggled between Restart and Stop on the menu)
D050207E.ai

l Window
Table [Window] Menu
Cascade Displays all windows that are currently opened by overlaying them.
Tile Vert Adjusts the sizes of all windows that are currently opened and displays them by arranging
horizontally so that all of them can be viewed.
Tile Horz Adjusts the sizes of all windows that are currently opened and displays them by arranging
vertically so that all of them can be viewed.
Arrange Icons Arranges iconized windows.
D050208E.ai
l Help
Table [Help] Menu
Using the
Online Manual Displays the Using the Online Manual.
Device Panel Items Displays a list of Device Panel items.

Reference Index Displays the index of references.
Version Information Displays the version information.
D050209E.ai
n Window Configuration
The following shows the window configuration of Device Panel.
Device Panel – [FCS0103:NODE1:1ALF111:1ALF111-1]
Project(P) Edit(E) View(V) Tool(T) Communication(C) Option(O) Window(W) Help(H)
Open Preview Print Update Stop ZoomIn ZoomOut Message DDMenu DevDlg AllRec Com Decom Help
Devices on FF-H1 bus Information Basic Info
MYPJT
FCS0102 Device Tag : YVP_01
FCS0103 242 Device ID : 5945430007PP2YVP15
NODE1 Device Class : BASIC
1ALF111-1 YVP_01 Update Time : 2008/03/31 14:41:22
1ALF111 2008/03/31 14:41:22
1ALF111-1
YVP_01 Device Tag : YVP_02
YVP_02 Device ID : 5945430007J0000390
245
Device Class : BASIC
1ALF111-2 YVP_02 Update Time : 2008/03/31 15:26:18
1ALF111-3 2008/03/31 15:26:18
1ALF111-4
Project
Ready Engineer
Project/plant configuration display area Device status display area

D050210E.ai
Figure Window Configuration

D5.3 Basic Operation

This section describes the basic operation to be performed in order to equalize Fieldbus
devices using Device Panel. The Device Panel operations pertaining to environment
settings, device recognition and status display, and equalization are explained.
n Workflow
The following describes the procedure for equalizing Fieldbus devices using Device Panel.
Start
Start Device Panel
Environment settings
Device recognition
and status display
Device information
display
Equalization
Quit Device Panel
End
D050301E.ai
Figure Workflow

l Start Device Panel
Start Device Panel in one of the following methods:
• Start from System View.
• Start from Fieldbus Builder.
• Start from the [Start] menu.
l Environment Settings
Set the following items:
• Path information to the library database
• Path information of the folder of the capabilities file/DD file
• Whether or not to set the block mode after equalization
• Whether or not to include the block parameters as the target of equalization
• Whether or not to include the difference of the block parameter values as the target of
comparison/detection.
• Wait time after changing the device class
l Device Recognition and Status Display

• Identifies whether or not a Fieldbus device is being connected to a segment.
• Displays the device status.
l Device Information Display

Displays the device information (device tag name, node address, device ID and device class).
l Equalization
Associates devices in the project database and devices on the FF-H1 bus, and performs
equalization.
IMPORTANT
If multiple Device Panels have been started for the same project from different PCs, only one
Device Panel can be equalized. An error will occur if equalization is performed while another
Device Panel is being equalized.
l Quit Device Panel

Quits Device Panel.

D5.3.1 Starting and Quitting

This section describes the startup method and quitting method of Device Panel.
n Starting Device Panel

The following three methods are available to start Device Panel.
l Starting from System View

In System View, specify a builder file on port-by-port basis of the ALF111 module defined in the
current project, and select [Fieldbus] and then [Display Device Information] from the [Tools]
menu.
System View
...Tools...
3ALF111-1
Select
3ALF111-2
3ALF111-3 Device Panel
3ALF111-4
3ALF11
1-1
D050302E.ai
Figure Starting from System View
l Starting from Fieldbus Builder

Select [Display Device Information] from the [Tools] menu of Fieldbus Builder.
System View
...Tools...
3ALF111-1
3ALF111-2
3ALF111-3 Device Panel
3ALF111-4
3ALF11
Double-click
1-1
Fieldbus Builder
...Tools...
Select
D050303E.ai
Figure Starting from Fieldbus Builder

l Starting from the [Start] Menu
Select [YOKOGAWA CENTUM] and then [Display Device Information] from the [Start] menu of
Windows.
Device Panel
Display Device Information
CENTUM
Start
D050304E.ai
Figure Starting from the Start Menu
If there is the current project, it is displayed on Device Panel.

If there is no current project, by selecting [Open] from the Project menu of Device Panel, the
Reference of a Folder dialog box will appear. Specify a project folder in the Reference of a Folder
dialog box.
(Example of a project folder)
C:\CENTUMVP\eng\BKProject\MYPJT
n Quitting Device Panel

Select [Exit Device Panel] from the Project menu of Device Panel. Or, click the [Close] button in
the Device Panel window.
However, if the progress bar is being displayed while some kind of communication is being
executed, it is not possible to quit Device Panel.

D5.3.2 Environment Settings

This section describes the environment settings of Device Panel. It is necessary to
perform environment settings before device recognition, status display and equalization.
TIP
Once environment settings are performed, the same settings will be used thereafter. It is not necessary to
perform environment settings every time Device Panel is started.
n Calling the Environment Settings Dialog Box

▼ Environment Settings Dialog Box
To call the Environment Settings dialog box, select [Environment Settings] from the Option menu
of Device Panel.
Library Database Folder Path : Option
C:\CENTUMVP\DevicePanel \LibraryDB Reference... Block mode is changed to the MAN mode after equalization.
The equalization of block parameter's values are
CF/DD files Folder Path :
targeted by the equalization processing.
C:\CENTUMVP\DevicePanel \LibraryDB\CFDDFILE Reference...
Equalization items
Template File Folder Path :
“Equalization needed flag( ! )” is displayed as additional
C:\CENTUMVP\eng \BKProject\MYPJT\Fieldbus\TEMPLATE Reference... information if there are differences after checking on the
difference of Devices in Project and Devices on Bus when
PRM Database Folder Path :
devices are recognized.
Reference... The difference comparison item is specified. Now, device
information is always the target of difference detection.
Interval of a constant cycle renewal : 5 (sec) Block parameter value is not targeted.
Block parameter value is targeted.
Waiting time after Device Class change : 30 (sec)
Resource Block
Transducer Block
OPC server computer name :
Function Block
OK CANCEL
D050305E.ai
Figure Environment Settings Dialog Box
The following items can be set in the Environment Settings dialog box.
• Library Database Folder Path
• CF/DD files Folder Path
• Template Folder Path
• Option
• Equalization items
• Interval of a constant cycle renewal
• Waiting time after Device Class change

n Library Database Folder Path

Specify the absolute path of the folder of the library database. The default path is “<CENTUM VP
installation folder>\DevicePanel\LIBRARYDB.” It is not necessary to change the default setting.
TIP
The library database is a folder in which template files provided for each DEV_REV of a Fieldbus device is stored.
A template file contains the information specific to a Fieldbus device and the information required to operate and
monitor that Fieldbus device.
n CF/DD Files Folder Path

Specify the absolute path of the folder in which CF/DD files (capabilities file and DD file) are
stored. The default path is “<CENTUM VP installation folder>\DevicePanel\LIBRARYDB\
CFDDFILE.”
If the DD file is shared by multiple PCs of the same project, the UNC path should be designated
for the project directory.
TIP
• The folder in which the capabilities file and DD file are stored is located under the folder of the library
database.
• It is also possible to specify the storage folder of the capabilities file and DD file on the CENTUM VP
system side. The default path on the CENTUM VP system side is “<CENTUM VP installation folder>\eng\
BKProject\MYPJT\Fieldbus\CFDDFILE.”
• If the DD file is shared by multiple PCs of the same project, the UNC path should be designated for the
project directory.
For example
The computer’s name is PC01.
\\PC01\Fieldbus\CFDDFILE
n Folder Path of Template Files

Designate the absolute path to the directory where template files are stored. The default path is
<Project Installed Folder>\Fieldbus\TEMPLATE
If the template file is shared by multiple PCs of the same project, the UNC path should be
designated for the project directory. This setting will be retained until the path is changed.
n Option
Option setting is performed when executing equalization. Set it as necessary.
The following two option settings are available:
• Block mode is changed to the MAN mode after equalization.
Select whether or not MODE_BLK.Target of all function blocks is set to the MAN mode or a
mode equivalent to the MAN mode when equalizing.
This option is not selected by default (check box is OFF).
• The equalization of block parameter’s values are targeted by the equalization processing.
Select whether or not the block parameter values will be equalized when equalizing.
This option is selected by default (check box is ON).
TIP
The MAN mode is the status in which MAN or MAN equivalent is set in MODE_BLK.Target. MAN equivalent is
the status in which a mode conforming to the MAN mode is set for a function block for which the MAN mode is not
allowed. For example, O/S is set in a function block without the MAN mode.

n Equalization Items
When recognizing a Fieldbus device, requirement of equalization is determined by detected
difference between the information of a registered device and the information of a device on the
FF-H1 bus. At that time, the block parameter values for difference check will be selected. The
device information including the block structure is always used to detect differences.
In case the difference of the block parameter values will be detected, the target block types can
also be selected individually. The following three block types are available:
• Resource block
• Transducer block
• Function block
n Interval of a Constant Cycle Renewal

Fieldbus devices are recognized in a constant cycle. Here, specify the interval for Device Panel
to recognize Fieldbus devices being connected to a segment. The default value is 5 seconds.
When recognizing Fieldbus devices, the live list (a list of Fieldbus devices being connected to a
segment) is updated and the device information (device tag name, device ID) is acquired.
TIP
When clicking [Stop] on the Option menu or [Stop] button on the toolbar, the constant cycle renewal of the device
panel can be stopped. The constant cycle renewal may be stopped when it is conflicting with other tasks such as
software downloading.
n Waiting Time after Device Class Change

The Fieldbus device restart function is executed when the device class is changed. Set the wait
time until the Fieldbus device restart function is executed after the device class is changed.
The default value is 30 seconds.
TIP
It is necessary to restart Fieldbus devices in order to reflect device class change. In Device Panel, the Fieldbus
device restart function is executed automatically when the device class is changed.
Since a Fieldbus device writes the information about device class change into EEPROM, it is necessary to set the
time until a write operation is completed as the wait time. The time to write into EEPROM varies depending on the
Fieldbus device in use.

D5.3.3 Device Recognition and Status Display

This section describes the operations pertaining to the recognition of Fieldbus devices
being connected to a segment as well as the status display.
n Device Recognition
Device recognition identifies the Fieldbus devices when they are connected to a segment. When
a Fieldbus device is recognized, the icon of the Fieldbus device appears in the device status
display area of Device Panel. Device Panel acquires the information required for equalization
from the recognized Fieldbus device.
Once the recognition of Fieldbus devices is complete, the Fieldbus devices are placed in a state
that allows on-demand communication. A temporary address is assigned to the node address of
a device on the FF-H1 bus. The following describes the conditions for determining the temporary
address.
• Temporary addresses are assigned in the descending order from 0xF7. Example: 0xF7,
0xF6, 0xF5, 0xF4
• Unique addresses are used among devices being connected to the same segment.
• Addresses that do not duplicate with the addresses registered in the project database are
used.
l Processing to Be Performed When Recognizing Fieldbus Devices

Using the node address as a search key, whether or not Fieldbus devices are being connected
to a segment is recognized. The result is reflected in the live list (a list of Fieldbus devices
being connected to a segment). This processing is performed in a constant cycle. The following
processing is performed according to the difference that occurred in the live list.
• If a device has been deleted
The device that corresponds to the deleted node address will be deleted from the device
status display area.
• If a device has been added
The device added will be recognized. The recognized device is displayed in the device
status display area.

l Processing to Be Performed When Displaying the Device Information of
Fieldbus Devices
The following describes the processing to be performed when displaying the device Information
of Fieldbus devices.
1. A Fieldbus device in the live list is displayed in the device status display area as the device
on the FF-H1 bus.
2. The device information (device tag name, device ID) is acquired from the Fieldbus device.
3. Using the device tag name acquired as a search key, the project database is searched. If
the corresponding device tag name does not exist in the project database, “?” (question
mark) is displayed on the device on the FF-H1 bus as an auxiliary mark. Conversely, if the
device registered in the project database does not exist under the segment, “?” (question
mark) is displayed on the device in the project database as an auxiliary mark.
4. The device information of the device in the project database with matching device tag
name and the device information of the device on the FF-H1 bus are compared. If there
is a difference, the mark to indicate the parameter value discrepancies is displayed on the
device on the FF-H1 bus as an auxiliary mark.
D050323E.ai
Figure The Mark to Indicate the Parameter Value Discrepancies
n Device Status Display

This function displays the status and device information (device tag name, node address, device
ID and device class) of Fieldbus devices being connected to a segment. The status and device
information of Fieldbus devices are checked when recognizing devices. Device Panel acquires
the information required for equalization by this check.
If there is mismatch between the information of devices in the project database and the
information acquired, it is necessary to perform equalization. For devices in this state, the mark
indicating that equalization has not been executed is displayed on the devices on the FF-H1 bus
as an auxiliary mark. There are following two types of device statuses:
• Connection status of the CENTUM VP system and Fieldbus devices
• Status of Fieldbus devices
D050323E.ai
Figure The Mark Indicating that Equalization has not been Executed

l Connection Status of the CENTUM VP System and Fieldbus Devices
There are two types of connection statuses between the CENTUM VP system and Fieldbus
devices: commission status and decommission status. The user can change the connection
status of the CENTUM VP system and Fieldbus devices. The following table shows the details of
the connection status between the CENTUM VP system and Fieldbus devices.
Table Connection Status of the CENTUM VP System and Fieldbus Devices
Status Description Display style Remark
Decommission status The decommission status signifies that a “ ” (tag It is necessary to change to this
device is in the status being logically mark) is status when replacing devices. The
detached from the CENTUM VP system. displayed on following functions can be selected
The device in this status can safely be the device. when changing to this status.
removed from a segment. If Address Clear • Address Clear
is selected, Auto Recognition stops after • Tag Clear
the node address is cleared. (To reset, After the above functions are
change to the commission status.) executed, devices will not be
recognized automatically.
Commission status The commission status signifies that a
device is in the status being logically
connected to the CENTUM VP system. –
Devices in this status will be recognized
automatically.
D050306E.ai
l Statuses of Fieldbus Devices

The statuses of Fieldbus devices to be displayed on Device Panel are listed below.
Table Statuses of Fieldbus Devices
Condition/work status Description Display style Remark
Indicate Parameter When the parameter values have discrepancies, a mark is Auxiliary mark
Value Discrepancies shown to indicate that the equalization is required.
Unknown device This is displayed for a device that has not been registered “ ? ” Auxiliary mark
in the project database, but has been connected to a
segment. This is diplayed on a device on the FF-H1 bus. It
is placed in decommission status.
Non-existent device This is displayed for a device that has been registered in “?” Auxiliary mark
the project database, but has not been connected to a
segment. This is displayed on a device in the project
database.
Error This is displayed for a device on which a communication Background Flashes several
error has occurred. Specifically, this is displayed when one in red times when an
of the following errors occured. error occurs, and
• Error when acquiring the live list: Displayed for ALF111 then settles.
• Error when executing SM_IDENTIFY (*1): Displayed for
ALF111
• Error when executing INITIATE (*2): Displayed for
individual devices
Failed acquiring data This is displayed if the communication was successful, but “NEG” Character string
could not aquire data due to a device problem.
Stop This is displayed for devices that have suspended update “X” (stop Auxiliary mark
processing. mark)
Acquiring data This is displayed while the required information is being “ ” Auxiliary mark
acquired. The equalization processing cannot be executed (hourglass
for devices in this condition. mark)
Assign This is displayed while assigning addresses. “i” Auxiliary mark
(information
mark)
D050307E.ai
*1: Acquires the device information (device tag name, device ID).
*2: Establishes a connection to a device.

l Help Display of Auxiliary Marks
It is possible to display the explanation of auxiliary marks.
l Device Status When Recognizing Again

If a device already recognized in Device Panel is recognized again, Device Panel compares
the information of the registered device with the newly acquired device information. The device
information to be compared is listed below.
• Device tag name
• Node address
• Device ID
• Device class
• MANUFAC_ID, DEV_TYPE, DEV_REV
• Software revision
• Block structure
If a mismatch is found in the device information during this comparison, the mark indicating that
equalization has not been executed is displayed on a device on the FF-H1 bus as an auxiliary
mark. It is necessary to perform equalization for devices indicated by this auxiliary mark.
D050323E.ai
SEE
ALSO For the operation when modifying equalized devices in Fieldbus Builder, see the following:

D5.3.4 Device Information Display

This section describes the operation to display the information of recognized devices.
n Device Information Display

Double-click the segment being displayed in the project/plant configuration display area.
The device information of Fieldbus devices being connected to the selected segment and the
statuses of devices and blocks are displayed in the device status display area.
In the case of newly recognized Fieldbus devices, the hourglass marks will be displayed with the
devices on the FF-H1 bus. The hourglass mark indicates that the processing for acquiring the
device information required for equalization is being executed. Since a new device information
file of Fieldbus devices is created here, this processing cannot be stopped. Therefore, devices in
this state cannot be equalized.
In the case of already recognized Fieldbus devices, the saved device information is acquired.
The number displayed at the right-hand side of the fieldbus device is the node address.
MYPJT
FCS0102
FCS0103
NODE1
1ALF111
1ALF111-1
YVP_01(247)
YVP_02(246)
1ALF111-2
1ALF111-3
1ALF111-4
D050308E.ai
Figure Selecting a Segment
n Device Information Update

If saved device information is displayed, it is necessary to update it to the latest device
information. To update the device information, select a device to be updated in the device status
display area, and select [Update] from the pop-up menu that appears when the right button is
clicked.
The device information and date are updated.
To stop updating the device information, select a device on which an hourglass mark is being
displayed, and select [Stop] from the pop-up menu that appears when the right button is clicked.
Doing so will not update the device information and update time.
Device Tag : YVP_01

242 Device ID : 5945430007PP2YVP15
YVP_01 Update Time : 2008/03/31 14:41:22
2008/03/31 14:41:22
Device Tag : YVP_02

Device ID : 5945430007J0000390
245
YVP_02 Update Time : 2008/03/31 15:26:18
2008/03/31 15:26:18
D050309E.ai
Figure Result of Device Information Update

n Customizing the Display Content

It is possible to select whether each item of the device information will be displayed. To customize
the display content of the device information, perform the following procedure:
1. Select [Device Info Display Settings] from the [View] menu.
The Detail Info Settings dialog box appears.
Detail Info Settings
Basic Info Detail Info

Device Tag MANUFAC_ID
Device ID DEV_TYPE
Device Class DEV_REV
Updae Time
OK CANCEL
D050310E.ai
Figure Detail Info Settings Dialog Box
2. Check the check box of an item to be displayed in the Detail Info Settings dialog box, and
then click the [OK] button. All check boxes are checked by default.
The selected items will be displayed as the device information.
n Connecting Devices to a Segment

To connect devices to a segment, perform the following procedure:
1. Connect Fieldbus devices on the field side to a segment.
2. Select the segment that is connecting the Fieldbus devices in the project/plant configuration
display area of Device Panel.
The device information and icons of the Fieldbus devices are displayed in the device status
display area.
Device Tag : YVP_01

242 Device ID : 5945430007PP2YVP15
YVP_01 Update Time : 2008/03/31 14:41:22
2008/03/31 14:41:22
Device Tag : YVP_02

Device ID : 5945430007J0000390
245
YVP_02 Update Time : 2008/03/31 15:26:18
2008/03/31 15:26:18
Device Tag : YVP_03

Device ID : 5945430007J0000424
246
YVP_03 Update Time : 2008/03/31 18:26:22
2008/03/31 18:26:22
D050311E.ai
Figure Connecting Devices to a Segment

D5.3.5 Equalization
This section describes the equalization operation that matches the information of devices
in the project database and the information of devices on the FF-H1 bus, as well as the
processing.
n Flow of Equalization
The following shows the procedure of equalization using Device Panel.
Start
Call the Device

Information Display
dialog box
Display the difference
Equalization
End
D050312E.ai
Figure Flow of Equalization Using Device Panel
When recognizing devices, the status and device information of Fieldbus devices are checked.
The Device Panel acquires the information required for equalization from the Fieldbus device.
The statuses of Fieldbus devices are displayed in the device status display area based on the
information acquired. If mismatch is found between the information of device in the project
database and the information of device on the FF-H1 bus, the auxiliary mark is displayed on
device on the FF-H1 bus to indicate that equalization has not been executed.
D050323E.ai
After the statuses of devices are displayed, association is made between the devices in the
project database and the devices on the FF-H1 bus using the device tag names of the Fieldbus
devices as search keys. If the same device tag name as that of a device on the FF-H1 bus exists
for a device in the project database, association will automatically be made between the device
in the project database and the device on the FF-H1 bus. If the same device tag name as that of
a device on the FF-H1 bus does not exist for a device in the project database, it is necessary to
manually associate the device in the project database to the device on the FF-H1 bus. Select a
device on the FF-H1 bus in the device status display area, and drag and drop it onto a device in
the project database in the project/plant configuration display area.

When association between the device in the project database and the device on the FF-H1 bus is
complete, the following information will be compared:
• Device information (device tag name, node address, device ID, device class, MANUFAC_
ID, DEV_TYPE and DEV_REV)
• Software download condition
• Block structure
• Block parameter values
TIP
The software download condition is a value that indicates whether or not the software installed on a Fieldbus
device has been switched to the newly downloaded software. If the work to switch software (activation) has
not been completed, the software download condition is displayed. It is necessary to activate the device in this
condition.
IMPORTANT
While an auxiliary mark (hourglass mark) indicating “acquiring data” is displayed, equalization
cannot be executed. To execute equalization, the information required to detect the difference
must have been acquired from a device on the FF-H1 bus.

n Processing Content of Equalization

If a mismatch is found between the information of a device in the project database and the
information of a device on the FF-H1 bus, Device Panel performs equalization. When performing
equalization, select either the information of a device in the project database or the information
of a device on the FF-H1 bus as the master. The information selected as the master is reflected
on the other information that was not selected as the master and, as a result, the information of
the device in the project database and the information of the device on the FF-H1 bus will match.
Basically, in equalization, the information of a device in the project database is used as the
master.
The processing to be performed when equalizing varies according to the information of a device
to be selected as the master. The processing to be performed when equalizing also varies
according to information to be compared. The following table shows the details of equalization
processing performed according to the information to be selected and the information to be
compared.
Table Equalization Processing According to the Information to Be Compared
Information
Equalization processing Remark
to be compared
Software revision If a device in the The software corresponding to the Software download can be
project database is software revision of a device in the executed only if a device on
selected project database is downloaded to a the FF-H1 bus supports
device on the FF-H1 bus (execution of software download.
software download). If the software
revision is not specified for the device in
the project database, no download will
be performed. If the software revision
cannot be conformed to the device in the
project database, the equalization
processing of the applicable device will
stop. After replacing the software,
execute equalization work again.
If a device on the The software revision of a device in the
FF-H1 bus is project database is changed.
selected
Block structure If a device in the Block instantiation is executed for a Block instantiation can be
project database is device on the FF-H1 bus based on the executed only if a device on
selected block structure of a device in the project the FF-H1 bus supports block
database. If the block structure cannot instantiation.
be conformed to the device in the project
database, the equalization processing of
the applicable device will stop. After
changing the block structure, execute
equalization work again.
If a device on the The block structure of a device in the The change of the block
FF-H1 bus is project database is changed. Capabilities structure can be executed only
selected file/DD file update is executed based on if a device in the project
the block information acquired from a database supports block
device on the FF-H1 bus. instantiation.
Block parameter If a device in the It is reflected on the block parameter
value project database is values of a device on the FF-H1 bus.
selected
If a device on the It is reflected on the block parameter
FF-H1 bus is values of a device in the project
selected database.
D050313E.ai

The following shows the content of equalization processing of device information.
Table Equalization Processing of Device Information
Information
Equalization processing Remark
to be compared
MANUFAC_ID If a device in the Not selectable
project database is
selected
If a device on the “Capabilities file/DD file update” is
FF-H1 bus is selected executed for a device in the project
database. The capabilities file to be
selected is a file that supports DEV_REV
of a device on the FF-H1 bus. However,
if there is no such file, equalization
processing will stop.
DEV_TYPE If a device in the Not selectable This may be solved by
project database is equalizing the software
selected revision. After equalizing the
If a device on the software revision in Device
“Capabilities file/DD file update” is
FF-H1 bus is selected executed for a device in the project Panel, check it again.
DEV_REV If a device in the Not selectable This may be solved by
project database is equalizing the software
selected revision. After equalizing the
If a device on the software revision in Device
“Capabilities file/DD file update” is
FF-H1 bus is selected executed for a device in the project Panel, check it again.
Device tag name If a device in the Tag assignment/address assignment for The setting of the VCR (virtual
project database is a device on the FF-H1 bus is executed. communication route) for the
selected application is performed after
If a device on the assignment, and no problem
The device tag name of a device in the
FF-H1 bus is selected project database is changed. will occur in the subsequent
equalization.
Node address If a device in the The address assignment for a device on
project database is the FF-H1 bus is executed.
selected
If a device on the The node address of a device in the
FF-H1 bus is selected project database is changed.
Device class If a device in the The device class is changed. The device Wait until the device starts up.
project database is is restarted.
selected
If a device on the The device class is changed.
FF-H1 bus is selected
Device ID If a device in the Not selectable
project database is
selected
If a device on the The device ID of a device in the project
FF-H1 bus is selected database is changed.
D050314E.ai

n Operation of Equalization
l Calling the Device Information Display Dialog Box

▼ Device Information Display Dialog Box
To call the Device Information Display dialog box, perform the following procedure:
1. Select a device on the FF-H1 bus used to detect the difference in the device status display
area. Multiple devices can be selected.
2. Click the right button, and select [Display Device Info] from the pop-up menu that appears.
The Device Information Display dialog box is displayed. Association between the devices
in the project database and the devices on the FF-H1 bus will be automatically made using
device tag names as search keys.
If the device contains the intact block parameter items (that have never obtained parameter
values from the physical fieldbus device), a dialog box will be displayed to prompt for updating
the block parameters. Clicking [OK] button on the dialog box, all the block parameters will be
uploaded from the physical fieldbus device so as the parameters values on the project database
will be updated. Clicking [NO] button on the dialog box, the parameters will not be updated.
TIP
If multiple fieldbus devices are selected on the device information dialog box, only the first fieldbus device will be
prompted for updating the block parameters. For other devices, the block parameter updating can be performed
by selecting them separately on the device information dialog box. For the fieldbus device that does not contain
any intact parameter item, the parameter updating will not be prompted.
Device Information Display:YVP_01
Equalization Mode Editing Mode
YVP_01 Device Block parameter Property

YVP_02
Update Time : 2008/3/31 20:24:14
Solution Item Devices in Project database Devices on FF-H1 bus
Device ID 5945430007PP2YVP15 5945430007PP
MANUFAC_ID 0x594543 (Yokogawa Electric) 0x594543 (Yokogo

DEV_TYPE 0x0007 (YVP (Software Download) ) 0x0007 (YVP (Sof
DEV_REV 0x01 0x01
Software Revision R101 R101
Device Tag Name YVP_01 YVP_01
Node Address 0xF2 0xF2
Block Structure RESOURCE 01 (0x0133, 0x0101, 1000) RESOURCE 01 (0
TRANSDUCER 01 (0x8001, 0x0001, 2000) TRANSDUCER 01
AO 01(0x0102, 0x0001, 5000) AO 01(0x0102, 0x
DI 01(0x0103, 0x0001, 6000) DI 01(0x0103, 0x0
DI 02(0x0103, 0x0001, 6100) DI 02(0x0103, 0x0
PID 01(0x0108, 0x0001, 8000) PID 01(0x0108, 0x
OS 01(0x011C, 0x0001, 14000) OS 01(0x011C, 0x
Device Class BASIC BASIC
Back to default Difference All Update
The equalization of the block parameter is executed. Equalization Cancel
D050315E.ai
Figure Device Information Display Dialog Box

The Device Information Display dialog box has the following three tabs:
• Device tab
This displays the device information.
• Block Parameter tab
This displays the block parameter values.
• Property tab
This displays the properties of devices and blocks.
The following shows the buttons commonly used in the Device Information Display dialog box.
• [Equalization Mode] button
This mode allows executing equalization. The [Equalization] button is enabled.
• [Editing Mode] button
This mode allows editing the device information and parameter values of a device on the
FF-H1 bus. The Editing mode is the default mode.
• [The equalization of the block parameter is executed.] check box
It will equalize the block parameter values. The check box is checked (ON) by default.
• [Equalization] button
It executes equalization. This is valid only when in the Equalization mode.
• [Cancel] button
It stops the work, and closes the dialog box.
TIP
The following two operating procedures can also be used to call the Device Information Display dialog box:
• Select a device on the FF-H1 bus in the device status display area, and drag and drop it onto a device in
the project database in the project/plant configuration display area. Association will be made between the
device in the project database and the device on the FF-H1 bus.
MYPJT
Device Tag : YVP_01
FCS0102
242 Device ID : 5945430007PP2YVP15
FCS0103 Device Class : BASIC
NODE1 1ALF111-1 YVP_01 Update Time : 2008/03/31 14:41:22
1ALF111 2008/03/31 14:41:22
1ALF111-1
Device Tag : YVP_02
YVP_01(242
Device ID : 5945430007J0000390
YVP_02(245 245
YVP_02 Update Time : 2008/03/31 15:26:18
1ALF111-2 2008/03/31 15:26:18
1ALF111-3
1ALF111-4
D050316E.ai
Figure Calling the Device Information Display Dialog Box by Drag and Drop
• Double-click a device on the FF-H1 bus in the device status display area. Association will be made between
a device in the project database and a device on the FF-H1 bus automatically using the device tag name as
the search key. If the same device tag name as that of the device on the FF-H1 bus does not exist on the
device in the project database, the dialog box cannot be called.

l Displaying Differences
The information of the Fieldbus device acquired when recognizing the device and the information
of a device in the project database are compared. The difference information is displayed in the
Device Information Display dialog box. If the Device Information Display dialog box was called
by selecting multiple devices, a device list is displayed in the list view. To display the difference
information corresponding to a specific device, select that device in the list view.
List View

YVP_02
Update Time : 2008/3/31 20:24:14

DEV_REV 0x01 0x01
AO 01(0x0102, 0x0001, 5000) AO 01(0x0102, 0x
DI 01(0x0103, 0x0001, 6000) DI 01(0x0103, 0x0
DI 02(0x0103, 0x0001, 6100) DI 02(0x0103, 0x0
PID 01(0x0108, 0x0001, 8000) PID 01(0x0108, 0x
OS 01(0x011C, 0x0001, 14000) OS 01(0x011C, 0x
D050317E.ai
Figure Displaying Differences
l Equalization of Individual Devices

The operation of equalizing a device is as follows:
1. Check the update time in the Device Information Display dialog box regarding the
differences. If the saved difference information is being displayed, it may not be the latest
difference information; click the [Update] button on each tab. The difference information
and update time are updated. In the case of the Block Parameter tab, the tab is divided by
category. The difference information can be updated for each tab.
To stop updating, press the [Stop] button in the dialog box that appears during an update
operation. The difference information and update time are not updated.
2. Click the [Equalization Mode] button.
The [Equalization] button is enabled. Since the Editing mode is set by default, equalization
cannot be performed without switching the mode.
3. Turn on the radio button of the value to be used as the master during equalization
processing.
The value selected is underlined.

4. Check the check box of the difference information with which equalization processing will
be performed in the solution items on the Device tab. All the check boxes are checked
by default. Specify the items sequentially from the top. The following table shows the
relationships among MANUFAC_ID, DEV_TYPE, DEV_REV and software revision.
Table Relationships Among MANUFAC_ID, DEV_TYPE, DEV_REV and Software Revision
Solution item Relationship with other solution item
MANUFAC_ID The DEV_TYPE, DEV_REV and software revision are selected at
the same time. The selections of these items cannot be changed.
DEV_TYPE The DEV_REV and software revision are selected at the same
time. The selections of these items cannot be changed.
DEV_REV The software revision is selected at the same time. The selection
of this item cannot be changed.
Software Revision There is no influence to other items.
D050318E.ai
5. Specify whether or not to use the block parameter values in equalization processing. The
[The equalization of the block parameter is executed.] check box is checked by default. If
this check box is unchecked, the processing after the equalization of the block parameter
values will not be performed. As a result, equalization will be incomplete.
6. Click the [Equalization] button.
A confirmation dialog box appears.
7. Click the [OK] button in the confirmation dialog box.
The Equalizing Devices dialog box appears.
Equalization Execute
Execute for the following devices
YVP_01
YVP_02
OK Cancel
D050319E.ai
Figure Equalizing Devices Dialog Box

8. Select the device to be equalized in the Equalizing Devices dialog box. The check box of the
device selected is checked by default. After selecting the device, click the [OK] button.
The Equalization Execute dialog box appears.
Equalization Execute
Equalization proccess of YVP_01

Equalization proccess of MANUFACID
Equalization proccess of DEV_TYPE
Equalization proccess of DEV_REV
Equalization proccess of Software Rev
Equalization proccess of Device Tag
Equalization proccess of Node Address
Equalization proccess of Device Class
Proccess of Generation
Proccess of Download to Device
Finish Execute Stop

Result
message
D050320E.ai
Figure Equalization Execute Dialog Box

9. The contents for equalization will be displayed in the Equalization Execute dialog box.
The equalization of the device ID, generation, and download to the device are executed
regardless of whether or not the difference of the device information exists. The following
contents will be displayed in the Equalization Execute dialog box.
Table Contents of Equalization Processing
Step Item to be equalized Processing Remark
1 MANUFAC_ID To equalize this item according to the device on the FF-H1 bus, To match this item with
the capabilities file/DD file will be updated. To equalize this item a device on the FF-H1
according to the device in the project database, equalization bus, execute steps 2
cannot be performed (the device on the FF-H1 bus needs to be and 3 at the same time.
changed).
2 DEV_TYPE To equalize this item according to the device on the FF-H1 bus, To match this item with
the capabilities file/DD file will be updated. To equalize this item a device on the FF-H1
according to the device in the project database, the bus, execute step 3 at
DEV_TYPE may be changed due to software downloading. the same time.
Proceed to step 4, “Software revision.” If software downloading
is not supported, equalization cannot be performed (the device
on the FF-H1 bus needs to be changed).
3 DEV_REV To equalize this item according to the device on the FF-H1 bus,
the capabilities file/DD file will be updated. To equalize this item
according to the device in the project database, the DEV_REV
may be changed due to software downloading. Proceed to step
4, “Software revision.” If software downloading is not
supported, equalization cannot be performed (the device on
the FF-H1 bus needs to be changed).
4 Software revision The software revision is matched. Software download is Since the device is
executed. When software download is executed, equalization recognized again after
processing is stopped temporarily. After the device is starting with new
recognized again, execute equalization processing again. software, execute
equalization processing
subsequently.
5 Device tag name The device tag name is matched. If a device on the FF-H1 bus
has been changed, the following processing is executed.
• Address assignment (using the address of a device on the
FF-H1 bus)
• VCR download (setting application VCR)
6 Node address The node address is matched. If a device on the FF-H1 bus If a difference has been
has been changed, VCR download (setting of application VCR) detected at the same
is executed. time with step 5, only
step 5 is executed.
7 Block structure The block structure is matched with a device in the project If device does not
database. Block instantiation is executed. If the device does support block
not support block instantiation, equalization processing is instantiation, either
stopped. step 3 or 4 is
implemented.
8 Device class The device class is matched. If a device on the FF-H1 bus has
been changed, the device is restarted. After the device is
restarted, resume equalization processing.
9 Block tag name The block tag name is matched.
10 Block parameter value The block parameter values are matched.
11 Device ID The device ID is matched.
12 Execution of Generation is executed for the target segment, and the loading
generation the difference to the FCS and the ALF111 and equalization to
the HIS are executed.
13 Execution of The initial download is executed. This initial download
download to device excludes the handling of the block parameters.
D050321E.ai

10. Click the [Execute] button in the Equalization Execute dialog box.
Equalization processing starts. The progress bar indicating the progress status of
equalization is displayed in the Equalization Execute dialog box.
To stop the work before executing equalization processing, click the [Stop] button, and then
close the Equalization Execute dialog box. To stop the work while executing equalization
processing, click the [Stop] button. After the processing currently in execution is completed,
equalization processing is suspended.
To resume the suspended processing, click the [Execute] button again. Errors generated
during the execution of equalization processing and the processing status are displayed in
the message display area. A check mark is displayed for processing executed successfully.
11. When all of equalization processing is completed, the [Finish] button is enabled. Click the
[Finish] button, and then close the Equalization Execute dialog box.
The device information is updated at this time. When update is completed, the device
information after equalization is displayed in the Device Information Display dialog box.
TIP
• To execute only the equalization processing that caused an error, click the [Execute] button again.
• To display errors generated while executing equalization processing, click the [Result] button.
l Equalization for Device Requiring Software Download

There are three classes of Fieldbus devices that support the software download function, and the
operation of equalization varies depending on the class. The following describes the classes of
Fieldbus devices that support the software download function.
• Class 1: Software download can be executed without stopping control.
• Class 2: Each block becomes O/S (Out of Service) when executing the software download.
• Class 3: A Fieldbus device is restarted when executing software download.
The following describes the equalization operation for devices that require software download.
1. After the equalization of a device that does not require software download is performed,
software download is executed for the target device in batch mode.
The Device Settings dialog box appears.
2. Click the [Download] button in the Device Settings dialog box. Software download is
executed.
3. When downloading to a fieldbus device of Class 1 after changing its software, the activation
needs to be performed. (Thus the downloaded software will replace the existing software.)
The device will be then recognized again.
The activation is not required for devices of Class 2 and Class 3. The device is automatically
recognized again.
For any class, execute equalization processing again.
SEE
ALSO For more information about the Device Settings dialog box and the software download function, see the following:

D5.4 Advanced Operations

This section describes the advanced operations among Device Panel operations.
n Advanced Operations
The following describes the advanced operations of Device Panel.
• Editing device information
Edit the device information of devices on the FF-H1 bus.
• Displaying block parameter values
Display the parameter values of the blocks built in a device in the project database added by
offline engineering and to a device on the FF-H1 bus.
• Adjusting the block parameter values
Change the block parameter values of a device on the FF-H1 bus.
• Displaying detailed device information
Display the detailed information of devices.
• Replacing devices
Replace devices on the FF-H1 bus. Change software.
• Communication function
Execute the communication function for devices.
SEE
ALSO For more information about each of the operations described above, see the following:
D5.4.1, “Editing Device Information”
D5.4.2, “Displaying Block Parameter Values”
D5.4.3, “Adjusting Block Parameter Values”
D5.4.4, “Displaying Detailed Device Information”
D5.4.5, “Replacing Devices”
D5.4.6, “Communication”

D5.4.1 Editing Device Information

This section describes the operation for editing device information. The editing of device
information is performed on the Device tab in the Device Information Display dialog box.
SEE
ALSO For the procedure to display the Device Information Display dialog box, see the following:
“l Calling the Device Information Display Dialog Box” in “n Operation of Equalization” in D5.3.5,
“Equalization”
n Configuration of Device Tab

The following shows the configuration of the Device tab in the Device Information Display dialog
box.

YVP_02
Update Time : 2008/3/31 20:24:14

DEV_REV 0x01 0x01
AO 01(0x0102, 0x0001, 5000) AO 01(0x0102, 0x
DI 01(0x0103, 0x0001, 6000) DI 01(0x0103, 0x0
DI 02(0x0103, 0x0001, 6100) DI 02(0x0103, 0x0
PID 01(0x0108, 0x0001, 8000) PID 01(0x0108, 0x
OS 01(0x011C, 0x0001, 14000) OS 01(0x011C, 0x
D050401E.ai
Figure Device Tab
The following describes each information and buttons displayed on the Device tab.
l Information Displayed
• Solution Item
Check the check box(es) of the item(s) to be equalized. All check boxes of items for which a
difference has been generated are checked by default.
• Devices in Project database
The device information of a device in the project database is displayed.
• Devices on FF-H1 bus
The device information of a device on the FF-H1 bus is displayed.

l Buttons Displayed
• [Back to default] button
This button returns each item of the Device tab to its default setting.
• [Difference] button
Only the items having a difference are displayed. If a device is selected again, all items will
be displayed again.
• [All] button
This button displays all items. All items are displayed by default.
• [Update] button
This button reacquires and then displays the information of devices on the FF-H1 bus being
displayed.
n Editing Device Information

There are four types of device information that can be edited: device tag name, node address,
software revision and block structure. The dialog box used to edit the device information varies
according to the device information to be edited. The following two types of dialog boxes are
used for editing.
• Editing the device tag name, node address and software revision
The Input dialog box is used for editing.
• Editing the block structure
The Instantiation Definition dialog box is used for editing.
l Editing the Device Tag Name, Node Address and Software Revision
Device information is edited according to the following procedure:
1. Call the Device Information Display dialog box, and select the Device tab.
2. Click [Editing Mode], and set the state that allows editing of device information. The
following lists the information that can be edited:
• Device tag name
• Node address
• Software revision (MANUFAC_ID, DEV_TYPE, DEV_REV)
3. Double-click the value of a device on the FF-H1 bus.
The Input dialog box appears.
Input Dialog
Device Tag Name

YVP_01
OK Cancel
D050402E.ai
Figure Input Dialog Box
4. After editing the device information in the Input dialog box, click the [OK] button.
The Editing Execute dialog box appears, and the edited device information is updated.
SEE
ALSO When changing the software revision, the software download function is started. For more information about the
software download operation, see the following:

l Editing the block structure
The block structure is edited according to the following procedure:
1. Call the Device Information Display dialog box, and select the Device tab.
2. Click [Editing Mode], and set the state that allows editing of the block structure.
3. Double-click the value of a device on the FF-H1 bus.
The Instantiation Definition dialog box appears.
Instantiation definition
Definition Name: Instantiation3
Level: 0x00000001
Type Number Max number (total 20 blocks)
Parmanent blocks:
Transducer x 2 block(s)
Display x 1 block(s)
Diagnostic Transducer x 1 block(s)
Instantiable blocks:
Analog Output x 1 block(s) 2 block(s)
PID Control x 1 block(s) 20 block(s)
Arithmetic x 1 block(s) 20 block(s)
Signal Characterizer x 0 block(s) 20 block(s)
Integrator x 0 block(s) 20 block(s)
Analog Alarm x 0 block(s) 20 block(s)
OK Cancel
D050403E.ai
Figure Instantiation Definition Dialog Box
4. Change the necessary information in the Instantiation Definition dialog box.

5. Click the [OK] button.
The Editing Execute dialog box appears, and the edited block structure is updated.
l Set Node Address during Tag Assignment

When performing tag assignment, the node address can be set as follows:
1. Call the device information dialog box and open the Device tab.
2. Click [Edit Mode] so as to edit the device information.
3. Double click a device tag name of a device on FF-H1 fieldbus, the tag assignment dialog
box can be opened.
SEE
ALSO For more information about setting node address during tag assignment, see the following:
“n Tag Assignment” in D5.4.6, “Communication”

D5.4.2 Displaying Block Parameter Values

This section describes the operation for displaying block parameter values. Block
parameter values are displayed on the Block Parameter tab in the Device Information
Display dialog box.
n Configuration of Block Parameter Tab

The following shows the configuration of the Block Parameter tab in the Device Information
Display dialog box.
RESOURCE BLOCK Basic Observation Basic Config Observation Other Config Other
RESOURCE_R01-01 Update Time : 2008/3/31 20:24:14

TRANSDUCER BLOCK Parameter Name. ElementName Devices in Project database Devices on FF-H1 bu
TRANSDUCER_T01-0 Block Tag Name TRANSDUCE T01-0 TRANSDUCE T0
FUNCTION BLOCK
ST_REV 0 0
(AO_01)
MODE_BLK. TARGET 0 0
(DI_01)
MODE_BLK. ACTUAL O/S 0
(DI_02)
MODE_BLK. PERMITTED 0 0
(PID_01)
MODE_BLK.NORMAL 0 0
(OS_01)
BLOCK_ERR 0 0
Update Tab
Set Equalization direction Back to default Set Display style Create Template Open Template Update
Block list display area Parameter display area

D050404E.ai
Figure Block Parameter Tab

The following shows each information and buttons to be displayed on the Block Parameter tab.
• Block list display area
A block list is displayed.
When the block parameters of the device in the project database and the physical device on
the FF-H1 fieldbus are discrepant, a mark will be displayed next to the block name and the
block type name to indicate that the discrepancies exist.
D050323E.ai
Figure The Mark to Indicate the Parameter Value Discrepancies
• Parameter display area

The contents in the parameter display area are divided into the following categories.
Moreover, if a category contains the discrepant block parameters, a mark will also be
displayed next to the name of the tab to indicate that the discrepancies exist.
- Basic Observation
- Basic Config
- Observation
- Other Config
- Other
The block parameter values of a device in the project database and a device on the FF-H1 bus
are displayed by category. The value to be used as the master during equalization is underlined.
The structure is displayed in the format of <parameter name>.<element name>.
As a reference, the manufacturer’s default values (parameter values set at shipping from the
factory) and the user’s default values (parameter values specified when a device is ordered) are
displayed.
If a device has not been equalized, or a device for which no association with a device in the
project database has not been made, only the parameter values of a device on the FF-H1 bus
are displayed.
l Buttons Displayed
• [Set Equalization direction] button
This button displays the Equalization Direction Settings dialog box. Specify the direction and
unit of equalization in the Equalization Direction Settings dialog box. If the manufacturer’s
default or the user’s default is selected, only the default parameters and elements will be
equalized.
Equalization direction settings
Direction
Devices in Project database
Devices on FF-H1 bus
Manufacturer Default
User Default
Unit
Device
Block
Tab
OK Cancel
D050405E.ai
Figure Equalization Direction Settings Dialog Box

• [Back to default] button
This button returns each item of the Block Parameter tab to its default setting.
• [Set Display Style] button
This button displays the Display Style Settings dialog box. In the Display Style Settings
dialog box, select the option for Show (all parameters, only parameters with differences)
to be displayed in the Device Information Display dialog box as well as the option for
Priority (Not specify: Display all parameters; Prefer Device in Project Database: Display the
parameters with the device in the project database as masters; and Prefer Device on FF-H1
Bus: Display the parameters with the device on the FF-H1 bus as masters). For example,
when [Difference] and [Prefer Device on FF-H1 Bus] are selected, the parameters displayed
in the parameter area are the parameters of differences based on the selected parameters
of the master devices on the FF-H1 bus. The contents set are held even if other device is
selected.
Display style settings
Show
All
Difference
Priority
Not Specify
Prefer Device in Project database
Prefer Device on FF-H1 bus
OK Cancel
D050406E.ai
Figure Display Style Settings Dialog Box
• [Create Template] button

This button can be used when creating template files.
After clicking this button, the template file can be saved in a specified location.
• [Open Template] button
This button can be used when opening template files.
After clicking this button, the template file can be opened, and then the block parameters will
be displayed on the Device Information dialog box.

• [Update] button
This button displays the Select Block dialog box. After the parameter values of the block
selected in the Select Block dialog box are reacquired, they are displayed in the Device
Information Display dialog box. At that time, the display content of a device in the project
database is also updated. Two or more blocks can be selected in the Select Block dialog
box. By default, only the currently selected block will be selected.
Select Block
RESOURCE BLOCK:
RESOURCE_R01-01 (RESOURCE_01)
TRANSDUCER BLOCK:
TRANSDUCE_T01-01 (TRANSDUCER_01)
FUNCTION BLOCK :
(AO_01)
(DI_01)
(DI_02)
(PID_01)
(OS_01)
Select All OK Cancel
D050407E.ai
Figure Select Block Dialog Box
• [Update Tab] button

The parameter values displayed on a tab are reacquired and then displayed. At that time,
the display content of a device in the project database is also updated.
n Displaying Block Parameter Values

The following describes the operation for displaying block parameter values.
1. Call the Device Information Display dialog box, and select the Block Parameter tab.
2. Select a block in the block list display area.
The parameter values of the block selected are displayed by category in the parameter
display area.

D5.4.3 Adjusting Block Parameter Values

The block parameter values to be displayed on the Block Parameter tab of the Device
Information Display dialog box in Device Panel can be adjusted if necessary. This section
describes the adjustment of block parameter values.
n Configuration of Block Parameter Tab

SEE
ALSO For more information about the configuration of the Block Parameter tab, see the following:
“n Configuration of Block Parameter Tab” in D5.4.2, “Displaying Block Parameter Values”
n Adjusting Block Parameter Values

Adjust block parameter values according to the following procedure:
1. Call the Device Information Display dialog box, and select the Block Parameter tab.
2. Select a block in the block list display area.
The parameter values of the block selected are displayed by category in the parameter
display area.
3. Click the [Editing Mode] button to set the state that allows editing of the block parameter
values of a device. The Editing mode is the default mode.
4. Double-click a block parameter value.
The Input dialog box appears.
Input field
Input Dialog
MODE_BLK.NORMAL
0
Reflect to project database
OK Cancel
D050408E.ai
Figure Input Dialog box

5. Enter a value in the input field.
When the input field is clicked, a combo box may be displayed depending on the block
parameter value. In such a case, select the applicable value from the list in the combo box.
If no applicable value is found, enter a value in the input field.
If the [Reflect to project database] check box is checked, the changed contents of
parameters are reflected in the project database.
If the [Reflect to project database] check box is unchecked, values are set only for devices
on the FF-H1 bus. The changed contents can be reflected in the project database at
equalization even if the check box is unchecked.
IMPORTANT
If the [Reflect to project database] check box is checked, off-line download (initial download
without block parameters) to a device is not executed. In other words, online adjustment can be
performed. However, to adjust block parameter values when performing equalization, off-line
download to a device is executed even if it is the equalization only for the block parameter values.
6. Click the [OK] button in the Input dialog box.

The Editing Execute dialog box appears, and the edited block parameter values are
updated.
TIP
If a parameter that cannot be written unless the block mode is set to O/S (Out of Service) is edited, a confirmation
dialog box appears. Clicking the [Yes] button in the confirmation dialog box sets block mode to O/S. If the [No]
button is clicked, editing is stopped. If the block mode has already been set to O/S, a confirmation dialog box is
not displayed.
Device Info Display Dialog
CHANNEL needs to make the mode of the block O/S.

Is it all right as for O/S?
Yes No
D050409E.ai

D5.4.4 Displaying Detailed Device Information

This section describes the operation for displaying the detailed information of devices on
the Property tab of the Device Information Display dialog box in Device Panel.
n Configuration of Property Tab

The following shows the configuration of the Property tab in the Device Information Display dialog
box.
Update Time : 2008/3/31 20:24:14

Item Value
Device Tag Name YVP_01
Software Download Function Supported

Block Instantiation Function Unsupported
MANUFAC_ID 0x594543 (Yokogawa Electric )
DEV_TYPE 0x0007 (YVP (Software Download) )
DEV_REV 0x01
DD_REV 0x01
Software Revision R101
Software Download Condition DWNLD_INCOMPLETE
Block List
Block Tag... Block Mode Block Label DD_Item Block Index Execution...
RESOURCE_D01_01 Resource_D1 0x00000459 1000 0
Update
D050410E.ai
Figure Property Tab
The following shows the information and buttons displayed in the Property tab.
Table Detailed Information of Devices
Display item Display content

Software Download Function Supported/Unsupported
Block Instantiation Function Supported/Unsupported
Device Information • MANUFAC_ID
• DEV_TYPE
• DEV_REV
• Software Revision
• Software Download Condition
Block List • Block Tag Name
• Block Mode (MODE_BLK.ACTUAL)
• Block Label
• Block header information
(DD_Item, Block_Index, Execution_Time, Profile,
Profile_Revision, Num_Of_Parms, Views_Index,
Number_View_3, Number_View4)
D050411E.ai
l Buttons Displayed
• [Update] button
The detailed information of the device being displayed is reacquired and then displayed.

n Displaying the Detailed Information of a Device

The detailed information of a device will be displayed on the Property tab. The detailed
information of a device can be displayed with the following procedure.
l Displaying the Detailed Information of a Device in the Project Database

Display the detailed information of a device in the project database according to the following
procedure:
1. Select a device in the project database for which detailed information is displayed in the
project/plant configuration display area in Device Panel.
2. Click the right button, and select [Property] from the pop-up menu that appears.
The Device Information Display dialog box appears while the Property tab is being selected.
In this case, the Device tab and the Block Parameter tab cannot be selected.
l Displaying the Detail Information of a Device on the FF-H1 bus

Display the detailed information of a device on the FF-H1 bus according to the following
procedure:
1. Double-click a device on the FF-H1 bus for which detailed information is displayed in the
device status display area in Device Panel.
The Device Information Display dialog box appears.
2. Select the Property tab.

D5.4.5 Replacing Devices

This section describes the procedure for replacing devices.
n Flow of Device Replacement

The following shows the procedure of device replacement using Device Panel.
Start
Prepare to
replace device
Replace device
Equalize
End
D050412E.ai
Figure Flow of Device Replacement
n Preparing to Replace a Device

To replace a device, it is necessary to place a Fieldbus device in the decommission status. In
order to place a Fieldbus device in the decommission status, select the target device on the FF-
H1 bus in the device status display area, and select [Decommission] from the pop-up menu that
appears when the right button is clicked.
A tag mark indicating the decommission status is displayed on the device of the bus as an
auxiliary mark. The tag clear operation can be executed on devices on the FF-H1 bus that are
placed in this status.
SEE
ALSO For more information about the decommission status, see the following:
“l Connection Status of the CENTUM VP System and Fieldbus Devices” in “n Device Status Display” in
D5.3.3, “Device Recognition and Status Display”

n Replacing Devices
To replace with the same device, a device with different DEV_REV or a device made by other
manufacturer, perform the following procedure:
1. Remove a Fieldbus device in the decommission status from a segment on the field side.
2. Connect a new Fieldbus device to a segment on the field side.
The Fieldbus device is automatically recognized, and the device information is displayed in
the device status display area in Device Panel.
3. Execute the equalization of the replaced device in Device Panel.
n Changing Software
Software can be changed by the following two operations:
• If software change is performed in the Device Information Display dialog box
• If software change is performed directly in Device Panel
SEE
ALSO To change software, Fieldbus devices must support the software download function. For more information about
the software download operation, see the following:
l If Software Change Is Performed in the Device Information Display Dialog Box

To change software, perform the following procedure:
1. Double-click a device on the FF-H1 bus in the decommission status.
The Device Information Display dialog box appears.
2. Double-click the value of the software revision of a device on the FF-H1 bus on the Device
tab of the Device Information Display dialog box.
3. Click the [Option] button in the Device Settings dialog box.
The Option dialog box appears.
Specify [ACTIVATE is executed in each device] in the Option dialog box, and click the [OK]
button.
The Option dialog box is closed, returning to the Device Settings dialog box.
4. Select a Fieldbus device to which software download is executed in the Device Settings
dialog box, and then click the [Download] button.
Software files are downloaded.
5. When the download operation is completed, close the Device Information Display dialog
box.
The Fieldbus device will be recognized again in Device Panel. The device information is
displayed in the device status display area.
6. Perform the equalization of the Fieldbus device that was recognized again. Equalization
processing is described as follows:
• Difference detection
• Capabilities file/DD file update (This is executed due to the difference of
DEV_TYPE or DEV_REV.)
• Block instantiation (This is executed as necessary.)
• Difference load (This downloads the difference when updating the capabilities file/
DD file to a device, ALF111 and FCS.)

l If Software Change Is Performed Directly in Device Panel
To change software, perform the following procedure:
1. Select a device on the FF-H1 bus in the device status display area, and select [Software
Download] from the Communication menu. Or, select [Software Download] from the pop-up
menu that appears when the right button is clicked.
2. Select a device, and click the [Download] button.
Software files are downloaded.
3. When the download operation is completed, close the Device Information Display dialog
box.
The Fieldbus device will be recognized again in Device Panel. The device information is
displayed in the device status display area.
4. Perform the equalization of the device that was recognized again.

D5.4.6 Communication
This section describes the functions provided on the Communication menu of Device
Panel. The functions provided in the Communication menu are as follows:
• Master data download
• Tag assignment
• Address assignment
• Tag clear
• Address clear
• Device class setting
• Device restart
The [Reassignment] on the [Tools] menu is explained as follows:
SEE
ALSO • For more information about software download, see the following:
n Master Data Download

When a Fieldbus device is selected in the device status display area, and then [Master Data
Download] is selected from the Communication menu, master data download will be executed on
the Fieldbus device.
n Tag Assignment
In the area for displaying device status, choose a fieldbus device and then click [Tag Assignment]
from [Communication] menu, a dialog box for setting device tag name and node address will
be displayed. It is necessary to enter the device tag name and the node address on this dialog
box. However, if the [Automatic Assignment] option box is checked, the address is assigned
automatically. This option is checked as default for the devices that the engineering is not
completed. Thus, the node address and the device tag name for the fieldbus device can be
automatically defined by clicking [OK] button.
TIP
If the node address is entered while the option of [Automatic Assignment] is checked, the option of [Automatic
Assignment] will have higher preference. If all the addresses are occupied, an error will occur to indicate that no
address is available within the range of polling address.
n Reassign Node Address

When [Reassignment] on the [Tools] menu is selected, a dialog box for reassigning the node
address of the device will be displayed. On the dialog box, the fieldbus devices for reassigning
node addresses can be selected. By default, the fieldbus devices that are not completely
configured are automatically selected. After clicking the [OK] button, the selected devices will be
reassigned sequentially with node addresses.

n Address Assignment
In the area for displaying the device status, choose a fieldbus device that already assigned with
a device tag name, and then click [Address Assignment] on the [Communication] menu. A dialog
box for setting node address will be displayed. Enter a node address to this dialog box. The node
address can be automatically assigned by checking the option of [Automatic Assignment]. If the
device is not assigned with a device tag name, the node address cannot be assigned. So that, it
is necessary to assign the device tag name first.
n Tag Clear
When a Fieldbus device in the decommission status is selected in the device status display area,
and then [Tag clear] is selected from the Communication menu, the content set in the device tag
name of the Fieldbus device will be erased.
n Address Clear
When a Fieldbus device in the decommission status is selected in the device status display
area, and [Address clear] is selected from the Communication menu, the content set in the node
address of the Fieldbus device will be erased.
n Device Class Setting

When a Fieldbus device is selected in the device status display area, and then [Set Device Class]
is selected from the Communication menu, a dialog box for setting the device class appears.
Select the device class of [BASIC] or [LINKMASTER] from the menu in the dialog box, and then
click the [OK] button. The device class is set in the Fieldbus device.
n Device Restart
Select the Fieldbus device in the device status display area, and select [Device Restart] from
the Communication menu. A confirmation dialog box appears. Click the [OK] button in the
confirmation dialog box. The selected Fieldbus device will be restarted.
IMPORTANT
• To restart a Fieldbus device after the device class has been set, wait for a while (20 to 40
seconds) after setting the device class, and then execute. This wait time varies depending
on the Fieldbus device; for Yokogawa Fieldbus devices, it is approximately 30 seconds.
• It takes time to restart Fieldbus devices. An alarm, such as IOP/OOP, occurs from the FF
faceplate block during that time.
• Since Fieldbus device is immediately restarted by a restart instruction to the Fieldbus
device, a communication error occurs for data setting, displaying an error message. Be
sure to update the device information after setting the device class and restarting a Fieldbus
device, and verify the result.
• When the restart of a Fieldbus device after setting the device class is complete, execute
master data download to the Fieldbus device. However, if the initial download is required
due to an error occurred at the initial download, execute the initial download from Fieldbus
Builder.

D5.4.7 Registering New Device on Device Panel

A new FF-H1 device can be recognized and registered to the project database on Device
Panel. When the fieldbus builder is started for registering the device, a dialog box will be
displayed to prompt for closing the fieldbus builder.
n Procedure of Registering New Device on Device Panel

Device Panel
Project Edit View Tool Communication Option Window Help
MYPJT
FCS1601 247 Device TagName:FI1001

Device ID:
1ALF111-1
Device Class:
1ALF111-2
246 Device TagName:TI1001
FCS1602
Device ID:
1ALF111-1
FCS1603 Device Class:

1ALF11
245 Device TagName:CV1001
FI1001 Device ID:
block 1 Device Class:
block 2
TI1001
46
D050413E.ai
Figure Registering New Device on Device Panel
1. Drag the new device on the connected segment. (In the above example, drag the device
with node address of 245 ).
2. Drop the device to the port name of the segment displayed in the Project/Plant tree view.
3. A dialog box for confirmation will be displayed.
4. Click the [OK] button on the dialog box. The device will be processed for registering in the
project database. This process is the same process of “Add device” on the fieldbus builder.
If the appropriate template files are available for the newly registered device, the dialog box
for selecting the template files will be displayed. The template file can be selected for the
new device.
TIP
When adding a new fieldbus device to a project and the node address is already occupied by an existing fieldbus
device, a dialog box will be displayed to prompt a different node address. Clicking [OK] button, the added fieldbus
device will be applied with the prompted node address.

IMPORTANT
• When registering a new device on Device Panel, the block parameters cannot be
downloaded to the device. The equalization on Device Panel or the initial downloading on
fieldbus builder needs to be performed.
• If an identical device tag name exists in the same project, the device cannot be registered.
The device should be registered after the device tag name is changed.

D5.4.8 Create or Open Template File on Device Panel

How to create or open the template files on Device Panel will be explained as follows.
n Procedure of Creating Template File on Device Panel

▼ Create Template
A template file can be created on Device Panel.
The procedure of creating the template files on Device Panel is as follows.
+ TRANSDUCER B Update Time:3/4/2008 22:09:11 PM
- FUNCTION BLOC
(AI_01)
ST_REV 120 0 (No

BLOCK_ERP 0 0 (No
PV.VALUE 0 0 (No
OUT.VALUE 3 3 (No
Update Tab
Set Equalization direction Back to default Set Display Style Create Template Open Template Update
User default value

D050414E.ai
Figure Creating Template File on Device Information Display Dialog Box of Device Panel
1. Open the Device Information Display dialog box.

2. Choose [Block Parameter] tab and open it.
3. Set the user default values. Double click a blank in User default column, a dialog box for
entering the user specified values would be displayed.
4. Check the option of [It is a user default value].
5. Enter the user specified default values. The values can be chosen from the list in the combo
box.
6. Set equalization directions.
7. Click [Create Template] button. A dialog box for creating template would be displayed.
8. On the dialog box for creating the template file, enter the file name and comment.
9. On the dialog box for creating the default template file, check the option of [This template file
is the default].
10. Click [OK] button.
SEE
ALSO For more information about template, see the following:

n Create Template File Dialog Box

After clicking the [Create Template] button, the Create Template File dialog box will be
displayed. On this dialog box, the file name and comment for the template file need to be
entered. Moreover, the template file can also be specified as the default template.
Create Template File
Template File 594543_0004_01_ 01 .xml

Name
Comment transmitter
This template file is the default.
Save Cancel
D050415E.ai
Figure Create Template File Dialog Box
l Template File Comment

A comment text with up to 48 alphanumeric characters or 24 double-byte characters can be
entered.

The format of the template file name is as follows:
<MANUFAC_ID>_<DEV_TYPE>_<DEV_REV>_<***>.XML
Where the *** stands for a user-defined string contains up to 8 alphanumeric characters. If this
string is not specified by user, the file name will be automatically affixed with a number and the
file name becomes follows:
<MANUFAC_ID>_<DEV_TYPE>_<DEV_REV>_nn.XML
Where nn=01,02,03,04,05, and so on. This number nn will make the template file has a unique
file name from the existing files.
l Set the Template as Default Template File

A created template file can be set as the default template file.
On the Create Template File dialog box, checking the option of [This template file is the default],
the template file will be set as a default template file. In general, this option is checked.
IMPORTANT
When calling the Create Template File dialog box, if the option of [This template file is the default]
is not checked, there is a possibility that the template of the same type (with the same vendor ID,
device type and revision number) is set as the default template file.
Checking the option of [This template file is the default] will set the created template as the
default template file.

n Read Template File on Device Panel

▼ Open Template
The Device Panel will read the template file with the same vendor ID, device type and revision
number correspond to the selected device.
For opening a template file, a template file list will be displayed for selecting the required
template. A template file can be selected and then opened.
On Device Panel, the template settings will be applied to the project database after equalization.
l Action of Reading Template File on Device Panel

When Device Panel reads the template file, the user default values and equalization directions
set for the User default column of Device Information Display dialog box will be displayed on the
Device Information Display dialog box.
IMPORTANT
If the proper template file for the device with the same vendor ID, device type and revision
number (MANUFAC_ID, DEV_TYPE, DEV_REV) cannot be found in the folder for the template
files, the Device Panel will not able to read the template file.
l Procedure of Reading Template File on Device Panel

The procedure of reading the template files on Device Panel is as follows.
+ TRANSDUCER B Update Time:3/4/2008 22:09:11 PM
- FUNCTION BLOC
(AI_01)
ST_REV 120 0 (No

BLOCK_ERP 0 0 (No
PV.VALUE 0 0 (No
OUT.VALUE 3 3 (No
Update Tab
Set Equalization direction Back to default Set Display Style Create Template Open Template Update
User default value

D050416E.ai
Figure Reading Template File on Device Information Display Dialog Box of Device Panel
1. Open the Device Information Display dialog box.

2. Choose Block Parameters tab and open it.

3. Click [Open Template] button. The dialog box of Choose Template File will be displayed.
On this Choose Template File dialog box, only the template files correspond the device
are displayed in a list. The displayed template files are the template files correspond to the
device with the same vendor ID, device type and revision number.
If a template file has been used for handling the device before, this template file will be
selected on the Choose Template File dialog box. If no template file is appreciated for the
selected device, a message will be displayed to indicate that no appreciated template file in
the list.
Choose Template
594543 (Yokogawa Electric) Default Name Comment Date

- 0003 (EJA100A) 594543_0003_01_01.xml pressure 2008/03/01
+ 01 594543_0003_01_02.xml level 2008/03/03
OK Cancel
D050417E.ai
Figure Choose Template File Dialog Box
4. Select the required template file.

5. Checking and unchecking the option of template file name on the dialog box can change the
device’s default template file.
6. Click [OK] button. The template files will be accessed.
l Apply a Template after Changing Some of Settings

A template file can be applied after some of settings are changed when open the file on Device
Panel.
When a template file is opened on Device Information Display dialog box, some of the settings
can be changed according to the actual requirements. Then the changed template can be saved
as a new template file. This new template file can be applied.

Blank Page
TocE-1
CENTUM VP
CONTENTS
PART-E Variety Fieldbus Device Engineering
E1. Fieldbus Block Instantiation..................................................................E1-1
E1.1 Overview of Block Instantiation.....................................................................E1-2
E1.2 Engineering of Fieldbus Devices Supporting Block Instantiation.............E1-4
E1.2.1 Overview of Block Instantiation Engineering....................................E1-5
E1.2.2 Windows Related to Block Instantiation...........................................E1-7
E1.2.3 Defining Block Instantiation Information.........................................E1-11
E1.2.4 Executing Block Instantiation..........................................................E1-14
E1.2.5 Block Instantiation Definition at Fieldbus Device Maintenance......E1-15
E2. Software Download.................................................................................E2-1
E2.1 Overview of Software Download ...................................................................E2-2
E2.2 Functional Details of Software Download.....................................................E2-5
E2.3 Software Download Operation ....................................................................E2-11
E2.3.1 General Operation Flow . ...............................................................E2-12
E2.3.2 Device Settings Dialog Box and Communication Executing
Dialog Box . ....................................................................................E2-14
E2.3.3 Setting Up the Target Devices........................................................E2-21
E2.3.4 Downloading Software....................................................................E2-24
E2.3.5 Exporting/Importing the Information of the Target Devices for
Software Replacement ..................................................................E2-26
E2.3.6 Performing Reengineering..............................................................E2-27
E2.3.7 Downloading Software Controlled by License................................E2-28
E3. Devices of Multiple Levels......................................................................E3-1
E3.1 What is a Device of Multiple Levels?.............................................................E3-2
E3.2 Registering Devices of Multiple Levels.........................................................E3-3

Blank Page
<E1. Fieldbus Block Instantiation> E1-1
E1. Fieldbus Block Instantiation

This chapter explains each of the items to be engineered for Fieldbus devices that
have the mechanism of Fieldbus block instantiation (hereinafter referred to as block
instantiation).

E1.1 Overview of Block Instantiation

This section explains the following:
• Mechanism of block instantiation implemented in Fieldbus devices
• How to engineer Fieldbus devices connected to ALF111 that allow block instantiation
n What is Fieldbus Block Instantiation?

Fieldbus block instantiation is a mechanism that is used for assigning the functions of blocks
implemented in a Fieldbus device in advance to a specific Fieldbus device as entities. A Fieldbus
device has an area for defining block entities (instances) and definable block functions (classes).
Instantiation means creating instances of the blocks and assigning them to the Fieldbus device.
Instantiation is possible for function blocks and transducer blocks.
Instantiation
H1 Fieldbus
Device FBAP
Block class
AI1 AI (program)
AI2
PID
PID
1
Block instance (block entity)

E010101E.ai
Figure Block Instantiation
In the case of Fieldbus devices that do not allow block instantiation, the types and number of
blocks in a Fieldbus device have been defined and cannot be changed by the user. In the case
of Fieldbus devices that allow block instantiation, however, the user can define the number
of blocks for each block type according to the purpose within the range of blocks that can be
instantiated. This allows efficient use of Fieldbus devices.

n Mechanisms for Engineering Devices Supporting Block Instantiation

The following mechanisms are provided to engineer Fieldbus devices connected to ALF111 that
allow block instantiation:
• Definition of block instantiation
It is possible to define block instantiation for Fieldbus devices that allow block instantiation
according to the purpose.
• Execution of block instantiation
It is possible to instantiate function blocks of Fieldbus devices that allow block instantiation
via communication. Instantiation information is acquired from capability files.
• Creation of block instance information files for device registration
Fieldbus Builder creates block instance information, either obtained via communication or
specified by block instantiation definition, and saves it as a text file conforming to the FS1.7
capability file format. This file allows offline engineering of Fieldbus devices.
n Operating Environment (Block Instantiation)

• Hardware environment
The hardware environment must conform to the hardware requirements of CENTUM VP.
Used for the purpose of engineering Fieldbus devices supporting block instantiation.
• Software environment
The software environment must conform to the software requirements of CENTUM VP.

E1.2 Engineering of Fieldbus Devices

Supporting Block Instantiation
This section explains engineering tasks necessary when using Fieldbus devices
supporting block instantiation by connecting via ALF111.

E1.2.1 Overview of Block Instantiation Engineering

This section provides an overview of the engineering tasks involved in block instantiation
performed in Fieldbus Builder.
n Mechanisms Used in Engineering Tasks for Block Instantiation

Fieldbus Builder provides the following mechanisms in order to perform engineering tasks for
block instantiation.
l Selection of Fieldbus Device

This mechanism allows selecting a Fieldbus device for which block instantiation is to be
executed.
l Definition of Block Instantiation

This mechanism provides a dialog box for specifying which and how many blocks should be
instantiated for the selected Fieldbus block.
l Execution of Block Instantiation

This mechanism downloads the block instantiation definition to the Fieldbus device via
communication. It also acquires the block information after instantiation from the Fieldbus device
and stores it in a block instance information file.
l Block Instance Information File

Definition information of block instantiation for each Fieldbus device and information of blocks
acquired from Fieldbus devices are stored in block instance information files.
n Flow of Block Instantiation Engineering

Engineering tasks related to block instantiation can largely be classified into offline engineering,
which can be started without establishing a connection to a Fieldbus device, and online
engineering, which is performed upon establishing a connection to a Fieldbus device. In online
engineering, the user can select either manual registration or automatic registration for the
Fieldbus device in question.
l Procedure of Offline Engineering

Perform the following operations before obtaining a Fieldbus device:
1. Register the Fieldbus device manually in Fieldbus Builder.
2. The Manual Registration dialog box (The Capability File Selection dialog box) appears.
3. Select the capability file corresponding to the target Fieldbus device and define the
information necessary for block instantiation in the Capability File Selection dialog box.
Perform the following operations after obtaining the Fieldbus device:

4. Connect the Fieldbus device to a segment.
5. Open the Device Panel.
6. Update the display of the Device Panel.
7. Select the Fieldbus device for which the block instantiation is to be executed in the Device
Panel and execute the block instantiation.
8. Download the information from Fieldbus Builder.

l Procedure of Online Engineering (Manual Registration)
1. Perform manual device registration in Fieldbus Builder.
3. On the Capability File Selection dialog box, choose capability file for the corresponding
fieldbus device and configure the block instantiation settings.
7. Select the Fieldbus device for which the block instantiation is to be executed in the Device
Panel and execute the block instantiation.
l Procedure of Online Engineering (Automatic Registration)

2. Perform registration via [Device Recognition Registration] in Fieldbus Builder.
l Operations after Online Engineering (Automatic Registration)

1. Confirm that the blocks of the added Fieldbus device are correct in Fieldbus Builder.
Perform the following additional operations if the expected blocks do not exist.
2. Obtain the proper capability file.
3. Update the capability file/DD file in Fieldbus Builder.
4. The Updating Capabilities File/DD Files dialog box (The Capability File Selection dialog box)
appears.
5. In the Capability File Selection dialog box, select the Fieldbus device for which you want to
perform block instantiation and define the information necessary for block instantiation.
8. Select the Fieldbus device for which the block instantiation is to be executed from the
Device Panel and execute the block instantiation.

E1.2.2 Windows Related to Block Instantiation

This section explains the dialog boxes used in engineering tasks related to block
instantiation.
n Capability File Selection Dialog Box

Setting items for defining block instantiation are added in the Capability File Selection dialog box.
When a Fieldbus device supporting block instantiation is selected, the setting items for defining
block instantiation are displayed dynamically. The Capability File Selection dialog box is shown
below.
Device list display area Device information display area
Manual Registration
CFDDFILE Name Revision DEV_REV DD_REV Date

000302 (SMAR) Basic Positioner Transmitt 0x01 0x04 0x01 2003/08/12
0001 (LD302) Basic Positioner Transmitt 0x02 0x04 0x01 2003/06/20
0002 (TT302)
Basic Positioner Transmitt 0xFE 0x04 0x01 2003/08/13
0003 (IF302)
0004 (FP302) Basic Positioner Transmitt 0xFF 0x04 0x01 2003/07/25
0005 (FI302)
0006 (FY302)
OK Cancel
Definition Name: AI+PID+ARITH Add
Level: 0x00000001 Delete

Dynamically
added/displayed
Type Number Max number (total 20 blocks)
area (block
Parmanent blocks: instantiation
Transducer x 2 block(s) definition area)
Block instantiation definition Combo box displaying block instantiation

information display area definition names
E010201E.ai
Figure Capability File Selection Dialog Box (with Block Instantiation Definition Area)
TIP
Capability files of Fieldbus devices supporting block instantiation contain information related to block instantiation.
l Block Instantiation Definition Area

This area is dynamically added and displayed in the Capability File Selection dialog box if the
selected Fieldbus device supports block instantiation. This area is not displayed for Fieldbus
devices that do not support block instantiation.

l Definition Name
• Select a block instantiation definition in this field. The combo box lists all the block instance
information files that match with the selected Fieldbus device up to DEV_REV.
• This field is blank by default if this dialog box is opened by selecting [Add Device]. [Current]
is displayed by default if this dialog box is opened by selecting [Update Capabilities File/DD
File].
• Note that no block instantiation is performed for the Fieldbus device if you leave the field
blank and click the [OK] button.
l Level
This field displays the level of the capability file. Several levels are displayed separated by
commas if the level is set to Combinable Level.
l Block Instantiation Definition Information Display Area

This area displays the block instantiation definition information corresponding to the definition
name selected in the [Definition Name] combo box (the information cannot be selected or edited).
• Type, Number of blocks:
A list of block types for which block instantiation can be performed and the number of blocks
that are instantiated, are displayed.
• Maximum number:
The maximum number of blocks for each type of block that can be instantiated and the total
maximum number of blocks, are displayed.
• Permanent block:
Block types and the number of permanent blocks are displayed.
l Add
This button is used to open the Instantiation Definition dialog box, where you can edit the block
instantiation definition corresponding to the definition name selected in the [Definition Name]
combo box in this dialog box.
l Delete
This button is used to delete the block instantiation definition information corresponding to the
definition name selected in the [Definition Name] combo box. Note that the block instantiation
definition information displayed by default when updating a capability file/DD file cannot be
deleted.
l How to Call Up This Window

Select [Add Device] from the [Device Registration] menu of Fieldbus Builder. Alternatively, select
“Update Capabilities File/DD File” from the [Device Registration] menu.

n Instantiation Definition Dialog Box

This dialog box is used to define block instantiation. Click [OK] to register the block instantiation
definition with the information entered. A resource check is performed when you click OK. An
error is displayed and the definition information is not registered if the resource check fails. The
display on the Capability File Selection dialog box is updated and a block instance information file
is created if the resource check succeeds.
Definition Name: AI+PID+ARITH

Level: 0x00000001
Type Number Max number (total 20 blocks) Block instantiation definition

Parmanent blocks: information setting area
Transducer x 2 block(s)
Instantiable blocks:
Analog Output x 1 block(s) 2 block(s)
PID Control x 1 block(s) 20 block(s)
Arithmetic x 1 block(s) 20 block(s)
Signal Characterizer x 0 block(s) 20 block(s)
Integrator x 0 block(s) 20 block(s)
Analog Alarm x 0 block(s) 20 block(s)
OK Cancel
E010202E.ai
Figure Instantiation Definition Dialog Box
l Definition Name
The selected definition name is displayed by default, but you can enter a new definition name.
You can enter any definition name that specifies a valid block instantiation definition.
l Level
Select the level of the capability file. You can select multiple levels if the level is Combinable
Level.
l Block Instantiation Definition Information Setting Area

• Type:
Types of blocks that can be instantiated are listed.
• Number of blocks:
Set the number of blocks to be instantiated for each block type.
• Maximum number:
The maximum number of blocks for each type of block that can be instantiated and the total
maximum number of blocks, are displayed.
• Permanent block:
Block types and the number of permanent blocks are displayed.
l How to Call Up This Window

Click the [Add] button in the Capability File Selection dialog box.

n Device Panel
The block instantiation is executed for the actual Fieldbus device from the Device Panel.
l Block Instantiation Execution

Select [Block Instantiation] from the [Communication] menu to display a confirmation dialog box
before executing block instantiation. The definition information of block instantiation is displayed
in the confirmation dialog box. Click [OK] to execute or [Cancel] to cancel the execution. If you
click [OK], block instantiation is executed for the Fieldbus device with the information defined in
the block instance information file, and the information related block instantiation is acquired from
the Fieldbus device and stored in the block instance information file.
SEE
ALSO For the details about the Device Panel, see the following:
l How to Call Up the Device Panel

Select [Display Device Information...] from the [Tools] menu of Fieldbus Builder.

E1.2.3 Defining Block Instantiation Information

This section explains how to define block instantiation information.
• Operations to create a new Fieldbus device and define block instantiation
• Operations to select an existing Fieldbus device and define block instantiation
• Operations to change, add or delete block instantiation definition of an existing
Fieldbus device
• Operations to change the device revision of an existing Fieldbus device
n Defining Block Instantiation (New Fieldbus Device)

The following steps provide an overview of the operations involved in creating a new Fieldbus
device and defining block instantiation information.
1. Selecting a Fieldbus device and displaying block instantiation information
2. Defining block instantiation information
3. Registering the Fieldbus device
Each of the operations is explained in detail below.
l Selecting a Fieldbus Device and Displaying Block Instantiation Information

1. Select a segment in Fieldbus Builder and select [Add Device] from the [Device Registration]
menu.
Select the device type for which block instantiation is to be executed in the Capability File
Selection dialog box.
3. Select a Fieldbus device among those displayed by DEV_REV in the device information
display area.
4. The block instantiation definition area appears if the Fieldbus device supports block
instantiation.
5. The [Definition Name] field is blank by default.
6. You can select a definition name from the combo box if block instantiation has already been
defined for the selected device type.
l Defining Block Instantiation Information

7. Click the [Add] button in the block instantiation definition area.
8. Change the definition name and set the number of blocks for each block type to be
instantiated in the Instantiation Definition dialog box. Specify the level as well.
9. Click [OK]. An error is displayed if there is an error in the number of resources. In that case,
change the block instantiation definition and click [OK] again.
You can create multiple block instantiation information definitions for a Fieldbus device by
repeating steps 7 to 9.
10. Click [OK] in the Capability File Selection dialog box.

l Registering the Fieldbus Device
11. When the capability file is properly updated, the Device Registration dialog box appears.
12. Confirm the device tag name, node address and device class and change them if necessary
in the Device Registration dialog box.
13. Click the [OK] button in the Device Registration dialog box. The dialog box closes and the
registered information of the Fieldbus device is displayed in Fieldbus Builder.
14. Confirm the displayed information.
n Defining Block Instantiation (Existing Fieldbus Device)

This is a method for selecting a Fieldbus device and defining block instantiation. Change, add
and delete definition information and change the device revision according to the following
procedure.
l Selecting a Fieldbus Device and Displaying Block Instantiation Information

1. Select a Fieldbus device in Fieldbus Builder and select [Update Capabilities File/DD file]
from the [Device Registration] menu. The Updating Capabilities File/DD Files dialog box
(the Capability File Selection dialog box) appears.
2. Select a Fieldbus device among those displayed by DEV_REV in the device information
display area.
3. The block instantiation definition area appears if the Fieldbus device supports block
instantiation.
4. The definition of the selected Fieldbus device is displayed in the [Definition Name] field by
default.
5. You can select a definition name from the combo box if other block instantiation definitions
have already been made for the selected device type.
l Defining Block Instantiation Information

7. Change the definition name and set the number of blocks for each block type to be
instantiated in the Instantiation Definition dialog box. Specify the level as well.
You can create multiple block instantiation information definitions for a Fieldbus device by
repeating these steps.
l Operations to Delete Block Instantiation Definition

1. Open the Capability File Selection dialog box using the same procedure as for selecting an
existing Fieldbus device.
2. Select the definition name you want to delete in the block instantiation definition area and
click the [Delete] button.
3. The instantiation definition and the corresponding block instance information file are
deleted, and the display in the dialog box changes to the initial status where no definition
name is selected.

l Operations to Change Block Instantiation Information
2. Select the definition name of the block instantiation you want to modify from the [Definition
Name] combo box in the block instantiation definition area. Select [Current] if you want to
modify the currently used definition.
3. The information corresponding to the selected definition is displayed in the block
instantiation definition information display area.
5. The Instantiation Definition dialog box appears. Set the number of blocks for each block
type to be instantiated. Specify the level as well.
l Operations to Change Device Revision of Capability File

2. Select a capability file of a different device revision. The [Definition Name] combo box in
the block instantiation definition area becomes blank and the block instantiation definition
information display area is placed in the status where no definition is made.
3. In order to refer to a definition with an existing device revision, select [Use previous DEV_
REV definition]. The definition with the existing device revision is displayed and a resource
check is performed.
4. Click [OK] if the resource check is completed without errors. The device revision of the
capability file is changed.
5. An error is displayed if the defined number of resources is larger than the number allowed
in the new device revision or devices not allowed are defined. The device revision is not
changed if you click [OK] while an error is displayed.
6. Click the [Add] button in the block instantiation definition area if an error is displayed. The
Instantiation Definition dialog box appears.
7. Change the number of blocks for each type to a value within the limit and click the [OK]
button in the Instantiation Definition dialog box.
8. The display of the block instantiation definition area of the Capability File Selection dialog
box is updated if there are no errors; click the [OK] button. The device revision is changed.
9. The information of the updated Fieldbus device is displayed in Fieldbus Builder. Confirm the
updated information.

E1.2.4 Executing Block Instantiation

This section explains the operations involved in executing block instantiation for a
Fieldbus device connected to a segment.
n Executing Block Instantiation for a Fieldbus Device

Follow the procedure below to execute block instantiation for a Fieldbus device.
1. In Fieldbus Builder, select [Display Device Information] from the [Tools] menu. The Device
Panel appears.
2. Select [Update] from the [Tool] menu in the Device Panel. Information of all the Fieldbus
devices connected to a segment is displayed.
3. In the Device Panel, select a Fieldbus device for which you want to execute block
instantiation and select [Block Instantiation] from the [Communication] menu. Block
instantiation is executed for the selected Fieldbus device.
4. Perform [Download] in the [File] menu.

E1.2.5 Block Instantiation Definition at Fieldbus Device

Maintenance
This section explains how to perform block instantiation definition when maintaining
Fieldbus devices.
• Replacing with a Fieldbus device of the identical type
• Replacing with a Fieldbus device of a higher device revision
n Replacing with a Fieldbus Device of the Identical Type

Perform block instantiation according to the following procedure to replace an existing Fieldbus
device with a Fieldbus device whose type matches up to the device revision.
1. Set the device tag name and node address of the new Fieldbus device in advance.
2. Upload the block parameters before disconnecting the existing Fieldbus device from the
segment.
3. Connect the new Fieldbus device to the segment.
5. Select [Block Instantiation] from the [Communication] menu in the Device Panel to execute
block instantiation.
6. Select [Device Registration] and then [Device ID acquisition] in Fieldbus Builder, then select
[Offline Load to Device] - [Master Data Download].
SEE
ALSO For the procedure involved in replacing Fieldbus devices of the identical type, see the following:
“n Replacing with a Fieldbus Device of the Identical Type” in D2.4.4, “Replacing Fieldbus Devices”
n Replacing a Fieldbus Device with a Higher Device Revision

Perform block instantiation according to the following procedure to replace an existing Fieldbus
device for the purpose of upgrading the revision.
1. Set the device tag name and node address of the new Fieldbus device in advance.
2. Upload the block parameters before disconnecting the existing Fieldbus device from the
segment.
3. Connect the new Fieldbus device to the segment.
4. Select the replaced Fieldbus device in Fieldbus Builder and select [Update Capabilities
File/DD File] from the [Device Registration] menu. The Updating Capabilities File/DD Files
dialog box (the Capability File Selection dialog box) appears.
5. In the Capability File Selection dialog box, select the capability file for the device revision
corresponding to the new Fieldbus device and define block instantiation.
6. Select [File] - [Download] in Fieldbus Builder.
7. After the downloading succeeds, resolve any invalid elements in System View.
SEE
ALSO For the procedure involved in replacing Fieldbus devices for the purpose of upgrading the revision, see the
following:
“n Replacing with a Fieldbus Device of Different Device Revision” in D2.4.4, “Replacing Fieldbus Devices”

Blank Page
<E2. Software Download> E2-1
E2. Software Download

This chapter describes the function and operation of software download to Fieldbus
devices.

E2.1 Overview of Software Download

This section describes the functional structure of software download and flow of software
download operation.
n Functional Structure of Software Download

Software download is a function that downloads the software (all or part of firmware including
communication stacks) stored on an HIS or ENG equipped with the engineering function to the
Fieldbus devices via V net, FCS and H1 Fieldbus, thereby replacing the existing software with
the new downloaded version.
The functional structure of software download is illustrated below:
Engineering function
(System View/Device Panel)
Start
Software download function
Target device
configuration function
Device batch
registration function
Result reflection
function Internal memory
Communication Export/Import
Software files function
Forecast/progress
display function
Download
Work data
Data flow
Fieldbus device E020101E.ai
Figure Functional Structure of Software Download
l Target Device Configuration

This function sets the target device whose software will be replaced. You can add, delete or
change the device information of the target device. Device information can be set simultaneously
for a group of devices using the device batch registration function.
l Device Batch Registration

The Fieldbus devices requiring software replacement can be searched for using the search
function and the device information of the devices found can be obtained via the file interface, so
that these devices can be simultaneously set as the target devices for software replacement.

l Communication (Download)
Software is downloaded to the Fieldbus devices via the communication compliant to the FF-
H1 protocol. In case of KFCS2, FFCS, RFCS5, since independent communication function
can be performed for each segment, if the target devices belong to multiple segments, the
communication (download) will be performed for each segment independently. Download can be
performed in parallel to the target devices in the different segments.
l Result Reflection
The device information of each device whose software replacement has been completed is
notified to the engineering function (System View or Fieldbus Builder). This information is
required when performing reengineering.
l Export/Import
The device information of each target device for software replacement, and the information
regarding the result of download, can be exported and imported. Exporting means outputting
information externally, and the work session that was in progress at the time of export can be
continued by importing the exported information.
l Forecast/Progress Display Function

The time required for software download is calculated in advance and the estimated time is
displayed. Progress of download for the entire target devices is displayed in a single view.
Progress of download for each segment is also displayed.
n Flow of Software Download Operation

The flow of replacing the existing software on a Fieldbus device with the software of the new
revision is illustrated below:
Start
Store the new software

on the HIS/ENG
Specify the target devices

for software replacement
Safely stop the controls currently

executed by the target devices
Execute a software download

and ACTIVATE processing
Save the revision

upgrade history
Perform reengineering
End
E020102E.ai
Figure Flow of Software Download Operation

l Storing the New Software in the HIS/ENG
Store the new software files obtained from the device vendors on the HIS or ENG in which the
engineering function is installed. Store the files in the same folder as the DD files and capability
files.
l Setting the Target Devices for Software Replacement

Start the software download function and use the target device configuration function or device
batch registration function to set the target devices for software replacement.
l Safely Stopping the Controls Currently Being Executed by the Target Devices
Since software replacement requires the applicable Fieldbus devices to be reset, safely stop the
controls currently executed by the target devices or perform other necessary operation prior to a
software download.
l Executing a Software Download and ACTIVATE Processing

From the target devices for software replacement, select the devices to download the software to
and execute a software download and ACTIVATE processing (switching of the existing software
to the downloaded software).
If it is specified so that ACTIVATE processing will be executed for each target download device,
software download and ACTIVATE processing will be performed successively for each target
device. If it is specified so that ACTIVATE processing will be executed simultaneously for all
target software download devices in the applicable segment, the software download will be
performed to all target download devices in the segment first. When all downloads are complete,
a dialog box will be displayed to confirm if the operation is to be continued, where you can
choose to continue with ACTIVATE processing or perform it at a later date.
l Saving the Revision Upgrade History

If the software replacement was successful, the result reflection function will be activated and
the device information of the devices completing the software replacement will be notified to the
Fieldbus Builder of the engineering function. The HIS will also be notified of the software revision
upgrade in the applicable devices, if OPC server is applied to the Fieldbus system.
l Performing Reengineering
Use the engineering function to perform reengineering on the devices whose software was
replaced.

E2.2 Functional Details of Software Download

This section describes how to store software files on the HIS/ENG, as well as the
following functions of software download:
• Target device configuration
• Device batch registration
• Communication (download)
• Forecast/progress display
• Result reflection
• Export/import
n Storing Software Files

Store the new software files obtained from the Fieldbus device vendors in the folder in which the
DD files and capability files are stored.
SEE
ALSO For more information about the folder in which the DD files and capability files are stored, see the following:
The following shows an example of storing a software file:

MANUFAC_ID
DEV_TYPE
Capability file (.CFF)
DD file (.ffo)
DD file (.sym)
Software file (.ffd)
Folder
File
E020201E.ai
Figure Example of Storing a Software File
TIP
The new software you obtained may be controlled by a license regarding the number of target devices to which it
can be downloaded.
SEE
ALSO For storing software controlled by a license, see the following:
“n Storing Software Controlled by License” in E2.3.7, “Downloading Software Controlled by License”

n Target Device Configuration

Set the target devices requiring software replacement in the Device Settings dialog box.
Device Settings
Check License...
Device List Display Area
Add
Delete
Export
Pop-Up Menus
Import
Predicted Download Overall Progress

Time Display Area Display Area
Option... Register all devices Select all Show Progress Print file Update Download
Stop
Predicted Download Time:
1 Hours 35 minutes 47
E020202E.ai
Figure Device Settings Dialog Box
The Device Settings dialog box will be displayed when the software download function is started
in the System View or Device Panel.
The target devices for software replacement can be set individually or in a batch mode.
l Individual Configuration
The target devices on which to execute software replacement can be added, changed or deleted
in the Device Settings dialog box.
To add a target device, specify its segment information and individual device information. The
software file names will be automatically searched for and set.
When changing the details of a target device, all displayed information including the software file
names can be changed freely.
Deleting a target device means removing the selected device from the target of software
replacement. All device information of the selected device will be deleted. You cannot delete
(empty) any part of information.
l Batch Configuration
Use the search function to find the Fieldbus devices that require software replacement.
Obtain the device information for the devices found and set all these devices as the software
replacement target simultaneously. Use the batch configuration function when replacing the
software in devices that are connected to multiple segments requiring software replacement.

n Device Batch Registration

Device batch registration is a function used in the “batch setting” mode of target device
configuration.
The target devices requiring software replacement are searched for in the Search dialog box
called from the Device Settings dialog box. One or more of the following device information
can be specified as a search key or keys. Note that the device tag name is in the exclusive
relationship with other items.
• Device tag name
• MANUFAC_ID
• DEV_TYPE
• DEV_REV
When a condition is set for each specified search key and a search is executed, the search
results will be displayed in the Search dialog box. Verifying the search results and clicking the
[OK] button will set a group of target devices simultaneously based on the device information of
the devices listed as the search results.
Search
Device Tag TI1001

MANUFAC_ID
DEV_TYPE
DEV_REV
Software revision
Search
Search Results
Device tag NodeAddress MANUFAC_ID DEV_T
OK Cancel
E020203E.ai
Figure Search Dialog Box

n Communication (Download)
A desired number of devices can be selected from the list of target devices for software
replacement, in order to execute downloads to the selected devices. The download status will be
displayed in the Communication executing dialog box.
l Downloading to Multiple Segments

In case of KFCS2, FFCS, RFCS5, downloading to multiple segments can be executed
simultaneously. Downloads are executed separately for each of the segments, and the
Communication executing dialog box can be displayed for each segment to which the download
is currently in progress.
In case of KFCS, RFCS2, downloading to multiple segments can be executed sequentially.
l Downloading to Multiple Devices

If a download is executed with multiple devices selected, the processing will continue until
downloading to all selected devices is complete. If a download to a device has failed, the
download to that device is cancelled and the download to the next device will be started.
l Canceling a Download
The download in progress can be cancelled in a safe timing. Issue a download cancellation
command from the Device Settings dialog box or Communication executing dialog box. The
download can be cancelled in one of the following two ways:
• Cancel the download upon completion of processing on the device to which the download is
currently in progress
• Cancel the download immediately
l Downloading Multiple Files

If there are multiple software files to be downloaded to one Fieldbus device, all files will be
downloaded. If the download of any one file has failed, the download of all files is considered
failed.

l Software Download Options
The following four items can be specified as the software download options:
You can specify whether or not to perform a download when the revision of the downloading
software is the same as or lower than the revision of the existing software in the applicable
Fieldbus devices. The default is “Do not download” when the revision of the downloading
software is the same as the existing software, and “Download” when the revision of the
downloading software is lower.
• ACTIVATE processing
You can specify whether to perform ACTIVATE processing (switching of the existing
software to the downloaded software) for each device or each segment following the
software download. The default is “Each device.” If ACTIVATE processing is set to be
performed for each device, the software download and ACTIVATE processing will be
performed successively for each target device.
If ACTIVATE processing is set to be performed for each segment, the software download
will be performed to all target download devices in the segment first. When all downloads
are complete, you can choose to continue with ACTIVATE processing, or perform it at a
later date in the operation continuation confirmation dialog box to be displayed. To perform
ACTIVATE processing at a later date, select the target devices that have completed the
software download in the Device Settings dialog box and click the [Download] button. Select
the applicable item in the operation details confirmation dialog box to be displayed.
Since ACTIVATE processing requires the applicable Fieldbus devices to be reset, safely
stop the controls currently executed by the target devices or perform other necessary
operation prior to a ACTIVATE processing.
• Processing mode
The “Standard Mode” and “High-Speed Mode” are available as the software download
processing modes. In the standard mode, the processing of other applications is
given priority. In the high-speed mode, other operations are adjusted to improve the
communication performance. In the high-speed mode, however, a larger bandwidth is
occupied and therefore the FF-H1 communication applications (PRM communication
server, etc.) that require assurance of periodicity will be affected. The default is “Standard
Mode.”
• OPC server computer name
If an OPC server is defined and the PRM (Plant Resource Manager) exists on the network,
set the OPC server computer name to notify all HISs of the historical messages of software
download results by the software download function, via the OPC.
n Reflecting the Result

When the download is complete, the information of all devices that have completed the software
replacement will be notified to the engineering function and HIS.
l Reflecting in the Engineering Function

The device information of devices completing the software replacement will be notified to the
Fieldbus Builder of the engineering function for each segment.
The notified device information will be used for the engineering function when performing
reengineering.
l Notifying to the HIS

The fact that the software revision has been upgraded for the devices completing the software
replacement will be notified to the HIS for each segment using a historical message; if a
computer name is specified for “OPC Server Computer Name” field on Option dialog box.

n Export/Import
The information of the target devices for software replacement, as well as the information
regarding the replacement result, can be exported or imported in the text file format.
l Export
The information of the target devices for software replacement, as well as the information
regarding the replacement result, can be output in the text file format.
l Import
A text file output via the export function can be imported. By importing an exported text file, the
work session that was in progress at the time of export can be continued. Executing an import will
clear the current work data.
n Forecast/Progress Display
The time required for software download is estimated and displayed in the Device Settings
dialog box. At the same time, the progress of software download is displayed in the Device
Settings dialog box. The progress of software download to each segment is displayed in the
Communication executing dialog box for each segment.
l Estimating the Download Time

The estimated software download time is calculated from the size of the downloading software. If
multiple devices are selected, the sum of estimated download times for the selected devices will
be displayed. When the download is performed simultaneously to a group of devices connected
to multiple segments, the download time will be calculated by considering the concurrent status
of the applicable segments. The estimated download time is recalculated when the download is
completed for each device.
l Displaying the Progress of Download

The progress of download is displayed. The progress of download to all target download devices
is displayed in a single view.
You can also display at a desired timing the progress of download to a segment to which the
selected target devices belong.
The progress is indicated not by the remaining download time, but by the progress of processing
on the devices.

E2.3 Software Download Operation

This section describes the software file download operation to Fieldbus devices.

E2.3.1 General Operation Flow

The following describes the general flow of software replacement operation.
n Operation Flow
The software replacement operation is performed in the Device Settings dialog box called from
the System View or Device Panel of the engineering function. Status monitoring and operation
of the software download in progress is performed in the Communication executing dialog box
opened from the Device Settings dialog box.
Engineering function HIS

Start
(System View/Device Panel) (historical messages)
Device Settings
Reflection Result dialog box Reflection
File Start
Start
Communication
executing dialog box
Communication
executing dialog box
Multiple downloads can

Download Download be executed concurrently.
Segment 2
Segment 1
Fieldbus device
Fieldbus device
E020301E.ai
Figure General Operation Flow
Before executing a software download, the new software files obtained from the device vendors
must be stored in the folder in which the DD files and capability files are stored.
If the device type (DEV_TYPE) will change as a result of software replacement, the target
devices must be deleted and the devices of the new device type must be registered using the
Fieldbus Builder before the download. The software download will be performed to the devices of
the new device type.
SEE
ALSO • For storing software files obtained from the device vendors, see the following:
“n Storing Software Files” in E2.2, “Functional Details of Software Download”
• For the operation required prior to a software download when DEV_TYPE will change as a result of
software replacement, see the following:
“l When the Device Type (DEV_TYPE) Will Change as a Result of Software Replacement”

l Flow of Software Download Operation
The following describes the flow of software download operation:
1. Device Setting dialog box can be started from System View or Device Panel.
2. Set the target devices in the Device Settings dialog box. The target devices can be set
individually or in a batch mode.
3. Select the devices in the Device Settings dialog box and execute a download.
4. During the download, the progress of download as well as warnings and errors, if any,
will be displayed in the Communication executing dialog box opened from the Device
Settings dialog box. If the applicable devices are distributed over multiple segments,
the Communication executing dialog box can be displayed for each segment. Each
Communication executing dialog box operates independently.
5. When the download was successful, the device information of the devices whose software
has been replaced will be notified to the Fieldbus Builder of the engineering function. The
fact that the software revision has been upgraded for the applicable Fieldbus devices will
also be notified to the historical message function of the HIS, if OPC server is applied to the
Fieldbus system.
SEE
ALSO For more information about the software download procedure, see the following:
E2.3.3, “Setting Up the Target Devices”
E2.3.4, “Downloading Software”
l Reengineering Required after Software Replacement

The following reengineering items will be executed automatically when [Resolve Invalid Element]
is selected in the [Project] menu of the System View.
• Update of DD files and capability files in the target devices
• Download
• Resolution of invalid elements
SEE
ALSO For more information about the reengineering procedure, see the following:
E2.3.6, “Performing Reengineering”
l When the Device Type (DEV_TYPE) Will Change as a Result of Software

Replacement
If DEV_TYPE will change as a result of software replacement, the target devices must be deleted
and the devices of the new device type must be registered prior to a software download. The
procedure is as follows:
1. Delete the target devices in the Fieldbus Builder.
2. Register new DEV_TYPE devices. At this time, make sure their device tag names and node
addresses are the same as the settings of the deleted devices.
3. Select [Device ID acquisition] from the [Device Registration] menu of the Fieldbus Builder to
acquire the device IDs.
4. Select [Download] from the [File] menu. (An error will generate because the device type is
different, but ignore the error and continue with the processing.)
5. Perform a software download to the registered devices.

E2.3.2 Device Settings Dialog Box and Communication

Executing Dialog Box
The following describes the Device Settings dialog box and the Communication executing
dialog box.
n Device Settings Dialog Box

The Device Settings dialog box plays a central role in the software download operation, where
it is used for setting the target devices, registering the devices in a batch mode, and issuing a
download command as well as export/import commands.
Device Settings
Check License...
Device List Display Area
Add
Delete
Export
Pop-Up Menus
Import
Predicted Download Overall Progress

Time Display Area Display Area
Option... Register all devices Select all Show Progress Print file Update Download
Stop
Predicted Download Time:
1 Hours 35 minutes 47
E020302E.ai
Figure Device Settings Dialog Box

l Device List Display Area
This area displays a list of target devices for software replacement.
The display items in the device list are summarized below.
Table Display Items in the Device List
Display item Description Item that can be set Remark
Selection check These check boxes are used to specify the target x All check boxes are
boxes download devices. Clicking the [Select all] button unselected by default.
will select all check boxes.
Download result This area displays the download result. Successful, Failed,
display area If the download to a device was successful, the Not downloaded
check mark will be removed from the selection
check box of the applicable device.
Device tag name Tag name of the device on FF-H1 bus x
Node address Node address of the target device x
MANUFAC_ID Manufacturer ID of the target device. A desired ID x (When the devices Accompanied by the
can be selected from the menu. are set individually) vendor name.
DEV_TYPE Device type of the target device. A desired type x (When the devices Accompanied by the
can be selected from the menu. are set individually) device name.
DEV_REV Device revision of the target device
Software Revision Software revision of the target device
Software file name Name of the binary software file to be downloaded. x (When the devices Multiple files may be
The applicable file name can be selected from the are set individually) selected (in the case of
menu. (*1) multi-domain download).
To specify multiple files,
separate the file names
by a semicolon.
MANUFAC_ID (file) Manufacturer ID of the software to be downloaded
DEV_TYPE (file) Device type of the software to be downloaded
DEV_REV (file) Device revision of the software to be downloaded
Software Revision Software revision of the software to be
(File) downloaded
Domain Domain number of the FCS Segment
information
Station Station number of the FCS
Node Number of the node in which the ALFI11 is
installed.
Slot Number of the slot in which the ALFI11 is installed
Port Port number of the ALFI11
E020303E.ai
x: Set by the user

*1: The content of the displayed menu will be different in each of the following three levels:
. • When both MANUFAC_ID and DEV_ID are known:
A list of software file names under DEV_ID is displayed.
. • When only MANUFAC_ID is known:
A list of software file names under MANUFAC_ID is displayed.
. • When neither is known:
A list of all software file names is displayed.

Device information can be added, deleted or changed, or desired Fieldbus devices can be
selected as the software download target on the list of target devices for software replacement.
• Add:
Click the right mouse button and select [Add] in the displayed pop-up menu, and add
desired information in the Add Device dialog box to be displayed.
SEE
ALSO For the Add Device dialog box, see the following:
“l Setting Up the Target Devices Individually” in “n Setting Up the Target Devices” of E2.3.3, “Setting Up
the Target Devices”
• Delete:
From the target devices for software replacement, select the device you want to delete and
click the right mouse button. Select [Delete] in the displayed pop-up menu to delete the
selected device.
• Change:
Make a desired change directly to the target device list.
• Select the target software download device:
In the list of target devices for software replacement, check the corresponding selection
check box in the far left column to select the device you want to execute a software
download to.
l [Download] Button
Clicking this button will execute a software download to the devices selected as the download
target.
If the download was successful, the result will be reflected in the engineering function.
l [Stop] Button
Clicking this button will cancel the download when processing on the currently downloading
device is complete.
Note that the download will be cancelled immediately if [Stop urgently (Downloading the software
is canceled immediately)] is selected in the confirmation dialog box displayed when the [Stop]
button is clicked.
l [Register all devices] Button

Clicking this button will display the Search dialog box.
In the Search dialog box, look for the devices requiring software replacement and simultaneously
set the information of all devices found as the target devices for software replacement. The
specified devices will be displayed in the Device Settings dialog box.
l [Select all] Button

Clicking this button will select all devices on the target device list as the target software download
devices, by checking all selection check boxes. All devices are not selected by default.

l [Update] Button
Clicking this button will refresh the download result display.
l [Print file] Button

Clicking this button will output the device information of all registered devices to a text file.
l [Option] Button
Click the [Option] button to display the Option dialog box, where you can specify the following
items:
Specify whether or not to execute a download when the revision of the downloading
software is the same as the revision of the existing software in the applicable Fieldbus
devices, and when the revision of the downloading software is lower than the existing
software.
• ACTIVATE processing
Specify whether to perform ACTIVATE processing (switching of the existing software to the
downloaded software) for each device or each segment following the software download.
• Processing mode
Specify “Standard” or “High-Speed” as the software download processing mode.
• OPC server computer name
If an OPC server is defined and the PRM (Plant Resource Manager) exists on the network,
set the OPC server name to notify all HISs of the historical message of software download
result, via the OPC.
SEE
ALSO For the four items that can be specified in the Option dialog box, see the following:
“l Software Download Options” in “n Communication (Download)” of E2.2, “Functional Details of Software
Download”
Option
Download even if the software is same revision.

Download even if the software is lower revision.
Activation
ACTIVATE is executed in each device.
ACTIVATE is executed in each segment.
Mode
Standard: Please select this usually.
High-speed: The FF-H1 communication
applications (PRM communication server etc.) that
the fixed cycle should be guaranteed are affected
because the communication band is occupied.
OPC Server
Computer name:
OK
E020304E.ai
Figure Option Dialog Box

l [Close (X)] Button
Clicking this button will close the Device Settings dialog box.
l [Export] (Pop-Up Menu)

Clicking this button will execute export.
l [Import] (Pop-Up Menu)

Clicking this button will execute import.
l Predicted Download Time Display Area

This area displays the sum of estimated download times for the selected target software
download devices in each segment, adjusted by the concurrent status of simultaneous
downloads to multiple segments. The estimated time is dynamically calculated and displayed
when each device is selected.
Display format: <Number> Hours <Number> Minutes
l Overall Progress Display Area

The progress of download is displayed using a progress bar. The completion of downloading to
all selected devices is assumed as 100%.
l [Show Progress] Button

Clicking this button will display a Communication executing dialog box for the segment to
which the target download devices belong. If the target download devices are connected to
multiple segments, multiple Communication executing dialog boxes will be displayed, each
corresponding to one segment.
l [Check Licenses] Button

Clicking this button will open the Licenses Manager dialog box.
SEE
ALSO For more information on verifying the number of licenses, see the following:
E2.3.7, “Downloading Software Controlled by License”

n Communication Executing Dialog Box

The Communication executing dialog box is displayed when a software download is executed.
The Communication executing dialog box is called by clicking the [Show Progress] button in the
Device Settings dialog box. A separate Communication executing dialog box is provided for each
segment.
The Communication executing dialog box displays the progress of download, and a download
cancellation command can be issued from this dialog box.
Communication executing: MYPJT_0101_010112
Segment Information
Display Area
Message Display Area
Pop-Up Menu
Copy
41 Progress
display area
Stop
E020305E.ai
Figure Communication Executing Dialog Box
l Segment Information Display Area

The title bar of the dialog box displays the information of the segment to which the download is
being executed.
l Message Display Area

The download sequence is displayed. Warnings and errors, if generated, are also displayed in
this area.
l Progress Display Area

The progress of download to the applicable segment is displayed using a progress bar. The
completion of downloading to all selected devices in the segment is assumed as 100%.

l [Stop] Button
The download will be cancelled when processing on the currently downloading device is
completed.
Note that the download will be cancelled immediately if [Stop urgently (Downloading the software
is canceled immediately) ] is selected in the confirmation dialog box displayed when the [Stop]
button is clicked.
Stop
Is the software downloading stopped?

Stop urgently
(Downloading the software is canceled immediately)
Stop when downloading for device in an executing ends
OK Cancel
E020306E.ai
l [Copy] (Pop-Up Menu)

Clicking this button will copy the message displayed in the message display area to the
temporary save area.

E2.3.3 Setting Up the Target Devices

This section describes the operation to set up the target devices for software
replacement.
n Starting the Target Device Configuration Function

Device Setting dialog box can be started from System View or Device Panel.
l Start from System View

Select [Fieldbus] and then [Software Download] from the [Tools] menu in the System View to start
up the target device configuration function. The Device Settings dialog box will be displayed. The
device list display area of the Device Settings dialog box is initially blank.
l Start from Device Panel

Follow the procedure below to start Device Setting dialog box from Device Panel.
1. In the device status area of Device Panel, choose the device that the software needs to be
changed. Multiple devices can be chosen together. When designating the chosen devices
shown in step 2, the devices can be designated. When designating the devices as shown in
step 2 on the device setting dialog box, this step 1 can be omitted.
2. Choose [Software Download] from [Communication] menu and start the setting dialog box
for the designated devices. Then Device Setting dialog box will be displayed. In the device
list area of Device Setting dialog box, the information of the fieldbus devices corresponding
to the designated devices will be displayed on Device Panel.

n Setting Up the Target Devices

The target devices for software replacement can be set up individually or in a batch mode in the
Device Settings dialog box.
l Setting Up the Target Devices Individually

Set up the target devices for software replacement individually according to the following
procedure:
1. Click the right mouse button in the device list display area of the Device Settings dialog box,
and select [Add] in the displayed pop-up menu to display the Add Device dialog box.
Add Device
Device Tag name:
Node Address:
MANUFAC_ID:
DEV_TYPE:
Software File name:
Station name:
Track number: 1
Node:
Slot:
Port:
OK Cancel
E020307E.ai
Figure Add Device Dialog Box
2. Enter the following items in the Add Device dialog box and click the [OK] button:
• Device tag name
• Node address
• MANUFAC_ID (Select from the menu)
Example: 0x594543 (Yokogawa Electric Corp.)
• DEV_TYPE (Select from the menu)
Example: 0x0008 (EJA SD)
• Software file name (Select from the menu)
• Station name
• Track number (Fixed to 1)
• Node
• Slot
• Port
3. The device information entered in the Add Device dialog box will be displayed in the Device
Settings dialog box.

l Setting Up the Target Devices for Software Replacement in a Batch Mode
Set a group of target devices for software replacement simultaneously according to the following
procedure:
1. Click the [Register all devices] in the Device Settings dialog box.
2. The Search dialog box will be displayed.
Search
Device Tag TI1001

MANUFAC_ID
DEV_TYPE
DEV_REV
Software revision
Search
Search Results
Device tag NodeAddress MANUFAC_ID DEV_T
OK Cancel
E020308E.ai
Figure Search Dialog Box
In the Search dialog box, select the search condition items you want to use from the five
available items (device tag name, MANUFAC_ID, DEV_TYPE, DEV_REV and Software
Revision), by checking the check box of each desired item. Select a condition for each
selected item from the menu displayed by clicking the combo box at right. When the search
conditions have been set, click the [Search] button.
3. The search results will be displayed. Verify the search results and click the [OK] button.
4. The Search dialog box will close, and all devices that have been found will be set as the
target devices and displayed in the Device Settings dialog box.
5. If necessary, the device information can be corrected in the Device Settings dialog box.

E2.3.4 Downloading Software

The following explains the procedure for executing software downloads.
n Selecting the Target Download Devices

Select the device to download to by checking the corresponding selection check box in the far
left column of the device list displayed in the Device Settings dialog box. You can select multiple
devices. Devices can also be selected from multiple segments.
To select all devices currently displayed, clicking the [Select all] button will check all selection
check boxes.
n Executing Downloads
Execute downloads according to the following procedure:
1. Select the target download device or devices in the Device Settings dialog box.
2. Click [Option] button to display the Option dialog box. The option settings can be modified if
necessary, and then click [OK] to close this dialog box.
3. Click the [Download] button in the Device setting dialog box. The download will start and the
progress will be displayed in the overall progress display area.
To verify the progress of download to each device, click the [Show Progress] button. This
will display the Communication executing dialog box for each segment to which the target
devices belong. The Communication executing dialog box will display the progress of
download to that segment.
4. If the [ACTIVATE is executed in each segment] software download option is selected,
an operation continuation confirmation dialog box will be displayed when the software
download is completed to all target devices in the segment. To execute ACTIVATE
processing successively, click the [OK] button in the operation continuation confirmation
dialog box. ACTIVATE processing will be performed simultaneously for all target
devices in the segment that have already completed the software download. To perform
ACTIVATE processing at a later date, click the [Cancel] button in the operation continuation
confirmation dialog box. ACTIVATE processing will not be executed and the communication
will be disconnected.
5. The result of communication will be displayed in the [Result] column of the device list display
in the Device Settings dialog box. If the software replacement was successful, the check
mark will be removed from the selection check boxes of the applicable devices.
When [ACTIVATE is executed in each segment] is selected, you may choose not to perform
ACTIVATE processing for some devices after completion of software download. In this case,
execute ACTIVATE processing for the applicable devices at a later date according to the
following procedure:
1. Select the target devices in the Device Settings dialog box and click the [Download]
button. If the devices have already completed the software download, the operation details
confirmation dialog box will be displayed.
2. Select the type of ACTIVATE processing you want to execute in the operation details
confirmation dialog box. Next, click the [Yes] button. ACTIVATE processing will be executed.

IMPORTANT
If a communication error occurs during a software download, restore the system according to the
1. Execute a software download again.
2. Depending on the internal status of the applicable Fieldbus device, the processing may fail
again. In this case, execute a software download again.
TIP
When the downloading software is controlled by license, clicking the [Download] button will prompt the system to
verify the license. The download will start if the number of target download devices is the same as or less than the
number of licenses held by the corporate user.
SEE
ALSO For the download operation of software controlled by license, see the following:
“n Download Operation of Software Controlled by License” in E2.3.7, “Downloading Software Controlled
by License”
n Canceling a Download
Cancel a software download according to the following procedure.
Once a download is canceled by emergency stop, it must be performed again.
l Canceling a Download for Each Segment

The download to the target devices in a segment can be cancelled.
1. In the Device Settings dialog box, select the target devices connected to the segment
you want to cancel the download to, and click the [Show Progress] button to display the
Communication executing dialog box.
2. Click the [Stop] button in the Communication executing dialog box. A confirmation dialog
box will be displayed.
3. In the confirmation dialog box, select “Stop urgently (Downloading the software is canceled
immediately)” or “Stop when downloading for device in an executing ends,” and then click
the [OK] button.
4. The download will be cancelled.
l Stopping All Downloads Simultaneously

The downloads currently in progress concurrently to the target devices in all segments can be
cancelled simultaneously.
1. Click the [Stop] button in the Device Settings dialog box. A confirmation dialog box will be
displayed.
2. In the confirmation dialog box, select “Stop urgently (Downloading the software is canceled
immediately)” or “Stop when downloading for device in an executing ends,” and then click
the [OK] button.
3. All downloads will be cancelled.

E2.3.5 Exporting/Importing the Information of the Target

Devices for Software Replacement
The following describes the procedures for exporting and importing the information of the
target devices for software replacement.
n Export
Export the information of the target devices for software replacement according to the following
procedure:
and select [Export] in the displayed pop-up menu. The Save As dialog box will be displayed.
2. Specify a desired file name and folder name in the Save As dialog box, and click the [OK]
button.
3. The information of the target devices for software replacement will be saved in the specified
folder under the specified file name.
n Import
Import the exported information of the target devices for software replacement according to the
and select [Import] in the displayed pop-up menu. The Open dialog box will be displayed.
2. In the Open dialog box, select a desired file to which the information of the target devices for
software replacement has been exported and click the [OK] button.
3. The import will be executed and the data will be displayed in the Device Settings dialog box.

E2.3.6 Performing Reengineering

The following describes the procedure for performing reengineering.
n Reengineering
After the software has been replaced, perform reengineering according to the following
procedure:
1. In the System View, select [Resolve Invalid Element] from the [Project] menu.
2. Reengineering will be performed automatically in the order specified in the following steps.
3. The Fieldbus Builder executes a download.
4. The DD files and capability files will be updated for all devices whose software has been
replaced. Note that the DD files and capability files will not be updated if the revision
information of DD files and capability files to be acquired from the file name of the new
software has not been changed from the current revision information.
5. Upon a successful update of the DD files and capability files of all devices whose software
has been replaced, a download will be executed and the downloaded information will be
written over the exiting information.
6. The Control Drawing Builder executes a download.

E2.3.7 Downloading Software Controlled by License

The following describes how to store software files controlled by license and their
download to Fieldbus devices.
n Protect Key Control

Software controlled by license is subject to a limitation regarding the number of target devices
whose existing software can be replaced with a new version.
If the applicable software is controlled by license, the License Manager dialog box will be
displayed when a software file is stored or a software download to the target devices is started,
and the user will be prompted to set a protect key. Here, use the protect key provided when the
software files were purchased. This protect key determines the number of target devices for
which software replacement is permitted (number of licenses). The number of licenses can be
verified under “Remaining Licenses” displayed in the License Manager dialog box.
No software download will be executed if the number of selected target devices exceeds the
number of remaining licenses for any software to be downloaded. The number of remaining
licenses will be decremented each time a target device completes the software replacement
successfully (completion of ACTIVATE processing). The figure below shows the License
Manager dialog box.
License Manager
Software File Name Protect Key Remaining License DEV_TYPE Device Family
5945430008_0008_EJA-SD_ XXXXXXXXX 10 0x0008(EJA) 0x0008
5945430007_0007_YVP-SD_ (Free) 0x0007(YVP) 0x0007
Enter Protect Key
OK Cancel
E020309E.ai
Figure License Manager Dialog Box
The following information is displayed in the License Manager dialog box:

• Software File Name
• Protect Key:
Protect key needs to be entered. However, for the license-free version, the entry field is
lockout.
On the Device Settings dialog box, click the [Check Licenses] button to open the License
Manager dialog box (no protect key entry field on this dialog box); choose a software file
name and then click [Update License] button to open the Enter Protect Key dialog box so
as to enter the license code.
• Remaining License:
Free licenses are indicated by “(Free),” while service licenses are indicated by “(No
Limitation).”

• DEV_TYPE:
A hexadecimal number followed by a character string. Example) 0x0007 (YVP)
• Device Family
• Software Revision
• Software Name
• Domain Name
• MANUFAC_ID:
A hexadecimal number followed by a character string. Example) 0x594543 (Yokogawa
Electric)
n Storing Software Controlled by License

Store the files of software controlled by license in the HIS or ENG in which the engineering
function is installed according to the following procedure:
1. From the Windows [Start] menu, select [YOKOGAWA CENTUM] and then [Copy Tool for
Fieldbus associated files] to start the Copy Tool for Fieldbus associated files.
Copy Tool for Fieldbus associated files
Select copy folder or file, and destination folder.
Select copy source

Copy folders
...
Copy files
...
Select copy destination

C:\Fieldbus\KAPPA\DD ...
Advanced... Protect Key... OK Cancel
E020310E.ai
Figure Copy Tool for Fieldbus associated files
2. Use the Copy Tool for Fieldbus associated files to specify the copy source, which should be
the software folder/files obtained from the device vendors, as well as the copy destination
(storage location), which should be the folder in which the DD files are stored. Click the [OK]
button.
3. The License Manager dialog box will be displayed. Only the software files that require
protect key setting are displayed in the License Manager dialog box.
4. In the protect key entry field of the License Manager dialog box, enter the protect key
provided when the software files were purchased, and click the [OK] button.
5. The software files will be stored in the specified folder and the protect key will be set.

n Download Operation of Software Controlled by License

Download the software files controlled by license according to the following procedure:
1. Set up the target devices for software replacement in the Device Settings dialog box, and
select the devices to download the software to.
2. Click the [Download] button.
3. If a protect key was set when the software files were stored, the download will be started.
If no protect key was set when the software files were stored, the License Manager dialog
box will be displayed. Only the software files that require protect key setting are displayed in
the License Manager dialog box. Enter in the protect key entry field the protect key provided
when the software files were purchased, and click the [OK] button. The License Manager
dialog box will close and the download will start.
SEE
ALSO For the operation to be performed after a software file download has started, see the following:
“n Executing Downloads” in E2.3.4, “Downloading Software”
n Setting Up Additional Licenses

If additional licenses were purchased to add target devices to which the software files can be
downloaded (number of licenses), set the new protect key provided when the additional licenses
were purchased according to the following procedure:
1. From the Windows [Start] menu, select [YOKOGAWA CENTUM] and then [Copy Tool for
Fieldbus associated files] to start the Copy Tool for Fieldbus associated files.
2. Click the [Protect Key] button. The License Manager dialog box will be displayed.
In the License Manager dialog box, enter (overwrite) the protect key provided when the
additional licenses were purchased. Enter the protect key in the protect key entry field for
the software files to which the licenses are to be added, and click the [OK] button.
3. The new protect key will be stored and the number of currently remaining licenses will be
incremented by the number of additional licenses.
IM 33M20T10-40E
n Verifying the Number of Licenses

The number of remaining licenses can be verified according to the following procedure:
1. Click the [Check Licenses] button in the Device Settings dialog box. The License Manager
dialog box will be displayed. (In this case, the protect key entry field will not be displayed.)
License Manager
Software File Name Remaining License DEV_TYPE Device Family Software Revision
5945430008_0008_EJA-SD_ 10 0x0008(EJA) 0x0008 R1.01
5945430007_0007_YVP-SD_ (Free) 0x0007(YVP) 0x0007 R1.01
Update License OK Cancel
E020312E.ai
Figure License Manager Dialog Box started by clicking [Check License] button
2. In the License Manager dialog box, verify the number of remaining licenses for each
software file.
3. When you check the number of licenses and want to add more licenses, you need to
choose the software file name and then click [Update License] button to open the Enter
Protect Key dialog box so as to enter the license code of the software.
Enter Protect Key
Protect Key:
- - - - -
OK Cancel
E020311E.ai
Figure Enter Protect Key Dialog Box
4. On the Enter Protect Key dialog box, enter the license code and then click [OK] button.
The entered license will be authenticated and added to the number of licenses. Then the
Enter Protect Key dialog box will be closed.

Blank Page
<E3. Devices of Multiple Levels> E3-1
E3. Devices of Multiple Levels

In this section, the devices of multiple levels and how to register the devices of multiple
levels will be explained.

E3.1 What is a Device of Multiple Levels?

A Device of Multiple Levels is a fieldbus device that supports multiple capability levels.
n Capability Levels
▼ Capability Level
According to FOUNDATION fieldbus specifications, one type fieldbus device may support
multiple capability levels. The function blocks of a fieldbus device may vary with the capability
levels. For an example, when applying capability level 1 to a fieldbus device, the device only
supports two AI function blocks. However, if applying capability level 2 to the device, the same
device will support two AI blocks and one PID block.
The devices supporting the multiple capability levels are referred to as the devices of multiple
levels.

E3.2 Registering Devices of Multiple Levels

How to register the devices of multiple levels are explained in this section.
n How to Register Devices of Multiple Levels

The devices of multiple levels can be registered as follows:
1. Choose [Add Device] from [Device Registration] menu. Manual Registration dialog box will
be displayed.
2. On Manual Registration dialog box, choose a device of multiple levels. An additional area for
selecting capability levels will be displayed on the Manual Registration dialog box.
3. Click [Select] button, the Capability Level Select dialog box will be displayed.
IMPORTANT
Do not click [OK] without clicking [Select]. If clicking [OK] without clicking [Select], the device will
be registered without selecting a capability level. In this case, only the resource blocks will be
registered.
4. Choose a capability level on the Capability Level Select dialog box.

5. Click [OK] on the Capability Level Select dialog box, then the defined contents of the
capability level will be displayed on the Manual Registration dialog box.
6. Click [OK] on the Manual Registration dialog box, then registration for the device of multiple
levels will be completed.
n How to Change Capability Level of Existing Device

When changing the capability level of an existing device, do the following:
1. Choose [Update Capability File/DD File] from [Device Registration] menu. Update Capability
File/DD File dialog box will be displayed.
2. Choose a device of multiple levels on the displayed dialog box. An additional area for
selecting capability levels will be displayed on the dialog box.
3. Click [Select] button, the Capability Level Select dialog box will be displayed.
4. Choose a capability level on the Capability Level Select dialog box.
5. Click [OK] on the Capability Level Select dialog box, then the defined contents of the
capability level will be displayed on the Update Capability File/DD File dialog box.
6. Click [OK] on the Update Capability File/DD File dialog box, the device will be set with a
capability level.

Blank Page
Ind-1
CENTUM VP
INDEX
Symbols Capability Level................................................. D2-10
%Z Auto Assignment............................................B2-5 Client/Server Type Communication.....................B1-3
Command Line.................................................... D1-6
A Communication Executing Dialog Box............. E2-19
Configuration Data File........................................A1-2
Additional License............................................. E2-30
Constant............................................................ B2-41
Address Assignment......................................... D2-49
CONTROL_OPTS............................................ B2-38
ALARM_SUM................................................... B2-39
Controlled by License....................................... E2-28
Alarm Off........................................................... B2-18
Create and Use Template on Fieldbus
Alert......................................................................A1-2 Builder............................................................. D2-74
ALF111 Create or Open Template File on Device
ALF111.........................................................A1-2 Panel............................................................... D5-52
Breaks Down............................................ B1-14 Custom Block...........................................A3-9, D1-23
Duplexing.................................................. B1-17
Engineering................................................ D1-2 D
Module Status Display................................ C1-5 DD_REV............................................................. D2-9
Arrester................................................................A1-9 DD File.................................................................A1-2
Detection of Front Connector Disconnection.... B1-18
B DEV_REV........................................................... D2-9
Barrier...................................................................A1-9 DEV_TYPE......................................................... D2-9
Batch Self-Documentation................................ D1-37 Device Class
Block Alarm....................................................... B2-17 Changing.................................................. D2-36
Block Instantiation Device ID
Block Instantiation.......................................E1-2 Acquisition................................................ D2-34
Defining.....................................................E1-11 Changing.................................................. D2-35
Engineering.................................................E1-5 Device ID.................................................... D2-9
Executing.................................................. E1-14 Device Management Tool................................. D1-41
Block Mode Equalization.....................................B2-9 Device of Multiple Levels.....................................E3-2
Block Parameter............................................... D2-44 Device Panel....................................................... D5-2
Block Tag Name Device Tag Name
Block Tag Name....................................... D2-13 Changing.................................................. D2-35
Changing.................................................. D2-35 Download to All Fieldbus Devices..................... D1-40
Builder Definition Items..................................... B2-31 Duplexing
Builder Quick Start............................................ D2-23 LAS........................................................... B1-20
C E
Cable....................................................................A1-8 Edit Block Parameter Dialog Box...................... D2-54
Calibration......................................................... B2-13 Edit Communication Parameters Dialog Box... D2-68
Capabilities File....................................................A1-2 Enhanced MC/Switch Instrument Block........... A2-13
Capability File Selection Dialog Box....................E1-7 Environment Settings Dialog Box..................... D2-16
Examples of Illegal Connection........................ A2-14

Ind-2
Extended Parameter FF-MAO
Extended Parameter...................................A1-2 Connecting Terminals, Data Items, and
High-Speed Transmission Terminals..........B2-6 Parameters............................................. B2-25
Data Items................................................ B3-68
F Input/Output Test...................................... D3-19
FF-MDI
Fallback Operation............................................ B1-13
Connecting Terminals, Data Items, and
Fallback Operation Specification.........................B1-8
Parameters............................................. B2-24
Fault State Operation Specification.....................B1-8
Data Items................................................ B3-54
FF.........................................................................A1-2
Input/Output Test...................................... D3-18
FF-AI
FF-MDO
Parameters............................................. B2-20
Parameters............................................. B2-24
Data Items...................................................B3-4
Data Items................................................ B3-58
FF-AO
FF-OS
Parameters............................................. B2-22
Parameters............................................. B2-22
Data Items................................................ B3-27
Data Items................................................ B3-35
FF-CS
FF-PID
Parameters............................................. B2-20
Parameters............................................. B2-21
Data Items................................................ B3-12
Data Items................................................ B3-16
Input/Output Test.......................................D3-11
FF Mode/CENTUM Mode........................ D1-35
FF-DI
FF-RA
Parameters............................................. B2-20
Data Items...................................................B3-8
Parameters............................................. B2-21
Data Items................................................ B3-22
FF-DO
FF-SC
Parameters............................................. B2-22
Data Items................................................ B3-31
Parameters............................................. B2-23
Data Items................................................ B3-39
FF-IS
FF Faceplate Block
Parameters............................................. B2-23
Abnormality Detection Operation............. B2-12
Data Items................................................ B3-49
Alarm Processing..................................... B2-15
FF Faceplate Block.....................................A2-2
FF-IT
State Transition............................................A4-9
Parameters............................................. B2-23 Fieldbus Block
Data Items................................................ B3-44 Engineering.................................................A4-4
Input/Output Test...................................... D3-16 Fieldbus Block.............................................A1-2
FF-MAI Fieldbus Block Instantiation.................................A1-3
Connecting Terminals, Data Items, and Fieldbus Block List Dialog Box............................ D1-8
Parameters............................................. B2-25 Fieldbus Builder
Data Items................................................ B3-63 Menu List.................................................. D2-81
Input/Output Test...................................... D3-18 Window Structure....................................... D2-6
Fieldbus Communication Module........................A1-8

Ind-3
Fieldbus Device O
Already Registered................................... D1-10 O/S Mode.......................................................... B2-10
Automatic Registration............................. D2-30 Offline Download............................................... D2-39
Fieldbus Device...........................................A1-3 Optional Definition Items................................... B2-36
Not Registered......................................... D1-12
Registering............................................... D2-25 P
Fieldbus I/O..........................................................B2-5
Polling Node Address
Fieldbus Message............................................... C1-4
Default Value.................................D2-11, D2-30
Fieldbus Overall Upload................................... D1-39
Print................................................................... D2-65
Fieldbus Power Supply........................................A1-9
Process Alarm..................................................... C1-3
FOUNDATION fieldbus Faceplate Block.............A1-3
Profile................................................................ D2-14
Function Block.....................................................A1-3
Prohibiting MAN Entry........................................B2-11
Protect Key Control........................................... E2-28
H
Publisher/Subscriber Type Communication........B1-3
Host File...............................................................A1-3
Host File Set...................................................... D1-38 R
Registering New Device on Device Panel........ D5-50
I
Resolving Invalid Elements............................... D1-30
I/O is Disconnected............................................. D3-2 Revision Name.................................................... D2-9
I/O Simulation.................................................... B2-19
Import................................................................ D2-80 S
Initial Downloading............................................ D2-43
Saving Tuning Parameters............................... A2-16
Instantiation Definition Dialog Box.......................E1-9
Schedule Display Dialog Box............................ D2-63
INTEG_OPTS................................................... B2-37
Scheduled Load................................................ D2-66
IO_OPTS.......................................................... B2-36
Scheduled Load Setting.................................... D2-22
IOM Initialization Downloading......................... B1-22
Segment...............................................................A1-3
Self-Documentation.......................................... D2-80
L
Sequence Table................................................ B2-41
LAS......................................................................A1-3 SHED_OPTS.................................................... B2-37
Local Mode........................................................ B2-10 Simplified Universal Block
Builder Definition Item.............................. A3-12
M Connection Terminals, Data Items and
Macrocycle...........................................................A1-3 Parameters............................................. A3-10
Manually Copying Device For Registering Control Loop................................................A3-4
Device............................................................. D2-72 Creating.................................................... D1-17
MANUFAC_ID..................................................... D2-9 I/O Parameter Name.....................A3-11, D1-25
Master Data Download..................................... D2-46 Simplified Universal Block...........................A3-2
Maximum Execution Time................................ D2-14 Software Download
MO_OPTS........................................................ B2-36 ACTIVATE Processing................................E2-4
MODE_BLK...................................................... B2-39 Communication (Download)........................E2-8
Model Name........................................................ D2-9 Device Settings Dialog Box...................... E2-14
Multiple Levels Compliant Devices......................A1-3 Forecast/Progress Display....................... E2-10
Reflecting the Result...................................E2-9
N Software Download.....................................E2-2
NM Parameter Software File........................................................E2-5
Optimum Value......................................... D2-19 Software Revision
Node Address Changing.................................................. D2-36
Changing.................................................. D2-36 Software Revision...................................... D2-9
Speeding Up Data Access................................ D1-15

Ind-4
Standard Block Parameter...................................A1-4
STATUS_OPTS................................................ B2-38
Subschedule......................................................D2-11
Subschedule Number....................................... D2-14
System Alarm...................................................... C1-3
T
Tag Assignment................................................. D2-49
Template............................................................ A4-13
Terminator............................................................A1-9
Trend Object............................................A1-4, D2-71
Tuning the Parameters Common in a
Segment.......................................................... D2-69
Tuning the Parameters Unique to a Device...... D2-69
U
Upload............................................................... D2-48
V
VCR......................................................................A1-4
Vendor Name...................................................... D2-9
View Object..........................................................A1-4
W
Wiring.................................................................. D3-4

Rev-1
Revision Information
 Title : CENTUM VP FOUNDATION fieldbus Reference
 Manual No. : IM 33M20T10-40E
Mar. 2008/1st Edition/R4.01 or later*

* : Denotes the release number of the software corresponding to the contents of this user's manual. The
revised contents are valid until the next edition is issued.
Newly published
n For Questions and More Information

If you have any questions, you can send an E-mail to the following address.
E-mail: support-CENTUM@csv.yokogawa.co.jp
n If you want more information about Yokogawa products, you can visit Yokogawa’s
homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by Process Automation Product Marketing Dept.
Industrial Automation Systems Business Div.
Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN
n Printed by KOHOKU PUBLISHING & PRINTING INC.

Blank Page

M20T10 40e 01 PRT

Uploaded by

Copyright:

Available Formats

M20T10 40e 01 PRT

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

M20T10 40e 01 PRT

Uploaded by

Copyright:

Available Formats

FOUNDATION fieldbus

• Part A Fieldbus Overview

• Part B FCS Fieldbus Support

• Part C System Fieldbus Support

• Part D Fieldbus Engineering

• Part E Variety Fieldbus Device Engineering

CENTUM VP Document Map

Engineering Engineering Reference

 Operation and Operating

Communication Field Control

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

Indicates that the main switch is ON.

Indicates that the main switch is OFF.

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

n Notes on Handling User’s Manuals

n Warning and Disclaimer

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

l Commonly used conventions throughout user’s manuals:

Character string to be entered:

Character string enclosed by brackets ({ }):

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

Characters enclosed by brackets ([ ]):

l Conventions used in command syntax or program statements:

Characters enclosed by angle-brackets:

Characters enclosed by brackets ([ ]):

Characters enclosed by separators (| |):

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

Identifies a source to be referred to.

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

Copyright and Trademark Notices

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

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

A1. What is a Fieldbus?

CENTUM VP support the FOUNDATION fieldbus and PROFIBUS-DP communication

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

n Configuration Data File (Value File)

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

n Fieldbus Block Instantiation

n FOUNDATION fieldbus Faceplate Block

n LAS (Link Active Scheduler)

n Multiple Levels Compliant Devices

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

n Standard Block Parameter

n VCR (Virtual Communication Relationship)

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

A1.2 Fieldbus Systems

n CENTUM VP System and Fieldbus

l Integration of Control Function

l Integration of Operation and Monitoring

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

A1.3 Configuration of Fieldbus Systems

n Overall Configuration of the Fieldbus System

• System Builders Device Management

HIS: Human Interface Station

Figure Example of Fieldbus System Configuration

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

n Fieldbus System Configuration and Data Flow

FF faceplate block Parameter uploading

ALF111 status Parameter