F ™ Fieldbus Toolkit For Field Communicator Device Developers

FOUNDATION™ Fieldbus
Toolkit for Field

Communicator Device
Developers
User Manual
Field Communicator Fieldbus

Application, Revision 6.1
April 2012
FOUNDATION Fieldbus Toolkit for Field Communicator Device Developers
Disclaimer
The contents of this publication are presented for informational
purposes only, and while every effort has been made to ensure their
accuracy, they are not to be construed as warranties or guarantees,
express or implied, regarding the products or services described
herein or their use or applicability. We reserve the right to modify or
improve the designs or specifications of such products at any time
without notice.
Copyright and Trademark Information

©Emerson Process Management. 2012. All Rights Reserved. Printed
in the USA.
FOUNDATION™ fieldbus is a mark of the Fieldbus Foundation of
Austin, Texas, USA.
AMS and PlantWeb™ are marks of one of the Emerson group of
companies.
All other marks are property of their respective owners.
Document History
Date Description
March 2004 Original toolkit release, software version 1.1.1
August 2004 Toolkit version 2.0.1
July 2007 Toolkit version 4.0.0

Support Block Instantiation. Works with
Foundation fieldbus Tokenizer Rev 4 and 5.
Supports Common File Format specifications
1.5 and 1.7.
December 2009 Toolkit version 5.0.0

Supports both 375 and 475 Field
Communicators. Supports Common File
Format specification 1.8 .
February 2012 Toolkit version 6.1.0

Supports all minor versions of the Common File
Format specification version 1 (1.x)
ii ©Emerson Process Management. 2012

Table of Contents
Disclaimer ...................................................................................... ii
Copyright and Trademark Information .......................................... ii
Document History .......................................................................... ii
Introduction Introduction..................................................................................... 1-1
Overview..................................................................................... 1-1
System Requirements ................................................................. 1-1
Files............................................................................................. 1-3
References................................................................................... 1-4
Toolkit Questions........................................................................ 1-4
Using the Toolkit ............................................................................ 2-1
Install the FOUNDATION Fieldbus DD Developer Kits ............... 2-1
Write and Tokenize Your Device Description............................ 2-1
Create Your CFF File ................................................................. 2-1
Generate the FOUNDATION fieldbus DDP .................................. 2-2
Load the FOUNDATION fieldbus DDP......................................... 2-5
Importing FOUNDATION fieldbus DDPs into the Easy Upgrade
Utility PC Database .................................................................... 2-6
Downloading FOUNDATION fieldbus DDPs to the Field
Communicator through IrDA...................................................... 2-7
Downloading FOUNDATION fieldbus DDPs to the 475 Field
Communicator through Bluetooth .............................................. 2-9
Using a Card Reader ................................................................... 2-9
Menus ....................................................................................... 2-10
Methods .................................................................................... 2-11
Block Items Definitions ............................................................ 2-12
Read/Write Parameter Access .................................................. 2-12
Block Instantiation .................................................................... 2-12
Rules for Displaying Parameter Labels .................................... 2-13
Supported EDDL Features ........................................................ 2-14
Help in DD................................................................................ 2-14
DD Restrictions and Known Issues ................................................ 3-1
DD Restrictions .......................................................................... 3-1
Issue with Refresh Actions for Charts and Graphs ..................... 3-2
DD Testing and Registration .......................................................... 4-1
Testing Guidelines ...................................................................... 4-1
DD Registration .......................................................................... 4-2
Glossary .......................................................................................... 5-1
©Emerson Process Management. 2012. iii

iv ©Emerson Process Management. 2012

Section 1 Introduction
Overview
This toolkit is used to develop Device Driver Packages (DDPs) for
FOUNDATION fieldbus devices for use on the 375 or 475 Field
Communicator. The toolkit takes output from the FOUNDATION
fieldbus Device Description Integrated Development Environment
(not included) and processes it for use on the Field Communicator.
The toolkit consists of the following components:
• Field Communicator FF DD Package Wizard
• FOUNDATION Fieldbus Toolkit for Field Communicator Device
Developers User Manual (this document)
System Requirements
PC Hardware Requirements
• 1 GB disk space - More space may be required as you add file
packages
• 256MB RAM
• 866MHz processor
• Windows XP Professional SP2 or higher, Windows Vista
Business SP1 or higher, or Windows 7 Professional (32 or 64
bit)
PC Software Requirements
Note: The following software is not included in the toolkit:
©Emerson Process Management. 2012. 1-1

• FOUNDATION fieldbus Device Description Integrated

