B0400EF - Foxboro

I/A Series® System
Extended Frame
Services 2.3 and
I/A Series
Communication DTMs
B0400EF
Rev H
November 30, 2011
Invensys, Avantis, Foxboro, FoxCom, I/A Series, the Invensys logo, and Triconex are trademarks of
Invensys plc, its subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.
Copyright 2003 - 2011 Invensys Systems, Inc.

All rights reserved
SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Invensys Systems, Inc. supplied software supported by this documentation, you
should read and understand the following information concerning copyrighted software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Invensys Systems, Inc. will no longer provide you
with support services and assumes no further responsibilities for your system or its
operation.
2. All software issued by Invensys Systems, Inc. and copies of the software that you are
specifically permitted to make, are protected in accordance with Federal copyright
laws. It is illegal to make copies of any software media provided to you by
Invensys Systems, Inc. for any purpose other than those purposes mentioned in the
software license.
Contents
Figures................................................................................................................................... vii
Tables.................................................................................................................................. xiii
Preface................................................................................................................................... xv
Who Should Read This Book .................................................................................................. xv
What You Should Know ......................................................................................................... xv
Revision Information .............................................................................................................. xv
Database Migration and Software Upgrades .......................................................................... xvii
100 Series FBM Migration ............................................................................................... xvii
PACTware Upgrade ......................................................................................................... xvii
Reference Documents .......................................................................................................... xviii
1. Extended Frame Services 2.3 ............................................................................................. 1

Overview ................................................................................................................................... 1
Device DTMs ........................................................................................................................... 1
Using Vendor Device DTMs with EFS ................................................................................ 2
Communication DTMs ............................................................................................................ 2
PACTware Frame Application .................................................................................................. 2
Offline Configuration .......................................................................................................... 3
Configuration of Off-platform Devices ................................................................................ 3
Extended Frame Services 2.3 ..................................................................................................... 3
Valid Configurations for EFS 2.3 On-Platform Configuration ............................................. 4
EFS Hardware and Software Requirements .......................................................................... 7
I/A Series Platform Requirements .................................................................................... 7
Off-Platform Requirements ............................................................................................. 7
Invensys Condition Monitoring and Avantis.Pro ............................................................. 7
2. Software Installation.......................................................................................................... 9
Before you Begin ....................................................................................................................... 9
Installation Directory ......................................................................................................... 10
Database Migration and Software Upgrades ....................................................................... 10
100 Series FBM Migration ............................................................................................ 10
Upgrading PACTware ................................................................................................... 10
Install PACTware .................................................................................................................... 11
Install Microsoft .NET Framework 2.0 .............................................................................. 11
Install PACTware 4.0.6 ...................................................................................................... 12
Installing the HART Communication DTM ..................................................................... 19
iii
B0400EF – Rev H Contents
Install EFS and HART/FoxCom Device Manager .................................................................. 25

Install Microsoft .NET Framework 4.0 .............................................................................. 25
Install EFS and HART/FoxCom Communication Device Type Managers ......................... 28
Install the Device DTMs ......................................................................................................... 36
Invensys 3rd Party DTMs for Non Invensys HART Devices .............................................. 36
DTMs for Invensys Instruments ......................................................................................... 44
Initialize PACTware V4.0 Device Catalog .............................................................................. 45
Uninstall EFS .......................................................................................................................... 47
3. Online Configuration...................................................................................................... 51
Intelligent Field Device Connection to an I/A Series System ................................................... 52
System and Database Hierarchy ......................................................................................... 52
Workflow for Online Configuration ....................................................................................... 55
Initialize the Device Catalog and Start a Project ...................................................................... 56
Configure the FBM Communication DTM ............................................................................ 57
Configure Devices in PACTware ............................................................................................ 62
Configuring the Device ........................................................................................................... 65
Save and Close the PACTware Project .................................................................................... 67
Configuring a Router DTM with a DVC 6000 ...................................................................... 68
Important Note about EFS Scanning of Field Devices ............................................................ 68
4. Offline Configuration: Bulk Data Import ....................................................................... 69

Introduction ............................................................................................................................ 69
Creating a Worksheet for Bulk Import .................................................................................... 70
Importing the ECB Data from Excel to EFS ........................................................................... 71
Importing to a New EFS Database ..................................................................................... 72
Importing to an Existing EFS Database .............................................................................. 74
Resolving Conflicts within the Imported Data ................................................................... 77
Resolving Conflicts Between the Imported Data and the Database ..................................... 78
Validating the Offline Configuration ...................................................................................... 79
5. Offline Configuration: Manual Entry.............................................................................. 87

Introduction ............................................................................................................................ 87
Entering ECB Information ...................................................................................................... 89
Editing Manually Entered Device ECB Information ............................................................... 90
Validating the Offline Configuration ...................................................................................... 92
6. Setting Up the EFS Database Using Microsoft SQL Server 2008 .................................... 95
Selecting Microsoft SQL Server 2008 as the Database Application .......................................... 96
Create the New Database ........................................................................................................ 98
iv
Contents B0400EF – Rev H
Setting Options on EFS Database .................................................................................... 102

Set the DSN for the Microsoft SQL Server Database ............................................................ 103
Best Practices for Advanced Users ......................................................................................... 108
Programmatic Access to Device Databases ............................................................................ 108
Invensys Condition Monitoring ............................................................................................ 108
Avantis Enterprise Asset Management ................................................................................... 109
7. Configuring Devices for EFS Scanning.......................................................................... 111

HART Device Scan Considerations ...................................................................................... 112
HART Devices Connected To I/A Series HART FBMs ................................................... 113
HART Devices Connected To HART Multiplexers ......................................................... 113
Exporting the PACTware Project .......................................................................................... 114
Selecting the Devices and Setting the Frequency ................................................................... 115
Viewing Scanned Devices ................................................................................................. 117
Alphabetically Sorted Groups ...................................................................................... 117
Grouping by Communication Device .......................................................................... 119
Removing Devices ............................................................................................................ 120
Updating the Service ........................................................................................................ 120
Managing the Scan Service .................................................................................................... 120
Starting the Scan Service .................................................................................................. 121
Configuring Automatic Startup ........................................................................................ 122
Stopping DevScan ............................................................................................................ 122
Updating the Service on the Fly ....................................................................................... 123
8. Configuring and Scanning Off-Platform Devices .......................................................... 125

HART Multiplexer Example ................................................................................................. 125
Hardware and Software Prerequisites ................................................................................ 126
Getting Started ...................................................................................................................... 127
Add HART Communication and Multiplexer DTMs ........................................................... 130
Multiplexer Master DTM ................................................................................................ 131
Multiplexer Slave DTM ................................................................................................... 133
Add the DTMs for Field Devices .......................................................................................... 135
Verify Device Connections .................................................................................................... 136
Configuring the Device ......................................................................................................... 138
Important Note about EFS Scanning of Field Devices ..................................................... 139
Configure EFS Scanning ....................................................................................................... 140
Deletion of the Unused Non-I/A Series Device Objects ................................................... 142
Other Off-platform Configurations ....................................................................................... 143
MTL Multiplexer and Devices ......................................................................................... 144
HART or FoxCom Modem with a Device ....................................................................... 149
Pepperl+Fuchs Elcon 2700G HART Multiplexer with Devices ........................................ 151
v
B0400EF – Rev H Contents
Appendix A. Troubleshooting ........................................................................................... 161

Errors from the Scan Process EFS Component ...................................................................... 161
Informational Messages .................................................................................................... 161
Scanner Internal Failures .................................................................................................. 161
EFS Access Errors ............................................................................................................. 162
Processing Errors .............................................................................................................. 162
Errors from the Device Access EFS Component .................................................................... 162
Configuring the Log Settings for EFS Components .............................................................. 168
EFSObject ........................................................................................................................ 169
FBM Passthru Communication DTMs ............................................................................ 169
Device Access ................................................................................................................... 169
Configuring the Retry Count for Global Find of a CP from PT_API .................................... 170
Reading Device Parameters of the EFS Database ................................................................... 171
Case 1: Microsoft SQL Server 2008 ................................................................................. 171
Case 2: Microsoft Access .................................................................................................. 171
Restoring the Database in SQL Server 2008 .......................................................................... 172
Appendix B. Upgrading to PACTware 4.0 and EFS 2.3 .................................................... 183

Maintenance Only Applications ............................................................................................ 183
Converting PACTware Projects ........................................................................................ 184
Maintenance and Asset Management Applications ................................................................ 185
Converting PACTware Projects ........................................................................................ 187
Appendix C. Database Migration ...................................................................................... 189

Migration to Microsoft SQL Server 2008 .............................................................................. 189
Import from the Access Database ..................................................................................... 189
Set the Primary Key for the Database Tables .................................................................... 197
Set Default Values for the CommunicationDevices Table ................................................ 202
Migrating Databases from Previous Versions to EFS 2.3 ....................................................... 204
Migration Procedure When the Database is SQL Server ................................................... 205
Migration Procedure When the Database is Microsoft Access .......................................... 207
Appendix D. Choosing a Proper DTM for a Field Device................................................. 209
vi
Figures
1-1. Typical EFS Configuration with EFS Server on Enterprise Network ............................. 5
1-2. EFS Configuration with EFS Server on Platform .......................................................... 6
1-3. Alternate EFS Configuration with EFS Server on the I/A Series Network ..................... 6
2-1. Welcome Wizard ........................................................................................................ 11
2-2. License Agreement ...................................................................................................... 12
2-3. Choose Setup Language Dialog Box ............................................................................ 12
2-4. Welcome Page ............................................................................................................. 13
2-5. PACTware License Agreement .................................................................................... 14
2-6. Customer Information Page ........................................................................................ 14
2-7. Setup Type Page ......................................................................................................... 15
2-8. Choose Destination Location ...................................................................................... 16
2-9. Changing the Installation Folder ................................................................................. 17
2-10. Reviewing the Setup .................................................................................................... 17
2-11. Setup Status Page ........................................................................................................ 18
2-12. Installation Complete Wizard ..................................................................................... 19
2-13. Generic HART DTM Welcome Page ......................................................................... 20
2-14. HART DTM License Agreement ................................................................................ 21
2-15. Customer Information for the Generic HART DTM Installation ............................... 22
2-16. Ready to Install ........................................................................................................... 23
2-17. Installation Progress .................................................................................................... 24
2-18. Completing the Generic HART DTM Installation ..................................................... 25
2-19. .NET Framework 4 Setup ........................................................................................... 26
2-20. .NET Framework 4 Installation Progress .................................................................... 27
2-21. .NET Framework 4 Installation Complete .................................................................. 28
2-22. Loading the Installation Program for FDT Components ............................................. 29
2-23. EFS License Agreement Page ....................................................................................... 29
2-24. Choose Destination Location Page with Default Selection .......................................... 30
2-25. Choosing the Installation Folder ................................................................................. 31
2-26. Changing the Installation Directory ............................................................................ 31
2-27. Installation Directory Is Changed ............................................................................... 32
2-28. Installation Location Must Include \FDM_EFS .......................................................... 33
2-29. Selecting the Product Features ..................................................................................... 34
2-30. EFS 2.3 Setup Status ................................................................................................... 34
2-31. Configure EFS Database Dialog Box ........................................................................... 35
2-32. Installation of EFS and Communication DTMs is Complete ...................................... 36
2-33. Invensys Third Party DTMs Welcome Wizard ........................................................... 37
2-34. Invensys Third Party DTMs License Agreement ......................................................... 38
2-35. Invensys Third Party DTMs Customer Information ................................................... 39
2-36. Invensys Third Party DTMs - Choose Setup Type ...................................................... 39
2-37. Invensys Third Party DTMs - Customer Setup ........................................................... 40
2-38. Changing the Installation Folder ................................................................................. 41
2-39. Custom Setup for Third Party DTMs ......................................................................... 42
2-40. DTM Library Ready to Install Page ............................................................................ 43
2-41. DTM Library Installation Complete Wizard ............................................................... 44
vii
B0400EF – Rev H Figures
2-42. PACTware Project Window ........................................................................................ 46

2-43. PACTWare Device Catalog ........................................................................................ 47
2-44. Choosing Remove Option for EFS .............................................................................. 48
2-45. Confirm Uninstall ....................................................................................................... 48
2-46. Uninstallation of EFS is Complete .............................................................................. 49
3-1. HART Device Management Architecture ................................................................... 51
3-2. EFS Displaying I/A Series Hierarchy ........................................................................... 53
3-3. Configuring Devices for Maintenance and Tuning Online ......................................... 55
3-4. PACTware Project Window ........................................................................................ 56
3-5. PACTWare Device Catalog ........................................................................................ 57
3-6. Device for HOST PC ................................................................................................. 58
3-7. FBM Communication DTM Parameters .................................................................... 59
3-8. Network Object Selection Dialog Box ......................................................................... 60
3-9. FBM Communication DTM Parameters .................................................................... 61
3-10. Dialog Box Shows Four FBM Channels ...................................................................... 62
3-11. Adding a Device DTM ............................................................................................... 63
3-12. Configuring the Device DTM .................................................................................... 64
3-13. Verifying Communications DTM ............................................................................... 65
3-14. Editing the Slave Device Online .................................................................................. 67
4-1. Device Configuration Starting with Bulk Data Import ................................................ 70
4-2. Entering ECB Information in the Excel Spreadsheet ................................................... 71
4-3. Parameter Dialog Box for a New FBM ........................................................................ 72
4-4. Open Dialog ............................................................................................................... 73
4-5. Select Device in PACTware ........................................................................................ 74
4-6. Updating the EFS Database with Bulk Imports ........................................................... 75
4-7. Offline Configuration Dialog Box ............................................................................... 76
4-8. EFSBulkImport.log, Yes Selected in the Offline Configuration Dialog Box ................ 76
4-9. EFSBulkImport.log, No Selected in the Offline Configuration Dialog Box ................ 77
4-10. Incremental Validation of an Offline Configuration ................................................... 80
4-11. Network Object Selection Dialog Box ......................................................................... 81
4-12. Offline Configuration Dialog Box ............................................................................... 81
4-13. EFSValidate.log, Yes Selected in the Offline Configuration Dialog Box ...................... 83
4-14. EFSValidate.log, No Selected in the Offline Configuration Dialog Box ...................... 83
4-15. Log file for Parent and Child Device ECB Mismatch .................................................. 84
5-1. Device Configuration Starting with Manual ECB ....................................................... 88
5-2. Entering ECB Names .................................................................................................. 89
5-3. Manually Entering Changes to EFS Database ............................................................. 90
5-4. Offline Comparison Dialog Box ................................................................................. 91
6-1. Welcome Page ............................................................................................................. 96
6-2. Configure EFS Database Dialog Box ........................................................................... 97
6-3. Maintenance Complete Page ....................................................................................... 97
6-4. Creating a New Database ............................................................................................ 98
6-5. Database Properties ..................................................................................................... 99
6-6. Microsoft SQL Server Management Studio ................................................................. 99
6-7. Opening the Login - New Window ........................................................................... 100
6-8. Login Window for a New Database .......................................................................... 101
6-9. User Mapping Page ................................................................................................... 102
6-10. Database Properties Pane .......................................................................................... 103
viii
Figures B0400EF – Rev H
6-11. ODBC Data Source Administrator ........................................................................... 104

6-12. Create New Data Source Dialog Box ........................................................................ 104
6-13. Create New Data Source to SQL Server Wizard ........................................................ 105
6-14. Specifying Authentication Method ............................................................................ 105
6-15. Setting Additional Properties ..................................................................................... 106
6-16. Final Wizard Page ..................................................................................................... 106
6-17. Selected Data Source Settings .................................................................................... 107
6-18. SQL Server ODBC Data Source Test ....................................................................... 107
7-1. Setting up I/A Series Devices for EFS Scanning ........................................................ 112
7-2. Exporting Device Configurations from PACTware ................................................... 114
7-3. EFS Export with Warnings ....................................................................................... 114
7-4. Selecting a Field Device for Scanning ........................................................................ 115
7-5. Setting the Scanning Frequency ................................................................................ 116
7-6. Device Grouping List Control ................................................................................... 117
7-7. Selecting the Group Size ........................................................................................... 118
7-8. Alphabetically Sorted Grouping ................................................................................ 118
7-9. Removing Devices from Alphabetic Grouping .......................................................... 119
7-10. Start Service Button .................................................................................................. 121
7-11. Configuring the Device Scanner Service .................................................................... 122
7-12. Stop Service Button ................................................................................................... 123
7-13. Click Update Service to Make Changes on the Fly .................................................... 124
7-14. Scanner Configuration Update in Progress ................................................................ 124
7-15. Update Service is Successful ...................................................................................... 124
8-1. Example HART Multiplexer Configuration .............................................................. 125
8-2. Configuring Devices Connected via a HART Multiplexer for EFS Scanning ............ 127
8-3. Updating the Device Catalog .................................................................................... 128
8-4. Setting Up the Project View ...................................................................................... 129
8-5. Naming the PACTware Project ................................................................................. 129
8-6. Add the HART Communication DTM to the Host PC ........................................... 130
8-7. HART Communication DTM Parameters ................................................................ 131
8-8. Adding the Master DTM .......................................................................................... 132
8-9. Editing Master Multiplexer Parameters ..................................................................... 133
8-10. Adding a Slave DTM ................................................................................................ 134
8-11. Selecting the Slave Communication Channel ............................................................ 134
8-12. Editing the Slave Multiplexer Parameters .................................................................. 135
8-13. Selecting a Slave Device ............................................................................................ 136
8-14. Rebuild Loops Dialog Box ........................................................................................ 137
8-15. Connecting to the Multiplexer Slave ......................................................................... 138
8-16. Editing the Slave Device Online ................................................................................ 139
8-17. Exporting Device Configurations from PACTware ................................................... 140
8-18. Selecting an Off-Platform Field Device for Scanning ................................................ 141
8-19. Setting the Scanning Frequency ................................................................................ 142
8-20. EFSExportWarning Dialog Box ................................................................................ 142
8-21. Network Object Selection ......................................................................................... 143
8-22. Confirm Deletion Dialog Box ................................................................................... 143
8-23. Configuring Devices Connected via an MTL Multiplexer for EFS Scanning ............. 144
8-24. Selecting Scan List in PACTware .............................................................................. 145
8-25. Selecting RS-485 Address in PACTware ................................................................... 146
ix
8-26. Refreshing the Instrument List in PACTware ............................................................ 147

8-27. List of Devices in PACTware .................................................................................... 148
8-28. Channel Selection in PACTware ............................................................................... 149
8-29. FoxCom Modem with a FoxCom Device .................................................................. 150
8-30. HART Modem with a HART Field Device .............................................................. 150
8-31. Configuring Devices Connected via a Modem for EFS Scanning .............................. 151
8-32. Multiplexer and Device Setup Procedure .................................................................. 152
8-33. Adding HART Communication DTM to HOST PC ............................................... 153
8-34. Configuring HART Communication DTM ............................................................. 154
8-35. Adding Mux 2700G (FDT) Master DTM to the HART Communication DTM ..... 155
8-36. Adding 2700 Slave (FDT) Slave DTM to the Mux Master DTM ............................. 156
8-37. Channel Scan Completed .......................................................................................... 157
8-38. Connecting the Device DTMs in PACTware ............................................................ 158
8-39. Choosing Extras > EFS Export from PACTware Main Menu ................................... 159
A-1. Microsoft SQL Server Management Studio - Restore Database ................................. 172
A-2. Restore Database Window ........................................................................................ 173
A-3. Specify Backup Dialog Box ....................................................................................... 173
A-4. Locate Backup File Dialog Box ................................................................................. 174
A-5. Backup Location Listed ............................................................................................. 175
A-6. Restore Checkbox ..................................................................................................... 175
A-7. Restore Options and Standby File ............................................................................. 176
A-8. Restore State and Modified Paths .............................................................................. 177
A-9. EFSDB Restored Successfully .................................................................................... 178
A-10. Opening a New Query .............................................................................................. 179
A-11. Query Successfully Executed ..................................................................................... 179
A-12. Login Properties Window, General Page ................................................................... 180
A-13. Login Properties Window, User Mapping Page ......................................................... 181
B-1. Choices for Maintenance Only Applications ............................................................. 184
B-2. EFS Displaying I/A Series Hierarchy ......................................................................... 185
B-3. Ensure that the DevScan Service is Stopped .............................................................. 186
B-4. Selecting the Product Features ................................................................................... 187
B-5. EFS Displaying I/A Series Hierarchy ......................................................................... 188
C-1. SQL Server Import and Export Wizard Dialog Box .................................................. 190
C-2. Choose a Data Source Page ....................................................................................... 191
C-3. Choose a Destination Page ........................................................................................ 192
C-4. Specify Table Copy or Query Page ............................................................................ 193
C-5. Select Source Tables and Views Page ......................................................................... 194
C-6. Save and Execute Package Page ................................................................................. 195
C-7. SQL Server Import and Export Wizard ..................................................................... 196
C-8. Final Wizard Page Indicates the Import Was a Success .............................................. 197
C-9. Option Dialog Box in SQL Server Management Studio ............................................ 198
C-10. Tables Summary Tab ................................................................................................ 199
C-11. Tables Design View .................................................................................................. 200
C-12. Setting the Primary Key ............................................................................................ 201
C-13. Option Dialog Box in SQL Server Management Studio (Checking) ......................... 202
C-14. FBMTypeSoftware Column Properties ..................................................................... 203
C-15. Channel Column Properties ...................................................................................... 204
C-16. Selecting 100 Series Migration .................................................................................. 206
x
Figures B0400EF – Rev H
D-1. Configure Communication DTM ............................................................................. 210

D-2. Listing DTMs for a Vendor in the Device Catalog .................................................... 211
D-3. Choosing Device DTM to Print Online Parameterization ........................................ 212
D-4. Adding Device DTM to Proper Channel .................................................................. 213
D-5. Device DTM Added Under Communication DTM ................................................. 214
D-6. Putting the Device Online ........................................................................................ 215
D-7. Device Online ........................................................................................................... 216
D-8. Choosing Print Online Parameterization ................................................................... 217
D-9. Showing Online Parameterization ............................................................................. 218
D-10. Online Parameterization Showing “Fld Dev Rev” and “Software Rev” ...................... 219
D-11. Selecting Correct DTM From List of DTMs for a Vendor ........................................ 220
xi
xii
Tables
2-1. Replacing 100 Series FBMs ......................................................................................... 10
3-1. 200 Series FBMs and Associated ECBs ....................................................................... 53
3-2. 100 Series FBMs and Associated ECBs ....................................................................... 54
3-3. New 200 Series FBMs and Associated ECBs ............................................................... 54
4-1. Resolving Conflicts Between Imported Data and the EFS Database ............................ 78
4-2. How Validation Resolves Differences Between CSA and the EFS Database ................ 84
5-1. Resolving Conflicts Between Manually Entered Data and The EFS Database ............. 92
C-1. Migration to 200 Series FBMs (Partial) ..................................................................... 206
xiii
B0400EF – Rev H Tables
xiv
Preface
This document provides information for installing, configuring, operating and troubleshooting
I/A Series® system Extended Frame Services and Communication DTMs.
Who Should Read This Book

This book is intended for process control engineers and operators, instrument and maintenance
engineers and other qualified and authorized personnel involved in setting up, configuring and
maintaining I/A Series equipment to provide an interface to intelligent field devices using the
HART™ or FoxCom™ communication protocols.
What You Should Know

Prior to using this book, you should be generally familiar with the I/A Series system. Detailed
information relating to the various I/A Series software and hardware elements is found in the ref-
erence documents listed below. You should also be familiar with the field device protocol that you
intend to interface to an I/A Series system.
If you intend to use Microsoft SQL Server® 2008 with Extended Frame Services, it is presumed
that you are proficient in the administration and configuration of Microsoft SQL Server 2008.
Installation of the server is not covered in this document, and the database configuration instruc-
tions are limited to EFS specific tasks.
Revision Information
For this release of the document (B0400EF-H), the following changes were made:
Global
 Updated all references to “EFS2.2” to “EFS2.3”, “PACTware 3.6 SP1” to “PACTware
4.0” and “Microsoft SQL Server 2005” to “Microsoft SQL Server 2008”.
Chapter 1 “Extended Frame Services 2.3”
 Revised the content of chapter to reflect use of PACTware V4.0 and Microsoft SQL
Server 2008 with EFS2.3.
Chapter 2 “Software Installation”
 Revised the content of chapter to reflect use of PACTware V4.0 and Microsoft SQL
Server 2008 with EFS2.3.
 Updated “Install PACTware” on page 11.
 Added “Install Microsoft .NET Framework 4.0” on page 25.
 Updated “Install EFS and HART/FoxCom Communication Device Type Managers”
on page 28 and “Install the Device DTMs” on page 36.
 Updated screenshots in “Initialize PACTware V4.0 Device Catalog” on page 45.
 Added “Uninstall EFS” on page 47.
xv
B0400EF – Rev H Preface
Chapter 3 “Online Configuration”

 Added FBM247 to Table 3-3, “New 200 Series FBMs and Associated ECBs”.
 Updated “Initialize the Device Catalog and Start a Project” on page 56.
 Updated Figure 3-3, Figure 3-7, Figure 3-9, Figure 3-10, Figure 3-11, Figure 3-12
