Ow351 60 PDF

Developer Studio User Guide for Ovation 3.5.
1
OW351_60
Version 5
July 2018
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
the use and application of the OvationTM Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@EmersonP rocess.com

Web site: https://www.ovationusers.com
Summary of Changes
Developer Studio User Guide for Ovation 3.5.1

OW351_60
July 2018
Version 5
This version of the Developer Studio User Guide includes the following new information:
 Added the new I/O modules in the following sections:

 Compact Digital Input module configuration (see page 243).
 Digital Output module configuration (see page 244).
 Sequence of Events module configuration (see page 265).
 Speed Detector module configuration (see page 270).
 Added the new section Getting RAID fault information (see page 313).
 Made miscellaneous corrections and clarifications.
Contents
1 Introduction to the Ovation Developer Studio 1

1.1 What is the Ovation Developer Studio? ........................................................................ 1
1.2 What information is included in this manual? ................................................................ 2
1.3 Using the Ovation Developer Studio online help ............................................................ 3
1.3.1 Help System search methods .......................................................................... 4
1.3.2 Viewing online help ......................................................................................... 4
2 Understanding the Developer Studio windows, menus,

and toolbars 5
2.1 Accessing the Ovation Developer Studio ...................................................................... 5
2.2 What are the Developer Studio window components? ................................................... 6
2.3 What are the main windows of the Developer Studio? ................................................... 7
2.4 Understanding the Developer Studio Overview window ................................................. 8
2.4.1 System view bar ............................................................................................. 8
2.4.2 Hardware view bar .......................................................................................... 9
2.4.3 Defaults view bar .......................................................................................... 10
2.4.4 To configure defaults for items in the Defaults view bar ................................... 11
2.4.5 TrashCan view bar........................................................................................ 12
2.5 Understanding the WorkPad window.......................................................................... 13
2.6 What are the Developer Studio menus ? ..................................................................... 13
2.6.1 File menu on the Developer Studio window .................................................... 14
2.6.2 Edit menu on the Developer Studio window .................................................... 14
2.6.3 Operation menu on the Developer Studio window ........................................... 15
2.6.4 Operation right-click menu............................................................................. 18
2.6.5 Browse menu on the Developer Studio window .............................................. 19
2.6.6 View menu on the Developer Studio window .................................................. 19
2.6.7 Help menu on the Developer Studio window................................................... 20
2.7 What are the Developer Studio toolbars? ................................................................... 20
2.7.1 Standard toolbar ........................................................................................... 21
2.7.2 Browse toolbar ............................................................................................. 21
2.7.3 Window toolbar............................................................................................. 22
2.7.4 Operation toolbar .......................................................................................... 22
2.7.5 To customize toolbars ................................................................................... 24
2.8 What are the Developer Studio subwindows? ............................................................. 26
2.8.1 Wizards........................................................................................................ 26
2.8.2 Dialog boxes ................................................................................................ 27
2.9 What tools are available for status and error checking on the Developer Studio? .......... 29
2.9.1 Status bar .................................................................................................... 29
2.9.2 Developer Studio - Alert window .................................................................... 29
2.9.3 Dynamic Status feature ................................................................................. 29
2.10 Data validation.......................................................................................................... 31
OW351_60 i
Table of Contents
3 Understanding the Developer Studio hierarchical tree structure 33

3.1 What is the Developer Studio system tree structure? ................................................... 33
3.2 Systems folder feat ures and functions ........................................................................ 35
3.2.1 Subfolders available in the Systems folder...................................................... 35
3.2.2 To modify the Systems configuration parameters ............................................ 37
3.3 Networks folder features and functions ....................................................................... 39
3.3.1 Subfolders available in the Net works folder .................................................... 40
3.3.2 To modify the Networks configuration parameters ........................................... 41
3.4 Units folder features and functions ............................................................................. 43
3.4.1 Subfolders available in the Units folder........................................................... 43
3.4.2 To insert a Unit folder.................................................................................... 44
3.5 Drops folder features and functions ............................................................................ 46
3.5.1 Subfolders available in the Drops folder ......................................................... 46
3.6 Understanding the Configuration subfolder at all levels in the Developer Studio ............ 47
3.6.1 Configuration subfolder components by level .................................................. 48
3.6.2 Configuration subfolder component descriptions ............................................. 49
3.7 Creating Studio icons using the Image Builder ............................................................ 52
3.7.1 To access the Image Builder ......................................................................... 53
3.7.2 To associate an image to a class (Studio item) ............................................... 55
3.7.3 To change class associations ........................................................................ 56
3.7.4 To add or delete images (icon) in the dictionary .............................................. 57
3.7.5 To complete the image building or editing process .......................................... 59
4 Working with common Developer Studio operations 63

4.1 Common Operation menu functions ........................................................................... 63
4.2 Delet e function ......................................................................................................... 63
4.2.1 To use the Delete function............................................................................. 64
4.3 Purge function .......................................................................................................... 64
4.3.1 To use the Purge function ............................................................................. 64
4.4 Undelete function...................................................................................................... 64
4.4.1 To use the Undelete function ......................................................................... 65
4.5 Search function ........................................................................................................ 65
4.5.1 To begin the Search function ......................................................................... 66
4.5.2 To use the Search function to perform a narrow search ................................... 68
4.5.3 To use the Search function to display results .................................................. 70
4.5.4 To use the Search function to add columns .................................................... 71
4.6 Where Used function ................................................................................................ 73
4.6.1 To use the Where Used function .................................................................... 74
4.6.2 Example of the Find all references to ... option................................................ 77
4.6.3 Example of the Find all references to and children ... option ............................ 79
4.6.4 Example of the Find all references made by ... option...................................... 81
4.6.5 Example of the Find all references made by and children ... option .................. 83
4.7 Find function............................................................................................................. 85
4.7.1 To use the Find feature ................................................................................. 85
4.8 Backup/Restore ........................................................................................................ 86
4.8.1 To use the Ovation Backup function ............................................................... 87
4.8.2 Understanding the Backup/ Restore Parameters tab ........................................ 88
4.8.3 To schedule backups .................................................................................... 89
4.8.4 To use the Restore function........................................................................... 91
ii OW351_60
Table of Contents
4.9 Consistency Checking............................................................................................... 91

4.9.1 To run a Consistency Check .......................................................................... 92
4.10 Load function............................................................................................................ 94
4.10.1 To load application information ...................................................................... 95
4.10.2 To use the Load Preview function .................................................................. 96
4.10.3 To load error messages ................................................................................ 98
4.11 Download function .................................................................................................... 99
4.11.1 To download information ............................................................................. 100
4.11.2 To bypass a download preview .................................................................... 102
4.11.3 Downloading configuration changes to multiple drops ................................... 102
4.12 Reconcile function .................................................................................................. 104
4.12.1 Reconciled fields for Analog and Delux e Analog fields .................................. 104
4.13 Coefficient calculation ............................................................................................. 106
4.13.1 To run a Coefficient Calculation ................................................................... 107
4.14 Clear function ......................................................................................................... 110
4.14.1 To clear application information ................................................................... 110
4.14.2 Clear error messages.................................................................................. 111
4.15 Reboot function ...................................................................................................... 113
4.15.1 To Reboot .................................................................................................. 113
4.16 Update Security Infrastructure function ..................................................................... 114
4.16.1 To use the Update Security Infrastructure Wizard ......................................... 115
4.16.2 To specify a Network Alias name ................................................................. 116
4.16.3 To specify the type of update to perform ....................................................... 117
4.16.4 To specify a new Network Alias name .......................................................... 118
4.16.5 To select the type of update to perform ........................................................ 119
4.16.6 To review and confirm the options you selected ............................................ 120
4.16.7 To exit a successful or unsuccessful Security Infrastructure Update wizard .... 121
4.17 Baseline Creation function....................................................................................... 123
4.17.1 To Create a Bas eline .................................................................................. 124
4.18 Baseline Comparison function ................................................................................. 124
4.18.1 To run a Baseline Comparison..................................................................... 125
4.18.2 To delet e a Baseline Comparison entry ........................................................ 126
4.19 What is the Print Screen utility? ............................................................................... 126
5 Working with special Developer Studio functions 127

5.1 Setting the Online/Offline mode ............................................................................... 127
5.1.1 Enabled Offline mode attributes ................................................................... 127
5.1.2 Enabling Offline Mode through Import Operations ......................................... 128
5.1.3 Operations permitted in Offline mode ........................................................... 128
5.1.4 Disabled Offline mode attributes .................................................................. 128
5.2 Defining Ancillary labels .......................................................................................... 129
5.2.1 To create Ancillary labels ............................................................................ 129
5.2.2 To modify Ancillary labels ............................................................................ 130
5.3 DDB Configuration (Net works folder)........................................................................ 130
5.3.1 To modify the net work DDB configuration ..................................................... 131
5.4 Network Time Protocol (NTP) (Net works folder) ........................................................ 132
5.4.1 To configure an external server as the NTP server........................................ 132
5.4.2 To configure an Ovation Domain Controller as the NTP server ...................... 134
5.5 Plant Mode (Units folder)......................................................................................... 135
5.5.1 To define the analog point that represents your Plant Mode ........................... 135
5.5.2 To modify the analog point that represents your Plant Mod e .......................... 136
OW351_60 iii
Table of Contents
5.6 Point Processing (All folders) ................................................................................... 136

5.6.1 To process a point ...................................................................................... 136
5.7 SNMP (Drops) ........................................................................................................ 138
5.7.1 To configure SNMP..................................................................................... 138
5.7.2 SNMP Parameter settings ........................................................................... 140
5.7.3 DeviceX. TimeOutPoint Name ....................................................................... 140
5.7.4 DeviceX. TimeOutBitNumber........................................................................ 140
5.7.5 DeviceX. CommunityName........................................................................... 141
5.7.6 DeviceX.V ariableY. Name ............................................................................ 141
5.7.7 DeviceX.V ariableY.Frequency ..................................................................... 141
5.7.8 DeviceX.V ariableY. Test .............................................................................. 141
5.7.9 DeviceX.V ariableY. ConfiguredV alue ............................................................ 142
5.7.10 DeviceX.V ariableY. UpperLimit ..................................................................... 142
5.7.11 DeviceX.V ariableY.LowerLimit ..................................................................... 142
5.7.12 DeviceX.V ariableY.BitMaskEnabled ............................................................. 142
5.7.13 DeviceX.V ariableY.BitMask ......................................................................... 143
5.7.14 DeviceX.V ariableY.PointName .................................................................... 143
5.7.15 DeviceX.V ariableY.BitNumber ..................................................................... 143
5.7.16 DeviceX. Name ........................................................................................... 143
5.7.17 To modify SNMP ........................................................................................ 144
6 Managing Ovation licenses 145

6.1 Understanding Ovation licensing.............................................................................. 145
6.2 What are the types of licenses? ............................................................................... 146
6.3 Licensing requirements for an Ovation Windows-based system ................................. 146
6.4 Licenses warning boxes and error messages ........................................................... 147
6.5 What is the License Manager?................................................................................. 148
6.5.1 To access the License Manager .................................................................. 148
6.6 License Manager components ................................................................................. 149
6.6.1 Query Options tab....................................................................................... 149
6.6.2 Environment tab ......................................................................................... 150
6.6.3 License Key tab .......................................................................................... 150
6.6.4 Commuter tab ............................................................................................ 151
7 Adding drops to the Developer Studio 153

7.1 What are drops? ..................................................................................................... 153
7.2 Determining the need for a new drop ....................................................................... 154
7.3 What types of drops are available? .......................................................................... 154
7.3.1 To insert a workstation drop in the Developer Studio ..................................... 155
7.3.2 To insert a Controller drop in the Developer Studio ....................................... 157
7.3.3 To edit drop information .............................................................................. 161
7.4 To insert a drop point .............................................................................................. 161
iv OW351_60
Table of Contents
8 Creating Points in the Developer Studio 165

8.1 What is a point?...................................................................................................... 165
8.1.1 What is a point record? ............................................................................... 166
8.1.2 What is a record field? ................................................................................ 166
8.2 Understanding point names ..................................................................................... 167
8.2.1 Using fully qualified point names .................................................................. 167
8.2.2 Rules for using fully qualified point names .................................................... 168
8.3 Points folder feat ures and functions ......................................................................... 168
8.4 Understanding point record types and sizes ............................................................. 169
8.5 Adding points in the Ovation Developer Studio ......................................................... 169
8.5.1 To add a point in the Developer Studio ......................................................... 170
8.5.2 To use the Point Copy function to add points to the Developer Studio ............ 171
8.6 What information must be configured for each point type? ......................................... 172
8.6.1 Configuring Analog (LA) point types ............................................................. 172
8.6.2 Configuring Deluxe Analog (DA ) point types ................................................. 173
8.6.3 Configuring Digital (LD) point types .............................................................. 173
8.6.4 Configuring Deluxe Digital (DD) point types .................................................. 174
8.6.5 Configuring Packed (LP) point types ............................................................ 174
8.6.6 Configuring Deluxe Packed (DP ) point types ................................................ 175
8.6.7 Configuring Algorithm (LC) point types ......................................................... 175
8.6.8 Configuring Drop (DU) point types ............................................................... 175
8.6.9 Configuring Module (RM) point types ........................................................... 176
8.6.10 Configuring Node (RN) point types............................................................... 176
8.6.11 Configuring Packed Digital (P D) point types ................................................. 176
8.7 Understanding the Points dialog box and its tabs ...................................................... 177
8.7.1 Point tab field description ............................................................................ 180
8.7.2 Config tab field descriptions ......................................................................... 182
8.7.3 Security tab field descriptions ...................................................................... 187
8.7.4 Ancillary tab field descriptions ...................................................................... 187
8.7.5 Hardware tab field descriptions .................................................................... 188
8.7.6 Initial tab field descriptions........................................................................... 190
8.7.7 Alarm tab field descriptions .......................................................................... 192
8.7.8 Instrumentation tab field descriptions ........................................................... 203
8.7.9 Limits tab field descriptions .......................................................................... 206
8.7.10 Display tab field descriptions ....................................................................... 211
8.7.11 Plant Mode tab field descriptions ................................................................. 213
8.7.12 Byte, Int., Real, and ASCII Params tab field descriptions ............................... 215
8.8 What are PDS Point Groups? .................................................................................. 215
8.8.1 To add a new PDS Point Group ................................................................... 215
8.8.2 To modify PDS Point Groups ....................................................................... 217
8.8.3 To add a PDS Point Group Member ............................................................. 217
8.8.4 To modify PDS Point Groups Member.......................................................... 218
8.9 What are Packed Group Numbers? .......................................................................... 219
8.9.1 To define a group number ........................................................................... 219
8.9.2 To define text string values in an XML file..................................................... 221
8.9.3 Sample of XML file...................................................................................... 222
OW351_60 v
Table of Contents
9 Adding I/O to the Developer Studio 225

9.1 What is the purpose of an Ovation I/O module? ........................................................ 225
9.2 Information needed before adding an I/O module ...................................................... 226
9.3 Overview of adding I/O modules to the Developer Studio .......................................... 227
9.3.1 To insert an I/O Device number in a Controller .............................................. 227
9.3.2 To insert an I/O Device in the Developer Studio ............................................ 229
9.3.3 To insert an Ovation I/O module in the Developer Studio ............................... 231
9.3.4 To configure an I/O module ......................................................................... 232
9.3.5 To assign a Module (RM) point to the I/O module .......................................... 233
9.3.6 To load the configured I/O module to the Controller....................................... 235
9.4 Defining and configuring Ovation I/O modules .......................................................... 236
9.4.1 Analog Input module configuration ............................................................... 237
9.4.2 Analog Output module configuration ............................................................ 240
9.4.3 Cont act Input module configuration .............................................................. 242
9.4.4 Compact Contact Input module configuration ................................................ 242
9.4.5 Digital Input module configuration ................................................................ 242
9.4.6 Compact Digital Input module configuration .................................................. 243
9.4.7 Digital Output module configuration .............................................................. 244
9.4.8 HART Analog Input module configuration ..................................................... 247
9.4.9 HART Analog Output module configuration .................................................. 247
9.4.10 HART High Performanc e Analog Input module configuration ......................... 248
9.4.11 HART High Performanc e Analog Output module configuration ....................... 249
9.4.12 Loop Interface module configuration ............................................................ 250
9.4.13 Machinery Health Monit or module configuration ............................................ 252
9.4.14 Pulse Accumulator module configuration ...................................................... 253
9.4.15 Relay Output module configuration .............................................................. 256
9.4.16 RTD module configuration ........................................................................... 258
9.4.17 Sequence of E vents module configuration .................................................... 265
9.4.18 Serial Link Cont roller module configuration ................................................... 269
9.4.19 Servo Drive module configuration ................................................................ 269
9.4.20 Speed Detector module configuration ........................................................... 270
9.4.21 Valve Position Controller module configuration ............................................. 273
9.4.22 Digital Excitation Controller module configuration .......................................... 276
9.4.23 Foundation Fieldbus module configuration .................................................... 278
9.4.24 Profibus module configuration...................................................................... 278
9.4.25 DeviceNet module configuration .................................................................. 279
9.4.26 Ethernet Link module configuration .............................................................. 279
9.5 QLine module configuration ..................................................................................... 280
9.5.1 QLine Analog Input module configuration ..................................................... 281
9.5.2 QLine Analog Output module configuration ................................................... 283
9.5.3 QLine HART High Performance Analog Input module configuration ............... 284
9.5.4 QLine HART High Performance Analog Output module configuration ............. 285
9.5.5 QLine RTD module configuration ................................................................. 286
9.5.6 QLine Compact Contact Input module configuration ...................................... 288
9.5.7 QLine Digital Input module configuration ...................................................... 288
9.5.8 QLine Digital Output module configuration .................................................... 289
9.5.9 QLine Loop Interface module configuration ................................................... 290
9.5.10 QLine Pulse Accumulator module configuration ............................................ 292
9.5.11 QLine Relay Output module configuration .................................................... 295
9.5.12 QLine Sequence of E vents module configuration .......................................... 296
9.5.13 QLine Serial Link Controller module configuration ......................................... 296
9.5.14 QLine Servo Drive module configuration ...................................................... 297
9.5.15 QLine Valve Position Controller module configuration ................................... 298
9.5.16 QLine Speed Detector module configuration................................................. 300
vi OW351_60
Table of Contents
10 Adding and configuring redundant I/O modules 301

10.1 Understanding redundant I/O modules ..................................................................... 301
10.2 Hardware placement for redundant modules............................................................. 302
10.3 Redundant module failover and recovery.................................................................. 303
10.4 Adding redundant I/O modules ................................................................................ 303
10.4.1 Before adding redundant I/O modules .......................................................... 303
10.4.2 To add the device number to the Controller .................................................. 304
10.4.3 To insert the Primary I/O module into the Developer Studio system tree ......... 306
10.4.4 To insert the Secondary I/O module into the Developer Studio system tree .... 308
10.4.5 To link the Primary and Secondary I/O modules............................................ 310
10.4.6 To assign a module (RM) point to the Primary and Secondary I/O modules .... 311
10.4.7 To load the Controller (for a redundant I/O module) ....................................... 312
11 Getting RAID fault information 313

11.1 Introduction to RAID fault information ....................................................................... 313
11.1.1 Terminology used with S NMP and RA ID ...................................................... 314
11.2 Overview of configuring iDRA C, SNMP, and points ................................................... 314
11.2.1 Selecting a connection met hod .................................................................... 315
11.2.2 Recommendations for IP address selection .................................................. 315
11.2.3 To access the iDRA C Settings utility ............................................................ 316
11.2.4 To access the iDRA C Web interfac e ............................................................ 317
11.3 Configuring the connection to the iDRAC using the OS to iDRAC Pass
Through option ....................................................................................................... 321
11.3.1 To enable iDRA C pass through ................................................................... 321
11.3.2 To configure the managed comput er's virtual adapter ................................... 323
11.3.3 To modify the OS to iDRAC Pass Through IP address .................................. 326
11.4 Configuring the connection to the iDRAC using the Loopback Access option .............. 326
11.4.1 To configure iDRA C net work settings ........................................................... 327
11.4.2 To configure the managed comput er's host interface adapt er ........................ 328
11.5 Changing the iDRA C SNMP Community String ......................................................... 332
11.6 Creating Ovation points for iDRAC status information ................................................ 333
11.6.1 To create points for SNMP RAID ................................................................. 333
11.6.2 To configure the S NMP ............................................................................... 337
11.7 Viewing the RA ID status in the System Viewer application ......................................... 339
11.8 Resetting iDRA C to Factory Default Settings ............................................................ 340
11.8.1 Using the Settings utility .............................................................................. 340
11.8.2 Using the Web Interface .............................................................................. 340
12 Engineering Tools Audit 341

12.1 What is the Engineering Tools Audit function? .......................................................... 341
12.2 What Ovation applications are audited with the Engineering Audit Tools function? ...... 342
12.3 To set the Engineering Audit level ............................................................................ 344
12.4 Auditing examples .................................................................................................. 345
12.4.1 High-level auditing example......................................................................... 345
12.4.2 Medium-level auditing example.................................................................... 346
12.4.3 Low-level auditing example ......................................................................... 347
12.5 Using the Ovation Audit Viewer ............................................................................... 347
12.5.1 To access the Ovation Audit Viewer ............................................................. 348
OW351_60 vii
Table of Contents
12.5.2 AuditView menu bar .................................................................................... 349

12.5.3 AuditView toolbar........................................................................................ 350
12.5.4 To view current Engineering Tool audits ....................................................... 350
12.5.5 To define search criteria for an audit report ................................................... 352
12.5.6 To view individual event information ............................................................. 354
12.5.7 To show or hide columns using the menus ................................................... 355
12.5.8 To adjust columns using the right-click menu ................................................ 356
12.6 What is the Audit log archive?.................................................................................. 356
12.6.1 To archive audit dat a .................................................................................. 357
12.7 Audit Log storage ................................................................................................... 357
12.7.1 What are the storage limits? ........................................................................ 358
12.7.2 What if the storage limits are exceeded? ...................................................... 358
13 Adding Holding Registers 359

13.1 What are Holding Registers ? ................................................................................... 359
13.1.1 To insert a new Holding Register ................................................................. 359
13.1.2 To open an existing Holding Register ........................................................... 360
13.2 Understanding the Holding Register Editor window ................................................... 361
13.2.1 Holding Register Editor menu and toolbar functions ...................................... 363
13.2.2 To use the holding Register Editor preferences window ................................. 365
13.2.3 To change Holding Register values .............................................................. 366
13.2.4 Holding Register print dialog box ................................................................. 367
13.2.5 Holding Register print setup dialog box ........................................................ 368
13.2.6 Holding Register print preview dialog box ..................................................... 369
14 DIOB testing for Q-Line modules 371

14.1 What is the optional DIOB Test tool used for? ........................................................... 371
14.2 Q-Line I/ O module addressing ................................................................................. 372
Index 373
viii OW351_60
SECTION 1
1 Introduction to the Ovation Developer Studio
IN THIS SECTION
What is the Ovation Developer Studio? ........................................................................ 1

What information is included in this manual? ................................................................ 2
Using the Ovation Developer Studio online help ............................................................ 3
1.1 What is the Ovation Developer Studio?
The Ovation Developer Studio is a comprehensive software application that manages the
configuration of the entire Ovation system. As a fully integrated advanced software program, the
Developer Studio creates and maintains Ovation drop types, control strategies, process graphics,
point records, and system-wide configurations, including integrated security features.
The Developer Studio is a single launch point for various functions, each aimed at managing
and/or configuring a different portion of the Ovation system:
 Define and configure an Ovation system.

 Create, modify, and delete points.
 Create and modify drops.
 Define the I/O modules used in an Ovation system.
 Store values from algorithms (typically, for Special Functions and ladder applications).
 Load control and originating point information into drops in an Ovation system.
 Links the Master Database with other drops in the system.
 Manage licensing for Ovation applications.
 Upload Controller changes (online) into the database.
 Create point groups used in trends or graphics.
 Create, modify, and delete security objects and definitions.
 Track changes made to the database.
 Create control logic that runs on the Ovation Controller.
 Create and edit system process diagrams that display on the Operator Station.
 Serves as a launch point for many Ovation programs, such as the Control Builder and the
Graphics Builder.
 Manages security privileges in an Ovation system.
The Developer Studio also serves as a "window" into the Ovation Database Server. It allows you
to see what is defined and configured. For most projects, the creation of the Ovation Database
and the Developer Studio is a combined effort between customer design engineers and Emerson
project engineers. Careful planning before the database or the Developer Studio is installed is
essential to a successful project by reducing time and cost.
OW351_60 1
1.2 What information is included in this manual?
1.2 What information is included in this manual?
The Ovation Developer Studio is the engineer tool for the entire Ovation system. Based on the
number of functions the Developer Studio performs, it would be impossible to include all of them
in one user guide.
The Ovation Developer Studio User Guide discusses the basic functionality and use of the
Developer Studio application. In addition, the guide provides information on general Ovation
applications and on functions that must be configured before other applications can be used.
However, since many of the Ovation applications are complex, they must be di scussed in
separate manuals, even though they are configured and/or accessed from the Developer Studio.
For this reason, the Ovation Developer Studio User Guide serves as a "map" to other Ovation
user guides.
The following is a list of other Ovation user manuals that may be helpful when using the
Developer Studio:
 Ovation Software Installation Manual
 Ovation Operator Station Configuration Guide
 Ovation Foundation Fieldbus User Guide
 Ovation Profibus User Guide
 Ovation DeviceNet User Guide
 Ovation Safety Instrumented Systems (SIS) User Guide
 Ovation Controller (OCR400) User Guide
 Ovation Controller (OCR1100) User Guide
 Ovation Simulation User Guide
 Ovation Virtual Controller User Guide
 Ovation Multiple Network s User Guide
 Ovation Wireless Devices User Guide
2 OW351_60
1.3 Using the Ovation Developer Studio online help
The Windows-based Ovation system has an online help system. The Help structure follows the
same scheme as Microsoft Windows applications.
You can access this help in several ways:

 By pulling down the Help menu on the main Developer Studio window.
 By pressing the F1 key on the keyboard while the cursor is anywhere on the Developer Studio
window.
 By pressing a Help button on any of the various Developer Studio dialog boxes.
Since the Developer Studio is the launch point for so many Ovation applications and functions,
the online help accesses and presents information in many different Ovation manuals. Use the
Table of contents for Ovation 3.5.1 topic to access the manual you need.
The following figure depicts an example of the Ovation 3.5.1 Developer Studio online help
window.
Figure 1: Developer Studio online help
OW351_60 3
1.3.1 He lp Syste m se arch me thods
The online help window has the following three tabs:

 Contents: This tab displays a directory tree structure of the contents of the help file for the
current application. It follows the same scheme as Windows Explorer. Each subject is
represented by a book icon that contains individual files. The individual file contains the help
text. To display help information, click the subject in the left pane of the window. The right
pane of the window displays the corresponding help information.
 Index: This tab has a text entry field in the left pane to search the index for specific
information. The system searches the index for an entry as you type the information. As you
type, it highlights index help topics that alphabetically match your entry in the closest manner.
Choose a topic and click Display to view the help text. The right pane of the window displays
the corresponding help information.
 Search: This tab enables a search function. Enter a keyword in an entry field and then click
List Topics. The topics that match the keyword appear. Select a topic and click Display to
view the topic. The right pane of the window populates with the corresponding help
information.
1.3.2 Vie wing online he lp
You can set the viewing preferences with the icons on the menu bar at the top of the Help
window:
 Hide and Show icons: Hides or shows the three tabs (Contents, Index, and Search). If you
click the Hide icon, the three tabs disappear. The Hide icon then becomes the Show icon.
Click the Show icon to display the tabs again.
 Back icon: Displays the previous help selection.
 Print icon: Prints the current help screen.
 Options icon: Presents the options shown in the following table:
Options icon
O P TI O N D E S C R I P TI O N
Hide/Show Tabs Hides or shows the three tabs (Contents, Index, and Search).
Back Displays the previous help selection.
Forward Displays the next help selection.
Home Displays the home page of the online help.
Stop Stops an operation in process.
Refresh Refreshes the results in the left pane of the window.
Internet Options Displays the Internet Options window.
Print Prints the current help screen.
Search Highlight Displays the search results with or without highlights.
Off/On
4 OW351_60
SECTION 2
2 Understanding the Developer Studio windows,

menus, and toolbars
IN THIS SECTION
Accessing the Ovation Developer Studio ...................................................................... 5

What are the Developer Studio window components? ................................................... 6
What are the main windows of the Developer Studio? ................................................... 7
Understanding the Developer Studio Overview window ................................................. 8
Understanding the Work Pad window.......................................................................... 13
What are the Developer Studio menus ? ..................................................................... 13
What are the Developer Studio toolbars? ................................................................... 20
What are the Developer Studio sub windows? ............................................................. 26
What tools are available for status and error check ing on the Developer Studio? .......... 29
Data validation.......................................................................................................... 31
2.1 Accessing the Ovation Developer Studio
When your Ovation system is loaded, the Developer Studio icon appears on your desktop.
Double-click the icon and the Developer Studio window appears.
You can also access the Developer Studio from the context menu of the Operator Station
applications, such as Point Information.
Note: Much of the setup and configuration of the Developer Studio contents and hierarchy is
performed by an Emerson representative before the system is installed in your plant.
OW351_60 5
2.2 What are the Developer Studio window components?
2.2 What are the Developer Studio window components?
The Developer Studio main window consists of a base frame with a drop-down menu panel,
various view bars and toolbars, subwindows, workspace, horizontal and vertical scrollbars, and a
footer for displaying messages.
The following figure shows an example of the Ovation Developer Studio with various window
components labeled.
Figure 2: Example of Ovation Developer Studio window components
6 OW351_60
2.3 What are the main windows of the Developer Studio?
2.3 What are the main windows of the Developer Studio?
There are three main areas of the Developer Studio:

 Overview window (see page 8).
 WorkPad window (see page 13).
 Workspace (appears as the background canvas of the Developer Studio).
The Overview window shows the hierarchical relationship (see page 33) between all of the
elements in your Ovation system. The WorkPad window shows selectable items, programs, or
files based on what is highlighted in the Overview window. The Workspace is where wizards,
applications and other dialog boxes display (see What are the Developer Studio subwindows?
(see page 26)).
Each window has a different function, but they all work together to give you a complete picture of
your system. Any window that you display in the Workspace is accessed from a specific item in
the Overview window. Any files that are part of a folder you select in the Overview window are
displayed in the WorkPad area.
Since the three main areas of the Developer Studio give you a different perspective on your
system, there are many ways to perform various tasks. This makes the Developer Studio
application flexible and easy to use since you choose which way is best to perform a certain
function.
OW351_60 7
2.4 Understanding the Developer Studio Overview window
The Overview window provides the following view bars.

 System view bar (see page 8): Displays the system where the Developer Studio is currently
mapped.
 Hardware view bar (see page 9): Contains the hierarchical file structure view (system tree) of
the database.
 Defaults view bar (see page 10): Reveals a file structure in which you set defaults for point
types and I/O devices.
 TrashCan view bar (see page 12): Stores deleted items. This function behaves much like the
Microsoft Windows Recycle Bin.
The following figure depicts the Overview window with its view bars.
Figure 3: Overview window

2.4.1 Syste m v ie w bar
The Ovation Systems view bar sits at the top of the Overview window and displays the system to
which the Developer Studio is currently mapped. (Refer to the Ovation Multiple Network s User
Guide for more information.)
Figure 4: Ovation Systems Bar
8 OW351_60
2.4.2 Hardware v iew bar
The Hardware view bar provides a hierarchical file structure view of the database. The Hardware
view is referred to as the system tree. The highest level in the system tree is the System,
followed by the Network, Unit, and Drop. Within the Hardware view bar, you configure almost
every aspect of your Ovation system.
Note: Throughout this manual, the phrase “Use the system tree to navigate to” refers to opening
a folder in the Hardware view hierarchical structure to reveal more folders.
By default, the Developer Studio displays the Hardware view bar expanded (the Defaults and
TrashCan view bars are collapsed). When no system has been defined, only the Hardware root
folder is displayed. To expand or collapse the folder structure within the Hardware view, click the
plus (+) or minus (-) signs in front of each folder. By expanding into the file structure of the
Hardware view bar, you are able to configure every aspect of the System down to the Points
folder level.
Figure 5: Hardware view bar expanded in Overview window
See Understanding the Developer Studio hierarchical tree structure (see page 33) for additional
information about the system tree that is illustrated in the Hardware view bar.
OW351_60 9
2.4.3 De faults v iew bar
The Defaults bar provides a tool to create default settings for certain items. By setting point
defaults, each new point created in the Hardware bar will initially possess the attributes or values
established as a default for that type of point. Creating/modifying default points saves time when
creating multiple points with similar characteristics. By eliminating the need to enter repetitive
information for each point type, you can focus on the unique settings of the specific point.
When the Ovation system is first installed, the items in the Defaults bar are configured with factory
default information. However, you can override these "factory" defaults by modifying the settings
for the point types and/or I/O types shown in the Defaults bar.
Not all attributes of a point type can be set as defaults. Information that is drop- or unit-specific
cannot be set as a default. Additionally, all information that has been set as a default can be
overwritten when the point is created in the Hardware view bar (system tree).
Note: The same principle applies to remote I/O and Remote Q-Line I/O defaults.
Some examples of point fields that can be set as defaults are:
 Description.
 Characteristics.
 Min/Max scale.
 Number of Digits displayed.
 Security Groups.
The following figure shows all 13 default types.
Figure 6: Defaults view bar displayed in Overview window
10 OW351_60
2.4.4 T o configure de faults for ite ms in the De faults v iew bar
Note: For example purposes, the following procedure discuss configuring default analog points.
However, these procedures are applicable for all of the items in the Defaults bar.
1. Access the Developer Studio (see page 5).

2. Expand the Default view bar in the Developer Studio.
3. Select the + sign in front or the DefaultRoot folder to reveal the default items.
4. Select one of the Default Point types. For example purposes here, the following figure shows
the window for a default analog point.
5. Double-click on the default item in the WorkPad window (see page 13). The appropriate
default dialog box appears:
Figure 7: Default Analog point dialog box
6. Enter the desired point information into the appropriate tabs and fields. All information entered
in these fields will be used for each new point whenever a point of that type is created in the
Ovation database. Any field that is grayed out cannot be set as a default.
Note: See Creating Points to the Developer Studio (see page 165) for point-specific tab and
field information.
7. Select Ok/Apply to add the information to the database.
OW351_60 11
2.4.5 T rashCan v iew bar
The TrashCan view bar behaves much like the Microsoft Windows Recycle Bin. All files and
folders deleted from the Hardware folders are moved to the TrashCan folder. The deleted files are
stored in the trashcan so that you can open the previously deleted folders, restore the folders to
their original location, or purge the files from the system entirely.
Notice that the hierarchy in the TrashCan view bar contains placeholders for Systems, Networks,
Units, Drops, Points, and Graphics. Not all items deleted from the Hardware view bar are stored
in the TrashCan folder. Only items in the Hardware view bar with corresponding placeholders in
the TrashCan view bar can be shown in the TrashCan.
For example, if you delete a unit from the Hardware view bar, the folder and all its contents are
moved from the Hardware view bar to the TrashCan view bar and placed in the Units placeholder
folder. However, if you delete only a configuration item from the Hardware view bar, that record is
not shown in the TrashCan view bar.
All points deleted from the Hardware view bar are listed under the Points placeholder folder in the
TrashCan, regardless of the drop folder from which the points were removed. If a point is
removed from the TrashCan and returned to the Hardware view bar, it will return to its original
drop.
Note: If you delete a folder, all of its subfolders are removed with it.
Figure 8: TrashCan view bar expanded
12 OW351_60
2.5 Understanding the WorkPad window
2.5 Understanding the WorkPad window
The WorkPad window displays selectable folders and objects of the highlighted tree object. The
WorkPad view buttons change the way objects appear in the WorkPad window.
WorkPad view buttons
B U TTO N DE S C R I P TI O N
Icons — Changes the appearance of the folders and objects listed in the WorkPad
window.
Single Column — Lists the folders, objects in the WorkPad window in one vertical
column.
Multi-column/Vertical — Lists the folders and objects in the WorkPad window in
several vertical columns.
Multi-column/Horizontal — Lists the folders and objects in the WorkPad window in
several horizontal columns.
2.6 What are the Developer Studio menus?
The Developer Studio pull-down menu panel is actually a floatable and dockable Menu bar. The
following menus are available on the Menu bar:
 File (see page 13).

 Edit (see page 14).
 Operation (see page 15).
 Browse (see page 19).
 View (see page 19).
 Help (see page 20).
Figure 9: Menu bar
OW351_60 13
2.6.1 File me nu on the De v eloper Studio win dow
The File menu allows you to access print options and to close the Developer Studio application.
File menu items
MEN U I TE M DE S C R I P TI O N
Print Setup Displays a standard Microsoft Windows Print Setup window, which allows you to
specify a printer, paper, s ize, print mode, and so forth.
Print Prints what is currently displayed on the Developer Studio screen.
Print Preview Allows you to see what will be printed before actually printing.
Exit Quits the Developer Studio.
2.6.2 Edit me nu on the De veloper Studio window
The Edit menu provides the tools to perform common edit functions.
Edit menu items
MEN U I TE M DE S C R I P TI O N
Undo Reverts to the last action.
Cut Removes the currently selected items and places them in an internal buffer
(clipboard) for pasting later.
Copy Copies the currently selected items to an internal buffer (clipboard) for pasting
later.
Paste Adds the contents of the internal buffer (clipboard) to the active document.
Select All Selects (highlights) all of the items in the active window.
14 OW351_60
2.6.3 Ope ration me nu on the De veloper Studio window
The Operation menu lists the functions that can be performed on the Developer Studio.
The Operation menu provides an additional feature to the user. When an item is highlighted in the
Developer Studio system tree, only operations that can be performed on the highlighted item will
be active on the Operation menu; all other menu items will be grayed out.
Note: Several functions in the following table are specific to a particular Ovation application. For
these operations, the corresponding manual is listed for more information.
Operation menu
FU N C TI O N D E S C R I P TI O N W H ER E TO F I N D MO R E
I N F O R MATI O N
Insert New Inserts a new item in the hierarchy. ---
Open Opens the selected item for editing. ---
Copy Copies the selected item for editing. ---
Engineer Opens the selected engineering tool. Ovation Foundation Fieldb us User
Guide
Delete Deletes/moves the selected item(s) to the Delete function (see page 63)
TrashCan folder.
Purge Permanently deletes the selected item(s) Purge function (see page 64)
from the TrashCan folder.
Undelete Restores the previously deleted item from Undelete function (see page 65)
the TrashCan to the previous location in
the hardware hierarchy.
Search Searches the database for items that Search function (see page 65)
match specified criteria.
Where Used Searches the database to find where an Where Used function (see page 73)
item is used by another item in the
system.
Find Provides a quick name search for items in Find function (see page 84)
the database.
Map Remote System Allows the connection to and operation of Ovation Multiple Networks User
a remote system for engineering the Guide
system via the Developer Studio.
Disconnect Remote Disconnects the Developer Studio from Ovation Multiple Networks User
System the remotely mapped system. Guide
Compile Compiles the selected diagram/macro or Ovation Graphics Builder User

folder of diagram/macros. Guide
Control Options Opens the Control Builder options dialog Ovation Control Builder User Guide
box.
Backup/Restore Used to backup and restore the system Backup/Restore (see page 86)
information.
OW351_60 15
I N F O R MATI O N
Lock Used with Safety Instrumented Systems. Ovation Safety Instrumented

System (SIS) User Guide
Unlock Used with Safety Instrumented Systems. Ovation Safety Instrumented

In addition, this operation is also System (SIS) User Guide
applicable for other database objects that
can be implicitly locked during an
Engineer operation, such as Profibus
ports, DeviceNet ports, and so forth.
Assign Performs an Assignment operation for the Safety Instrumented System (SIS)
selected item. with Electronic Marshalling User
Guide
UnAssign Performs an Unassignment operation for Safety Instrumented System (SIS)
the selected item. with Electronic Marshalling User
Guide
Consistency Check Performs a consistency check at the Consistency Checking (see page
selected hierarchy location. 91)
Load Loads database and control contents to Load function (see page 94)
the specified Ovation target drop.
DownLoad Downloads configuration and diagram Download function (see page 99)
files to one or more specified Ovation
target drops.
Reconcile Reconciles the database against a Reconcile function (see page 104)
specified Ovation target drop.
and
Ovation Control Builder User Guide
Coefficient Calc Automatically calculates analog Coefficient calculation
conversion coefficients. (see page 106)
Restore Reload mismatched Controllers to a prior Ovation Controller User Guide

matched state (if the system is configured
for Restore Mode).
Reboot Reboots the selected Ovation drop. Reb oot function (see page 113)
Import Imports items into the database. Ovation Graphics Builder User
Guide
Export Exports the selected item from the Ovation Graphics Builder User
database. Guide
Update Security Provides a mechanism by which computer Update Security Infrastructure
Infrastructure and network information stored in the function (see page 114)
Ovation database and in the Ovation
domain Controller can be made constant.
Run SIS Used with Safety Instrumented Systems. Ovation Safety Instrumented
Configuration System (SIS) User Guide.
Create Baseline Captures a snapshot-in-time of the Baseline Creation function
Ovation Database. (see page 123)
Compare to Baseline Used to view changes in the Ovation Baseline Comparison function
Database over time. (see page 124)
16 OW351_60
I N F O R MATI O N
Dump CRC Used with Safety Instrumented Systems. Ovation Safety Instrumented
System (SIS) User Guide.
Statistics Used to view communication activity for a Ovation Foundation Fieldb us User
given Foundation Fieldbus port. Guide
Tuning Applies to active (in use) Foundation Ovation Foundation Fieldb us User
Fieldbus function blocks. Use this Guide
operation to set the necessary parameters
in order to get the active function block(s)
behave as intended.
Commission Commissions the specified object/device. Ovation Foundation Fieldb us User
Guide
Safety Instrumented System (SIS)
with Electronic Marshalling User
Guide
Decommission Uncommissions the specified Ovation Foundation Fieldb us User
object/device. Guide
Guide
Download Downloads configuration and diagram Download function (see page 99)
files to one or more specified Ovation
Ovation Foundation Fieldb us User
target drops. In addition, this operation is
Guide
also applicable for some Foundation
Fieldbus objects.
Clear Clears application data (originated and Clear function (see page 109)
received point's lists and control
information) from the specified target.
Guide
Upload Takes values of a given Foundation Ovation Foundation Fieldb us User
Fieldbus function block’s parameters and Guide
stores them in the associated database
object.
View Live Devices Used to view the Foundation Fieldbus Ovation Foundation Fieldb us User
devices that are connected to a given port Guide
and the pertinent information for each
device.
Migrate Trend Group Moves the trend configuration from the Ovation Operator Station User
Ovation database (where it existed in pre- Guide
Ovation 3.5.0 releases) into the newer
format Trend Group Definition files.
Refresh Refreshes the hierarchy (not listed in the ---
(F5) Operation toolbar).
For more information, see Work ing with common Developer Studio operations (see page 63).
OW351_60 17
2.6.4 Ope ration right-click me nu
Perhaps one of the easiest ways to access most operations is through the right -click menu. The
right-click menu is available on all folders in the System Tree (see page 33) and on all WorkPad
items. The right-click menu displays a subset of the Operations menu. All of the operations shown
on the Operation menu/toolbar can be available on the right-click menu. However, the right-click
menu only displays operations that are appropriate for the folder or item that is highlighted.
The following figure shows an example of a right-click menu.
Figure 10: Example right-click menu
18 OW351_60
2.6.5 Browse me nu on the De v eloper Studio window
The Browse menu allows you to change your view of the system hierarchy tree (see page 33).
Browse menu
FU N C TI O N S DE S C R I P TI O N
Expand Child Shows all of the child items of a selected item.
Note: In hierarchical relationships, items in a hierarchy tree structure are often

referred to as "parent and child" to define inherited group membership. A Parent
and Child hierarchical relationship refers to a folder that contains one or more
sub ordinate folder hierarchies underneath it. For more information, see
Understanding the Developer Studio hierarchical tree structure (see page 33).
Collapse Child Closes all of the child folders of a selected item.
Expand All Shows all of the items in the tree.
Collapse All Closes all folders in the tree.
2.6.6 Vie w me nu on the De v eloper Studio window
The View menu allows you to change the appearance of the Developer Studio windows.
View menu
FU N C TI O N S DE S C R I P TI O N
Workbook Mode Provides tabs for each functional dialog box opened in the Workspace window.
Fullscreen Mode Increases workspace size by eliminating all menu and menu bars.
Customize Toolbar Opens the Customize Toolbar dialog box (see page 23).
Overview window Displays or hides the Overview window. A check box enables the Overview
window.
Workpad window Displays or hides the WorkPad window. A check box enables the WorkPad
window.
Status Bar Displays or hides the Status bar. A check box enables the Status bar.
Lookup List As Determines the look of the WorkPad window.
 Icons — change the appearance of the folders and items listed in the
WorkPad window.
 Single-column — lists the folders and items in the WorkPad window in one
vertical column.
 Multi-column/Horiz. — lists the folders and items in the WorkPad window in
several horizontal columns.
 Multi-column/Vert. — lists the folders and items in the WorkPad window in
several vertical columns.
OW351_60 19
2.7 What are the Developer Studio toolbars?
2.6.7 He lp me nu on the De veloper Studio window
The Help menu provides access to online help information (see page 3).
Help menu
FU N C TI O N S D E S C R I P TI O N
Contents and Index Provides access to the online Ovation user manuals that are part of
the Developer Studio suite of manuals.
About Ovation DevStudio Displays program, version number, and copyright information.
Toolbars provide quick, easy access to the more frequently used Developer Studio windows and
functions. Most functions represented on a toolbar can also be accessed from a menu.
There are five Developer Studio toolbars:

 Menu bar (pull-down menu panel) (see page 13).
 Standard (see page 21).
 Browse (see page 21).
 Window (see page 22).
 Operation (see page 22).
Toolbar buttons, like their associated menu items, can be active or inactive. If a function is
currently not active, the associated toolbar button and menu item are not active (grayed out). If a
function is active, both the toolbar button and the menu item are active.
All Developer Studio windows and toolbars are dockable and floatable. Dockable means it can be
attached to one of the sides of the main window. Floatable means it can be displayed as a pop-
up window with a title and a window close button in the upper right corner.
The typical position for toolbars is above the Workspace, underneath the menu panel. However,
you can move toolbars to different locations on the screen. To move a docked toolbar, grab the
left end of the toolbar at the dotted vertical line. Notice how the cursor changes. Press and hold
the left mouse button and drag the toolbar to the desired place/position. Release the mouse
button, and the toolbar is docked to that side.
Each toolbar button has an associated “tooltip” for that button. A tooltip is a short descriptive text
string describing the button function. To see the tooltip for a particular button, hover the mouse
pointer over the toolbar button.
In addition, you can customize the look of the default Developer Studio toolbars or you can create
new toolbars. See Customizing toolbars (see page 23) for more information.
20 OW351_60
2.7.1 Standard toolbar
The Standard toolbar icons represent the functions that can be accessed from the
File (see page 13), Edit (see page 14), and Help (see page 20) menus.
Figure 11: Standard toolbar
The toolbar icons, from left to right, are as follows:

 Print Setup
 Print
 Undo
 Cut
 Copy
 Paste
 Help
 About
2.7.2 Browse toolbar
The Browse toolbar icons represent the functions that are found on the Browse (see page 19)
menu.
Figure 12: Browse toolbar
 Expand Child
 Collapse Child
 Expand All Items
 Collapse All Items
 Refresh
Note: In hierarchical relationships, items in a hierarchy tree structure are often referred to as
"parent and child" to define inherited group membership. A Parent and Child hierarchical
relationship refers to a folder that contains one or more subordinate folder hierarchies
underneath it. For more information, see Understanding the Developer Studio hierarchical tree
structure (see page 33).
OW351_60 21
2.7.3 Window toolbar
The Window toolbar functions help you display and navigate the Developer Studio windows.
Figure 13: Window toolbar

 Close Window: Closes the active window.
 Close all windows: Closes all open windows.
 Next Window: Activates the next undocked window.
 Previous Window: Activates the previous undocked window.
 Cascade: Arranges windows as overlapping tiles.
 Tile Horizontally: Arranges windows as horizontal, non-overlapping tiles.
 Tile Vertically: Arranges windows as vertical, non-overlapping tiles.
2.7.4 Ope ration toolbar
The Operation toolbar icons represent the functions found on the Operation menu.
Figure 14: Operation toolbar

 Insert item
 Open item
 Copy item
 Engineer
 Delete item
 Permanent delete
 UnDelete
 Search
 Where used
 Find pull-down menu
 Map remote system
 Disconnect
 Compile Graphic
 Control options
 Backup or Restore
 Lock
 Unlock
 Assign
22 OW351_60
 UnAssign
 Consistency Check
 Load
 Download config
 Reconcile
 Coefficient Calc
 Clear
 Reboot
 Import
 Export
 Restore
 Ensure consistency of security infrastructure
 Create Switch Config
 Create Baseline
 Compare Baseline
 Dump CRC
 Statistics
 Tuning
 Commission
 Decommission
 Download
 Clear
 Upload
 View Live Devices
 Migrate Trend Group
OW351_60 23
2.7.5 T o customize toolbars
You can customize the look of the default Developer Studio toolbars, or you can create new
toolbars with the Customize window.
Use the following steps to access the Customize window:

2. Pull down the View menu and select Customize Toolbar. The Customize window appears:
Figure 15: Customize window showing Toolbars tab
When the window initially appears, the Toolbars tab is displayed. The Toolbars tab allows you
to configure which toolbars will display on the Developer Studio window and how the toolbars
will look.
3. In the Toolbars list, place a check mark beside the toolbar(s) that you want to display on the
Developer Studio window. To remove a check mark, click on the item again. The toolbar will
not display on the window.
4. Select the Show Tooltips box to display tooltips (descriptive text) for each of the toolbars. If
this box is not checked, tooltips will not display for any of the toolbars.
5. Select the Cool Look box to display the toolbars as flat, one-dimensional surfaces. Uncheck
the Cool Look box and the icons will appear as raised tiles on the toolbars. Note that whatever
you select for this option (checked or unchecked), it affects all of the toolbars.
6. Select the Large Buttons box to expand the size of the icons and the toolbars. If the Large
Buttons box is not checked, the icons will display at their default size.
7. After any changes are made to the Customize window, select the OK or Apply button to save
the changes.
24 OW351_60
To create a new toolbar
You can create a new toolbar using the Customize window.

2. Pull down the View menu and select Customize Toolbar. The Customize window appears.
3. Select the New button on the Customize window. The New Toolbar window appears:
Figure 16: New Toolbar window
4. Enter a name for the new toolbar in the entry field.

5. Select the OK button. The new toolbar name appears in the Customize window, and the new,
empty (no icons on it) toolbar appears in the upper left-corner of the Developer Studio
window.
Figure 17: Customize window showing name of newly created toolbar
6. Select the Commands tab. Go to the various default toolbars and select the icons that you
want to appear on your new, customized toolbar. Drag the desired icon(s) to the new toolbar
that appears in the upper-left corner of the Developer Studio window.
7. When you have dragged all of the desired icons on the new toolbar, click the OK button on
the Customize window.
OW351_60 25
2.8 What are the Developer Studio subwindows?
In addition to the three main areas of the Developer Studio, there are subwindows and
informational items. Typically, these subwindows are the means by which you perform the
majority of the Ovation configuration.
 Wizards
 Dialog boxes
2.8.1 Wizards
A wizard is a series of windows that are accessed consecutively.
In Ovation, wizards are used to create database objects in the Developer Studio. A wizard
presents a subset of object fields that need to be addressed in order to create a specific object.
These object fields represent the minimum required input for the particular item being inserted.
Any fields shaded in gray contain system-generated information that is read-only and is provided
for informational purposes.
A wizard can contain fields, buttons, drop-down lists, and check boxes. The title bar at the top of
the wizard indicates the type of information to be inserted. The buttons on the bottom of the
window provide the functionality of the wizard. At the very minimum, wizards usually contain a
Next and a Back button.
26 OW351_60
The following figure shows an example of a Developer Studio wizard.
Figure 18: Example Wizard dialog box
Standard Wizard dialog box buttons
Back Takes you back one step. Only used in wizards with more than one step.
Next Takes you forward one step. Only used in wizards with more than one step.
Finish Accepts the input, closes the wizard, and opens a dialog box containing all object attributes.
Cancel Cancels/aborts the operation.
2.8.2 Dialog boxe s
Dialog boxes are functional windows containing information about a specific object. Dialog boxes
can contain information fields, tabs, buttons, drop-down lists, and check boxes.
The title bar at the top of the dialog box describes the function of the window. The body is the
workspace in the dialog box. The body of most dialog boxes contain one or more sets of fields,
such as Attributes (information that is needed by or helps describe the object), and values (in the
form of drop-down lists, radio buttons, entry fields, or other forms of input to help format and
describe the object). The fields shaded in gray contain system-generated information that is read
only and is provided for informational purposes.
OW351_60 27
Selecting the tabs at the bottom of the window causes the dialog box to display new attributes,
values, and parameters that pertain to that tab. The tool buttons on the right side of the window
provide the functionality of the dialog box.
Figure 19: Dialog box window example
Dialog box buttons
Ok Saves changes to the database and closes the dialog box.

Apply Saves changes to the database but the dialog box remains open.
Cancel Cancels any changes made and closes the dialog box.
Refresh Updates the values on the dialog box based on the current values in the database.
Help Displays information about the dialog box and provides help filling in the fields.
28 OW351_60
2.9 What tools are available for status and error checking on the Developer Studio?
2.9 What tools are available for status and error checking on the
Developer Studio?
The Developer Studio uses the following items to alert you of systems errors and status:
 Status bar (see page 29).

 Alert window (see page 29).
 Dynamic Status flags (see page 29).
2.9.1 Status bar
The Status bar of the Developer Studio window provides additional information as it relates to
your editing session.
The following figure shows an example of the Developer Studio Status bar.
Figure 20: Developer Studio Status bar
2.9.2 De v eloper Studio - Ale rt window
Alert windows provide important information regarding errors in the Ovation system.
The following message is a generic example of an alert message that may appear while working
in the Developer Studio. Select the Details button to obtain an error message that will provide
information on the specific error. Make any changes necessary to correct the problem, and then
proceed with the task.
Figure 21: Alert message
2.9.3 Dynamic Status fe ature
Dynamic status refers to a graphical indication (flag) that appears in front of a database object in
the system tree whenever that object requires user attention and/or action. Currently, the
following database changes that are monitored (and could result in a flagged object) are:
 Ovation points.
 Holding registers.
 Control sheets.
Note: If you change a point, no flag appears on the point item; however, a flag will appear on
the parent drop item.
OW351_60 29
2.9 What tools are available for status and error checking on the Developer Studio?
To use the Dynamic Status feature

2. Use the system tree to navigate to the Drops folder:
Systems -> Networks -> Units -> Drops
3. Locate the item(s) needing attention as indicated by the Dynamic Status markers (graphical
indication (flag)).
Figure 22: Dynamic Status Indicators
4. Select the down-arrow that appears after the item name. The Ovation Diagnostics window
that is appropriate for that item appears:
Figure 23: Ovation Diagnostics window
5. Diagnostic information about the item is provided and recommended actions are suggested.
Perform the appropriate actions and the Dynamic Status indicator disappears.
30 OW351_60
2.10 Data validation
2.10 Data validation
The Developer Studio checks user input and provides feedback if it detects inconsistent data.
Data validation in the Developer Studio is performed at three levels:
 Per field basis ensures valid data type and range as the input is entered. For example, fields
may be limited in the number of characters or the types of characters entered. Field validation
occurs whenever a user changes focus from one field to another in an open dialog box.
 Per object basis ensures that various fields make sense in combination with each other. The
checking of objects is performed as objects are added to or updated in the database. If
inconsistencies are discovered, the Developer Studio displays an Alert window indicating the
problem.
 Inter-object or system basis checks ensure that the information in the newly modified object
is consistent with the other objects in the system. An example of this is the check for duplicate
point names within the same unit.
The last two types of data validation occur whenever an object is changed via a dialog (that is, the
Apply or Ok button is pressed).
OW351_60 31
SECTION 3
3 Understanding the Developer Studio hierarchical

tree structure
IN THIS SECTION
What is the Developer Studio system tree structure? ................................................... 33

Systems folder feat ures and functions ........................................................................ 35
Net work s folder features and functions ....................................................................... 39
Units folder features and functions ............................................................................. 43
Drops folder features and functions ............................................................................ 46
Understanding the Configuration subfolder at all levels in the Developer Studio ............ 47
Creating Studio icons using the Image Builder ............................................................ 52
3.1 What is the Developer Studio system tree structure?
The Developer Studio is designed in a tree or system hierarchy structure. This structure
separates the functions of the system and makes it easy to see and understand the dependence
and flow of the configuration as well as the usage of the various hardware and software objects.
With the Developer Studio, you are able to configure parameters and settings at the System
(see page 35), Network (see page 39), Unit (see page 43), and Drop (see page 46) levels.
The tree structure separates the system functions into levels with the highest level being the most
general and the lowest level being the most specific. Each level is defined by a folder. There are
four major folders in the Ovation Developer Studio tree: System, Network, Unit, and Drops.
Each folder (or item) of the system tree contains all the specific elements for that level. For
example, the Drops folder contains all Drops for a specific unit.
Configuration at the highest folder level (System) filters down through the entire system. However,
changes made at a lower level (Units) overrides the System configuration for everything defined
in its level and below it.
For example, if the trend screen background color is set to black at the highest folder level
(System), all trend screen background colors down throughout the entire system (Networks,
Units, and Drops) default to black . If, however, you change a trend screen background color to
green at the Units folder level, trend screens in that unit, including all of the drops in that unit,
utilize the green background. Trend screens above the Units folder level (or in different units)
remain black. This tree structure allows you to customize configuration information where
necessary.
Each of the major folders contains subfolders. Some subfolders reside in more than one major
folder. Some subfolders can only be found in one major folder. Two subfolders, Configuration and
Graphics, are found in all four major folders. Any settings made to the Configuration or Graphics
folder made at a higher level defaults down through the other folders to the point where you make
a change. That change then defaults down through the remainder of the folders.
OW351_60 33
3.1 What is the Developer Studio system tree structure?
The Developer Studio hierarchical structure (system tree) is shown when the Hardware view bar
is expanded (see the following figure).
Figure 24: Developer Studio System tree as seen from Hardware view bar
Note: Throughout the remainder of this manual, navigation procedures will use the term "system
tree" to describe moving down the hierarchy folder structure.
34 OW351_60
3.2 Systems folder features and functions
The Systems folder is the top-level folder in the Ovation system. It resides directly beneath the
Hardware View bar at the top of the system tree. The Systems folder contains all of the specific
elements for the system and sets the Licensing and Security parameters for all of Ovation.
Configuration settings defined in Systems folder subfolders filter down throughout the entire
system. You also create the Networks folder from the Systems level.
Figure 25: Systems folder
Building a new system for the first time in the Developer Studio tree is typically done by Emerson
personnel. However, you may want to make changes to the initial settings (see To modify the
Systems configuration parameters (see page 36)). Also, building a system usually involves
importing data from an existing database source. As this data is imported, the information
contained in the database is populated into appropriate folders throughout the Ovation Developer
Studio. Different database import files might provide only part of the information required for
system configuration. In this case, you will need to use the Ovation Developer Studio to enter
missing data.
Currently, the Developer Studio is limited to one system. However, a Remote Network can be
processed through the External System Interface.
3.2.1 Subfolders av ailable in the Syste ms folde r
The following table lists the folders that are found in the System folder. The settings that you
define in these subfolders filter down through the entire Ovation system.
Note: The Configuration and Graphics folders are the only folders that are found in all four
major folders (System, Network s, Units, and Drops). Information defined at a lower level
Configuration folder tak es precedence over configuration settings at a higher level folder. See
Understanding the Configuration folder at all levels in the Developer Studio (see page 47) for
more information.
OW351_60 35
Systems subfolders
S YS TE M S SU B F OL D ER DE S C R I P TI O N W H ER E TO F I N D MO R E
I N F O R MATI O N
External System Used to define, map, and access Refer to the Ovation Multiple
Interface remote Networks. Networks User Guide.
Licenses Allows you to add and configure See Managing Ovation licenses (see
licenses in your Ovation system page 145).
through the License Manager.
Security Accesses the Security Manager Refer to the Managing Security for
application that is used to configure Ovation manual.
Ovation security.
Ancillary Allows you to define up to 100 See Defining Ancillary lab els
ancillary labels per Ovation point (see page 129).
type. These labels will be used on the
Ancillary tab when creating points.
Point Groups Allows you to group together various Refer to the Ovation Operator Station
points for monitoring, trending, and Configuration User Guide.
for process diagram purposes.
Note (for Ovation 3.5.0 and later

releases): The Ovation Trend
application has adopted a different
approach to trend groups called
Trend Group Definitions. The
Ovation Developer Studio can
convert existing groups to the TGD
format. Trend Groups will b e
presented from the Oracle Datab ase
in a read-only form. You can then
right-click a trend group name and
click Migrate Trend Group to
convert the trend group into new
TGD files.
Configuration Used to configure various See Understanding the Configuration

applications throughout the Ovation folder at all levels in the Developer
system. Studio (see page 47).
Graphics Stores the graphics and macros for Refer to the Ovation Graphics Builder
the Ovation system. User Guide.
Networks Allows you to insert and modify a See Networks folder features and
network. functions (see page 39).
36 OW351_60
3.2.2 T o modify the Syste ms configuration parame ters
After a system has been created, it may need to be updated or modified.

2. Use the system tree (in the Hardware view bar) to navigate to the Systems folder.
3. Right-click the Systems folder to be modified, and click Open. The Systems dialog box
appears:
Figure 26: Systems dialog box
Note: If Deluxe points exist in the database, the Disable Deluxe Points check box is grayed out
and cannot be check ed.
OW351_60 37
4. Make any desired changes. See the following table for parameter descriptions.
5. When finished, select Ok/Apply to save these settings to the database.
Systems dialog box fields
FI E L D D E S C R I P TI O N
System Name Can be 1 - 8 characters in length. Invalid characters are period (.), dollar sign ($),
percent sign (%), pound sign (#), at sign (@), and space.
System Value Value of your choice.
Database Used internally by Ovation applications to talk to other computers (for informational
Machine purposes only).
Domain Server The drop-down menu contains the list of IP Addresses of the Domain Controller.
IP Address Select a valid IP Address for this attribute.
Offline Mode Permits certain changes to be made off line (See Online/Offline mode
(see page 127)) (Default - Not Checked.)
Restore Mode Online Controller Restore Mode. Reload mismatched Controllers to a prior matched
state. The choices are:
 Restore Mode Disable
 Restore Mode Enable All Drops
 Restore Mode Enable Redundant Drops
(Default - Restore Mode Disabled.)
Refer to the Ovation Controller User Guide for more information.
Disable Deluxe Allows systems not using deluxe points to hide those folders to reduce screen clutter.
Points You cannot insert through the Developer Studio or an input operation while this box is
checked (Default - Not Checked.)
Alarm Cutout Specifies the operation of alarm cutout for the system:
 Inhibit alarms generation.
 Inhibit alarms display cutout, but alarming is still enable.
Bypass If checked, you will not get a preview window before completing a download
Download operation. (Default - Not Checked (and preview window will appear.))
Preview
Enable Load If checked, you will get a preview window of what you are about to Load onto the
Preview Controller. (Default - Not Checked (and preview window does not appear.))
Enable Remote Allows you to enable the use of remote summary alarms (refer to the Ovation Multiple
Summary Networks User Guide). (Default - Not Checked (and remote summary alarms are
Alarms disabled.))
38 OW351_60
3.3 Networks folder features and functions
The Networks folder is a child of the System folder and contains a folder for each network in the
system. It also contains all of the settings for the network objects under it. Any configuration
changes made to items in the Networks folder overrides those same setting in the Systems folder
but the changes only apply to the items in that network.
The Networks folder is the parent folder to the Units folder and contains all the files, items, and
folders that pertain to that Network.
Figure 27: Networks folder
The SIS Network folder is also a child of the Networks folder and contains additional folders for a
SIS network. A Safety Instrumented System (SIS) is a set of components that includes sensors,
Logic Solvers, and final control elements whose purpose is to respond to dangerous plant
conditions. If your plant does not use SIS components, an SIS network folder will not appear in
the system tree.
Note: Currently, only one SIS Network is allowed per database. Refer to the Ovation Safety
Instrumented System (SIS) User Guide for SIS Network folder configuration information.
Building a new network for the first time in the Developer Studio tree is typically done by Emerson
personnel. However, you may want to make changes to the initial settings. See To modify the
Network s configuration parameters (see page 40) for more information.
OW351_60 39
3.3.1 Subfolders av ailable in the Ne tworks folder
The following table lists the folders that are found in the Networks folder. The settings that you
define in these subfolders filter down through the defined network.
more information.
Networks subfolders
NE TW O R K S DE S C R I P TI O N W H ER E TO F I N D MO R E
SU B F OL D ER I N F O R MATI O N
Configuration Used to configure various See Understanding the

applications throughout the Ovation Configuration folder at all levels in
system. the Developer Studio (see page 47).
Graphics Stores the graphics and macros for Information found in the Ovation
the defined network. Graphics Builder User Guide.
Wireless HART Allows you to insert and configure a Information found in the Ovation
wireless HART Gateway. Wireless Devices User Guide.
SIS-System Allows you to insert and configure an Information found in the Safety
SIS network. Instrumented Systems (SIS) User
Guide.
Units Allows you to insert and modify a See Units folder features and
unit. functions (see page 43).
40 OW351_60
3.3.2 T o modify the Ne tworks configuration parame ters
After a network has been created, it may need to be updated or modified.

2. Use the system tree (in the Hardware view bar) to navigate to the Networks folder:
Systems -> Networks
3. Right-click on the Networks folder to be modified, and click Open.
Figure 28: Networks dialog box
OW351_60 41
4. The Networks dialog box appears. Make any desired changes to the window parameters. See
the following table for parameter descriptions.
Figure 29: Networks dialog box
5. When finished, select Ok/Apply to save these settings to the database.

Network dialog box fields
Network Name Can be 1-8 character in length. Invalid characters are period (.), dollar
sign ($), percent sign (%), pound sign (#), at sign (@), and s pace.
Network Name Alias Used internally by Ovation applications to communicate to other
computers (1-8 characters).
Network Value Local network must be assigned a value of 0.
DB Xmit Multicast Address Used internally by Ovation applications to talk to other computers (for
informational purposes only).
Alarm Multicast Address Used internally by Ovation applications (for informational purposes only).
Simulator Multicast Address Used internally by Ovation applications (for informational purposes only).
Advanced Algorithms Used internally by Ovation applications (for informational purposes only).
Multicast Address
Operator Event Multicast Used internally by Ovation applications (for informational purposes only).
Address
6. Select Ok/Apply to save these settings to the database.

7. Ensure that the subfolder with the new Network name is created in the Networks folder, and
that it contains all the necessary folders - Configuration, Graphics, and Unit.
42 OW351_60
3.4 Units folder features and functions
The Units folder is a child of the Networks folder and contains a subfolder for each unit in the
network. The Units folder can be composed of multiple units in one plant to allow for various
configurations. The Units folder is the parent folder to the Drops folder and also to all the files,
items, and folders that pertain to that particular unit.
Any configuration changes made to items in the Units folder overrides those same setting in the
Networks and the Systems folders but the changes only apply to that particular unit.
Figure 30: Units folder
The Units folder allows multiple units (such as two units in a power plant) to operate under the
same system and allows for each unit to have separate configurations from the Network and from
each other.
Note: Currently, up to 16 units can be defined per Network .
To add a new Units folder, see To insert a Unit folder (see page 44).
3.4.1 Subfolders av ailable in the Units folde r
The following table lists the folders that are found in the Units folder. The settings that you define
in these subfolders filter down through the defined unit.
more information.
Units subfolders
S YS TE M SU B F OL D ER DE S C R I P TI O N W H ER E TO F I N D MO R E
I N F O R MATI O N
Configuration Used to configure various applications See Understanding the

for the particular unit. Configuration folder at all levels in
the Developer Studio (see page 47).
Graphics Stores the graphics and macros for the Information found in the Ovation
defined unit. Graphics Builder User Guide.
Drops Allows you to insert and modify drops. See Drops folder features and
functions (see page 46).
OW351_60 43
3.4.2 T o inse rt a Unit folde r
Use the following procedure to insert a new Unit folder.

2. Use the system tree (in the Hardware view bar) to navigate to the Units folder:
Systems -> Networks -> Units
3. Right-click the Units folder.
4. Select Insert New. The Insert New [Units] Wizard dialog box appears.
Figure 31: Insert New [Units] Wizard
5. Type a unit name (using one to six characters) in the Unit Name entry field. Do NOT use the
following invalid characters in a Unit name: period (.), dollar sign ($), percent sign (%), pound
sign (#), at sign (@), and a space.
6. Select a unit value by selecting the appropriate radio button. The unit must have a unique
value within the Network.
44 OW351_60
7. Select Finish and the New [Units] dialog box appears:
Figure 32: New Units dialog box
8. Check that the settings are correct in the New [Units] dialog box.
New [Units] dialog box field description
Unit Name User defined name of the unit (1-6 characters).

Unit Value Internal identifier used by the system (0-15).
9. Select Ok/Apply to save these settings to the database.

10. Ensure that the subfolder with the new unit name is created in the Network folder, and t hat it
contains all the necessary folders - Configuration, Graphics, and Drops.
11. Once a unit is defined, you can make modifications to the settings. To do this:
a) Right-click the Units folder that needs to be modified.
b) Select Open. The Units dialog box appears.
c) Make the desired modifications based on the table above.
OW351_60 45
3.5 Drops folder features and functions
3.5 Drops folder features and functions
The Drops folder is a child of the Units folder. Like the other major folders, the Drops folder takes
its configuration from the Systems, Networks, and Units folders above it. In addition, each drop
can have its own unique configuration parameters that override the settings that were made
higher in the tree. There are two types of Drops folders: one for Controllers and one for
Workstations.
Under the Controller Drops folders, you add and configure I/O devices, points, control tasks, and
holding registers. Under the Workstation Drops folder, you add and configure points and graphics.
Figure 33: Drops folders
Note: Currently, Ovation is limited to 254 drops per network .
See Adding drops to the Developer Studio (see page 153) for more information.
3.5.1 Subfolders av ailable in the Drops folde r
The following tables list the folders that are found in the Controller and Workstation Drops folders.
The settings that you define in these subfolders are for an individual drop.
more information.
Drops subfolders (for Controllers)
DR O P S S U B F O L D E R DE S C R I P TI O N W H ER E TO F I N D MO R E
( F O R CO N TR O L L E R S ) I N F O R MATI O N

throughout the Ovation system. Configuration folder at all levels in
the Developer Studio (see page
47).
Points Used to add and configure points in a See Creating Points in the
Controller. Developer Studio (see page 165).
I/O Devices Used to add and configure I/O devices See Adding I/O to the Developer
in a Controller Studio (see page 225).
Control Tasks Allows you to configure the control Information found in the
tasks in the Controller. applicable Ovation Controller User
Guide.
Holding Registers Opens the Ovation Holding Registers See Adding Holding Registers
Editor. (see page 359).
46 OW351_60
3.6 Understanding the Configuration subfolder at all levels in the Developer Studio
Drops subfolders (for Workstation Drops)
DR O P S S U B F O L D E R DE S C R I P TI O N W H ER E TO F I N D MO R E
( F O R W O R K S TATI O N S ) I N F O R MATI O N

throughout the Ovation system. Configuration folder at all levels
in the Developer Studio (see
page 47).
Points Used to add and configure points in a See Creating Points in the
drop. Developer Studio (see page
165).
Graphics Stores the graphics and macros for the Information found in the Ovation
defined network. Graphics Builder User Guide.
3.6 Understanding the Configuration subfolder at all levels in the

Developer Studio
Configuration is the process of entering data into the Ovation system, usually through a user
interface window, to specify a drop or application (program) function. Configuration is the main
function of the Developer Studio. The Developer Studio is involved in the configuration of
Controllers, Operator Stations, Fieldbus, Simulators, Security, and so forth.
The Configuration folder exists in all four of the major folders: Systems, Networks, Units, and
Drops. The Configuration folder at the Systems through Drops level contains the tools necessary
to configure components at that level. However, at each level, some of the Configuration folder’s
subfolders vary. When a particular component is not applicable to a particular level, the subfolder
is not available. For example, in the Controller Drops folder, there is no subfolder for Alarms. This
is because there is no need to configure alarms for a Controller drop.
Configuration settings made at the Systems folder level filter down through the Networks, Units,
and Drops folder levels. Any configuration changes at a lower folder level (Networks, Units, or
Drops) takes precedence over the configuration at the higher level and also filters down through
its subfolders and lower levels.
For example, if an alarm configuration change is made at the Units folder level, it affects all
alarms in that unit and in all the Drops folders contained in the unit. However, the change does
not affect other units in the Network or system.
OW351_60 47
3.6.1 Configuration subfolder compone nts by le v el
The following table shows each Configuration subfolder component in each of the major
Developer Studio folders.
Configuration subfolder components listed by folder level
S YS TE M F OL D ER NE TW O R K UN I TS F OL D ER DR O P S F O L D E R DR O P S F O L D E R
F OL D ER (W O R K S TATI O N ) (C O N TR O L L E R )
Alarm Alarm Alarms Alarms Controller

Engineering Tools Alarm Check Controller Drop Alarm Controller
Audit Remove Reconfirm Networking Summary Networking
Foundation Alarm Summary External External Network Custom
Fieldbus Network Connections Networking
Connections Interface
Historians Controller MMI MMI External Network
Networking Connections
Graphic Redirect DDB Configuration Ovation Error Domain Ctrl Network Point Processing
Window Log Time Protocol
Definitions
Image Builder External Network Ovation Ovation Error Log Sim Controller
Connections Keyboard
MMI Local Alarm Plant Mode Ovation Keyboard
Collectors
OPC Local Data Servers Point Menu Ovation Session
Manager
Ovation Error Log Master Virtual Point Point Menu
Controller Host Processing
Ovation Keyboard MMI Process Point Processing
Diagrams
Point Menu Network Time Quality Process Diagrams
Protocol
Point Processing Ovation Error Log Review Quality
Process Diagrams Ovation Keyboard Sim Controller Review
Quality Point Menu Simulation Simulation Model
Model
Review Point Processing Trend SCADA
Sim Controller Process Diagrams SNMP
Simulation Model Quality Trend
Simulation Drop Review
Config
Trend Sim Controller
Simulation Model
Trend
48 OW351_60
3.6.2 Configuration subfolder compone nt de scriptions
The following table briefly describes and lists all of the possible components that can be found in
the default Configuration subfolder.
Configuration subfolder components listed in alphabetical order
CO MP O N E N T DE S C R I P TI O N FO L D E R ( S ) RE F E R E N C E
F OU N D I N
Alarms Allows you to monitor and Systems Ovation Operator Station

detect abnormal plant Networks Configuration Guide
conditions. Units
Drops
(Workstation)
Alarm Check Reconfirms points that have Networks Ovation Operator Station
Remove Reconfirm been removed from being Configuration Guide
checked for alarms
Alarm Summary Allows you to define alarm Networks Ovation Multiple Networks
summary groups that are used User Guide
in multiple networks.
Controller Drop containing input and Drops (Controller) Ovation Controller User
output modules connected to Guide
field devices by wires. These
modules monitor each device
for changes in the device's
condition.
Controller Specifies network routing Networks, Ovation Controller User
Networking information. Units Guide
Drops (Controller)
Custom Networking Specifies the configuration of Drops (Controller) Ovation Controller User
Interfaces the unused Controller network Guide
interfaces. Configuration of a
network interface means
specifying the IP address,
subnet mask, and
speed/duplex of the interface.
DDB Configuration Dynamic data is a portion of a Networks See DDB Configuration
point record. It is broadcast on (Networks folder) (see
the Ovation Network in page 130).
Dynamic Data Blocks or DDBs.
Domain Ctrl Network Defines which clock (internal or Drops (Operator See To configure the
Time Protocol external) the Domain Controller Station) Domain Controller
should take its time from. Network Time Protocol
(see page 134).
Drop Alarm Allows you to define alarms Drops Ovation Multiple Networks
Summary summary groups at the drop (Workstation) User Guide
level.
Engineering Tools Provides an automated way to Systems See Engineering Tools

Audit log engineering events. Audit (see page 341).
OW351_60 49
F OU N D I N
External Network Used to define a remote Networks Ovation Multiple Networks

Connections connection. Units User Guide
Drops
(Workstation)
Drops (Controller)
Foundation Fieldbus An all-digital, two-way, multi- Systems Ovation Foundation
drop communication protocol Fieldb us User Guide
that interconnects intelligent
devices such as actuators,
sensors, discrete devices, and
Controllers in the field.
Graphic Redirect Allows you to take a standard Systems Ovation Operator Station
Window Definitions graphic file that is currently Configuration Guide
displayed on an Ovation
Operator Station (source drop)
and display it on another
Operator Station (destination
drop
Historians Drop that collects process Systems Ovation Process Historian
values and messages that are User Guide
generated by your Ovation
control system.
Image Builder A dictionary that contains a list Systems See Creating Studio icons
of all Image files used in the using the Image Builder
Ovation system tree. These (see page 52).
images replace the folders that
represent Ovation database
hierarchy classes in the system
tree.
Local Alarm Drops on the local network that Networks Ovation Multiple Networks
Collectors connect to the remote User Guide
networks in order to collect
remote alarm data.
Local Data Servers Drops on the local system that Networks Ovation Multiple Networks
handle remote requests for User Guide
point data.
Master Virtual Drop that is designated as the Networks Ovation Virtual Controller
Controller Host Master Host to coordinate User Guide
timing between all other hosts
on the network. Necessary on
systems with more than one
host.
MMI Defines how certain Ovation System Ovation Operator Station

information (such as alarm Networks Configuration Guide
information) is displayed on the Units
Operator Station drop. Drops
(Workstation)
Network Time Identifies the drop or external Networks See Network Time
Protocol server that is providing the time Protocol (NTP) (Networks
base for the Ovation system folder) (see page 132).
50 OW351_60
F OU N D I N
OPC OPC (Object Linking Systems OPC Tools User Guide

Embedding) is a series of
standard specifications that are
created based on general
computing technology to allow
for interoperability between
various industry standards.
The OPC standard specifies
the communication of real-time
plant data between any
manufacturers control devices.
Ovation Error Log Contains error, warning, and Systems Ovation Operator Station
informational messages Networks Configuration Guide
generated by the various Units
Ovation services and Drops
applications (Workstation)
Ovation Keyboard Optional keyboard that is used Systems Ovation Operator Station
in conjunction with the Networks Configuration Guide
standard keyboard and mouse.
Units
Drops
(Workstation)
Ovation Session Provides quick access to Drops Ovation Operator Station
Manager useful system information such (Workstation) Configuration Guide
as the current Ovation version,
remote data server status, and
security information
Plant Mode Defines the current state of the Units See Plant Mode (Units
plant, with up to six folder) (see page 135)
configurable states.
Point Menu Provides a quick method to Systems Ovation Operator Station
select a point displayed at the Networks Configuration Guide
Operator Station and access Units
information about that point Drops
from different application (Workstation)
windows.
Point Processing Processes commands and Systems See Point Processing (All
performs alarming/limit Networks folders) (see page 136).
checking for points Units
Drops
(Workstation)
Drops (Controller)
Process Diagrams Allows you to view graphic Systems Ovation Operator Station
diagrams at the Operator Networks Configuration Guide
Station. Units
Drops
(Workstation)
Quality Ovation supports four quality Systems Ovation Operator Station
states: GOOD, FAIR, POOR, Networks Configuration Guide
and BAD. Each state indicates Units
the condition of the point to the Drops
operator and algorithms. (Workstation)
OW351_60 51
3.7 Creating Studio icons using the Image Builder
F OU N D I N
Review Allows you to search the Systems Ovation Operator Station

database for points having Networks Configuration Guide
specific characteristics or Units
belonging to a particular point Drops
group. (Workstation)
SCADA SCADA (Supervisory Control Drops SCADA User Guide for
and Data Acquisition) is a (Workstation) Windows-Based Ovation
control system that gathers Systems
data from remote locations in
order to monitor and manage
equipment and conditions.
Sim Controller Standard Ovation Controller or Systems Ovation Simulation User
Virtual Controller loaded with Networks Guide
Simulator software in addition Units
to the normal plant database Drops (Controller)
and control software.
Sim Model Imitates how an actual plant Systems Ovation Simulation User
would respond to the outputs Networks Guide
of the SimControllers. Units
Drops
(Workstation)
Simulation Drop Drop with simulator software Systems Ovation Simulation User
Config loaded on it. Guide
SNMP Program designed to monitor Drops See SNMP (Drops) (see
and report the activity in (Workstation) page 138).
various devices on the
Network.
Trend Allows you to view Live and Systems Ovation Operator Station
Historical data in the form of Networks Configuration Guide
graphical charts, tables, and Units
printouts. Drops
(Workstation)
The Image Builder is a dictionary that contains a list of all images (sometimes called Icons
because of the .ico extension to the file name) files used in the Ovation system tree. These
images represent the folder in the system tree. For example, the globe image is the default setting
for the system and replaces the folder image in the system tree.
Using the Image Builder, you can apply the default image settings to your system tree and
replace many of the folder images with images more relevant to a particular item (for example,
analog points.) The Image Builder is only located at the System level.
In addition to the default image settings, you can use the Image Builder to import a variety of
other images to associate with items in the system tree. You can import any image saved as an
image (.ico) file into the image dictionary and use it as a folder image.
52 OW351_60
3.7.1 T o acce ss the Image Builde r

2. Use the system tree (in the Hardware view bar) to navigate to the ImageBuilder folder:
Systems -> Configuration -> ImageBuilder
3. Select the ImageBuilder folder.
4. Check the WorkPad window to ensure that there is no ImageBuilder Dictionary file already
created (OvPTClsImage.ild).
Note: If the OvPTClsImage.ild file already exists, double-click on it to open the file.
5. If there is NO ImageBuilder Dictionary file present in the WorkPad window, right -click the
Image item.
6. Select Insert New from the right-click menu. The Insert New Image Builder Wizard appears.
The name of the dictionary (OvPTClsImage.ild) is already entered in the Name field. You
cannot modify this field.
7. Select the Finish button. The Ovation Image Builder Wizard appears:
Figure 34: Image Builder Wizard
OW351_60 53
8. Select the Next button and the Image Builder Dictionary dialog box appears. The dictionary
contains image files associated with database classes by default. These default settings can
be edited and additional images can be added to the dictionary.
Figure 35: Image Builder dialog box
The following table lists and describes the Ovation Image Builder window fields.
Image Builder window fields and descriptions
FI E L D DE S C R I P TI O N
Image List:
Image Displays a picture of the image file.
ID System-generated ID number of the image. Given when an image is ad ded to the
dictionary.
In Use Determines whether or not the image is associated to a class (item in the Developer
Studio system tree).
Class List:
Name Name of the class (item in the Developer Studio system tree).
Class System-generated number associated with the class.
Used by List of classes that are associated with an image.
(scrolling list)
Image List of available images that can be used to make an association.
(drop-down menu)
Use Default Image Associates the selected item in the Class List with the default image that is defined
(check box) in the Ovation software.
54 OW351_60
3.7.2 T o associate an image to a class (Studio ite m)

3. Right-click on the ImageBuilder item in the WorkPad window.
4. Select Open. The Ovation Image Builder Configuration dialog box appears.
5. Go to the Class List and select the name of the class that you want to associate with an
image.
6. Pull down the Image menu.
Figure 36: Image Builder dialog box (associate/di sa ssociate a class)
7. Select the appropriate image. The image association is made.
Note: If a user default image is associated with the class, it appears next to the Image drop-
down list. Simply select the Use Default Image to select that image.
8. See To complete the image building or editing process (see page 59) for information on
finalizing the process.
OW351_60 55
3.7.3 T o change class associations
There are two ways to change associations between classes and icons.
Method 1

3. Right-click the ImageBuilder item in the WorkPad window.
5. Select the image to be changed in the Image List.
6. Notice that the “Used by” window contains a list of class associations that are affected by the
change.
7. Select the Change button and the Select a New Icon File to Replace dialog box appears.
8. Select an icon file (.ico).
9. Select Open.
10. The new image is added to the dictionary and replaces the previous image in all its
associations.
Method 2

3. Right-click the ImageBuilder item in the WorkPad window.
5. Go to the Class List and select the name of the class that you want to disassociate with an
image.
56 OW351_60
6. Open the Image drop-down menu.
Figure 37: Image Builder dialog box (changing class associations)
7. Select None or another Image. The image for that class is disassociated with the old image or
re-associated to a new image.
8. See To complete the image building or editing process (see page 59) for information on
finalizing the process.
3.7.4 T o add or de le te image s (icon) in the dictionary

3. Right-click on the ImageBuilder item in the WorkPad window.
OW351_60 57
5. To add a new image to the dictionary, perform the following:

a) Select the New button. The Select a new icon file to add dialog box appears:
Figure 38: Select a new icon file to add dialog box
b) Select an image file (.ico) and select Open. The new image is added to the dictionary.
6. To delete an image (icon) from the dictionary, perform the following steps:
a) From the Ovation Image Builder Configuration dialog box, select the Image in the Image
List.
b) Select each of the names from the Class List that are found in the Used by list for that
Image.
c) Remove all image associations for that image in the Class List. See To change class
associations (see page 56).
d) Select the image and then the Delete button. The icon is deleted from the dictionary.
Note: All icon/class associations must be removed before an icon can be deleted from the
dictionary. If associations have not been removed, the following error message appears: “You
cannot delete the image because it is referenced by one or more classes in the class list. Please
delete all references and try again”.
58 OW351_60
3.7.5 T o comple te the image building or e diting process
After you make any additions or changes to the Image Builder, perform the following steps to
complete the image building process:
1. After you are finished with all of the changes on the Ovation Image Builder window, click the
Next button.
Figure 39: Image Builder dialog box
OW351_60 59
2. The Image List Dictionary File - Save screen appears asking you how you want to save the
changes.
Figure 40: Ovation Image Builder - Image List Dictionary File - Save screen
3. Select one of the following options:

 Save the changes to the OvPtClsImage.ild file.
 If the OvPtClsImage.ild file is read-only, save the changes to a different file. (Enter the full
path name in the File entry field or use the Browse button.)
 Discard the changes made to the OvPtClsImage.ild file.
4. Click the Next button.
60 OW351_60
5. The Ovation Image Builder Complete window appears. Click the Finish button.
Figure 41: Ovation Image Builder Finish window
6. Perform a Download function (see page 99).

7. Exit the Developer Studio.
8. Restart the Developer Studio to apply the changes.
OW351_60 61
SECTION 4
4 Working with common Developer Studio operations
IN THIS SECTION
Common Operation menu functions ........................................................................... 63

Delet e function ......................................................................................................... 63
Purge function .......................................................................................................... 64
Undelete function...................................................................................................... 64
Search function ........................................................................................................ 65
Where Used function ................................................................................................ 73
Find function............................................................................................................. 84
Back up/Restore ........................................................................................................ 86
Consistenc y Check ing............................................................................................... 91
Load function............................................................................................................ 94
Download function .................................................................................................... 99
Reconcile function .................................................................................................. 104
Coefficient calculation ............................................................................................. 106
Clear function ......................................................................................................... 109
Reboot function ...................................................................................................... 113
Update Security Infrastructure function..................................................................... 114
Baseline Creation function....................................................................................... 123
Baseline Comparison function ................................................................................. 124
What is the Print Screen utility? ............................................................................... 126
4.1 Common Operation menu functions
The Operations menu on the Developer Studio lists the functions you can perform on the
Developer Studio. Some of the common functions performed in the Developer Studio are listed in
the following sections.
Note: This section only describes the operations that are not discussed in other Ovation User
manuals. For a complete list of items on the Operations menu and where they are described,
see Operation menu on the Developer Studio window (see page 15).
4.2 Delete function
Deleting an item from the Developer Studio’s Hardware view bar removes it from the system tree.
As discussed in TrashCan view bar (see page 12), certain items can be restored from the
TrashCan view bar to their original location.
Note: If an item is being used by something that remains in the system tree, the references
must be removed before the delete operation is permitted. (See Where Used function (see page
73) for assistance in determining reference information.)
OW351_60 63
4.3 Purge function
4.2.1 T o use the De lete function
Note: The deletion of control sheets is handled in a slightly different manner. The database
item, the Control Builder files, and the default points associated with the sheet are permanently
deleted (that is, purged.) In addition, if a higher level folder (Drop, Unit, Network , or System) is
deleted, all control sheet items under it are purged.

2. Use the system tree to navigate to the folder or item to be deleted.
3. Right-click on the desired folder or item.
4. Select Delete. The “Are You Sure...” dialog box appears.
5. Select Yes to delete.
 Select No to cancel the operation.
Note: After deleting a point, you must perform a load (Load function (see page 94)) before the
deletion is recognized by the system.
4.3 Purge function
Purging permanently removes an object from the TrashCan view bar. Once an object has been
purged from the TrashCan view bar, it is removed from the system. This includes any files that
are associated with the object.
4.3.1 T o use the Purge function

2. Select the TrashCan view bar. The TrashCan view bar displays the system tree within the
Developer Studio Overview window.
3. In the TrashCan view bar, right-click the item to be deleted.
4. Select Purge. The “Are You Sure...” dialog box appears.
5. Select Yes to permanently delete the item from the system
 Select No to cancel the operation.
4.4 Undelete function
Individual objects or objects with descendants that have been deleted from the Hardware view bar
and moved to the TrashCan view bar can be restored to their original location in the Hardware
view bar.
Note: For an item to be undeleted, it is validated to ensure that it is legitimate to return the
object to the system tree. For example, a duplicate name validation may occur. In other words, if
A100 point is deleted, then a new A100 point is added to the same Unit, the system will not
allow the object A100 in the TrashCan to be "undeleted" (restored).
64 OW351_60
4.5 Search function
4.4.1 T o use the Unde lete function

2. Select the TrashCan view bar in the Developer Studio.
3. Right-click the item to be restored to the Hardware view bar.
4. Select Undelete. The “Are You Sure...” dialog box appears.
5. Select Yes to move the deleted item(s) back to the original location in the Hardware view bar,
 Select No to cancel the action.
Note: After restoring a point, use the Load function (see page 94) on the drop where the point
has been replaced.
4.5 Search function
The Search function allows you to search for items under the currently selected folder using
optional user-specified criteria to limit the results of the search. Additionally, the Search function
provides a tool to:
 Edit individual items.
 Perform global/mass changes.
 Query the database and sort items according to a user-specified criteria.
 View all attributes of the item(s).
All items in the system can be searched. Searches are performed downward in the tree structure.
A search at the Units folder level queries the database for information only about that unit and
drops and points associated with that unit. The search does not query other Units or Networks in
the system. If the search is performed at the System folder level, all Networks, Units, and Drops in
the system are queried.
Note: Be careful entering text in the Search function dialog box because the function is case
sensitive.
OW351_60 65
4.5 Search function
4.5.1 T o be gin the Se arch function

2. Use the system tree to navigate to the level where you want to begin the search.
3. Right-click the desired item. If the search was initiated at the Ovation Systems folder, all
appropriate objects that fall below the Ovation system item in the tree structure are available
for query. The Search Options Wizard - (Step 1/2) appears:
Figure 42: Search Options Wizard (Step 1 of 2)
4. Choose the type of object to search for from the menu.

If you select a "Family" item, the search will be performed across all objects of similar types.
For example, if you select Family: Point, the search will be conducted for all types of points.
However, if you select an object item, such as Object:Analog Points, the search will only be
on analog points.
5. Click Next.
66 OW351_60
4.5 Search function
6. The Search Options Wizard (Step 2/2) appears:
Figure 43: Search Options Wizard (Step 2 of 2)
7. Select the type of search to perform:

 Find all items searches the database for all instances of the object and lists all of the
instances in the Search: Item: dialog box.
 Find specific items using search clauses allows you to define search criteria that will
narrow your search (see page 68).
8. Select Finish.
9. If you select Find all items, see to To use the Search function to display results (see
page 70).
10. If you select Find specific items using search clauses, see To use the Search function to
perform a narrow search (see page 68).
OW351_60 67
4.5 Search function
4.5.2 T o use the Se arch function to pe rform a narrow se arch

1. If you selected Find specific items using search clauses, the Search dialog box appears.
In this Search example, analog points are selected.
Figure 44: Search window items
Search window items
I TE M DE S C R I P TI O N
Search (Top) Displays the search criteria that the user selected.
Search (Bottom) Area where a limiting clause is created.
Attribute Pull-down menu that contains a list of all the attributes in the Developer
Studio.
Condition Pull-down menu that contains conditional text used to create a limiting
clause. The choices are: Equal To, Not Equal To, Less Than, Greater
Than, Less Than or Equal To, Greater Than or Equal To, Like, Not Like,
In, Not In, Null, Not Null.
Value Enter the applicable name, number, and so forth to search for.
Add button Takes the information defined in the bottom Search window and adds it
to the top Search window and sets it as the search criteria.
Delete button Removes the selected limiting clause from the Search window.
2. Pull down the Attribute menu and select an attribute from the list. This item is used to further
narrow your search from the previous window. Selected Object:Analog Points from the S earch
Options Wizard (Step 1/2), and the Attribute menu will display different attributes of an analog
point such as object name, frequency, description, and so forth.
68 OW351_60
4.5 Search function
3. Pull down the Condition menu and select conditional text that is used to create a limit ing
clause (equal to, not equal to, and so forth).
4. Enter the item to search for in the Value entry field. For example, if you select Object Name
as the attribute, you may enter all or part of a point name and the system will search for
analog points that have that name.
You can utilize wild cards to help broaden or narrow your search:
 Use the percent symbol (%) to match the text you entered plus additional characters
included in the object.
 Use the underscore (_) to match exactly one character.
 To match the % or _ literally, precede the character with \ (back slash.) For example, to
find the title Drop %, type Drop\% in the Find What field.
5. Select the Add button to add the search criteria (attribute, condition, and value) to the top part
of the Search window.
6. Add additional clauses to broaden or restrict the search, if necessary.
Note: To delete search criteria, select one of the search criteria strings in the top portion of the
Search window. Once a search string is highlighted, the Delete button becomes active. If you
want to mak e a change to search criteria, you must delete the old one first and then create a
new one.
Figure 45: Search window showing a defined search criteria
7. Select Ok to perform the search.

8. Proceed to To use the Search function - results (see page 70).
Note: Each of the limiting clauses are implicitly separated by AND operators. In other words, the
list of objects retrieved are those where <clause1> AND <clause2> AND...<clauseX> are true.
OW351_60 69
4.5 Search function
4.5.3 T o use the Se arch function to display re sults

1. If you selected Find all items on the Search Options Wizard (Step 2/2) or if you chose to
narrow the search by defining search criteria (see page 68), the Search window (results)
appears:
Figure 46: Search results
Search window items
I TE M D E S C R I P TI O N
item(s) found Shows how many items were found in the search.
Object column Lists, by name, the objects found in the search.
Search Again button Opens the Search dialog box, enabling you to modify the search
criteria.
Add Column(s) button Adds columns that provide additional attributes of the objects listed
in the Object column. See To use the Search function to add
columns (see page 71) for information on this helpful feature.
Refresh Column(s) button Refreshes the data in the columns.
2. To expand or limit the search, select the Search Again button and the Search dialog box
appears. Repeat the steps described in To use the Search function to perform a narrow
search (see page 68).
3. To make modifications to the point, click on the point name and a Point window appears (see
page 177). From this window, you can make changes to many of the point's parameters. For
additional information on your search item, see To use the Search function - add columns
(see page 71).
70 OW351_60
4.5 Search function
4.5.4 T o use the Se arch function to add columns
After you have obtained the results of a search, you may want to gather additional information on
the points or even change some of the information. Adding columns of data to your search results
gives you this ability.
1. From the Search (results) window (see page 68), select the Add Column(s) button. The Add
Columns dialog box appears.
Note: The available attributes are based on the type of object being searched.
Figure 47: Add Column(s) window
2. Highlight the column(s) that you want to add to the Search (results) window.
OW351_60 71
4.5 Search function
3. Select Ok. The column(s) are added to the Search (results) dialog box.
Figure 48: Search (results) window with an added column
4. When you add columns, you can perform the following functions:
 Edit information in a single cell and select the Apply/Ok button. The change is saved to
the database.
 Make global changes to all of the entries in a column. To do this, enter new informat ion to
one cell. Right-click on the cell and select Copy to column. All of the entries in that
column change to display the new information.
 Select a column heading to sort the list alphabetically, based on the selected column.
 Rearrange columns by dragging and dropping the column heading.
 Delete a column by right-clicking on the column header and selecting the option to delete
the column.
 Use the File menu to print or save the search results to a file (all dialog boxes in the
Studio provide this feature).
72 OW351_60
4.6 Where Used function
The Where Used function searches the database and finds all the references of the specified
object. If an object is used in the database, the Where Used feature provides a detailed report of
what program uses it, where it is used, and how it is used.
The Where Used wizard provides for four different types of searches:
 Find all references to.
 Find all references to ... and its children, outside of.
 Find all references made by.
 Find all references made by ... and its children, outside of.
Figure 49: WhereUsed Wizard
OW351_60 73
4.6.1 T o use the Whe re Use d function
Use the following procedure to use the Where Used function:

2. Use the system tree to navigate to the desired item (point, graphic, drop, and so forth).
3. Right-click on the desired item.
4. Select Where Used. The Where Used Options Wizard appears.
Note: The Where Used option will only display on the right-click menu if it is applicable to the
selected item.
Figure 50: WhereUsed Wizard
74 OW351_60
The four types of reference searches are as follows:

 Find all references to ... shows all references to the selected item
 Find all references to ... and its children, outside of ... shows all references to the
selected item and its children (those items inside its folder) and any references to items
outside of the folder.
 Find all references made by ... shows all references made by the item to any other item.
 Find all references made by ... and its children, outside of ... shows all references
made by the selected item and its children (those items inside or under its folder) to items
outside of the folder.
5. Select Find Now. The results display in a window that is applicable to the type of search you
requested. The following figure shows one example of a results window for the Where Used
function.
Figure 51: Example of Find all references made by ... and its children, outside of ... results
window
OW351_60 75
Where Used results -- Column descriptions
C O L U MN DE S C R I P TI O N
Object Object in system tree that references the selected item. Select the button to open the
item’s configuration dialog box.
Type Describes the referencing object.
How Used Describes how the referencing object uses the selected item.
Path Describes where the referencing object is located in the system.
The following columns only appear after a Find all references made to/made b y and its children, outside
of is selected.
Who Selected item or the child that is being referenced. Select the button to open the item’s
configuration dialog box.
Who Type Describes the referenced Who item.
See the following sections for examples of each of these Where Used options:
 Example of the Find all references to ... option (see page 77).
 Example of the Find all references to and children ... option (see page 79).
 Example of the Find all references made by ... option (see page 81).
 Example of the Find all references made by and children ... option (see page 83).
76 OW351_60
4.6.2 Example of the Find all re ferences to ... option
In the following example, a Where Used search was selected from analog point ,
01_PSN_D14_ASSIGN_FLA in the system tree. The Find all references to option was used as
the search method.
Figure 52: Find all references to ... option selected
OW351_60 77
The following figure shows the results of the search.
Figure 53: Example of Find all references to ... results window
In this example, the two control sheets (as indicated by the Type column) reference point
01_PSN_D14_ASSIGN_FLA. In one sheet, it is a referenced point, and in the other, it is an
originated point.
If you click on the button, (which is the name of the sheet in the Object column), the Cont rol
Builder displays with that sheet loaded. From the Control Builder, you can access the Find Point
Name dialog box and search for the point on the sheet. (Refer to the Ovation Control Builder User
Guide for more information.)
78 OW351_60
4.6.3 Example of the Find all re ferences to and childre n ... option
In the following example, a Where Used search was conducted from I/O module
1C1142G01/1C31110G03 Contact Input w/Onboard 48V wetting in the system tree. The Find all
references to ... and its children, outside of option was used as the search method.
Figure 54: Find all references to and its children, outside of ... option selected
OW351_60 79
Figure 55: Find all references to ... and its children, outside of ... results window
In this example, the results window displays the items that reference I/O module
1C31142G01/1C31110G03 Contact Input w/Onboard 48V wetting and its children and the items
outside of that folder.
The Type column shows what kind of object references the I/O module. In the figure above, the
type of object that is referencing this I/O module is a point. If you click on the name of a point
(found in the Object column), the Point dialog box displays appears for that point, showing all of
its entire configuration. You can also click on the module (found in the Who column) to display the
Module window showing all of its entire configuration. From the respective configuration windows,
you can make any necessary changes.
80 OW351_60
4.6.4 Example of the Find all re ferences made by ... option
In the following example, a Where Used search was selected from Diagram #1800 in the system
tree. The Find all references made by option was used as the search method.
Figure 56: Find all references made by ... option selected
OW351_60 81
Figure 57: Example of Find all references made by ... results window
In this example, the results window displays the items that Diagram #1800 references. The type
of object that this diagram is referencing is a drop point (as shown in the Type column).
If you click on the button, (which is the name of the point in the Object column), the Point dialog
box displays for that point, showing its entire configuration. From the Point configuration window,
you can make any necessary changes.
82 OW351_60
4.6.5 Example of the Find all re ferences made by and childre n ... option
In the following example, a Where Used search was selected from Control Sheet 002 DropStatus
Drop 14 in the system tree. The Find all references made by and its children, outside of option
was used as the search method.
Figure 58: Find all references made by and its children, outside of ... option selected
OW351_60 83
Figure 59: Example of Find all references made by ... and its children, outside of ... results
window
In this example, the results window displays the items that Control Sheet 002 DropStatus Drop 14
and its children and the items outside of that folder references.
The Type column shows what kind of object the sheet references. In the figure above, the type of
object that the sheet is referencing is a point (analog, packed, and so forth). If you click on the
name of a point (found in the Object column), the Point dialog box displays appears for that point,
showing all of its entire configuration. You can also click on a sheet name (found in the Who
column) to display that sheet in the Control Builder. From the Control Builder, you can access the
Find Point Name dialog box and search for the point on the sheet. (Refer to the Ovation Control
Builder User Guide for more information.)
84 OW351_60
4.7 Find function
4.7 Find function
The Find function provides a tool to search for objects by name, using wild cards to broaden the
search. Unlike the Search function, the Find function does not allow editing of found items.
Note: Use caution when entering text in the Find function; it is case sensitive.
4.7.1 T o use the Find fe ature

2. Use the system tree to navigate to a folder at the level where you want to begin the search.
3. Right-click the desired folder. (For example, if a search was initiated at the Networks level, all
items that fall below that level in the file structure are available for query .) The Find: All
Objects dialog box appears:
Figure 60: Find:All Objects window
OW351_60 85
4.8 Backup/Restore
4. In the "Find what" field, enter a name, or part of a name of an item you are looking for. Utilize
wild cards to help broaden or narrow your search:
 Use the % (percent symbol) to match the text you entered plus additional characters
included in the item.
 Use the _ (underscore) to match exactly one character.
 To match the % or _ literally, precede the character with \ (back slash.) For example, to
find the title Drop%, type Drop\% in the "Find What" field.
5. Select one of the following radio buttons:
 Find anywhere in database to locate the item wherever it occurs in the entire database,
 Find in <specific folder> only to locate occurrences of the item within the folder where
you began the search.
6. Select Find Now and the fields populate with the items found.
7. Select an item in the Object column and click the Open button. The applicable configuration
dialog box appears for the selected item. However, you will not be able to interact with the
dialog box until you close the Find:All Objects window.
Note: You can select several items in the Object column (or select them all by click ing the
Select All button) at one time. If multiple items are selected when you click the Open button, all
of the applicable dialog boxes will open in succession. To deselect a selected item, click the
Clear All button.
8. When you are finished with the Find window, select the Close button.
4.8 Backup/Restore
This utility backs up and restores the Ovation database. It performs an export of the database in
Oracle and saves it to a file. If necessary, this file can be imported back into the database to
restore it to a previous state.
Note: The Back up/Restore utility in the Ovation Developer Studio is only designed to back up
the Oracle database. It does NOT back up a complete image of the entire Ovation system. For
this function, the Acronis Back up and Recovery application is needed. Refer to the System
Backup and Recovery User Guide for more information.
86 OW351_60
4.8 Backup/Restore
4.8.1 T o use the Ov ation Backup function

2. Use the system tree to navigate to the Systems folder.
3. Right-click on the Systems item.
4. Select Backup/Restore. The Ovation Backup/Restore window appears:
Figure 61: Ovation Backup/Restore window
5. Enter the full path of where the exported file backup should be placed in the Place Back ups in
entry field. If you do not know the full path, select the folder icon beside the entry field to
browse for a directory.
6. Specify how many backups you want to keep (before they are automatically deleted) in the
Keep at most this many back up field. The default is 3. Once the number of backup files
exceeds the number specified here, the oldest file will be deleted.
7. The configuration settings for the backup are defined in the Parameters tab (see page 88).
Note: Emerson recommends that you do NOT change the default settings when running a
back up.
8. To schedule a backup to automatically run at regular intervals, press the Schedule button
(see page 89).
9. Select the Backup Now button.
The database backs up, and the file is saved in the specified directory. To view a status of the
backup, select the Status Log tab.
OW351_60 87
4.8 Backup/Restore
4.8.2 Unde rstanding the Backup/Restore Parame ters tab
The Parameters tab on the Ovation Backup/Restore window displays the configuration settings
for the backup. The settings that appear are the default Ovation parameters for your system.
Emerson recommends that you use the default settings when running a backup.
Figure 62: Ovation Backup / Restore window -- Parameters tab
Parameters tab field descriptions
ATTR I B U TE V AL U E
Ovation
Data Directory Name of the Ovation data directory. The default is
D:\OvPtSvr\Ovation.
User ID User identification.
OvPtExport Other Parameters Names of other export parameters.
Oracle
Home Directory Name of the Oracle home directory.
User ID User identification.
Other Export Parameters Names of other export parameters.
Import Program Name Name of the input program
Export Program Name Name of the export program.
Restore Defaults button Restores the entries on the window to their default settings.
88 OW351_60
4.8 Backup/Restore
4.8.3 T o sche dule backups
You can define a schedule of when you want the system to automatically back -up your data.
1. Access the Ovation Backup/Restore window (see page 86).

2. Select the Schedule button. A notice window appears:
Figure 63: Notice window for the Task Scheduler
3. Read the notice and if you still want to schedule a backup, click the Yes button. If you want to
quit without scheduling, click No.
OW351_60 89
4.8 Backup/Restore
If you select Yes, the Task Scheduler window appears:
Figure 64: Task Scheduler
4. The Task Scheduler is part of the Microsoft Management Console software. For information
on using the Task Management, refer to the user documentation or select Help Topics on the
Help menu.
90 OW351_60
4.9 Consistency Checking
4.8.4 T o use the Re store function
You can restore the database to a previous state by importing the most current version of a
backup file.
1. Access the Ovation Backup/Restore window (see page 86).

2. Select the Restore button. A notice window appears:
Figure 65: Restore Notice window
3. Read the Restore Notice window. If you still want to continue with the restore, click the Yes
button. If you want to quit the restore function, click the No button.
4. If you selected the Yes button, the database is restored to the last backup (using the most
current backup file).
The Ovation system periodically checks for consistency throughout different levels of the system.
One example of a consistency check would be if the system gives you an error message because
you entered an invalid character in a window field. Other consistency checks are run
automatically before a user runs a Load or a Download function. This is done to preserve the
integrity of the Ovation system.
However, the Developer Studio allows you to manually run a consistency check any time you
make any additions, corrections, or deletions to the system. If you run a consistency check and
errors are detected, a report displays which allows you to correct the errors before performing a
load or a download.
OW351_60 91
4.9.1 T o run a Consistency Che ck
You can run consistency checking at the Systems, Networks, Units, or Drops folder level. For
example purposes here, the Drops folder is used in the following procedures.

2. Use the system tree (in the Hardware view bar) to navigate to the Drops folder:
3. Right-click on the appropriate Drop<number> folder and select Consistency Check.
Figure 66: Right-click menu on Drop<number> folder
92 OW351_60
4. A consistency check report generates. When it finishes, the results are shown in the
Consistency Check Report window. See the following figure.
Figure 67: Consistency check Report window
5. There are three types of items that are reported:

 Errors - Represents problems in the system that must be corrected before the system
allows you to perform a Load or a Download function.
 Warnings - Represents the fully functional inconsistencies that should be fixed prior to the
completion of engineering configuration of the Ovation system.
 Information - Provides information to the user. Does not affect the ability to load or
download.
6. A series of columns display for each message that is reported. Two of these columns, Group
and Object, have raised buttons. Click on a button to display a configuration dialog box for a
point or a drop (as is applicable to the message).
The Attribute column specifies the properties that describe the object and the Value column
specifies the f type of input that object requires.
7. Make any desired changes and rerun the consistency check to ensure that all errors and
warning are corrected before loading or downloading.
OW351_60 93
4.10 Load function
8. If you choose to run a load or a download and errors still exist, the following window appears
(Download example shown):
Figure 68: Download Preview window
9. You can view the details of the errors or ignore the errors and select the Ok button to
continue the load or download. You can also choose to Abort the operation.
10. If necessary, correct any errors before proceeding with the load or download.
4.10 Load function
The Load function is used to load control sheets, points, and holding registers onto the system.
Note: If you modify, add, or delete a point, the Load flag will display on the point originator. On
occasion, the system event that notifies the Ovation Developer Studio to display its flags may
not be detected. The Refresh operation may be used to display and to confirm the flag status.
94 OW351_60
4.10 Load function
4.10.1 T o load application information

1. Access the Ovation Developer Studio (see page 5).
2. Use the system tree to navigate to the Drops item:
3. Right-click on the appropriate Drops item.
4. Select Load to perform the load function.
 If the drop is non-redundant AND the Load Preview function is not enabled, the load
automatically starts.
 If the drop is non-redundant AND the Load Preview function is enabled, the Load
Preview window (see page 96) appears.
 If the drop is redundant, the Load Wizard dialog box appears (see the following figure).
Figure 69: Load Wizard
5. Select the appropriate target drop(s) from the redundant drop options.
6. Select Finish.
7. If the Load Preview function is enabled, the Load Preview window (see page 96) appears. If it
is NOT enabled, the load starts.
For specific information regarding loading control information to a Controller drop, refer to the
appropriate Ovation Controller User Guide.
OW351_60 95
4.10 Load function
4.10.2 T o use the Load Pre v iew function
The Load Preview window allows you to see what will be loaded into a Controller or workstation
before the actual load occurs.
Use the following procedure to enable and use the Load Preview function:

2. Ensure that the Load Preview function is enabled. To do this:
a) Use the system tree (in the Hardware view bar) to navigate to the Systems folder.
b) Right-click on the Systems folder.
c) Select Open; the Systems dialog box appears.
d) Select the Enable Load Preview check box. A check mark appears in the box. (Note that
the default is not checked.)
e) Click the Ok button.
3. Return to the Developer Studio tree.
6. Select Load. The Load Preview window appears listing the items to be loaded.
Figure 70: Load Preview window
96 OW351_60
4.10 Load function
7. Use the tabs at the bottom of the Load Preview window to view the various items that will be
loaded:
 New Objects -- shows new objects that have been added to the database but have not
yet been loaded to the target drop.
 Deleted Objects -- shows objects that have been deleted from the database but still exist
in the target drop.
 Modified Objects -- shows objects that have been changed in the database but not yet
modified in the target drop.
 New Received Points -- shows points that should be received by the target drop and
which do not already exist in the target as a received point.
 Deleted Received Points -- shows points that the target drop is currently receiving but
which should no longer be received.
8. To get more information on a loaded item, highlight an item in the list and right -click to display
a menu.
Figure 71: Load Preview right-click menu
9. Select one of the following items from the menu:

 Open item -- opens the item in a Developer Studio window so that it can be modified.
 Opens item in Control Sheet -- opens a viewable copy of the control sheet (a picture).
The sheet cannot be modified here. The Control Builder does not open.
10. If you are satisfied with the items to be loaded, press the Continue button on the Load
Preview window. The load starts.
Note: If there is any modification to anything in the drop to be loaded, you cannot simply press
the Continue button to Load. You must begin the Load procedure from the beginning (return to
Step 5).
11. To cancel the load, select the Abort Load button.
OW351_60 97
4.10 Load function
4.10.3 T o load e rror me ssages
If you attempt to load redundant Controllers incorrectly or if there is a condition with one of the
Controllers that will not allow a load to occur, a message dialog box appears. Typically, you
should correct the situation and then attempt to load the Controller again.
A message may occur for the following reasons:

 Loading the Partner (Backup) Controller first.
 Loading the Controller while a mismatch exists between the redundant Controllers.
 Loading a Controller that has failed.
 Loading a Controller that is offline.
Redundant drops
DR O P MO D E ER R O R ME S S AG E EX P L AN A TI O N DI AL O G B OX C H OI C ES
Offline (<DROP#>) is in <DROP You attempted to load a Select OK and then OK, the
Or MODE> and cannot b e redundant drop that is message closes, and the drop
Failed loaded at this time Offline, Failed, or in an does not load.
Or indeterminate state.
Select OK and then Details,
Undetermined
the message closes, and a
box opens with information
showing that the system
terminated the load operation.
Backup The Target's> partner You attempted to load a Select YES and the drop
Or <DROP#> is <DROP redundant drop that is in loads.
Standby MODE> backup or standby.
Select NO and then OK, the
Do you wish to proceed? message closes, and the drop
OR does not load.
The second message
WARNING: <Target#> is
does not display if the Select NO and then Details.
<DROP MODE>
partner drop is in control The message closes, and a
The target's partner and mismatched with box opens showing that you
<DROP#> is <DROP respect to the database terminated the load operation.
MODE> and <is or is not> and you selected YES
up-to-date with the on the first message.
Datab ase.
Do you wish to proceed?
Control The Target's partner You attempted to load a Select YES and the drop
<DROP#> is <DROP redundant drop that is in loads.
MODE> control.
Select NO and then OK. The
Do you wish to proceed? message closes, and the drop
does not load.
OR The second message
only occurs if the drops Select NO and then Details,
WARNING: Although are mismatched with the message closes, and a
<target#> is in CONTROL, it respect to each other box opens up showing that
is currently mismatched with and you selected YES you terminated the load
its partner
on the first message. operation.
The target's partner
<DROP#> is <DROP
MODE>
98 OW351_60
4.11 Download function
Non-redundant drops
DR O P MO D E ER R O R ME S S AG E EX P L AN A TI O N DI AL O G B OX C H OI C ES
Offline <DROP#> is <DROP You attempted to load a Select OK and then OK.
Or MODE> and cannot b e non-redundant drop that The message closes, and
Failed loaded at this time is Offline, Failed, or in the drop does not load.
Or an indeterminate state.
Select OK and then
Undetermined
Details. The message
closes and a box opens
with information showing
that the system terminated
the load operation.
Backup <DROP#> is in <DROP You attempted to load a Select YES and the drop
Or MODE> non-redundant drop that loads.
Standby is in Backup or Standby.
(The target is not Select NO and then OK.
configured to have a The message closes, and
partner) the drop does not load.
Do you wish to proceed? Select NO and then
Details. The message
closes and a box opens
showing that you
terminated the load
operation.
Control There is no message You attempted to load a There are no control issues
about the mode of the non-redundant drop that with non-redundant drops.
drop. is in Control.
Note: If communication to the Target Failed, or if the drop is powered down, you are presented
with a message box stating that the drop is unavailable. Select OK, then OK. The message
closes and the drop does not load. Select OK and then Details. The message closes and a box
opens with information showing that the system terminated the load, the drop was unavailable,
and that the system was unable to determine the drop mode for the selected target.
When changes are made to configuration diagrams, audio files, bitmap files, and/or Controller
software, you must download these changes to the appropriate drop(s) using the Download
function.
Note: The Download operation will not perform if the target has any consistency check errors.
OW351_60 99
4.11.1 T o download information

3. Right-click the drop where you wish to view the changes. (The right-click menu only displays
objects that are appropriate for that drop.)
4. Select Download from the pop-up menu, if the drop is redundant; the Download Wizard
appears.
Note: If the drop has no partner drop, the download begins and no further action needs to be
tak en.
Figure 72: Download Wizard
5. Select a drop (Primary or Secondary) to download.

6. Select Finish.
7. The Download Preview dialog box appears if the Bypass Download Preview is not enabled. If
Bypass Download Preview is enabled (see page 102), you will not get the Download Preview
window.
100 OW351_60
The Download Preview dialog box lists any items that may have been altered during
configuration. You can select the files you would like to include in the download process by
placing a check in the box next to the file.
Figure 73: Download Preview window
Download Preview window items
I TE M DE S C R I P TI O N
Select All/ load All Use the check box to the left of Query Results to select all or load all.
Download When checked, the download action downloads all of the selected previewed
files after you select the Ok button.
Reboot When checked, the reboot action shuts down and then restarts the drop after
you select the Ok button and the download action has completed.
Abort Aborts the download process and returns to the Developer Studi o without
executing any commands.
Ok Executes the settings and closes the window.
Skip to Next Drop Advances to the next drop for file preview. (The current drop is not
downloaded.)
8. If the information in the Download Preview dialog is acceptable, select the Download check
box (if it is deselected).
9. Select the Ok button, which downloads the changes. When both Download and Reboot are
selected, the drop downloads the changes and the machine restarts.
OW351_60 101
4.11.2 T o bypass a download pre view
You can choose to perform the download operation without getting a preview window of the items
that will be downloaded.
Use the following procedure to enable and use the Bypass download preview function:

2. Ensure that the Bypass Download Preview function is enabled. To do this:
a) Use the system tree (in the Hardware view bar) to navigate to the Systems folder.
b) Right-click on the Systems folder.
c) Select Open; the Systems dialog box appears.
d) Select the Bypass Download Preview check box. A check mark appears in the box.
(Note that the default is not checked, which means the window will appear.)
e) Click the Ok button.
3. Return to the Developer Studio tree.
6. Select Download. The Download process begins without a preview window appearing.
4.11.3 Downloading configuration changes to multiple drops
It is possible to download configuration changes to multiple drops. Configuration changes can be

downloaded to multiple drops at the Systems, Networks, or Units folder level in the Developer
Studio system tree.
 A download at the Systems folder level allows you to select and download any of the drops
under the system.
 A download at the Networks folder level allows you to select and download all of the drops
under the network.
 A download at the Units folder level allows you to select and download all of the drops under
the unit.
Note: The Download drop list is based on the object type being downloaded. The drop list
contains all drops for the specific level when the download is performed on the Unit, Network , or
System object. However if the download is performed on a specific configuration object, the
drop list is built based on the drop types that the object applies to. For example, when a
download is performed on graphics at the Unit level or above, Controller drops will not be
contained in the list of drops to download.
To download configuration changes to multiple Drops

2. Use the system tree to navigate to the Systems, Networks, or Units folder.
3. Right-click the appropriate folder (Systems, Networks, or Units).
102 OW351_60
4. Select Download from the right-click menu. A Drop Preview dialog box appears (similar to
the dialog box in To Download information (see page 99), but without the options.) A Drop
Preview window only appears if you did not choose to Bypass a download preview (see page
102).
Note: The Drop Preview dialog box contains a list of drops that fall under the selected level in
the hierarchy. For example, if you choose to download from the Systems folder level, all drops in
the system appear in the Drop Preview dialog box. If you choose to download from the Units
folder level, all drops under that unit appear in the Drop Preview dialog box.
Figure 74: Download Preview window with Drop Preview
5. Select the Drops you would like to download, using one of the following methods:
 Place a check in the box next to the individual drop number(s).
 Select all drops by placing a check in the box next to the Drops folder.
 Deselect all drops by removing the check in the box next to the Drops folder.
6. Select Ok to download these drops. You may abort the download by choosing the Abort
button in the Drop Preview dialog box.
7. If the information in the Download Preview dialog is acceptable, select the Ok button.
Downloading is now complete.
Note: Use the Reboot function (Reboot function (see page 113)) for the configuration changes
to tak e effect. No Reboot is necessary if only graphics are downloaded.
Note: Process diagram downloads can also be done by right click ing on the Diagram folder at
any level in the Developer Studio system tree and selecting Download. The changed process
diagrams download to multiple drops. Changed process diagrams must be downloaded in order
to be viewed in the Process Diagrams System. (Refer to the Ovation Operator Station User
Guide.)
OW351_60 103
4.12 Reconcile function
The Reconcile function enables you to compare the database contents of Ovation points with
drop contents in order to capture changes made in the online system. Examples of items that can
be reconciled include tuned algorithms and modified alarm limits.
Reconcile is a two-step process. Changes are reconciled from the Controller to the database and
then from the database to the Control Builder. For more information on the Reconcile function,
refer to the Ovation Control Builder User Guide.
4.12.1 Re conciled fie lds for Analog and De luxe Analog fie lds
Reconciled fields for Analog and Deluxe Analog fields
A N AL O G P O I N TS DE L U X E AN AL O G P O I N TS DE L U X E AN AL O G P O I N TS
1V Conversion Coefficient #1 1V Conversion Coefficient #1 6S Low Alarm Limit #1-Plant 3

5V Conversion Coefficient #5 5V Conversion Coefficient #5 5S High Alarm Inc. Limit-Plant
3
6V Conversion Coefficient #6 6V Conversion Coefficient #6 0S Low Alarm Inc. Limit-Plant
3
7V Conversion Coefficient #7 7V Conversion Coefficient #7 1Y High Alarm Limit #1-Plant 4
8V Conversion Coefficient #8 8V Conversion Coefficient #8 2T High Alarm Limit #2-Plant 4
HL High Alarm Limit #1 UH High User Defined Alarm 3T High Alarm Limit #3-Plant 4
Limit
ZH High Alarm Limit #2 UL Low User Defined Alarm 4T High Alarm Limit #4-Plant 4
Limit
3Y High Alarm Limit #3 1Q High Alarm Limit #1-Plant 6T Low Alarm Limit #1-Plant 4
1
4Y High Alarm Limit #4 2Q High Alarm Limit #2-Plant 7T Low Alarm Limit #2-Plant 4
1
UH High User Defined Alarm 3Q High Alarm Limit #3-Plant 8T Low Alarm Limit #3-Plant 4
Limit 1
LL Low Alarm Limit #1 4Q High Alarm Limit #4-Plant 9T Low Alarm Limit #4-Plant 4
1
ZL Low Alarm Limit #2 6Q Low Alarm Limit #1-Plant 1 5T High Alarm Inc. Limit-Plant
4
3Z Low Alarm Limit #3 7Q Low Alarm Limit #2-Plant 1 0T Low Alarm Inc. Limit-Plant
4
4Z Low Alarm Limit #4 8Q Low Alarm Limit #3-Plant 1 1U High Alarm Limit #1-Plant 5
UL Low User Defined Alarm 9Q Low Alarm Limit #4-Plant 1 2U High Alarm Limit #2-Plant 5
Limit
ZI High Alarm Incremental 5Q High Alarm Inc. Limit-Plant 3U High Alarm Limit #3-Plant 5
Limit 1
104 OW351_60
ZM Low Alarm Incremental 0Q Low Alarm Inc. Limit-Plant 4U High Alarm Limit #4-Plant 5
Limit Mode 1
DB High Alarm Deadband DB High Alarm Deadband 6U Low Alarm Limit #1-Plant 5
DJ Low Alarm Deadband DJ Low Alarm Deadband 7U Low Alarm Limit #2-Plant 5
EL Engineering Low Limit 1R High Alarm Limit #1-Plant 8U Low Alarm Limit #3-Plant 5
2
EH Engineering High Limit 2R High Alarm Limit #2-Plant 9U Low Alarm Limit #4-Plant 5
2
RW Reasonability Low Limit 3R High Alarm Limit #3-Plant 5U High Alarm Inc. Limit-Plant
2 5
RV Reasonability High Limit 4R High Alarm Limit #4-Plant 0U Low Alarm Inc. Limit-Plant
2 5
6R Low Alarm Limit #1-Plant 2 1X High Alarm Limit #1-Plant 6
5R High Alarm Inc. Limit-Plant 6X Low Alarm Limit #1-Plant 6
2
0R Low Alarm Inc. Limit-Plant 7X Low Alarm Limit #2-Plant 6
2
1S High Alarm Limit #1-Plant 8X Low Alarm Limit #3-Plant 6
3
2S High Alarm Limit #2-Plant 9X Low Alarm Limit #4-Plant 6
3
3P High Alarm Limit #3-Plant 5X High Alarm Inc. Limit-Plant
3 6
4S High Alarm Limit #4-Plant 0X Low Alarm Inc. Limit-Plant
3 6
EL Engineering Low Limit RW Reasonability Low Limit
EH Engineering High Limit RV Reasonability High Limit
Note: Refer to the Ovation Record Types Reference Manual for more information about these
reconciled fields.
OW351_60 105
4.13 Coefficient calculation
The coefficient calculation function automatically calculates coefficients for analog hardware input
points assigned to the following types of modules. All coefficients are accessible for user
adjustment, if required.
RTD input
Select the type of RTD and desired span on the Instrument tab of an analog point edit dialog. A
typical coefficient generates and creates a six-point curve of ohms verses temperature and a 5th
order polynomial to configure the input.
Thermocouple input
Select the type of thermocouple and whether it is in degrees F or C. The values of the eight
conversion coefficients are inserted into the dialog box. In addition, the thermocouple links to the
associated cold junction IC by default.
Standard analog input
Set the instrument span on the Instrument tab of an analog point edit dialog box, and the interface
calculates all coefficients.
Note: For the Ovation 3.5.0 (or later) release, you do not have to specify the high/low operating
and high/low transmitter ranges for thermocouple inputs (applicable conversion type is fifth
order) since they are not utilized in the generation of the conversion coefficient values by the
Coefficient Calculation operation.
106 OW351_60
4.13.1 T o run a Coe fficient Calculation

2. Use the system tree (in the Hardware view bar) to navigate to the Systems, Networks,
Units, or Drops folder:
3. Right-click on the appropriate Drop folder.
4. Select Coefficient Calculation from the right-click pop-up menu.
Note: The right-click menu only displays items that are appropriate for that drop.
5. The software performs the requested function and displays a list of any points that it could not
calculate at the top of the dialog box.
Figure 75: List of points that could not be calculated
OW351_60 107
6. Left-click on an item, a Point configuration window opens.
Figure 76: Point configuration window
7. Go to the Instrumentation tab on the Drop configuration window, find, and fix the missing
information indicated in the Reason box of the Coefficient Calc dialog box (shown in Step 5).
Note: For the Ovation 3.5.0 (or later) release, you do not have to specify the high/low operating
and high/low transmitter ranges for thermocouple inputs (applicable conversion type is fifth
order) since they are not utilized in the generation of the conversion coefficient values by the
Coefficient Calculation operation.
108 OW351_60
8. Select Apply or Ok. Points that have sufficient information to perform the calculation have
their conversion coefficient fields compared (actual versus calculated.) The differences are
shown in the lower half of the dialog.
Figure 77: Calculation differences
9. If you wish to revert from the current values to the calculated values, you must highlight the
desired fields (or point item to take all values.)
10. Select Apply or Ok.
OW351_60 109
4.14 Clear function
4.14 Clear function
The Clear function is used to remove all of the application information data, such as Ovation point
and control data, from an Ovation drop. The Clear function is performed at the Drops folder level.
Upon completion of the Clear process, the drop automatically reboots.
4.14.1 T o cle ar application information

4. Select Clear.
5. If the Drop is non-redundant, go to Step 7.
6. If the drop is redundant, the Select a drop to clear dialog box appears (similar to Download
function (see page 99)).
 Select the appropriate target drop.
 Select Finish.
7. A confirmation dialog box appears, select Yes.
After the action is complete, the system automatically reboots and the application information
is cleared from the drop.
For specific information regarding loading application information to a Controller drop, refer to the
applicable Ovation Controller User Guide.
110 OW351_60
4.14 Clear function
4.14.2 Cle ar e rror me ssage s
If you attempt to clear redundant Controllers incorrectly, or if there is a condition with one of the
Controllers that will not allow a clear to occur, a message dialog box appears. Typically, you
should correct the situation and then attempt to clear the Controller again.
The following tables outline the possible messages you might encounter when performing a Clear
to either redundant or non-redundant drops.
Non-redundant drops
DR O P MO D E M E S S AG E EX P L AN A TI O N CH O I C E S
<DROP#> is Offline You attempted to Select OK and then OK. The

Offline
and cannot b e cleared clear a non- message closes, and the drop does
at this time redundant Drop not clear.
that is offline.
Select OK and then Details. The
message closes and a box opens
showing that the system terminated
the clear operation.
<DROP#> is <Drop You attempted to Select YES and the drop clears and
Failed
Mode> clear a non- then reboots.
or redundant Drop
Undetermined (Note: Depending on Select NO and then OK. The
that is in an
the internal s tatus of Indeterminate or message closes, and the drop does
the drop, a reboot may not clear.
Failed state.
be required before a
Select NO and then Details. The
clear operation can be
successfully executed.)
showing that you terminated the clear
Do you wish to operation.
proceed?
<DROP#> is <Drop You attempted to Select YES and the drop clears and
Backup
Mode> clear a non- then reboots.
or redundant Drop
Standby Clearing will reb oot the Select NO and then OK. The
that is in Backup
drop. message closes, and the drop does
or Standby.
not clear.
Do you wish to
proceed? Select NO and then Details. The
showing that you terminated the clear
operation.
WARNING: Non- You attempted to Select YES and the drop clears and
Control
Redundant <DROP#> clear a non- then reboots.
is in CONTROL redundant Drop
Select NO and then OK. The
that is in Control.
Clearing will reb oot the message closes, and the drop does
drop: NO DROP WILL not clear.
ASSUME CONTROL.
Do you wish to message closes and a box opens
proceed? showing that you terminated the clear
operation.
OW351_60 111
4.14 Clear function
Redundant drops
DR O P MO D E M E S S AG E EX P L AN A TI O N CH O I C E S
<DROP#> is Offline and You attempted to Select OK and then OK. The
Offline
cannot b e cleared at this clear a redundant message closes, and the drop does
time Drop that is offline. not clear.
Select OK and then Details. The
showing that the system terminated
the clear operation.
<DROP#> is in a <DROP You attempted to Select YES and the drop clears and
Failed
MODE> clear a redundant then reboots.
or Drop that is in an
Undetermined (Note: Depending on the Select NO and then OK. The
Indeterminate or
internal status of the message closes, and the drop does
Failed state.
drop, a reboot may be not clear.
required before a clear
operation can be
successfully executed.) message closes and a box opens
showing that you terminated the
Do you wish to proceed? clear operation.
<DROP#> is in <DROP You attempted to Select YES and the drop clears and
Backup or
MODE> clear a redundant then reboots.
Standby Drop that is in
Clearing will reb oot the Select NO and then OK. The
Backup or Standby.
drop. message closes, and the drop does
not clear.
showing that you term inated the
clear operation.
<DROP#> is in Control You attempted to Select YES and the drop clears and
Control
clear a redundant then reboots.
The target's partner
Drop that is in
(<Drop#>) is in backup, Select NO and then OK. The
control and its
but NOT up to date with message closes, and the drop does
partner is in
the database. backup. not clear.
OR Select NO and then Details. The
Note: This message closes and a box opens
The target's partner message only showing that you terminated the
(<Drop#>) is in backup, occurs if the clear operation.
and up to date with the redundant partner
database. is in b ackup;
Clearing will reboot the otherwise, the
drop and cause failover. message reflects
the non-redundant
Do you wish to proceed? drop clear error
message.
Note: If communication to the target failed, or if the drop is powered down, you are presented
with a message box stating that the drop is unavailable. Select OK, then OK. The message
closes and the drop does not clear. Select OK and then Details. The message closes and a box
opens with information showing that the system terminated the clear, the drop was unavailable,
and that the system was unable to determine the drop mode for the selected target.
112 OW351_60
4.15 Reboot function
4.15 Reboot function
In most cases, the Reboot command should be executed immediately following the completion of
any Download command involving configuration changes. Even though this may not always be
necessary, it is a safe and recommended practice to reboot a drop after it has been downloaded.
4.15.1 T o Re boot
3. Right-click on the Drop item you want to reboot.
4. Select Reboot from the right-click menu. The right-click menu only displays items that are
appropriate for that drop.
Note: You can also reboot the drop by check ing Reboot in the Download Preview dialog box as
described in Download function (see page 99).
5. For non-redundant drop configurations, a confirmation window appears. Select Yes to close
the window and reboot the machine.
Figure 78: Reboot confirmation
6. For redundant drop configurations, the Select a drop to reboot dialog box appears (similar to
Download function (see page 99)).
 Select the drop to reboot.
 Select Ok.
 A confirmation window appears.
 Select Yes to close the window and reboot the machine.
OW351_60 113
4.16 Update Security Infrastructure function
The Update Security Infrastructure function provides the mechanism to reconcile differences
between the network and computer names stored in the Ovation domain Cont roller and the
Ovation database.
A domain may contain multiple Ovation networks, so in order to distinguish between all the drops
in a system, several naming rules are enforced in an Ovation system:
 Drop names (for example, drop230) must be unique within a Network. You assign Drop
names or drop numbers when you insert a new drop into the Developer Studio hierarchy. This
name is stored in the Ovation database.
 Computer names (for example, BoilerRoomdrop230) must be unique within a domain. You
assign computer names when the system security administrator creates a new computer
account. This name is stored in the security database. (Refer to the Managing Security for
Ovation manual.)
 Network alias names should be unique within a domain. You assign Network alias names (for
example, Net8) when you insert a new network into the Developer Studio hierarchy. This
name is stored in the Ovation database and the Security database.
Under some circumstances (for example, importing an external database into an existing Ovati on
system), this security infrastructure may become out-of-date and will not be able to provide
security services. In this case, you can use the Update Security Infrastructure Wizard (see page
114) to update the security infrastructure.
The Update Security Infrastructure program is run on the Database Server. Use the Update
function when you import a Network into a domain that is engineered at another site. The Update
function provides a wizard that reconciles the mappings of drop names, computer names, and
network alias names between the Ovation Database Server and the Security Manager Server.
The Update can also be used at any time to reconcile the two databases.
The wizard provides the following services:

 Queries the Ovation system and collects the network and drop information.
 Determines whether the security infrastructure is up-to-date with the Ovation system.
 If necessary, updates the security infrastructure.
 Provides the appropriate dialog box to continue the reconciliation process.
The wizard performs many time saving tasks in the background and automatically makes
decisions as to what information is needed to continue the Update function. In order to access
and use the Update Security Infrastructure Wizard, you must first be on a Database Server. See
To use the Update Security Infrastructure function (see page 114).
114 OW351_60
4.16.1 T o use the Update Se curity Infrastructure Wizard

2. Use the system tree (in the Hardware view bar) to navigate to the Networks folder:
Systems -> Networks
3. Right-click on the appropriate Networks folder.
4. Select Update Security Infrastructure and the Security Infrastructure Update Wizard start
page appears:
Figure 79: Security Infrastructure Update Wizard
5. In the Update Security Infrastructure Wizard start page, select Next.

6. The program checks to see if a network alias name exists in the Ovation database, then
displays the appropriate dialog box with additional instructions.
 If the Specify a network alias name (see page 116) dialog box appears, no network alias
name was found in the Ovation database.
 If the Specify the type of update to perform (see page 117) dialog box appears, the
network alias exists in the Ovation database, and it matches an existing network alias.
 If the Select the type of update to perform (see page 119) dialog box appears, the
network alias exists in the Ovation database, but was not found in the security database.
The program assigned an alias, then gathered the drop information and due to errors is
not ready to reconcile all of the drop information between the two databases.
 If the Review and confirm the options you selected (see page 120) dialog box appears,
the network alias exists in the Ovation database, but was not found in the security
database. The program assigned an alias, then gathered the drop information and is
ready to reconcile the drop information between the two databases.
OW351_60 115
4.16.2 T o spe cify a Ne twork Alias name

1. If no network alias name was found in the Ovation database, the Specify a network alias
name screen appears:
Figure 80: Network Alias Update (Specify network alias name)
2. In the Network Alias Name entry field, enter an alias name. Select Next, and the appropriate
dialog box appears:
 If the Specify the type of update to perform (see page 117) dialog box appears, the
network alias name entered in the Ovation database matches an existing security network
alias.
 If the Review and confirm the options you selected (see page 120) dialog box appears,
the network alias exists in the Ovation database, but was not found in the security
database. The program assigned an alias, then gathered the drop information and is
ready to reconcile the drop information between the two databases.
 If the Select the type of update to perform (see page 119) dialog box appears, the
network alias name entered in the Ovation database was not found in the security
database. The program assigned an alias, then gathered the drop information and due to
errors is not ready to reconcile all of the drop information between the two databases.
116 OW351_60
4.16.3 T o spe cify the type of update to pe rform

1. If the network alias exists in the Ovation database, and it matches an existing network alias,
the Specify the type of update to perform screen appears:
Figure 81: Network Alias Update (Specify type of update to perform)
2. In the Specify the type of update to perform dialog box, make the appropriate selection and
the appropriate dialog box appears:
 Select Yes to accept the network alias already provided in the Security database. Use
this option only if you are sure that the network alias is not used by any other Ovation
database in the domain.
 If you select Yes, and the Select the type of update to perform (see page 119) dialog
box appears, the system gathered the drop information and due to errors is not ready
to reconcile all of the drop information between the two databases.
 If you select Yes, and the Review and confirm the options you selected (see page
120) dialog box appears, the network alias exists in the Ovation database, but was
not found in the security database. The program assigned an alias, then gathered the
drop information, and is ready to reconcile the drop information between the two
databases.
 Select No if you are not sure that the database is used by any other Ovation database in
the domain, or if you want to assign a different network alias to the Ovation database.
 If you select No, the Specify a new network alias name (see page 118) dialog box
appears.
OW351_60 117
4.16.4 T o spe cify a ne w Ne twork Alias name

1. If you selected No on the Specify the type of update to perform (see page 117) screen, the
Specify a new network alias name screen appears:
Figure 82: Network Alias Update (Specify a new network alias name)
2. Enter the New Network Alias Name in the entry field, and select Next.
The program will reverify the databases. See the bulleted items under Step 1 of Specify a
network alias name (see page 116) to see what screen may appear next.
118 OW351_60
4.16.5 T o se le ct the type of update to pe rform

1. If the network alias name entered in the Ovation database was not found in the security
database, the Select the type of update to perform screen appears:
Figure 83: Drop Update (Select the type of update to perform)
2. Make the appropriate selection and the appropriate dialog box appears:
 If you select Yes, the errors are ignored and the Review and confirm the options you
selected (see page 120) window appears.
 If you select No, the drops are not reconciled and the final Security infrastructure has not
been fully updated wizard appears (see To exit a successful or unsuccessful Security
Infrastructure Update wizard (see page 121)).
OW351_60 119
4.16.6 T o re v iew and confirm the options you se le cted

1. If the network alias exists in the Ovation database, but was not found in the security
database, the Review and confirm the options you selected screen appears:
Figure 84: Summary (Review and confirm the options you selected)
2. Make the appropriate selection and the appropriate dialog box appears:
 If you want to change an option, select Back to take you to the previous step, which is
either Select the type of update to perform (see page 117) or Specify the type of update to
perform (see page 117).
 Once you are satisfied with your review, select Next and the "successfully updated"
window appears (see To exit a successful or unsuccessful Security Infrastructure Update
wizard (see page 121)).
120 OW351_60
4.16.7 T o e xit a succe ssful or unsuccessful Se curity Infrastructure Update wizard
When the last screen of the Security Infrastructure Update Wizard, it can appear as unsuccessful
or successful.
1. If the update has not been fully updated, the screen will appear as shown in the following
figure:
Figure 85: Security Infrastructure Update wizard (update interrupted)
 Select the Finish button to exit the program. Run the Update Security Infrastructure (see
page 114) again, fixing any problems, to try for a successful update.
OW351_60 121
2. If the update is successful, the screen will appear as shown in the following figure:
Figure 86: Security Infrastructure Update wizard (update successful)
 Select Finish to complete the update. You have successfully completed an Update
Security Infrastructure and the program exits.
122 OW351_60
4.17 Baseline Creation function
4.17 Baseline Creation function
The Baseline Creation/Comparison function provides the ability to view changes made to the
Ovation database over time. You can create and store a snapshot (that is, Baseline) of the
Ovation database and later compare it with other stored baselines or with the current contents of
the database.
You can compare any baseline with the current contents of the database itself.
The comparison of two saved baselines must be between any two baselines created with the
same context. For example, two baselines taken at the Ovation System object can be compared,
but a baseline taken at the Ovation System object cannot be compared with a baseline taken at
the Ovation Network object.
Note: The comparison functionality is intended for informational use only. The results presented
should not be used as a shortcut to bypasses sound engineering practices such as thorough
testing and validation of configuration data and Ovation control logic.
The functionality of the Baseline Creation/Comparison includes:
 Creating a baseline image via the Developer Studio at various nodes in the Ovation hierarchy
(for example, System, Network, Unit, and Drop).
 The objects and attributes stored in the Ovation database itself as well as the appropriate
Ovation control sheets.
 The captured Ovation database images include:
 Creation time/date.
 User-specified description field.
 Baseline context (that is, the Ovation database hierarchy node where the baseline was
created).
 Who created the baseline.
 The machine where the baseline creation operation was initiated.
 Viewing the differences between any two baselines of the same context or between a
baseline and the current contents of the Ovation database.
 The Deletion of baselines that are no longer needed.
The specific set of data collected will be based on the context in which the Baseline was created.
(For example, network configuration data would not be included if a Baseline were performed on
an Ovation Controller.)
Note: An Ovation binary export (that is, an Oracle binary export performed through the Ovation
Back up/Restore utility) includes all Baselines currently existing in the database. These
Baselines will be included if the Ovation binary export is restored through the
do_ptadmin_import.bat file.
OW351_60 123
4.18 Baseline Comparison function
4.17.1 T o Cre ate a Base line

2. Use the system tree to navigate to the desired folder (Systems, Networks, Units, or Drops).
3. Right-click the appropriate folder.
OR
Access the Operations menu.
4. Select Create Baseline. The Create Baseline window appears:
Figure 87: Create Baseline window
5. Type the description for the Baseline in the Description field.

6. Select OK; a baseline will be created.
Note: See Baseline Comparison (see page 124) to perform a baseline comparison.
Baseline Comparison permits the comparison of any two baselines created with the same
context. You have the option of ignoring Ovation control sheets during the comparison operation.
The operation can be performed through the Operation menu or through the right -click menu on
the Ovation hierarchy itself. You can select specific context for comparison purposes. These are
shown on a list of baselines appropriate to the specific context from which you will select two for
comparison. The current contents of the database can also be selected as the second item to be
compared.
The comparison results will show the following:
1. Objects existing in the second baseline (or database), but do not exist in the first baseline
(that is, objects which have been added).
 If a whole sub-tree of objects has been created, the comparison results will show the root
of the new sub-tree. (For example, if an Ovation drop and all of its user-defined points
have been added to the database after a Baseline has been taken, the comparison
results will simply show that the Ovation drop has been added.)
124 OW351_60
2. Objects not existing in the second baseline (or database), but ex ist in the first baseline (that
is, object which have been deleted).
 If a whole sub-tree of objects has been deleted, the comparison results will show the root
of the deleted sub-tree. (For example, if an Ovation drop and all of its points and control
sheets have been removed from the database after a Baseline has been taken, the
comparison results will simply show that the Ovation drop has been deleted.)
3. Objects that have been modified (as well as the specific attributes that are different).
4. You can select from a list specific default point differences as well as read-only views of the
control sheets themselves.
Note: The Ovation database will not be lock ed during a Baseline comparison operation.
Modifications or the addition/deletion of objects while a comparison between a baseline and the
current contents of the database is tak ing place may produce indeterminate results (that is,
modifications may or may not be included in the comparison results, depending on when the
changes were made relative to the Baseline creation progress).
The comparison results window provides “Save as” functionality to save the comparison report in
an electronic format that can be viewed later with standard browser applications such as Windows
Explorer.
4.18.1 T o run a Base line Comparison

OR
Pull down the Operations menu.
4. Select Baseline Compare; a Compare to Baseline dialog similar to the one shown in the
following figure will appear. Flagged drops will only show "(Current Baseline)."
Figure 88: Compare to Baseline window
5. Select the check boxes next to the baselines to be compared.

6. Select Compare; if there are any differences, a list of differences will appear.
OW351_60 125
4.19 What is the Print Screen utility?
4.18.2 T o de le te a Base line Comparison e ntry

OR
Access the Operations menu.
4. Select Baseline Compare; the Compare to Baseline window appears:
Figure 89: Compare to Baseline window
5. Select the baseline or baselines (can select two at a time) to be deleted.

6. Select Remove.
4.19 What is the Print Screen utility?
The Print Screen utility allows you to print a copy of the current computer screen without using a
keyboard.
The Print Screen utility captures what is displayed on the computer screen(s) and sends that
image to an installed printer. By default, the printer is set to use landscape mode to print the
screen.
The application can be invoked from the Start menu, from a shortcut on the desktop, or from the
Windows taskbar.
To use the Print Screen utility, click the Start menu -> All Programs -> Ovation -> Ovation
Utilities -> Print Screen Utility. When accessed, the print occurs. There is no user interface for
this utility.
126 OW351_60
SECTION 5
5 Working with special Developer Studio functions
IN THIS SECTION
Setting the Online/Offline mode ............................................................................... 127

Defining Ancillary labels .......................................................................................... 129
DDB Configuration (Net work s folder)........................................................................ 130
Net work Time Protocol (NTP) (Net work s folder) ........................................................ 132
Plant Mode (Units folder)......................................................................................... 135
Point Processing (All folders) ................................................................................... 136
SNMP (Drops) ........................................................................................................ 138
5.1 Setting the Online/Of f line mode
Setting the Online/Offline Mode function permits engineering changes in an Offline Mode of
operation. This may be useful when testing a change that you do not want to take effect
immediately in the online (operational) system. The Offline Mode permits the changes of an
Ovation point’s originator or broadcast frequency and the movement of a control sheet between
control areas under certain conditions, and enforces the clear/load sequence for affected Ovation
drops.
Offline mode is enabled through the check box attribute on the System folder. This attribute is
labeled Offline Mode and has an import/export reference of OFFLINE_MODE. By default, this
attribute is not enabled (that is, by default, operation of the Ovation Engineering Tools restricts
you from making changes, which disrupt the system).
5.1.1 Enable d Offline mode attributes
Enabling the Offline Mode attribute causes the following to occur:
1. A dynamic status entry is created in the Ovation database that identifies the system as being
in Offline mode. This causes the red flag to show next to the Syst em folder in the Developer
Studio.
2. A message is logged in the Ovation Error Log (on the Ovation Database Server) indicating
that the system has been placed into Offline mode.
3. The moving of Ovation points (with restrictions), the moving of a control sheet between
control areas of the same Ovation Controller, and the changing of an Ovation point’s
broadcast frequency are enabled.
OW351_60 127
5.1 Setting the Online/Offline mode
5.1.2 Enabling Offline M ode through Import Operations
Offline Mode can be enabled and disabled through an Ovation Engineering Tools import
operation with the same effects as if it were performed through the Developer Studio.
Note: An import operation can be used to change the broadcast frequency of an Ovation point
with the same effects as if done through the Developer Studio. However, an import operation is
not appropriate to move Ovation points or control sheets.
5.1.3 Ope rations pe rmitted in Offline mode
The following operations are permitted in Offline mode, subject to various conditions:
 Moving control sheets from one control task to another. Control sheets can only be moved
within an Ovation Controller.
 Moving Ovation points from one Ovation drop to another. Points can only be moved if both of
the following are true:
 The Ovation point has no bound local reference that is not able to follow the point to
another Ovation drop. Typically, such bound local references are hardware-related. To
move an Ovation point that is bound to local hardware, it must first be removed from the
hardware (that is, it must be a non-I/O point.)
 The point must not be driven/originated by a control sheet.
Note: Non-local references are permitted to remain. For example, an Ovation point referenced
by another point as an Alarm Cutout field or in various Alarm Limit fields can still be moved
without removing the references.
 Changing the broadcast frequency of a point (there are no restrictions.)
In general, execution of the above operations causes any affected Ovation drop to be set to the
Reload Required state (that is, the drop must be cleared before it is loaded.)
 Moving a control sheet causes only the Ovation drop owning the control sheet to be set to the
Reload Required state.
 Moving an Ovation point causes the previous originating Ovation drop to be set to the Reload
Required state, as well as any other Ovation drop explicitly receiving that point (for any
reason.) The Ovation drop that the point is moved to is set to the Load Required state unless
it was also explicitly receiving the point (it also sets to the Reload Required state.)
 Changing the broadcast frequency of a point causes the originating Ovation drop to be set to
the Reload Required state, as well as any other drop explicitly receiving that point (for any
reason.)
5.1.4 Disable d Offline mode attributes
Disabling the Offline Mode attribute causes the following to occur:
1. The dynamic status entry for the Systems folder is removed from the Ovation database. This
causes the red flag to disappear from the Systems folder in the Developer Studio.
2. A message is logged in the Ovation Error Log (on the Ovation Database Server) indicating
that the system is no longer in Offline mode.
3. The changing of an Ovation point’s broadcast frequency and the moving of Ovation points
and control sheets are all disabled.
128 OW351_60
5.2 Defining Ancillary labels
5.2 Defining Ancillary labels
The Ancillary folder allows you to define the labels associated with the ancillary fields of Ovation
point records. The text-based ancillary information is not required, but it is provided to add project -
specific information to Ovation point records. This user-defined ancillary information is stored in
the Ovation database but does not affect the operation of the point.
Each point type can have up to 100 different ancillary labels (fields). Each field takes a maximum
of 30 characters.
For example, suppose you want to specify for a drop point, information on the drop cabinet name,
department where the drop resides, and additional hardware attached to the drop. This
information has no bearing on the operation of the point, but it may be necessary or helpful for
administrative purposes. You could create three ancillary labels (one for drop cabinet name, one
for the drop's department, and one for additional hardware). Then, when you create a drop point,
those three labels will be available in the Ancillary tab on the Point dialog box.
5.2.1 T o cre ate Ancillary labe ls
Note: For example purposes, the following procedures discuss creating ancillary labels for an
algorithm point. However, these procedures are applicable for all point types.

2. Use the system tree (in the Hardware view bar) to navigate to the Ancillary folder:
Systems -> Ancillary item
3. Open the Ancillary folder.
4. Select a Point Labels item from the WorkPad window. The applicable Points Labels dialog
box appears.
5. Type in the title to be used as the Ancillary data label for the item. For exampl e, Drop
Cabinet Name in the Value Column in row Field 1 Label (maximum length of 30 characters in
each Value field.)
Figure 90: Example of a Points Labels dialog box
6. Type additional information in the successive fields as needed.

7. When finished, select Apply or OK. When a point is created, the labels that have been
defined in the Points Labels dialog box will appear on the Ancillary tab of the Point dialog box
(see page 187). Only fields with information will appear.
OW351_60 129
5.3 DDB Configuration (Networks folder)
5.2.2 T o modify Ancillary labe ls

2. Use the system tree (in the Hardware view bar) to navigate to the Ancillary Labels folder:
Systems -> Ancillary -> Ancillary Labels
3. Right-click on Ancillary Labels. The WorkPad window at the bottom of the Developer Studio
populates with the point labels that have been created.
4. Right-click on the Ancillary <point_type> Label item to be updated.
5. Select Open. The applicable Ancillary dialog box appears.
6. Make the necessary changes and select Ok/Apply.
The dynamic portion of a point record is broadcast periodically on the Ovation Network by the
originating drop. Both the originating and receiving drops store dynamic data in volatile memory.
Dynamic data is broadcast on the Ovation Network in Dynamic Data Blocks or DDBs. DDB size is
configured through the DDB Configuration folder.
The DDB configuration item is established when the Network is created. Only one DDB
configuration exists per Network.
The number of DDBs can be increased at any time, but the maximum DDB size should not be
changed unless the system is going to be rebuilt. If the maximum DDB size needs to be
decreased (for example, due to a change in the Network implementation), a full import load of the
system is required.
Note: Only configure DDB information through the Developer Studio. Changing DDB values
through the Control Panel may mak e the system unusable.
130 OW351_60
5.3.1 T o modify the ne twork DDB configuration

2. Use the system tree to navigate to the DDB Configuration folder:
Systems -> Networks -> Configuration -> DDB Configuration
3. Open the DDB Configuration folder.
4. Right-click on the DDB item in the WorkPad window.
5. Select Open. The DDB Configuration dialog box appears. The following figure and table
describe the fields of the DDB Configuration dialog box.
Figure 91: DDB Configuration window
DDB Configuration window fields
Maximum DDB Size 1400 bytes for Ethernet, must be defined before points are added to the
database. For the Ovation 3.5.0 (or later) release, the only support choice is
1400 Bytes (Ethernet).
Maximum Number of Maximum number of DDBs that can be defined for the system. The valid
DDBs range is 100 to 3072 and cannot be reduced after points have been added
to the database.
Number of Small DDBs Quantity of DDBs assigned to drop records (for informational purposes
only.)
Small DDB Size Size of the small DDBs assigned to drop records (for informational purposes
only.)
Fast Period Periodicity of a fast point, measured in milliseconds (for informational
purposes only.)
DDB Ratio Ratio of slow to fast DDBs (for informational purposes only.)
Age Fast Age where a fast point is considered to be timed out, measured in tenths of
a second (for informational purposes only.)
OW351_60 131
5.4 Network Time Protocol (NTP) (Networks folder)
Age Slow Age where a slow point is considered to be timed out, measured in tenths of
a second (for informational purposes only.)
Age Drop Status Age where a DU record is considered to be timed out, measured in tenths of
a second.
DDB Multicast address Internal Ovation network control (for informational purposes only.)
6. Select the Maximum DDB Size using the drop-down menu.

7. Select the Maximum Number of DDBs using the spin control button.
8. Select Ok/Apply to add the DDB configuration to the database.
Note: The changes do not tak e effect until downloaded (see page 99) and the drop is rebooted
(see page 113). You should download and reboot all the drops in the system to ensure the DDB
change is valid throughout the system.
Network Time Protocol (NTP) identifies the drop or external server that is providing the time base
for the Ovation system. NTP is automatically created when a Network is inserted.
You can use the following options as the NTP or time server:
 External server (GPS clock) (see page 132).
 Ovation Domain Controller (see page 134).
 Non-Ovation Domain Controller.
Note: Emerson recommends that you use the External Server (GPS clock ), if available, as the
primary time source. In this case, you can use an Ovation or non-Ovation Domain Controller as
the secondary time source.
5.4.1 T o configure an e xte rnal se rver as the NT P se rver
Use the following steps to configure an external server as the NTP or time server:

2. Use the system tree to navigate to the Network Time Protocol folder:
Systems -> Networks -> Configuration -> Network Time Protocol
3. Right-click the Network Time Protocol folder.
132 OW351_60
4. Select Insert New. The NTP Configuration dialog box appears. The following figure and table
describe the fields of the NTP Configuration dialog box.
Figure 92: NTP (Time) Configuration dialog box
NTP (Time) Configuration dialog box fields
Time Server Standard NTP Server.
Domain Server Domain Server IP Address (System use only.)

NTP Server NTP Server IP Address (System use only.)
Time Server 1 Time server where the remaining drops in the system are synchronized. The
NTP (Time) Server choices are Blank, Drop #, or External Time Server. The field is not available
unless Standard NTP Server is chosen for the Time Server; otherwise, the field is
grayed out.
External Time Time Server IP address for an external time server. The field only appears if
Server Standard NTP Server is chosen for the Time Server, and if External Time Server
is selected from the Time Server 1 drop-down menu.
Time Server 2 Back-up time server to be used if Time Server 1 cannot be accessed. The choices
NTP (Time) Server are Blank, Drop #, or External Time Server. The field is not available unless
Standard NTP Server is chosen for the Time Server.
External Time Time Server IP address for an external time server. The field only appears if
Server Standard NTP Server is chosen for the Time Server, and if External Time Server
is selected from the Time Server 2 drop-down menu.
5. Select the drop to be used as Time Server 1 from the drop-down menu. If External Time
Server is selected, enter the IP address.
6. Select the drop to be used as Time Server 2 from the drop-down menu. If External Time
Server is selected, enter the IP address.
7. Select Ok to activate the NTP.
Note: The changes do not tak e effect until the drop is Downloaded (see page 99) and Rebooted
(see page 113). You should download and reboot all the drops in the system to ensure the NTP
change is valid throughout the system.
OW351_60 133
5.4.2 T o configure an Ov ation Domain Controller as the NT P se rver
Use the following steps to configure an Ovation Domain Controller as the NTP or time server:

2. Use the system tree to navigate to the Network Time Protocol folder of the Domain
Controller:
Systems -> Networks -> Units -> Drops -> Configuration -> Domain Ctrl Network Time
Protocol
3. Right-click the Domain Ctrl Network Time Protocol folder, and select Insert New.
Note: Only the drop designated as the Domain Controller will be allowed to set the time.
4. The New Domain Ctrl Network Time Protocol window appears. Select the proper clock. The
choices are Internal Clock and External Clock.
Figure 93: New Domain Ctrl Network Time Protocol window
5. Select Ok to activate the Domain Controller NTP.
134 OW351_60
5.5 Plant Mode (Units folder)
5.5 Plant Mode (Units folder)
Plant Mode is used to define the current state of a plant, with up to six configurable states. For
example, Mode 1 may indicate plant startup, Mode 2 could indicate plant shutdown, and Mode 3
may indicate full load.
One analog point in the Unit is used as the Plant Mode point, the value of which indicates the
Plant Mode (1 - 6). This Plant Mode point is used by Ovation point originators to determine which
deluxe point plant mode attributes are in effect.
Defining the plant mode point is done through the Plant Mode subfolder in the Units folder.
However, setting the limits for the plant mode values for the configured states is done in the Plant
Mode tab in the Points dialog box. Plant Mode values can be used with Deluxe Analog, Deluxe
Digital, and Deluxe Packed points.
Note: Custom control logic is required to drive the value of the point.
5.5.1 T o de fine the analog point that re presents your Plant M ode
2. Use the system tree to navigate to the Plant Mode item:
Systems -> Networks -> Units -> Configuration -> Plant Mode item
3. Right-click on the Plant Mode item.
4. Select Insert New. The New Plant Mode dialog box appears:
Figure 94: New Plant Mode dialog box
5. Type the name of the analog point to be used as the plant mode in the Value column.
6. Select Ok/Apply to add the changes to the database.
OW351_60 135
5.6 Point Processing (All folders)
5.5.2 T o modify the analog point that re presents your Plant M ode
It may be necessary to change the designation of the analog point that represents the Plant
Mode. Use the following procedure to modify this designation:

2. Use the system tree to navigate to the Plant Mode folder:
Systems -> Networks -> Units -> Configuration -> Plant Mode item
3. Right-click on the Plant Mode item in the WorkPad window.
4. Select Open. The Plant Mode dialog box appears.
5. Make necessary changes and select Ok/Apply to add the changes to the database.
The purpose of point processing is to process commands and perform alarming/limit checking for
points. Point processing can be configured at the Systems, Networks, Units, or Drops level in the
system tree. The lowest level of configuration overrides the higher level of configuration. For more
information about Point Processing or Originated Point Processor (OPP), refer to the Ovation
Record Types Reference Manual.
The Point Processing dialog box defines the configuration used during point processing such as
user-definable frequency and manually entered quality. Access this folder if you would like to
process points at a quality and rate other than the default settings.
5.6.1 T o proce ss a point

2. Use the system tree to navigate to the desired folder.
Systems -> Networks -> Units -> Drops -> Configuration -> Point Processing
3. Select the Point Processing folder.
136 OW351_60
4. Double-click the Point Process Configuration folder in the WorkPad window; the Point
Processing Config dialog box appears. The following figure and table explains the fields
available in the Point Processing Config dialog box.
Figure 95: Point Processing Config dialog box
Point Processing Config dialog box fields
I TE M DE S C R I P TI O N S E TTI N G O P TI O N
Manually Entered Quality Specifies the quality that is assigned to a Good, Fair (Default),
manually entered point. Poor, Bad
User Defined Frequency Enables or disables the defined OPP Disabled (Default)
(Originated Point Processing) task. Enabled.
User Defined Frequency Specifies the frequency of the enabled user- 2000 (Default).
(msec.) defined OPP task in milliseconds.
Millisecond Resolution Enables or disables OCR400 Controller Disabled (Default)
timestamping to the 1 millisecond resolution. Enabled.
The millisecond format must also be selected
in the Alarm Display tab to allow for
millisecond timestamping. (Refer to the
Ovation Operator Station Configuration
Guide.)
5. Enter the appropriate changes and select Apply or Ok to accept the changes.
6. You must download (see page 99) and reboot (see page 113) the drop before the new
settings take effect.
OW351_60 137
5.7 SNMP (Drops)
5.7 SNMP (Drops)
Simple Network Management Protocol (SNMP) is a program designed to monitor and report the
activity in various devices on the Network. The choice of devices to poll, and the variables in each
device to poll is configurable. The SNMP application program (SNMP Ovation) uses SNMP
variables, known as Management Information Blocks (MIBs), in Ovation points.
The SNMP folder is only found in the Operator Stations, Sim Operator Stations, Base Station, and
Virtual Controller Host drops.
5.7.1 T o configure SNMP

2. Use the system tree to navigate to and open the appropriate drop to be configured for SNMP.
Systems -> Networks -> Units -> Drops -> Applicable Drop folder -> Configure -> SNMP
Note: The SNMP folder is only found in the Operator Station, Sim Operator Station, Base
Station, or Virtual Controller Host drops.
3. Open the Configuration folder and right-click on the SNMP item. Select Insert New; the
SNMP Wizard appears.
4. There are no settings to be made. Select Finish. When an SNMP item is created, a blank
SNMP Notepad file opens.
Figure 96: SNMP configuration file header
138 OW351_60
5.7 SNMP (Drops)
5. All SNMP settings are typed into the file. Enter all the settings needed to complete the SNMP
configuration. See SNMP Parameter settings (see page 140) for more information. See
example SNMP file below.
Figure 97: SNMP configuration file
6. On the Notepad window, pull down the File menu and select Save.
Note: Do not perform a Save As function. The SNMP file could be permanently lost.
7. After saving the SNMP configuration, perform a Download (see page 99) and a Reboot (see
page 113) function.
OW351_60 139
5.7 SNMP (Drops)
5.7.2 SNM P Parame ter se ttings
In order to complete the SNMP configuration you need to configure various settings. The setting
information is described in the following section. "DeviceX_*" topics must be hand typed into the
snmp_config file if they are not already present.
 DeviceX. TimeOutPoint Name (see page 140).
 DeviceX. TimeOutBitNumber (see page 140).
 DeviceX.CommunityName (see page 141).
 DeviceX.VariableY. Name (see page 141).
 DeviceX.VariableY.Frequency (see page 141).
 DeviceX.VariableY. Test (see page 141).
 DeviceX.VariableY. ConfiguredV alue (see page 142).
 DeviceX.VariableY. UpperLimit (see page 142).
 DeviceX.VariableY.LowerLimit (see page 142).
 DeviceX.VariableY.BitMaskEnabled (see page 142).
 DeviceX.VariableY.BitMask (see page 142).
 DeviceX.VariableY.PointName (see page 143).
 DeviceX.VariableY.BitNumber (see page 143).
 DeviceX.Name (see page 143).
Note: In the following parameter settings, "X" refers to the device number. “Y” refers to the
variable number. SNMP2Ovation reads the device or the variable only in numerical order and
stops reading at the last number. For example, if devices or variables have been numbered 1, 2,
3, 5, SNMP2Ovation reads 1, 2, 3 and then stops, ignoring all numbers after the missed
number.
5.7.3 De v iceX.TimeOutPointName
Parameter Description: Point Name used to indicate device time out. The point must be a digital
or packed digital point.
Example
Device1.TimeOutPointName: LP158s001
5.7.4 De v iceX.TimeOutBitNumber
Parameter Description: Bit Number to use in the case of a packed digital point.
Example
Device1.TimeOutBitNumber: 0
140 OW351_60
5.7 SNMP (Drops)
5.7.5 De v iceX.CommunityName
Parameter Description: Community name or password. By default, the program uses “public” as
the community name.
Example
Device1.CommunityName: Public
5.7.6 De v iceX.VariableY.Name
Parameter Description: Variable to be polled on device.
Example
Device1.Variable1. Name: transmission.fddi.fddimib.fddimibMACCounters.fddimibMA CCo
5.7.7 De v iceX.VariableY.Frequency
Parameter Description: How often, measured in seconds, to retrieve this variable from the device.
Example
DeviceX.Variable1.Frequency: 10
5.7.8 De v iceX.VariableY.Test
Parameter Description: Test to perform on variable. Possible tests are:
 ValueNEConfiguredValue - If the value of the variable is not equal to the configured value,
then the result of the test is true.
 ValueEQConfiguredValue - If the value of the variable is equal to the configured value,
then the result of the test is true.
 ValueGTLimit - If the value of the variable is greater than the configured limit, then the
result of the test is true.
 DeltaGTLimit - If the difference in the variables’ values at the n and (n-1)t samples is
greater than the configured limit, then the result of the test is true.
 DeltaLTLimit - If the difference in the variables’ values at the n and (n-1)th samples is less
than the configured limit, then the result of the test is true.
 PostActualValue - Do not test this variable in any way; post the value of the variable in an
Analog or Digital point.
Examples
Device2.Variable4. Test: ValueNEConfiguredV alue

Device3.Variable5. Test: DeltaGTLimit
OW351_60 141
5.7 SNMP (Drops)
5.7.9 De v iceX.VariableY.ConfiguredValue
Parameter Description: A value to test against a variable. This parameter is used if the test
parameter is ValueNEConfiguredValue, ValueEQConfiguredValue, or ValueGTLimit.
Example
Device2.Variable4. ConfiguredV alue:4
5.7.10 De v iceX.VariableY.UpperLimit
parameter is DeltaGTLimit.
Example
Device2.Variable4. UpperLimit:
5.7.11 De v iceX.VariableY.LowerLimit
parameter is DeltaLTLimit.
Example
Device2.Variable4.LowerLimit:
5.7.12 De v iceX.VariableY.BitMaskEnabled
Parameter Description: Values are True or False, and are not case sensitive. This parameter
indicates whether the variable should be masked before testing against a configured value or
limit.
Examples
Device1.Variable3.BitMaskEnabled: true
Device1.Variable4.BitMaskEnabled: False
142 OW351_60
5.7 SNMP (Drops)
5.7.13 De v iceX.VariableY.BitMask
Parameter Description: The variable read from the network equipment is logically ANDed with the
assigned variable before testing it against a configured value or limit. The value can be expressed
as either a decimal or a hex number. When expressed as a hex number, it must be prefaced with
Ox. The parameter is used only if:
 The bit mask is enabled for the variable.
 The test applied is one of the following:
 ValueNEConfiguredValue
 ValueEQConfiguredValue
 ValueGTLimit
 The variable is an integer.
Examples
Device1.Variable3.BitMask: 384
Device1.Variable4.BitMask: 0x180
Note: The above two examples are equivalent.
5.7.14 De v iceX.VariableY.PointName
Parameter Description: Point to update with result of the test. The point can be an analog, digital ,
or packed digital. If the point is a packed digital, it is necessary to specify a bit number as well.
Example
Device1.Variable3.PointName: LP158s001
5.7.15 De v iceX.VariableY.BitNumber
Parameter Description: Bit number is to be used if the point configured in

DeviceX.VariableY.PointName is a packed digital point.
Example
Device1.Variable5.BitNumber: 7
5.7.16 De v iceX.Name
Parameter Description: Device Name or IP Address.
Example
Device1.Name: 127.9.200.101
Note: Due to security reasons, an IP address in an Ovation manual is shown with "127" as the
first octet. These IP addresses are for example purposes only and should not be used in an
actual Ovation system. Contact your Emerson project representative for assistance in obtaining
the IP addresses for your system.
OW351_60 143
5.7 SNMP (Drops)
5.7.17 T o modify SNM P
If SNMP Configuration is already established, you may need to update it. Use the following
procedure to modify SNMP.

2. Use the system tree to navigate to and open the Operator Station, Sim Operator Station,
Base Station, or Virtual Controller Host drop folder you are planning to modify.
3. Select the Configuration folder.
4. Right-click the SNMP folder; the SNMP item appears in the WorkPad window.
5. Open the SNMP item in the WorkPad window. The SNMP file appears in a Notepad window.
6. Make any necessary changes.
7. Choose File from the Menu bar and select Save.
8. After saving the SNMP configuration, perform a Download (see page 99) and Reboot (see
page 113).
144 OW351_60
SECTION 6
6 Managing Ovation licenses
IN THIS SECTION
Understanding Ovation licensing.............................................................................. 145

What are the types of licenses? ............................................................................... 146
Licensing requirements for an Ovation Windows -based system ................................. 146
Licenses warning boxes and error messages ........................................................... 147
What is the License Manager?................................................................................. 148
License Manager components ................................................................................. 149
6.1 Understanding Ovation licensing
Licensing is a way to receive permission to enable certain Emerson Process Control software
products and processes. Since the Ovation Developer Studio can be customized to meet the
needs of large or small systems, licensing allows the ability to easily scale the size of a system to
provide for its growth over time.
Licenses are stored on a License Server and are accessed through the Ovation Developer
Studio. (The Ovation Database Server can be defined as a System License Server.) As you log
into the Developer Studio, licenses are retrieved from the License Server. When a license is
accessed, that license becomes locked so no other user can access it. Licenses remain locked as
long as the licenses are in use. If all licenses are in use, you must wait until a license becomes
available.
The Developer Studio has a License folder, which is only located at the Systems folder level.
When you open the License folder, the Ovation License Manager starts (see page 148).
The License Manager displays the details of the Ovation license. For example, it reports the
quantity of each Ovation drop type, Remote Network, and Data Server that can be configured and
utilized. For floating licenses (see page 146), the License Manager reports the total number of
users who may simultaneously execute an Ovation engineering application, as well as where and
by whom the applications are being executed, such as User:Administrator@host:drop 200.
The license codes, called code keys, are obtained from Emerson Process Management and
entered into the system using the License Manager. The License Manager can be accessed
through the System folder, as well as through the warning boxes indicating that you have been
locked out of the system (see Licenses warning boxes and error messages (see page 147).)
Note: If the operating system is reloaded on the Database Server, the license k ey is no longer
valid. You are required to get a new license k ey code from SWLicensing@Emerson.com.
OW351_60 145
6.2 What are the types of licenses?
6.2 What are the types of licenses?
There are two basic types of licenses in Ovation:

 Fixed or hard licenses.
 Floating licenses.
Fixed licenses provide limitations on the size of an Ovation Syst em, such as the number of certain
types of drops in the system. The Developer Studio prevents you from adding or configuring any
Ovation drops when the licensed limit has been reached.
Note: The Base Station drop uses the Operator Station drop licenses. Licenses are also
required for Remote Network s and/or Data Servers.
Floating licenses limit the number of each type of Ovation engineering applications that can be
executed concurrently on the Ovation system. The Ovation engineering applications that are
bound by floating licenses are:
 Ovation Developer Studio.

 Ovation Control Builder.
 Ovation Graphics Builder.
6.3 Licensing requirements for an Ovation Windows -based system
Plan your software installation or upgrade to ensure that you have key codes or license files
readily available when they are needed during the installation. These licenses are available during
normal work hours from your Emerson representative. Depending on your situation, this contact
might be your project engineer, after-market representative, or Field Service engineer. Contact
Emerson prior to installations or upgrades to ensure the availability of required key codes or
licenses.
 If you are planning to perform a new installation, you would typically contact your project
engineer.
 If you are planning to perform an upgrade, you would typically contact your Field Service
engineer or possibly your after-market representative.
Note: If your system was initially loaded at the Emerson plant, the license codes that were used
for the load procedures are provided in your Software and Licensing Kit binder. If you are
upgrading the Windows Operating System, you will need a new Microsoft product k ey code.
 If you are performing an emergency reload, you can call 1-800-445-9723 for license
assistance. Be prepared to provide your name, your project or company name, and the exact
nature of your installation needs. Your call will be evaluated for emergency status and then
forwarded to the appropriate support department. You will receive a response as soon as
possible, based on your need and on the level of your Support Agreement with Emerson.
146 OW351_60
6.4 Licenses warning boxes and error messages
The following software packages require licensing:

 Microsoft Operating System - A product key is provided by Microsoft with the software
media or by Emerson in the Software and Licensing Kit binder. This key is needed when you
prepare a drop to be a Database Server or an Operator/Base Station.
Ensure that you register your operating system with Microsoft within 30 days or you may be
locked out of your system.
Note: If you are upgrading to a new Windows operating system, you will need a new Microsoft
product k ey code from Microsoft or Emerson.
 Ovation - A key code will be requested during the installation. Send the Locking Code that is
displayed in the License Manager to Emerson. A key code will then be provided by Emerson
(this key code is needed when you install Ovation on a Database Server or an Operator/Base
Station).
Note: A ten-day trial license automatically tak es effect at the initial installation of Ovation on the
Ovation Database Server. The trial license permits the configuration/specification of the
maximum number of Ovation drop types, limited only by the overall number of drops in the
system.
The trial license also provides one floating license for each of the engineering applications. The
ten-day trial permits the system to be used until the proper license codes and license k eys are
acquired from Emerson Process Management. During the trial period, messages appear stating
the number of days that remain in your trial license.
6.4 Licenses warning boxes and error messages
Warning boxes appear if you attempt to access the Developer Studio or Developer Studio
features when there are no available licenses. The warning boxes inform you that no licenses are
currently available to perform the operation.
One of two warning boxes may appear: the Developer Studio Alert warning box or the Licenses
Error message.
Developer Studio alert warning box
The Developer Studio Alert dialog box appears where the statement reads, “There are no
Developer Studio Licenses Available.” When this dialog box appears, you must wait for a license
to become available. Select the Details button to view license-specific information.
If the Developer Studio Alert dialog box appears regularly, contact your network administrator. It
may be necessary to purchase more licenses.
License error message
The License error message appears only if you have gained access to the Developer Studio. The
License Error message appears when you attempt to open a feature that has no licenses
available.
 Select the Details button to gain license-specific information.
 Select the License Manager button to access the License Manager.
OW351_60 147
6.5 What is the License Manager?
6.5 What is the License Manager?
The License Manager is the graphical user interface used to manage your licenses. It provides
the tools necessary to view license details, add new licenses, and establish commuter licenses for
laptops.
6.5.1 T o acce ss the Lice nse M anager

2. Use the system tree to navigate to the Systems folder.
3. Right-click the Licenses folder.
4. Select Insert New from the menu. The Insert New License Wizard appears.
5. Select Finish. A new License icon appears in the WorkPad Window.
6. Right-click Licensing from the WorkPad window. Select Open. The License Manager dialog
box appears:
Figure 98: License Manager window
148 OW351_60
6.6 License Manager components
The License Manager is comprised of four components:

 Server List window — Displays where the system software and licenses reside. It also lists
the features Ovation Power Tool (OVPT), Ovation Control Builder (OCB), and Graphic Builder
(GBNT) and their subfolders.
 Feature Details window — Lists the Fixed Licenses (located under Feature: System). It also
provides information about the feature selected in the Server List window. Information such as
type of license, number of licenses purchased, and number of licenses used is contained in
the Feature Details window.
 Client Details window — Provides details about the client, including user name, host name,
start and end time.
 Operations area — Contains four tabs:
 Query Options tab (see page 149).
 Environment tab (see page 150).
 License Key tab (see page 150).
 Commuter tab (see page 151).
6.6.1 Que ry Options tab
Unless there are multiple License Servers in the system, the Query Options tab is not utilized.
Figure 99: License Manager window (Query Options tab)
Query Options tab function description
FU N C TI O N DE S C R I P TI O N
All in Subnet (Server Options) Queries any license server drops.

LSHOST list (Server Options) Provides the drop name of the license server. All software
shipped from Emerson uses this field.
Single Server (Server Options) Queries a specific drop.
All Features (Feature Options) Searches for all features on a specific drop.
Single Feature (Feature Options) Provides a specific feature the queried drop is licensed to
perform.
OW351_60 149
6.6.2 Env ironme nt tab
The Environment tab provides information about the drops and licenses. This information is
usually requested by Emerson customer service representatives and is not necessary for daily
operations.
Figure 100: License Manager window (Environment tab)
6.6.3 Lice nse Ke y tab
The License Key tab is only available when the License Manager is accessed from a License
Server. This tab provides the information necessary to retrieve license codes from Emerson and
the field to enter the license key code to activate applications.
Figure 101: License Manager window (License Key tab)
Note: In the License Key tab, the Server drop number and the Lock ing Criteria are provided.
The Lock ing Code, which is highlighted in yellow on the screen, must be given to Emerson in
order to receive the valid license k ey code. The k ey code unlock s purchased services on the
Developer Studio.
150 OW351_60
6.6.4 Commute r tab
The Commuter tab allows you to sign out a license from the server to a laptop computer for a
period of up to 30 days. By signing out a license to a laptop, the laptop is able to operate
Developer Studio software.
Figure 102: License Manager window (Commuter tab)
The signed-out license becomes locked on the server. No one can use that license until either it is
signed back in or 30 days passes. At the end of the 30 days, the commuter license on the laptop
times out and locks the Ovation application on the laptop. On the server, the license lock is
released, freeing up that license for other users.
OW351_60 151
SECTION 7
7 Adding drops to the Developer Studio
IN THIS SECTION
What are drops? ..................................................................................................... 153

Determining the need for a new drop ....................................................................... 153
What types of drops are available? .......................................................................... 154
To insert a drop point .............................................................................................. 161
7.1 What are drops?
A drop is any computer (such as an Operator Station) that contains Ovation software and
communicates with other drops in the system. The Ovation system contains several types of
drops. The Developer Studio provides a mechanism for the adding, modifying, and deleting of
drops to the system database.
The process of installing and maintaining the required software on your Ovation system drops
consists of several operations. For this reason, most drops are added to your system at the time
of installation. Refer to the Ovation Software Installation Manual for more information.
After your Ovation system is loaded, you may need to add a few additional drops to your system.
Typically, drops are added to the Developer Studio one at a time, on a case-by-case basis. When
you add drops through the Developer Studio, you should already know which drops are domain
controllers and which drops are of which drop type.
Note: You are only able to add as many drops as defined by the license k ey. Before entering
drops, verify that the maximum number of drops for each drop category has not been reached.
The Base Station drop uses the Operator Station drop licenses. See Managing Ovation licenses
(see page 145) for more information about licensing.
After a drop has been created, you must create a drop point in order for the system to recognize
the new drop. The drop point corresponds to the drop’s required DU record. See To insert a Drop
Point (see page 161).
After a drop and the drop point have been created and loaded to the target drop, it may be
necessary to make modifications to the drop (see page 161). Drops are established and
configured using the items within a Drop folder.
OW351_60 153
7.2 Determining the need for a new drop
7.2 Determining the need for a new drop
Before adding a new drop to your Ovation system, consider the following:
 A drop is added to accommodate the addition of a station.
 A drop is added to accommodate additional points, because:
 The Controller is full (depends on configuration):
 Normal configuration is a maximum of 6,000.
 Expanded configuration is a maximum of 16,000 points.
 32,000 is a maximum of 32,000 points.
 Physical limitations (cost of wiring, signal loss, location reasons) require a new drop.
 A new license is needed prior to adding a drop. Once it is determined that a new drop must
be installed, obtain the appropriate licensing requirements from Emerson. See Managing
Ovation licenses (see page 145).
 A drop point (see page 161) must be added to a new Drop in order to supply a DU record. A
DU record type is used to store status information for a drop.
Note: Currently, Ovation is limited to 254 drops per network .
7.3 What types of drops are available?
There are two basic types of drops that can be added to a system: workstations and Controllers.
Workstation drops:
 Operator Station
 Sim Operator Station
 Base Station
 Virtual Controller Host
Controller drops:
 Controller
 Advanced Controller
 Sim Controller
 Advanced Sim Controller
 Virtual Controller
 Advanced Virtual Controller
Detailed information on adding Controller-type drops can be found in the following manuals:
 Ovation Controller (OCR400) User Guide.
 Ovation Controller (OCR1100) User Guide.
 Ovation Simulation User Guide.
 Ovation Virtual Controller User Guide.
154 OW351_60
7.3.1 T o inse rt a workstation drop in the De veloper Studio
Perform the following steps to insert an Operator Station, Base Station, or Sim Operator Station
drop:

3. Right-click the Drops folder and click Insert New. The Insert New Drop Wizard appears.
4. Type the drop ID in the Drop ID value field (1-254).
5. If a partner drop is to be used, type the ID in the Partner ID value field (1-254).
6. Pull down the Drop Type menu and select a drop type.
7. Click Finish. The New [Drops] dialog box appears:
Figure 103: New Drops dialog box (for Workstations)
8. Enter the appropriate information for the selected drop type.
OW351_60 155
New Drops dialog box fields (for Workstations)
Drop Type Drop-down menu with drop type selection (Operator Stations, Base
Stations, and Sim Operator Stations).
Maximum Point Limit Not used for workstation drops (Normal, Expanded).
Local Data Servers Read-only field that tells if the drop has been defined as a local data
server. (No, Yes). Refer to the Ovation Multiple Networks User
Guide for more information.
Local Alarm Collector Read-only field that tells if the drop has been defined as a local
alarm collector. (No, Primary, Partner, Both). Refer to the Ovation
Multiple Networks User Guide for more information.
PRIMARY or PARTNER Drop number of the new drop (1-254). If the drop has a partner drop,
Drop ID or Partner ID it is identified in the field (1-254).
Computer Name Name of the new drop. The name entered here will be shown in the
Developer Studio tree along with the Ovation drop name. If the
Computer Name is different than the Drop ID, both are shown. If
they are the same, only one name is shown. See the following
figure.
Computer Sid Read only field added by the system. ID for domain name server.
Computer Sid (cont) Read only field added by the system. ID for domain name server.
Ovation Network IP Address The Internet Protocol (IP) address for a drop is typically assigned by
the system administrator. The IP address consists of four groups of
decimal numbers and has the following format:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as the Internet),
the IP address can be any valid range.
Ovation Network Ethers Not used.
Address
Restore Not used for workstation drops. See To insert a Controller drop in
Restore Mode the Developer Studio (see page 157).
9. Click Apply to save these settings without closing the dialog box, or click Ok to save the
settings and close the dialog box. A new <DROP#> item appears under the Drops folder in
the Developer Studio tree hierarchy.
Note: Once a new drop is created, a drop point (primary and partner (if appropriate)) must be
added to provide a Drop status (DU) point (see page 161) record type.
156 OW351_60
10. If you chose to enter a more descriptive name for the Computer name, the Developer Studio
tree appears as shown below:
Figure 104: Computer name shown beside drop ID in Studio tree
Note: After the addition of an Ovation work station drop (or drops), you must query download all
drops on the network .
7.3.2 T o inse rt a Controller drop in the De veloper Studio
Perform the following steps to insert a Controller, Sim Controller, Advanced Controller, or
Advanced Sim Controller drop:

3. Right-click the Drops folder, and click Insert New. The Insert New Drop Wizard appears.
4. Type the drop ID in the Drop ID value field (1-254).
5. If a partner drop is to be used, type the ID in the Partner ID value field (1-254).
6. Pull down the Drop Type menu and select a drop type.
OW351_60 157
7. Click Finish. The New [Drops] dialog box appears:
Figure 105: New Drops dialog box (for Controllers)
8. Enter the appropriate information for the selected drop type. Refer to the following table for
information on each window entry.
9. Click Apply to save these settings without closing the dialog box, or click Ok to save the
settings and close the dialog box. A new <DROP#> item appears under the Drops folder.
Note: Once a new drop is created, you must add a Drop Point for the primary and partner to
provide a Drop status (DU) point (see page 161) record type.
158 OW351_60
New Drops dialog box fields (for Controllers)
Drop Type This procedure deals specifically with the Controller selection from the drop -
down menu. The menu has the following options:
 Controller
 SimController
 Advanced Controller
 Advanced SimController
 Virtual Controller
 Advanced Virtual Controller
Controller Type Choose the correct Controller type. - (OCR400, OCR1100)
Control Synchronization Available when both a primary and partner Controller are inserted and allows
both Controllers to be automatically synchronized.
You can choose whether to have information sent over a dedicated cable or
over the Ovation network by making one of the following selections:
 Ovation Network
 Dedicated Cable
By default, the Dedicated Cable option is enabled. When possible, the
Dedicated Cable option is recommended to alleviate network traffic.
Maximum Point Limit This radio button selects the maximum number of points that the Controller
can be configured to monitor.
Due to the way points are indexed, the actual point numb er is the maximum
point count minus 1.
Normal handles up to 6000 points. (Actual limit = 5,999)
Expanded handles up to 16,000 points. (Actual limit = 15,999)
32000 handles up to 32,000 points. (Actual limit = 31,999)
Note: Additional shared memory may b e required to accommodate additional

points.
Radius Server Provides user authentication and authorization. Refer to the Managing Security
for Ovation manual for more information.
Primary & Partner When the primary/partner configuration is not used, no information input is
Section required in the partner section.
Drop ID Drop number of the originating drop of the point (1-254).

Ovation Network IP The IP address consists of four groups of decimal numbers and the format is:
Address
xxx.xxx.xxx.xxx
The System Administrator typically assigns these addresses. They can also be
assigned to be any valid range if the network is isolated from other networks
(such as the Internet).
Ovation Network Ethers The format for the hardware address is:
Address
xx:xx:xx:xx:xx:xx (where the last four numbers (xx:xx) are typically located
on a label on the NIC).
If the hardware address cannot be located on the NIC, see Determining NIC
Addresses in the applicable Ovation Controller User Guide.
OW351_60 159
Ovation Highway Ethernet interface that connects the Controller to the Ovation network.
Interface
(Automatically selected for the OCR400 and OCR1100.)
(ZNYX, Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)
NIC Interface Automatically selected by the system. Name of physical port that the Ethernet
cable is connected to.
(OCR400) - (OCR1100)
(N1) - used for third-party Ethernet interface
(N2) - dedicated for use as the Ovation network interface
(N3) - used for Dual or third-party Ethernet interfaces
(N4) - used for Dedicated control synchronization cable or third-party Ethernet
interfaces
Ovation Highway Configures the speed of the Controller on the network. Currently, the only
Interface Mode option is 100 mbps / full duplex.
Backup NIC Interface Automatically selected by the system.

(Available if a backup (N1 - N4) - (fei0 - fei4) for OCR400 Controllers
NIC is used.)  N3
(N1 - N4) - (gei0 - gei4) for OCR1100 Controllers
 N3
Control Synchronization The Controller software is configured to automatically run control
Interface synchronization of redundant controllers over the network.
(OCR400) - (OCR1100)
(N1 - N4)
Note: The OCR400 and OCR1100 allow direct connection (port N4 to N4)
and synchronization of redundant controllers. This connection allows for
faster and safer Controller synchronization.
When using the direct connection (Port N4 to N4) Control Synchronization,

ensure that b oth controllers have Control Synchronization enabled and that
the cab le is attached b efore performing a download, reb oot and load.
If a pair of redundant controllers has b een running with Control

Synchronization enabled and Control Synchronization is then disab led, the
dedicated cab le should b e disconnected from the controllers b efore reb ooting
the controllers with the new configuration.
Conversely, if a pair of redundant controllers has b een running with Control

Synchronization disabled and Control Synchronization is then enab led, the
dedicated cab le should b e connected between the controllers after they have
b een running with the new configuration.
160 OW351_60
7.4 To insert a drop point
Ethernet Remote Interface
Network Port Automatically selected by the system. Name of physical port that the remote
Ethernet cable is connected to. N1 - N4 are possible choices.
IP Address Generated by the system.
DHCP Enabled Generated by the system.
Subnet Mask Generated by the system.

Interface Mode Defines the mode of the remote node.
(Primary)
Interface Mode (Partner) Generated by system. Will be same as the Primary.
Restore Mode Online Controller Restore Mode - Reloads mismatched Controllers to a prior
matched state. The choices are Restore Mode Disable, Restore Mode Enable
All Drops, and Restore Mode Enable Redundant Drops. Refer to the Ovation
Controller User Guide for more information.
Note: After the addition of an Ovation Controller drop (or drops), you must query download all
drops on the network .
7.3.3 T o e dit drop information

Systems -> Networks -> Units -> Drops item
3. Right-click the applicable Drop folder.
4. Select Open. The Drop dialog box appears.
5. Make the necessary changes and select Ok/Apply.
6. Download (see page 99) configuration changes to the drop by using the right-click menu.
7. Reboot (see page 113) (as necessary) using the right-click menu.
The drop point or DU record (also known as a Drop Status record) is automatically configured in
each Ovation drop. The purpose in broadcasting this record is to alert the system to any faults
that may occur in a specific drop and to show the current status of the drop.
Standard status diagrams are designed to extract information from DU records. Normally, the
status diagrams are sufficient to gather all pertinent data about the status of an individual drop.
OW351_60 161
Use the following procedure to create a drop point:

2. Use the system tree to navigate to the Points folder:
Systems -> Networks -> Units -> Drops -> Points
3. Right-click on the Points item. Select Insert New from the resulting pop-up menu.
4. The Insert New Drop Point Wizard appears. Provide the following information:
 Define a name for the drop point in the Point Name Value field (the name must be the
word Drop immediately followed by the drop's number).
 Select the appropriate drop number to correspond with the point name entry.
Figure 106: New Drop Point dialog box
162 OW351_60
New Drop Point dialog box tabs and fields
T AB FI E L D DE S C R I P TI O N
Point Point Alias Sixteen character alias for the point name.
Description Description maps directly to the ED field of the point record and can be
up to 30 characters.
Characteristics Characteristics maps directly to the KR field of the point record, with the
first character mapping directly to the AY field (destination) of the point
record.
Up to eight alphanumeric characters can be used and the first character
must be a letter (A - Z, the dash character can be used also).
Drop Number The Drop Number of the originating drop of the point (1-254).
Partner Drop Identifies the drop number of the partner drop (if appropriate).
Security Security Group Represents the defined security groups for each point in the system, up
to 32 check boxes can be defined.
Note: At least one security group must b e selected to allow point

modification.
Ancillary Ancillary Additional user-defined information about the points.

Alarm Alarm Priority Sets the alarm priority field (1- 8; 1 being the highest).
Alarm This text identifies the point that is in alarm, the alarm message boxes in
Annunciator Text the Alarm Annunciator alarm bands display two lines of text (up to 12
(only appropriate characters per line), for a total of 24 characters.
if Alarm You can separate the two lines of text by using a vertical bar ("|") as a
Annunciator is line delimiter, this bar does not count toward the 12 characters in the
used) line.
For example, if you enter FD FAN AA|AIR FLOW, it appears in
the alarm message box as:
FD FAN AA
AIR FLOW
If you do not use the line delimiter, the first 12 characters are used for
line one and any additional characters are us ed for line two.
Alarm Description A text description of the alarm (maximum string of 45 characters.)
Display This field defines the appropriate summary diagram that is sent to the
process diagram system.
Signal Diagram The Signal Diagram field defines the signal diagram number.
5. After the required information is provided, select Finish.

6. The configuration tabs within the New Drop Point dialog box appear. Tab through the New
Drop Point dialog box and complete any desired changes to the default field values.
7. Select the Apply button to save these settings without closing the dialog box. Select the Ok
button to save the settings and close the dialog box.
8. Repeat the "Insert a drop point" procedure (Steps 1 through 6) if there is a Partner Drop.
9. Right-click on the new Drop Point item.
10. Select Load from the resulting pop-up menu to update the system with the new drop.
OW351_60 163
SECTION 8
8 Creating Points in the Developer Studio
IN THIS SECTION
What is a point?...................................................................................................... 165

Understanding point names ..................................................................................... 167
Points folder feat ures and functions ......................................................................... 168
Understanding point record types and sizes ............................................................. 169
Adding points in the Ovation Developer Studio ......................................................... 169
What information must be configured for each point type? ......................................... 172
Understanding the Points dialog box and its tabs ...................................................... 177
What are PDS Point Groups? .................................................................................. 215
What are Pack ed Group Numbers?.......................................................................... 219
8.1 What is a point?
CAUTION! Understanding point information is a complex subject. For this reason, this section
provides an overview of points and how they relate to the Developer Studio. More information
about points and record types is described in the Ovation Record Types Reference Manual.
Since correct point configuration is very important to the integrity of your Ovation system, only
knowledgeable personnel should create points.
A point is a record in the global database that contains a value and other related data. Points
include inputs and outputs from field devices, calculated values, and internal system information.
A name and a unique System ID number identify each point, and this information is stored in the
Ovation Master Database. An Ovation system can support up to 200,000 process points.
The Ovation control system scans or processes the following types of input/output. The control
system converts incoming information to engineering units then stores it in the point records. This
information is available for use in all parts of the system and for transmission to all parts of the
system.
 Analog Input
 Thermocouples
 RTD
 Milliamp DC
 Millivolt DC
 Volt DC
 Digital Input
 Standard Digital
 Sequence of Events
 Pulsed Input
OW351_60 165
8.1 What is a point?
 Transforms of Analog inputs

 Calculated logicals (Boolean)
 Analog calculated values
 Analog outputs
 Digital outputs
 Relay outputs
 Loop Controllers (modulating and digital)
 Serial interfaces
 Turbine Control I/O
 PLCs
 Smart Transmitters
 Digital Valve Controllers
 FOUNDATION Fieldbus
 Profibus DP I/O
 DeviceNet I/O
 Third-party I/O interfaces
 OPC
 Ovation multi-network I/O
Note: Ovation Control Builder-generated points should never be modified in the Studio. These
points are intentionally hidden from the Hardware view. User-defined points should be used if
customization is necessary.
8.1.1 What is a point re cord?
A point record stores the set of information that defines the attributes of the point. Point records
are used within each drop, and to communicate over the Ovation Network to other drops. There
are 11 types of point records.
Point record information is required in many contexts when programming the Ovation system.
Every drop incorporates a point database, which must be defined to include all of the points
originated or received by the drop. In addition, each drop's application may use specific point
record fields. Examples of tasks that require familiarity with point records include the following:
 Defining the point database for any drop.
 Creating graphics that include process point information.
 Troubleshooting system faults.
8.1.2 What is a re cord fie ld?
Point records are constructed of record fields. Some fields can be defined by the user, while other
fields store information the system needs to process the point value. Examples of record fields
are 1W, AV, AZ, and so forth.
Refer to Ovation Record Types Reference Manual for information required to select the proper
record type, based on the point's application. This includes information on the record fields
included in each record type, the size of each type of point record, and the applications where
specific record types are used.
166 OW351_60
8.2 Understanding point names
8.2 Understanding point names
Point names are defined early in the system configuration process by plant personnel and
Emerson project team members. Sometimes, existing point names are imported into a new
Ovation system with some minor enhancements. Other times, point names are created in the
Developer Studio.
Note: Points can also be created in the Control Builder. Refer to the Ovation Control Builder
User Guide for more information.
Typically, the point names are based on the field equipment they will be associated with.
For example, a point name that can be used for a pump valve could be B1AHVAO1232.
Where:
B = Boiler.
1 = Boiler number.
AH = Ash Handling.
VAO = Valve - Air Operated.
1 = First Floor.
232 = Individual equipment number.
A database contains multiple point names that should be appropriately named to ensure that the
point names can be mapped to the applicable element in the plant.
Note: Typically, these point names become fully qualified point names (see page 167) when
they are used in the Ovation Distributed Database.
8.2.1 Using fully qualifie d point name s
A fully qualified point name in the Ovation system uses the following format:
“name.unit@network”
This format consists of three parameters:

 A 24-character maximum point name.
 A six-character maximum unit name.
 An eight-character maximum network name.
The “.” and “@” are required and are reserved characters. They are part of a fully qualified point
name, but are not allowed in the name portion of the fully qualified point name. Therefore, the
maximum number of characters in a fully qualified point name is 40.
For example, B1AHVAO1232.UNIT3@NE TWORK 1 would reference point B1AHVAO1232

located in the unit whose name is UNIT3 and in the network whose name is NETWORK1. This
allows for the use of the same point name in different units or networks. Ovation is able to identify
each point since a unique SID was assigned to each point as it was entered into the system.
OW351_60 167
8.3 Points folder features and functions
In a multiple network implementation, the network name segment must be one of the following:
 Actual name of the local or remote network.
 Any of the defined network aliases (the alias for the remote or local network).
Note: For more information about multiple network s, refer to the Ovation Multiple Networks User
Guide.
8.2.2 Rule s for using fully qualified point name s
Use the following rules when creating fully qualified point names:
1. Characters in the name portion may be any combination of alphabetic, numeric (0 - 9), or
special punctuation characters. The only characters that are not allowed in the name are *, @,
., %, $, ~, \, “, ‘, comma, space.
2. Point names are not case sensitive. That is, “Testai01.unit1@wdpf” is the same as
“TESTAI01.UNIT1@WDPF”.
3. A point name cannot be a reserved word (refer to the Ovation Graphics Language Reference
Manual for information on reserved words).
4. Do not begin user-defined point names or Control Builder default point names with OCB.
5. Do not include a space in a point name.
6. When creating a point name through the Ovation Developer Studio, do not enter fully
qualified names. Only the point name parameter is used.
8.3 Points folder features and functions
Every drop in the Developer Studio must contain a Points folder. The Points folder has a folder for
each of the 11 types of point records (see page 169).
The Points folder is a child of a Drops folder and contains an item for each user-defined point in
the Drop. Points contain the data gathered from the various hardware devices used by the
operators as well as by the system to make decisions concerning the operation of hardware in the
plant. Some of the types of information are the field inputs and outputs, calculated values, and
internal system information. The gathered information can be in the form of a temperature, level of
solids or fluids, weight, vibration, amount of rotation, timing, and so forth. You can identify each
point by a name and a unique System ID number.
Figure 107: Points folder
To add a new point, see Adding points in the Ovation Developer Studio (see page 169).
168 OW351_60
8.4 Understanding point record types and sizes
8.4 Understanding point record types and siz es
The Ovation system has 11 record types:

 Analog (two sizes)
 Long Analog (LA)
 Deluxe Analog (DA)
 Digital (two sizes)
 Long Digital (LD)
 Deluxe Digital (DD)
 Packed (two sizes)
 Long Packed (LP)
 Deluxe Packed (DP)
 Packed Digital (one size - PD)
 Algorithm (one size - LC)
 Drop (one size - DU)
 Module (one size - RM)
 Node (one size - RN)
Long record types are the default and have full alarming and I/O capabilities.
Deluxe record types (an optional feature not used by standard Ovation software) provide two
additional functions:
 Limits can be defined that are based on plant mode (1 to 6). Plant mode is configurable and is
used to define the current state of the plant (for example, 1 could represent plant start-up). If
the plant mode changes, the active limits would be the limits that were defined for that specific
plant mode.
 The scan time can be displayed in deluxe record fields.
8.5 Adding points in the Ovation Developer Studio
Points can be created manually or imported into the database. The procedures described in this
section are typically used for adding a small number of points. For information on importing a
large number of points, contact your Emerson project personnel.
Note: Certain values can be configured to be defaults prior to adding new points. See To
configure defaults for items in the Defaults view bar (see page 11) for more information.
The Point Copy function (see page 170) can also be used to simplify the process of adding
points.
OW351_60 169
8.5.1 T o add a point in the De v eloper Studio
The following procedure is an example of adding a point to the Ovation system but does not
detail specific field input. An analog point is used in the example, but the procedure is appropriate
for all point types. Since there are 11 types of points and each type requires different input, the
specific field information that is available for each tab is provided in the section called,
Understanding the Points dialog box and its tabs (see page 177).

3. Right-click the appropriate Points folder (such as analog points in this example).
4. Select Insert New. The Insert New [Analog] Points Wizard appears.
5. Enter the point name in the Point Name Value field. See Understanding point names (see
page 167) for more information.
6. Select the frequency from the drop-down menu.
 S - Slow (1 second).
 F - Fast (0.1 second).
 A - Aperiodic (as needed).
7. Select Finish and the New [Analog] Point dialog box appears.
Note: When look ing through the tabs, some fields are already filled in. If the box has gray
shading, the contents are added by the system; they cannot be changed and are provided for
information only.
8. Find the tabs needed for a particular point type. Then use the tables in Understanding the
Points dialog box and its tabs (see page 177) to enter the correct information.
9. Select the Apply or Ok button. If all required fields have been completed, the point is added
to the database. If a required field was not completed, a warning box appears prompting you
to complete the necessary information.
10. The point is not available on the Ovation network until it is loaded using the procedures
discussed in Load function (see page 94).
Note: If you modify, add, or delete a point, the Load flag will display on the point originator. On
occasion, the system event that notifies the Ovation Developer Studio to display its flags may
not be detected. The Refresh operation may be used to redisplay and so confirm the flag status.
170 OW351_60
8.5.2 T o use the Point Copy function to add points to the De v eloper Studio
The Point Copy function enhances the process of entering point information by allowing you to
copy a point with similar information and only changing the parameters that are different.
Note: When copying a point, hardware information is not copied.
Use the following procedures to copy a point:

2. Use the system tree to navigate to a particular Point type folder:
Systems -> Networks -> Units -> Drops -> Points -> <Point type>
3. Select the type of point to copy (analog, digital, packed, and so forth) from the system tree.
The points that are defined for the selected type appear in the Workpad window (see page
13).
4. From the Workpad window, highlight the point you want to copy and right -click. A menu
appears.
5. Select Copy. The Insert Copy of <point_name> Wizard appears:
Figure 108: Insert Copy of <point_name> wizard
6. Enter a name for the new point in the Point Name entry field and click Finish.
7. The Copy of <point_name> window appears. All of the tab settings are the same as the point
you copied. Modify any of the parameters on any of the tabs as applicable to the new point.
8. Select the Apply or Ok button. If all required fields have been completed, the point is added
to the database. If a required field was not completed, a warning box appears prompting you
to complete the necessary information.
9. The point is not available on the Ovation network until it is loaded using the procedures
discussed in Load function (see page 94).
OW351_60 171
8.6 What information must be configured for each point type?
Points are configured in the Developer Studio using the Points dialog box (see page 177). The
following sections discuss the Point dialog box tabs that are applicable for each record type.
8.6.1 Configuring Analog (LA) point type s
Analog (LA) points have the ability to continuously change values (for example, voltage). The
purpose of an analog process point record is to pass 32-bit, floating-point, real numbers
throughout the system. In addition to carrying basic value information, each long analog record
type has full alarming I/O capabilities.
The Analog Point window displays the following tabs:
 Point tab (see page 179).

 Config tab (see page 181).
 Security tab (see page 187).
 Ancillary tab (see page 187).
 Hardware tab (see page 188).
 Initial tab (see page 190).
 Alarm tab (see page 191).
 Instrumentation tab (see page 203).
 Limits tab (see page 205).
 Display tab (see page 210).
172 OW351_60
8.6.2 Configuring De luxe Analog (DA) point type s
Deluxe Analog (DA) points are like Long Analog (LA) points but also have mode setting
capabilities that are used to define the current state or mode of the plant.
The Deluxe Analog Point window has the following tabs:

 Instrumentation tab (see page 203).
 Limits tab (see page 205).
 Plant Mode tab (see page 213).
8.6.3 Configuring Digital (LD) point type s
Digital (LD) points pass discrete data throughout the system. Discrete data is logical in nature (for
example ON/OFF or TRUE/FALSE).
Note: All points assigned to the same SOE module must be assigned to the same task index
and that task must be 100ms or faster.
The Digital Point window has the following tabs:

OW351_60 173
8.6.4 Configuring De luxe Digital (DD) point type s
Deluxe Digital (DD) points are like Long Digital (LD) points but also have mode setting capabilities
that are used to define the current state or mode of the plant.
The Deluxe Digital Point window has the following tabs:

8.6.5 Configuring Packe d (LP) point type s
Packed (LP) points may be used to pack up to 16 discrete digital (logical) states in one point
record. Each bit of the packed point may be separately configured for I/O scanning. Additionally,
the packed point can be configured for register-wide addresses. Therefore, you can configure all
16 bits by the specification of only one I/O location (you only need one packed point to read the
16 channels on the card).
The Packed Point window has the following tabs:

174 OW351_60
8.6.6 Configuring De luxe Packe d (DP) point type s
Deluxe Packed (DP) points are like Long Digital (LD) points but also have mode setting
capabilities that are used to define the current state (mode) of the plant.
The Deluxe Packed Point window has the following tabs:

8.6.7 Configuring Algorithm (LC) point type s
The Algorithm records are used to store tuning or data configuration for each algorithm in the
system. Information is different for each algorithm.
The Algorithm Point window has the following tabs:

 Byte, Int., Real, & ASCII Params (see page 215).
8.6.8 Configuring Drop (DU) point type s
The drop point or DU record (also known as a Drop Status record) is automatically configured in
each Ovation drop. The purpose in broadcasting this record is to alert the system to any faults
that may occur in a specific drop and to show the current status of the drop.
Standard status diagrams are designed to extract information from DU records. Normally, the
status diagrams are sufficient to gather all pertinent data about the status of an individual drop.
The Drop Status Point window has the following tabs:

OW351_60 175
8.6.9 Configuring M odule (RM) point type s
The Module (RM) record is used to configure and monitor the status of Ovation I/O modules.
The Module Point window has the following tabs:

8.6.10 Configuring Node (RN) point type s
RN records are used to configure and monitor PCRL, PCRR, PCRQ, and remote I/O nodes.
The Node Point window has the following tabs:

8.6.11 Configuring Packe d Digital (PD) point type s
Packed Digital (PD) points pass discrete data from an Ovation drop without any other information,
such as alarming status or I/O information. A packed digital point record contains either 32
separate digital values or two 16-bit register (analog) values. Packed digitals are frequently used
to pass information contained in special functions and in text algorithms.
The Packed Digital Point window has the following tabs:

176 OW351_60
8.7 Understanding the Points dialog box and its tabs
Each point type has specific properties and configurations that differentiate it from other point
types. Point information is displayed in the Points dialog box. Notice the tabs across the bottom of
the Points dialog box. For example purposes, the Analog Points dialog box is shown below.
Figure 109: Example Points dialog box
Each Points dialog box has tabs representing various categories of attributes related to that point.
The following table identifies the tabs that pertain to a particular point type and provides a brief
description of each tab. It also lists which point types use that tab.
Points dialog box tabs
T AB S US E D F O R P O I N T TYP E S DE S C R I P TI O N
Point (see  Long Analog (LA) Provides general information about the point.
page 179)  Deluxe Analog (DA)
 Long Digital (LD)
 Deluxe Digital (DD)
 Long Packed (LP)
 Deluxe Packed (DP)
 Algorithm (LC)
 Drop (DU)
 Module (RM)
 Node (RN)
 Packed Digital (PD)
Config (see  Long Analog (LA) Used to establish the various configurations of the point.
 Algorithm (LC)
 Module (RM)
 Node (RN)
OW351_60 177
Security (see  Long Analog (LA) Represents the defined security groups for each point in
page 187)  Deluxe Analog (DA) the system.
 Algorithm (LC)
 Drop (DU)
 Module (RM)
 Node (RN)
Ancillary (see  Long Analog (LA) Provides additional user-defined information about the
page 187)  Deluxe Analog (DA) point.
 Algorithm (LC)
 Drop (DU)
 Module (RM)
 Node (RN)
Hardware (see  Long Analog (LA) Defines the I/O hardware configuration for the point.
 Module (RM)
 Node (RN)
Initial (see  Long Analog (LA) Used to establish the initial values of the various points.
Alarm (see  Long Analog (LA) Sets the various alarm priority fields for the point.
 Drop (DU)
 Module (RM)
 Node (RN)
178 OW351_60
Instrumentation  Long Analog (LA) Used to establish hardware information, including

(see page 203)  Deluxe Analog (DA) sensor limits for the point.
Limits  Long Analog (LA) Specifies the limits of point records.
 Deluxe Analog (DA)
Display  Long Analog (LA) Represents the type of display (standard, exponential,
 Deluxe Analog (DA) or technical), scale limits, engineering units, set and
 Long Digital (LD) reset descriptions, summary and signal diagrams.
 Drop (DU)
 Module (RM)
 Node (RN)
Plant Mode  Deluxe Analog (DA) Shows a collection of parameters that can be set
(see page 213)  Deluxe Digital (DD) differently for each of the six modes.
Byte Params  Algorithm (LC) Represents the byte parameters of the algorithm.
(see page 215) Labels are dependent on the algorithm name chosen on
the Config tab.
Int Params  Algorithm (LC) Represents the integer parameters of the algorithm.
the Config tab.
Real Params  Algorithm (LC) Represents the real (floating-point) parameters of the
(see page 215) algorithm. Labels are dependent on the algorithm name
chosen on the Config tab.
ASCII Params  Algorithm (LC) Represents the ASCII parameters of the algorithm.
the Config tab.
OW351_60 179
8.7.1 Point tab fie ld de scription
The Point tab window fields vary depending on the point type. The fields that apply to the
applicable point type(s) are described in the tables.
Note: All point types have a Point tab.
Point tab fields for Long Analog (LA), Deluxe Analog (DA), Digital (LD), Deluxe Digital (DD),
Packed (LP), Deluxe Packed (DP), Module (RM), and Node (RN)
Point Alias Alias for the point name. Up to 24 characters can be used.
Description Description of the point. Maps directly to the ED field of the point record.
Characteristics Characteristics provide a method for sorting the database based on plant
area, signal type, equipment, or other concepts you might want to use. There
are eight alphanumeric characters available per point.
Characteristics maps directly to the KR field of the point record, with the first
character mapping directly to the AY field (destination) of the point record.
Up to eight alphanumeric characters can be used. The first character must be
a letter (A-Z.)
Frequency Represents the broadcast frequency of the point. The choices are:
S (S)low, F (F)ast, A (A)periodic
Note: Aperiodic points are b roadcast in special aperiodic Dynamic Data

Blocks (DDBs). These are b roadcast on the Ovation network b y
sub scription. When a point’s dynamic data is accessed from another drop,
that drop sends a request to the originator to start b roadcasting (once a
second) the DDB containing the point. These sub scriptions are renewed with
the sub sequent accesses. Once the sub scription runs out, the point (DDB) is
no longer b roadcast.
OPP Rate Defines the processing rate for alarm and limit checking of the point.
S (S)low, F (F)ast, A (A)periodic, U (U)ser
Point tab fields for Drop (DU) points
Characteristics Characteristics maps directly to the KR field of the point record, with the first
character mapping directly to the AY field (destination) of the point record.
Up to eight alphanumeric characters can be used. The first character must be
a letter (A-Z.)
Drop Number Number of the drop.
Partner Drop Number of the partner drop (if redundant).
180 OW351_60
Point tab fields for Algorithm (LC) points
Frequency The field represents the broadcast frequency of the point. The choice s are:

Point tab fields for Packed Digital (PD) points
Frequency The field represents the broadcast frequency of the point. The choices are:

OPP Rate The field defines the processing rate for alarm and limit checking of the point
S (S)low, F (F)ast, A (A)periodic, U (U)ser.
OW351_60 181
8.7.2 Config tab fie ld de scriptions
The Config tab window fields vary depending on the point type. The fields that apply to the
applicable point type(s) are described in the following tables.
Note: There is no Config tab for Drop (DU) or Pack ed Digital (PD) points.
Config tab fields for Analog points
The following tables list and describe the Config tab window fields for Long Analog and Deluxe
Analog point types.
Config tab fields for Long Analog (LA) points
Originating Sheet The field is reserved for Emerson use except in a node point. In a
node point, the signal diagram number is derived from this field.
New Alarm/Limit Configuration
Auto reset If the check box is selected, the point is automatically reset.
Auto acknowledge If the check box is selected, the point is automatically

acknowledged.
Simulation
Simulation Point Name Fully qualified point name of the simulation point that contains the
simulated value to be used for this point when in simulation mode.
Simulation Point SID SID of the point:
 SID of the simulation point, if it exists.
 For a remote point, the SID is stored if it can be retrieved from the
remote network.
Calculate Simulation Point SID Used to calculate or re-calculate the System ID (SID) of the
referenced simulation point.
Config tab fields for Deluxe Analog (DA) points
node point, the signal diagram number is derived from the field.
Simulation
remote network.
Calculate Simulation Point SID Used to calculate or re-calculate the point System ID (SID).
182 OW351_60
Config tab fields for Digital points
The following tables list and describe the Config tab window fields for Long Digital and Deluxe
Digital point types.
Config tab fields for Long Digital (LD) points
Inverted If checked, the value read from or written to the I/O cards is
inverted.
Reset Sum If checked, the reset sum is used. This maps directly to bit 2 of the
EQ field of the point record.
Status Checking type Determines the alarm state of each bit in the packed point that has a
bit set in the alarm group mask. The choices are
 No status checking
 Alarm on zero
 Alarm on one
 State change
 Alarm on 0 to 1 transition
 Alarm on 1 to 0 transition
Relay close delay time (msec) The field is used to set the relay close delay time, in milliseconds.
Oscillation count (counts/min) Indicates the number of oscillations allowed before the point enters
oscillation alarm. Must be a valid integer in the range 0 through
65,535.
Simulation
remote network.
Auto Reset If the Auto Reset bit is set, the point automatically resets.
Auto acknowledge If the Auto Acknowledge bit is set, the point is automatically
acknowledged.
Power Check
Power check enable Enables the power check.
Power check channel Used for the power check function.
OW351_60 183
Config tab fields for Deluxe Digital (DD) points
inverted.
Reset Sum If checked, the reset sum is used. This maps directly to bit 2 of the
EQ field of the point record.
Relay close delay time (msec) Sets the relay close delay time, in milliseconds.
Oscillation count (counts/min) Indicates the number of oscillations allowed before the point enters
65,535.
Simulation
remote network.

Summary Alarm Point Defines a summary alarm point that is used in multiple networks. A
summary point corresponds to a group of points that have been
defined to accommodate the large number of remote networks that
can be configured. When there is an alarm condition on a specific
network, the appropriate summary point is set into alarm.
Power Check
Power check channel Used for the power check function.
184 OW351_60
Config tab fields for Packed points
The following tables list and describe the Config tab window fields for Long Packed and Deluxe
Packed point types.
Config tab fields for Long Packed (LP) points
Oscillation Count (counts/min) Indicates the number of oscillations allowed before the point enters
65,535.
Alarm group mask Determines the bits of the packed point that alarm (0-15).
Alarm group bit sense Determines the alarm state of each bit in the packed point that has a
bit set in the alarm group mask (0-15).
inverted.
Simulation
remote network.

Auto Reset If the Auto Reset bit is set, the point automatically resets.
Auto acknowledge If the Auto Acknowledge bit is set, the point is automatically
acknowledged.
Power Check
Power check channel (bit 0 - bit Used for the power check function.
15)
OW351_60 185
Config tab fields for Deluxe Packed (DP) points
Oscillation Count (counts/min) Indicates the number of oscillations allowed before the point enters
65,535.
Inverted If checked, the value read from or written to the I/O cards is inverted.
Simulation
Simulation Point Name Fully qualified point name of the Simulation Point that contains the
simulated value to be used for this point when in s imulation mode.
remote network.
Power Check
Power check channel (bit 0 - bit 15) Used for the power check function.
Config tab fields for Algorithm points
The following tables list and describe the Config tab window fields for the Algorithm point type.
Config tab fields for Algorithm (LC) points
Originating Sheet Reserved for Emerson use except in a node point. In a node point,
the signal diagram number is derived from the field.
Tunable Defines whether or not the algorithm is tunable (0-1).
Tuning diagram Defines the number of the appropriate tuning diagram.
Algorithm name Represents the name of the algorithm.
186 OW351_60
Config tab fields for Module (RM) and Node (RN) points
The following tables list and describe the Config tab window fields for Module and Node point
types.
Config tab fields for Module (RM) and Node (RN) points
Int parameter (1 - 8) System-generated values for certain specialty I/O modules.
Real parameter 1
Real parameter 2
8.7.3 Se curity tab fie ld de scriptions
The Security tab allows you to define the security group for your points. The Security tab is the
same for all point types, and all point types have a Security tab.
Security tab fields for all points
Security group There are 32 possible point security groups in an Ovation system. A group is
inactive by default until it is activated by assigning a custom label or name to the
group. Once a group is labeled and activated, points can be assigned to the security
group. During the point building process, every Ovation point must be assigned to a
security group.
Refer to the Managing Security for Ovation manual for more information.
8.7.4 Ancillary tab fie ld de scriptions
The Ancillary tab allows you to define up to 100 fields to provide additional information about a
point. If desired, all point types can have an Ancillary tab.
The Ancillary tab on the Point Configuration dialog box is empty unless you first define the fields
at the Ancillary node at the Systems level. Once defined, these fields appear in the Point
Configuration dialog boxes.
See Defining Ancillary labels (see page 129) for more information.
OW351_60 187
8.7.5 Hardware tab fie ld de scriptions
The Hardware tab window fields vary depending on the point type. The fields that apply to the
Note: There is no Hardware tab for Algorithm (LC), Drop (DU), and Pack ed Digital (PD) points.
Hardware tab fields for Long Analog (LA), Deluxe Analog (DA) points
Hardware
I/O type Determines the I/O type of the point: Q-Line, Ovation (R-Line), third-party
(device), or Null if the point is not an I/O point.
I/O module Indicates the specific I/O card where the point is attached (IOIC, Local Q-
line, Remote Q-Line).
I/O channel Used to specify the channel of the appropriate I/O module (1 -16).
I/O task index Represents the processing task index used by the Controller. Points that
are assigned to a digital output module must have an identical task index
value for every point on the same module (1-4).
I/O module units Describes the units of the I/O card at the card level.
Refer to the appropriate Ovation Controller User Guide for more information about the Hardware
tab.
Hardware tab fields for Long Digital (LD), Deluxe Digital (DD) points
Hardware
I/O type Determines the I/O type of the point: Q-Line, Ovation (R-Line), third-party
(device) or Null if the point is not an I/O point.
I/O module Indicates the specific I/O card where the point is attached (IOIC, Local Q-
line, Remote Q-Line).
I/O channel Used to specify the channel of the appropriate I/O module (1-16).
I/O task index Represents the processing task index used by the Controller. Points that are
assigned to a digital output module must have an identical task index value
for every point on the same module (1-4).
SOE
SOE point If the check box is checked, it indicates that the point is an SOE point.
SOE 1 shot enable If the check box is checked, it indicates that the point is an SOE one shot
point.
188 OW351_60
SOE reporting option Determines what should trigger an SOE event:

 State Change.
 0 to 1 Transition.
 1 to 0 Transition.
Note: The 0 to 1 Transition and 1 to 0 Transition options only apply to

SOE one shot points.
For digital points, all points assigned to the same SOE module must be assigned to the same task
index and that task must be 100ms or faster.
Hardware tab fields for Long Packed (LP), Deluxe Packed (DP) points
Hardware
IO task index Represents the processing task index used by the Controller. Points
that are assigned to a digital output module must have an identi cal task
index value for every point on the same module (1-4).
Register to Register Pull down menu that describes the register to register mapping. The
Mapping choices are:
 Off -- No register to register mapping is used.
 CH 1 - 16 -- Use the first 16 bits of the module.
 CH 17 - 32 -- Use the second 16 bits of the module.
Bit 0 *
IO type Determines the I/O type of the point: Q-Line, Ovation (R-Line), third-
party (device) for Bit 0. Null if the point is not an I/O point.
IO module Indicates the specific I/O card where the point is attached (IOIC, Local
Q-line, Remote Q-Line) for Bit 0.
IO channel Used to specify the channel of the appropriate I/O module (1 -16) for Bit
0.
* Repeat parameters for Bits 1 - 15.
Hardware tab fields for Module (RM) and Node (RN) points
Hardware
I/O module Indicates the specific I/O card where the point is attached (IOIC, Local
Q-line, Remote Q-Line).
I/O task index Represents the processing task index used by the Controller. Points
that are assigned to a digital output module must have an identical task
index value for every point on the same module (1-4).
OW351_60 189
8.7.6 Initial tab fie ld de scriptions
The Initial tab window fields vary depending on the point type. The fields that apply to the
applicable point type(s) are described in the tables
Note: There is no Initial tab for Algorithm (LC), Drop (DU), Module (RM), and Node (RN) points.
Initial tab fields for Long Analog (LA) and Deluxe Analog (DA) points
Initial Conditions:
Value Establishes the initial first pass value of the point.

Initial status
Tagout Establishes the initial tagout state of each bit for the point. Also valid for analog
and digital points.
Uncommissioned Establishes the uncommissioned s tate of each bit for the point. Also valid for
analog and digital points.
Periodic save Represents whether or not the value of the point should be periodically saved to
flash.
Initial tab fields for Long Digital (LD) and Deluxe Digital (DD) points
Initial status:
and digital points.
Uncommissioned Establishes the uncommissioned state of each bit for the point. Also valid for
analog and digital points.
flash.
Initial Conditions:
Value Establishes the initial first pass value of the point. The choices are: None, 0, or 1.
190 OW351_60
Initial tab fields for Long Packed (LP) and Deluxe Packed (DP) points
Initial status:
and digital points (0-15).
Uncommissioned Establishes the uncommissioned state of each bit for the point. Also valid for
analog and digital points (0-15).
flash.
Bit 0 *
Value Establishes the initial first pass value of the point. The choices are: None, 0, or 1.
* Repeat parameter for Bits 1 - 15.
Initial tab fields for Packed Digital (PD) points
Value Establishes the initial first pass value of the point (0 - 15).
OW351_60 191
8.7.7 Alarm tab fie ld de scriptions
The Alarm tab window fields vary depending on the point type. The fields that apply to the
applicable point type(s) are described in the following tables.
Note: There is no Alarm tab for Algorithm (LC) or Pack ed Digital (PD) points.
Alarm tab fields for Long Analog and Deluxe Analog points
The following tables list and describe the Alarm tab window fields for Long Analog and Deluxe
Analog point types.
Alarm tab fields for Long Analog (LA) points
Normal
Alarm delay time (sec.) The Alarm delay time field sets the initial alarm delay time, in seconds.
The delay is the time between the alarm being detected (a 0 bit going to a
1 or true) and being reported in alarm.
Valid time entry is from 0 to 65,535 seconds. This field does not apply to
sensor alarms since the alarms never delay or cutout from reporting.
Alarm return delay time (sec) Defines the amount of time, in seconds, that a point will be delayed from
returning from the alarm state after it has reached normal limits (that is,
how long the system waits to take the point out of alarm after it has
returned to normal). Valid time entry is from 0 to 65,535 seconds. This
time will be in seconds and will be valid from 0 to 65,535. The default is
blank or 0, which indicates that there is no delay.
Cutout
Alarm cutout delay time (sec) Sets the alarm cutout delay time, in seconds. The delay is the time after
the cutout is released before the alarm is actually reported.
Alarm cutout name Name of the point (digital or packed) used for the alarm cutout function. Its
current value (0 or 1) sets or releases the cutout function for the process
point. The name should not be fully qualified, since the Developer Studio
was not designed to support a fully-qualified point reference that includes
the Network Alias.
Treat packed alarm cutout as Identifies the cutout point as a packed point whose value field (A2) is
a bit mask treated as a bit mask. This determines the individual analog limit to cut out
rather than using a specific bit number to cut out the entire analog point.
This option is available only for analog points. For example, A2 Bit 0 will
cut out High 1 analog limit. A2 Bit 1 will cut out High 2 analog limit.
Alarm cutout bit If alarm cutout is a packed point, the bit number that is entered in the field
is mapped to bits 28-32 of the SJ field. The current bit value sets or
releases the cutout function for the process point (0-15).
Alarm cutout on zero If this is checked, the cutout point cuts out the process point if the cutout
point value or designated bit value is zero. If this is not checked, the
cutout point cuts out the process point if the cutout point value or
designated bit value is one.
Cutout sensor alarm Determines whether or not the alarm cutout will inhibit sensor alarms.
192 OW351_60
Priorities: Analog points can have up to five different high and five different low
priorities (the priority may be from 1-8, where 1 is the most critical alarm).
The priority should be defined only if the corresponding limit is defined:
that is, High Limit 1-4 and High User Alarm, and Low Limit 1-4 and Low
User Alarm.
Sensor and SID alarms use the highest value from all of the defined
priorities; returns use the lesser value of all defined priorities.
Low alarm priority 1-4 Maps to the various alarm priority fields of the point record (1 -8 AP, P6-8).
Low alarm user priority Maps to the alarm priority field of the point record (P9).
High alarm priority 1-4 Maps to the various alarm priority fields of the point record (1-8 AP, P6-8).
High alarm user priority Maps to the alarm priority fields of the point record (P9).
Alarm Check/Limit Check Remove
Disable Alarm Check/Limit Disables the Alarm Check and Limit Check On/Off operations on a point-
Check Remove by-point basis. This check box gets translated into the LM record field. If
the check box is selected, bit 0 of the LM field is set on; otherwise, it is off.
If bit 0 of the LM field is on, the Alarm Check/Limit Check On/Off o peration
is disabled for the specific point.
Annunciation
Alarm Annunciation Text (only Identifies the point that is in alarm. The alarm message boxes in the Alarm
appropriate if alarm Annunciator alarm bands display two lines of text (up to 12 characters per
annunciator is used) line), for a total of 24 characters.
You can separate the two lines of text by using a vertical bar ("|") as a line
delimiter. This bar does not count toward the 12 characters in the line.
For example, if you enter FD FAN AA|AIR FLOW, it appears in the
alarm message box as:
FD FAN AA
AIR FLOW
If you do not use the line delimiter, the first 12 characters are used for line
one and any additional characters are used for line two.
Description
Alarm Description A text description of the alarm (maximum string of 45 characters).

Alarm Guidance
Alarm Guidance 1 These five Alarm Guidance fields, which can accommodate 80 bytes per
field, contain the alarm guidance information. In these fields, you can
Alarm Guidance 2 provide a description of possible corrective actions or causes of the
situation. These fields are optional and can be left blank.
Alarm Guidance 3
Alarm Guidance 4
Alarm Guidance 5
OW351_60 193
Alarm tab fields for Deluxe Analog (DA) points
Normal
The delay is the time between the alarm being detected (a 0 bit going to
a 1 or true) and being reported in alarm.
Valid time entry is from 0 to 65535 seconds. This field does not apply to
sensor alarms since the alarms never delay or cutout from reporting.
Alarm return delay time (sec) Defines the amount of time, in seconds, that a point will be delayed from
returning from the alarm state after it has reached normal limits (that is,
how long the system waits to take the point out of alarm after it has
returned to normal). Valid time entry is from 0 to 65,535 seconds. This
time will be in seconds and will be valid from 0 to 65,535. The default is
blank or 0, which indicates that there is no delay.
Priorities
Low alarm user priority Maps to the alarm priority field of the point record (P9).
High alarm user priority Maps to the alarm priority fields of the point record (P9).
Alarm Check/Limit Check Remove

Disable Alarm Check/Limit Disables the Alarm Check and Limit Check Remove operations on a
Check Remove point-by-point basis. This check box is translated into the LM record
field. If the check box is selected, bit 0 of the LM field is set on;
otherwise, it is off. If bit 0 of the LM field is on, the Alarm Check/Limit
Check Remove operation is disabled for the specific point.
Annunciation
Alarm Annunciation Text This text identifies the point that is in alarm. The alarm message boxes
(only appropriate if alarm in the Alarm Annunciator alarm bands display two lines of text (up to 12
annunciator is used) characters per line) for a total of 24 characters.
You can separate the two lines of text by using a vertical bar ("|") as a
line delimiter. This bar does not count toward the 12 characters in the
line.
FD FAN AA
AIR FLOW
line one and any additional characters are used for line two.
Description
Alarm Guidance
Alarm Guidance 1 These five Alarm Guidance fields, which can accommodate 80 bytes
per field, contain the alarm guidance information. In these fields, you
Alarm Guidance 2 can provide a description of possible corrective actions or causes of the
Alarm Guidance 3 situation. These fields are optional and can be left blank.
Alarm Guidance 4
Alarm Guidance 5
194 OW351_60
Alarm tab fields for Long Digital and Deluxe Digital points
The following tables list and describe the Alarm tab window fields for Long Digital and Deluxe
Digital point types.
Alarm tab fields for Long Digital (LD) points
Normal
Alarm delay time (sec.) The Alarm delay time field sets the initial alarm delay time, in
seconds. The delay is the time between the alarm being detected (a
0 bit going to a 1 or true) and being reported in alarm.
Valid time entry is from 0 to 65,535 seconds. This field does not
apply to sensor alarms since the alarms never delay or cutout from
reporting.
Alarm return delay time (sec) Defines the amount of time, in seconds, that a point will be delayed
from returning from the alarm state after it has reached normal limits
(that is, how long the system waits to take the point out of alarm
after it has returned to normal). Valid time entry is from 0 to 65,535
seconds. This time will be in seconds and will be valid from 0 to
65,535. The default is blank or 0, which indicates that there is no
delay.
Cutout
Alarm cutout delay time (sec) Sets the alarm cutout delay time, in seconds. The delay is the time
after the cutout is released before the alarm is actually reported.
Alarm cutout name Name of the point (digital or packed) used for the alarm cutout
function. Its current value (0 or 1) sets or releases the cutout
function for the process point. The name should not be fully
qualified, since the Developer Studio was not designed to support a
fully-qualified point reference which includes the Network Alias
Alarm cutout bit If alarm cutout is a packed point, the bit number that is entered in
the field is mapped to bits 28-32 of the SJ field. The current bit value
sets or releases the cutout function for the process point (0 -15).
Alarm cutout on zero If this is checked, the cutout point cuts out the process point if the
cutout point value or designated bit value is zero. If this is not
checked, the cutout point cuts out the process point if the cutout
point value or designated bit value is one.
Cutout sensor alarm Determines whether or not the alarm cutout will inhibit sensor
alarms.
Priorities: Digital points can have up to five different high and five different low
priorities, (the priority may be from 1-8, where 1 is the most critical
alarm.
The priority should be defined only if the corresponding limit is
defined: that is, High Limit 1-4 and High User Alarm, and Low Limit
1-4 and Low User Alarm.
Alarm Priority Priority of the point. The priority may be from 1-8, where 1 is the
most critical alarm.
OW351_60 195
Alarm Check
otherwise, it is off. If bit 0 of the LM field is on, the Alarm
Check/Limit Check Remove operation is disabled for the specific
point.
Annunciation
Alarm Annunciation Text (only This text identifies the point that is in alarm. The alarm message
appropriate if alarm annunciator boxes in the Alarm Annunciator alarm bands display two lines of text
is used) (up to 12 characters per line) for a total of 24 characters.
You can separate the two lines of text by using a vertical bar ("|") as
a line delimiter, this bar does not count toward the 12 characters in
the line.
For example, if you enter FD FAN AA|AIR FLOW, it appears in
the alarm message box as:
FD FAN AA
AIR FLOW
If you do not use the line delimiter, the first 12 characters are used
for line one and any additional characters are used for line two.
Description

Alarm Guidance
Alarm Guidance 1 These five Alarm Guidance fields, which can accommodate 80
bytes per field, contain the alarm guidance information. In these
Alarm Guidance 2 fields, you can provide a description of possible corrective actions or
Alarm Guidance 3 causes of the situation. These fields are optional and can be left
blank.
Alarm Guidance 4
Alarm Guidance 5
196 OW351_60
Alarm tab fields for Deluxe Digital (DD) points
Normal
The delay is the time between the alarm being detected (a 0 bit g oing
to a 1 or true) and being reported in alarm.
Valid time entry is from 0 to 65535 seconds. The field does not apply
to sensor alarms since the alarms never delay or cutout from
reporting.
Alarm return delay time (sec) Defines the amount of time, in s econds, that a point will be delayed
(that is, how long the system waits to take the point out of alarm after it
has returned to normal). Valid time entry is from 0 to 65,535 seconds.
This time will be in seconds and will be valid from 0 to 65,535. The
default is blank or 0, which indicates that there is no delay.
Alarm Check
Annunciation
Alarm Annunciation Text (only This text identifies the point that is in alarm. The alarm message boxes
appropriate if alarm annunciator in the Alarm Annunciator alarm bands display two lines of text (up to
is used) 12 characters per line) for a total of 24 characters.
line delimiter, this bar does not count toward the 12 characters in the
line.
FD FAN AA
AIR FLOW
Description

Alarm Guidance
Alarm Guidance 2 can provide a description of possible corrective actions or cau ses of
Alarm Guidance 3 the situation. These fields are optional and can be left blank.
Alarm Guidance 4
Alarm Guidance 5
OW351_60 197
Alarm tab fields for Long Packed and Delux e Packed points
The following tables list and describe the Alarm tab window fields for Long Packed and Deluxe
Packed point types.
Alarm tab fields for Long Packed (LP) points
Normal
Alarm delay time (sec.) The Alarm delay time field s ets the initial alarm delay time, in seconds.
The delay is the time between the alarm being detected (a 0 bit going
Valid time entry is from 0 to 65,535 seconds. The field does not apply
reporting.
has returned to normal). Valid time entry is from 0 to 65535 seconds.
This time will be in seconds and will be valid from 0 to 65535. The
default is blank or 0, which indicates that there is no delay.
Cutout
Alarm cutout delay time (sec) Sets the alarm cutout delay time, in seconds. The delay is the time
after the cutout is released before the alarm is actually reported.
Alarm cutout name Name of the point (digital or packed) used for the alarm cutout
function. Its current value (0 or 1) sets or releases the cutout function
for the process point. The name should not be fully qualified, since the
Developer Studio was not designed to support a fully-qualified point
reference which includes the Network Alias
Alarm cutout bit If alarm cutout is a packed point, the bit number that is entered in the
field is mapped to bits 28-32 of the SJ field. The current bit value sets
or releases the cutout function for the process point (0-15).
Alarm cutout on zero If this is checked, the cutout point cuts out the process point if the
cutout point value or designated bit value is zero. If this is not
checked, the cutout point cuts out the process point if the cutout point
value or designated bit value is one.
Cutout sensor alarm Determines whether or not the alarm cutout will inhibit sensor alarms.
Priorities: Long Packed points can have up to five different high and five different
low priorities (the priority may be from 1-8, where 1 is the most critical
alarm).
The priority should be defined only if the corresponding limit is defined
(that is, High Limit 1-4 and High User Alarm, and Low Limit 1-4 and
Low User Alarm).
Alarm Priority Priority of the point. The priority may be from 1-8, where 1 is the most
critical alarm.
198 OW351_60
Alarm Check
Check Remove point- by-point basis. This check box is translated into the LM record
Annunciation
Alarm Annunciation Text (only This text identifies the point that is in alarm. The alarm message
appropriate if alarm annunciator boxes in the Alarm Annunciator alarm bands display two lines of text
is used) (up to 12 characters per line) for a total of 24 characters.
line.
FD FAN AA
AIR FLOW
Description
Alarm Guidance
Alarm Guidance 2 can provide a description of possible corrective actions or causes of
Alarm Guidance 4
Alarm Guidance 5
OW351_60 199
Alarm tab fields for Deluxe Packed (DP) points
Normal
The delay is the time between the alarm being detected (a 0 bit going
Valid time entry is from 0 to 65535 seconds. The field does not apply
reporting.
from returning from the alarm state after it has reached normal lim its
has returned to normal). Valid time entry is from 0 to 65535 seconds.
The default is blank or 0, which indicates that there is no delay.
Alarm Check
Disable Alarm Check/Lim it Disables the Alarm Check and Limit Check Remove operations on a
Check Remove point- by-point basis. This check box is translated into the LM record
Annunciation
line.
FD FAN AA
AIR FLOW
Description

Alarm Guidance
the situation. These fields are optional and can be left blank.
Alarm Guidance 3
Alarm Guidance 4
Alarm Guidance 5
200 OW351_60
Alarm tab fields for Drop points
The following tables list and describe the Alarm tab window fields for the Drop point type.
Alarm tab fields for Drop (DU) points
Priorities: Drop points can have up to five different high and five different low
priorities (the priority may be from 1-8, where 1 is the most critical
alarm).
Low User Alarm).
critical alarm.
Annunciation
line.
FD FAN AA
AIR FLOW
Description
Alarm Guidance
Alarm Guidance 4
Alarm Guidance 5
OW351_60 201
Alarm tab fields for Module and Node points
Alarm tab fields for Module (RM) and Node (RN) points
Priorities: Module and Node points can have up to five different high and five
different low priorities (the priority may be from 1-8, where 1 is the
most critical alarm).
Low User Alarm).
priorities; returns use the lesser value of all defined priorities .
critical alarm.
Alarm Check
Annunciation
line delimiter, this bar does not count toward the 12 characters in the
line.
FD FAN AA
AIR FLOW
Description
Alarm Guidance
Alarm Guidance 3 the situation. Thes e fields are optional and can be left blank.
Alarm Guidance 4
Alarm Guidance 5
202 OW351_60
8.7.8 Instrume ntation tab fie ld de scriptions
The Instrumentation tab parameters are described in the following table. The Instrumentation tab
is ONLY available for Long Analog (LA) and Deluxe Analog (DA) points.
Instrumentation tab fields for Long Analog (LA) and Deluxe Analog (DA) points
Scaling
Bottom output scale Used to linearly convert the value to the card output level.
Top output scale Used to linearly convert the value to the card output level.
Sensor
Low sensor limit Indicates the low limit of the signal’s operating range.
High sensor limit Indicates the high limit of the signal’s operating range.
Low sensor deadband range Maps to the BL field of the point record. Indicates the low sensor
deadband range.
High sensor deadband range Maps to the BH field of the point record. Indicates the high sensor
deadband range.
Low operating range ** Performs conversion coefficient calculation and checking.
High operating range ** Performs conversion coefficient calculation and checking.

Field transmitter low value ** Indicates the low limit of the transmitter’s operating range.
Field transmitter high value ** Indicates the high limit of the transmitter’s operating range.
Signal conditioner value Defines a signal conditioner value that can be used to allow milliamp
type sensors to be read by volt cards.
** For the Ovation 3.5.0 (or later) release, you do not have to specify the high/low operating and
high/low transmitter ranges for thermocouple inputs (applicable conversion type is fifth order) since they
are not utilized in the generation of the conversion coefficient values b y the Coefficient Calculation
operation.
OW351_60 203
Conversion
Field transmitter type The field identifies the field transmitter type for use in standard
thermocouple conversions. If the field is specified, and the individual
conversion coefficient fields are not specified, the conversion coefficient
fields are automatically assigned based on the thermocouple units. The
conversion type is set to the P5 field. If the field is not specified, the
conversion type must be specified individually.
B or TB = 70% Platinum + 30% Rhodium or
94% Platinum + 6% Rhodium
E or TE = Chromel/Constantan
J or TJ = Iron/Constantan
K or TK = Chromel/Alumel
R or TR = Platinum+13% Rhodium
S or TS = Platinum+10% Rhodium
T or TT = Copper/Constantan
HZ = Hertz
MV = Millivolts
VT = Volts
RC = Copper
PU = Pulse
MA = Milliamps
RP = Platinum
RN = Platinum
Transmitter temperature units Identifies the temperature units used for conversion coefficient
calculation based on known field transmitter types (F=Fahrenh eit or
C=Celsius).
Disable auto coefficient This Boolean, when set, indicates that you have modified the
update conversion coefficients from their calculated values (that is, by way of
the Sensor Calibration application) and do NOT want the system to
recalculate these values (check box.)
Conversion Type Identifies the type of equation to be used for conversion to engineering
units (See Notes 0-5 below).
 X=Y
 Linear
 5th Order
 Square Root
 Exponential
 Square Root of 5th Order
Conversion Coefficient (1-6) If the field _transmitter_ type and thermocouple unit fields are specified,
these conversion coefficient fields are assigned automatically based on
a table lookup. Otherwise, the fields can be specified individually.
204 OW351_60
Cold Junction Compensation
CJ compensation name Identifies the point name providing the cold-junction compensation
value for the point being configured.
CJC temperature units Used for cold-junction compensation conversion.
CJC conversion Maps directly to field 7V of the point record and are used for cold
coefficient 1 junction compensation.
CJC conversion Maps directly to field 8V of the point record and are used for cold
coefficient 2 junction compensation.
Notes:
0 - Y = X- Linear
1 - Y = {1V}X + {2V} - Linear
2 - Y = {1V} + {2V}X + {3V}X2 + {4V}X3 +{5V}X4 + {6V}X5 Fifth Order Polynomial
3 - Y = {1V} [SQRT (X + {2V})] + {3V}Square Root
4 - Y = {1V}[EXP ({2V}X)] + {3V}Exponential
5 - Y = SQRT (Fifth Order Polynomial Y, as defined for Entry 2) SQRT of Fifth Order Polyno mial
The variab les used in the equations are defined as follows:
X = Original input value that is converted to Y (engineering units) b y the specified type of conversion.
Y = Final, converted value of the analog input.
C1 - C6 = Conversion coefficients.
OW351_60 205
8.7.9 Limits tab fie ld de scriptions
The Limits tab parameters are described in the table below. The Limits tab is ONLY available for
Long Analog (LA) and Deluxe Analog (DA) points.
Note: Calculated limits can exist for low limits, high limits, user limits, incremental, and
deadband.
Limits tab fields for Long Analog (LA) points
Low Limits
Low clamp limit Low Value Clamp Limit - 32-bit real number. The field maps directly to the VL
field of the point record.
Used to clamp the analog value above this limit. Clamping is when the point's
engineering unit value is limited (clamped). Applicable to hardware inputs only.
High Limits
High clamp limit High Value Clamp Limit - 32-bit real number. The field maps directly to the VH
Used to clamp the analog value below this limit. Clamping is when the point's
Low Limits
Low engineering limit Engineering Low Limit - 32-bit real number. The field maps directly to the EL
Used by the limit checking routine associated with the Originated Point
Processor (OPP).
High Limits
High engineering limit High Engineering Limit - 32-bit real number. The field maps directly to EH field
of the point record.
Processor (OPP).
Low Limits
Low reasonability limit Low Reasonability Limit - 32-bit real number. The fields map directly to the RW
Processor (OPP).
Analog points can have a high/low engineering range limit and a high/low
reasonability limit. These limits can be defined as a value o nly.
Engineering range limits and the reasonability limits do not generate alarms.
When a point exceeds the engineering range limit, the point quality is set to
(P)oor. When a point exceeds the reasonability limit, the point quality is set to
(B)ad. The high/low deadbands defined for the high/low alarm limits described
above also apply to these limits.
These fields map directly to the LL, ZL, 3Z, and 4Z of the point record.
206 OW351_60
High Limits
High reasonability High Reasonability Limit - 32-bit real number. The field maps directly to the RV
limit field of the point record.
Processor (OPP).
Analog points can have a high/low engineering range limit and a high/low
reasonability limit. These limits can be defined as a value only.
Engineering range limits and reasonability limits do not generate alarms. When
a point exceeds the engineering range limit, the point quality is set to (P)oor.
When a point exceeds the reasonability limit, the point quality is set to (B)ad.
The high/low deadbands defined for the high/low alarm limits described above
apply also to these limits.
Low Limits
Low alarm limit (1-4) Low Alarm Limit (1 - 4) - 32-bit real number. Limits 1 - 4 map to the LL, ZL, 3Z,
and 4Y fields of the point record respectively.
Processor (OPP).
May be a real value or analog SID.
Low alarm limit user Low Alarm Limit #4 - 32-bit real number. The field maps directly to the UL field
Processor (OPP).
Analog points can have two user-defined alarms; one high and one low. The
limits may be either a value or the name of another analog point in the system.
These alarms are independent of the four high and four low alarms. The
high/low deadbands defined for the four high/low alarms apply to these user
limits also. Exceeding these alarms generates an alarm message.
A separate alarm priority can be defined for the high and low user defined
alarms.
Low alarm limit Low Alarm Incremental Limit - 32-bit real number. The field maps directly to the
incremental ZM field of the point record.
Used to add more low alarm limits above the lowest defined limit.
Processor (OPP).
Low normal operating Low Operating Range 32-bit real number. Initialized by Power Tools.
range limit
Note: The low normal operating range limit is used for the High Performance
Analog Indicator.
OW351_60 207
Deadbands
Low alarm deadband Low Alarm Deadband - 32-bit real number. The field maps directly to the DJ
Deadband for Low Alarm Limits 1, 2, 3, and 4 and Low User Defined Limit.
Processor (OPP).
If the current value of a point is oscillating near an alarm limit, this value
prevents the point from going into and out of alarm:
 A positive value indicates the deadband is the actual value of DB.
 A negative value indicates the deadband is a percentage of the corresponding
alarm limit.
High Limits
High alarm limit (1-4) High Alarm Limit #1 - 32-bit real number. High limits 1 - 4 map directly to the
HL, ZH, 3Y, and 4Y fields of the point record respectively.
Processor (OPP).
High alarm limit user High User Defined Alarm Limit - 32-bit real number. The field maps directly to
the UH field of the point record.
Processor (OPP).
High alarm limit High Alarm Incremental Limit - 32-bit real number. The field maps directly to the
incremental ZI field of the point record.
Used to add more high alarm limits above the highest defined limit.
Processor (OPP).
High normal operating High Operating Range 32-bit real number. Initialized by Power Tools.
range limit
Note: The high normal operating range limit is used for the High Performance
Analog Indicator.
208 OW351_60
Deadbands
High alarm deadband High Alarm Deadband - 32-bit real number. The field maps directly to the DB
Deadband for High Alarm Limits 1, 2, 3, and 4 and High User Defined Limit.
Processor (OPP).
alarm limit.
Limits tab fields for Deluxe Analog (DA) points
Low Limits
Low clamp limit Low Value Clamp Limit - 32-bit real number. The field maps directly to the VL
Used to clamp the analog value above this limit. Clamping is when the point's
High Limits
High clamp limit High Value Clamp Limit - 32-bit real number. The field maps directly to the VH
Used to clamp the analog value below this limit. Clamping is when the point's
Low Limits
Low engineering limit Engineering Low Limit - 32-bit real number. The field maps directly to the EL
Processor (OPP).
High Limits
High engineering limit High Engineering Limit - 32-bit real number. The field maps directly to EH field
Processor (OPP).
OW351_60 209
Low Limits
Low alarm limit user Low Alarm Limit #4 - 32-bit real number. The field maps directly to the UL field
Processor (OPP).
Analog points can have two user-defined alarms; one high and one low. The
limits may be either a value or the name of another analog point in the system.
These alarms are independent of the four high and four low alarms. The
high/low deadbands defined for the four high/low alarms apply to these user
limits also. Exceeding these alarms generate an alarm message.
A separate alarm priority can be defined for the high and low user defin ed
alarms.
Deadbands
Low alarm deadband Low Alarm Deadband - 32-bit real number. The field maps directly to the DJ
Deadband for Low Alarm Limits 1, 2, 3, and 4 and Low User Defined Limit.
Processor (OPP).
alarm limit.
High Limits
High alarm limit user High User Defined Alarm Limit - 32-bit real number. The field maps directly to
the UH field of the point record.
Processor (OPP).
Deadbands
High alarm deadband High Alarm Deadband - 32-bit real number. The field m aps directly to the DB
Deadband for High Alarm Limits 1, 2, 3, and 4 and High User Defined Limit.
Processor (OPP).
alarm limit.
210 OW351_60
8.7.10 Display tab fie ld de scriptions
The Display tab window fields vary depending on the point type. The fields that apply to the
Note: There is no Display tab for Algorithm (LC) points.
Display tab fields for Long Analog (LA) and Deluxe Analog (DA) points
Engineering Units Text description of the engineering units.

Summary Diagram Defines the appropriate summary diagram that is sent to the process
diagram system.
Signal Diagram Defines the signal diagram number.
Minimum Scale Scales the value of the point for display.
Maximum Scale Scales the value of the point for display.
Display Type Represents the type of display. The choices are Standard, Exponential,
and Technical).
Digits Displayed Represents the number of significant digits to display for Standard
format.
Display tab fields for Long Digital (LD) and Deluxe Digital (DD) points
Time of scan format Only displays for Deluxe Digital (DD) points. Defines how the scan time
will be measured. The choices are Nanosecond, Microsecond,
Millisecond, Second, and Minute.
Set description Text description of the set state.
Reset description Text description of the reset state.
diagram system.
OW351_60 211
Display tab fields for Long Packed (LP), and Deluxe Packed (DP) points
Group Number
Note: Group Numb er is only for LP and DP points.
Identifies the packed group number for packed and deluxe packed points.
The value range is between 0 and 65,539.
If the defined group number for the packed point is greater than 0, the
value field and the bits in the alarm field display as a configured text
string, rather than as a binary or hexadecimal representation of the bits.
For more information see What are Packed Group Numbers? (see page
219)
Note: If the group numb er value is 0, it implies that the packed point
does not have a packed group identified, and the value field and b its in
alarm field display as a b inary and hexadecimal representation of the
b its.
Time of scan format Only displays for Deluxe Digital (DD) points. Defines how the scan time
will be measured. The choices are Nanosecond, Microsecond,
Millisecond, Second, and Minute.
diagram system.
Bit 0 **
Set Description, bit 0 Text description of the set state for bit 0.
Reset Description, bit 0 Text description of the reset state for bit 0.
Description, bit 0 Text description for bit 0.
** Repeat these parameters for Bits 1 - 15.
Display tab fields for Module (RM), and Node (RN) points
Time of scan format Only displays for Deluxe Digital (DD) points. Defines how the scan time will
be measured. The choices are Nanosecond, Microsecond, Mi llisecond,
Second, and Minute.
diagram system.
Bit 0 **
Set Description, bit 0 Text description of the set state for bit 0.
Reset Description, bit 0 Text description of the reset state for bit 0.
Description, bit 0 Text description for bit 0.
** Repeat these parameters for Bits 1 - 15.
212 OW351_60
Display tab fields for Drop (DU) and Packed Digital (PD) points
diagram system.
8.7.11 Plant M ode tab fie ld de scriptions
The Plant Mode tab window fields vary depending on the point type. The fields that apply to the
Note: The Plant Mode tab is only applicable to Deluxe Analog (DA), Deluxe Digital (DD), and
Deluxe Pack ed (DP) points.
Plant Mode tab fields for Deluxe Analog (DA) points
T AB F I EL D FI E L D D E S C R I P TI O N
Auto reset These fields are the same as the ones previously described in the
Deluxe Analog Alarm (see page 192), Config (see page 182), and
Auto acknowledge Limit tabs. If Plant Modes are used, each parameter must be
defined for each Plant Mode (1-6) used in the system.
Low alarm priority (1 - 4)
Low alarm limit (1 - 4)
Low alarm limit incremental
Low reasonability limit
Alarm cutout delay time (sec)
Alarm cutout name
Alarm cutout bit
Alarm cutout on zero
Cutout sensor alarm
High alarm priority (1 - 4)
High alarm limit (1 - 4)
High alarm limit incremental
High reasonability limit
OW351_60 213
Plant Mode tab fields for Deluxe Digital (DD) points
Deluxe Digital Alarm (see page 195) and Config (see page 183)
Auto acknowledge tabs. If Plant Modes are used, each parameter must be defined for
each Plant Mode (1-6) used in the system.
Alarm priority (1 - 8)
Alarm cutout name
Alarm cutout bit
Cutout sensor alarm
Status checking type
Plant Mode tab fields for Deluxe Packed (DP) points
Deluxe Packed Alarm (see page 198) and Config (see page 184)
Auto acknowledge tabs. If Plant Modes are used, then each parameter must be
defined for each Plant Mode (1-6) used in the system.
Alarm priority (1 - 8)
Alarm cutout name
Alarm cutout bit
Alarm group mask (0 - 15)
Alarm group bit sense (0 - 15)
214 OW351_60
8.8 What are PDS Point Groups?
8.7.12 Byte , Int., Re al, and ASCII Params tab fie ld de scriptions
The Byte, Int., Real, and ASCII Params tabs are only used with Algorithm (LC) points. The fields
that display in these tabs are dependent on the type of algorithm that is associated with the LC
point. The information that is entered into these fields reflects the information that was entered in
the Control Builder's Property Editor.
For more information, refer to the following manuals:
 Ovation Standard Algorithms Reference Manual

 Ovation Q-Line and Specialty Algorithms Reference Manual
 Ovation Control Builder User Guide
8.8 What are PDS P oint Groups?
Point groups are various points grouped together for process diagram purposes. You can add
point groups through the Developer Studio or through your Ovation import file from the system.
Members are points included in the point group.
The Point Groups folder is located in the Systems folder in the system tree. Point groups are
distributed to all Ovation Windows type drops. Point groups have configurable items at the group
level and the member level.
PDS Point Groups allow generic graphics to be created that do not hard code points, but rather
reference points via the point group.
The new point groups or members are added (or edited) online; therefore, the changes take effect
immediately and are automatically distributed to the Operator Stations for inclusions in their
distributed databases.
For information about adding points to the system, see Adding points in the Ovation Developer
Studio (see page 169).
8.8.1 T o add a ne w PDS Point Group
Use the following steps to add a new PDS Point Group:

2. Use the system tree to navigate to the PDS Point Groups folder:
Systems -> Point Groups -> PDS Point Groups item
3. Right-click the PDS Point Groups folder.
4. Select Insert New. The Insert New PDS Point Groups Wizard appears.
5. Enter the PDS group name in the Group Name field, using up to 30 characters.
6. Enter a group number (to define the group) in the Group Number field. The group number is
used to identify group information. A maximum of 5,000 groups can be defined.
Note: If a group number is outside the range of 1 to 5,000, a warning box appears and the
group is not added. If the group number currently exists, a warning box appears when you try to
add the group number to the database.
OW351_60 215
7. Select Finish. The New PDS Point Groups dialog box appears:
Figure 110: PDS Point Groups dialog box
PDS Point Groups dialog box fields
Group Number Number of the group. Valid range is 1 - 5000. Defaults from information
entered in the New PDS Point Groups Wizard.
Group Title Title of the group (up to 30 characters).
String 1 Optional text that describes the point group.
Text group number Used for attaching additional text strings to the point group. Valid range is 0 to
5000. Each text group can have up to 100 text strings.
Diag number Displays the number of the diagram to be loaded when the point group is
loaded.
Up group Group number(s) associated with the paging group. Enter an integer from 0 to
1,000.
Down group Group number(s) associated with the paging group. Enter an integer from 0 to
1,000.
Right group Group number(s) associated with the paging group. Enter an integer from 0 to
1,000.
Left group Group number(s) associated with the paging group. Enter an integer from 0 to
1,000.
8. Enter the title of the PDS group in the Group Title field, using up to 30 characters.
9. Enter optional text in the String fields that describes the point group.
216 OW351_60
10. You can attach additional text strings to the point group when you display diagrams. The Text
Group Number field allows you to do this by entering values into this field. A range of 0 to
5000 is valid for text group numbers and each text group can have up to 100 text strings.
Note: Additional information on text groups can be found in the Ovation Graphics Builder User
Guide.
11. The Diag Number field displays the number of the diagram to be loaded when the point group
is loaded. If the field is left blank or set equal to zero, then the requested group is displayed
with the current diagram. If the field is non-zero, then the diagram of that number is displayed
with the requested group.
12. The Group Paging fields (Up Group, Down Group, Right Group, and Left Group) allow you to
enter the group numbers associated with the group to be used for paging. Enter the group
numbers in the associated Group fields. A paging group number must be an integer from 0 to
1,000. If the value is outside the range, the default value of zero is used, indicating no paging
in that direction.
13. Select Ok to activate the new point group. A sub-folder with the new PDS group name is
added to the PDS Point Groups folder.
8.8.2 T o modify PDS Point Groups
Use the following steps to modify PDS Point Groups:

2. Use the system tree (in the Hardware view bar) to navigate to the PDS Point Groups folder:
Systems -> Point Groups -> PDS Point Groups
Note: Folders for all existing PDS point groups appear under the PDS Point Groups folder.
3. Right-click the PDS points group item in the WorkPad window that you wish to modify.
4. Select Open. The PDS Point Group dialog box appears similar to the one in To add a new
PDS Point Group (see page 215).
5. Make the necessary changes.
6. Select Ok.
8.8.3 T o add a PDS Point Group M e mber
Use the following steps to add a PDS Point Group Member:

Systems -> Point Groups -> PDS Point Groups -> Group item -> PDS Point Group
Members
Note: Folders for all existing PDS point groups appear under the PDS Point Groups folder.
3. Right-click the PDS Point Group Members folder.

4. Select Insert New. The Insert New PDS Group Members Wizard appears.
5. Enter the point name in the Point Name entry field.
6. Use the arrows (or type it in) to select a Rank. Rank is the reference that corresponds to the
point that the graphic uses to retrieve the information to display.
OW351_60 217
7. Select Finish and the PDS Point Group Member dialog box appears. Information provided in
the Insert New PDS Group Members Wizard displays in the dialog box.
PDS Point GroupM ember dialog box fields
Point name Name of the point (1-30 Characters).

Rank Order of the point within the group (0-249).
Slot Internal use. Defined as Rank + 1.
8. Select Ok to activate the PDS point group member. The new PDS point item appears in the
system tree.
8.8.4 T o modify PDS Point Groups M ember
Use the following steps to modify PDS Point Groups Member:

Systems -> Point Groups -> PDS Point Groups -> Groups subfolder -> PDS Group
Members
3. Double click the appropriate PDS Group Members item in the WorkPad window. The PDS
Point Group Member dialog box appears similar to the one in To add a Point Group Member
to a PDS Point Group (see page 217).
4. Make necessary changes to the Point name (1-30 characters) or Rank (0-249).
5. Select Ok to add the modified member to the database.
218 OW351_60
8.9 What are Packed Group Numbers?
A packed group number decodes the packed value and bits in alarm of the packed points and
displays the value as a configured text string description instead of representing the value bits as
binary or hexadecimal bits.
You can define a packed group number for packed and deluxe packed points through the
Developer Studio. The Group Number field is located on the Display tab of each packed point.
The value of the group number can be between 0 to 65,539.
 A value of 0 implies that the point does not have a packed group defined; therefore, it will
display the value and bits in alarm fields as a binary or hexadecimal representation of the bits.
 A value of 1 or more (up to 65,539) implies that the point has a packed group defined;
therefore, it will display the value and bits in alarm fields as a text string description.
You need to define the text strings in a separate xml file that will display based on the point's
group number and value.
For information about adding points to the system, see Adding points in the Ovation Developer
Studio (see page 169).
8.9.1 T o de fine a group numbe r
Perform the following steps to define a group number for packed and deluxe packed points:

3. Right-click the appropriate Points folder (packed or deluxe packed point).
4. Configure the packed/deluxe point with the required information. See What information must
be configured for each point type? (see page 172)
5. Go to the Display tab, enter the group number (to define the value and bits in alarm fields as
a text string) in the Group number field. The group number value can be between 0 to 65,539.
Notes:
 A value of 1 or more (up to 65,539) implies that the point has a pack ed group defined;
therefore, it will display the value and bits in alarm fields as a text string description.
 A value of 0 implies that the point does not have a pack ed group defined; therefore, it will
display the value and bits in alarm fields as a binary or hexadecimal representation of the
bits.
OW351_60 219
6. Click Apply.
Figure 111: Defining the group number
7. Click Ok to save the changes.
Display tab fields for Long Packed (LP) and Deluxe Packed (DP) points
Group Number Identifies the packed group number for packed and deluxe packed points.
The value range is between 0 and 65,539.
If the defined group number for the packed point is greater than 0, the
value field displays as a configured text string, rather than in a b inary or
hexadecimal representation of value bits.
Note: If the group numb er value is 0, it implies that the packed point
does not have a packed group identified, and the value field displays as
a b inary and hexadecimal representation of the value b its.
220 OW351_60
8.9.2 T o de fine te xt string v alues in an XM L file
You need to define the text string values in a separate XML file for each group number to ensure
that it will display the text string descriptions based on the point’s group number and value. The
following table describes each parameter that needs to be defined in the XML file:
Parameters for each group number
P AR AME T E R S D E S C R I P TI O N
Group Number Identifies the packed group number.

Value or bits in alarm Identifies the mapping strings that are defined for either the value field
(A2) or the bits in alarm field (C9).
Pattern match Identifies the pattern match specification. For each pattern match, the
following nodes are defined: Priority, Mask, Value, String, Default text,
and text.
Priority Defines priority of the criteria. Valid priorities are 1 to 32 with 1 being the
highest and 32 being the lowest.
Mask Identifies the bits to be matched. The bits that are 1 in the mask are the
bits that will be matched.
Value Defines the bit pattern to be matched (that is, identifies the value (1 or 0)
of the bits that are to be matched).
Default text Identifies the string to use if the value does not match any of the pattern
match specifications.
Text Defines the string value to display. The string value cannot exceed 16
characters
To create the XML file
1. Manually create the XML file that defines the text string values for each group number. See
Sample of XML file (see page 222).
 If the XML file contains the group number without a definition for the value or bits in
alarm, the appropriate fields (value or bits in alarm) will display as the binary or
hexadecimal representation of its value.
 If the value in the XML file does not match any of the defined pattern match sequences
and there is no default text defined, the appropriate fields (value or bits in alarm) will
display as the binary or hexadecimal representation of its value.
2. Store the XML file in the network configuration directory that is located in the OvPtSvr
directory path. For example, if the OvptSvr directory is located on the C: \ drive and the system
is Ovation and the Network is Network35, the file name would be
C:\OvptSvr\Ovation\Network35\ Config\PackedGroupDesc.xml.
3. If the XML file is present, it will be query downloaded to each Operator Station. See Download
function (see page 99).
Note: Applications that use the XML file will only read it into memory one time. If you modify the
XML file and query/download it, you must restart the application to read the new information.
OW351_60 221
8.9.3 Sample of XM L file
The following is a sample of the PackedGroupDesc.XML file.

<?xml version="1.0" encoding="utf-8"?>
<Document version ="1">
<Groups>
<Group GroupNumber="1">
<value>
<PatternMatch>

<PM priority="1" mask="0x0C00" value="1280" text="OFF MP"/>
<PM priority="2" mask="0x0400" value="0x0400" text="OFF"/>
<PM priority="3" mask="0x0300" value="0x0300" text="ON MP"/>
<PM priority="4" mask="0x0500" value="0x0500" text="ON"/>
<PM priority="6" mask="0x4000" value="0x4000"
text="UNDEFINED"/>
<PM priority="5" mask="0x4100" value="0x4101" text="UNDEFINED MP"/>
</PatternMatch>
<Default text="UNKNOWN STATE1"/>
</value>
<bitsinalarm>
<PatternMatch type="bitsinalarm">

<PM priority="1" mask="1280" value="1280" text="OFF MP"/>
<PM priority="2" mask="0x0400" value="0x0000" text="OFF"/>
<PM priority="3" mask="0x0300" value="0x0200" text="ON MP"/>
<PM priority="4" mask="0x0500" value="0x0500" text="ON"/>
<PM priority="6" mask="0x4000" value="0x4000" text="UNDEFINED"/>
<PM priority="5" mask="0x4100" value="0x4100" text="UNDEFINED MP"/>
</PatternMatch>
</bitsinalarm>
</Group>
<value>
<PatternMatch>
<PM priority="2" mask="0x0200" value="0x0200" text="REMOTE"/>
<PM priority="3" mask="0x0400" value="0x0400" text="AUTO"/>
</PatternMatch>
</value>
222 OW351_60
</Group>
<value>
</value>
<bitsinalarm>
</bitsinalarm>
</Group>
<value>
</value>
</Group>
<value>
<PatternMatch>
<PM priority="12" mask="0x0200" value="0x0200" text="REMOTE"/>
<PM priority="13" mask="0x0400" value="0x0400" text="AUTO"/>
</PatternMatch>
</value>
<bitsinalarm>
</bitsinalarm>
</Group>
</Groups>
</Document>
OW351_60 223
SECTION 9
9 Adding I/O to the Developer Studio
IN THIS SECTION
What is the purpose of an Ovation I/O module? ........................................................ 225

Information needed before adding an I/O module ...................................................... 226
Overview of adding I/O modules to the Developer Studio .......................................... 226
Defining and configuring Ovation I/O modules .......................................................... 236
QLine module configuration ..................................................................................... 280
9.1 What is the purpose of an Ovation I/O module?
Ovation control systems consist of a configurable mix of functional Input/Output (I/O) modules that
communicate with the Ovation Controller.
I/O modules provide an interface between the Ovation Controller and the processes in the plant.
Ovation I/O modules are a plug-in component with built-in fault tolerance and diagnostics. They
are able to operate on a wide range of signals and perform a multitude of functions.
Ovation I/O modules are seated into base units and are latched into place. Base units are housed
in the Controller cabinet where they are mounted on DIN rails and wired to the appropriate field
devices.
The standard modular components typically consist of the following:

 Electronics module (Emod).
 Personality module (Pmod).
 Base unit (containing the field terminations).
The relay output modular components consist of the following:
 Electronics module.
 Base unit (containing the field terminations).
OW351_60 225
9.2 Information needed before adding an I/O module
9.2 Information needed before adding an I/O module
Before configuring an I/O module, design a plan that lists the requirements for your Ovation
system. Make a list of:
 Modules to be added.
 I/O module part numbers.
 Where in the system the modules are to be placed.
Note: The module(s) can be installed prior to, or after, entering the information into the system.
However, the module(s) must be installed prior to downloading the information to the Controller.
In addition, consider the following before adding I/O modules to your Ovation system.
 Ensure that you have the appropriate engineering privileges that are needed to add I/O
modules to the Ovation system.
 You should be familiar with point naming conventions (see page 167) for module records.
 You should know how to use the Controller Diagnostic Tool to download firmware to the I/O
modules. Refer to the applicable Ovation Controller User Guide for more information.
Adding and configuring I/O modules involves a hardware component and a software component.
Hardware information related to Ovation I/O modules can be found in:
 Planning Your Ovation System
 Ovation I/O Reference Manual
 Ovation Bus and Specialty I/O Reference Manual
 Q-Line I/O to Ovation I/O Migration Reference Manual
Software configuration information can be found in this manual and:

 Ovation Controller User Guide
226 OW351_60
9.3 Overview of adding I/O modules to the Developer Studio
The following steps provide an overview of adding a new I/O module to an Ovation system. Refer
to the specific topics for detailed instructions.
1. Ensure that you have read the section called Information needed before adding an I/O
module (see page 226).
2. Add an I/O device number in the Controller (see page 227).
3. Add an I/O device in the Developer Studio (see page 229).
4. Add an Ovation I/O module in the Developer Studio (see page 230).
5. Configure the applicable Ovation module (see page 232).
6. Assign a module point to the I/O module. (All Ovation I/O modules must have a module (RM)
point assigned to it (see page 233).
7. Load the module in the Controller (see page 235).
9.3.1 T o inse rt an I/O De v ice numbe r in a Controller
Note: The following procedure is only performed once. If you already added a specific driver,
you do not have to perform this procedure. Refer to the applicable Ovation Controller User
Guide for detailed information on device drivers.
A Controller driver is a software program that acts as a translator between a hardware device and
the applications that use the device. Every version of a hardware device, such as a printer,
requires its own specialized commands.

2. Use the system tree to navigate to the Device Number item:
Systems -> Networks -> Units -> Drops -> Configuration -> Controller -> Devices ->
Device Number
3. Right-click Device Number.
OW351_60 227
4. Select Insert New. The Insert New Device Numbers wizard appears:
Figure 112: Insert New Device Numbers Wizard
Note: If you add, change, or delete device drivers, perform a clear/load function on the
Controller.
5. From the Device Number drop-down menu, select an unused number (for example, you
might start with 2, and continue numbering successive devices sequentially).
6. Click Finish. The New Device Numbers window appears.
7. From the I/O Driver Type drop-down menu, select OVATION (for examples purposes here).
Figure 113: New Device Numbers window
8. Click Ok.
Note: After you insert a device number in the Controller, proceed to the steps on inserting an
I/O device in the Developer Studio (see page 229). You should not perform Download and Clear
functions until you have inserted a device number in the Controller and a device in the
Developer Studio.
Also, if the configuration of an I/O device number changes, you must Download and Reboot the
Controller. If the quantity of a Controller’s I/O device numbers changes, you must Download and
Clear the Controller.
228 OW351_60
9.3.2 T o inse rt an I/O De v ice in the De veloper Studio

2. Use the system tree to navigate to the I/O Device item:
Systems -> Networks -> Units -> Drops -> <Controller Drop number> -> I/O Devices
3. Right-click I/O Device and select Insert New. The Insert New [I/O Devices] Wizard appears.
4. Select the I/O Device Number from the drop-down menu. The choices are 0 for IOIC and
5 - 11 for third-party and Bus devices.
5. From the I/O Device Type drop-down menu, select IOIC.
Figure 114: Insert New [I/O Devices] Wizard
6. Click Finish. The New [I/O Devices] window appears showing the selection that you made.
7. Select the Ok button.
8. Perform the Download (see page 99) and Clear (see page 110) functions.
OW351_60 229
Refer to the applicable Ovation Controller User Guide for an explanation of the attributes and
value selections for the IOIC and third-party devices:
 IOIC Devices:
 Local Ovation
 Remote Ovation
 Local Q-Line
 Remote Q-Line
 Allen-Bradley PLC
 Modbus Master
 RTP IOBC6700
 GE Mark V
 GE Mark VI/Ve
 External Ovation Network
 MHI
 Toshiba
 Foundation Fieldbus Module
 GE Genius
 Modbus -R
 Machinery Health Monitor
 Digital Excitation Controller
Refer to the indicated User Guide for an explanation of the attributes and value selections for the
I/O Device Types not discussed in the Controller manual:
 Fieldbus Module - Refer to the appropriate Ovation Foundation Fieldbus User Guide.
 Profibus Module - Refer to the appropriate Ovation Profibus User Guide.
 DeviceNet Module - Refer to the appropriate Ovation DeviceNet User Guide.
 Wireless HART - Refer to the appropriate Ovation Wireless Devices User Guide.
 Ethernet Link - Refer to the appropriate Ovation Ethernet Link Controller User Guide.
 Ovation SIS - Refer to the appropriate Ovation SIS User Guide.
 Machinery Health Monitor - Refer to the Machinery Health Monitor User Guide.
 Digital Excitation Controller - Refer to the Digital Excitation Controller User Guide.
230 OW351_60
9.3.3 T o inse rt an Ov ation I/O module in the De v eloper Studio

2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
Systems -> Networks -> Units -> Drops -> I/O Devices -> I/O Device 0 IOIC -> IO
Interfaces -> Branch -> Slot
3. Right-click on Ovation Module in the empty slot and select Insert New.
Figure 115: Inserting a new module
OW351_60 231
4. The Insert New Ovation Module Wizard appears. From the Module Type drop-down menu,
select the applicable module.
Figure 116: Insert New Ovation Module Wizard
5. Select Finish. The New Ovation Module window appears.

6. Proceed to the section on To configure an I/O module (see 232).
9.3.4 T o configure an I/O module
The New Ovation Module window has four tabs located at the bottom of the window. All of the
tabs, except the Module tab, are populated by the software. The Module tab contains the
selectable module information. The parameters shown on the tab vary, depending on the type of
module you select.
1. From the New Ovation Module window, go to the Module tab at the bottom of the New
Ovation Module window.
Figure 117: New Ovation Module window showing Module tab
2. Complete the information on the window fields per the module you are configuring. For
information on configuring the various modules, see the applicable module parameter tables
in the section, Defining and configuring Ovation I/O modules (see page 236).
232 OW351_60
9.3.5 T o assign a M odule (RM ) point to the I/O module
Note: You must assign a module (RM) point to every Ovation I/O module.

2. Use the system tree to navigate to Module Points:
System -> Networks -> Units -> Drops -> Points -> Module Points
3. Right-click on Module Points to select Insert New. The Insert New Module Points wizard
appears:
Figure 118: Insert New Module Points Wizard
4. Enter a point name.

5. Pick a frequency (S = Slow (1 second), F = Fast (0.1 second), or A = As needed).
OW351_60 233
6. Click Finish. The New Module Points window appears:
Figure 119: New Module Points window
7. Navigate to the Hardware tab.

8. Choose the I/O module from the location where you added the Primary I/O module.
9. Click OK. If you navigate to your card and Open/Refresh, you will see the fully qualified
module record point name (for example, TEST.UNIT@FB).
234 OW351_60
9.3.6 T o load the configured I/O module to the Controller
After you have added and completely configured the I/O module, you must load the changes to
the Controller.
Note: The Load function is necessary any time an I/O module is added.
1. Access the Ovation Developer Studio.

3. Right-click on the appropriate Controller that you want to load.
4. Select Load from the pop-up menu.
5. For redundant Controller drop configurations, the Load wizard appears.
Figure 120: Load wizard
6. Select the Controller drop that you want to load. The Controller drop that is in control must
be loaded first. Click Finish.
7. Repeat the entire Load procedure for the other Controller drop.
OW351_60 235
9.4 Defining and configuring Ovation I/O modules
The New Ovation Module window contains the following tabs:

 Config
 Module
 Digital Channels
 Analog Channels
All tabs except the Module tab are completed by the software.
The Module tab is populated when you complete the Insert New Ovation Module Wizard. The tab
contains the selectable module information. The parameters shown on the tab vary, depending on
the type of module you select. You must define and configure the parameters for each different
type of an Ovation module.
The modules can be categorized as follows:
 Analog Input modules (see page 237).

 Analog Output modules (see page 240).
 Contact Input modules (see page 242).
 Compact Contact Input modules (see page 242).
 Digital Input modules (see page 242).
 Compact Digital Input modules (see page 243).
 Digital Output modules (see page 244).
 HART Analog Input modules (see page 246).
 HART Analog Output modules (see page 247).
 HART High Performance Analog Input modules (see page 248).
 HART High Performance Analog Output modules (see page 248).
 Loop Interface modules (see page 250).
 Machinery Health Monitor module (see page 252).
 Pulse Accumulator modules (see page 252).
 Relay Output modules (see page 255).
 RTD modules (see page 258).
 Sequence of Events modules (see page 265).
 Serial Link Controller modules (see page 269).
 Servo Drive modules (see page 269).
 Speed Detector modules (see page 270).
 Valve Position Controller modules (see page 273).
 Digital Excitation Controller module (see page 276).
 Foundation Fieldbus modules (see page 275).
 Profibus modules (see page 278).
 DeviceNet modules (see page 279).
 Ethernet Link modules (see page 279).
 QLine modules (see page 280).
For more information on module configuration, refer to the Ovation I/O Reference Manual and
Ovation Bus and Specialty I/O Reference Manual.
236 OW351_60
9.4.1 Analog Input module configuration
The following tables describe the Module tab parameters for the Analog Input modules.
Applies to:
 16 Ch Analog Input 4 to 20 mA (2/4-Wire)

 16 Ch Analog Input 4 to 20 mA (2-Wire)
Module tab parameters for select Analog Input modules
P AR AME T E R DE S C R I P TI O N
A/C Line Frequency Defines the type of A/C line frequency used in the system (50 Hz or 60 Hz).
Input sampling rate is 80 ms at 50 Hz, and 83.3 ms at 60 Hz.
Default is 60 Hz.
Applies to:
 Analog Input 14 bit 4 to 20mA
 Analog Input 14 bit -1 to 1V
Default is 60 Hz.
A/D Conversion Defines the speed at which the A/D conversion is performed by the I/O
Rate module. The options are Normal and High Speed. Default is Normal.
Suppress Point Prevents the RM module point from going into alarm if one or more of the
Fault Module Alarm analog inputs are in an alarm or sensor condition. For example, if one or
more channel(s) of a 4-20 mA card are unused (and left open), setting this
parameter prevents the RM module point from going into alarm. The default
is to NOT suppress the point fault module alarm.
OW351_60 237
Applies to:
 Analog Input 14 bit HS 4 to 20mA
 Analog Input 14 bit HS +/-1mA remote powered
 Analog Input 14-bit HS +/-1mA local powered
 Analog Input (13 bit) +/- 20mV
 Analog Input (13 bit) +/- 20mV w/ temperature sensor
 Analog Input (13 bit) -1 to 1V
 Analog Input (13 bit) 0 to 20mA remote powered
 Analog Input (13 bit) 0 to 20mA local powered
Default is 60 Hz.
Suppress Point Prevents the RM module point from going into alarm if one or more of the analog
Fault Module Alarm inputs are in an alarm or sensor condition. For example, if one or more channe l(s)
of a 4-20 mA card are unused (and left open), setting this parameter prevents the
RM module point from going into alarm. The default is to NOT suppress the point
fault module alarm.
238 OW351_60
Applies to:
 Analog Input 14 bit HS +/-100mV, 250mV, 1V
 Analog Input 14 bit HS +/-5V, 10V
 Analog Input 14 bit MS +/-20mV, 50mV, 100mV w/OTD
 Analog Input 14 bit MS +/-20mV, 50mV, 100mV w/OTD (CE/61131-2)
Default is 60 Hz.
Voltage Range Selects the voltage ranges, as applicable.
Selection
Fault Module Alarm analog inputs are in an alarm or sensor condition. For example, if one or more
channel(s) of a 4-20 mA card are unused (and left open), setting this parameter
prevents the RM module point from going into alarm. The default is to NOT
suppress the point fault module alarm.
Applies to:
 Analog Input (13 bit) 4 to 20mA remote powered
 Analog Input (13 bit) 4 to 20mA local powered
Default is 60 Hz.
Enable Blown Fuse When set, the module reports a blown fuse and lights the “E” LED.
Detection
Fault Module Alarm analog inputs are in an alarm or sensor condition. For example, if one or more
OW351_60 239
Applies to:
 16 CH Analog Input 14 bit +/-20mV,50mV,100mV w/OTD
 8 CH Compact Analog Input 14 bit +/-20mV,50mV, 100mV w/OTD

Selection
Fault Module Alarm inputs are in an alarm or sensor condition. For example, if one or more
Applies to:
 8 CH Analog Input HI 0-10V
P AR AME T E R D E S C R I P TI O N
No parameter No parameter appears in the Analog Input Module tab because user
configuration is not required for the module.
9.4.2 Analog Output module configuration
The following tables describe the Module tab parameters for the Analog Output modules.
Applies to:
 Analog Output 0 to +5V
 Analog Output 0 to +10V
 Analog Output 0 to 20mA w/ diagnostics
 Analog Output 0 to 20mA w/o diagnostics
 Analog Output 4 to 20mA w/ diagnostics
 Analog Output 4 to 20mA w/o diagnostics
240 OW351_60
Module tab parameters for select Analog Output modules
Timeout Action Reset: After the timeout period, output goes to 0.

Latch: After the timeout period, the last output remains.
Timeout Selection Drop-down menu used to define the timeout period:
 16 seconds
 4 seconds
 2 seconds
 1 second
 500 milliseconds
 62.5 milliseconds
The tolerance on the timeout period is / 35%.
Applies to:
 Analog Output 4 to 20mA (RED.)
Module tab parameters for select Analog Output modules

 16 seconds
 4 seconds
 2 seconds
 1 second
Redundancy
Redundancy Specifies whether the operation of the module is redundant or simplex.
Redundant Partner Specifies the redundant partner.
OW351_60 241
9.4.3 Contact Input module configuration
The following table describes the Module tab parameters for the Contact Input modules.
Applies to:
 Contact Input w/ Onboard 48V wetting
Module tab parameters for select Contact Input modules
Disable Points on When set, the module reports an error when an input line or return line is
Ground Fault shorted to earth ground, and lights the “E” LED.
9.4.4 Compact Contact Input module configuration
The following table describes the Module tab parameters for the Compact Contact Input modules.
Applies to:
 Compact Contact Input w/ Onboard 48V wetting
Module tab parameters for select Compact Contact Input modules
Disable Points on When set, the module reports an error when an input line or return line is
Ground Fault shorted to earth ground, and lights the “E” LED.
9.4.5 Digital Input module configuration
The following tables describe the Module tab parameters for the Digital Input modules.
Applies to:
 Digital Input 24 VDC, 32 Ch
 Digital Input 24VAC/DC or 48VDC differential
 Digital Input 125VAC/DC differential
Module tab parameters for select Digital Input modules
No parameter No parameter appears in the Digital Input Module tab.
242 OW351_60
Applies to:
 Digital Input 24VAC/DC or 48VDC single ended
 Digital Input 125VAC/DC single ended
Blown Fuse Detection When set, if an auxiliary power supply fuse is blown, the module reports an
error and lights the “E” LED.
Applies to:
 Digital Input 24 VDC (RED.)
Redundancy
9.4.6 Compact Digital Input module configuration
The following tables describe the Module tab parameters for the Compact Digital Input modules.
Applies to:
 Digital Input Compact 24VAC/DC or 48VDC differential
 Digital Input Compact 24/48V diff. individually fused
 Digital Input Compact 125V diff. individually fused
 Digital Input Compact 125VAC/DC differential
 Compact Digital Input 24 VDC w/Ind Ch current limiter
Module tab parameters for select Compact Digital Input modules
No parameter No parameter appears in the Compact Digital Input Module ta b.
OW351_60 243
Applies to:
 Digital Input Compact 24VAC/DC or 48VDC single ended
Module tab parameters for select Compact Digital Input modules
9.4.7 Digital Output module configuration
The following tables describe the Module tab parameters for the Digital Output modules.
Applies to:
 Digital Output 24 VDC High Side
Module tab parameters for select Digital Output modules
Timeout Action Reset: After the timeout period, output clears (output transistor is shut off).
 16 seconds
 4 seconds
 2 seconds
 1 second
External Error On Field If you set the parameter by selecting the check box, the following holds true:
Power Loss  If the module’s external 24V DC power supply voltage is not present, the
External Error LED is illuminated and the module goes into Attention status.
If you do not want to set the parameter and clear the check box, the following
holds true:
 If the module’s external 24V DC power supply voltage is not present, the
External Error LED is not illuminated and the module is not forced into
Attention status.
Redundancy
244 OW351_60
Output Test Time Drop-down menu used to define the output test time:
Selection  24 hours
 12 hours
 8 hours
 4 hours
 2 hours
 1 hour
 30 minutes
 15 minutes
Output Fault Handling Selects from the following options:
Method  Shut off field power: In case of the digital output fault, the module shuts
off its 24V DC field power switch in order to disconnect all of its power
switches from the field power.
 Alarm only: In case of the digital output fault, the module only reports
alarms.
Applies to:
 Digital Output 5-60 VDC

 Digital Output 5-60 VDC w/relay pnl comm
 Digital Output 5-60 VDC w/relay pnl comm ext fuses
 16 seconds
 4 seconds
 2 seconds
 1 second
Blown Fuse Detection When set, if a fuse is blown, the module reports an error and lights the “E” LED.
OW351_60 245
Applies to:
 High Side Digital Output, 32 Ch
 16 seconds
 4 seconds
 2 seconds
 1 second
Applies to:
 Digital Output 5-60 VDC w/ Ch STO

 Digital Output 5-60 VDC w/ Ch STO and relay pnl comm
 Digital Output 5-60 VDC w/ Ch STO and relay pnl comm ext fuses
Timeout Action Configures the timeout action for the available channels. Check the appropriate
channel check boxes to configure the timeout action as Latch, which is after the
timeout period, the last output remains. If the appropriate channel ch eck
box(es) is not selected, the timeout action for that channel(s) is Reset, which is
after the timeout period, output clears.
 16 seconds
 4 seconds
 2 seconds
 1 second
Blown Fuse Detection When set, if a fuse is blown, the module reports an error and lights the “E” LED.
246 OW351_60
9.4.8 HART Analog Input module configuration
The following table describes the Module tab parameters for the HART Analog Input modules.
Applies to:
 HART Analog Input
Module tab parameters for select HART Analog Input modules
HART Device on Channel This I/O card has eight channels. Therefore, this parameter has eight check
boxes – one for each channel. To indicate a HART device is attached to a
channel, select the corresponding check box.
Scan HART Variables on Use this parameter if you want to provide HART multiple variable support for
Channel any of the eight channels. However, the channel(s) selected in this
parameter must be defined in the parameter HART Device on Channel.
9.4.9 HART Analog Output module configuration
The following table describes the Module tab parameters for the HART Analog Output modules.
Applies to:
 HART Analog Output
Module tab parameters for select HART Analog Output modules

Timeout Drop-down menu used to define the timeout period:
Selection  16 seconds
 4 seconds
 2 seconds
 1 second
HART Device This I/O card has eight channels. Therefore, this parameter has eight check boxes –
on Channel one for each channel. To indicate a HART device is attached to a channel, select the
corresponding check box.
Scan HART Use this parameter if you want to provide HART multiple variable support for any of
Variables on the eight channels. However, the channel(s) selected in this parameter must be
Channel defined in the parameter HART Device on Channel.
OW351_60 247
9.4.10 HART High Pe rformance Analog Input module configuration
The following table describes the Module tab parameters for the HART High Performance Analog
Input modules.
Applies to:
 HART High Performance Analog Input w/ current limiting
 HART High Performance Analog Input w/ current limiting (CE/61131-2)
 HART High Performance Analog Input
 HART High Performance Analog Input (CE/61131-2)
Module tab parameters for select HART High Performance Analog Input modules
Default is 60 Hz.
HART Device on This I/O card has eight channels. Therefore, this parameter has e ight check boxes
Channel – one for each channel. To indicate a HART device is attached to a channel, select
the corresponding check box.
Variables on the eight channels. However, the channel(s) selected in this parameter must be
Channel defined in the parameter HART Device on Channel.
Suppress Point Permits the RM module point from going into alarm if one or more of the analog
Fault Module Alarm inputs are in an alarm or sensor condition. For example, if one or more channel(s)
of a 4-20 mA card are unused (and left open), setting this attribute prevents the
fault module alarm.
248 OW351_60
9.4.11 HART High Pe rformance Analog Output module configuration
The following table describes the Module tab parameters for the HART High Performance Analog
Output modules.
Applies to:
 HART High Perf. Analog Output: AO pin-compatible
 HART High Performance Analog Output
Module tab parameters for select HART High Performance Analog Output modules

Timeout Drop-down menu used to define the timeout period:
Selection  16 seconds
 4 seconds
 2 seconds
 1 second
HART Device This I/O card has four channels. Therefore, this parameter has four check boxes – one
on Channel for each channel. To indicate a HART device is attached to a channel, select the
corresponding check box.
Variables on the four channels. However, the channel(s) selected in this parameter must be defined
Channel in the parameter HART Device on Channel.
OW351_60 249
9.4.12 Loop Inte rface module configuration
The following tables describe the Module tab parameters for the Loop Interface modules.
Applies to:
 Loop Interface AI/AO: 0-10V

 Loop Interface AI: 0-5V AO: 0-10V
 Loop Interface AI/AO: 4-20mA local powered
 Loop Interface AI/AO: 4-20mA field powered
 Loop Interface AI/AO: 0-10V User DI
 Loop Interface AI: 0-5V AO: 0-10V User DI
 Loop Interface AI/AO: 4-20mA local powered User DI
 Loop Interface AI/AO: 4-20mA field powered User DI
Module tab parameters for select Loop Interface modules
Default is 60 Hz.
Blown Fuse Detection When set, if a fuse is blown, the module reports the appropriate error and lights
Enabled (inputs) the “4 Fuse” LED.
Blown Fuse Detection When set, if a fuse is blown, the module reports the appropriate error and lights
Enabled (outputs) the “4 Fuse” LED.
Digital Outputs on Shutoff: After the timeout period, output clears (output transistor shuts off).
Controller Timeout
Hold: After the timeout period, the last output remains.
Communications Drop-down menu used to define the timeout period:
Timeout Selection  16 seconds
 4 seconds
 2 seconds
 1 second
Inverse Analog Output Select the check box if you want the module to perform an inverse analog
Operation output operation. Inverse operation of the analog output means:
 When the output value is 0%, the analog output has the maximum value (+10
V or +5 V for voltage modules, and 20 mA for current modules).
 When the output value is 100%, the analog output has the minimum value (0
V for voltage modules, and 4 mA for current modules).
250 OW351_60
EMOD 1C31174 Rev 5 or later

Controller Defined When set, the parameter indicates that the Controller is defining the process
Process Variable 1 variable. The process variable can then be configured as the analog point
assigned to analog channel 7.
Controller Defined When set, the parameter indicates that the Controller is defining the setpoint.
Setpoint 1 The process variable can then be configured as the analog point assi gned to
analog channel 8.
1 The parameter is only valid if the Electronics Module firmware is at Version 5 or later.
Applies to:
 Loop Interface AI: 4-20mA local powered
 Loop Interface AI: 4-20mA field powered
 Loop Interface AI: 4-20mA local powered User DI
 Loop Interface AI: 4-20mA field powered User DI
Module tab parameters for select Loop Interface modules
Default is 60 Hz.
Blown Fuse Detection When set, if a fuse is blown, the module reports the appropriate error and
Enabled (inputs) lights the “4 Fuse” LED.
Enabled (outputs) lights the “4 Fuse” LED.
 4 seconds
 2 seconds
 1 second
Digital Outputs Start Off Time: Pulses start with Off time.
With
On Time: Pulses start with On time.
Electric Drive Mode Electric drive provides two mode options:
 Normal (Mode 1): Calculates process variable as normal type. Output is two
digital outputs (raise/lower.)
 Mode 2: Calculates process variable. Output is two digital outputs.
For all modes except local, a demand of 0 forces the lowest limit.
OW351_60 251
Inverse Analog Output Select the check box if you want the module to perform an invers e analog
 When the output value is 0 percent, the analog output has the maximum
value (+10 V or +5 V for voltage modules, and 20 mA for current modules).
 When the output value is 100 percent, the analog output has the minimum
value (0 V for voltage modules, and 4 mA for current modules).
Setpoint 1 The process variable can then be configured as the analog point assigned to
analog channel 8.
9.4.13 M achinery He alth M onitor module configuration
The following table describes the Module tab parameters for the Machinery Health Monitor
module.
Applies to:
 Machinery Health Monitor
Module tab parameters for Machinery Health Monitor module
Network Interface 1
NIC 1 Enabled Enables network interface 1.
NIC 1 IP Address Specifies the IP address of interface 1.
NIC 1 Subnet Mask Specifies the subnet mask of interface 1.
NIC 1 Interface Mode Specifies the speed and duplex configuration of interface 1.
 100 mbps/ full duplex
 100 mbps/ half duplex
 Auto-negotiate
 1 Gb/ full duplex
Network Interface 2
252 OW351_60
 Auto-negotiate
General Network Configuration
Default Gateway IP Specifies the IP Address of the default gateway used by the
Address module.
Time Sync Type Specifies the source of time synchronization.
 RLine (Controller group write)
 NTP
NTP Server IP Specifies the IP Address of the NTP server that should be
Address synchronized with the module.
9.4.14 Pulse Accumulator module configuration
The following table describes the Module tab parameters for the Pulse Accumulator modules.
Applies to:
 Pulse Accumulator 24/48V 5/12V med speed pos com

 Pulse Accumulator 24/48V 5/12V med speed neg com
 Pulse Accumulator 24/48V 5/12V med speed ext PS
 Pulse Accumulator 5V high speed pos com
 Pulse Accumulator 5V high speed neg com
 Pulse Accumulator 5V high speed ext PS
Module tab parameters for select Pulse Accumulator modules
All parameter descriptions are applicable to Channel 1 or Channel 2.

Count Type Field input voltage range that defines different terminal block connections:
 5 V (high speed)
 12 V (medium speed)
 24/48 V
OW351_60 253
Configuration  A: Count pulses until reset by Controller.

Style  B: Count pulses count and reset.
(See the next  C: Measure width of long pulse.
table for a  D: Measure width of last pulse.
matrix of  E: Measure total width of several pulses since last read.
parameters to
 F: Measure period of repetitive pulses.
set for each
style.)  G: Measure puls e width ratios. Channel 1 measures pulse width. Channel 2
measures pulse period.
 H: Measure speed (frequency). Channel 1 is used for the time base.
Channel 2 counts the input pulses.
Note: Configuration styles can b e mixed on a card, except styles G and H.
Count Select Selects input to the counter through bits 15 and 14 in register D:
 External
 1 KHz
 10 KHz
 100 KHz
Disable When set, the parameter disables the de-bounce (chattering or noise) on
Debounce on enable and snapshot inputs.
ENABLE and
SNAPSHOT
ENABLE for When set, the open time of an ENABLE input is measured.
OFF Input When not set, the closed time of an ENABLE input is measured.
Snapshot Count Select Leading to snapshot on the leading edge of an input pulse.
on Pulse Edge
Select Trailing to snapshot on the trailing edge of an input pulse.
Measure Close Time: The closed time of an ENABLE input is measured.
Open Time: The open time of an ENABLE input is measured.
The third radio button is selected where neither Close Time nor Open Time is
appropriate or applicable.
Increment Count Select Leading to increment count on the leading edge of an input pulse.
on Pulse Edge
Select Trailing to increment count on the trailing edge of an input pulse.
Reset on Read When set, the counter goes back to zero (0) after the pulse is read.
Debounce When set, the parameter de-bounces (reject chatter or noise) the input count.
Count Input
Compare and Only set for configuration H.
Snapshot
Reset on When set, the counter goes back to zero (0) after the snaps hot occurs.
Snapshot
Enable When set, the counter is enabled to count and does not require the external
command ENABLE signal.
254 OW351_60
Parameters to configure for Pulse Accumulator Configuration Styles
P AR AME T E R Configuration style
A B C D E F G H
Module Record Point Name X X X X X X X X

Count Type X X X X X X X X
Configuration Style A B C D E F G H
Count Select X X X X X X
Disable Debounce on ENABLE and X X X X X X X
SNAPSHOT
ENABLE for OFF Input X X
Snapshot Count on Pulse Edge X X
Measure X X X
Increment Count on Pulse Edge X X
Reset on Read X X
Debounce Count Input X X X
Compare and Snapshot X
Reset on Snapshot X X X X
Enable command X X X X X
OW351_60 255
9.4.15 Re lay Output module configuration
The following table describes the Module tab parameters for the Relay Output modules.
Applies to:
 Relay Output Module w/Ch STO G2R

 Relay Output Module w/Ch STO KUEP
 Relay Output Assembly w/Ch STO G2R Fused, Marshalling
 Relay Output Assembly w/Ch STO G2R Fused, Customer Termination
 Relay Output Assembly w/Ch STO KUEP Form C, Fused, Marshalling
 Relay Output Assembly w/Ch STO KUEP Form X, Fused, Marshalling
 Relay Output Assembly w/Ch STO KUEP Form C, Fused, Customer Termination
 Relay Output Assembly KUEP Form X, Fused, Customer Termination
Module tab parameters for select Relay Output modules
Timeout Action Configures the timeout action for the available channels. Check the appropriate
(Latch) channel check boxes to configure the timeout action as Latch, which is after the
timeout period, the last output remains.
If the appropriate channel check box(es) is not selected, the timeout action for
that channel(s) is Reset, which is after the timeout period, output clears.
 16 seconds
 4 seconds
 2 seconds
 1 second
Blown Fuse Should be set; the module reports a blown fuse and lights the “E” LED.
Detection
256 OW351_60
Applies to:
 32 CH Relay Output w/O Fuse
 32 CH Relay Output w/Fuse
 Relay Output w/Contact Mon & w/Ch STO KUEP Form X, Marshalling
 Relay Output w/Contact Mon & w/Ch STO KUEP Form X, Customer Termination
 Relay Output Module G2R
 Relay Output Module KUEP
 Relay Output Assembly G2R Fused, Marshalling
 Relay Output Assembly G2R Fused, Customer Termination
 Relay Output Assembly KUEP Form C, Fused, Marshalling
 Relay Output Assembly KUEP Form X, Fused, Marshalling
 Relay Output Assembly KUEP Form C, Fused, Customer Termination
 Relay Output Assembly KUEP Form X, Fused, Customer Termination
 Relay Output w/Contact Mon Assembly KUEP Form X, Marshalling
 Relay Output w/Contact Mon Assembly KUEP Form X, Customer Termination
Module tab parameters for select Relay Output modules
 16 seconds
 4 seconds
 2 seconds
 1 second
Detection
OW351_60 257
9.4.16 RT D module configuration
The following tables describe the Module tab parameters for the RTD modules.
Applies to:
 RTD Interface
 RTD Interface (CE Mark certified)
Module tab parameters for select RTD modules
Default is 60 Hz.
Suppress Point Fault Permits the RM module point from going into alarm if one or more of the analog
Mode Alarm inputs are in an alarm or sensor condition. For example, if one or more
channel(s) of a 4-20 mA card are unused (and left open), setting this attribute
RTD Selections
Channel 1 Scale See RTD values (4-channel) (see page 262) for details on the drop-down menu
options.
Channel 2 Scale
Channel 3 Scale Note: The default value is Unused Channel.
Channel 4 Scale
258 OW351_60
Applies to:
 RTD Interface (8 channel)
 RTD Interface (8 channel) (CE/61131-2)
 8 CH RTD Input
Default is 60 Hz.
RTD Selections
Channel 1 Scale See RTD values (8-channel) (see page 263) for details on the drop-down menu
options.
Channel 2 Scale
Channel 3 Scale Note: The default value is Unused Channel.
Channel 4 Scale
Channel 5 Scale
Channel 6 Scale
Channel 7 Scale
Channel 8 Scale
Applies to:
 16 CH RTD Input
Channel Configurations
Channel 1/2 Configuration Use the drop-down menu to configure the channel pairs for the
supported ohmic ranges:
Channel 3/4 Configuration
 31.25 ohms
Channel 5/6 Configuration  125 ohms
 500 ohms
 1000 ohms
Note: The default value is 31.25 ohms.
RTD Selections
Channel 1 Scale See RTD values (16-channel and 8-channel compact) (see page 265) for
OW351_60 259
Channel 1 R(cold) details on the drop-down menu options.
Channel 1 R(hot) Note: The default value is Unused Channel.

Channel 2 Scale
Channel 2 R(cold)
Channel 2 R(hot)
Channel 3 Scale
Channel 3 R(cold)
Channel 3 R(hot)
Channel 4 Scale
Channel 4 R(cold)
Channel 4 R(hot)
Channel 5 Scale
Channel 5 R(cold)
Channel 5 R(hot)
Channel 6 Scale
Channel 6 R(cold)
Channel 6 R(hot)
Channel 7 Scale
Channel 7 R(cold)
Channel 7 R(hot)
Channel 8 Scale
Channel 8 R(cold)
Channel 8 R(hot)
Channel 9 Scale
Channel 9 R(cold)
Channel 9 R(hot)
Channel 10 Scale
Channel 10 R(cold)
Channel 10 R(hot)
Channel 11 Scale
Channel 11 R(cold)
Channel 11 R(hot)
Channel 12 Scale
Channel 12 R(cold)
260 OW351_60
Channel 12 R(hot)
Channel 13 Scale
Channel 13 R(cold)
Channel 13 R(hot)
Channel 14 Scale
Channel 14 R(cold)
Channel 14 R(hot)
Channel 15 Scale
Channel 15 R(cold)
Channel 15 R(hot)
Channel 16 Scale
Channel 16 R(cold)
Channel 16 R(hot)
Applies to:
 8 CH Compact RTD Input
Channel Configurations
Channel 1 Configuration Use the drop-down menu to configure the channel pairs for the
supported ohmic ranges:
Channel 2 Configuration
 31.25 ohms
Channel 3 Configuration  125 ohms
 250 ohms
 500 ohms
Channel 7 Configuration Note: The default value is 31.25 ohms.

OW351_60 261
RTD Selections
Channel 1 Scale See RTD values (16-channel and 8-channel compact) (see page 265) for
details on the drop-down menu options.
Channel 1 R(cold)
Channel 1 R(hot) Note: The default value is Unused Channel.
Channel 2 Scale
Channel 2 R(cold)
Channel 2 R(hot)
Channel 3 Scale
Channel 3 R(cold)
Channel 3 R(hot)
Channel 4 Scale
Channel 4 R(cold)
Channel 4 R(hot)
Channel 5 Scale
Channel 5 R(cold)
Channel 5 R(hot)
Channel 6 Scale
Channel 6 R(cold)
Channel 6 R(hot)
Channel 7 Scale
Channel 7 R(cold)
Channel 7 R(hot)
Channel 8 Scale
Channel 8 R(cold)
Channel 8 R(hot)
262 OW351_60
RTD values (4-channel)
4-channel RTD values
% O F SPA N
EXC I T A T I ON
ACCURACY
ACCURACY
C
C U R R EN T
F
SC A L E #
C OU N T S
O
R C OL D
WI R E S
(H EX)
(OH M )
(OH M )
R H OT
TE M P
TE M P
(M A )
TY P E
1 3 10 Ohm Pl 0 to 1200 –18 to 649 6 106.3 0.1556 9 0.22
2 3 10 Ohm Cu 0 to 302 –18 to 150 8.5 16.5 1.51 13 0.32
D 3 50 Ohm Cu 32 to 284 0 to 140 50 80 1.0756 11 0.27
11 3 50 Ohm Cu 32 to 230 0 to 110 53 78 1.1291 12 0.30
19 3 100 Ohm Pl –4 to 334 –20 to 168 92 163.67 0.5121 11 0.27
22 3 100 Ohm Pl 32 to 520 0 to 271 100 200 0.4087 10 0.25
23 3 100 Ohm Pl 32 to 1040 0 to 560 100 301 0.2554 10 0.25
25 3 120 Ohm Ni 12 to 464 –11 to 240 109 360 0.2104 10 0.25
26 3 120 Ohm Ni 32 to 150 0 to 66 120 170 0.5240 13 0.32
28 3 120 Ohm Ni 32 to 278 0 to 122 120 225 0.3682 11 0.27
80 4 100 Ohm Pl 32 to 554 0 to 290 100 208 0.3921 10 0.25
81 4 100 Ohm Pl 356 to 446 180 to 230 168 186 0.5240 30 0.74
82 4 200 Ohm Pl 32 to 698 0 to 370 200 473 0.1675 12 0.30
83 4 200 Ohm Pl 514 to 648 268 to 342 402 452 0.2142 29 0.71
84 4 100 Ohm Pl 32 to 124 0 to 51 100 120 0.7860 19 0.47
85 4 100 Ohm Pl 32 to 217 0 to 103 100 140 0.6386 13 0.32
86 4 100 Ohm Pl 32 to 412 0 to 211 100 180 0.4644 11 0.27
87 4 100 Ohm Pl 32 to 714 0 to 379 100 240 0.3296 10 0.25
88 4 200 Ohm Pl 511 to 662 266 to 350 200 230 0.4170 24 0.59
OW351_60 263
RTD values (8-channel)
8-channel RTD values
SC A L E # H EX)
R C OL D (OH M )
% O F SPA N
R H OT (OH M )
EXC I T A T I ON
ACCURACY
ACCURACY
C
C U R R EN T
F
SC A L E #
(H E X ) 1
C OU N T S
O
O
WI R E S
TE M P
TE M P
(M A )
TY P E
2
0 0 3 10 Ohm Pl 0 to 1200 –18 to 649 6 106.3 1.0 9 0.22

1 1 3 10 Ohm Cu 0 to 302 –18 to 150 8.5 16.5 1.0 13 0.32
2 2 3 50 Ohm Cu 32 to 284 0 to 140 50 80 1.0 11 0.27
3 3 3 50 Ohm Cu 32 to 230 0 to 110 53 78 1.0 12 0.30
4 4 3 100 Ohm Pl –4 to 334 –20 to 168 92 163.6 1.0 11 0.27
7
5 5 3 100 Ohm Pl 32 to 520 0 to 271 100 200 1.0 10 0.25
6 6 3 100 Ohm Pl 32 to 1040 0 to 560 100 301 1.0 10 0.25
7 7 3 120 Ohm Ni 12 to 464 –11 to 240 109 360 1.0 10 0.25
8 8 3 120 Ohm Ni 32 to 150 0 to 66 120 170 1.0 13 0.32
9 9 3 120 Ohm Ni 32 to 278 0 to 122 120 225 1.0 11 0.27
0 10 4 100 Ohm Pl 32 to 554 0 to 290 100 208 1.0 10 0.25
1 11 4 100 Ohm Pl 356 to 446 180 to 230 168 186 1.0 30 0.74
2 12 4 200 Ohm Pl 32 to 698 0 to 370 200 473 1.0 12 0.30
3 13 4 200 Ohm Pl 514 to 648 268 to 342 402 452 1.0 29 0.71
4 14 4 100 Ohm Pl 32 to 124 0 to 51 100 120 1.0 19 0.47
5 15 4 100 Ohm Pl 32 to 217 0 to 103 100 140 1.0 13 0.32
6 16 4 100 Ohm Pl 32 to 412 0 to 211 100 180 1.0 11 0.27
7 17 4 100 Ohm Pl 32 to 714 0 to 379 100 240 1.0 10 0.25
8 18 4 200 Ohm Pl 511 to 662 266 to 350 200 230 1.0 24 0.59
9 19 4 100 Ohm Pl -4 to 334 -20 to 168 92 164 1.0 11 0.27
A 20 4 100 Ohm Pl 32 to 520 0 to 271 100 200 1.0 10 0.25
B 21 4 100 Ohm Pl 32 to 1040 0 to 560 100 301 1.0 10 0.25
C 22 4 100 Ohm Pl -94 to 237 -70 to 114 72 144 1.0 10 0.25
D 23 4 100 Ohm Pl -58 to 419 -50 to 215 80 181 1.0 10 0.25
E 24 4 100 Ohm Pl -58 to 930 -50 to 499 80 281 1.0 10 0.25
1 For Hardware configuration.
2 For Software purposes. This value is used in Import/Export files.
264 OW351_60
RTD values (16-channel and 8-channel compact)
16-channel RTD and 8-channel compact RTD values
S C AL E R( C O L D ) I N OH M R( H O T ) I N OH M
Unused Channel NA NA
3W 10 Ohm Pl (0 to 1200F) (-18 to 649C) 6 106.3
3W 10 Ohm Cu (0 to 302F) (-18 to 150C) 8.5 16.5
3W 50 Ohm Cu (32 to 284F) (0 to 140C) 50 80
3W 50 Ohm Cu (32 to 230F) (0 to 110C) 53 78
3W 100 Ohm Pl (-4 to 334F) (-20 to 168C) 92 163.67
3W 100 Ohm Pl (32 to 520F) (0 to 271C) 100 200
3W 100 Ohm Cu (-148 to 500F) (-100 to 260C) 56.76 211.57
3W 100 Ohm Pl (32 to 1040F) (0 to 560C) 100 300
3W 120 Ohm Ni (12 to 464F) (-11 to 240C) 109 360
3W 120 Ohm Ni (32 to 150F) (0 to 66C) 120 170

3W 120 Ohm Ni (32 to 278F) (0 to 122C) 120 225
3W 500 Ohm Pl (32 to 932F) (0 to 500C) 500 1404.9
Note: The additional selection Custom is utilized in cases where you have chosen a particular
RTD that is not on the pre-defined list of RTDs.
9.4.17 Se quence of Ev ents module configuration
The following tables describe the Module tab parameters for the Sequence of Events modules.
Applies to:
 32-Channel Sequence of Events contact input w/48V wetting
Module tab parameters for select Sequence of Events modules
Chatter Control Action Chatter control counter is reset or decremented every 100 milliseconds.
Reset setting is recommended.
Chatter Control Disable Emerson recommends that this parameter should not be set, which
enables the chatter control.
Ground Fault Detection Use this parameter to detect whether the input line or return line for any
channel has a ground fault.
Contact Wetting Voltage Use this parameter to detect the wetting voltage failure at the contact input.
Failure Detection
Event Tagging Enable Channels (1-16 and 17-32) that are set for the event tagging mask.
Event Tagging Enable Note: All channels enab led for event tagging MUST have an associated
(CH17-32) digital point configured.
OW351_60 265
Applies to:
 Sequence of Events enhanced contact input w/48V wetting
 Sequence of Events 24VDC or 48VDC differential
 Sequence of Events 125VDC differential
 Sequence of Events contact input w/48V wetting
 Sequence of Events compact 24VDC or 48VDC differential
 Sequence of Events compact 24/48V diff. individually fused
 Sequence of Events compact 125VDC diff. individually fused
 Sequence of Events compact 125VDC differential
 Sequence of Events compact contact input w/48V wetting
 SOE compact digital input 24 VDC w/ Ind Ch Current Limiter
Contact Wetting Voltage Use this parameter to detect the wetting voltage failure at the contact
Failure Detection input.
Event Tagging Enable Channels (1-16) that are set for the event tagging mask.
Note: All channels enab led for event tagging MUST have an associated
digital point configured.
266 OW351_60
Applies to:
 Sequence of Events 24VDC or 48VDC single ended
 Sequence of Events 125VDC single ended
 Sequence of Events compact 24VDC or 48VDC single ended
Contact Wetting Voltage Use this parameter to detect the wetting voltage failure at the contact input.
Failure Detection
Blown Fuse Detection When set, the module reports a blown fuse and lights the “E” LED.
Applies to:
 Sequence of Events enhanced 24/48VDC single ended
Chatter Control Action Chatter control counter is reset or decremented every 100 mil liseconds.
Blown Fuse Detection When set, the module reports a blown fuse and lights the “E” LED.
OW351_60 267
Applies to:
 Sequence of Events enhanced 24/48VDC differential
 Sequence of Events enhanced 24/48VDC single ended individually fused
 Sequence of Events enhanced 125VDC differential
 Sequence of Events enhanced 125VDC single ended individually fused
 Enhanced SOE Compact Digital Input 24 VDC w/ Ind Ch current limiter
Applies to:
 Sequence of Events enhanced 24VDC differential w/wirebreak detect
 Sequence of Events enhanced 24VDC ind. fused w/wirebreak detect
 Enhanced SOE Compact Digital Input 24 VDC w/ Ind Ch current limiter WBD
Wire Break Detect Enable Use this parameter to enable the wire break detection capability.
268 OW351_60
9.4.18 Se rial Link Controller module configuration
Applies to:
 Serial Link Controller RS232 (Ver 2)
 Serial Link Controller RS232
 Serial Link Controller RS485 4 wire (Ver 2)
 Serial Link Controller RS485 4 wire
Module tab parameters for select Serial Link Controller modules
No parameter No parameter appears in the Serial Link Controller Module tab.
9.4.19 Se rvo Drive module configuration
The following table describes the Module tab parameters for the Servo Drive modules.
Applies to:
 Servo Drive with Readback DC LVDT Output

 Servo Drive with Readback 1 kHz LVT Output
 Servo Drive with Readback 3 kHz LVT Output
 Servo Drive w/Readback DC LVDT Output, Firmware Download(CE/61131-2)
 Servo Drive w/Readback 1 kHz LVT Output, Firmware Download(CE/61131 -2)
 Servo Drive w/Readback 3 kHz LVT Output, Firmware Download(CE/61131 -2)
Module tab parameters for select Servo Drive modules
IO Bus Timeout Drop-down menu used to define the timeout period:

Bits  16 seconds
 4 seconds
 2 seconds
 1 second
OW351_60 269
9.4.20 Spe e d De tector module configuration
The following tables describe the Module tab parameters for the Speed Detector modules.
Applies to:
 Speed Detector Interface
Module tab parameters for select Speed Detector modules
Number of Teeth Number of teeth on the output gear (that is, pulses per revolution).
Gear Ratio Ratio between motor/device and the output gear.
Overspeed Limit (RPM) Overspeed limit at the motor.
Overspeed Limit (PPS) at Read-only information parameter.
module
Nominal Speed (RPM) Nominal speed at the motor.
Req. Update Period (msec) Maximum time in microseconds for the speed calculation requested for
at Nominal Speed high-resolution reading. When motor operates at nominal speed or
faster, the update period is guaranteed to be less than the requested
update period.
Pulse Count per Update Pulse Count per Update is a read-only information parameter. It displays
the number of pulses used for high revolution speed calcu lation.
Open Wire Test Enabled Enables the option that the module checks for a broken wire, and if the
source resistor is below 1000 ohms.
Overspeed/Overacceleration There are four different modes for energizing the relay outputs when an
Mode overspeed/overacceleration condition exists.
Mode 1 - Controller command or card overspeed/overacceleration
trip
Relay is energized by the Controller or the module when an
overspeed/overacceleration condition is detected.
Mode 2 - Card overspeed/overacceleration trip only
Relay is energized by the module when an overspeed/overacceleration
condition is detected.
Mode 3 - Controller command only
Relay is energized by the Controller.
Mode 4 - Controller command or card overspeed trip with controller
timed out
Relay is energized by the Controller when an overspeed condition is
detected. However, the relay can be energized by the module if the
Controller is timed out for 2 seconds and an overspeed condition is
detected.
Note: Mode 4 is the recommended default mode.
270 OW351_60
Applies to:
 Speed Detector Interface (Acceleration)
module
update period.
Pulse Count per Update Pulse Count per Update is a read-only information parameter. It
displays the number of pulses used for high revolution speed
calculation.
trip
Mode 4 - Controller command or card overspeed trip with
controller timed out
detected.
Acceleration Measurement Enables the acceleration measurement filtering.

Filtering Enabled
Acceleration Measurement Performs acceleration measurement on the basis of the low-resolution
based on Low-Res Speed speed value.
OW351_60 271
Applies to:
 Speed Detector Interface (Enhanced)
 Speed Detector Interface (G04)
Number of Teeth per Sample Number of pulses per sample.
Number of Samples per Rev Suggested number of samples in a revolution.
(suggested)
Number of Samples per Rev Actual number of samples in a revolution.

Mechanical Trip Speed Mechanical Trip speed in revolutions per minute (rpm).
(RPM)
Update Period at Nominal Maximum time (in microseconds) for the speed calculation, requested for
Speed (msec) high-resolution reading. When the motor operates at nominal speed or
update period.
Interrupt Rate at Mechanical Interrupt rate (in Hz) during a mechanical trip.
Trip Speed (Hz)
trip
timed out
detected.
272 OW351_60
Speed Filtering Enabled Enables the speed filtering mechanism.
Acceleration Filtering Enables the acceleration filtering mechanism.

Enabled
Disable Filtering Disables the filtering mechanism.
Acceleration-Only Limiting Enables the acceleration-only limiting. The acceleration limit is an I/O
point. If the Controller is continuously updating the value of the I/O point
and the value is exceeded, the relay is activated. The limit can be an
acceleration-only value in rpm/min.
9.4.21 Valv e Position Controller module configuration
The following tables describe the Module tab parameters for the Valve Position Controller
modules.
Applies to:
 Valve Position Controller Enhanced 17 Volt LVDT: 24.9 mA
 Valve Position Controller Enhanced 17 Volt LVDT: 36 mA
 Valve Position Controller Enhanced 24 Volt DC LVDT: 50 mA (G03)
 Valve Position Controller Enhanced 23.75 Volt LVDT: 24.9 mA
 Valve Position Controller Enhanced 23.75 Volt LVDT: 36 mA
 Valve Position Controller Enhanced 24 Volt DC LVDT: 50 mA (G04)
OW351_60 273
Module tab parameters for select Valve Position Controller modules
IO Bus Timeout Bits Drop-down menu used to define the timeout period:
 16 seconds
 4 seconds
 2 seconds
 1 second
Ignore Shutdown If selected, the Valve Positioner module ignores the input in Normal mode.
Input
If not selected, the Valve Positioner module closes the valve when the
shutdown input is activated.
Feedback A Select from the following options in the drop-down menu:
Configuration  6-wire LVDT
Feedback B  4-wire LVDT
Configuration  4-20mA
 Reserved
RS485 Select from the following options in the drop-down menu:

Magnetostrictive  Not used
Sensor
 Start/STOP protocol
 SSI protocol
 Reserved
Dual Channel / Select from the following options in the drop-down menu:
Backup Feedback  Reserved
 Dual Channel
 Backup Feedback
274 OW351_60
Applies to:
 Valve Position Controller 17 Volt LVDT: 24.9 mA
 Valve Position Controller 17 Volt LVDT: 36 mA
 Valve Position Controller 24 Volt DC LVDT: 50 mA (G01)
 Valve Position Controller 23.75 Volt LVDT: 24.9 mA
 Valve Position Controller 23.75 Volt LVDT: 36 mA
 Valve Position Controller 24 Volt DC LVDT: 50 mA (G02)
Module tab parameters for select Valve Position Controller modules
 16 seconds
 4 seconds
 2 seconds
 1 second
Input
OW351_60 275
9.4.22 Digital Excitation Controller module configuration
The following table describes the Module tab parameters for the Digital Excitation Controller
modules.
Applies to:
 Digital Excitation Controller +/-10V Analog Outputs
 Digital Excitation Controller 4-20mA Analog Outputs
Module tab parameters for select Digital Excitation Controller module
Timeout Selection Defines the timeout period:

 16 seconds
 4 seconds
 2 seconds
 1 second
Redundancy
Network Interface 1
 Auto-negotiate
Network Interface 2
 Auto-negotiate
276 OW351_60
General Network Configuration
Default Gateway IP Specifies the IP Address of the default gateway used by the module.
Address
Time Sync Type Specifies the source of time synchronization:
 RLine (Controller group write)
 NTP
NTP Server IP Specifies the IP address of the NTP server that should be synchronized
Address with the module.
Digital Excitation
Timeout Action Trip Unit: After the timeout period in a redundant module configuration, if
the backup module is able to control, the module fails over to the backup.
However, the unit trip digital output activates in the following scenarios:
 In a non-redundant module configuration.
 In a redundant configuration if the backup module is not able to control.
 If the failover has already occurred.
Relinquish Control: After the timeout period in a redundant module
configuration, if the backup module is able to control, the module fails over
to the backup. The module exits automatic control mode and holds its
demand output at “no demand” in the following scenarios:
 In a non-redundant module configuration.
 In a redundant configuration if the backup module is not able to control.
 If the failover has already occurred.
Redundant PT Enables processing of the redundant potential transformer inputs.
Enabled
CTA Enabled Enables processing of the phase A current transformer input.
CTB Enabled Enables processing of the phase B current transformer input.
CTC Enabled Enables processing of the phase C current transformer input.
Field Current 2 Enables processing of the field current transducer 2 input.
Enabled
Rotor Current Enables processing of the generator rotor current input.
Enabled
PT Rotation Specifies the rotation of the potential transformer.
 ABC
 ACB
OW351_60 277
9.4.23 Foundation Fieldbus module configuration
The following tables describe the Module tab parameters for the Foundation Fieldbus modules.
Applies to:
 Foundation Fieldbus BusModule
Module tab parameters for select Foundation Fieldbus modules
No parameter No parameter appears in the Foundation Fieldbus Module tab.
Applies to:
 Foundation Fieldbus BusModule (Redundant)
Module tab parameters for select Foundation Fieldbus modules
Redundancy
9.4.24 Profibus module configuration
The following table describes the Module tab parameters for the Profibus modules.
Applies to:
 Profibus BusModule
 Profibus BusModule (Time Synchronization)
Module tab parameters for select Profibus modules
Redundancy
Redundancy Specifies the type of redundancy:
 Simplex / Port Redundancy: Select this option if Ovation Profibus Port
Redundancy is used for ports on the module. This option is also used if
the I/O module is used for a simplex, that is, non-redundant
configuration.
 Module-Level Redundancy: Select this option if module redundancy is
used for ports on the module.
278 OW351_60
9.4.25 De v iceNet module configuration
Applies to:
 DeviceNet BusModule
Module tab parameters for select DeviceNet modules
No parameter No parameter appears in the DeviceNet Module tab.
9.4.26 Ethe rnet Link module configuration
The following table describes the Module tab parameters for the Ethernet Link modules.
Applies to:
 Ethernet Link BusModule

 Ethernet Link BusModule (Time Synchronization)
Module tab parameters for select Ethernet Link modules
Redundancy
Network Configuration
IP Address Specifies the IP Address.
Shared IP Address Specifies the Shared IP Address.
Subnet Mask Specifies the Subnet Mask.
Default Route Specifies the default route.
Communicate via Network Select the box to allow the module to communicate via network.
Scan Rate (msec) Set as 1000.
OW351_60 279
9.5 QLine module configuration
QLine modules can be further categorized as follows:

 QLine Analog Input modules (see page 280).
 QLine Analog Output modules (see page 283).
 QLine HART High Performance Analog Input modules (see page 284).
 QLine HART High Performance Analog Output modules (see page 284).
 QLine RTD modules (see page 285).
 QLine Compact Contact Input modules (see page 288).
 QLine Digital Input modules (see page 288).
 QLine Digital Output modules (see page 289).
 QLine Loop Interface modules (see page 290).
 QLine Pulse Accumulator modules (see page 292).
 QLine Relay Output modules (see page 295).
 QLine Sequence of Events modules (see page 296).
 QLine Serial Link Controller modules (see page 296).
 QLine Servo Drive modules (see page 297).
 QLine Valve Position Controller modules (see page 298).
 QLine Speed Detector modules (see page 300).
280 OW351_60
9.5.1 QLine Analog Input module configuration
The following tables describe the Module tab parameters for the QLine Analog Input modules.
Applies to:
 QLine 8-Ch Analog Input 14 bit HS +/-5V,10V

 QLine 4-Ch Analog Input 14 bit MS +/-20mV,50mV,100mV w/OTD
 QLine 6-Ch Analog Input 14 bit MS +/-20mV,50mV,100mV w/OTD, no OTC
 QLine 6-Ch Analog Input 14 bit MS +/-20mV,50mV,100mV w/OTD, w/OTC
 QLine 6-Ch Analog Input 14 bit HS +/-5V,10V w/OTD, no OTC
 QLine QAX 6-Ch Analog Input 14 bit HS +/-5V,10V w/OTD, no OTC
 QLine QAX 6-Ch Analog Input 14 bit MS +/-20mV,50mV,100mV w/OTD, no OTC
 QLine 8-Ch Analog Input 14 bit HS +/-5V,10V (Old Latch)
 QLine 4-Ch Analog Input 14 bit MS +/-20mV,50mV, 100mV w/OTD (Old Latch)
 QLine 6-Ch AI 14 bit MS +/-20mV,50mV,100mV w/OTD, no OTC (Old Latch)
 QLine 6-Ch AI 14 bit MS +/-20mV,50mV,100mV w/OTD, w/OTC (Old Latch)
 QLine 6-Ch Analog Input 14 bit HS +/-5V,10V w/OTD, no OTC (Old Latch)
 QLine QAX 6-Ch AI 14 bit HS +/-5V,10V w/OTD, no OTC (Old Latch)
 QLine QAX 6-Ch AI 14bit MS +/-20mV,50mV,100mV w/OTD,no OTC (Old Latch)
Module tab parameters for select QLine Analog Input modules
Default is 60 Hz.
Selection
fault module alarm.
OW351_60 281
Applies to:
 QLine 4-Ch Analog Input 14 bit HS +/-1V
 QLine 4-Ch Analog Input 14 bit HS +/-10V
 QLine 4-Ch Analog Input 14 bit HS 0 to 20mA
 QLine 6-Ch Analog Input 14 bit HS +/-1V w/OTD, no OTC
 QLine 6-Ch Analog Input 14 bit HS 0 to 20mA local powered
 QLine 6-Ch Analog Input 14 bit HS 4 to 20mA local powered
 QLine QAX 6-Ch Analog Input 14 bit HS +/-1V w/OTD, no OTC
 QLine 4-Ch Analog Input 14 bit HS +/-1V (Old Latch)
 QLine 4-Ch Analog Input 14 bit HS +/-10V (Old Latch)
 QLine 4-Ch Analog Input 14 bit HS 0 to 20mA (Old Latch)
 QLine 6-Ch Analog Input 14 bit HS +/-1V w/OTD, no OTC (Old Latch)
 QLine 6-Ch Analog Input 14 bit HS 0 to 20mA local powered (Old Latch)
 QLine 6-Ch Analog Input 14 bit HS 4 to 20mA local powered (Old Latch)
 QLine QAX 6-Ch Analog Input 14 bit HS +/-1V w/OTD, no OTC (Old Latch)
Default is 60 Hz.
RM module point from going into alarm. The default is to NOT suppress the poi nt
fault module alarm.
Applies to:
 QLine 6 CH Analog Input HI 0-10V
No parameter No parameter appears in the QLine Analog Input Module tab because user
configuration is not required for the module.
282 OW351_60
9.5.2 QLine Analog Output module configuration
The following table describes the Module tab parameters for the QLine Analog Output modules.
Applies to:
 QLine 4-Ch Analog Output 0 to 20mA w/ diagnostics

 QLine 4-Ch Analog Output 4 to 20mA w/ diagnostics
 QLine 4-Ch Analog Output 0 to +10V
 QLine 4-Ch Analog Output 0 to +5V
 QLine 4-Ch Analog Output 0 to 20mA w/ diagnostics (Old Latch)
 QLine 4-Ch Analog Output 4 to 20mA w/ diagnostics (Old Latch)
 QLine 4-Ch Analog Output 0 to +10V (Old Latch)
 QLine 4-Ch Analog Output 0 to +5V (Old Latch)
Module tab parameters for select QLine Analog Output modules

 16 seconds
 4 seconds
 2 seconds
 1 second
OW351_60 283
9.5.3 QLine HART High Pe rformance Analog Input module configuration
The following table describes the Module tab parameters for the QLine High Performance Analog
Input modules.
Applies to:
 QLine 6-Ch HART High Perf. Analog Input, 4 to 20 mA (24V AUX Power)
 QLine 6-Ch HART High Perf. Analog Input, 4 to 20 mA (24V Ext Power)
 QLine QAX/G05 6-Ch HART High Performance Analog Input, 4 to 20 mA
 QLine 6-Ch HART High Perf. AI, 4 to 20 mA (24V AUX Power) (Old Latch)
 QLine 6-Ch HART High Perf. AI, 4 to 20 mA (24V Ext Power) (Old Latch)
 QLine QAX/G05 6-Ch HART High Perf Analog Input, 4 to 20 mA (Old Latch)
Module tab parameters for select QLine High Performance Analog Input modules
Default is 60 Hz.
HART Device on This I/O card has eight channels. Therefore, this parameter has eight check
Channel boxes – one for each channel. To indicate a HART device is attached to a
Scan HART Use this parameter if you want to provide HART multiple variable support for any
Variables on of the eight channels. However, the channel(s) selected in this parameter must
Channel be defined in the parameter HART Device on Channel.
Suppress Point Permits the RM module point from going into alarm if one or more of the analog
Fault Module Alarm inputs are in an alarm or sensor condition. For example, if one or more
channel(s) of a 4-20 mA card are unused (and left open), setting this attribute
284 OW351_60
9.5.4 QLine HART High Pe rformance Analog Output module configuration
The following table describes the Module tab parameters for the QLine High Performance Analog
Output modules.
Applies to:
 QLine HART High Performance Analog Output, 4 to 20mA
 QLine HART High Performance Analog Output, 4 to 20mA (Old Latch)
Module tab parameters for select QLine High Performance Analog Output modules

 16 seconds
 4 seconds
 2 seconds
 1 second
HART Device on This I/O card has four channels. Therefore, this parameter has four check
Channel boxes – one for each channel. To indicate a HART device is attached to a
Scan HART Use this parameter if you want to provide HART multiple variable support for
Variables on any of the four channels. However, the channel(s) selected in this parameter
Channel must be defined in the parameter HART Device on Channel.
OW351_60 285
9.5.5 QLine RT D module configuration
The following tables describe the Module tab parameters for the QLine RTD modules.
Applies to:
 QLine RTD Interface (6 channel, 4-wire)

 QLine RTD Interface (6 channel, 4-wire) (Old Latch)
Module tab parameters for select QLine RTD modules
Default is 60 Hz.
RTD Selections
Channel 1 Scale Refer to the table RTD scrolling list values for details on the drop-down
menu options.
Channel 2 Scale
Channel 3 Scale
Channel 4 Scale
Channel 5 Scale
Channel 6 Scale
286 OW351_60
Applies to:
 QLine RTD Interface (4 channel, 3-wire)
 QLine RTD Interface (4 channel, 3-wire) (Old Latch)
Module tab parameters for select QLine RTD modules
Default is 60 Hz.
RTD Selections
Channel 1 Scale Refer to the table RTD scrolling list values for details on the drop-down
menu options.
Channel 2 Scale
Channel 3 Scale
Channel 4 Scale
RTD scrolling list values
% O F SPA N
EXC I T A T I ON
ACCURACY
ACCURACY
C
C U R R EN T
F
SC A L E #
C OU N T S
O
R C OL D
WI R E S
(H EX)
(OH M )
(OH M )
R H OT
TE M P
TE M P
TY P E
(M A )
1 3 10 Ohm Pl 0 to 1200 –18 to 649 6 106.3 0.1556 9 0.22
2 3 10 Ohm Cu 0 to 302 –18 to 150 8.5 16.5 1.51 13 0.32
D 3 50 Ohm Cu 32 to 284 0 to 140 50 80 1.0756 11 0.27
11 3 50 Ohm Cu 32 to 230 0 to 110 53 78 1.1291 12 0.30
19 3 100 Ohm Pl –4 to 334 –20 to 168 92 163.67 0.5121 11 0.27
22 3 100 Ohm Pl 32 to 520 0 to 271 100 200 0.4087 10 0.25
23 3 100 Ohm Pl 32 to 1040 0 to 560 100 301 0.2554 10 0.25
25 3 120 Ohm Ni 12 to 464 –11 to 240 109 360 0.2104 10 0.25
26 3 120 Ohm Ni 32 to 150 0 to 66 120 170 0.5240 13 0.32
28 3 120 Ohm Ni 32 to 278 0 to 122 120 225 0.3682 11 0.27
80 4 100 Ohm Pl 32 to 554 0 to 290 100 208 0.3921 10 0.25
81 4 100 Ohm Pl 356 to 446 180 to 230 168 186 0.5240 30 0.74
82 4 200 Ohm Pl 32 to 698 0 to 370 200 473 0.1675 12 0.30
83 4 200 Ohm Pl 514 to 648 268 to 342 402 452 0.2142 29 0.71
OW351_60 287
9.5.6 QLine Compact Contact Input module configuration
The following table describes the Module tab parameters for the QLine Compact Contact Input
modules.
Applies to:
 QLine Compact Contact Input w/ Onboard 48V wetting
 QLine Compact Contact Input w/ Onboard 48V wetting (Old Latch)
Module tab parameters for select QLine Compact Contact Input modules
Disable Points on Ground Fault When set, the module reports an error when an input line or return
line is shorted to earth ground, and lights the “E” LED.
9.5.7 QLine Digital Input module configuration
The following tables describe the Module tab parameters for the QLine Digital Input modules.
Applies to:
 QLine Digital Input 24/48 VDC single ended
 QLine Digital Input 24/48 VAC single ended
 QLine Digital Input 125 VDC single ended
 QLine Digital Input 125 VAC single ended
 QLine Digital Input 24/48 VDC
 QLine Digital Input 24/48 VAC
 QLine Digital Input 125 VDC
 QLine Digital Input 125 VAC
 QLine Digital Input 24/48 VDC single ended (Old Latch)
 QLine Digital Input 125 VDC single ended (Old Latch)
 QLine Digital Input 24/48 VDC (Old Latch)
 QLine Digital Input 125 VDC (Old Latch)
Module tab parameters for select QLine Digital Input modules
Blown Fuse Detection When set, if an auxiliary power supply fuse is blown, the module
reports an error and lights the “E” LED.
288 OW351_60
Applies to:
 QLine Digital Input 24VAC/VDC or 48VAC/VDC differential
 QLine Digital Input 125 VAC/VDC differential
 QLine Digital Input 24VAC/VDC or 48VAC/VDC differential (Old Latch)
 QLine Digital Input 125 VAC/VDC differential (Old Latch)
Module tab parameters for select QLine Digital Input modules
No parameter No parameter appears in the QLine Module tab.
9.5.8 QLine Digital Output module configuration
The following table describes the Module tab parameters for the QLine Digital Output modules.
Applies to:
 QLine Digital Output 5-60 VDC, IEEE SWC

 QLine Digital Output 5-60 VDC, no IEEE SWC
 QLine Digital Output 5-60 VDC, no IEEE SWC, 10K dim pull-up
 QLine Digital Output 5-60 VDC, IEEE SWC (Old Latch)
 QLine Digital Output 5-60 VDC, no IEEE SWC (Old Latch)
 QLine Digital Out 5-60 VDC, no IEEE SWC, 10K dim pull-up (Old Latch)
Module tab parameters for select QLine Digital Output modules
Timeout Selection Drop-down menu used to define the tim eout period:
 16 seconds
 4 seconds
 2 seconds
 1 second
Blown Fuse Detection When set, if a fuse is blown, the module reports an error and li ghts the “E”
LED.
OW351_60 289
9.5.9 QLine Loop Inte rface module configuration
The following tables describe the Module tab parameters for the QLine Loop Interface modules.
Applies to:
 QLine Loop Interface AI/AO: 0-10V

 QLine Loop Interface AI/AO: 0-10V User DI
 QLine Loop Interface AI: 0-5V AO: 0-10V
 QLine Loop Interface AI: 0-5V AO: 0-10V User DI
 QLine Loop Interface AI/AO: 4-20mA
 QLine Loop Interface AI/AO: 4-20mA User DI
 QLine Loop Interface AI/AO: 0-10V (Old Latch)
 QLine Loop Interface AI/AO: 0-10V User DI (Old Latch)
 QLine Loop Interface AI: 0-5V AO: 0-10V (Old Latch)
 QLine Loop Interface AI: 0-5V AO: 0-10V User DI (Old Latch)
 QLine Loop Interface AI/AO: 4-20mA (Old Latch)
 QLine Loop Interface AI/AO: 4-20mA User DI (Old Latch)
Module tab parameters for select QLine Loop Interface modules
Default is 60 Hz.
Digital Outputs on Shutoff: After the timeout period, output clears (output transistor shuts off.)
Controller Timeout
Hold: After the timeout period, the last output remains.
 4 seconds
 2 seconds
 1 second
290 OW351_60
Inverse Analog Output Select the check box if you want the module to perform an inverse analog
Setpoint 1 The process variable can then be configured as the analog point assigned to
analog channel 8.
Applies to:
 QLine Loop Interface AI: 4-20mA

 QLine Loop Interface AI: 4-20mA User DI
 QLine Loop Interface AI: 4-20mA (Old Latch)
 QLine Loop Interface AI: 4-20mA User DI (Old Latch)
Module tab parameters for select QLine Loop Interface modules
A/C Line Frequency Defines the type of A/C line frequency used in the system (5 0 Hz or 60 Hz).
Default is 60 Hz.
 4 seconds
 2 seconds
 1 second
Digital Outputs Start Off Time: Pulses start with Off time.
With
On Time: Pulses start with On time.
OW351_60 291
Electric Drive Mode Electric drive provides two mode options:

 Normal (Mode 1): Calculates process variable as normal type. Output is 2
digital outputs (raise/lower.)
 Mode 2: Calculates process variable. Output is 2 digital outputs.
For all modes except local, a demand of 0 forces the lowest limit.
Inverse Analog Output Select the check box if you want the module to perform an inverse an alog
Setpoint 1 The process variable can then be configured as the analog p oint assigned to
analog channel 8.
9.5.10 QLine Pulse Accumulator module configuration
The following table describes the Module tab parameters for the QLine Pulse Accumulator
modules.
Applies to:
 QLine Pulse Accumulator 24/48V 5/12V med speed
 QLine Pulse Accumulator 5V high speed
 QLine Pulse Accumulator 24/48V 5/12V med speed (Old Latch)
 QLine Pulse Accumulator 5V high speed (Old Latch)
Module tab parameters for select QLine Pulse Accumulator modules
All parameter descriptions are applicable to Channel 1 or Channel 2.

Count Type Field input voltage range that defines different terminal block connections:
 5 V (high speed)
 12 V (medium speed)
 24/48 V
292 OW351_60
Configuration  A: Count pulses until reset by Controller.

Style  B: Count pulses count and reset.
(See the next  C: Measure width of long pulse.
table for a  D: Measure width of last pulse.
matrix of  E: Measure total width of several pulses since last read.
parameters to
 F: Measure period of repetitive pulses.
set for each
style.)  G: Measure pulse width ratios. Channel 1 measures pulse width. Channel 2
measures pulse period.
 H: Measure speed (frequency). Channel 1 is used for the time base. Channel 2
counts the input pulses.
Note: Configuration styles can b e mixed on a card, except styles G and H.
Count Select Selects input to the counter through bits 15 and 14 in register D:
 External
 1 KHz
 10 KHz
 100 KHz
Disable When set, the parameter disables the de-bounce (chattering or noise) on enable and
Debounce on snapshot inputs.
ENABLE and
SNAPSHOT
ENABLE for When set, the open time of an ENABLE input is measured.
OFF Input When not set, the closed time of an ENABLE input is measured.
Snapshot Count Select Leading to snapshot on the leading edge of an input pulse.
on Pulse Edge
Select Trailing to snapshot on the trailing edge of an input pulse.
Measure Close Time: The closed time of an ENABLE input is measured.
Open Time: The open time of an ENABLE input is measured.
The third radio button is selected where neither Close Time nor Open Time is
appropriate or applicable.
Increment Count Select Leading to increment count on the leading edge of an input pulse.
on Pulse Edge
Select Trailing to increment count on the trailing edge of an input pulse.
Reset on Read When set, the counter goes back to zero (0) after the pulse is read.
Debounce When set, the parameter de-bounces (reject chatter or noise) the input count.
Count Input
Compare and Only set for configuration H.
Snapshot
Reset on When set, the counter goes back to zero (0) after the snapshot occurs.
Snapshot
Enable When set, the counter is enabled to count and does not require the external ENABLE
command signal.
OW351_60 293
Parameters to configure for Pulse Accumulator Configuration Styles
P AR AME T E R Configuration style
A B C D E F G H
Module Record Point Name X X X X X X X X

Count Type X X X X X X X X
Configuration Style A B C D E F G H
Count Select X X X X X X
Disable Debounce on ENABLE and X X X X X X X
SNAPSHOT
ENABLE for OFF Input X X
Snapshot Count on Pulse Edge X X
Measure X X X
Increment Count on Pulse Edge X X
Reset on Read X X
Debounce Count Input X X X
Compare and Snapshot X
Reset on Snapshot X X X X
Enable command X X X X X
294 OW351_60
9.5.11 QLine Re lay Output module configuration
The following table describes the Module tab parameters for the QLine Relay Output modules.
Applies to:
 QLine 8-Ch Relay Output 140VAC/125VDC Res/Ind Form A (NO)

 QLine 8-Ch Relay Output 140VAC/125VDC Res/Ind Form B (NC)
 QLine 8-Ch Relay Output 140VAC/125VDC Res only Form A (NO)
 QLine 8-Ch Relay Output 140VAC/125VDC Res only Form B (NC)
 QLine 8-Ch Relay Output 140VAC Solid State
 QLine 8-Ch Relay Output 140VAC/125VDC Res/Ind Form A (NO) (Old Latch)
 QLine 8-Ch Relay Output 140VAC/125VDC Res/Ind Form B (NC) (Old Latch)
 QLine 8-Ch Relay Output 140VAC/125VDC Res only Form A (NO) (Old Latch)
 QLine 8-Ch Relay Output 140VAC/125VDC Res only Form B (NC) (Old Latch)
 QLine 8-Ch Relay Output 140VAC Solid State (Old Latch)
Module tab parameters for select QLine Relay Output modules

 16 seconds
 4 seconds
 2 seconds
 1 second
Detection
OW351_60 295
9.5.12 QLine Se quence of Ev e nts module con figuration
The following table describes the Module tab parameters for the QLine Sequence of Events
modules.
Applies to:
 QLine Sequence of Events compact contact input w/48V wetting
 QLine Sequence of Events compact contact In w/48V wetting (Old Latch)
Module tab parameters for select QLine Sequence of Events modules
Contact Wetting Voltage Use this param eter to detect the wetting voltage failure at the contact input.
Failure Detection
9.5.13 QLine Se rial Link Controller module configuration
Applies to:
 QLine Serial Link Controller RS232 (Ver 2)
 QLine Serial Link Controller RS232
 QLine Serial Link Controller RS485 4 wire (Ver 2)
 QLine Serial Link Controller RS485 4 wire
 QLine Serial Link Controller RS232 (Old Latch)
 QLine Serial Link Controller RS485 4 wire (Old Latch)
Module tab parameters for select QLine Serial Link Controller modules
No parameter No parameter appears in the QLine Serial Link Controller Module tab.
296 OW351_60
9.5.14 QLine Se rvo Drive module configuration
The following table describes the Module tab parameters for the QLine Servo Drive modules.
Applies to:
 QLine Servo Drive with Readback +/-16VDC LVDT Output

 QLine Servo Drive with Readback 19VAC 1 KHz LVT Output
 QLine Servo Drive with Readback 3 kHz LVT Output
 QLine Servo Drive w/Readback DC LVDT Output, Firmware Download
 QLine Servo Drive w/Readback 1 kHz LVT Output, Firmware Download
 QLine Servo Drive w/Readback 3 kHz LVT Output, Firmware Download
 QLine Servo Drive with Readback +/-16VDC LVDT Output (Old Latch)
 QLine Servo Drive with Readback 19VAC 1 KHz LVT Output (Old Latch)
Module tab parameters for select QLine Servo Drive modules
IO Bus Timeout Drop-down menu used to define the timeout period:

Bits  16 seconds
 4 seconds
 2 seconds
 1 second
OW351_60 297
9.5.15 QLine Valv e Position Controller module configuration
The following table describes the Module tab parameters for the QLine Valve Position Controller
modules.
Applies to:
 QLine Valve Position Controller 1 KHz LVDT, 82ohm
 QLine Valve Position Controller 1 KHz LVDT, 82ohm (Old Latch)
Module tab parameters for select QLine Valve Position Controller modules
 16 seconds
 4 seconds
 2 seconds
 1 second
Input
298 OW351_60
Applies to:
 QLine Valve Position Controller Enhanced 1KHZ LVDT: 25mA
 QLine Valve Position Controller Enhanced 1KHZ LVDT: 16.8 mA
 QLine Valve Position Controller Enhanced 1KHZ LVDT: 36 mA
 QLine Valve Position Controller Enhanced 3KHZ LVDT: 25mA
 QLine Valve Position Controller Enhanced 3KHZ LVDT: 36 mA
Module tab parameters for select QLine Valve Position Controller modules
 16 seconds
 4 seconds
 2 seconds
 1 second
Input
Feedback A Select from the following options in the drop-down menu:
Configuration  6-wire LVDT
Feedback B  4-wire LVDT
Configuration  Reserved
Dual Channel / Select from the following options in the drop-down menu:
Backup Feedback  Reserved
 Dual Channel
 Backup Feedback
OW351_60 299
9.5.16 QLine Speed De tector module configuration
The following table describes the Module tab parameters for the QLine Speed Detector modules.
Applies to:
 QLine Speed Detector Interface

 QLine Speed Detector Interface (Old Latch)
Module tab parameters for select QLine Speed Detector modules
module
update period.
Pulse Count per Update Pulse Count per Update is a read-only information parameter. It displays
the number of pulses used for high revolution speed calculation.
trip
timed out
detected.
300 OW351_60
SECTION 10
10 Adding and configuring redundant I/O modules
IN THIS SECTION
Understanding redundant I/O modules ..................................................................... 301

Hardware placement for redundant modules............................................................. 302
Redundant module failover and recovery.................................................................. 303
Adding redundant I/O modules ................................................................................ 303
10.1 Understanding redundant I/O modules
Redundant I/O modules allow the Ovation system to continue communicating with a device in the
event that one of the I/O modules fails. These two redundant I/O modules are referred to as the
Primary module and the Secondary module.
The module that is currently exchanging process point information between the device and the
Ovation Controller is referred to as the active module. The module that is waiting to take control
is the standby module. Note that the active module is not always the Primary module. Refer to
Redundant module failover and recovery (see page 303).
OW351_60 301
10.2 Hardware placement for redundant modules
10.2 Hardware placement for redundant modules
Redundant I/O modules must be physically located on adjacent branches. The Primary module
must be located on an odd branch with the lower hardware address. The corresponding
Secondary module is located on the next higher even branch. The redundant modules can be
located in any slot on the adjacent branches, but are normally located directly across from each
other.
Figure 121: Example of redundant module placement in branches
Redundant I/O modules must be physically connected using two NULL modem serial
communication cables. These are used by the modules to exchange redundancy status
information.
302 OW351_60
10.3 Redundant module failover and recovery
10.3 Redundant module failover and recovery
The Ovation Controller monitors the status of the active and standby modules to determine when
to trigger a failover. A failover is triggered if the active module fails and the standby module is able
to take control. The following conditions will cause a module to fail:
 Loss of communication.
 Module hardware failure.
 Rebooting the module.
You can manually trigger a failover by pulling the active module from the backplane or by
rebooting the module using the Reboot Module button in the Controller Diagnostic Tool. (Refer to
the applicable Ovation Controller User Guide for more information on the Controller Diagnostic
Tool.)
The Ovation Controller triggers a failover by commanding the active module to go to standby
mode and then commanding the standby module to go to the active mode. The standby module
will remain in standby mode until the fault condition is cleared and it is commanded to go to the
active mode. The Primary module does not automatically reassume the active mode. In some
cases, it may be necessary to reboot the module to clear the fault condition.
10.4 Adding redundant I/O modules
Use the following procedures to add and configure redundant I/O modules.
10.4.1 Be fore adding re dundant I/O module s
The procedures for adding and configuring redundant modules are similar to adding and
configuring single I/O modules, with a few differences. Ensure that the following prerequisites are
met before you add redundant I/O modules:
 Ensure that you have the appropriate engineering privileges that are needed to add I/O
modules to the Ovation system.
 Ensure that the redundant modules are located in the correct slots in the correct branches
(see page 302).
 You should be familiar with point naming conventions for module records.
 You should know how to use the Controller Diagnostic Tool to download firmware to the I/O
modules. See the applicable Ovation Controller User Guide for more information.
OW351_60 303
10.4.2 T o add the de v ice numbe r to the Controller
Note: The following procedure is only performed once. If you already added a specific driver,
you do not have to perform this procedure.

2. Use the system tree to navigate to the Device Number item:
Systems -> Networks -> Units -> Drops -> Configuration -> Controller -> Devices ->
Device Number
3. Right-click Device Number.
4. Select Insert New. The Insert New Device Numbers wizard appears:
Figure 122: Insert New Device Numbers Wizard
Note: If you add, change, or delete device drivers, perform a clear/load function on the
Controller.
5. From the Device Number drop-down menu, select an unused number (for example, you
might start with 2, and continue numbering successive devices sequentially).
6. Click Finish. The New Device Numbers window appears.
304 OW351_60
7. From the I/O Driver Type drop-down menu, select OVATION.
Figure 123: New Device Numbers window
8. Click Ok.
9. Return to the system tree and navigate to the I/O Device item:
Systems -> Networks -> Units -> Drops -> <Controller Drop number> -> I/O Devices
10. Right-click I/O Device and select Insert New. The Insert New [I/O Devices] Wizard appears.
11. Select the I/O Device Number from the drop-down menu. The choices are 0 for IOIC and 5 -
11 for third-party and Bus devices.
12. From the I/O Device Type drop-down menu, select IOIC.
Figure 124: Insert New [I/O Devices] Wizard
13. Click Finish. The New [I/O Devices] window appears showing the selection that you made.
OW351_60 305
10.4.3 T o inse rt the Primary I/O module into the De v eloper Studio syste m tre e
Note: Ensure that the Primary module is located on an odd branch with the lower hardware
address. The corresponding Secondary module must be located on the next higher even
branch.

2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
Interfaces -> Branch 1 (for Primary module) -> Slot
3. Right-click on Ovation Module in the empty slot and select Insert New.
Figure 125: Inserting a new Primary module
306 OW351_60
4. The Insert New Ovation Module Wizard appears. From the Module Type drop-down menu,
select the applicable module. For example a purpose, the following figure shows the
redundant Analog Output 4 to 20mA module (RED).
Note: Only certain modules can be configured for redundancy. These modules are Profibus
BusModule, Profibus BusModule (Time Synchronization), Digital Input 24 VDC (RED), Analog
Output 4 to 20mA (RED), Digital Output 24 VDC High Side, Ethernet Link BusModule, Ethernet
Link BusModule (Time Synchronization), and Foundation Fieldbus BusModule (Redundant).
Figure 126: Insert New Ovation Module window
OW351_60 307
6. Go to the Module tab at the bottom of the New Ovation Module window.
7. Select the Redundant radio button as the Redundancy attribute.
Note: Only the modules that can be redundant carry the Redundancy attribute in the New
Ovation Module window.
Figure 127: New Ovation Module window
Note: For Analog Output modules, the Timeout Action attribute on the New Ovation Module
window should be set to Reset. Do not set this attribute to Latch as this will jeopardize the
redundant operation of the back up module.

9. Once you have inserted the Primary module, you must insert the secondary module (see
page 308).
10.4.4 T o inse rt the Se condary I/O module into the De veloper Studio syste m tre e
Note: Ensure that the Primary module is located on an odd branch with the lower hardware
address. The corresponding Secondary module must be located on the next higher even
branch.

2. Use the system tree to navigate to an empty slot in the next higher even branch under your
Ovation IOIC branch:
Interfaces -> Branch 2 (for Secondary module) -> Slot
308 OW351_60
3. Right-click on Ovation Module and select Insert New.
Figure 128: Inserting a new Secondary module
The Insert New Ovation Module Wizard appears.

4. From the Module Type drop-down menu, select the applicable module. To use our example,
select Analog Output 4 to 20mA (RED).
6. Go to the Module tab at the bottom of the New Ovation Module window.
7. Select the Redundant radio button as the Redundancy attribute.
9. Once you have configured the Secondary module, you must link the Primary and Secondary
modules (see page 310).
OW351_60 309
10.4.5 T o link the Primary and Se condary I/O module s

2. Use the system tree to navigate to the Primary redundant I/O module:
Interfaces -> Branch 1 (for Primary module) -> Slot -> Applicable module (for example,
Analog Output 4 to 20mA (RED))
3. Right-click on the applicable Primary redundant I/O module, and select Open.
Figure 129: Open Primary I/O module to link to Secondary I/O module
The Redundant module window appears.

4. Select the Module tab.
5. Pull down the Redundant Partner menu, and find the module that you configured as the
Secondary module. This list will only show the modules in the next higher even branch that
are configured to be redundant and are of the same I/O module type.
310 OW351_60
7. You can verify that the Secondary module is linked to the Primary module. To do this:
a) Use the system tree to navigate to the Secondary redundant module :
Interfaces -> Branch 2 (for Secondary module) -> Slot -> Applicable Secondary I/O
module
b) Right-click on the Secondary I/O module, and select Open. The Redundant module
window appears.
c) Select the Module tab.
d) Notice that the Redundant Partner menu is grayed out and lists the Primary I/O module
as its redundant partner.
10.4.6 T o assign a module (RM ) point to the Primary and Se condary I/O module s
Note: These procedures must be performed for both the Primary and Secondary I/O modules.

2. Use the system tree to navigate to Module Points:
System -> Networks -> Units -> Drops -> Points -> Module Points
3. Right-click on Module Points to select Insert New. The Insert New Module Points wizard
appears:
Figure 130: Insert New Module Points Wizard
4. Enter a point name.

5. Pick a frequency (S = Slow (1 second), F = Fast (0.1 second), or A = As needed).
OW351_60 311
6. Click Finish. The New Module Points window appears:
Figure 131: New Module Points window
7. Navigate to the Hardware tab.

8. Choose the I/O module from the location where you added the Primary I/O module.
9. Click OK. If you navigate to your card and Open/Refresh, you will see the fully qualified
module record point name (for example, TEST.UNIT@FB).
10. Repeat Steps 2 through 9 for the Secondary I/O module.
10.4.7 T o load the Controller (for a re dundant I/O module )
After you have added and configured the Primary and Secondary I/O modules, you must load the
changes to the appropriate Controller.
Note: The Load function is necessary any time an I/O module is added.

3. Right-click on the appropriate Controller that you want to load.
4. Select Load from the pop-up menu.
5. For redundant Controller drop configurations, the "Select a drop to load" dialog box appears.
6. Select the Controller drop that you want to load. Typically, load the Secondary (Backup)
Controller first. Select Finish.
Note: Since it is not in control, if there are any problems when you load the Secondary
Controller, no system disruption will occur.
7. Repeat the Load procedure for the Primary Controller drop if you are using a redundant
Controller.
312 OW351_60
SECTION 11
11 Getting RAID fault information
IN THIS SECTION
Introduction to RAID fault information ....................................................................... 313

Overview of configuring iDRA C, SNMP, and points ................................................... 314
Configuring the connection to the iDRAC using the OS to iDRAC Pass
Through option ....................................................................................................... 320
Configuring the connection to the iDRAC using the Loopback Access option .............. 326
Changing the iDRA C SNMP Community String......................................................... 331
Creating Ovation points for iDRAC status information ................................................ 332
Viewing the RAI D status in the System Viewer application ......................................... 339
Resetting iDRA C to Factory Default Settings ............................................................ 339
11.1 Introduction to RAID fault information
You can monitor a Dell Server’s system and storage status using Ovation tools. This is done
using Ovation’s snmp2ovation program to query the Integrated Dell Remote Access Controller
(iDRAC), included in Dell PowerEdgeTM Servers. From this query, you can obtain the current
state of the machine and then populate Ovation points with the results. You can monitor the
server status through the Operator Station's System Viewer application (refer to Ovation Operator
Station User Guide for information on the System Viewer).
Emerson provides drops with two different types of storage options:
 Redundant Array of Independent Disks (RAID) is a data storage technology that combines
multiple disk drive components in a logical unit. Data is distributed across the drives in one of
several ways called "RAID levels," depending on the level of redundancy and performance
required.
RAID encompasses various data storage schemes that can divide and replicate data among
multiple physical drives. The different schemes or architectures are named by the word RAID
followed by a number (for example, RAID 0, RAID 1, and so forth). Each scheme provides a
different balance between reliability, availability, performance, and capacity.
If you choose RAID technology, Emerson offers RAID 1 for use with the Ovation Database
Server. Emerson's offering of RAID 1 consists of four physical disks that are configured as
two RAID 1 volumes, also referred to as Virtual Disks by the RAID controller.
Note: Ovation Process Historian (OPH) server drops use RAID 5 technology. For more
information on RAID 5 and the OPH, refer to the applicable Ovation Process Historian User
Guide.
 Regular, physical hard disks come from the manufacturer of the machine. For Database
Servers, you must have at least two physical hard disks. However, all Domain Controllers are
configured with a minimum of two disks.
OW351_60 313
11.2 Overview of configuring iDRAC, SNMP, and points
11.1.1 T e rminology use d with SNM P and RAID
The following terms and descriptions may be helpful while reading this sectionl.
Terms used with SNMP and RAID
TE R M DE S C R I P TI O N
iDRAC Integrated Dell Remote Access Controller (iDRAC). An embedded interface card
included in all Dell PowerEdge™ servers that provides out-of-band management
facilities. The iDRAC has its own processor, memory, network connection, and access
to the system bus. This gives system administrators the ability to configure a machine
as if they were sitting at the local console (terminal).
LOM LAN (local area network) on Motherboard (LOM). Refers to a chip or chipset capable
of network connections that have been embedded directly on the motherboard of a
desktop, workstation, or server. Instead of requiring a separate network interface card
to access a local-area network, such as Ethernet, the circuits are attached to the
motherboard. An advantage of a LOM system is an extra available PCIslot that is not
used by the network adapter.
RAID Redundant Array of Independent Disks (RAID) is a data storage technology that
combines multiple disk drive components in a logical unit. Data is distributed across
the drives in one of several ways called "RAID levels," depending on the level of
redundancy and performance required.
SNMP Simple Network Management Protocol (SNMP) is a program designed to monitor and
report the activity of various devices on the Network. The choice of devices to poll and
the variables in each device to poll is configurable. The SNMP2Ovation application
program uses SNMP variables, known as Management Information Blocks (MIBs), in
Ovation points.
The following steps provide a brief overview of the process to configure the iDRAC, SNMP, and
Ovation points.
1. Configure the connection to the iDRAC using one of the following methods:
 The operating system to iDRAC pass through option (see page 320).
OR
 The Loopback access option (see page 326).
2. Change the iDRAC SNMP Community string (see page 331).
3. Create Ovation points for iDRAC status information (see page 332).
314 OW351_60
11.2.1 Se le cting a conne ction me thod
Before you begin the procedure, decide which method to use to connect to the server's iDRAC.
There are two ways to configure the connection depending on the firmware version of your
iDRAC. Currently, all servers are shipped with iDRAC8. If you have a server with firmware version
8, then you can use either the Pass through method or the Loopback method without any
additional steps. However, if your server has an iDRAC with firmware version 7 (iDRAC7), you
must perform extra steps:
To use the Pass through method:

 If you have iDRAC7, you must update the firmware to iDRAC8
 If you have iDRAC8, no additional steps are needed for the Pass through method.
To use the Loopback method:

 If you have iDRAC7, you cannot use a dedicated port unless you purchase a new iDRAC
license. If you do not want to buy a license, you must use a shared NIC.
 If you have iDRAC8, no additional steps are needed for the Loopback method.
Note: For information on upgrading the iDRAC firmware, refer to the Dell documentation.
11.2.2 Re comme ndations for IP addre ss se lection
In keeping with the Ovation IP address guidelines, Emerson recommends that the l east significant
octet of both the iDRAC interface and the host interface correspond directly to the Ovation drop
number. The third octet should be used to differentiate between the iDRAC interface and the host
interface. For example, see the following table:
Example of Ovation IP addressing
DR O P I DRAC I N TE R F AC E IP H O S T I N TE R F AC E IP
140 169.254.0.140 169.254.1.140
When using the OS to iDRAC Pass through method to connect to the iDRAC (see page 320), you
must define a link-local address within the 169.254.0.0/16 address block for the iDRAC interface.
The address cannot be 169.254.0.3 or 169.254.0.4 as these are reserved for the USB NIC ports
on the front panel.
OW351_60 315
11.2.3 T o acce ss the iDRAC Se ttings utility
Use the following procedure to access the iDRAC Settings utility, which is used in later sections.
1. Turn on or reboot the Server.

2. Press F2 System Setup during Power-on Self-test (POST).
Figure 132: Power-on Self-test (POST) menu
3. On the System Setup Main Menu page, click iDRAC Settings.
Figure 133: iDRAC Settings option from the System Setup Main Menu page
316 OW351_60
The iDRAC Settings page appears.
Figure 134: iDRAC Settings page
11.2.4 T o acce ss the iDRAC We b inte rface
Use the following procedure to access the iDRAC Web interface, which is used in later sections.
1. Open an internet browser, such as Internet Explorer.
Note: If you use Internet Explorer 11, mak e sure that you add the iDRAC IP address. To do this,
click the Tools button at the top right corner of the window. Select Compatibility View Settings
from the Tools menu. Enter the iDRAC IP address in the entry field and click Add. Close the
window.
2. In the Address bar, type https://[iDRAC-IP-addre ss] and press the Enter key.
Note: If the default HTTPS port number (port 443) was changed enter: https://[iDRAC-
IP_address]:[port_number] where [iDRAC_IP_address] is the iDRAC IPv4 or IPv6 address
and [port_number] is the HTTPS port number.
OW351_60 317
3. If a web browser security certificate warning message appears, select the option to Continue
to this website.
Figure 135: Website's security certificate warning
4. The Login page appears. Perform the following steps:

a) Enter the iDRAC user name and password. The default user name is root, and the
default password is calvin.
b) Pull down the Domain drop-down menu and select This iDRAC.
c) Click the Submit button.
Figure 136: iDRAC Web Interface login page
318 OW351_60
Note: The Default Password Warning page allows you to change the password. For more
information on this window, refer to the Dell User Documentation at www.dell.com.
Figure 137: Default Password Warning page
OW351_60 319
The iDRAC main window appears.
Figure 138: Main iDRAC window
320 OW351_60
11.3 Configuring the connection to the iDRAC using the OS to iDRAC Pass Through option
11.3 Configuring the connection to the iDRAC using the OS to iDRAC

Pass Through option
In the Pass Through option, access to the iDRAC is achieved over a virtual NIC within the host
operating system. This option is best used when only the host machine needs access to the
iDRAC information or when there are no unused NICs available on the Server.
11.3.1 T o e nable iDRAC pass through

1. Access the iDRAC Settings utility (see page 315).
2. Click Network from the iDRAC Settings page.
Figure 139: Network option on the iDRAC Settings window
3. The iDRAC Settings - Network page appears. Perform the following:

a) Under the IPV4 Settings section, select the Disable option for Enable IPv4. This prevents
access to the iDRAC over its dedicated NIC and the shared LOM (LAN on Motherboard)
ports.
OW351_60 321
b) Click the Back button.
Figure 140: Network Settings page
4. You are returned to the iDRAC Settings page. Click the Back button and navigate to
Communications Permissions. (In firmware versions prior to iDRAC8, this page may be
titled, OS to iDRAC Pass Through.)
5. The Communications Permissions page appears. Under Pass Through Configuration, select
the USB NIC option.
6. Under the USB NIC Address, enter the desired IP address.
Note: In firmware versions prior to iDRAC8, this field may not be configured from this screen.
However, the IP address can be changed from within the web interface. Therefore, mak e a note
of the address, and accept the default address. See Recommendations for IP address selection
(see page 315).
7. Click Back to return to the iDRAC Settings page.

8. Click Finish to save the settings and return to the main menu.
9. Click Yes to save the changes.
10. Click Exit to leave the System Setup and reboot the machine.
322 OW351_60
11.3.2 T o configure the manage d compute r's v irtual adapter

1. From your Dell Server, navigate to Windows Start > Control Panel > Network and Sharing
Center.
2. In the left pane of the window, click the Change adapter settings link.
3. The Network Connections page appears. Right-click the iDRAC Virtual NIC USB device and
select Properties.
Figure 141: Network Connections showing right-click menu
Note: If this adapter is disabled, enable it by selecting Enable this network device from the
toolbar.
If the adapter cannot be enabled or periodically appears and disappears, the iDRAC firmware
may need to be upgraded.
4. The iDRAC Properties dialog box appears. Perform the following:

a) Ensure that DDB Protocol is not checked.
b) Select Internet Protocol Version 4 (TCP/IPv4).
c) Click the Properties button.
Figure 142: iDRAC Properties dialog box
OW351_60 323
5. The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears. Perform the
following:
a) Select the Use the following IP address option.
b) Enter the desired IP address.
c) Enter a subnet mask of 255.255.0.0.
d) Click OK to close the window.
Figure 143: Internet Protocol Version 4 (TCP/IPv4) Properties dialog box
6. Click OK on the iDRAC Properties dialog box (from Step 4).

7. From the Network Connections window, pull down the Advanced menu and select
Advanced Settings.
Note: If the Advanced menu is not visible, press the Alt k ey.
Figure 144: Network Connections window showing Advanced Settings menu option
324 OW351_60
8. The Advanced Settings dialog box appears. Confirm that the iDRAC virtual adapter is listed
below the Ovation adapter(s). Click the OK button.
Figure 145: Advanced Settings dialog box
OW351_60 325
11.4 Configuring the connection to the iDRAC using the Loopback Access option
11.3.3 T o modify the OS to iDRAC Pass T hrough IP addre ss

1. Access the iDRAC Web Interface (see page 317).
2. Go to Overview > iDRAC Settings > Network. The Network Settings page appears.
3. Select the OS to iDRAC Pass Through tab. The OS to iDRAC Pass through page appears
(see the following figure).
Figure 146: OS to iDRAC Pass Through page
4. Confirm that the Pass-through Configuration option is set to USB NIC.

5. Under Network Settings, enter the desired IP address for the USB NIC IP Address (see
Recommendations for IP address selection (see page 315)).
6. Click Apply.
Note: If you access the iDRAC web interface over the current Pass through IP address, the
connection to the iDRAC is lost after click ing Apply.
7. Click Logout to close the session.
11.4 Configuring the connection to the iDRAC using the Loopback

Access option
In Loopback Access configuration, access to the iDRAC is achieved by wiring a spare NIC in the
host to either the dedicated iDRAC port or to a shared LOM port.
The following procedure refers to the spare NIC as the host interface and the dedicated or shared
LOM port as the iDRAC interface.
326 OW351_60
11.4.1 T o configure iDRAC ne twork se ttings

1. Access the iDRAC Settings Utility (see page 315).
2. Go to Network from the iDRAC Settings page.
3. The iDRAC Settings - Network page appears. Perform the following steps:
a) Under the Network Settings section, select the Enabled option for Enable NIC.
b) For NIC Selection, select the desired NIC for the iDRAC interface (such as, Dedicated).
Note: In previous versions, the Dedicated iDRAC NIC requires an additional license. However, if
there are unused NICs available, the iDRAC can be configured to use a shared LOM (LOM3).
c) Under the IPv4 Settings section, confirm that Enabled IPv4 is Enabled.
d) Set Enable DHCP to Disabled.
Figure 147: iDRAC Settings - Network page
e) Enter the desired IP address and subnet mask. See Recommendations for IP address
selection (see page 315).
4. Click Back and navigate to Communications Permissions. (In previous firmware versions,
this page may be titled OS to iDRAC Pass Through.)
5. The Communications Permissions page appears. Under Pass Through Configuration, select
the Disabled option.
6. Click Back to return to the iDRAC Settings page.
7. Click Finish to save settings and return to the main menu.
8. Click Yes to confirm the saved changes.
9. Click Exit to leave System Setup and reboot the machine.
10. Physically connect the host interface to the iDRAC interface using a standard Ethernet cable.
OW351_60 327
11.4.2 T o configure the manage d compute r's host inte rface adapter
1. From your Dell Server, navigate to Windows Start > Control Panel > Network and Sharing
Center.
2. In the left pane of the window, click the Change adapter settings link.
3. The Network Connections page appears. Right-click the host interface adapter and select
Properties.
Figure 148: Network Connections showing right-click menu
Note: If the host adapter is disabled, select Enable this network device from the toolbar
Emerson recommends that you disable the adapter corresponding to the iDRAC interface by
selecting Disable this network device if the iDRAC is configured to use a shared LOM.
328 OW351_60
4. The Properties dialog box (for the host adapter) appears. Perform the following:
a) Make sure that DDB Protocol is not checked.
b) Select Internet Protocol Version 4 (TCP/IPv4).
c) Click the Properties button.
Figure 149: NIC Properties dialog box
OW351_60 329
5. The Internet Protocol Version 4 (TCP/IPv4) Properties dialog box appears. Perform the
following steps:
a) Select the Use the following IP address option.
b) Enter the desired IP address and subnet mask to place this adapter in the same subnet
as the iDRAC interface.
c) Click OK to close the Internet Protocol Version 4 (TCP/IPv4) Properties dialog box.
Figure 150: Internet Protocol Version 4 (TCP/IPv4) Properties dialog box
6. Click Close on the Properties dialog box (Step 4).

7. From the Network Connections page, pull down the Advanced menu and select Advanced
Settings.
Note: If the menu on the Network Connections window is not visible, press the Alt k ey.
8. In the Advanced Settings dialog box, ensure that the adapters for the host interface and
iDRAC interface are listed below the Ovation adapter(s).
330 OW351_60
9. Click OK.
Figure 151: Advanced Settings dialog box
OW351_60 331
11.5 Changing the iDRAC SNMP Community String
11.5 Changing the iDRAC SNMP Community String
Note: This procedure assumes that you have already configured the connection to the iDRAC
from either the Pass through method (see page 320) or the Loopback Access method (see page
326).
1. Access the iDRAC Web Interface (see page 317).

2. Navigate to Overview > iDRAC Settings > Network.
3. The Network Settings page appears. Select the Services tab.
4. The Services page appears. Under the SNMP Agent section, enter the desired SNMP
Community Name.
Figure 152: Services page showing SNMP Agent area
5. Click the Apply button at the bottom of the page.

6. Click Logout at the top right corner of the page to close the session.
332 OW351_60
11.6 Creating Ovation points for iDRAC status information
11.6 Creating Ovation points for iDRAC status informa tion
You must create and configure points to hold the SNMP values from the iDRAC. The following
sections discuss creating and configuring a single packed point for the SNMP values of the
iDRAC’s system and storage statuses.
Note: You can also associate SNMP values to individual analog or digital points.
For more information on point types, refer to Ovation Record Types Reference Manual.
11.6.1 T o cre ate points for SNM P RAID

Systems -> Networks -> Units -> Drops -> <Applicable Drops folder> Points
3. Right-click the Packed Points folder and select Insert New.
Figure 153: Ovation Developer Studio showing the Packed Points folder
OW351_60 333
4. The Insert New Packed Points Wizard appears. Perform the following steps:
a) Enter the desired point name (for example, IDRAC_DROP140_S TA TUS) in the Point
Name Value field. See Understanding point names (see page 167) for more information.
b) Select the desired frequency from the drop-down menu.
 S - Slow (1 second).
 F - Fast (0.1 second).
 A - Aperiodic (as needed).
c) Click Finish.
Figure 154: Insert New Packed Points Wizard window
334 OW351_60
5. The New Packed Points dialog box appears. On the Point tab, enter an appropriate
description (for example, iDRAC SNMP Values).
Figure 155: New Packed Points dialog box with Point tab selected
OW351_60 335
6. Select the Display tab. Use the following table to complete the values for Bits 0, 1, and 2 in
the New Packed Points dialog box:
Bit description
BI T S E T D E S C R I P TI O N R E S E T DE S C R I P TI O N DE S C R I P TI O N
0 Down Up SNMP Timeout

1 Not OK OK Global System Status
2 Not OK OK Global Storage Status
Figure 156: New Packed Points dialog box showing Display tab selected and bit
information completed
7. Click OK on the New Packed Points dialog box.

8. Load the drop (see page 94).
336 OW351_60
11.6.2 T o configure the SNMP

2. Use the system tree to navigate to and open the appropriate drop to be configured for SNMP:
Systems -> Networks -> Units -> Drops -> Applicable Drop folder -> Configure -> SNMP
Note: The SNMP folder is only found on the Operator Station, Sim Operator Station, Base
Station, or Virtual Controller Host drops.
3. Open the Configuration folder and right-click the SNMP item. Select Insert New.
4. The SNMP Wizard appears. No settings are required. Click Finish.
5. When an SNMP item is created, a blank SNMP Notepad file opens (see the following figure).
Figure 157: SNMP configuration file header in Notepad
6. Type the necessary SNMP settings into the file to complete the SNMP configuration. Use the
configuration settings defined in the following table. (See SNMP Parameter settings (see page
140) for general information.)
SNMP variables description
V AR I AB L E DE S C R I P TI O N EX AM P L E
<folder> Name of the folder displayed in the Workstation Management Status

System Viewer
<drop_name> Name of the drop to be shown in the DROP140
System Viewer
<idrac_ip> IP address of the iDRAC interface 169.254.0.140
<snmp_comm> SNMP community name idracpub
<point_name> Name of the point to update IDRAC_DROP140_STATUS
OW351_60 337
Based on the settings defined in the table, an example SNMP file is shown in the following
figure.
Figure 158: Sample SNMP configuration file
7. On the Notepad window, pull down the File menu and select Save.
Note: Do not perform a Save As function. The SNMP file could be permanently lost.
8. After saving the SNMP configuration, perform a Download (see page 99) and a Reboot (see
page 113) function.
338 OW351_60
11.7 Viewing the RAID status in the System Viewer application
11.7 Viewing the RAID status in the System Viewer application
The Ovation System Viewer application allows you to view the overall health of your Ovation
system as well as the health of individual Ovation components. With the System Viewer, you can
navigate through the various levels of an Ovation system, from the System level to the drop level,
to view drop status, point, and I/O information, as well as fault code information. Anything related
to the SNMP appears in the Network Asset folder.
Note: For more information on the System Viewer application, refer to Ovation Operator Station
User Guide.
1. Access the Ovation System Viewer application.

2. From the hierarchy tree, navigate to the SNMP folder: Network > Network Asset > <folder>
<idrac_ip drop_name>
The example in the figure shows:
NET2 > Network Asset > Workstation Management Status > 169.254.0.140 DROP 140 >
IDRAC_DROP140_STATUS. UNIT0@ NET2.
Figure 159: System Viewer showing the SNMP status points
OW351_60 339
11.8 Resetting iDRAC to Factory Default Settings
11.8 Resetting iDRAC to Factory Default Settings
If necessary, use the following procedures to reset the iDRAC to its factory default settings.
11.8.1 Using the Se ttings utility

1. Access the iDRAC Settings utility (see page 315).
2. Go to Reset iDRAC configurations to defaults. The iDRAC Settings Reset iDRAC
configurations to defaults page appears.
3. Click Yes. The iDRAC reset starts.
4. Click Back and navigate to the same Reset iDRAC configurations to defaults page to view the
success message.
Note: You may need to reboot or perform these steps multiple times to see the effects of the
reset.
11.8.2 Using the We b Inte rface

1. Access the iDRAC Web interface (see page 317).
2. Go to Overview > Server > Troubleshooting > Diagnostics. The Diagnostics Console page
appears.
3. Click Reset iDRAC to Default Settings. The completion status appears as a percentage.
The iDRAC reboots and is restored to factory defaults. The iDRAC IP is reset and is not
accessible. You can configure the IP using the front panel or BIOS.
Note: You may need to reboot or perform these steps multiple times to see the effects of the
reset.
340 OW351_60
SECTION 12
12 Engineering Tools Audit
IN THIS SECTION
What is the Engineering Tools Audit function? .......................................................... 341

What Ovation applications are audited with the En gineering Audit Tools function? ...... 342
To set the Engineering Audit level ............................................................................ 343
Auditing examples .................................................................................................. 345
Using the Ovation Audit Viewer ............................................................................... 347
What is the Audit log archive?.................................................................................. 356
Audit Log storage ................................................................................................... 357
12.1 What is the Engineering Tools Audit function?
The Ovation Engineering Tools Audit (Audit Trail) provides an automated way to log engineering
events. It provides an extra tool to help troubleshoot and quickly identify the root cause of
abnormal conditions that can translate into loss of operation and resources.
Not only does the Engineering Tools Audit reduce troubleshooting time, but it also complies with
more stringent security requirements imposed by NERC (North American Electric Reliability
Corporation). NERC specifies mechanisms to protect the cyber assets of a plant and provide
auditable records of all control system changes to achieve compliance.
The Engineering Tools Audit enables a Distributed Control System (DCS) to be self-documented.
The DCS system keeps track of all changes performed and provides a record of those activities
when requested at a future time. The Engineering Tools Audit eliminates the time-consuming
paper trail documentation of actions taken. It also presents properly controlled electronic records
that are both reliable and easily available. The Engineering Tools Audit eliminates readability
problems and the possibility of errors that may occur with manual paper trail audits.
The electronic Engineering Tools Audit activities normally require some type of information
storage in a database or control memory. The more information that the Engineering Tools Audit
is asked to save, the more media space it uses, which could result in a loss of system speed.
This function captures (audits) and views Ovation Engineering Tool actions/operations, including:
 Changes made to the Ovation database by Engineering Tool applications such as the
Developer Studio, Control Builder, and Graphics Builder.
 Changes made to Ovation configurations.
 Operations performed by Engineering Tool applications such as the loading, clearing,
query/downloading, and rebooting of Ovation drops.
 Database import operations logged (as well as the name of the import file).
OW351_60 341
12.2 What Ovation applications are audited with the Engineering Audit Tools function?
12.2 What Ovation applications are audited with the Engineering

Audit Tools function?
The following table lists the Ovation applications that can use the Audit Tool and the auditing
levels that can be applied.
For a description of auditing levels, see To set the Engineering Tools Audit level (see page 343).
Ovation applications and auditing levels
A P P L I C ATI O N A U D I TI N G L EVEL S
Control Builder Note: The addition and deletion of Control Builder default points are N OT audited.
High Level (1)
Reconciling a control sheet to the current database point values.
Medium Level (2)
Addition, modification, and deletion of an Ovation control sheet.
Addition, modification, and deletion of named (that is, non -default) Ovation process
points. In this context, the captured data simply identifies the point by name.
Low Level (3)
Modification of Ovation process points. This includes non-default points, as it may
be related to algorithm set points, and so forth. The amount of informati on captured
in this context is equivalent to that captured by the Developer Studio during low -
level auditing of an Ovation point.
Graphics Builder Medium Level (2)
Addition of new diagrams or macros. Note that this also includes the first-time
compilation of a new diagram or macro.
Modification of a diagram or macro when performed by the UI version of the
Ovation Graphics Builder (that is, not when running in the non -UI Compilation
mode.) No additional information concerning the specific changes made to a
diagram or macro is captured.
Deletion of a diagram or macro (only with the Windows Engineering Tool Suite.)
Holding Register Medium Level (2)
Builder/Editor
Addition, modification, and deletion of Holding Registers. In this context, the data
captured simply identifies the Holding Register number. No additional information
based on specific values is captured.
Low Level (3)
Modification of Holding Registers. Additional information is captured to indicate the
previous and new values of the Holding Register. One entry is generated per
modified field. Note that since the ultimate storage of holding registers consists of
16-bit words, the values captured are based on this data format.
342 OW351_60
12.2 What Ovation applications are audited with the Engineering Audit Tools function?
A P P L I C ATI O N A U D I TI N G L EVEL S
Database Import Since an Ovation import operation has the potential to update or create a vast
Application amount of data, you are warned if the current Auditing Level is "too low." If such a
state is detected, the Ovation Import application temporarily raises the auditing
level to a "recommended level." In all cases, the recommended auditing level is a
high-level configuration. (Essentially, this results in an entry being captured at the
start of the import operation and an entry being captured at the conclusion of the
import operation).
You have the ability to override any "automatically-adjusted" configuration settings
at the time of the import operation. For example, if the Auditing Level at the time of
import is "Low-level," you will be prompted to either:
1) Permit the temporary change to the recommended level.
2) Override the recommendation and permit the import operation at the lower level.
3) Abort the import operation.
High Level (1)
An entry is captured at the start of the import operation and includes the specified
command-line parameters.
An entry is captured at the conclusion of the import operation and indicates if errors
and/or warnings were encountered.
Medium Level (2)
In this context, additions and modifications of objects are captured.
Low Level (3)
Additional information is captured to indicate the previous and new values of the
data base object. One entry is generated per modified field.
OW351_60 343
12.3 To set the Engineering Audit level
12.3 To set the Engineering Audit level

2. Use the system tree (in the Hardware view bar) to navigate to the Engineering Tools Audit
folder:
Systems -> Configuration -> Engineering Tools Audit
3. Right-click on the Engineering Tools Audit item.
4. Select Insert New. The Engineering Tool Audit dialog box appears. The following figure and
table describe the fields of the Engineering Tool Audit dialog box.
Note: If the Engineering Tool Audit already exists in the system, it will appear in the Work Pad
area when you right-click on the Engineering Tools Audit item in the system tree. To open t he
window, right-click on the Engineering Tool Audit item in the Work Pad window and select Open.
The Engineering Tool Audit window appears. You can then adjust the audit level as you choose.
Figure 160: Engineering Tool Audit dialog box
5. Set the Audit Configuration Level using the drop-down menu. Auditing the Engineering
tools/operations might influence their overall performance. Therefore, different auditing levels
are available that depend on your needs and the required response of your system. The
choices are:
 OFF
 High-Level Auditing
 Medium-Level Auditing
 Low-Level Auditing
6. Select Ok/Apply to apply the desired audit level.
344 OW351_60
12.4 Auditing examples
The following table describes the auditing levels.
Audit level descriptions
LE V E L DE S C R I P TI O N
OFF Auditing is disabled. Modifications to the Ovation database, Ovation configurations,

and engineering tool operations are not captured.
High User operations are captured. For example, the audit function captures the clear and
load of Ovation drops, initiation and completion of import operations, and
reconciliation of tuning changes to the database.
Medium All functions performed in the High audit state are captured. Also captured are
changes including identification of added and deleted items (such as points) and a
simple indication that a point has been modified (not including the values of the
modified fields). Import operations indicate affected database objects.
Low All functions performed in the High and Medium audit states are captured, including
the old and new values of each field of a modified database object. The same is true
for Ovation import operations.
The following topics provide examples of high-, medium-, and low-level auditing.
12.4.1 High-level auditing e xample
High-level auditing captures events such as operations. If you perform modifications of database
items during high-level auditing, there is only one entry associated with the event. No additional
information, such as which fields were modified or what the old and new values are, is included.
The following table is an example of a high-level audit entry.
I TE M V AL U E
Time 08-Jan-2006 10:21:42.

OS User Engineer1.
Machine drop148.
Action Load.
Object Type Drop.
Object Name drop1.
Program Developer Studio.
OW351_60 345
12.4.2 M e dium-level auditing e xample
Medium-level auditing captures events such as insertions, modifications, and deletions. If you
perform modifications of database items during medium-level auditing, there is only one entry
associated with the event. No additional information, such as which fields were modified or what
the old and new values are, is included. The following tables are examples of medium-level audit
data.
Audited insertion of an Ovation point
I TE M V AL U E
Time 08-Jan-2006 10:15:38.

OS User Engineer1.
Machine drop148.
Action Insert.
Object Type LA Point.
Object Name LA001S001.UNIT1@W3.
Audited modification of an Ovation point
I TE M V AL U E
Time 08-Jan-2006 10:17:15.

OS User Engineer1.
Machine drop148.
Action Modify.
346 OW351_60
12.5 Using the Ovation Audit Viewer
12.4.3 Low-le vel auditing e xample
Low-level auditing provides additional information about events such as which fields were
modified and what the old and new values are. If multiple fields of an object are modified by an
Engineering Tool, multiple audit log entries are created (one for each field that was modified.) The
following table is an example of low-level audit data of an Ovation point.
Example of low-level audit data
I TE M V AL U E
Time 08-Jan-2006 14:17:03.

OS User Engineer1.
Machine drop148.
Action Update.
Parameter DESCRIPTION.
Old Value Initial Description.
New Value Test I/O Point.
The Ovation Audit Viewer is used to view, filter, and sort the current contents of the Engineering
Station Audit logs.
You can perform searches as well as sort and filter audit log entries on the interface. Your actions
do not change the information stored in the audit database.
In addition to specifying a time frame for the retrieval of the audit log entries, you can filter on
other items such as Audit Level, Action, Object Type, Object Name, Parameter, OS User
(Operating System User), and Machine.
OW351_60 347
12.5.1 T o acce ss the Ov ation Audit Vie we r
Use the following procedure to access the AuditView window.
1. Select Start -> Ovation -> Ovation Engineering Tools -> Ovation Audit Viewer.
The Ovation AuditView window appears. Since you can configure which columns to show or
hide (see page 354), not all of the possible columns may appear at start up.
Figure 161: AuditView window
348 OW351_60
12.5.2 AuditVie w me nu bar
The following table describes the AuditView menu items.
AuditView menu descriptions
MEN U DR O P - D O W N ME N U I TE MS AN D D E S C R I P TI O N
File Open — Open a saved Audit.

Save As — Saves the information in the currently selected dialog box to an xml file.
Save As Text — Saves the information in the currently selected dialog box to a txt
file.
Print — Prints the selected tab in the active document.
Print Preview — Displays the active document as it will appear when printed.
Recent File — Opens the most recent file.
Exit — Exits the application.
Data Search — Searches for audit information.
Date/Time Retrieval — Displays information using the date and time shown on the
toolbar.
Show/Hide Column — Allows manipulation of the appearance of the output.
Archive Data — Allows archiving data to allow space for new data.
Edit Undo — Undoes the last action.
Cut — Cuts the selected item to the clipboard.
Copy — Copies the selected item to the clipboard.
Paste — Pastes the clipboard contents to the desired location.
View Toolbar — Opens or closes the main toolbar.
Status\Bar — Opens or closes the status bar.
Help About Auditview — Displays information about this program.
OW351_60 349
12.5.3 AuditVie w toolbar
The following table shows the AuditView toolbar icons and their descriptions.
AuditView toolbar icons and descriptions
IC O N DE S C R I P TI O N
Open — Opens a saved Audit.
Save As — Saves the currently selected dialog

box to a file.
Print — Prints the selected tab in the active

document.
Search — Searches for audit information (see

page 351).
Date/Time Retrieval — Displays information

from a particular date and time.
12.5.4 T o v ie w current Engineering T ool audits
Use the following procedure to view current audit information:
1. Access the Ovation Audit Viewer (see To access the Audit Ovation Viewer (see page 347)).
2. Specify the time range from which you want to extract information by updating the date and
time fields on the toolbar (see AuditView toolbar (see page 350)). To do this:
 Select the date drop-down menus to access a calendar and select a day.
OR
 Type the date into the fields. (You can also use the increment/decrement buttons to
advance the date, forward or backward, one day at a time.)
3. Enter the appropriate time into the date field.
350 OW351_60
4. Choose one of the following options:

 Select the Date/Time Retrieval icon on the toolbar.
OR
 Select Date/Time Retrieval from the Data menu. The following window appears:
Figure 162: Audit View Estimated Entries
5. Select Continue to get a listing of the entries.
OW351_60 351
12.5.5 T o de fine se arch criteria for an audit re port
Use the following procedure to define specific search criteria to view audit logs.
1. Access the Ovation Audit Viewer (see To access the Ovation Audit Viewer (see page 347)).
2. Select the Search icon on the toolbar, or select Data -> Search from the Ovation Audit
Viewer menu.
The Audit View: Search dialog box appears:
Figure 163: Audit View: Search dialog box
3. Choose a time range from the Date/Time Range drop-down menu. Choosing Custom Time
enables the Begin and End fields.
Note: Leaving the Date/Time Range set to "All Times available" could create long drop-down
lists in the search selections, which could include items not available. It also lengthens the
search time available.
4. If you choose Custom Date/Time, choose a Begin and End time frame for the search.
352 OW351_60
5. Select the appropriate criteria from the drop-down menus (see the following table for more
information).
Audit View: Search dialog box fields
D AT A CH O I C E S
Date/Time The Choices are:

Range  All Times available
 Last 1 hour
 Last 8 hours
 Last 24 hours
 Last 1 week
 Last 2 weeks
 Last 1 month
 Custom Date/Time
Audit Level 1, 2, 3 (depending on the database). See What Ovation applications are audited with
the Engineering Audit Tools function? (see page 342).
Action Blank, Clear, Delete, Engineer, Insert, Load, Reboot, and so forth.
Status Blank, Begin, Initiate, Initiated, Success, and so forth.
Object Type Blank, AnalogPoint, Audit level status, Audit status, Drop, ProfibusPort, and so forth.
Object Name Blank, Drop name, Alarm Display, Audit Status, and so forth.
OS User Blank, Administrator, System, and so forth.
Machine Blank, Name of machine.

Program Blank, db_xmit_server.exe, Developer Studio, OvPtTest.exe, SQLLDR.exe, and so
forth.
Parameter Blank, Alarm Display Number, Audit_Level, Display Diagram In, Position 1, and so
forth.
Old Value Blank, 1 (High-Level Auditing), 3 (Low level auditing), -4, and so forth.
New Value Blank, 0, 1 (High-Level Auditing), 3 (Low level auditing), -4, Enabled, Group1, and so
forth.
Data Blank, Clear operation to "Drop1" complete..., Load operation to "Drop100", and so
forth.
6. Select the Search button on the AuditView toolbar (see page 350).
7. A pop-up dialog box appears stating the number of items found and asking if you want to
proceed. Click Continue to display the items or Cancel to quit the search. If you select
Continue, the Audit View window populates with information.
OW351_60 353
12.5.6 T o v ie w indiv idual e v ent information
Once you have searched and displayed audit results in the Audit View window, you can display
information on a single entry. To do this:
1. Double-click on any item in the Audit View window. The Audit View: Entry Properties window
appears displaying all of the information on the item you selected.
2. Use the Next button to advance to the next item on the Audit View window. Use the Previous
button to navigate back to the item that appears before the selected item on the Audit View
window.
Figure 164: Audit View:Entry Properties
354 OW351_60
12.5.7 T o show or hide columns using the me nus
You can configure which columns will appear on the Audit View window. Use the following
procedure to use this feature:
1. Access the Ovation Audit Viewer (see page 347).

2. In the Audit View window, select Show/Hide Columns from the Data menu.
The Show Columns window appears:
Figure 165: Audit View: Show Columns
3. Select the items that you want to appear in the Audit View window. The items are highlighted.
To hide a column that was highlighted, select the item again, and it is no longer highlighted.
The column will not appear on the Audit View window.
4. Click OK.
5. The Audit View window columns update based on your selections.
OW351_60 355
12.6 What is the Audit log archive?
12.5.8 T o adjust columns using the right -click me nu
You can make adjustments to the columns on the Audit View window to improve the readability of
the information.
1. From an Audit View window populated with entries, right-click anywhere on the window and a
menu appears:
Figure 166: Audit View: Column adjustment menu
2. Select one of the following menu items:

 Hide Column -- hides the column on which you currently have cursor.
 Show All Columns -- displays all of the possible columns on the window, whether or not
they are populated with information.
 Sort Column Ascending -- reorganizes the column so that it displays in ascending order
(lowest to highest/A - Z).
 Sort Column Descending -- reorganizes the column so that it displays in descending
order (highest to lowest/Z - A).
12.6 What is the Audit lo g archive?
The Ovation Process Historian is used as a mechanism for long-term archival of engineering audit
logs. The storage is in the form of files, but the contents of the files are not known by the historian.
Retrieval requests to the Historian returns the entire file.
The Audit_Archive table contains entries for archive file names, the start/end times of the entries
in the archive, and the time/date when the archive was generated.
Note: The Ovation Process Historian does not support file storage. The archive function saves
the archived entries to a user-specified file. You are responsible for long-term storage of these
archive files.
The format of the archive files is equivalent to an unfiltered export of the audit log entries from the
earliest entries up to a specified time/date.
356 OW351_60
12.7 Audit Log storage
12.6.1 T o archiv e audit data
Use the following procedure to archive audit data:
1. Access the Ovation Audit Viewer (see page 347).

2. Select Archive Data from the Data menu on the Audit View window.
The Archive Data dialog box appears:
Figure 167: Audit View: Archive Data
3. Select the appropriate date and time:

 Use the arrow to display a calendar. Scroll to the desired month and select the
appropriate day.
OR
 Enter a valid date and time in the entry field.
Note: Data archival must be performed from the earliest date forward.
4. Select OK. (See Audit Log storage (see page 357) for information on storing the data after it
is archived.)
The Ovation Engineering Tool audit entries reside in the Ovation database. The schema used for
this storage differs from the schema used for the Ovation Systems database. The use of a
separate schema provides a degree of isolation from the rest of the Ovation database, as it allows
the Engineering Tools Audit to be maintained during and across full Ovation database imports.
The Ovation database import tools that currently exist deal with the Ovation System database.
Therefore, a full import operation does not delete or remove entries from the audit log. In addition,
the full Oracle export that is currently employed for backup procedures includes the audi ting
information. Therefore, if a full restoration of an Ovation Database Server is required, the latest
Engineering Tools Audit is not lost.
OW351_60 357
12.7.1 What are the storage limits?
The audit database, like the standard Ovation master database, utilizes Oracle tablespaces (files)
of fixed size. Because the audit system is designed to track engineering changes to the system
on a continuous basis, without explicit intervention, these tablespaces eventually become filled. If
this occurs, any Engineering change that is normally inserted as a new audit log entry is blocked.
A process running on the database server monitors the amount of free space in the audit tables. If
the amount of free space drops below specified levels, entries are generated in the Ovation Error
Log and the Audit Log, and in some cases, drop error/alarms post for the Ovation Database
Server. The following is an example of error reporting:
 If the amount of free space on an Oracle tablespace drops below 15 percent, an error
message appears in the Ovation Error Log of the Ovation Database Server and in the
Engineering Tools Audit Log.
 If the amount of free space on an Oracle tablespace drops below 10 percent, an additional
(and different) error message appears in the Ovation Error Log of the Ovation Database
Server and in the Engineering Tools Audit Log. In addition, the Ovation Database Server
posts a drop fault to indicate an error condition.
 If the amount of free space on an Oracle tablespace drops below 2 percent, anot her
additional (and different) error message appears in the Ovation Error Log of the Ovation
Database Server and in the Engineering Tools Audit Log. In addition, the Ovation Database
Server posts a drop fault to indicate a severe error condition.
12.7.2 What if the storage limits are e xceeded?
If audit log storage limits are exceeded, you must use the archive function (see page 356) to save
older entries and thereby free-up space within the audit log.
358 OW351_60
SECTION 13
13 Adding Holding Registers
IN THIS SECTION
What are Holding Registers ? ................................................................................... 359

Understanding the Holding Register Editor window ................................................... 361
13.1 What are Holding Registers?
Generally, an algorithm stores a value in a point, but holding registers give the option of storing
values outside of a point. Holding registers are typically used for storing values in Special
Function and ladder applications. Each holding register uses one word (16 bits) of memory. A
maximum of 10,000 holding registers are available. Valid entries are zero through 9999. On a
ladder, an algorithm can read or write a value to a holding register.
A holding register is an integer value; it cannot be a real number because it is only a 16-bit value.
However, by pairing two adjacent 16-bit holding registers, the Ovation Controller can utilize the
“pair” as if it were a 32-bit floating-point number.
A register can be associated with more than one special function. A given special function can
store numerical data in one register, which also is used to supply the same numerical data to
another special function.
For example, consider an output register whose value operates a seven-segment, four-digit BCD
display. This register also can provide numerical input data to another special function.
You access and insert the holding registers application from any Controller Drops folder in the
Developer Studio.
13.1.1 T o inse rt a ne w Holding Re gister
Use the following procedure to add a new holding register to the Developer Studio:

2. Use the system tree to navigate to the Holding Registers folder:
Systems -> Networks -> Units -> Drops -> <applicable Controller Drop number> ->
Holding Registers
3. Open the Holding Registers folder to reveal the Holding Register item.
4. Check the WorkPad window to ensure that there is no holding register already created. If a
register already exists, you can open it for editing (see page 360).
5. If no holding register exists for the desired drop, right-click the Holding Register item.
OW351_60 359
13.1 What are Holding Registers?
6. Select Insert New. The Insert New Holding Registers Wizard appears:
Figure 168: Insert New Holding Registers Wizard
7. Select a value between 0 and 9,999 for the holding register by entering the value in the entry
field or using the up/down arrows.
8. Select the Finish button. The Holding Register Editor window appears. The window opens to
the newly inserted register value, and the Register icon appears in the WorkPad window (see
Understanding the Holding Register Editor window (see page 361)).
13.1.2 T o ope n an e xisting Holding Re gister
Use the following procedure to open an existing holding register:

2. Use the system tree to navigate to the Holding Register folder:
Holding Register
3. Open the Holding Register folder to reveal the Holding Register item.
4. Double-click the Holding Register item to display a list of holding registers in the WorkPad
window.
5. Right-click the appropriate holding register Item.
6. Select Open. The Holding Register Editor appears. See Understanding the Holding Register
Editor window (see page 361) for a description of how to use the Editor.
Note: There is a holding register item assigned for every register that contains a value. The
holding register item selected in the Work Pad window determines the first register displayed in
the Holding Register Editor's Register column. All registers from 0-9,999 are available once in
the editor.
360 OW351_60
13.2 Understanding the Holding Register Editor window
13.2 Understanding the Holding Regis ter Editor window
The Holding Register Editor allows you to configure and edit holding register information. It
appears after you insert a new register number (see page 359) into the Developer Studio or you
open an existing register number (see page 360) from the Studio.
Note: Only one Holding Register Editor can be opened at a time in order to avoid confusion
while creating new registers.
Figure 169: Holding Register Editor with all columns shown
OW351_60 361
When using the Holding Register Editor, consider the following:

 The Apply and Data Entry columns do not display until one or both of the Permit Changes
boxes are checked.
 Changes can only be applied to columns that have their Permit Change box checked. For
example, the Database Value column will be grayed out and cannot access any entries from
the Data Entry column if the Permit Changes to Database check box is not checked.
 The Permit Changes boxes can be set to appear checked at startup if they are configured to
be initially selected from the Holding Register Editor Preferences window (see page 365).
 Once the Holding Register Editor is open, you can create a new Holding Register by entering
a value in the Data Entry field of an unused Register, and selecting the corresponding Apply
arrow button.
 A new Holding Register is created but does NOT appear in the WorkPad window until the
Holding Register item is closed and reopened.
The following table describes the Holding Register Editor window fields.
Holding Register Editor window field and button descriptions
W I N D OW I TE M DE S C R I P TI O N
Fields and buttons at top part of window

Server Server where the drop you are currently accessing resides.
Controller(s) Defines the Controller(s) (Control and Backup) that the Holding Register Editor
is connected to.
First Register Shows the register number in the top column of the Editor window. This is the
first number that appears on the current "page." If you select the Next Page
button, you advance to the next register number.
Disconnect Disconnects you from the server, allowing you to enter a new server name in
the Server entry field.
Permit Changes to Allows holding register changes to be made to the Database.
Database
Permit Changes to Allows holding register changes to be made to the Controller(s).
Controller(s)
Refresh Refreshes the entries on the Editor window.
Columns
Register Number of the register.
Database Value Value of the register in the Database.
Dropx Value Value of the register in the Controller that is in control.

(in Control)
Dropx Value Value of the register in the backup Controller. This column only displays for
(Backup) redundant Controllers.
Apply Executes the change made in the Data Entry field to the Database and/or
Controller(s) whichever is permitted.
Data Entry Field where you can enter changes to register values.
362 OW351_60
W I N D OW I TE M DE S C R I P TI O N
Side Buttons
Next Page Advances the display to the next page of register entries in the sequence. The
number of entries that appear on a "page" of the Holding Register Editor
window is configured in the Holding Register editor Preferences dialog box
(see page 365).
Previous Page Reverts the display to the previous page of register entries in the sequence.
The number of entries that appear on a "page" of the Holding Register Editor
window is configured in the Holding Register editor Preferences dialog box
(see page 365).
Apply Page Executes all of the changes made in the Data Entry fields on a single page.
Clear Page Removes all changes made in the Data Entry fields on a single page.
Copy DB -> Ctrl Copies any changes/information from the databas e to the Controller(s).
Copy Ctrl -> DB Copies any changes/information from the Controller(s) to the database.
Help Provides online help on the Holding Register Editor window.
13.2.1 Holding Re gister Editor me nu and toolbar functions
The Holding Register Editor menu bar provides all the necessary functions for working with the
tool. The following table describes each menu item.
Holding Register Editor Menu item descriptions
MEN U I TE M AN D D E S C R I P TI O N
File Print - Opens a standard Microsoft Windows Print dialog box.

Print Preview - Displays a view of what will be printed before actually printing.
This option is useful in determining if a change to the print setup is needed.
Print Setup - Opens a standard Microsoft Windows Print Setup window that
allows you to select a specific printer, paper size, print mode, and so forth
Preferences - Opens the Preferences dialog box, which allows you to change
the number of rows displayed in the editor, text color, and write access. See
Holding Register Editor Preferences dialog b ox (see page 365).
Exit - Quits the Holding Register Editor window.
Edit Undo - Reverses the last data entry in the Data Entry column, but does NOT
undo any value that has been applied.
Cut - Cuts the selected value and stores it in a clipboard area for possible
pasting later.
Copy - Copies the selected value to a clipboard for pasting later.
Paste - Pastes the contents of the clipboard into the selected field.
OW351_60 363
MEN U I TE M AN D D E S C R I P TI O N
View Display As Decimal Values - Displays all values in the Holding Register Editor
as decimal values.
Display As Hex Values - Displays all values in the Holding Register Editor as
hexadecimal values.
Display As Real Values - Displays all values in the Holding Register Editor as
real numbers. Only the even numbered register contains a value. The real value
displayed is the data in the even numbered register appended to the next odd
numbered register.
Toolbar - If this item is checked, the toolbar will appear on the window. If this
item is not checked, the toolbar will not appear on the window.
Status Bar - If this item is checked, the status bar will appear on the window. If
this item is not checked, the status bar will not appear on the window.
Help Help Topics - Provides access to help information on the Holding Register
Editor.
About HREGInfo - Provides the Holding Register Editor application version
number.
The toolbar provides quick, easy access to the more frequently used Holding Register Editor
functions. Most functions represented on a toolbar can also be accessed from a menu.
Holding Register Editor toolbar button descriptions
B U TTO N FU N C TI O N
Cut - Cuts the selected value and stores it in a clipboard area for possible pasting later.
Copy - Copies the selected value to a clipboard for pasting later.
Paste - Pastes the contents of the clipboard into the selected field.
Display Decimal - Displays all values in the Holding Register Editor as decimal values.
Display Hexadecimal - Displays all values in the Holding Register Editor as

hexadecimal values.
Display Real Value - Displays all values in the Holding Register Editor as real numbers.
Only the even numbered register contains a value. The real value displayed is the data
in the even numbered register appended to the next odd numbered register.
Preferences - Opens the Holding Register Editor Preferences dialog box.
Print - Opens a standard Microsoft Windows Print dialog box.
About - Provides the Holding Register Editor application version number.
364 OW351_60
13.2.2 T o use the holding Re gister Editor pre ferences window
Use the Preferences dialog box to change the settings on the Holding Register Editor. See the
following figure and table for descriptions of the Preferences settings.
1. To access the Preference dialog box, pull down the File menu on the Holding Register Editor
window and select Preferences. You can also click the Preferences icon on the toolbar. The
Preferences window appears:
Figure 170: Holding Register Editor Preferences window
2. Make any applicable changes to the Preferences dialog box. See the following table for
information on each field. When you are finished, click the OK button.
Holding Register Editor Preferences window fields
Number of Rows Defines the number of rows that display on one "page" of the Holding
Register Editor window.
Entry Column Text Color Defines the color of the text in the Data Entry column.
Initially Permit Changes to If checked, when you first access the Holding Register Editor, the Permit
Database Changes to Database check box will be checked, meaning that you ca n
write changes to the database. Also, the Apply and Data Entry columns
will appear when the Holding Register Editor is accessed.
Initially Permit Changes to If checked, when you first access the Holding Register Editor, the Permit
Controller(s) Changes to Controller(s) check box will be checked, meaning that you can
write changes to the Controller(s). Also, the Apply and Data Entry columns
will appear when the Holding Register Editor is accessed.
OK Applies the preference settings to the Holding Register Editor dialog box.
Cancel Cancels the changes made to the preferences settings.
Help Provides online help on the Holding Register Editor Preferences window
OW351_60 365
13.2.3 T o change Holding Re gister v alues
Use the following procedure to change a single or multiple holding register values:

2. Use the system tree to navigate to the Holding Register folder:
Holding Registers
3. Open the Holding Register folder to reveal the Holding Register item.
4. Double-click the Holding Register item to display a list of holding registers in the WorkPad
window.
5. Right-click the appropriate holding register Item.
6. Select Open. The Holding Register Editor appears
7. Select the register number to be changed and click in the Data Entry field.
Note: The Data Entry field is only available if one of the “Permit Changes” boxes is check ed;
otherwise, the Data Entry field is grayed out (not available for input.)
8. Type in the new value and select the Apply button. The value is added to the writable fields.
OR
Type in a new value for several entries on one page of the Holding Register Editor window.
Select the Apply Page button to apply all the new values.
Note: Values must be applied for all registers on a page before moving to another page. If you
add a value to the Data Entry field and move to another page, a message appears ask ing “Do
you want to apply the changes on the page?" Select Yes to apply the changes and move to the
next page (next set of registers). Select No to discard the changes and move to the next set of
registers.
366 OW351_60
13.2.4 Holding Re gister print dialog box
The Print function sends one page (the current set of register items shown on the Editor window)
to the printer.
1. Access the Holding Register Editor (see page 359).

2. Pull down the File menu, and select Print. You can also select the Print icon on the toolbar.
The standard Microsoft Windows print mechanism is used to perform the print operation. It is
assumed that you have a printer properly configured on your system.
Figure 171: Holding Register Print dialog box
OW351_60 367
13.2.5 Holding Re gister print se tup dialog box
The Print Setup window allows you to set a specific printer, paper size, print mode, and so forth.
The Holding Register Print Setup dialog box (a selection found under the File menu) operates
exactly like the standard Microsoft Windows print setup dialog box.

2. Pull down the File menu, and select Print Setup. A standard Microsoft Windows Print Setup
window displays
Figure 172: Holding Register Print Setup window
3. Make any desired changes to the options defined in the following table:
Holding Register Print Setup window fields
Name Lists the names of the printers that are available for printing.
Properties Displays another window that further defines the fields of the particular printer.
Status Gives status of printing (ready, processing, and so forth).
Type Shows the type of printer to be used for the print.

Where Shows the location of the printer being used.
Comment Gives any comments about the printer.
Size Lists size of the paper to be used for the print (letter, 11 x 14, and so forth).
Source Determines the source of the paper (from where the paper is coming from). The choices
change depending on the printer.
Orientation Allows you to choose between Portrait (prints vertically) or Landscape (prints horizontally).
Network Displays another window that shows the network connections for the printers defined.
4. Press OK to confirm the settings on the Print Setup window. The OK button does NOT send
the file to print. After you confirm the settings, you must go back to the File menu and select
Print to print the file.
To exit the Print Setup window without saving any changes, press the Cancel button.
368 OW351_60
13.2.6 Holding Re gister print preview dialog box
Print Preview displays a view of what will be printed before actually printing. This option is useful
in determining if a change to the print setup (see page 367) is needed.

2. Pull down the File menu, and select Print Preview. A standard Microsoft Windows Print
Preview window displays.
Figure 173: Holding Register Print Preview window
3. Select one of the following buttons:

 Print -- sends the page to the printer.
 Next Page -- navigates to the page after the current page (used for multiple pages).
 Prev Page -- navigates to the page before the current page (used for multiple pages and
if the current page is not the first page).
 Two Page -- displays two pages at a time if you have multiple pages.
 Zoom In -- enlarges the magnification of the page.
 Zoom Out -- reduces the magnification of the page.
 Close -- exits the Print Preview window without sending the page to the printer.
OW351_60 369
SECTION 14
14 DIOB testing for Q-Line modules
IN THIS SECTION
What is the optional DI OB Test tool used for? ........................................................... 371

Q-Line I/O module addressing ................................................................................. 372
14.1 What is the optional DIOB Test tool used for?
The Ovation Controller contains an optional Q-Line I/O bus checking diagnostic tool that may be
used to monitor the health of the Controller’s Q-Line I/O bus. This tool is known as the DIOB Test
(Distributed I/O Bus Test.)
Initializing the DIOB test addresses enables the I/O bus test. During the DIOB test, signals are
sent between the Q-Crate cards until faults are found.
On a redundant system, when the DIOB test fails, the Controller performs a “conditional” fail over.
This means that the partner or backup Controller assumes control of the system until the fault is
cleared. This only occurs if the backup Controller is operating properly at the time of the failure. If
the backup Controller is not operating properly at the time of alarm, the primary Controller goes
into alarm and continues to control the system.
On a non-redundant system, the Controller will go into alarm while it continues to control the
system. When the fault is identified, it can be cleared from the system.
OW351_60 371
14.2 Q-Line I/O module addressing
14.2 Q-Line I/O module addressing
The address for Ovation modules is determined by the location of the module in the I/O cabinet.
However, the address for a Q-Line card is determined by the jumper settings on the actual Q-Line
card. A visual inspection of the card should be performed to determine the jumper settings. (Refer
to the Q-Line Installation Manual.)
Q-Line QBO modules are used to perform DIOB testing. The QBO card is addressed by entering
it in hexadecimal format into a dialog box. The box appears when a Q-Line module is defined and
configured through the Developer Studio.
Figure 174: Insert New Q-Line Module Wizard
372 OW351_60
Index
Compact Digital Input module configuration •

A 243
Accessing the Ovation Developer Studio • 5 Config tab field descriptions • 182
Adding and configuring redundant I/O Config tab fields for Algorithm points • 186
modules • 301 Config tab fields for Analog points • 182
Adding drops to the Developer Studio • 153 Config tab fields for Digital points • 183
Adding Holding Registers • 359 Config tab fields for Module (RM) and Node
Adding I/O to the Developer Studio • 225 (RN) points • 187
Adding points in the Ovation Developer Config tab fields for Packed points • 185
Studio • 169 Configuration subfolder component
Adding redundant I/O modules • 303 descriptions • 49
Alarm tab field descriptions • 192 Configuration subfolder components by level
Alarm tab fields for Drop points • 201 • 48
Alarm tab fields for Long Analog and Deluxe Configuring Algorithm (LC) point types • 175
Analog points • 192 Configuring Analog (LA) point types • 172
Alarm tab fields for Long Digital and Deluxe Configuring Deluxe Analog (DA) point types
Digital points • 195 • 173
Alarm tab fields for Long Packed and Deluxe Configuring Deluxe Digital (DD) point types •
Packed points • 198 174
Alarm tab fields for Module and Node points Configuring Deluxe Packed (DP) point types
• 202 • 175
Analog Input module configuration • 237 Configuring Digital (LD) point types • 173
Analog Output module configuration • 240 Configuring Drop (DU) point types • 175
Ancillary tab field descriptions • 187 Configuring Module (RM) point types • 176
Audit Log storage • 357 Configuring Node (RN) point types • 176
Auditing examples • 345 Configuring Packed (LP) point types • 174
AuditView menu bar • 349 Configuring Packed Digital (PD) point types •
AuditView toolbar • 350 176
Configuring the connection to the iDRAC
B using the Loopback Access option • 326
Configuring the connection to the iDRAC
Backup/Restore • 86
using the OS to iDRAC Pass Through
Baseline Comparison function • 124
option • 321
Baseline Creation function • 123
Consistency Checking • 91
Before adding redundant I/O modules • 303
Contact Input module configuration • 242
Browse menu on the Developer Studio
Copyright Notice • 2
window • 19
Creating Ovation points for iDRAC status
Browse toolbar • 21
information • 333
Byte, Int., Real, and ASCII Params tab field
Creating Points in the Developer Studio •
descriptions • 215
165
C Creating Studio icons using the Image
Builder • 52
Changing the iDRAC SNMP Community
String • 332 D
Clear error messages • 111
Data validation • 31
Clear function • 110
DDB Configuration (Networks folder) • 130
Coefficient calculation • 106
Defaults view bar • 10
Common Operation menu functions • 63
Defining Ancillary labels • 129
Commuter tab • 151
Defining and configuring Ovation I/O
Compact Contact Input module configuration
modules • 236
• 242
Delete function • 63
OW351_60 373
Index
Determining the need for a new drop • 154

Developer Studio - Alert window • 29 G
Developer Studio definition • 1 Getting RAID fault information • 313
DeviceNet module configuration • 279
DeviceX.CommunityName • 141 H
DeviceX.Name • 143
Hardware placement for redundant modules
DeviceX. TimeOutBitNumber • 140
• 302
DeviceX. TimeOutPoint Name • 140
Hardware tab field descriptions • 188
DeviceX.VariableY.BitMask • 143
Hardware view bar • 9
DeviceX.VariableY.BitMaskEnabled • 142
HART Analog Input module configuration •
DeviceX.VariableY.BitNumber • 143
247
DeviceX.VariableY. ConfiguredV alue • 142
HART Analog Output module configuration •
DeviceX.VariableY.Frequency • 141
247
DeviceX.VariableY.LowerLimit • 142
HART High Performance Analog Input
DeviceX.VariableY. Name • 141
module configuration • 248
DeviceX.VariableY.PointName • 143
HART High Performance Analog Output
DeviceX.VariableY. Test • 141
module configuration • 249
DeviceX.VariableY. UpperLimit • 142
Help menu on the Developer Studio window
Dialog boxes • 27
• 20
Digital Excitation Controller module
Help System search methods • 4
configuration • 276
High-level auditing example • 345
Digital Input module configuration • 242
Holding Register Editor menu and toolbar
Digital Output module configuration • 244
functions • 363
DIOB testing for Q-Line modules • 371
Holding Register print dialog box • 367
Disabled Offline mode attributes • 128
Holding Register print preview dialog box •
Display tab field descriptions • 211
369
Download function definition • 99
Holding Register print setup dialog box • 368
Downloading configuration changes to
multiple drops • 102 I
Drops folder features and functions • 46
Dynamic Status feature • 29 Information needed before adding an I/O
module • 226
E Initial tab field descriptions • 190
Inserting a drop point • 161
Edit menu on the Developer Studio window •
Instrumentation tab field descriptions • 203
14
Introduction to RAID fault information • 313
Enabled Offline mode attributes • 127
Introduction to the Ovation Developer Studio
Enabling Offline Mode through Import
•1
Operations • 128
Engineering Tools Audit • 341 L
Environment tab • 150
Ethernet Link module configuration • 279 License Key tab • 150
Example of the Find all references made by License Manager components • 149
... option • 81 Licenses warning boxes and error messages
Example of the Find all references made by • 147
and children ... option • 83 Licensing requirements for an Ovation
Example of the Find all references to ... Windows-based system • 146
option • 77 Limits tab field descriptions • 206
Example of the Find all references to and Load application information • 95
children ... option • 79 Load function definition • 94
Loop Interface module configuration • 250
F Low-level auditing example • 347
File menu on the Developer Studio window • M
14
Find function • 85 Machinery Health Monitor module
Foundation Fieldbus module configuration • configuration • 252
278 Managing Ovation licenses • 145
Medium-level auditing example • 346
374 OW351_60
Index
QLine Sequence of Events module

N configuration • 296
Network Time Protocol (NTP) (Networks QLine Serial Link Controller module
folder) • 132 configuration • 296
Networks folder features and functions • 39 QLine Servo Drive module configuration •
297
O QLine Speed Detector module configuration
• 300
Operation menu on the Developer Studio
QLine Valve Position Controller module
window • 15
Operation right-click menu • 18
Query Options tab • 149
Operation toolbar • 22
Operations permitted in Offline mode • 128 R
Overview of adding I/O modules to the
Developer Studio • 227 Reboot function • 113
Overview of configuring iDRAC, SNMP, and Recommendations for IP address selection •
points • 314 315
Reconcile function • 104
P Reconciled fields for Analog and Deluxe
Analog fields • 104
Plant Mode (Units folder) • 135
Redundant module failover and recovery •
Plant Mode tab field descriptions • 213
303
Point description • 165
Resetting iDRAC to Factory Default Settings
Point name understanding • 167
• 340
Point names (fully qualified) • 167
RTD module configuration • 258
Point Processing (All folders) • 136
RTD values (16-channel and 8-channel
Point tab field description • 180
compact) • 265
Points folder features and functions • 168
RTD values (4-channel) • 263
Profibus module configuration • 278
RTD values (8-channel) • 264
Pulse Accumulator module configuration •
Rules for using fully qualified point names •
253
168
Purge function • 64
Q S
Sample of XML file • 222
QLine Analog Input module configuration •
Search function • 65
281
Security tab field descriptions • 187
QLine Analog Output module configuration •
Selecting a connection method • 315
283
Sequence of Events module configuration •
QLine Compact Contact Input module
265
Serial Link Controller module configuration •
QLine Digital Input module configuration •
269
288
Servo Drive module configuration • 269
QLine Digital Output module configuration •
Setting the Online/Offline mode • 127
289
SNMP (Drops) • 138
QLine HART High Performance Analog
SNMP Parameter settings • 140
Input module configuration • 284
Speed Detector module configuration • 270
QLine HART High Performance Analog
Standard toolbar • 21
Output module configuration • 285
Status bar • 29
Q-Line I/O module addressing • 372
Subfolders available in the Drops folder • 46
QLine Loop Interface module configuration •
Subfolders available in the Networks folder •
290
40
QLine module configuration • 280
Subfolders available in the Systems folder •
QLine Pulse Accumulator module
35
Subfolders available in the Units folder • 43
QLine Relay Output module configuration •
Summary of Changes • 3
295
System view bar • 8
QLine RTD module configuration • 286
Systems folder features and functions • 35
OW351_60 375
Index
To download configuration changes to

T multiple Drops • 102
Terminology used with SNMP and RAID • To download information • 100
314 To edit drop information • 161
To access the iDRAC Settings utility • 316 To enable iDRAC pass through • 321
To access the iDRAC Web interface • 317 To exit a successful or unsuccessful
To access the Image Builder • 53 Security Infrastructure Update wizard •
To access the License Manager • 148 121
To access the Ovation Audit Viewer • 348 To insert a Controller drop in the Developer
To add a new PDS Point Group • 215 Studio • 157
To add a PDS Point Group Member • 217 To insert a Module point • 233
To add a point in the Developer Studio • 170 To insert a new Holding Register • 359
To add a point name to the Primary and To insert a Unit folder • 44
Secondary I/O modules • 311 To insert a workstation drop in the
To add or delete images (icon) in the Developer Studio • 155
dictionary • 57 To insert an I/O Device in the Developer
To add the device number to the Controller • Studio • 229
304 To insert an I/O Device number in a
To adjust columns using the right-click menu Controller • 227
• 356 To insert an Ovation I/O module in the
To archive audit data • 357 Developer Studio • 231
To associate an image to a class (Studio To insert the Primary I/O module into the
item) • 55 Developer Studio system tree • 306
To begin the Search function • 66 To insert the Secondary I/O module into the
To bypass a download preview • 102 Developer Studio system tree • 308
To change class associations • 56 To link the Primary and Secondary I/O
To change Holding Register values • 366 modules • 310
To clear application information • 110 To load error messages • 98
To complete the image building or editing To load the Controller (for a redundant I/O
process • 59 module) • 312
To configure an external server as the NTP To modify Ancillary labels • 130
server • 132 To modify PDS Point Groups • 217
To configure an Ovation Domain Controller To modify PDS Point Groups Member • 218
as the NTP server • 134 To modify SNMP • 144
To configure defaults for items in the To modify the analog point that represents
Defaults view bar • 11 your Plant Mode • 136
To configure iDRAC network settings • 327 To modify the network DDB configuration •
To configure SNMP • 138 131
To configure the managed computer's host To modify the Networks configuration
interface adapter • 328 parameters • 41
To configure the managed computer's virtual To modify the OS to iDRAC Pass Through
adapter • 323 IP address • 326
To configure the SNMP • 337 To modify the Systems configuration
To Create a Baseline • 124 parameters • 37
To create a new toolbar • 25 To open an existing Holding Register • 360
To create Ancillary labels • 129 To process a point • 136
To create points for SNMP RAID • 333 To Reboot • 113
To customize toolbars • 24 To review and confirm the options you
To define a group number • 219 selected • 120
To define search criteria for an audit report • To run a Baseline Comparison • 125
352 To run a Coefficient Calculation • 107
To define text string values in an XML file • To run a Consistency Check • 92
221 To schedule backups • 89
To define the analog point that represents To select the type of update to perform • 119
your Plant Mode • 135 To set the Engineering Audit level • 344
To delete a Baseline Comparison entry • 126 To show or hide columns using the menus •
355
376 OW351_60
Index
To specify a Network Alias name • 116 Using the Web Interface • 340
To specify a new Network Alias name • 118
To specify the type of update to perform • V
117 Valve Position Controller module
To use the Delete function • 64 configuration • 273
To use the Dynamic Status feature • 30 View menu on the Developer Studio window
To use the Find feature • 85 • 19
To use the holding Register Editor Viewing online help • 4
preferences window • 365 Viewing the RAID status in the System
To use the Load Preview function • 96 Viewer application • 339
To use the Ovation Backup function • 87
To use the Point Copy function to add points W
to the Developer Studio • 171
What are drops? • 153
To use the Purge function • 64
What are Holding Registers? • 359
To use the Restore function • 91
What are Packed Group Numbers? • 219
To use the Search function to add columns •
What are PDS Point Groups? • 215
71
What are the Developer Studio menus? • 13
To use the Search function to display results
What are the Developer Studio
• 70
subwindows? • 26
To use the Search function to perform a
What are the Developer Studio toolbars? •
narrow search • 68
20
To use the Undelete function • 65
What are the Developer Studio window
To use the Update Security Infrastructure
components? • 6
Wizard • 115
What are the main windows of the
To use the Where Used function • 74
Developer Studio? • 7
To view current Engineering Tool audits •
What are the storage limits? • 358
350
What are the types of licenses? • 146
To view individual event information • 354
What if the storage limits are exceeded? •
TrashCan view bar • 12
358
U What information is included in this manual?
•2
Undelete function • 64 What information must be configured for
Understanding Ovation licensing • 145 each point type? • 172
Understanding point record types and sizes • What is a point record? • 166
169 What is a record field? • 166
Understanding redundant I/O modules • 301 What is the Audit log archive? • 356
Understanding the Backup/Restore What is the Developer Studio system tree
Parameters tab • 88 structure? • 33
Understanding the Configuration subfolder What is the Engineering Tools Audit
at all levels in the Developer Studio • 47 function? • 341
Understanding the Developer Studio What is the License Manager? • 148
hierarchical tree structure • 33 What is the optional DIOB Test tool used
Understanding the Developer Studio for? • 371
Overview window • 8 What is the Print Screen utility? • 126
Understanding the Developer Studio What is the purpose of an Ovation I/O
windows, menus, and toolbars • 5 module? • 225
Understanding the Holding Register Editor What Ovation applications are audited with
window • 361 the Engineering Audit Tools function? •
Understanding the Points dialog box and its 342
tabs • 177 What tools are available for status and error
Understanding the WorkPad window • 13 checking on the Developer Studio? • 29
Units folder features and functions • 43 What types of drops are available? • 154
Update Security Infrastructure function • 114 Where Used function • 73
Using the Ovation Audit Viewer • 347 Window toolbar • 22
Using the Ovation Developer Studio online Wizards • 26
help • 3 Working with common Developer Studio
Using the Settings utility • 340 operations • 63
OW351_60 377
Index
Working with special Developer Studio

functions • 127
378 OW351_60

Ow351 60 PDF

Загружено:

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

Оригинальное название

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

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

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

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

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

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

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

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

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

Ow351 60 PDF

Загружено:

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

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

Developer Studio User Guide for Ovation 3.5.

E-Mail: Technical.Communications@EmersonP rocess.com

Developer Studio User Guide for Ovation 3.5.1

 Added the new I/O modules in the following sections:

1 Introduction to the Ovation Developer Studio 1

2 Understanding the Developer Studio windows, menus,

3 Understanding the Developer Studio hierarchical tree structure 33

4 Working with common Developer Studio operations 63

4.9 Consistency Checking............................................................................................... 91

5 Working with special Developer Studio functions 127

5.6 Point Processing (All folders) ................................................................................... 136

6 Managing Ovation licenses 145

7 Adding drops to the Developer Studio 153

8 Creating Points in the Developer Studio 165

9 Adding I/O to the Developer Studio 225

10 Adding and configuring redundant I/O modules 301

11 Getting RAID fault information 313

12 Engineering Tools Audit 341

12.5.2 AuditView menu bar .................................................................................... 349

13 Adding Holding Registers 359

14 DIOB testing for Q-Line modules 371

1 Introduction to the Ovation Developer Studio

What is the Ovation Developer Studio? ........................................................................ 1

1.1 What is the Ovation Developer Studio?

 Define and configure an Ovation system.

1.2 What information is included in this manual?

1.3 Using the Ovation Developer Studio online help

You can access this help in several ways:

Figure 1: Developer Studio online help

1.3.1 He lp Syste m se arch me thods

The online help window has the following three tabs:

1.3.2 Vie wing online he lp

2 Understanding the Developer Studio windows,

Accessing the Ovation Developer Studio ...................................................................... 5

2.1 Accessing the Ovation Developer Studio

2.2 What are the Developer Studio window components?

Figure 2: Example of Ovation Developer Studio window components

2.3 What are the main windows of the Developer Studio?

There are three main areas of the Developer Studio:

2.4 Understanding the Developer Studio Overview window

The Overview window provides the following view bars.

Figure 3: Overview window

Figure 4: Ovation Systems Bar

2.4.2 Hardware v iew bar

Figure 5: Hardware view bar expanded in Overview window

2.4.3 De faults v iew bar

Some examples of point fields that can be set as defaults are:

The following figure shows all 13 default types.

Figure 6: Defaults view bar displayed in Overview window

2.4.4 T o configure de faults for ite ms in the De faults v iew bar

1. Access the Developer Studio (see page 5).

Figure 7: Default Analog point dialog box

7. Select Ok/Apply to add the information to the database.

2.4.5 T rashCan v iew bar

Figure 8: TrashCan view bar expanded

2.5 Understanding the WorkPad window

WorkPad view buttons

2.6 What are the Developer Studio menus?

 File (see page 13).

Figure 9: Menu bar

2.6.1 File me nu on the De v eloper Studio win dow

File menu items

Exit Quits the Developer Studio.