Development Environment (DD-IDE) and Device Description
Library Subscription version 1.2 or higher. This supports Device
Description Language Specification Release 5.2 (FF-900
Revision FS 5.2).
• Easy Upgrade Utility version 3.6 or higher for transferring DDs
to the Field Communicator
Field Communicator Requirements

• A 375 or 475 Field Communicator running System Software
version 3.6 or higher. This corresponds with the Field
Communicator Fieldbus Application 6.1.
• Easy Upgrade license
• FOUNDATION fieldbus license
DD File Transfer Requirements

Use one of the following:
• Secure Digital card reader – The fastest form of file transfer
• Bluetooth adapter – Use one of the following:
o SMK-Link VP6494 USB 2.0 adapter
o Kensington 33902 Bluetooth USB Micro Adapter
o Internal Bluetooth adapters in the Panasonic Toughbook
CF-29 and CF-30 (only on Windows XP and Vista).
Bluetooth adapters must use the Windows Bluetooth software

and drivers included with the Microsoft Windows operating
system. If other Bluetooth drivers are installed, you may need to
set up the adapter to use the Windows Bluetooth drivers. See the
Easy Upgrade Utility online Help for more information.
• IrDA port or adapter - If your PC does not have a built-in IrDA
port, use one of the following IrDA adapters:
o ACTiSYS -IR2000UL USB to IrDA adapter
o ACTiSYS IR2002UL USB to IrDA adapter
Email any questions concerning upgrading/renewing Field

Communicator licenses to
FieldCommunicatorToolkit@emerson.com
1-2 ©Emerson Process Management. 2012

Files
The toolkit consists of the following files:
• Readme.pdf - Readme file in PDF format
• License.pdf - License file in PDF format
• FieldCommunicatorFFToolkit.pdf - This document in PDF
format
• Facsimile Lead Sheet.pdf – Field Communicator FF Device
Description Production Approval Form
• FieldCommunicatorFFDDPWizard.exe – Field Communicator
FF DDP wizard
• TazTskGen.exe – Field Communicator FF DD stack information
generator is a tool used by the Field Communicator FF DDP
wizard
• GenPackedSym.exe – Field Communicator FF packed symbol
file generator is a tool used by the Field Communicator FF DDP
wizard
• TazCifGen.exe – Field Communicator capability information file
(CIF) generator is a tool used by the Field Communicator FF
DDP wizard
• DDPEngine.dll – Field Communicator FF DDP Engine DLL is a
library used by the Field Communicator FF DDP wizard
• ManufacturerIDTable.xml - List of all manufacturer names and
IDs used by the Field Communicator FF DDP wizard
• PVECommonTools.dll - Common tools DLL is a library used by
the Field Communicator FF DDP wizard
• PVETranslator.dll - Translation DLL is a library used by the
Field Communicator FF DDP wizard
• zlib.dll - Zip utility DLL is a library used by the Field
Communicator FF DDP wizard
• PVEStandard.dct - Standard translation dictionary (note: this is
not the FOUNDATION fieldbus dictionary file).
• 375FFDDPWizard.dct – Field Communicator FF DDP Wizard
dictionary
• TAZDDWizard.hlp - Field Communicator FF DDP Wizard
online help file
• TAZDDWizard.cnt - Field Communicator FF DDP Wizard
online help content file

References
FOUNDATION Fieldbus Specification – Device Description Language
(document number: FF-900, Revision FS 5.1)
FOUNDATION Specification Common File Format (document
number: FF-103, Revision 1.9)
Toolkit Questions
Email any questions concerning the use of this toolkit to:
FieldCommunicatorToolkit@emerson.com.

Section 2 Using the Toolkit
Install the FOUNDATION Fieldbus DD

Developer Kits
Load the FOUNDATION Fieldbus Device Description Tokenizer Kit
and Device Description Library Subscription on your PC, following
the instructions provided with the kits.
Write and Tokenize Your Device

Description
Create your device description and tokenize it, following the
instructions provided with the FOUNDATION Fieldbus Tokenizer Kit.
See the DD Constructs section for information on DDL constructs
specific to the Field Communicator.
Create Your CFF File

Create your CFF file following the instructions provided in the
FOUNDATION Specification Common File Format.

Generate the FOUNDATION fieldbus DDP