and Figure 3-13.
Chapter 4 “Offline Configuration: Bulk Data Import”
 Minor update to directories listed in “Creating a Worksheet for Bulk Import” on
page 70, “Importing to an Existing EFS Database” on page 74, and “Validating the
Offline Configuration” on page 79.
 Updated Figure 4-1 on page 70, Figure 4-3 on page 72, Figure 4-6 on page 75, and
Figure 4-10 on page 80.
Chapter 5 “Offline Configuration: Manual Entry”
 Updated Figure 5-1 on page 88, Figure 5-2 on page 89, Figure 5-3 on page 90, and
Figure 5-4 on page 91.
 Minor edits to “Editing Manually Entered Device ECB Information” on page 90.
Chapter 6 “Setting Up the EFS Database Using Microsoft SQL Server 2008”
 Added “Setting Options on EFS Database” on page 102.
 Edits to “Best Practices for Advanced Users” on page 108.
Chapter 7 “Configuring Devices for EFS Scanning”
 Added “HART Device Scan Considerations” on page 112.
 Updated Figure 7-1 “Setting up I/A Series Devices for EFS Scanning” on page 112.
 Updated the note at the end of “Exporting the PACTware Project” on page 114.
 Updated screenshots in and added the final warning to “Selecting the Devices and Set-
ting the Frequency” on page 115.
 Updated “Updating the Service” on page 120, “Starting the Scan Service” on
page 121, “Stopping DevScan” on page 122 and “Updating the Service on the Fly” on
page 123.
Chapter 8 “Configuring and Scanning Off-Platform Devices”
 Updated the list of CD-ROMs required during the installation process for the HART
multiplexer in “Hardware and Software Prerequisites” on page 126.
 Upgraded screenshots in “Getting Started” on page 127, “Add HART Communica-
tion and Multiplexer DTMs” on page 130, Figure 8-12 on page 135, “Add the DTMs
for Field Devices” on page 135 and “Configure EFS Scanning” on page 140.
 In “Multiplexer Master DTM” on page 131, changed the HART communications
DTM in the Project view from COM2 to COM1.
 Added another procedure to the beginning of “Verify Device Connections” on
page 136.
 Updated “MTL Multiplexer and Devices” on page 144, including Figure 8-23.
 Added figures to “Pepperl+Fuchs Elcon 2700G HART Multiplexer with Devices” on
page 151.
Appendix A “Troubleshooting”
xvi
Preface B0400EF – Rev H

Minor update to “Case 1: Microsoft SQL Server 2008” on page 171.
 Updated “Restoring the Database in SQL Server 2008” on page 172.
Appendix B “Upgrading to PACTware 4.0 and EFS 2.3”
 Updated “Maintenance Only Applications” on page 183.
 Updated Figure B-4 on page 187.
Appendix C “Database Migration”
 Updated the steps are to be executed to create SQL Server 2008 EFS database from an
Access EFS database on page 189.
 Updated “Import from the Access Database” on page 189, “Set the Primary Key for
the Database Tables” on page 197, “Set Default Values for the CommunicationDe-
vices Table” on page 202 and “Migrating Databases from Previous Versions to EFS
2.3” on page 204.
Appendix D “Choosing a Proper DTM for a Field Device”
 Added this appendix.
Database Migration and Software Upgrades

If you are upgrading your EFS application from the previous version (EFS1.1, 2.1 and 2.2), you
should first review Appendix C “Database Migration” for important information on migrating
the database to the latest EFS version. The appendix also contains information on changing the
database software from Microsoft Access to Microsoft SQL Server 2008.
100 Series FBM Migration

If you are replacing certain 100 Series FBMs with the new 200 Series FBM243 and FBM243b,
you can select an option in the migration procedure that will convert the database records for 100
Series FBMs to reflect the new FBMs. The table below provides a partial list of the 100 Series
FBMs and their 200 Series replacements. The option is described in “Migrating Databases from
Previous Versions to EFS 2.3” on page 204.
100 Series FBM 200 Series Upgrade
FBM18 FBM243
FBM39 FBM243b
FBM43 FBM243
FBM44 FBM243b
FBM46 FBM246b
The full list of 200 Series FBM replacements for 100 Series FBMs is available in 100 Series Field-
bus Module Upgrade User's Guide (B0700BQ).
PACTware Upgrade
If you are currently using EFS 1.1, EFS 2.0, EFS 2.1 or EFS 2.2, you should also review
Appendix B “Upgrading to PACTware 4.0 and EFS 2.3” for information on managing PACTware
projects as you install PACTware Version 4.0, which is required for EFS 2.3.
xvii
B0400EF – Rev H Preface
Reference Documents
In addition to the information in this document, you should be familiar with the following
documents.
For information on integrating FBMs and intelligent field devices into an I/A Series sys-
tem, refer to:
 DIN Rail Mounted Subsystem User’s Guide (B0400FA)
 Measurement Integration (B0193RA)
 HART™ Communication Interface Modules User’s Guide (B0400FF)
 100 Series Fieldbus Module Upgrade User's Guide (B0700BQ).
For information about defining blocks and compounds, refer to:
 Integrated Control Block Descriptions (B0193AX)
 Integrated Control Software Concepts (B0193AW).
For information about configuring your system, refer to:
 System Definition: A Step-by-Step Procedure (B0193WQ)
 Integrated Control Configurator (B0193AV).
For details on the application programming interface of EFS, refer to:
 Extended Frame Services 2.x Application Programming Interface (B0400EG).
Most are available on the I/A Series Electronic Documentation CD-ROM (K0173TQ or
K0173WT) provided by the Foxboro business unit of Invensys. The latest revisions may also be
available through the Global Customer Support at http://support.ips.invensys.com.
xviii
1. Extended Frame Services 2.3
This chapter describes FDT Manager Components including Extended Frame Services 2.3, an
I/A Series system application that is compliant with the Field Device Tool V1.2 and Addendum
standard, as well as the I/A Series system communication Device Type Managers (DTMs).
Overview
Field Device Tool (FDT) uses industry-standard technology to provide a single application to
translate and use the vendor-defined functions of many different intelligent field devices. Using
Field Device Tool technology in your I/A Series system, you can integrate a number of different
field devices that use the HART or FoxCom communication protocol into your system, and you
can access, configure, calibrate and maintain each of them, regardless of manufacturer.
 To enable communication between the control network and field devices, the
I/A Series system uses combinations of the following FDT Components:
 Instrument Device Type Managers (device DTMs)
 Communication Device Type Managers (communication DTMs)
 PACTware™ 4.0 FDT Frame Application
 Extended Frame Services 2.3
Device DTMs
Each device is associated with a device DTM, which is a software component created by the
device manufacturer that provides the functionality to configure and calibrate the device, and per-
form device diagnostics. A typical device DTM enables you to:
 View full screen displays of device parameters to speed device DTM’s off-line
configuration
 Reconfigure the tag number, tag name, device name, location, upper and lower range
values, damping time, digital or 4 to 20 mA output, type of units measured and other
configurable parameters as required
 Accurately re-range a device without applying a calibrated input signal
 Diagnose problems and determine if they are process or device errors
 Adjust the device output to any value for verification, troubleshooting, or loop
calibration.
NOTE
When working with EFS and HART devices, use only the CodeWrights Invensys
3rd Party DTMs in the Code Wrights library CD (K0201AW) in the EFS deliver-
ables. Exceptions to the rule are indicated later.
1
B0400EF – Rev H 1. Extended Frame Services 2.3
NOTE
Refer to Appendix D “Choosing a Proper DTM for a Field Device” before proceed-
ing to use DTMs from Code Wrights DTM library.
Invensys Foxboro provides DTMs for Invensys manufactured HART and FoxCom field devices.
DTMs are available in the Code Wrights DTM library in the EFS deliverables for many non
Invensys devices. These are devices for which the device manufacturer provided the device DD
source to the HART Communication Foundation.
There are some devices for which you will not find DTMs in the Code Wrights DTM library, as
the device manufacturers do not provide DD source files to the HART Communication Founda-
tion. In such cases, if you can secure the DD source from the vendor, Invensys provides a service
to generate the DTM from the DD source files. Contact Global Customer Support for informa-
tion on pricing and a quotation.
Using Vendor Device DTMs with EFS

Vendor DTMs are very desirable for performing advanced device functions. However, most ven-
dor DTMs do not implement the interfaces required by EFS for background monitoring of
devices. The following recommendations are made.
 EFS scans should be performed only with a DTM from the CodeWrights Invensys
3rd Party DTMs package.
 Although vendor-supplied device DTMs should not be used to run EFS scans, they
can be used in PACTware 4.0 for device configuration and calibration, and advanced
device diagnostics.
Communication DTMs
The I/A Series system also requires an FBM Communication DTM (sometimes referred to as a
communication passthrough DTM), which is created as per fieldbus type, for communication
through the I/A Series Control Network, Control Processor and FBM to the device. Two FBM
Communication DTMs are shipped on the EFS media kit: one for communication with HART
devices via an FBM, the other for communication with FoxCom devices. These DTMs should be
installed when you install PACTware.
A generic HART Communication DTM is required to communicate with HART field devices in a
non I/A Series system environment. These devices are connected to the host workstation via a
modem or multiplexer, and not via an FBM on the I/A Series Control Network. In the this docu-
ment, these devices are referred to as off-platform devices. The HART Communication DTM is
shipped along with the PACTware installation. If you connect the device via a multiplexer, such as
a multiplexer, you must use a vendor-provided DTM for the device communication in addition
to the HART Communication DTM.
PACTware Frame Application

Process Automation Configuration Tool (PACTware) is a standard frame application for device
DTMs. PACTware allows the combination of intelligent field devices from different manufactur-
ers into one project and provides a single user interface to each device DTM.
2
1. Extended Frame Services 2.3 B0400EF – Rev H
PACTware is installed on an I/A Series workstation with the FBM Communication DTMs and
device DTMs and enables you to configure and manage HART and FoxCom devices online.
PACTware queries the I/A Series Compound Summary Access (CSA) instance to discover the
equipment control blocks (ECBs) that have been deployed for the FBMs and their attached
devices. Use PACTware to associate the FBM ECB with the appropriate FBM Communication
DTM and the individual devices with their respective device DTMs. You can then open the
device DTMs and configure the devices, and upload and download the device configurations.
Configuration of the intelligent field devices on the I/A Series system is discussed in Chapter 3
“Online Configuration”.
NOTE
If you are currently using EFS 1.1, EFS 2.0, EFS2.1 or EFS 2.2, you should review
Appendix B “Upgrading to PACTware 4.0 and EFS 2.3” for information on manag-
ing PACTware projects as you install PACTware Version 4.0, which is required for
EFS 2.3.
Offline Configuration
PACTware can also be used in conjunction with EFS to configure HART and FoxCom devices
before their ECBs are deployed to the I/A Series system. Instead of querying the CSA for ECB
information, the ECB names are sourced from the EFS database. You can enter the names by
importing them from a spreadsheet or using manual data entry. The two methods are described in
Chapter 4 “Offline Configuration: Bulk Data Import” and Chapter 5 “Offline Configuration:
Manual Entry”, respectively.
Configuration of Off-platform Devices

PACTware can also be used to configure and manage off-platform HART and FoxCom devices
connected to the I/A Series workstation via a modem or multiplexer. Chapter 8 “Configuring and
Scanning Off-Platform Devices” provides an extended example in which the workstation is con-
nected to a HART device via a Pepperl+Fuchs multiplexer.
Extended Frame Services 2.3

Extended Frame Services (EFS) provide FDT compliant data collection services to scan instru-
ment data to link instrument maintenance information from HART or FoxCom devices to the
Avantis Condition Manager. EFS scans the desired information and stores the data in a relational
database with a predefined, documented data structure and table definition. Then the Avantis
Condition Manager application extracts selected asset management data from the relational data-
base. The data can include device identification information, device health status and DTM-sup-
plied cycle counts for valve positioners. The Condition Manager application monitors data
scanned by EFS into the relational database and creates a work order within Avantis.PRO® when
a device malfunctions.
Usage of the EFS scanner is intended and recommended for HART devices connected to HART
multiplexers. For devices connected to I/A Series FBMs, scanning data through the Control Pro-
cessor and Foxboro Control Software (FCS) with ArchestrA application objects is recommended
when Foxboro Control Software (FCS) is used. Primary instrument health data is automatically
scanned into the Control Processor. Additional extended device status, automatically collected by
3
HART FBMs, as well as additional HART device data can be scanned into the Control Processor
as desired. Refer to “HART Devices Connected To I/A Series HART FBMs” on page 113 for fur-
ther details. Alarming and communicating abnormal device status may be performed through
ArchestrA application objects and the ArchestrA system platform, or alternatively through alarm
capabilities in applications such as FoxView. These techniques result in much faster instrument
alarms compared to using EFS and the Avantis Condition Manager.
In the FBM-connected scenario, if it is desirable to use the Avantis.PRO work order system, the
Condition Manager's OPC or historian interfaces may be used instead of its EFS interface.
The EFS database is implemented with either Microsoft Access or Microsoft SQL Server 2008.
Microsoft Access is installed as the default EFS database and requires no additional setup.
Microsoft SQL Server 2008 is the recommended database for all systems that use EFS. However
Microsoft Access can be selected and used for proof of concept and systems used for training.
 See Chapter 6 “Setting Up the EFS Database Using Microsoft SQL Server 2008” for
information on creating the EFS database with Microsoft SQL Server 2008.
 See Appendix C “Database Migration” for information on converting an existing EFS
database from Microsoft Access to Microsoft SQL Server 2008, and on managing the
EFS database as you upgrade the application to EFS 2.3.
NOTE
Extended Frame Services 2.3 requires PACTware 4.0 for configuration, and
supports Microsoft SQL Server 2008 only (not any earlier versions).
A scanning process is provided with EFS to ensure that intelligent field device information in the
database is updated periodically. The scanner retrieves device parameters and status, and saves the
updated information to the database. You can configure the scanner to specify which devices to
scan and the frequency of scanning.
 See Chapter 7 “Configuring Devices for EFS Scanning” for instructions on configur-
ing EFS scans of devices connected to the I/A Series system.
 Refer to Chapter 8 “Configuring and Scanning Off-Platform Devices” for informa-
tion on configuring EFS scans of off-platform devices.
Valid Configurations for EFS 2.3 On-Platform Configuration

NOTE
Do not install EFS and I/A Series Intelligent Field Device Configurator (IFDC)
software on the same workstation.
Licenses for EFS 2.3 are available in both EFS Server and EFS Client versions. The EFS Server is
used on the computer that stores the EFS database.
Figure 1-1 shows a typical configuration where the EFS Server is installed on a server-class com-
puter located on the Enterprise Network, with SQL Server 2008 database installed. In this config-
uration, I/A Series communication DTMs are installed on the EFS Client on the I/A Series
system redundant control network.
4
Figure 1-1. Typical EFS Configuration with EFS Server on Enterprise Network
When an EFS Server is installed on-platform as in Figure 1-2, the control processor is typically
hosted by a different I/A Series workstation. However, the EFS Server may also be installed on the
control processor’s host workstation. You can install EFS software on Windows workstations in
systems having mixture of UNIX® and Windows workstations.
Figure 1-3 shows an alternate configuration, where the EFS Server is installed on an I/A Series sys-
tem Windows® XP workstation located on the redundant control network. In this case, the EFS
Server uses the Microsoft Access database, and communication DTMs are installed on both the
server and client workstations.
EFS Client software may be installed on any Windows compatible workstation meeting the hard-
ware requirements identified in “EFS Hardware and Software Requirements” on page 7 either on
the I/A Series platform or on the Enterprise network. This allows device information to be shared
anywhere across the plant enterprise. An EFS Client typically accesses scan database information
from the EFS Server, but it can also access direct device information through the communication
DTMs. Avantis.PRO can be installed on any computer having either EFS Server or EFS Client
software. Invensys Condition Monitoring (ICM) application monitors the asset management data
within EFS and creates a work order within Avantis.PRO when a device malfunctions.
5
Figure 1-2. EFS Configuration with EFS Server on Platform
Figure 1-3. Alternate EFS Configuration with EFS Server on the I/A Series Network
6
EFS Hardware and Software Requirements

I/A Series Platform Requirements
NOTE
Extended Frame Services 2.3 is supported on a client with Windows XP Profes-
sional operating system, or a server with Windows Server 2003 operating system
with Microsoft SQL Server 2008.
NOTE
I/A Series system FBM Communication DTMs must be installed on an I/A Series
workstation that has the EFS software installed and that has a second Ethernet
Interface to the Enterprise Network.
Off-Platform Requirements
An off-platform EFS Client must be a workstation running the Windows XP Professional
operating system.
The recommended off-platform EFS Server is a server-class computer with the Windows Server
2003 operating systems with Microsoft SQL Server 2008. Alternatively, you can use a computer
running the Windows XP Professional or Windows 7 Professional operating systems with Micro-
soft Access software. Microsoft SQL Server 2008 database is recommended for better perfor-
mance on larger applications.
Invensys Condition Monitoring and Avantis.Pro

The Invensys Condition Monitoring application monitors the asset management data within EFS
and creates a work order within Avantis.PRO when a device malfunctions. Additional asset man-
agement information can be obtained from the EFS database by utilizing the Application Pro-
gramming Interface, as described in Extended Frame Services 2.x Application Programming Interface
(B0400EG).
NOTE
Minimum hardware requirements include a Pentium 4 machine of 1.5 GHz with
512MB of main memory, 4 GB hard disk with at least 100 MB of space for installa-
tion, CD-ROM drive and 100 MHz TCP/IP switched Ethernet Interface.
7
8
2. Software Installation
This chapter describes installation of PACTware, Extended Frame Services and related DTMs.
The software described in this chapter is located on the following CD-ROMs and is used for
installing PACTware, EFS and related DTMs:
 K0201AV - PACTware 4.0 FDT Frame Application
This CD includes Microsoft .NET Framework 4.0 (Version 4.0.30319), which
the EFS V2.3 application requires.
 K0201AX - FDT Device Manager Components V2.3 (EFS V2.3)
This CD includes HART and FoxCom communication DTMs, Extended Frame
Services, and user documentation.
Install the FBM communication DTMs from this CD and not from D0197BZ
(PC50 package).
 K0201AW - Device Type Managers for HART by CodeWrights V1.7.169
This CD contains device DTMs for non Invensys HART devices.
 D0197BZ - Device Type Managers for Invensys Instruments V2.5 (also referred to as
the PC50 Intelligent Transmitter Configurator package or PC50 package)
Use this CD to install device DTMs for Invensys HART devices and FoxCom
devices.
Do not install the HART and FoxCom FBM Communication DTM versions
that are on this CD.
It is recommended that proper DTM revision is acquired for the device based on
the device revision and firmware revision of the physical device. If the PC50 Intel-
ligent Transmitter Configurator package is missing the required DTM, obtain the
latest and proper DTM from the following Invensys Operations Management
website:
http://iom.invensys.com/EN/Pages/Foxboro_MandI_DocTools_DeviceManagers.aspx
Alternatively, you can obtain the latest and proper DTM by contacting the Inven-
sys Operations Management Global Customer Support at http://support.ips.inven-
sys.com.
D0197BZ is not included in the EFS 2.3 media. If you are installing Invensys
HART devices or FoxCom devices, order the D0197BZ through BuyAutomation.
Before you Begin

NOTE
Do not install EFS and I/A Series Intelligent Field Device Configurator (IFDC)
software on the same workstation.
9
B0400EF – Rev H 2. Software Installation
Installation Directory
This chapter provides detailed step-by-step instructions for installation of the FDT software. In
many cases, you can simply insert the CDs in the workstation, run setup.exe and follow the
setup wizard prompts to perform a Complete installation of the software to the default installa-
tion location on the workstation’s C: drive.
However, if you are installing the software in an I/A Series (v8.5 or later) secured environment,
you must install the software on the D: drive. Each wizard presents a slightly different method for
changing the installation location, as described in the following sections:
 “Install PACTware” on page 11
 “Install EFS and HART/FoxCom Device Manager” on page 25
 “Invensys 3rd Party DTMs for Non Invensys HART Devices” on page 36
 “DTMs for Invensys Instruments” on page 44
The instructions in this chapter follow the recommended sequence for installation.
Database Migration and Software Upgrades

If you are upgrading your EFS application from previous versions, you should first review
Appendix C “Database Migration” for important information on migrating the database to the
latest EFS version. The appendix also contains information on changing the database software
from Microsoft Access to Microsoft SQL Server 2008.
100 Series FBM Migration

If you are replacing 100 Series FBMs with the new 200 Series FBM243 and FBM243b, you can
select an option in the migration procedure that will convert the database records for 100 Series
FBMs to reflect the new 200 Series FBMs. The Table 2-1 lists the 100 Series FBMs and their 200
Series replacements. The option is described in “Migrating Databases from Previous Versions to
EFS 2.3” on page 204.
Table 2-1. Replacing 100 Series FBMs

FBM18 FBM243
FBM39 FBM243b
FBM43 FBM243
FBM44 FBM243b
FBM46 FBM246b
Upgrading PACTware
If you are currently using EFS 1.1, EFS 2.0, EFS 2.1 or EFS 2.2, you should also review
Appendix B “Upgrading to PACTware 4.0 and EFS 2.3” for information on managing PACTware
projects as you install PACTware Version 4.0, which is required for EFS 2.3.
10
2. Software Installation B0400EF – Rev H
Install PACTware
The PACTWare 4.0 requires Microsoft .NET Framework 2.0. If Microsoft .NET Framework 2.0
is not already installed on the system, you should install it before installing PACTware 4.0.
The PACTware 4.0 FDT Frame Application CD-ROM (K0201AV) includes Microsoft .NET
Framework 2.0.
Install Microsoft .NET Framework 2.0

To install the MS .NET software, proceed as follows:
1. On the CD-ROM, switch to the .NET Framework 2.0 directory and double-click
setup.exe. The Welcome wizard appears, as shown in Figure 2-1.
Figure 2-1. Welcome Wizard
2. Click Next in the Welcome wizard (Figure 2-1). The License agreement page opens
(Figure 2-2).
11
Figure 2-2. License Agreement
3. Select the I accept the terms of the License agreement check box and
then click Install (Figure 2-2). The software is installed.
Install PACTware 4.0.6

To install the PACTware FDT Frame Application software v4.0:
1. Switch to the PACTware directory on the K0201AV CD-ROM and double-click
setup.exe.
2. Select English (United States) in the Choose Setup Language dialog box
(Figure 2-3) and click OK to start the installation wizard.
Figure 2-3. Choose Setup Language Dialog Box
12
NOTE
Do not select any language except English, as the PACTware FDT Frame Applica-
tion supports only English.
3. Select Next on the Welcome page (Figure 2-4) to proceed with the installation.
Figure 2-4. Welcome Page
4. Click the radio button for I accept the terms... on the License Agreement page
(Figure 2-5) and then click Next.
13
Figure 2-5. PACTware License Agreement
5. Provide the details for the Customer Information page (Figure 2-6) and click Next.
Figure 2-6. Customer Information Page
14
6. Choose Custom for Setup Type (Figure 2-7) and click Next.
Figure 2-7. Setup Type Page
The wizard displays the Choose Destination Location page with a default installation
location on the C: drive (Figure 2-8).
15
Figure 2-8. Choose Destination Location
NOTE
If you are installing the software in an I/A Series secured environment, you must
install the software on the D: drive.
7. Do the following if you are installing the software in an I/A Series secured environ-
ment:
a. Click Browse to open the Choose Folder dialog box (Figure 2-9)
b. Change C:\ to D:\ in the Path field and click OK.
16
Figure 2-9. Changing the Installation Folder
8. Click Next on the Choose Destination Location page when the correct installation
folder is shown.
9. Click Next on the Start Copying Files page to install the PACTware software
(Figure 2-10).
Figure 2-10. Reviewing the Setup
17
10. The wizard displays the progress of the install on the Setup Status page (Figure 2-11)
and then displays the Installation Wizard Complete page (Figure 2-12).
Figure 2-11. Setup Status Page
11. Click Finish to complete the installation (Figure 2-12).
18
Figure 2-12. Installation Complete Wizard
Installing the HART Communication DTM

To install the HART Communication DTM, proceed as follows:
1. Switch to the HART Communication DTM installation directory and double-click
setup.exe, which redirects to the Welcome page (Figure 2-13)
19
Figure 2-13. Generic HART DTM Welcome Page
2. Click Next on the Welcome page (Figure 2-14), to display the License Agreement
page.
20
Figure 2-14. HART DTM License Agreement
3. Click the radio button for I Accept the terms... and then click Next. The Cus-
tomer Information page opens (Figure 2-15).
21
Figure 2-15. Customer Information for the Generic HART DTM Installation
4. Enter your user name and organization in the Customer Information page
(Figure 2-15) and click Next. The Ready to Install page (Figure 2-16) opens.
22
Figure 2-16. Ready to Install
5. Click Install on the Ready to Install page (Figure 2-16). The Installing page opens
to display the progress of the installation (Figure 2-17).
23
Figure 2-17. Installation Progress
6. Click Finish when the wizard indicates that the DTM has been installed successfully
(Figure 2-18).
24
Figure 2-18. Completing the Generic HART DTM Installation
Install EFS and HART/FoxCom Device Manager

