Вы находитесь на странице: 1из 566

Toc-1

FOUNDATION fieldbus Tools

IM 33S05P10-01E 6th Edition

CONTENTS
1. Overview of Fieldbus Communication .................................................. 1-1
1.1 What is Fieldbus? ........................................................................................... 1-2
1.2 Configuration of Fieldbus System ................................................................. 1-3
1.3 Component Equipment of Fieldbus System ................................................. 1-8
1.4 Fieldbus Hardware ........................................................................................ 1-10
1.5 Software for Configuring a Fieldbus System .............................................. 1-15
1.6 Fieldbus System Engineering ...................................................................... 1-16
1.7 Device Management ..................................................................................... 1-24
1.8 Operation and Monitoring ............................................................................ 1-25
1.9 System Maintenance .................................................................................... 1-28
1.10 Glossary ........................................................................................................ 1-29
2. Fieldbus Communication Module .......................................................... 2-1
3. FCS Control Function Using Fieldbus ................................................... 3-1
3.1 Position of Fieldbus Block ............................................................................. 3-2
3.2 FCS Control Functions Related to the Fieldbus ............................................ 3-4
3.3 Connection to Fieldbus Block ...................................................................... 3-12
3.3.1 Connection to the Faceplate Block .................................................. 3-15
3.3.2 Connection to the Regulatory Control Block .................................... 3-24
3.3.3 Connection to the Sequence Control Block ..................................... 3-27
3.3.4 Connection to the Calculation Block ................................................ 3-32
3.3.5 Connection to the Off-Site Block ..................................................... 3-36
3.3.6 List of Parameters that can be Connected ...................................... 3-37
3.4 Reliability ....................................................................................................... 3-48

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Toc-2
4. System Builders Related to Fieldbus..................................................... 4-1
4.1 What is Fieldbus Engineering? ...................................................................... 4-2
4.1.1 Positioning of Fieldbus-Related System Builders .............................. 4-3
4.1.2 Fieldbus Engineering Flow ................................................................ 4-6
4.1.3 Overview of System Builders Related to Fieldbus ............................. 4-9
4.2 System Builders ............................................................................................ 4-12
4.2.1 Create New IOM Dialog Box ........................................................... 4-14
4.2.2 Download to IOM ............................................................................ 4-21
4.2.3 IOM Builder .................................................................................... 4-22
4.2.4 Download from IOM Builder ............................................................ 4-29
4.2.5 Control Drawing Builder .................................................................. 4-30
4.2.6 Start Fieldbus Engineering Tool ...................................................... 4-31
4.3 Test Function ................................................................................................. 4-32
4.4 Engineering and Startup Procedure for Fieldbus System .......................... 4-33
4.5 Procedure for Modifications After Fieldbus System Startup...................... 4-37
4.6 On-line Maintenance ..................................................................................... 4-39
5. Fieldbus Engineering Tool ..................................................................... 5-1
5.1 Overview of Fieldbus Engineering Tool ......................................................... 5-2
5.1.1 What is the Fieldbus Engineering Tool? ............................................ 5-3
5.1.2 Position of the Fieldbus Engineering Tool .......................................... 5-4
5.1.3 Features of the Fieldbus Engineering Tool ...................................... 5-13
5.1.4 Operating Environment Requirements ............................................ 5-15
5.1.5 Overview of Fieldbus Engineering Tool ........................................... 5-17
5.1.6 Project Manager ............................................................................. 5-19
5.1.7 Editors ............................................................................................ 5-32
5.1.8 Utilities ............................................................................................ 5-43
5.1.9 Network Startup .............................................................................. 5-46
5.1.10 Maintenance ................................................................................... 5-48
5.1.11 Directory Structure for the Fieldbus Engineering Tool ...................... 5-49
5.1.12 Configuration Procedure Using Fieldbus Engineering Tool .............. 5-52
5.2 Initial Settings of Fieldbus Engineering Tool .............................................. 5-54
5.2.1 Procedure for Initial Setting of the Fieldbus Engineering Tool .......... 5-55
5.2.2 Calling Project Manager .................................................................. 5-57
5.2.3 Setting Security .............................................................................. 5-59
5.2.4 Configuring Control Bus .................................................................. 5-61
5.2.5 Setting Environment ....................................................................... 5-62
5.2.6 Importing Capabilities Files and DD Files to System Database ....... 5-64
5.3 Setting Project and Fieldbus Device ............................................................ 5-68
5.3.1 Setting Procedure for the Project and Fieldbus Device .................... 5-69
5.3.2 Creating a New Project or Opening a Project .................................. 5-72
5.3.3 Importing Capabilities Files and DD Files to the Project Database .. 5-76
5.3.4 Importing Device Configuration Data to the Project Database ......... 5-78

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Toc-3
5.3.5 Calling Device Editor ...................................................................... 5-79
5.3.6 Display Device ID ........................................................................... 5-81
5.3.7 Registering a Device to the Project ................................................. 5-85
5.3.8 Calling Network Editor .................................................................... 5-88
5.3.9 Setting or Changing Network Parameters ....................................... 5-90
5.3.10 Changing Device Parameters ......................................................... 5-92
5.3.11 Upload to the Project Database ...................................................... 5-99
5.3.12 Updating Capability File and DD File ............................................. 5-102
5.3.13 Replace Fieldbus Device, Update Capability File and DD File ....... 5-104
5.4 Settings for FBAP ....................................................................................... 5-105
5.4.1 Procedure for Setting the FBAP .................................................... 5-106
5.4.2 Calling FB Editor ........................................................................... 5-109
5.4.3 Create a New or Open a FBAP Block Diagram .............................. 5-110
5.4.4 Placement of Function Blocks in the FBAP Block Diagram ............. 5-113
5.4.5 Connecting Function Blocks .......................................................... 5-118
5.4.6 Other Operations Related to Creating the FBAP Block Diagram ... 5-123
5.4.7 Setting Block Parameters ............................................................. 5-125
5.4.8 Generation of the FBAP Configuration .......................................... 5-131
5.4.9 Creating FBAP Schedule .............................................................. 5-134
5.4.10 Output Host File Set ...................................................................... 5-144
5.5 Project Startup ............................................................................................ 5-145
5.5.1 Project Startup Procedure ............................................................. 5-146
5.5.2 Opening or Importing a Project ..................................................... 5-149
5.5.3 Changing a Registered Device ID ................................................. 5-150
5.5.4 Advanced LM Settings .................................................................. 5-151
5.5.5 Executing Project Startup ............................................................. 5-152
5.5.6 Project Backup ............................................................................. 5-167
5.6 Fieldbus Engineering Tool Error Messages .............................................. 5-169
5.6.1 Project Manager Error Messages ................................................. 5-170
5.6.2 Export and Import Error Messages ............................................... 5-172
5.6.3 Download Error Messages ............................................................ 5-174
5.6.4 Upload Error Messages ................................................................ 5-182
5.6.5 Error Messages Regarding to Upgrading Capability File and
DD File ......................................................................................... 5-184
5.6.6 Error Messages Regarding to Display Device ID ........................... 5-185
5.6.7 Device Editor Error Messages ...................................................... 5-186
5.6.8 Network Editor Error Messages .................................................... 5-187
5.6.9 FB Editor Error Messages ............................................................. 5-188
5.6.10 Schedule Dialog Box Error Messages ........................................... 5-191
5.6.11 Parameter Dialog Box Error Messages ......................................... 5-192
5.6.12 Error Messages for Other Dialog Boxes ........................................ 5-193
5.7 Connecting DAQ Station ............................................................................ 5-194

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Toc-4
6. Device Management Tool ...................................................................... 6-1
6.1 Overview of Device Management Tool .......................................................... 6-2
6.1.1 What is Device Management Tool? ................................................... 6-3
6.1.2 Position of the Device Management Tool .......................................... 6-4
6.1.3 Operating Environment of Device Management Tool ........................ 6-7
6.1.4 Application Capacities of Device Management Tool .......................... 6-9
6.1.5 Functional Overview of Device Management Tool ........................... 6-10
6.1.6 Naming Rules in Device Management Tool ...................................... 6-11
6.1.7 Window Configuration of Device Management Tool ........................ 6-13
6.2 Security Settings of Device Management Tool ........................................... 6-15
6.2.1 User Registration ............................................................................ 6-16
6.2.2 Security Check ............................................................................... 6-18
6.3 Register and Display Device Tag List .......................................................... 6-19
6.3.1 Device Tag List Registration ............................................................ 6-20
6.3.2 Auto Setup ...................................................................................... 6-28
6.3.3 Device Tag List Display ................................................................... 6-30
6.4 Fieldbus Device Status Display ................................................................... 6-32
6.5 Fieldbus Device Parameter Display and Setting ......................................... 6-34
6.6 Run a Device Method .................................................................................... 6-40
6.7 Message Display ........................................................................................... 6-44
6.8 Operational History Display ......................................................................... 6-53
6.9 Event Display ................................................................................................ 6-55
6.10 Configuration of Control Bus ....................................................................... 6-59
6.11 Environment Setting ..................................................................................... 6-60
6.12 Maintenance .................................................................................................. 6-64
6.12.1 Creating Backup and Restoring Database ...................................... 6-65
6.12.2 Optimizing and Repairing Database ................................................ 6-66
6.12.3 Deleting Database .......................................................................... 6-67
6.13 Data Export .................................................................................................... 6-68
6.14 Printout .......................................................................................................... 6-69
6.15 On-line Help ................................................................................................... 6-70
6.16 Starting/Exiting Device Management Tool .................................................. 6-71
6.17 Login and Logout .......................................................................................... 6-72
6.17.1 Login .............................................................................................. 6-73
6.17.2 Logout ............................................................................................ 6-74
6.17.3 Setting and Changing Password ..................................................... 6-75
6.18 Common Window Operations ...................................................................... 6-76
6.18.1 Bookmark Operation ....................................................................... 6-77
6.18.2 Printing ........................................................................................... 6-79
6.18.3 Print Preview .................................................................................. 6-80

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Toc-5
6.19 Device Tag List Registration ........................................................................ 6-81
6.19.1 Registering by Accessing Host File Set ........................................... 6-82
6.19.2 Registering when Host File Set can not be Accessed ...................... 6-89
6.19.3 Registering by Auto Setup Command ............................................. 6-92
6.20 Device Tag List Display Operations ............................................................. 6-94
6.20.1 Device Tag List Table Display .......................................................... 6-95
6.20.2 Individual Device Tag Display ......................................................... 6-98
6.21 Fieldbus Device Status Display Operations .............................................. 6-100
6.22 Parameter Display/Change Operations ..................................................... 6-103
6.22.1 Displaying Parameters .................................................................. 6-104
6.22.2 Changing Parameters ................................................................... 6-108
6.23 Method Execution ........................................................................................ 6-112
6.24 Message Display Operations ...................................................................... 6-116
6.25 History Message Display Operations ......................................................... 6-119
6.26 Maintenance Operations ............................................................................ 6-121
6.27 Event Display .............................................................................................. 6-125
6.28 Configuring Control Bus ............................................................................ 6-127
6.29 Environment Setting for Device Management Tool .................................. 6-128
6.29.1 Specifying Directories and OPC Server ........................................ 6-129
6.29.2 Options ......................................................................................... 6-132
6.30 Security Specification ................................................................................. 6-133
6.30.1 Registering User Groups .............................................................. 6-134
6.30.2 Registering User ........................................................................... 6-137
6.31 Export Operations ....................................................................................... 6-139
7. Installation of Tools ................................................................................ 7-1
7.1 Installing Fieldbus Tools ................................................................................ 7-3
7.2 Uninstalling Fieldbus Tools .......................................................................... 7-20

Appendix A. Setting Security (Windows Vista) ..................................... App.A-1


Appendix B. Setting Security (Windows XP/Windows Server 2003) .... App.B-1
Appendix C. Installation of Control Bus Driver (Windows Vista) ......... App.C-1

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Blank Page
<1. Overview of Fieldbus Communication> 1-1

1. Overview of Fieldbus Communication


The fieldbus communication can be applied to the CENTUM VP/CS 3000/CS 1000 to
communicate with a field device using the fieldbus system. A fieldbus is a method of
communication for a field device in which digital signals make it possible to commu-
nicate in both directions. A system that uses a fieldbus is called a fieldbus system.
The CENTUM VP/CS 3000/CS 1000 positions the fieldbus system as a subsystem.
This chapter explains the configuration of the hardware and software for the fieldbus
system to give an overview of the fieldbus communication. It also explains the
CENTUM VP/CS 3000/CS 1000 system builders, Fieldbus Engineering Tool, Device
Management Tool, operation and monitoring function, as well as, the system mainte-
nance tools, which are necessary for the construction and operation of a fieldbus
system.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-2

1.1 What is Fieldbus?


The fieldbus is a bus type method of communication using digital signals to make it
possible to communicate in both directions that replaces the 4 to 20 mA analog
signal that was the earlier standard. By using the high level communication of the
fieldbus, optimized control can be performed by working in concert with the distrib-
uted control and control station (FCS) using the fieldbus device.

■ Communication Using Fieldbus


Communication using the fieldbus replaces the 4 to 20 mA analog communication and
hybrid communication that was the standard for the earlier instrumentation control system.
Large quantities of highly precise data can be transmitted by fieldbus communication, as
compared to the earlier communication method.
The control system that uses a fieldbus is called a fieldbus system. Also, field devices that
are connected to the fieldbus are generally referred to as fieldbus devices.
With the CENTUM VP/CS 3000/CS 1000, the fieldbus system is positioned as a subsystem
for using the fieldbus. The fieldbus is connected to the FCS via the fieldbus communication
module (ACF11 or ALF111). The ACF11 or ALF111 controls and monitors the communica-
tion status of the fieldbus.
Unlike the earlier analog signal, more than one fieldbus device can be connected to one
line with fieldbus communication. Fieldbus devices can communicate with each other in
both directions and because of this, self-distribution control can be performed. Moreover,
process information such as process data and system alarms generated by the fieldbus
can be collected by the FCS and referenced through HIS. Using sophisticated control and
calculation of the FCS, calculation results can be fed back to the fieldbus device. Fieldbus
devices also can be operated and monitored from the HIS via the FCS function block. This
enables the user to execute optimal control that meets with the condition of the system.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-3

1.2 Configuration of Fieldbus System


The fieldbus system consists of the HIS, general-purpose PC, FCS, ACF11, ALF111
and other hardware equipment. The fieldbus system can be configured with the
Fieldbus Engineering Tool installed either in the HIS or in the PC.

■ Overall Configuration of the Fieldbus System


The H1 fieldbus, a fieldbus designed to be intrinsically safe, is connected to the fieldbus
system.
The overall configuration of the fieldbus system is described below.

SEE ALSO
For information about configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, RFCS5 or RFCS2 (migration FCS2), see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-4
● When the Fieldbus Engineering Tool is Loaded into the HIS ¡
The Fieldbus Engineering Tool can be called from CENTUM CS 1000 system builders in
the HIS. This allows engineering in which the system builders and the Fieldbus Engineering
Tool are integrated.
Shown below is an example of an overall configuration of the fieldbus system.

Ethernet

• System builders HIS Master PC

• Operation and monitoring • Device Management Tool (*1)

• Fieldbus
Engineering Tool

Control bus
PFCS

PC connected
to H1 Fieldbus
• FieldMate
ACF11

H1 fieldbus

Fieldbus device Fieldbus device


010201E.EPS
*1: This tool can also be installed on the HIS.

HIS: Human Interface Station


Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
PFCS: Control Station
ACF11: Fieldbus Communication Module

Figure A System Configuration Where the Fieldbus Engineering Tool is Loaded in the HIS ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-5
● When the Fieldbus Engineering Tool is Loaded into the HIS £
The Fieldbus Engineering Tool can be called from CENTUM VP/CS 3000 system builders
in the HIS. This allows engineering in which the CENTUM VP/CS 3000 system builders and
the Fieldbus Engineering Tool are integrated.
Shown below is an example of an overall configuration of the fieldbus system.

Ethernet

HIS Master
• System builders
PC

• Operation and monitoring • Device Management Tool (*1)

• Fieldbus
Engineering Tool

Control bus
LFCS2/LFCS SFCS

FCU PC connected
to H1 Fieldbus
RIO bus
• FieldMate
NIU
ACF11
ACF11

H1 fieldbus

Fieldbus device Fieldbus device


010202E.EPS
*1: This tool can also be installed on the HIS.

HIS: Human Interface Station


Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
SFCS: Control Station (Compact Type)
LFCS2/LFCS: Control Station
FCU: Field Control Unit
RIO Bus: Remote Input/Output Bus
NIU: Node Interface Unit
ACF11: Fieldbus Communication Module

Figure A System Configuration Where the Fieldbus Engineering Tool is Loaded in the HIS £

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-6
● When the Fieldbus Engineering Tool is Loaded in the General-Purpose PC
¡
Engineering can be performed with the CENTUM CS 1000 system builders and the Field-
bus Engineering Tool installed in different machines. It is necessary to share the same disk
for storing data for the system builders and the Fieldbus Engineering Tool.
Shown below is an example of an overall configuration of a fieldbus system.

Ethernet

• System builders HIS Master PC


• Fieldbus Engineering Tool
• Operation and monitoring
• Device Management Tool (*1)

Control bus
PFCS

PC connected
to H1 Fieldbus

ACF11 • FieldMate

H1 fieldbus

Fieldbus device Fieldbus device


010203E.EPS
*1: This tool can also be installed on the HIS.

HIS: Human Interface Station


Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
PFCS: Control Station
ACF11: Fieldbus Communication Module

Figure A System Configuration Where the Fieldbus Engineering Tool is Loaded in the PC ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-7
● When the Fieldbus Engineering Tool is Loaded in the General-Purpose PC
£
Engineering can be performed with the CENTUM VP/CS 3000 system builders and the
Fieldbus Engineering Tool installed in different machines. It is necessary to share the same
disk for storing data for the system builders and for the Fieldbus Engineering Tool.
Shown below is an example of an overall configuration of the fieldbus system.

Ethernet

HIS PC
• System builders • Fieldbus Engineering Tool
• Device Management Tool (*1)
• Operation and
monitoring

Control bus
LFCS2/LFCS SFCS

FCU PC connected
to H1 Fieldbus
RIO bus
• FieldMate
NIU
ACF11
ACF11

H1 fieldbus

Fieldbus device Fieldbus device


010204E.EPS
*1: This tool can also be installed on the HIS.

HIS: Human Interface Station


Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
SFCS: Control Station (Compact Type)
LFCS2/LFCS: Control Station
FCU: Field Control Unit
RIO Bus: Remote Input/Output Bus
NIU: Node Interface Unit
ACF11: Fieldbus Communication Module

Figure A System Configuration Where the Fieldbus Engineering Tool is Loaded in the PC £

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-8

1.3 Component Equipment of Fieldbus System


This section explains each of the equipment, the FCS, HIS and PC, that make up the
fieldbus system.

■ Components of the Fieldbus System


The role of each equipment comprising the fieldbus system is explained below.

SEE ALSO
For information about configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

● Control Station (FCS)


This station performs instrumentation control for the entire plant including the fieldbus
system. It performs the role of an interface for CENTUM VP/CS 3000/CS 1000 with the
fieldbus devices via the fieldbus communication module (ACF11).

SEE ALSO
For details on the FCS hardware, see the followings:
CENTUM VP Field Control Stations (IM 33M50E40-40E)
CS 1000/CS 3000 Field Control Stations (IM 33Q06C20-01E)

● Human Interface Station (HIS)


This station performs engineering for the fieldbus communication module (ACF11) using
the CENTUM VP/CS 3000/CS 1000 system builders. It can also perform engineering
related to the communication and control of the fieldbus by using the Fieldbus Engineering
Tool.
Once the fieldbus system is running, the HIS uses the operation and monitoring functions
and the Device Management Tool to operate and monitor the function block (fieldbus block)
configured inside the fieldbus device.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-9
● General - Purpose Personal Computer (Mater PC)
The Fieldbus Engineering Tool and the fieldbus Device Management Tool can be installed
to a dedicated PC instead of an HIS for engineering work. This PC can perform engineering
related to the communication and control of the fieldbus by using the installed Fieldbus
Engineering Tool. It can also perform operation, monitoring and maintenance of the fieldbus
device by using the installed Device Management Tool. The PC connected to the control
bus is referred to as Master PC.
Also, information related to the fieldbus created by the Fieldbus Engineering Tool (host file
set) can be fetched to the HIS via Ethernet.

IMPORTANT
When the master PC is connected with CENTUM VP, the IT security settings in CENTUM
VP should be defined with Legacy model.
If the Fieldbus Engineering Tool and the Device Management Tool are installed in the HIS
of the CENTUM VP project, the IT security of entire CENTUM VP system can be defined
with Standard model.

SEE ALSO
For more information about the IT security settings of CENTUM VP, see the following:
CENTUM VP Installation (IM 33M01A20-40E)

● General-purpose PC Connected to H1 Fieldbus (PC Connected to H1 Field-


bus)
A general-purpose PC with FieldMate can be connected to H1 Fieldbus and used to define
the fieldbus physical device tag names and node addresses.

SEE ALSO
For more information about FieldMate, see the following:
FieldMate Versatile Device Management Wizard (IM 01R01A01-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-10

1.4 Fieldbus Hardware


This section explains the hardware comprising the fieldbus.

■ Fieldbus Hardware Configuration : PFCS/SFCS/LFCS2/LFCS ¡ £


The fieldbus is connected to the fieldbus communication module (ACF11) loaded into the
nest for I/O communication module (AMN33). And connected with the hardware compo-
nents configured on the fieldbus. This section explains the fieldbus configuration in the filed
side from AMN33.

AMN33 and ACF11


When using the ACF11
power supply

Terminator

External bus Safe area


power supply Hazardous area
Barrier/
arrester
Terminator Coupler Coupler Coupler Terminator
Cable

When not using the ACF11 Fieldbus device


power supply
010401E.EPS

Figure Configuration of Hardware for AMN33 and under in the Fieldbus

TIP
The power supply and each device requires protective grounding (with 100 ohms or less). However, the
barrier is based on the specified standard.

● Nest for the Communication Module (AMN33)


Use the nest for I/O communication modules (AMN33) manufactured by Yokogawa. Up to
two ACF11 can be loaded into the AMN33.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<1. Overview of Fieldbus Communication> 1-11
● Fieldbus Communication Module (ACF11)
Use the fieldbus communication module (ACF11) manufactured by Yokogawa. The ACF11
has a link active scheduler (LAS) function and controls the fieldbus communication sched-
ule.
It also relays data between the FCS and fieldbus device. If an error occurs in the fieldbus
device of the ACF11 itself, an alarm is notified to the HIS via FCS.
Also, power can be supplied from the ACF11 to the fieldbus device.

SEE ALSO
For more information about the ACF11, see the following:
2, “Fieldbus Communication Module”

● Cable
Select the cable from the wiring materials indicated below according to the environment in
which the cable is to be installed.
• Type A (individually sheathed twisted pair cable)
• Type B (group sheathed twisted pair cable)
• Type D (group sheathed non-twisted pair cable)

SEE ALSO
For more information about the cable to install, see the following:
“■ Cable Used in the Fieldbus” in 2, “Fieldbus Communication Module”

● Barrier
This is a device that shuts down the power supply so that excessive power is not supplied
to the fieldbus. Install a barrier when an intrinsically safe circuit is required. The barrier acts
as the border and the bus power supply on the fieldbus side is called the safe side while the
side opposite is called the danger side.
The number of fieldbus devices that can be connected when a barrier is installed is about
up to 4 on the danger side and up to 2 on the safe side. However, the number of connected
fieldbus devices will vary somewhat depending on the current consumption for the fieldbus
device connected to the danger side and the standards of the barrier installed.

● Arrester
This is a device that discharges the excess voltage impulse wave to the ground when an
excess voltage impulse wave is generated due to a thunderbolt or other cause.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<1. Overview of Fieldbus Communication> 1-12
● External Bus Power Supply
This is the power supply specifically for the fieldbus that supplies power to the fieldbus
device. Connect an external bus power supply if the total amount of current consumed by
the connected fieldbus device exceeds the capacity that can be supplied by the ACF11
internal bus power supply (80 mA). However, when an external bus power supply is used,
the ACF11 internal bus power supply can no longer be used. In this case, set the output of
the ACF11 internal bus power to OFF.
Also, a signal decoupling circuit is built into the external bus power supply.

TIP
• The guideline regarding the number of fieldbus devices to which the ACF11 internal bus power
supply capacity (80 mA) can supply power is normally up to 6 devices. Even if there are less than 6
devices, an external bus power supply is necessary if the 80 mA is exceeded.
• The decoupling circuit refers to a circuit that prevents the signal from attenuating because of effects
from the power supply. Generally, when the power supply device output impedance is low and signals
are superimposed in the communication line, the signal is considerably attenuated. To prevent
attenuation of the signal, it is necessary to raise the impedance with respect to the communication
carrier. The decoupling circuit inserts a coil between the power supply and communication line or
uses the power supply device itself to raise the impedance with respect to the communication carrier.
Also, in the case of the ACF11, it manages using the power supply device itself.

● Terminator
The terminator is a device that is installed to adjust the network.
Model YCB138 can be used as the terminating device for the ACF11. Connect the terminat-
ing device to both ends of the fieldbus.

● Coupler
This is the tool for connecting the fieldbus device to the communication cable.
Using a coupler makes it easy to install and maintain the fieldbus device.

● Fieldbus Device
This a fieldbus device such as a transmitter or positioner.
As long as the device is Fieldbus Foundation compliant and passed the ITK4.0X test the
device from any manufacturer can be connected.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<1. Overview of Fieldbus Communication> 1-13
■ Fieldbus Hardware Configuration : KFCS2/KFCS/FFCS/RFCS5/RFCS2
£
The fieldbus is connected to the fieldbus communication module (ALF111) loaded into
FCS. And connected with the hardware components configured on the fieldbus. This
section explains the fieldbus configuration in the field side from ALF111.

Fieldbus power
supply unit ALF111

Terminator

(*1)
Safe area
Hazardous area
Barrier/
Arrester
Coupler Coupler Coupler Terminator
Cable

Fieldbus device
010402E.EPS
*1: Make sure to install a terminator if ALF111 terminates the network, e.g. if the network is not terminated by a power
supply unit with terminator.
• If a pressure clamp terminal block is used on ALF111, the built-in terminator of the terminal block should be set ON
so as to terminates the network.
• If ALF111 is connected with a terminal board through a connector, a terminator (Model: YCB138) should be
connected to the terminal board.

Figure Configuration of Hardware for ALF111 and under in the field

● Fieldbus Communication Module (ALF111)


Fieldbus communication module ALF111 behaves as a Link Active Scheduler (LAS) to
control the communication on the fieldbus. It also passes data between field devices and
FCS.

SEE ALSO
For more information about ALF111, see the follwings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-14
● Cables
The following types of cables can be chosen in accordance with fieldbus installation envi-
ronment.
• Type A Each twisted pair has a shield
• Type B Multiple twisted pairs with overall shield
• Type D Multiple conductor cable, no pairing of wires

SEE ALSO
For more information about Fieldbus wiring cables, see the following:
“■ Cable Used in the Fieldbus” in 2, “Fieldbus Communication Module”

● Barrier
Barrier is a device to keep the Fieldbus power supply under a certain level to prevent from
igniting the hazardous atmosphere. The intrinsic safety barriers are installed to isolate safe
area and hazardous area. For a Fieldbus system, the Fieldbus power supply is in the safe
side of the barrier, while the other side of the barrier is hazardous area.
If intrinsic safety barrier is used on a Fieldbus, generally, the number of devices is two on
safe side and four on hazardous side. However, the number of devices on hazardous side
varies with the current consumption of the Fieldbus devices and type of barriers.

● Arrester
It is a protective device to reduce the excessive voltage resulting from lightning to a safe
level by grounding the discharge.

● Fieldbus Power Supply Unit


It is a specific power supply unit for providing power to Fieldbus devices via the Fieldbus.

● Terminator
The terminator is a device that is installed to adjust the network.

● Coupler
This is the tool for connecting the fieldbus device to the communication cable. Using a
coupler makes it easy to install and maintain the fieldbus device.

● Fieldbus Devices
The field devices such as transmitters and positioners that complaint to Foundation Field-
bus specifications. All the devices passed the interoperability tests (ITK version 4.0 or later)
can be used regardless the maker of the devices.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-15

1.5 Software for Configuring a Fieldbus System


This section explains the software for configuring a fieldbus system. The software
for FCS control, operation and monitoring, system builders and Fieldbus Engineer-
ing Tool are necessary to configure a fieldbus system. A Device Management Tool is
provided to improve the operation and monitoring as well as maintenance for the
fieldbus device.

■ Summary of Software for Configuring a Fieldbus System


The software used in configuring a fieldbus system is summarized in the table below.

SEE ALSO
For information about configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

Table Summary of Software for Configuring a Fieldbus System


No. Item Hardware Remarks Necessity
Exaopc OPC interface package (for HIS) is
Operation and 
1 HIS required for displaying messages when using
monitoring function
Device Management Tools.
Foundation Fieldbus Communication Package
2 System builders HIS 
is required.
3 FCS control function FCS 
4 Fieldbus Engineering Tool HIS or PC 
5 Device Management Tool PC 
010501E.EPS

: Required
: Helps to improve function

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-16

1.6 Fieldbus System Engineering


The system builders and Fieldbus Engineering Tool are used in engineering for the
fieldbus system. Configuration information for the fieldbus device and fieldbus block
are defined in the Fieldbus Engineering Tool. With the system builders, engineering
for the supervisory system including the ACF11 is performed based on the informa-
tion defined by Fieldbus Engineering Tool.

■ Position of Fieldbus System Engineering


The position of fieldbus system engineering relative to the flow of overall system is indi-
cated below

System design

Creation of I/O list

Selection of
Control loop design Construction
fieldbus devices

Using FieldMate to configure


Engineering with the Engineering with the
tag name and node address
system builders fieldbus engineering tool
of Physical Device. (*1)

Individual device
setting

On-line Legend
debug/loop check
Work flow
Flow of output information

Receive Fieldbus system engineering

Application/service
010601E.EPS
*1: When the following condition is satisfied, the engineering work by FieldMate on the PC connected to H1 fieldbus is not
required.
The physical device tag names and node addresses already configured in the field devices.

The tag names and node addresses for physical devices can also be configured using Fieldbus Engineering Tool.

Figure Position of Fieldbus System Engineering

Before performing fieldbus system engineering, the processes indicated below must be
completed and output information for those processes be prepared.
• Control loop design: output information is [Control loop design plans]
• Selection of fieldbus devices: output information is [List of fieldbus devices to be used]

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-17
■ Fieldbus System Engineering
The fieldbus system engineering is a general term for using the system builders related to
the fieldbus for the fieldbus engineering.

SEE ALSO
For information about configuring Fieldbus communication module (ALF111), see the follwings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

● System Builders
Using system builders such as IOM Builder on System View can configure ACF11
I/O module.
When downloading the contents defined on the IOM Builder to the ACF11 module, the data
defined by the Fieldbus Engineering Tool can be obtained by fetching the host file set.

SEE ALSO
For more information about the fieldbus related CENTUM VP/CS 3000/CS 1000 system builders, see the
following:
4, “System Builders Related to Fieldbus”

● Fieldbus Engineering Tool


The Fieldbus Engineering Tool is used to perform configuration for the fieldbus device,
fieldbus block and fieldbus communication setup. The Fieldbus Engineering Tool on HIS or
the master PC may download configured data to the ACF11 and fieldbus devices.

SEE ALSO
For more information about the Fieldbus Engineering Tool, see the following:
5, “Fieldbus Engineering Tool”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-18
● Target Scope of Fieldbus System Engineering
In fieldbus system engineering, the engineering target scope differs from the CENTUM VP/
CS 3000/CS 1000 system builders and the Fieldbus Engineering Tool.
The engineering target scope for the system builders and the Fieldbus Engineering Tool is
indicated below.

HIS

Control bus

Engineering section of
system builders
FCS FCS

ACF11

Engineering section for


Fieldbus Fieldbus fieldbus engineering tool
device device
function function
010602E.EPS

Figure Scope of Fieldbus System Engineering

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-19
● Download Destination and Upload Destination
It is necessary to download the information defined in the fieldbus system engineering to
the fieldbus device and the ACF11. Also, the data defined by the fieldbus device can be
uploaded to the Fieldbus Engineering Tool.
The download destination and upload destination in fieldbus system engineering are
indicated in the following diagram.

System builders Fieldbus engineering tool

Project
System Start manager
View
Network
IOM Maintenance
startup
builder function
function

Download

HIS Download
IOM download

Download

FCS

Upload

ACF11

Fieldbus Fieldbus
device device

010603E.EPS

Figure Download Destination and Upload Destination in Fieldbus System Engineering

TIP
• Download or upload between the Fieldbus Engineering Tool and the fieldbus devices is done via the
FCS and ACF11.
• When the Fieldbus Engineering Tool and system builders are installed in different machines, a control
bus interface card is required to be installed to the master PC where the Fieldbus Engineering Tool is
applied for downloading and uploading.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-20
■ Fieldbus System Engineering Format ¡ £
The engineering may be performed differently when the system builders and Fieldbus
Engineering Tool are applied in the same machine or in different machines, and the fieldbus
system engineering method will differ depending on this difference.

● When HIS is Installed with Fieldbus Engineering Tool ¡


When using the system builders and Fieldbus Engineering Tool in the same machine, the
Fieldbus Engineering Tool can be started from system builders, IOM Builder. Also, data
defined with the Fieldbus Engineering Tool is saved under the directory specified in System
View.

Ethernet

HIS
• CENTUM CS 1000 System builders

• Fieldbus Engineering Tool

Control bus
PFCS

ACF11

H1 fieldbus

Legend
Downloading channel

010604E.EPS

Figure Engineering Format When Performed in the Same Machine ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-21
● When HIS is Installed with Fieldbus Engineering Tool £
When using the system builders and Fieldbus Engineering Tool in the same machine, the
Fieldbus Engineering Tool can be started from system builders IOM Builder. Also, data
defined with the Fieldbus Engineering Tool can be created under the directory specified in
System View.

Ethernet

HIS
• CENTUM VP/CS 3000 System builders

• Fieldbus Engineering Tool

Control bus

LFCS2/LFCS SFCS

FCU

ACF11
ACF11

H1 fieldbus

Legend
Downloading channel

010605E.EPS

Figure Engineering Format When Performed in the Same Machine £

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-22
● When General-Purpose PC is Installed with Fieldbus Engineering Tool ¡
When the CENTUM CS 1000 system builders and the Fieldbus Engineering Tool are
installed in different machines, downloading to the fieldbus devices will be performed from
the Fieldbus Engineering Tool on the master PC. ACF11 data will be downloaded from the
system builders in the HIS.
It is required to designate a directory on the system builders of System View for holding the
data of Fieldbus Engineering Tool. This directory should be shared by HIS and master PC.

Ethernet
Master
HIS PC
CENTUM CS 1000
Fieldbus Engineering Tool
System builders

Control bus

PFCS

ACF11

H1 fieldbus

Legend
Downloading channel

010606E.EPS

Figure Engineering Performed in Different Machines ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-23
● When General-Purpose PC is Installed with Fieldbus Engineering Tool £
When the CENTUM VP/CS 3000 system builders and the Fieldbus Engineering Tool are
installed in different machines, downloading to the fieldbus devices will be performed from
the Fieldbus Engineering Tool on the master PC. ACF11 data will be downloaded from the
system builders in the HIS.
It is required to designate a directory on the system builders of System View for holding the
data of Fieldbus Engineering Tool. This directory should be shared by HIS and master PC.

Ethernet
Master
HIS PC
CENTUM VP/CS 3000
Fieldbus Engineering Tool
System builders

Control bus

LFCS2/LFCS SFCS

FCU

ACF11
ACF11

H1 fieldbus

Legend
Downloading channel

010607E.EPS

Figure Engineering Performed in Different Machines £

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-24

1.7 Device Management


The Device Management Tool provides device management service for operating
and monitoring the fieldbus devices. The Device Management Tool runs on HIS or
master PC.

■ Operation and Monitoring of Fieldbus Device with Device


Management Tool
The Device Management Tool runs on HIS or master PC. It can also change the param-
eters for the fieldbus block when required. It provides additional fieldbus device operation
and monitoring functions to the HIS, it is also useful for maintaining the fieldbus devices.

SEE ALSO
For more information about the Device Management Tool, see the following:
6, “Device Management Tool”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-25

1.8 Operation and Monitoring


Parameters for the fieldbus block are assigned beforehand to the terminal number of
the fieldbus communication module (ACF11) and this terminal number is connected
to the faceplate block. This allows an operator to run and monitor the fieldbus device
using the HIS operation and monitoring window.

SEE ALSO
For information about configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

■ Overview of Operation and Monitoring


The HIS operation and monitoring window can be used to perform the following operation
and monitoring.
• The internal parameters for the fieldbus block (diagnostic data, etc.) can be displayed.
• Using the same operation as in the case of the FCS function block, parameters for the
fieldbus block can be adjusted.
• Error alarms arising from a failure of the fieldbus device and device alarms automati-
cally generated from the fieldbus device (IO failure) can be constantly monitored.

■ Display and Revision of Parameters Assigned to the Terminal Number


It is necessary to assign the fieldbus block parameters to a corresponding terminal number
(%Znnusmm) with the system builders in order to display or change the fieldbus block
parameters on operation and monitoring console. By connecting this terminal number for
which assignment has been completed to the faceplate block, the fieldbus block param-
eters can be displayed or changed using the HIS operation and monitoring windows (tuning
window, graphic window, trend window, etc.). The fieldbus block parameters cannot be
displayed or changed unless the terminal number is connected to the faceplate block.

TIP
• The external I/O terminal parameters for the fieldbus block can be displayed only with the operation
and monitoring window after the terminal number is connected to an FCS function block other than
the faceplate block. The parameters cannot be changed.
• Parameters that have not been assigned to a terminal number are displayed or changed using the
parameter display and setting function for the device management tool.

● Tuning Window
The fieldbus block parameters can be changed in the tuning window. To do this, the face-
plate block connected to the terminal number corresponding to the fieldbus block param-
eters is assigned to the tuning window and the parameters are changed in relation to that
faceplate block.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-26
● Graphic Window
The fieldbus block parameters can be displayed in the graphic window. After connecting
the terminal number corresponding to the fieldbus block parameters to an FCS function
block such as the PVI, the FCS function block tag is assigned to the graphic window.

● Trend Window
The fieldbus block parameters can be displayed in the trend window. After connecting the
terminal number corresponding to the fieldbus block parameters to an FCS function block
such as the PVI, the FCS function block tag is assigned to the trend window.

■ Historical Message Report Window


The fieldbus messages (alarms and events) are displayed in the historical message report
window.

Historical Report - [Operation and Monitoring Message]


File Edit View Window Help

STOP

Message No Date Message Text


1401 08/06/16 08:05:14 PM PID040301 ************************ MAN
0040 08/06/16 08:05:14 PM FCS0104 PID040301 Normal from PI/O not Ready
1106 08/06/16 08:05:14 PM PID040301 ************************ NR
1102 08/06/16 08:05:14 PM PID040301 ************************ PV =0.000000 **** CNF Recover
1102 08/06/16 08:05:14 PM PID040301 ************************ PV =0.000000 **** IOP Recover
1104 08/06/16 08:05:14 PM PID040301 ************************ MV =74.000000 **** OOP Recover
1101 08/06/16 08:05:06 PM PID040301 ************************ PV =0.000000 **** CNF
0471 08/06/16 08:05:06 PM FCS0104 Online Download Complete
1101 08/06/16 08:04:19 PM PID040301 ************************ PV =0.000000 **** IOP
1102 08/06/16 08:04:19 PM PID040301 ************************ PV =0.000000 **** CNF Recover
0039 08/06/16 08:04:19 PM FCS0104 PID040301 IN PI/O not Ready
0089 08/06/16 08:04:18 PM FCS0104 SS-COM Error UNIT 04 SLOT 01 STN001 CODE= A3D2
1401 08/06/16 08:04:12 PM PID040301 ************************ MAN IMAN
Ready 33Items Found
010801E.EPS

Figure Historical Message Report Window

TIP
When the CAMS for HIS is enabled, the fieldbus messages are displayed in the Historical Viewer of
CAMS for HIS.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-27
■ Message Monitor Window
Fieldbus messages (message nos. 3xxx) are displayed in real time. Also, the types of
messages to be displayed can be specified in the message registration dialog box. Mes-
sage filtering function is operative in message monitor window.

SEE ALSO
For details on messages displayed in the message monitor window, see the followings:
CENTUM VP Operating Messages (IM 33M05D20-40E)
CS 1000/CS 3000 Operating Messages (IM 33S02H10-01E)

Message Monitor

Header Message

1 3001 2008/06/16 17:10:14 FCS01 FB RIO1 NODE 01 UNIT 01 SLOT 01 Device Error

2 3002 2008/06/16 15:03:22 FCS01 FB RIO1 NODE 01 UNIT 02 SLOT 01 Device Recover

Ready range: All 2/2


010802E.EPS

Figure Message Monitor Window

● Message Registration Dialog Box


The items indicated below can be specified in the message registration dialog box.
• Number of messages to be retained in the window
• Type of messages to be displayed
• Color of messages to be displayed

Message Registration

Maximun Number Of Line: 200


Color
Sequence Messages White

Operation Messages White

Field Bus Messages White

All Messages White

Details

OK Cancel Apply

010803E.EPS

Figure Message Registration Dialog Box

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-28

1.9 System Maintenance


The system maintenance function refers to the function that displays the status of
the ACF11 in the system status overview window, or displays an ACF11 error as a
system alarm message.

SEE ALSO
For information about configuring Fieldbus communication module (ALF111), see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

■ System Status Overview Window


The status of the ACF11 is displayed in the system status overview window.

■ System Alarm Message Display : PFCS/SFCS


When an error occurs in the ACF11, a system alarm message is displayed. Messages
generated by other devices are also displayed. A list of the system alarm messages that
are displayed is given below.
Table List of ACF11 Related System Alarm Messages : PFCS/SFCS
Message
Alarm message
number
0081 STNxx IOM Fail UNIT xx SLOT xx
0082 STNxx IOM Recover UNIT xx SLOT xx
0083 STNxx IOM Configuration Error UNIT xx SLOT xx
0085 STNxx IOM Communication Error UNIT xx SLOT xx
010901E.EPS

■ System Alarm Message Display : LFCS2/LFCS £


When an error occurs in the ACF11, a system alarm message is displayed. Messages
generated by other devices are also displayed. A list of the system alarm messages that
are displayed is given below.
Table List of ACF11 Related System Alarm Messages : LFCS2/LFCS £
Message
Alarm message
number
0081 STNxx IOM Fail RIOx NODE xx UNIT xx SLOT xx
0082 STNxx IOM Recover RIOx NODE xx UNIT xx SLOT xx
0083 STNxx IOM Configuration Error RIOx NODE xx UNIT xx SLOT xx
0085 STNxx IOM Communication Error RIOx NODE xx UNIT xx SLOT xx
010902E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-29

1.10 Glossary
This manual uses the terms given below in addition to basic terminology. Refer to
this list as necessary.

■ ACF11
ACF11 is a Fieldbus communication module.
ACF11 can be installed in a PFCS, SFCS, LFCS2 or LFCS field control station for Founda-
tion Fieldbus H1 communication.

■ ALF111
ALF111 is a Fieldbus communication module.
ALF111 can be installed in a KFCS2, KFCS, FFCS, RFCS5 or RFCS2 filed control station
for FOUNDATION fieldbus H1 communication.

■ Common File Format


This is the name of the format for the files (Capabilities File, Configuration File) for informa-
tion exchange used in fieldbus engineering and the specifications that prescribe that
format.

■ DDL (Device Description Language)


This is the description language for describing the device configuration elements and the
specifications of that language.

■ DD (Device Description) File


The source of a DD file is written in DDL. After the source file is compiled by Tokenizer, a
program for making object file, the DD file of a device is created. The DD files of various
Fieldbus devices can be downloaded from web site of Fieldbus Foundation
(www.fieldbus.org).

■ DDOD (Device Description Object Dictionary)


This is the object file in which the DD source described using DDL has been compiled
using the software called Tokenizer. Specifications for the device function resources are
described in the DD source.

■ FB Pool
This is where the block resources that all of the devices in the project are stored. This is
created in the project database at the time the devices are registered using the Device
Editor (device editing function) of the fieldbus engineering tool.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<1. Overview of Fieldbus Communication> 1-30
■ LAS (Link Active Scheduler)
This is the function that controls the fieldbus communication schedule. Only one device
with the LAS function exists in a network for a single segment.

■ MIB (Management Information Base)


This is a general term for the network and system management information database that
each device has.

■ Network Management (NM)


This is the name of the communication protocol for network configuration management and
statistical management. The Network Management client is called the network manager
(NMgr) and the server is called the network management agent (NMA). The fieldbus
engineering tool corresponds to NMgr.

■ System Management (SM)


This is the name of the protocol that directs the operation of the various fieldbus devices
distributed in the fieldbus. System management includes the physical device tag assign
function, address assign function, time synchronization function and the function block
scheduling function.

■ VCR (Virtual Communication Relationship)


Configured application layer channels that provide for the transfer of data between Fieldbus
device applications.

■ VFD (Virtual Field Device)


This is a logical device and there are multiple copies inside the fieldbus device. A single
VFD includes multiple function block application configuration elements.

■ Alert
The messages initiated from the Fieldbus devices for the upper level system (such as
CENTUM VP/CS 3000/CS 1000) including the alarm messages and the event messages.

■ Export/Import
Export outputs configuration data for the fieldbus in accordance with the Common File
Format so that it can be used in a variety of media. Import means to import a configuration
data file that has been described in a format that follows the Common File Format, to the
project database from external media.

■ Extended Parameters
In a Fieldbus function block, other than the parameters stipulated by FOUNDATION
fieldbus, the device vendor specific parameters are referred to as extended parameters.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-31
■ Capabilities File
A Capability File describes the communication objects in a Fieldbus device. It is a text file
that contains the resource information, the capabilities, default settings and index informa-
tion of the device. The information in the capability file is indispensable when performing
offline configuration.
In general, each model of device requires one capability file. The capability files can be
downloaded from web site of Fieldbus Foundation (www.fieldbus.org).

■ Configuration Data File (Value File)


This is the text file that describes information for downloading to the fieldbus device or link
master device. Download means to read the configuration data file. The configuration data
file is described according to the Common File Format.

■ Scheduling Function
This is the function for creating the schedule that prescribes the execution timing for peri-
odic communication and the function block. The schedule can be created off-line.

■ Segment
A Segment is a section of an H1 Fieldbus that is terminated in its characteristic impedance.
Each Segment can include H1 devices and an ACF11 or an ALF111 Fieldbus communica-
tion module.

■ Terminal Number
This is the numbered software terminal (%Znnusmm) for identifying FCS process I/O. This
is used instead of using the tag name. I/O terminal data or internal parameters for the
fieldbus block can be treated as process I/O for the FCS function block. In this case, the
correlation between the two can be defined with CENTUM VP/CS 3000/CS 1000 system
builders.

■ Communication and FB Schedule


This refers to the execution timing for periodic communication and the function block
determined beforehand.

■ Device Pool
Device pool is a location for keeping the DD (Device Description) files and capability files
provided by device vendors. The DD files can be downloaded from vendors' web sites or
from Fieldbus Foundation web site (http://www.fieldbus.org).

■ Trend Object
Trend object is an object for keeping a Fieldbus function block short-term trend data locally.

■ View Object
View object is an object for viewing and storing the Fieldbus device static and dynamic
parameters such PV, scale high and low limit values

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<1. Overview of Fieldbus Communication> 1-32
■ Standard Block Parameters
In a Fieldbus function block, the parameters stipulated by FOUNDATION fieldbus are
referred to as Standard Block Parameters.

■ Function Blocks
Function Blocks (FBs) are built into Fieldbus devices to achieve the desired control func-
tionality such as PID or AI. In this document the function blocks are also referred to as
Fieldbus function blocks.

■ Fieldbus Device
This is the general term for field devices connected to the fieldbus, such as a transmitter or
positioner that has a fieldbus communication function.

■ Fieldbus Block
This is the general term for the function block of the fieldbus device. The resource block,
function block and transducer block corresponds to the function of fieldbus. One resource
block is always installed in the fieldbus device. The function block and transducer block are
installed as necessary.
When something is called a fieldbus block in this manual, it refers to a function block. When
using FCS function block, this refers to a function block for the FCS.

■ Fieldbus Block I/O Terminal


This is the I/O terminal (Input terminal, Output terminal) for the fieldbus device function
block.

■ Host File Set


This is a set of information for the fieldbus configuration that is necessary to the application
(host application) of Device Management Tool and CENTUM VP/CS 3000/CS 1000 system
builders .

■ Host Application
Host means the DCS or PC controller. Host application is the general term for the applica-
tion that operates in the DCS or PC controller.

■ Macro Cycle
A macro cycle is a period that all function blocks are executed, and all operational traffic is
passed during the macro cycle. The synchronous and asynchronous communications are
scheduled in LAS according to the macro cycle.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<2. Fieldbus Communication Module> 2-1

2. Fieldbus Communication Module


The fieldbus communication module (ACF11) has the function to control 1 segment
of fieldbus using a communication method specific to the fieldbus. The ACF11 is
installed in the nest for I/O communication modules. Also, there is an upper limit to
the number of fieldbus devices that can be connected to the fieldbus, and when
connecting, it is necessary to select the appropriate cable.

SEE ALSO
For information about the Fieldbus communication module (ALF111), see Fthe follwings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

■ Fieldbus Communication Method


The fieldbus communication module (ACF11) has the function to control 1 segment of the
fieldbus (one bus segment) using the communication method specific to the fieldbus
(fieldbus communication). Compared to the earlier used 4 to 20 mA analog communication
method and hybrid communication method, this method has the following superior charac-
teristics.
• Multiple fieldbus devices can be connected to a single fieldbus cable
• Communication is performed with digital signals
• Large quantities of multiple data can be transmitted by a communication method that
is based on dual directions and multiple signals.

Further, the fieldbus communication method solves problems that occurred with the hybrid
communication method, such as, the slow speed of the digital transmission and low level of
inter-operability with fieldbus devices of other manufacturers.

■ Work Required Before Installing the ACF11 to the IOM Nest


Before installing the ACF11 to the IOM nest, use the worksheet given in this manual,
ACF11 device ID management table, and register the device ID for the ACF11. When
downloading from the Fieldbus Engineering Tool to the ACF11, set the physical device tag
name and device ID for the ACF11, which is the download target in the Fieldbus Engineer-
ing Tool. Refer to the ACF11 device ID management table to set the device ID when per-
forming this procedure.

SEE ALSO
On how to set the device ID in the Fieldbus Engineering Tool, see the following:
5.5.3, “Changing a Registered Device ID”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<2. Fieldbus Communication Module> 2-2
Table ACF11 Device ID Management Table
System Node numbers Unit Slot
No. FCS station name ACF11 device ID
(1 or 2) (1 to 8) numbers numbers
1 1 1 5945431001:ACF11-
2 2 5945431001:ACF11-
3 2 1 5945431001:ACF11-
4 2 5945431001:ACF11-
5 3 1 5945431001:ACF11-
6 2 5945431001:ACF11-
7 4 1 5945431001:ACF11-
8 2 5945431001:ACF11-
9 5 1 5945431001:ACF11-
0 2 5945431001:ACF11-
1 1 1 5945431001:ACF11-
2 2 5945431001:ACF11-
3 2 1 5945431001:ACF11-
4 2 5945431001:ACF11-
5 3 1 5945431001:ACF11-
6 2 5945431001:ACF11-
7 4 1 5945431001:ACF11-
8 2 5945431001:ACF11-
9 5 1 5945431001:ACF11-
0 2 5945431001:ACF11-
1 1 1 5945431001:ACF11-
2 2 5945431001:ACF11-
3 2 1 5945431001:ACF11-
4 2 5945431001:ACF11-
5 3 1 5945431001:ACF11-
6 2 5945431001:ACF11-
7 4 1 5945431001:ACF11-
8 2 5945431001:ACF11-
9 5 1 5945431001:ACF11-
0 2 5945431001:ACF11-
1 1 1 5945431001:ACF11-
2 2 5945431001:ACF11-
3 2 1 5945431001:ACF11-
4 2 5945431001:ACF11-
5 3 1 5945431001:ACF11-
6 2 5945431001:ACF11-
7 4 1 5945431001:ACF11-
8 2 5945431001:ACF11-
9 5 1 5945431001:ACF11-
0 2 5945431001:ACF11-
020001E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<2. Fieldbus Communication Module> 2-3
■ Installing Fieldbus Communication Module : PFCS/SFCS
Up to two ACF11 can be installed in the nest for I/O communication modules (AMN33).
Also, up to five AMN33 can be connected for one FCS.
One ACF11 can control per segment of fieldbus. A maximum of 10 segments can be
controlled in one FCS.

Nest for I/O communication modules Fieldbus


(model AMN33) communication module
(model ACF11)

Insert LED

Terminator
(model YCB138)

Terminal block
(can be removed)

To the fieldbus device


020002E.EPS

Figure Installing the ACF11 in the Nest for I/O Communication Modules : PFCS/SFCS

IMPORTANT
When one ACF11 is installed in the AMN33, a communication module other than the
ACF11 (ACM11 or ACM12) cannot be installed as another communication module.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<2. Fieldbus Communication Module> 2-4
■ Installing Fieldbus Communication Module : LFCS2/LFCS £
Up to two ACF11 can be installed in the nest for I/O communication modules (AMN33).
Also, up to forty AMN33 can be connected for one FCS. One ACF11 can control per seg-
ment of fieldbus. A maximum of 80 segments can be controlled in one FCS. This cannot be
used in the RIO bus system 2.

Nest for I/O communication modules Fieldbus


(model AMN33) communication module
(model ACF11)

Insert LED

Terminator
(model YCB138)

Terminal block
(can be removed)

To the fieldbus device


020003E.EPS

Figure Installing the ACF11 in the Nest for I/O Communication Modules : LFCS2/LFCS £

IMPORTANT
When one ACF11 is installed in the AMN33, a communication module other than the
ACF11 (ACM11 or ACM12) cannot be installed as another communication module.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<2. Fieldbus Communication Module> 2-5
■ The Number of Connected Fieldbus Devices ¡ £
The number of fieldbus devices that can be connected per 1 segment is 32 including the
ACF11. However, it is necessary to determine the number of fieldbus devices to be con-
nected based on the capacity of power that can be supplied from the power supply. Also,
the more fieldbus devices connected, the longer the fieldbus communication and control
cycles. Accordingly, it is necessary to limit the number of connected fieldbus devices in
order to obtain the expected communication and control cycle.
The table below indicates the number of fieldbus devices that can be connected per 1
segment.
Table Number of Connected Fieldbus Devices
Connected Maximum devices
With Barrier Remarks
device type connected per 1 segment

Self Power supply No 32 (*1)

Bus Power supply No 12 Guideline for number of devices to which


power can be supplied by the ACF11 built-in
bus power supply is up to 6.External bus power
Bus Power supply Yes 6 (*2) supply is required , if more than six devices are
connected.
020004E.EPS

*1: This value includes all devices connected in the fieldbus. Thus, in addition to the fieldbus devices, the ACF11, Hand
Held Terminal, etc. are counted as devices.
*2: Generally, up to 4 devices can be connected to the danger side and up to 2 devices to the safe side.

● Number of Connected Devices in Consideration of the Power Consump-


tion
When using the ACF11 built-in bus power supply, the number of fieldbus devices connected
to the segment should be such that the power consumption amount is 80 mA or less. As a
guideline, the number of fieldbus devices to which power can be supplied by the ACF11
built-in bus power supply is up to six. To connect more than this number of fieldbus devices
will require an external bus power supply. Also, when an external bus power supply is used,
the ACF11 built-in bus power supply cannot be used.

● Number of Connected Devices in Consideration of the Communication


and Control Cycles : PFCS/SFCS
The fieldbus communication and control cycles are determined according to the number of
connected fieldbus devices. When the total number of fieldbus devices connected to 1
segment exceeds the fieldbus capacity, the expected communication and control cycles
cannot be obtained in that segment. For example, to make the dead time for the process 2
seconds or less when the FCS control cycle is the standard cycle of 1 second, the guideline
for the number of I/O points per 1 segment is 16.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<2. Fieldbus Communication Module> 2-6
● Number of Connected Devices in Consideration of the Communication
and Control Cycles : LFCS2/LFCS £
The fieldbus communication and control cycles are determined according to the number of
connected fieldbus devices. Elements that determine the communication and control cycles
are indicated below.
• Total number of fieldbus devices connected to 1 segment (fieldbus capacity)
• Total number of fieldbus devices connected to the nest for I/O communication modules
(RIO bus capacity)

When the total number of fieldbus devices connected to 1 segment exceeds the fieldbus
capacity, the expected communication and control cycles cannot be obtained in that seg-
ment even if the total number of fieldbus devices connected to the nest for I/O communica-
tion modules is below the RIO bus capacity. For example, to make the dead time for the
process 2 seconds or less when the FCS control cycle is the standard cycle of 1 second,
the guideline for the number of I/O points per 1 segment is 16 when [Read at high speed
from IOM] is specified.

● Number of Fieldbus Blocks per Segment


• In the case of the AI block, the maximum number of fieldbus blocks that can be linked
to the I/O terminalQYs is 32 per segment. Only the function block parameters are
targets for linking to the I/O terminal.
• The maximum number of blocks that can acquire alarms or events is 64 per segment.
The blocks targeted for acquisition are the function blocks and resource blocks of the
fieldbus devices defined by the fieldbus engineering tool.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<2. Fieldbus Communication Module> 2-7
■ Cable Used in the Fieldbus
Selection of cable type and setting of the cable length is determined by the environment in
which the fieldbus is installed.

● Type and Total Length of Cable


Select cable appropriate to the installation environment from the following wiring materials.
There is a limit on the total length of the cable.
Determine the total length of the cable within the range of lengths indicated below.
• Type A (individually sheathed twisted pair cable) 1900 m
• Type B (group sheathed twisted pair cable) 1200 m
• Type D (group sheathed non-twisted pair cable) 200 m

For type B cables, some cables’ signal attenuation is large. In this case, it is necessary to
limit the total length of the cables or the total number of fieldbus devices connected in order
to maintain the signal amplitude.
For example, when the total number of connected fieldbus devices is 11 to 20, limit the total
length of the cable to 600 m or less. When the number of devices is 10 or less, the total
length of cable should be 1200 m or less.
When using Type D cable, up to 2 twisted pair cables are used, and avoid mutual interfer-
ence by using non-twisted pair cables.
Also, when using multi-conductor cable, make sure that only fieldbus signals, analog
signals and hybrid signals overlay the multi-conductor cable.

● Number and Length of Branch Cables


When connecting fieldbus devices to branched cables, there are limits to the length of the
branch cable according to the number of branch cables (number of connected fieldbus
devices).
Determine the total length of the branch cables within the range indicated below.
• Number of connected devices 1 to 12 120 m
• Number of connected devices 13 to 14 90 m
• Number of connected devices 15 to 18 60 m
• Number of connected devices 19 to 24 30 m
• Number of connected devices 25 to 32 0m

TIP
When there are many fieldbus devices connected, it may become necessary to have the actual number of
connected devices less than the number indicated above depending on conditions such as the power
supply and communication performance.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


Blank Page
<3. FCS Control Function Using Fieldbus> 3-1

3. FCS Control Function Using Fieldbus


Fieldbus process information is acquired using the FCS control function. The ac-
quired process information can be referenced with the operation and monitoring
function. Also, the plant including the fieldbus can be controlled properly using the
sophisticated control and calculation available in the FCS control function.

SEE ALSO
For information about configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

■ Overview of FCS Control Function in the Fieldbus System


Data in the fieldbus system and process information, such as, system alarms are acquired
using the FCS control function. The acquired process information can be referenced with
the operation and monitoring function. Also, control of the plant including the fieldbus can
be properly performed by combining the sophisticated control and calculation functions
available in the FCS control function with the control loop of the fieldbus.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-2

3.1 Position of Fieldbus Block


In the FCS, the fieldbus block parameters can be treated as process I/O.

■ Position of the Fieldbus Block in the FCS


Parameters for fieldbus blocks can be assigned to the numbered software terminals
(%Znnusmm) so that they can be treated as the process I/O signals. The assigned software
terminals (%Znnusmm) can be connected to the function blocks in the FCS.
Via the numbered software terminals, FCS control function can be linked to the fieldbus
block function, so that the parameters of the fieldbus function blocks can be set or refer-
enced by operation and monitoring function of HIS.

FCS

PID SET

IN OUT

Process I/O

ACF11

Terminal number

AI AO SP
CAS
PV OUT OUT
IN

Fieldbus block Back Calculation

Fieldbus device Fieldbus device


030101E.EPS

Figure Position of the Fieldbus Block

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-3
Fieldbus parameters consist of the fieldbus block external I/O parameters (CAS_IN, OUT,
etc.) and the fieldbus block internal parameters (PV, SV, etc.)
For the fieldbus block external I/O parameters (CAS_IN, OUT, etc.), software terminals
(%Znnusmm) with all different numbers can be assigned. Moreover, the assigned software
terminals can be connected to various types of FCS function blocks.
For the internal parameters, only the specific types of parameters such as PV, SV or etc.
can be assigned to the software terminals (%Znnusmm). Moreover, the assigned software
terminals can only be connected to faceplate function blocks. However, using the device
management tool can set and reference the internal parameters that can not be assigned
to the software terminals (%Znnusmm).

SEE ALSO
• For more information about the assignment of fieldbus block parameters to the software terminals
(%Znnusmm), see the following:
3.3, “Connection to Fieldbus Block”
• For more information about the connection between the fieldbus block internal parameters and faceplate
blocks, see the following:
3.3.1, “Connection to the Faceplate Block”

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-4

3.2 FCS Control Functions Related to the Fieldbus


This section explains the characteristics of the FCS control function in the fieldbus
system for the following items.
• Fieldbus blocks connectable to FCS function blocks
• Fieldbus block data type
• Conversion of the data status from the fieldbus block to the FCS function block
• Output value tracking
• Output clamp detection
• Output fault state
• Fieldbus block alert display

SEE ALSO
For more information about the “Referencing and setting the fieldbus block internal parameters”, “Refer-
encing and setting the fieldbus block mode (MODE_BLK)” and “Referencing the fieldbus block alarm
status (ALARM_SUM)”, see the following:
3.3.1, “Connection to the Faceplate Block”

■ Fieldbus Blocks Connectable to FCS Function Blocks


The fieldbus block can be cascade connected to the FCS function block as process I/O.
Because of this, the fieldbus block internal parameters can be referenced. In addition,
alarms and events occurring in the fieldbus device are notified to the HIS.
Of the standard fieldbus blocks prescribed by the FOUNDATION Fieldbus (Low speed
Voltage Mode), those that are handled in the fieldbus system are indicated in the list below.
Table List of Fieldbus Blocks Handled in the Fieldbus System
SYMBOL FUNCTION BLOCK
AI Analog input block
AO Analog output block
DI Digital input block
DO Digital output block
PID PID control block
RA Ratio Block
CS Control Selector Block
OS Output Splitter Block
SC Signal Characterizer Block
IT Integrator Block
IS Input Selector Block
MDI Multiple Discrete Input Block
MDO Multiple Discrete Output Block
MAI Multiple Analog Input Block
MAO Multiple Analog Output Block
030201E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-5
■ Fieldbus Block Data Type
The data type is defined according to the type of data handled by the FCS. The table below
indicates the FCS data type used in fieldbus block data.
Table List of Data Types for the Fieldbus Block
Name FCS data type
32 bit IEEE754 format floating point data (with data status) AF32S
32 bit IEEE754 format floating point data AF32
32 bit signed integer data AI32
16 bit signed integer data AI16
8 bit signed integer data AI8
32 bit unsigned integer data AU32
16 bit signed integer data AU16
8 bit unsigned integer data AU8
Contact data (with data status) DS
Contact data D
Mode data MODE
Alarm summary data ALARM
030202E.EPS

● Correlation Between Fieldbus Block Parameters and Data Type


The table below indicates the correlation between typical parameters and data type for the
fieldbus block.
Table Correlation Between Fieldbus Block Typical Parameters and Data Type
Data type
Corresponding fieldbus block parameters
Fieldbus FCS
Float with Status AF32S OUT, CAS_IN, BKCAL_OUT, PV, SP, etc.
Unsigned8 with Status DS(*2) OUT_D, CAS_IN_D, BKCAL_OUT_D, PV_D, SP_D, etc.
Bit String ALARM ALARM_SUM(*1)
Mode structure MODE MODE_BLK(*1)
Float AF32 GAIN(P), RESET(I), RATE(D), etc.
030203E.EPS

*1: Alarm status (ALARM_SUM) and block mode (MODE_BLK) for the fieldbus block can be referenced and set from the
faceplate block.
*2: Among the Fieldbus block parameters applied for FCS data type DS, ON=1, OFF=0 will be the values for the items of
OUT_D, CAS_IN_D, BKCAL_OUT_D, PV_D, SP_D and so on.
However, for the internal parameter such BYPASS, ON=2 and OFF=1. These data items can not be connected to
digital I/O.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-6
■ Conversion of Data Status from the Fieldbus Block to the FCS Function
Block
Data status for the fieldbus block consists of information that indicates the data quality,
substatus and limit. In the FCS, these data statuses are converted to those for the FCS
function block.
The table below indicates the conversion of data status from the fieldbus block to the FCS
function block.
Table List of Conversion of Data Status from the Fieldbus Block to the FCS Function Block (1/2)
Fieldbus block FCS function block
Quality Sub status Limit
Data status
Level Name Level Name Level Name
0 Non-specific
BAD (PTPF)
1 Configuration Error
- Unrelated
2 Not Connected CND
3 Device Failure BAD (OOP)
0 Not limited BAD (BAD | OOP)

0 Bad 1 Low limited BAD | IOP- (BAD | OOP)


4 Sensor Failure
2 High limited BAD | IOP+ (BAD | OOP)
3 Constant BAD | IOP- | IOP+ (BAD | OOP)
5 No Communication with LUV BAD (PTPF)
6 No Communication - Unrelated CND
7 Out of Service
BAD (PTPF)
Combination of sub status 8 to 15 and limit 0 to 3
1 Uncertain Combination of sub status 0 to 15 and limit 0 to 3 QST
0 Not limited NORMAL
Good 1 Low limited CLP -
2 All sub status
(Non-cascade) 2 High limited CLP+
3 Constant CLP- | CLP+
030204E.EPS

Note 1: ( ) indicates the data status in the case of output data.


Note 2: [|] means satisfied simultaneously.

Quality
• Bad Invalid value (true measured value and calculated value are not reflected)
• Uncertain Uncertain value
• Good (Non-cascade) Valid value (there is a possibility an alarm will occur)
• Good (Cascade) Valid value (can be used for control)
Limit
• Non limited Change in the value is unrestricted
• Low limited Change in the value is limited in the low value direction
• High limited Change in the value is limited in the high value direction
• Constant Change in the value is not possible in the low value or high value direction

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-7
Table List of Conversion of Data Status from the Fieldbus Block to the FCS Function Block (2/2)
Fieldbus block FCS function block
Quality Sub status Limit
Data status
Level Name Level Name Level Name
0 Non-specific
NORMAL
1 Initialization Acknowledge
2 Initialization Request MINT
3 Not Invited CND
4 Not Selected
0 Not limited NORMAL
5 Do Not Select
Good
3 6 Local Override
(Cascade) CND
7 Fault State Active
8 Initiate Fault State
NORMAL
9 to 15
1 Low Limited CLP- (*1)
All sub status 2 High Limited CLP+ (*1)
3 Constant CLP- | CLP+ (*1)
030205E.EPS

Note 1: ( ) indicates the data status in the case of output data.


Note 2: [|] means satisfied simultaneously.
*1: The FCS function block data status under Good (Cascade) Not Limited is also satisfied at the same time.

Quality
• Bad Invalid value (true measured value and calculated value are not reflected)
• Uncertain Uncertain value
• Good (Non-cascade) Valid value (there is a possibility an alarm will occur)
• Good (Cascade) Valid value (can be used for control)
Limit
• Non limited Change in the value is unrestricted
• Low limited Change in the value is limited in the low value direction
• High limited Change in the value is limited in the high value direction
• Constant Change in the value is not possible in the low value or high value direction

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-8
■ Output Value Tracking
Output value tracking is the output operation that matches the manipulated output value for
the FCS function block to the value (actual output value) of the connected fieldbus block.
When an error occurs in the fieldbus communication, the data status will indicate an error in
addition to the fieldbus block mode making a switch. At this time, the output operation for
the connected FCS function block will stop. After that, when the data status of the value
read back (read back value) from the fieldbus block returns to normal, the FCS function
block manipulated output value is matched to the actual output value of the fieldbus block.
Due to this process, the FCS function block output operation will have a bumpless restart.
Readback of the manipulated output value, which is synchronized to the execution of the
fieldbus block, is automatically performed in the fieldbus communication module (ACF11) to
bumplessly control the output, in addition to the writing of the manipulated output.

■ Output Clamp Detection


The FCS function block can detect an output clamp from the data status of the connected
fieldbus block.

SEE ALSO
For details on the output clamp, see the followings:
C4.3, “Output Clamp” in CENTUM VP Reference, Function Block Details (IM 33M01A30-40E)
C4.3, “Output Clamp” in CS 1000/CS 3000 Reference, Function Block Details (IM 33S01B30-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-9
■ Output Fault State : PFCS/SFCS
When a function failure in the areas of the FCS processor is detected by the ACF11, an
instruction to execute output fault state is sent from the ACF11 to the fieldbus device.
Output fault state is a function of the fieldbus output block (AO, DO).
Also, when the block that is cascade connected to the fieldbus output block, or the fieldbus
output block detects a communication error or other error in the input value from the upper
level block, there is a forced output of the pre-specified value (hold or reset) from the output
block. This keeps the process out of danger when a function failure occurs in the areas of
FCS processor.
When recovered, an instruction to cancel the fault state is sent from the ACF11 to the
fieldbus device.

An example of the execution of the output fault state operation is shown below.
1. Function failure in the area of FCS processor is detected by the ACF11.
2. The data status is changed to Initiate Fault State by writing to the AO block from the
ACF11.
3. The output fault state is executed in the AO block.

1. FCS 2. FCS

Communication error

ACF11
Good-Non_Specific Good-Initiate Fault State

Fallback detected

Fieldbus device Fieldbus device


030206E.EPS

Figure Output Fault State Operation : PFCS/SFCS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-10
■ Output Fault State : LFCS2/LFCS £
When a function failure in the areas of the FCS processor is detected by the ACF11, an
instruction to execute output fault state is sent from the ACF11 to the fieldbus device.
Output fault state is a function of the fieldbus output block (AO, DO).
Also, when the block that is cascade connected to the fieldbus output block, or the fieldbus
output block detects a communication error or other error in the input value from the upper
level block, there is a forced output of the pre-specified value (hold or reset) from the output
block. This keeps the process out of danger when there is an FCU function stop or RIO bus
transmission stop.
When recovered, an instruction to cancel the fault state is sent from the ACF11 to the
fieldbus device.

An example of the execution of the output fault state operation is shown below.
1. An FCU function stop or RIO bus transmission stop is detected by the ACF11.
2. The data status is changed to Initiate Fault State by writing to the AO block from the
ACF11.
3. The output fault state is executed in the AO block.

1. FCS 2. FCS

Communication error

ACF11
Good-Non_Specific Good-Initiate Fault State

Fallback detected

Fieldbus device Fieldbus device


030207E.EPS

Figure Output Fault State Operation : LFCS2/LFCS £

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-11
■ Fieldbus Block Alert Display : PFCS/SFCS
A fieldbus device alert (alarm or event) is transmitted to the HIS via the ACF11 and FCS.
The alert is displayed in the HIS historical message report window and message monitor
window.
However, if multiple alerts occur in a short interval in a fieldbus device, some of the alerts
might not be acquired by the ACF11. In this case, the alerts will be resent to the ACF11
according to the protocol between the ACF11 and fieldbus device. This ensures that the
alerts are sent to the HIS.

IMPORTANT
• When the resending time of the fieldbus alert is too short (about 2 seconds or less),
two of the same alerts may be transmitted to the HIS.
• “Auto-acknowledge” for the acknowledgment option parameter (ACK-OPTION) of the
fieldbus device should be specified using the fieldbus engineering tool.
• The alert confirmation notification (Acknowledge Event Notification) is performed by
the ACF11.
• When there is an error in the FCS processor, the alert taken in by the ACF11 is de-
leted without being sent.
• To display the fieldbus alert messages in the message monitor window, the massages
to be displayed need to be registered in the monitor registration dialog box.

■ Fieldbus Block Alert Display : LFCS2/LFCS £


A fieldbus device alert (alarm or event) is transmitted to the HIS via the ACF11 and FCS.
The alert is displayed in the HIS historical message report window and message monitor
window.
However, if multiple alerts occur in a short interval in a fieldbus device, some of the alerts
might not be acquired by the ACF11. In this case, the alerts will be resent to the ACF11
according to the protocol between the ACF11 and fieldbus device. This ensures that the
alerts are sent to the HIS.

IMPORTANT
• When the resending time of the fieldbus alert is too short (about 2 seconds or less),
two of the same alerts may be transmitted to the HIS.
• “Auto-acknowledge” for the acknowledgment option parameter (ACK-OPTION) of the
fieldbus device should be specified using the fieldbus engineering tool.
• The alert confirmation notification (Acknowledge Event Notification) is performed by
the ACF11.
• When there is an error in the FCU and RIO bus, the alert taken in by the ACF11 is
deleted without being sent.
• To display the fieldbus alert messages in the message monitor window, the messages
to be displayed need to be registered in the monitor registration dialog box.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-12

3.3 Connection to Fieldbus Block


The fieldbus block can be connected to the following FCS function blocks.
• Faceplate block
• Regulatory control block
• Sequence control block
• Calculation block
*1: ¡ £ Off site block can only be used with the CENTUM VP/CS 3000.

TIP
The fieldbus block cannot be connected to the following FCS function blocks.
• SFC block
• Unit instrument, Operation

■ Fieldbus Block I/O Connection


The I/O terminal parameters (CAS_IN, OUT, etc.) and internal parameters (PV, SP) for the
fieldbus block are treated as process I/Os in the FCS. Process I/Os are distinguished by the
terminal number (%Znnusmm).
The fieldbus block parameters are assigned to the process I/O terminal number and by
connecting this terminal number to the FCS function block, the fieldbus block can be
operated and monitored using the operation and monitoring function.

FCS

PID SET

IN OUT

AI Terminal number AO SP
AUTO
CAS
PV OUT OUT
IN CAS

Back Calculation

Fieldbus device Fieldbus device


030301E.EPS

Figure Connection of the FCS Function Block and Fieldbus Block I/O

SEE ALSO
For more information about a list of the fieldbus block parameters that can be connected as FCS process
I/O, see the following:
3.3.6, “List of Parameters that can be Connected”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-13
● Assignment to the Fieldbus Block Terminal Number : PFCS/SFCS
The range of numeric values specified for the process I/O terminal numbers is given below.
Also, the assignment to the terminal number of the fieldbus block parameter is done with
the IOM Builder of CENTUM VP/CS 3000/CS 1000 system builders.
Table Terminal Number Assignment : PFCS/SFCS
Terminal number: %Znnusmm
Symbol Name Range Remarks
nn Node number 1 (fixed)
u Unit number 1 to 5 Position of the AMN33
s Slot number 1 to 2 Position of the ACF11
mm Terminal position 1 to 32
030302E.EPS

● Assignment to the Fieldbus Block Terminal Number : LFCS2/LFCS £


The range of numeric values specified for the process I/O terminal numbers is given below.
Also, the assignment to the terminal number of the fieldbus block parameter is done with
the IOM Builder of CENTUM VP/CS 3000/CS 1000 system builders.
Table Terminal Number Assignment : LFCS2/LFCS £
Terminal number: %Znnusmm
Symbol Name Range Remarks
nn Node number 1 to 8 (max. 16)
u Unit number 1 to 5 Position of the AMN33
s Slot number 1 to 2 Position of the ACF11
maximum of 16 when two ACF modules are installed or
mm Terminal position 1 to 32
when high-speed reading is set.
030303E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-14
● Connection of Fieldbus Block External I/O Terminal Parameters
The terminal number to which is assigned the fieldbus block external I/O terminal param-
eters (CAS_IN, OUT, etc.) can be connected to the FCS function block. The external I/O
terminal parameters that were connected can be displayed using the operation and moni-
toring function.

IMPORTANT
Connecting remote external I/O terminal parameters (RCAS_IN, RCAS_OUT, ROUT_IN,
RCAS_IN_D, RCAS_OUT_D) of fieldbus function blocks to FCS function blocks is not yet
supported up, so do not do this.

● Connection of Fieldbus Block Internal Parameters


Display and change of the fieldbus block internal parameters (PV, SP, etc.) are basically
done with the device management tool.
After assigning them to a terminal number, certain fieldbus block internal parameters can
only be connected to the faceplate block out of the various FCS function blocks. The con-
nected internal parameters can be displayed and changed with the operation and monitor-
ing function. Further, in order to monitor the fieldbus block internal parameters, these
parameters are periodically transmitted.

IMPORTANT
Do not write the fieldbus block internal parameters from any FCS function block other than
the faceplate block.

TIP
To change the fieldbus block mode from the operation and monitoring function, it is necessary to connect
the fieldbus block internal parameter MODE_BLK to the faceplate block.
Because the fieldbus block mode may automatically switch due to an error in the final control element, we
recommend connecting this parameter to the FCS faceplate block, so that the output block (AO, DO) and
control block (PID) of the fieldbus block can change the mode from the operation and monitoring function.

SEE ALSO
• For more information about displaying and changing the parameter with the device management tool, see
the following:
6.5, “Fieldbus Device Parameter Display and Setting”
• For more information about connecting the fieldbus block internal parameters and the faceplate block,
see the following:
3.3.1, “Connection to the Faceplate Block”

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-15

3.3.1 Connection to the Faceplate Block


In order to reference or set the fieldbus block parameters, it is necessary to connect
them to the faceplate block. The fieldbus block internal parameters (MODE_BLC,
ALARM_SUM, PV, SP, OUT, SP_HI_LIM, SP_LO_LIM, OUT_HI_LIM, OUT_LO_LIM) can
be connected to one section of the faceplate block.

■ Connection of the Fieldbus Block and Faceplate Block


The fieldbus block parameters can be referenced or set by connecting the fieldbus block
and faceplate block. As with process I/O, the fieldbus block parameters and faceplate block
data items are connected by a data connection that uses a terminal number (%Znnusmm).
Connect the fieldbus block parameters and faceplate block data items in the following
cases.
• When a fieldbus block output block (AO, DO) mode is operated from the operation and
monitoring function
Connect the output block (AO, DO) of the fieldbus block and the faceplate block.
• When a fieldbus block control block is applied for local control
Connect the control block (PID) and the faceplate block to perform operation and
monitoring from the operation and monitoring function. However, this is not necessary
when there is a local operation and monitoring device, and the output to the setpoint
value for the fieldbus block control block is regarded as a process output.

Faceplate block

PV SV MV

MODE

Terminal number

AI PID AO
CAS_IN CAS_IN

PV PV SP MODE

OUT IN BKCAL_IN OUT BKCAL_OUT OUT

Fieldbus block

030304E.EPS

Figure Referencing the Fieldbus Block Internal Parameters

TIP
When the fieldbus block internal parameters are changed directly from a device such as the Hand Held
Terminal in the fieldbus, the faceplate block parameters are automatically tracked to the post-change
value.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-16
■ List of Faceplate Blocks that Can be Connected ¡ £
There are three types of faceplate blocks: the analog type, sequence type and hybrid type.
The table below gives a list of the faceplate blocks that can be connected to the fieldbus
block.

SEE ALSO
For details on the faceplate block, see the follwings:
D4, "Faceplate Blocks" in CENTUM VP Reference, Function Block Details (IM 33M01A30-40E)
D4, "Faceplate Blocks" in CS 1000/CS 3000 Reference, Function Block Details (IM 33S01B30-01E)

Table List of Faceplate Blocks That Can Be Connected to the Fieldbus Block ¡ £
Connection
Type Model Name
possibility
INDST2 Dual-Pointer indicating Station Block 
Analog type INDST2S Dual-Pointer Manual Station Block 
INDST3 Triple-Pointer Manual Station Block 
BSI Batch Status Indicator Block  (*2)
Sequence type PBS5C Extended 5-Push-Button Switch Block  (*2)
PBS10C(*1) Extended 10-Push-Button Switch Block  (*2)
Hybrid type HAS3C Extended Hybrid Manual Station Block  (*2)
030305E.EPS

: Can connect.
-: Cannot connect.
*1: ¡ £ This is a function block that can only be used for the CENTUM VP/CS 3000.
*2: Fieldbus digital I/O can be connected. But I/O other than status does not have any meaning because a time delay
occurs in the fieldbus.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-17
■ Data Referencing and Setting for the Fieldbus Block Parameters
¡£
By connecting the connection terminal of the faceplate block analog data (JPV, JSV, JMV,
J01, J02, J03 and J04) and the connection terminal (JMOD, JALM) for MODE or ALRM
data to the ACF11 I/O terminal using the terminal number, the fieldbus block parameters
can be referenced or set.

● Parameters That Can be Connected to the Faceplate Block ¡ £


All of the fieldbus block parameters that can be connected to each terminal of the faceplate
block are indicated in the table below.
Table Parameters of the Fieldbus Block That Can be Connected to the Faceplate Block
Faceplate Block Fieldbus Block
I/O Terminal Related Data Item Parameter Access
JMOD MODE MODE_BLK READ / WRITE
JALM ALRM ALARM_SUM READ
JPV PV PV READ
JSV SV SP READ / WRITE
JMV MV OUT READ / WRITE
J01 SVH SP_HI_LIM READ / WRITE
J02 SVL SP_LO_LIM READ / WRITE
J03 MH OUT_HI_LIM READ / WRITE
J04 ML OUT_LO_LIM READ / WRITE
030306E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-18
The table below gives a list of the fieldbus block parameters that can be connected to each
faceplate block.
Table List of Fieldbus Block Parameters That Can be Connected to Each Faceplate Block
¡£

I/O terminal JMOD JALM JPV JSV JMV J01 J02 J03 J04

Data item MODE ALRM PV SV MV SVH SVL MH ML

INDST2      
INDST2S        
FCS
Block INDST3         
BSI  
PBS5C  
PBS10C (*1)  
HAS3C         
Corresponding MODE_ ALARM_ SP_HI_ SP_LO_ OUT_HI_ OUT_LO_
PV SP OUT
parameters BLK SUM LIM LIM LIM LIM
Access R/W R R R/W R/W R/W R/W R/W R/W
AI   
DI  
PID         
AO    
DO 
RA         
Fieldbus
Block CS    
OS   (*2)
SC  (*2)
IT  
IS  
MDI  (*3)
MDO  (*4)
MAI  (*5)
MAO  (*6)
030307E.EPS

Note: The only parameters that can be connected to the faceplate block I/O terminal with the  mark indicated in the upper
portion of the table are the fieldbus block parameters with the  mark indicated in the lower portion of the table.
*1: ¡ £ These are function blocks that can only be used with the CENTUM VP/CS 3000.
*2: The output parameter is OUT_N (N=1 or 2)
*3: Connect the MDI output parameter OUT_DN (N= 1 to 8) to the faceplate block, the corresponding PV can be moni-
tored.
*4: Connect the MDO input parameter IN_DN (N= 1 to 8) to the faceplate block, the corresponding MV can be manipu-
lated.
*5: Connect the MAI output parameter OUT_N (N= 1 to 8) to the faceplate block, the corresponding PV can be monitored.
*6: Connect the MAO input parameter IN_N (N= 1 to 8) to the faceplate block, the corresponding MV can be manipulated.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-19
● Example of a Faceplate Block and Fieldbus Block Connection
The diagram below is an example of a faceplate block and fieldbus block connection.

MODE ALRM PV SV MV MODE MV

[INDST3] [INDST2S]
JMOD JALM JPV JSV JMV JMOD JMV

FCS
%Znnus03 %Znnus04 %Znnus05 %Znnus06 %Znnus07 %Znnus12 %Znnus13

Fieldbus
ALARM_SUM PV SP
MODE_BLK
[PID]

IN BKCAL_IN OUT

OUT CAS_IN MODE_BLK OUT

[AI] BKCAL_OUT [AO]

030308E.EPS

Figure Faceplate Block and Fieldbus Block Connection

IMPORTANT
• Alarm setpoint values for the fieldbus block (HI_HI_LIM, HI_LIM, LO_LIM,
LO_LO_LIM) cannot be connected to the faceplate block. Set the fieldbus block alarm
setpoint values with the device management tool in the PC.
• Faceplate block data is updated at unfixed intervals. This cannot be used in control
requiring a precise response time.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-20
■ Fieldbus Block Mode Referencing and Setting
Same as FCS function blocks, the fieldbus block also has block execution mode repre-
sented in MODE_BLK. When connecting the MODE_BLK to JMOD terminal of a faceplate
block via a PIO terminal(%Znnusmm), the fieldbus block mode can be referenced or ma-
nipulated on the faceplate block.
It is important to set the correct block mode when fieldbus blocks are connected to each
other or connected to FCS function blocks.

● Correlation Between the Mode Display Symbols for the Fieldbus Block and
Faceplate Block
The mode display symbols differ in the faceplate block mode and fieldbus block mode. The
table below shows the correlation between the respective mode display symbols.
Table Correlation Between the Mode Display Symbols for the Fieldbus Block and Faceplate Block
Fieldbus block Faceplate block
Block mode Block mode
O/S O/S
IMAN IMAN
LO TRK
MAN MAN
AUTO AUT
CAS CAS
(*1) PRD
RCAS RCAS
ROUT ROUT
030309E.EPS

*1: The fieldbus block primary direct operating status (mode is PRD) is placed as one status of the MAN mode in the
faceplate block. Accordingly, when the fieldbus block changes to the primary direct operating status, the mode for the
faceplate block connected to the fieldbus block becomes MAN. Conversely, even if the faceplate block mode is set to
PRD, the setting is invalid.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-21
● Setting Recommended Mode
A fieldbus block is executed in a pre-defined valid mode.
When connecting a fieldbus block to an FCS function block in a cascade loop, the fieldbus
block should be set to the mode recommended in the table below.
Table Recommended Mode and Valid Mode for the Fieldbus Block
Is cascade
Recommended
Fieldbus block Valid mode connection to the FCS
mode
function block allowed?
AI AUTO O/S, MAN, AUTO
DI AUTO O/S, MAN, AUTO
PID CAS (*1) O/S, MAN, AUTO, CAS, RCAS, ROUT Allowed
AO CAS (*1) O/S, MAN, AUTO, CAS, RCAS Allowed
DO CAS (*1) O/S, MAN, AUTO, CAS, RCAS Allowed
RA MAN O/S, (MAN), AUTO (*2)
CS MAN O/S, (MAN), AUTO (*2)
OS AUTO O/S, MAN, AUTO, CAS Allowed
SC AUTO O/S, MAN, AUTO
IT MAN O/S, MAN, AUTO
IS MAN O/S, MAN, AUTO
MDI AUTO O/S, MAN, AUTO
MDO AUTO O/S, AUTO
MAI AUTO O/S, MAN, AUTO
MAO AUTO O/S, AUTO
030310E.EPS

*1: AUTO mode is recommended if the loop is not a cascade-connected loop.


*2: The parenthesised mode is optional.

If a mode other than the recommended one is defined, the cascade loop with the FCS
function block does not function properly. In this case, the data status of the fieldbus block
will show “Good-Not Invited, “ and the FCS function block mode will become IMAN.
Also, it is recommend to set the AUTO mode for the fieldbus blocks not connected with FCS
function blocks in cascade loops.

TIP
• When the fieldbus block mode is set to AUTO, connect SP to the faceplate block to change the
fieldbus block manipulated setpoint value (SP) from the HIS.
Also, when the fieldbus block mode is set to MAN, if the fieldbus block manipulated output value
(OUT) is connected to the faceplate block, manual output can be performed.
• Even when the MODE change operation is not performed, the mode may automatically switch due to
an error found in final control element. Thus, we recommend connecting the control block (PID) and
output block (AO, DO) for the fieldbus block to the faceplate block.
• When an error occurs in the process, the mode switches to the specified status (different parameter
value). After that, if the process returns to normal, the mode automatically returns to the setpoint
value. However, if the process does not return to normal, the execution mode remains in the
transitioned state.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-22
● Effect on Connected Blocks when the Mode Changes from O/S to Others
If a fieldbus block or a faceplate block changes its mode from O/S to others, the mode of
the connected block will change its mode accordingly. The special relationship in the mode
transition in this case is indicated below.
“MAN” mode in this table represents a mode other than O/S.
Table Effect on Connected Blocks when the Mode Changes from O/S to Others
Mode Change Operation Result
Faceplate block Fieldbus block Faceplate block Fieldbus block
O/S→MAN O/S MAN MAN
O/S→MAN MAN MAN MAN
O/S(MAN)→MAN O/S MAN MAN
O/S(MAN)→O/S O/S O/S O/S
MAN→O/S MAN O/S MAN
O/S O/S→MAN O/S MAN
O/S MAN→O/S O/S O/S
O/S(MAN) O/S→MAN MAN MAN
MAN MAN→O/S O/S(MAN) O/S
030311E.EPS

Note: The section enclosed by the thick line frame indicates the mode change operation. There are two operations: the
faceplate block mode change operation and the fieldbus block mode direct change operation.

● Mode Transition Because of Local Device Operation


The effect on the FCS function block mode when the fieldbus block mode has switched due
to operation of a local device is indicated below.
• Changes in the fieldbus block parameters because of the Hand Held Terminal may
cause the fieldbus block mode to change to O/S. In this case, because the fieldbus
block data status becomes Bad, an IOP or OOP will be detected by the connected
FCS function block.
• If the fieldbus block mode is set to anything other than CAS, the mode for the FCS
function block at the cascade connected destination changes to IMAN

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-23
■ Referencing Fieldbus Block Alarm Status
When connecting the ALARM_SUM of fieldbus block to JALM terminal of a faceplate block
via a PIO terminal(%Znnusmm), the fieldbus block alarm status can be referenced on the
faceplate block.
However, the alarm status display symbols for the faceplate block and fieldbus block differ.
The table below shows the correlation between the respective alarm status display sym-
bols.
Table Correlation Between the Alarm Status Symbols for the Faceplate Block and Fieldbus Block

Fieldbus block alarm status Faceplate block alarm status

High high Alarm HIHI


High Alarm HI
Low low Alarm LOLO
Low Alarm LO
Deviation high Alarm DV+
Deviation low Alarm DV-
Block Alarm BLCK
Discrete Alarm DISC
030312E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-24

3.3.2 Connection to the Regulatory Control Block


The regulatory control blocks that can be connected to the fieldbus block I/O termi-
nal parameters are indicated below. When connecting, there are precautions related
to settings for the regulatory control block.

■ List of Regulatory Control Blocks that can be Connected


Regulatory control blocks can be connected to the fieldbus block external I/O terminal. They
cannot be connected to the fieldbus block internal parameters. To connect to the internal
parameters, use the faceplate block.
The table below gives a list of the regulatory control blocks that can be connected to the
fieldbus block.
Table List of Regulatory Control Blocks That Can Be Connected to the Fieldbus Block (1/2)
Connection
Block Type Code Name
Possible
PVI Input Indicator Block 
Input terminal
PVI-DV Input Indicator-Block with Deviation Alarm 
PID PID Controller Block  (*1)
PI-HLD Sampling PI Controller Block  (*1)
PID-BSW PID Controller Block with Batch Switch -
ONOFF Two-Position ON/OFF Controller Block -
Enhanced Two-Position ON/OFF Controller
ONOFF-E  (*1)
Block
Adjustment
ONOFF-G Three-Position ON/OFF Controller Block  (*1)
control
Enhanced Three-Position ON/OFF Controller
ONOFF-GE  (*1)
Block
PID-TP Time-Proportioning ON/OFF Controller Block  (*1)
PD-MR PD Controller Block with Manual Reset  (*1)
PI-BLEND Blending PI Controller Block  (*1)
PID-STC Self-Tuning PID Controller Block  (*1)
MLD Manual Loader Block 
MLD-PVI Manual Loader Block with Input Indicator 
MLD-SW Manual Loader Block with Auto/Man SW  (*1)
Manual operation MC-2 Two-Position Motor Control Block -
MC-2E Enhanced Two-Position Motor Control Block  (*2)
MC-3 Three-Position Motor Control Block -
MC-3E Enhanced Three-Position Motor Control Block  (*2)
RATIO Ratio Set Block  (*1)
PG-L13 13-Zone Program Set Block 
Signal setting
BSETU-2 Flow-Totalizing Batch Set Block  (*3)
BSETU-3 Weight-Totalizing Batch Set Block  (*3)
Signal limit VELLIM Velocity-Limiter Block  (*1)
030313E.EPS

: Can be connected.
-: Cannot be connected.
*1: Cannot be connected to the SET terminal.
*2: Inching output cannot be done because a time difference occurs in the fieldbus.
*3: Cannot be connected to the OUT2 terminal.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-25
Table List of Regulatory Control Blocks That Can Be Connected to the Fieldbus Block (2/2)
Connection
Block Type Code Name
Possible
AS-H/M/L Auto Selector Block  (*1)
Signal selection SS-H/M/L Signal Selector Block  (*1)
SS-DUAL Dual-Redundant Signal Selector Block 
FOUT Cascade Signal Distributor Block -
FFSUM Feedforward Signal Summing Block  (*2)
Dual signal
selector block XCPL Non-Interference Control Output Block  (*3)
SPLIT Control Signal Splitter Block  (*4)
Pulse count PTC Pulse Count Input Block -
Alarm ALM-R Representative Alarm Block -
030314E.EPS

: Can be connected.
-: Cannot be connected.
*1: Cannot be connected to IN1 to IN3 terminals.
*2: Cannot be connected to the IN terminal or SET terminal.
*3: Cannot be connected to the IN terminal.
*4: Cannot be connected to the SET terminal.

IMPORTANT
• Output operation cannot be performed normally in a pulse width time that is less than
the fieldbus control cycle in the pulsive output for the Enhanced Motor Control Blocks
(MC-2E, MC-3E).
• When a “3-position status input” is specified as the answerback input for the Enhanced
Motor Control Blocks (MC-2E, MC-3E), synchronicity cannot be guaranteed between
the two data that are read as the answerback signal.
When a “3-position status output” is specified as the output for the Enhanced 3-
Position Motor Control Block (MC-3E), synchronicity cannot be guaranteed between
the two data the are output.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-26
■ Precautions When Connecting to a Regulatory Control Block
Precautions when connecting the fieldbus block and a regulatory control block are given
below.
• When a signal has already been converted in the fieldbus block’s analog input block
(AI), specify “non-conversion” as the setting for the input signal conversion type in the
Function Block Detail Builder.
• When a low-input cutoff has already been performed in the fieldbus block’s analog
input block (AI), with the Function Block Detail Builder, set the “square root low-input
cutoff value” to 0 % for the input processing in the FCS function block.
• When outputting from the FCS function block to the fieldbus block, match the FCS
function block’s output range to the output destination, that is the fieldbus block’s input
parameter range.
• When cascade connecting to the fieldbus block, set the [tight shut/full open specifica-
tion] to “not available” with the Function Block Detail Builder, so that the tight-shut
specification is not executed.
• To enable FCS function block alarm processing when the fieldbus block I/O are
treated the same as process I/O up to this point, set the fieldbus block alarm’s setpoint
value outside the range in the FCS function block.
• The output value tracking is valid only in the connection to the fieldbus block’s cascade
input parameters (CAS_IN, RCAS_IN, ROUT_OUT (*1)). It will not operate normally in
a connection to parameters other than these.
*1: Connecting to RCAS_IN, ROUT_OUT is not yet supported.

IMPORTANT
Do not write to the fieldbus block internal parameters from any FCS function block other
than the faceplate block.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-27

3.3.3 Connection to the Sequence Control Block


The sequence control blocks that can be connected to the fieldbus block I/O terminal
parameters are indicated below. When connecting, there are precautions related to
settings for the sequence control block.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-28
■ List of Sequence Control Blocks that can be Connected
Sequence control blocks can be connected to the fieldbus block external I/O terminal. They
cannot be connected to the fieldbus block internal parameters.
The table below gives a list of the sequence control blocks that can be connected to the
fieldbus block.
Table List of Sequence Control Blocks that can be Connected to the Fieldbus Block (1/2)

Connection
Block type Code Name
Possible
ST16 Sequence Table Block  (*1)
Sequence table
ST16E Rule Extension Block  (*1)
Logic chart LC64 Logic Chart Block  (*1)
SI-1 Switch Instrument Block with 1 Input  (*2)
SI-2 Switch Instrument Block with 2 Inputs  (*2)
SO-1 Switch Instrument Block with 1 Output  (*2)(*4)
SO-2 Switch Instrument Block with 2 Outputs  (*2)(*4)
SIO-11 Switch Instrument Block with 1 Input, 1 Output  (*2)(*4)(*5)
SIO-12 Switch Instrument Block with 1 Input, 2 Outputs  (*2)(*4)
SIO-21 Switch Instrument Block with 2 Inputs, 1 Output  (*2)(*4)(*5)
SIO-22 Switch Instrument Block with 2 Inputs, 2 Outputs  (*2)(*4)
Switch Instrument Block with 1 Input,
SIO-12P  (*2)(*4)
2 One-Shot Outputs
Switch Instrument Block with 2 Inputs,
SIO-22P  (*2)(*4)
2 One-Shot Outputs
Switch instrument
SI-1E Enhanced Switch Instrument Block with 1 Input  (*2)
SI-2E Enhanced Switch Instrument Block with 2 Inputs  (*2)
SO-1E Enhanced Switch Instrument Block with 1 Output  (*2)
SO-2E Enhanced Switch Instrument Block with 2 Outputs  (*2)
Enhanced Switch Instrument Block with 1 Input,
SIO-11E  (*2)
1 Output
Enhanced Switch Instrument Block with 1 Input,
SIO-12E  (*2)
2 Outputs
Enhanced Switch Instrument Block with 2 Inputs,
SIO-21E  (*2)
1 Output
Enhanced Switch Instrument Block with 2 Inputs,
SIO-22E  (*2)
2 Outputs
Enhanced Switch Instrument Block with 1 Input,
SIO-12PE  (*2)
2 One-shot Outputs
Enhanced Switch Instrument Block with 2 Inputs,
SIO-22PE  (*2)
2 One-shot Outputs
030315E.EPS

: Can be connected.
*1: The fieldbus block discrete I/O block (DI, DO) can be connected. However, due to a time delay occurring in the fieldbus,
a short time delay output or one-shot output will not work correctly.
*2: The fieldbus block discrete I/O block (DI, DO) can be connected. In this case, however, a time delay will occur in the
fieldbus.
*4: It is necessary to aware of the restrictions when connecting the OUT terminal to fieldbus function block DO. Though the
switch instrument can open or close properly, the handshake between the switch instrument and DO block is not
supported.
*5: In order to connect the output of switch instrument to fieldbus function block DO, it is necessary to have a logic
operation block such as a logical OR block in between. Moreover, the answerback input should use a signal from
fieldbus function block DI.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-29
Table List of Sequence Control Blocks that can be Connected to the Fieldbus Block (2/2)
Connection
Block type Code Name
Possible
TM Timer Block  (*2)
CTS Software Counter Block  (*2)
CTP Pulse Train Input Counter Block  (*2)
Sequence auxiliary CI Code Input Block  (*3)
CO Code Output Block  (*3)
RL Relational Expression Block  (*3)
RS Resource Scheduler Block -
Valve monitor VLVM Valve Monitoring Block  (*2)
030322E.EPS

: Can be connected.
-: Cannot be connected.
*2: The fieldbus block discrete I/O block (DI, DO) can be connected. In this case, however, a time delay will occur in the
fieldbus.
*3: The parameters for the connected fieldbus block are limited to 4 bytes or less.

■ Precautions when Connecting to a Sequence Control Block


In the sequence control block and fieldbus block connection, everything becomes status I/O.
Pulse output cannot be done.

IMPORTANT

• Pulse output and flashing output for the sequence table do not work.
• In the switch-instrument block’s pulse contact output, normal output cannot be per-
formed in a pulse time that is less than the fieldbus control cycle.
• Data synchronicity between the two data that is read as the answerback input signal
for the Switch Instrument Block with 2 Inputs (SI-2, SIO-21, SIO-22, SIO-22P, SI-2E,
SIO-21E, SIO-22E, SIO-22PE) cannot be guaranteed.
Also, data synchronicity between the two data output as the output signal for the
Switch Instrument Block with 2 Outputs (SO-2, SIO-12, SIO-22, SIO-22P, SO-2E,
SIO-12E, SIO-22E, SIO-22PE) cannot be guaranteed.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-30
● Cautions when Connecting Fieldbus Function Block DO to Switch Instru-
ments
When connecting the fieldbus DO function blocks to switch instrument blocks, the en-
hanced type (SO-1E, SO-2E, SIO-11E, SIO-12E, SIO-21E, SIO-22E, SIO-12PE and SIO-
22PE) switch instrument blocks should be used.
If non-enhanced type (SO-1, SO-2, SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P and SIO-
22P) switch instrument blocks are used, the following restrictions are applied.
Among the switch instruments, only SIO-11 and SIO-21 can be connected to function block
DO. If other switch instruments are connected to DO, the handshake between the switch
instruments and DO block does not function, though the switch instruments can open and
close.
Configure the switch instrument (SIO-11 or SIO-21) as follows when connecting to fieldbus
function block DO.

[SIO-21] [OR]

IN MV Q01 OUT
0 : Close
1 : Open
%Znnus02
%Znnus01
%Znnus03
FCS

0: Close
Fieldbus 0 : Close
1: Open
2 or more : Varies with 1 : Open
switch instruments
Limit Switches
BK_CAL CAS

[DO]

Answer back inputs 0 : Not Open


from limit switches 1 : Open
OUT

[Up-scale Limit]

0 : Not Close
1 : Close
OUT

[Down-scale Limit]

030321E.EPS

Figure Connection Between SIO-21 and Fieldbus Function Block DO

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-31
• In order to connect the output of SIO-11 or SIO-21 to fieldbus function block DO, it is
necessary to have a calculation block such as a logical OR block in between. The
calculation block should only have the boolean output 0/1. The calculation block with
different value such as 0/2 should not be used.
Since the handshake does not function between the switch instrument block (SIO-11
or SIO-21) and DO block, the connection error cannot be detected.
Regarding to the connection between SIO-11 or SIO-21 switch instrument and the
calculation block, connect the MV of the switch instrument block to the input terminal
of the calculation block. Regarding to the connection between the operation block and
fieldbus function block DO, connect the output of the calculation block to the I/O
element (%Z) assigned to CAS terminal of the DO block.
• The answerback signals of SIO-11 and SIO-21 should be the signals from the fieldbus
function block DI.
A sample of using the answerback signals from DI block is shown as follows.

On the IOM Builder to define the process I/O terminal elements (%Z) as follows and
then connected the defined elements to the SIO-21 IN terminal.
%Znnusmm DI01.OUT RD (Connect this element to SIO-21 IN termi
nal)
%Znnusmm+1 DI02.OUT RD
Then define the fieldbus DI function blocks DI01 and DI02 to make them behave as
follows.
DI01.OUT 0 (Valve Not Open), 1 (Valve Open)
DI02.OUT 0 (Valve Not Close), 1 (Valve Close)

The output (OUT) of DI block such as [0 (Valve Not Open), 1 (Valve Open)] indicates
different situation varies with the types of the applied transducer blocks. It is necessary
to check the specification of the transducer blocks corresponding to the DI blocks, and
decide the DI block parameters properly.

After the above settings are completed, the SIO-21 should initiate the answerback
error alarms (ANS+/ANS) if the SIO-21 has output abnormality. Unless the DO block is
in CAS mode, the answerback error alarms (ANS+/ANS) occurs even when the
transducer block is in O/S mode.

TIP
• When DI01.OUT data status is BAD, the alarm status of the connected SIO-11 or SIO-21 switch
instrument block becomes IOP.
• When the fieldbus device fails, the alarm status of SIO-11 and SIO-21 becomes IOP instead of OOP.
• When the DI block DI01, assigned to %Znnusmm, becomes O/S, the alarm status of SIO-11 and
SIO-21 becomes IOP. However, if the DI block DI02, assigned to %Znnusmm+1, becomes O/S, the
alarm status of SIO-11 and SIO-21 does not become IOP.
• The alarm status of SIO-11 and SIO-21 may become PERR (answerback undefined alarm) due to
the inconsistency between FCS scan period and Fieldbus link active scheduler (LAS). If block returns
to normal status right after the occurrence of PERR, this phenomenon is not considered as an error.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-32

3.3.4 Connection to the Calculation Block


The calculation blocks that can be connected to the fieldbus block I/O terminal
parameters are indicated below.

■ List of Calculation Blocks that can be Connected : PFCS/SFCS


Calculation blocks can be connected to the fieldbus block external I/O terminal. They
cannot be connected to the fieldbus block internal parameters.
The table below gives a list of the calculation blocks that can be connected to the fieldbus
block.
Table List of Calculation Blocks that can be Connected to the Fieldbus Block (1/2) : PFCS/SFCS
Connection
Block Type Code Name
Possible
ADD Addition Block 
Arithmetic MUL Multiplication Block 
calculations DIV Division Block 
AVE Averaging Block 
SQRT Square root Block 
EXP Exponential Block 
LAG First-order lag Block 
INTEG Integration Block 
LD Derivative Block 
RAMP Ramp Block 
LDLAG Lead/lag Block 
Analog
DLAY Dead-Time Block 
calculations
DLAY-C Dead-Time Compensation Block 
AVE-M Moving-Average Block 
AVE-C Cumulative-Average Block 
FUNC-VAR Variable Line-Segment Function Block 
TPCFL Temperature and Pressure Correction Block 
ASTM1 ASTM Correction Block: Old JIS 
ASTM2 ASTM Correction Block: New JIS 
General-purpose CALCU General-Purpose Calculation Block 
calculations CALCU-C General-Purpose Calculation Block with string I/O  (*1)
030316E.EPS

: Can be connected.
-: Cannot be connected.
*1: Cannot be connected to the character string data terminal.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-33
Table List of Calculation Blocks that can be Connected to the Fieldbus Block (2/2) : PFCS/SFCS
Connection
Block Type Code Name
Possible
SW-33 Three-Pole Three-Position Selector Switch Block 
SW-91 One-Pole Nine-Position Selector Switch Block 
DSW-16 Selector Switch Block for 16 Data 
DSW-16C Selector Switch Block for 16 String Data -
DSET Data Set Block 
Calculation DSET-PVI Data Set Block with Input Indicator 
auxiliary BDSET-1C One-Batch String Data Set Block -
BDSET-1L One-Batch Data Set Block -
BDSET-2C Two-Batch String Data Set Block -
BDSET-2L Two-Batch Data Set Block -
BDA-C Batch String Data Acquisition Block -
BDA-L Batch Data Acquisition Block -
030317E.EPS

: Can be connected.
-: Cannot be connected.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-34
■ List of Calculation Blocks that can be Connected : LFCS2/LFCS £
Calculation blocks can be connected to the fieldbus block external I/O terminal. They
cannot be connected to the fieldbus block internal parameters.
The table below gives a list of the calculation blocks that can be connected to the fieldbus
block.
Table List of Calculation Blocks that can be Connected to the Fieldbus Block (1/2) : LFCS2/LFCS
£
Connection
Block Type Code Name
Possible
ADD Addition Block 
Arithmetic MUL Multiplication Block 
calculations DIV Division Block 
AVE Averaging Block 
SQRT Square root Block 
EXP Exponential Block 
LAG First-order lag Block 
INTEG Integration Block 
LD Derivative Block 
RAMP Ramp Block 
LDLAG Lead/lag Block 
Analog
DLAY Dead-Time Block 
calculations
DLAY-C Dead-Time Compensation Block 
AVE-M Moving-Average Block 
AVE-C Cumulative-Average Block 
FUNC-VAR Variable Line-Segment Function Block 
TPCFL Temperature and Pressure Correction Block 
ASTM1 ASTM Correction Block: Old JIS 
ASTM2 ASTM Correction Block: New JIS 
General-purpose CALCU General-Purpose Calculation Block 
calculations CALCU-C General-Purpose Calculation Block with String I/O  (*1)
030318E.EPS

: Can be connected.
-: Cannot be connected.
*1: Cannot be connected to the character string data terminal.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-35
Table List of Calculation Blocks that can be Connected to the Fieldbus Block (2/2) : LFCS2/LFCS
£
Connection
Block Type Code Name
Possible
SW-33 Three-Pole Three-Position Selector Switch Block 
SW-91 One-Pole Nine-Position Selector Switch Block 
DSW-16 Selector Switch Block for 16 Data 
DSW-16C Selector Switch Block for 16 String Data -
DSET Data Set Block 
DSET-PVI Data Set Block with Input Indicator 
Auxiliary
BDSET-1C One-Batch String Data Set Block -
BDSET-1L One-Batch Data Set Block -
BDSET-2C Two-Batch String Data Set Block -
BDSET-2L Two-Batch Data Set Block -
BDA-C Batch String Data Acquisition Block -
BDA-L Batch Data Acquisition Block -
AND Logical AND Block 
OR Logical OR Block 
NOT Logical NOT Block 
SRS1-S Set-Dominant Flip-Flop Block with 1 Output 
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output 
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs 
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs 
WOUT Wipeout Block 
Logical operation OND ON-Delay Timer Block 
block OFFD OFF-Delay Timer Block 
TON One-Shot Block (Rising-Edge Trigger) 
TOFF One-Shot Block (Falling-Edge Trigger) 
GT Comparator Block (Greater Than) 
GE Comparator Block (Greater Than or Equal) 
EQ Equal Operator Block 
BAND Bitwise AND Block -
BOR Bitwise OR Block -
BNOT Bitwise NOT Block -
030319E.EPS

: Can be connected.
-: Cannot be connected.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-36

3.3.5 Connection to the Off-Site Block


The off-site blocks that can be connected to the fieldbus block I/O terminal param-
eters are indicated below.

■ List of Off-Site Blocks that can be Connected £


Off-site blocks can be connected to the fieldbus block’s external I/O terminal. They cannot
be connected to the fieldbus block internal parameters.
The table below gives a list of the off-site blocks that can be connected to the fieldbus block.
Table List of Off-Site Blocks that can be Connected to the Fieldbus Block £
Connection
Code Name
Possible
FSBSET Batch Set Control Block 
BLEND Blending Master Control Block -
030320E.EPS

: Can be connected.
-: Cannot be connected.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-37

3.3.6 List of Parameters that can be Connected


This section explains the fieldbus block parameters that can be connected to the I/O
terminal of an FCS function block.

■ Parameters that can be Connected to an FCS Function Block


The parameters that can be connected refer to those fieldbus block parameters that can be
assigned to the ACF11 terminal numbers (%Znnusrrun). Parameters that have been
assigned to terminal numbers can be connected to the FCS function block I/O terminals.
The parameters that can be connected are listed below by type of fieldbus block.

● Notes when Referencing the Parameter Lists


The items marked with “-” indicate that they cannot be defined to ACF11 terminal numbers.
“Readback parameter,” “VIEW No” and “Communication module,” are not definition items on
the builder. The readback parameter is automatically connected.

● A Note when Setting Definitions on the Builder Screen


The fieldbus block parameters MODE_BLK and ALARM_SUM can only be connected to a
faceplate block.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-38
■ Resource Block (R_B)
Table List of Resource Block (R_B) Parameters
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
ALARM_SUM - RD ALARM 1 D_RD
030321E.EPS

■ Analog Input Block (AI)


Table List of Analog Input Block (AI) Parameters
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
PV - RD AF32S 1 D_RD
OUT - RD AF32S 0 CAS_RD
Write enabled only
OUT OUT WT AF32S 1 D_RW when block mode is
MAN
FIELD_VAL - RD AF32S 1 D_RD
ALARM_SUM - RD ALARM 1 D_RD
030322E.EPS

■ Analog Output Block (AO)


Table List of Analog Output Block (AO) Parameters
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
PV - RD AF32S 1 D_RD
SP - RD AF32S 1 D_RD
Write enabled only
SP SP WT AF32S 1 D_RW when block mode is
AUTO or MAN
OUT - RD AF32S 1 D_RD
Write enabled only
OUT OUT WT AF32S 1 D_RW when block mode is
MAN
READBACK - RD AF32S 1 D_RD
CAS_IN - RD AF32S 1 D_RD When monitoring
CAS_IN BKCAL_OUT WT AF32S 0 CAS_RW When configuring
control loop
SP_HI_LIM - RD AF32 2 S_RD
SP_HI_LIM SP_HI_LIM WT AF32 2 S_RW
SP_LO_LIM - RD AF32 2 S_RD
SP_LO_LIM SP_LO_LIM WT AF32 2 S_RW
RCAS_IN(*1) RCAS_OUT(*1) WT AF32S 0 CAS_RW
030323E.EPS

*1: Connecting to RCAS_IN, RCAS_OUT is not yet supported.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-39
■ Discrete Input Block (DI)
Table List of Discrete Input Block (DI) Parameters
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
PV - RD DS 1 D_RD
OUT_D - RD DS 0 CAS_RD
Write enabled only
OUT_D OUT_D WT DS 1 D_RW when block mode is
MAN
FIELD_VAL_D - RD DS 1 D_RD
ALARM_SUM - RD ALARM 1 D_RD
030324E.EPS

■ Discrete Output Block (DO)


Table List of Parameters for Discrete Output Block (DO)
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
PV_D - RD DS 1 D_RD
SP_D - RD DS 1 D_RD
Write enabled only
SP_D SP_D WT DS 1 D_RW when block mode is
AUTO or MAN
OUT_D - RD DS 1 D_RD
Write enabled only
OUT_D OUT_D WT DS 1 D_RW when block mode is
MAN
READBACK_D - RD DS 1 D_RD
CAS_IN_D - RD DS 1 D_RD When monitoring
CAS_IN_D BKCAL_OUT_D WT DS 0 CAS_RW When configuring
control loop
When configuring
RCAS_IN_D(*1) RCAS_OUT_D(*1) WT DS 0 CAS_RW
control loop
030325E.EPS

*1: Connecting to RCAS_IN_D, RCAS_OUT_D is not yet supported.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-40
■ PID Controller Block (PID)
Table List of PID Controller Block (PID) Parameters
Readback Communication
Parameter Direction Data type VIEW No Remarks
parameter Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
PV - RD AF32S 1 D_RD
SP - RD AF32S 1 D_RD
Write enabled only
SP SP WT AF32S 1 D_RW when block mode is
AUTO or MAN
OUT - RD AF32S 1 D_RD
Write enabled only
OUT OUT WT AF32S 1 D_RW when block mode is
MAN
CAS_IN - RD AF32S 1 D_RD When monitoring
CAS_IN BKCAL_OUT WT AF32S 0 CAS_RW When configuring
control loop
SP_HI_LIM - RD AF32 2 S_RD
SP_HI_LIM SP_HI_LIM WT AF32 2 S_RW
SP_LO_LIM - RD AF32 2 S_RD
SP_LO_LIM SP_LO_LIM WT AF32 2 S_RW
OUT_HI_LIM - RD AF32 2 S_RD
OUT_HI_LIM OUT_HI_LIM WT AF32 2 S_RW
OUT_LO_LIM - RD AF32 2 S_RD
OUT_LO_LIM OUT_LO_LIM WT AF32 2 S_RW
RCAS_IN(*1) RCAS_OUT(*1) WT AF32S 0 CAS_RW
ROUT_IN(*1) ROUT_OUT(*1) WT AF32S 0 CAS_RW
TRK_IN_D - RD DS 1 D_RD When monitoring
TRK_VAL - RD AF32S 1 D_RD When monitoring
FF_VAL - WT AF32S 0 CAS_WT
ALARM_SUM - RD ALARM 1 D_RD
030326E.EPS

*1: Connecting RCAS_IN, RCAS_OUT, ROUT_IN, ROUT_OUT to FCS function block is not yet supported.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-41
■ Ratio Set Block (RA)
Table List of Ratio Set Block (RA) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
ALARM_SUM — RD ALARM 1 D_RD
PV — RD AF32S 1 D_RD
SP — RD AF32S 1 D_RD
SP SP WT AF32S 1 D_RW Write enabled only
when block mode is
AUTO or MAN.
OUT — RD AF32S 0 D_RD
OUT OUT WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
CAS_IN — RD AF32S 1 D_RD When monitoring;
CAS_IN BKCAL_OUT WT AF32S 0 CAS_RW When in a control loop
SP_HI_LIM — RD AF32 2 S_RD
SP_HI_LIM SP_HI_LIM WT AF32 2 S_RW
SP_LO_LIM — RD AF32 2 S_RD
SP_LO_LIM SP_LO_LIM WT AF32 2 S_RW
OUT_HI_LIM — RD AF32 2 S_RD
OUT_HI_LIM OUT_HI_LIM WT AF32 2 S_RW
OUT_LO_LIM — RD AF32 2 S_RD
OUT_LO_LIM OUT_LO_LIM WT AF32 2 S_RW
RCAS_IN(*1) RCAS_OUT(*1) WT AF32S 0 CAS_RW
TRK_IN_D — RD DS 1 D_RD When monitoring
TRK_VAL — RD AF32S 1 D_RD When monitoring
030327E.EPS

*1: Connecting RCAS_IN, RCAS_OUT to function blocks is not supported.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-42
■ Control Selector Block (CS)
Table List of Control Selector Block (CS) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT — RD AF32S 0 D_RD
OUT OUT WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
SEL_1 — RD AF32S 1 D_RD When monitoring;
SEL_1 BKCAL_SEL_1 WT AF32S 0 CAS_RW When in a control loop.
SEL_2 — RD AF32S 1 D_RD When monitoring;
SEL_2 BKCAL_SEL_2 WT AF32S 0 CAS_RW When in a control loop.
SEL_3 — RD AF32S 1 D_RD When monitoring;
SEL_3 BKCAL_SEL_3 WT AF32S 0 CAS_RW When in a control loop.
OUT_HI_LIM — RD AF32 2 S_RD
OUT_HI_LIM OUT_HI_LIM WT AF32 2 S_RW
OUT_LO_LIM — RD AF32 2 S_RD
OUT_LO_LIM OUT_LO_LIM WT AF32 2 S_RW
030328E.EPS

■ Output Splitter Block (OS)


Table List of Output Splitter Block (OS) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
SP — RD AF32S 1 D_RD
SP SP WT AF32S 1 D_RW
OUT_1 — RD AF32S 0 D_RD
OUT_1 OUT_1 WT AF32S 1 D_RW Write enabled only
when block mode
supports MAN.
OUT_2 — RD AF32S 0 D_RD
OUT_2 OUT_2 WT AF32S 1 D_RW Write enabled only
when block mode
supports MAN.
CAS_IN — RD AF32S 1 D_RD When monitoring;
CAS_IN BKCAL_OUT WT AF32S 0 CAS_RW When in a control loop.
030329E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-43
■ Signal Characterizer Block (SC)
Table List of Signal Characterizer Block (SC) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT_1 — RD AF32S 0 D_RD
OUT_1 OUT_1 WT AF32S 1 D_RW Write enabled only
when block mode
supports MAN.
OUT_2 — RD AF32S 0 D_RD
OUT_2 OUT_2 WT AF32S 1 D_RW Write enabled only
when block mode
supports MAN.
030330E.EPS

■ Integrator Block (IT)


Table List of Integrator Block (IT) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT — RD AF32S 1 D_RD
OUT OUT WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
OUT_TRIP — RD AF32S 1 D_RD
OUT_TRIP OUT_TRIP WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
OUT_PTRIP — RD AF32S 1 D_RD
OUT_PTRIP OUT_PTRIP WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
030331E.EPS

■ Input Selector Block (IS)


Table List of Input Selector Block (IS) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT — RD AF32S 1 D_RD
OUT OUT WT AF32S 1 D_RW Write enabled only
when block mode is
MAN.
SELECTED — RD AF32S 1 R_RD
030332E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-44
■ Multiple Discrete Input Block (MDI)
Table List of Multiple Discrete Input Block (MDI) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT_D1 — RD DS 0 CAS_RD
OUT_D1 OUT_D1 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D2 — RD DS 0 CAS_RD
OUT_D2 OUT_D2 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D3 — RD DS 0 CAS_RD
OUT_D3 OUT_D3 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D4 — RD DS 0 CAS_RD
OUT_D4 OUT_D4 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D5 — RD DS 0 CAS_RD
OUT_D5 OUT_D5 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D6 — RD DS 0 CAS_RD
OUT_D6 OUT_D6 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D7 — RD DS 0 CAS_RD
OUT_D7 OUT_D7 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
OUT_D8 — RD DS 0 CAS_RD
OUT_D8 OUT_D8 WT DS 1 D_RW Write enabled only
when block mode is
MAN.
030333E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-45
■ Multiple Discrete Output Block (MDO)

IMPORTANT
• When using Fieldbus Engineering Tool FB editor to create FBAP drawings, do not use
the FB editor's "connection terminals" to connect the MDO inputs (IN_DN:N=1 to 8) to
FCS I/Os. Otherwise, the control data cannot be transmitted.
• The data updating period is in proportional to the number of manipulations to the MDO
inputs. It ranges between 1 to 8 seconds.

Table List of Multiple Discrete Output Block (MDO) Parameters


Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
IN_D1 IN_D1 WT DS 1 D_RW
IN_D2 IN_D2 WT DS 1 D_RW
IN_D3 IN_D3 WT DS 1 D_RW
IN_D4 IN_D4 WT DS 1 D_RW
IN_D5 IN_D5 WT DS 1 D_RW
IN_D6 IN_D6 WT DS 1 D_RW
IN_D7 IN_D7 WT DS 1 D_RW
IN_D8 IN_D8 WT DS 1 D_RW
030334E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-46
■ Multiple Analog Input Block (MAI)
Table List of Multiple Analog Input Block (MAI) Parameters
Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
OUT_1 – RD AF32S 0 CAS_RD

OUT_1 OUT_1 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_2 – RD AF32S 0 CAS_RD

OUT_2 OUT_2 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_3 – RD AF32S 0 CAS_RD

OUT_3 OUT_3 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_4 – RD AF32S 0 CAS_RD

OUT_4 OUT_4 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_5 – RD AF32S 0 CAS_RD

OUT_5 OUT_5 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_6 – RD AF32S 0 CAS_RD

OUT_6 OUT_6 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_7 – RD AF32S 0 CAS_RD

OUT_7 OUT_7 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
OUT_8 – RD AF32S 0 CAS_RD

OUT_8 OUT_8 WT AF32S 1 D_RW Write is allowed when


block mode is MAN.
030335E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-47
■ Multiple Analog Output Block (MAO)

IMPORTANT
• When using Fieldbus Engineering Tool FB editor to create FBAP drawings, do not use
the FB editor's "connection terminals" to connect the MAO inputs (IN_N:N=1 to 8) to
FCS I/Os. Otherwise, the control data cannot be transmitted.
• The data updating period is in proportional to the number of manipulations to the MAO
inputs. It ranges between 1 to 8 seconds.

Table List of Multiple Analog Output Block (MAO) Parameters


Communication
Parameter Readback Parameter Direction Data Type VIEW No. Remarks
Model
MODE_BLK MODE_BLK WT MODE 1 D_RW
IN_1 IN_1 WT AF32S 1 D_RW
IN_2 IN_2 WT AF32S 1 D_RW
IN_3 IN_3 WT AF32S 1 D_RW
IN_4 IN_4 WT AF32S 1 D_RW
IN_5 IN_5 WT AF32S 1 D_RW
IN_6 IN_6 WT AF32S 1 D_RW
IN_7 IN_7 WT AF32S 1 D_RW
IN_8 IN_8 WT AF32S 1 D_RW
030336E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-48

3.4 Reliability
This section explains the Reliability in the connection to the fieldbus block.

SEE ALSO
For information about the Fieldbus system with Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
B1, "FCS Fieldbus Compatibility" in CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
B1, "FCS Fieldbus Compatibility" in CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

■ Operation in Response to the Power Failure and Failure Mode :


PFCS/SFCS
For power failure and failure, a power failure and failure mode in conjunction with the
contents of the fault that occurred, is provided. When a fault occurs, output of process I/O or
FCS control action in response to the respective power failure and failure mode is per-
formed.
Table Output of Process I/O and FCS Control action By Power Failure and Failure Mode :
PFCS/SFCS

Power failure and Output of process I/O FCS control action


failure mode At occurrence At recovery At occurrence At recovery
FBD single power
- Initialization start (*4) MAN fallback Output restart
failure
Initialization start or
FCS power failure - -
restart
Fieldbus device
-
maintenance (*3)
ACF11 maintenance Fault state operation (*1)
Initialization start (*4)
Fieldbus device
- MAN fallback Output restart
failure (*3)
Fieldbus transmission
stop Fault state operation (*1)
ACF11 operation stop
CPU operation stop Fault state operation (*2) Output restart - Initialization start
Processor unit control
No change No change No change Restart
right switching
030401E.EPS

*1: Fault state operation for the fieldbus device is executed. If power is still being supplied to the fieldbus, this operates.
*2: Fault state operation for the fieldbus device is forcibly executed.
*3: The operation is the same as when there is a prolonged power failure in a single power failure for the fieldbus device.
*4: Output value tracking is performed.

Operations in the above table assume the following operation and processing.

● Fault State Operation in the I/O Module : PFCS/SFCS


When a fieldbus device or an FCS recovers from power failure state, the output values held
at the moment just prior to the power failure may be used depending on the recovery
function when the output operation restarts.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<3. FCS Control Function Using Fieldbus> 3-49
■ Operation in Response to the Power Failure and Failure Mode :
LFCS2/LFCS £
For power failure and breakdowns, a power failure and failure mode in conjunction with the
contents of the fault that occurred, is provided. When a fault occurs, output of process I/O or
FCS control action in response to the respective power failure and failure mode is per-
formed.
Table Output of Process I/O and FCS Control Action by Power Failure and Failure Mode : LFCS2/
LFCS £

Power failure and Output of process I/O FCS control action


failure mode At occurrence At recovery At occurrence At recovery
FBD single power Operation of
- Initialization start (*4)
failure process I/O
Output restart
ACF11 single power when a power
Fault state operation (*1) failure occurs
failure
Output restart
FCU single power
Fault state operation (*2) Initialization start
failure -
or restart
FCS power failure -
Fieldbus device
-
maintenance (*3)
ACF11 maintenance Fault state operation (*1)
Fieldbus device Initialization start (*4)
failure (*3) - MAN fallback Output restart
Fieldbus transmission
stop
Fault state operation (*1)
ACF11 operation
stop
FCU operation stop Fault state operation (*2) Output restart - Initialization start
Processor unit
No change No change No change Restart
control right switching
030402E.EPS

*1: Fault state operation for the fieldbus device is executed. If power is still being supplied to the fieldbus, this operates.
*2: Fault state operation for the fieldbus device is forcibly executed.
*3: The operation is the same as when there is a prolonged power failure in a single power failure for the fieldbus device.
*4: Output value tracking is performed.

Operations in the above table assume the following operation and processing.

● Fault State Operation in the Process I/O Module : LFCS2/LFCS £


When a fieldbus device or an FCS recovers from power failure state, the output values held
at the moment just prior to the power failure may be used depending on the recovery
function when the output operation restarts.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-50
■ Control Action When FCS Loses Power : PFCS/SFCS
When FCS loses power supply, the fieldbus block behaves differently according to the
elapsed time of the power failure (TIM) is longer or shorter than the fieldbus block fault state
detection time (Tfs). While the FCS function block connected will change to IMAN (AUT)
mode after an FCS power failure events regardless of the elapsed time of the power failure.
The control actions are illustrated as follows. The actions illustrated is under the condition
that the power supply for fieldbus devices are guaranteed by external power sources and
the FCS start condition is set as AUTO (Restart).

● When Power Failure Time (TIM) is Longer Than Fault State Detection Time
(Tfs) : PFCS/SFCS
AC power supply
for an FCS

TIM Tih
Block mode of FCS
function block
AUT IMAN(AUT) AUT

Tfs
Block mode of
fieldbus block
CAS LO IMAN(AUT) CAS

Output of fieldbus block


(AO block, in this case)
030403E.EPS

Figure When Power Failure (TIM) Time is Longer Than Fault State Detection Time (Tfs) : PFCS/
SFCS

• When FCS power failure duration exceeds the fault state detection time (Tfs):
The fieldbus block performs fault state operation, and the fieldbus block mode be-
comes LO. At this time, the fieldbus block either holds its current output value or
outputs a user defined value.
• When FCS Recovers from Power Failure:
The ACF11 starts initialization and the fieldbus block mode is kept as LO, so the FCS
function block mode is IMAN (AUT).
When the ACF11 initialization and output value tracking is completed (execution time
Tih), the FCS function block mode changes to AUT and the fieldbus block mode
changes to CAS to start the output.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-51
● When Power Failure Time (TIM) is Shorter Than Fault State Detection Time
(Tfs) : PFCS/SFCS
AC power supply
for an FCS

TIM Ti
Block mode of FCS
function block
AUT IMAN(AUT) AUT

Block mode of
fieldbus block
CAS

Output of fieldbus block


(AO block, in this case)

030404E.EPS

Figure When Power Failure (TIM) Time is Shorter Than Fault State Detection Time (Tfs) : PFCS/
SFCS

• At the Moment of FCS Momentary Power Failure:


The fieldbus block does not perform fault state operation, and there is no change on its
output.
• When FCS Recovers from the Momentary Power Failure:
ACF11 starts initialization while “No communication with fieldbus” is indicated as the
data status. At this moment, the FCS function block mode is IMAN (AUT). When
ACF11 initialization is completed (execution time Ti), the FCS function block changes
to AUT.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-52
■ Control action When the Process I/O Section Has a Power Failure :
LFCS2/LFCS £
FCS function block and fieldbus block perform the following operation when the process I/O
section has a power failure, or in the cases of RIO bus transmission stops, node operation
stops and ACF11 operation stops.
The following explanation takes the case where the process I/O section has a power failure
as an example. In other cases, the operations for the FCS function block and the fieldbus
block are the same as for the process I/O power failure.
When the process I/O section stops operating, the fieldbus block operation differs accord-
ing to whether the power failure time (TIM) is longer or shorter than the fieldbus block fault
state detection time (Tfs). Whether the power failure time is longer or shorter, the FCS
function block mode temporarily changes to IMAN (AUT) mode. Due to this condition, the
restart operation during the process I/O power failure will differ depending on whether the
communication module is the ACF11, or another module. Control action when the ACF11
stops operating is indicated below. The control action described here is based on the
assumption that the power supply to the fieldbus device is maintained by the external bus
power supply.

● When the power failure time (TIM) is longer than the fault state detection
time (Tfs) : LFCS2/LFCS £
PI/O AC
power supply

TIM Tih
Block mode of
FCS function block
AUT IMAN(AUT) AUT

Tfs
Block mode of
fieldbus block
CAS LO IMAN(AUT) CAS

Output of fieldbus block


(AO block, in this case)
030405E.EPS

Figure When the Power Failure Time (TIM) is Longer than the Fault State Detection Time (Tfs) :
LFCS2/LFCS £

• After the fault state detection time (Tfs) has elapsed from when the process I/O sec-
tion has a power failure:
The fieldbus block performs fault state operation, and the fieldbus block mode be-
comes LO. At this time, fieldbus block output changes to hold or to a user defined
value.
• When the process I/O section recovers power:
The ACF11 recovers from a momentary power failure. At this time, the ACF11 under-
goes initialization and the fieldbus block mode is LO. Because of this, the FCS function
block mode changes to IMAN (AUT).
When the ACF11 initialization and output value tracking is completed (execution time
Tih), the FCS function block mode is restored to AUT and the fieldbus block mode is
restored to CAS. This restarts output.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<3. FCS Control Function Using Fieldbus> 3-53
● When the power failure time (TIM) is shorter than the fault state detection
time (Tfs) : LFCS2/LFCS £
PI/O AC
power supply

TIM Ti
Block mode of
FCS function block AUT IMAN(AUT) AUT

Block mode of
fieldbus block
CAS

Output of fieldbus block


(AO block, in this case)
030406E.EPS

Figure When the Power Failure Time (TIM) is Shorter than the Fault State Detection Time (Tfs) :
LFCS2/LFCS £

• When the process I/O section has a power failure:


The fieldbus block fault state operation is not performed, and output does not change.
• When the process I/O section recovers power:
ACF11 undergoes initialization, and “Not communicating with the fieldbus” is displayed
as the data status. At this time, the FCS function block mode changes to IMAN (AUT).
When ACF11 initialization is completed (execution time Ti), the FCS function block is
restored to AUT.

■ Control Action when the Processor Section Stops Operating :


PFCS/SFCS
When the FCS processor section stops because of an error, the fallback operation is
performed by the ACF11. When the FCS processor section recovers from the error, the
fallback operation stops.
• When fallback starts:
Fault state execution is requested to the fieldbus device from ACF11.
• When fallback stops:
A request to cancel fault state execution is sent to the fieldbus device from ACF11.

■ Control Action when RIO Bus Transmission Stops or FCU Operation


Stops : LFCS2/LFCS £
When RIO bus transmission or FCU operation stops due to a power failure or error, fallback
operation is executed by the ACF11. When there is a recovery from the power failure or
error, the fallback operation stops.
• When fallback starts:
Fault state execution is requested to the fieldbus device from ACF11.
• When fallback stops:
A request to cancel fault state execution is sent to the fieldbus device from ACF11.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


Blank Page
<4. System Builders Related to Fieldbus> 4-1

4. System Builders Related to Fieldbus


This chapter explains CENTUM VP/CS 3000/CS 1000 system builders related to the
fieldbus used to perform fieldbus engineering. The startup procedure for fieldbus
system and the revision procedure after startup are also explained.
Note that the fieldbus engineering described in this chapter only covers the engi-
neering for the fieldbus system can be carried out in the scope of system builders
including the upper lager system engineering related to ACF11.

SEE ALSO
For information about the system builders regarding to Fieldbus communication module (ALF111)
connected to CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-2

4.1 What is Fieldbus Engineering?


A system configured with fieldbus can be separated into upper level system and
lower level system with the ACF11 module as the boundary. The fieldbus engineering
for the upper level system can be performed using CENTUM VP/CS 3000/CS 1000
system builders installed in an HIS.

■ Fieldbus Engineering for Upper Level System


Fieldbus engineering for upper level system is mainly composed of the definition of the
fieldbus communication module (ACF11), assignment of fieldbus block parameters to the
ACF11 software terminals (%Znnusmm), and connection of the ACF11 software terminals
and the FCS function blocks. Through these operations, the logical correlation between the
fieldbus devices connected to the fieldbus and the ACF11 software terminals can be
established, so that data can be exchanged between the fieldbus devices and the FCS
function blocks.

Ethernet

HIS Master PC

Fieldbus engineering for upper level system


• Definition of ACF11
• Assignment of fieldbus block parameters
to ACF11 software terminals
• Connection of ACF11 software terminals
and FCS function blocks
Control bus
FCS

Upper level system

Lower level system

PC connected
to H1 Fieldbus
ACF11

• FieldMate

H1 fieldbus

Fieldbus device Fieldbus device

040101E.EPS

Figure Fieldbus Engineering for Upper Level System

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-3

4.1.1 Positioning of Fieldbus-Related System Builders


The following diagram shows the positioning of the fieldbus-related CENTUM VP/CS
3000/CS 1000 system builders within the overall configuration of a fieldbus system
and the positioning of the fieldbus-related system builders within the overall engi-
neering flow for the fieldbus system.

■ Positioning Within the Overall Fieldbus System ¡


The CENTUM CS 1000 system builders are implemented in the HIS. The positioning of the
system builders within the overall fieldbus system is shown below.

Ethernet

HIS Master PC

CENTUM CS 1000
system builders

Control bus
PFCS

PC connected
to H1 Fieldbus

ACF11 • FieldMate

H1 fieldbus

Fieldbus device Fieldbus device


040102E.EPS
HIS: Human Interface Station
Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
PFCS: Control station
ACF11: Fieldbus communication module

Figure Positioning of CENTUM CS 1000 System Builders Within the Overall Fieldbus System ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-4
■ Positioning Within the Overall Fieldbus System £
The system builders are implemented in the HIS. The positioning of the system builders
within the overall fieldbus system is shown below.

Ethernet

HIS Master PC

CENTUM VP/CS 3000


system builders

Control bus
LFCS2/LFCS SFCS
FCU

FCU
RIO bus PC connected
to H1 Fieldbus
NIU
ACF11 • FieldMate
ACF11

H1 fieldbus

Fieldbus device Fieldbus device


040103E.EPS
HIS: Human Interface Station
Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
SFCS: Control station (compact type)
LFCS2/LFCS: Control station
FCU: Field control unit
RIO bus: Remote I/O bus
NIU: Node interface unit
ACF11: Fieldbus communication module

Figure Positioning of CENTUM VP/CS 3000 System Builders Within the Overall Fieldbus System
£

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-5
■ Positioning within the Engineering Flow
The positioning of the system builders within the engineering flow for the overall fieldbus
system is shown below.

System design

Creation of I/O list

Selection of
Control loop design Construction
fieldbus devices

Engineering Engineering Using FieldMate to configure


with the system with the fieldbus tag name and node address
builders engineering tool of Physical Device. (*1)

Individual
device setting

On-line debug Legend


/loop check
Work flow
Flow of output information

Test operation Engineering performed with


system builders

Application/service

040104E.EPS
*1: When the following condition is satisfied, the engineering work by FieldMate on the PC connected to H1 fieldbus is not
required.
The physical device tag names and node addresses are already configured in the field devices.

The tag names and node addresses of physical devices can be configured using Fieldbus Engineering Tool.

Figure Positioning of CENTUM VP/CS 3000/CS 1000 System Builders within the Engineering Flow

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-6

4.1.2 Fieldbus Engineering Flow


The basic flow of fieldbus engineering is shown below.

■ Basic Flow of Fieldbus Engineering

Engineering start

Fieldbus system design

Define ACF11

Download to ACF11
from system view

Engineering using
Define ACF11 terminal number
the fieldbus engineering tool (*2)

Download from the IOM


builder to the FCS and ACF11 (*1)

Download to the fieldbus device

Connect the ACF11 terminal


number and FCS function block

Parameter adjustment

Legend
Upload parameters Workflow
(HIS or Master PC)
Operation performed by
the system builders
Operation performed by other tools
Engineering completed without using the system builders

040105E.EPS

Figure Basic Flow of Fieldbus Engineering

*1: If the data defined on Fieldbus Engineering Tool are saved under the designated directory, these data will be down-
loaded together to ACF11.
*2: Engineering can be performed on HIS or master PC.

TIP
When using Fieldbus Engineering Tool to perform online maintenance to the fieldbus devices connected
to the H1 fieldbus, the physical device tag names and the node addresses should be set to the devices
before hand.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-7
● Fieldbus System Design
The fieldbus devices configuration, fieldbus block configuration, communication specifica-
tions, and control specifications are designed.

TIP
When performing the fieldbus engineering works, the Capabilities files and the DD files of the
corresponding fieldbus physical devices are required. You need to get these files ready before starting the
engineering works.

● Definition of the ACF11


New registration and setting of the fieldbus communication module (ACF11) are performed.
Also, the directory where definition data is located is specified in order to import definition
data for the Fieldbus Engineering Tool.
This operation is done using The new IOM dialog box called from the system builders of
System View.

● Downloading from System View to the ACF11


Definition data is downloaded to the ACF11.
This operation is done using the system builders of System View.

● Engineering Using the Fieldbus Engineering Tool


Engineering for the lower layer system including the ACF11 is performed. The fieldbus
device configuration, fieldbus block configuration and definitions related to communication
information are performed, and generation is executed.
This can be done using the Fieldbus Engineering Tool installed in HIS or master PC.
If the CENTUM VP/CS 3000/CS 1000 system builders and Fieldbus Engineering Tool are
residing in the same machine, the Fieldbus Engineering Tool can be started from the IOM
Builder of the system builders.

TIP
Even when engineering for the lower level system is done using the engineering tool of another manufac-
turer, the Yokogawa Electric’s fieldbus engineering tool is required for data definitions related to the
ACF11.

SEE ALSO
For more information about the engineering using the fieldbus engineering tool, see the following:
5, “Fieldbus Engineering Tool”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-8
● Definition of the ACF11 Terminal Number
Fieldbus block parameters are assigned to the ACF11 terminal number. This operation is
done using the IOM Builder of the system builders.

● Downloading from the IOM Builder to the FCS and ACF11


Definition data is downloaded to the FCS and ACF11.
This operation is performed using the IOM Builder of the system builders.

TIP
If there is definition data for the fieldbus engineering tool under the directory specified in the new IOM
dialog box when ACF11 was defined, then this engineering tool definition data will also be downloaded to
the ACF11.

● Downloading to Fieldbus Devices


The data configured with Fieldbus Engineering Tool on HIS or on master PC can be down-
loaded to the field devices via ACF11 module.
The downloading will be performed by Fieldbus Engineering Tool installed on HIS or master
PC.

● Connection of ACF11 Software Terminals and FCS Function Blocks


The ACF11 software terminals and FCS function blocks may be connected using the
Control Drawing Builder of the system builders.

● Parameter Adjustment
Parameters for the fieldbus block may be adjusted.
This operation is performed using the operation and monitoring function or Device Manage-
ment Tool on HIS or master PC.

● Uploading Parameters (HIS or Master PC)


Parameters for fieldbus blocks may be uploaded to the Fieldbus Engineering Tool. Upload-
ing parameters should be performed accordingly when required parameters need to be
adjusted in Fieldbus Engineering Tool.
This can be performed using the Fieldbus Engineering Tool installed on HIS or master PC.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-9

4.1.3 Overview of System Builders Related to Fieldbus


The fieldbus-related system builders are mainly for system generation and system
test.

■ Configuration of System Builders Related to Fieldbus


Fieldbus-related system builders

System builders

System View

New IOM dialog box

IOM download

IOM Builder
(*1)
Fieldbus Engineering Tool start

Function for downloading


from IOM Builder

Control Drawing Builder

System test

Wiring

FCS simulation

Fieldbus Engineering Tool

Project manager

Various builders Host File Set

Host File Set output

Download

Legend
Calling function
Data flow

040106E.EPS
*1: When the system builders and the fieldbus engineering tool are in the same machine, this function can be called up.

Figure Configuration of System Builders Related to Fieldbus

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-10
■ CENTUM VP/CS 3000/CS 1000 System Builders
Definitions related to ACF11, assignment of fieldbus block parameters to the ACF11 termi-
nal number, and connection of the terminal number and FCS function block are performed
in the builders for system generation.

SEE ALSO
For more information about engineering in System View, see the following:
4.2, “System Builders”

● System View
Opens various system builders.

● New IOM Dialog Box


Definitions related to the ACF11 such as the loading position of the ACF11 and number of I/
O points are set. Also, the directory where definition data for the Fieldbus Engineering Tool
is specified.

● Download to IOM
Downloads definition data to the ACF11. At this time, definition data for the Fieldbus Engi-
neering Tool is also automatically downloaded to the ACF11.

● IOM Builder
This defines the ACF11 terminal number. The fieldbus block parameters are assigned to
the terminal number.

● Fieldbus Engineering Tool Start


When the System Builders and the Fieldbus Engineering Tool are used in the same ma-
chine, the project manager for the Fieldbus Engineering Tool can be called from the IOM
Builder. This becomes necessary when the system and fieldbus engineering are performed
in parallel.

● Downloading from IOM Builder


Definition data is downloaded to the ACF11. At this time, definition data for the Fieldbus
Engineering Tool is also automatically downloaded to the ACF11.

● Host File Set Read/Expansion


Imports definition data for the Fieldbus Engineering Tool. When download is executed on
IOM Builder, definition data for the Fieldbus Engineering Tool is automatically opened as
the host file set.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-11
● Control Drawing Builder
Connects the terminal number defined on IOM Builder and the I/O terminal for the FCS
function block.

TIP
For CS 1000, Control Drawing Builder is optional.

■ Test Function
System testing and debugging can be performed with test function. During the implementa-
tion of engineering, testing and debugging should be performed regularly.

SEE ALSO
For more information about the test function, see the following:
4.3, “Test Function”

● Wiring
Debugging can be performed without the fieldbus device being connected. However, a
simulation of the fieldbus block cannot be done.

● FCS Simulation
A test can be performed without using the physical FCS when using the FCS simulation.

■ Conditions for Using Fieldbus Engineering Tool


With the CENTUM VP/CS 3000/CS 1000 system builders, the Fieldbus Engineering Tool
can be called or definition data for the Fieldbus Engineering Tool can be imported. To do
this however, there are the following conditions.
Table Operation Allowed Based on Position of Fieldbus Engineering Tool Data
Installed in the Not installed in the
same machine same machine
Data is Data is not Data is Data is not
in specified in specified in specified in specified
position position position position
Fieldbus Engineering Tool start  
Host file set opens automatically when  
data downloaded
During download to IOM,
Fieldbus Engineering Tool definition data  
is downloaded to ACF11
During download from IOM Builder,
Fieldbus Engineering Tool definition data  
is downloaded to ACF11
040107E.EPS

: Can be executed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-12

4.2 System Builders


ACF11 and fieldbus related definitions can be set on the builders for system genera-
tion. For these definitions, the new IOM dialog box, IOM Builder and Control Drawing
Builder are used.

■ Builders for System Generation


The builders for system generation are shown below.

Fieldbus-related system builders

System builders

System View

New IOM dialog box

IOM download

IOM Builder

(*1)
Fieldbus Engineering Tool start

Downloading from IOM Builder

Control Drawing Builder

Fieldbus Engineering Tool

Project manager

Various builders Host File Set

Host File Set output

Download

Legend
Calling function
Data flow

040201E.EPS
*1: When the system builders and the fieldbus engineering tool are in the same machine, this function can be called up.

Figure Builders for System Generation

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-13
■ Items Need to be Defined
The table below gives a list of the items that need to be defined for ACF11.
Table List of Items That Need to be Set for ACF11
Category Item Data acquisition (*1) Remarks
Category Create New IOM dialog box
Type Create New IOM dialog box
Unit Create New IOM dialog box
Card
Slot Create New IOM dialog box
information
Node address Create New IOM dialog box
Duplicate Next Card Create New IOM dialog box Dual redundancy cannot be specified.
Information on detail setting tab.
HighSpeed Read Data Create New IOM dialog box
Fixed to 0x14.
Block tag name IOM Builder
I/O number Parameter IOM Builder
specification Direction IOM Builder
Data type IOM Builder
P & ID Tag Name IOM Builder
Tag Name IOM Builder
Tag Comment IOM Builder
Lv 1 IOM Builder
Switch Position Label IOM Builder
Tag
Label IOM Builder
information
Btn 1 IOM Builder
Btn 2 IOM Builder
Tag mark IOM Builder
Upper window IOM Builder
Help number IOM Builder
040202E.EPS

*1: Where the data is acquired from is indicated below.


• New IOM dialog box
Acquired from the new IOM dialog box setting in system view
• IOM Builder
Acquired from the IOM Builder setting

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-14

4.2.1 Create New IOM Dialog Box


The ACF11 can be configured using Create New IOM dialog box in System View.

■ Open a Create New IOM Dialog Box : PFCS/SFCS


In one section of the system view data tree, with a folder or file under FCS being selected,
select [Create new], then [IOM] from the [File] menu. The new IOM dialog box is displayed.
The new IOM dialog box has the following two tabs.
• Type and position tab
Specify the type of communication I/O module (IOM type) and the position where the
module is loaded.
• Details setting tab
Set details related to fieldbus communication such as the number of I/O points for the
ACF11 and communication error processing.

The following is an example of a new IOM dialog box display.

Create New IOM

Type and Position Set Details

IOM Type
Category AMN33 (Fieldbus Communication)

Type ACF11 (Fieldbus Communication Module)

Installation Position
Unit 1 Slot 1

Duplicate Next Card


High Speed Read

IOM Comment

OK Cancel

040203E.EPS

Figure Create New IOM Dialog Box : PFCS/SFCS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-15
■ Open a Create New IOM Dialog Box : LFCS2/LFCS £
In the data tree section of System View, with NODExx folder under FCS-IOM folder being
selected, select [Create new], then [IOM] from the [File] menu. The new IOM dialog box is
displayed.
The new IOM dialog box has the following two tabs.
• Type and position tab
Specify the type of communication I/O module (IOM type) and the position where the
module is loaded.
• Details setting tab
Set details related to fieldbus communication such as the number of I/O points for the
ACF11 and communication error processing.

The following is an example of a new IOM dialog box display.

Create New IOM

Type and Position Set Details

IOM Type
Category AMN33 (Fieldbus Communication)

Type ACF11 (Fieldbus Communication Module)

Installation Position
Unit 1 Slot 1

Duplicate Next Card


High Speed Read

IOM Comment

OK Cancel

040204E.EPS

Figure Create New IOM Dialog Box : LFCS2/LFCS £

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-16
■ Setting Items in the Type and Position Tab ¡ £
The setting items for the type and position tab is given below.

● IOM Type
Specify the type of communication I/O module used. For the IOM class, specify [Fieldbus
communication], and for the IOM type, specify [Fieldbus communication (ACF11)].

● Installation Position ¡ £
Set the items indicated below as the loading position for the ACF11.
• Unit position: 1 to 5
• Slot position: 1 to 2

Also, the slot position where the ACF11 can be loaded will differ depending on the setpoint
values for the following two items.
• [High Speed Read] in the type and position tab
• [Number of Terminals] in the details setting tab

The relationship between the settings for the two items above and the slot position where
the ACF11 can be loaded is shown in the table below.
Table Slot Position where ACF11 Can Be Loaded ¡ £
Number of
High Speed Read Slot 1 Slot 2
Terminals
Not specified 16  
Specified 16 
Not specified 32   (*1)
Specified 32  (*1)
040205E.EPS

: Can be loaded.
Blank: Cannot be loaded.
*1: ¡ £ Can be loaded only in the case of PFCS/SFCS. Cannot be loaded with the LFCS2/LFCS.

● Duplicate Next Card


This cannot be specified in the ACF11.

● High Speed Read


If only one ACF11 is loaded in 1 unit and when this item is specified, the data output from
the ACF11 can be read to the FCS at high speed.
In the default setting, this is not specified.

● IOM Comment
The comment text related to the defined ACF11 should be entered.
Up to 24 alphanumeric or 12 double-byte characters can be used.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-17
■ Setting Items in the Detail Setting Tab ¡ £
An example of the ACF11 detail setting tab is given below.

IOM Properties

Type and Position Set Details

IOM AMN33 (Fieldbus Communication)


IOM type ACF11 (Fieldbus Communication Module)
Unit 2 Slot 1
Node Address 0x 14
Number of Terminals 16

Communication Error Process


Stale Count Limit 2

Interval of Communication Establishment Retries 10 sec

Perform Fallback
Fieldbus Database Directory
Default...
Command

Revert to initial value

OK Cancel

040206E.EPS

Figure ACF11 Detail Setting Tab

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-18
● Node Address
▼ Node Address
This cannot be specified. The node address is fixed at 0x14.

● Number of Terminals : PFCS/SFCS


▼ Number of Terminals
For the number of software terminals for an ACF11, 16 or 32 can be specified. The default
setting is 16. It can be selected from the list box.
Note that when changing the number of terminals on an ACF11 already defined, it may
cause the following effects.
Table Ability to Change the Number of Terminals and Effects of Change : PFCS/SFCS
Number of Terminals Default Setting Change
With high-speed read Change is not allowed.
From 16 to 32 Change is allowed. The terminals from 17 will be
Without high-speed read
undefined.
Terminals from 17 are not defined. Change is allowed.
From 32 to 16 Change is allowed. The error message [Definitions
Terminals from 17 are defined. on terminals from 17. Delete them.] will occur when
saving or downloading the changed module.
040207E.EPS

● Number of Terminals : LFCS2/LFCS £


▼ Number of Terminals
For the number of software terminals for an ACF11, 16 or 32 can be specified. The default
setting is 16. It can be selected from the list box.
Note that when changing the number of terminals on a ACF11 already defined, it may
cause the following effects.
Table Ability to Change the Number of Terminals and Effects of Change : LFCS2/LFCS £
Number of Terminals Default Setting Change
With high-speed read Change is not allowed.
From 16 to 32 Change is allowed. The terminals from 17 will be
Without high-speed read
undefined.
Terminals from 17 are not defined. Change is allowed.

From 32 to 16 Change is allowed. The error message [Definitions


Terminals from 17 are defined. on terminals from 17. Delete them.] will occur when
saving or downloading the modified module.
040208E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-19
● Communication Error Processing
▼ Communication Error Process
The settings for Stale Count Limit and Interval of Communication Establishment Retries
should be defined.
Normally, the default settings should be used. Clicking on [Revert to initial value] resets all
settings to the default.
• Stale Count Limit
This is the limit value for the number of BNU communication error counted in the
fieldbus system. The communication between fieldbus devices and between a device
and ACF11 module is referred to as BNU (Buffered, Network Schedule, Unidirectional
Broadcast) communication. Even when BNU data transmission stops, as long as the
number of errors is within the limit specified, system does not consider it as an abnor-
mal status. Only when the limit is exceeded, system will consider it as an abnormality.
An integer between 0 and 255 can be specified.
The default is 2, and normally the default setting should be used.
If 0 is specified, system will not check the communication error.
• Interval of Communication Establishment Retries
This is the interval for the time to send the communication retry signals to re-establish
the communication between the ACF11 and the fieldbus devices. An integer between
0 and 25 (seconds) can be specified. The default setting is 10, and normally the
default setting should be used.
If 0 is specified, system will not perform the communication establishment retry.

● Perform the Fallback Operation


▼ Perform Fallback
Check this when performing the fallback operation. The default setting is to fallback.

● Fieldbus Database Directory


▼ Fieldbus Database Directory
Specify the directory in which definition data for the fieldbus engineering tool used in the
system builders is stored. This directory is called the fieldbus database directory.
The defined data under the specified directory will be used by the following operations.
• When performing an IOM download from System View.
• When performing an IOM download from FCS status display window.
• When performing an IOM download from IOM Builder.

When the [Browse] button is clicked, the dialog box for selecting the directory is displayed.
Specify the fieldbus database directory in this dialog box. The definition data under the
specified directory can be created, revised and deleted using the fieldbus engineering tool
function.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-20
● Command Line
▼ Command
To set an optional setting to an I/O module, a line of command script can be put in the field
of Command Line. For ACF11, QUBTIM (Communication Time Out) can be used to set the
tolerant time limit for waiting for a response.
QUBTIM (Communication Time Out):
This command script can be used to specify the tolerant time limit for waiting for a response
in QUB communication, one of the communication methods of Fieldbus.
Syntax:
QUBTIM=65.0 (65.0 is a default setting)

QUBTIM (Communication Time Out) can be set within the range of 0.0 to 6550.0
(seconds). The time resolution is 100 millisecond. When 0.0 is specified, the QUB
communication response time will have no limit. The default setting is 65.5 (second).

IMPORTANT
When command scripts are modified in command lines of an I/O module, downloading the
I/O module configuration will be necessary. During downloading, the I/O module will be in
FAIL state for a while. So that be careful when changing the command line.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-21

4.2.2 Download to IOM


Download to the ACF11 is executed on System View.

■ Download to ACF11 in System View


In one section of System View data tree, with the IOM folder, or NODE folder of LFCS2,
LFCS, that contains the ACF11 selected, select [IOM download], from System View [Load]
menu. The dialog box to confirm execution of download is displayed. Data defined on
system builders will be downloaded to the ACF11 from this dialog box.
When downloading from IOM Builder, the files in the same directory but defined on
Fieldbus Engineering Tool will be downloaded together with the data defined on the IOM
Builder to the ACF11 module.

TIP
When the defined data for the fieldbus engineering tool exists in the specified directory, the above
described download method will download the data to the ACF11, together the data defined by the
system builders.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-22

4.2.3 IOM Builder


With the IOM Builder, the block tag name and parameters for the fieldbus block are
assigned to various terminal numbers. In the assigned terminal numbers, direction
of the parameter data and parameter data type are defined.

■ Function of IOM Builder


As with the analog I/O module, process I/O for a fieldbus device is logically expressed by
terminal number (%Znnusmm). With the IOM Builder, the block tag name and parameters
for the fieldbus block are assigned to these terminal numbers.
After the assignment to the terminal number, the number can be connected to FCS function
blocks. For this reason, the terminal numbers are required as many as the number of
parameters in the fieldbus block connected to the FCS function block.

● Assigning a Terminal Number


The same number of terminal numbers as the number of ACF11 I/O points (16 or 32)
specified in System View, is displayed in the IOM Builder. Accordingly, the maximum num-
ber of terminal numbers that can be assigned in one ACF11 is 32. Because of this, it is
necessary to determine the fieldbus configuration, so that the total number of terminal
numbers is 32 or less.
The following is an example of assignment to a fieldbus block’s terminal number.

FCS function block


to be connected
FIC100 IN FIC100 OUT
PID PID

%Z012101 %Z012102
To assigned
software terminals
AI AO AI AO

FI-1001A VO-1004 FI-1001A VO-1004


040209E.EPS

Figure Assignment to a Terminal Number

In the IOM Builder, it is necessary to define the data direction and data type in addition to
assigning the fieldbus block’s block tag name and parameters to terminal number.
An example of the definition of a terminal number is given below. Also, the values in the
table correspond to the above figure.
Table Example of Terminal Number Definition
Terminal number Block tag name Parameter Direction Data type
%Z012101 FI-1001A OUT RD AF32S
%Z012102 VO-1004 CAS_IN WT AF32S
040210E.EPS

SEE ALSO
For more information about the fieldbus block parameters for connection assignment, see the following:
3.3.6, “List of Parameters that can be Connected”

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-23
● Example of Connecting the Faceplate Block and Internal Parameters
By connecting the fieldbus block internal parameters and the faceplate block, the internal
parameters can be referenced and set. The diagram below is an example of connecting the
faceplate block’s I/O terminals and the fieldbus block internal parameters.

MODE ALRM PV SV MV MODE MV

[INDST3] [INDST2S]
JMOD JALM JPV JSV JMV JMOD JMV

FCS
%Znnus03 %Znnus04 %Znnus05 %Znnus06 %Znnus07 %Znnus12 %Znnus13

Fieldbus
ALARM_SUM PV SP
MODE_BLK
[PID]

IN BKCAL_IN OUT

OUT CAS_IN MODE_BLK OUT

[AI] BKCAL_OUT [AO]

040211E.EPS

Figure Example of Connecting the Faceplate Block and Fieldbus Block

The table below gives an example of assignment to the terminal numbers in the above
diagram.
Table Example of Assignment to Terminal Numbers in a Faceplate Block and Fieldbus Block
Connection
Terminal number Block Parameter Contents
%Znnus01 AI OUT Output process value
%Znnus02 CAS_IN/BKCAL_OUT Setpoint
%Znnus03 MODE_BLK Block mode
%Znnus04 ALARM_SUM Alarm summary
%Znnus05 PV Process value
%Znnus06 SP Setpoint
PID
%Znnus07 OUT Output setpoint
%Znnus08 SP_HI_LIM High-limit setpoint
%Znnus09 SP_LO_LIM Low-limit setpoint
%Znnus10 OUT_HI_LIM Output high-limit
%Znnus11 OUT_LO_LIM Output low-limit
%Znnus12 MODE_BLK Block mode
AO
%Znnus13 OUT Output value
040212E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-24
■ Opening IOM Builder
Clicking on the ACF11 definition file in System View may open IOM Builder.

IOM Builder - [Pjt:MYPJT Stn:FCS0101 Train:1 Node:1 File:2-1ACF11.edf]


File Edit View Tool Window Help

Block Tag Name Terminal Number Block Tag Name Parameter Direction Data Type
Specify Block Tag Name. %Z012101 RD AF32S
%Z012102 RD AF32S
%Z012103 RD AF32S
%Z012104 RD AF32S
%Z012105 RD AF32S
%Z012106 RD AF32S
%Z012107 RD AF32S
%Z012108 RD AF32S
%Z012109 RD AF32S
%Z012110 RD AF32S
%Z012111 RD AF32S
%Z012112 RD AF32S
%Z012113 RD AF32S
%Z012114 RD AF32S

Message

Ready Position: Line 2 Column 2


040213E.EPS

Figure IOM Builder

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-25
■ Setting Items for IOM Builder
Setting items for the IOM Builder are given below.
User specification is mandatory for the block tag name, parameters, direction and data
type. For setting items where there is a setpoint value in the default, an error occurs and the
setting returns to the previous value if the setting is left blank. For setting items where the
default is a blank column, there is no problem with leaving the setting blank.

IMPORTANT
For software terminals with different numbers, the definitions of block tag name, parameters
and direction should not be duplicated. A compiler error will occur if all the three items of the
different terminals have the same definitions.

● Terminal Number ¡ £
Terminal numbers below are displayed.
%Znnusmm
%Z: Fixed
nn: Node number (*1) (01 to 08)
u: Unit number (1 to 5)
s: Slot number (1 or 2)
mm: Terminal number (01 to 16)

*1: ¡ £ In the case of PFCS/SFCS, 01 is fixed.

● Block Tag Name


▼ Block Tag Name
This is the block tag name for the fieldbus block that is assigned to the terminal number.
Always enter this item. The name can be input within 16 alphanumeric characters.

IMPORTANT
If the tag name for a fieldbus block exceeds 16 characters, a WARNING will be prompt at
the time of download. Therefore the tag name should be modified within 16 characters
using the fieldbus engineering tool.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-26
● Parameters
▼ Parameter
These are the fieldbus block parameters assigned to the terminal number. Always enter
these, make a selection from the list, or enter manually. Enter the parameters not displayed
in the list manually. Even after a parameter is selected from the list, it can be revised by
manual entry. The table below gives a list of the parameters displayed in the list.
Table Parameters Displayed in the List
Parameters displayed in the list Explanation
OUT Output value
CAS_IN Cascade setpoint
MODE_BLK Mode
ALARM_SUM Alarm summary
PV Process variable
SP Setpoint
OUT_HI_LIM Output high-limit setpoint
OUT_LO_LIM Output low-limit setpoint
SP_HI_LIM Setpoint high-limit
SP_LO_LIM Setpoint low-limit
RCAS_IN (*1) Remote cascade setpoint
ROUT_IN (*1) Remote output value
TRK_IN_D External tracking SV
TRK_VAL Tracking value
FF_VAL Feed forward value
OUT_D Output value (contact data)
CAS_IN_D Cascade setpoint (contact data)
PV_D Process variable (contact data)
SP_D Setpoint (contact data)
RCAS_IN_D (*1) Remote cascade setpoint (contact data)
040214E.EPS

*1: Connecting RCAS_IN, ROUT_IN, RCAS_IN_D to FCS function block is not yet supported.

SEE ALSO
Specification of parameters is based on Foundation Fieldbus specifications. Refer to the Foundation
Fieldbus specifications for details.

● Direction
▼ Direction
This is the direction of the exchange of data with the fieldbus block parameters. Always
specify this item. Select either [RD] or [WT] from the list.
Thd default setting is [RD].
Direction for exchange of data indicated by [RD] and [WT] is as follows.
RD: Read from the fieldbus block to the FCS.
WT: Write from the FCS to the fieldbus block

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-27
● Data Type
▼ Data Type
This is the data type of the fieldbus block. Always specify this item. Select the data type
from the list. The default is [AF32S].
The table below shows the data types that are displayed.
Table Data Types Displayed in the List
Data types displayed in the list Explanation
AI8 Analog I/O (8 bit signed integer data)

AU8 Analog I/O (8 bit unsigned integer data)

AI16 Analog I/O (16 bit signed integer data)

AU16 Analog I/O (16 bit unsigned integer data)

AI32 Analog I/O (32 bit signed integer data)

AU32 Analog I/O (32 bit unsigned integer data)

AF32 Analog I/O (32 bit signed floating point data)

AF32S Analog I/O (32 bit signed floating point data with status)
MODE Mode I/O
ALARM Alarm summary I/O
D Discrete (contact) I/O
DS Discrete (contact) I/O (with status)
040215E.EPS

● P&ID Tag Name


The P&ID tag name is optional. Enter name with up to 16 standard-width or 8 double-width
characters.

● Tag Name
The tag name is optional. The tag name can be entered only when the data type is digital I/
O. Enter the name with up to 16 alphanumeric characters. A user-defined label can also be
specified.

● Tag Comment
This is a comment attached to the tag. This item is optional. Enter a comment with up to 24
alphanumeric characters or 12 double-width characters.
Also, this is treated as a service comment when the data type is analog I/O.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-28
● Switch Position Label
This defines the key label. Make a selection from the list or enter manually. The default
setting is [ON., OFF,ON].

TIP
The “Switch Position Label” and the “Help Window Name” setting items described here are only required
when the I/O data type is digital.

● Label
This is the display position of the label. Select either “Direct” or “Reverse”. The recom-
mended position is “Direct”.
The default setting is “Direct”.

● Btn 1, Btn 2
This is the Button color for the tag list. Make a selection from the list or manually enter the
code that indicates the color. The default is [Red].

● Lv 1
This is the security level for the data. Select levels 1 to 8 from the list. The recommended
level is 4. The default setting is 4.

● Tag Mark - Detailed Setting Items


This is the tag mark type. Make a selection from the list.
The default setting is “General”.

● Upper Window - Detailed Setting Items


This is the window name when extending to the upper screen. This item is optional.

● Help - Detailed Setting Items


This is the help message number defined by the user. This item is optional.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-29

4.2.4 Download from IOM Builder


When download is executed in the IOM Builder, on-line load to the FCS and down-
load to the ACF11 are performed. If there are definition data for the fieldbus engineer-
ing tool under the directory specified in System View, this definition data will also be
downloaded to the ACF11.

■ Download to FCS and ACF11 in IOM Builder


The following download is executed when [Download] is selected from the [File] menu of
the IOM Builder.
• On-line load to the FCS
• Download of system builders definition data to the ACF11

If there are definition data for the fieldbus engineering tool under the directory specified in
System View, this definition data will also be downloaded to the ACF11.

IMPORTANT
• Even when there are no modifications in the system builders, definition data of the
system builders will be downloaded to the ACF11.
• If fieldbus engineering tool data does not exist in the specified position, definition data
for the fieldbus engineering tool is not downloaded to the ACF11. In this case, WARN-
ING is generated and only data defined in the system builders is downloaded to the
ACF11.
• When download of definition data for the fieldbus engineering tool to the ACF11 fails,
WARNING is generated and unsuccessful download is notified to the user. Processing
continues and on-line load to the FCS is performed.

The number of information expanded as a host file set from the fieldbus engineering tool to
the system builders is indicated below.
Table Quantity of Information Expanded from the Fieldbus Engineering Tool
Expanded information Per ACF11 Per fieldbus device
Device list 31 -
Block list 64 34
VCR list 128 36
040216E.EPS

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-30

4.2.5 Control Drawing Builder


The software terminals defined on the IOM Builder can be connected to the FCS
function block.

■ Connection of Software Terminal and FCS Function Block on Control


Drawing Builder
FCS function block can be registered, removed, wired and assigned with execution priority
on the Control Drawing Builder. By these operations, the software terminals defined on the
IOM Builder can be connected to the FCS function blocks. The created control drawing can
be downloaded to the FCS.
An example of connecting software terminals to an FCS function block on Control Drawing
Builder is shown below.

Control Drawing Builder - [Pjt:MYPJT Stn:FCS0102 Draw:DR0002 File:DR0002.edf - [100%]]


File Edit View Insert Format Tools Draw Window Help

100%

Tag Name Mod... Tag Comment 300 350 400 450 500 550 600 650 700 750 800
001 TIC1001 PID TEMPERATURE CON
002 FIC1001 PID STEAM FLOW CONT
100

003
150

IN FIC100 OUT
200

PID
250
300

%Z012101 %Z012102
350
400

Message

Ready X:675 Y:168 1024x686 Select Change

040217E.EPS

Figure Connecting Software Terminals to an FCS Function Block on Control Drawing Builder

SEE ALSO
For details on the Control Drawing Builder, see the followings:
F3, "Control Drawing Builder" in CENTUM VP Reference, Engineering (IM 33M01A30-40E)
F3, "Control Drawing Builder" in CS 1000/CS 3000 Reference, Engineering (IM 33S01B30-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-31

4.2.6 Start Fieldbus Engineering Tool


The fieldbus engineering tool project manager can be started in IOM Builder.

■ Starting Project Manager


When [Fieldbus Engineering] is selected from the IOM Builder [Tool] menu, the fieldbus
engineering tool project manager is started. However, if the fieldbus engineering tool is not
installed in the same machine, it cannot be started.

TIP
The following engineering is performed in the fieldbus engineering tool.
• Fieldbus device registration
• Definition of the fieldbus device network configuration
• Construction of the fieldbus block control loop
Even if fieldbus engineering is not performed in the fieldbus engineering tool, defining a temporary input
value in the IOM Builder allows engineering to progress as usual. Also, by using the system test function,
the system can be operated and system debug performed. In this case, engineering with the fieldbus
engineering tool is performed after system debug.

SEE ALSO
For more information about the fieldbus engineering tool, see the following:
5, “Fieldbus Engineering Tool”

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-32

4.3 Test Function


By using the Test Functions, the system can be operated and debugged even when
the I/O connection to the fieldbus devices is not established.

■ I/O Disconnection and Wiring


With I/O disconnection status in the Test Function, communication with the fieldbus devices
is not performed. In this state, IOP or OOP does not occur.
Wiring method is the same as for other communication I/O modules.
The data types that can be “wired” are indicated below.
Table Data Types Can Be Wired
Data type Wiring type that can be used

AI8
AU8 Wiring type where the wiring connection destination is analog input
AI16
AU16
AI32
AU32
AF32 Wiring type where the wiring connection destination is analog output
AF32S

D Wiring type where the wiring connection destination is contact input


DS Wiring type where the wiring connection destination is contact output
040301E.EPS

SEE ALSO
For details on the wiring, see the followings:
CENTUM VP Engineering Test Guide (IM 33M10D20-40E)
CS 1000/CS 3000 Engineering Test Guide (IM 33S04N10-01E)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-33

4.4 Engineering and Startup Procedure for Fieldbus


System
This section explains the engineering and starting up procedures of the fieldbus
system in the following sections.
• Performing FCS and fieldbus engineering in parallel
• Performing fieldbus engineering afterwards
• Off-line loading procedure after the system is constructed

■ Before Connecting the Fieldbus Device to the Fieldbus


Before connecting the fieldbus devices to the fieldbus, the following settings need to be set
to the fieldbus devices. If these settings are not correctly set, the fieldbus devices on the
fieldbus can not be recognized by the ACF11, communication such as downloading cannot
be carried out. These settings may be set with the FieldMate on the PC connected to H1
fieldbus.
• Tag names of the devices on the fieldbus
• Node addresses on the fieldbus
The tag names and node addresses of physical devices can be configured using Fieldbus
Engineering Tool.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-34
■ When FCS and Fieldbus Engineering are Performed in Parallel
The procedure for connecting the fieldbus to FCS function blocks, and operating the
fieldbus system is given below.
1. After FCS startup, define ACF11 on System View. At this time, specify 16 or 32 as the
number of software terminals for the ACF11 then specify the path of the fieldbus
database directory. When the definition is completed, execute IOM download to the
ACF11. When this download is completed, the ACF11 will be displayed in the FCS
status display window.
2. Use the Fieldbus Engineering Tool to perform fieldbus engineering.
3. Assign the block tag name and parameters of the fieldbus block to a terminal number
with the IOM Builder.
4. Execute download with the IOM Builder.

TIP
• When download is executed on the IOM Builder, the data defined with the Fieldbus Engineering Tool
(host file set) will be imported to the system builders. Then, the definitions from the Fieldbus Engi-
neering Tool will be automatically downloaded to the ACF11.
• When downloading to ACF11, the whole data defined on the standard builder will always be com-
pletely downloaded even though there is no discrepancy with the existing information in the ACF11.

5. Download the configured data to the fieldbus devices using Fieldbus Engineering Tool.
Downloading can be carried out from HIS or master PC via ACF11 module to the
fieldbus devices.

TIP
Download to the fieldbus device can be executed even after Step 6. However, data for the fieldbus device
to which download has not been completed, cannot be accurately referenced.

6. On the Control Drawing Builder, connect the FCS function blocks with software termi-
nals of ACF11, then download to the FCS. Thus data of the fieldbus devices can be
read and written from the FCS function blocks.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-35
■ When Performing Fieldbus Engineering Afterwards
This section explains how to perform engineering and system debug for the FCS while the
fieldbus is not connected, then connect the fieldbus afterwards.
The so called “fieldbus not connected” cases are as follows:
• Engineering with the fieldbus engineering tool has not been performed.
• ACF11 module is not installed.
• Fieldbus devices are not connected.

Before connecting to the fieldbus system, the FCS engineering and system debugging
should be performed. And the FCS engineering and system debugging should include the
FCS function blocks created for connecting to fieldbus blocks.
At the point where the fieldbus can be connected, the fieldbus engineering should be
performed. The data defined via this engineering work can be downloaded to the ACF11 on
the IOM Builder. After this downloading, data from the fieldbus devices can be correctly
referenced.

● Procedure Until System Debug is Performed


The procedure up to the point where system debug is performed is indicated below.
1. The ACF11 is defined in System View. At this time, 16 or 32 is selected as the number
of I/O points for the ACF11. After being defined, the ACF11 is not yet installed, but
IOM download to the ACF11 is executed. When this download is complete, the ACF11
will be displayed in the FCS status display window.
2. On the IOM Builder, fieldbus block tag names and parameters can be assigned to the
software terminals of ACF11.

IMPORTANT
When the software terminals are not defined, they can still be connected to the FCS blocks.
However, when the system starts up, IOP/OOP alarms will occur in the FCS function blocks
because of the lack of connections. To prevent IOP/OOP from occurring, it is necessary to
perform the following:
• If the actual fieldbus block tag name and parameter are determined, they should be
assigned to the software terminals.
• If the actual fieldbus block tag name and parameter are determined, temporary tag
name and parameter should be assigned to the software terminals.

When the above operation is completed, a WARNING indicating an consistency error


between the fieldbus engineering tool and engineering data will occur when downloading
from the IOM Builder. Therefore, the terminals that will have IOP/OOP are determined
before putting the system online.

3. Perform downloading on the IOM Builder.


4. On the Control Drawing Builder, connect the FCS function blocks to software terminals
and download to the FCS.
However, if the software terminal are not defined, IOP or OOP will occur in the FCS
function blocks connected to the terminals when the system is started up.
5. Perform system debugging without the fieldbus connected.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-36
● Procedure for Connecting the Fieldbus
Connect the fieldbus after system debug is finished. The procedure for connecting the
fieldbus is indicated below.
1. Perform fieldbus engineering in Fieldbus Engineering Tool.
2. On System View, specify the directory where definition data of the Fieldbus Engineer-
ing Tool is to be placed.
3. Assign the block tag name and parameters of the fieldbus block to a terminal number
with the IOM Builder.
4. Download to the ACF11 with the IOM Builder.

■ Procedure for Off-line Load After the System is Constructed


After the system is configured with the FCS, fieldbus, etc., off-line loading the defined data
can be performed in the procedure indicated below.
1. Execute FCS off-line load in System View.
2. Execute IOM download to the ACF11 in System View.

IMPORTANT
If IOM Builder download is not executed after engineering with Fieldbus Engineering Tool is
completed, the system may not startup even after IOM download is executed in System
View. The reason the system does not startup is that a misalignment in the database in the
ACF11 defined respectively by the system builders and Fieldbus Engineering Tool is
occurring. If this happens, download on IOM Builder.

3. If necessary, download to the fieldbus device with the Fieldbus Engineering Tool.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-37

4.5 Procedure for Modifications After Fieldbus


System Startup
This section explains how to change the fieldbus system after the system startup,
such as how to change the assignment of the software terminal and how to add or
remove a fieldbus device and so on.
The detailed procedures vary with the contents to be changed. The procedures for
the various type changes are shown as follows.

IMPORTANT
It is necessary to complete the download on the IOM Builder after making changes with the
fieldbus engineering tool. If the download is not completed correctly, the ACF11 may not
operate properly, or may not startup after FCS off-line download or IOM download from
System View or from FCS Status Display window.

■ Adding Fieldbus Devices or Changing Contents with the Fieldbus Engi-


neering Tool
Procedures to be executed when a fieldbus device has been added or when changes have
been made in conjunction with re-generation or re-scheduling with the Fieldbus Engineer-
ing Tool are indicated below.
1. Fieldbus Engineering Tool can be applied in HIS, master PC or salve PC for fieldbus
engineering.
2. Revise the terminal number with the IOM Builder.
3. Execute download with the IOM Builder.
4. Download the configured data to the fieldbus devices using Fieldbus Engineering Tool.
The procedure for downloading at this stage is the same as the downloading for
fieldbus system start-up.
5. With the Control Drawing Builder, connect the FCS function block and terminal num-
ber, and download to the FCS.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-38
■ Replacing a Fieldbus Device or Changing the Contents with the Fieldbus
Engineering Tool
When a fieldbus device is replaced, certain contents need to be changed with the fieldbus
engineering tool though the change does not require system re-generation. Changes made
to each part should be downloaded separately to the fieldbus devices.
Also, when replacing a fieldbus device, a physical device tag and node address must be
correctly set for the fieldbus device.

■ Deleting a Fieldbus Device


The procedure when deleting a fieldbus device is given below.
1. Revise the FCS function block and terminal number connection with the Control
Drawing Builder, and download to the FCS.
2. Do re-engineering or re-scheduling using the Fieldbus Engineering Tool on HIS or
master PC.
3. Revise the terminal number with the IOM Builder.
4. Execute download with the IOM Builder.
5. Download the configured data to the fieldbus devices using Fieldbus Engineering Tool.
The procedure for downloading at this stage is the same as the downloading for
fieldbus system start-up.

TIP
All data will be downloaded to the fieldbus device regardless of the modification with the fieldbus engi-
neering tool. Accordingly, it will take the same amount of time as a download at the time of fieldbus
system startup.

■ Replacing or Resetting the ACF11


After replacing or resetting the ACF11, select ACF11 in system view or the HIS status
display window, and execute an IOM download.

■ Changing a Terminal Number Definition


The procedure when changing a terminal number definition is indicated below.
1. Revise the terminal number with the IOM Builder, then download with the IOM Builder.
2. With the Control Drawing Builder, connect the FCS function block and terminal num-
ber, and download to the FCS.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-39

4.6 On-line Maintenance


The on-line maintenance can be applied for changing definition items on-line that
are related to the fieldbus.

IMPORTANT
To perform the process management safely, do not connect link master devices such as the
fieldbus-direct-connection type PC tool to the fieldbus in operation. If such a connection is
necessary, take safety precautions such as setting the FCS control function related to the
corresponding process, to Manual.

■ Definition Items Subject to On-line Maintenance


Of the various definition items related to the fieldbus, those that are subject to on-line
maintenance are indicated below.

IMPORTANT
• When certain definition items are modified during online maintenance, ACF11 may
stops during the online downloading to modified contents to the ACF11 module. The
definition items are indicated in the following table. This phenomenon should be taken
into consideration when performing online maintenance.
• When online downloading the data defined in CENTUM VP/CS 3000/CS 1000 system
builders, the contents defined by Fieldbus Engineering Tool will be automatically
collected and downloaded. If the contents defined by Fieldbus Engineering Tool are
modified during the online maintenance, downloading the modified contents may
cause the ACF11 to stop.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<4. System Builders Related to Fieldbus> 4-40
Table List of Definition Items Subject to On-line Maintenance
Function item Item for maintenance Items causing ACF11 stop
Category 
IOM type
Type 

Installation Unit 
position Slot 
Duplicate Next Card
High Speed Read 
Create New
IOM Node Address  
Use points 
Stale count limit  
Communication
error processing Interval of Connection  
Establishment Retries
Perform fallback  
Fieldbus Database Directory 
Command
Block tag name  
Parameter  
Direction  
Data Type  
P&ID Tag Name 
Tag Name 

IOM Builder Tag Comment 


Switch Position Label 
Label 
Btn 1, Btn 2 
Lv 1 
Tag Mark 
Upper Window 
Help 
040601E.EPS

: Subject items

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<4. System Builders Related to Fieldbus> 4-41
■ Control Actions During ACF11 Online Maintenance
To add or remove an AFC11 module or to modify the settings on the defined items can be
performed during online maintenance. After the online maintenance, the FCS function
blocks connected to the ACF11 and the data and data status of the ACF11 software termi-
nals will behave as follows.

● When Adding a New ACF11 or Increasing the Number of Terminals


When adding a new ACF11 module or when increasing the number of software terminals of
the ACF11 from 16 to 32 (Increasing the number of terminals), the data of the terminals will
be initialized into BAD status.
After the online maintenance, when the ACF11 can properly access data from the fieldbus
devices, the BAD status will be released and the data status will return to normal.

● When Removing a ACF11 or Decreasing the Number of Terminals


When removing an ACF11 module or when decreasing the number of software terminals of
the ACF11 from 32 to 16 (Decreasing the number of terminals), the FCS function blocks
connected to the removed terminals will generate IOP/OOP and CNF (Connection Fails)
alarms.

● When Settings of ACF11 Definition Items are Changed


The data status of the modified definition items have the following behaviors during the
online maintenance. Note that the so called “during the online maintenance” stands for a
time period started from the beginning of downloading the configuration to ACF11 till the
completion of the downloading.
• The healthy terminals before the online maintenance will be kept normal during the
online maintenance. After downloading the ACF11 configuration, these terminals
continue the data update except for the time period of initialization.
• The abnormal terminals before the online maintenance will be abnormal during the
online maintenance. After downloading the ACF11 configuration, data and data states
of these terminals will be updated.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


Blank Page
<5. Fieldbus Engineering Tool> 5-1

5. Fieldbus Engineering Tool


In the engineering for the entire fieldbus system, the secondary system engineering
including the ACF11 is performed using the Fieldbus Engineering Tool. This chapter
explains the functions of the Fieldbus Engineering Tool. It also explains the indi-
vidual operating procedures following the overall flow of engineering with the Field-
bus Engineering Tool.
Fieldbus communication modules vary with the upper level systems. If the upper
level system is STARDOM FCN, NFLF111 should be used instead of ACF11. If the
upper level system is STARDOM FCJ (Foundation Fieldbus Communication Compat-
ible), NFJT100-H100 should be used instead of ACF11. The compatibility of upper
level systems, fieldbus modules and fieldbus engineering tool are shown as follows.

Table Compatibility of Upper Level Systems, Fieldbus Modules and Fieldbus Engineering Tool
Upper Level System Fieldbus Module Fieldbus Engineering Tool
CENTUM CS 1000 ACF11 Yes
ACF11 Yes
CENTUM VP/CS 3000
ACF11 Yes
ACF11 No
STARDOM NFLF111 Yes
NFJT100-H100 (*1) Yes
050001E.EPS

*1: FCJ with built-in NFLF111 capabilities.


Yes: Compatible
No: Incompatible

IMPORTANT
When configuring Fieldbus and Fieldbus communication module (ALF111) connected to
CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, do not use the package
of Fieldbus Engineering Tool.

SEE ALSO
For more information about configuring Fieldbus and Fieldbus communication module (ALF111) con-
nected to CENTUM VP/CS 3000 KFCS2, KFCS, FFCS, RFCS5 or RFCS2, see the followings:
CENTUM VP FOUNDATION fieldbus Reference (IM 33M20T10-40E)
CS 3000 FOUNDATION fieldbus Reference (IM 33Y05P10-01E)

TIP
For STARDOM system, NFLF111 is used instead of ACF11.
If the upper level system is STARDOM, the terms in this document are redefined with the following
meanings listed to the right-hand side.
CENTUM VP/CS 3000/CS 1000 System → STARDOM
ACF11 → NFLF111
Control Bus → Control Network
HIS or Master PC → Master PC
FCS → FCN/FCJ
CENTUM VP/CS 3000/CS 1000 System builders → Resource Configurator
IOM Builder → Resource Configurator

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-2

5.1 Overview of Fieldbus Engineering Tool


This section gives an overview of the Fieldbus Engineering Tool functions. It also
explains the configuration, features, and operating environment of the Fieldbus
Engineering Tool.

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<5. Fieldbus Engineering Tool> 5-3

5.1.1 What is the Fieldbus Engineering Tool?


The Fieldbus Engineering Tool is the software that performs the various configura-
tion tasks that are related to the fieldbus when performing engineering for the field-
bus system.

■ Tasks Performed with the Fieldbus Engineering Tool


The Fieldbus Engineering Tool is the software that performs tasks, such as, configuration of
the devices connected to the fieldbus (fieldbus devices) and configuration of the fieldbus
network when performing fieldbus system engineering.
The following are possible by using the Fieldbus Engineering Tool.
• The function blocks for each of the fieldbus devices can be combined to configure the
control loop (builder function).
• The control loop configuration data can be transmitted to the fieldbus device via the
network (download function)
• The control loop configuration data can be passed to the supervisory system (host file
set generation function)

The Fieldbus Engineering Tool conforms to the “Foundation fieldbus (Low speed Voltage
Mode)” standardized by the Fieldbus Foundation.
Hereafter, the “Foundation fieldbus (Low speed Voltage Mode)” will be referred to as “H1
fieldbus.”

IM 33S05P10-01E 5th Edition : Dec.29,2004-00


<5. Fieldbus Engineering Tool> 5-4

5.1.2 Position of the Fieldbus Engineering Tool


The Fieldbus Engineering Tool operates in the HIS or PC (master PC) connected to
the control bus. The position of the Fieldbus Engineering Tool is explained in this
section.

TIP
For STARDOM, control bus configuration is not required but control network needs to be configured using
Resource Configurator.

■ Positioning within the Overall Fieldbus System ¡


The Fieldbus Engineering Tool operates in the HIS or master PC connected to the control
bus for the CENTUM CS 1000 system.
The figure below indicates the position that the fieldbus engineering occupies in the overall
configuration of the fieldbus system.

Operates in the HIS or master PC

Ethernet

HIS Master PC

Fieldbus Engineering Fieldbus Engineering


Tool in the HIS Tool in the master PC

Control bus
PFCS

PC connected
to H1 Fieldbus

ACF11 FieldMate

H1 Fieldbus

Fieldbus device Fieldbus device


050101E.EPS
HIS: Human interface station
Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
PFCS: Control station
ACF11: Fieldbus communication module

Figure Positioning within the Overall Fieldbus System ¡

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-5
■ Positioning within the Overall Fieldbus System £
The Fieldbus Engineering Tool operates in the HIS or master PC connected to the control
bus for the CENTUM VP/CS 3000 system.
The figure below indicates the position that the fieldbus engineering occupies in the overall
configuration of the fieldbus system.

Operates in the HIS or master PC

Ethernet

HIS Master PC

Fieldbus Engineering Fieldbus Engineering


Tool in the HIS Tool in the master PC

Control bus
LFCS2/LFCS SFCS
FCU

FCU
RIO bus
PC connected
NIU to H1 Fieldbus
ACF11
ACF11
FieldMate

H1 Fieldbus

Fieldbus device Fieldbus device


050102E.EPS
HIS: Human interface station
Master PC: General-purpose PC (Connected to Control bus)
PC connected to H1 Fieldbus: General-purpose PC
SFCS: Control station (compact type)
LFCS2/LFCS: Control station
FCU: Field control unit
RIO bus: Remote I/O bus
NIU: Node interface unit
ACF11: Fieldbus communication module

Figure Positioning within the Overall Fieldbus System £

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-6
■ Positioning within the Overall Fieldbus System – STARDOM
The Fieldbus Engineering Tool operates on the master PC connected to control network for
the STARDOM system.
The figure below indicates the position that the fieldbus engineering occupies in the overall
configuration of the fieldbus system.

HMI

Ethernet

VDS Master PC

Fieldbus Engineering
Tool in the master PC

Control network
N FCN FCJ
F (Foundation Fieldbus
P C L Communication Compliant)
S P F
U U 1
1
1
PC connected
H1 Fieldbus
to H1 Fieldbus

FieldMate

H1 Fieldbus

Fieldbus device Fieldbus device


050131E.EPS
HMI: Human machine interface
VDS: Data server/HMI server
Master PC: General-purpose PC (connected to Control network)
PC connected to H1 Fieldbus: General-purpose PC
FCN: Modules Autonomous Controller
FCJ: All-in-one Autonomous Controller
NFLF111: Fieldbus communication module

Figure Positioning within the Overall Fieldbus System – STARDOM

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-7
■ Positioning within the Engineering Flow – CENTUM VP/CS 3000/CS 1000
In fieldbus system engineering, the Fieldbus Engineering Tool performs the various con-
figuration related to the fieldbus.
The following figure indicates the positioning of the operations performed using the Field-
bus Engineering Tool.

System design

Creation of I/O list

Selection of
Control loop design Instrumentation
fieldbus device

Using FieldMate to configure


Engineering with the Engineering with
tag name and node address
system builders Fieldbus Engineering Tool
of Physical Device. (*1)

Device setting

On-line debug Legend


/loop check
Work flow
Flow of output information
Operations performed with
Test operation
the Fieldbus Engineering Tool

Application/service
050104E.EPS
*1: When the following condition is satisfied, the engineering work by FieldMate on the PC connected to H1 fieldbus is not
required.
The physical device tag name and node address have been set for the fieldbus device.

The tag names and node addresses of physical devices can be configured using Fieldbus Engineering Tool.

Figure Positioning within the Engineering Flow

■ Positioning within the Engineering Flow – STARDOM

SEE ALSO
For more information about the fieldbus implementation with STARDOM and the information about
implementation of Fieldbus Engineering Tool, see “STARDOM FOUNDATION Fieldbus Manual” (IM
34P02Q51-01E).

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-8
■ Builders and Tools Used for Engineering – CENTUM VP/CS 3000/CS 1000
The builders and tools used in fieldbus system engineering are shown as follows according
to the engineering operation performed.

● CENTUM VP/CS 3000/CS 1000 System Builders Related to the Fieldbus


The CENTUM VP/CS 3000/CS 1000 system builders are used to perform configuration
related to the fieldbus for the CENTUM VP/CS 3000/CS 1000 and the configuration infor-
mation for connecting the ACF11 I/O terminal. The configuration data is also loaded to the
ACF11 communication content definition database.

● Fieldbus Engineering Tool in the HIS or the master PC


The Fieldbus Engineering Tool in the HIS or the master PC is used to perform configuration
tasks such as configuration of fieldbus devices, fieldbus blocks and fieldbus communication
information. It also downloads the configuration data to the fieldbus devices. The tag names
and node addresses of physical devices can be configured.

Ethernet

HIS Master PC

System builders Fieldbus Engineering Tool (*1)

ACF11 ACF11 Device Device


data data data data

Control bus

FCS

ACF11
Communication
content definition
database

H1 fieldbus
Fieldbus Fieldbus Legend
device device Data download
Fieldbus block Fieldbus block route

050105E.EPS
*1: Can also be used in the HIS.

Figure Builders and Tools Used for Engineering

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-9
■ Engineering Utilities – STARDOM
Vary with engineering details of fieldbus systems, the following three engineering utilities
can be used.

● Logic Designer
FCN/FCJ control applications can be created using Logic Designer. The PASPOU for
fieldbus access and the device lables assigned for Foundation Fieldbus communication
modules are needed when using Logic Designer to access fieldbus function blocks.

● Resource Configurator
Input and output configuration of Foundation Fieldbus communication modules can be
defined using Resource Configurator. When downloading to FCN/FCJ, the engineering
data defined by Fieldbus Engineering Tool are gathered automatically with host file set.

● Fieldbus Engineering Tool


Configuration of fieldbus devices, fieldbus function blocks and fieldbus communications are
defined using Fieldbus Engineering Tool. The configured data can be downloaded to the
fieldbus devices. The physical device tag name and node address can also be changed.
The configured data of the Foundation Fieldbus communication modules may be used by
the Resource Configurator.

■ Referencing Data Among the Various Engineering Functions


Data can be referenced among the various engineering functions in the fieldbus system.

● Sharing data between CENTUM VP/CS 3000/CS 1000 System Builders and
Fieldbus Engineering Tool
The configuration data set with the Fieldbus Engineering Tool can be imported to the
system builders. This makes it possible to ensure the information in the Fieldbus Engineer-
ing Tool is same as that in the system builders.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-10
■ Positioning within the Fieldbus Engineering Flow – CENTUM VP/
CS 3000/CS 1000
The position of fieldbus engineering within the standard engineering flow is indicated
below.

Engineering start

Fieldbus system design

Define ACF11

Download to ACF11
from System View

Engineering using the Fieldbus


Define ACF11 terminal number
Engineering Tool (*2)

Download from the IOM Builder to


the FCS and ACF11 (*1)

Download to the fieldbus device

Connect the ACF11 terminal number


and FCS function block

Parameter adjustment
(HIS or master PC)

Legend

Upload parameters Work flow


Operation performed with
the Fieldbus Engineering Tool
Operation performed with other
Engineering completed than the Fieldbus Engineering Tool

050106E.EPS

*1: If the definition data for the Fieldbus Engineering Tool is under the specified directory, then this definition data is also
included in the download to the ACF11.
*2: Either the HIS or master PC can be used in engineering.

Figure Positioning within the Fieldbus Engineering Flow

TIP
In order to perform engineering using the Fieldbus Engineering Tool when the fieldbus device connected
to the H1 fieldbus is in on-line state, a physical device tag name and node address must already be set for
the fieldbus device.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-11
● Fieldbus System Design
The fieldbus devices configuration, fieldbus block configuration, communication specifica-
tions, and control specifications are designed.

● Definition of the ACF11


New registration and setting of the fieldbus communication module (ACF11) are performed.
Also, the directory where definition data is located is specified in order to import definition
data for the Fieldbus Engineering Tool.
This operation is done using the New IOM dialog box opened from the system builders of
System View.

● Downloading from System View to the ACF11


Definition data is downloaded to the ACF11.
This operation is done using the system builders of System View.

● Engineering Using the Fieldbus Engineering Tool


Engineering for the secondary system including the ACF11 is performed. The fieldbus
device configuration, fieldbus block configuration and definitions related to communication
information are performed, and generation is executed.
This operation is done with the Fieldbus Engineering Tool that is operating in either the HIS
or master PC. Also, if the CENTUM VP/CS 3000/CS 1000 system builders and Fieldbus
Engineering Tool are used in the same machine, the Fieldbus Engineering Tool can be
started from the IOM Builder of the system builders.

TIP
To defined the ACF11 related settings requires Yokogawa Fieldbus Engineering Tool, even when engi-
neering for lower layer system is implemented with other vendors engineering tools.

SEE ALSO
For more information about the engineering flow using the Fieldbus Engineering Tool, see the following:
5.1.12, “Configuration Procedure Using Fieldbus Engineering Tool”

● Definition of the ACF11 Terminal Number


Fieldbus block parameters are assigned to the ACF11 terminal number. This operation is
done using the IOM builder.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-12
● Downloading from the IOM Builder to the FCS and ACF11
The definition data is downloaded to the FCS and ACF11.
This operation is performed using the IOM builder.

TIP
If the definition data for the Fieldbus Engineering Tool exist in the directory specified in IOM properties
dialog box when ACF11 was created, then the engineering tool definition data will also be downloaded to
the ACF11 together.

● Downloading to the Fieldbus Device


The data configured with Fieldbus Engineering Tool on HIS or on master PC can be down-
loaded to the field devices via ACF11 module.
This download is performed using the Fieldbus Engineering Tool in the HIS or master PC.

● Connection of the ACF11 Terminal Number and FCS Function Block


The ACF11 terminal number and FCS function block are connected.
This operation is performed on the Control Drawing Builder. (*1)
*1: For CS 1000, Control Drawing Builder is optional.

● Parameter Adjustment
Parameters for the fieldbus block are adjusted.
This operation can be done using the Operation and Monitoring Function, Device Manage-
ment Tool, on HIS or master PC.

● Uploading Parameters (HIS or Master PC)


Parameters for the fieldbus block are uploaded to the Fieldbus Engineering Tool. Perform
upload as required such as when adjusting the parameters in the Fieldbus Engineering
Tool.
This operation is performed using the Upload dialog box in the HIS or master PC Fieldbus
Engineering Tool.

■ Positioning within the Fieldbus Engineering Flow – STARDOM

SEE ALSO
For more information about the fieldbus implementation with STARDOM and the information about
implementation of Fieldbus Engineering Tool, see 1.5.1, "Fieldbus System Construction Procedure in
STARDOM FOUNDATION Fieldbus Manual (IM 34P02Q51-01E).

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-13

5.1.3 Features of the Fieldbus Engineering Tool


The following are the features of the Fieldbus Engineering Tool.

■ Function Block Application Process (FBAP)


The Fieldbus Engineering Tool conforms to the concept of “function block application
process (FBAP)” propounded by the FOUNDATION fieldbus.
Function resources peculiar to the respective device vendors are built into the fieldbus
device compatible with the FOUNDATION fieldbus. Fieldbus configuration in the FOUNDA-
TION fieldbus refers to selecting the necessary items from among the various function
resources of the device, and combining these to create a control loop that extends to
multiple devices. In the FOUNDATION fieldbus, this control loop is called the “function block
application process (FBAP)”.
The most important purpose of the Fieldbus Engineering Tool is to efficiently create the
FBAP.

■ Graphical User Interface


Various editors with a graphical user interface are provided in the Fieldbus Engineering
Tool. The various settings related to the device and network, as well as, the creation of the
FBAP configuration can be efficiently performed by using these editors.

● Various Settings Related to the Device and Network


The various parameter values can be set with the Fieldbus Engineering Tool by entering or
selecting a value in the editor or the various dialog boxes expanded from the editor.

● Creating the FBAP Configuration


The FBAP configuration refers to information related to the FBAP. The FBAP configuration
can be created in a block diagram format with the Fieldbus Engineering Tool. The function
blocks, one type of function resource, can be arranged in the editor window. By connecting
the various types of function blocks with lines, the FBAP configuration can be created.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-14
■ Off-line Configuration
Configuration data can be created with the Fieldbus Engineering Tool, even when commu-
nication with the device cannot be performed by using the device capabilities files and DD
File. This is called off-line configuration.

● Capabilities File and DD File


▼ Capabilities File and DD File
In fieldbus devices that conform to FOUNDATION fieldbus, a “Capabilities Files” and “DD
File” are provided for each type of device. The capabilities files and DD File are provided
from the Fieldbus Foundation or fieldbus device vendors. One capabilities file and one DD
File is required for each device type.
Information necessary for the configuration, such as, information on the resources of the
device type, parameter default values, and index information, are described in text format in
the capabilities file.
DD File is an object file in which the specifications for the device block parameters are
described. A DD source file, written in accordance with the DDL (Device Description Lan-
guage) specifications, is generated via compilation using the software called Tokenizer. By
using DD File, extended parameters and transducer block parameters specific to the
function block device can be handled.
Copy the capabilities files and DD File used in the Fieldbus Engineering Tool into a specific
directory.

TIP
Capabilities File is the same as Resource File by the previous terminology of Fieldbus Foundation.
According to the FS1.4 standard for Common File Format, the new terminology uses Capabilities File to
replace the original term of Resource File.
In Fieldbus Engineering Tool, the term Resource File changes to Capability File, the methods to handle
the files are not changed.

● Creating Configuration Data


Configuration data in the Fieldbus Engineering Tool is created by using information de-
scribed in the capabilities file and DD File. Even if the network wiring is not finished, or if the
device or Fieldbus Engineering Tool is not connected to the network, the fieldbus configura-
tion can be performed first.

■ Downloading the Configuration Data Created


When the device is connected to the fieldbus and communication becomes possible, the
Fieldbus Engineering Tool is connected to the network, and the created configuration data
is downloaded to the device via the network.

■ Separation from Upper Level System Configuration


With the Fieldbus Engineering Tool, the fieldbus is configured according to the “Control
Loop Design Specifications” and “List of Fieldbus Devices.”
Thus, the upper level system for the fieldbus system (FCS and etc.,) can be performed
using CENTUM VP/CS 3000/CS 1000 system builders and the fieldbus configuration can
be performed in parallel without waiting for the completion of the upper level system con-
figuration.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-15

5.1.4 Operating Environment Requirements


The Fieldbus Engineering Tool operates in the HIS and a personal computer (PC).
The operating environment for the Fieldbus Engineering Tool is indicated below.

■ Hardware Environment (Master PC) – CENTUM VP/CS 3000/CS 1000

● Unit Model
IBM PC/AT compatible computer

● Main Memory
1 GB or more

● Hard Disk
40 GB or more (1 GB or more free space)

● CPU
Pentium III 1 GHz or faster

● Interface Card
Ethernet card
Control Bus Interface Card

■ Hardware Environment (Master PC) – STARDOM

● Unit Model
IBM PC/AT compatible computer

● Main Memory
1 GB or more

● Hard Disk
40 GB or more (1 GB or more free space)

● CPU
Pentium III 1 GHz or faster

● Interface Card
Ethernet Card

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-16
■ Software Environment (Master PC)

● OS
Microsoft Windows Vista Business Edition Service Pack 1
Microsoft Windows XP Professional Service Pack 2, Service Pack 3
Microsoft Windows Server 2003 R2 Standard Edition Service Pack 2
Microsoft Windows Server 2003 Standard Edition Service Pack 2
All of the above support only 32 bit OS.

■ CENTUM VP/CS 3000/CS 1000 System

● ACF11
Fieldbus Communication Module ACF11 (Rev:R6 or later)
However, when tag assignment or addresses assignment is carried out on HIS or a master
PC with Fieldbus Engineering Tool, the ACF11 card R7 or later is required.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-17

5.1.5 Overview of Fieldbus Engineering Tool


The Fieldbus Engineering Tool consists of a project manager, various editors, utili-
ties, network startup and maintenance functions. This section explains the overview
of the engineering bus tool functional structure and the functions.

■ Overview of the Fieldbus Engineering Tool


The diagram below indicates the overview of the Fieldbus Engineering Tool.

Project manager Device pool

Various editors System database

System device pool

Default values for


Utilities configuration data

Network startup

Project database
Maintenance Project device pool

Configuration data

Legend
Data flow
Calling function
Fieldbus Engineering
Fieldbus devices Tool function

050107E.EPS

Figure Overview of the Fieldbus Engineering Tool

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-18
■ Project

● What is the Project?


▼ Project
A project is the unit of engineering managed by the Fieldbus Engineering Tool. The Field-
bus Engineering Tool performs configuration for each project.
One project has the configuration data related to one segment (range in which communica-
tion can be performed in the fieldbus without using a bridge).
The Fieldbus Engineering Tool can have multiple projects.

IMPORTANT
A Project created and controlled on Fieldbus Engineering Tool is a separated project,
different from the project created on CENTUM VP/CS 3000/CS 1000 System View.

● Project Database
The project database is the database that stores all configuration data related to one project.
A project database is created for each project.

Project A
Configuration data
for segment A is stored.
Ethernet Project
database A

HIS or Master PC

Fieldbus Engineering Tool Project B


Configuration data
for segment B is stored.
Project
database B
Control bus
FCS

ACF11 H1 fieldbus

Segment A

Segment B

050108E.EPS

Figure Relationship Between Project, Project Database and Segment

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-19

5.1.6 Project Manager


The project manager is the function that manages all of the data for the Fieldbus
Engineering Tool, such as, the project database and device pool. Also, it can retrieve
the various editors, utilities, network startup, and maintenance tool.

■ Overview of the Project Manager


The diagram below indicates the overview of Project Manager.

DD File
Project manager (Provided by the
Device pool fieldbus device
vendor)

File for printing


System database
Project management Capabilities
file
System device pool
(Provided by
Default value of the vendor of
configuration data the device)
Configuration Database management
data file

Device pool management

Project database
Host file set
Primary LM definition Project device pool

Configuration data

Range of addresses for polling

Function to change the physical


device tag name and node address Legend
Data flow

050109E.EPS

Figure Overview of the Project Manager Functions

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-20
■ Project Management
This function manages the project.
The project management function includes the functions indicated below.

● Create Project
This function generates a new project. When a new project is created, a directory (project
directory) with the same name as the project name is generated and various files, such as,
the project database file are generated in that directory.

● Project Maintenance
This function opens and closes an existing project.
When a project is opened, the configuration data can be changed for that project. With the
Fieldbus Engineering Tool, multiple projects cannot be opened at one time.
This function closes the project when changes are completed for the project.

● Save Project
A different name can be attached to the project currently opened and then saved.

● Read Project
This function reads the contents of an existing project to the currently opened project.

● Delete Project
This function deletes the project. All of the files for the project database, etc. in the project
directory are deleted.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-21
■ Database Management
This is the function for managing the project database. It also performs a portion of system
database management.

IMPORTANT
• In the course of generation or etc., database will be frequently accessed. If the power
is cut off during database access, the project database could be damaged. Never cut
off the power during database access.
• Do not use any software application other than the Fieldbus Engineering Tool to open
the database.

The database management function includes the functions indicated below.

● Project Export
▼ Export
This is the function used for backing up the project. When a project is exported, the configu-
ration data file is output. The configuration data file consists of multiple device object files
and the system configuration file. These files are in text format that conforms to the Com-
mon File Format that has been standardized by the Fieldbus Foundation.
If a necessity arises to download these files again, import them and then perform the
operation.
• Information output to the device object file
Configuration data for the device registered in the project is output to the device object
file. Basically, one device object file is generated for one device. The name of the
device object file is automatically created by using the first five letters of the project
name and a serial number.

Table Information Output to the Device Object File


No. Type of information Description
1 VCR list VCR (Virtual Communication Relationship) list
Parameter values related to communication, time synchronization, and scheduling
2 Network parameter
used in one part of the data link layer and physical layer (shared in the project)

Communication scheduling information (this is divided into Link Schedule Activation


Communication
3 Variable parameters and Schedule Domain information, due to different downloading
schedule
methods) used by the LAS (Link Active Scheduler)
4 SM parameter Parameter values necessary for the SM (System Management) application
5 FB schedule Scheduling information that indicates execution order for FB
6 FBAP parameter Parameter values for the FBAP constituents
050110E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-22
Information output to the device object file differs according to the device class. The table
below indicates the output information for each device class.
Table Device Class and Information that is Output
Device class Contents of the output file

Basic device VCR list, SM parameter, FB schedule, FBAP parameter (*1)

VCR list, SM parameter, FB schedule, FBAP parameter,


Linkmaster device
Network parameter, Communication scheduling
Master device
Host interface device (*2) VCR list, SM parameter, Network parameter,
Communication scheduling
050111E.EPS

*1: FBAP parameters are data downloaded to the FBAP VFD (a virtual device with function resources). Other data is
downloaded to the MIB (the network and system management information database that each device has).
*2: The host interface device has the same communication function as the linkmaster device, but does not have a FBAP
VFD. Thus, it does not have an FB schedule.

• Information output to the system configuration file


The names of all device object files and capabilities files related to a single project are
output to the system configuration file.
By selecting the system configuration file when importing a project, all related device
object files can be imported.

● Device Configuration Data Export


▼ Export
This is the function for backing up the device configuration file or using it in another project.
By exporting the device configuration data, the device object file for the exported device is
output in common file format.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-23
● Project Import
▼ Import
This function is used to import a project database so that the project can be restored from
the project backup. This function is only for re-engineering the projects with backup copies.
The engineering operation can also be performed in another HIS or PC where the Fieldbus
Engineering Tool is installed.
The following files are necessary to import a project.
• System configuration file
• The device object file with the file name being recorded to the system configuration
file.
• The capabilities file with the file name being recorded to the system configuration file.
• The DD File whose file name is stored in the system configuration file.

When selecting the system configuration file at the time of importing, all of the device object
files, capabilities files and DD File described in the selected system configuration file are
imported, and the project opens.

If the capabilities file does not exist in the specified directory when importing a project, a
message will be displayed and the import operation will be aborted.
In a case where the DD File to be imported does not exist under the specified directory,
whether to import without the DD File or to abort the import can be selected in the dialog
box displayed at the beginning of import operation. If the import is executed without the DD
File, the device will be registered in the project as one that handles only the standard
parameters.

IMPORTANT
• When the project is imported without the DD File, part of information for the extended
parameters of the device will be lost.
• The directory FF_PRJ\DEVPOOL is defined as the recommended location where the
capabilities file and DD File are to be copied. When changing the destination, change
the directory path using the environment setting.

TIP
The projects created with the Fieldbus Engineering Tool of release R2.01 or earlier does not support DD
File. These projects can be reconfigured to be DD File-compatible by using the project import. Check the
points noted below prior to executing the project import function.
• The project to be imported must be exported first.
• Prepare a DD File compatible with the capabilities file to be imported.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-24
● Cautions when Importing A Project Created with Fieldbus Engineering
Tools Release R2.01
When importing a project created with Fieldbus Engineering Tools release R2.01 into a
project created with Fieldbus Engineering Tools release R3.01, the capabilities file name
need to be changed on the system configuration before import. Change the resource file
name to the capabilities file name in accordance with Fieldbus Foundation standard by
change the setting for ResourceFileName in [Device n] item in the system configuration file.
• Example: Change Resource File into Capability File (EJA Series Differential Pressure
Transmitter).
In the old project, the script for EJA capabilities file is
D:Fieldbus\kappa\FF_PRJ\DEVPOOL\EJA.DRF
In the new project for importing the EJA capabilities file, the script should be changed to
594543\0003\010104.CFF

TIP
Capabilities File is the same as Resource File by the previous terminology of Fieldbus Foundation.
According to FS1.4 standard for Common File Format, the new terminology used Capabilities file to
replace the original term of Resource File, the new file extension .CFF is to replace the original file
extension .DRF.
In Fieldbus Engineering Tool, the method to handle the both of Resource File Format (.DRF) and Capa-
bilities format (.CFF) are not changed. When creating new project, choose Capabilities format.

When importing a project created with Fieldbus Engineering Tool release R2.01 into a
project created with Fieldbus Engineering Tool release R3.01, a dialog message box
[Includes Invalid Value] may appear and abort the importing. When this dialog message box
appears and the importing aborts, it means that the initial settings in the capabilities file
created with Fieldbus Engineering Tool are not described correctly. It may also means that
the designated capabilities file does not have description for initial settings when creating
the project with the tool of R2.01. However, if parameter uploading has been performed
after creating the project, this phenomenon will not occur.
When the importing aborts, do the following may recover the importing.
1. On Fieldbus Engineering Tool release R2.01 download dialog box, uncheck the
[Execute Block parameter download] option, then perform downloading. If download-
ing has been performed, this step may be skipped to go to next step directly.
2. Upload parameters.
3. Run Export.
4. Use Fieldbus Engineering Tool release R3.01 to import the file exported by the above
procedures.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-25
● What to Do when Specified Capabilities File is Wrong
Regardless the release number of the Fieldbus Engineering Tool used for creating the
project, a message dialog box [The specified capabilities file is wrong] may appear when
import the project into a project created with Fieldbus Engineering Tools release R3.01.
This means that the following settings corresponding to the field devices in the project
created do not meet the description in the imported capabilities file.
_MANUFACID=0xXXXXXX
_DEVTYPE=0xXXXX
_DEV_REV=0xXX

If this message dialog appears, check the above settings in the imported file and the
settings in exported file corresponding to the device that is giving the error. If the settings in
the two files are not same, either use the capabilities file for creating the project or the
capabilities file provided for the field device.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-26
● Import Device Configuration Data
▼ Import
This is the function for importing the configuration data for each device to the project
database. Since the imported device configuration data can be downloaded to the same
addressed same type device only, so that the imported data can not be changed except the
device ID.
Importing device configuration data requires the device object file, the capabilities file that is
the source of the device object file, and DD File.
When a fieldbus device is replaced, using this function can download the previous device’s
configuration to the new one.
Importing device configuration data requires the device object file and capabilities file that
were the source of the device object file.

● Host File Set Generation


▼ Generate the Host Files
Host file set consists of project configuration data output from the project database.
The project configuration data are divided into multiple files in the format that can be used
by CENTUM VP/CS 3000/CS 1000 system builders. These files are collectively referred to
as the host file set. A host file set consists of the following information.
Table Information Output to the Host File Set
No. File name Type of information Description
Correspondence table of device number, vendor name,
1 Device.hfs Device configuration list
model, device ID, physical device tag, and node address
Correspondence table of block tag name and block index
2 Blkinfo.hfs Block information (including index of view objects for referencing block type
and parameters within the block)
Correspondence table of vendor specific FBAP parameters
3 Blkparam.hfs Block parameter list
and parameter index added to the device
Information about the connected terminals and the
4 Terminal.hfs Terminal information
connection between the function block and object
List of purposes for the VCR (including information about
5 Vcrusage.hfs VCR application list
communication with which VFD for which device)
6 Alert.hfs Alert information Information for analyzing alert information
7 Trend.hfs Trend information Information about defined trend objects
Host interface device
8 Hostif.hfs Configuration of host interface device
information
Correspondence table of standard FBAP parameters and
9 Stblkpar.hfs Standard block parameter list
the parameter index
10 View.hfs View information Information about the defined view objects
11 Datatype.hfs Data type list List of data types
12 Reserved.hfs Reserved word list List of reserved words
050112E.EPS

Note: For information in 1 through 8, 10 and 11, a file is output in which the contents differ for each configuration performed.
For information in 9 and 12, files with the same contents are always output once output is performed. Information in 9
and 12 is called the option.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-27
● Consistency Check
▼ Check
This function checks if there are any contradictions in the contents of the configuration data
saved in the project database. If data outside the possible setting range is set, a warning
dialog box is displayed.

● Print Device List


A list of all devices registered in the project is created and printed.

IMPORTANT
Do not change the file name and folder configuration of the host file set that was output. If
the file name or folder configuration are changed, the configuration data cannot be im-
ported to an supervisory system, such as, the CENTUM VP/CS 3000/CS 1000.

■ Device Pool Management


▼ Device Pool
The device pool management is a function that manages the device pool in the system
database or project database. The device pool is the area for storing the capabilities files
and DD Files provided by the fieldbus device vendors. There is one capabilities file and one
DD File for each device model. Information for configuration such as device function re-
source information, parameter default values, and index information are described in text
script in the capabilities file. The device block parameter specifications are described in the
DD File.
The device pool management function includes the following functions.

● Importing a Capabilities File and DD File


Device capabilities files can be obtained from a CD-ROM, FDC, or network devices, etc. to
a device pool in the system database or a device pool in the project database. At the same
time, the DD File that corresponds to the capabilities file to be read is also read to the
device pool. In order to determine the file for the DD File that corresponds to the capabilities
file, the values of MANUFAC_ID, DEV_TYPE, DEV_REV and DD_REV are used.
If the DD File corresponding to the capabilities file does not exist under the specified direc-
tory, whether the file is imported without the DD File or the import operation is aborted can
be selected in the dialog box displayed at the beginning of import operation. When the
import is executed without the DD File, the device will be registered in the project as one
that only handles the standard parameters.
Prior to importing, the capabilities file and DD File to be used must be copied to the
FF_PRJ\DEVPOLL directory under the directory where the Fieldbus Engineering Tool is
installed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-28

IMPORTANT
• When the project is imported without the DD File, the extended parameters cannot be
adjusted with the Fieldbus Engineering Tool since the information cannot be acquired
for the extended parameters of the device.
• The directory FF_PRJ\DEVPOOL is defined as the recommended location where the
capabilities file and DD File are to be copied. When changing the destination, change
the directory path using the environment setting.

The capabilities files and DD Files of devices that are shared among multiple projects
should be imported to the system database. The project database is created by copying the
system database, and therefore all capabilities file and DD File setting data imported to the
system database will be copied to the project database.
The capabilities files and DD Files of devices that are used only in a specific project can be
directly imported to the project database.
The general idea of importing capabilities file and DD File is indicated below.

FF_PRJ\DEVPOOL
directory

Import capabilities file and


DD File to a device pool in
the system database.
Automatically copied
when the new project
is created.
System database Project database

System device pool Project device pool

Default value of
configuration data Configuration data

Import capabilities file and


DD File to a device pool in
the project database.
050113E.EPS

Figure Importing a Capabilities File and DD File

● Deleting a Capabilities File and DD File


A device capabilities file is deleted from the system database or project database. At the
same time, the DD File that corresponds to the capabilities file to be deleted will also be
deleted from the project.

● Print Device Model List


A list of all device models that can be registered in the project (capabilities file list) is cre-
ated and printed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-29
■ Primary LM Definition
▼ Primary LM Settings
The primary LM (Linkmaster) definition is a procedure for setting the “time publisher device”
and “scheduled linkmaster devices.”
The H1 fieldbus project has one or more of each of the time publisher device and
linkmaster device. A single device can be specified as both the time publisher device and
linkmaster device.

● Time Publisher
▼ Time Publisher
The time publisher device stores the standard time in the project and manages the sched-
ule for executing the application block processes (FB schedule).
The FB schedule is downloaded to the time publisher device when the project is down-
loaded.
Only a device in which the SM (System Management) is installed can be specified as a
time publisher device. SM is a function that performs physical device tag assignment,
address assignment, time synchronization, and FB schedule management.

● Time Synchronized Cycles


▼ Time Synchronized Cycles
This is the time interval at which the time publisher performs time synchronization (unit:
seconds).

● Linkmaster Device
▼ LINK Master
The link-master device executes the LAS (Link Active Schedule) function. The LAS function
manages the communication schedule according to the standard time of the project stored
in the time publisher device.
The “scheduled linkmaster device” refers to the device that has the first priority to become a
linkmaster device at the time the project begins control.
When the project is downloaded, the communication schedule is loaded to the linkmaster
device.

SEE ALSO
For details on the SM, see “System Management (FF-880)” published by the Fieldbus Foundation.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-30
■ Specify Polling Address Range
▼ Specify Polling Address Range
When assigning addresses or assigning tags, it is required to have the list (LIVE_LIST) of
the field devices that are communicating on the Fieldbus and the devises node addresses.
To acquire the LIVE_LIST, pre-set a range for searching the node addresses may speed up
the search. This precept range is referred to as Polling Address Range.
Polling address range can be specified manually or automatically. When the polling address
range is set automatically, the node addresses of all the registered field devices will be
included in the polling address range. To manually or to automatically setting the polling
address can be designated by user. Manually set polling address range will take effect only
after downloading from IOM Builder to ACF11 (*1). When adding a new field device, the
node address of the added device should be set within the polling address range.
*1: For STARDOM, downloading to Foundation Fieldbus communication modules of FCN/FCJ is performed from Resource
Configurator.

■ Change Physical Device Tag Name and Node Address


This function is used to change the physical device tag name and node address of a physi-
cal device connected to the fieldbus.
When the node address specified by the project manager is not within the range of 0x10 to
0xF7, the node address for the actual device will default to a preset value (0xF8 to 0xFB).
In this case, it will be necessary to change the node address after it has been assigned for
the actual device.

IMPORTANT
• In order to use this function to change the physical device tag name and node ad-
dress, it is necessary to set the device ID beforehand. Set “Display Device ID” or the
device ID acquired from the device using the FieldMate.
• After changing the physical device tag name and node address, it is necessary to
download the new tag name and address to the device.

● Tag Assignment
▼ Tag Assignment
Changes the physical device tag name and node address for the actual device specified.

● Address Assignment
▼ Address Assignment
Changes the node address for the actual device specified.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-31
■ Others

● Editors
Editors can be called for project configuration. Three types of editors are used in the Field-
bus Engineering Tool: device editor, network editor, and FB editor.

● Utilities
Various utilities include the security, on-line help, and control bus setting utilities can be
used. The security, on-line help, control bus setting and environment setting utilities are
available.

● Control Bus Configuration Window


To communicate HIS or master PC to control bus, the control bus needs to be configured.
The settings for the control bus can be defined on the Control Bus Configuration window.

TIP
Control bus configuration window is not available for STARDOM.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-32

5.1.7 Editors
Various editors are provided for creating project configuration data (device configu-
ration, network configuration, FBAP configuration, and schedule). All of the configu-
ration data created by those editors are stored in the project database.

■ Overview of the Editors


The following diagram indicates the overview of the editors.

Work of each Editor

Device editor

Network editor
Text file for printing

FB editor
FBAP block diagram Project database

Project device pool


Schedule creation
Text file for printing Configuration data

Entry check and save Legend


Data flow

050114E.EPS

Figure Overview of the Editors

■ Device Editor (Edit Device)


This is the function for registering the devices used for the project.
The device editor has the functions indicated below.

● Device Management
This is the function for registering to or deleting devices from the project.
The user selects a device from the device pool in the project database, sets a physical
device tag name and device ID to that device, and registers them to the project. When the
device is registered, its configuration data is created based on information contained in the
capabilities file for the registered device. The configuration data created is stored in the
project database.
Configuration data is information specific to each device that has been registered in the
project. When a device is deleted from the project, the configuration data related to the
deleted device is deleted from the project database.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-33
● Setting Device ID and Physical Device Tag Name
▼ Device ID, PD Tag
This is the function for setting the device ID and physical device tag name.
• Setting the device ID
The device ID is an identifier for specifying one device out of the whole universe of
devices. The device ID is pre-assigned by the vendor for the respective devices.
Normally, the device ID given to the actual device by the vendor is set. However, if the
device ID is unknown, such as, not having the actual device in hand, a temporary
device ID can be set and then changed later on to the actual device ID.
• Setting the physical device tag name
The physical device tag name is an identifier for specifying one device out of the
devices connected to the network. It is necessary to set one physical device tag name
for each of the devices in the network without any duplication.
Set the physical device tag name before connecting the device to the fieldbus.
If the physical device tag name is not set, the node address cannot be set in the
device.

SEE ALSO
• For more information about the setting of device ID, see the following:
5.5.3, “Changing a Registered Device ID”
• For more information about the display of device ID, see the following:
5.3.6, “Display Device ID”

■ Network Editor (For Network Configuration)


This is the function for setting the network configuration for the fieldbus device connected to
the fieldbus.
The network editor has the following functions.

● Setting Network Parameters


▼ Node Address, Device Classes
This is the function for setting the device network parameters.
Set the node address and device class for each device registered in the project.
• Node address
The node address is the parameter for identifying the device when communicating. It
is necessary to set node addresses without any duplication within the project.
• Device class
In the Fieldbus Engineering Tool, the fieldbus devices consist of basic devices and
link-master devices.
The device class basic or link-master can be set to a device.
A basic device does not run the LAS function while a link-master device does.
If the device class is set as basic then it becomes a basic device and if set as link-
master, it becomes a link-master device. Only devices with built-in LAS can be speci-
fied as a link-master device.
The default setting for device class is basic. In one project, at least one link-master
device is required.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-34
● Node Address Auto Assignment
This is the function that automatically assigns a node address to a device for which one has
not been set. The device type is determined from the DeviceClass value in the capabilities
file and the node address is assigned according to the device type that has been deter-
mined using one of the methods below.
• Basic device: DeviceClass=BASIC
For each device, a node address is assigned in descending order within the range of
0xF7 to 0x16. Note that a node address which is already in use cannot be assigned.
• Link-master device: DeviceClass=LINKMASTER
For each device, a node address is assigned in ascending order within the range of
0x16 to 0xF7. Note that a node address which is already in use cannot be assigned.
• Host interface device: DeviceClass=HOSTINTERFACE
For each device, a node address is assigned in ascending order within the range of
0x14 to 0x15. Note if both 0x14 and 0x15 are used, 0x16 can be assigned.

● Changing Device Parameters


This is the function for changing device parameters.
Using this function, values for parameters whose setpoint values were set through off-line
configuration can be changed manually.
Normally, the device parameters are generated automatically when the device is registered.
The default settings described in the capabilities file that are considered the most suitable
for the network based on communication capability, are set as the device parameters.
Normally, the default settings are used. But they can be changed when required. Using the
Parameter Edit dialog box can change device parameters.
The parameters indicated below are displayed in the Parameter Edit dialog box.
• NMIB: NM (Network Management) parameter (common)
• SMIB: SM (System Management) parameters (common)
• SMAA: SM (System Management) parameters
(for address assignment, common area)
• LAS: LAS schedule parameters (common area)
LASAR: Version part
LASDOM: Summary part
LASSUB: Sub-schedule part
• VCR: VCR (Virtual Communication Relationship) parameters

IMPORTANT
Use the default values as much as possible for the network parameters and SM param-
eters. If these parameters are changed without using discretion, there is a risk that the
fieldbus device may not operate properly.
If these parameters must be changed, take caution that no contradictions occur in the
parameter values.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-35
■ FB Editor (For FBAP Configuration)
▼ FBAP
This is the function for creating a block diagram of the function block application processes
(FBAP) and entering function block parameter values to create the FBAP configuration.
The FBAP block diagram is created in the drawing area in the center of the FB editor. The
setting of parameter values for the function block is performed in the dialog box expanded
from the FB editor. The FB editor includes the functions indicated below.

● FBAP Configuration Management


This is the function that executes creation, deletion, and save commands of the FBAP
configuration.

TIP
The save function in the FBAP configuration management saves the created FBAP block diagram. It does
not perform a consistency check of the entered data or automatic generation of necessary data. These
processes are performed by the FBAP generation function.

● Creating FBAP Block Diagram


▼ Function Block, Connection
This is the FBAP block diagram creation function.
The I/O connections between the function blocks can be described in a block diagram
format and an FBAP block diagram is created using the FB editor.

The FBAP block diagram consists of three elements: function blocks, connection terminals,
and connections. Connection terminals are treated the same as function blocks with the
Fieldbus Engineering Tool.
• Function blocks
A function block is the smallest unit of a collection of control and calculation functions
of the device has. The FB editor uses a variety of square frames to depict these blocks.
The FBAP block diagram is created by combining these function blocks.
Given below is an example of a function block.

AO_800 (AO_01)

CasIn BkcalOut
RcasIn
AO Out
RcasOut

AVP_2
050115E.EPS

Figure A Function Block

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-36
The following function blocks are available.
Table Function Block
SYMBOL FUNCTION BLOCK
AI Analog Input Block
AO Analog Output Block
DI Discrete Input Block
DO Discrete Output Block
PID PID Control Block
RA Ratio Set Block
CS Control Selector Block
OS Output Splitter Block
SC Signal Characterizer Block
IT Integrator Block
IS Input Selector Block
MDI Multiple Discrete Input Block
MDO Multiple Discrete Output Block
MAI Multiple Analog Input Block
MAO Multiple Analog Output Block
050116E.EPS

• Connection terminals
Connection terminals are terminals that perform inputs and outputs to and from
outside the project. In the FB editor, these terminals are indicated by a square frame to
which is attached an upside-down triangular mark.
I/O which corresponds to function blocks for devices outside the project can be set by
using the connection terminals. This enables settings related to exchange of data with
the supervisory system function block or the function block of another project.
The illustration below is an example of a connection terminal.

TO_1000-01 (TO-01)

In

ACF11_1
050117E.EPS

Figure A Connection Terminal

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-37
Block name of the connection terminal and function block is displayed in a pair of
parentheses together with the block ID. The block ID is a unique string, the string
should not be identical within the fieldbus system. The block ID cannot be modified.
The block ID format is as follows.
<Block Type>_<Number>
The block type for input terminal is TI and the block type for output terminal is TO.

<Number> is the same number of the I/O terminal in the connected host interface
device. Here are samples of block names attached with block IDs.
TO_1000-01(TO_02)
AI_600-02 (AI_01)

The block ID number of the connection terminal for receiving the input signal from the
I/O element and the block ID number of the connection terminal for sending the input
signal should be the same. If they are not consistent, a generation error will occur (*1).
So they must be consistent.

AO_600-02 (AO_01)
TI_1064-01 (TI_05) TO_1000-01 (TO_05)
CasIn BkcalOut
Out RcasIn
AO Out
RcasOut
In

ACF11-14 ACF11-14
New_valve_positioner_2
050132E.EPS

Figure A Readback Loop Connection

TO_1000-01(TO_05) is a connection terminal for readback input of DCS function


block. The connection terminal for the output signal from DCS TI_1064-01(TI_05)
must have the same block ID number.
If multiple outputs and multiple inputs are used for connection, the numbers should not
be identical except for the readback connection terminals, otherwise, generation
errors will occur (*1).
*1: Only when the option of [Check Read-Back Correspondence of Connection Terminal] is checked (default) in the
[Environment Settings] window, generation errors may occur for inconsistency of the numbers.

TIP
If a project exported from the older version of Fieldbus Engineering Tool prior than R4.10, and using
R4.10 or later Fieldbus Engineering Tool to import the project, the option [Check Read-Back Correspon-
dence of Connection Terminal] in [Environment Settings] window will be disabled. In this case, inconsis-
tence of readback terminal numbers will not trigger error alarms.
When maintaining an old version project, it is necessary to export the project using the old version
Fieldbus Engineering Tool, then import the project using the upgraded R5.01 Fieldbus Engineering Tool.

• Connection
A connection is the line connecting function blocks within the same project or connec-
tion terminals. In the FB editor, connections are indicated by a black, straight line.
In the function block and connection terminals, there are fieldbus I/O terminals (input
terminal, output terminal). By using connections between input terminals and output
terminals, the function blocks and connection terminals can be connected.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-38
● Changing FBAP Parameters
This is the function for changing parameters included in the function block that can be
rewritten. The FBAP parameters are set in the Parameter Edit dialog box.
In the resource block setting, only parameter changes can be performed. Set the channel
number of the function block to be connected in the channel parameter for the I/O function
block when connecting between the transducer block and I/O function block.
Parameters that cannot be overwritten cannot be changed. Also, the value of the link object
parameter is automatically generated at the time of generation. Therefore, it cannot be
changed.

● FBAP Generation
It is necessary to generate the FBAP configuration in order to download it to the device. The
VCR value and link object parameter values are generated when the FBAP configuration is
generated, based on the FBAP configuration and configuration data for the device. The
generated VCR value and link object parameter values are stored in the project database.
If there is an error in the configuration data, an error notification dialog box is displayed at
the time of generation.

TIP
The FBAP generation function is used by executing generation after first saving the FBAP block diagram.

● All FBAP Generation


All FBAP created on FB editor can be generated together. However, the FBAP configura-
tion that already successfully generated will not be generated again when applying All
FBAP Generation.

● Print FBAP Block Diagram


This is the function for printing the FBAP block diagram that was opened.
When the FBAP block diagram is not open, this function cannot be used.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-39
■ Schedule Creation
This is the function that creates a schedule for executing the function block (FB schedule)
and a schedule for communication between function blocks (LAS schedule).
It is necessary to create these schedules in order to efficiently perform the processes using
FBAP.

● Automatic Schedule Creation


This is the function for automatically creating an execution timing chart that becomes the
source information for generating a schedule. This function is automatically executed after
the execution of the FBAP configuration generation.
This can also be executed with the Schedule Display dialog box.

● Multi-schedule Creation
The schedule for multiple FBAP configurations are scheduled at the same time within a
single macro cycle in the Foundation fieldbus. The individual schedules that are scheduled
in a macro cycle are called sub-schedules. The schedule for each FBAP configuration
corresponds to a sub-schedule.
Also, the macro cycle schedule in which multiple sub-schedules are scheduled is called a
multi-schedule.
A multi-schedule is created with respect to all FBAP configurations in a project. Due to this,
the multi-schedule cannot be created unless the generation of all FBAP configurations has
been completed normally.
The illustration below is an example of a multi-schedule.

Macro cycle

Sub-schedule period
(control cycle for FBAP1)

DI
FBAP1
DO

Sub-schedule period
(control cycle for FBAP2)

AI

FBAP2 PID

AO

: Block execution time


: Communication time
: Background communication time
050118E.EPS

Figure A Multi-schedule

In the above example, two cycles are performed for FBAP1’s sub-schedule. FBAP2’s sub-
schedules are for three cycles.
The user sets the time for the macro cycle and each sub-schedule (FBAP control cycle).
When setting, it is necessary to make adjustments so that the macro cycle becomes the
least common multiple of each sub-schedule period.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-40
● Schedule Display and Revision
This is the function for graphically displaying and manually revising the execution timing
chart that was created with the automatic schedule creation function. The execution timing
for the FB schedule and execution timing for the communication schedule can be revised.

TIP
A new execution timing chart cannot be created with this function. Only an execution timing chart created
with the automatic schedule creation can be revised.

● Schedule Generation and Save


This is the function for generating parameter values (a portion of the block parameters and
a portion of the network parameters) related to the FB schedule, LAS schedule and sched-
ule. The generated schedule is saved in the project database.
This is executed when clicking the [OK] button in the Schedule Display dialog box.
• FB schedule
The FB schedule parameters are generated based on the execution timing chart.
The generated FB schedule parameters are shown in the table below.

Table Generated FB Schedule Parameters


Parameter name Description
StartTimeOffset Function block processing start time (relative time)
FbObjectIndex Function block index
VfdRef VFD reference number
050119E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-41
• LAS (Link Active Scheduler)
The parameters required by LAS and related to communication are generated based
on the execution timing chart.
The generated parameters are shown in the table below.

Table LAS Parameters Generated


Parameter name Description
LinkScheduleActivationVariable Version number of the schedule to be executed next
ScheduleSummary Schedule summary
ScheduleVersionNumber Version number of the schedule
ScheduleBuilderIdentifier ID of the person/object that created the schedule
NumberOfSubschedules Number of sub-schedules
V_MSO_ Overhead necessary for executing the schedule
StorageRequiredForTotalSchedule Schedule capacity
TimingResolutionRequiredTo
Timing resolution
MeetScheduleJitterCommitments
Macrocycle Duration Macro cycle
050120E.EPS

Table LAS Parameters Generated (Sub-scheduler Related)

Parameter name Description


SubSchedule Sub-schedule
SubscheduleVersionNumber Sub-schedule version number
SubscheduleIdentifier Sub-schedule ID
SubschedulePeriod Sub-schedule period
050121E.EPS

Table LAS Parameters Generated (Sequence Related)

Parameter name Description


ScheduleStartingTimeOffset Relative time for starting communication
MaximumComputedDurationOf
Maximum period for executing a sequence
SequenceExecution
050122E.EPS

Table LAS Parameters Generated (Element Related)

Parameter name Description


ElementType Element type
ElementParameter Address of DLCEP sending the CD
050123E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-42
• Block parameter
The function block parameters are generated based on the execution timing chart.
The generated function block parameters are shown in the table below.

Table Generated Function Block Parameter Values


Parameter name Description
PeriodOfExecution Repetition cycle for function block processing
Index of function block where the next process is
executed.
NextBlockToExecute
The function block existing in the same fieldbus device
as the generated parameters is the subject.
050124E.EPS

• Network parameter
The network parameters are generated based on the execution timing chart.
The generated function block parameters are shown in the table below.

Table Generated Network Parameter Values


Parameter name Description
Array indicating the delegation time given to each
MaxTokenHoldTimeArray fieldbus device while the delegated token makes the
round of all fieldbus devices
Default value for the delegation time given to each
DefTokenHoldTime fieldbus device while the delegated token makes the
round of all fieldbus devices
050125E.EPS

■ Entry Check and Save


This is the function that checks to see if there is anything wrong with all the data entered by
the user. If there is nothing wrong, the entered data is saved to the database. If something
is wrong, a message to this effect is displayed in the dialog box.
Also, in the FB editor and schedule creation function, the consistency check and save
functions are performed at the time of generation; not at input.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-43

5.1.8 Utilities
The utilities are provided in the Fieldbus Engineering Tool including security, on-line
help, and environment setting utilities.

■ Overview of Utilities
The diagram below shows the overview of utilities.

Utilities

Security
Project database
Project device pool

On-line help Configuration data

Environment setting
Legend
Data flow

050126E.EPS

Figure Overview of Utilities

■ Security
▼ Security
This is the utility that restricts the users who can use the Fieldbus Engineering Tool. This
function ensures the integrity of the configuration data.
The security function includes the functions indicated below.
• Login
• Setting Password
• User registration

● Login
The Login window is displayed when the Fieldbus Engineering Tool is started. The user
logs into the Fieldbus Engineering Tool by entering his/her pre-registered user name and
password in this Login window.
Only one person at a time can log into the Fieldbus Engineering Tool. To do a new login
when another user is already logged in, close the project manager that is already open, and
then have the new user login.

“MASTER” is a user name registered in the Fieldbus Engineering Tool beforehand by


default. At the time of installation, there is no password for “MASTER”. We recommend
setting a password for “MASTER” when using the Fieldbus Engineering Tool.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-44
● Setting Password
This is the function for setting and changing the password for a registered user. Open the
password setting window from the Login window, and then set or change the password.

● User Registration
This is the function for registering or deleting a user who can use the Fieldbus Engineering
Tool. A user is registered or deleted with the user account setting window. Enter the user
name and password with the user account setting window to register a user. The password
can later be changed using the password setting window.
User registration and deletion is performed by logging in with the default user “MASTER”.
User registration and deletion cannot be performed using another user name.

■ On-line Help
The following items are available in Online Help menu.
• Using the Online Manual
Explains how to use the online help
• Builder Definition Items
The items for configuration are listed as topic for help. Form the topic list, click the item
for configuration, the corresponding help message for the item will be opened.
• Fieldbus Index
Displays the contents of this document (Fieldbus Manual).
• Version Information
Displays the version of the Fieldbus Engineering Tool.

TIP
• When using online help, the Fieldbus Online Documents need to be installed. When CENTUM VP/CS
3000/CS 1000 system and the fieldbus tools (engineering tools and device management tools) or
when STARDOM system and the fieldbus tools are applied in the same PC, the Adobe Reader or the
Acrobat Reader in the CENTUM VP/CS 3000/CS 1000 system CD-ROM or in the STARDOM system
CD-ROM should be used.
• In CENTUM VP system, Adobe Reader or Acrobat Reader cannot be used. If the Fieldbus Tool is
installed in the same PC of CENTUM VP system, the Adobe Reader in the CD-ROM of CENTUM
FOUNDATION FIELDBUS TOOL should be used.

SEE ALSO
For more information about installing the Fieldbus Online Document, see the following:
“■ Installing Fieldbus Online Document” in 7.1, “Installing Fieldbus Tools”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-45
■ Environment Setting
▼ Environment Settings
The environment setting provides the three functions indicated below.

● Directory Path Setting


This is the function for setting or changing path information for the directory where the
capabilities files and DD File have been copied.
The default setting is \FF_PRJ\DEVPOOL which is located under the directory where the
Fieldbus Engineering Tool is installed. Change the directory path if the capabilities files and
DD File have been copied to a location other than the default directory.

● Switching Transducer Block Display


▼ Transducer Block
This is the function for switching between display and hide of the transducer block. By
switching to display, the transducer block can be handled in the following dialog boxes.
• Parameter dialog box called from the FB editor
• Download dialog box

TIP
Transducer blocks perform the following functions,
• Converts the data obtained from the physical devices such sensors or actuators into the format that
can be accessed by function blocks.
• Converts the output signals from function blocks into the format that can be applied to physical
devices like sensors or actuators.

● Check the Consistency of Readback Connection Terminal


▼ Check READ-BACK Correspondence of Connection Terminal
By default, the consistency between the output connection terminal and readback connec-
tion terminal is checked before generation. However, this option can be changed.

TIP
When implementing fieldbus system with STARDOM, it is necessary to check the consistency of
readback connection terminal.
When implementing fieldbus system with CENTUM VP/CS 3000/CS 1000, it is not necessary to check
the consistency of readback connection terminal.

SEE ALSO
For more information about checking the readback terminals, see the following:
“● Creating FBAP Block Diagram” in “■ FB Editor (For FBAP Configuration)” in 5.1.7, “Editors”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-46

5.1.9 Network Startup


This is the function for downloading the configuration data created using various
editors to the fieldbus device. Download is performed with the fieldbus device con-
nected to the fieldbus.

■ Overview of Network Startup


The diagram below shows the overview of the network startup.

Network startup
Project database

Project device pool


Download
Configuration data

Legend
Data flow
Fieldbus
050127E.EPS

Figure Overview of the Network Startup

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-47
■ Download
▼ Downloading
This will load the configuration data to the fieldbus device.
The download function includes the functions indicated below.
• Download using the Download dialog box
Data is downloaded to all devices (group download). Also, resource blocks, function
blocks, transducer blocks and devices can be selected in multiple and downloaded all
at once.
• Download using the project manager
Data is downloaded to individual devices (individual download.)

The user can set whether to include block parameters in the data targeted for downloaded.
Also, download history is saved.
Group download is required in the circumstances described below.
• When the function block configuration has been changed
• When the LAS has been changed
• When the FB schedule has been changed
• When the common communication parameters in the network have been changed
• When devices have been added or deleted

TIP
• It is necessary to change the function block parameters of the device subject for downloading, in
advance, in order to safely perform download process with respect to an operating fieldbus system.
This parameter change is performed with the operation and monitoring function.
• When downloading block parameters, it is necessary, in advance, to upload the block parameters of
the device subject for downloading.

SEE ALSO
For more information about changing parameters to safely perform a download, see the following:
“■ Performing Pre-Downloading Operation” in 5.5.5, “Executing Project Startup”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-48

5.1.10 Maintenance
With the maintenance function, the upload function is used to upload resource
block, function block, and transducer block parameter values to the project data-
base.

■ Overview of Maintenance
The diagram below shows the overview of the maintenance function.

Maintenance
Project database

Project device pool


Upload
Configuration data

Legend
Data flow
Fieldbus
050128E.EPS

Figure Overview of Maintenance

■ Upload
▼ Uploading
The upload function is the function that the configuration data set in the fieldbus device is
uploaded to the project database in the Fieldbus Engineering Tool. Resource block, func-
tion block, and transducer block parameter values are uploaded. Only static parameters
can be uploaded.
The upload function includes the functions indicated below.
• Upload function using the Upload dialog box
Parameter values for all devices are uploaded. Also, resource blocks, function blocks,
transducer blocks and devices can be selected in multiple and their parameter values
uploaded all at once.
• Upload function using the project manager
Parameter values for individual device are uploaded.

Also, upload history is saved.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-49

5.1.11 Directory Structure for the Fieldbus Engineering Tool


This section explains the overall structure of the directories controlled by the Field-
bus Engineering Tool, as well as each directory and each file.

■ Overall Structure of the Fieldbus Engineering Tool Directories


The structure of the directories controlled by the Fieldbus Engineering Tool is shown in the
diagram below. The management of these directories and files is performed with the project
manager.

KAPPA

Insthist.txt

Manifest.txt

Readme.txt

Bin

Various setting files, various executable files, help file, etc.

SysDb
System database file

Ff_prj
Configuration object file

DevPool
MANUFAC_ID(*1)
DEV_TYPE(*2)
Device capabilities file (.cff)

DD File (.ff5/.ffo, .sy5/.sym)

Project directory

PrjDb
Project database file

Lpr
Print file

Src
System configuration file

Device object file

Hfs
Host file

Log
Error log file
Legend
Project directory
Folder
File

050129E.EPS
*1: MANUFAC_ID is indicated by a 6-digit number in hexadecimal.
*2: DEV_TYPE is indicated by a 4-digit number in hexadecimal.

Figure Directory Structure

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-50
■ Summary of Directory and File

● KAPPA
This is the directory where all files and directories related to the Fieldbus Engineering Tool
are stored.

● Insthist.txt
This is a text file that saves the processing logs when the Fieldbus Engineering Tool is
installed.

● Manifest.txt
This is a text file that describes the Fieldbus Engineering Tool information at the time of
shipment.

● Readme.txt
This is a text file that describes important notes and precautions related to the Fieldbus
Engineering Tool.
Be sure to read this before using the Fieldbus Engineering Tool.

● Bin
This is the directory where SysDb, various executable files, setting files, help file, etc. are
stored.

● SysDb
This is the directory where the system database is stored.

● Configuration Object File


This is the file that stores the setup information for the HIS or PC where the Fieldbus
Engineering Tool is installed.

● DevPool
This is the directory where the device capabilities files and DD File are stored.

● Project Directory
This is the directory where all files and directories related to a single project are stored.

● PrjDb
This is the directory where the project database is stored.

● Project Database File


This is the file for the project database.

● Lpr
This is the directory where the print file is stored.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-51
● Print File
This is the file output using the print function.

● Src
This is the directory where the configuration data files are stored.

● System Configuration File


This is the file where configuration data for the project is recorded.

● Device Object File


This is the file where configuration data for devices registered in the project is recorded.

● Hfs
This is the directory where the host file set is stored.

● Host File Set


This is a group of files where project information is recorded. Information used in the
application that operates in the supervisory system (host application) is recorded in text
format. A host file set consists of multiple files. The individual files are called host files.

● Log
This is the directory that stores the error log files and history files when downloading or
uploading is performed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-52

5.1.12 Configuration Procedure Using Fieldbus Engineering Tool


This section explains the basic procedure when performing the fieldbus configura-
tion using the Fieldbus Engineering Tool.

■ Basic Configuration Procedure Using Fieldbus Engineering Tool


The basic procedure for configuring the fieldbus can be broadly divided into the following
phases.

Start

Initial setting of
the Fieldbus Engineering Tool

Settings for the project


and fieldbus device

Settings for FBAP

Project startup

End

050130E.EPS

Figure Basic Configuration Procedure when Using Fieldbus Engineering Tool

SEE ALSO
• For “initial setting of the Fieldbus Engineering Tool,” see the following:
5.2, “Initial Settings of Fieldbus Engineering Tool”
• For “settings for the project and fieldbus device,” see the following:
5.3, “Setting Project and Fieldbus Device”
• For “FBAP settings,” see the following:
5.4, “Settings for FBAP”
• For “project startup,” see the following:
5.5, “Project Startup”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-53
■ Outline of Procedures

● Initial Setting of the Fieldbus Engineering Tool


Security related settings such as user name and password, as well as settings related to
communication in the control bus are performed.
Also, capabilities files for the fieldbus device are imported to the Fieldbus Engineering Tool.

● Settings for the Project and Fieldbus Device


A project is created and devices are registered in the created project.
Also, settings related to the network configuration of the registered devices are performed.

● Settings for FBAP


Function blocks of registered devices are combined and the FBAP (function block applica-
tion process) is created. Scheduling of communication with the created FBAP function
block is performed.

● Project Startup
This procedure performs the preparations necessary for project startup, then starts a
project.
Also, it backs up the project for which startup was completed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-54

5.2 Initial Settings of Fieldbus Engineering Tool


As the initial settings of Fieldbus Engineering Tool, settings related to security,
communication and environment can be set; capabilities files and DD Files can be
imported to the system database.
This section explains the initial settings of Fieldbus Engineering Tool.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-55

5.2.1 Procedure for Initial Setting of the Fieldbus Engineering


Tool
In the initial setting of the Fieldbus Engineering Tool, settings necessary to perform
communication for the HIS or the master PC with the Fieldbus Engineering Tool
installed are set; and importing of capabilities files is performed.

■ What is the Initial Setting of the Fieldbus Engineering Tool?


In the initial setting of the Fieldbus Engineering Tool, security settings, control bus settings
and environment settings are determined.
Also, capabilities files and DD File are imported to the system database. When capabilities
files are imported to the system database, the capabilities file and DD File setting data is
automatically copied to a newly created project.

■ Flow of the Initial Setting of the Fieldbus Engineering Tool


The flow of the initial setting of the Fieldbus Engineering Tool is indicated below.

Start of initial setting


of the Fieldbus Engineering Tool

Calling the project manager

Security setting

Control bus setting

Environment setting

Importing capabilities files and


DD File to the system database Legend
Operations that
are always performed
Operations performed
as necessary
End of initial setting
of the Fieldbus Engineering Tool Start and end of operation

050201E.EPS

Figure Flow of the Initial Setting of the Fieldbus Engineering Tool

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-56
■ Summary of Each Procedure

● Calling the Project Manager


Start the Fieldbus Engineering Tool and call the project manager.
If the CENTUM VP/CS 3000/CS 1000 system builders and the Fieldbus Engineering Tool
are installed in the same machine, the project manager can be called from the system
builders.

SEE ALSO
For more information about calling the project manager from the system builders, see the following:
4.2.6, “Start Fieldbus Engineering Tool”

● Setting the Security


Security related settings, such as, user name and password are set to restrict the users
who can user the Fieldbus Engineering Tool, in order to ensure the integrity of the configu-
ration data.

● Setting the Control Bus


The control bus is set to specify the communication path of the HIS or master PC in the
network. The control bus settings are set using the “control bus communication function;”
and not the Fieldbus Engineering Tool.

● Setting the Environment


Specify the directory path where the capabilities files and DD File are stored. Whether to
display or hide the transducer block is also set.

● Importing Capabilities Files and DD File to the System Database


Device capabilities files and DD File are imported to the system database in order to
register devices in the project.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-57

5.2.2 Calling Project Manager


The project manager is called to perform settings with respect to the Fieldbus Engi-
neering Tool.
The various functions and editors of the Fieldbus Engineering Tool can be called
from the project manager.

■ Calling Project Manager


The following procedure is used to call the project manager.
1. Select [Fieldbus tool], then [Engineering tool] from the Windows [Start] menu.
The Login window is displayed.

Login

User Name(U) OK

Change Password
Password(P)
Tool Exit

050202E.EPS

Figure Login Window

2. Enter the user name and password. Then click the [OK] button.
Log into the Fieldbus Engineering Tool and the Copyright dialog box is displayed.

TIP
With the Fieldbus Engineering Tool, the default user name “MASTER” is automatically registered at the
time of installation. In the state in which it was installed, there is no password set for “MASTER”. Accord-
ingly, a user can login by clicking the [OK] button without entering a password.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-58
3. Click the [OK] button.
The Fieldbus Engineering Tool starts and the project manager is displayed.
a
p
p
a
Project Manager
Project System Device Pool View Option Help

050204E.EPS

Figure Project Manager

■ Exiting Project Manager


When configuration using the Fieldbus Engineering Tool is completed, exit the project
manager.
When exiting the project manager, select [Exit] from the [Project] menu for the project
manager.
The project manager closes and the Fieldbus Engineering Tool is exited.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-59

5.2.3 Setting Security


This is the operation for registering and deleting users, and setting passwords to
restrict the users, who can login to the Fieldbus Engineering Tool, to maintain the
integrity of the configuration data.

■ User Registration and Deletion


New users, who can log into the Fieldbus Engineering Tool, can be registered with the
Login User List dialog box. Registered users can also be deleted.
Registration and deletion of users can only be performed when logged in with the user
name “MASTER.” When registering or deleting users, login with the user name “MASTER.”
Also, the user name that can be entered are within 20 alphanumeric characters (including,
underscores and hyphens). For the user name, there is no distinction between uppercase
and lowercase characters.

TIP
A list of registered users can be viewed in the Login User List dialog box, even when a user name other
than “MASTER” is logged in. However, if the registration or deletion operation is performed, an error
message is displayed.

● User Registration
1. Select [Security], then [User entry] from the [Open ] menu in the project manager.
The Login User List dialog box is displayed.

Login User List

MASTER Register

Delete

Close

050205E.EPS

Figure Login User List Dialog Box

2. Click the [Register] button.


The Account Registration dialog box is displayed.
3. Enter the user name, then click the [OK] button.
The user is registered and the Account Registration dialog box closes. The user name
of the registered user is displayed in the Login User List dialog box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-60
● User Deletion
Select the user name of the user to be deleted in the Login User List dialog box, and then
click the [Delete] button.
The selected user is deleted.

TIP
The default user “MASTER” cannot be deleted. If an attempt is made to delete “MASTER”, an error
message is displayed.

■ Changing a Password
The password for a registered user can be changed in the Change Password dialog box.
Also, only the password of the user currently logged in can be changed. To change the
password of another user, login with that user’s name.
Furthermore, the user name that can be entered are within 14 standard-width alphanu-
meric characters (including, underscores and hyphens). For the password, there is a
distinction between uppercase and lowercase characters.

1. Select [Security], then [Change password] from the [Open] menu in the project man-
ager.
The Change Password dialog box is displayed.

Change Password

User Name: MASTER OK

Now Password(P) Cancel

New Password(N)

Re-enter New Password(R)

050206E.EPS

Figure Change Password Dialog Box

2. Enter the current password in the “now password” box, enter the password you wish to
change to in the “new password” box, and then re-enter this password in the “re-enter
new password” box.
3. After entry is complete, click the [OK] button.
The password is now changed and the Change Password dialog box closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-61

5.2.4 Configuring Control Bus


Control bus can be configured to specify the communication path of the HIS or
master PC in the network.

TIP
Control bus configuration is not required for STARDOM.

■ Configuring Control Bus


Control bus configuration is the operation for specifying the communication path to perform
communication with the fieldbus. Settings related to the control bus, such as, domain name,
station name, and segment name are set. Communication between the HIS or master PC
in the fieldbus system and the fieldbus devices is performed via two types of networks: the
control bus and the fieldbus. For this reason, the communication between the HIS or master
PC and fieldbus devices can not be established unless control bus setting is completed.

This control bus setting must be completed prior to downloading.


Control bus configuration window can be called from Feidlbus Engineering Tool on an HIS
or a master PC. Choose [Control Bus Configuration] taskbar on [Tools] menu may call up
the Control Bus Configuration Window.

The segment name and ACF11 loading position (FCS station name, RIO or ESB bus
number, node numbers, unit number and, slot number) need to be specified in the control
bus configuration window. When doing so, the project name defined by engineering tool
should be used as the segment name. If the segment name does not match the project
name, download cannot be performed.

SEE ALSO
For more information about the procedure for setting the control bus, see the following:
“■ Configuring Control Bus (Settings after Installation)” in 7.1, “Installing Fieldbus Tools”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-62

5.2.5 Setting Environment


When the location to store the capabilities files and DD File has been changed from
the default directory, specify the directory path indicating where the capabilities files
and DD File are stored. Also, whether to display or hide the transducer block can be
selected. These settings are done in the Environment Settings dialog box.
And whether to check consistency of readback connection terminals can be set.

TIP
The default location where the capabilities files and DD File are stored is FF_PRJ\DEVPOOL which is
found under the directory where the Fieldbus Engineering Tool is installed. The corresponding directory
path must be specified when the capabilities files and DD File are stored somewhere other than in this
directory.

■ Calling Environment Settings Dialog Box


▼ Environment Settings
Select [Environment settings...] from the [Option] menu in the project manager. The Envi-
ronment Settings dialog box opens.

Environment Settings

Directory Path of DD file/Capabilities File


D:/Fieldbus/kappa/DD Refer...

Show Transducer Blocks


✓ Check READ-BACK correspondence of Connection Terminal

OK Cancel

050207E .EPS

Figure Environment Settings Dialog Box

■ Specifying the Directory Path Indicating Where the Capabilities Files and
DD File are Stored
The procedure below is used to specify the directory path for where the capabilities files
and DD File are stored.
1. Specify the directory path using one of the following operations.
• Select the directory path from the [Directory Path of Capabilities files/DD Files] combo
box.
• Specify the directory path in the directory reference dialog box that appears when the
[Refer...] button is clicked.
2. Click the [OK] button.
The directory path is changed and the screen returns to the project manager.
Clicking on the [Cancel] button returns the screen to the project manager without
changing the directory path.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-63
■ Display or Hide Transducer Block
Select whether or not to display the transducer block in the following dialog boxes.
• Parameter dialog box called from the FB editor
• Download dialog box
Follow the procedure below to switch between display and hide.
1. Click the [Transducer block] check box to switch between display and hide.
• Enter a check mark in the box to display the transducer block.
• Remove the check mark, and the transducer block will not be displayed.
2. Click the [OK] button.
The display setting of the transducer block is switched and the screen returns to the
project manager.
Clicking on the [Cancel] button returns the window to the project manager without
switching the display setting.

■ Check the Consistency of Readback Connection Terminal


Whether to check or not check the consistency of the reaback connection terminals during
FB editor generation can be set.
The option is set as follows.
1. Option of [Check Read-Back Correspondence of Connection Terminal]
• Check the option box [Check READ-BACK Correspondence of Connection Termi
nal], consistency of the reaback connection terminals will be checked during FB
editor generation.
• Uncheck the option box [Check READ-BACK Correspondence of Connection
Terminal], consistency of the reaback connection terminals will not be checked
during FB editor generation.

2. Click [OK] Button


Click [OK] button, the option [Check READ-BACK Correspondence of Connection
Terminal] switches from Checked to Unchecked or vice versa, then the display returns
to Project Manager.
Click [Cancel] button, the option [Check READ-BACK Correspondence of Connection
Terminal] is intact, and the display returns to Project Manager.

IMPORTANT
When implementing fieldbus system with STARDOM, it is necessary to check the consis-
tency of readback connection terminal.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-64

5.2.6 Importing Capabilities Files and DD Files to System


Database
When there are shared device capabilities files or DD files in the created project,
these capabilities files and DD files are imported to the system database.

■ Importing Capabilities Files and DD Files to System Database


Before importing the capabilities files and DD files to the system database, specify in the
Environment Settings dialog box the directory path indicating where the capabilities files
and DD files are stored.
The following procedure is used to import capabilities files and DD files to the system
database.
1. Select [Display ...] from the [System device pool] in the project manager.
The System Device Pool dialog box is displayed.

System Device Pool

Imported Capabilities File


Add...
ACF11
Delete...

Close...

Vendor Name: Yokogawa Electric Co Device Revision: 05


Device Name: ACF11 DD Revision: 01
Model Name: ACF11 CF Revision: 03

050208E.EPS

Figure System Device Pool Dialog Box

By selecting the device name in the “Imported Capabilities File” list box in the System
Device Pool dialog box, the device revision, DD revision and CF (capabilities file) revision
can be checked.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-65
2. Click the [Add] button.
The Capabilities File Selection dialog box is displayed.

Capabilities File Selection

Model Name Revision Device Revision DD Revision


- DEVPOOL EJA 01 02 01
+ 001151 EJA 02 02 01
- 594543 EJA 01 02 02
+ 0001
- 0003
+ STD
- LC1

OK Cancel

050209E.EPS

Figure Capabilities File Selection Dialog box

In the tree view on the left side of the screen, manufacturer IDs, device types and
option folders are displayed hierarchically.

IMPORTANT
Before importing the capability files and DD files from external media, the following prepa-
ration should be done to create a location for holding the copied DD files and capability
files.
Under the folder for device type (such as 0003), create a subfolder for holding the imported
capability files. Imported DD files are not held in this folder. The DD files, regardless op-
tional or not, are held in the folder for device type. It is better to use a name for the subfolder
that is easy to understand what optional capability file is held.

3. Select the device type in the tree view.


In the list view on the right side of the screen, information for each capabilities file
including name (device name), revision information, file date and file type are dis-
played.
4. Select the capabilities file to be imported in the list view.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-66
5. Click the [OK] button.
Import begins.
To terminate the import operation, click on the [Cancel] button. The screen returns to
the Capabilities File Selection dialog box without importing the file.

After the import begins, the DD files corresponding to the capabilities file is also read.
The operation and results will differ depending on whether the DD files to be read
exists under the specified directory.
• When the DD files to be read exists under the specified directory
The Capabilities File Selection dialog box closes and the device name of the capabili-
ties file that has been imported is displayed in the “Imported Capabilities File” list box
found in the System Device Pool dialog box.
• When the DD files does not exist under the specified directory
The confirmation message dialog box appears.

Project Manager

The DD file corresponding to the selected


Capabilities File does not exist.
Continue without the DD file.

OK Cancel

050211E.EPS

Figure Confirmation Message Dialog Box

Click the [OK] button to import the capabilities file without importing the DD files . The
Capabilities File Selection dialog box closes and the device name of the capabilities
file that has been imported is displayed in the “Imported Capabilities File” list box
found in the System Device Pool dialog box.
To terminate the import operation, click on the [Cancel] button. The import operation is
aborted and the screen returns to the Capabilities File Selection dialog box.
6. Repeat the operation in steps 2 to 5 as necessary.
7. Click the [Close] button.
The System Device Pool dialog box closes.

TIP
• When importing a capability file, the revision of the device (DEV_REV), the revision of DD file, the
revision of capability file and the optional information are checked. If an identical capability file exists,
the importing is aborted.
• The same capabilities file as the one already imported cannot be imported again. If an attempt is
made to import the same capabilities file, an error dialog box is displayed.
To import the same capabilities file again, first delete the imported capabilities file from the system
database.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-67
■ Deleting Capabilities Files and DD Files from System Database
If for some reason such as a version upgrade, a capabilities file is no longer necessary, it
can be deleted from the system database. When a capabilities file is deleted, the DD Files
corresponding to that capabilities file is also deleted.
The following procedure is used to delete a capabilities file from the system database.
1. Select [Display...] from the [System device pool] in the project manager.
The System Device Pool dialog box is displayed.
2. Select the device name of the capabilities file to be deleted from the “Imported Capa-
bilities File” list box.
3. Click the [Remove] button.
The deleted file will disappear from the list box.
4. Repeat the operation in steps 2 to 4 as necessary.
5. Click the [Close] button.
The System Device Pool dialog box closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-68

5.3 Setting Project and Fieldbus Device


After the initial setting for the Fieldbus Engineering Tool is completed, settings for
the project and fieldbus device are determined next.
This section explains the setting for the project and fieldbus device.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-69

5.3.1 Setting Procedure for the Project and Fieldbus Device


In the settings for the project and fieldbus device, the project is created and the
devices are registered.

■ What are the Settings for the Project and Fieldbus Device?
First, a new project is created or an existing project is opened. Next, the devices to be used
in the project are registered in the project. The function block for the device can be used
with the FBAP when the device is registered.
The various parameters set for the registered device are changed as necessary.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-70
■ Setting Flow for the Project and Fieldbus Device
The setting flow for the project and fieldbus device are indicated below.

Start setting for the project


and fieldbus device

Create new project or open a project

Import capabilities files and DD Files


to the project database

Import device configuration data


to the project database

Call device editor

Display device ID. (*1)

Register device to project

Call network editor

Set or change network parameters

Change device parameters

Upload to project database

Update DD file and capability file.

Replace a physical device then update


its DD file and capability file. Legend
Operations that
are always performed
Operations performed
as necessary
End settings for the project
and fieldbus device Start and end of operation

050301E.EPS
*1: Only performed on HIS and master PC.

Figure Setting Flow for the Project and Fieldbus Device

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-71
■ Summary of Each Procedure

● Create New Project or Open a Project


Create a new project.
Also, to change an existing project, open the project to be changed.

● Import Capabilities Files and DD Files to the Project Database


Import the capabilities files and DD Files to the project database when using new devices
or new capabilities files and DD Files.

● Import Device Configuration Data to the Project Database


Import the device configuration data to the project database when appropriating a device.

● Call Device Editor


Call the device editor to perform device settings.

● Display Device ID
Display the device Ids of all devices connected to the fieldbus.

● Register Device to Project


Register the device to be used in the project to the project. Also, delete devices no longer
necessary.

● Call Network Editor


Call the network editor to set the node address of the device and device class.

● Set or Change Network Parameters


Set or change network parameters for each device. The parameters to be set are the node
address and device class.

● Change Device Parameters


Change the device parameters as necessary.

● Upload to Project Database


Upload block parameter values set in the fieldbus device to the project database as neces-
sary.

● Update DD File and Capability File


The registered device information is updated after the device DD file, capability file or the
physical device itself is changed.

● Replace a Physical Device then Update Its DD File and Capability File
If a physical device is replaced, the DD file and capability file of the device as well as the
device information needs to be updated.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-72

5.3.2 Creating a New Project or Opening a Project


The Fieldbus Engineering Tool controls the device connected to one segment of the
fieldbus in units called a project. Engineering is performed for each project.
If a project is not created, then a new project is created. If the settings for an existing
project are changed, then the project which to be changed is opened.

■ Creating a New Project


A project is created using the following procedure.
1. Select [New (N) ...] from the [Project (P)] menu in the project manager.
The file open dialog box is displayed.

Open ?

Save in: Ff_prj

DevPool
Example
Prj1

File name: Save


Save as type: Project files(*.prj) Cancel

050302E.EPS

Figure Example of File Open Dialog Box

2. If the project is to be created in a specific directory, select the directory where the
project will be created.
Select the same directory as the one specified in the create New IOM dialog box of the
system builders in order to use the Fieldbus Engineering Tool configuration data with
the system builders.
3. Enter the project file name for the project to be created in the “file name” box, then click
the [Save] button.
A new project is created and a project database is generated for saving the various
settings related to the project. Also, all of the capabilities files imported to the system
database are copied to the project database.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-73
Information related to the project is displayed in the project manager when the process
for creating a new project is completed.
a
p
p
a Project Manager
Project Device Pool Device Tools Network View Option Help

Devices in Project
Project Title: pr j
ACF11_14
PI101 Date of Creation: 06, 16, 2008
PCV101
Date of Modification: 06, 16, 2008

Project Comment

050303E.EPS

Figure Project Manager (With the Project being Opened)

Table Information Displayed in the Project Manager


Display contents Description
Devices in the project List of the tag names for the physical devices registered in the project
Project title Title of the project
Date of creation The date the project was created
Date of modification The date the last changes were made to the project
Comments that can be attached to the project (maximum of 255 standard-width
Project comment
characters, maximum of 127 double-width characters)
050304E.EPS

Clicking the [Cancel] button closes the file open dialog box without creating the
project.
4. Enter a comment in the “comment” input box in the project manager as necessary.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-74
■ Opening an Existing Project
Open the project using the following procedure when making changes to an existing
project.
1. Select [Open (O) ...] from the [Project (P)] menu in the project manager.
The file open dialog box is displayed.
2. Select the directory where the project file resides.
3. Select the name of the project file to be edited from the File name list box.
4. Click the [OPEN] button.
Information related to the selected project is displayed in the project manager. Clicking
the [Cancel] button closes the file open dialog box without opening the project.

TIP
• Only one project can be opened at a time. If a project is already opened, first close the project that is
open and then open another project.
• Information related to a project can be saved on to a print file. Select [Print (P) ...] from the [Project
(P)] menu in the project manager.

■ Reading a Project
The contents of an existing project can be accessed from the currently opened project.
1. Select [ReNew...] from the [Project] menu in the project manager window.
The file open dialog box will be displayed.
When a project is not open, the [ReNew ..] will not be displayed on [Project] menu.
2. Select the directory where the project file to be read has been saved.
3. Select the project file name to be read from the File name list box.
4. Click the [OPEN] button.
A dialog box will appear to prompt the confirmation of losing data in currently open
project. Click [OK] to continue.
The contents of the selected project are read to the currently open project.
Clicking the [Cancel] button closes the file open dialog box without opening the
project.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-75
■ Saving the Project with a New Name
Give the currently open project a different name and save.
1. Select [Save As...] on the [Project] menu in the project manager window.
The Save As dialog box will be displayed.
When a project is not open, the [Save As...] will not display on the [Project] menu.
2. Select the directory for saving the project.
3. Specify a different project name.
4. Click the [OK] button.
The currently open project will be saved into a file with a specified name. The specified
file name will become the name of the saved project.
Clicking the [Cancel] button can close the file open dialog box without saving the
project.

■ Closing a Project
Close the project after the project settings are completed.
When closing a project, select [Close (C)] from the [Project (P)] menu in the project man-
ager.

TIP
If various editors have been called from the project manager, all of the called editors will be closed when
the project is closed. At this time, whatever has been set in the editor will automatically be saved for all
editors other than the FB editor. If changes have been made in the FB editor, the message “Do you want
to save?” will be displayed.

■ Deleting a Project
An existing project can be deleted when it is no longer necessary. Deleting a project erases
the project file and project database.
Delete a project using the following procedure.
1. Open the project to be deleted.
2. Select [Delete (D)] from the [Project (P)] menu in the project manager.
A dialog box asking for confirmation whether it is okay to delete the project is dis-
played.
3. Click the [OK] button.
The opened project is deleted.
Clicking the [Cancel] button closes the dialog box without deleting the project.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-76

5.3.3 Importing Capabilities Files and DD Files to the Project


Database
Capabilities files and DD files are imported to the project database as necessary.
This operation is performed when there are capabilities files necessary for individual
projects other than those that were automatically copied at the time when the project
was created.
Importing capabilities files automatically imports the DD files corresponding to
those files. If for some reason, such as a version upgrade, capabilities files and DD
files become no longer necessary, they can be deleted from the project database.

■ Importing Capabilities Files and DD Files to the Project Database


Before importing the capabilities files and DD files to the system database, specify in the
Environment Settings dialog box the directory path indicating where the capabilities files
and DD files are stored.
The following procedure is used to import a capabilities file and DD files to the project
database.
1. Open the project with the capabilities file and DD files to be imported.
2. Select [Display (S) ...] from the [Device pool (E)] menu in the project manager.
The Device Pool dialog box is displayed.
3. Click the [Add] button.
The Capabilities File Selection dialog box is displayed.
4. Select the device type in the tree view on the left side of the screen.
In the list view on the right side of the screen, information for each capabilities file
including name (device name), revision information and file date are displayed.
5. In the list view, select the device name corresponding to the capabilities file to be
imported.
6. Click the [OK] button.
Import is executed after it is confirmed that the DD files corresponding to the capabili-
ties file to be read exists under the specified directory.
Clicking the [Cancel] button closes the Capabilities File Selection dialog box without
importing the file.
7. Repeat steps 3 to 6 of the procedure as necessary.
8. Click the [Close] button.
The Device Pool dialog box closes.

SEE ALSO
For more information about importing DD files, see the following:
5.2.6, “Importing Capabilities Files and DD Files to System Database”

TIP
A list of the devices that can be registered in the project can be saved as a print file. Select [Print (P) ...]
from the [Device pool (E)] menu.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-77
■ Deleting Capabilities Files and DD Files from the Project Database
Delete capabilities files from the project database. Along with the capabilities files, the
corresponding DD files will also be deleted. Deletion is done using the following procedure.
1. Select [Display (S) ...] from the [Device pool (E)] menu in the project manager.
The Device Pool dialog box is displayed.
2. Select the device name of the capabilities file to be deleted from the “Imported Capa-
bilities File” list box.
3. Click the [Remove] button.
A dialog box asking for confirmation whether it is okay to delete the file is displayed.
4. Click the [OK] button.
The device name of the capabilities file that has been deleted will disappear from the
“Imported Capabilities File” list box in the Device Pool dialog box.
5. Repeat steps 2 to 4 of the procedure as necessary.
6. Click the [Close] button.
The Device Pool dialog box closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-78

5.3.4 Importing Device Configuration Data to the Project


Database
The configuration data is imported to the project database when device settings are
appropriated from another project.

■ Importing Device Configuration Data to the Project Database


The following procedure is used to import device configuration data.
1. Create a new project.
2. Select [Import (I) ...] from the [Device (D)] menu in the project manager.
The file open dialog box is displayed.
3. Click [OK] button.
4. Select the device object file for the device to be imported from the [file name] list box.
5. Click the [OPEN] button.
The configuration data contained in the selected device object is registered to the
project database.
Clicking the [Cancel] button closes the file open dialog box without importing the file.
6. Repeat steps 2 to 5 of the procedure if required.

IMPORTANT
The device configuration data can not be imported to an existing project.

TIP
In order to import device configuration data, the capabilities file, which is the source of the device object
file, is copied beforehand to the FF_PRJ\DEVPOOL directory under the directory where the Fieldbus
Engineering Tool is installed (here, copy means copying the file from an external media). If there is no
capabilities file, the device configuration data cannot be imported.
If the capabilities file has already been copied, there is no need to copy the capabilities file.

SEE ALSO
For more information about the configuration data files that can be imported, see the following:
5.1.6, “Project Manager”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-79

5.3.5 Calling Device Editor


Call the device editor. The device editor is used to register a device to the project and
set the configuration data for the registered device.

■ Calling Device Editor


▼ Available Device Types, Devices in Project
The following procedure is used to call the device editor.
1. Open the project. This step is unnecessary if the project is already opened.
2. Select [Device editor] from the [Tool] menu in the project manager.
The device editor is displayed.
a
p
p
a
Device Editor
Edit View Help

Available Device Types Devices in Project

ACF11 ACF11
YVP Add > FI1001
EJA VP1001
Remove

Remove All

Device Name: ACF11 Device Name: ACF11


Vendor Name: Yokogawa Device ID: ACF11-176M
Model Name: ACF11*A PDTag: ACF11-14
Revision: 1 Modify

050305E.EPS

Figure Device Editor

TIP
When the devices with same model name but different revisions are imported, they are indicated with
same device name on device editor. However, their revision numbers displayed can distinguish them.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-80
The “available device types” group box and “devices in project” group box are displayed in
order to import device configuration data. The information for selecting the device to be
registered in the project is displayed in the “available device types” group box.
Information related to the configuration of the device registered in the project is displayed in
the “devices in project” group box.
Table Information Displayed in the “Available Device Types” Group Box.
Box name Display contents
“Available device types” list List of the device types that can be registered in the project
“Device name” Name of device selected in the “available device types” list
“Vendor name” Name of vendor offering the device selected in the “available device types” list
“Model name” Name of model of device selected in the “available device types” list
“Revision” Revision of the device selected in the “available device types” list
050306E.EPS

Table Information Displayed in the “Devices in Project” Group Box


Box name Display contents
“Devices in project” list List of device IDs set in the configuration data
“Device name” Device name of the device selected in the “devices in project” list
“Device ID” Device ID of the device selected in the “devices in project” list
“PD tag” Physical device tag of the device selected in the “devices in project” list
050307E.EPS

■ Exiting the Device Editor


Exit the device editor after the device configuration data setting is completed.
Select [Exit (X)] from the [Edit (E)] menu in the device editor.
The device editor closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-81

5.3.6 Display Device ID


▼ Display Device ID
The IDs of all fieldbus devices connected to the H1 fieldbus can be displayed. To
display the devices’ IDs, the fieldbus communication must be established via ACF11
module. The IDs can be displayed on HIS or master PC. The following items are
displayed together with the device IDs.
• Device Tag Name
• Node Address
• Device Class
• Device Revision Information

■ Displaying Device ID
On the dialog box for displaying device ID, an option [Display Device Revision Info] can be
checked so as to display the revision information together with the device ID. However, it
takes much more time to display the revision information. By default, this option is not
checked. Though this option is not checked, the revision information of each device is
displayed on the device ID dialog box for each individual device by performing the proce-
dure for displaying individual device ID after the device ID is updated (refreshed).
The process of gathering device information from the field devices can be interrupted. The
device information already gathered before interruption can be displayed. However, on the
device ID dialog box for each individual device the process cannot be interrupted.

● Display Device IDs of New Project


1. Create a new project on project manager window of Fieldbus Engineering Tool. Then
register ACF11 fieldbus communication module to the project.
2. Click [Control Bus Configuration] on [Tools] menu, then enter the segment name of the
fieldbus into Control Bus Configuration window.
3. Click [Download] on [Device] menu to download to ACF11.
After downloading to ACF11, the communication with fieldbus devices via ACF11 is
established.
4. Choose [Display Device ID] on [Project] menu.
[Display Device ID] dialog box displays.

Display Device ID

Device Tag Name Node Address Device ID Device Class MANUFAC_ID DEV_TYPE DEV_REV DD_REV
EJA1001 0xF5 594543EJA... BASIC 0x594543 0x0003 0x02 0x01

Display Device Revision Info Stop Save Individual Update Update

050308E.EPS

Figure Display Device ID Dialog Box

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-82
5. If the information regarding the device revision is required, check the option [Display
Device Revision Info]. By default, this option is not checked.
When the dialog box is closed, the checked option becomes invalid. So that this option
is remain unchecked when the dialog box is open again.
6. Click [Update] button on the dialog box.
The information gathered from the field devices are displayed. If the option [Display
Device Revision Info] is not checked, Device Tag Name, Node Address, Device ID and
Device Class items are displayed. If the option [Display Device Revision Info] is
checked, Device Tag Name, Node Address, Device ID, Device Class items and device
revision information (MANUFAC_ID, DEV_TYPE, DEV_REV and DD_REV) are
displayed.
The fieldbus devices are connected via ACF11 modules, the information of the
fieldbus devices cannot be displayed if they were not configured. However, STARDOM
can display the fieldbus device revision information even the fieldbus devices are not
configured.
To interrupt the process for updating the field device information, go to procedure step
8.
7. The displayed contents can be output to a CSV file by clicking [Save] button.
8. To interrupt the process for updating the field device information, click [Stop] button on
the Display Device ID dialog box. A confirmation dialog box displays. The [Stop] button
is valid only when the [Update] button is pressed.

Display DeviceID

Is Device ID display processing stopped?

Yes No

050327E.EPS

Figure Confirmation Dialog Box

9. Click [OK] button on the confirmation dialog box, the updating process stops after the
process for gathering an individual device is completed. To click [No] button on the
confirmation dialog box, the updating process continues.

SEE ALSO
For more information about displaying the individual device ID after the device information is updated in
the dialog box, see the following:
“● Displaying Individual Device ID”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-83
● Display Device IDs of Existing Project
1. Click [Polling Address Setting] on [Option] menu, then set the ranges of polling ad-
dress.
2. Click [Download] on [Device] menu to download to ACF11.
After downloading to ACF11, the communication with fieldbus devices via ACF11 is
established.
3. Choose [Display Device ID] on [Project] menu.
[Display Device ID] dialog box displays.
4. If the information regarding the device revision is required, check the option [Display
Device Revision Info]. By default, this option is not checked.
When the dialog box is closed, the checked option becomes invalid. So that this option
is remain unchecked when the dialog box is open again.
5. Click [Update] button on the dialog box.
The information gathered from the field devices are displayed. If the option [Display
Device Revision Info] is not checked, Device Tag Name, Node Address, Device ID and
Device Class items are displayed. If the option [Display Device Revision Info] is
checked, Device Tag Name, Node Address, Device ID, Device Class items and device
revision information (MANUFAC_ID, DEV_TYPE, DEV_REV and DD_REV) are
displayed.
To interrupt the process for updating the field device information, go to procedure step
7.
6. Click [Save] button on the dialog box can save the information into a CSV file.
7. To interrupt the process for updating the field device information, click [Stop] button on
the Display Device ID dialog box. A confirmation dialog box displays. The [Stop] button
is valid only when the [Update] button is pressed.
8. Click [OK] button on the confirmation dialog box, the updating process stops after the
process for gathering an individual device is completed. To click [No] button on the
confirmation dialog box, the updating process continues.

SEE ALSO
For more information about displaying the individual device ID after the device information is updated in
the dialog box, see the following:
“● Displaying Individual Device ID”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-84
● Displaying Individual Device ID
1. Following the procedure for displaying device IDs of new project or the procedure
displaying device IDs of existing project to update the device information on the dialog
box.

SEE ALSO
For more information about the procedure for displaying device IDs of new project, see the following:
“● Display Device IDs of New Project”
For more information about the procedure for displaying device IDs of existing project, see the following:
“● Display Device IDs of Existing Project”

2. Choose a device tag from the displayed device list.


If the information regarding the device revision is required, check the option [Display
Device Revision Info].
Click [Individual Update] button.
3. The information of the selected device is displayed.
If the option [Display Device Revision Info] is checked, Device Tag Name, Node
Address, Device ID, Device Class items and device revision information
(MANUFAC_ID, DEV_TYPE, DEV_REV and DD_REV) are displayed. If the option
[Display Device Revision Info] is not checked, Device Tag Name, Node Address,
Device ID and Device Class items are displayed.

TIP
The [Stop] button becomes invalid when the [Individual Update] button is pressed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-85

5.3.7 Registering a Device to the Project


The FBAP is created by combining the function blocks built in the device. In order to
use the device function blocks, the device is registered in the project.

■ Registering a Device to the Project


Configuration data for the device is automatically generated when a device is registered in
a project. The generated configuration data is registered in the project database.
The only devices that can be registered in the project are those whose capabilities files
have been imported to the project database.
The following procedure is used to register a device.
1. Select the type name of the device to be registered from the “available device types”
list box.
2. Click the [Add] button. Or, select [Add to the project (A)] from the [Edit (E)] menu.
The New Device dialog box is displayed. At this time, a character string to which has
been added the device serial number registered in the device type, is entered as the
default value in the “Device ID” box and “PD tag” box.

New Device

Device ID: TMP1


PDTag: TMP1

OK Cancel

050309E.EPS

Figure Example of New Device Dialog Box

3. Enter the device ID in the “Device ID” box.


4. Enter the physical device tag name in the “PD tag” box.
The physical device tag name can be specified with up to 16 alphanumeric characters.

IMPORTANT
• In the specifications for the fieldbus, the physical device tag name can be a maximum
of 32 characters. In the CENTUM VP/CS 3000/CS 1000 system builders, however, the
maximum is 16 characters (standard-width alphanumeric characters). If connecting to
the CENTUM VP/CS 3000/CS 1000 or STARDOM, be sure the physical device tag
name does not exceed 16 characters when setting the physical device tag name with
the Fieldbus Engineering Tool. If more than 16 characters are used, an error occurs
when expanding with system builders.
• Only one ACF11 can be registered in one fieldbus project.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-86
5. Click the [OK] button.
The New Device dialog box closes and the physical device tag name for the device
that has been added is displayed in the “Devices in Project” list box.
Clicking the [Cancel] button closes the New Device dialog box without changing the
device ID and physical device tag name.
6. When completed, close the device editor. And then the network parameters are
automatically calculated.

TIP
A list of the devices registered in the project can be saved to a print file. Select [Print (P) ...] from the
[Project (P)] menu in the project manager.

SEE ALSO
For more information about the device ID of a registered device, see the following:
5.5.3, “Changing a Registered Device ID”

■ Deleting a Device From the Project


Devices that are no longer necessary can be deleted from the project. The user can delete
a specified device only, or delete all devices at one time.

● Deleting a Specific Device


The following procedure is used to delete a specific device.
1. Select the device to be deleted from the “devices in project” list box in the device
editor.
2. Select [Remove (R)] from the [Edit (E)] menu in the device editor.
A dialog box for confirmation will appear.
3. Click [OK] to continue.
Configuration data for the selected device will be deleted from the project database,
then the display of the selected device will disappear from the “devices in project” list
box.
4. Repeat steps 1 and 3 of the procedure if required.
5. When completed, close the device editor. And then the network parameters are
automatically calculated.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-87
● Deleting All Devices
The following procedure is used to delete all devices.
1. Select [Delete all (I)] from the [Edit (E)] menu in the device editor.
A dialog box confirming whether user really wants to delete all devices is displayed.
2. Click the [OK] button.
All device configuration data is deleted from the project database and all device
displays disappears from the “devices in project” list box.
Clicking the [Cancel] button closes the dialog box without deleting the devices.
3. When completed, close the device editor. And then the network parameters are
automatically calculated.

TIP
If the function block for the device to be deleted is arranged in the FBAP block diagram, the device cannot
be deleted. If the delete operation is executed, a dialog box, indicating that the function block has been
arranged in the FBAP block diagram, is displayed.
Before deleting a device, delete all the function blocks for the device to be deleted from the FBAP block
diagram.

SEE ALSO
For more information about the procedure to delete function blocks from the FBAP block diagram, see the
following:
5.4.4, “Placement of Function Blocks in the FBAP Block Diagram”

IMPORTANT
When registering or deleting a device, always be sure to perform generation using the FB
editor.

SEE ALSO
For more information about generation, see the following:
5.4.8, “Generation of the FBAP Configuration”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-88

5.3.8 Calling Network Editor


Calls the network editor. The network editor is used to set the node address and
device class with respect to the device registered in the project.

■ Calling the Network Editor


▼ SM Support
The following procedure is used to call the network editor.
1. Open the project. This step is unnecessary if the project is already opened.
2. Select [Network editor (D)] from the [Tool (T)] menu in the project manager.
The network editor is displayed.
a
p
p
a
Network Editor
Edit View Help

Devices in Project Device


ACF11 Device ID:
EJA Vendor Name: Yokogawa Electric Corp:
YEWFLO Device Name: EJA
YVP Model Name: EJA100
Device Revision: 02 DDRevision :01 CF Revision :01
Option Folder: STD
Parameters
Device Class: Basic
SM Support: 0x17, 0x70, 0x00, 0x00
Node Address: 0xF7 Modify...

050310E.EPS

Figure Network Editor

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-89
In the network editor, the “Devices in project” list box, the “Device” group box, and the
“Parameter” group box are displayed. A list of the physical device tag names for the
devices registered in the project is displayed in the “Devices in project” list box. De-
tailed information regarding the device selected in the “Devices in project” list box is
displayed in the “Device” group box and the “Parameter” group box.
Table Information Displayed in the “Device” Box
Item Description
Device ID ID of the device registered in the project
Vendor Name Name of the vendor supplying the device
Device Name Name of the device (not the tag name)
Model Name Model name of the device
Device Revision Device revision (DEV_REV)
DD Revision DD File revision (DD_REV)
CF Revision Capability file revision
Option Folder Option folder for holding capability files
050312E.EPS

Table Information Displayed in the “Parameter” Box


Item Description
Device Class Class that indicates the communication function
Numeric value when the bit array indicating the function supported by System
Management is expressed as a hexadecimal. Expressed in code that
SM Support
conforms to SM section definitions in “Function Block Application Process
Part 1, 2” (FF 94 890/891)
Node Address Node address that was set
050313E.EPS

■ Exiting the Network Editor


Exit the network editor after the setting of the node address and device class for the device
are completed.
Select [Exit (X)] from the [Edit (D)] menu in the network editor.
The network editor closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-90

5.3.9 Setting or Changing Network Parameters


After a device is registered in the project, the node address and device class are set
manually as device network parameters. The node address can also be assigned
automatically for devices whose node address has not been set.

■ Manually Changing the Node Address and Device Class Settings


The following procedure is used to set or change the network parameters (node address
and device class) for the device.
1. From the “Devices in project” list box in the network editor, select the device for which
the network parameter is to be set or changed.
2. Click the [Modify] button.
The Network Parameter dialog box is displayed.

Network Parameter

Device ID: EJA_8


Node Address: 0x0

Device Class
Basic
Linkmaster

OK Cancel

050314E.EPS

Figure Network Parameter Dialog Box

3. Enter the node address in the “Node address” box.


Set the node address so that there are no duplicate addresses in the project.
ACF11: 0x14 is fixed
Basic: 0xF7 is the high limit
Linkmaster: 0x14 is the low limit
4. Select the device class.
Select either linkmaster or basic. If the device class for a device with built-in linkmaster
communication function is set as linkmaster, then it will operate as a linkmaster de-
vice.
The device class for a device that does not have the linkmaster communication func-
tion cannot be set as linkmaster.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-91
5. Click the [OK] button.
The Network Parameter dialog box closes and the network parameter that was set is
saved in the project database.
Clicking the [Cancel] button closes the Network Parameter dialog box without chang-
ing the network parameter.
6. Repeat steps 1 to 5 as necessary to set the network parameters for each device.

IMPORTANT
Always be sure to use the FB editor to perform generation when the node address has
been changed.

SEE ALSO
For more information about generation, see the following:
5.4.8, “Generation of the FBAP Configuration”

■ Automatically Assigning the Node Address


A node address can automatically be assigned to devices for which a node address has not
been set. To assign the address, select: [Node address auto assignment] from the [Edit]
menu.
The node address will be assigned automatically.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-92

5.3.10 Changing Device Parameters


Change the device parameters as necessary. Since the value described in the capa-
bilities file is set as the default value in the device parameters, it usually does not
matter if the setting is left as the default value. Change the default settings only if it
is necessary. Parameters can be changed also by directly entering a numeric value
or keyword or selecting a keyword from the keyword list.

■ Changing the Device Parameters


▼ All Parameters
The following procedure is used to change the device parameters.
1. Select [All Parameters (A)] from the [Edit (E)] menu in the network editor.
The Parameter dialog box is displayed.

Parameter Dialog

Devices in Project List


- example Parameter Element Value Type Range
+ Common FasArTypeAndRole SERVER+QUB+NOBYPAS OctetString
- Pressure_Transmitter_2 FasDllLocalAddr 248 Unsigned32 0~0xff
- VCR FasDllConfiguredRemot FREE Unsigned32 0~0xff
VCR1 FasDllSDAP NONSCHEDULED+DISOR OctetString
VCR2 FasDllMaxConfirmDelay 60000 Unsigned16
VCR3 FasDllMaxConfirmDelay 60000 Unsigned16
VCR4 FasDllMaxDlsduSize 128 Unsigned16 1~256
VCR5 FasDllResidualActivity TRUE Boolean 0x00,0xff
VCR6 FasDllTimelinessClass OctetString
VCR7 FasDllPublisherTimeWir TRUE Unsigned16
VCR8 FasDllPublisherSynchro FALSE Unsigned32
VCR9 FasDllSubscriberTimeW Unsigned16
+ Valve_Positioner_3 FasDllSubscriberSynchr Unsigned32
FmsVfdId Unsigned32 0~
FmsMaxOutstandingSer Unsigned8 0~
FmsMaxOutstandingSer Unsigned8 0~
FmsFeaturesSupported NONE,GET_OD+READ+W BitString

OK Cancel Print File

050315E.EPS

Figure Parameter Dialog Box

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-93
“Project,” “Common area or device,” “Group” and “Element” are expanded as a
hierarchical structure in the “Devices in Project” list.
Table Contents Displayed in the “Devices in Project” List
Display target Screen display Remarks
Project Project name
The screen display cannot be changed.
Common area “Common area” Parameter groups common to the network (projects) are
shown in the common area.
Device Physical device tag name
Group Parameter group name Parameters with the same meaning are displayed in group.
This is displayed when the group is comprised of multiple
Element Element name (number)
elements.
050316E.EPS

2. Select the parameter group, VCR or element to be edited from the “Devices in Project”
list.
A list of the parameters to be edited will be displayed in the list view on the right side of
the screen.
In the list view, “Parameter name,” “Element name,” “Value,” “Type” and “Range” will be
displayed. If the parameter is rewritable, only the value can be changed.
Table Details of the List View
Box name Display contents
Parameter Name of the parameter.
Element Name of the parameter element.
Value Value of the specified parameter. Setting is also possible.
Type Parameter data type.

Range High and low limit of the parameter and number of


characters that can be entered.
050317E.EPS

3. Enter the parameter value in the “Value” box using one of the following operations.
• Enter the value directly in the input area using the keyboard
• Select a keyword as the value to be set from the keyword list that is displayed by
clicking on the arrow button besides the input area.
4. Click the [OK] button.
The Parameter dialog box closes and the setting is saved in the project database.
Clicking the [Cancel] button closes the Parameter dialog box without changing the
device parameters.

TIP
• Parameters displayed in gray and the parameters (element) prohibited for changing can not be
rewritten.
• The settings of the selected parameter group or VCR parameters can be saved as a text file for
printing. When clicking on the “Print file” button in the Parameter dialog box, a dialog box for opening
a file appears. In this dialog box, enter the name of the file to be saved.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-94
The following parameter groups can be selected with the Parameter dialog box called from
the network editor.
• NMIB: NM (Network Management) parameters (common)
• SMIB: SM (System Management) parameters (common)
• SMAA: SM (System Management) parameters
(for address assignment, common)
• LAS: LAS schedule parameters (common)
LASAR: Version part
LASDOM: Summary part
LASSUB: Sub-schedule part
• VCR: VCR (Virtual Communication Relationship) parameters

TIP
Parameters can be changed also in the Parameter dialog box called from the FB editor. However, the
parameter groups that can be selected will differ.

IMPORTANT
When the network parameters are entered, the range of the values will be checked. This
check is performed based on the range provided as the default (range defined by the
Foundation Fieldbus). The parameter limit values described in the capabilities file are not
used for the check performed when parameters are entered, but used for the consistency
check performed prior to generation.

■ How to Enter Parameters Directly


When directly entering parameter values in the input area, values can be entered using a
keyword in addition to entering a numeric value. The keyword that has been entered is
converted to a numeric value and saved in the database. When the entry is re-displayed, it
is converted back to a keyword.
With those parameters that can be entered via keyword selection, a keyword can be se-
lected from the keyword list that is displayed by clicking on the arrow button besides the
input area.

● Entering a Parameter Directly Using a Numeric Value


Enter the value using the following input format.
• When the parameter data type is Bit String or Octet String
Enter in hexadecimal.
• When the parameter data type is Structure (DS: Data Structure)
Enter in hexadecimal, delimit with comma (,).
When element in the structure is Bit String type, that element can be entered in the
same way as with Bit String.
Example of entry is given below.
Example: Bit String: 0x1010
Data Structure: 0x10, 0x10

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-95
● Entering a Parameter Directly Using a Keyword
When entering a keyword, use the same input format that is used when entering a numeric
value. The elements of keyword are connected using the “+” symbol if the parameter is a
structure including connection type elements, connection type BitString or OctetString.
Example of entry is given below.
Example: ModeBlk=AUTO,AUTO,MAN,O/S
ModeBlk=AUTO,AUTO,AUTO+MAN+O/S,O/S
IoOpts=INVERT+FSTATE

■ How to Enter Parameters via Keyword Selection


The method for entering a parameter via keyword selection differs depending on the pa-
rameter data type.
Examples of entering parameters via keyword selection are given below.

TIP
Elements are entered with the same method that is used when entering parameters.

● BitString parameter (Selection type)


Select one keyword from the keyword list.

QUB_INITIATOR
QUB_RESPONDER

BUN_SUBSCRIBER

050318E.EPS

Figure Keyword Selection for BitString Parameter (Selection Type)

● BitString parameter (Connection type)


More than one keyword can be selected by placing a check mark in the check boxes.

NONE
GET_OD

ALL

050319E.EPS

Figure Keyword Selection for BitString Parameter (Connection Type)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-96
In the case of FmsFeaturesSupported which is one of the VCR parameters, separate
keywords are selected for the client part and server part. Display the slide menu for the
client part or server part. By placing a check mark in the check boxes in the slide menu,
more than one keyword can be selected. Note that a keyword that is not described in the
capabilities file cannot be selected.

Client
NONE
GET_OD

ALL_FMS

Server
NONE
GET_OD

ALL_FMS

050320E.EPS

Figure Keyword Selection for FmsFeaturesSupported

When [NONE] is checked, the check marks in all check boxes other than [NONE] will be
removed. If [ALL_FMS] is checked, all selectable check boxes other than [NONE] will be
checked off.

● OctetString Parameter (VCR Parameter: FasArTypeAndRole)


OctetString parameters are comprised of multiple bit groups and each bit group has a
specific meaning. The keywords for these parameters are determined by the bit groups.
In the case of FasArTypeAndRole, an OctetString VCR parameter, only the keywords for
FAS Role, which is one of the bit groups comprising the parameter, are displayed in the
keyword list. From this keyword list, select one FAS Role keyword. By doing so, the key-
words for bit groups other than FAS Role are automatically determined.

NOTCONFIG
PEERINITIATOR
PEERRESPONDER
CLIENT
SERVER
SOURCE
SINK
PUBLISHER
SUBSCRIBER

050321E.EPS

Figure Keyword Selection for FasArTypeAndRole

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-97
● OctetString Parameter (VCR Parameter: FasDIISDAP)
OctetString parameters are comprised of multiple bit groups and each bit group has a
specific meaning. In the keyword list, the keywords corresponding to different categories
are separated by delimiters.
In the case of FasDIISDAP, one of OctetString VCR parameters, select one keyword from
the corresponding slide menus by category.

LAS Scheduled
SCHEDULED
NONSCHEDULED

DLCEP Data Delivery Feaures


UNORDERD
ORDERD

DLPDU Authentication
ORDINARY

Priority
URGENT
NORMAL
TIMEAVAILABLE
050322E.EPS

Figure Keyword Selection for FasDIISDAP

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-98
● OctetString Parameter (VCR Parameter: FasDIITimelinessClass)
OctetString parameters are comprised of multiple bit groups and each bit group has a
specific meaning. In the keyword list, the keywords corresponding to different categories
are separated by delimiters.
In the case of FasDIITimelinessClass, one of OctetString VCR parameters, select one
keyword from the corresponding slide menus by category.

Publisher DL Timeliness Class


None
PUB_RESIDENCE

Duplicate PDU Detection Supported


DUPLICATION
NONDUPLICATION

Subscriber DL Timeliness Class


SUB_RESIDENCE

None
050323E.EPS

Figure Keyword Selection for FasDIITimelinessClass

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-99

5.3.11 Upload to the Project Database


Block parameter values set for the fieldbus device are uploaded to the project data-
base as necessary.

■ Calling the Upload Dialog Box


The following operations can be used to call up the Upload dialog box.
• Select [Upload] from the [Project] menu in the project manager
• Or, startup directly from an external application

Doing this displays the Upload dialog box.

Upload

Device in project
- STR3
- 2 Temperature_sensor_2 Temperature_sensor_2
3 Temperature_sensor_2(RESOURCE) New_valve_positioner_3
3 AI_400(AI) New_valve_positioner_4
- 2 New_valve_positioner_3 TI1001
3 New_valve_positioner_3(RESOURCE) VP1001
3 PID_400(PID)
3 (AO)
- 2 New_valve_positioner_4
3 New_valve_positioner_4(RESOURCE)
3 (PID)
3 AO_466(AO)
- 2 TI1001
3 TI1001(RESOURCE)
3 TI1001-AI(AI)
- 2 VP1001
3 VP1001(RESOURCE)
3 VP1001-PID(PID)
3 VP1001-AO(AO)

Execute Cancel

050324E.EPS

Figure Upload Dialog Box

The devices in project and the blocks are displayed in the Upload dialog box. The physical
device tag name is displayed in the device. Also, for the block, the block tag name and block
type are displayed. These tag names cannot be changed. The blocks that can be displayed
are resource blocks, function blocks and transducer blocks.
Further, the host interface device (ACF11) is not displayed, and therefore is not available for
upload.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-100
■ Executing an Upload
The following procedure is used to execute upload.
1. Select a project, device, or block.
Multiple devices and blocks can be selected as the upload target. Also, all of the
devices in project is uploaded when a project is selected.
2. Click the [Execute] button with the upload target selected.
Upload is executed. A message dialog box is displayed while upload is being ex-
ecuted.

PJT1

Project Name : PJT1

1998/12/14 15:11:57 Start uploading to YW1001.


1998/12/14 15:12:09 Start uploading block parameter toYW1001.
1998/12/14 15:12:09 Start uploading block parameter toYW1001 [View[2]].
1998/12/14 15:12:12 Start uploading block parameter toYW1001 [View[4]].
1998/12/14 15:12:16 Start uploading block parameter toYW1001 [TagDesc].
1998/12/14 15:12:18 Start uploading block parameter toYW1001 [AlarmSum].
1998/12/14 15:12:23 Start uploading block parameter toYI1001.
1998/12/14 15:12:23 Start uploading block parameter toYI1001 [View[2]].
1998/12/14 15:12:25 Start uploading block parameter toYI1001 [View[4]].
1998/12/14 15:12:29 Start uploading block parameter toYI1001 [TagDesc].
1998/12/14 15:12:31 Start uploading block parameter toYI1001 [AlarmSum].
1998/12/14 15:12:38 End uploading to YW1001.

Stop Close Save Detail

Progress bar 050325E.EPS

Figure Message Dialog Box

A message indicating the status of the upload execution is displayed in the message
dialog box. While upload is executing, all messages are stored in a text file
(upload.log) under the Log directory. Also, how the execution process is proceeding
can be seen in the progress bar.
A list of the messages displayed in the message dialog box is given below.

Upload of the **device ** block will start.


Upload of the **device ** block has been completed.

050326E.EPS
Note: In the area indicated by **, the physical device tag name or block name is displayed.

Figure List of Messages Displayed in the Message Dialog Box

3. To terminate the upload execution, click the [Stop] button. A dialog box to confirm
termination is displayed.
Clicking the [Stop] button in this dialog box terminates the upload. If [Cancel] is clicked,
the upload is not terminated and the dialog box closes.
Also, upload continues while the confirmation dialog box is being displayed.

TIP
During upload execution, whenever the upload for each block completes normally, the data is written to
the database by block. If an error occurs while upload is being executed or if the [Stop] button is clicked,
the block data being processed at the time the upload terminated is not written to the database.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-101
■ Saving Messages
After upload is completed, all messages generated during the upload can be saved to a text
file by specifying the directory name and file name.
The following procedure is used to save messages.
1. Click the [Save] button in the Upload dialog box.
The dialog box for specifying the file in which the messages are to be saved is dis-
played.
2. Specify the directory name and file name, and save them.
Further, in the default setting, the Log directory is specified as the storage location.

■ Saving the History


An upload log is saved when upload is executed.

SEE ALSO
For more information about the upload history, see the following:
“■ Downloading to the Fieldbus Devices” in 5.5.5, “Executing Project Startup”

■ Executing an Upload from the Individual Devices Using the Project


Manager
Instead of using the Upload dialog box, upload can be performed from the individual de-
vices using the project manager. Use the following procedure.
1. Select the device for which upload is to be executed from the “Devices in project” list
box within the project manager.
2. Select [Upload] from the [Device] menu in the project manager. Upload is executed.
While upload is being executed, a message display dialog box is displayed.
3. To terminate the upload, click the [Stop] button. The upload is discontinued after the
communication processing during execution is completed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-102

5.3.12 Updating Capability File and DD File


When Device Revision, DD (Device Description) Revision and CF (Capability File)
Revision are upgraded, the registered information is updated. Thus the correspond-
ing fieldbus physical device is also upgraded. The functionality of a physical device
can be enhanced by upgrading its capability file and DD file without changing the
existing applications.
By upgrading the capability file and DD file, the following device information is
updated.
• Device Revision (DEV_REV) and Option Folder.
• CF revision and DD Revision

■ Upgrade Device and Update Option Folder


When upgrading a device, the device needs to be re-registered. The function blocks may
need to be modified accordingly on FB editor so that Generate needs to be executed.
Option folder is also updated accordingly.
The procedure for upgrading the device to a newer revision (DEV_REV) for an existing
device, including the files in Option folder, is as follows.
1. Copy the capability files and DD files for the newer revision devices to a folder
(FF_PRJ\DEVPOOL is suggested) under the Fieldbus Engineering Tool installed
folder.
2. On Project Manager window of Fieldbus Engineering Tool, use “Import” in Device
menu to import the capability files and DD files to Device Pool.

SEE ALSO
For more information about importing capability files and DD files, see the following:
5.2.6, “Importing Capabilities Files and DD Files to System Database”

3. Choose a device on Project Manager window of Fieldbus Engineering Tool. Cannot


choose multiple devices.
4. Choose [Renew CF/DD] on [Device] menu, a dialog box displays with installed capa-
bility files. Click “Cancel” button may close this dialog box.
5. Select a capability file, then click [OK] button, the updating starts with a message box
indicating the updating process.
6. If the function blocks in the new version device are different from the previous device, it
is necessary to edit the function blocks on FB Editor, and to delete the invalid blocks.
7. Run “Generate” on FB Editor.

IMPORTANT
Even the device revision is upgraded, the existing function block tag names, function block
parameters and other information are intact. It may be required to modify the FBAP (func-
tion block configurations) on FB Editor accordingly, then run “Generate” on FB Editor.
After running “Generate,” it is necessary to download the new information to all fieldbus
devices including ACF11 module since the communication parameters (and segment
common parameters) are changed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-103
■ Upgrade Capability File and Device Description File
▼ Renew CF/DD
When upgrading a device's capability file and DD (Device Description) file, the CF Revision
and DD Revision are updated accordingly. Generally, there is no need to run “Generate” on
FB Editor after upgrading the capability file and DD file, though “Generate” may be required
under certain circumstances.
The procedure for upgrading the capability file and DD (Device Description) file for a device
registered is as follows.

1. Copy the capability files and DD files for the newer revision devices to a folder
(FF_PRJ\DEVPOOL) under the Fieldbus Engineering Tool installed folder.
2. On Project Manager window of Fieldbus Engineering Tool, use “Import” in Device
menu to import the capability files and DD files to Device Pool.

SEE ALSO
For more information about importing capability files and DD files, see the following:
5.2.6, “Importing Capabilities Files and DD Files to System Database”

3. Choose a device on Project Manager window of Fieldbus Engineering Tool. Cannot


choose multiple devices.
4. Choose [Renew CF/DD] on [Device] menu, a dialog box displays with installed capa-
bility files. Click “Cancel” button may close this dialog box.
5. Select a capability file, then click [OK] button, the updating starts with a message box
indicating the updating process.

■ Invalid Function Blocks


After upgrading the devices, capability files and DD files, the function blocks in the newer
version devices may be different. If a function block is removed from the device after up-
grading, the function block used in FBAP becomes invalid since its relationship to the
physical device is severed. The function block whose relationship to the physical device is
severed is referred to as Invalid Function Block.
When upgrading a device, the function blocks in the device may change but the corre-
sponding function blocks in FBAP not, so that the function blocks in FBAP may become
invalid.
If the invalid function block exists in FBAP, error occurs when run “Generate” on FB Editor.
So that it is necessary to delete the invalid function block from FBAP on FB Editor, or
change the function block into a proper one.

IMPORTANT
If the invalid blocks are involved in the internal parameter connections, it is necessary to
resolve the invalid block problem and the reconstruct the internal parameter connections.
Modifications may be required accordingly.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-104

5.3.13 Replace Fieldbus Device, Update Capability File and DD


File
After replacing a device, the information for the registered devices needs to be
updated. This can be performed.
When replace a device, if the new device has the same revision number with the old
one, the procedure for updating the capability file and DD file is different from that
has different revision number.

■ Replace a Device with Same Revision Number


1. Choose a device on Project Manager window of Fieldbus Engineering Tool. Then click
[Upload] in [Device] menu. If the communication of fieldbus devices is established, the
fieldbus device parameters can be uploaded.
2. Replace the physical device. The new device should have the same device tag, node
address and device class of the one to be replaced.
3. Choose the device on Project Manager window of Fieldbus Engineering Tool. Then
click [Download] in [Device] menu to download the parameters to the new device.

■ Replace a Device with Different Revision Number


1. Choose a device on Project Manager window of Fieldbus Engineering Tool. Then click
[Upload] in [Device] menu. If the communication of fieldbus devices is established, the
fieldbus device parameters can be uploaded.
2. Copy the capability file and DD file of the new device to a folder (FF_PRJ\DEVPOOL)
under the Fieldbus Engineering Tool installed folder.
3. On Project Manager window of Fieldbus Engineering Tool, use "Import" in Device
menu to import the capability file and DD file to Device Pool.

SEE ALSO
For more information about importing capability files and DD files, see the following:
5.2.6, “Importing Capabilities Files and DD Files to System Database”

4. Choose [Renew CF/DD] on [Device] menu to upgrade the device.


5. If the function blocks in the new version device are different from the previous device,
it is necessary to edit the function blocks on FB Editor, and to delete the invalid blocks.
6. Run “Generate” on FB Editor.
7. Replace the physical device. The new device should have the same device tag, node
address and device class of the one to be replaced.
8. Choose the device on Project Manager window of Fieldbus Engineering Tool. Select
[Download] in [Project] menu on Project Manager window of Fieldbus Engineering
Tool. Download dialog box displays.
9. On the Download dialog box, click [Execute] button to start download the information
to all the fieldbus devices including the newly replaced device.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-105

5.4 Settings for FBAP


The function blocks for the registered devices are combined and settings for the
FBAP set. This section explains how to perform the setting for the FBAP.

■ Precautions on the Number of Registered Devices and


When Configuring the FBAP
The specifications of the fieldbus communication module (ACF11), which is the subject of
engineering, indicate the number of field devices that can be registered with the Fieldbus
Engineering Tool; the number of registered connection terminals in the FBAP configuration;
and the communication count between the blocks, as follows:
• Number of registered devices
Maximum number: 32 (including the ACF11)
A maximum of 32 devices, including the ACF11, can be registered in one segment
(one project)
• Number of VCR (Virtual Communication Relationship)
Maximum number: 94
This is the maximum number of VCR that can be set in the ACF11.
• Number of connection terminals
Maximum number: 64
The ACF11 can use 32 each of connection terminals for inputs and for outputs.
• Communication count
Maximum count: 32
This is the maximum count of the communication schedules (sequences) for the LAS
(Link Active Scheduler) that the ACF11 contains.

In order to complete generation normally, always create the system to stay within the range
of registered quantities indicated above. If the configuration does not fall within the range of
registered quantities above, the following error messages will be displayed when the
generation function is executed.

When the number of configured VCRs exceeds the allowed maximum number
• Error while generating common objects.
• Error on generating a VCR object for Device <DeviceName>, FB <FbName>, Param-
eter <ParameterName>.
• Warning! There are not enough VCR definitions to generate all needed VCRs for the
Host Interface Devices!

When the number of communication schedules exceeds the allowed maximum number
• Error on generating a LAS Schedule object for Device <DeviceName>, FB
<FbName>, Parameter <ParameterName>.

SEE ALSO
For more information about the error messages, see the following:
“■ Generation” in 5.6.9, “FB Editor Error Messages”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-106

5.4.1 Procedure for Setting the FBAP


The procedure for setting the FBAP is explained below.

■ What is Setting the FBAP?


FBAP is a series of control loops created by combining the function blocks of multiple
devices.
By combining the function blocks of the registered devices, the FBAP used by the project is
set.
Primarily the following operations are performed when setting the FBAP.
• Creating the FBAP block diagram
A diagram indicating the configuration of the function blocks used in the FBAP (block
diagram) is created. This is called the FBAP block diagram.
• Setting function block parameters
The parameters for each function block are set.
• Generating the FBAP configuration
Generation is performed based on the block diagram and parameters and the VCR
values and link object parameter values are generated.

Performing these operations allows the setting data related to the FBAP to be downloaded
to the device.

TIP
The Fieldbus Engineering Tool can handle the following function resources of a device.
However, the function block is the only one of these resources that can be placed in the FBAP block
diagram.
• Function block
• Resource block
• Transducer block
• Link object
• Alert object

SEE ALSO
For details on the various function resources, see “Function Block Application Process Part 1, 2” (FF-890/
891.)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-107
■ Flow of Setting for the FBAP
▼ Flow of the Setting for the FBAP
The following shows the flow of setting for the FBAP.

Start setting for the FBAP

Calling FB editor

Creating or selecting
a FBAP block diagram

Placing function blocks


in the FBAP block diagram

Connecting the function blocks

Other operations related to


creating the FBAP block diagram

Setting block parameters

Generation of the FBAP configuration

Creating the FBAP schedule

Legend
Operations that
are always performed
Output host file set Operations performed
as necessary

Start and end of operation

Setting for the FBAP complete Group of operations


performed repeatedly

050401E.EPS

Figure Flow of Setting for the FBAP

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-108
■ Summary of Each Step

● Calling FB Editor
Call the FB editor to created the FBAP.

● Creating New or Select a FBAP Block Diagram


Create a new FBAP block diagram. To change an existing FBAP block diagram, open the
FBAP block diagram to be changed.

● Placing Function Blocks in the FBAP Block Diagram


Place the function blocks to be used in the FBAP in the FBAP block diagram.

● Connecting the Function Blocks


Connect the arranged function blocks.

● Other Operations Related to Creating the FBAP Block Diagram


Change the grid or move objects as necessary.

● Setting Block Parameters


Set the parameters included in the function block, resource block and transducer block. The
parameters of these blocks are set in the Parameter dialog.

● Generation of the FBAP Configuration


Execute generation of the FBAP configuration, and generate the VCR value and link object
parameter values.
The schedule automatic creation function starts automatically and the execution timing
chart, which is the basis for creating the schedule, is generated when generation is com-
pleted.

● Creating a FBAP Schedule


Create an execution schedule for function block processing and for communication based
on the execution timing chart generated upon completion of generation.
The schedule is created in the Schedule dialog box.

● Output Host File Set


Output the host file set used by the application that operates in the supervisory system
(host application).

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-109

5.4.2 Calling FB Editor


Calling the FB editor to create the FBAP block diagram.

■ Calling FB Editor
The following procedure is used to call the FB editor.
1. Open a project. This step is unnecessary if the project is already opened.
2. Select [FB editor (D)] from the [Tool (T)] menu in the project manager.
The FB editor is displayed.
a
p
p
a
FBAP1.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 250 msec BNU Communication Stale Count Limit: 2

050402E.EPS

Figure FB Editor

■ Exiting the FB Editor


After the FBAP has been created, exit the FB editor.
Select [Exit (X)] from the [FBAP] menu in the FB editor.
The FB editor closes. If there was an FBAP configuration open, it is automatically saved.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-110

5.4.3 Create a New or Open a FBAP Block Diagram


If the FBAP block diagram has not been created, create a new FBAP block diagram.
To change an existing FBAP block diagram, open the FBAP block diagram to be
changed.

■ Creating a New FBAP Block Diagram


The following procedure is used to create an FBAP block diagram.
1. Select [New (N) ...] from the [FBAP] menu in the FB editor. Or, click the [New] icon in
the toolbar.
The new FBAP dialog box is displayed.

New FBAP

FBAP Name:

OK Cancel

050403E.EPS

Figure Example of New FBAP Dialog Box

2. Enter the name of the new FBAP to be created in the “FBAP name” box.
3. Click the [OK] button.
The new FBAP dialog box closes.
The drawing area is initialized and the name of the new FBAP block diagram created
is displayed in the FB editor title bar.
Clicking the [Cancel] button closes the dialog box and the new FBAP block diagram is
not created.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-111
■ Opening an Existing FBAP Block Diagram
The following procedure is used to open an existing FBAP block diagram to make changes.
1. Select [Open (O) ...] from the [FBAP] menu in the FB editor. Or, click the [Open] icon in
the toolbar.
The open FBAP dialog box is displayed.

Open FBAP
_
FBAPs
FBAP1

Open
_ _
Cancel

050404E.EPS

Figure Open FBAP Dialog Box

2. Select the new FBAP block diagram to be changed from the “FBAP” list box.
3. Click the [Open] button.
The dialog box for opening an FBAP is displayed.
The name of the newly selected FBAP block diagram is displayed in the FB editor title
bar.
Clicking the [Cancel] button closes the open FBAP dialog box and the FBAP block
diagram will not be opened.

TIP
• When creating a new FBAP block diagram drawing or opening a FBAP block diagram drawing while
another FBAP block diagram is open on the FB editor, the opened FBAP block diagram drawing will
be automatically closed. If there is un-saved modification in the FBAP block diagram drawing to be
closed, a dialog box will be displayed prompt for confirmation.
• The FBAP block diagram drawing can be printed out. Select [Print (P) ...] from the [FBAP] menu on
the FB editor while the FBAP block diagram drawing is open.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-112
■ Deleting the FBAP Block Diagram
An existing FBAP block diagram can be deleted when it is no longer necessary. The func-
tion blocks that were used in the deleted FBAP block diagram are released and can be
used in another FBAP block diagram.
The following procedure is used to delete a FBAP block diagram.
1. Open the FBAP block diagram to be deleted.
2. Select [Remove (R)] from the [FBAP] menu.
The FB editor confirmation dialog box is displayed.

FB Editor

Do you really want to remove this FBAP?

Yes No

050405E.EPS

Figure Example of FB Editor Dialog Box

3. Click the [Yes] button.


The FB editor confirmation dialog box closes and the FBAP block diagram is deleted.
Clicking the [No] button closes the dialog box without deleting the FBAP block dia-
gram.

■ Closing the FBAP Block Diagram


Close the FBAP block diagram when setting for the FBAP block diagram has been completed.
To close the FBAP block diagram, select [Close (C)] from the [FBAP] menu in the FB editor.

■ Saving the FBAP Block Diagram


The FBAP block diagram can be saved during setting, so that the contents of the settings
will not be lost due to an operation error. To save an FBAP block diagram during setting,
select [Save (S)] from the [FBAP] menu in the FB editor.

TIP
If an attempt is made to close the FBAP block diagram when the FBAP block diagram has not been saved
during setting, a confirmation dialog box asking whether to save the FBAP block diagram is displayed.
• Clicking the [Yes] button closes the FBAP block diagram after it has been saved.
• Clicking the [No] button closes the FBAP block diagram without being saved.
• Clicking the [Cancel] button returns to the FB editor.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-113

5.4.4 Placement of Function Blocks in the FBAP Block Diagram


The function blocks for the device registered in the project database are stored in
the area called the “FB pool.” The function blocks used in the FBAP block diagram
are selected from the function blocks registered in this FB pool and placed in the
FBAP block diagram. Function blocks already being used cannot be placed in an-
other FBAP block diagram.

■ Placing the Function Blocks in the FBAP Block Diagram


1. Select [Insert function block (I) ...] from the [Edit (E)] menu in the FB editor. Or, click
the [Insert function block ] icon in the toolbar.
The FB Pool dialog box is displayed. The physical device tag name of the device is
shown in the “Devices in project” list box and the function block default block tag name
is shown in the “Available function blocks” list box.

TIP
The block ID is displayed in a pair of parentheses next to the block tag name.

FB Pool

Devices in Project Available Function Blocks

YVP_2 AO_800 (AO-01)


EJA_8 DI_900 (DI-01)
DI_1000 (DI-02)
Temperature_sensor_4
PID_1100 (PID-01)
YEWFLO_5

OK Cancel

050406E.EPS

Figure FB Pool Dialog Box

2. Select the device to be used from the “Devices in project” list box.
The block tag names of the function blocks included in the selected device is listed in
the “Available function blocks” list box. Also, the word “(used)” is shown in the function
blocks that have already been placed in another FBAP block diagram.
3. Select the function block to be used from the “Available function blocks” list box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-114
4. Click the [OK] button.
The FB Pool dialog box closes and the mouse cursor changes to a cross.
Click the [Cancel] button and the FB Pool dialog box closes.
5. Click anywhere in the drawing area.
a
p
p
a
FBAP1.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 250 msec BNU Communication Stale Count Limit: 2

Drawing area Place the cross cursor


at any position and click
050407E.EPS

Figure Deciding the Function Block Position

The Function Block Name dialog box is displayed.

Function Block Name

Block Tag Name: DEFAULT TAG

OK Cancel

050408E.EPS

Figure Function Block Name Dialog Box

TIP
The block ID in a pair of parentheses is not displayed next to the block tag name in the Function Block Tag
Name dialog box.

The default block tag name varies depending on whether or not the block tag name
has been changed in the Parameter dialog box called from the FBAP editor. The
default block tag names are as follows.
• When the block tag name has not been changed
A character string in which the function block type name and OD index are connected
by an underscore (<Type Name>_<ODIndex>).
• When the block tag name has been changed
The block tag name that was last set in the Parameter dialog box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-115
6. To change the default block tag name, enter the block tag name in the “block tag
name” box. The block tag name can be specified with up to 16 alphanumeric charac-
ters.

IMPORTANT
In the specifications for the fieldbus, the fieldbus device block tag name can be a maximum
of 32 characters but in the CENTUM VP/CS 3000/CS 1000 or STARDOM the maximum is
16 characters (alphanumeric characters, excluding block ID). If connecting to the CENTUM
VP/CS 3000/CS 1000 or STARDOM, make sure the tag name does not exceed 16 charac-
ters when setting the tag name with the Fieldbus Engineering Tool. If more than 16 charac-
ters are used, an error occurs when open on CENTUM VP/CS 3000/CS 1000 system
builders.

7. Click the [OK] button.


The function block is registered and is placed in the drawing area at the position of the
cross cursor.
At the top of the placed function block, the block tag name is displayed and the physi-
cal device tag name is shown at the bottom.
Click the [Cancel] button and the function block is not registered.

Input terminal
Display block tag name
input parameter
a
p
p
a
FBAP1.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 1000 msec BNU Communication Stale Count Limit: 5

AO_800 (AO_01)

CasIn BkcalOut
RcasIn
AO Out
RcasOut

YVP_2
Output terminal
Output parameter

Drawing that Physical device tag name of The function block


shows the block type the device where this function is placed
block resides
050409E.EPS

Figure Placement of Function Blocks

8. Repeat steps 1 to 7 as required.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-116
TIP
• When the block tag name of the function block is changed, the tag name displayed in the FB editor
changes. But the block tag name shown in the FB pool does not change and remains the default
name.
• The transducer block cannot be placed in the drawing area.
Connect the transducer block to a function block when using a transducer block in the FBAP.
The transducer block and function block can be connected by setting the channel number for the
transducer block as the “Channel” parameter for the AI or AO function block in the Parameter dialog
box.
• It is necessary to select the function block when setting or changing a placed function block or
deleting the function block.
Click the function block to select it.
When selecting multiple function blocks at the same time, drag the mouse, and enclose the function
blocks to be selected, using the displayed dotted line.

SEE ALSO
For more information about changing the settings of placed function blocks and setting the channel
parameter, see the following:
5.4.7, “Setting Block Parameters”

■ Changing the Block Tag Name for Function Blocks


The following procedure is used to change the block tag name of the function block.
1. Click the function block.
A small square is shown at each corner of the function block.
2. Select [Change block tag name (T) ...] from the [Edit (E)] menu in the FB editor. Or,
press the [Enter] key.
The Function Block Name dialog box appears.
3. Enter the block tag name in the “block tag name” box.
4. Click the [OK] button.
The Function Block Name dialog box closes.
Clicking the [Cancel] button closes the Function Block Name dialog box without
changing the block tag name of the function block.

TIP
The Function Block Name dialog box will also open by double-clicking the function block whose block tag
name is to be changed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-117
■ Deleting Function Block
The function block can be deleted when it is no longer necessary.
The following procedure is used to delete a function block.
1. Click the function block to be deleted in the drawing area.
2. Select [Remove (R)] from the [Edit (E)] menu in the FB editor. Or, press the [Delete]
key.
The selected function block will disappear from the drawing area.

■ Invalid Function Block in FBAP


When upgrading a physical device's capability file and DD file, the function blocks in the
physical device may be changed. If a function block in the physical device is deleted, its
virtual function block in FBAP becomes invalid function block. An invalid function block in
FBAP is shown in the figure below.
a
p
p
a
FBAP1.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 1000 msec BNU Communication Stale Count Limit: 5

Invalid Block TO_1000-2 (TO_02)

AI Out In

ACF11-14

050410E.EPS

Figure An Invalid Function Block in FBAP

SEE ALSO
For more information about invalid function blocks, see the following:
5.3.12, “Updating Capability File and DD File”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-118

5.4.5 Connecting Function Blocks


The function blocks placed in the drawing area are linked by connections.

IMPORTANT
The function which connects the remote terminals of the fieldbus function block (RCAS_IN,
RCAS_OUT, ROUT_IN, ROUT_OUT, RCAS_IN_D and RCAS_OUT_D) and the FCS
function block is currently not supported. Do not use the remote terminals.

■ Connecting Function Blocks


Connect the function blocks displayed in the drawing area.
The following procedure is used to connect the function blocks.
1. Select [Insert connection (C) ...] from the [Edit (E)] menu in the FB editor. Or, click the
[Insert connection] icon in the toolbar.
The mouse cursor changes to a cross.
2. Press the left mouse button on top of the I/O terminal for the connection origin function
block.
3. Drag the cross cursor to the top of the I/O terminal for the connection destination
function block with the left mouse button held down.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-119
4. Release the left mouse button.
A connecting line (connection) will be inserted from the position where the left mouse
button was pressed to the position where it was released. Only a straight line connect-
ing two points can be drawn for the connection. If the function blocks cannot be con-
nected with a single straight line, tie together multiple connections to connect the
function blocks.
a
p
p
a
FBAP2.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 1000 msec BNU Communication Stale Count Limit: 5

AO_466 (AO_01)
TO_1000 (TO_01)
CasIn BkcalOut
RcasIn
AO Out
RcasOut
In

ACF11-14
New_valve_positioner_2

Click here Drag to here and release


050411E.EPS

Figure Connecting Function Blocks

5. Repeat steps 1 to 4 as required.


6. Click the [Pointer] icon in the toolbar or select [Pointer] from the [Edit (E)] menu.
The mouse cursor returns to the arrow pointer.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-120
■ Registering Readback Connection Terminals
When registering the readback connection terminals, the number that following the block ID
should be the same as the number of the block ID in the Out connection terminal.

Choose the same number from FB pool.

a
p
p
a
FBAP2.lay - FB Editor
FBAP Edit Options View Help

Control Cycle: 1000 msec BNU Communication Stale Count Limit: 5

AO_900-02 (AO_01)
TI_1064-01 (TI_01) TO_1000-01 (TO_01)
CasIn BkcalOut
Out RcasIn
AO Out
RcasOut
In

ACF11-14 ACF11-14
New_valve_positioner_2

050432E.EPS

Figure Registering Readback Connection Terminals

IMPORTANT
It is necessary to register the readback connection terminal for STARDOM since the con-
troller builder cannot configure the connection to the fieldbus function blocks.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-121
■ Assigning Internal Parameters to Connection Terminals
For connecting internal parameters to host interface devices, the parameters need to be
assigned to the connection terminals.
1. On FB Editor window, choose [Contained Parameter Connection] from [Edit] menu.
The dialog box for assigning the parameters to connection terminals is shown as
follows.

Contained Parameter Connection

Num Of Mansetting 5

No Block Tag Name Parameter Label


44 FI1001
45 AI_600-02 PV
46 ST_REV
47 STRATEGY

48 AO_900-03 PV FI1001

Print File OK Cancel

050433E.EPS

Figure Dialog Box for Assigning Internal Parameters

2. Manually input the number of channels for parameters.


The specified number of continuous channels are reserved for the input terminals. The
detailed connection data can also be manually set for these input terminals. If the
number of channels is set to zero, the parameters cannot be manually set.
The connection data consist of Block Tag Name, Parameter and Label.
3. Choose the block tag name in the project by selecting from the block tag name combo
box.

TIP
The block tag name cannot be selected if a block is not defined with a tag name.

4. Choose a parameter name by selecting from the parameter combo box.

TIP
The parameters in the parameter combo box are the parameters of the block selected from the block tag
name combo box.
If no block is selected, the parameters cannot be selected either.

5. Enter label name.


6. Click [OK].
The entered data are saved and the dialog box for assigning the parameters closes.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-122
After designating the number of channels on the dialog box for assigning parameters,
(manual) is displayed next to each assigned function block on the [Available Function
Blocks] list box in [FB Pool] dialog box. The number of connection terminals includes both
the TI and TO blocks and they all displayed with (manual).

FB Pool

Project Device Available Function Blocks

ACF11-14 TO_1084 (TO_43)


EJA_02 TO_1086 (TO_44) (manual)
TO_1088 (TO_45) (manual)
YVP-03
TO_1090 (TO_46) (manual)
TO_1092 (TO_47) (manual)
TO_1094 (TO_48) (manual)
TI_1096 (TI_01)
TI_1098 (TI_02)
TI_1100 (TI_03)
TI_1102 (TI_04)

OK Cancel

050434E.EPS

Figure Dialog Box Displaying the Number of Manually Assigned Parameters

TIP
The connection terminals displayed together with (manual) cannot be selected. It has the same meaning
as (used).

When printing the defined contents on the contained parameter connection dialog box, it is
necessary to export the contents to a text file (CSV file), and then use a general-purpose
text editor to print out the text file.
1. Click [Print File] button on the contained parameter connection dialog box, a dialog
box for saving the file with a designated name displays.
2. Designate a name for the file on this dialog box.
The contents are saved into the text file (CSV file) and the file is located in the folder
LPR under the root folder of the project. By default, the file name is IOPARAM.CSV.
Both the folder name and the file name can be modified.
Save the file after the file name and folder name are confirmed.
3. Use a general-purpose text editor to open the text file.
4. Run print on the editor to print out the text file.
The print layout of the file is as follows.

Num of Mansetting
No Block Tag Name Parameter Label
1 OFC_25000-11 FLOW_OUT TO_1000-2
2 AO_5000-11 RCAS_IN TI_1100-2
...
48 TB_200-7 PRIMARY_VALUE_TYPE
050435E.EPS

Figure Print Layout

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-123

5.4.6 Other Operations Related to Creating the FBAP Block


Diagram
The other functions that can be performed in the FB editor are explained below. The
other functions include changing the grid and moving an object.

■ Changing Grid Setting


▼ Grid Settings
The type and spacing of the grid in the drawing area can be set.
The following procedure is used to set the grid.
1. Select [Grid (G) ...] from the [Option (O)] menu in the FB editor. The Grid Settings
dialog box is displayed.

Grid Settings

Display Grid OK

Cancel
Setting
Default
Dots
Lines

Spacing: 15

050412E.EPS

Figure Grid Settings Dialog Box

2. Clicking the “Display grid” check box switches whether to display the grid or not.
3. Select the grid type using the “Setting” radio button. Either points or lines can be
selected.
4. Enter the grid spacing in the “Spacing” box.
5. Click the [OK] button.
The Grid Settings dialog box closes and the changes in the grid settings will be re-
flected in the drawing area.
Clicking the [Cancel] button closes the Grid Settings dialog box without changing the
grid settings.

TIP
• The object display size changes when the grid spacing is changed. The wider the spacing, the larger
the display and the narrower the spacing, the smaller the display.
• The grid settings can be returned to the default settings by clicking the [Default] button in the Grid
Settings dialog box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-124
■ Moving an Object
The position of the object in the drawing area can be changed.
The following procedure is used to move the object.
1. Press the left mouse button on top of the object to be moved.
2. Drag the mouse cursor, with the left mouse button held down, to where the object will
be moved.
3. Release the left mouse button.
The object will move to the place where the left mouse button was released.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-125

5.4.7 Setting Block Parameters


Parameters included in the function block, resource block, and transducer block are
set in the Parameter dialog box.

■ Setting Block Parameters


▼ All Parameters
The following procedure is used to set the function block, resource block, and transducer
block parameters.
1. When setting parameters for a function block, click on the target function block in the
drawing area of the FB editor.
2. Select [All Parameters (A)] from the [Edit (E)] menu in the FB editor. The Parameter
dialog box appears.
When a function block has been selected in the drawing area of the FB editor, the
parameters for the selected function block are expanded on the screen.

Parameter Dialog

Devices in Project List


- EXAMPLE Parameter Element Value Type Range
+ EJA100A-2 PeriodOfExecution 32000 Unsigned3
Valve_Positioner-3 NextBlockToExecute 0 Unsigned1
Valve_Positioner-3(RES StRev Unsigned1
AO_800(AO) TagDesc 0x20202020202020202020 OctetStrin
DI_900(DI) Strategy 0 Unsigned1
(DI) AlertKey 1 Unsigned8 0~255
PID_1100(PID) ModeBlk TARGET O/S BitString
- Link object ModeBlk ACTUAL O/S BitString
Link object ModeBlk PERMITTED Cas+Auto+Man+O/S BitString
Link object ModeBlk NORMAL Auto BitString
Link object PvScale EU_100 100 FloatingPo
Link object PvScale EU_0 0 FloatingPo
Link object PvScale UNITS_INDEX % Unsigned1
Link object PvScale DECIMAL 0 Integer8
Link object OutScale EU_100 100 FloatingPo
Link object OutScale EU_0 0 FloatingPo
Link object OutScale UNITS_INDEX % Unsigned1
Link object OutScale DECIMAL 0 Integer8
GrantDeny GRANT BitString

OK Cancel Print File

050413E.EPS

Figure Parameter Dialog Box

“Project”, “Device”, “Block or link object” and “Element” are expanded as a hierarchical
structure in the “Devices in Project” list.
Table Contents Displayed in the “Devices in Project” List
Display target Window display Remarks
Project Project name
Device Physical device tag name
Block tag name.
Block
Block type
Link object “Link object”
This is displayed when the link object is
Element Element name (number)
comprised of multiple elements.
050414E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-126
3. To change the block tag name, click on the block tag name in the “Devices in Project”
list. This enables editing of the block tag name being displayed. Enter the new block
tag name.

TIP
When a block tag name has been deleted, only the block type will be displayed in the “Devices in Project”
list. Note that block tag names cannot be deleted for function blocks that are being used in the FBAP
configuration.

4. Select the block or link object to be edited in the “Devices in Project” list.
A list of the parameters and elements that can be edited will be displayed in the list
view on the right side of the screen.
5. To see the description of a parameter or element, click on the applicable parameter or
element in list view with the right mouse button. From the pop-up menu that appears,
select “Parameter description...”
A description dialog box appears.

Description

Name
Unit: % | (Space) | -> OUT(Engineering Unit)

This parameter describes the state of the block mode.

OK

050415E.EPS

Figure Description Dialog Box

The parameter name or element name, engineering unit and description (English) will
be displayed in the description dialog box.
If there is no DD file, the description dialog box will not be displayed.
6. Enter the parameter value in the “Value” box using one of the following operations.
• Enter directly in the input area using the keyboard.
• Select a keyword as the value to be set from the keyword list which is displayed by
clicking on the arrow button besides the input area.
7. Click the “OK” button.
The Parameter dialog box closes and the setting is saved in the project database.
Clicking on the “Cancel” button closes the Parameter dialog box without changing the
block parameters.

TIP
• Parameters displayed in gray and the parameters (element) prohibited for changing can not be
rewritten.
• Parameters for link objects are automatically created during generation. Do not change these
parameters. Note that the value of StaleCountLimit can be changed.
• Switching between display and hide of the transducer block can be done in the Environment Settings
dialog box.
• The settings of the selected block or link object can be saved as a text file for printing. When clicking
on the “Print file” button in the Parameter dialog box, a dialog box for opening a file appears. In this
dialog box, enter the name of the file to be saved.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-127
The appearance and operation of the Parameter dialog box called from the FB editor
is the same as for the Parameter dialog box called from the network editor. However,
the parameter groups that can be selected will differ.
The following parameter groups can be selected in the Parameter dialog box called
from the FB editor. The default values for these block parameters can be obtained from
the capabilities file.
• Resource Block parameters
• Function Block parameters
• Transducer Block parameters
• Link Object parameters

IMPORTANT
When the network parameters are entered, the range of the values will be checked. This
check is performed based on the range provided as the default (range defined by the
Foundation Fieldbus). The parameter limit values described in the capabilities file are not
used for the check performed when parameters are entered, but used for the consistency
check performed prior to generation.

SEE ALSO
For more information about the screen for and operation of the Parameter dialog box called from the
network editor, see the following:
5.3.10, “Changing Device Parameters”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-128
■ How to Enter Parameters
When directly entering parameter values in the input area, values can be entered using a
keyword in addition to entering a numeric value. The keyword that has been entered is
converted to a numeric value and saved in the database. When the entry is re-displayed, it
is converted back to a keyword.
With those parameters that can be entered via keyword selection, a keyword can be se-
lected from the keyword list that is displayed by clicking on the arrow button besides the
input area.

● Entering a Parameter Directly Using a Numeric Value


Enter the value using the following input format.
• When the parameter data type is Bit String or Octet String
Enter in hexadecimal.
• When the parameter data type is structure (DS: Data Structure)
Enter in hexadecimal, delimit with comma (,).
When element in the structure is Bit String type, that element is entered in the same
way as with Bit String.

Example of entry is given below.


Example: Bit String: IoOpts=0x1010
Data Structure: ModeBlk=0x80,0x80,0x10,0x10
AlarmSum=0x8010,0x8010,0x8010,0x8010

● Entering a Parameter Directly Using a Keyword


When entering a keyword, use the same input format that is used when entering a numeric
value. The elements of keyword are connected using the “+” symbol if the parameter is a
structure including connection type elements, connection type BitString or OctetString.

Example of entry is given below.


Example ModeBlk=AUTO,AUTO,MAN,O/S
ModeBlk=AUTO,AUTO,AUTO+MAN+O/S,O/S
IoOpts=INVERT+FSTATE

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-129
■ Fieldbus Block Mode
As with the FCS function block, there is a MODE parameter in the fieldbus block that
determines the block execution mode. It is necessary to set the fieldbus block mode
(MODE parameter value) correctly when connecting between fieldbus blocks, or between a
fieldbus block and an FCS function block. The fieldbus block is operated by the mode that
was set.

Use the recommended values given in the table below for the fieldbus block mode (Target)
when connecting the FCS function block and fieldbus block in cascade style. If anything
other than this mode is used, the cascade connection with the FCS connection block will
not function normally. If not doing a cascade connection, the recommended fieldbus block
mode is AUTO.
When using a cascade connection and if the fieldbus block mode is anything other than the
established value, then the data status for the fieldbus block becomes Good - Not Invited. In
such a case, the FCS function block mode becomes IMAN.
Table Fieldbus Block Mode
Fieldbus Recommended
Valid mode
Block mode
AI AUTO O/S, MAN, AUTO
DI AUTO O/S, MAN, AUTO
PID CAS (*1) O/S, MAN, AUTO, CAS, RCAS, ROUT
AO CAS (*1) O/S, MAN, AUTO, CAS, RCAS
DO CAS (*1) O/S, MAN, AUTO, CAS, RCAS
RA MAN O/S, (MAN), AUTO (*2)
CS MAN O/S, (MAN), AUTO (*2)
OS AUTO O/S, MAN, AUTO, CAS
SC AUTO O/S, MAN, AUTO
IT MAN O/S, MAN, AUTO
IS MAN O/S, MAN, AUTO
MDI AUTO O/S, MAN, AUTO
MDO AUTO O/S, AUTO
MAI AUTO O/S, MAN, AUTO
MAO AUTO O/S, AUTO
050416E.EPS

*1: AUTO is recommended when not in cascade loop.


*2: The parenthesized mode is optional.

TIP
When the parameter of MODE_BLK is Target, Permitted or Normal, if setting the mode to CAS corre-
sponds to each parameter, it becomes to Auto first then becomes to CAS mode. When releasing from
CAS mode, it returns to Auto mode. Nevertheless, it is possible to set to Auto mode and release from Auto
mode.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-130

IMPORTANT
The fieldbus block mode cannot be changed using the Fieldbus Engineering Tool. However,
by entering a value in the Parameter dialog box and then downloading that value, the initial
value for the mode can be set. The value can be entered as a keyword as in the case of
AUTO, or in hexadecimal bit string format.
An example of mode entry is shown as follows.
Table An Example of Mode Entry
Parameter Element Entry
ModeBlk Target Auto
ModeBlk Actual Auto
ModeBlk Permitted Auto
ModeBlk Normal Auto
050417E.EPS

If the mode contains multiple elements, the elements can be entered as follows.

ModelBlk=Target,Actual,Permitted,Normal

Mode Parameter (DS69)


1. Target (bit string)
2. Actual (bit string)
3. Permitted (bit string)
4. Normal (bit string)
Table Hexadecimal Expression when Setting the Mode

(Multiple Denied) (Multiple Permitted)


Target/Normal Keywords Hex Permitted Keywords Hex
ROUT ROUT,AUTO 0x90 ROUT ROUT 0x80
RCAS ROUT,AUTO 0x50 RCAS RCAS 0x40
CAS CAS,AUTO 0x30 CAS CAS 0x20
AUTO AUTO 0x10 AUTO AUTO 0x10
MAN MAN 0x08 MAN MAN 0x08
LO LO 0x04 LO LO 0x04
IMAN IMAN 0x02 IMAN IMAN 0x02
O/S O/S 0x01 O/S O/S 0x01
050418E.EPS

Example) ModeBlk=0x10,0x10,0x10,0x10
Or
ModeBlk=Auto,Auto,Auto,Auto

Also, this input format is the same as for the capabilities file and object file.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-131

5.4.8 Generation of the FBAP Configuration


It is necessary to generate the FBAP configuration in order to download the FBAP
configuration to the device. The FBAP block diagram is checked when the FBAP
configuration is generated. If there are no errors in the FBAP block diagram, the VCR
value and link object parameter value is generated. A consistency check is automati-
cally performed with respect to the generated values and if no errors are discovered,
the generated values are saved in the project database. Further more, the host file
set generation will be started, the configuration will be output from the project
database to host file set.
Also, if generation is successful, the schedule automatic creation function is started
and the execution timing chart required to create the schedule is generated.

■ Setting the Control Cycle and BNU Communication Stale Count Limit
▼ Control Cycle, BNU Communication Stale Count Limit
The control cycle and the BNU communication stale count limit for the opened FBAP block
diagram can be set. BNU communication is used for the communication between fieldbus
devices and between a fieldbus device and ACF11 module.
• Control Cycle
Time period of the control cycle for all control loops in the opened FBAP block diagram
drawing.
• BNU Communication Stale Count Limit
When the count of unhealthy transmissions detected on the fieldbus exceeds this limit,
BNU communication will be in abnormal status.

The settings for Control Cycle and for BNU Communication Stale Count Limit can be
entered from keyboard directly. The value entered will be effective after pushing <Enter>
key.
These settings are required for the generation of the FBAP configuration. When the settings
are modified, the [Generation] needs to be performed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-132
■ Generating FBAP Configuration
▼ Generation
Generation of the FBAP configuration is done with the FBAP block diagram open.
The following procedure is used to generate the FBAP configuration.
1. Select [Generation (G)] from the [Edit (E)] menu in the FB editor. Or, click the [Genera-
tion] icon in the toolbar.
A dialog box for confirmation pops out.
2. Click [OK] to continue for generation.
A dialog box showing generation progress displays.
When generation completes successfully, the automatic scheduler creator would start
and the Time Chart for the scheduler would be created.
The dialog box for Generation Successful message is shown as follows.

FB Editor

Generation successful.

OK

050419E.EPS

Figure FB Editor Generation Successful Dialog Box

If generation fails due to a mistake in the configuration data setting or other reason, a
dialog box indicating the error will appear.
3. Click [OK] button.
The dialog box closes.

TIP
• The only check performed prior to the generation of the VCR value and link object parameter value is
a check for the accuracy of the connections in the FBAP block diagram.
• After the VCR value and link object parameter value are generated, a consistency check with respect
to the generated values is performed.
• If generation fails, revise the configuration data in accordance with the contents displayed in the
dialog box indicating an error and then perform generation again.
• If the generation status is a fail, startup cannot be performed (a message is output).

IMPORTANT
Unless the generation is completed normally, the host file set generation function, export
function, download function and schedule creation function cannot be executed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-133
■ All FBAP Generation
▼ Generate All
All FBAP created on FB editor can be generated together. Click [Generate All] on [Edit]
menu, or click [Generate All] icon may start to generate all FBAP configuration.

050420E.EPS

Figure Generate All Icon

Moreover, All FBAP generation can be performed only when the FBAP configuration
drawing is not opened.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-134

5.4.9 Creating FBAP Schedule


Create the FBAP schedule. To efficiently perform the FBAP processes, it is neces-
sary to create a schedule that defines the execution order of the function block
processes and the execution order of the communication between the function
blocks.
Also, the Schedule dialog box is used to create the schedule.

■ Creating a Schedule
▼ Scheduling
Use the Schedule dialog box to create the schedule. In the Schedule dialog box, the sched-
ule is created using the following procedures.
• Create a new execution timing chart
Normally, the creation of a new execution timing chart is automatically performed with
the schedule automatic creation function in the FB editor after the FBAP configuration
is generated. However, if changing the version number of the schedule, the
macrocycle, time resolution, and safety factor, then a new execution timing chart is
created using the Schedule dialog box.
• Revising the execution timing chart
The detail for the newly created execution timing chart is revised using the Schedule
dialog box.
• Printing the execution timing chart
If necessary, the execution timing chart can be printed.
• Generating and saving the schedule
The schedule is generated based on the revised execution timing chart. Also, data for
the generated schedule is saved in the project database.

TIP
• As the result of creating the execution timing chart, a warning is displayed when the FBAP control
cycle exceeds the macrocycle.
• A warning is displayed when the lowest common multiple of the control cycle for each FBAP does not
match the macrocycle.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-135
● Creating a New Execution Timing Chart
Open the Schedule dialog box and create a chart indicating the execution timing for the
function blocks (FB execution timing chart) and a chart indicating the execution timing for
communication (communication execution timing chart).
Use the following procedure to create the execution timing charts.
1. Select [Schedule/display] from the [Edit (E)] in the FB editor. Or, click the schedule
creation icon in the toolbar.
The Schedule dialog box is displayed.

Schedule

Show Schedule

Auto Schedule Re-Schedule 100 % Undo

VersionNumber: 2 MacrocycleDuration: 1000 msec TimeResolution: 20 msec SafetyFactor: 0 % User Entry

msec
0 200 400 600 800 1000
TI1001-AI.Out
VP1001-PID
VP1001-PID.BkcalOut
ACF11-14-OUT-1
VP1001-AO
FBAP1
AI_400
AI_400.Out
TERMi_1064
TERMi_1064.Out
PID_400

Print Help OK Cancel

Communication bar Block bar


050421E.EPS

Figure Schedule Display Dialog Box

In the Schedule dialog box, all FBAP schedules are displayed in the range for 1 cycle
of the macrocycle. However, only the first cycle of each FBAP sub-schedule is avail-
able for revision. From the second cycle on, the contents of the first cycle are displayed
repeatedly.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-136
2. Click the [Modify] button when changing the default values for the version number,
macrocycle (*1), time resolution, or the safety factor.
The Modify Defaults dialog box is displayed.

*1: Macro-cycle can be changed in the [Modify Defaults...] dialog box on the FB editor. It can not be changed in the
[Modify Defaults...] dialog box opened from the schedule dialog box

Schedule

Modify Defaults

VersionNumber: 2

MacrocycleDuration: 1000 msec

TimeResolution: 20 msec

SafetyFactor: 0 %

OK Cancel

050422E.EPS

Figure Modify Defaults Dialog Box

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-137
3. Enter the version number, macrocycle, time resolution, or the safety factor.
For the safety factor, normally the default value is used as is. For the other setting
items as well, it usually does not matter if the default values are left as is.
The setting items in the Modify Details dialog box are indicated below.
• Version:
This is the schedule version name.
• Macrocycle Duration:
This is the control macrocycle (msec). Set this so that this is the lowest common
multiple of each FBAP control cycle.
• Time Resolution:
This is the time resolution for the schedule (msec).
When creating the schedule, multiples of the time resolution can be used as reference
value for calculating start time.
• Safety Factor:
This is the factor (%) indicating the percentage added to the communication time in
order to guarantee function block execution.
For example, if the safety factor is set at 10%, then the communication time will be
calculated as 1.1 times.
The default is 0%.

After the settings in the Modify Defaults dialog box are complete, always click the [OK]
button. The consistency check of the input values (range check and type check) is
executed. After that, rescheduling is automatically performed and the input values are
written to the database. The Modify Defaults dialog box closes and the setpoint values
will be reflected in the Schedule dialog box.
Also, the erase the changes to the default values, click the [Undo] button. The values
return to the setpoint values before they were changed.
4. Click the [New schedule] button.
Using the input default values and based on the entire FBAP configuration, the execu-
tion timing chart is generated. The execution timing chart that has been created is
displayed in the Schedule dialog box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-138
● Revising the Execution Timing Chart
The execution timing chart can be revised if necessary.
If rescheduling is performed after dragging and moving the block bar or communication bar,
the execution timing chart reflecting the revisions is created.
Use the following procedure to revise the execution timing chart.
1. Drag and move the block bar or communication bar.
The position of the bar is adjusted to match the grid specified by the time resolution.
The bar display status will be shaded (cancel fixed.) Also, the terminals cannot be
moved.
2. Cancel the fixed status of the bar if necessary.
Click above the bar with the right mouse button and select [Cancel fixed] from the
menu that appears. When the bar is in cancel fixed status, revisions can be made
using rescheduling.
3. Click [Reschedule].
If rescheduling is performed, the execution timing chart reflecting the revisions will be
created. The bar that was moved in step 1 changes to a pinned display (fixed status),
and it falls outside the target for revisions using rescheduling.
Also, to cancel rescheduling execution, click the [Undo] button. Execution can be
canceled only once.
4. Display the bar status if necessary.
Click above the bar with the right mouse button and select [Property] from the menu
that appears.
The bar property dialog box is displayed.

VP1001-PID.BkcalOut's property

VP1001-PID.BkcalOut's property

Start Time 140 msec

Execution Time 35 msec

OK

050423E.EPS

Figure Property Dialog Box

5. Repeat steps 1 to 4 as necessary.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-139
● Printing the Execution Timing Chart
The execution timing chart can be printed. Click the [Print] button to execute printing. The
standard print dialog box for Windows will appear. Printing can be executed from this dialog
box.
An example of a printed execution timing chart is given below. The printing is divided into a
header section and a Gantt chart. The header section prints on every page.

P1
Schedule results Project Name: Project 1
Header section
Version: 1 Macrocycle Duration: 1000 (msec) Time Resolution: 10 (msec) Safety Factor: 10(%)

20 40 60 80 100 (msec)
TI1001
TI1001.OUT
FIC1001
FIC1001.OUT
Gantt chart section
TERM1

050424E.EPS

Figure Printed Execution Timing Chart

● Generating and Saving a Schedule


After a new execution timing chart is created or one is revised, the schedule is generated
and saved.
To generate and save a schedule, click the [OK] button in the Schedule dialog box.
Based on the execution timing chart, the FB schedule, LAS schedule, communication
schedule, some of the block parameter values and some of the network parameter values
are automatically generated. The data thus generated is saved to the project database. At
the same time, the Schedule dialog box closes.
To exit without generating and saving the schedule, click the [Cancel] button.
The Schedule dialog box closes without generating or saving the schedule.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-140
■ Button Operation Availability in the Schedule Display Dialog Box
During or after the execution of an operation, there are buttons that can be operated and
those that cannot be operated in the Schedule dialog box.
The availability of button operation for each type of operation status is shown in the table
below.
Table Availability of Button Operation (1/2)
Buttons that
Status Buttons that operate Right button
do not operate
New schedule
Modify defaults
Undo
Initial status Print (when there is
OK Property
(when opening) an existing schedule
Reschedule
Cancel
Help
While creating a new
schedule (New schedule All
button is depressed)
Undo
Ok
After creating new Modify defaults New schedule
Property
schedule Print Reschedule
Cancel
Help
New schedule Undo
Areas of manual
Reschedule OK Erase
revisions (after
Cancel Print Property
moving elements)
Help Modify defaults
During rescheduling
(Reschedule button All
depressed)
Undo
OK
Print New schedule Cancel fixed
After rescheduling
Cancel Reschedule Property
Help
Modify defaults
Undo
After changing
OK Cancel fixed
default values
Modify defaults New schedule (when there are
(rescheduling
Print Reschedule manual revisions)
automatically
Cancel Property
performed)
Help
050425E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-141
Table Availability of Button Operation (2/2)
Buttons that
Status Buttons that operate Right button
do not operate
New schedule
OK
Fixed cancel (when
Modify defaults Undo
After executing undo there are manual
Print Reschedule
revisions)
Cancel
Property
Help
New schedule
Reschedule Undo
Erase
After cancel fixed Modify defaults OK
Property
Cancel Print
Cancel
New scheduleOK
OK
Property
Modify defaults Undo
After erasing Cancel fixed
Print Reschedule
(when fixed)
Cancel
Help
050426E.EPS

■ Revising an Existing Schedule


A schedule created in the Schedule dialog box and stored in the project database, can be
revised from the scheduler display dialog box, or on the FB Schedule dialog box or the
Communication Schedule dialog box called out form the device editor.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-142
● Revising a Function Block Execution Schedule
▼ FB Schedule
Use the following procedure to revise a function block execution schedule.
1. Select [Device editor (D)] from the [Tool (T)] menu in the project manager.
2. Select the device for which the function block execution schedule is to be changed
from the “Devices inside project” list box.
3. Select [FB schedule (F) ...] from the [Edit (E)] menu in the device editor.
The FB Schedule dialog box opens.

FB Schedule

PDTag: New_valve_positioner_2

Scheduled Function Blocks Schedule Parameters

AO_466 VFD Reference: 2


PID_400
Start Time Offset: 4480
(1/32msec)
Modify

Close

050427E.EPS

Figure FB Schedule Dialog Box

4. Select the function block for which the execution start time is changed from the
“Scheduled function block” list box.
5. Click the [Modify] button.
The Modify FB Schedule dialog box is displayed.

FB Schedule Modify

Start Time Offset: 64

OK Cancel

050428E.EPS

Figure Modify FB Schedule Dialog Box

6. Enter the function block execution start time in the “Start time offset” box.
7. Click the [OK] button.
The function block execution start time is changed and the Modify FB Schedule dialog
box closes.
Clicking the [Cancel] button closes the Modify FB Schedule dialog box without chang-
ing the function block execution.
8. Repeat steps 2 to 7 as necessary.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-143
● Revising a Communication Execution Schedule
▼ Communication Schedule
Use the following procedure to revise a communication execution schedule.
1. Select [Device editor (D)] from the [Tool (T)] menu in the project manager.
2. Select the device for which the communication execution schedule is to be changed
from the “Devices inside project” list box.
3. Select [Communication schedule (F) ...] from the [Edit (E)] menu in the device editor.
The Communication Schedule dialog box opens.

Communication Schedule

PDTag: ACF11_1

Scheduled Function Block Outputs Schedule Parameter

AI_400.Out Connection End Point: 0xf622


PID_400.BkcalOut
TERMI_1064.Out Time Offset: 1280
(1/32msec)
Modify

Close

050429E.EPS

Figure Communication Schedule Dialog Box

4. Select the communication item for which the execution start time will be changed from
the “Scheduled function block outputs” list box.
5. Click the [Modify] button.
The modify Communication Schedule dialog box is displayed.

Communication Schedule Modify

Connection End Point: 0x1822

Time Offset: 704

OK Cancel

050430E.EPS

Figure Modify Communication Schedule Dialog Box

6. Enter the communication execution start time in the “Time offset” box.
7. Click the [OK] button.
The communication execution start time is changed and the modify Communication
Schedule dialog box closes.
Clicking the [Cancel] button closes the modify Communication Schedule dialog box
without changing the function block execution time.
8. Repeat steps 2 to 7 as necessary.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-144

5.4.10 Output Host File Set


Output the host file set that the application operating in the supervisory system
(host application) uses.

■ Outputting the Host File Set


Use the following procedure to output a host file set.
1. Select [Generate host file set (G) ...] from the [Project (P)] menu in the project man-
ager.
The Host File Generation dialog box is displayed.

Host File Generation

Option Host Files


OK
Standard Block Parameter List
Cancel
Data Type
Reserved Word
View Information

050431E.EPS

Figure Host File Generation Dialog Box

2. The default setting on the host file generation dialog box is that all option boxes are
checked. Only the un-required options need to be removed for the host file.
3. Click the [OK] button.
The host file set is output to the Hfs directory in the project directory and the Host File
Generation dialog box closes.
Clicking the [Cancel] button closes the Host File Generation dialog box without output-
ting the host file set.

IMPORTANT
• Do not change the file name and folder configuration of the host file set that was
output. If the file name or folder configuration is changed, the configuration data
cannot be imported by the system builders.
• When importing the host file set to the CENTUM VP/CS 3000/CS 1000 or STARDOM,
select all options.

SEE ALSO
• For more information about the Hfs directory, see the following:
5.1.11, “Directory Structure for the Fieldbus Engineering Tool”
• For more information about the information output as the host file set, see the following:
5.1.6, “Project Manager”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-145

5.5 Project Startup


After the settings related to the project are completed, perform project startup. This
section explains project startup.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-146

5.5.1 Project Startup Procedure


In project startup, preparation for downloading and downloading of the project
configuration data to the device is performed.

■ What is Project Startup?


In project startup, the project configuration data that was set is downloaded to the device.
By downloading, operation of the device begins.

■ Work Performed Prior to Installing the Device


To perform project startup, the following work must be completed prior to installing the
ACF11 or the fieldbus device.

● Work Performed Before Installing the ACF11 to the IOM Nest


Before installing the ACF11 to the IOM nest, use the worksheet given in this manual,
ACF11 device ID management table, and register the device ID for the ACF11.
When downloading from the Fieldbus Engineering Tool to the ACF11, set the physical
device tag name and device ID for the ACF11, which is the download target in the Fieldbus
Engineering Tool. Refer to the ACF11 device ID management table to set the device ID
when performing this procedure.

SEE ALSO
• For more information about the worksheet, see the following:
2, “Fieldbus Communication Module”
• On how to set the device ID in the Fieldbus Engineering Tool, seethe following:
5.5.3, “Changing a Registered Device ID”

● Work Performed Before Installing Fieldbus Device


Before connecting the fieldbus, set the following values in the fieldbus device. If the values
are not set, or if the values set for the Fieldbus Engineering Tool is different from those set
for the actual device, the ACF11 cannot recognize the device in the fieldbus and download-
ing and other communication cannot be performed.
• Physical device tag name in the fieldbus
• Node address in the fieldbus

SEE ALSO
• The tag names and node addresses for physical devices need to be defined using the FieldMate in the
PC connected to H1 fieldbus. For more information about the FieldMate, see the following:
FieldMate Versatile Device Management Wizard (IM 01R01A01-01E)
• The tag names and node addresses of physical devices can also be defined using Fieldbus Engineer-
ing Tool. For more information, see the following:
“■ Changing Physical Device Tag Name and Node Address” in 5.5.5, “Executing Project Startup”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-147
■ Flow of Project Startup
The workflow for project startup is shown below.

Begin project startup

Set the control bus

Open or import project

Change registered device IDs

Set the advanced LM

Execute project startup

Project backup Legend


Operations that
are always performed
Operations performed
as necessary
End project startup Start and end of operation

050501E.EPS

Figure Flow of Project Startup

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-148
■ Summary of Each Step

● Setting the Control Bus


If setting related to the control bus were not performed at the time of installation, then the
control bus related settings are performed at this point.

SEE ALSO
For more information about settings related to the control bus, see the following:
5.2.4, “Configuring Control Bus”

● Opening or Importing a Project


To download the project, open the project created. Also, if a project that was backed up as
described later on is downloaded again, import the configuration data.

● Changing Registered Device IDs


If a temporary device ID is registered in the configuration data for the registered device,
change the temporary device ID to the device ID of the device actually connected to the
fieldbus (device ID assigned to the device by the vendor).

● Setting the Advanced LM


Set the advanced LM (linkmaster).
Setting the advanced LM means to specify the Ap clock sync interval, the device that
becomes the device and the device that is the highest priority linkmaster device.

● Executing Project Startup


After all settings are completed, perform the following operations prior to executing startup.
• Confirm that the fieldbus physical device tag, node address and device class have
been set so as not to generate an error when downloading. The tag names and node
addresses of physical devices and the devices classes can be changed when imple-
ment the devices to the field.
• Perform pre-download operations to safely execute download for a system currently
running.

Execute project startup after doing the above operations.


After startup is performed, project control starts after the project configuration data is
downloaded to the device.

● Project Backup
If necessary, back up the project for when performing re-engineering.
Project backup is performed using the export function.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-149

5.5.2 Opening or Importing a Project


To startup the project created, it is necessary to open the project.
If the project is not open, open the project.
Also, if starting up the project again after backup is completed, import the project.

■ Open the project


Open an existing project.

SEE ALSO
For more information about the procedure for opening a project, see the following:
5.3.2, “Creating a New Project or Opening a Project”

■ Import a Project
Use the following procedure to import a project.
1. Call the project manager. If a project is open, close the project.
2. Select [Import (I) ...] from the [Project (P)] menu in the project manager.
The file open dialog box is displayed.
3. Select the system configuration file for the project to be imported.
4. Click the [OK] button.
The file open dialog box closes and the information related to the selected project is
displayed in project manager.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-150

5.5.3 Changing a Registered Device ID


If a temporary device ID is registered for the device configuration data, change the
temporary device ID to the actual device ID.

■ Changing a Registered Device ID


The device ID is information for specifying the device that will download the configuration
data. If a temporary device ID was used at the time the device was registered, this tempo-
rary ID must be changed to the actual device ID assigned by the device vendor. Use the
following procedure to change the device ID.
1. Select [Device editor (D)] from the [Tool (T)] menu in the project manager.
The device editor is displayed.
2. Select the device to be changed from the “Devices in project’ list box.
3. Click the [Modify] button for the “Devices in project” group box.
The Device Modify dialog box is displayed.
4. Enter the device ID in the “Device ID” box.
5. Click the [OK] button.
The Device Modify dialog box closes.
Clicking the [Cancel] button closes the Device Modify dialog box without changing the
device ID.
6. Close the device editor.

SEE ALSO
• For more information about the device ID and physical device tag name, see the following:
5.1.7, “Editors”
• Actual device ID can be confirmed in “Device ID Display”. For more information about “Device ID Display”,
see the following:
5.3.6, “Display Device ID”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-151

5.5.4 Advanced LM Settings


Setting the advanced LM (Linkmaster) refers to specifying the Ap clock sync inter-
val, time publisher device and the preferred LM device.
If more than one device of the linkmaster class has been set in a single project, the
one that has priority is determined by this setpoint value.

■ Setting the Time Publisher Device and Linkmaster Device


Use the following procedure to do the advanced linkmaster settings.
1. Select [Advanced LM setting (P) ...] from the [Network (N)] menu in the project man-
ager.
A message dialog box will appear and the progress of downloading is displayed in the
dialog box.

Advanced LM Settings

WARNING!!!
The Information below is important for correct
download. It should only be changed by an
advanced User of the FF Engineering Tool.

ApClockSyncInterval(sec): 20

Time Publisher Device: 0x14

Preferred LM Device: 0x14

OK Cancel

050502E.EPS

Figure Advanced LM Settings Dialog Box

2. Enter the time interval at which time synchronization is performed in the “Ap clock
sync interval (seconds)” box.
3. Enter the node address of the device to be set as the time publisher device in the
“Time publisher device” box.
4. Enter the node address of the device to be set as the preferred LM device in the
“Preferred LM device” box.
5. Click the [OK] button.
The Advanced LM Settings dialog box closes.
Clicking the [Cancel] button closes the Advanced LM Settings dialog box without
setting the advanced LM.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-152

5.5.5 Executing Project Startup


Project startup refers to downloading the configuration data for all devices in the
project and starting control using the devices.
Prior to startup, it is necessary to perform the tag assignment, address assignment,
device class setting and pre-download operations.

TIP
In a case, such as, downloading imported configuration data where the consistency checks in conjunction
with the input or generation of configuration data have not been performed, the consistency check is done
prior to downloading. If an error occurs during the consistency check, downloading is not performed.

IMPORTANT
Confirm that the physical device tag name, node address and device class are set. If the
physical device tag name, node address and device class are not set, an error will occur
when downloading.
Also, set the physical device tag name, and node address before installing a device in each
field.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-153
■ Performing Pre-Downloading Operation
Pre-download operations must be performed to safely execute download for a system
currently running. Pre-download operation refers to changing the AO block parameters for
the fieldbus device to be downloaded prior to downloading.

IMPORTANT
Always perform the pre-download operation in order to download safely. Since the AO block
OUT parameter is not the one that is downloaded, the value for this parameter remains the
same before and after downloading. The value for the OUT parameter prior to download is
retained during download.
If pre-download operation is not performed, there is a risk that the control loop including the
fieldbus device targeted for downloading will perform unexpected operations during down-
load or after download is completed. For example, if the fieldbus device targeted for down-
loading is the valve that controls fuel supply, the valve may remain opened during down-
load.

Perform procedures 1 to 3 indicated below with respect to the AO block as the pre-down-
load operation. Also, when the current mode of the AO block is CAS, and if the same setting
as indicated in procedure 2 below can be performed by changing the output value of the
upper block connected to the AO block (FCS function block, etc.), then procedure 2 can be
omitted.
1. Set the AO block mode to MAN
To change the AO block output value, the mode must be changed to MAN. This opera-
tion is performed with the operation and monitoring function or the Device Manage-
ment Tool. If it is performed with the operation and monitoring function, then the
parameters required for the operation (MODE, OUT) should be assigned in the face-
plate block beforehand.
2. Set the AO block OUT value on the safe side
Set the AO block OUT value on the safe side.
For example, assume there is a fieldbus device that controls how much the valve
opens and that setting the OUT value of the AO block for that device to 0 is the specifi-
cation for the valve to close. Further, assume that in the control loop that contains this
fieldbus device, the valve closed state is the safe status. In this example, the OUT
value for the AO block is set to 0.

IMPORTANT
Take note that setting the OUT value for the AO block to 0 does not necessarily mean it is
the safe side. The safe side setting differs according to the specifications of the fieldbus
device and design of the control loop. Perform the pre-download operation after first con-
firming which setting is the safe side.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-154
3. Set the mode for the upper block connected to the AO block (for example, the FCS
function block) to MAN.
By setting the upper block mode to MAN, the upper block restarts output after tracking
the actual output value of the AO block so that the AO block output value does not
change from the initial status (value of the safe side set in procedure 2).
If the upper block is the fieldbus block, parameters required by the operation (MODE,
OUT) need to be assigned to the faceplate block beforehand and changed with the
operation and monitoring function or the Device Management Tool.

IMPORTANT
Always set the upper block mode to MAN.
After download is complete, the fieldbus block starts up from the mode value that was
downloaded. If the upper block mode is set to AUT and when the mode value downloaded
to the AO block is CAS, then cascade control by the upper block is restarted right after
download is completed. For this reason, there is a risk that the control loop including the
fieldbus device may perform unexpected operations depending on the upper block output
value.

■ Download to the ACF11 from the Fieldbus Engineering Tool


Even when the directory for fieldbus engineering configuration data of the engineering tool
is not specified in CENTUM VP/CS 3000/CS 1000 system builders, downloading to the
ACF11 can be performed from the Fieldbus Engineering Tool. While when the directory is
specified, downloading to the ACF11 can be performed from the system builders. Fieldbus
engineering configuration data the engineering tool will be downloaded together.
When downloading to the ACF11 the control bus communication function must be working
normally. After downloading to the ACF11 is completed, the ACF11 module begins operat-
ing.
When downloading to the ACF11 performed from the Fieldbus Engineering Tool, follow the
procedures below.
1. Select ACF11 as the device where downloading is performed from the “Devices in
project” list box in the project manager.
2. Select [Download (D)] from the [Device (D)] menu in the project manager.
A dialog box will appear to indicate the downloading progress.

IMPORTANT
Do not perform any parameter change operations whatsoever with the operation and
monitoring function during download. If a parameter is changed with the operation and
monitoring function during download, the fieldbus device will start up according to the
changed parameter after download is completed which is extremely dangerous. For ex-
ample, if the AO block mode is set to MAN and OUT to “50” with the operation and monitor-
ing function, the AO block will output “50%” after download is completed.
Also, parameters cannot be changed from the Device Management Tool during download.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-155
TIP
For STARDOM, it is not possible to download to NFLF111 from Fieldbus Engineering Tool but possible
from Resource Configurator.

● Action when the Download Is Terminated Before Completion


If the user forcibly terminates the tool or if download is terminated due to an error in the
communication route, download cannot be re-executed until the time the FCS detects a
timeout (approximately 60 seconds). If download is executed before a timeout is detected,
an error will occur. Re-execute the download after the timeout time has elapsed.
There may be an error termination with the first download request after timeout. The reason
for this is that the ACF11 has detected a contradiction in the ACF11 internal status, be-
cause communication was terminated abnormally; and it is not because of a fault. In this
case, continue to re-execute download.
The data downloaded to the ACF11 up to the point the download was terminated is valid. If
an IOM load was executed, data after this will be reflected in the ACF11 EEPROM. Thus, if
download was terminated due to an error, always perform download again once the cause
of the error has been removed.

● Action when the Network Manager in the Fieldbus (NMgr) Is Accessing the
ACF11
The network manager (Network Manager: NMgr) may access the device in the fieldbus to
monitor the operating condition of the device. If the NMgr is accessing the ACF11, a down-
load request will result in an error, since the ACF11 cannot accept any other requests.
Immediately stop accessing by the NMgr while downloading.

■ Physical Device Tag Name and Device ID for the ACF11


When executing download, the physical device tag name set with the device editor and the
actual physical device tag name for the download destination are compared, and download
begins only if they match. The device ID is used for managing by the user.
The following values are specified as the physical device tag name and device ID for the
ACF11.

Physical device tag name: ACF11-14

Fixed Node Address (hexadecimal notation)


Device ID: 5945431001:ACF11-176M201512

Fixed Manufacturing Serial No.


050503E.EPS

IMPORTANT
The ACF11 node address is fixed as 0x14 (hexadecimal).
If the ACF11 is replaced because of a malfunction, it is recommended that the ACF11
device ID set with the device editor be rewritten to the device ID for the ACF11 following
replacement. Also, the device ID manufacturing serial number is printed on the ACF11
circuit board.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-156
■ Downloading to ACF11 from CENTUM VP/CS 3000/CS 1000 Builder
Data configured on the builder need to be downloaded to ACF11. This operation is per-
formed with the system builders.

SEE ALSO
For more information about downloading to the ACF11 from CENTUM VP/CS 3000/CS 1000 builders,
see the following:
4.2.4, “Download From IOM Builder”

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-157
■ Changing Physical Device Tag Name and Node Address

IMPORTANT
• The physical device tag names and node addresses can be changed with the Field-
bus Engineering Tool. If the physical device tag names and node addresses are not
set, these setting must be set by the FieldMate in the PC connected to H1 fieldbus.
• To change the physical device tag names and node addresses, it is necessary to
register the correct device ID of the device in the project for which changes are to be
made. Use “Display Device ID” or the FieldMate to register the device ID obtained from
the physical device.

SEE ALSO
For more information about the FieldMate, see the following:
FieldMate Versatile Device Management Wizard (IM 01R01A01-01E)

When changing the tag names and node addresses of physical devices, tag assignment
and addresses assignment need to be done.
When assigning a tag name and a node address to a H1 conformed physical device, only
that device should be connected to the Fieldbus.
For newly created project or an existing, the tag name assignment and addresses assign-
ment can be done in the following procedures.

● For a Newly Created Project


1. Create a New Project.
2. Assign a physical tag name and node address to ACF11, and then register them into
the project.
3. Click [Generate All] to start generation.
4. Register the segment name on Control Bus Configuration Window.
5. Download to ACF11 on IOM builder.
Then, tag assignment and node address assignment can be carried out.

● For an Existing Project


1. Open the project.
2. Set a polling address range if required.
3. Download to ACF11 on IOM builder, one of system builders.
Then, tag assignment and node address assignment can be carried out.
When tag assignment or address assignment is completed, the further tag alignment or
address assignment change can be carried out only after the previous assignment is
generated and downloaded.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-158
● Set Polling Address Range
For address assignment, the polling address range should have been set. The procedure
for setting the polling address range is shown as follows.
When the dialog box for polling address range setting is displayed, the tasks for accessing
the devices database will be denied.
1. Click [Polling Address Setting..] on [Option] menu in Project Manager, the dialog box
for setting the polling address range will be displayed.

Polling Address Setting

Automatic decision of Polling Address range


Manual decision of Polling Address range

Range of Polling Address

0x10˜ 0x23 Range of node address polled


ascending order continuously
0xE8 ˜0xFF Range of node address polled in
descending order continuously

OK Cancel

050504E.EPS

Figure Polling Address Setting Dialog Box

2. Clicking the option button for [Automatic decision of Polling Address Range] may allow
the Project Manger set the range automatically.
Clicking the option button for [Manual decision of Polling Address Range] will only
allow the range to be set manually.
The default option is [Manual decision of Polling Address Range].
3. Polling address range can be manually specified is limited with the range of 0x14 to
0xF7 in hexadecimal. A value beyond this range will generate an error message.
4. Clicking [OK] button, the specified polling address range will be set and the dialog box
will be closed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-159
● Tag Assignment
When physical tag name or both physical tag name and node address are changed, tag
assignment is required. Tag assignment can be performed as follows.
1. Using the network editor, confirm that the physical device tag name and node address
for changing have been registered in the project.
If they are not registered, use the device editor or the network editor to register them.
2. Once the registration the physical device tag name and node address is confirmed
correct, choose a device in the “Devices in Project” list box in Project Manager.
3. Click [Tag Assign..] on [Device] menu.
The physical device tag name and node address assigning for corresponding field
device will start. When it is completed, a message will pop out to notify the completion
of the changes.

● Address Assignment
When node address of a physical device is changed, address assignment is required.
Address assignment can be performed as follows.
1. Using the network editor, confirm that the node address of the designated device has
been registered in the project.
If the node address is not registered, use the network editor to register it.
2. Once the registration the physical device node address is confirmed correct, choose a
device in the “Devices in Project” list box in Project Manager.
3. Click [Address Assign] on [Device] menu.
The node address assignment for corresponding field device will start. When it is
completed, a message will pop out to notify the completion of the changes.

■ Setting the Device Class for Physical Devices


▼ Device Class Setting
Download cannot be started if the device class entered with the network editor is different
from the one set for the actual device in the fieldbus. In this case, it is necessary to enter the
correct device class with the network editor or to set the device class entered with the
network editor for the actual device.
1. Choose a device for setting device class from the [Device in Project] list box of Project
Manager.
2. Choose [Device Class Setting] on [Device] menu of Project Manager.

To set the device class for the actual device, select [Set device class] from the [Edit] menu.
By doing this, the device class entered using the network editor will be set for the actual
device. While the setting is in progress, the progress is displayed in the message dialog
box.
An error will occur if the field device can not be found or can not be reached.

IMPORTANT
The device class set for the actual device will be retained even if the power to the device is
cut off.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-160
Set the device class after completing the following steps.
• Create the project (the entire process from the registration of the device to the comple-
tion of generation)
• Set the physical device tag name and node address for the actual device
• Download to the ACF11
• Connect the fieldbus device to the H1 fieldbus

■ Downloading to the Fieldbus Devices


Downloading to the various fieldbus devices is executed with the Fieldbus Engineering Tool.
The following methods are available for executing download.
• Using the Download dialog box
By selecting a project as the download target, the entire project can be started up.
Also, download can be performed to multiple devices and blocks in the project.
• Using the project manager
Download can be performed directly to individual devices from the project manager
menu.

The device begins operating when downloading is completed normally.


If download is executed for all devices in the project, the device does not begin operating
unless data download to all devices is completed normally. If an error occurs during down-
loading, the process is immediately terminated. At this time, downloaded data will be set in
those devices where download was already completed normally.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-161
● Calling the Download Dialog Box
Perform one of the following operations to call up the Download dialog box.
• Select [Download] from the [Project] menu in the project manager
• Start directly using an external application

By doing this, the Download dialog box is displayed.

Download

Device in project
- 1 toms
- EJA_4 EJA_4(RESOUR...
- 3 EJA_4(RESOURCE) toms(AI)
3 toms(AI) (AI)
3 (AI)

Execute Block parameter download

Execute Close

050505E.EPS

Figure Download Dialog Box

The devices and blocks in the project are displayed in the Download dialog box. For the
device, the physical device tag name is displayed. Also, for the block, the block tag name
and block type are displayed. These tag names cannot be changed. The blocks available for
display are the resource block, function block, and transducer block. However, if the check
box for [Display transducer block] is marked off in the environment setting dialog box, the
transducer block will not be displayed.
Also, because the host interface device (ACF11) is not displayed, download to the ACF11
cannot be performed with the Download dialog box.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-162
● Executing a Download
Use the following procedure to execute download.
1. Select the project, device or block.
Multiple devices and blocks can be selected as the download target. Also, all of the
devices in project is downloaded when a project is selected.
2. Check [Execute block parameter download] when downloading block parameters. This
is not checked in the default setting.
Also, if a block was selected in step 1, this cannot be checked.
3. Click the [Execute] button with the download target selected.
The following actions differ depending on whether [Execute block parameter down-
load] was checked.
• When [Execute block parameter download] is checked
The message dialog box, “Did you execute block parameter upload?” is displayed. If
the [Yes] button is clicked in this dialog, download is executed. If the [No] button is
clicked, the screen returns to the Download dialog box without executing download.
• When [Execute block parameter download] is not checked
Download is executed.

An Example of a message dialog box display is given below.

PJT1

Project Name : PJT1

2008/06/16 15:27:36 Start downloading to YW1001.


2008/06/16 15:29:18 Start downloading block parameter to YW1001.
2008/06/16 15:29:48 Start downloading block parameter to YI1001.
2008/06/16 15:30:55 End downloading to YW1001.

Stop OK Save Detail

Progress bar 050506E.EPS

Figure Message Dialog Box

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-163
A message indicating the status of the download execution is displayed in the message
dialog box. All messages are stored in a text file (download.log) under the Log directory.
Also, how the execution process is proceeding can be seen in the progress bar.
There are two types of messages: regular messages and detail messages. During down-
load, only regular messages are displayed. Also, an error message is treated as a regular
message.
A list of the messages displayed in the message dialog box is given below.

Project Name : PJT1

1998/12/14 15:27:36 Start downloading to YW1001. ------- (*1)


1998/12/14 15:27:36 Lock FCS Segment.
1998/12/14 15:27:36 Initializing Engineering Tool.
1998/12/14 15:27:42 Getting LiveList.
1998/12/14 15:27:44 Checking Physical Device Tag.
1998/12/14 15:27:46 Connecting VCR for system.
1998/12/14 15:28:01 Read OD information.
1998/12/14 15:28:03 Initializing VCR for application.
1998/12/14 15:28:05 Downloading VCR (No.2).
1998/12/14 15:28:08 Downloading VCR (No.4).
1998/12/14 15:28:11 Downloading VCR (No.6).
1998/12/14 15:28:14 Downloading VCR (No.7).
1998/12/14 15:28:17 Downloading VCR (No.8).
1998/12/14 15:28:20 Aborting VCR.
1998/12/14 15:28:22 Connecting VCR for application.
1998/12/14 15:28:24 Change mode of resource block to O/S.
1998/12/14 15:28:26 Initializing LinkObject (No.1).
1998/12/14 15:28:28 Initializing LinkObject (No.2).
1998/12/14 15:28:30 Initializing LinkObject (No.3).
1998/12/14 15:28:32 Initializing LinkObject (No.4).
1998/12/14 15:28:34 Initializing LinkObject (No.5).
1998/12/14 15:28:36 Aborting VCR.
1998/12/14 15:28:38 Connecting VCR for system.
1998/12/14 15:28:41 Downloading VCR (No.3).
1998/12/14 15:28:43 Downloading VCR (No.5).
1998/12/14 15:28:46 Downloading SMIB.
1998/12/14 15:28:55 Initializing block schedule (No.1).
1998/12/14 15:28:58 Initializing block schedule (No.2).
1998/12/14 15:29:01 Initializing block schedule (No.3).
1998/12/14 15:29:04 Initializing block schedule (No.4).
1998/12/14 15:29:07 Downloading Macrocycle.
1998/12/14 15:29:10 Downloading block schedule (No.1).
1998/12/14 15:29:13 Aborting VCR.
1998/12/14 15:29:15 Connecting VCR for application.
1998/12/14 15:29:18 Start downloading block parameter to YW1001. ------- (*1)
1998/12/14 15:29:48 Start downloading block parameter to YI1001.
1998/12/14 15:30:47 Downloading LinkObject (No.1).
1998/12/14 15:30:49 Downloading LinkObject (No.2).
1998/12/14 15:30:51 Change mode of resource block to AUTO.
1998/12/14 15:30:53 Aborting VCR.
1998/12/14 15:30:55 Unlock FCS Segment.
1998/12/14 15:30:55 End downloading to YW1001. -------------- (*1)
-----------------------
xxxx/xx/xx xx:xx:xx Stop downloading to *** --------------(*1)
050507E.EPS
Note: In the area indicated by **, the actual physical device tag name or block name is displayed.
*1: Normal message

Figure List of Messages Displayed in the Message Dialog Box

IMPORTANT
When downloading is aborted due to VCR initialization error, do the following to handle the
error.
1. Performs address assignment to the device that the error occurs.
2. Start downloading again.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-164
4. To terminate the download execution, click the [Stop] button. A dialog box to confirm
termination is displayed.
Clicking on the [Stop] button in this dialog box terminates the download. If [Cancel] is
clicked, the download is not terminated and the display returns to the Download dialog
box.
Also, download continues while the confirmation dialog box is being displayed.

IMPORTANT
If execution of download was terminated, operation of the device and block cannot be
guaranteed. To correctly operate the device and block, it is necessary to execute download
once more.

5. After download is completed, a detail message can be displayed. Clicking the [Detail]
button displays the detail message. Also, clicking the [Detail] button once more returns
to the regular message display.

● Saving Messages
After download is completed, all messages generated during the download can be saved to
a text file by specifying the directory and file.
Use the following procedure to save messages.
1. Click the [Save] button in the Download dialog box.
The dialog box for specifying the file in which the messages are to be saved is dis-
played.
2. Specify the directory and file, and save them.
Further, in the default setting, the Log directory is specified as the storage location.

● Saving the History


▼ History
An download history is saved when download is executed. The upload history is also saved
when the upload function is called from the download function. A maximum of 255 historical
information can be saved. Further, the history cannot be changed.
The following types of historical information are saved.
• Physical device tag name
• Block tag name
• Type of loading (download or upload)
• Date and time (Year, month, day and time)
• Result (error, terminated, or completed)

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-165
History is displayed in the Download/Upload History dialog box. To call the Download/
Upload History dialog box, select [History] from the [Project] menu in the project manager.

Download/Upload History

Device tag name Block tag name Download Download Date Upload Upload
ACF11_5 Error 2008/06/12 17:15
ACF11-14 Normal 2008/06/16 12:23
EJA_4
EJA_4 AI_600
EJA_4 EJA_4

Close Update

050508E.EPS

Figure Download/Upload History Dialog Box

TIP
The following operations can be performed in the Download/Upload History dialog box.
• The history can be rearranged in order of date or tag name
• A search can be performed using the date or tag name as the keyword
• The Download/Upload History dialog box can be displayed while download is being executed. In this
case, click the [Update] button and the historical display on the screen will be updated

● Executing Download for Individual Devices Using the Project Manager


Instead of the Download dialog box, download can be performed from the individual de-
vices using the project manager. When downloading to individual devices, the devices to
which download has been completed will start operating.
Use the following procedure to execute download to individual devices.
1. Select the device for executing download from the devices in project list box within the
project manager.
2. Select [Download (D)] from the [Device (D)] menu in the project manager.
First, a consistency-check is performed. If an error occurs due to the consistency-
check, download is terminated.
After the Consistency-check is completed, a confirmation dialog box prompting for
block parameter download is displayed.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-166
3. Click [Yes] or [No] in the confirmation dialog box.
• When the [Yes] button is clicked
Block parameters become the download target and a message dialog, “Did you
execute block parameter upload?” will be displayed.
If the [Yes] button is clicked, download is performed.
If the [No] button is clicked, the screen returns to the project manager without perform-
ing the download.
• When the [No] button is clicked
The block parameters do not become the download target. Download is performed.

While download is being executed, a message dialog box is displayed.

4. To terminate the download, click the [Stop] button. The download will be discontinued
after the communication processing during execution is completed.

■ Confirming the Download Completion


A confirmation dialog box indicating normal completion is displayed when download is
dialog box is displayed that indicates the cause of the error and up to which device down-
load was completed normally (or, which device did not complete download).

If a fieldbus communication error occurs when downloading, download may be terminated.


If a communication error occurs, a communication error dialog box is displayed. The follow-
ing four items are possible causes for the communication error to occur.
• Connection for download cannot be established
• Connection for download was disconnected
• An error response was returned with respect to the request
• Response to request did not return within the specified time (60 seconds)

Re-execute the download if a communication error occurs. If the download is re-executed,


the download may complete normally.
If an error occurs again even when download is re-executed, the segment status or the
download target device needs to be examined.

■ Operation After Download


The fieldbus device begins operation immediately after download from the Fieldbus Engi-
neering Tool is completed. The operation start time block mode becomes the value set with
the Fieldbus Engineering Tool. Change the mode as required.
After download, change the mode from the Device Management Tool if the current mode is
O/S and change it with the operation and monitoring function or Device Management Tool if
the current mode is MAN. If the fieldbus device mode is O/S, the mode cannot be changed
with the operation and monitoring function.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-167

5.5.6 Project Backup


After project startup has been completed, back up the project if necessary. By back-
ing up the project, if for some reason ,such as, the project stops, the back up can be
used to start the project again. There are two methods for backup, backing up the
data for the entire project and backing up the data for individual devices.
Project backup is done using the export function.

■ Backing Up the Configuration Data for the Entire Project


Use the following procedure to backup configuration data for the entire project.
1. Select [Export (E)] from the [Project (P)] menu in the project manager.
The save-as dialog box is displayed.
2. Enter the system configuration file name in the “File name” box.
3. Click the [OK] button.
The save-as dialog box is closed and the system configuration file and device object
file is output to the Src directory in the project directory.
Clicking the [Cancel] button closes the save-as dialog box without outputting the
system configuration file and device object file.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-168
■ Backing Up Device Configuration Data
Use the following procedure to back up device configuration data.
1. Select [Export (E) ...] from the [Device (D)] menu in the project manager.
The Save As dialog box is displayed.
2. Enter the device object file name in the “File name” box.
3. Click [SAVE] button.
The Save As dialog box is closed and the device object file name is output to the Src
directory in the project directory.
Clicking the [Cancel] button closes the save-as dialog box without outputting the
device object file.

SEE ALSO
• On how to import a project that has been backed up, see the following:
5.3.4, “Importing Device Configuration Data to the Project Database”
• For more information about the Src directory, see the follwing:
5.1.11, “Directory Structure for the Fieldbus Engineering Tool”

■ Backing Up the Project Directory


Each project directory can be copied and backed up without using the project import
function.
However, because the size of the project database can be several MB, use an external
memory medium, such as, an MO disk when copying each project directory.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-169

5.6 Fieldbus Engineering Tool Error Messages


If an error occurs, the Fieldbus Engineering Tool displays an error message that
indicates the contents of that error. This section explains the Fieldbus Engineering
Tool error messages.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-170

5.6.1 Project Manager Error Messages


The project manager error messages are listed in the table below.

■ General
Table Error Messages (General)
Error message Cause Steps to take
<File Name> 1, 2, or 25 or more characters input, Set file name within 3 to 24
The above file name is invalid. or [|] input characters. Or, delete [|]
Included invalid character. ['] (single quotation) was input Delete [']
Check whether location and conten
ts of ..BIN\SYSDB directory is correct.
Unable to create new Database for Database file for new project cannot Check whether the home path is
the project. be found entered in the Path section of the
KAPPA.INI file, which indicates the
location of executable files
Database being used in another Restart after the other
Unable to open the database. application is completed
application
<Directory> Path not found. Check
Specified directory cannot be found Check the path and the directory
that the correct path was specified.
Error while deleting Project Path. Project was not completely deleted Delete the project directory manually
Could not remove current project
from ODBC list! ODBC driver not installed properly Check the version of the ODBC driver

050601E.EPS

■ Consistency Check
If the consistency check function detects an error, an error message containing one of the
following error codes is output.
Table Error Messages (Consistency Check)
Error code Description
0 No error
-1 Error during range test: value is not within the valid range
-2 Value conversion error: incorrect string
-3 Value conversion error: value is not within the valid format range
050602E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-171
■ Security Function
Table Error Messages (Security Function)
Error message Cause Steps to take
(Login Dialog Box)
Logged in with a user name Login with a user name
You don't have permission to access
not registered in the database registered in the database
Engineering Tool.
[OK] button clicked without specifying
Invalid User name. Specify user name
user name
Entered something other than the login
Invalid Password. Enter password for the login user
user’s password
(Change Password Dialog Box) Started Change Password dialog box
You don’t have permission to access and performed password change Specify user name
Engineering Tool. procedure without entering user name
Entered a string different from
That password is invalid. Enter current password
the current password
New password is invalid.
Entered double-width characters. Enter standard-width characters
(Can not use double-width characters)
Re-entered password did not Entered a character string different from Enter same character string as
correspond to new password. the new password new password
(Account Registration Dialog Box)
Maximum number of users that can be Registered the 201st user Register only up to 200 users
registered is 200.
Entered a user name already registered
User name already registered. Enter a unique user name
(for example, MASTER)
Entered something other than double- Enter double-width characters,
Invalid user name.
width character, alphanumeric character, - or _ alphanumeric characters, - or _
(User Entry Dialog Box) Clicked [Delete] button without
User name is invalid. Specify user name
specifying user name
Logged in with name other than
Must login as MASTER to register or
MASTER and performed registration/ Login using MASTER
delete.
deletion Login using
Do you really want to remove
the user name? Performed a deletion

Could not update database.


Unable to remove user name. Deleted MASTER

(Project Manager) Started project manager when it is Use the project manager already started
Engineering Tool now in use. already running or delete it and then start a new one
050603E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-172

5.6.2 Export and Import Error Messages


The export and import error messages are listed in the table below.

■ Export and Import


Table Error Messages (Export and Import) (1/2)
Error message Reason Solution
Included invalid character. ‘ ' ’ was entered. Remove the ‘ ' ’.
<File Name>
‘ | ’ was entered. Remove the ‘ | ’.
The above file name is invalid.
The key (section or parameter) which
Obtain a correct Capabilities File from
should be described is sure not to exist
Section or Entry Identifier not found. the device vender or FF. Or examine
in the Capabilities File or the Device
the content of the Device Object File.
Object File.
Replace the existing database with the
Error while accessing the Project
The Database is damaged. database from the installation disk,
Database
and re-import all projects.
The Database is either being used by Close the other application, or create
Unable to open the database
another application or is damaged. a new project.
The parameter name not described in
the DDOD file exists in the Device Examine whether the block parameter
The parameter can not be interpreted
Object File (DOF file). Or the importing name of the importing Device Object
exists. Please examine the content of
processing was advanced by File is correct. Or the DD file is
the file under importing.
“DD none” though it was project which prepared then importing again.
corresponded to DD.
1. Provide the Capabilities File under a
correct directory.
The specified file is not found: 2. Set the stored directory of the
The specified Capabilities File does not
<file_name> Provide the file then Capabilities File using the
exist.
execute this function again. Environment Setting dialog.
3. Obtain the Capabilities File from the
device vender or FF.
Number of characters of the block
parameter value exceeds 255. Number of characters of the block The import of the Capabilities File is
Parameter name: <par_name> parameter value described in the continued, then input any value using
Continue? (This parameter value is Capabilities File exceeds 255. the Parameter Edit dialog.
not read)
If you want to improve the revision,
The Capabilities File with the upward The Capabilities File with the upward
you continue it. If not, stop the import
compatibility exists. File name: compatibility exists though the
process, provide the Capabilities File
<file_name> Improve the Resource Capabilities File to read when importing
used in the project then execute it
File’s revision? a project was not found.
again.
Because the block type was not 1. Continue as it is. The skipped block
The processing of this block is skipped described in the Capabilities File, the is treated as nothing.
because the block type is unknown. block information was not able to be 2. Obtain the Capabilities File from the
registered. device vender or FF.
Failed in the initialization of the DDS
(Corresponding DDOD) Set the directory path stored the
library because the directory path
The directory path stored the Capabilities File using the Environment
stored the Capabilities File was not
Capabilities File is not correctly set. Setting dialog then execute it again.
correctly set.
Error message Reason Solution
050604E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-173
Table Error Messages (Export and Import) (2/2)
Error message Reason Solution
Failed in the parameter information The process will continue without the
acquisition. (or the DD file is not found.) parameters. The block parameters
Fails to access the parameters from
Continue? can not be displayed or set. If not to
DD file.
(You can not treat parameters of this continue, importing the capabilities file
block concerned.) will be aborted.
Failed in the view information The process will continue without the
acquisition. (or the DD file is not found.) Fails to access the view information view information. Upload may fail.
Continue? from DD file. If not to continue, importing the
(Upload function may fail.) capabilities file will be aborted.
The DD file corresponding to the Obtain the DD file corresponding to
The DD file corresponding to the
selected Capabilities File does not exist. the Capabilities File used from the
Capabilities File used does not exist.
Continue without the DD file. device vender or FF.
050605E.EPS

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-174

5.6.3 Download Error Messages


The download error messages are listed in the table below.

■ Download
Table Error Messages (Download)

Error message Cause Steps to take


Generate project, restart tool and do
Internal error Database is damaged
download process again
Eliminate cause of error by referring to
Indicates that an error has occurred in
Fieldbus communication error (*1) detail information, restart tool and do
communication with the device
download process again
Indicates that an error has occurred Eliminate cause of error by referring to
FCS communication error (*2) during communication between the detail information, restart tool and do
Fieldbus Engineering Tool and the ACF11. download process again
Re-input the correct device ID
Invalid Device ID. (<Other Device ID>) Device ID in database differs from
(shown in <Other Device ID>),
"User Error (2)" (*3) actual device ID
then do download process again
Physical device tag name in database Re-input the correct physical device
Invalid Physical Device Tag.
differs from actual physical device tag tag name (shown in <Other PDTag>),
(<Other PDTag>) "User Error (1)" (*3)
name then do download process again
Check whether the device to download
The fieldbus device subject to download
exists on the fieldbus, then perform
does not exist on fieldbus
download process again
Can’t find device to download to
The node address in the database Re-input the correct node address,
differs from the actual node address for execute generation and then perform
the device download process again
Check whether ODRevisions for
device and for capabilities file match,
then do download process again
VFD OdRevision in database differs
Invalid OdRevision "User Error (3)" (*3) When they are different, replace the
from actual VFD ODRevision
device or perform engineering again
using the corresponding capabilities
file.
Re-input the correct device class
Invalid Device Class. Device class in database differs from
(shown in <Other Device class>),
(<Other Device Class>) actual device class
then do download process again
Device to download does not match Perform engineering again after replacing
Device to download differs from contents
contents of capabilities file used the device to download or obtaining a
of capabilities file
(<error factor>) capabilities file that matches the device
050606E.EPS

*1: Displays contents of No. 1 to No. 3 in “Table Others” discussed later.


*2: Displays contents of No. 4 in “Table Others” discussed later.
*3: Displays contents in “Table User Errors” discussed later.

Detail information is added to the error messages concerning download. The detail informa-
tion includes data that is useful for specifying the location of the error generated during
downloading.
Particularly for fieldbus communication errors, the error class and error code (class_code)
specified by Foundation fieldbus are attached and using them, it is possible to pinpoint the
cause of the error.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-175
● Detail Information
Table Details of Error Messages (Download) (1/3)

Error code
Error message Details (part 1) Details (part 2) (*1)
(0x)
See 1 or 2 of "Negative
Fieldbus communication error 801260 acknowledgment"
See 1, 2, or 3 of "Other"
Download initializing
FCS communication error 801029 See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 1 or 2 of "Negative
Fieldbus communication error 801260 acknowledgment"
See 1, 2, or 3 of "Other"
FCS communication error 801029 Acquiring node addresses
See 4 of "Other"
for all devices in the fieldbus
Device subject to download does not exist. 801261
Other error See 5 of "Other"
Internal error
code
See 4 of "Negative acknowledgment"
Fieldbus communication error 801260
See 1, 2, or 3 of "Other"
FCS communication error 801029 See 4 of "Other"
Acquiring physical device
Invalid Physical Device Tag. tag name and device ID
801261
(<Other PDTag>) "User Error (1)" (*2) when node address
=<node address>
Invalid Device ID. (<Other Device ID>) See 5 of "Other"
801261
"User Error (2)" (*2)
Other error
Internal error
code
See 3 or 5 of "Negative
Fieldbus communication error 801260 acknowledgment"
Establishing communication See 1, 2, or 3 of "Other"
path for the <physical
FCS communication error 801029 See 4 of "Other"
device tag name> (when
VCR=<VFD number>)
Invalid OdRevision "User Error (3)" (*2) 801261 network
See 5 of "Other"
Other error
Internal error
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing <parameter name> See 1, 2, or 3 of "Other"
FCS communication error 801029 to <physical device tag name> See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing the nth (<number>)
number of FB start entry when See 1, 2, or 3 of "Other"
FCS communication error 801029 VFD to the <physical device See 4 of "Other"
tag name>=<VFD number>
Other error
Internal error See 5 of "Other"
code
Error code
Error message Details (part 1) Details (part 2) (*1)
(0x)
050607E.EPS

*1: For specifics of “Details (part 2),” see “Table Negative Acknowledgment” and “Table Others” discussed later.
*2: Displays contents in “Table User Errors” discussed later.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-176
Table Details of Error Messages (Download) (2/3)
Error code
Error message Details (part 1) Details (part 2)
(0x)
See 3, 6, 7, 8 or 9 of "Negative
Fieldbus communication error 801260 acknowledgment"
Download of <parameter See 1, 2, or 3 of "Other"
name> to <physical device
FCS communication error 801029 tag name> failed See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing LAS schedule to See 1, 2, or 3 of "Other"
FCS communication error 801029 <physical device tag name> See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 3 or 5 of "Negative
Fieldbus communication error 801260 acknowledgment"
See 1, 2, or 3 of "Other"
Establishing communication
FCS communication error 801029 path for <physical device tag See 4 of "Other"
name> (when VCR=<VFD
Invalid OdRevision "User Error (3)" (*2) 801261 number>) function block
See 5 of "Other"
Other error
Internal error
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing the nth (<number>)
number of the communication See 1, 2, or 3 of "Other"
FCS communication error 801029 path data to the <physical See 4 of "Other"
device tag name>
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing the function block
parameter <parameter name> See 1, 2, or 3 of "Other"
FCS communication error 801029 to the <physical device See 4 of "Other"
tag name>
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing the %dth number of
the link object data when See 1, 2, or 3 of "Other"
FCS communication error 801029 VFD to the <physical device See 4 of "Other"
tag name>=<VFD number>
Other error
Internal error See 5 of "Other"
code
See 3 or 5 of "Negative
Fieldbus communication error 801260 acknowledgment"
Establishing communication
path for the <physical device See 1, 2, or 3 of "Other"
FCS communication error 801029 tag name> (when VCR=<VFD See 4 of "Other"
number> network
Other error
Internal error See 5 of "Other"
code
Error code
Error message Details (part 1) Details (part 2)
(0x)
050608E.EPS

*1: For specifics of “Details (part 2),” see “Table Negative Acknowledgment” and “Table Others” discussed later.
*2: Displays contents in “Table User Errors” discussed later.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-177
Table Details of Error Messages (Download) (3/3)
Error code
Error message Details (part 1) Details (part 2)
(0x)
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Writing the <physical device See 1, 2, or 3 of "Other"
FCS communication error 801029 tag name> macro cycle See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Initializing the <physical See 1, 2, or 3 of "Other"
device tag name> macro
FCS communication error 801029 cycle See 4 of "Other"
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Changing the resource block
MODE to O/S when VFD to See 1, 2, or 3 of "Other"
FCS communication error 801029 <physical device tag name> See 4 of "Other"
=<VFD number>
Other error
Internal error See 5 of "Other"
code
See 3 or 6 of "Negative
Fieldbus communication error 801260 acknowledgment"
Restoring the resource block
MODE to AUT when VFD for See 1, 2, or 3 of "Other"
FCS communication error 801029 <physical device tag name> See 4 of "Other"
=<VFD number>
Other error
Internal error See 5 of "Other"
code
050609E.EPS

*1: For specifics of “Details (part 2),” see “Table Negative Acknowledgment” and “Table Others” discussed later.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-178
● Detail Information (user error)
Table User Error
No. Contents
1 (%s) Sets the device ID acquired using SM-Identify.
2 (%s) Sets the physical device tag name acquired using SM-Identify.
3 Device: od_revision=%d. Engineering tool: od_revision = %d
050610E.EPS

● Detail Information (negative acknowledgment)


Table Negative Acknowledgment
No. Contents
Negative Confirmation:: FMS-Service=0x%x, class_code=0x%x, add_detail=0x%x, add_description=%s,
1
vfd_number=0x%x index=0x%x
2 Negative Confirmation:: NMA-Service=0x%x, class_code=0x%x, add_detail=0x%x, add_description=%s
3 Abort Indication:: FMS-Service=0x%.2x, local=0x%x, abort_id=0x%x, reason=0x%x, detail_length=%d, detail=%s
4 Negative Confirmation:: SM-Service=0x%x,rc=0x%x, add_detail=0x%x
Negative Confirmation:: FMS-Service=0x0, class_code=0x%x, snd_len=0x%x, rcv_len=0x%x,
5
supported_features=0x%.2x0%.2x0x%.2x0x%.2x0x%.2x0x%.2x0x%.2x0x%.2x
6 to 9 Negative Confirmation:: FMS-Service=0x%x, class_code=0x%x, add_detail=0x%x, add_description=%s
050611E.EPS

FMS_service:
FMS service code (42:OD_READ_LOC, 38:ABORT, 0:INITIATE, 5:WRITE, 61:GEN_INIT_DOWNL_SEQ,
62:GEN_DOWNL_SEG, 63:GEN_TERM_DOWNL_SEQ)
NMA_service: NMA service code (36:MGMT_READ)
class_code: FMS service or NMA service error code
SM_service: SM service code (3:SM_IDENTIFY)
rc: SM service reason code

SEE ALSO
• For details on the class_code for FMS_Service and NMA_Service, see the Foundation Fieldbus speci-
fication.
• When the class_code for FMS_Service or NMA_Service is 0x0800, see 4.12.2, “Function Block Services
and Protocol” found in “Function Block Application Process Part 1,” based on the add_detail value. Even
more detailed information can be obtained from it.
• For details on the SM_Service rc, see the Foundation Fieldbus specification.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool> 5-179
● Detail Information (Other)
Table Other
No. Contents
1 Wrong Confirmation:: comm_ref = 0x%x, layer = 0x%.2x,service = 0x%.2x, primitive = 0x%.2x
2 Wrong Indication:: comm_ref = 0x%x, layer = 0x%.2x,service = 0x%.2x, primitive = 0x%.2x
3 Reject receive:: comm_ref = 0x%x, layer = 0x%.2x,service = 0x%.2x, primitive = 0x%.2x
4 EventContent = 0x%x, Event Details = 0x%x, Supplement = %s or Errcode = 0x%x
5 Detail = 0x%x
050612E.EPS

No. 4 error occurs mainly because the ACF11 or device to download is not physically
connected or because configuration of the VCS or ACF11 has not been performed cor-
rectly.
The following explains the causes of typical errors and their corrective measures.
• EventContent=0x170306, EventDetail=0xC7BB Supplment=dReturn=0x252B
The ACF11 is not installed or the power supply to the ACF11 is OFF. Install the ACF11
in the proper position.
• EventContent=0x170304, EventDetail=0x12 Supplment= (or EventContent=)
0x170304, EventDetail=0x12 Supplment=0x34
The HIS and ACF11 or the master PC and ACF11 are logically unconnected because
of a failure in the FCS or control bus. Check the connection.
• EventContent=0x170306, EventDetail=0xC7AA Supplment=dReturn=C5D8
Generation for the ACF11 is not completed correctly. Because this means that engi-
neering has not been performed, the ACF11 cannot recognize the device to download.
Follow the engineering procedure to download to the ACF11.
• EventContent=0x170306, EventDetail=0xC793 Supplment=dReturn=0000
FCS on-demand communication resources have not been released. This situation
occurs when the communication path between the HIS and FCS or between the
master PC and FCS is interrupted during download or when operation of the HIS or
master PC is stopped due to a power outage.
The on-demand communication resources are released automatically after one
minute has elapsed. Execute download after waiting about a minute.
• Errcode=0x170004
The project to download is not defined. Set the correct project name with the control
bus configuration definition window.

IM 33S05P10-01E 6th Edition : Jun.16,2008-00


<5. Fieldbus Engineering Tool>