The device developer uses the Field Communicator FF DD Package
Wizard to create the FOUNDATION fieldbus DDP. The inputs of the
Field Communicator FF DD Package Wizard are .ffo (or .ff5), .sym
(or .sy5), and .cff files. The outputs are the .fdd and .fhd files, which
comprise the FOUNDATION fieldbus DDP.
Before running the Field Communicator FF DD Package Wizard,
store the .ffo (or .ff5), .sym (or .sy5), and .cff files previously created
in a folder on the PC. Store only one set of files in your folder. The
DDP wizard can only work on one set of files at a time.
1. Start the Field Communicator FF DD Package Wizard by
clicking the “Field Communicator FF DD Package Wizard” icon
on your PC desktop or by selecting Start | Programs | Field
Communicator FF Toolkit | Field Communicator FF DD
Package Wizard.
2. Click Next.
3. Enter or browse to the location of your input files.

4. Click Next.
5. If necessary, modify the device name that will be encoded in the
DD package by the FF DDP wizard.

The default name chosen by the wizard is based on the 4-hex-

digit device type as defined in your CFF file. Up to 12 ASCII
characters can be used for the device name. This device name is
shown with the DD in the Easy Upgrade Utility, in the DD list of
the Field Communicator Fieldbus Application, and also at the
top of each menu while using the Field Communicator Fieldbus
Application to communicate with your device.
6. Click Next.
7. The DD Package Wizard displays a summary of the DDP it will
create. Click Back to make corrections or click Finish to create
the DDP.
The output .fdd and .fhd files are stored in the same folder with the
input files. The naming convention used for these files is the
combination of the manufacturer ID (6 hex digits), the device ID (4
hex digits), the device revision (2 hex digits), and the device
description revision (2 hex digits).


Load the FOUNDATION fieldbus DDP

Device developers must install the Easy Upgrade Utility to transfer
DDPs from a PC to a Field Communicator. All DDPs created by
device developers appear on the Field Communicator and in the Easy
Upgrade Utility as Untested. Only after a DDP is submitted and
release approved in writing by the developer, does Emerson Process
Management distribute the DDP as “Tested”.
NOTE: Do not run the Field Communicator FF DD Package
Wizard and Easy Upgrade Utility at the same time.

Importing FOUNDATION fieldbus DDPs

into the Easy Upgrade Utility PC
Database
After you create FOUNDATION fieldbus DDPs, you must import them
into the Easy Upgrade Utility PC database.
1. Launch the Easy Upgrade Utility by selecting Start | All
Programs | Field Communicator Easy Upgrade Utility | Field
Communicator Easy Upgrade Utility.
2. In the Utilities window, click Import DDs from a local source.
3. Browse to the location of the FOUNDATION fieldbus DDPs.
4. Click OK after the desired FOUNDATION fieldbus DDPs are

found.
The Easy Upgrade Utility adds the selected FOUNDATION
fieldbus DDPs into the PC database. If there is a FOUNDATION
fieldbus DDP with the same filename already in the PC database,
the Easy Upgrade Utility compares the timestamp in the DDPs
and imports the DDP only if a newer timestamp is found.

Downloading FOUNDATION fieldbus

DDPs to the Field Communicator
through IrDA
Please see the System Requirements section for information about
IrDA adapters.
1. Place the Field Communicator into Listen For PC mode, and
align the Field Communicator IrDA port with the PC IrDA port.
Refer to the Field Communicator User’s Manual for more
information.
2. Launch the Easy Upgrade Utility.
3. In the Upgrade window, set the Connection type to IrDA and
click Connect. When the Field Communicator is connected, the
following screen is displayed.
4. Click More Options and select the DDs tab.

NOTE: To see all tested and untested DDs in the PC database,

select the Show all DDs option in the Settings window.
5. Expand the PC database and the Field Communicator trees in the

DDs tab.
If you previously downloaded this DDP to the Field
Communicator, you must remove it from the Field
Communicator. Then select the device DDP from the PC
database, and click the >>> button (download) to send the DDP
to the Field Communicator.
6. After you move the new DDPs from your PC Database to the
Field Communicator, shut down and restart the Field
Communicator. You can now test and use the new DDPs.
NOTE: Performing steps 5 and 6 ensures that the correct version of
the DDP (i.e., the most recent one you downloaded) is
installed by the Field Communicator Fieldbus Application.

Downloading FOUNDATION fieldbus