The EFS and HART/FoxCom Communication DTMs require Microsoft .NET Framework 4.0.
If Microsoft .NET Framework 4.0 is not already installed on the system, you should install it
before installing EFS or HART/FoxCom Communication DTMs.
Install Microsoft .NET Framework 4.0

1. On the K0201AV CD-ROM, open the .NET 4.0 Framework installation directory
and double-click the installation executable (dotNetFx40_Full_x86_x64.exe).
The .NET Framework 4 Setup page opens (Figure 2-19).
25
Figure 2-19. .NET Framework 4 Setup
2. Click the I have read and accept the license terms check box.
3. Click Install to continue the installation. The Installation progress page opens
(Figure 2-20).
26
Figure 2-20. .NET Framework 4 Installation Progress
4. Click Finish to complete the installation (Figure 2-21).
27
Figure 2-21. .NET Framework 4 Installation Complete
Install EFS and HART/FoxCom Communication Device Type

Managers
The next step is to install the FDT Components from the FDT Device Manager Components
V2.3 (EFS V2.3) CD (p/n K0201AX):
 Extended Frame Services (EFS)
 FBM Communication DTM for HART (HART Device Manager)
 FBM Communication DTM for FoxCom (FoxCom Device Manager)
 Documentation including this document, Extended Frame Services 2.x Application Pro-
gramming Interface (B0400EG) and related release notes.
To install the FDT Device Manager Components software:
1. Insert the FDT Device Manager Components V2.3 CD into the workstation CD-
ROM drive and execute setup.exe to begin the installation process.
2. The program displays a Startup screen (Figure 2-22) as it loads a setup wizard. Then
the License Agreement page opens (Figure 2-23).
28
Figure 2-22. Loading the Installation Program for FDT Components
Figure 2-23. EFS License Agreement Page
3. Click Yes to accept the license and display the Choose Destination Location page
(Figure 2-24), which shows the default installation directory on the C: drive
29
(C:\Program Files\Invensys\FDM_EFS) on an off-platform system or shows the

D: drive (D:\Invensys\FDM_EFS) on an I/A Series System.
Figure 2-24. Choose Destination Location Page with Default Selection
At this point, you can either accept the default location or change the installation
directory to a folder of your choice.
NOTE
If you are installing the software in an I/A Series secured environment, you must
install the software on the D: drive.
4. Do the following to specify a different installation location:

a. Click the Browse button in the Destination Folder box to open the Choose
Folder dialog box (Figure 2-25).
b. Use the dialog box to browse to and select a different location, or type the new
location in the Path field.
In Figure 2-26, the user has entered the root directory of the D: drive.
c. Click OK to display the new selection on the Choose Destination Location page
(Figure 2-27).
30
Figure 2-25. Choosing the Installation Folder
Figure 2-26. Changing the Installation Directory
31
Figure 2-27. Installation Directory Is Changed
d. Click Next on the Choose Destination Location page with the Destination Folder
selected (Figure 2-27).
If the Destination Folder does not have the \FDM_EFS in the path (as is the case in
Figure 2-26), the Installation wizard displays a message box indicating that it will
append \FDM_EFS to your selection (Figure 2-28).
32
Figure 2-28. Installation Location Must Include \FDM_EFS
e. Do one of the following:

 Click OK to install the software in the path shown in the Information dialog
box (D:\FDM_EFS in Figure 2-28) and proceed to the Select Features page
(Figure 2-29).
 Click Cancel to return to the Choose Destination Location page, specify a
different Destination Folder, and click Next when the correct directory is
shown under Destination Folder to move to the Select Features page
(Figure 2-29).
f. Select all the features listed in the left pane of the Select Features page
(Figure 2-29). Click Next. The Setup Status page opens (Figure 2-30).
33
Figure 2-29. Selecting the Product Features
Figure 2-30. EFS 2.3 Setup Status
34
5. After the installer finishes computing space requirements, the Configure EFS Data-
base wizard (Figure 2-31) opens. Select either Microsoft Access Database or
Microsoft SQL Server Database.
 By default, Microsoft Access Database is selected.
 Click OK to continue with the Microsoft Access Database installation.
 To continue with SQL server database installation, select Microsoft SQL
Server Database. Then, from the SQL Server drop-down menu, select the
SQL server database name on the workstation. Type the password and click OK.
Figure 2-31. Configure EFS Database Dialog Box
6. Once the installation is completed, the Install Shield Wizard Complete page opens
(Figure 2-32).
7. Click Finish to complete the installation.
35
Figure 2-32. Installation of EFS and Communication DTMs is Complete
Install the Device DTMs

Install the device DTMs, both 3rd party DTMs and the DTMs for Invensys Instruments on the
same workstation as the FDT Components (PACTware, FBM Communication DTMs and EFS).
NOTE
EFS scans should be performed only with a DTM from the CodeWrights Invensys
3rd Party DTMs package. Although vendor supplied device DTMs should not be
used to run EFS scans, they can be used in PACTware 4.0 for device configuration
and calibration, and for advanced device diagnostics.
Invensys 3rd Party DTMs for Non Invensys HART Devices

To install the DTMs for the non-Invensys HART devices, proceed as follows:
1. Insert the Device Type Managers V1.7.169 CD for HART by CodeWrights into the
workstation CD-ROM drive and execute the setup.exe to start the setup wizard.
36
Figure 2-33. Invensys Third Party DTMs Welcome Wizard
2. Click Next on the Welcome page (Figure 2-33) to display the software licence.
3. Click the radio button for I accept the terms... (Figure 2-34) and then click
Next.
37
Figure 2-34. Invensys Third Party DTMs License Agreement
4. In the displayed Customer Information page (Figure 2-35), enter the Customer
details and click Next. The wizard displays the Choose Setup Type page
(Figure 2-36).
38
Figure 2-35. Invensys Third Party DTMs Customer Information
Figure 2-36. Invensys Third Party DTMs - Choose Setup Type
39
5. Click Custom to open the Custom Setup dialog box (Figure 2-37), which lists the
DTMs by vendor. The default installation setup is to install the entire library in:
C:\Program Files\CodeWrights\DTMStudio\Invensys DTM
Library 3rd Party
NOTE
If you are installing the software on an I/A Series secured environment, you must
install the software on the D:\ drive.
Figure 2-37. Invensys Third Party DTMs - Customer Setup
6. Do the following if you are installing the software in an I/A Series secured environ-
ment:
a. Click Browse on the right side of the page to display the Change Current Loca-
tion Folder page (Figure 2-38).
b. Change C:\ to D:\ in the Folder Name field, and click OK.
40
Figure 2-38. Changing the Installation Folder
It is recommended that you install the complete DTM library. If you have limited
disk capacity on the workstation, you may want to install only selected DTMs. The
complete library requires about 990 megabytes of disk space.
7. Do the following to install only selected DTMs:
a. Click the “+” sign to the left of a vendor name to expand the folder and display
specific DTMs (Figure 2-39); click the “-” sign to collapse the display and hide
the DTMs.
b. Select a vendor folder or a DTM to display the item’s storage requirement on the
right.
c. Use the pull-down for a vendor folder or DTM to specify whether it is to be
excluded from the installation (Figure 2-39).
By default, all items are included.
41
Figure 2-39. Custom Setup for Third Party DTMs
d. Click the Disk Usage button to see the space required for your selections.
e. Click Next when you have finished selecting DTMs.
The wizard displays the Ready to Install dialog box (Figure 2-40).
8. Click Install on the Ready to Install page to load the DTMs (or click Back to
change the installation settings).
42
Figure 2-40. DTM Library Ready to Install Page
9. Click Finish when the setup wizard indicates that the installation is complete
(Figure 2-41), and then remove the CD from the CD-ROM drive.
43
Figure 2-41. DTM Library Installation Complete Wizard
DTMs for Invensys Instruments

If you are installing FoxCom devices or Invensys manufactured HART devices, install their device
DTMs from the Device Type Managers for Invensys Instruments V2.5 CD.
NOTE
Do not install the versions of the FBM Communication DTMs for HART and
FoxCom devices (the Passthru DTMs) that are located on this CD. For EFS, install
the Passthru DTMs from FDT Device Manager Components V2.3 (EFS V2.3) CD
(p/n K0201AX). See “Install EFS and HART/FoxCom Device Manager” on
page 25.
To install the Invensys HART device DTMs, proceed as follows:

1. Insert the Device Type Managers V2.5 CD into the workstation CD-ROM drive and
double-click setup.exe to begin the installation.
2. Click Run to start the setup wizard.
3. Click Next on the first wizard page and follow the instructions on the screen during
the installation process.
4. Accept the License Agreement and click Next.
5. Provide details for the Customer Information window (or simply accept the defaults)
and click Next.
6. Choose Custom in the Setup Type page and click Next to display the page for specify-
ing the installation directory.
44
NOTE
If you are installing the software on an I/A Series secured environment, you must
install the software on the D:\ drive.
7. Do the following if you are installing the software on an I/A Series secured environ-
ment:
a. Click Browse to open the Choose Folder dialog box.
b. Change C:\ to D:\ in the Path field, and click OK.
Otherwise, accept the default installation directory (C:\Program Files\Code-
Wrights\DTMstudio\Invensys DTMLibrary for FDT) and click Install.
8. Click Finish when the wizard indicates it has completed the installation.
To install FoxCom device DTMs, proceed as follows:
1. Locate and run FoxComInstall.exe under the FoxCom folder.
2. Follow the installation sequence described for HART device DTMs in steps 2 to 8.
3. Remove the CD.
Initialize PACTware V4.0 Device Catalog

The final step is to load the recently-installed device DTMs and communication DTMs into the
PACTware database, creating the Device Catalog.
To initialize the Device Catalog, proceed as follows:
1. Do one of the following to start the PACTware Frame Application:
 Double-click the PACTware desktop icon ( ).
 Click the Start button and choose PACTware 4.0 > PACTware 4.0 from the
popup menu.
The initial PACTware window is displayed (Figure 2-42). The window includes the
main menu and toolbar at the top of the window, a Project view on the left or at the
top of the window and a Device view. Initially, the Project view includes a single node,
HOST PC, under which you will build a hierarchy of communication DTMs and the
device DTMs associated with them. When you select any item in this Project view,
the parameters for the DTM are displayed in the Device view.
45
Main Menu
Toolbar
Project View Device

Catalog
Icon
Device View
Figure 2-42. PACTware Project Window
2. Choose View > Device Catalog from the PACTware main menu or click the
Device Catalog icon ( ) in the PACTware toolbar to open the Device Catalog
(Figure 2-43).
The catalog lists the DTMs currently available for the project.
3. Click the Update device catalog button to bring the newly installed DTMs into
the PACTware database, and click Yes when the confirmation dialog box
(Figure 2-43) prompts you to Create a new PACTware device catalog?
46
Figure 2-43. PACTWare Device Catalog
NOTE
Update Device Catalog cannot be performed when an existing project is opened in
PACTware.
At this point, you are creating a new project, which you can name at any time by
choosing File > Save from the main menu. You can also edit an existing project by
choosing File > Open from the main menu and selecting the project in the Open
dialog box.
4. Click in the PACTware title bar to close the application.
Uninstall EFS
Proceed as follows to uninstall EFS:
1. Open Settings -> Control Panel -> Add/Remove Programs.
2. Select Extended Frame Services [current version number] and click
Change/Remove.
47
3. Click the Remove radio button on the InstallShield Wizard page (Figure 2-44) and
click Next.
Figure 2-44. Choosing Remove Option for EFS
NOTE
The Modify option is provided for migration of previous version EFS database to
EFS2.3. Refer to Appendix C “Database Migration” on page 189 for details.
The Repair option is provided to repair a corrupted EFS program when it fails to
work reporting missing program or DLL.
4. Click OK in Confirmation dialog box (Figure 2-45) to begin the uninstallation pro-
cess.
Figure 2-45. Confirm Uninstall
5. Several dialog boxes appear during the unistallation process to indicate the progression
of the uninstallation. Once the process is complete, the Maintenance Complete page
opens (Figure 2-46).
48
Figure 2-46. Uninstallation of EFS is Complete
6. Click Finish to complete the uninstallation process.
49
50
3. Online Configuration
This chapter describes how to associate the HART and FoxCom communication DTMs and
device DTMs with an FBM in a PACTware project.
This chapter covers configuration of HART and FoxCom devices where the devices are connected
to I/A Series system via protocol specific fieldbus modules (FBMs).
NOTE
For the sake of simplicity, the instructions and example configuration in this chap-
ter deal with configuring the HART communication DTM and a single HART
device. However, the instructions apply to both HART and FoxCom
communication DTMs and device DTMs.
Figure 3-1 shows the example configuration. The equipment control blocks (ECBs) for the FBMs
and the field devices have been configured and deployed, the field devices have been installed and
connected to the control processor, and the system can be accessed by the I/A Series workstation.
In this workflow, the PACTware Frame application is installed on an I/A Series workstation along
with FBM Communication DTM and the device DTMs that will be associated with the FBMs
and the devices using the PACTware application.
Enterprise Network
I/A Series Workstation

PACTware
I/A Series Communication DTM
HART Device DTMs
I/A Series MESH Control Network
FCP270
HART FBM
HART Device
Figure 3-1. HART Device Management Architecture
51
B0400EF – Rev H 3. Online Configuration
Intelligent Field Device Connection to an I/A Series

System
In a typical I/A Series system, intelligent field devices are wired to the termination assembly of an
FBM, which allows the devices to communicate to the I/A Series workstations via a passthrough
mechanism. The FBM is connected to the control processor (CP), which integrates the device
data into the control strategy, and the CP is hosted by an I/A Series AW software type worksta-
tion.
For detailed information on integrating intelligent field devices into an I/A Series system, includ-
ing installation and configuration instructions, refer to the following documents:
 Measurement Integration (B0193RA)
 HART™ Communication Interface Modules User’s Guide (B0400FF).
System and Database Hierarchy

If Extended Frame Services 2.3 is running as part of an I/A Series system, the EFS database has
knowledge of the current I/A Series topology from the control processors down to the individual
devices.
FBMs and their attached devices are reflected to the I/A Series system control database through
equipment control blocks (ECBs). For each FBM in the I/A Series system, you must configure an
ECB to define its characteristics. This ECB is the parent ECB. Each device connected to the FBM
also needs an associated ECB and the device ECB is the child ECB to the FBM ECB.
To obtain the system hierarchy, PACTware and EFS use the I/A Series system Object Manager to
identify:
 All workstations
 For each workstation, all control processors hosted by the station
 For each control processor, all parent ECBs running on the CP (each parent ECB rep-
resents the FBM to which the device is connected)
 For each parent ECB, all child ECBs (each child ECB represents the device).
The hierarchy of the system is reflected in the Network Object Selection dialog box (Figure 3-2).
You can refresh the entire system's hierarchy (CPs, FBMs and devices) by clicking All in the
Refresh database section of the dialog box. You can refresh children under the CPs by selecting the
corresponding CP and clicking the Children or update only the child devices of FBMs by select-
ing the corresponding FBM and clicking Children.
In this chapter, the Network Object Selection dialog box is used to acquire the ECB information
online from the I/A Series Compound Summary Access (CSA) instance. For offline configura-
tion, the Network Object Selection dialog box presents ECB information in the EFS database
that was either imported or entered manually. Offline configuration is covered in Chapter 4
“Offline Configuration: Bulk Data Import” and Chapter 5 “Offline Configuration: Manual
Entry”.
In the I/A Series systems, the system tag of the device is a unique identifier. The tag is the full path
name (COMPOUND:BLOCK) of the ECB that maps the device or FBM. In the Network
Object Selection dialog box in Figure 3-2, the display for workstation MESH05 has been
expanded to show the two control processors (MC6F05 and MFC75F) assigned to it. In turn, the
52
3. Online Configuration B0400EF – Rev H
display for MC6F05 has been expanded to show the ECBs for an FBM (FB0043) the devices
assigned to it.
Figure 3-2. EFS Displaying I/A Series Hierarchy
The following FBMs and associated ECBs are used with PACTware and EFS:
Table 3-1. 200 Series FBMs and Associated ECBs
Communication Parent (FBM) Child (Device)

FBM FBM Description Protocol ECB ECB
FBM214 HART Communication HART ECB200 ECB201
Input Interface Module
FBM215 HART Communication Out- HART ECB200 ECB201
put Interface Module
Redundant Input Interface
Module
Redundant Output Interface
Module
FBM243 Dual Baud Rate Intelligent FoxCom ECB73 ECB18 or
Device Interface Module ECB74
(DIN Form factor)
FBM246 Redundant Dual Baud Rate FoxCom ECB38R ECB18 or
Intelligence Device Interface ECB74
Module (DIN Form factor)
In addition to the FBMs listed in the Table 3-1, EFS is backward compatible and can be used
with the FBMs in Table 3-2.
53
Table 3-2. 100 Series FBMs and Associated ECBs
FBM FBM Description Parent (FBM) ECB Child (Device) ECB

FBM18 Intelligent Transmitter ECB12 ECB18
Interface Module
FBM39 Intelligent Transmitter/0 to ECB23 ECB18
20 mA Output Interface
Module
FBM43 Dual Baud Rate Intelligent ECB12 and ECB73 ECB18 or ECB74
Transmitter Interface Module
FBM44 Dual Baud Rate Intelligent ECB23 ECB18
Transmitter/0 to 20 mA Out-
put Interface Module
FBM46 Redundant Dual Baud Rate ECB23 and ECB38R ECB18
Interface to Intelligent
Transmitters and Redundant
Analog Outputs
In addition to the FBMs listed in the Table 3-1 and Table 3-2, EFS V2.3 supports 200 Series
FBMs introduced with I/A Series V8.6 release for replacement of corresponding 100 Series FBMs
(Table 3-3).
Table 3-3. New 200 Series FBMs and Associated ECBs
Parent (FBM) Child (Device)

FBM243b Replaces the FBM39. The FoxCom ECB23 ECB18
FBM243b contains four
dual baud, FoxCom com-
munication channels and
four 0 to 20 mA analog out-
puts for similar field devices.
FBM244 0 to 20 mA I/O interface HART ECB200 ECB201
module with HART sup-
port. The FBM244 contains
four input and four output
channels, supporting any
mix of standard 4 to 20 mA
devices and HART devices.
FBM245 Redundant version of the HART ECB200 ECB201
FBM244
54
Table 3-3. New 200 Series FBMs and Associated ECBs
Parent (FBM) Child (Device)

FBM246b Replaces the FBM46. The FoxCom ECB38R ECB18
FBM246b contains four
dual baud, FoxCom com-
munication channels and
four 0 to 20 mA analog out-
put channels. Can be
installed as redundant pairs.
FBM247 Universal FBM that sup- HART ECB200 ECB201
ports configurable HART
channels - see B0400FF for
details.
Workflow for Online Configuration

Figure 3-3 depicts the workflow described in this chapter.
Figure 3-3. Configuring Devices for Maintenance and Tuning Online
55
Initialize the Device Catalog and Start a Project

The first step is to start PACTware and update the Device Catalog to ensure that all DTMs
installed on the workstation are loaded into the catalog.
To initialize the Device Catalog, proceed as follows:
popup menu.
main menu and toolbar at the top of the window, a Project view on the left or at the
top of the window and a Device view. Initially, the Project view includes a single node,
device DTMs associated with them. When you select any item in this Project view,
the parameters for the DTM are displayed in the Device view.
Main Menu
Toolbar
Project View Device

Catalog
Icon
Device View
Figure 3-4. PACTware Project Window
2. Choose View > Device Catalog from the PACTware main menu or click the
Device Catalog icon ( ) in the PACTware toolbar to open the Device Catalog
(Figure 3-5).
The catalog lists the DTMs currently available for the project.
the PACTware database, and click Yes when the confirmation dialog box (Figure 3-5)
prompts you to Create a new PACTware device catalog?
56
Figure 3-5. PACTWare Device Catalog
NOTE
PACTware.
At this point, you are creating a new project, which you can name at any time by
choosing File > Save from the main menu. You can also edit an existing project by
choosing File > Open from the main menu and selecting the project in the Open
dialog box.
4. Click in the PACTware title bar to close the application.
Configure the FBM Communication DTM

Use the PACTware Frame Application to configure the FBM communication DTM. The
sequence described below presumes that the FBM and device ECBs are deployed and that the
I/A Series system is functional.
To associate the communication DTM with an online FBM ECB:
57
1. Right-click HOST PC in the PACTware Project view (Figure 3-4), and choose Add
device from context menu to open the Device for HOST PC dialog box
(Figure 3-6).
Figure 3-6. Device for HOST PC
2. Select FBM Communication (HART) and click OK to add the DTM to HOST PC in
the Project view and close the dialog box.
3. Double-click on the DTM in the Project view to display the Parameters dialog box,
which is used to identify the FBM and attached devices by their ECBs (Figure 3-7).
58
Figure 3-7. FBM Communication DTM Parameters
4. Click Browse in the Parameter dialog box to open the Network Object Selection dia-
log box (Figure 3-8, left).
5. Click All in the Refresh box to bring all the online devices into the Network Object
Selection dialog box.
PACTware queries the I/A Series Compound Summary Access (CSA) for the deployed
ECBs that are compatible with the HART FBM Communication DTM. The dialog
box displays a hierarchy of workstations, control processors, FBM ECBs and the
device ECBs assigned to each FBM (Figure 3-8, right). You only need to perform this
step once, if there are no more ECBs deployed to the I/A Series system.
59
Figure 3-8. Network Object Selection Dialog Box
6. Select the FBM that you want to configure for the HART devices and click OK (or
click Close to exit the dialog box without making a selection).
The ECB fields in the Parameter dialog box are now populated with ECB names from
the I/A Series system. In Figure 3-9, the FBM is an eight-channel HART FBM, with a
device attached to each channel.
NOTE
The Network Object Selection dialog box prevents you from selecting an already
configured FBM to preclude re-configuration of the FBM Communication DTM.
If you select a previously configured FBM, the dialog box prompts you to make
another choice.
NOTE
To ensure that the PACTware project reflects what actually exists in the I/A Series
system, use the Network Object Selection box to populate ECB fields in the Param-
eters dialog box, rather than manually entering ECB names.
60
Figure 3-9. FBM Communication DTM Parameters
NOTE
The CHAN1 ECB through CHAN8 ECB fields are enabled or disabled based on
the number of devices supported by the ECB type. Thus, for an FBM243b or
FBM246b, only CHAN1 ECB through CHAN4 ECB would be enabled
(Figure 3-10).
61
Figure 3-10. Dialog Box Shows Four FBM Channels
7. Click OK to save and close the dialog box.

The DTM is now identified by the FBM ECB name in the Project view
(Figure 3-11).
Configure Devices in PACTware

NOTE
Refer to Appendix D “Choosing a Proper DTM for a Field Device” to choose the
correct DTM for a device from Code Wrights DTM library.
To associate an instance of a device DTM with device on an FBM channel:

1. Choose View > Device Catalog if the catalog is not already open on the screen.
2. Select the FBM ECB in the Project view.
62
3. Click the device manufacturer in the Vendor tab in the Device Catalog to list devices
from that vendor on the right.
4. Double-click the device in the catalog to open the Select Communication Channel
dialog box (Figure 3-11).
Figure 3-11. Adding a Device DTM
5. Select the proper communication channel and click OK.

The device DTM is added to the selected communication channel of the FBM com-
munication DTM and the device is shown in the PACTware Project view
(Figure 3-12).
6. Double-click the device in the Project view to open the DTM in the Device view
(Figure 3-12).
7. Modify the device parameters using the editing interface provided by the DTM.
Refer to the device and DTM documentation.
8. Save and close the DTM.
63
Figure 3-12. Configuring the Device DTM
9. Right-click a column header in the Project view and choose Online State from the
context menu to add the column to the Project view (Figure 3-13).
10. Right-click the header a second time and choose Channel from the context menu.
11. Right-click the FBM Communication (HART) DTM in the Project view, choose
Connect from the context menu and verify that the communication DTM is online.
The icon in the Online State column changes from to with a green back-
ground indicating that the DTM is online.
64
Figure 3-13. Verifying Communications DTM
12. Right-click a device DTM in the Project tree, choose Connect from the context menu
and verify that the device DTM is online.
The icon in the Online State column changes from to with a green back-
ground indicating that the DTM is online.
NOTE
The green background in Online State is not a sufficient check to confirm that the
device is online and that the correct DTM has been selected. A successful upload
from the device (Load from Device described in the next section) will confirm that
the device is online and the DTM is correct.
Configuring the Device

Once you have established connectivity with a field device, you can upload parameters from the
device to the DTM and/or download configurations from the DTM to the device.
65
The following sequence is recommended, especially if application specific-parameters have been

set in the device at the factory:
1. Right-click the device in the Project view and choose Connect from the context menu
to go online to the device.
2. Right-click the device in the Project view and choose Load from Device in the con-
text menu to upload parameter values to the DTM.
3. Choose File > Save from the PACTware main menu to save the uploaded values in
the project.
4. Double-click the device in the Project view to open the DTM and edit the parameters
using the functions provided by the DTM (Figure 3-14).
NOTE
If you need to make extensive changes to the configuration, you may want to take
the DTM offline, edit and save the configuration, then reconnect and download the
changes by choosing Store to Device from the device’s context menu in the Project
view.
66
Figure 3-14. Editing the Slave Device Online
5. Right-click the device in the Project view and choose Disconnect from the context
menu to go offline.
Save and Close the PACTware Project