DDPs to the 475 Field Communicator
through Bluetooth
Using the Bluetooth interface is similar to using the IrDA interface to
transfer files, but the Bluetooth interface has faster upload and
download speeds than IrDA. See the System Requirements section
for information about supported Bluetooth adapters.
NOTE: The 375 Field Communicator does not support Bluetooth
communication. The 475 Field Communicator must be
licensed for Bluetooth to use this functionality.
1. Place the 475 Field Communicator into Listen For PC mode and
make sure Bluetooth is selected as the connection type. Refer to
the Field Communicator User’s Manual for more information.
3. In the Upgrade window, set the Connection type to Bluetooth
and click Connect. See the Easy Upgrade Utility Online Help
for more information about Bluetooth setup.
4. Follow steps 4 to 6 of the Downloading FOUNDATION fieldbus
DDPs to the Field Communicator through IrDA topic to
complete the process.
Using a Card Reader

A device developer can use a USB Secure Digital (SD) card reader
to transfer system software updates and DDPs from the Easy
Upgrade Utility to the Field Communicator System Card. Using a
card reader is similar to using the IrDA interface to transfer files, but
a card reader has faster upload and download speeds than IrDA and
Bluetooth. Please note that some upgrades may require a card reader.
See the System Requirements section for information about
supported card readers.

2. Attach the card reader to your PC, if you are using a USB card
reader.
3. Insert the Field Communicator System Card into the card reader.
4. In the Upgrade window, set the Connection type to Card Reader
and click Connect.
5. If the Select a drive for your Card Reader dialog box appears,
click Browse and select the card reader. Click OK.
6. After the System Card is connected, the Easy Upgrade Utility
will default to this drive in future connection attempts.

7. Follow steps 4 to 6 of the Downloading FOUNDATION fieldbus

DDPs to the Field Communicator through IrDA topic to
complete the process.
More information about using a card reader, such as what tasks
cannot be done by a card reader, is available in the Easy Upgrade
Utility online Help.
Menus
Menus can be displayed as block menus or device-level menus. If
device-level menus are defined in the DD, they are used by the Field
Communicator.
Device-level Menus
Device-level menus are not associated with any one block and may
not be listed in any block's MENU_ITEMS list.
To display device-level menus, define root menus in the DD. There

can be as many as 3 device-level root menus with the following
names:
hh_device_root_menu
hh_process_variables_root_menu
hh_diagnostic_root_menu
There can be any level of device-level menus under each root menu.
In a device-level menu, references to block items must use cross

block syntax, which explicitly specifies the block to which the item
belongs. This includes references to parameters, local parameters,
menus, methods, charts, graphs, and grids. To be cross-block
referenced in a device menu, a block item must be included in the
block's PARAMETERS, LOCAL_PARAMETERS, MENUS,
METHODS, CHARTS, GRAPHS, or GRIDS attribute lists. See FF-
900, section 2.5 for information on the block attributes.
Example cross block references in a menu:

__resource_block_2[0].PARAM.MODE_BLK.ACTUAL,
transducer_block[0].PRIMARY_VALUE.STATUS
See FF-901, section 4.5.5 for more information on device-level

menus.
Block Menus
A block menu is associated with a particular block. A DD may

define menus for some or all blocks in a device, or it may have no
block menus defined. To display block menus, the DD should define
a single root menu with a name beginning with "Menu_Top" (case
sensitive). Examples:

Menu_Top_TB, Menu_Top_AI
The block root menu must be listed in the block's MENU_ITEMS.
If block menus are not defined for a particular block, the Field
Communicator uses a set of default menus to group the block
parameters and methods.
a) If there is just one menu in the MENU_ITEMS list, that menu is
chosen as the root menu.
b) If there are multiple menus in the MENU_ITEMS list, and one of
the menus in the list includes the string "Menu_Top" in its symbol
name, that menu is chosen as the root menu.
c) If there are multiple menus in the MENU_ITEMS list, but no
menu's name includes "Menu_Top", all the menus in the list are
combined to create a single root menu.
d) If the DD does not declare any MENU_ITEMS for a block, the
Field Communicator uses its own default menus to group the block
parameters.
Methods
Methods can be classified as device-level methods or block methods.
Device-level Methods
Device-level methods may be referenced only in a device-level

menu. They may not be listed in any block's MENU_ITEMS. To
access block parameters, a device-level method must use builtins that
have call arguments that explicitly specify the block. Examples are
display_message2(), edit_device_value2(), and get_float_value2().
See FF-900, Appendix B for information on method builtins.
Block Methods
Block methods may be referenced in a block menu or in a device-
level menu using cross block references.
If a block has no DD menus defined and no menus containing
methods, the Field Communicator also groups DD methods in
separate submenus based on each method’s CLASS attribute as
defined in the DD. The submenu “Diagnostic Methods,” contains all
methods with the Class DIAGNOSTIC attribute. If no methods meet
this class criteria, the submenu “Diagnostic Methods” is not
displayed. Submenu, “Calibration Methods,” contains all methods
not listed in the “Diagnostic Methods” submenu, and has one or
more of the following class attributes: SERVICE, OPERATE,
ALARM, TUNE. If no methods meet this class criteria, the submenu
“Calibration Methods” is not displayed. If neither of these class
criteria is met, submenu “Methods” contains all of the block’s
methods.

Block Items Definitions

FOUNDATION fieldbus DDL specifications require that all User
methods and Abort methods must be listed in the block’s
METHOD_ITEMS attribute. The Field Communicator requires that
at least the User methods must be listed in the block’s
METHOD_ITEMS attribute.
Read/Write Parameter Access

In the Field Communicator Fieldbus Application, read/write
parameter access is only supported for the Resource, Transducer, and
I/O blocks. All other function blocks are read-only.
The handling of the RESTART parameter in the resource block has
been overridden by the Field Communicator to be read-only. This
parameter should only be modified from within a method.
Block Instantiation
The Field Communicator Fieldbus Application lets you
instantiate/delete function blocks and transducer blocks in devices
that support block instantiation. The Field Communicator Fieldbus
Application uses information contained in the device CFF file to
determine if there are instantiable block types in the device.

Rules for Displaying Parameter Labels

The Field Communicator Fieldbus Application uses the following
rules for displaying a parameter label:
1. If the parameter is a simple variable:
a. Use the Description field of the Block Parameter list
member, if it is not empty.
b. Otherwise, use the Label attribute of the DD variable.
2. If the parameter is an array:
b. Otherwise, use the Label attribute of the DD array’s
associated variable.
The resulting string has [index] appended for each Array
element, where index is the Array index.
3. If the parameter is a record:
The Full Label for a record member is displayed in the following
form:
Parameter Label Member Label
For the Parameter Label:
b. Otherwise, use the Label attribute of the DD record.
For the Member Label:
a. Use the Description field of the record member, if it is not
empty.
b. Otherwise, use the Label attribute of the member DD
variable.

Supported EDDL Features

The supported EDDL features are listed in the “TP 206 - Field
Communicator EDDL Feature Set” document. This document is
saved in the Field Communicator FOUNDATION fieldbus Toolkit
Install folder at C:\Program Files\ Field Communicator FF Toolkit.
Help in DD
Customer feedback indicates that a robust Help implementation in
DD is very beneficial. The Field Communicator group recommends
device developers create Help for their DDs.

Section 3 DD Restrictions and Known
Issues
DD Restrictions
The following FOUNDATION fieldbus DDL constructs and variable
attributes are not supported in the Field Communicator:
• Edit Displays construct
• Programs construct
• Domains construct
• Response Codes construct
• Read/Write Timeout variable attributes
• Pre/Post Edit Actions variable attributes
• PreWrite Actions variable attribute

Issue with Refresh Actions for Charts

and Graphs
There is an issue with the Field Communicator Fieldbus Application
that prevents a user from performing User Interface actions while a
method is executing. If a chart has refresh_actions methods defined
for its source members, the action methods execute at every chart
cycle time interval. Device developers using refresh_actions should
set a cycle time interval that allows the user to perform UI actions
after the methods complete.
The same issue applies to refresh actions defined for a graph's
waveform members.

Section 4 DD Testing and Registration
Testing Guidelines
Device developers are responsible for testing the device and device
description with the Field Communicator to ensure operational
integrity and quality.
When testing the DD with the Field Communicator, the device
developer should check every block. In each block, the device
developer must ensure:
• Menus (either the DD menus or the Field Communicator default
menus) are displayed correctly.
• Parameters in each menu are displayed correctly.
• Read/write access to a parameter is correct.
• Methods can be run correctly.
When testing a device with the Field Communicator, the device
developer should check the following:
• The device is correctly identified on the live list.
• The block list correctly shows all the blocks in the device.
• The block list correctly shows the actual modes of all the blocks.
• The Scheduling menu under the block list allows the Field
Communicator to successfully schedule the I/O blocks of the
device.

• The Detail menu shows the device ID and device revision