Do the following if you have not already saved the PACTware project:
1. Choose File > Save from the PACTware main menu to open the Save dialog box.
2. Enter a project name and specify location for storing the project file.
3. Click Save, and then exit PACTware.
Do the following if you have already saved the project once.
 Choose File > Save from the PACTware main menu, and then exit PACTware.
67
Configuring a Router DTM with a DVC 6000

PACTware supports configuration of an Emerson DVC 6000 connected to the I/A Series system
via an FBM for maintenance and tuning using the FieldVue DTM (successor to the Router
DTM) and a device DTM.
Please note the following:
 Emerson now offers a FieldVue DTM, and recommends FieldVue DTM over the
older Router DTM.
 The FieldVue DTM and Router DTM are installed to be able to utilize the AMS
ValveLink Snap-On.
 The FieldVue DTM and Router DTM are not supported by EFS for device scanning
for asset management.
 The FieldVue DTM and Router DTM are not included in the CodeWrights DTM
library. Contact the vendor for the DTMs software.
 Use DVC6000 V2.1 DTM from the CodeWrights DTM library for the device itself.
NOTE
See I/A Series EFS 2.3 Release Notes (B0400EH-D) for further details.
To set up the FieldVue DTM and device in PACTware for device maintenance and tuning:
1. Install the FieldVue DTM on the workstation, start PACTware and update the Device
Catalog.
2. Start a PACTware project or open an existing project.
3. Add the FieldVue DTM to the appropriate instance of the FBM Communication DTM
and then add DVC6000 V2.1 DTM to the correct channel of the router DTM.
4. Install the devices, and test connectivity to the FieldVue DTM and device DTMs.
NOTE
To configure a DVC6000 in PACTware for EFS scanning, add the DVC6000 V2.1
DTM from the CodeWrights DTM library directly to the appropriate FBM
channel. Do not use the FieldVue DTM or the Router DTM.
Important Note about EFS Scanning of Field Devices

At this point, you can configure the device for EFS scanning, adding the device to a scan list and
setting the scan frequency. See Chapter 7 “Configuring Devices for EFS Scanning” for informa-
tion on adding the device to the scan list and starting and stopping the scanning service.
If the device is on a scan list and you need to access the device via PACTware and the device
DTM for maintenance or diagnostics, make sure that the scanning service is stopped before
you connect to the device. Stopping the scanner service will avoid communication errors and
possible device configuration problems.
68
4. Offline Configuration: Bulk Data
Import
This chapter describes how to associate communication and device DTMs with HART and
FoxCom field devices offline, that is, before the FBM and device ECBs have been deployed. The
method discussed in this chapter is importing the device information into PACTware from an
Microsoft Excel spreadsheet. Manual entry of the ECB names is discussed in the next chapter.
Introduction
Connectivity to the intelligent field devices in an I/A Series System is provided through equip-
ment control blocks (ECBs). During the engineering phase, ECBs may not be online or hardware
may not be present. Starting with Version 2.0, EFS supports the configuration of field devices in
this offline environment.
See “Intelligent Field Device Connection to an I/A Series System” on page 52 for additional infor-
mation on I/A Series system equipment hierarchy, FBM types, and parent (FBM) and child
(device) ECBs.
In offline configuration, PACTware acquires the ECB information from the EFS database rather
than from the deployed ECBs in the I/A Series system. You can add the ECB information to the
database with either Bulk Import, discussed in this chapter, or Manual Entry, as described in
Chapter 5 “Offline Configuration: Manual Entry”. With either approach, a validation sequence
must be performed when the hardware is present in the system and the ECBs have been deployed.
Manual entry of ECB information into the configuration screen of the DTM for the FBM may
be appropriate for small projects, but for larger projects, it is more efficient to enter ECB informa-
tion into an Excel spreadsheet and then import data into the EFS database for use in the
PACTware project.
NOTE
The FBM Communication DTMs use the information present in the EFS database
and not the information present in the PACTware project to identify the ECBs to
which they will connect.
If the EFS database is lost and a newly initialized database is used, the existing PACTware project
files should not be used. The offline definition of the EFS database must be performed first.
NOTE
Always make a backup of the EFS database. If the database is lost, it can be restored
from the backup avoiding the need to re-generate the database.
Microsoft SQL Server 2008 is the recommended database application for EFS. The standard
backup and recovery procedures for the Microsoft SQL databases should be followed.
69
B0400EF – Rev H 4. Offline Configuration: Bulk Data Import
Once you have configured the EFS database offline, you can use the database to create a
PACTware project associating communication and device DTMs with the imported ECBs.
When the system hardware is installed and the ECBs are deployed, a validation function checks
the EFS database against the deployed ECB configurations in the Compound Summary Access
(CSA).
The validation function detects any errors such as spelling mistakes and incomplete data. The
result of the validation is an EFS database that represents the deployed system. Any differences
between the EFS database and the deployed system hardware are recorded in a validation log file.
Figure 4-1 depicts the workflow described in this chapter.
Figure 4-1. Device Configuration Starting with Bulk Data Import
Creating a Worksheet for Bulk Import

Starting with Version 2.0, EFS features a bulk data entry method of loading data from an Excel
spreadsheet and provides the template EFS.xls for entering ECB information in a fixed format
for the import. The template is located in the Database folder in the EFS installation folder; for
example:
C:\Program Files\Invensys\FDM_EFS\Database, when the software is installed
to the default installation folder, or
70
4. Offline Configuration: Bulk Data Import B0400EF – Rev H
D:\Invensys\FDM_EFS\Database in an I/A Series workstation.

To prepare a spreadsheet for bulk data import:
1. Make a copy of ...\FDM_EFS\Database\EFS.xls to use as your working bulk data
entry spreadsheet.
In this example, the copied spreadsheet has been renamed EFS_Example.xls.
2. Open the working spreadsheet and enter the appropriate ECB and FBM information
as indicated by the column heads (Figure 4-2).
 Identify the FBMs and devices using the full pathname of their equipment control
blocks (FCP333_ECB:ARC_1A, for example).
 Place the cursor over the FBM TYPE cell to display the tooltip help to identify the
correct FBM type, then use pull-down list column to select the FBM type.
NOTE
During import of FBMs and associated child ECB information, if the number of
channels supported by an FBM type is four (FBM243b and FBM246b), only the
first four child ECB entries for that FBM are imported and the remaining are
ignored. The ignored child ECB entries information are logged into
EFSBulkImport.log file.
3. Save the spreadsheet as an Excel 97-2003 Worksheet (extension .xls).

Excel 2007 worksheets (extension .xlsx) are not compatible with the EFS import
function.
Figure 4-2. Entering ECB Information in the Excel Spreadsheet
Importing the ECB Data from Excel to EFS

This section is divided into two scenarios: one in which there are no records in the EFS database
at the time of import, the second when the spreadsheet is imported into an existing EFS database
to add new ECBs and/or correct existing records in the database.
71
Refer to the workflow listed in Figure 4-6 “Updating the EFS Database with Bulk Imports” on
page 75 for additional details on how to implement these scenarios.
Importing to a New EFS Database

To start an EFS database by importing ECBs from an Excel spreadsheet:
1. Open PACTware, add an FBM Communication DTM to Host PC and double-click
the new FBM in the Project view to display the Parameter dialog box for the DTM
(Figure 4-3).
See “Configure the FBM Communication DTM” on page 57 for step-by-step
instructions.
2. Click Browse to open the Network Object Selection dialog box (Figure 4-3).
3. Click the check box for Import from Excel in the Refresh database box in the
upper right and then click All.
Figure 4-3. Parameter Dialog Box for a New FBM
4. Use the Open dialog box (Figure 4-4) to browse for and select the spreadsheet, and
click Open.
72
Figure 4-4. Open Dialog
The data is entered into the database with each row in the spreadsheet becoming an
FBM record, which includes:
 Full pathname of the FBM ECB (the parent ECB)
 Control processor to which the FBM will be connected
 Control processor’s software host
 Channel assignment for each device to be attached to the FBM
 Full pathname of the device ECBs (the child ECBs)
The resulting hierarchy is shown in the Network Object Selection dialog box
(Figure 4-5).
73
Figure 4-5. Select Device in PACTware
At this point, you can select one of the FBMs in the Network Object Selection to begin associat-
ing FBM and device ECBs with the appropriate DTMs, as described for online configuration in
Chapter 3 “Online Configuration”. The only difference is that the Network Object Selection dia-
log box displays ECBs read from the EFS database rather than from the I/A Series system.
You can also click Close in the Network Object Selection dialog box and exit PACTware without
saving the project, having populated the EFS database with the ECB names. The EFS database is
not specific to any one PACTware project and can be used with any new or existing PACTware
project on the workstation.
Importing to an Existing EFS Database

After the initial import, you can import from the same or different Excel spreadsheets to add to or
correct entries in the database. An import validation routine and import log help you reconcile
differences between the database and the data being imported.
EFS supports successive imports of the bulk data from multiple sources that can be expected as
you build the EFS database because of the following:
 Phased engineering of the devices to be used in the plant
 Input from multiple engineers assigned to device configuration by plant area or con-
trol processor
 Use of multiple spreadsheets, each created for a different PACTware project
 Changes to the configurations arising out of qualification of the devices
74
 Engineering changes such as new devices added to FBMs already in the database
 Devices moved to different channels in the same FBM or to a different FBM for bal-
ancing of load or optimizing wiring
 Needed corrections to ECB names.
Figure 4-6 shows the workflow for modifying the EFS database in these situations. In Step 8, the
user chooses whether to overwrite the ECB names in the database with the imported data, as
described in this section. You can import the data twice, selecting No on the first pass to make no
changes to the database and use the import log to identify conflicts. You can then modify the
source Excel spreadsheet to fix any problems in the data. Then, on the second import, you select
Yes in step 8 to implement the changes, and clear any incorrect records from the EFS database.
Figure 4-6. Updating the EFS Database with Bulk Imports
To edit an existing EFS Database:

1. Start a PACTware project or open an existing project and the follow the instructions
in the preceding section to:
a. Add an FBM Communication DTM, open the DTM in the Parameter dialog box
and then click Browse to open the Network Object Selection dialog box.
b. Use the dialog box to import the Excel spreadsheet.
If an imported FBM ECB has the same name as an existing FBM ECB record, EFS
compares the imported data with the record. If there is a data mismatch, the Offline
Configuration dialog box (Figure 4-7) asks whether you want to overwrite the mis-
matched data, replacing records in the EFS database with imported data.
75
Figure 4-7. Offline Configuration Dialog Box
The dialog box is presented when the first mismatch is encountered. The option you
select is applied to that mismatch and all subsequent conflicting records. Data already
imported is not affected by your choice.
See Table 4-1 on page 78 for more details on how EFS handles conflicts between
imported data and records already in the EFS database.
2. Do one of the following to resolve the mismatches:
 Click Yes to overwrite the FBM ECB record with the imported data.
 Click No to insert only new FBM ECBs.
 Click Cancel to stop the import.
Records already imported are retained.
Whichever option you select, EFS records the transactions to the file EFSBulkIm-
port.log in the log folder in the EFS installation folder; for example:
C:\Program Files\Invensys\FDM_EFS\log, when the software is installed to
the default installation folder, or
D:\Invensys\FDM_EFS\log in an I/A Series workstation.
Figure 4-8 is an example of the log file when the user selected Yes to overwrite mis-
matched records.
Figure 4-8. EFSBulkImport.log, Yes Selected in the Offline Configuration Dialog Box
76
Figure 4-9 is an example of the log file when the user decided not to overwrite mismatched
records and selected No in the Offline Configuration dialog box (Figure 4-7).
Figure 4-9. EFSBulkImport.log, No Selected in the Offline Configuration Dialog Box
3. Review the import log to locate errors in either the spreadsheet or the EFS database.
4. Use the spreadsheet to correct all errors and then re-import the spreadsheet selecting
Yes to overwrite any EFS database records that do not match the imported data.
Resolving Conflicts within the Imported Data

During editing of imported entries from the spreadsheet, there might be conflict between the data
present in an imported record and the data existing in the EFS database. But first, the import val-
idation resolves duplicate device ECB names in the imported data itself. For example, the shaded
cells in two imported records below show duplicate device ECB names, one assigned to channel 1
of the FBM in the first row, the second assigned to channel 2 of the FBM in the second row.
FBM ECB HOST AW CP LETTERBUG FBM TYPE CHAN1 ECB CHAN2 ECB
FCP701_ECB:IFBM03 XP1HPS FCP701 214 FCP701_ECB:IDEV01 FCP701_ECB:IDEV02
The import function overwrites the previously imported child ECB entries with that of the last
entry. In the example, when the second record is imported, the validation process deletes the entry
created for device FCP701_ECB:IDEV01 under FBM FCP701_ECB:IFBM03, and adds all of
the data for the second FBM (FCP701_ECB:IFBM04) as is.
FBM ECB HOST AW CP LETTERBUG FBM TYPE CHAN1 ECB CHAN2 ECB
FCP701_ECB:IFBM03 XP1HPS FCP701 214 FCP701_ECB:IDEV02
77
Resolving Conflicts Between the Imported Data and the

Database
See Table 4-1 details how EFS handles conflicts between imported data and records already in the
EFS database. The right column in the table shows how the EFS handles the conflict based on
you choice in the Offline Configuration dialog box (Figure 4-12). Remember that the dialog box
is presented when the first mismatch is encountered and that the option you select is applied to all
subsequent records in the imported data.
Table 4-1. Resolving Conflicts Between Imported Data and the EFS Database
Child ECBs in the Conflicting Handling, Option Selected in the

Imported FBM ECB Imported FBM Record Offline Configuration Dialog Box
Name matches a data- Child ECBs match those in No changes to EFS database. The imported record is
base record the database for the FBM skipped. The skipped record is logged to Bulkimport.log
file
Name matches a data- The import includes some New ECBs are added to EFS database. Matching ECB
base record new ECB entries and ECB entries are left untouched. Updated records are logged
entries matching ECBs in to BulkImport.log, which provides the original (before
the database for this FBM import) and final data (after import).
Name matches a data- Import includes some new Click Yes to write imported data to database, adding
base record ECB entries and other ECB new ECB entries for the previously unassinged chan-
entries that do not match nels, and replacing existing records for those channels
names already assigned to where the names did not match.
the channel for the FBM Records that were added or modified are logged in Bulk
import.log, which provides the original (before import)
and final data (after import) for this record in EFS data-
base.
Click No to make no changes to the EFS database, but
log the skipped spreadsheet record to Bulkimport.log.
Click Cancel to stop the import. All entries imported
prior to the first mismatch are retained in the EFS data-
base and all subsequent spreadsheet records, including
the first mismatch, are not processed.
Name matches a data- An imported record does Click Yes to delete ECB entries from the database that
base record not have definitions to all are not in the imported data. Matching records are left
the child ECB entries in untouched.
EFS database. Overwritten records are logged to Bulkimport.log, listing
Other device ECB entries in the original (before import) and final data (after import)
the import match ECBs in for this record in EFS database.
the database Click No to make no changes to the EFS database, but
log the skipped spreadsheet records to Bulkimport.log.
78
Table 4-1. Resolving Conflicts Between Imported Data and the EFS Database (Continued)
Child ECBs in the Conflicting Handling, Option Selected in the

Imported FBM ECB Imported FBM Record Offline Configuration Dialog Box
Name matches a data- An imported record does Click Yes to add new device ECBs and modify existing
base record not have definitions to all device ECB records in the database with ECB names in
the child ECB entries in the imported data.
EFS database. Overwritten ECB records in the database are logged to
Other device ECB entries in Bulkimport.log, listing the original (before import) and
the import do not match the final data (after import) for record in EFS database.
ECB assigned to the same Click No to make no changes to device ECBs in the EFS
channel in the database database, but log the skipped spreadsheet record to
Bulkimport.log.
ECB name in the spread- All child ECB entries asso- FBM ECB and the device ECBs assigned to it are added
sheet is not found in EFS ciated with the FBM are to the database
database new, that is, the ECB
names are not associated
with another FBM ECB
ECB name in the spread- Some child ECB entries Click Yes to add the imported data and delete the dupli-
sheet is not found in EFS associated with the FBM cate device ECB names that were assigned to other
database are new, but others are FBM ECBs.
associated with another Overwritten database records are logged to
FBM ECB Bulkimport.log, listing the original (before import) and
final data (after import) for record in EFS database.
Click No to make no changes to device ECBs already in
the EFS database, but log the skipped spreadsheet
records to Bulkimport.log.
You can now associate DTMs with the FBM and device ECBs as described for online configura-
tion in Chapter 3 “Online Configuration”, except that the Network Object Selection dialog box
displays ECBs imported from the EFS database rather than from the I/A Series system.
Validating the Offline Configuration

After the I/A Series System is available and the ECBs are online, you should verify the contents of
the EFS database against the I/A Series system Compound Summary Access (CSA).
NOTE
Do not export a PACTware project to EFS to configure EFS scanning until all ECBs
are fully validated against the ECBs in the CSA.
You may need to run offline validation several times, as the FBMs and attached devices are
deployed in phases, changes are made to the configuration, and corrections are made to the EFS
database through imports from an Excel spreadsheet or manual entry. Figure 4-10 is a workflow
for a single pass of validating an offline configuration. In step 6, the user decides whether to
remove unvalidated ECBs, that is, ECBs that are in the EFS database but not present in the
79
I/A Series system. For the first pass at validation, you should answer No at step 6 and use the vali-
dation log to resolve differences between the I/A Series system and the EFS database. Several iter-
ations may be needed, as additional FBMs and device are deployed, adjustments made to the field
devices and naming conflicts are resolved. When the discrepancies have been resolved and all the
FBMs and devices are deployed, you can run the validation again, this time answering Yes in
step 6 and removing unvalidated ECB records from the database.
Figure 4-10. Incremental Validation of an Offline Configuration
To validate the data:

1. Start PACTware project and add an FBM Communication DTM to HOST PC.
2. Open the DTM in the Parameter dialog box and then click Browse to open the
Network Object Selection dialog box (Figure 4-11).
80
Figure 4-11. Network Object Selection Dialog Box
3. Click the Validate button in the dialog box to validate the EFS database.
EFS queries the CSA for ECBs that have been deployed to the I/A Series system and
compares the deployed ECBs with those defined in the EFS database.
The Network Object Selection dialog box allows you to run Validation only once per
invocation to prevent workflow-related issues. Once you click the Validate button, all
buttons and options are disabled with the following conditional exceptions:
 If an FBM ECB is selected and there are no validation errors, the OK button is
enabled.
Click OK to assign the selected FBM ECB and its device ECBs to the communica-
tion DTM and close the Network Object Selection dialog.
 If there is a validation error, the Close button is enabled.
Click Close to exit the Network Object selection dialog.
EFS displays the Offline Configuration dialog box (Figure 4-12).
Figure 4-12. Offline Configuration Dialog Box
81
NOTE
If an FBM entry is validated as a four-channel FBM (FBM243b or FBM246b), any
entries for channels 5 to 8 are removed from EFS database if you selected Yes in
Offline Configuration dialog box. Log entries describing the deleted records are
logged to EFSValidate.log.
4. Do one of the following to resolve differences between the I/A Series system and the
EFS database:
 Click Yes to delete all records in the EFS database that do not match a corre-
sponding ECB in the I/A Series system.
 Click No to keep all records in the EFS database even those that do not match the
corresponding ECB in the I/A Series system. This enables you to perform partial
validations as FBMs are commissioned in the system.
 Click Cancel to take no action.
Important Exception
Whether you select Yes or No, EFS resolves a mismatch between a device (or child)
ECB name in the EFS database and the actual ECB name read from CSA by doing
the following:
 Deletes the record of the device in EFS database with all offline information
including the device information and DTM information.
 Creates a new record with the device information fetched from CSA.
A mismatch could include the ECB in the database being assigned to a different
channel of the same FBM or to a channel of a different FBM.
All records in the EFS database that are found in the I/A Series system are marked as
validated. During validation, records previously validated are skipped.
If there is an ECB in the CSA that is not in the EFS database, EFS adds that ECB to
the database.
EFS records the validation results to EFSValidate.log in the log folder in the EFS
installation folder; for example:
C:\Program Files\Invensys\FDM_EFS\log, when the software is installed to
the default installation folder, or
D:\Invensys\FDM_EFS\log in an I/A Series workstation.
The report also shows any records that were deleted from the EFS database.
The log in Figure 4-13 resulted from a validation in which the user opted to delete all
records in the EFS database that were not validated, that is, that were not found in the
CSA. The user made the choice by clicking Yes in the Offline Configuration dialog
box (Figure 4-13).
82
Figure 4-13. EFSValidate.log, Yes Selected in the Offline Configuration Dialog Box
The log in Figure 4-14 resulted from a validation in which the user opted to maintain
all records in the EFS database even those that were not validated. The use made that
choice by click No in the Offline Configuration dialog box (Figure 4-13).
Figure 4-14. EFSValidate.log, No Selected in the Offline Configuration Dialog Box
EFSValidate.log has multiple sections with headers that can be interpreted as follows:
The following entries are Validated:
These entries were successfully validated, that is, the records in the EFS database
matched the ECBs in the CSA.
The following entries are not found online and retained in the data-
base:
The entries logged under this section were not found in the CSA, but are retained in
the EFS database because user selected No in the Offline Configuration dialog box
(Figure 4-12).
The following entries are not found online and deleted in the data-
base:
83
The entries logged under this section were not found in the CSA and were deleted
from the EFS database because user selected Yes in the Offline Configuration dialog
box (Figure 4-12).
The following entries are Inserted from CSA:
These entries were added to the EFS database from the CSA.
Errors in the EFS database such as an incorrect control processor letterbug or FBM type are
logged under the appropriate sections, as shown in the following examples:
HOST AW Entry for FBM <FBM_ECB_NAME> is not correct, as per CSA.
CP LETTERBUG Entry for FBM <FBM_ECB_NAME> is not correct, as per CSA.
FBM Type Entry for FBM <FBM_ECB_NAME> is not correct, as per CSA.
Communication Device for device <FBM_ECB_NAME> is not correct, as per
CSA
Communication Device for device <DEVICE_ECB_NAME> is not validated,
Device cannot be validated.
Channel Number of the device <DEVICE_ECB_NAME> is not correct, as per
CSA.
NOTE
If there is a mismatch between the parent and the child device ECB such that the
child device is entered against a different parent, the record cannot be validated.
Figure 4-15. Log file for Parent and Child Device ECB Mismatch
Table 4-2 provides a detailed description of how the validation process handles differences
between the CSA and the EFS database.
Table 4-2. How Validation Resolves Differences Between CSA and the EFS Database
FBM ECB Device ECBs Action

Name in the CSA matches an FBM All child ECBs of this FBM ECB EFS database records are validated and
ECB name in the EFS database in the CSA match EFS data- these validated records are logged to
base EFSValidate.log
84
Table 4-2. How Validation Resolves Differences Between CSA and the EFS Database (Continued)
FBM ECB Device ECBs Action