correctly and allows successful changing of both the device tag
and the device node address.
• The information shown on the Advanced submenus is correct for
the device.
The device developer may discover incorrect behavior not caused by
the device description or the device (i.e., it appears to be a Field
Communicator issue). Email the issue to
FieldCommunicatorToolkit@emerson.com.
DD Registration
When the device developer is satisfied with the amount of Field
Communicator testing performed on the DD, the tested DD should
be registered with the Fieldbus Foundation. After the tested DD has
been registered, the device developer should sign the Field
Communicator FF Device Description Production Approval
Form (Facsimile Lead Sheet.pdf). This form is saved in the Field
Communicator FOUNDATION fieldbus Toolkit Install folder at
C:\Program Files\ Field Communicator FF Toolkit. The Production
Approval Form indicates that the development and test process
associated with DD files has been successfully completed and the
DD is ready for release to a production environment.
Only after the signed Field Communicator FF Device Description
Production Approval Form has been received by Emerson Process
Management is the DD integrated into the next Field Communicator
release as “Tested.” If the DD is not marked as “Tested,” whenever it
is accessed during run time, the Field Communicator displays the
warning message:
“This Device Description may not have been tested with this version
of Field Communicator software. Do you want to proceed with this
DD anyway?”

Glossary
Field Communicator Handheld communicator made by

Emerson Process Management. This
may be a 475 or 375 Field
Communicator
DD Device Description
DDL Device Description Language
DDP Device Driver Package. A set of files
representing a device. This consists of a
.fdd binary file and a .fhd header file
describing the individual device.
Easy Upgrade Utility The abbreviated name for Field
Communicator Easy Upgrade Utility
FF FOUNDATION fieldbus
IrDA Infrared Data Association
USB Universal Serial Bus

F ™ Fieldbus Toolkit For Field Communicator Device Developers

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

F ™ Fieldbus Toolkit For Field Communicator Device Developers

Încărcat de

Drepturi de autor:

Formate disponibile

FOUNDATION™ Fieldbus

Toolkit for Field

Field Communicator Fieldbus

Copyright and Trademark Information

March 2004 Original toolkit release, software version 1.1.1

August 2004 Toolkit version 2.0.1

July 2007 Toolkit version 4.0.0

December 2009 Toolkit version 5.0.0

February 2012 Toolkit version 6.1.0

ii ©Emerson Process Management. 2012

©Emerson Process Management. 2012. iii

iv ©Emerson Process Management. 2012

©Emerson Process Management. 2012. 1-1

• FOUNDATION fieldbus Device Description Integrated

Field Communicator Requirements

DD File Transfer Requirements

Bluetooth adapters must use the Windows Bluetooth software

Email any questions concerning upgrading/renewing Field

1-2 ©Emerson Process Management. 2012

©Emerson Process Management. 2012. 1-3

1-4 ©Emerson Process Management. 2012

Install the FOUNDATION Fieldbus DD

Write and Tokenize Your Device

Create Your CFF File

©Emerson Process Management. 2012. 2-1

Generate the FOUNDATION fieldbus DDP

3. Enter or browse to the location of your input files.

2-2 ©Emerson Process Management. 2012

The default name chosen by the wizard is based on the 4-hex-

©Emerson Process Management. 2012. 2-3

2-4 ©Emerson Process Management. 2012

Load the FOUNDATION fieldbus DDP

©Emerson Process Management. 2012. 2-5

Importing FOUNDATION fieldbus DDPs

3. Browse to the location of the FOUNDATION fieldbus DDPs.

4. Click OK after the desired FOUNDATION fieldbus DDPs are

2-6 ©Emerson Process Management. 2012

Downloading FOUNDATION fieldbus

4. Click More Options and select the DDs tab.

©Emerson Process Management. 2012. 2-7

NOTE: To see all tested and untested DDs in the PC database,

5. Expand the PC database and the Field Communicator trees in the

2-8 ©Emerson Process Management. 2012

Downloading FOUNDATION fieldbus

Using a Card Reader

1. Launch the Easy Upgrade Utility.

©Emerson Process Management. 2012. 2-9

7. Follow steps 4 to 6 of the Downloading FOUNDATION fieldbus

To display device-level menus, define root menus in the DD. There

In a device-level menu, references to block items must use cross

Example cross block references in a menu:

See FF-901, section 4.5.5 for more information on device-level

A block menu is associated with a particular block. A DD may

2-10 ©Emerson Process Management. 2012

The block root menu must be listed in the block's MENU_ITEMS.

Device-level methods may be referenced only in a device-level

©Emerson Process Management. 2012. 2-11

Block Items Definitions

Read/Write Parameter Access

2-12 ©Emerson Process Management. 2012

Rules for Displaying Parameter Labels

©Emerson Process Management. 2012. 2-13

Supported EDDL Features