Name in the CSA matches an FBM CSA shows some new child New child ECB entries from the CSA are
ECB name in the EFS database ECB entries which are not found inserted into EFS database. ECBs in the
in EFS database and some that database that match those in the CSA are
match ECBs in the database untouched.
Click Yes to delete any unvalidated
records and log them to EFSValidate.log.
Click No to retain unvalidated records and
log them to EFSValidate.log.
Name in the CSA matches an FBM CSA shows some new child New child ECBs from CSA are inserted
ECB name in the EFS database ECB entries which are not found into EFS database and marked validated.
in EFS database and some that Previously validated ECBs in the data-
do not match ECBs in the database are untouched.
base ECBs in the database that do not match
ECBs in the CSA are left unvalidated.
Click Yes to delete the unvalidated
records.
Click No to retain the unvalidated ECBs.
Records validated and inserted are
logged to EFSValidate.log file.
FBM ECB name in the CSA Some channels for this FBM EFS database records that match records
matches an FBM ECB name in the have ECBs assigned in the in the CSA are marked validated.
database database record but not in the A database entry for which there is no
CSA data matching entry in the CSA is left unvali-
There are other channels for dated.
which there are matching Click Yes to delete unvalidated records.
records in the database and Click No to retain the unvalidated records.
CSA All transactions are logged to EFSVali-
date.log
FBM ECB name in the CSA Some channels for this FBM ECBs in the database that do not match
matches an FBM ECB name in the have ECBs assigned in the ECBs in the CSA are left unvalidated.
database database record but not in the Click Yes to delete the unvalidated ECBs.
CSA data. There are other Click No to retain the unvalidated records.
channels for which for which the All transactions are logged to EFSVali-
ECB name assigned in the date.log
database does not match the
name in the CSA.
FBM ECB name found in the CSA is Child ECB names associated Entries in the CSA query output are
not found in the EFS database with the FBM in CSA are not inserted into EFS database.
found in the EFS database All transactions are logged to EFSVali-
date.log
FBM ECB name found in the CSA is Some child ECB names associ- The data from the CSA is presumed to be
not found in the EFS database ated with the FBM in CSA are correct. The FBM ECB and its child ECBs
assigned to other FBMs in the are added to the EFS database and
EFS database marked validated.
ECBs incorrectly assigned to another
FBM ECB in the database are deleted.
These actions are not dependent on your
choice of Yes or No in the Offline Configu-
ration dialog box.
All transactions are logged to EFSVali-
date.log
Once the EFS database has been fully validated, you can configure the devices for EFS Scanning,
as described in Chapter 7 “Configuring Devices for EFS Scanning”.
85
86
5. Offline Configuration: Manual
Entry
This chapter describes how to associate communication and device DTMs with HART and
FoxCom field devices offline, that is, before the FBM and device ECBs have been deployed. The
method discussed in this chapter is to manually enter ECB information into the EFS database.
Bulk data import of ECB information is discussed in the previous chapter.
Introduction
Connectivity to the intelligent field devices in an I/A Series System is provided through equip-
ment control blocks (ECBs). During the engineering phase, ECBs may not be online or hardware
may not be present. Starting with Version 2.0, EFS supports the configuration of field devices in
this offline environment.
See “Intelligent Field Device Connection to an I/A Series System” on page 52 for additional infor-
mation on I/A Series system equipment hierarchy, FBM types, and parent (FBM) and child
(device) ECBs.
In offline configuration, PACTware acquires the ECB information from the EFS database rather
than from the deployed ECBs in the I/A Series system. You can add the ECB information to the
database with either Manual Entry or Bulk Import. With either approach, a validation sequence
must be performed when the hardware is present in the system and the ECBs have been deployed.
For larger projects, it is more efficient to enter ECB information into an Excel spreadsheet and
then import data into the EFS database for use in the PACTware project, as described in
Chapter 4 “Offline Configuration: Bulk Data Import”.
NOTE
The FBM Communication DTMs use the information present in the EFS database
and not the information present in the PACTware project to identify the ECBs to
which they will connect.
If the EFS database is lost and a newly initialized database is used, the existing PACTware project
files should not be used. However, the offline definition of the EFS database must be performed
first.
NOTE
Always make a backup of the EFS database. If the database is lost, it can be restored
from the backup avoiding the need to re-generate the database.
Microsoft SQL Server 2008 is the recommended database application for EFS. The standard
backup and recovery procedures for the Microsoft SQL databases should be followed.
Once you have configured the EFS database offline, you can use the database to create a
PACTware project and configure field devices with the DTMs installed in Chapter 2.
87
B0400EF – Rev H 5. Offline Configuration: Manual Entry
NOTE
Offline configurations do not update the EFS database with the information pro-
vided for performing the asset management device scans.
When the system hardware is installed and the ECBs are deployed, a validation function checks
the EFS database against the deployed ECB configuration.
The validation function detects any errors such as spelling mistakes and incomplete data. The
result of the validation is an EFS database that represents the deployed system. Any differences
between the EFS database and the deployed system hardware are recorded in a validation log file.
The EFS database must be completely validated against the I/A Series system before you configure
the database for scanning.
Steps 1 through 8 in Figure 5-1 depict the workflow described in this chapter. See “Offline Con-
figuration: Bulk Data Import” on page 69 for the remaining steps.
Figure 5-1. Device Configuration Starting with Manual ECB
88
5. Offline Configuration: Manual Entry B0400EF – Rev H
Entering ECB Information

To manually enter ECB information:
1. Open PACTware FDT Frame Application.
Starting with V2.0, EFS supports the use of multiple PACTware project files. As the
offline configuration is provided in IA mode only, use separate project files for IA and
Non IA mode configurations.
2. Choose File > Save from the PACTware main menu and use the Save dialog box to
name the project and specify its storage location.
3. Right-click HOST PC and choose Add device from the context menu to open the
Device for HOST PC dialog box.
4. Select FBM Communication DTM (HART) or FBM Communication DTM (FoxCom)
from the dialog box and click OK.
5. Double-click the new communication DTM to display the parent and child ECBs in
the Parameter dialog box (Figure 5-2).
Figure 5-2. Entering ECB Names
6. Enter the FBM ECB and device ECB names.

 Enter the full pathname name of each ECB (that is,
ECB_COMPOUND:BLOCK).
 Follow the I/A Series naming conventions for compounds and blocks. If you are
not familiar with them, these are detailed in Control Processor 270 (CP270) Inte-
grated Control Software Concepts (B0700AG).
89
7. Click OK.
The newly added ECB information is now stored in the EFS database.
You can now associate DTMs with the FBM and device ECBs as described for online
configuration in Chapter 3 “Online Configuration”.
8. Choose File > Save from the PACTware main menu and close the PACTware proj-
ect when you have finished adding the DTM information.
Editing Manually Entered Device ECB Information

Manual data entry can be used to modify ECB Information that has already been entered into the
EFS database, whether by manual entry or bulk data import. Modifications can include:
 Adding an FBM and devices to the configuration
 Adding devices to FBMs that have already been configured in the EFS database
 Moving a device to a different channel or a different FBM
 Deleting FBM and device ECBs
 Correcting ECB names.
Figure 5-3 shows the workflow for modifying existing device ECBs under a previously configured
FBM ECB.
Figure 5-3. Manually Entering Changes to EFS Database
90
To modify ECB information for any channel of an FBM DTM:

1. Start PACTware and choose File > Open from the PACTware main menu, select the
project in the dialog box and click Open.
2. Double-click the FBM Communication DTM whose channel information has to be
modified to display the ECB names in the Parameter dialog box (Figure 5-4).
3. Edit the required device ECBs and then click OK.
If there is no mismatch between the edited device ECBs and the existing device ECBs
in EFS Database, the edited information is saved in EFS Database and the Parameter
dialog box closes.
When there is any mismatch between the device ECB information already present in
the EFS database and the ECB information entered through manual configuration,
PACTware displays the Offline Comparison dialog box (Figure 5-4) asking whether
you want to overwrite the data in the EFS database.
a. Click Yes to overwrite entries in the EFS database. New entries entered manually
are added and the information in the EFS database is updated. The Parameter dia-
log box closes.
b. Click No to maintain the entries that already exist in the EFS database.
In the example in Figure 5-4, the user has manually deleted the child ECBs for chan-
nels 5 through 8 in the Parameter dialog box. The Offline Comparison dialog box is
asking the user whether the ECBs in the database should be overwritten with blanks.
Figure 5-4. Offline Comparison Dialog Box
91
Table 5-1 describes seven different scenarios where the data in the Parameter dialog box does or
does not match records in the EFS database, and the actions taken when you click Yes or No in
the Offline Comparison dialog box.
Table 5-1. Resolving Conflicts Between Manually Entered Data and The EFS Database
Manually Entered Manually Entered Option Selected in the Offline

FBM ECB Device ECBs Comparison Dialog Box
Matches name in EFS Match device ECBs in the No changes to EFS database. Dialog box not shown
database EFS database
Matches name in EFS Includes new ECBs, others Yes: New child ECB entries are added to the EFS
database match entries in the EFS database. Existing matched records in EFS data-
database base are left untouched.
No: No changes to EFS database
Matches name in EFS Includes new ECBs, other Yes: New child ECB entries are added to EFS data-
database ECBs do not match the ECB base. Existing mismatched EFS database records
name in the database for the are overwritten.
same channel No: No changes to EFS database.
Matches name in EFS The Parameter dialog box Yes: EFS database records not in the FBM configu-
database does not contain definitions ration screen are deleted from the EFS database.
to all the child ECB present Existing matched device ECB records in EFS data-
in the EFS database. See base are left untouched.
blank fields for channels 5 No: No changes to EFS database.
through 8 in Figure 5-4
Matches name in EFS The Parameter dialog box Yes: EFS database records not in the Parameter dia-
database does not contain definitions log box are deleted from EFS Database.
to all the child ECBs present Existing mismatched children records in EFS data-
in the EFS database. base are overwritten.
Parameter dialog box also No: No changes to EFS database.
contains entries that do not
match the name in the EFS
database for that channel
Name is not found in EFS Each child ECB entry in FBM ECB and its device ECB entries are entered
database. Parameter dialog box is new, into EFS database. Dialog box not shown
that is, there is no device
ECB in the database with
the same name
Name is new, that is, not A child ECB in the Parame- Close operation on the Parameter dialog box aborts
found in EFS database ter dialog box has the same writing FBM and child ECB information into EFS
name as an ECB already database with the message:
assigned to a different FBM Configuring FBM and its child ECBs
ECB in the database aborted. <Compound:Block> device
configured under this FBM is
already configured under another
FBM.
4. Choose File > Save from the PACTware main menu when you have completed the
edits and then exit PACTware.
Validating the Offline Configuration

When the I/A Series System is available and the ECBs are online, you should verify the contents
of the EFS database against the I/A Series System, as described for the bulk data import method in
“Validating the Offline Configuration” on page 79.
92
NOTE
Do not configure the EFS database for scanning until the database has been fully
validated against the I/A Series system.
93
94
6. Setting Up the EFS Database
Using Microsoft SQL Server 2008
This chapter describes how to configure the EFS database using Microsoft SQL Server 2008.
EFS instances can use either of two database applications for scanning and offline configuration:
 Microsoft Access, the default database, should be used with benchtop systems and for
proof of concept, but not for scanning in the production system.
 Microsoft SQL Server 2008 provides a robust database server suitable for operation of
large scale systems. The standard backup and recovery procedures for the Microsoft
SQL databases should be followed.
Configuration of the EFS database is required for the following applications:
 Offline configuration of FBMs and field devices using bulk data import from a
Microsoft Excel spreadsheet, as described in Chapter 4 “Offline Configuration: Bulk
Data Import”
 Manually entering FBM and device configurations into the EFS database, as
described in Chapter 5 “Offline Configuration: Manual Entry”
 Scanning HART and FoxCom devices for selected asset management data and com-
municating the data to the Invensys Condition Monitoring application and
Avantis.Pro. See Chapter 7 “Configuring Devices for EFS Scanning” for information
on selecting the devices to be scanned and setting the scanning rate.
NOTE
Configuration of the EFS database is not required if you are using PACTware and
EFS for online configuration of HART and FoxCom devices (described Chapter 3
“Online Configuration”) and will not be scanning the devices with EFS.
This chapter describes how to set up Microsoft SQL Server 2008, which includes defining the
database in SQL Server Management Studio and setting the DSN for the database server.
The chapter assumes that the Microsoft SQL Server 2008 software is already installed and prop-
erly configured. The database definition and DSN setting should probably be performed by your
on-site SQL administrator.
Setting up the EFS database with SQL Server involves the following tasks:
 Identifying SQL Server as the EFS database application in the EFS setup wizard. This
task may already have performed during software installation. This chapter begins
with instructions on switching the database selection if the software was installed with
Microsoft Access, the default selection.
 Creating the database itself using Microsoft SQL Server Management Studio as
described in “Create the New Database” on page 98.
95
B0400EF – Rev H 6. Setting Up the EFS Database Using Microsoft SQL Server
 Configuring the Data Source Name (DSN) along with setting authentication mode
and other database attributes. See “Set the DSN for the Microsoft SQL Server Data-
base” on page 103.
Refer to Appendix C “Database Migration” if you are upgrading an EFS scanning application
from Microsoft Access to Microsoft SQL Server 2008, or if you are migrating an EFS application
from Microsoft SQL Server 2005 to Microsoft SQL Server 2008.
Selecting Microsoft SQL Server 2008 as the Database

Application
If you selected Microsoft Access (the default) as the EFS database application during installation
of the software, change the selection now using the Change or Remove Programs applet in the
Control Panel:
1. Click the Start button the task bar, choose Settings > Control Panel from the
popup menu and double-click Change or Remove Programs in the Control Panel.
2. Choose Extended Frame Services 2.3 to open the setup wizard.
After inspecting the already installed software, the wizard displays a Welcome page,
which presents three options: Modify, Repair and Remove (Figure 6-1).
Figure 6-1. Welcome Page
3. Click the radio button for Modify and then click Next.
4. Check all components on the Selected Features page and then click Next to display
the Configure EFS Database dialog box (Figure 6-2).
96
6. Setting Up the EFS Database Using Microsoft SQL Server 2008 B0400EF – Rev H
Figure 6-2. Configure EFS Database Dialog Box
5. Click the radio button for Microsoft SQL Server Database and enter (local)
in the SQL Server field.
6. Ensure that the Login Name sa is sa.
7. Enter the password given for the sa login during Microsoft SQL Server 2008
installation.
8. Click OK.
9. Click Finish when the installation wizard displays the Maintenance Complete page
(Figure 6-3).
Figure 6-3. Maintenance Complete Page
97
Create the New Database

The next step is to create a new SQL database. To create the new database, proceed as follows:
1. Open the SQL Server Management Studio, right-click Databases in the Object
Explorer and choose New Database from the context menu (Figure 6-4).
Figure 6-4. Creating a New Database
The New Database window displays the General properties of the new database
(Figure 6-5).
2. Type EFSDB in the Name field on the General tab, but leave the Owner as
<default>.
98
Figure 6-5. Database Properties
3. Click OK to save the setup and return to the Microsoft SQL Server Management Stu-
dio, where the EFSDB database is shown under the Databases node (Figure 6-6).
Figure 6-6. Microsoft SQL Server Management Studio
4. Expand Security > Logins in the Object Explorer, right-click Logins and choose
New Login from the context menu (Figure 6-7).
99
Figure 6-7. Opening the Login - New Window
5. Set these attributes on the General page of the Login window (Figure 6-8):
 Enter efsobj in the Name field.
 Select the SQL Server Authentication radio button.
 Enter fox$FDT12 as password.
 Select EFSDB from the Default database pull-down list.
 Leave the Default language as <default>.
 Uncheck Enforce password policy.
 Uncheck Enforce password expiration.
 Uncheck User must change password at the next login.
100
These three
options should
be unchecked
Figure 6-8. Login Window for a New Database
6. Select the User Mapping page (Figure 6-9) and check the box for EFSDB under
Users mapped to this login to specify which databases can be accessed by the login.
7. Check the boxes for the following items under Database role membership for
EFSDB:
 db_datareader
 db_datawriter
 public (already selected by default).
101
Figure 6-9. User Mapping Page
8. Click OK to close the window and return to Microsoft SQL Server Management Stu-
dio.
9. Choose File > Save All from the main menu and exit Microsoft SQL Server
Management Studio.
Setting Options on EFS Database

Proceed as follows to set the options for the EFS database:
1. Right-click on EFSDB -> Properties.
2. In the Database Properties pane, select Options.
3. Change the Recovery Model drop-down menu from FULL to Simple (Figure 6-10).
102
Figure 6-10. Database Properties Pane
4. Click OK to complete configuration of the options.
Set the DSN for the Microsoft SQL Server Database

To set the DSN for the SQL Server database:
1. Click the Start button in the task bar and choose Settings > Control Panel
from the popup menu to open the Control Panel.
2. Click Administrative Tools > Data Sources (ODBC) in the Control Panel to
open the ODBC Data Source Administrator properties dialog box.
3. Click the System DSN tab.
The tab lists existing data sources including EFSDB, if Microsoft Access was selected
during initial installation of the software (Figure 6-11).
103
Figure 6-11. ODBC Data Source Administrator
4. Click Add to open the Create New Data Source dialog box, select SQL Server
(Figure 6-12) and click Finish to start the Create a New Data Source wizard.
Figure 6-12. Create New Data Source Dialog Box
5. Enter EFSDB for both Name and Description and select (local) on the first wizard
page and then click Next (Figure 6-13).
104
Figure 6-13. Create New Data Source to SQL Server Wizard
6. Click the radio button for SQL Server authentication on the next wizard page
(Figure 6-14).
Figure 6-14. Specifying Authentication Method
7. Enter efsobj for the Login ID and fox$FDT12 for the Password, and then click
Next to move to the next page (Figure 6-15).
105
Figure 6-15. Setting Additional Properties
8. Click the check box for Change the default database to and select the new data-
base (EFSDB) from the pull-down list.
9. Accept all other default selections and click Next to move to the final wizard page
(Figure 6-16).
Figure 6-16. Final Wizard Page
10. Accept the default selections and click Finish.

The ODBC Microsoft SQL Server Setup dialog box lists the selections you have made
(Figure 6-17).
106
Figure 6-17. Selected Data Source Settings
11. Click the Test Data Source button.

The next dialog box shows the test results (Figure 6-18).
Figure 6-18. SQL Server ODBC Data Source Test
12. Click OK to exit the wizard.
107
Best Practices for Advanced Users

The following are recommendations for Advanced EFS users:
1. It is recommended to use the Microsoft SQL Server 2008 as the EFS database for all
kinds of applications, irrespective of the nature of use; whether EFS is used for both
maintenance and asset management or it is used for device maintenance alone.
2. Use multiple PACTware projects in the configuration of DTMs instead of overloading
a single PACTware project. This approach makes working with the PACTware proj-
ects easier as load is distributed among multiple PACTware projects.
3. A PACTware project should contain less than 30 devices.
4. It is not advisable to modify or replace the EFS database. However, if you require mul-
tiple databases for offline configuration, ensure that you have backed up the following
project components:
 EFS database:
 If Microsoft Access is chosen as the EFS database, copy the file
FDMEFSAccessDatabase.mdb located in the Database folder of your installa-
tion directory.
 If Microsoft SQL Server 2008 is chosen as the EFS database, take a backup of
the EFS database.
 PACTware projects used in offline configuration
 Bulk data spreadsheet files used in bulk data import.
After making the backup, save it in a folder giving it an unique name such as
Plant area_datetime.
NOTE
If you desire offline PACTware project files to be used on a new empty EFS data-
base, all the data entered via the Manual Entry method must be re-entered and all
the data entered via the Bulk Import method must be re-imported.
Programmatic Access to Device Databases

The Invensys Condition Monitoring application monitors the asset management data within EFS
and creates a work order within Avantis.PRO when a device malfunctions. Additional asset man-
agement information can be obtained from the EFS database by utilizing the Application Pro-
gramming Interface, as described in Extended Frame Services 2.x Application Programming Interface
(B0400EG).
Invensys Condition Monitoring

Invensys Condition Monitoring (ICM) is an optional component of Avantis.PRO. ICM provides
performance-based preventive maintenance, condition-based monitoring and predictive alerts by
using the I/A Series function blocks and the AIM* Historian. The AIM* Historian is the data
source for these capabilities. The user selects process variables for monitoring, and ICM monitors
and analyzes the data for possible maintenance conditions. If a pending failure is detected, ICM
108
can automatically generate an appropriate maintenance work order request and action can be
taken to prevent the failure.
Using Invensys Condition Monitoring, you can:
 Create maintenance work requests from the process operator's console of the
I/A Series system.
 Provide performance-based preventive maintenance.
 Allow process operators to track equipment history and maintenance activity associ-
ated with a work order request.
 Analyze plant floor data to predict failures and ensure timely maintenance.
 Alert maintenance personnel as to the health of the assets.
Avantis Enterprise Asset Management

Extended Frame Services (EFS) provides FDT compliant data collection services to link instru-
ment maintenance information from HART and FoxCom devices and interfaces this data to
Invensys Condition Monitoring. In turn, EFS communicates selected asset management data
such as device identification information, device health status and DTM-supplied cycle counts for
valve positioners to the Invensys Condition Monitoring application. The Invensys Condition
Monitoring application monitors this asset management data within EFS and creates a work order
within Avantis.PRO when a device malfunctions.
Avantis.PRO is an Enterprise Asset Management solution which ultimately reduces maintenance
costs including maintenance labor and spare parts inventory costs while maximizing return on
assets. Avantis.PRO provides planning and scheduling of asset management functions, including
preventive maintenance, materials management, supply chain management and work order man-
agement. Using Avantis.PRO, you can:
 Track costing and maintenance activities on any equipment needing repair or service.
 Record detailed equipment failure histories including the symptoms, the cause of
failure and the actions taken.
 Automatically generate work orders, based on any combination of user-defined crite-
ria such as performance statistics, elapsed time and calendar date.
 Easily control equipment inventory and spare parts inventory.
 Automate the procurement process. For example, by automatically creating requisi-
tions and purchase orders.
109
110
7. Configuring Devices for EFS
Scanning
This chapter describes how to select devices in the I/A Series system for scanning by EFS, set the
scanning frequency and start the scanning service.
The Invensys Field Device Scanner process, which runs on each workstation with EFS client soft-
ware, ensures that intelligent field device information in the database maintained by EFS is
updated periodically. The scanner retrieves device parameters and status at a user-set frequency
and saves the updated information to the database.
You can configure and execute the scanning process on any workstation on which EFS software is
installed. Use the EFS Scanner Configuration dialog box to specify which devices are to be
scanned and the frequency of scanning.
The EFS Scanner Configuration application sets up only those devices to be scanned by the work-
station from which you are running the configuration application. For example, using the scanner
configuration application on Workstation 1, you can configure the scanner process executing on
Workstation 1 to scan device FT104 every hour. From the scanner configuration application on
Workstation 2, you can configure the scanner process executing on Workstation 2 to scan the
device FV201 every hour. Every hour, both devices are scanned; the scanning process in Worksta-
tion 1 scans device FT104 and the scanning process in Workstation 2 scans FV107.
Although there are scanning processes executing on multiple workstations, one central database is
updated. Separating the devices to be scanned among multiple workstations, allows a higher num-
ber of devices to be scanned in a given time period.
The scanner configuration application only displays those devices that are configured to be
scanned by the scanner process in the computer running the configuration application.
Figure 7-1 depicts a complete workflow for selecting on-platform devices (that is, devices con-
nected to the I/A Series system via an FBM) for EFS scanning. Steps 1 through 11 in this scenario
are discussed in Chapter 3 “Online Configuration”. The equivalent work for devices configured
offline is covered in Chapter 4 “Offline Configuration: Bulk Data Import” and Chapter 5
“Offline Configuration: Manual Entry”.
111
B0400EF – Rev H 7. Configuring Devices for EFS Scanning
Figure 7-1. Setting up I/A Series Devices for EFS Scanning
HART Device Scan Considerations

The primary purpose for scanning HART devices is to collect diagnostic status indications in
order to alert operators to device problems. HART devices have extensive diagnostics and condi-
tion monitoring within themselves. Therefore, it is typically preferable to collect the diagnostic
status bits representing problem alerts, rather than collecting data readings. For example, on a
valve positioner, it is more appropriate to read a status bit indicating the low air supply pressure
alarm limit has been violated rather than collecting the air pressure reading itself and having to
test it against limits within a computer application.
Every HART device has a standard device status byte with indications such as Field Device Mal-
function, Non-PV Out-of-Limits, More Status Available, etc. Up to 25 bytes of additional manu-
facturer specific status bits are available as Extended Status. The More Status Available bit is an
indicator that bits are set in the Extended Status. This is discussed in detail in the “Control Block
Configuration Information” chapter in the HART™ Communication Interface Modules User’s
Guide (B0400FF).
112
7. Configuring Devices for EFS Scanning B0400EF – Rev H
HART Devices Connected To I/A Series HART FBMs

The HART-supporting FBM regularly receives the standard device status byte in replies to the
commands it issues, and has built in checks on the More Status Available bit. When the bit is set,
the FBM reads the 25 bytes of extended status approximately every ten seconds. In the control
processor, the standard device status is read into the DDIAG1 parameter of the ECB201.
Extended status, as a hex string, may be read by a single STRIN block, or be read in a bit enumer-
ation by multiple PAKIN blocks.
Follow these recommendations:
1. Using the standard and extended status bits collected by the FBM and the control
processor is the fastest and most efficient diagnostic information collection mecha-
nism, and is recommended for devices connected to HART FBMs, rather than using
the EFS Scanner.
2. The use of a STRIN block to collect extended status is the preferred mechanism for
collecting all extended status from the FBM into the control processor. A PAKIN
block would be used on applications where only a specific set of 32 extended status
bits are needed. The frequency of status collection is set via the PERIOD parameter of
the block. To reduce and evenly distribute the communication load between control
processor and FBM the collection frequency should be set slow, e.g. 60 seconds, and
the blocks should be phased.
3. The ArchestrA System Platform with ArchestrA application objects should be used to
collect device status and extended device status from the control processor. Within
this engineered solution resides the device specific interpretation of the text strings
that should be matched to the extended status bits appropriate to that make and
model of HART device. The ArchestrA System Platform allows other products and
capabilities of the Invensys Enterprise Control System to be used in a comprehensive
solution encompassing alarming, reporting, and maintenance workflow for the
HART devices.
4. Use of the EFS Scanner is not recommended for devices connected to HART FBMs.
If it is desirable to collect actual readings, e.g., the actual air pressure, it can optionally
complement the above recommendations by reading all device variables into a data-
base. If this is done, follow the recommendations in “Selecting the Devices and Set-
ting the Frequency” on page 115 for engineering the data collection periods.
HART Devices Connected To HART Multiplexers

Digital HART data can be collected through HART multiplexers, scanning a single device at a
time. The EFS Scanner is aware of the necessary device specific commands through the Device
Type Managers.
Follow these recommendations:
1. The EFS Scanner is the recommended solution for collecting a comprehensive
snapshot of readable HART variables for devices connected to HART Multiplexers.
2. Follow the recommendations in “Selecting the Devices and Setting the Frequency” on
page 115 for engineering the data collection periods.
113
Exporting the PACTware Project

To set up EFS scanning for devices in the I/A Series system:
1. Open the PACTware project that contains the devices to be scanned.
2. Choose Extras > EFS Export from the PACTware main menu to export the con-
figuration to the EFS database (Figure 7-2).
Figure 7-2. Exporting Device Configurations from PACTware
3. Click OK when the EFSExport dialog box indicates that the export is complete.
If dialog box displays EFS Export completed with warnings (Figure 7-3):
 Click the EFSExportWarnings link to display the EFSExportWarnings.txt file.
 Review the warning messages and then close the file.
 Click OK in the EFSExport dialog box.
 Resolve any problems in the PACTware project and re-export the project to EFS.
Figure 7-3. EFS Export with Warnings
114
NOTE
By default, EFSExportWarnings.txt is located in the log folder of EFS installation
directory (C:\Program Files\Invensys\FDM_EFS\log on a non-I/A Series plat-
form or D:\Invensys\FDM_EFS\log in an I/A Series workstation).To save warnings
to a different location, double-click the file log directory and save the opened file to
the desired location.
4. Save the Project and exit PACTware.
Selecting the Devices and Setting the Frequency

To identify the devices to be scanned and set the scanning rate:
1. Do one of the following to open the EFS Scanner Configuration dialog box
(Figure 7-4):
 Double-click the EFS Scanner Configuration desktop icon ( ).
 Click the Start button in the task bar and choose Programs > Invensys >
FDM_EFS > EFSScannerConfig.
2. Click the radio button for I/A mode in the Environment group in the upper right
corner of the dialog box if the mode is not already selected.
Figure 7-4. Selecting a Field Device for Scanning
3. Click the Add device button to open the Network Object Selection dialog box
(Figure 7-4).
115
The dialog box displays the FBM and device ECBs present in the I/A Series system
Compound Summary Access (CSA).
4. Expand the data tree, select the device and click OK to insert the full pathname of the
device ECB into the Devices table in the EFS Scanner Configuration dialog box
(Figure 7-5).
Figure 7-5. Setting the Scanning Frequency
5. Right-click the device and use the context menu to set the scanning period.
The default scanning period is one hour. You can select a longer period from the
menu or click User defined and specify the frequency in the Scan period dialog box
(Figure 7-5).
! WARNING
The time required to scan each HART device varies considerably based on the make
and model of device, and the number of parameters that device contains. The scan
for a simple device with few parameters might require around 1½ minutes. The
scan for a complex device such as a valve positioner might require around three
minutes.
The scan cycle for a long list of devices is the sum of the scan times of the individual
devices. Therefore multiple computers each having an EFS Scanner should be used
if there is a long list of devices to scan.
It is generally advisable to scan all devices at the same scanning frequency. The
product allows phasing, so that more critical devices such as valve positioners can be
scanned more frequently. Therefore the scan period is entered on each device row.
However, with a large number of devices it is typically more practical to scan all
116
devices at the same period. The period represents the time required for all devices at
that rate. If the scan period is set lower than the time required, the system scan will
continue until the scan list is complete. For example if every device in the list was
set at a 12 hour scan period, and it requires 12.5 hours to scan, the effective scan
period would actually be 12.5 hours rather than the 12 requested. Typically the scan
period is entered in hours.
Under no circumstances, even with only 1 or 2 devices to scan, is it advisable to set

the scan period less than 10 minutes.
6. Select other devices for scanning and set the scanning rate.
Viewing Scanned Devices

Devices that are set up to be scanned from the current PC are displayed in groups. As shown in
Figure 7-6, the group names are displayed in the list on the left side of the dialog box and the
devices contained in the selected group and their scan periods are displayed in the list on the right.
Figure 7-6. Device Grouping List Control
Devices are grouped either alphabetically by system tag or by communication device, and you can
switch between the two grouping styles.
Alphabetically Sorted Groups

By default, the scanner sorts the devices alphabetically by system tag and divides them into groups
of 25. When grouping alphabetically, use the pull-down list under Devices groups to select:
 10 devices in a group
 25 devices in a group
 50 devices in a group.
The name of the device group is the system tag of the first device in the group. Inserting or
removing a device causes all the groups and their names to be recalculated.
117
Figure 7-7. Selecting the Group Size
Figure 7-8 is an example of devices grouped alphabetically. The first group contains the first ten
devices, Device A through Device J. The name of the first group is Device A, which is the system
tag of the first device in the group. The second group is named Device K and contains the second
ten devices, Device K through Device T. The third group is named Device U and contains the
last three devices set up to be scanned from this PC.
Alphabetically Sorted Groups of 10 Devices
Groups Devices
Device A
Device B
Device A
Device I
Device J
Device K
Device L
Device K
Device S
Device T
Device U
Device U Device V
Device W
Figure 7-8. Alphabetically Sorted Grouping
118
Inserting or removing a device causes all the groups and their names to be recalculated. Figure 7-9
shows the reconfiguration of the device group names and contents when you remove Device B.
GROUPS DEVICES GROUPS DEVICES
DEVICE A DEVICE A
DEVICE B DEVICE C
DEVICE A DEVICE A
DEVICE I DEVICE J
DEVICE J DEVICE K
DEVICE K DEVICE L
DEVICE L DEVICE M
DEVICE K DEVICE L
DEVICE S DEVICE T
DEVICE T DEVICE U
DEVICE U
DEVICE V
DEVICE U DEVICE V DEVICE V
DEVICE W
DEVICE W
Figure 7-9. Removing Devices from Alphabetic Grouping
Removing Device B from the list of scanned devices causes Device K to be moved into the first
group, Device U to be moved into the second group, and the second and third groups to update
their names. If removing a device causes the last group to remain without devices, the last group is
removed and is no longer displayed.
When you add a new device to the scanned devices list, the scanner performs similar actions. The
scanner inserts the device in a position corresponding to the sorting rules, and updates the device
group names and contents after the inserted device.
Grouping by Communication Device

In order for a device to be scanned, it must be connected to an FBM, or in the case of off-plat-
form devices to a modem or multiplexer. When the current PC is set up to scan a large number of
devices, grouping devices by the communication device to which they are attached provides a
more logical presentation method. All devices to be scanned by the current PC that are connected
to the same communication device are united into a group. The name of such a group is created
by using the host station name of the communication device and the system tag of the communi-
cation device:
<host station name>.<communication device system tag>
If the communication device is not connected to a host station, that is, the communication device
is directly connected to the PC performing the scanning, the host station name remains empty.
<>.<communication device system tag>
All devices in a group sorted by communication device are displayed alphabetically by the device
system tags. Group names are also sorted and displayed alphabetically.
When you add a new device and your devices are grouped by communication device, the scanner
searches for the group corresponding to the appropriate communication device and appends the
119
device to that group. If no such group is found, the scanner creates a new group and adds the
device to it.
If you remove a device from the list of devices to be scanned from the current PC, the scanner
application finds the communication group containing the device and removes the device from
the list. If the communication group has no devices left after removing the device, the application
deletes this group and no longer displays it.
Removing Devices
To discontinue scanning a device:
1. Select the device’s group form the list on the left of the EFS Scanner Configuration
dialog box.
2. Select the device in Devices and click the Remove device button to the right.
3. Update the service as discussed in the next section.
Updating the Service

When you have finished specifying the devices to be scanned, the scanning frequency and the
grouping, do the following to update the scanning service with the new scan list:
 Click Update Service to add the newly added devices to the service now and then
click Close to exit the Configurator dialog box.
If the scanner service is currently running, it will add the new devices to its schedule.
If the service is stopped, Update Service starts the service and updates the schedule
accordingly.
NOTE
If Update Service is NOT clicked (as discussed above) after specifying the devices to
be scanned, the scanning frequency, the grouping, and the newly specified devices
will NOT be added to the scanner and they will not be scanned. The newly
specified devices will be added to the scanner and be scanned when scanner service
is restarted or when the system is restarted.
 Click Close to exit the EFS Scanner Configuration dialog box without immediately
updating the scanner service.
The scanner will add the devices when it is started. If the service is currently running
it will not update the list until scanner is restarted.
Managing the Scan Service

NOTE
Do not connect to a device with PACTware when a device is scheduled for scanning
in EFS Scanner Configurator as that will lead to device communication errors when
trying to connect and upload parameters. The tasks of scanning a device using EFS
and accessing of the device through PACTware must never be attempted at the same
time.
120
Starting the Scan Service

During installation, the EFS Scanning Service (DevScan) is set to start up at your request, that is,
it is set up for Manual startup.
On an I/A Series workstation, DevScan starts automatically after all the I/A Series services are up
and running.
On an off-platform workstation, the DevScan service does not start automatically. You must start
the service manually.
If the DevScan service is up and running, the Start service button is disabled in the EFS
Scanner Configuration dialog box.
If the DevScan service is stopped or it is not started, the Start service button is enabled in the
EFS Scanner Configuration dialog box.
To start DevScan manually:
(Figure 7-4):
2. Click the Start service button on the right side of the EFS Scanner Configuration
NOTE
The Start service button is in the “enabled” state only if the service is in the
“stopped” state.
Figure 7-10. Start Service Button
3. Click Close to exit the EFS Scanner Configuration dialog box.
121
Configuring Automatic Startup

You can configure the service’s startup options using the Services applet in the Control Panel to
start DevScan automatically on a non I/A Series station during system boot.
! CAUTION
You should configure automatic startup only on non I/A Series workstations. Do
not change the startup options on an I/A Series workstation.
To configure automatic start on reboot:

1. Click the Start button in the task bar and choose Control Panel (or Settings >
Control Panel) from the pop-up menu.
2. Double-click Administrative Tools in the Control Panel.
3. Double-click Services, and then double-click DevScan to open the DevScan
Properties dialog box (Figure 7-11).
Figure 7-11. Configuring the Device Scanner Service
4. Pull down the list in the Startup type field and select Automatic, and then click
Apply.
5. Click OK in the DevScan properties dialog box to close the dialog box, and
click in the Services window title bar to close the applet.
Stopping DevScan
To stop the scanning service:
(Figure 7-4):
122
NOTE
The Stop service button is in the “enabled” state only if the service is in the
“Started” state.
2. Click the Stop service button on the right side of the EFS Scanner Configuration
Figure 7-12. Stop Service Button
3. Click Close to close the EFS Scanner Configuration dialog box.
Updating the Service on the Fly

The Update service button in the EFS Scanner Configuration dialog box (Figure 7-13)
enables you to implement changes in the scan list and scan frequencies on the fly, that is, while the
service is running. If the service is not running, clicking Update service modifies the scan list
and frequencies and starts the service.
123
Figure 7-13. Click Update Service to Make Changes on the Fly
When the DevScan service is updating, a “Busy” icon is shown and a non-interactive dialog box is
shown with the message “Scanner configuration update in progress…”.
Figure 7-14. Scanner Configuration Update in Progress
Once the DevScan service has updated successfully, a message box with message “Update service
successful” appears. Click OK to close the message box.
Figure 7-15. Update Service is Successful
124
8. Configuring and Scanning Off-
Platform Devices
This chapter describes how to use PACTware to configure intelligent field devices that are off-
platform, that is, they are not connected to the I/A Series system network. Association of the
communication and device DTMs in the PACTware projects enables configuration of the
devices for EFS scanning.
Figure 8-1 shows a typical configuration where the PACTware application resides directly on an
I/A Series workstation. The PACTware application frame is utilized to configure and manage the
HART devices connected directly through the HART FBM, as described in Chapter 3 “Online
Configuration”.
Other examples of off-platform devices are provided at the end of this chapter.
HART Multiplexer Example

Figure 8-1 shows a HART valve positioner connected to a Triconex™ safety system, which
directly monitors and controls the device and other devices. The device is also connected to an I/A
Series workstation via a HART multiplexer. This connection and software installed on the work-
station enable configuration and maintenance of the device, and scanning of the device for asset
management.
Enterprise Network
I/A Series Workstation
PACTware
I/A Series Communication DTM
HART Device DTMs
Multiplexer DTMs
Extended Frame Services 2.3 Pepperl+Fuchs
4-Port RS232C with RS485 Converter Multiplexer
RS-485 Master and Slave
Modules
I/A Series MESH Control Network
See Chapter 3 “Online Configuration”
Fisher
DVC6000
Positioner
4-20 mA I/O
Triconex Interface
Figure 8-1. Example HART Multiplexer Configuration
125
B0400EF – Rev H 8. Configuring and Scanning Off-Platform Devices
This section addresses configuration of the components contained in the architecture shown in
Figure 8-1:
 I/A Series workstation with the PACTware, EFS and DTMs installed using the proce-
dures described in Chapter 2.
 4 Port RS232C (PCI card) and RS485 Converter
 Pepperl+Fuchs KFD2-HMM-16 HART Multiplexer (master)
 Pepperl+Fuchs KFD2-HMS-16 HART Multiplexer (slave)
 Fisher DVC6000, single HART device attached to the HART Multiplexer.
The Fisher DVC6000 is configurable without the presence of the Triconex controller.
Hardware and Software Prerequisites

Some prerequisites must be in place before we begin the HART Multiplexer configuration:
 Install the multi-port RS232C serial card in the AW70 workstation along with the
RS232C to RS485 protocol converter (Figure 8-1).
 Install the KFD2 Master and KFD2 Slave HART Multiplexers.
Pepperl+Fuchs KFD2 Multiplexer installation is provided as an example. The KFD2
Master and KFD2 Slave contain communication channels to which devices are
attached.
 Attach the HART devices to the slave multiplexer and record the channels to which
you attach the HART devices.
In this example, only one HART device, a Fisher DVC6000 positioner, is attached to
the multiplexer. It is connected via channel 1.
In addition to the software installed on the workstation in the Chapter 2 “Software Installation”,
the following CD-ROMs are required during the installation process for the HART multiplexer
illustrated in Figure 8-1:
 P&F KFD2 HART Multiplexer DTM V1.5.9
 HART Comm DTM V1.0.39
These DTMs are obtained directly from Pepperl+Fuchs.
 Follow the manufacturer’s instructions to install the multiplexer software on the
I/A Series workstation.
Figure 8-2 illustrates the sequence of steps involved in the HART multiplexer example.
126
8. Configuring and Scanning Off-Platform Devices B0400EF – Rev H
Figure 8-2. Configuring Devices Connected via a HART Multiplexer for EFS Scanning
Getting Started
Once the hardware is in place and you have installed the DTMs, start PACTware and update the
Device Catalog. You can have multiple PACTware projects for EFS scanning and you should cre-
ate a separate project for devices installed on the I/A Series system network.
To get started:
1. Do one of the following to open the PACTware Frame Application:
 Click the Start button in the task bar and choose Programs > Invensys > PAC-
Tware 4.0 > PACTware 4.0 from the popup menu.
main menu and toolbar at the top of the window, a Project view either on the left or
arrayed across the top of the window. Initially, the Project view includes a single node,
device DTMs associated with them. When you double-click any item in this Project
127
view, the parameters for the DTM are displayed in the appropriate editor in a separate
window.
NOTE
PACTware.
2. Click the Device Catalog icon ( ) in the PACTware toolbar to open the Device Cat-
alog (Figure 8-3), which lists all the DTMs currently available for the project except
the P+F multiplexer DTMs you just installed.
Figure 8-3. Updating the Device Catalog
the PACTware database.
4. Click Yes when the confirmation dialog box (Figure 8-3) prompts you to Create a
new PACTware device catalog?
For the examples in this chapter, the Project view has been moved to the top of the
window and expanded to show additional information about the selected device: Data
Changed in Project, Online State, Channel and Device Type (Figure 8-4).
5. Right-click any of the column headers in the Project view and use the context menu
to add or remove Project view columns.
128
Data changed Online

in project state
Figure 8-4. Setting Up the Project View
6. Do the following to name and save the new project:

a. Choose File > Save from the main menu to open the Save As dialog box
(Figure 8-5).
b. Use the dialog box to name project file and specify its storage location, and then
click Save.
Figure 8-5. Naming the PACTware Project
129
Add HART Communication and Multiplexer DTMs

The next step is to add the generic HART communication DTM to the HOST PC and then add
the multiplexer DTMs. The Pepperl+Fuchs multiplexer in the example uses two DTMs, one for
the master module and one for the slave. Individual device DTMs are added to the slave module.
The MTL multiplexer uses a single serial communication DTM. When you use the context menu
in the Project view to add a device, PACTware presents only those DTMs that are compatible
with the selected device.
To configure the DTMs for the HART multiplexer:
1. Right-click the HOST PC in the Project view and choose Add Device from the con-
text menu to open the Device for dialog box (Figure 8-6).
2. Select HART Communication (CodeWrights GmbH) and click OK.
Figure 8-6. Add the HART Communication DTM to the Host PC
To configure the HART Communication DTM to reference its HART multiplexer network:
1. Double-click the DTM in the Project view to open the HART communication DTM
Parameter dialog box (Figure 8-7).
130
Figure 8-7. HART Communication DTM Parameters
2. Select HART multiplexer in the Communication interface pull-down list.

3. Select the port and baud rate based upon the HART network parameters.
4. Accept the default values for the remaining parameters and click OK.
Multiplexer Master DTM

To configure the KFD2 HART Multiplexer master:
1. Choose View > Device Catalog from the main menu if the catalog is not already
displayed.
2. Use the pushpin icon in the catalog title bar to position the catalog within the
PACTware window as shown in Figure 8-8 and select the Vendor tab on the left.
3. Click the HART communications DTM (COM1) in the Project view.
131
Figure 8-8. Adding the Master DTM
4. Select PEPPERL+FUCHS GmbH in the Vendor tab to display available DTMs in the
device list on the right and then double-click KFD2-HMM-16 (FDT) to add the master
to COM1.
5. Double-click KFD2-HMM-16 (FDT) in Project view to open the DTM in the Devices
view (Figure 8-9).
132
Figure 8-9. Editing Master Multiplexer Parameters
6. Set the RS-485 address to 1 and press Enter to confirm the selection.
NOTE
These addresses and channel selections are based on the topology that was built and
recorded earlier.
The pencil symbol in the Data Changed in Project column indicates that there are
unsaved changes to the device configuration.
Multiplexer Slave DTM

To configure the KFD2 HART Multiplexer slave module:
1. Right-click KFD2-HMM-16 (FDT) in the Project view and choose Add Device from
the context menu to open a dialog box listing only those DTMs that can be added to
the KFD2 HART Multiplexer master module (Figure 8-10).
133
Figure 8-10. Adding a Slave DTM
2. Double-click KFD2-HMS-16 (FDT) to select the slave DTM and to display a dialog
box for specifying the communication channel (Figure 8-11).
Figure 8-11. Selecting the Slave Communication Channel
3. Select channel 1 and click OK.
NOTE
These addresses and channel selections are based upon the topology that was built
and recorded earlier.
The slave multiplexer DTM (Slave00) is added under the master in Project view.
You can also select the slave DTM by browsing the Device Catalog as was done to add
the master to HOST PC (page 131).
4. Double-click Slave00 in the Project view to open the DTM in the Devices view and
edit the parameters (Figure 8-12).
134
Figure 8-12. Editing the Slave Multiplexer Parameters
Add the DTMs for Field Devices

The next step is to add HART devices to the slave multiplexer. In the example, a single device, a
Fisher DVC6000 is added to the Pepperl+Fuchs multiplexer.
NOTE
To create an instance of the device DTMs:

1. Select the slave multiplexer DTM (SLAVE00) in the Project view and select the device
manufacturer (FISHER CONTROLS in the example) in the Device Catalog Vendor tab.
2. Select the device (DVC6000 V1.6) in the list to the right and click the Add button in
the lower right corner of the catalog.
135
Figure 8-13. Selecting a Slave Device
PACTware displays the Channel Selection dialog box (Figure 8-11 on page 134).
3. Choose the proper communication channel (Channel 1) and click OK.
The device DTM (DVC6000) is added under the slave multiplexer in the Project view.
4. Choose File > Save from the PACTware main menu to save the project.
The pencil icons are removed from the Data Changed in Project column indicating
that the configurations have been saved.
Verify Device Connections

The next step is to verify the connections between the DTMs in the PACTware project and the
field devices connected to the workstation via the multiplexer.
Before verifying the connections, you must rebuild the loops on the Master Multiplexer DTM as
follows:
1. Select the Master Multiplexer DTM, right-click on it and click Connect. The Master
Multiplexer DTM is moved into the connected state.
136
2. Right-click the Master Multiplexer DTM again and click Additional Functions -
> Rebuild Loops. The Rebuild Loops dialog box appears.
3. Click the “>>” button to begin the rebuild loops operation. This button is disabled
during this operation.
Figure 8-14. Rebuild Loops Dialog Box
The operation will complete, and the “>>” button becomes selectable again.
Now, verify the connections as follows:
1. Right-click each DTM in the Project view starting with the HART communication
DTM (COM2) and choose Connect from the context menu to verify the online state of
the DTM.
The slave multiplexer is being connected in Figure 8-15. The HART Communication
DTM and the Multiplexer master module are already connected.
When the DTM is online to the device, the icon in the Online State column changes
from to and the device is displayed in bold type.
137
Figure 8-15. Connecting to the Multiplexer Slave
2. Double-click DVC6000 in the Project view to open the DTM in the Device view
(Figure 8-16) and verify the connectivity by displaying online parameters of the device
in device DTM.
3. Close the DTM and right-click the device in the Project view and choose
Disconnect from the context menu to go offline.
Configuring the Device

Once you have established connectivity with a field device, you can upload parameters from the
device to the DTM and/or download configurations from the DTM to the device.
The following sequence is recommended, especially if application specific-parameters have been
set in the device at the factory:
1. Right-click the device in the Project view and choose Connect from the context menu
to go online to the device.
2. Right-click the device in the Project view and choose Load from Device in the con-
text menu to upload parameter values to the DTM.
3. Choose File > Save from the PACTware main menu to save the uploaded values in
the project.
4. Double-click the device in the Project view to open the DTM and edit the parameters
using the functions provided by the DTM (Figure 8-16).
138
NOTE
If you need to make extensive changes to the configuration, it is advisable to take
the DTM offline, edit and save the configuration. Then reconnect and download
the changes by choosing Store to Device from the device’s context menu in the Proj-
ect view.
Figure 8-16. Editing the Slave Device Online
5. Right-click the device in the Project view and choose Disconnect from the context
menu to go offline.
6. Choose File > Save from the PACTware main menu to save the values in the proj-
ect.
Important Note about EFS Scanning of Field Devices

At this point, you can configure the device for EFS scanning, adding the device to a scan list and
setting the scan frequency, as described in the next section.
If the device is on a scan list and you need to access the device via PACTware and the device
DTM for maintenance or diagnostics, make sure that the scanning service is stopped before
you connect to the device to avoid communication errors and possible device configuration
problems.
See Chapter 7 “Configuring Devices for EFS Scanning” for information on the following topics:
 “Viewing Scanned Devices” on page 117
 “Alphabetically Sorted Groups” on page 117
 “Grouping by Communication Device” on page 119
139
 “Updating the Service” on page 120

 “Managing the Scan Service” on page 120
Configure EFS Scanning

To set up EFS scanning for off-platform devices:
1. Choose Extras > EFS Export from the PACTware main menu to export the con-
figuration to the EFS database (Figure 8-17).
2. Click OK when the EFSExport dialog box indicates that the export is complete.
Figure 8-17. Exporting Device Configurations from PACTware
3. Save the project and exit PACTware.

4. Do one of the following to open the EFS Scanner Configuration dialog
box(Figure 8-18):
FDM_EFS > EFSScannerConfig from the popup menu.
140
5. Click the radio button for NonI/A mode in the Environment group in the upper right
corner of the dialog box if the mode is not already selected.
6. Click the Add device button to open the Network Object Selection dialog box
(Figure 8-18).
Figure 8-18. Selecting an Off-Platform Field Device for Scanning
The dialog box displays the DTMs that were configured in the PACTware project and
exported to the EFS database. In Figure 8-18, the database contains the example
HART multiplexer configuration created in this chapter and an MTL multiplexer
DTM with it attached devices.
7. Expand the data tree, select the device and click OK to insert the full pathname of the
device DTM in the Devices table in the EFS Scanner Configuration dialog box
(Figure 8-19).
141
Figure 8-19. Setting the Scanning Frequency
8. Right-click the device and use the context menu to set the scanning period.
The default scanning period is one hour. You can select a longer period from the
menu, or click User defined and specify the frequency in the Scan period dialog
box. In Figure 8-19, the scan frequency is being set to 12 hours.
Deletion of the Unused Non-I/A Series Device Objects

A PACTware project might not contain the complete hierarchy of multiplexers with a large num-
ber of devices. It is recommended that a PACTware project contains a small number of devices;
this requires multiple PACTware projects to represent a multiplexer with 120 channels. Because of
the fragmentation of the multiplexer hierarchy, the EFS export may not detect that a device tag
has been modified, resulting in multiple entries in the EFS database after an EFS Export:
 An entry for the device tag before modification.
 An entry for the device tag after the modification.
The EFS Export warnings file reports if a communication DTM has multiple devices assigned to
the same channel (Figure 8-20).
If multiple devices are identified as being assigned to the same channel, delete the unused device
entry from the EFS database.
Figure 8-20. EFSExportWarning Dialog Box
142
Do the following to delete unused device objects from Network Object Selection window,
1. Open the EFS Scanner Configuration dialog box.
2. Ensure that Non-IA radio button is selected.
3. Click Add device to open the Network Object Selection dialog box (Figure 8-21).
Figure 8-21. Network Object Selection
4. Select the unused device object and click Delete.
NOTE
If a parent object is selected for deletion all the associated child objects of that par-
ent are deleted along with the selected parent object.
5. Click Yes in the confirmation dialog box (Figure 8-22) to confirm deletion of the
selected object along with its child objects.
Figure 8-22. Confirm Deletion Dialog Box
Other Off-platform Configurations

The section briefly describes setting up other off-platform devices in PACTware for EFS scanning.
The instructions in each of these examples go up to the point where the project is exported to
EFS.
143
MTL Multiplexer and Devices

Configuration of devices that are connected via an MTL multiplexer are similar to those for con-
figuring the Pepperl+Fuchs multiplexer and device discussed in the extended example. One differ-
ence is that you add only one communication DTM to host PC, whereas for the Pepperl+Fuchs
multiplexer you add a DTM for the master multiplexer module and a DTM for the slave module.
Figure 8-23 shows the steps needed to configure scanning of off-platform devices using an MTL
multiplexer. This section covers steps 1 through 9 of the workflow.
Figure 8-23. Configuring Devices Connected via an MTL Multiplexer for EFS Scanning
NOTE
144
To configure and scan a device connected to an MTL Multiplexer:

1. Start a PACTWare and add MTL Serial Communication DTM to HOST PC in the
PACTware.
2. Right-click on “MTL Serial Communication DTM” and choose Additional func-
tions -> Scan List, as shown in Figure 8-24. Click Yes when a message prompts
you to establish the connection.
Figure 8-24. Selecting Scan List in PACTware
Wait for the scan list to generate. Once the scan list is displayed, record the RS-485
address of the Multiplexer.
3. Add MTL 4840 Multiplexer under “MTL Serial Communication DTM”.
4. Double click on MTL 4840 Multiplexer, as shown in Figure 8-25, and select the
RS-485 Address as the one recorded from the scan list. Then, click Apply.
145
Figure 8-25. Selecting RS-485 Address in PACTware
5. Right-click MTL 4840 Multiplexer and select Additional functions ->

Instrument List.
6. Click Refresh to refresh the list and display the details for all connected devices.
146
Figure 8-26. Refreshing the Instrument List in PACTware
Wait for the refresh operation to complete. After it is complete, the details of all the
connected instruments/devices are displayed.
147
Figure 8-27. List of Devices in PACTware
7. Using the device details in the Instrument List, add the field device DTM’s below
“MTL 4840 Multiplexer” on the corresponding Channel Address’.
148
Figure 8-28. Channel Selection in PACTware
8. Connect the device DTMs.

9. Click Load from Device to upload the parameters for a connected device. Repeat
this for all devices added.
10. Choose Extras > EFS Export from the PACTware main menu and follow the pro-
cedures described in “Configure EFS Scanning” on page 140.
HART or FoxCom Modem with a Device

Generally, this off-platform configuration mode is used for a single input device that is not used
in process control. Figure 8-29 illustrates the device connection using a FoxCom modem;
Figure 8-30 diagrams the connection for a HART modem and single device.
149
Figure 8-29. FoxCom Modem with a FoxCom Device
Figure 8-30. HART Modem with a HART Field Device
Figure 8-31 shows the steps needed to configure scanning of off-platform devices using a
FoxCom or HART modem. This section covers steps 1 through 9 of the workflow.
150
Figure 8-31. Configuring Devices Connected via a Modem for EFS Scanning
NOTE
Do the following in PACTware to prepare a HART or FoxCom device using a modem:

1. Add a communication DTM to HOST PC using either the FoxCom Communica-
tion or the HART Communication DTM.
2. Double-click the DTM and select Modem from the Communication Interface field.
3. Add the device DTM to the communication DTM.
4. Connect the intelligent field device and verify connectivity by displaying the current
measurement of the device.
5. Choose Extras > EFS Export from the PACTware project.
Pepperl+Fuchs Elcon 2700G HART Multiplexer with Devices

Figure 8-32 shows the setup for a Pepperl+Fuchs Elcon 2700G Mux and devices.
See also the workflow illustrated in Figure 8-2 on page 127 for steps involved in this configura-
tion.
151
Figure 8-32. Multiplexer and Device Setup Procedure
NOTE
Do the following in PACTware to prepare a device connected to multiplexer for scanning:

1. Add HART Communication DTM to the HOST PC in the Project view.
152
Figure 8-33. Adding HART Communication DTM to HOST PC
2. Double-click the HART Communication DTM and configure as follows:

 Set Communication Interface to HART multiplexer
 Set the following in Serial Interface;
 Port: COM1
 Baud rate: 19200
 RTS Control: Toggle
 Set HART protocol;
 Master: Primary Master
 Preamble: 7
 Number of communication retries: 3
 Address scan:
 Start Address: 0
 End Address: 15
153
Figure 8-34. Configuring HART Communication DTM
3. Click Save and OK.

4. Add Mux 2700G (FDT) master DTM to the HART Communication DTM in the
PACTware.
 Configure RS-485 Address = 1 and Master Type = Primary Master.
 Close DTM.
154
Figure 8-35. Adding Mux 2700G (FDT) Master DTM to the HART Communication DTM
5. Add 2700 Slave (FDT) slave DTM to the Mux Master DTM.
155
Figure 8-36. Adding 2700 Slave (FDT) Slave DTM to the Mux Master DTM
6. Double click on Mux Slave DTM and configure the following items:
 Select Communication Channel 1.
7. Select field device DTM for your project.
8. Select device Communication Channel 1.
9. Provide power connection to devices.
10. Provide power connection to the multiplexer.
Fault LED turns ON Red and then OFF and the Power LED blinks for approxi-
mately 5 seconds then turns solid ON Green.
11. Wait for Rebuild scan to complete scanning of channels.
The completed scan is indicated by the HART TX LED on the 2700G Mux module
going from blinking to OFF.
156
Figure 8-37. Channel Scan Completed
NOTE
Sometimes the scanning can take up to approximately 30 minutes based on default
settings.
12. Connect the HART Comm DTM, and Master and Slave DTMs.
13. Connect the device DTMs.
157
Figure 8-38. Connecting the Device DTMs in PACTware
14. Perform an online parameter test for each device.

15. Choose Extras > EFS Export from the PACTware main menu.
158
Figure 8-39. Choosing Extras > EFS Export from PACTware Main Menu
159
160
Appendix A. Troubleshooting
This appendix lists error messages generated by the device scanner and device access components
of Extended Frame Services 2.3. All these error messages are visible to the user either in a
message box or written to the system event logger, which can be viewed using Windows Event
Viewer application.
Errors from the Scan Process EFS Component

Informational Messages
The following messages are informational.
“ScanThread: Stop Event is signaled but there are X ScanWorker threads
started yet.”
“ScanThread: Update Event is signaled but there are X ScanWorker threads
started yet.”
“ScanThread: Update Event is signaled. DevToScanTable is reinitialized!”
“ScanThread: Pause Event is signaled.”
“ScanThread: Resume Event is signaled. Read new register parameters.”
“ScanThread: Creation of new ScanWorker thread for SystemTag = AAAA is
OK m_ullNextScan = XXXXX
“ScanThread: Timeout but there are nothing to scan!”
“ScanThread: Timeout but ScanThread State is _SCAN_PAUSED_STATE. Do
nothing.”
“ScanThread: Worker thread finished for SystemTag = XXXX. Next TimeTo-
Scan = X.”
“ScanThread: Stop Event is signaled but there are X ScanWorker threads
started yet.”
“ScanThread: The ScanThread is in UpdatePending state and the last Scan-
Worker thread finished. DevToScanTable is reinitialized!”
“ScanThread: The ScanThread is in ResumePending state!”
“ScanThread: Update Event is signaled but there are X ScanWorker threads
started yet.”
“Starting processing Device SystemTag : XXXX”
“Finishing Processing Device SystemTag : XXXX”
Scanner Internal Failures

The following errors indicate internal failures. Stopping and restarting the Scan Process may clear
the problem. These errors may also be an indication of inadequate system resources to reboot the
computer.
“Can’t initialize COM. hr = X.”
“ScanThread: The ScanThread wait failed.”
“ScanThread: Creation of new thread number X failed.”
“ScanThread: Worker thread finished but it isn’t ScanWorkerThread.”
161
B0400EF – Rev H Appendix A. Troubleshooting
EFS Access Errors

The following errors indicate a failure to access EFS components. Verify that the components are
properly installed in the system.
“Creating instance of DeviceAccess.FoxDeviceAccess interface failed
with HRESULT = X.”
“Creating instance of DeviceAccess.FoxDviceAccess interface failed.
Invalid pointer.”
“_com_error on DeviceAccess.FoxDeviceAccess interface. SystemTag = X,
HRESULT = X, Source = X, Description = X.”
“Creating instance of EFSObject.FoxEFS interface failed with HRESULT
= X.”
“Creating instance of EFSObject.FoxEFS interface failed. Invalid
pointer.”
“_com_error on EFSObject.FoxEFS interface. HRESULT = X, Source = X,
Description = X.”
“Get UpdateTime() failed. Type is not VT_DATE.”
“_com_error on EFSObject.FoxEFS interface. SystemTag = X, HRESULT =
X, Source = X, Description = X.”
Processing Errors
The following errors indicate processing errors:
“GetCurrentComputerName failed.”
“GetComputerName failed.”
These errors indicate a system failure. Reboot your computer to attempt
to clear the problem.
“Unable to fetch path from registry”
This error indicates an incorrect installation of the EFS components.
Reinstall the EFS software.
“Unable to write event into file”
This error indicates an inability to enter information into the System
Event Log. Verify that the event log is not full.
“ScanThread: Worker thread finished for SystemTag = XXXX with error X.”
This message indicates that an error occurred while performing the device
scan. Additional error information should have been reported by the
device access component.
Errors from the Device Access EFS Component

“DEVICE ALREADY OPEN”
Device is already being accessed. This may be a result of user interaction
with the device through a configurator. The scan will retry.
“UNABLE TO CREATE NEW DEVICE”
Internal error that may be due to a lack of resources. If the problem per-
sists, reboot the system.
162
Appendix A. Troubleshooting B0400EF – Rev H
“NEW DEVICE INITIALISATION FAILED”

Internal error – unable to initialize the DTM for the device. The DTM
may be incorrectly installed or there may be insufficient system resources.
“FAILED TO GET IDTM INTERFACE TO THE DEVICE”
Internal error – unable to initialize the DTM for the device. The DTM
may be incorrectly installed or there may be insufficient system resources.
“FAILED TO GET DEVICE PARAMETERS”
The DTM failed to provide device parameters. The device DTM may not
support the interfaces required to get device parameters.
“UNABLE TO CREATE EFS OBJECT”
Internal error – unable to initialize the database EFS component. There
may be insufficient system resources.
“FAILED TO GET DEVICE RECORD FROM EFS DATABASE”
The device information was not retrievable from the device database. This
may be due to the removal of devices from the database or database cor-
ruption. There should be additional error information from the database
component.
“UNHANDLED EXCEPTION”
“FAILED TO SET DEVICE PARAMETERS”
Parameter values must be set for the communication DTM. The commu-
nication DTM failed the set parameter request. The communication
DTM may not support the interfaces required to set device parameters.
“FAILED TO SET PARAMETERS IN EFS DATABASE”
The device information was not settable in the device database. This may
be due to the removal of devices from the database or database corruption.
“System time conversion failed.”
“Unable to connect to EFSObject library.”
Unable to locate the database component of the EFS set. Reinstalling the
EFS software may fix the problem.
“Unable to get information from database for device. Device tag XXX.”
The device information was not retrievable from the device database.
There should be additional error information from the database compo-
nent.
“Invalid device record type. Device is not of type FOXDEVICE. Device tag is
XXX. Record type is X.”
The device to which you are establishing connectivity is not a field device.
Check the device type selected for scanning.
163
“Cannot find in the database CLSID of the device. Device tag is XXX.”
The device being accessed is not associated with a DTM. This error can be
caused by selecting a device that has never been accessed by the configura-
tor. Devices must be accessed by the configurator to establish an associa-
tion with a DTM.
“Database contains invalid channel value of device. Device tag is XXX.”
A field device does not have the proper association with a communication
device.
“Cannot find in the database Info parameters of the device. Device tag is
XXX.”
tion with a DTM.
“Cannot find in the database Device parameters of the device. Device tag is
XXX.”
tion with a DTM.
“Cannot find in the database Communication device of the device. Device tag
is XXX.”
A field device does not have a proper association with its communication
device.
“Invalid device record type. Device is not of type FOXCOMMDEVICE. Device
tag is XXX. Record type is XXX.”
The device to which you are establishing connectivity is not a field device.
Check the device type selected for scanning.
“Load DTM failed. DTM CLSID is XXX.”
Unable to start the device DTM. This error may be caused by insufficient
system resources or by an improperly installed DTM.
“Unable to get IDtmChannels interface from DTM. DTM CLSID is XXX.”
Unable to get communication channels from the communication DTM.
This error may be caused by insufficient system resources or by an
improperly installed DTM.
“Unable to get FDT channels collection interface from DTM. DTM CLSID is
XXX.”
164
“Unable to get count of FDT channels in DTM. DTM CLSID is XXX.”

“Cannot establish communication between device and communication device.
Device channel index is XXX. Communication device channels count is XXX.
Device system tag is XXX. Communication device system tag is XXX.”
Unable to connect the communication DTM and the device DTM. Com-
munication may be failed, the communication DTM may not be properly
configured, or the DTMs are incompatible.
“Unable to get FDT channel. Device channel index is X. Device system tag is
XXX. Communication device system tag is XXX.”
“Cannot query IFdtChannelSubTopology interface from communication channel.
Communication device tag is XXX. Communication device CLSID is XXX.”
This error may be caused by insufficient system resources, an improperly
installed DTM, or selecting a device that has never been accessed by the
configurator. Devices must be accessed by the configurator to establish an
association with a DTM.
“Notification of communication channel that device is added has failed.
Device system tag is XXX. Communication device system tag is XXX.”
“DTM configuration failed. Device system tag is XXX.”
Unable to initialize the device DTM. This error may be caused by insuffi-
cient system resources, an improperly installed DTM, or selecting a device
that has never been accessed by the configurator. Devices must be accessed
by the configurator to establish an association with a DTM.
“Cannot query IFdtCommunication interface from communication channel.
Device tag is XXX. Communication device tag is XXXX.”
“Set communication failed. Device tag is XXX. Communication device tag is
XXX.”
165
“Cannot establish communication. Communication timeout. Device tag is XXX.

Communication device tag is XXX.”
Error occurred during communication. Connectivity to the device may be
lost.
“Unknown error occurs during operation.”
“Unable to find device. Device handle is XXX.”

Internal error that should not be seen during normal operation. Stop the
device scan process and restart it.
“Unable to create IPresistPropertyBag of DTM. DTM CLSID is XXX.”
“Failed initialize new property bag. DTM CLSID is XXX.”
“Failed to get DTM interface from Property Bag. DTM CLSID is XXX.”
“Failed to set the Environment of DTM. DTM CLSID is XXX.”
“Failed initialize new device type manager. DTM CLSID is XXX.”
“Failed to get Dtm Parameters interface from DTM. DTM CLSID is XXX.”
The DTM failed to provide device parameters. The device DTM may not
support the interfaces required to get device parameters.
“Failed to set parameters of the communication device DTM. DTM CLSID is
XXX.”
The DTM failed to provide device set parameters. The device DTM may
not support the interfaces required to get device parameters.
166
“Failed to prepare releasing of communication. Device system tag is XXX.”

Closure of communication interfaces failed.
“Cannot prepare releasing of communication. Communication timeout. Device
tag is XXX. Communication device tag is XXX.”
Closure of communication failed. This error may be caused by insufficient
resources or a prior error.
“Prepare to release failed. Device tag is XXX.”
“Release of communication failed. Device tag is XXX.”
“Prepare to delete device failed. Device tag is XXX.”
“Invalid device connection. The device handle is pointing to invalid DTM
connection.”
This is an internal error. Stop the device scan service and restart it.
“Cannot send upload request. Upload request failed. Device system tag is
XXX.”
A communication error occurred while reading parameters from the
device. Check connectivity with the device.
“Failed to complete the upload request. Communication timeout. Device
system tag is XXX.”
“Unable to retrieve device parameters. Device system tag is XXX.”
“Unable to set device parameters. Device system tag is XXX.”
A communication error occurred while writing parameters to the device.
Check connectivity with the device.
“Cannot send download request. Download request failed. Device system tag
is XXX.”
“Failed to complete the download request. Communication timeout. Device
system tag is XXX.”
167
“Cannot get Online diagnosis interface from DTM. Device system tag is XXX”
The DTM failed to provide device status interface. The device DTM may
not support the interfaces required to get device status.
“Unable to get the status of device. Device system tag is XXX.”
“Cannot open device. There is already opened device with same system tag.
Device system tag is XXX.”
The same device is being opened more than once. There may be multiple
device scanners accessing the device. Check the configuration.
“Could not communicate with the device as the Device DTM XXX failed to respond.”
The same device is being accessed by FDT frame application and
Extended frame services.
“Unable to read ECB Configuration for <ECB Block name>.”
This error message is displayed when EFS tries to scan an FBM ECB and
the CP containing the ECB is not present on the network. If this message
is displayed, acknowledge each dialog box (one per ECB); or make the CP
with these ECB’s available.
Configuring the Log Settings for EFS Components

Following components of EFS are capable of generating trace/log files that can be used for
advanced troubleshooting and debugging.
 EFSObject
 FBM Passthru Communication DTMs
 Device Access component.
The settings for generating these trace/log files are configurable through an INI file. EFS installa-
tion places EFSSettings.ini in the bin folder of the EFS installation folder.
Below are the contents of the INI file on a workstation where EFS was installed in the default
installation directory (C:Program Files\Invensys\FDM_EFS).
[EFSObject]
Count=1
EFSloglevel=0
LogfilePath="C:\Program Files\Invensys\FDM_EFS\log"
[FBMCommunicationDTMs]
loglevel=0x00000
[DeviceAccess]
LogDetails=1
LogDTMEvents=1
LogErrors=1
LogFDTEvents=1
LogInfo=1
LogWarnings=1
MaxLogFileSize=19000
UploadCheck=1
UseLog=0
UseMultipleLogFiles=0
[PTAPI]
Count=5
Names enclosed in the square brackets specify the application name and entries below the applica-
tion are the settings corresponding to that application.
Following are descriptions of the configurable settings provided for each component or applica-
tion.
EFSObject
Count - can take an unsigned integer value and specifies the maximum number of
EFSObject log files that can be generated at a particular time.
EFSloglevel – can be either 0 or 1. If the value is 0 then EFSObject component does
not generate the log. If the value is 1, it generates the log.
LogfilePath – takes string specifying the path of a folder in which the EFSObject shall
generate log files.
FBM Passthru Communication DTMs

loglevel – this is an hex number that can take a value of 0x00000 or 0xfffff. If the
value is 0x00000 then FBM Passthru Communication DTM components doesn’t
generate the log. If the value is 0xfffff then they generate the log.
LogfilePath – takes string specifying the path of a folder in which the FBM Passthru
Communication DTM components shall generate log files.
Device Access
LogDetails – Is the setting indicating if the detailed log shall be enabled or not. If the
value is 0 (zero) then details logging shall be disabled and if the value is 1 (one)
detailed logging shall be enabled.
LogDTMEvents – Is the setting indicating if the DTM Events logging shall be
enabled or not. If the value is 0 (zero) then DTM Events logging shall be disabled and
if the value is 1 (one) DTM Events logging shall be enabled.
169
LogErrors – Is the setting indicating if the Error logging shall be enabled or not. If the
value is 0 (zero) then error logging shall be disabled and if the value is 1 (one) error
logging shall be enabled.
LogFDTEvents – Is the setting indicating if the FDT events logging shall be enabled
or not. If the value is 0 (zero) then FDT events logging shall be disabled and if the
value is 1 (one) FDT events logging shall be enabled.
LogfilePath – Is the setting that shall indicate the path to a folder where the trace/log
files shall be generated. Device access log files shall get generated in the path specified
in this setting.
LogInfo – This setting indicates if the information logging shall be enabled or not. If
the value is 0 (zero) then information logging shall be disabled and if the value is 1
(one) information logging shall be enabled.
LogWarnings – Is the setting indicating if the warning error logging shall be enabled
or not. If the value is 0 (zero) then warning error logging shall be disabled and if the
value is 1 (one) warning error logging shall be enabled.
MaxLogFileSize – Is the setting indicating the maximum file size to which the device
access log can grow. After reaching the maximum size the file shall be truncated.
UploadCheck – This setting specifies how EFS should work after Upload is complete
during device scan as follows:
0 = After the Upload is complete and successful EFS should update the device
parameters and update time in to database. If the upload fails, device parameters
and update time are not updated in the database.
1 = After the Upload is complete irrespective of the completion status, that is, suc-
cess or failure, EFS updates the device parameters and the update time in data-
base.
UseMultipleLogFiles – This setting specifies whether to continue logging to a differ-
ent file if the current file has exceeded the size specified in MaxLogFileSize.
1 = If the current log file reaches MaxLogFileSize, EFS continues logging but to a
newly created file.
UseLog – Is the setting that indicates if the trace/log is enabled or not. This is a kind
of master key for all other log settings. If the value of this is 0 (zero) then log files shall
not be generated. If the value is 1 then log files shall get generated.
Configuring the Retry Count for Global Find of a CP

from PT_API
In case of heavy network load, PT_API provides a retry count mechanism for sending global find
messages. This count is defaulted to 5. However, this can be configured based on the network size.
To configure the retry count for global find messages of CP:
1. Open the EFSSettings.ini file in located in bin folder of the EFS installation
folder in Notepad or WordPad.
2. Locate the section corresponding to PTAPI.
3. Modify the value against the count key to the desired value.
170
4. Save and close the INI file.
Reading Device Parameters of the EFS Database

Case 1: Microsoft SQL Server 2008
To read device parameters if the EFS database is configured using SQL Server 2008:
1. Create a text file on the desktop (for example, SQL_XML_DB.txt).
2. Open the SQL Management Studio, connect to the SQL Server and navigate to
Databases\EFSDB\Tables\Devices.
3. Right-click the Devices table and choose Select Top 1000 Rows from the context
menu.
4. Find the row with the device you are accessing, and go to the DeviceParameters
column.
5. Place the cursor in the cell (for the required device parameters) and choose Copy from
the context menu when the entire contents have been selected.
NOTE
It may take a while the entire contents of the cell to be selected. After you have
selected the contents, wait until the context menu appears with the Copy com-
mand.
6. Open the text file (SQL_XML_DB.txt) that you created on the desktop.
7. Paste the parameters into the file, and begin your analysis.
The pasted text will be in XML format.
Case 2: Microsoft Access

To read device parameters if the EFS database is a Microsoft Access database:
1. Open the EFS database using Microsoft Access.
2. Open the Devices table.
3. Find the row with the device you are accessing and go to the DeviceParameters
column.
4. Place the cursor in the column and Select/Copy the contents.
5. Open Notepad.exe.
6. Paste the copied parameters into the file and examine the data.
The pasted text appears in XML format.
171
Restoring the Database in SQL Server 2008

NOTE
The EFS instance in the example in the following instruction was installed to the
default location: C:\Program Files\Invensys\FDM_EFS\log. If the software was
installed in an I/A Series workstation, the installation folder would be
D:\Invensys\FDM_EFS\log.
To restore the database from an SQL Server 2008 backup:

1. Open Microsoft SQL Server Management Studio and connect to the server
(Figure A-1).
Figure A-1. Microsoft SQL Server Management Studio - Restore Database
2. Right-click Databases in the Object Explorer and choose Restore Database from
the context menu to open the Restore Database window (Figure A-2).
172
Figure A-2. Restore Database Window
3. Select EFSDB in the pull-down menu in the To Database field, check the radio button
for From Device and then click the button to the right to open the Specify
Backup dialog box (Figure A-3).
Figure A-3. Specify Backup Dialog Box
4. Select File in the pull-down menu for Backup media and click Add.
173
The Locate Backup File dialog box is displayed (Figure A-4).
Figure A-4. Locate Backup File Dialog Box
5. Select All Files (*) in the pull-down menu in the Files of type field, select
the backup file (EFS_BACKUP in Figure A-4) and click OK to add the file to Backup
location list in the Specify Backup dialog box (Figure A-5).
174
Figure A-5. Backup Location Listed
6. Click OK to return to the Restore Database window (Figure A-6).

7. Check the Restore checkbox in the box labeled Select backup sets to
restore.
Figure A-6. Restore Checkbox
175
8. Click Options in the Select a page pane on the left, and check the Overwrite
the existing database checkbox (Figure A-7).
Figure A-7. Restore Options and Standby File
9. Check the first option under Recovery state:

Leave the database ready to use...(RESTORE WITH RECOVERY)
10. Modify the paths for EFSDB_Data and EFDB_Log under “Restore the database
file as” to the path of the “Database” folder in the EFS installation folder
(Figure A-8).
For example, if EFS is installed in the path “D:\Invensys\FDM_EFS”, the path for the
database folder is “D:\Invensys\FDM_EFS\Database”.
a. Modify the path for EFSDB_Data as
D:\Invensys\FDM_EFS\Database\EFSDB.MDF
b. Modify the path for EFSDB_Log as:
D:\Invensys\FDM_EFS\Database\EFSDB_1.LDF
176
Figure A-8. Restore State and Modified Paths
11. Click OK.

A popup messages indicates that you have successfully restored the SQL Server 2008
EFS database (Figure A-9).
177
Figure A-9. EFSDB Restored Successfully
NOTE
While upgrading the database from SQL 2000 to SQL 2008 on the same system,
the following query (EXEC Sp_dropuser ‘efsobj’) need not be executed.
12. Navigate to Databases > EFSDB in the Object Explorer, right-click EFSDB and
choose New Query from the context menu (Figure A-10).
178
Figure A-10. Opening a New Query
13. Type EXEC Sp_dropuser ‘efsobj’ as shown in the Figure A-11 and click the
Execute command.
Command(s) completed successfully should be displayed in the Messages frame
(below the query frame) as shown in Figure A-11.
Figure A-11. Query Successfully Executed
179
14. Expand Databases > EFSDB > Security > Logins in the Object Explorer, right-
click Logins and choose New Login from the context menu to open Login
Properties window to the General Page (Figure A-12).
Figure A-12. Login Properties Window, General Page
15. Enter efsobj in the Name field, click the radio button for SQL Server
Authentication and enter fox$FDT12 in Password and Confirm password.
16. Uncheck the Enforce password expiration option.
17. Use the pull-down lists to select EFSDB for the Defaults database and <Default> for
Default language.
18. Select the User Mapping page (Figure A-13) and click the checkbox for EFSDB under
Users mapped to this login to specify which databases can be accessed by this
login.
180
Figure A-13. Login Properties Window, User Mapping Page
19. Select the following checkboxes in the list box labeled Database role membership
for: ESFDB:
db_datareader
db_datawriter
public (selected by default).
20. Click on OK.
21. Set the DSN for the restored database.
See “Set the DSN for the Microsoft SQL Server Database” on page 103 for detailed
instructions.
181
182
Appendix B. Upgrading to
PACTware 4.0 and EFS 2.3
This appendix describes the steps involved in upgrading PACTware and EFS software. The
next appendix covers migration of an EFS database from Microsoft Access to a Microsoft SQL
Server 2008.
Upgrading to the software described in this document may involve backing up PACTware proj-
ects and EFS databases, removing the current software, installing PACTware 4.0, Extended Frame
Services and related DTMs, and setting up the EFS database.
Two scenarios are discussed in this appendix based on your current application:
 Maintenance Only
You are using PACTware for device configuration, diagnostics and maintenance. You
have installed EFS 2.2 for the FBM Communication DTMs (Passthru DTMs). You
are not using EFS 2.2 with Invensys Condition Monitoring to scan the devices for
asset management information.
 Maintenance and Asset Management
You are using EFS 2.2 to scan the devices for asset management information and pass
that information via Invensys Condition Monitoring to Avantis.Pro.
See Appendix C “Database Migration” if you are also migrating the EFS database from Microsoft
Access to Microsoft SQL Server 2008.
Maintenance Only Applications

This section describes the procedure for upgrading from PACTware 3.6 SP1 to PACTware 4.0.
To upgrade the software:
1. Save your PACTware 3.6 SP1 projects on a safe media.
2. Use the Add or Remove Programs applet in the Control Panel to remove the following
software:
 PACTware 3.6 SP1
 Generic HART DTM Release 3
 HART Communication DTM 1.0.25
3. Install PACTware 4.0 and HART Comm DTM 1.0.39 from Application CD (p/n
K0201AV), as described in “Install PACTware” on page 11.
4. Install the FDT components from the FDT Device Manager Components V2.3 (EFS
V2.3) CD (p/n K0201AX), as discussed in “Install EFS and HART/FoxCom Device
Manager” on page 25.
 Select Passthru DTMs and Documentation on the wizard Select Features page
(Figure B-1), but not Extended Frame Services 2.3.
183
B0400EF – Rev H Appendix B. Upgrading to PACTware 4.0 and EFS 2.3
 Click OK in the Configure EFS Database dialog box to accept the default database
selection, Microsoft Access Database.
Figure B-1. Choices for Maintenance Only Applications
5. Start PACTware 4.0 and update the PACTware Device Catalog, as described in “Ini-
tialize PACTware V4.0 Device Catalog” on page 45.
Converting PACTware Projects

Do the following for each PACTware project:
1. Open the project to convert the file to a V4.0 project, and then save the converted
project to a new folder for PACTware 4.0 projects.
2. Double-click an FBM Communication DTM to open the Parameter dialog box.
3. Click Browse to open the Network Object Selection dialog box (Figure B-2) and click
All in the Refresh database group.
184
Appendix B. Upgrading to PACTware 4.0 and EFS 2.3 B0400EF – Rev H
Figure B-2. EFS Displaying I/A Series Hierarchy
4. For each device in the project:

a. Connect the parent FBM Communication DTM and the device DTM.
b. Perform a Load from Device and save the DTM.
c. Disconnect device DTM.
See “Configuring the Device” on page 65 for information on connecting to the device
and uploading device parameters.
5. Save and close the PACTware project.
Maintenance and Asset Management Applications

This section describes the upgrade procedures if you are currently using EFS 2.2 for device scan-
ning, and you want to upgrade to EFS 2.3 and PACTware 4.0.
NOTE
Extended Frame Services 2.3 requires PACTware 4.0 for configuration.
To upgrade the software:

1. Save your PACTware 3.6 SP1 projects on a safe media.
2. Ensure that the EFS Scanner service (DevScan) is stopped.
See “Managing the Scan Service” on page 120 for information on stopping the service
(Figure B-3).
185
Figure B-3. Ensure that the DevScan Service is Stopped
3. Back up the EFS database.

 For a Microsoft Access database, make a copy of FDMEFSAccessDatabase.mdb
and move it to safe media.
 For Microsoft SQL Server, use the standard SQL Server backup procedure.
4. Use the Add or Remove Programs applet in the Control Panel to remove the following
software:
 PACTware 3.6 SP1
 Generic HART DTM Release 3
 HART Communication DTM 1.0.25
5. Install PACTware 4.0, the Generic HART DTM Release 4.0 and the HART Comm
DTM 1.0.25, as described in “Install PACTware” on page 11.
6. Install the FDT components from the FDT Device Manager Components V2.3 (EFS
V2.3) CD (p/n K0201AX), as discussed in “Install EFS and HART/FoxCom Device
Manager” on page 25.
 Select all three components on the Select Features page in installation wizard
(Figure B-1).
 Select the database application in the Configure EFS Database dialog box. Micro-
soft SQL Server 2008 is the recommended database. See Appendix C “Database
Migration” if you plan to migrate from Microsoft Access to Microsoft SQL 2008.
186
Appendix B. Upgrading to PACTware 4.0 and EFS 2.3 B0400EF – Rev H
Figure B-4. Selecting the Product Features
7. Start PACTware 4.0 and update PACTware Device Catalog, as described in “Initialize
PACTware V4.0 Device Catalog” on page 45.
Converting PACTware Projects

Do the following for each PACTware project:
1. Open the project to convert the file to a V4.0 project, and then save the converted
project to a new folder for PACTware 4.0 projects.
2. Do the following if the EFS database is a Microsoft Access database:
a. Double-click an FBM Communication DTM to open the Parameter dialog box.
b. Click Browse to open the Network Object Selection dialog box (Figure B-2) and
click All in the Refresh database group.
187
Figure B-5. EFS Displaying I/A Series Hierarchy
NOTE
Refreshing the database is unnecessary if the EFS database is a Microsoft SQL
Server 2008 database.
3. For each device in the project:

a. Connect the parent FBM Communication DTM and the device DTM.
b. Perform a Load from Device and save the DTM
c. Disconnect device DTM.
See “Configuring the Device” on page 65 for information on connecting to the device
and uploading device parameters.
4. Export the project to EFS if the EFS database is Microsoft Access.
This step is not necessary if the database is Microsoft SQL Server 2008.
5. Save and close the PACTware project.
188
Appendix C. Database Migration
This appendix describes the procedure for migrating an EFS database from Microsoft Access to
a Microsoft SQL Server 2008, and for migrating a database from a previous EFS version to
EFS 2.3.
Migration to Microsoft SQL Server 2008

The EFS installation uses an Access database. For robust operation of large scale systems, it is rec-
ommended that you switch to Microsoft SQL. This section provides the information on migrat-
ing an existing EFS Access database to the Microsoft SQL database. It is presumed that the SQL
Server 2008 has already been installed and correctly configured.
NOTE
If you are upgrading the Microsoft SQL software from SQL Server 2000/2005 to
SQL Server 2008 and you want to migrate the EFS data on the same system from
SQL Server 2000 to Server SQL 2008, select Analysis services as a mandatory
option while installing SQL Server 2008.
NOTE
To convert the EFS database from Access to SQL Server 2008, you must have
administrator privileges on the system as well as administrative privileges for
the SQL 2008 database.
The following steps are to be executed to create SQL Server 2008 EFS database from an Access
EFS database:
 Create a new SQL Server database as described in “Create the New Database” on
page 98.
 Perform “Setting Options on EFS Database” on page 102.
 “Import from the Access Database” on page 189
 “Set the Primary Key for the Database Tables” on page 197
 “Set Default Values for the CommunicationDevices Table” on page 202.
Import from the Access Database

To import the EFS Access database, proceed as follows:
1. Right-click Databases\EFSDB in the SQL Management Studio navigation tree and
choose Tasks -> Import Data from the context menu to start the SQL Server
Import and Export Wizard (Figure C-1).
189
B0400EF – Rev H Appendix C. Database Migration
Figure C-1. SQL Server Import and Export Wizard Dialog Box
2. Click Next on the first page (Figure C-1) to move to the Choose a Data Source page
(Figure C-2)
190
Appendix C. Database Migration B0400EF – Rev H
Figure C-2. Choose a Data Source Page
Do the following:
a. Choose Microsoft Access from Data source pull-down list.
b. Click the File name Browse button to browse for and select the EFS database:
D:\Invensys\FDM_EFS\Database\EFSEFSAccessDatabase.mdb
This path may vary based on where EFS is installed.
c. Leave the Username and Password fields blank.
d. Click Next. The wizard displays the Choose a Destination page (Figure C-3).
191
Figure C-3. Choose a Destination Page
3. Make the following selections on the Choose a Destination page (Figure C-3):
a. Use the Destination pull-down list to select Microsoft OLE DB Provider for
SQL Server if it is not already selected.
b. Select the database server from the Server pull-down list.
If the SQL Server database resides in the same system, select either (local) or
the database name as your server. If the SQL Server database does not reside in the
same system, browse for the Server name.
c. Accept the default selection of Use Windows Authentication.
d. Select EFSDB (the new database created) from the Database pull-down list.
e. Click Next to move to the Specify Table Copy or Query page (Figure C-4).
192
Figure C-4. Specify Table Copy or Query Page
4. Accept the default option (Copy data from one or more tables or views) and
click Next to move to the next wizard page to select the tables and views to be copied
(Figure C-5).
193
Figure C-5. Select Source Tables and Views Page
5. Check the Source check box on the Select Source Tables and Views page to select all
three tables and then click Next.
The wizard displays the Save and Execute Package page (Figure C-6).
194
Figure C-6. Save and Execute Package Page
6. Accept the default selections and click Next to move to the SQL Server Import and
Export Wizard (Figure C-7).
195
Figure C-7. SQL Server Import and Export Wizard
7. Click Finish to launch the import.

The next wizard displays progress of the import tasks (Figure C-8).
196
Figure C-8. Final Wizard Page Indicates the Import Was a Success
8. Click Close when the wizard indicates that the import was successful to close the
SQL Server Import and Export Wizard.
Set the Primary Key for the Database Tables

Once the EFS Access database has been imported, the next task is to set the Primary Key for the
database tables, as follows:
1. Select Tools -> Options from the tool bar on Microsoft SQL Server management
Studio. Select Designers and uncheck the “Prevent saving changes that
requires table re-creation” check-box (Figure C-9) in the Options dialog box
and click OK.
197
Figure C-9. Option Dialog Box in SQL Server Management Studio
2. In the Microsoft SQL Server Management Studio navigation pane, expand

Databases -> EFSDB -> Tables to list all the tables of EFS database in the pane to
the right (Figure C-10).
The tables of interest for EFS are “CommunicationDevices”, “Devices” and “FBMIn-
foTable”.
198
Figure C-10. Tables Summary Tab
3. Right-click the CommunicationDevices table and choose Design from the context
menu to open the table in the Design view (Figure C-11).
199
Figure C-11. Tables Design View
4. Right-click the SystemTag field in the Design view and choose Set Primary Key
from the context menu (Figure C-12). Then select SystemTag.
200
Figure C-12. Setting the Primary Key
5. Save and close the table to return to the Summary tab for Tables (Figure C-11 above).
6. Use the procedure described in steps 3, 4 and 5 to set SystemTag as the Primary Key
for the Devices table and to set SoftwareType as the Primary Key for the
FBMInfoTable table.
7. In the Microsoft SQL Server Management Studio, select Tools -> Options from the
tool bar. Select Designers and check the “Prevent saving changes that
requires table re-creation” checkbox in the Options dialog box
(Figure C-13), and then click OK.
201
Figure C-13. Option Dialog Box in SQL Server Management Studio (Checking)
Set Default Values for the CommunicationDevices Table

The next step is to set default values for various fields in the CommunicationDevices table, by
doing the following:
1. Go to the Databases > EFSDB > Tables if the Summary tab for Tables is not
already displayed in Microsoft SQL Server Management Studio.
2. Right-click the CommunicationDevices table and choose Design from the context
menu to open the table in the Design view (Figure C-10 above).
3. Select FBMTypeSoftware field to display the column’s properties in a table below the
list (Figure C-14).
202
Figure C-14. FBMTypeSoftware Column Properties
4. Enter 0 in the Default Value field (Figure C-14).

5. Select Channel in the list of columns to display its properties and set the Default
Value field to 0 (Figure C-15).
203
Figure C-15. Channel Column Properties
6. Save and close the Design view of CommunicationDevices table.
Migrating Databases from Previous Versions to EFS

2.3
This section describes procedures for handling the EFS database when upgrading to EFS 2.3 from
a previous version, but not changing the database software from Microsoft Access to Microsoft
SQL Server 2008. There are two separate procedures: one when the database application is Micro-
soft SQL Server, the other when the database application is Microsoft Access.
Before proceeding with migration, please carefully read and understand the following constraints
and restrictions that come with the procedures described in this section:
1. Database migration from EFS 1.1 to EFS 2.3 is not allowed if the EFS 1.1 database
contains any non I/A Series configurations because of the following difference in the
way non I/A Series devices are tagged:
 EFS 2.3 supports naming of non I/A Series device tags to uniquely identify the
devices.
204
 EFS 1.1 uses integers to identify non I/A Series devices and the integer device tags
are not supported in EFS 2.3.
2. If a DTM version of a device in the previous version of the EFS database is at a lower
level than the desired device firmware, that DTM may not support device calibration
or device maintenance. This case might arise due to the upgrading of a device or a
DTM package.
3. The EFS database depends not only on ECB information (in case of an I/A Series
configuration) or device tag information (in case of a non I/A Series configuration)
but also on the DTM package. If the DTM package does not have backward compat-
ibility to an older version, the DTM information contained in the previous version of
EFS database must be synchronized with that of the package installed on the system in
order to run EFS scans.
Migration Procedure When the Database is SQL Server

Use the following procedure when the previous database used SQL Server:
1. Back up the EFSDB database from SQL Server.
2. Uninstall the previous version of EFS (V1.1, V2.0,V2.1 or V2.2).
3. Restore the backed-up EFSDB database.
4. Install EFS V2.3 selecting Microsoft SQL Server 2008 as the database.
5. Click the Start button in the Task Bar and choose Control Panel > Add or
Remove Programs from the pop-up menu to open the Add or Remove Programs
applet.
6. Select Extended Frame Services 2.3 in the applet and click Change/Remove.
7. Click the Modify button on the InstallShield Wizard page and proceed with the
installation, choosing Microsoft SQL Server Database as the EFS Database and
providing the SQL Server name, sa login/username (sa) and password as the pass-
word for the sa user during SQL Server 2008 installation.
The wizard displays the 100 Series migration option selection page
(Figure C-16).
205
Figure C-16. Selecting 100 Series Migration
8. Select the option Migrate 100 series FBMs and click Next if the 100 series FBMs
are to be migrated to corresponding new 200 series FBMs in EFS database, or click
Next to proceed without selecting the option.
Selecting the Migrate 100 series FBMs option migrates the 100 Series FBMs to
new 200 Series FBMs. A partial list of these mappings is listed in Table C-1.
Table C-1. Migration to 200 Series FBMs (Partial)

FBM18 FBM243
FBM39 FBM243b
FBM43 FBM243
FBM44 FBM243b
FBM46 FBM246b
The full list of 200 Series FBM replacements for 100 Series FBMs is available in
100 Series Fieldbus Module Upgrade User's Guide (B0700BQ).
9. Continue with the installation to finish migration.
206
NOTE
Steps to backup EFSDB from the SQL Server and restore the database are optional
if the same station with SQL server installation will be used as database server for
EFS 2.3.
Migration Procedure When the Database is Microsoft Access

Use the following procedure when the previous database used Microsoft Access:
1. Make a backup copy of the FDMEFSAccessDatabase.mdb file in Database folder of
the EFS Installation directory.
2. Uninstall the previous version of EFS (V1.1, V2.0, V2.1, V2.2).
3. Install EFS2.3 selecting Microsoft Access as the database.
4. Replace the FDMEFSAccessDatabase.mdb file in Database folder of EFS Installation
directory with the backup file.
5. Click the Start button in the Task Bar and choose Control Panel > Add or
Remove Programs from the pop-up menu to open the Add or Remove Programs
applet.
6. Select Extended Frame Services 2.3 in the applet and click Change/Remove.
7. Click the Modify button on the InstallShield Wizard page and proceed with the
installation, choosing Microsoft SQL Server Database as the EFS Database.
The wizard displays 100 Series migration option selection page (Figure C-16 in the
previous section).
8. Select the option Migrate 100 series FBMs and click Next if the 100 series FBMs
are to be migrated to corresponding new 200 series FBMs in EFS database, or click
Next to proceed without selecting the option.
Selecting the Migrate 100 series FBMs option migrates the 100 Series FBMs to
new 200 Series FBMs per the mapping in Table C-1 in the previous section.
9. Continue with the installation to finish migration.
207
208
Appendix D. Choosing a Proper
DTM for a Field Device
This appendix describes how to choose a proper DTM for a field device.
To choose the proper DTM for a field device, proceed as follows:
1. Record the Device Revision from the appropriate label on the field device.
NOTE
This procedure uses the Metso ND9100H Valve Positioner as the device listed in all
the examples and figures. The Device Revision for this device will be “Rev. 2”.
2. Physically connect the field device to its associated FBM/Multiplexer/Modem.
NOTE
In this procedure, all examples assume that the device (the Valve Positioner listed
above) is connected to an FBM.

popup menu.
209
B0400EF – Rev H Appendix D. Choosing a Proper DTM for a Field Device
4. Configure Communication DTM/DTMs corresponding to the one used. In the

example shown in Figure D-1, the device is being connected to a HART FBM Com-
munication DTM.
Figure D-1. Configure Communication DTM
210
Appendix D. Choosing a Proper DTM for a Field Device B0400EF – Rev H
5. In PACTWare, select the appropriate device catalog for your device. In the example
shown in Figure D-2, this is the Metso Automation in the Device catalog. PACTWare
displays the entire device DTMs corresponding to Metso devices.
Figure D-2. Listing DTMs for a Vendor in the Device Catalog
211
6. Select the appropriate revision for your device in the Device catalog. In the example
shown in Figure D-3, to match the device revision for the Metso ND9100H Valve
Positioner (Rev. 2), DTM ND9100H V2.2 should be selected.
If device revision is not available on any label on the field device, select the DTM with
earliest revision. In the example shown in Figure D-3, this would be ND9100H V1.1.
Figure D-3. Choosing Device DTM to Print Online Parameterization
212
7. Add the selected DTM under the field device’s associated FBM/Multiplexer/Modem;
in the example shown in Figure D-4, that is the FBM Communication DTM. While
adding this DTM, select proper channel on which device is connected, as shown in
Figure D-5.
Figure D-4. Adding Device DTM to Proper Channel
213
Figure D-5. Device DTM Added Under Communication DTM
214
8. Right-click on the Device DTM and select Connect as shown in Figure D-6. Wait for
the DTM to go online, as shown in Figure D-7.
Figure D-6. Putting the Device Online
215
Figure D-7. Device Online
216
9. Right-click on the Device DTM and select Print -> Online Parameterization as
shown in Figure D-8.
Figure D-8. Choosing Print Online Parameterization
217
10. The Device DTM starts uploading the parameters. Wait until the upload is complete
and you see printed material in the right pane as shown in Figure D-9.
Figure D-9. Showing Online Parameterization
218
11. In the right pane, move the scroll bar to locate where the “Fld Dev Rev” and “Software
Rev” fields are printed and record these values.
In the example shown in Figure D-10, the “Fld Dev Rev” value is “2”, matching the
Device revision on the label of the field device. Also in this example, the value of
“Software Rev” is “153”.
Figure D-10. Online Parameterization Showing “Fld Dev Rev” and “Software Rev”
219
12. Return to the Device Catalog and open the DTM list for the field device. In the
example shown in Figure D-11, this is “Metso Automation devices”.
Figure D-11. Selecting Correct DTM From List of DTMs for a Vendor
For this example, in the available list of DTMs for ND9100H device, choose the
DTMs whose major revision matches with the value of “Fld Dev Rev” value. In this
example, the “Fld Dev Rev” value is “2” and there is only one DTM whose major revi-
sion is “2”; i.e. ND9100H V2.2.
If there are multiple DTMs whose major revision matches “Fld Dev Rev” value, select
the DTM whose minor revision is much closer to the value of the “Software Rev”
field.
220
221
Invensys Operations Management
5601 Granite Parkway Suite 1000
Plano, TX 75024
United States of America
http://www.iom.invensys.com
Global Customer Support

Inside U.S.: 1-866-746-6477
Outside U.S.: 1-508-549-2424 or contact your
local Invensys representative.
Website: http://support.ips.invensys.com

B0400EF - Foxboro

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

B0400EF - Foxboro

Загружено:

Авторское право:

Доступные форматы

I/A Series® System

Copyright 2003 - 2011 Invensys Systems, Inc.

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

1. Extended Frame Services 2.3 ............................................................................................. 1

Install EFS and HART/FoxCom Device Manager .................................................................. 25

4. Offline Configuration: Bulk Data Import ....................................................................... 69

5. Offline Configuration: Manual Entry.............................................................................. 87

Setting Options on EFS Database .................................................................................... 102

7. Configuring Devices for EFS Scanning.......................................................................... 111

8. Configuring and Scanning Off-Platform Devices .......................................................... 125

Appendix A. Troubleshooting ........................................................................................... 161

Appendix B. Upgrading to PACTware 4.0 and EFS 2.3 .................................................... 183

Appendix C. Database Migration ...................................................................................... 189

Appendix D. Choosing a Proper DTM for a Field Device................................................. 209

2-42. PACTware Project Window ........................................................................................ 46

6-11. ODBC Data Source Administrator ........................................................................... 104

8-26. Refreshing the Instrument List in PACTware ............................................................ 147

D-1. Configure Communication DTM ............................................................................. 210

Who Should Read This Book

What You Should Know

Chapter 3 “Online Configuration”

Database Migration and Software Upgrades

100 Series FBM Migration

Using Vendor Device DTMs with EFS

PACTware Frame Application

Configuration of Off-platform Devices

Extended Frame Services 2.3

Valid Configurations for EFS 2.3 On-Platform Configuration

Figure 1-2. EFS Configuration with EFS Server on Platform

EFS Hardware and Software Requirements

Invensys Condition Monitoring and Avantis.Pro

Before you Begin

Database Migration and Software Upgrades

100 Series FBM Migration

Table 2-1. Replacing 100 Series FBMs

100 Series FBM 200 Series Upgrade

Install Microsoft .NET Framework 2.0

Figure 2-1. Welcome Wizard

Figure 2-2. License Agreement

Install PACTware 4.0.6

Figure 2-3. Choose Setup Language Dialog Box

Figure 2-4. Welcome Page

Figure 2-5. PACTware License Agreement

Figure 2-6. Customer Information Page

Figure 2-7. Setup Type Page

Figure 2-8. Choose Destination Location

Figure 2-9. Changing the Installation Folder

Figure 2-10. Reviewing the Setup

Figure 2-11. Setup Status Page

11. Click Finish to complete the installation (Figure 2-12).

Figure 2-12. Installation Complete Wizard

Installing the HART Communication DTM

Figure 2-13. Generic HART DTM Welcome Page

Figure 2-14. HART DTM License Agreement

Figure 2-16. Ready to Install

Figure 2-17. Installation Progress

Figure 2-18. Completing the Generic HART DTM Installation

Install EFS and HART/FoxCom Device Manager

Install Microsoft .NET Framework 4.0

Figure 2-19. .NET Framework 4 Setup

Figure 2-20. .NET Framework 4 Installation Progress

4. Click Finish to complete the installation (Figure 2-21).

Figure 2-21. .NET Framework 4 Installation Complete

Install EFS and HART/FoxCom Communication Device Type