Developer Studio User Guide for Ovation 2.

4
OW240_60

Revision 0
April 2005
 Contents

1 Introduction to the Ovation Developer Studio 1

1.1 Ovation Developer Studio Philosophy ........................................................................................1
1.2 Common Functions Performed in the Developer Studio ............................................................2
1.3 What is the Developer Studio System Tree? ..............................................................................5
1.3.1 Philosophy of the Developer Studio System Tree ....................................................5
1.3.2 The Developer Studio System Tree Structure ..........................................................6
1.3.3 What are the Systems Folder Features and Functions?...........................................6
1.3.4 What are the Networks Folder Features and Functions? .........................................7
1.3.5 What are the Units Folder Features and Functions? ................................................7
1.3.6 What are the Drops Folder Features and Functions?...............................................8
1.3.7 What are the Points Folder Features and Functions? ..............................................8
1.4 Using Ovation Online Help........................................................................................................10

2 The Ovation Developer Studio Interface 11

2.1 Developer Studio Components .................................................................................................12
2.1.1 Menu Bar Options ...................................................................................................14
2.1.2 Right-Click & Operation Pull-Down Menu, Operation Tool Bar...............................16
2.1.3 Tool Bars .................................................................................................................16
2.1.4 Overview Window View Bars ..................................................................................20

3 How Do I Configure Objects? 27

3.1 To Insert New or Open a Dialog Box ........................................................................................28
3.2 To Insert New or Open a Dialog Box in the WorkPad ..............................................................29
3.3 Typical Dialog Box ....................................................................................................................30
3.4 Typical Wizard Dialog Box ........................................................................................................31

4 Developer Studio Functions 33

4.1 Backup/Restore.........................................................................................................................33
4.2 Clear Function...........................................................................................................................33
4.2.1 To Clear Application Information .............................................................................34
4.3 Coefficient Calculation ..............................................................................................................34
4.3.1 To Run a Coefficient Calculation.............................................................................35
4.4 Data Validation..........................................................................................................................36
4.5 Consistency Checking...............................................................................................................37
4.5.1 To Run Consistency Checking ................................................................................37
4.5.2 Consistency Checking Report .................................................................................38
4.6 Download Function ...................................................................................................................38
4.6.1 To Download Information ........................................................................................39
4.6.2 Downloading Configuration Changes to Multiple Drops .........................................40

OW240_60 i
Table of Contents

4.7 Delete Function .........................................................................................................................42

4.7.1 To Use the Delete Function.....................................................................................43
4.8 Dynamic Status Feature............................................................................................................43
4.8.1 To Use Dynamic Status Features ...........................................................................44
4.9 Export Function .........................................................................................................................45
4.9.1 To Use the Export Function.....................................................................................45
4.10 Find Function ............................................................................................................................45
4.10.1 To Use the Find Feature .........................................................................................45
4.11 Import Function .........................................................................................................................46
4.11.1 To Use the Import Function.....................................................................................47
4.12 Load Function ...........................................................................................................................47
4.12.1 To Load Application Information..............................................................................47
4.13 Purge Function..........................................................................................................................48
4.13.1 To Use the Purge Function .....................................................................................48
4.14 Reboot Function........................................................................................................................48
4.14.1 To Reboot................................................................................................................49
4.15 Reconcile Function....................................................................................................................49
4.15.1 Reconciled Fields for Analog and Deluxe Analog Fields ........................................50
4.15.2 To Reconcile Originated Points and Controller Drop Changes...............................52
4.16 Search Function ........................................................................................................................53
4.16.1 To Use the Search Function - Object Selection ......................................................54
4.16.2 To Use the Search Function - Item Selection .........................................................55
4.16.3 To Use the Search Function - Narrow Search ........................................................56
4.16.4 To Use the Search Function - Results ....................................................................57
4.17 Undelete Function .....................................................................................................................59
4.17.1 To Use the Undelete Function.................................................................................60
4.18 Where Used Function ...............................................................................................................60
4.18.1 To Initiate the Where Used Function - Options .......................................................61
4.18.2 To Initiate the Where Used Function - Results .......................................................61
4.19 Ovation Developer Studio - Alert ..............................................................................................63

5 Building a System 65
5.1 To Insert a System ....................................................................................................................66
5.1.1 To Modify a System.................................................................................................67
5.2 To Insert a Network...................................................................................................................68
5.2.1 To Modify a Network ...............................................................................................69
5.3 To Insert a Unit..........................................................................................................................70
5.3.1 To Modify a Unit ......................................................................................................71
5.4 To Insert a Drop ........................................................................................................................71
5.5 To Add a Point ..........................................................................................................................72

6 Managing Ovation Licenses 73

6.1 License Philosophy ...................................................................................................................74
6.2 Licenses Warning Boxes and Error Messages .........................................................................75
6.3 To Access the License Manager...............................................................................................75
6.3.1 License Manager Operations Area .........................................................................76

ii OW240_60
 Table of Contents

7 Working with Developer Studio Functionality 79

7.1 Building Security .......................................................................................................................79
7.2 Setting Default Folders..............................................................................................................80
7.3 Defining Ancillary Labels...........................................................................................................80
7.3.1 To Create Ancillary Labels ......................................................................................81
7.3.2 To Modify Ancillary Labels ......................................................................................82
7.4 Working with Graphics ..............................................................................................................82
7.5 Setting the Online/Offline Mode ................................................................................................82
7.5.1 To Enable the Offline Mode Attribute ......................................................................83
7.5.2 To Disable the Offline Mode Attribute .....................................................................83
7.5.3 Operations Permitted in Offline Mode .....................................................................83
7.5.4 Offline Mode via Import Operations ........................................................................84
7.6 Working with Control Tasks ......................................................................................................84

8 Developer Studio Configuration Folder 85

8.1 Configuration Folder Philosophy...............................................................................................85
8.1.1 Configuring the External Interface...........................................................................85
8.2 Configuration Components .......................................................................................................86
8.3 Modifying Dynamic Data Blocks (DDB) ....................................................................................88
8.3.1 To Modify a DDB Configuration ..............................................................................89
8.4 Inserting External Networks Connections .................................................................................90
8.4.1 To Create an External Network Connections Folder ..............................................91
8.5 Working with the Image Builder ................................................................................................92
8.5.1 To Insert the Image Builder Dictionary....................................................................93
8.5.2 To Edit the Image Builder Dictionary.......................................................................94
8.5.3 To Remove an Icon/Class Association ...................................................................95
8.5.4 To Add an Icon/Class Association ..........................................................................95
8.5.5 To Add an Icon to the Dictionary.............................................................................96
8.5.6 To Delete an Icon From the Dictionary ...................................................................97
8.5.7 To Change an Icon in the Dictionary and All of its Associations.............................97
8.6 Configuring the Simple Network Management Protocol (SNMP) .............................................98
8.6.1 To Configure SNMP ................................................................................................98
8.6.2 SNMP Parameter Settings ....................................................................................100
8.6.3 Modifying SNMP....................................................................................................103
8.7 Configuring the Network Time Protocol (NTP)........................................................................104
8.7.1 To Configure the Network Time Protocol (NTP) Folder ........................................104
8.8 Working with the Plant Mode ..................................................................................................106
8.8.1 To Add a Plant Mode to a Unit ..............................................................................107
8.8.2 To Modify the Plant Mode .....................................................................................108
8.9 Point Processing .....................................................................................................................108
8.9.1 To Process a Point ................................................................................................109
8.10 Online Controller Restore Mode .............................................................................................111
8.10.1 To Configure the Online Controller Restore Mode................................................112

OW240_60 iii
Table of Contents

9 Building Drops 113

9.1 Drop Philosophy......................................................................................................................113
9.2 Drop Types..............................................................................................................................114
9.3 Is a New Drop Needed, and Can It Be Installed? ...................................................................114
9.4 What Information is Needed before Adding a Drop? ..............................................................115
9.4.1 To Determine the IP Address of a Windows Machine/Drop..................................115
9.4.2 To Determine NIC (Network Ethers) Address .......................................................116
9.5 To Insert a Drop ......................................................................................................................118
9.5.1 To Enter Drops Info for Controllers .......................................................................119
9.5.2 To Enter Drops Info for SimController...................................................................121
9.5.3 To Enter Drops Info for Advanced SimController..................................................123
9.5.4 To Enter Drops Info for Advanced Controller ........................................................125
9.5.5 To Enter Drops Info for Base Stations ..................................................................126
9.5.6 To Enter Drops Info for Operator Station ..............................................................128
9.5.7 To Enter Drops Info for Sim Operator Station .......................................................130
9.5.8 Virtual Controller & Virtual Controller Host............................................................132
9.6 To Insert a Drop Point .............................................................................................................138
9.7 To Modify a Drop.....................................................................................................................140

10 Defining and Configuring the I/O Devices 141

10.1 Planning I/O for Your System .................................................................................................142
10.2 Ovation I/O Base Types ..........................................................................................................143
10.2.1 Standard I/O Base.................................................................................................143
10.2.2 Relay Output Base ................................................................................................144
10.3 Addressing the Ovation I/O Modules ......................................................................................144
10.3.1 Addressing Format ................................................................................................144
10.3.2 Examples of Module Addresses (Controller Cabinet) ...........................................146
10.3.3 Examples of Module Addresses (Extended I/O Cabinet).....................................147
10.3.4 Examples of Module Addresses (Remote Node Cabinet) ....................................148
10.3.5 Examples of Module Addresses (Relay Output Modules) ....................................149
10.3.6 Addressing the Q-Line I/O Modules ......................................................................150
10.4 Guidelines for Positioning Modules.........................................................................................150
10.5 Creating Local or Remote Ovation I/O Devices ......................................................................151
10.6 Third Party Devices.................................................................................................................151
10.7 Creating Foundation Fieldbus Devices ...................................................................................151
10.8 Modifying an I/O Device ..........................................................................................................152
10.8.1 To Modify an I/O Device........................................................................................152
10.9 Modifying an External Ovation Networks Device ....................................................................152

11 Building Points 153

11.1 Point Builder Philosophy .........................................................................................................153
11.1.1 I/O Point Hardware Mapping .................................................................................153
11.1.2 Point Naming Rules...............................................................................................154
11.2 To Create a Point ....................................................................................................................156
11.2.1 Point Dialog Box....................................................................................................157

iv OW240_60
 Table of Contents

11.3 Point Types and Dialog Box Tab Descriptions........................................................................159

11.3.1 Analog Point Type and Dialog Box Tabs ..............................................................159
11.3.2 Deluxe Analog Point Type and Dialog Box Tabs ..................................................160
11.3.3 Digital Point Type and Dialog Box Tabs................................................................162
11.3.4 Packed Digital Point Type and Dialog Box Tabs...................................................163
11.3.5 Deluxe Digital Point Type and Dialog Box Tabs ...................................................164
11.3.6 Packed Point Type and Dialog Box Tabs..............................................................164
11.3.7 Deluxe Packed Point Type and Dialog Box Tabs .................................................165
11.3.8 Algorithm Point Type and Dialog Box Tabs ..........................................................166
11.3.9 Drop Point Type and Dialog Box Tabs..................................................................167
11.3.10 Module Point Type and Dialog Box Tabs..............................................................168
11.3.11 Node Point Type and Dialog Box Tabs .................................................................170
11.3.12 Alarm Tab ..............................................................................................................171
11.3.13 Ancillary Tab..........................................................................................................172
11.3.14 ASCII Params Tab ................................................................................................172
11.3.15 Byte Params Tab...................................................................................................172
11.3.16 Config Tab .............................................................................................................172
11.3.17 Display Tab............................................................................................................174
11.3.18 Hardware Tab........................................................................................................175
11.3.19 eDB Tab ................................................................................................................177
11.3.20 Initial Tab ...............................................................................................................177
11.3.21 Instrumentation Tab ..............................................................................................178
11.3.22 Int Params Tab......................................................................................................181
11.3.23 Limits Tab ..............................................................................................................181
11.3.24 Plant Mode Tab .....................................................................................................184
11.3.25 Point Tab ...............................................................................................................184
11.3.26 Real Params Tab ..................................................................................................185
11.3.27 Security Tab ..........................................................................................................185
11.4 Configuring Complex Points....................................................................................................186
11.4.1 Analog Input Points ...............................................................................................186
11.4.2 Analog Output Points ............................................................................................187
11.4.3 Analog/Thermocouple Points ................................................................................187
11.4.4 Digital Input Points ................................................................................................187
11.4.5 Digital Output Points..............................................................................................188
11.4.6 Pulse Accumulator Points .....................................................................................188
11.4.7 RTD Points ............................................................................................................188
11.5 Third Party Points....................................................................................................................188
11.6 Modifying a Point.....................................................................................................................189
11.6.1 To Modify a Point ..................................................................................................189

12 Building Point Groups 191

12.1 Point Groups Philosophy.........................................................................................................191
12.2 To Access the Point Groups Folder ........................................................................................191
12.3 To Add a Trend Point Group ...................................................................................................192
12.3.1 To Modify a Trend Point Group .............................................................................194
12.3.2 To Add a Trend Point Group Member...................................................................194
12.3.3 To Modify a Trend Point Group Member...............................................................198
12.4 To Add a New PDS Point Group.............................................................................................199
12.4.1 To Modify PDS Point Groups ................................................................................200
12.4.2 To Add a PDS Point Group Member.....................................................................201
12.4.3 To Modify PDS Point Groups Member..................................................................202

OW240_60 v
Table of Contents

12.5 To Add a New eDB Point Group .............................................................................................203

12.5.1 To Modify eDB Point Groups.................................................................................204
12.5.2 To Add a eDB Point Group Member .....................................................................204
12.5.3 To Modify eDB Point Groups Member ..................................................................205

13 Adding Holding Registers 207

13.1 Holding Register Philosophy ...................................................................................................207
13.2 To Insert a New Holding Register ...........................................................................................208
13.3 To Open an Existing Holding Register....................................................................................209
13.3.1 To Change a Single Holding Register Value.........................................................210
13.3.2 To Change Multiple Holding Register Values .......................................................210
13.4 Holding Register Editor Dialog Box.........................................................................................211
13.4.1 Holding Register Editor Functions.........................................................................212
13.4.2 Holding Register Editor Preferences Dialog Box ..................................................214
13.4.3 Holding Register Print Dialog Box.........................................................................215
13.4.4 Holding Register Print Preview Dialog Box ...........................................................215
13.4.5 Holding Register Print Setup Dialog Box ..............................................................216

14 Ovation I/O Module Dialog Boxes 217

14.1 Defining and Configuring Ovation I/O Modules.......................................................................217
14.1.1 Analog Input Configuration....................................................................................217
14.1.2 Analog Output Configuration .................................................................................217
14.1.3 Compact Contact Input Configuration ...................................................................218
14.1.4 Contact Input Configuration...................................................................................218
14.1.5 Compact Digital Input Configuration .....................................................................218
14.1.6 Digital Input Configuration .....................................................................................219
14.1.7 Digital Output Configuration ..................................................................................219
14.1.8 HART Analog Input Configuration.........................................................................220
14.1.9 HART Analog High Performance Input Configuration...........................................220
14.1.10 HART Analog Output Configuration ......................................................................220
14.1.11 Loop Interface Configuration .................................................................................221
14.1.12 Loop Interface Dialog Box (Electric Drive Mode) ..................................................222
14.1.13 Pulse Accumulator Configuration..........................................................................223
14.1.14 RTD Configuration.................................................................................................225
14.1.15 Relay Output Module G2R Configuration..............................................................226
14.1.16 Relay Output Module KUEP Configuration ...........................................................227
14.1.17 Sequence of Events Configuration........................................................................227
14.1.18 Compact Sequence of Events Configuration ........................................................228
14.1.19 Serial Link Controller Configuration .....................................................................230
14.1.20 Servo Driver Configuration ...................................................................................230
14.1.21 Speed Detector Configuration ...............................................................................230
14.1.22 Valve Positioner Configuration ..............................................................................232

vi OW240_60
 Table of Contents

A DIOB Testing for Q-Line Modules 233

A.1 How is Q-Line Testing Accomplished? ...................................................................................233
A.2 Addressing the Q-Line I/O Modules........................................................................................234

Index 237

OW240_60 vii
S E C T I O N 1

INTRODUCTION TO THE OVATION DEVELOPER STUDIO

In This Section

Ovation Developer Studio Philosophy ................................................................... 1

Common Functions Performed in the Developer Studio ....................................... 2
What is the Developer Studio System Tree? ......................................................... 5
Using Ovation Online Help................................................................................... 10

1.1 OVATION DEVELOPER STUDIO PHILOSOPHY

The Ovation Developer Studio integrates process control engineering functions such as building
I/O, points and point groups; and configuring networks, Foundation Fieldbus and operator station
functions. In addition to process control functions, you manage Ovation licensing using the
Developer Studio. The Developer Studio enables you to configure system functions seamlessly,
reducing the number of different applications used, engineering time and the possibility of error.

You can configure a system in the Developer Studio both before system startup and when the
system is live. Use the Developer Studio to create and maintain Ovation drop types, control
strategies, process graphics, point records and system-wide configurations. Build an entire
system or import information form a previously created database. Configure all Operator Station
functions and attributes.

The Developer Studio's intuitive menu-driven graphic interface uses standard drag-and-drop
functionality to easily move or copy elements such as control logic, I/O points and process
graphics to different locations within the Ovation system. The object-oriented approach to system
configuration provides an operating environment that reduces the learning curve, simplifies
development and saves significant engineering effort.

Ovation Developer Studio categorizes functionality in a tree or hierarchal structure with System
information residing at the top of the tree followed by network, unit, drop and point information.
When you configure attributes in the system, the system attributes filter down the system tree into
the networks, units and drops that are subsets of that system.

You can also configure networks, units and drops to have different attributes then defined at the
system level by defining the attributes at lower levels in the system tree. Though attributes set at
the system level default down through the tree, attributes made in lower levels of the tree override
attribute definitions made at higher levels.

OW240_60 1
1.2 Common Functions Performed in the Developer Studio

1.2 COMMON FUNCTIONS PERFORMED IN THE DEVELOPER STUDIO

Ovation Developer Studio provides the tools necessary to configure your process control system.
Some of the common functions performed in the Developer Studio:

Licensing System Components

Licensing is a way to receive permission to enable certain Emerson Process Control software
products and processes. 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 the growth of a system over time. Small systems can normally operate with fewer licenses
than larger systems.

Configuring Drops

A Drop is any hardware/software that has enough Ovation software to receive and transmit
information to other Ovation hardware/software. The Ovation software contains several Drop
Types (see page 114)). The Developer Studio provides a mechanism for the adding and deleting
of Drops to the system database.

Note: You will only be able to add as many drops as defined by the license key. Before entering
drops, verify that the 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 73) for more information about licensing.

After a drop has been created, a Drop Point must be created in order for the system to recognize
the new drop. This Drop Point corresponds to the drop’s required DU record, see To Insert a
Drop Point (see page 138). (See Ovation Record Types.)

After a drop and its Drop Point have been created, and loaded to the target drop, it may be
necessary to make modifications to the drop. To modify a drop, see To Modify a Drop (see page
140). Drops are established and configured using the objects within a Drop folder.

Configuring the Operator Station

The Configuration folder (see page 86) exists in the Systems folder, Networks folder, Units
folder, and Drops folder. At each level, the Configuration folder’s subfolders vary. The
Configuration folder at the Systems thru Drops level contains the tools necessary to configure
components on the system level.

Configurations made at the Systems level default down through the Networks, Units and Drops
levels. Any configurations changed at a lower level will also default down through its subfolders
and lower levels. The configuration defined at the lowest level takes precedence in its subfolders.

For example, if an alarm configuration change is made at the unit level, it will affect all alarms in
that unit and in all the drops contained in the unit. However, the change does not affect other units
in the network or system.

Accessing the Ovation Security Manager

Security for an Ovation system is designed to prevent an unauthorized user from performing an
unauthorized action on an Ovation control system. This is accomplished by the assignment of
security roles for users and drops in the domain. All security selections and assignments are
saved in the Active Directory database.

2 OW240_60
 1.2 Common Functions Performed in the Developer Studio

Configuring I/O

The I/O (Input/Output) Devices folder contains tools used to define the I/O modules for the
Ovation system. The I/O Device folders contain Setup Wizards and dialog boxes that provide
visual representation of the I/O Devices for an Ovation system.

The following hardware reference information may be useful when defining I/O modules in the
Ovation Developer Studio.

Commissioning Field Devices

Commissioning is the act of setting a control system to properly address and know how to
communicate to a field instrument, and for that instrument to have all the blocks in the control
scheme configured to the desired parameters (for example, tag name, analog input scaling,
channel assignment, etc.) Gateways and devices are commissioned through the Foundation
Fieldbus engineering window.

Building Points

A Point is a record in the global database that contains a value (such as an input or output) and
other related data. There are currently 11 point types in Ovation.

Each point type has its own dialog box with distinct tabs and fields. Thus each Point Dialog Type
will have its own Point Dialog Box tabs, fields, and descriptions. The table under Point Dialog
Box Tabs (see page 159) lists all possible tabs and all the fields available for each Point Type.
Not all tabs will appear in the dialog box for each Point type. (See Ovation Record Types
Reference Manual.)

Creating Point Groups

Point Groups are various points grouped together for monitoring and trending and process
diagram purposes. Point Groups can be added through the Developer Studio or through an
Ovation 1.x or 2.x import file from an existing Ovation 1.x system. Points included in the Point
Group are called members.

The Point Group folder is located under the System object in the System Tree. Point Groups are
distribute to all Ovation Windows type drops.

There are three types of Point Groups: eDB Point Groups, Trend Point Groups and PDS Point
Groups. Trend Point Groups associate a commonly used set of points and track them over time.
eDB Point Groups used for PDS Point Groups allow generic graphics to be created that do not
hard code points, but rather reference points via the point group. Point Groups have configurable
items at the group level and the member level.

The new point groups or members are added (or edited) on-line; 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 Building Points (see page 153).

Accessing the Graphics Builder

OW240_60 3
1.2 Common Functions Performed in the Developer Studio

The Graphics folder provides access to the Graphics Builder application (GBNT). GBNT resides
on the Ovation Developer Studio and is used to develop the Process diagrams that are displayed
on the Ovation Operator Station. These process diagrams are software programs, which display
graphical images representing plant process control equipment.

Creating Trend Groups

A trend is a display that plots point values over a selected time interval. The display is based on
MMI trend history, or on information gathered from the systems databases. A Trend Group is a
collection of points that have similar usage. The trend group will display point value plots of the
grouped points for comparison.

Creating 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.

4 OW240_60
 1.3 What is the Developer Studio System Tree?

1.3 WHAT IS THE DEVELOPER STUDIO SYSTEM TREE?

1.3.1 P HILOSOPHY OF THE D EVELOPER S TUDIO S YSTEM T REE

The Developer Studio was designed in a tree (or system hierarchy) structure, as seen when the
Hardware View Bar (see page 21) is selected. 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 6), Network (see page 7),
Unit (see page 7), Drop (see page 8), and Point (see page 8) level.

The configuration of an element at a higher level folder enables the user to specify, in one place,
how to configure a particular item of the Ovation System. The configuration settings at a high level
drives the configuration of all applicable items (e.g., Ovation drops) below it in the hierarchy,
UNLESS that same type of configuration object is redefined at a lower level.

For example, if the trend screen background color is set to black at the System level, all trend
screen background colors will default to black throughout the entire system. If, however, a trend
screen background color is changed to green at the Unit level, trend screens in that unit, including
all of the drops in that unit, will utilize the green background. Trend screens above the units' level
will remain black. By having defaults move down through the system, configuration information
can be specified easily and customized where necessary.

Any settings made to the Configuration or Graphic contents will default down through the other
major folders to the point where you make a change, then that change will default down through
the remainder of the folders.

OW240_60 5
1.3 What is the Developer Studio System Tree?

1.3.2 T HE D EVELOPER S TUDIO S YSTEM T REE S TRUCTURE

Each object (or element) of the System Tree contains all the specific elements for that level. For
example, the Drops object will contain all drops for a specific unit. You can insert and configure
Drops through the Studio Drops object. The functionality for each level, listed at the right of each
folder, will be explained as needed, most functions can be found in Adding Functionality to the
Developer Studio (see page 79).

Figure 1: The Developer Studio System Tree

1.3.3 W HAT ARE THE S YSTEMS F OLDER F EATURES AND F UNCTIONS ?

6 OW240_60
 1.3 What is the Developer Studio System Tree?

The Systems folder resides directly beneath the Hardware node and at the top of the System
Tree. A System folder encompasses all settings and configurations for the entire system below it,
and is the parent of the Networks folder. If there were multiple systems within one database, each
system object would appear in the Systems folder and would provide for the configuration for
each system.

Think of the processes in the system area as the overall control of everything in the total system,
as it sets up and limits how all the other layers of the system below it will function.

Additional Systems functionalities includes the External Systems Interface (see page 90),
Licenses (see page 73), Security (see page 79), Ancillary (see page 80), Point Groups (see
page 191), general Configuration (see page 85) and Graphics (see page 82) functions.

Configuration components that are controlled by the Developer Studio starting at the System level
are the Image Builder (see page 92) and Point Processing (see page 108).

Working at the system level makes it easy to generically configure parameters and graphics
throughout the Developer Studio. External System Interface through the Point Groups is exclusive
to the System object, while Configuration and Graphics are found in each major folder.

1.3.4 W HAT ARE THE N ETWORKS F OLDER F EATURES AND F UNCTIONS ?

The Networks Folder is a child of a System object and contains an object for each network in that
system. A Network folder contains all settings for that network, and is the parent of the Units
folder. The Networks folder is the parent folder to all files, objects and folders that pertain to the
Network.

The only additional functionality at the Networks level is Graphics (see page 82) and
Configuration (see page 85).

Configuration components that are controlled by the Developer Studio at the Networks level are
the DDB (see page 88), Network Time Protocol (see page 104) and Point Processing (see
page 108).

Note: Currently only one network is allowed per database.

1.3.5 W HAT ARE THE U NITS F OLDER F EATURES AND F UNCTIONS ?

OW240_60 7
1.3 What is the Developer Studio System Tree?

The Units folder is a child of the Network and contains a sub-folder for each Unit in the network.
The Unit object contains all settings for each unit, and has direct control over the Drops and their
Points below. The Unit object is the parent to all files, objects, and folders that pertain to that
particular unit.

If there were multiple units, each unit would appear in the Units folder and would provide for the
same configuration for each unit.

The Unit Folder was set up to allow multiple units (such as two units in a power plant) to operate
under the same system and allow separate configurations from what the Network sets up where
needed.

Functionality at the Units level includes Graphics (see page 82) and Configuration (see page
85). Configuration components that are controlled by the Developer Studio at the Units level are
the Network Time Protocol (see page 104) and Point Processing (see page 108).

Note: Currently, Ovation Studio is limited to 16 units per network.

1.3.6 W HAT ARE THE D ROPS F OLDER F EATURES AND F UNCTIONS ?

Note: Currently, Ovation Studio is limited to 254 drops per network.

The Drops folder is controlled directly from the Network, System and Unit object configuration
above it, and has direct control over the Points attached to it. This is the first level where we see
some hardware directly associated with its objects.

The additional functionality at the Drops level are Points (see page 153), I/O Devices (see page
217), Control Tasks (see page 84), Holding Registers (see page 207) and Configuration (see
page 85).

1.3.7 W HAT ARE THE P OINTS F OLDER F EATURES AND F UNCTIONS ?

8 OW240_60
 1.3 What is the Developer Studio System Tree?

Each item of data used within the Ovation system is referred to as a point. Points include field
inputs and outputs, calculated values, and internal system information. This gathered information
can be in the form of a temperature, level of solids or fluids, weight, vibration, amount of rotation,
timing, etc. You can identify each point by a name and a unique System ID number.

The Points folder is the standard interface to the points in the database. The Points folder is a
child of a Drops folder and contains an object for each point in the drop, which opens to reveal
Ovation point record information. Point records store the information that defines the attributes of
an Ovation point. These records contain the user definable fields of an Ovation point record and
in many cases have a direct bearing on how the point records function within the Ovation System.

OW240_60 9
1.4 Using Ovation Online Help

1.4 USING OVATION ONLINE HELP

The Ovation Windows-based system has an online Help system. The Help structure follows the
same scheme as Microsoft Windows applications.

Information can be found by using the Table of Contents, Index, Search tool, or by pressing the
F1 key when using an application dialog box. For example, when using an Edit Algorithm dialog
box, pressing F1 will display the complete description for the selected algorithm.

HELP SYSTEM SEARCH METHODS

If you select the Online Help option from an application menu, a pop-up window will appear. The
window contains three tabs:
ƒ Contents
ƒ Index
ƒ Search
The Contents tab is 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 access the information in the dialog box, click on the subject in the left-hand window. The
right-hand window will be populated with the corresponding help information.

The Index tab dialog box has a text entry field to search the index for specific information. The
system will search the index for an entry as you type the information. As you type, it will highlight
index help topics that alphabetically match your entry the closest. Choose a topic and click the
Display button to view help text. The right-hand window will be populated with the corresponding
help information.

The Search tab dialog box enables selection by entering a key word into the find box and clicking
the List Topics button. Topics will then be shown that match the keyword. Choose a topic and
click Display to view the topic. The right-hand window will be populated with the corresponding
help information.

VIEWING ONLINE HELP

You can set viewing preferences with the icons on the Menu Bar:
ƒ Hide and Show icons- Hide or show the three tabs (Contents, Index, Search). Click on the
Hide icon When the tabs are hidden, only the help text will be displayed. Click on the Show
icon to display the tabs again.
ƒ Back icon – Displays the previous help selection.
ƒ Forward icon – Displays the next help selection.
ƒ Print icon – Prints current help screen.

10 OW240_60
S E C T I O N 2

THE OVATION DEVELOPER STUDIO INTERFACE

In This Section

Developer Studio Components ............................................................................ 12

OW240_60 11
2.1 Developer Studio Components

2.1 DEVELOPER STUDIO COMPONENTS

The Developer Studio’s interface is comprised of:
ƒ Menu Bar — Provides access to Studio functions.
ƒ Overview Window — Displays the Hardware, Defaults or TrashCan View Bars.
ƒ Status Bar — Displays information about the current Studio session. The Status bar displays
menu information, identification of the drop where the database resides, the drop that is
servicing the current database connection, and whether certain keyboard functions such as
Caps Lock, Num Lock and Insert are operational.
ƒ Tool Bar — Provides specific Studio functions such as Save, Open and Create.
ƒ Dialog Box — Functional windows in which operations are performed. Files are stored in
folders called objects. Opening a file will generally spawn a function or document dialog box
in the Workspace window. Specific functionality of the dialog box will be discussed in To
Insert a System (see page 66) through To Build a Point (see page 72).
ƒ Workspace — Displays functional and document dialog boxes.
ƒ View Bars — The three function bars provide views of different aspects of the database. The
Hardware view bar accesses the System Tree. The System Tree is expandable to expose
additional objects and files. The Defaults view bar shows a tree structure of the default point
types and I/O devices. The TrashCan view bar is similar to the Windows Recycle Bin.
ƒ WorkPad Window — Displays selectable objects.
ƒ System Bar — Displays the Ovation system to which it is currently connected.
ƒ Tab — Allows a dialog box to contain multiple dialog windows for setting up the many aspects
of an object.
ƒ View Buttons — Change the appearance of objects in the WorkPad Window.

12 OW240_60
 2.1 Developer Studio Components

Figure 2: Developers Studio Interface

OW240_60 13
2.1 Developer Studio Components

2.1.1 M ENU B AR O PTIONS

The Menu Bar contains seven cascade buttons. Each button displays a pull-down menu.

Developer Studio Menu Bar

Menu Bar Pull-Down menu Items and Description

Button

File Print Setup — changes the printer and print options.

Print — prints the selected tab in the active document.
Print All — prints all the tabs in the active document.
Print Preview — displays the active document as it will appear printed.
Save As — saves the currently selected dialog box to a file.
Exit — exits the Developer Studio application.
Edit Undo — undoes the last action.
Cut — cuts the selection to the clipboard.
Copy — copies the selection to the clipboard.
Paste — pastes the clipboard contents.
Select All — selects everything in an active document.
Operation (See Right-Click & Operation Pull-Down Menu, Operation Tool Bar (see
page 16).)
Browse Also see Browse Tool Bar (see page 19).
Expand Child — shows all child objects of a selected object.
Collapse Child — closes all child folders of a selected folder.
Expand All — shows all objects up to the leaf nodes.
Collapse All — closes all folders and shows only the root node.

14 OW240_60
 2.1 Developer Studio Components

Menu Bar Pull-Down menu Items and Description

Button

View Workbook Mode — provides tabs for each functional dialog box opened in
the Workspace window.
Full Screen Mode — increases workspace size by eliminating all menu and
menu bars.
Customize Toolbar — opens the Customize Toolbar dialog box.
Overview Window — displays or hides the Overview window.
WorkPad Window — displays or hides the WorkPad window.
Status Bar — displays or hides the Status bar.
Lookup List As — displays objects in the WorkPad window in single
columns, multiple columns, or as icons.
ƒ Icon — changes the appearance of the folders and objects listed in the
WorkPad window.
ƒ Single column — lists the folders and objects in the WorkPad window
in one vertical column.
ƒ Multi-column/Vert. — lists the folders and objects in the WorkPad
window several vertical columns.
ƒ Multi-column/Horiz. — lists the folders and objects in the WorkPad
window in several horizontal columns.
Window Also see Window Tool Bar (see page 19).
(only Close — closes the active window in the Workspace.
available
when Close all — closes all windows open in the Workspace.
window is in
Next — if several windows are open in the Workspace, next activates the
work-space)
next window in the sequence.
Previous — if several windows are open in the Workspace, previous
activates the previous window in the sequence.
Cascade — stacks all windows in the Workspace diagonally, active window
always in front.
Tile Horizontally — stacks all windows horizontally in the Workspace;
double click a window's Title bar to activate it.
Tile Vertically — stacks all windows vertically in the Workspace; double
click a window's Title bar to activate it.
Help Contents and Index — displays the online Help for Ovation Developer
Studio.
About Ovation DevStudio — displays program information, version
number and copyright.

OW240_60 15
2.1 Developer Studio Components

2.1.2 R IGHT -C LICK & O PERATION P ULL -D OWN M ENU , O PERATION T OOL B AR

The Right-Click Menu and the Operation Pull-Down Menu, plus the Operation Tool Bar all have
most of the same functions, with the exception of Hide and Allow Docking which are only in the
Right-Click Menu, and Refresh which is not in the Operation Tool Bar (see Operation Tool Bar
(see page 17)).

Though it is not displayed in the Developer Studio interface, the main tool used to perform these
operations is the Right-Click menu, and is accessed by right clicking the mouse over an object or
folder.

Most common operations of the Developer Studio can be performed using any one of the three
options. Only those functions that are available for the object selected will appear in the Right-
Click menu.

The available options are described briefly in Operation Tool Bar (see page 17); some of the
specific functions are discussed in Developer Studio Functions (see page 33).

2.1.3 T OOL B ARS

The Tool bars in the Developer Studio provide tools to perform several tasks. There are four Tool
bars: Standard, Operation, Browse, and Windows. Each of the Tool bars and the button functions
are described below. See Right-Click & Operation Pull-Down Menu, Operation Tool Bar (see
page 16) for a description of the Operation Tool Bar.

Another type of Tool Bar, the WorkPad Tool Bar, can be found at the bottom right hand side of the
screen just above the WorkPad Window. The WorkPad Tool Bar is described at the end of this
subsection.

STANDARD TOOL BAR

Standard Tool Bar Buttons

Button Description

Print Setup — changes the printer and print options.

Print — prints the active document.

Undo — undoes the last action.

Cut — cuts the selection to the clipboard.

Copy — copies the selection to the clipboard.

Paste — pastes the clipboard contents.

16 OW240_60
 2.1 Developer Studio Components

Button Description

Help — displays the online help.

About (About Ovation DevStudio) — displays program

information, version number and copyright.

OPERATION TOOL BAR

Operation Tool Bar Items, Right-Click Menu, Operation Pull Down Menu

Menu Item Button # Description (see Developer Studio Functions (see page
33) for more information)

Insert New Inserts a new object in the hierarchy.

Open Opens the selected object for editing.

Foundation Opens the selected item to engineer/Configure.

Fieldbus
Engineer
GE Genius Opens the selected item to engineer/Configure.
Engineering
Delete Deletes/moves the selected item(s) to the TrashCan
folder.
Purge Permanently deletes the selected item(s) from the
TrashCan folder.

Undelete Restores the previously deleted item from the TrashCan

to its previous location in the hardware hierarchy.

Search Searches the database for objects that match specified

criteria.

Where Used Searches the database to find where an object is used by

another object in the system.

Find Quick name search for items in the database.

Map Remote Allows the connection to and operation of a remote

System system for engineering the system via the Developer
Studio.
Disconnect Disconnects the Ovation Developer Studio from the
Remote System remotely mapped system.

OW240_60 17
2.1 Developer Studio Components

Menu Item Button # Description (see Developer Studio Functions (see page
33) for more information)

Compile Compiles the selected diagram/macro or folder of

diagram/macros.

Control Options Opens Control Builder options dialog box. (See Ovation
Control Builder User Guide.)
Backup/Restore Used to backup and restore the system information. (See
Ovation Installation Manual)

Consistency Performs a consistency check at the selected hierarchy

Checks location.

Load Loads database and control contents to the specified

Ovation target drop.

Download Downloads configuration and diagram files to one or more

specified Ovation target drops.

Reconcile Reconciles the database against a specified Ovation

target drop.

Coefficient Calc. Automatically calculates analog conversion coefficients.

Restore Online Controller Restore Mode - Reload mismatched

controllers to a prior matched state (if the system is
configured for Restore Mode).
Clear Clears application data (originated and received point's
lists and control information) from the specified Ovation
target drop.
Reboot Reboots the selected Ovation drop.

Import Imports objects into the database (context sensitive on

the types of objects imported).

Export Exports the selected item from the database.

Refresh Refreshes the hierarchy (Not in the Operation Tool Bar).

Allow Docking None Places current window in one fixed position (Only in the
Right-Click Menu).
Hide None Closes current window (Only in the Right-Click Menu).

Note: See to Developer Studio Components (see page 12) for a description of the Operation
Tool Bar.

18 OW240_60
 2.1 Developer Studio Components

BROWSE TOOL BAR

Browse Tool Bar Buttons

Button Description

Expand Child — shows all child items of a selected item.

Collapse Child — closes all child folders of a selected item.

Expand All Items — shows all items up to the leaf nodes.

Collapse All — closes all folders and shows only the root node.

Refresh — refreshes the hierarchy.

WINDOW TOOL BAR

Window Tool Bar Buttons

Button Description

Close Window — closes the window.

Close All Windows — closes all the open windows.

Next Window — activates the next unlocked window.

Previous Window — activates the previous unlocked window.

Cascade — arranges the windows as overlapping tiles.

Tile Horizontally — arranges the windows as horizontal, non-overlapping

tiles.
Tile Vertically — arranges the windows as vertical, non-overlapping tiles.

OVATION SYSTEMS TOOL BAR

The Ovation Systems tool bar sits of top of the Ovation Window and displays the system to which
the Developer Studio is currently mapped. (See Ovation Multiple Networks User Guide.)

Tool bars can be added or removed from the Developer Studio so that the screen can be
customized. To add, move or remove tool bars or buttons, follow these procedures.

OW240_60 19
2.1 Developer Studio Components

TO CUSTOMIZE THE TOOL BAR

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Select View from the Menu bar and choose Customize Toolbar. The Customize dialog box
appears (see Typical Dialog Box (see page 30)).
4. Select the tool bars that you want to appear in the Developer Studio tool bar, and de-select
the tool bars you want to remove.
5. You can select or de-select Show Tooltips (gives a description of the tools when the mouse
hovers over the icon), Cool Look (with Cool Look checked the tool bars are smooth,
unchecked the buttons on the tool bars are raised), or choose small or large buttons.
6. Selecting the New button allows the creation of a new tool bar.
7. In order to add, delete or move buttons on the tool bars, select the Commands tab.
8. Press Apply (if changes were made), then press the OK. The Tool bars that you selected
appear in the Studio, while any other requested changes are also performed.

2.1.4 O VERVIEW W INDOW V IEW B ARS

The Overview Window provides the Hardware, Defaults and TrashCan View Bars.
ƒ Hardware View Bar (see page 21) - contains the System Tree hierarchical file structure view
of the database.
ƒ Defaults View Bar (see page 23) - reveals a file structure in which you set defaults for point
types and I/O Devices.
ƒ TrashCan View Bar (see page 25) - behaves much like the Windows Recycle Bin.

20 OW240_60
 2.1 Developer Studio Components

HARDWARE VIEW BAR

The Hardware view bar provides a hierarchical file structure view of the database. This view is
referred to as the System Tree. The highest level in the System Tree is the system, followed by
the Network, Unit, Drop and Point. Within the Hardware view bar, you can create new systems,
import existing systems using the Backup/Restore Tool, export files, plus configure and edit
existing attributes of a system.

Figure 3: Developer Studio Hardware View Bar

OW240_60 21
2.1 Developer Studio Components

Note: The term “Expand the System Tree” refers to opening a folder to reveal more folders, and
then opening one of those folders. To open a folder, select the plus sign in the box to the right of
the folder. Other folders or objects will open under the original folder, and the box will then
contain a minus sign. By expanding into the file structure of the Hardware view bar, you are able
to configure every aspect of the system down to the point level.

See The Developer Studio System Tree (see page 6) for additional information about the
System Tree that is illustrated in the Hardware view bar.

22 OW240_60
 2.1 Developer Studio Components

DEFAULTS VIEW BAR

The Defaults view bar reveals a file structure in which you set defaults for point types and I/O
Devices.

The Defaults Bar provides a tool to create default settings for certain object types. By setting point
defaults, each object created in the Hardware Bar will initially possess the attributes or values
established as a default for that object type. This saves time when creating multiple points with
similar characteristics.

Establishing defaults for objects such as points can save considerable time when creating points.
By eliminating the need to enter repetitive information for each point of that type, you can focus on
the unique settings of the specific point. Some examples of point fields that can be set as defaults
are:
ƒ Description
ƒ Characteristics
ƒ Min/Max scale
ƒ Number of Digits displayed
ƒ Security Groups
Plus any additional configurable characteristics common to points of a certain type.

By using the tools in the Defaults view bar, you are able to pass on point characteristics instead of
entering the same information repeatedly for each point.

Figure 4: Defaults View Bar

Not all attributes can be set as defaults. Information that is drop or unit specific cannot be set as a
default. Additionally, all information set as a default can be overwritten when an object is created.

OW240_60 23
2.1 Developer Studio Components

TYPES OF DEFAULTS

There are 13 Default Point Types:

ƒ Default Analog Point
ƒ Default Deluxe Analog Point
ƒ Default Digital Point
ƒ Default Deluxe Digital Point
ƒ Default Packed Point
ƒ Default Deluxe Packed Point
ƒ Default Packed Digital Point
ƒ Default Algorithm Point
ƒ Default Drop Point
ƒ Default Module Point
ƒ Default Node Point
ƒ Default Remote I/O Node (under Remote Ovation I/O), Used by Node objects.
ƒ Default Remote Q-Line I/O Node (under Remote Q-Line I/O), Used by Node objects.

24 OW240_60
 2.1 Developer Studio Components

TRASHCAN VIEW BAR

The TrashCan view bar in the Developer Studio behaves much like the Windows Recycle Bin. All
files and folders deleted from the Hardware or Defaults folders are moved to the TrashCan folder
where they are stored. You can open the deleted folders, undelete them and return them to their
original folder, or purge the files from the system entirely.

Notice that the file hierarchy in the TrashCan view bar contains placeholders for Systems, Users,
Networks, Units, Drops, and Points.

Not all objects deleted from the Hardware view bar will be stored in the TrashCan folder. Only
objects in the Hardware view bar with corresponding placeholders in the TrashCan view bar can
be moved to the TrashCan.

For example, if you delete a unit from the Hardware view bar, its folder and all of its contents will
moved from the Hardware view bar to the TrashCan view bar and placed in the Units placeholder.
However, if you delete only a Configuration object from the Hardware view bar, that record will
not be moved to the TrashCan view bar.

Figure 5: Trash Can View Bar

OW240_60 25
2.1 Developer Studio Components

DELETIONS FROM THE TRASHCAN VIEW BAR

ƒ A Systems folder can be moved from the Hardware view bar and placed in the TrashCan
view bar. When you remove the Systems folder, all of its subfolders are moved with it.
ƒ A Networks folder can be moved from the Hardware view bar to the TrashCan view bar.
When you remove the Networks folder, all of its subfolders are moved with it.
ƒ A Units folder can be moved from the Hardware view bar to the TrashCan view bar. When
you remove the Units folder, all of its subfolders are moved with it.
ƒ A Drops folder can be moved from the Hardware view bar to the TrashCan view bar. When
you remove the Drops folder, all of its subfolders are moved with it.
ƒ You can also move individual point objects, graphics, and graphic macros to the Trashcan
view bar.
All points deleted from the Hardware view bar are listed under the Points placeholder in the
TrashCan, regardless of the drop folder from which the points were removed. If a point is
undeleted and returned to the Hardware view bar, it will be returned to its original drop.

WORKPAD WINDOW

The WorkPad Window displays selectable folders and objects of the highlighted tree object.

WorkPad View Buttons

Button Description

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.

26 OW240_60
S E C T I O N 3

HOW DO I CONFIGURE OBJECTS?

Configuration is the process of entering data into the Ovation system, usually through a user
interface window, to specify a drop or function. Configuration is the main function of the Developer
Studio. The Studio is involved in the configuration of Controllers, Operator Stations, Fieldbus,
Simulators, Security, etc.

Configuration can be accomplished in several ways, the Operation Tool bar or the Operation pull
down menu, or the Right-Click menu. The easiest way to open a dialog box is by right clicking of
one of the objects in the System Tree and selecting Open. All topics are accessed through the
system tree in the Hardware View Bar (See What is the Developer Studio System Tree? and
Right-Click & Operation Pull-Down Menu, Operation Tool Bar (see page 16)). One of the
biggest advantages to using the Right-Click menu is that it only displays functions that are
available for the folder or object being worked on.

The procedures found in the configuration topics that start with "To ..." will often give the system
tree path taken to get to the proper folder. To open a folder, select on the plus sign in the box to
the right of the folder. Other folders or objects will open under the original folder; the box will then
contain a minus sign. By expanding into the file structure of the Hardware view bar, you are able
to configure every aspect of the system down to and including the point level. The procedure will
then describe the rest of the steps needed to configure a particular object.

In This Section

To Insert New or Open a Dialog Box ................................................................... 28

To Insert New or Open a Dialog Box in the WorkPad ......................................... 29
Typical Dialog Box ............................................................................................... 30
Typical Wizard Dialog Box ................................................................................... 31

OW240_60 27
3.1 To Insert New or Open a Dialog Box

3.1 TO INSERT NEW OR OPEN A DIALOG BOX

A procedure (setting up the controller parameters, in this case) will usually start out like the
following:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the Controller folder:
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Configuration]
Controller
4. Right click on the Controller folder and select Open from the resulting pop-up menu.

Figure 6: Right Clicking on the Controller

28 OW240_60
 3.2 To Insert New or Open a Dialog Box in the WorkPad

3.2 TO INSERT NEW OR OPEN A DIALOG BOX IN THE WORKPAD

When working with an object in the WorkPad Window, the procedure is similar to, To Insert New
or Open a Dialog Box (see page 28):

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the Control Tasks folder:
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Configuration]
Control
Control Tasks
4. Select the Control Tasks folder and observe Control Task 1 and Control Task 2 listed in the
WorkPad Window.
5. Right click on the Control Task folder and select Open from the resulting pop-up menu.

Figure 7: Right Clicking on the Control Tasks

6. Select the Open Icon (or Insert New) to bring up the Dialog Box.

OW240_60 29
3.3 Typical Dialog Box

3.3 TYPICAL DIALOG BOX

Dialog boxes are functional windows in which operations are performed. Dialog boxes can contain
fields, tabs, buttons, drop down lists, and check boxes.

The title bar is at the top of the dialog box and describes the function of the box. The window is
the workspace in the dialog box and contains the fields of that dialog box, which can contain
information gathered by other information input or requires data entry. The areas shaded in gray
are those that have been automatically determined by previous information input, they are
provided to give information and cannot be changed in this dialog box.

Selecting the tabs at the bottom of the dialog box opens new dialog windows within the box. The
tool buttons on the right side of the dialog box provides the functionality of the dialog box.

Figure 8: Typical Dialog Box

Dialog Box Tool Buttons

Button Description

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.

30 OW240_60
 3.4 Typical Wizard Dialog Box

Button Description

Help Displays information about the Dialog Box as well as help filling in the
fields.

3.4 TYPICAL WIZARD DIALOG BOX

The Wizard dialog box is a special case of the dialog box. Like the dialog box operations are
performed in a functional window. Wizard dialog boxes can contain fields, buttons, drop down
lists, and check boxes, and are used to "build" dialog boxes for a specific purpose.

The Wizard dialog box is generally used to provide the minimum required input for the particular
object being inserted.

The title bar, at the top of the dialog box, indicates the type of dialog box to be built. The tool
buttons on the bottom of the box provides the functionality of the Wizard dialog box.

Figure 9: Typical Wizard Dialog Box

Dialog Box Tool Buttons

Button Description

Back Only used in Wizards with more than one step.

Next Only used in Wizards with more than one step.

OW240_60 31
3.4 Typical Wizard Dialog Box

Button Description

Finish Accepts the input made by the user, closes the Wizard, and
opens a dialog box containing all the required object attributes.
Cancel Cancels/aborts the insert operation.

32 OW240_60
S E C T I O N 4

DEVELOPER STUDIO FUNCTIONS

In This Section

Backup/Restore.................................................................................................... 33
Clear Function ...................................................................................................... 33
Coefficient Calculation ......................................................................................... 34
Data Validation ..................................................................................................... 36
Consistency Checking.......................................................................................... 37
Download Function .............................................................................................. 38
Delete Function .................................................................................................... 42
Dynamic Status Feature....................................................................................... 43
Export Function .................................................................................................... 45
Find Function........................................................................................................ 45
Import Function .................................................................................................... 46
Load Function ...................................................................................................... 47
Purge Function ..................................................................................................... 48
Reboot Function................................................................................................... 48
Reconcile Function............................................................................................... 49
Search Function ................................................................................................... 53
Undelete Function ................................................................................................ 59
Where Used Function .......................................................................................... 60
Ovation Developer Studio - Alert.......................................................................... 63

4.1 B A C K U P /R E S T O R E
This utility backs up and restores the Ovation Database server. This back up is also sufficient for
systems with Foundation Fieldbus. However, this utility does not back up data stored for the
Ovation Fieldbus Engineering Server. Once the backup image is restored, Foundation Fieldbus
data must be re-exported from the Ovation database and imported into the Ovation Fieldbus
Engineering Server (See Planning and Installing Your Ovation System.)

4.2 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 Drop level. Upon
completion of the clear process, the drop will automatically reboot.

OW240_60 33
4.3 Coefficient Calculation

4.2.1 T O C LEAR A PPLICATION I NFORMATION

Use the following procedure to clear the application information from the drop:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the Drop level.
{Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click on the appropriate Drops folder and select Clear.
à If the drop is redundant, the “Select a drop to clear” dialog box appears (similar to
Download Function (see page 39)).
à Select the appropriate target drop and then select Ok.
A confirmation dialog box appears (Similar to reboot). After the action is complete, the
system will automatically reboot and the application information will be cleared from the
drop.

For specific information regarding loading application information to a Controller drop. (See
Ovation Controller User Guide.)

4.3 COEFFICIENT CALCULATION

The coefficient calculation 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 will be generated creating 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 if it is in degrees F or C. The values of the 8 conversion
coefficients will be inserted. In addition, the Thermocouple will be linked 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, and the interface
will calculate all coefficients.

34 OW240_60
 4.3 Coefficient Calculation

4.3.1 T O R UN A C OEFFICIENT C ALCULATION

Use the following procedure to run a coefficient calculation:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the System folder, Units folder,
or Drop folder level.
{Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click on the desired folder and select Coefficient Calculation from the right click pop-
up menu.

Note: The Right-Click menu will only display objects that are applicable for that drop.

5. The software will perform the requested function and will bring up a list of any points that it
could not calculate in the top of the window, if any.

Figure 10: Coefficient Calculation Dialog

OW240_60 35
4.4 Data Validation

6. Double left click on an Object, which will open a Drop dialog box.
7. Go to the Instrumentation tab on the Drops Dialog box, fill in the missing information indicated
in the Reason box, and press Apply or Ok.
8. Points which have sufficient information to perform the calculation will have their conversion
coefficient fields compared (actual vs. calculated). The differences will be shown in the lower
half of the U.I.

Figure 11: One Drop Calculated

9. If the user wishes to revert from the current values to the calculated values, they must
highlight the desired fields (or point folder to take all values) and press Apply or Ok.

4.4 DATA VALIDATION

The Developer Studio checks user input and provides feedback if it detects inconsistent data. The
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 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 (i.e., the
Apply or Ok button is pressed).

36 OW240_60
 4.5 Consistency Checking

4.5 CONSISTENCY CHECKING

Before the system runs a load or download function, Consistency Checking runs automatically to
make sure that the setup agrees with a predetermined set of rules. When a check is run by the
system, and errors are detected, a dialog box will be displayed giving the user an opportunity to
open up the report. A Consistency Check can also be run manually.

4.5.1 T O R UN C ONSISTENCY C HECKING

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Right click on the desired object and choose consistency check.
4. A consistency check will be performed.

Figure 12: Consistency Check

5. If there are errors shown in the "Error(s)" column got the "Action" pull-down list and select
View Details if you would like more information about the errors.

OW240_60 37
4.6 Download Function

4.5.2 C ONSISTENCY C HECKING R EPORT

Figure 13: Consistency Checking Report

The Group and Object boxes allow those dialog boxes to be opened for inspection and any
corrections needed.

4.6 DOWNLOAD FUNCTION

When changes are made to configuration diagrams, audio files, bitmap files, and/or Controller
software, these changes must be downloaded to the applicable drop(s) using the Download
Function.

Note: If the target has any consistency check errors, the download operation will be aborted.
The Drop must be rebooted (Reboot Function (see page 48)) in order for the configuration
changes to take effect. No Reboot is necessary if items like graphics are downloaded.

38 OW240_60
 4.6 Download Function

4.6.1 T O D OWNLOAD I NFORMATION

Use the following procedure to download the changes to the drop of your choice:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the Drop level.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
4. Right click on the folder of the drop where you wish to view the changes and select
Download from the pop-up menu. The Right-Click menu will only display objects that are
applicable for that drop.
5. Redundant vs. Non-Redundant Drops.
à If this is a non-redundant drop, go to Step #6.
à If this is a redundant drop, the “Select a drop to download” will appear. Select the drop to
download.
6. The Download Preview window appears. The Download Preview window 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 14: Download Preview Dialog

OW240_60 39
4.6 Download Function

7. If the information in the Download Preview Dialog is acceptable, select the Download check
box if it is deselected, and select the Ok button. This will download the changes. When both
Download and Reboot are selected, the drop will download the changes and the machine will
restart.
8. Downloading is now complete.

Download Preview Window Options

Item Description

Select All/ Use the check box to the left of Query Results to select all or clear all.
Clear All
Download When checked, this action downloads all of the selected previewed files
after pressing the Ok button.
Reboot When checked, this action shuts down and then restarts the drop after
the Ok button is selected.
Abort Aborts the download process and returns to the Ovation Developer
Studio without executing any commands.
Ok Executes the settings and closes the window.
Skip to Next This button advances to the next drop for file preview. (The current drop
Drop is not downloaded.)

4.6.2 D OWNLOADING C ONFIGURATION C HANGES TO M ULTIPLE D ROPS

It is possible to download configuration changes to multiple drops. Configuration changes can be

downloaded to multiple drops at the System, Network or Unit level in the Studio System Tree.
ƒ A download at the System level will allow the user to select any of the drops under the system
to be downloaded.
ƒ A download at the Network level will allow the user to select all of the drops under the network
to be downloaded.
ƒ A download at the Unit level allows the user to select all of the drops under the unit to be
downloaded.

40 OW240_60
 4.6 Download Function

TO DOWNLOAD CONFIGURATION CHANGES TO MULTIPLE DROPS

To download configuration changes to multiple drops using the following procedure:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access Developer Studio and expand the system tree to:
{Systems] (or [Network] or [Unit]).
Unique System Name (or Network or Unit name).
4. Right click on the System Name folder (or appropriate level such as Network or Unit).
5. Select Download from the right-click menu. A Drop Preview dialog box appears (looks like
the dialog box in To Download Information (see page 39), without the options).

Note: The Drop Preview window contains a list of drops that fall under the selected level in the
hierarchy. For example, if you choose to download from the System level, all drops in the
System will appear in the Drop Preview window. If you choose to download from the Unit Level,
all drops under that Unit will appear in the Drop Preview window.

Figure 15: Download Multiple Drops

OW240_60 41
4.7 Delete Function

6. Select the Drops you would like to download by placing a check in the box next to the Drop
number. You may select all drops by choosing Select All or you may deselect all drops by
choosing Clear All.
7. Select Ok to download these Drops. You may abort the download by choosing Abort in the
Drop Preview window.
8. If the information in the Download Preview Dialog is acceptable, select the Download check
box if it is deselected, and select the Ok button. This will download the changes. When both
Download and Reboot are selected, the drop will download the changes and the machine will
restart.

Note: Use the Reboot function (Reboot Function (see page 48)) for the configuration changes
to take effect. No Reboot is necessary if things like graphics are downloaded.

9. Downloading is now complete.

Download Preview Window Options

Item Description

Select All/ Use the check box to the left of Query Results to select all or clear all.
Clear All
Download When checked, this action downloads all of the selected previewed files
after pressing the Ok button.
Ok Executes the settings and closes the window.
Skip to Next This button advances to the next drop for file preview. (The current drop is
Drop not downloaded.)

Note: Process Diagrams downloads can also be done by right clicking on the Diagram folder at
any level in the Studio System Tree and selecting Download. This will download the changed
process diagrams to multiple drops. Changed process diagrams must be downloaded in order to
be viewed in the Process Diagrams System. (See Ovation Operator Station User Guide.)

4.7 DELETE FUNCTION

Deleting an object from the Developer Studio’s Hardware view bar removes it from the System
Tree. As discussed in TrashCan View Bar (see page 25), certain objects can be restored from
the TrashCan view bar to their original location.

Note: If an object is being used by something that will remain in the System Tree, the
references must be removed before the delete operation is permitted. (See Where Used
operations for assistance in determining reference information.)

42 OW240_60
 4.8 Dynamic Status Feature

4.7.1 T O U SE THE D ELETE F UNCTION

To delete an object from the Hardware view bar, use the following procedures:

Note: The deletion of control sheets is handled slightly different. The database object, the
control builder files and the default points associated with the sheet are permanently deleted
(i.e. purged). In addition, if a higher level object (drop, unit, network, or system) is deleted, all
control sheet items under it will be purged.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the Hardware view bar, right click the object to be deleted and select Delete. The “Are You
Sure...” dialog box appears.
4. Select Yes to delete the object, or select No to cancel the operation.

Note: After deleting a point, you must load (Load Function (see page 47)) before the deletion
is recognized by the system.

4.8 DYNAMIC STATUS FEATURE

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 are:
ƒ Ovation points
ƒ Holding registers
ƒ Control sheets

OW240_60 43
4.8 Dynamic Status Feature

4.8.1 T O U SE D YNAMIC S TATUS F EATURES

Perform the following to use the Dynamic Status feature:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the desired drops level.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
4. Locate the objects that need attention as indicated by the Dynamic Status markers (graphical
indication (flag)).
5. Select the down arrow that appears after the object name. The Ovation Diagnostics window
that is applicable for that object will appear.

Figure 16: Ovation Diagnostics Window

6. Diagnostic information about the object is provided and recommended actions are suggested.
Perform the appropriate actions and the Dynamic Status indicator will disappear.

44 OW240_60
 4.9 Export Function

4.9 EXPORT FUNCTION

The Developer Studio Export function allows you to export Control Sheets to a user-defined
location for later use. This function is used for exporting selected sheets at the Control Sheet
level.

Note: In order to export sheets at the Drop level, use the Control Options item from the Right-
select menu.
The Export function is also applicable for Fieldbus Gateway objects. In this case, the function
produces a configuration file that the Ovation Fieldbus Engineering Software utilizes.

4.9.1 T O U SE THE E XPORT F UNCTION

Use the following procedure to export Control Sheets:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Ovation Developer Studio and select the desired sheets.
4. Select the Export item from the Right-click menu. The Ovation Export Control window
appears.
5. Perform the necessary configuration and exporting (See Ovation Control Builder User Guide.)

4.10 F I N D F U N C T I O N
The Find function provides a tool to search for objects by name, using wild cards to broaden the
search.

Note: The Find function is case sensitive.

4.10.1 T O U SE THE F IND F EATURE

Use this procedure to find objects in the Ovation system.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Right click a folder at the level you want to begin searching for an object. (Because the search
was initiated in the Networks folder at the System level, all objects that fall below the Ovation
system folder in the file structure are available for query.) The Find: All Objects dialog box
appears.
4. In the "Find what" field, enter the name, or part of the name of an object 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 object.
à Use the _ (underscore) to match exactly one character.

OW240_60 45
4.11 Import Function

à 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 Find anywhere in database to locate the object wherever it occurs in the entire
database or select Find in <current folder> to locate occurrences of the object beneath the
folder where you began the search.
6. Select Find Now and the fields are populated with objects found.

Figure 17: Find Dialog Box

Note: The objects themselves can be opened by checking the box adjacent to the object name
and selecting the Open button. When the Find Results dialog box is open, no other windows or
dialog boxes can be accessed.

4.11 I M P O R T F U N C T I O N
The Developer Studio Import function allows you to import Graphic Sheets, Control Sheets, Audio
files, and Bitmap files. Import is context sensitive so the type of import performed is based on the
folder where the import is initiated.

46 OW240_60
 4.12 Load Function

4.11.1 T O U SE THE I MPORT F UNCTION

For example, use the following procedure to import graphics into the database.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Right click upon the folder into which the files will be imported and select Import. The Import
dialog box appears.
4. Fill in the necessary fields and select Import:
à Specific information regarding importing Audio files and Bitmaps for alarms. (See
Configuring Your Ovation Operator Station.)
à Specific information regarding importing Control Sheets. (See Ovation Control Builder
User Guide.)
à Specific information regarding importing Graphics Sheets. (See Ovation Graphics
Builder.)

4.12 L O A D F U N C T I O N
The load function is used to load Ovation point and control data to an Ovation drop. The load
function is performed at the Drop level. The target drop will have all the information data
necessary to perform its application.

Note: If the target has any consistency check errors, the load operation will be aborted.

4.12.1 T O L OAD A PPLICATION I NFORMATION

Use the following procedure to load the application information to the drop:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the Drop level.
{Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click on the appropriate Drops folder, and select Load to perform the load function.
à If the drop is redundant, the “Select a drop to load” dialog box appears (similar to
Download Function (see page 39)).
à Select the appropriate target drop and then select Ok.

OW240_60 47
4.13 Purge Function

For specific information regarding loading application information to a Controller drop, (See
Ovation Controller User Guide.)

4.13 P U R G E F U N C T I O N
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.13.1 T O U SE THE P URGE F UNCTION

To purge objects from the TrashCan view bar, use the following procedure.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the TrashCan Function Bar, the TrashCan Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the TrashCan view bar, right click the object to be deleted and select Purge. The “Are You
Sure...” dialog box appears.
4. Select Yes to permanently delete the object from the system, or select No to cancel the
operation.

4.14 R E B O O T F U N C T I O N
In most cases, the Reboot command should be executed immediately following the completion of
any Download command involving configuration changes. This may not always be completely
necessary, but it is a safe and recommended practice.

48 OW240_60
 4.15 Reconcile Function

4.14.1 T O R EBOOT

Use the following procedure to reboot a drop:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the Drop level.
{Systems ]
Unique System Name
[Networks
Unique Network Name
[Units
Unique Unit Name
[Drops
Unique Drops Name
4. Right click on the folder of the drop you want to reboot and select Reboot from the right-click
pop-up menu. The Right-Click menu will only display objects that are applicable for that drop.

Note: You can also reboot the drop by checking Reboot in the Download Preview window as
described in Download Function (see page 39).

5. Redundant and Non-Redundant Drops:

à For non-redundant Drop configurations, skip to Step #6.
à For redundant Drop configurations, the “Select a drop to reboot” dialog box appears
(similar to Download Function (see page 39)), select the drop to reboot and select Ok.
6. A confirmation dialog box appears.
7. Select Yes to close the window and execute the reboot process.

Figure 18: Reboot Drop Confirmation Box

4.15 R E C O N C I L E F U N C T I O N
The Reconcile function enables you to compare the database contents of Ovation points with
drop contents in order to capture changes made in the on-line system. Examples of items that can
be reconciled include tuned algorithms and modified alarm limits.

OW240_60 49
4.15 Reconcile Function

4.15.1 R ECONCILED F IELDS FOR A NALOG AND D ELUXE A NALOG F IELDS

The table below contains Analog and Deluxe Analog Points reconcilable fields. (See Ovation
Algorithms Reference Manual.)

Analog and Deluxe Analog Points Reconciled Fields

Analog Points Deluxe Analog Points Deluxe Analog Points

1V Conversion Coefficient 1V Conversion Coefficient #1 6S Low Alarm Limit #1 - Plant

#1 3
2V Conversion Coefficient 2V Conversion Coefficient #2 7S Low Alarm Limit #2 - Plant
#2 3
3V Conversion Coefficient 3V Conversion Coefficient #3 8S Low Alarm Limit #3 - Plant
#3 3
4V Conversion Coefficient 4V Conversion Coefficient #4 9S Low Alarm Limit #4 - Plant
#4 3
5V Conversion Coefficient 5V Conversion Coefficient #5 5S High Alarm Inc. Limit -
#5 Plant 3
6V Conversion Coefficient 6V Conversion Coefficient #6 0S Low Alarm Inc. Limit -
#6 Plant 3
7V Conversion Coefficient 7V Conversion Coefficient #7 1Y High Alarm Limit #1 - Plant
#7 4
8V Conversion Coefficient 8V Conversion Coefficient #8 2T High Alarm Limit #2 - Plant
#8 4
HL High Alarm Limit #1 UH High User Defined Alarm 3T High Alarm Limit #3 - Plant
Limit 4
ZH High Alarm Limit #2 UL Low User Defined Alarm 4T High Alarm Limit #4 - Plant
Limit 4
3Y High Alarm Limit #3 1Q High Alarm Limit #1 - Plant 6T Low Alarm Limit #1 - Plant
1 4
4Y High Alarm Limit #4 2Q High Alarm Limit #2 - Plant 7T Low Alarm Limit #2 - Plant
1 4
UH High User Defined 3Q High Alarm Limit #3 - Plant 8T Low Alarm Limit #3 - Plant
Alarm Limit 1 4
LL Low Alarm Limit #1 4Q High Alarm Limit #4 - Plant 9T Low Alarm Limit #4 - Plant
1 4
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

50 OW240_60
 4.15 Reconcile Function

Analog Points Deluxe Analog Points Deluxe Analog Points

UL Low User Defined 9Q Low Alarm Limit #4 - Plant 1 2U High Alarm Limit #2 - Plant
Alarm Limit 5
ZI High Alarm Incremental 5Q High Alarm Inc Limit - Plant 3U High Alarm Limit #3 - Plant
Limit 1 5
ZM Low Alarm Incremental 0Q Low Alarm Inc. Limit- Plant 4U High Alarm Limit #4 - Plant
Limit Mode 1 5
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
1R High Alarm Limit #1 - Plant 8U Low Alarm Limit #3 - Plant
2 5
2R High Alarm Limit #2 - Plant 9U Low Alarm Limit #4 - Plant
2 5
3R High Alarm Limit #3 - Plant 5U High Alarm Inc. Limit -
2 Plant 5
4R High Alarm Limit #4 - Plant 0U Low Alarm Inc. Limit -
2 Plant 5
6R Low Alarm Limit #1 - Plant 2 1X High Alarm Limit #1 - Plant
6
7R Low Alarm Limit #2 - Plant 2 2X High Alarm Limit #2 - Plant
6
8R Low Alarm Limit #3 - Plant 2 3X High Alarm Limit #3 - Plant
6
9R Low Alarm Limit #4 - Plant 2 4X High Alarm Limit #4 - Plant
6
5R High Alarm Inc. Limit - Plant 6X Low Alarm Limit #1 - Plant
2 6
0R Low Alarm Inc. Limit - Plant 7X Low Alarm Limit #2 - Plant
2 6
1S High Alarm Limit #1 - Plant 8X Low Alarm Limit #3 - Plant
3 6
2S High Alarm Limit #2 - Plant 9X Low Alarm Limit #4 - Plant
3 6
3P High Alarm Limit #3 - Plant 5X High Alarm Inc. Limit -
3 Plant 6
4S High Alarm Limit #4 - Plant 0X Low Alarm Inc. Limit -
3 Plant 6

OW240_60 51
4.15 Reconcile Function

4.15.2 T O R ECONCILE O RIGINATED P OINTS AND C ONTROLLER D ROP C HANGES

Use the following procedure to reconcile the originated points and Controller drop changes to the
drop of your choice:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Developer Studio and expand the system tree to the Drop level.
{Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click on the appropriate Drops folder and select Reconcile.
If the drop is redundant, the “Select a drop to reconcile” dialog box appears (similar to
Download Function (see page 39)). Select the appropriate target drop and then select Ok.

Communications are established at the target drop and the Reconcile dialog box appears.

Figure 19: Reconcile Dialog Box

52 OW240_60
 4.16 Search Function

5. Check for points listed in the "item(s) not compared" field. Points that cannot be reconciled
and the reasons are listed in this field. A common reason would be that the point has been
deleted from the database, but is still in the controller (i.e. the "delete" has not yet been
loaded to the controller)..
6. Check for items that have differences and that can be reconciled listed in the "difference(s)
found" field.
7. Expanding the point folder reveals the values of the Point field(s) that are different between
the target drop and the database. To open the point itself, select "Open Item..." on the right
click menu over the applicable point folder or field.
8. Highlight the points or the specific field(s) of points that need to be uploaded from the target to
the database.
9. Select Ok to copy the target’s highlighted point/field values to the database (reconcile) and
close the dialog box, or select Apply to reconcile the items, re-query the database and target
drop, then refresh the dialog box.

4.16 S E A R C H F U N C T I O N
The Search function allows you to search for objects 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 objects.
ƒ Perform global/mass changes.
ƒ Query the database and sort objects according to a user-specified criteria.
ƒ View all attributes of the object(s).
All objects in the system can be searched. Searches are performed downward in the tree
structure. A search at the unit level will query the database for information only about that unit and
drops and points associated with that unit. The search will not query other units or networks in the
system. If the search is performed at the system level, all networks and units in the system will be
queried.

Note: The Search function is case sensitive.

OW240_60 53
4.16 Search Function

4.16.1 T O U SE THE S EARCH F UNCTION - O BJECT S ELECTION

Use the following procedure to search for objects in the database:

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.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Right click on a folder at the level you want to begin the search. Because the search was
initiated at the Ovation system folder, all applicable objects that fall below the Ovation system
folder in the tree structure are available for query. The Search Options Wizard - (Step 1/2)
appears.

Figure 20: Search Options Wizard Step 1/2

4. Choose the type of object to search for from the menu.

54 OW240_60
 4.16 Search Function

4.16.2 T O U SE THE S EARCH F UNCTION - I TEM S ELECTION

1. Select Next, the Search Options Wizard - (Step 2/2) appears.

Figure 21: Search Options Wizard Step 2

2. Select the type of search to perform:

à Find all items searches the database for all instances of the object and lists them in the
Search: Item: dialog box.
à Find specific items using search clauses, allows setting up search criteria such as
limits and restrictions using the Search dialog box.

OW240_60 55
4.16 Search Function

4.16.3 T O U SE THE S EARCH F UNCTION - N ARROW S EARCH

1. Select Next, the Search dialog box appears.

Figure 22: Search Dialog Box

Search Dialog Box

Item Description

Search Window Displays the search criteria selected.

Search Criteria Area where a limiting clause is created.
Window
Attribute Pull-down menu that contains attributes of the object to be searched.
Condition Pull-down menu that contains conditional text used to create a limiting
clause.
Value Enter the name, location, etc. used to search for the object.
Add After specifying a limiting clause in the Search Criteria window, use
this button to add it to the Search window and set it as the criteria with
which to search.
Delete Removes the selected limiting clause from the Search window.

56 OW240_60
 4.16 Search Function

2. 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.
3. Select the attribute from the pull-down menu.
4. Select the condition from the pull-down menu.
5. Type a value in the Value field.
6. Select Add to add the limiting clause to the Search window.
7. Add additional clauses to limit or restrict the search, if necessary.

Note: Each of the limiting clauses are implicitly separated by AND operators. In other words, the
list of objects retrieved will be those where <clause1> AND <clause2> AND...<clauseX> are
true.

4.16.4 T O U SE THE S EARCH F UNCTION - R ESULTS

1. Select Ok to perform the search. The Search: dialog box appears.

Figure 23: Search: Dialog Box

Search: Dialog Box

Item Description

item(s) found Indicates how many items were found in the search.

OW240_60 57
4.16 Search Function

Item Description

Object column Lists, by name, the objects found in the search.

Search Again Opens the Search dialog box enabling the user to modify the search
criteria.
Add Column(s) Adds columns that detail attributes of the objects listed in the Object
Column.
Refresh Refreshes the data in the columns.
Column(s)
2. To expand or limit the search, select the Search Again button and the Search dialog box
appears. Review Step 2 of To Use the Search Function - Clauses (see page 56) through
Step 1 of this topic to perform the Search Again option.
3. Select Add Column(s) and the Add Columns dialog box appears.

Note: The available attributes are based on the type of object being searched.

Figure 24: Add Column(s) Dialog Box

58 OW240_60
 4.17 Undelete Function

4. Highlight the columns to add to the Search: Object dialog box and select Ok. The columns
are added to the Search: Object dialog box.

Figure 25: Search: Dialog Box with Additional

Additional functions that can be performed in the Search: dialog box include:

Double click on the object name in the Object column to open the record.
ƒ Make global changes to columns by entering the new information to one cell, and using the
right click to copy the new information and paste it to the entire column.
ƒ Select the Ok button to add any changes made in the Search: dialog box to the database.
ƒ Select a column heading to sort the list alphabetically, based on the selected column.
ƒ Rearrange columns by dragging and dropping the column heading.
ƒ Right click on a column header to display a menu that can be used to delete a column.
ƒ As for all dialog boxes in the Studio, the search results can be printed or saved to a file via the
File menu.

4.17 U N D E L E T E F U N C T I O N
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 make sure 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.

OW240_60 59
4.18 Where Used Function

4.17.1 T O U SE THE U NDELETE F UNCTION

Use the following procedure to restore a deleted item to the Hardware view bar.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Select the TrashCan view bar in the Developer Studio.
4. Right click the object to be restored (to the Hardware view bar) and 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,
or select No to cancel the action.

Note: After restoring a point, load (Load Function (see page 47)) the drop where the point has
been replaced.

4.18 W H E R E U S E D F U N C T I O N
Where Used searches the database and finds all the references to the specified object. If an
object is used in the database, the Where Used feature provides a detailed report of who uses it,
where it is used, and how it is used.

60 OW240_60
 4.18 Where Used Function

4.18.1 T O I NITIATE THE W HERE U SED F UNCTION - O PTIONS

Use the following procedures to find out where objects are used in the Ovation system.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System Tree down to the desired object, and right click on the object then select
Where Used. The Where Used Wizard appears.

Figure 26: Where Used Wizard

The three types of reference searches are:

ƒ "Find all references to ...", Shows all references to the selected object.
ƒ "Find all references to ... and its children, outside of ..." Shows references to the portion of the
system tree including the object and those inside its folder (its children) made by objects
outside this portion of the tree. In other words, you can go to a graphic on a Computer Work
Station and see if it uses any part of a selected object and/or its children.
ƒ "Find all references made by ...", Shows all references made by the object to any other object.

4.18.2 T O I NITIATE THE W HERE U SED F UNCTION - R ESULTS

1. Select one of the following, then select Find Now:
à Select Find all references to DROPXXX.
à Select Find all references to DROPXXX and its children, outside of DROPXXX.
à Select Find all references made by DROPXXX.

OW240_60 61
4.18 Where Used Function

Note: (DROPXXX = the drop # being checked.) The Figure below shows the second choice,
"Find all references to ... and its children...". If either of the other two option are selected, the
dialog box will appear similar, but without the “Who” and “Who Type’ columns.

Figure 27: Where Used - Find All Drop References and its

Where Used Dialog Box Column Description

Column Description

Object Object in System Tree that references the selected item. Select this
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.
Who Selected item or its child that is being referenced. Select this button to
open the item’s configuration dialog box.
Who Type Describes the referenced Who item.

62 OW240_60
 4.19 Ovation Developer Studio - Alert

4.19 O V A T I O N D E V E L O P E R S T U D I O - A L E R T
The message below is a common that may come up when working in the Studio. Something
running in the background may have conflicted with your operation (possibly the function you
were running involved a point that is being used and the alert is false). It is suggested that you try
the function one more time before looking for problems. If the Alert persists, open up and look at
the "Details >>" for helpful information.

Figure 28: Ovation Developer Studio Alert Window

OW240_60 63
S E C T I O N 5

BUILDING A SYSTEM

In This Section

To Insert a System ............................................................................................... 66

To Insert a Network.............................................................................................. 68
To Insert a Unit..................................................................................................... 70
To Insert a Drop ................................................................................................... 71
To Add a Point ..................................................................................................... 72

OW240_60 65
5.1 To Insert a System

5.1 TO INSERT A SYSTEM

Note: Currently, Ovation Studio is limited to one System. However, a remote network can be
processed through the External System Interface.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the System folder.
[Systems]
4. Right click the System object and select Insert New. The "Insert New [Systems] Wizard"
dialog box appears (see Typical Wizard Dialog Box (see page 31)).
5. Type a System Name (of your choice, up to eight characters) in the System Name entry field.
This example uses the name Ovation. Do NOT use the following invalid characters in a
System name: period (.), dollar sign ($), percent sign (%), pound sign (#), at sign (@), and a
space.
6. Select a System Value (of your choice) by selecting the appropriate radio button. At this time,
only one system can exist, but it can be assigned any value.
7. Select Finish and the "New [Systems]" dialog box appears.

Figure 29: System Dialog Box

66 OW240_60
 5.1 To Insert a System

8. Check that the settings are correct in the New Systems dialog box.

System Dialog Box Descriptions

Field Description

System Name Eight character limit. Forced uppercase. Invalid characters are
period (.), dollar sign ($), percent sign (%), pound sign (#), at sign
(@), and space.
System Value Value of your choice.
Database Machine Used internally by Ovation applications to talk to other computers -
for informational purposes only.
Offline Mode Check Box. See Online/Offline Mode (see page 82) (Default - Not
Checked.)
Restore Mode Online Controller Restore Mode - Reload mismatched controllers to
a prior matched state. (Restore Mode Disable, Restore Mode
Enable All Drops, and Restore Mode Enable Redundant Drops.)
(See Ovation Planning and Installing Your Ovation System.)
(Default - Restore Mode Disabled.)
Disable Deluxe Allows systems not using Deluxe Points to hide those folders to
Points reduce screen clutter. Deluxe Points can not be inserted via the
Developer Studio or input operation while this box is checked.
(Default - Not Checked.)
9. Select Ok or Apply to save these settings to the database.
10. Ensure that the new system subfolder is created in the System object and that it contains all
the necessary folders - External System Interface, Licenses, Security, Ancillary, Point Groups,
Configuration, Graphics, and Networks.

5.1.1 T O M ODIFY A S YSTEM

After a System has been created, it may need to updated or modified, use the following
procedures.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the System folder.
<HardwareRoot>
[Systems]
Unique System Name
4. Right click on the system object to be updated and select Open. The System dialog box
appears.

Note: If Deluxe points exist in the database, the “Disable Deluxe Points” check box will be
grayed out and cannot be checked.

5. Make necessary changes and select Ok or Apply.

OW240_60 67
5.2 To Insert a Network

5.2 TO INSERT A NETWORK

Note: Currently, Ovation Studio is limited to one network per system. However, a remote
network can be processed through the External System Interface in the Systems folder.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Network folder.
[Systems]
Unique System Name
[Networks]
4. Within the System object, right click the Networks folder and choose Insert New. The "Insert
New [Network] Wizard" dialog box appears (see Typical Wizard Dialog Box (see page 31)).
5. Type a Network Name (of your choice, up to eight alphanumeric characters) in the Network
Name entry field. Do NOT use the following invalid characters in a Network name: period (.),
dollar sign ($), percent sign (%), pound sign (#), at sign (@), and a space.
6. Select a Network Value by selecting the appropriate radio button (the local network must be
assigned a value of 0).
7. Select Finish and the "New [Networks]" dialog box appears.

Figure 30: Network Dialog Box

68 OW240_60
 5.2 To Insert a Network

8. Check that the settings are correct in the New Networks dialog box.

Network Dialog Box Descriptions

Field Description

Network Name Eight character limit. Forced uppercase. Invalid characters are
period (.), dollar sign ($), percent sign (%), pound sign (#), at
sign (@), space.
Network Name Alias Used internally by Ovation applications to talk to other
computers.
Network Value Must be set to 0.
DB Xmit Multicast Used internally by Ovation applications to talk to other
Address computers- for informational purposes only.
Alarm Multicast Used internally by Ovation applications - for informational
Address purposes only.
Simulator Multicast Used internally by Ovation applications - for informational
Address purposes only.
Advanced Algorithms Used internally by Ovation applications - for informational
Multicast Address purposes only.
Operator Event Used internally by Ovation applications - for informational
Multicast Address purposes only.

Note: The last five fields should show up in the host file, typically located in
C:\windows\system32\drivers\etc\hosts.

9. Select Ok or Apply to save these settings to the database.

10. Ensure that the subfolder with the new Network name is created in the Network object, and
that it contains all the necessary folders - Configuration, Graphics, and Unit.

5.2.1 T O M ODIFY A N ETWORK

In may be necessary to make changes to an existing network. Use the following procedures to
modify a network.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Network folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
4. Right click on the Networks folder to be modified and select Open. The Network dialog box
appears.
5. Make necessary changes and select Ok or Apply to add to the database.

OW240_60 69
5.3 To Insert a Unit

5.3 TO INSERT A UNIT

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Units folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
4. Within the Network object, right click the Units folder and choose Insert New. The "Insert
New [Units] Wizard" dialog box appears (see Typical Wizard Dialog Box (see page 31)).
5. Type a Unit Name (of your choice, up 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 (of your choice) by selecting the appropriate radio button. The Unit must
have a unique value within the network.
7. Select Finish and the "New [Units]" dialog box appears.

Figure 31: New Unit Dialog Box

70 OW240_60
 5.4 To Insert a Drop

8. Check that the settings are correct in the New Unit dialog box.

Network Dialog Box Descriptions

Field Description

Unit Name Unit name, your choice.

Unit Value 0-15

9. Select Ok or Apply to save these settings to the database.
10. Ensure that the subfolder with the new Unit name is created in the Network object, and that it
contains all the necessary folders - Configuration, Graphics and Drops.

5.3.1 T O M ODIFY A U NIT

In may be necessary to make changes to the unit. Use the following procedures to modify the
Unit.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Units folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
4. In the Units folder, right click on the Unit to be modified and select Open. The Unit dialog box
appears.
5. Make necessary changes and select Ok or Apply to add the changes to the database.

5.4 TO INSERT A DROP

Because of the many choices available more information is needed than can be discussed in one
topic, go to Building Drops (see page 113) to set up a new drop.

OW240_60 71
5.5 To Add a Point

5.5 TO ADD A POINT

Because of the many choices available more information is needed than can be discussed in one
topic, use the following topics when adding a point:
ƒ Building Points (see page 153) all of the topics below can be found under this main topic.
ƒ What are the Point Types? (see page 153) lists the different Ovation point types.
ƒ Point Naming Rules (see page 154) provides rules for naming points.
ƒ I/O Point Hardware Mapping (see page 153) discusses mapping for I/O points.
ƒ Point Dialog Box (see page 157) discusses point dialog boxes.
ƒ To Create a Point (see page 156) describes how to create a point.
ƒ Configuring Complex Points (see page 186) describes the configuration for complex points.
ƒ Third Party Points (see page 188) describes the configuration for third-party points.
ƒ Modifying a Point (see page 189) describes how to modify an existing point.
ƒ Point Processing (see page 108) process commands and perform alarming/limit checking
for points.

72 OW240_60
S E C T I O N 6

MANAGING OVATION LICENSES

In This Section

License Philosophy .............................................................................................. 74

Licenses Warning Boxes and Error Messages .................................................... 75
To Access the License Manager.......................................................................... 75

OW240_60 73
6.1 License Philosophy

6.1 LICENSE PHILOSOPHY

Licensing is a way to receive permission to enable certain Emerson Process Control software
products and processes. 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 the growth of a system over time. Small systems can normally operate with fewer licenses
than larger systems.

Licenses are stored on the License Server and manage access to the Ovation Developer Studio.
As you log into the 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 they are in use. If all licenses are in use, you must wait until a license becomes available.

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 System, such as the number of certain
types of drops in the system. The Developer Studio will prevent 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 Networks 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.
The License folder is only located at the System level. When the License folder is opened, the
Ovation License Manager is started. The Ovation Database Server is also defined as a System
License Server.

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, 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 object, as well as through the warning boxes indicating that you have been
locked out (see Licenses Warning Boxes and Error Messages (see page 75)).

Note: If the operating system is reloaded on the database server, the license key will no longer
be valid. You will be required to get a new license key code from
SWLicensing@EmersonProcess.com.

74 OW240_60
 6.2 Licenses Warning Boxes and Error Messages

6.2 LICENSES WARNING BOXES AND ERROR MESSAGES

Warning boxes appear if you attempt to access the Studio or 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 that may appear; the Ovation Developer Studio Alert warning box and
the Licenses Error message.

Ovation Developer Studio Alert Warning Box

The Ovation Developer Studio Alert dialog box appears where the statement reads “There are no
Ovation 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 Ovation 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.

6.3 TO ACCESS THE LICENSE MANAGER

The Licenses manager is a subfolder in the Systems folder. The License Manager provides the
tools necessary to view license details, add new licenses, and establish commuter licenses for
laptops. There are two types of licenses - the trial license and the normal license. The trial license
is a ten-day license that, when expired, locks the software until the normal license is purchased
and the key code entered. To access the License manager, perform the following procedures:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the System Tree to display its subfolders in the Overview window.
[Systems]
Unique System Name
4. Select and right click the Licenses folder and select Insert New from the popup menu, the
Insert New License Wizard will appear (see Typical Wizard Dialog Box (see page 31)).
5. Select Licensing from the WorkPad window. The License Manager dialog box will appear.

OW240_60 75
6.3 To Access the License Manager

6.3.1 L ICENSE M ANAGER O PERATIONS A REA

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 — Where the Fixed Licenses are listed. It provides information
about the feature selected in the Server List window. Information such as type of license, the
number of licenses purchased, and number of licenses used is contained in the Feature
Details window.

Note: Fixed License information is located under “Feature: System”.

ƒ 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 76)
à Environment Tab (see page 76)
à License Key Tab (see page 77)
à Working with Commuter Licenses

QUERY OPTIONS TAB

Unless there are multiple License Servers in the system, the Query Options tab (see Managing
Ovation Licenses (see page 73)) will not be utilized. The operations of the Query Options tab are
explained below.

Licenses Manager, Query Options Tab

Function Description

All in Subnet (Server Options) Queries any license server drops.

LSHOST list (Server Options) Provides the drop name of license server. All software
shipped from Emerson uses this field.
Single Server (Server Queries a specific drop.
Options)
All Features (Feature Options) Searches for all features on a specific drop.
Single Feature (Feature Provides a specific feature the queried drop is licensed
Options) to perform.

ENVIRONMENT 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.

76 OW240_60
 6.3 To Access the License Manager

LICENSE KEY TAB

The License Key tab is only available when accessed from a licensed server. This tab provides
information necessary to retrieve license codes from Emerson and the field to enter the license
key code to activate applications.

Notice in the License Key tab that the Server drop number and the Locking Criteria are provided.
The Locking Code, which is highlighted in yellow on the screen, must be given to Emerson in
order to receive the valid license key code. The Key Code unlocks purchased services on the
Ovation Developer Studio.

OW240_60 77
S E C T I O N 7

WORKING WITH DEVELOPER STUDIO FUNCTIONALITY

In This Section

Building Security .................................................................................................. 79

Setting Default Folders......................................................................................... 80
Defining Ancillary Labels...................................................................................... 80
Working with Graphics ......................................................................................... 82
Setting the Online/Offline Mode ........................................................................... 82
Working with Control Tasks ................................................................................. 84

7.1 BUILDING SECURITY

Security for an Ovation system is designed to prevent an unauthorized user from performing an
unauthorized action on an Ovation control system. This is accomplished by the assignment of
security roles for users and drops in the domain. All security selections and assignments are
saved in the Active Directory database. (See Ovation Security User Guide.)

OW240_60 79
7.2 Setting Default Folders

7.2 SETTING DEFAULT FOLDERS

This procedure uses defaults (see Defaults View Bar (see page 23) for more information about
defaults) for an analog point as an example. See Building Points (see page 153) for point-
specific instruction about dialog box, tab and field information.

1. Select the Default View Bar in the Ovation Developer Studio.

2. Open the Default Root folder to reveal the default object placeholder.
3. Select the subject Default Point Type folder (Default Analog Point for example).
4. Open the subject default object from the WorkPad window. The Appropriate default dialog
box appears.

Figure 32: Default Analog Point Dialog Box

5. Enter necessary point information into the appropriate tabs and fields. All information entered
for this point will then appear in every dialog box of a new point for this point type throughout
the system.

Note: See Building Points (see page 153) for point-specific tab and field information
instruction.

6. Select Ok or Apply to add the information to the database.

7.3 DEFINING ANCILLARY LABELS

The Ancillary folder contains the configuration tool needed 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.

There are 11 Ovation point record types. The figure above shows an Analog Point type and its
ancillary label information. Different Ancillary labels can be created for each point type.

For example, in this system, every Analog point supports the ability to specify information
regarding the drop cabinet name, department where the drop resides and additional hardware
attached to the drop. This information, in text form, has no bearing on the operation of the point,
but it may be necessary or helpful for administrative purposes.

80 OW240_60
 7.3 Defining Ancillary Labels

7.3.1 T O C REATE A NCILLARY L ABELS

The following example will illustrate how to create Ancillary Labels for an Analog Point type. The
procedures are the same for each point type, as long as the appropriate Point Label file is
selected. The field length for each Value is 30 characters.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the System object and locate the Point Groups folder.
[Systems]
Unique System Name
[Ancillary]
4. In the System object, open the Ancillary folder.
5. Select a Point Labels object from the WorkPad window. The Analog Points Labels dialog box
appears (for this illustration).
6. Type in the title to be used as the Ancillary data label for the object. For example, Drop
Cabinet Name: in the Value Column in row Field 1 Label (maximum length of 30 characters
in each “Value” field).
7. Type additional information in the successive fields as needed.
8. When finished, select Apply or OK. For each Analog Point created, the labels will be included
in the Analog Point dialog box, Ancillary tab. Only fields with information entered will appear in
the points dialog box.

Figure 33: Ancillary Tab in the Analog Points Dialog Box

OW240_60 81
7.4 Working with Graphics

7.3.2 T O M ODIFY A NCILLARY L ABELS

After an Ancillary object has been created, you may need to update it.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the Ancillary subfolder to display the list of Ancillary objects in the
Workpad window.
[Systems]
Unique System Name
[Ancillary]
4. Right click on the Ancillary object to be updated then select Open. The Ancillary dialog box
appears.
5. Make necessary changes and select Ok or Apply.

7.4 WORKING WITH GRAPHICS

The Graphics folder provides access to the Graphics Builder application (GBNT). GBNT is
accessed through the Ovation Developer Studio and develops the Process diagrams displayed on
the Ovation Operator Station. These process diagrams are software programs that display
graphical images representing plant process control equipment.

Two diagram files (source and object) are created and edited within GBNT. The source (.src)
format is a readable ASCII representation of the diagram that adheres to the syntax of the
graphics language. The object (.diag) format is the corresponding executable diagram file that is
displayed at the Ovation Operator Station.

All graphics set at the system level default throughout the system. Working at the system level
makes it easy to generically configure graphics throughout the Developer Studio. All graphics
established at the system level are available to every drop and every point setting throughout the
environment, unless they are overridden at the network, unit or operator station drop level. Adding
or editing graphics at a lower level changes them for only that level and any lower level. All
graphics at lower levels override those at the higher levels.(See Ovation Graphics Builder User
guide.)

7.5 SETTING THE O N L I N E /O F F L I N E M O D E

The Online/Offline Mode will permit engineering changes in an “Offline Mode” of operation. 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 via the check-box attribute on the System object folder. This attribute is
labeled “Offline Mode” and has an import/export reference of “OFFLINE_MODE”. By default, this
attribute is not enabled (i.e., by default, operation of the Ovation Engineering Tools restricts the
user from making changes which are “system disruptive”).

82 OW240_60
 7.5 Setting the Online/Offline Mode

7.5.1 T O E NABLE THE O FFLINE M ODE A TTRIBUTE

Enabling the “Offline Mode” attribute will cause 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 System object in the Ovation
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 all enabled.

7.5.2 T O D ISABLE THE O FFLINE M ODE A TTRIBUTE

Disabling the “Offline Mode” attribute will cause the following to occur:

1. The dynamic status entry for the System object is removed from the Ovation database. This
causes the red flag to disappear from the System object in the Ovation 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.

7.5.3 O PERATIONS P ERMITTED IN O FFLINE M ODE

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 will not be able to follow the point to
another Ovation drop. Typically, such bound local references are hardware-related. To
move an Ovation point which is bound to local hardware, it must first be removed from the
hardware (i.e., it must be a non-I/O point).
à The point must not be driven/”originated” by a control sheet.

OW240_60 83
7.6 Working with Control Tasks

Note: Non-local references are permitted to remain. For example, an Ovation point referenced
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 on this operation.
In general, execution of the above operations will cause any affected Ovation drop to be set to the
“Reload Required” state (i.e., the drop must be cleared before it is loaded). More specifically:
ƒ Moving a control sheet will cause only the Ovation drop owning the control sheet to be set to
the “Reload Required” state.
ƒ Moving an Ovation point will cause 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 to which the point is moved will be set to the “Load Required”
state unless it was also explicitly receiving the point (in which case it will also be set to the
“Reload Required” state).
ƒ Changing the broadcast frequency of a point will cause 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).

7.5.4 O FFLINE M ODE VIA I MPORT O PERATIONS

“Offline Mode” can be enabled and disabled via an Ovation Engineering Tools import operation
with the same effects as if it was performed via the Ovation Developer Studio.

An import operation can be used to change the broadcast frequency of an Ovation point with the
same effects as if done via the Ovation Developer Studio.

Note: Since an import operation cannot be used to move Ovation points or control sheets, these
actions are not applicable.

7.6 WORKING WITH CONTROL TASKS

The Ovation Control Builder (OCB) is an AutoCADTM based graphical editor that acts as an
AutoCAD plug-in and is used to create the control logic that is run in the Ovation Controller.

The functional drawings produced and edited by the Control Builder represent portions of
Controller logic. Typically, there are many different control drawing sheets linked together to form
the complete control structure.

The OCB drawings are stored in the Control Sheets sub folders located under the Control Tasks
folder.

The drawings display information about the algorithms that are used to build the control logic.
(See Ovation Control Builder User Guide.)

Note: You should never modify Ovation Control Builder generated points in the Studio. These
points are intentionally hidden from the hardware view. User defined points should be used if
customization is necessary. If hidden points are modified ACCIDENTALLY via a search, both
controllers (Primary and Backup) must be cleared before either is loaded.

84 OW240_60
S E C T I O N 8

DEVELOPER STUDIO CONFIGURATION FOLDER

In This Section

Configuration Folder Philosophy .......................................................................... 85

Configuration Components .................................................................................. 86
Modifying Dynamic Data Blocks (DDB) ............................................................... 88
Inserting External Networks Connections ............................................................ 90
Working with the Image Builder ........................................................................... 92
Configuring the Simple Network Management Protocol (SNMP) ........................ 98
Configuring the Network Time Protocol (NTP)................................................... 104
Working with the Plant Mode ............................................................................. 106
Point Processing ................................................................................................ 108
Online Controller Restore Mode......................................................................... 111

8.1 CONFIGURATION FOLDER PHILOSOPHY

The Configuration folder (see page 86) exists in the Systems folder, Networks folder, Units
folder, and Drops folder. At each level, the Configuration folder’s subfolders vary. The
Configuration folder at the Systems thru Drops level contains the tools necessary to configure
components on the system level.

Configurations made at the Systems level default down through the Networks, Units and Drops
levels. Any configurations changed at a lower level will also default down through its subfolders
and lower levels. The configuration defined at the lowest level takes precedence in its subfolders.

For example, if an alarm configuration change is made at the unit level, it will affect all alarms in
that unit and in all the drops contained in the unit. However, the change does not affect other units
in the network or system.

8.1.1 C ONFIGURING THE E XTERNAL I NTERFACE

The External Systems Interface allows users to define, map, and access remote networks. This is
also the location where specific local information required for remote access into the local network
is defined. (See Ovation Multiple Networks User Guide.)

OW240_60 85
8.2 Configuration Components

8.2 CONFIGURATION COMPONENTS

Configuration Components

Component S N U D Drop Level Described in:

y e n r
s t i o
t w t p
e o s s
m r
s k
s

Alarms X X X X Operator Stations, Operator Station Configuration

Sim Operator Guide, Simulator User Guide
Stations, Base
Station, Virtual
Controller Host
Foundation X Foundation Fieldbus User Guide
Fieldbus
Historian X Operator Station Configuration
Guide
Controller, X Controllers, Sim Controller User Guide, Simulator
Advanced Controllers, Virtual User Guide
Controllers Controller Host
Advanced X X X Controllers, Sim Controller User Guide, Simulator
Controller, Controllers, Virtual User Guide
Advanced Controller Host
Sim Controller
Image Builder X Working with the Image Builder
(see page 92)
Computer Work X X X X Operator Stations, Operator Station Configuration
Station (MMI) Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host
DDB X Modifying Dynamic Data Blocks
(DDB) (see page 88)
Master Virtual X Virtual Controller User Guide
Controller Host
OPC X Operator Station Configuration
Guide
External Network X X X All Drop Types Multiple Networks User Guide
Connections
Local Data Servers X

Local Alarm X
Collectors

86 OW240_60
 8.2 Configuration Components

Component S N U D Drop Level Described in:

y e n r
s t i o
t w t p
e o s s
m r
s k
s

Network Time X All Drop Types Configuring the Network Time

Protocol Protocol (NTP) (see page 104),
Simulator User Guide
Domain Controller
Network Time
Protocol
Ovation Keyboard X X X X Operator Stations, Operator Station Configuration
Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host
Point Menu X X X X Operator Stations, Configuring Your Ovation Operator
Sim Operator Station, Operator Station User
Stations, Virtual Guide
Controller Host
Point Processing X X X X All Drop Types Point Processing (see page 108),
Simulator User Guide, Ovation
Record Types Reference Manual
Process Diagrams X X X X Operator Stations, Operator Station Configuration
Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host
Plant Mode X Working with the Plant Mode
(see page 106)
Quality X X X X Operator Stations, Operator Station Configuration
Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host
Review X X X X Operator Stations, Operator Station Configuration
Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host
SCADA X Operator Stations, Simulator User Guide
Sim Operator
Stations, Base
Station, Virtual
Controller Host

OW240_60 87
8.3 Modifying Dynamic Data Blocks (DDB)

Component S N U D Drop Level Described in:

y e n r
s t i o
t w t p
e o s s
m r
s k
s

SNMP X Operator Stations, Simulator User Guide

Sim Operator
Stations, Base
Station, Virtual
Controller Host
Sim Controller X X X X Sim Controller, Simulator User Guide
Advanced Sim
Controller, Virtual
Controller Host
Sim Station X X X X Sim Operator Simulator User Guide
Stations, Virtual
Controller Host
Simulation Model X X X X Sim Operator Simulator User Guide
Stations, Virtual
Controller Host
Trend X X X X Operator Stations, Operator Station Configuration
Sim Operator Guide, Simulator User Guide
Stations, Virtual
Controller Host

8.3 M O D I F Y I N G D Y N A M I C D A T A B L O C K S (DDB)
The dynamic data portion of a point record is broadcast periodically on the highway by the
originating drop. Both the originating and receiving drops store dynamic data in volatile memory.
Dynamic data is broadcast on the highway in Dynamic Data Blocks or DDBs. DDB size is
configured through the DDB Configuration folder.

The DDB configuration object 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 values through
the Control Panel may make the system unusable.

88 OW240_60
 8.3 Modifying Dynamic Data Blocks (DDB)

8.3.1 T O M ODIFY A DDB C ONFIGURATION

Use the following procedure to modify a DDB Configuration.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the Networks folder, expand the Configuration folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
Configuration
4. Open the DDB Configuration folder.
5. Right click on the DDB object in the WorkPad window and select Open. The DDB
Configuration dialog box appears. The table below describes the fields of the DDB
Configuration dialog box.

Figure 34: DDB Configuration Dialog Box

DDB Configuration Dialog Box Descriptions

Field Description

Maximum DDB 4044 bytes for FDDI/CDDI. 1400 bytes for Ethernet.
Size
Must be defined before points are added to the database.
Maximum Number Maximum number of DDBs that can be defined for the system. Valid
of DDBs range is 100 to 2048. Cannot be reduced after points have been
added to the database.
Number of Small Quantity of DDBs assigned to drop records. For informational
DDBs purposes only.

OW240_60 89
8.4 Inserting External Networks Connections

Field Description

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 at which a fast point is considered to be timed out,
measured in tenths of seconds. For informational purposes only.
Age Slow Age at which a slow point is considered to be timed out,
measured in tenths of seconds. For informational purposes only.
DDB Multicast Internal Ovation network control. For informational purposes only.
address
6. Select the Maximum DDB Size using the spin button control.
7. Select the Maximum Number of DDBs using the pull-down menu.
8. Select Ok or Apply to add the DDB configuration to the database.

Note: The changes will not take affect until they are downloaded (Download Function (see
page 38)) and the drop is rebooted (Reboot Function (see page 48)). All the drops in the
system should be downloaded and rebooted to ensure the DDB change is valid throughout the
system.

8.4 INSERTING EXTERNAL NETWORKS CONNECTIONS

Use the following procedure to insert External Network Connection for a System.

90 OW240_60
 8.4 Inserting External Networks Connections

8.4.1 T O C REATE AN E XTERNAL N ETWORK C ONNECTIONS F OLDER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the System Tree to the Configuration folder under the Networks folder, open the
External Network Connections folder.
[Systems]
Unique System Name
Configuration
[External Networks Connections]
4. Right click on the External Network folder and select Insert New. The New External Network
Wizard appears (see Typical Wizard Dialog Box (see page 31)).
5. Select the Remote Network, then select Finish. The New External Networks dialog box
appears.

Figure 35: External Networks Dialog Box

6. The Primary and Secondary Data Servers will automatically be filed in using information
provided when setting up the External Systems Interface. (See Ovation Multiple Networks
User Guide.) The user can change this information, if no secondary is required, set the value
to blank.
7. Fill in the Remote Data Information:
à Point Count - Maximum number of points that can be received.
à Dynamic Age - Length of time (In Seconds) before the data is unchecked.

OW240_60 91
8.5 Working with the Image Builder

à Refresh Period - How often (In Seconds) info is checked.

à Data Lifetime - How Long (In Seconds) before data is purged.
8. Select Ok or Apply.

8.5 WORKING WITH THE IMAGE BUILDER

The Image Builder is a dictionary that contains a list of all icon files used in the Ovation System
Tree. These icons replace the folders that represent Ovation database hierarchy classes in the
System Tree. For example, the globe icon is the default setting for the System and replaces the
folder icon in the System Tree.

Using the Image Builder, you can apply the default icon settings to your System Tree and replace
many of the folder icons with images more relevant to the particular class (for example, Analog
Points). The Image Builder is only located at the System level.

In addition to the default icon settings, you can use the Image Builder to import a variety of other
icons to associate with classes in the System Tree. You can import any image saved as an icon
file into the image dictionary and use it as a class icon.

92 OW240_60
 8.5 Working with the Image Builder

8.5.1 T O I NSERT THE I MAGE B UILDER D ICTIONARY

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Select the ImageBuilder folder.
5. Check the Workpad window to ensure that there is no Image Builder Dictionary file already
created (OvPTClsImage.ild). If the file already exists, simply open the dictionary (Descriptions
of Point Dialog Box Tabs).
6. If there is NO Image Builder Dictionary file present in the Workpad window, right click the
Image folder and select Insert New from the right-click menu. The Insert New Image Builder
Wizard appears (see Typical Wizard Dialog Box (see page 31)).
7. Select the Finish button, and the Ovation Image Builder Wizard appears.

Figure 36: Ovation Image Builder Wizard

OW240_60 93
8.5 Working with the Image Builder

8. Select the Next button and the Image Builder Dictionary dialog box appears. Now the Image
Dictionary icon appears in the WorkPad window. The dictionary contains icon files associated
with database classes by default. These default settings can be edited, and additional icons
can be added to the dictionary. Section C through Section G provides information on editing
the dictionary.

Figure 37: Image Builder Dictionary Dialog Box

8.5.2 T O E DIT THE I MAGE B UILDER D ICTIONARY

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration folder.
[Systems]
Unique System Name
Configuration
4. Select the ImageBuilder folder.
5. Check the Workpad window to ensure that there is an Image Builder Dictionary already
created (OvPTClsImage.ild). If there is no file, insert one (see Ovation Modules (see page
217)).
6. Double click the Image Dictionary icon in the WorkPad window and the Ovation Image
Builder Wizard opens (see To Insert the Image Builder Dictionary (see page 93)).
7. Select Next and the Image Dictionary dialog box appears. The following procedures describe
how to edit the Dictionary (see To Insert the Image Builder Dictionary (see page 93)).

94 OW240_60
 8.5 Working with the Image Builder

8.5.3 T O R EMOVE AN I CON /C LASS A SSOCIATION

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Access the Image Dictionary dialog box (To Insert the Image Builder Dictionary (see page
93)).
5. Go to the Class List and select the name of the class that you want to disassociate.
6. Open the Image drop-down menu and select None. The icon association is removed.
7. When all the desired Image Dictionary edits have been completed, select the Next button.
8. Select to either Save or Discard the changes by choosing the appropriate radio button.
9. Perform a Download, shut down the Studio, and then restart the Studio to apply the changes.

8.5.4 T O A DD AN I CON /C LASS A SSOCIATION

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Access the Image Dictionary dialog box.
5. Go to the Class List and select the name of the class that you want to associate.
6. Open the Image drop-down menu and select the appropriate icon. The icon association is
made.
7. When all the desired Image Dictionary edits have been completed, select the Next button.
8. Select to either Save or Discard the changes by choosing the appropriate radio button.
9. Perform a Download, shut down the Studio, and then restart the Studio to apply the changes.

OW240_60 95
8.5 Working with the Image Builder

8.5.5 T O A DD AN I CON TO THE D ICTIONARY

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Access the Image Dictionary dialog box.
5. Select the New button and the Select a new Icon file to Add dialog box appears.

Figure 38: Select a New Dictionary Icon Dialog Box

6. Select an Icon file (.ico) and choose Open. The new icon is added to the dictionary.
7. Make an Icon/Class association.
8. When all Image Dictionary edits have been completed, select the Next button.
9. Select to either Save or Discard the changes by choosing the appropriate radio button.
10. Perform a Download, shut down the Studio, and then restart the Studio to apply the changes.

96 OW240_60
 8.5 Working with the Image Builder

8.5.6 T O D ELETE AN I CON F ROM THE D ICTIONARY

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Access the Image Dictionary dialog box.
5. Select the Image in the Image List.
6. Remove all Icon/Class Associations for the selected icon using the procedures above.
7. Select the Delete button and 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 will appear: “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.”

8. When all Image Dictionary edits have been completed, select the Next button.
9. Select to either Save or Discard the changes by choosing the appropriate radio button.
10. Perform a Download, shut down the Studio, and then restart the Studio to apply the changes.

8.5.7 T O C HANGE AN I CON IN THE D ICTIONARY AND A LL OF ITS A SSOCIATIONS

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the System icon and open the Configuration Folder.
[Systems]
Unique System Name
Configuration
4. Access the Image Dictionary dialog box.
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 will be affected by
the change.
7. Select the Change button, and the Select a New Icon File to Replace dialog box appears
(see To Add an Icon to the Dictionary (see page 96) for similar screen).
8. Select an Icon file (.ico) and choose Open.
9. The new icon is added to the dictionary and replaces the previous Icon in all its associations.
10. When all Image Dictionary edits have been completed, select the Next button.
11. Select to either Save or Discard the changes by choosing the appropriate radio button.
12. Perform a Download, shut down the Studio, and then restart the Studio to apply the changes.

OW240_60 97
8.6 Configuring the Simple Network Management Protocol (SNMP)

8.6 CONFIGURING THE SIMPLE NETWORK MANAGEMENT PROTOCOL

(SNMP)
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. SNMP Ovation (the SNMP application program) uses SNMP
variables, known as Management Information Blocks (MIBs), in Ovation Points.

8.6.1 T O C ONFIGURE SNMP

To set SNMP, use the following procedures:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the station drop to be configured for SNMP.
4. Open the Configuration folder and right click on the SNMP folder. The Insert New SNMP
Wizard appears (see Typical Wizard Dialog Box (see page 31)).
5. There are no settings to be made, select Finish. When an SNMP object is created, a blank
SNMP Notepad file is opened.

Figure 39: SNMP File

98 OW240_60
 8.6 Configuring the Simple Network Management Protocol (SNMP)

6. All SNMP settings are typed into the file. Enter all the settings needed to complete the SNMP
configuration. See SNMP Parameter Settings (see page 100) for details about SNMP
settings. See example of an SNMP file below.

Figure 40: SNMP Configuration File

7. Save the changes by choosing File from the Menu bar and selecting 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 (Download Function (see page
38)) and Reboot (Reboot Function (see page 48)).

OW240_60 99
8.6 Configuring the Simple Network Management Protocol (SNMP)

8.6.2 SNMP P ARAMETER S ETTINGS

In order to complete the SNMP configuration there are several settings that have to be made. The
setting information described in the "DeviceX____" topics must be hand typed into the
snmp_config file if they are not already present.

DEVICEX.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

DEVICEX.TIMEOUTBITNUMBER

Parameter Description

Bit Number to use in the case of a packed digital point.

Example
Device1.TimeOutBitNumber: 0

DEVICEX.COMMUNITYNAME

Parameter Description

Community name or password. By default, the program uses “public” as the community name.

Example
Device1.CommunityName: Public

DEVICEX.VARIABLEY.NAME

Note: Y refers to the variable number. SNMP2Ovation reads the variable only in numerical
order and stops reading at the last number.

For example, if variables have been numbered

1, 2, 3, 5, SNMP2Ovation reads 1, 2, 3 and then stops, ignoring all numbers after the missed
number.

Parameter Description

Variable to be polled on device.

Example
Device1.Variable1.Name:
transmission.fddi.fddimib.fddimibMACCounters.fddimibMACCo

100 OW240_60
 8.6 Configuring the Simple Network Management Protocol (SNMP)

DEVICEX.VARIABLEY.FREQUENCY

Parameter Description

How often, measured in seconds, to retrieve this variable from the device.

Example
DeviceX.Variable1.Frequency: 10

DEVICEX.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 nth and
(n-1)th 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 nth 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.

Example
Device2.Variable4.Test: ValueNEConfiguredValue
Device3.Variable5.Test: DeltaGTLimit

DEVICEX.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.ConfiguredValue:4

DEVICEX.VARIABLEY.UPPERLIMIT

Parameter Description

A value to test against a variable. This parameter is used if the test parameter is
DeltaGTLimit.

Example
Device2.Variable4.UpperLimit:

OW240_60 101
8.6 Configuring the Simple Network Management Protocol (SNMP)

DEVICEX.VARIABLEY.LOWERLIMIT

Parameter Description

A value to test against a variable. This parameter is used if the test parameter is DeltaLTLimit.

Example
Device2.Variable4.LowerLimit:

DEVICEX.VARIABLEY.BITMASKENABLED

Parameter Description

Values are “True” or “False”, and 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

DEVICEX.VARIABLEY.BITMASK

Parameter Description

Value to “AND” variable with 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”.
This parameter is used only if:
à The bit mask is enabled for this variable and
à 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.

DEVICEX.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.

102 OW240_60
 8.6 Configuring the Simple Network Management Protocol (SNMP)

Example
Device1.Variable3.PointName: LP158s001

DEVICEX.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

DEVICEX.NAME

Note: X refers to the device number. SNMP2Ovation reads the device only in numerical order
and stops reading at the last number.

For example, if devices have been numbered 1, 2, 3, 5, SNMP2Ovation reads 1, 2, 3 and then
stops, ignoring all numbers after the missed number.

Parameter Description

Device Name or IP Address.

Example
Device1.Name: 192.9.200.101

8.6.3 M ODIFYING SNMP

If SNMP Configuration is already established and needs updated, use the following procedure.

TO MODIFY SNMP
1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the drop folder you are going to modify and select the Configuration folder.
4. Right click the SNMP folder and the SNMP object appears in the Workpad window.
5. Open the SNMP object in the Workpad window and the SNMP Notepad appears.
6. Make necessary changes.
7. Choose File from the menu bar and select Save.
8. After saving the SNMP configuration, perform a Download (Download Function (see page
38)) and Reboot (Reboot Function (see page 48)).

OW240_60 103
8.7 Configuring the Network Time Protocol (NTP)

8.7 CONFIGURING THE N E T W O R K T I M E P R O T O C O L (NTP)

Network Time Protocol (NTP) identifies the drop or external server that is providing the time base
for the system. NTP is automatically created when a Network is inserted.

8.7.1 T O C ONFIGURE THE N ETWORK T IME P ROTOCOL (NTP) F OLDER

Use the following procedures to configure the NTP.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the Networks folder, expand the Configuration folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
Configuration
[Networks Time Protocol]
4. Open the Network Time Protocol folder.
5. Right click the NTP object in the WorkPad window and select Open. The NTP Configuration
dialog box appears, as shown in the table below describes the fields of the NTP Configuration
dialog box.

Figure 41: NTP Configuration Dialog Box

104 OW240_60
 8.7 Configuring the Network Time Protocol (NTP)

NTP Configuration Dialog Box Descriptions

Field Description

Time Server Standard NTP Server or Domain Server

Domain Server Domain Server IP Address (System use only)

NTP Server NTP Server IP Address (System use only)

Time Server 1 Time server with which the rest of the drops in the system are
synchronized. (Blank, Drop #, or External Time Server.) This
NTP (Time) Server
field is not available unless "Standard NTP Server" is chosen for the
Time Server, otherwise the
External Time Time Server IP address for an external time server. This field only
Server appears if "Standard NTP Server" is chosen for the Time Server,
and if "External Time Server" is selected from the Time Server 1
pull-down menu.
Time Server 2 Back up time server to be used if Time Server 1 cannot be
accessed. (Blank, Drop #, or External Time Server.) This field is
NTP (Time) Server
not available unless "Standard NTP Server" is chosen for the Time
Server.
External Time Time Server IP address for an external time server. This field only
Server appears if "Standard NTP Server" is chosen for the Time Server,
and if "External Time Server" is selected from the Time Server 2
pull-down menu.
6. Select the drop to be used as Time Server 1 from the pull-down menu. If External Time
Server is selected, enter the IP address.
7. Select the drop to be used as Time Server 2 from the pull-down menu. If External Time
Server is selected, enter the IP address.

Note: A time standard WEB site such as NISTIME can be used.

8. Select Ok to activate the NTP.

Note: The changes will not take affect until they are downloaded (Download Function (see
page 38)) and the drop is rebooted (Reboot Function (see page 48)). All the drops in the
system should be downloaded and rebooted to ensure the NTP change is valid throughout the
system.

OW240_60 105
8.8 Working with the Plant Mode

8.8 WORKING WITH THE PLANT MODE

The Plant Mode is used to define the current state of the plant, with up to six configurable states.
For example, mode 1 may indicate plant start up, mode 2 could indicate plant shutdown, and
mode 3 may indicate full load.

Plant Mode is the identification of the analog point in the unit that is to be used by Ovation Point
Originators to determine which deluxe plant mode attributes are in affect.

The deluxe analog point is created in the points folder, which is discussed in Building Points
(see page 153). Instructing the unit which point is the plant mode point is done through the Plant
Mode subfolder in the Units folder.

106 OW240_60
 8.8 Working with the Plant Mode

8.8.1 T O A DD A P LANT M ODE TO A U NIT

Use the following procedure to insert Plant Mode for a unit.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the appropriate Configurations folder in the Units folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
Configuration
4. In the Units folder which you want to update open the Configuration folder.
5. Right click on the Plant Mode folder and select Insert New. The New Plant Mode dialog box
appears, as shown in.

Figure 42: Plant Mode Dialog Box.

6. Type the name of the analog point to be used as the plant mode in the Value column.
7. Make necessary changes and select Ok or Apply to add the changes to the database.

OW240_60 107
8.9 Point Processing

8.8.2 T O M ODIFY THE P LANT M ODE

In may be necessary to make changes to Plant Mode. Use the following procedures to modify
Plant Mode.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the appropriate Configurations folder in the Units folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
Configuration
4. Open the Plant Mode folder and right click on the Plant Mode object in the Workpad window
and select Open. The Plant Mode dialog box appears.
5. Make necessary changes and select Ok or Apply to add the changes to the database.

8.9 POINT PROCESSING

The purpose of point processing is to process commands and perform alarming/limit checking for
points. Point Processing can be configured at the System, Network, Unit or Drop 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), (See Ovation
Record Types Reference Manual.)

The Point Processing configuration folder resides in the Developer Studio System Tree.

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.

108 OW240_60
 8.9 Point Processing

8.9.1 T O P ROCESS A P OINT

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the Configuration folder.
[Systems]
Configuration
[Point Processing]

Note: Point Processing can also be performed at the Network, Unit and Drop levels.

4. Open the Point Process Configuration in the Point Processing folder and the Point
Processing dialog box appears. The table below explains the topics available in the Point
Processing dialog box.

Figure 43: Point Processing Dialog Box

Point Processing Dialog Box Options

Item Description Setting Option

Manually Entered Quality Specifies the quality that will be Good, Fair (Default),
assigned to a manually entered Poor, Bad
point.

User Defined Frequency Enables or disables the user Disabled (Default)

defined OPP (Originated Point
Enabled
Processing) task.
User Defined Frequency Specifies the frequency of the 2000 (Default)
(msec.) enabled user defined OPP task
in milliseconds.

OW240_60 109
8.9 Point Processing

5. Enter the desired changes and select Apply or Ok to accept the changes.
6. The changes must be downloaded and the drop must be rebooted before the new settings will
take effect.

110 OW240_60
 8.10 Online Controller Restore Mode

8.10 O N L I N E C O N T R O L L E R R E S T O R E M O D E
The Ovation System contains an optional Online Controller Restore Mode of operation which will
capture images of an Ovation drop’s application data (Ovation originated points and control) and
associated system files. The primary purpose of this Mode is to provide a mechanism to restore a
redundant drop to its former fully matched condition after undesirable and/or catastrophic control
behavior is observed following the load of new application data to one half of a pair of redundant
Ovation drops/Controllers. The Restore Mode provides the ability to back-out the engineering
changes made to the drop so it can be reloaded with the same application data that its partner
contains.

You must decide whether or not to operate the Ovation Online Controller Restore Mode. No
special user interactions are required when operating in Restore Mode, but there are some issues
that must be considered:
ƒ System performance and disk space issues.
ƒ Engineering limitations.
ƒ Point Information.

CAUTION: The Restore Mode is intended to recover from a failed load that may result in a
partner mismatch between redundant Controllers. It is NOT intended to “undo” programming
mistakes. Restore should NOT be used casually since the process is time-consuming and
requires operator action (including a drop reload) to ensure a complete drop restore.

The following items are included in Restore Mode images:

ƒ Database tables associated with the drop (including point and control information, hardware
configuration and holding registers)
ƒ Monitor Graphics created by the Control Builder
ƒ Control information (Control Builder drawing files)
ƒ Data Not Included in Restore Images
The following items are NOT included in Restore Mode images and must be regenerated
manually:
ƒ Ovation configuration information
ƒ Custom Graphics (built by the Graphics Builder)
ƒ Reports
ƒ Reference information generated by the Graphics Builder and the Report Builder (information
required to support the Where Used function for a point).
ƒ Reference information can be regenerated by recompiling any effected Graphics and Reports.
ƒ Any applicable HSR PIC files must be regenerated and query/downloaded to the appropriate
drop (if the system is utilizing an eDB, the PIC file must be imported into the eDB).

CAUTION: Arbitrarily switching between Restore Mode functions is NOT encouraged. When
the system is taken out of Restore Mode, any existing Restore Images are marked as invalid
and can never be used again. When the system is placed into a Restore Mode, you have the
option of immediately taking Restore Images. However, the system will only be able to take a
Restore Image if a drop is fully loaded and matched with its partner (if redundant).

OW240_60 111
8.10 Online Controller Restore Mode

8.10.1 T O C ONFIGURE THE O NLINE C ONTROLLER R ESTORE M ODE

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the System (System level) folder:
[Systems]
Unique System Name
4. Right click the System Folder object and select Open from the resulting pop-up menu (see
Right-Click to Insert New or Open a Dialog Box). The System Folder dialog box appears.
5. Find Restore Mode in the Attributes column and choose the appropriate function from the
pull down menu.

112 OW240_60
S E C T I O N 9

BUILDING DROPS

In This Section

Drop Philosophy................................................................................................. 113

Drop Types......................................................................................................... 114
Is a New Drop Needed, and Can It Be Installed? .............................................. 114
What Information is Needed before Adding a Drop? ......................................... 115
To Insert a Drop ................................................................................................. 118
To Insert a Drop Point ........................................................................................ 138
To Modify a Drop................................................................................................ 140

9.1 DROP PHILOSOPHY

A Drop is any hardware/software that has enough Ovation software to receive and transmit
information to other Ovation hardware/software. The Ovation software contains several Drop
Types (see page 114)). The Developer Studio provides a mechanism for the adding and deleting
of Drops to the system database.

Note: You will only be able to add as many drops as defined by the license key. Before entering
drops, verify that the 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 73) for more information about licensing.

After a drop has been created, a Drop Point must be created in order for the system to recognize
the new drop. This Drop Point corresponds to the drop’s required DU record, see To Insert a
Drop Point (see page 138). (See Ovation Record Types.)

After a drop and its Drop Point have been created, and loaded to the target drop, it may be
necessary to make modifications to the drop. To modify a drop, see To Modify a Drop (see page
140). Drops are established and configured using the objects within a Drop folder.

OW240_60 113
9.2 Drop Types

9.2 DROP TYPES

The current Drop Types are seen in the table below.

Note: Currently, Ovation Studio is limited to 254 drops per network.

If there are multiple drops, each drop would appear in the Drop object and would provide objects
for each drop (based on the drop type):

Drop Types

Drop Type Config Points Graphics I/O Control Control Holding

Devices Compo- Tasks Registers
nents

Operator Station X X X

Sim Operator Station X X X

Base Station X X

Controller X X X X X X

Advanced Controller X X X X X X

Sim Controller X X X X X X

Advanced Sim Controller X X X X X X

Virtual Controller Host X X X

Virtual Controller X X X X X X

9.3 IS A NEW DROP NEEDED, AND CAN IT BE INSTALLED?

Before adding a new Drop there are several things that must be considered.

A Drop is added to accommodate the addition of a station, or to create a place to add points.
ƒ A Drop is added to accommodate additional points, because:
à The controller is full (8000 - 16000 points depending on configuration).
à Physical limitations (cost of wiring, signal loss, location reasons) require a new drop.
ƒ A new license is needed prior to adding a drop.
ƒ A Drop Point must be added to a new Drop in order to supply a DU record (Record type used
to store status information for a drop).

114 OW240_60
 9.4 What Information is Needed before Adding a Drop?

9.4 WHAT INFORMATION IS NEEDED BEFORE ADDING A DROP?

Once it is determined that a new Drop must be installed, and that licensing to permit it,
information must be gathered in order to complete the Drop and drop point addition.

1. Information needed to Add a Drop:

a) The Drop type (see page 114).
b) Normal or Expanded Maximum Point limit (not applicable to Operator Station, Sim
Operator Station, or Base Station Drops).
c) Drop ID.
d) To Determine IP Address (see page 115)
e) Is there a Partner Drop, the same information gathered for e-k is needed?
The following are for controller type machines:
f) Computer Name (Must have for primary and partner on widows machines)
g) To Determine NIC Address (see page 116) (also known as Network Ethers Address).
h) Backup NIC Interface.
i) Highway Interface (ZNYX, or Onboard).
j) Highway Connection.
2. Information needed to add a Drop Point
a) Point Alias (name) (Required, must be DROPXXX, where XXX is the Drop ID)
b) Drop Number (Required) (Must be either primary or partner ID, and must be consistent
with the Point Name)
c) Broadcast Frequency (Required)
d) Description
e) Characteristics
f) Security Group
g) Ancillary information
h) eDB Collection enabled or disabled.
i) Scan Frequency
j) Alarm Priority
k) Summary Diagram
l) Signal Diagram.

9.4.1 T O D ETERMINE THE IP A DDRESS OF A W INDOWS M ACHINE /D ROP

It is necessary to obtain and record the Internet Protocol (IP) address for proper Ovation software
configuration.

1. Determine and record the Internet Protocol (IP) address that will be assigned to the drop.
These numbers will be needed for the configuration (when inserting a drop). The IP address
consists of four groups of decimal numbers which can have one to three places and the
format is:
xxx.xxx.xxx.xxx

OW240_60 115
9.4 What Information is Needed before Adding a Drop?

The System Administrator typically assigns these addresses. The addresses can also be
assigned to be any valid range if the network is isolated from other networks (such as, the
Internet).
For Windows machines:
2. Go to the Start button and run the Command Prompt.
3. Type "ipconfig" then press the Return.
4. Copy the IP address, needed for the configuration.

9.4.2 T O D ETERMINE NIC (N ETWORK E THERS ) A DDRESS

It is necessary to obtain and record the Network Interface Card (NIC) address (either from the
card, or as assigned) for proper Ovation Controller software configuration.

Note: The Controller can support a dual attached highway configuration utilizing the onboard
NIC ports.

NIC CARD LABELS CONTAINING THE HARDWARE ADDRESS

1. For access to the NIC, refer to Removing and Re-installing the Controller Cover.
2. Some earlier NIC cards have a label containing the hardware address.
3. Obtain the address from the NIC card in the Controller.
4. Determine and record the NIC hardware address. The format for the hardware address is:
xx:xx:xx:xx:xx:xx
(where the last four numbers (xx:xx) are located on a label on the NIC).
5. Record the address; it is needed for the Controller configuration.

NIC ADDRESS ASSIGNED TO THE CONTROLLER DROP

1. Determine and record the Network Interface Card (NIC) address that will be assigned to the
Controller drop. The NIC (Hardware) address will look like:
xx:xx:xx:xx:xx:xx
Where the last four numbers (xx:xx) are located on a label on the NIC. These numbers will be
needed for the Controller configuration (used in the “Ovation Network Ethers Address” field of
To Insert New Controller Drop).

116 OW240_60
 9.4 What Information is Needed before Adding a Drop?

2. Confirm that the blue power switch on the Controller is in the Off (0) position.
3. Remove the Controller front panel cover(s), described in Removing and Re-installing the
Controller Cover.
4. Check that all the network cables are connected.

Note: Some earlier NIC cards have a label containing the hardware address, if so skip to Step
10.

5. Re-install the Controller front panel cover(s) (described in Removing and Re-installing the
Controller Cover).
6. Ensure that the Power Supply is ON.
7. Turn the blue power switch to the ON position (1) for the Controller whose NIC card address
is needed. The LED on the Controller Power Supply module will light steadily. If more than
one Controller is turned on, the addresses will be displayed in the order that the Controllers
are turned on.
8. To view the hardware addresses, look at the Ovation Error.log file under Start->Programs-
>Ovation Applications-.Error Log.
9. Begin with the bottom of the list (most recent entries) and scroll backwards until you locate
the following message:
Hardware Address not found xx:xx:xx:xx:xx:xx.
10. Record the address that is displayed in the message, this address is needed for the Controller
configuration.

OW240_60 117
9.5 To Insert a Drop

9.5 TO INSERT A DROP

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the Drops folder:
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
4. Right click on the Drops folder in the System Tree and select Insert New. The Insert New
Drop Wizard appears (see Typical Wizard Dialog Box (see page 31)).
5. Type the Drop ID in the Drop ID value field.
6. Type the Partner ID in the Partner ID value field (if used).
7. Select the desired drop type (Controller, SimController, Operator Station, Sim Operator
Station, Base Station, Advanced Controller, Advanced SimController, Virtual Controller
Host, Virtual Controller) from the Drop-type pull-down menu.

Insert New Drop Wizard Field Descriptions

Field Description

Drop ID This is the drop number of the new drop (1-254).

Partner ID This field identifies the drop ID of the partner drop (1-254).
Drop Type This pull-down menu contains drop type choices: Controller, SimController,
Operator Station, Sim Operator Station, Base Station, Advanced
Controller, Advanced SimController, Virtual Controller Host, Virtual
Controller.
8. Select Finish. The New [Drops] dialog box appears (see Typical Dialog Box (see page 30)).
9. Choose from the following list for the selected drop types:
à For the Controller, Sim Controller, Advanced Controller, and Advanced Sim Controller see
To Enter Drops Info for Controllers (see page 119).
à For the Operator Station, Sim Operator Station and Base Station see To Enter Drops
Info for Operator and Base Stations (see page 126).
à To Enter Drops Info for the Virtual Controller Host (see page 133).
à To Enter Drops Info for the Virtual Controller (see page 136).

118 OW240_60
 9.5 To Insert a Drop

9.5.1 T O E NTER D ROPS I NFO FOR C ONTROLLERS

1. For the Controller enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.

Figure 44: New Controller Drop Dialog Box

New Controller Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Controller, SimController,
Advanced Controller, or Advanced SimController.
Maximum Point Limit This radio button selects the maximum number of points that the
Controller can be configured to monitor.
Normal handles up to 6000 points.
Expanded handles up to 16000 points.
PRIMARY
Drop ID This is the drop number of the originating drop of the point. (1-254).

OW240_60 119
9.5 To Insert a Drop

Field Description

Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection. (Only active for Highway Connection
Connection Onboard.)
(Single, Dual)
NIC Interface Name of physical port that the ethernet cable is connected to,
automatically filled in fei0 for Highway Connection "Onboard".
(None, fei0, fei1, fei2)
NIC Backup Interface This is to accommodate a second onboard NIC , automatically filled in
fei1 for a NWIF Highway Connection "Onboard" and Highway
Connection "Dual".
(None, fei0, fei1, fei2)
PARTNER
Partner ID If the drop has a partner drop, it is identified in this field (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).

120 OW240_60
 9.5 To Insert a Drop

Field Description

Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)

NIC Interface Name of physical port that the ethernet cable is connected to.
(None, fei0, fei1, fei2)

Backup NIC Interface This is to accommodate the second onboard NIC. (None, fei0, fei1, fei2)

Once a new drop is created, a Drop Point must be added for the primary and partner to provide a
drop status (DU) point record type.

9.5.2 T O E NTER D ROPS I NFO FOR S IM C ONTROLLER

1. For the Sim Controller enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.
3. The New [Drops] dialog box will look similar to the one in To Enter Drops Info for
Controllers (see page 119).

New Sim Controller Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Controller, SimController,
Advanced Controller, or Advanced SimController.
Maximum Point Limit This radio button selects the maximum number of points that the
Controller can be configured to monitor.
Normal handles up to 6000 points.
Expanded handles up to 16000 points.
PRIMARY
Drop ID This is the drop number of the originating drop of the point. (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.

OW240_60 121
9.5 To Insert a Drop

Field Description

Ovation Network The format for the hardware address is:

Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection. (Only active for On Board.)
Connection
(Single, Dual)
NIC Interface Name of physical port that the ethernet cable is connected to,
automatically filled in fei0 for On Board.
(None, fei0, fei1, fei2)
NIC Backup Interface This is to accommodate a second onboard NIC , automatically filled in
fei1 for a NWIF On Board for Highway Connection:dual.
(None, fei0, fei1, fei2)
PARTNER
Partner ID If the drop has a partner drop, it is identified in this field (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)

NIC Interface Name of physical port that the ethernet cable is connected to.
(None, fei0, fei1, fei2)

122 OW240_60
 9.5 To Insert a Drop

Field Description

Backup NIC Interface This is to accommodate the second onboard NIC. (None, fei0, fei1, fei2)

Once a new drop is created, a Drop Point must be added for the primary and partner to provide a
drop status (DU) point record type.

9.5.3 T O E NTER D ROPS I NFO FOR A DVANCED S IM C ONTROLLER

1. For the Advanced Sim Controller, enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.
3. The New [Drops] dialog box will look similar to the one in To Enter Drops Info for
Controllers (see page 119).

New Controller Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Controller, SimController,
Advanced Controller, or Advanced SimController.
Maximum Point Limit This radio button selects the maximum number of points that the
Controller can be configured to monitor.
Normal handles up to 6000 points.
Expanded handles up to 16000 points.
PRIMARY
Drop ID This is the drop number of the originating drop of the point. (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection. (Only active for On Board.)
Connection
(Single, Dual)

OW240_60 123
9.5 To Insert a Drop

Field Description

NIC Interface Name of physical port that the ethernet cable is connected to,
automatically filled in fei0 for On Board.
(None, fei0, fei1, fei2)
NIC Backup Interface This is to accommodate a second onboard NIC , automatically filled in
fei1 for a NWIF On Board conn:dual.
(None, fei0, fei1, fei2)
PARTNER
Partner ID If the drop has a partner drop, it is identified in this field (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)

NIC Interface Name of physical port that the ethernet cable is connected to.
(None, fei0, fei1, fei2)

Backup NIC Interface This is to accommodate the second onboard NIC. (None, fei0, fei1, fei2)

Once a new drop is created, a Drop Point must be added for the primary and partner to provide a
drop status (DU) point record type.

124 OW240_60
 9.5 To Insert a Drop

9.5.4 T O E NTER D ROPS I NFO FOR A DVANCED C ONTROLLER

1. For the Advanced Controller, enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.
3. The New [Drops] dialog box will look similar to the one in To Enter Drops Info for
Controllers (see page 119).

New Controller Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Controller, SimController,
Advanced Controller, or Advanced SimController.
Maximum Point Limit This radio button selects the maximum number of points that the
Controller can be configured to monitor.
Normal handles up to 6000 points.
Expanded handles up to 16000 points.
PRIMARY
Drop ID This is the drop number of the originating drop of the point. (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection. (Only active for On Board.)
Connection
(Single, Dual)
NIC Interface Name of physical port that the ethernet cable is connected to,
automatically filled in fei0 for On Board.
(None, fei0, fei1, fei2)
NIC Backup Interface This is to accommodate a second onboard NIC , automatically filled in
fei1 for a NWIF On Board conn:dual.
(None, fei0, fei1, fei2)

OW240_60 125
9.5 To Insert a Drop

Field Description

PARTNER
Partner ID If the drop has a partner drop, it is identified in this field (1-254).
Ovation Network IP The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
Ovation Highway Type of ethernet interface that connects the Controller to the Ovation
Interface Highway.
(ZNYX, or Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)

NIC Interface Name of physical port that the ethernet cable is connected to.
(None, fei0, fei1, fei2)

Backup NIC Interface This is to accommodate the second onboard NIC. (None, fei0, fei1, fei2)

Once a new drop is created, a Drop Point must be added for the primary and partner to provide a
drop status (DU) point record type.

9.5.5 T O E NTER D ROPS I NFO FOR B ASE S TATIONS

1. For the Base Station, enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.
3. The New [Drops] dialog box will look similar to the one in To Enter Drops Info for Operator
Station (see page 128).

Base Station Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Operator Station, Sim
Operator Station, or Base Station).

126 OW240_60
 9.5 To Insert a Drop

Field Description

Maximum Point Limit Not applicable for Operator or Base Station drops (Normal, Expanded).
Local Data Servers Read-only field which tells if the drop has been defined as a local data
server (No, Yes).
Local Alarm Collector Read-only field which tells if the drop has been defined as a local alarm
collector (No, Primary, Partner, Both).
PRIMARY
Drop ID Drop number of the new drop (1-254).
Computer Name Name of a new machine or computer.
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 Not Applicable.
Ethers Address
PARTNER
Partner ID If the station drop has a partner drop, it is identified in this field (1-254).
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network Not Applicable.
Ethers Address

Once a new drop is created, a Drop Point (primary and partner (if applicable)) must be added to
provide a drop status (DU) point record type.

OW240_60 127
9.5 To Insert a Drop

9.5.6 T O E NTER D ROPS I NFO FOR O PERATOR S TATION

1. For the Operator Station, enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.

Figure 45: New Operator Stations and Base Station Drop Dialog Box

New Operator Station Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Operator Station, Sim
Operator Station, or Base Station).
Maximum Point Limit Not applicable for Operator or Base Station drops (Normal, Expanded).
Local Data Servers Read-only field which tells if the drop has been defined as a local data
server (No, Yes).

128 OW240_60
 9.5 To Insert a Drop

Field Description

Local Alarm Collector Read-only field which tells if the drop has been defined as a local alarm
collector (No, Primary, Partner, Both).
PRIMARY
Drop ID Drop number of the new drop (1-254).
Computer Name Name of a new machine or computer.
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 Not Applicable.
Ethers Address
PARTNER
Partner ID If the station drop has a partner drop, it is identified in this field (1-254).
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network Not Applicable.
Ethers Address

Once a new drop is created, a Drop Point (primary and partner (if applicable)) must be added to
provide a drop status (DU) point record type.

OW240_60 129
9.5 To Insert a Drop

9.5.7 T O E NTER D ROPS I NFO FOR S IM O PERATOR S TATION

1. For the Sim Operator Station, enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.
3. The New [Drops] dialog box will look similar to the one in To Enter Drops Info for Operator
Station (see page 128).

Figure 46: New Operator Stations and Base Station Drop Dialog Box

New Sim Operator Station Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Operator Station, Sim
Operator Station, or Base Station).
Maximum Point Limit Not applicable for Operator or Base Station drops (Normal, Expanded).

130 OW240_60
 9.5 To Insert a Drop

Field Description

Local Data Servers Read-only field which tells if the drop has been defined as a local data
server (No, Yes).
Local Alarm Collector Read-only field which tells if the drop has been defined as a local alarm
collector (No, Primary, Partner, Both).
PRIMARY
Drop ID Drop number of the new drop (1-254).
Computer Name Name of a new machine or computer.
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
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 The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).
PARTNER
Partner ID If the station drop has a partner drop, it is identified in this field (1-254).
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 The Internet Protocol (IP) address for a drop is typically assigned by the
Address system administrator. The IP address consists of four groups of decimal
numbers and the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the
IP address can be any valid range.
This field is unavailable if there is no Partner Drop.
Ovation Network The format for the hardware address is:
Ethers 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 To
Determine NIC Address (see page 116).

Once a new drop is created, a Drop Point (primary and partner (if applicable)) must be added to
provide a drop status (DU) point record type.

OW240_60 131
9.5 To Insert a Drop

9.5.8 V IRTUAL C ONTROLLER & V IRTUAL C ONTROLLER H OST

The Ovation Virtual Controller Host provides direction and guidance to Virtual Controllers and
permits them to mimic the operation of actual Ovation Controllers. Host machines co-ordinate the
activity of Virtual Controllers.

A Virtual Controller is a software representation of an actual or real Ovation Controller, but no

controller hardware is required.

Virtual Controllers have all the same functionality as real controllers but do not have the ability to
actually connect to the plant I/O. A Virtual Controller replicates the operation of actual Ovation
controllers providing an identical representation of an actual Ovation Controller. (See Ovation
Virtual Controller User Guide.)

132 OW240_60
 9.5 To Insert a Drop

TO ENTER DROPS INFO FOR THE VIRTUAL CONTROLLER HOST

1. Enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.

Figure 47: New Virtual Controller Host Drop Dialog Box

OW240_60 133
9.5 To Insert a Drop

Once a new drop is created, a Drop Point must be added to provide a drop status (DU) point
record type.

Note: A Virtual Controller Host can not be redundant.

New Virtual Controller Host Drop Dialog Box Fields

Field Description

Drop Type Pull-down menu with drop type selection (Virtual Controller Host).
Maximum Point Limit Not applicable for Operator or Base Station drops (Normal,
Expanded).
Local Data Servers Read-only field which tells if the drop has been defined as a local
data server (No, Yes).
Local Alarm Collector Read-only field which tells if the drop has been defined as a local
alarm collector (No, Primary, Partner, Both).
PRIMARY
Drop ID Drop number of the new drop (1-254).
Computer Name Name of a new machine or computer.
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 the format is:
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 Applicable.
Address
PARTNER
Partner ID If the station drop has a partner drop, it is identified in this field (1-
254). (0) for Virtual Controller Host.
Computer Sid Read only field added by the system. ID for domain name server.
Blank for Host.
Computer Sid (cont) Read only field added by the system. ID for domain name server.
Blank for Host.
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 the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet),
the IP address can be any valid range.
This Field Blank for Host.

134 OW240_60
 9.5 To Insert a Drop

Field Description

Ovation Network Ethers Not Applicable.

Address
VIRTUAL CONTROLLER
HOST
TCP port used for communication to Virtual Controllers.
Port
Master Virtual Controller Pull down list of all configured Virtual controller Hosts. One Host is
Host designated as the Master Host to coordinate timing between all
other hosts on the Network. Necessary on systems with more than
one Host.
Master Virtual Controller TCP port used for communication to Virtual Controllers. (Default -
Host Port 6001)
VIRTUAL CONTROLLER 1
Virtual Controller at Index 1 Read only field, specifies drop name configuration for this index.
Port TCP port used for communication to Virtual Controllers. (Default -
6010)
Virtual Controller at Index 2-5 Read only field, specifies drop name configuration for this index.
Port 2-5 TCP port used for communication to Virtual Controllers. (Default -
6010)

OW240_60 135
9.5 To Insert a Drop

TO ENTER DROPS INFO FOR THE VIRTUAL CONTROLLER

1. Enter the appropriate information for the selected drop type.
2. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window. A new <DROP#> folder will now appear
under the Drops folder.

New Virtual Controller Drop Dialog Box

See New Virtual Controller Host Drop Dialog Box Fields for applicable field information.

Once a new drop is created, a Drop Point must be added to provide a drop status (DU) point
record type.

New Virtual Controller Drop Dialog Box

Field Description

Drop Type Pull-down menu with drop type selection (Virtual Controller Host).
Maximum Point Limit Not applicable for Operator or Base Station drops (Normal,
Expanded).
PRIMARY
Drop ID Drop number of the new drop (1-254).

136 OW240_60
 9.5 To Insert a Drop

Field Description

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 the format is:
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 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 To
Determine NIC Address (see page 116).
PARTNER
Partner ID If the station drop has a partner drop, it is identified in this field (1-
254). (0) for Virtual Controller Host.
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 the format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet),
the IP address can be any valid range.
This Field Blank for Host.
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).
VIRTUAL CONTROLLER
HOST
Virtual Controller Host Drop name. (DropXXX).
Virtual Controller Host
Virtual Controller Index Virtual Controller Host Index Number. (1-5)

OW240_60 137
9.6 To Insert a Drop Point

9.6 TO INSERT A DROP POINT

Use the following procedure to create a Drop Point:

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the Points folder for the new drop.
{Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Points]
4. Right click on the Drop Point folder and select Insert New from the resulting pop-up menu.
5. The Insert New Drop Point Wizard appears (see Typical Wizard Dialog Box (see page 31)).
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 its number).
à Select the appropriate Drop Number to correspond with the Point Name entry.

138 OW240_60
 9.6 To Insert a Drop Point

6. After the required information is provided, select Finish.

7. 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.
8. Select the Apply button to save these settings without closing the window, or select the Ok
button to save the settings and close the window.
9. Repeat the Insert New Drop Point procedure (Steps 1 through 6) if there is a Partner Drop.

Figure 48: New Drop Point Dialog Box

10. Load the drop by using the Right-click menu.

New Drop Point Dialog Box

Tab Field Description

Point Point Alias Sixteen character alias for the point name.
Description This maps directly to the ED field of the point record
and can be up to 30 characters.
Characteristics This 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 8 alphanumeric characters can be used and
the first character must be a letter (A - Z, the dash
character can be used also).
Drop Number This is the drop number of the originating drop of
the point. (1-254).
Partner Drop This field identifies the drop number of the partner
drop (if applicable)

OW240_60 139
9.7 To Modify a Drop

Tab Field Description

Security Security Group Represents the defined security groups for each
point in the system.
Note: At least one Security Group must be selected
to allow Point modification.
Ancillary Ancillary Additional user defined information about the
points.
eDB Collection Enabled A check box that specifies if a point will be collected
by eDB.
Scan Frequency Frequency (in milli-seconds) at which a specific
point will be scanned by the eDB on the Highway to
determine if it meets collection criteria.
Alarm Alarm Priority Sets the alarm priority field (1- 8, 1 being the
Highest).
Display This field defines the applicable summary diagram
which is sent to the process diagram system.
Signal Diagram This field defines the signal diagram number.

9.7 TO MODIFY A DROP

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the Drop folder to be modified:
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click the Drop folder and select Open. The Drop dialog box appears.
5. Make necessary changes and select Ok or Apply.
6. Download (see page 38) configuration changes to the drop by using the Right click menu.
7. Reboot (see page 48) (as necessary) using the Right click menu.

140 OW240_60
S E C T I O N 10

DEFINING AND CONFIGURING THE I/O DEVICES

In This Section

Planning I/O for Your System............................................................................. 142

Ovation I/O Base Types ..................................................................................... 143
Addressing the Ovation I/O Modules ................................................................. 144
Guidelines for Positioning Modules.................................................................... 150
Creating Local or Remote Ovation I/O Devices ................................................. 151
Third Party Devices............................................................................................ 151
Creating Foundation Fieldbus Devices .............................................................. 151
Modifying an I/O Device .....................................................................................152
Modifying an External Ovation Networks Device ............................................... 152

OW240_60 141
10.1 Planning I/O for Your System

10.1 P L A N N I N G I/O FOR YOUR SYSTEM

The I/O (Input/Output) Devices folder contains tools used to define the I/O modules for the
Ovation system. The I/O Device folders contain Setup Wizards and dialog boxes that provide
visual representation of the I/O Devices for an Ovation system.

Before the I/O Devices folder can be used to define the I/O hardware, a plan should be designed
that lists the I/O needed for your Ovation system. The elements that will be included in the table
below.

After the plan has been designed, this information is entered into the I/O Devices portion of the
system hierarchy to define the I/O for your Ovation system. I/O Devices are defined individually
for each drop.

During configuration, the following elements are assigned point names by the system to identify
the elements to the Ovation database:
ƒ Each PCI card in the Controller is assigned a Node (RN) Record Type point name. The RN
record type is used because it contains bits that are used to monitor the Controller power
supply.
ƒ Each remote node is assigned a Node (RN) Record Type point name. The RN record type is
used because it contains bits that are used to monitor the node power supply.
ƒ Each Ovation I/O module is given a Module (RM) Record Type point name. The RM point is
used to configure the I/O module and to provide status/alarm information about the I/O
module. Points can then be assigned to each module by using the Hardware Tab in the
Points folder.

I/O Elements

Element Description

I/O Device I/O Interface Card (IOIC) or I/O Driver used to transfer data between a
Controller and I/O modules or a third party communications interface. These
I/O devices are located in a Controller drop with a maximum of five total I/O
Drivers per drop, only two of which can be used for physical I/O (for
example, Q-Line or Ovation I/O).
For local Q-Line I/O, the applicable hardware is a PCQL PCI card which can
support up to four crates of Q-Line I/O cards.
For remote Q-Line I/O, the applicable hardware is a PCRR PCI card which
can support up to eight remote Q-Line nodes.
For local Ovation I/O, the applicable hardware is a PCRL PCI card which can
support up to eight branches of Ovation I/O cards.
For remote Ovation I/O, the applicable hardware is a PCRR PCI card which
can support up to eight remote Ovation nodes.
For third party I/O devices, select the applicable I/O Device Type from the I/O
Device Type dialog box. There are no elements under the device and it
cannot be configured or serviced via the I/O Device folder.
Crate Location in I/O cabinet where Q-Line I/O modules are placed. A maximum of
four crates can be defined for each PCQL (local Q-Line I/O Device) and for
each Remote Q-Line I/O Node. Select on the Crate element to display all the
slots (12) available for that crate.

142 OW240_60
 10.2 Ovation I/O Base Types

Element Description

Branch Location in I/O cabinets where Ovation I/O modules are placed.
A maximum of Eight branches can be defined for each PCRL card (local
Ovation I/O Device) and for each Remote Ovation I/O Node.
Click on the Branch element to display all the slots (8) available for that
branch.
Node A segregated portion of a Controller’s I/O hardware which is supported by the
PCRR PCI card. A maximum of eight nodes can be defined for each PCRR
card.
Each Ovation I/O node can contain up to eight branches of Ovation I/O
hardware.
Each Q-Line I/O node can contain up to four crates of Q-Line I/O hardware.
Slot Position in branch (Ovation I/O) or crate (Q-Line) where module is located.
A maximum of 48 slots can be defined for each local Q-Line I/O device (four
crates of 12 Q-Line I/O cards).
A maximum of 64 slots can be defined for each local Ovation I/O device (eight
branches of eight Ovation I/O cards).
A maximum of 512 slots can be defined for each remote Ovation I/O device
(eight nodes of eight branches of eight Ovation I/O cards).
A maximum of 384 slots can be defined for each remote Q-Line I/O Device
(eight nodes of four crates of 12 Q-Line I/O cards).

10.2 O V A T I O N I/O B A S E T Y P E S
Ovation I/O bases house the Ovation I/O modules and provide a mechanism for the user to land
field wiring and connect field signals to the Ovation I/O. Series of bases can be connected
together to form a “branch” of Ovation I/O.

The Ovation system supports two different types of bases:

ƒ Standard I/O base.
ƒ Relay Output base.
The different bases can be mixed within a given I/O branch and cabinet. There are restrictions as
to how these bases can be mixed. (See Planning and Installing Your Ovation System (For Use
with FDDI).) (See Planning and Installing Your Ovation System (For Use with Fast Ethernet).)

10.2.1 S TANDARD I/O B ASE

The Standard I/O base houses up to two standard I/O modules as seen below. Ovation I/O
modules supported in the standard I/O bases include analog input, analog output, contact input,
digital input, digital output, loop interface, pulse accumulator, RTD interface, sequence of events,
serial link controller, servo driver, speed detector, and valve positioner.

Each Standard I/O module is assigned a logical address. Since each Standard I/O base can
house two Ovation I/O modules, a Standard I/O base occupies two logical module addresses.

OW240_60 143
10.3 Addressing the Ovation I/O Modules

10.2.2 R ELAY O UTPUT B ASE

The Relay Output base houses one module and requires one I/O address. The Relay Output
base is longer than the Standard I/O base unit because of the additional space required to house
the relays. Although the Relay Output base only contains one module, it is 1.5 times longer than
the Standard I/O module base.

Figure 49: Standard I/O and Relay Output Bases

10.3 A D D R E S S I N G THE O V A T I O N I/O M O D U L E S

The System assigns an address to each Ovation module defined by the Studio. This address is
based on the logical location of the module with respect to the Ovation Controller and is used by
the Studio to configure the hardware information for a point.

A standard I/O base consists of two logical modules; and a Relay Output base has one logical
module.

10.3.1 A DDRESSING F ORMAT

The logical I/O address is composed of three numbers (four when remote I/O is used) separated
by decimals and in the following format:
ƒ D.N.B.S where:
D =Device number assigned to the PCI card (1-5).
N = Node (only used in Remote I/O; 1 through 8).
B = Branch (1 through 8).
S = Slot where module is located (1 through 8 for Ovation I/O)
(1 through 12 for Q-Line I/O).

144 OW240_60
 10.3 Addressing the Ovation I/O Modules

ƒ Standard I/O Base Assemblies

The I/O addressing for the Ovation database is determined from the positions of the bases
installed in the cabinets. Installation of standard I/O bases requires at least two I/O module
addresses on a branch. Their I/O module position must always start on odd positions.

I/O modules should be in the left-most branch of each side of a cabinet from the TOP down to the
BOTTOM. I/O modules in the right-most branch of each side of a cabinet are addressed from the
BOTTOM up to the TOP.

Emerson Process Management recommends that all bases (typically four) be installed in the right
side of a cabinet, even if they are not all filled with I/O modules. This will prevent disruption of the
database if additional I/O modules are installed in the future.
ƒ Relay Output Base Assemblies
Relay Output bases can be located before or after standard I/O bases. Installation of relay output
bases requires one I/O module address on a branch and can begin on an odd or even position.

Note: Physical cabinet space may limit the maximum number of bases in a given cabinet style.

When a relay output base is used before a standard I/O base, an even number of relay output
bases must be used so the I/O base will start at an odd position. If a standard I/O base follows an
odd number of relay output bases, the configuration is incorrect and will not work (see the figure
below for examples).

Figure 50: I/O and Relay Module Configuration Examples

OW240_60 145
10.3 Addressing the Ovation I/O Modules

10.3.2 E XAMPLES OF M ODULE A DDRESSES (C ONTROLLER C ABINET )

PCI Card 1 is directly connected to Branches 1 and 2, and controls Branches 3 through 8 via a
connector on the right side of the Controller enclosure.

PCI Card 2 controls Branches 1 through 8 via a connector on the left side of the Controller
enclosure.

Figure 51: I/O Address Examples (Controller Cabinent)

ƒ Module A address = 1.1.2.
ƒ Module B address = 1.2.4.
ƒ Module C address = 1.3.6.

146 OW240_60
 10.3 Addressing the Ovation I/O Modules

10.3.3 E XAMPLES OF M ODULE A DDRESSES (E XTENDED I/O C ABINET )

Note: ROP transition panel is used when configuring cabinets (front of cabinet).

Figure 52: I/O Address Examples (Extended I/O Cabinent)

ƒ Module D address = 1.5.6.
ƒ Module E address = 1.6.1.
ƒ Module F address = 1.8.8.

OW240_60 147
10.3 Addressing the Ovation I/O Modules

10.3.4 E XAMPLES OF M ODULE A DDRESSES (R EMOTE N ODE C ABINET )

Note: ROP transition panel is used when configuring cabinets (front of cabinet). Branch 7 in the
last figure (back of cabinet) is composed solely of relay panels using RRP and RRB transition
panels. (See Ovation I/O Reference).

The Node address (1 through 8) for Ovation remote I/O is determined by where the Node is
connected to the MAU Attachment Unit (located in the Controller cabinet). The Node Selector
Switch in the Remote Node Cabinet is then set to match the connection position. (See Ovation I/O
Reference Manual.) in the Ovation Remote I/O section for details about addresses for remote
nodes.

Assume the PCRR card is in position 1, and the Node is in MAU position 1 for the following
examples:
ƒ Module G address = 1.1.1.3.
ƒ Module H address = 1.1.3.5.

148 OW240_60
 10.3 Addressing the Ovation I/O Modules

10.3.5 E XAMPLES OF M ODULE A DDRESSES (R ELAY O UTPUT M ODULES )

Note: ROP transition panel is used when configuring cabinets (front of cabinet). Branch 7 (back
of cabinet) is composed solely of relay panels using RRP and RRB transition panels. (See
Ovation I/O Reference).

Figure 53: I/O Address Examples (Relay Output Cabinent)

OW240_60 149
10.4 Guidelines for Positioning Modules

Assume the PCRL card is in position 1, and the cable is connected from Branch 4 of PCI Card 1
card:
ƒ Module I address = 1.5.3.
ƒ Module J address = 1.6.2.
ƒ Module K address = 1.7.6.

Note: The back of this extended cabinet contains only one branch of relay output modules due
to physical limitations.

The relay output modules can also be used with the RRP and RRB transition panels (instead of
the ROP or TND panel). Using the RRP and RRB transition panel allows one “branch” of up to
eight relay bases to be housed in a single side of an Ovation ventilated extended cabinet in two
columns of four bases.

10.3.6 A DDRESSING THE Q-L INE I/O M ODULES

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 used to determine the jumper settings. This address must
be entered on the Q-line module configuration window. (See Ovation Q-Line Installation Manual.)

10.4 G U I D E L I N E S FOR POSITIONING MODULES

The following guidelines should be observed when selecting module positions.
ƒ Modules are placed from top to bottom on the left side of a cabinet and from bottom to top
on the right side of a cabinet.
ƒ If Relay Output modules are mixed with Standard I/O modules on the same branch, the
Standard I/O module base must ALWAYS start in an odd-numbered module position on the
branch (positions 1/2, 3/4, 5/6, or 7/8).
Relay Output modules can be placed in odd or even numbered positions. For example,
modules can begin in 1, 2, 3, 4, 5, 6, 7, or 8 slots.

150 OW240_60
 10.5 Creating Local or Remote Ovation I/O Devices

ƒ Physical cabinet size and branch power requirements may limit the number of modules that
can be configured in a branch.

Figure 54: Examples of Cabinets with Standard I/O and Relay Modules

10.5 C R E A T I N G L O C A L OR R E M O T E O V A T I O N I/O D E V I C E S
The Ovation Controller book addresses creating each I/O device/connector created under the I/O
Device folder. (See Ovation Controller User Guide.)

10.6 T H I R D P A R T Y D E V I C E S
The corresponding device must exist for each I/O device/connector created under the I/O Device
folder. (See Ovation Controller User Guide.)

10.7 C R E A T I N G F O U N D A T I O N F I E L D B U S D E V I C E S
The Foundation Fieldbus book addresses configuring the Foundation Fieldbus Devices and
working with the Fieldbus Engineering. (See Ovation Foundation Fieldbus User Guide.)

OW240_60 151
10.8 Modifying an I/O Device

10.8 M O D I F Y I N G AN I/O D E V I C E
After an I/O device has been created and loaded to the target drop, it may be necessary to make
changes.

10.8.1 T O M ODIFY AN I/O D EVICE

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Use the following path to access the I/O folder or subfolder to be modified:
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[I/O Devices]
Unique I/O Device Name
4. Right click the appropriate folder and select Open. A dialog box appears.
5. Make necessary changes (for a description of the tabs found in the Ovation Module dialog
box, see Ovation Modules (see page 217)) and select Ok or Apply.

10.9 M O D I F Y I N G AN EXTERNAL OVATION NETWORKS DEVICE

For external networks modification information. (See Ovation Multiple Networks User Guide.)

152 OW240_60
S E C T I O N 11

BUILDING POINTS

In This Section

Point Builder Philosophy .................................................................................... 153

To Create a Point ............................................................................................... 156
Point Types and Dialog Box Tab Descriptions................................................... 159
Configuring Complex Points............................................................................... 186
Third Party Points............................................................................................... 188
Modifying a Point................................................................................................ 189

11.1 P O I N T B U I L D E R P H I L O S O P H Y
A Point is a record in the global database that contains a value (such as an input or output) and
other related data. There are currently 11 point types in Ovation.

Each point type has its own dialog box with distinct tabs and fields. Thus each Point Dialog Type
will have its own Point Dialog Box tabs, fields, and descriptions. The table under Point Dialog
Box Tabs (see page 159) lists all possible tabs and all the fields available for each Point Type.
Not all tabs will appear in the dialog box for each Point type. (See Ovation Record Types
Reference Manual.)

11.1.1 I/O P OINT H ARDWARE M APPING

The Points folder allows you to identify the I/O parameters, hardware and configuration of each
point (see To Create a Point (see page 156)). This includes:
ƒ I/O Type (Q-Line, Ovation, and third party).
ƒ I/O Location and Card Type, or identification of third-party driver.
ƒ I/O Channel.
The Points folder calculates hardware addresses. It also ensures that the card type is valid for the
point. The following information is also provided:
ƒ Sensor Type.
ƒ Conversion Coefficients.
ƒ Instrumentation Limit/Range and Engineering.

OW240_60 153
11.1 Point Builder Philosophy

11.1.2 P OINT N AMING R ULES

The following rules must be followed to ensure valid point names:

1. All points in the Ovation system are fully specified by three parameters, a sixteen character
maximum point name, a six character maximum unit, and an eight character maximum
network name. The fully qualified name will be of the format “name. unit@network.” The (.)
and @ are therefore reserved characters for point names. However, when inserting a point
into the Ovation Studio, fully qualified names should not be entered. Only the point name
parameter is used.
2. A point name cannot be a reserved word or contain reserved characters.
à For a listing of reserved graphic words, (See Ovation Graphics Language Reference
Manual.) (Character Tables (see page 154)).
à For a listing of reserved point name characters (Character Tables (see page 154)).
3. Characters may be any combination of alphabetic, numeric (0 - 9), or special punctuation
characters (Character Tables (see page 154)).
4. Do not begin User Defined Points’ or Control Builder Default Points’ names with OCB.
5. Some special characters that may be used are listed in (Character Tables (see page 154))
under Valid Point Name Characters.
6. Point names are not case sensitive. Lower case characters will be converted to upper case.
For example, point name A0113 is considered the same as a0113.
7. Do not include a space in a point name.

CHARACTER TABLES

Reserved Point Name Characters

Character ASCII Character ASCII Character ASCII

(in HEX) (in HEX) (in HEX)

$ 24 * 2A ~ 7E
% 25 , 2C ‘ 60
& 26 @ 40 ’ 27
. 2E \ 5C “ 22

Valid Point Name Characters

Character ASCII Character ASCII Character ASCII

(in HEX) (in HEX) (in HEX)

! 21 ? 3F V 56
# 23 A 41 W 57
( 28 B 42 X 58
) 29 C 43 Y 59
+ 2B D 44 Z 5A

154 OW240_60
 11.1 Point Builder Philosophy

Character ASCII Character ASCII Character ASCII

(in HEX) (in HEX) (in HEX)

- 2D E 45 [ 5B
/ 2F F 46 ] 5D
0 30 G 47 ^ 5E
1 31 H 48 _ 5F
2 32 I 49 { 7B
3 33 J 4A | 7C
4 34 K 4B } 7D
5 35 L 4C
6 36 M 4D
7 37 N 4E
8 38 O 4F
9 39 P P
: 3A Q 51
; 3B R 52
< 3C S 53

= 3D T 54
> 3E U 55

OW240_60 155
11.2 To Create a Point

11.2 T O C R E A T E A POINT
The following procedure is an example of creating or adding a point to the system (specifically,
an Analog point, but the procedure is applicable for all point types.), and does not detail specific
field input. 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 Point Dialog Box Tabs.

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the appropriate Drops folder and open the Points folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Points]
Unique Point Name
4. Right click the desired Points folder (in this case Analog Points) and select Insert New. The
Insert New "Analog" Points Wizard appears (see Typical Wizard Dialog Box (see page 31)).
5. Enter the Point Name (see page 154) in the Point Name Value field.
6. Select the frequency from the pull-down menu.
à S - Slow (1 second).
à F - Fast (0.1 second).
à A - Aperiodic (as needed).

156 OW240_60
 11.2 To Create a Point

7. Select Finish and the New Analog Point dialog box appears.

Note: When looking through the tabs some items are already filled in. The dialog box that
comes up is a default, and the defaults can be changed to help automate point building, see
Defaults View Bar (see page 23).

8. Find the tabs needed for a particular Point Type using the table in Point Types and Dialog
Box Tab Descriptions (see page 159), then go to the appropriate tab to help in entering the
correct values.
9. Make sure to go to Configuring Complex Points (see page 186) to access special
configuration for Analog Input Points (see page 186), Analog Output Points (see page
187), Analog/Thermocouple Points (see page 187), Digital Input Points (see page 187),
Digital Output Points (see page 188), Pulse Accumulator Points (see page 188), and RTD
Points (see page 188).
10. Select the Apply or Ok button to add the point to the database. 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.

Note: The point will not be available on the Ovation highway until it is loaded using the
procedures discussed in The Ovation Developer Studio Components (see page 11).

11.2.1 P OINT D IALOG B OX

Each point type has specific properties and configurations that differentiate it from other point
types. Point information is displayed in the Point dialog box. Notice the tabs across the bottom of
the Points dialog box.

Figure 55: Point Dialog Box

Each Point dialog box has tabs representing various categories of attributes related to that point.
The table below identifies all tabs and provides a brief description of each, for more information
see Point Dialog Box Tabs.

Points Folder Tab Descriptions

Tabs Description

Alarm Sets the various alarm priority fields.

OW240_60 157
11.2 To Create a Point

Tabs Description

Ancillary Additional user defined information about the point.

ASCII Params Represents the ASCII parameters of the algorithm. Labels are dependent on
the algorithm name chosen on the Config tab.
Byte Params Represents the byte parameters of the algorithm. Labels are dependent on
the algorithm name chosen on the Config tab.
Config Used to establish the various configurations of the points.
Display Represents the type of display (standard, exponential, or
technical), scale limits, Engineering Units, Set and Reset descriptions,
Summary and Signal diagrams.
Hardware Defines the I/O hardware configuration for the point.
eDB Defines if and how the process points are to be collected by the various eDB
Station “history subsystems.”
Initial Used to establish the initial values of the various points.
Instrumentation Used to establish hardware information, including sensor limits.
Int Params Represents the integer parameters of the algorithm. Labels are dependent on
the algorithm name chosen on the config tab.
Limits Specifies the limits of point records.
Plant Mode Collection of parameters that can be set differently for each of the six modes.
Point Information about the point.
Real Params Represents the real (floating point) parameters of the algorithm. Labels are
dependent on the algorithm name chosen on the config tab.
Security Represents the defined security groups for each point in the system.

158 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3 P O I N T T Y P E S AND DIALOG BOX TAB DESCRIPTIONS

The Tabs are listed in alphabetical order, not in the order that they appear in the dialog boxes, as
that may change. Additionally, fields are also listed alphabetically by grouping.

Point Types and Dialog Box Tab Descriptions

Point P C S A e H I A I m L D P Byte,
Type o o e n D a n l n e i i l Int.,
i n c c B r i a s n m s a Real,
n f u i d t r t t i p n &
t i r l w i m r a t l t ASCII
g i l a a u t s a M Prams
t a r l - i y o
y r e o d
y n e

Analog X X X X X X X X X X X

Deluxe X X X X X X X X X X X X
Analog
Digital X X X X X X X X X

Deluxe X X X X X X X X X X
Digital
Packed X X X X X X X X X

Deluxe X X X X X X X X X X
Packed
Packed X X X X X
Digital
Algorith X X X X X
m
Drop X X X X X X

Module X X X X X X X X

Node X X X X X X X X

11.3.1 A NALOG P OINT T YPE AND D IALOG B OX T ABS

Analog Point Type and Dialog Box Tabs

Analog Point

Point X

Configure X

OW240_60 159
11.3 Point Types and Dialog Box Tab Descriptions

Analog Point

Security X

Ancillary X

eDB X

Hardware X

Initial X

Alarm X

Instrumentation X

Limits X

Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Analog Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

11.3.2 D ELUXE A NALOG P OINT T YPE AND D IALOG B OX T ABS

Deluxe Analog Point Type and Dialog Box Tabs

Deluxe Analog Point

160 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Deluxe Analog Point

Point X

Configure X

Security X

Ancillary X

eDB X

Hardware X

Initial X

Alarm X

Instrumentation X

Limits X

Display X

Plant Mode X

Byte Params.
Initial Params
Real Params
ASCII Params

Deluxe Analog Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

OW240_60 161
11.3 Point Types and Dialog Box Tab Descriptions

11.3.3 D IGITAL P OINT T YPE AND D IALOG B OX T ABS

Digital Point Type and Dialog Box Tabs

Digital Point

Point X

Configure X

Security X

Ancillary X

eDB X

Hardware X

Initial X

Alarm X

Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Digital Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

162 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3.4 P ACKED D IGITAL P OINT T YPE AND D IALOG B OX T ABS

Packed Digital Point Type and Dialog Box Tabs

Packed Digital Point

Point X

Configure
Security X

Ancillary X

eDB
Hardware
Initial X

Alarm
Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Packed Digital Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

OW240_60 163
11.3 Point Types and Dialog Box Tab Descriptions

11.3.5 D ELUXE D IGITAL P OINT T YPE AND D IALOG B OX T ABS

Deluxe Digital Point Type and Dialog Box Tabs

Deluxe Digital Point

Point X

Configure X

Security X

Ancillary X

eDB X

Hardware X

Initial X

Alarm X

Instrumentation
Limits
Display X

Plant Mode X

Byte Params.
Initial Params
Real Params
ASCII Params

11.3.6 P ACKED P OINT T YPE AND D IALOG B OX T ABS

Packed Point Type and Dialog Box Tabs

Packed Point

Point X

Configure X

Security X

Ancillary X

eDB X

164 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Packed Point

Hardware X

Initial X

Alarm X

Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Packed Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

11.3.7 D ELUXE P ACKED P OINT T YPE AND D IALOG B OX T ABS

Deluxe Packed Point Type and Dialog Box Tabs

Deluxe Packed Point

Point X

Configure X

Security X

OW240_60 165
11.3 Point Types and Dialog Box Tab Descriptions

Deluxe Packed Point

Ancillary X

eDB X

Hardware X

Initial X

Alarm X

Instrumentation
Limits
Display X

Plant Mode X

Byte Params.
Initial Params
Real Params
ASCII Params

Deluxe Packed Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

11.3.8 A LGORITHM P OINT T YPE AND D IALOG B OX T ABS

Algorithm Point Type and Dialog Box Tabs

Algorithm Point

Point X

166 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Algorithm Point

Configure X

Security X

Ancillary X

eDB
Hardware
Initial
Alarm
Instrumentation
Limits
Display
Plant Mode
Byte Params. X

Initial Params X

Real Params X

ASCII Params X

Algorithm Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Frequency Slow, Fast, or Aperiodic.

11.3.9 D ROP P OINT T YPE AND D IALOG B OX T ABS

Drop Point Type and Dialog Box Tabs

Drop Point

Point X

Configure

OW240_60 167
11.3 Point Types and Dialog Box Tab Descriptions

Drop Point

Security X

Ancillary X

eDB X

Hardware
Initial
Alarm X

Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Drop Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Drop Number Number of drop
Partner drop Number of Partner Drop

11.3.10 M ODULE P OINT T YPE AND D IALOG B OX T ABS

Module Point Type and Dialog Box Tabs

Module Point

Point X

168 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Module Point

Configure X

Security X

Ancillary X

eDB X

Hardware X

Initial
Alarm X

Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Module Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

OW240_60 169
11.3 Point Types and Dialog Box Tab Descriptions

11.3.11 N ODE P OINT T YPE AND D IALOG B OX T ABS

Node Point Type and Dialog Box Tabs

Node Point

Point X

Configure X

Security X

Ancillary X

eDB X

Hardware X

Initial
Alarm X

Instrumentation
Limits
Display X

Plant Mode
Byte Params.
Initial Params
Real Params
ASCII Params

Node Point Dialog Box Descriptions

Attribute Value

Point Alias Name given the point.

Description Information to help identify
the point.
Characteristics Other identifying
information.
Frequency Slow, Fast, or Aperiodic.
Opp Rate Slow, Fast, Aperiodic or
User defined.

170 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3.12 A LARM T AB

Alarm Tab

Tab Field Description

Alarm Normal:
Alarm delay time. This field sets the initial alarm delay time, in seconds. This
delay is the time between the alarm being detected and being
reported in alarm. Valid time entry is from 0 to 65535
seconds. This field does not apply to sensor alarms since
they never delay or cutout from reporting.
Cutout:
Alarm cutout delay This field sets the alarm cutout delay time, in seconds. This
time. delay is the time after the cutout is released before the alarm
is actually reported.
This field is the point used as a cutout for the base point
Alarm cutout name. (digital or packed point).
If Alarm Cutout is a packed point, the bit number that is
Alarm cutout bit. entered in this field is mapped to bits 28-32 of the SJ field.
Priorities: Analog points can have up to 5 different high and 5 different
low priorities. The priority may be from 1 to 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 to 4 and
High User Alarm, and Low Limit 1 to 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 These fields map to the various alarm priority fields of the
point record. (AP, P6, P7, P8)
Low alarm user This field maps to the user alarm priority field of the point
priority record. (P9)
These fields map to the various alarm priority fields of the
High alarm priority 1-4 point record. (AP, P6, P7, P8)

This field maps to the user alarm priority fields of the point
High alarm user record. (P9)
priority
These fields map to the various alarm priority fields of the
point record. (AP)
Alarm priority

OW240_60 171
11.3 Point Types and Dialog Box Tab Descriptions

11.3.13 A NCILLARY T AB

Ancillary Tab

Tab Field Description

Ancillary Fields appear only if they These are user defined fields that provide additional
have been created as information about the point. Up to 100 fields can be
described in To Insert a created.
System (see page 66).

11.3.14 ASCII P ARAMS T AB

ASCII Params Tab

Tab Field Description

ASCII 1 through Represent the ASCII parameters of the algorithm. Only apply to the
Params 4 algorithms selected in the Config tab. This allows you to see what
fields apply to the algorithm.

11.3.15 B YTE P ARAMS T AB

Byte Params Tab

Tab Field Description

Byte 1 through Represent the byte parameters of the algorithm. Only apply to the
Params 16 algorithms selected in the Config tab. This allows you to see what
fields apply to the algorithm.

11.3.16 C ONFIG T AB

Config Tab

Tab Field Description

Config 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.
Alarm group mask Determines which bits of the packed point will alarm.
Algorithm name This field represents the name of the algorithm.
Int Parameter Reserved for Emerson use.

172 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Inverted The value read from or written to the I/O cards is

inverted if the corresponding bit is set in this field.
New Alarm/Limit
Configuration:
Auto Reset If this bit is set, the point will be automatically reset.
Auto Acknowledge If this bit is set, the point will be automatically
acknowledged.
Originating Sheet This field is reserved for Emerson use except in a Node
Point. In a Node Point, the signal diagram number is
derived from this field.
Oscillation count Indicates the number of oscillations allowed before the
(counts/min) point enters oscillation alarm. Must be a valid integer in
the range 0 through 65535.
Partner drop This field identifies the drop ID of the partner drop.
Power Check:
Power check enable for Used for the power check function for packed points.
bits
Used for the power check function for packed points.
Power check channel
(bit 1-16)
This field enables the power check.
Power check enable
Real Parameter Reserved for Emerson use.
Relay close delay time This field is used to set the relay close delay time, in
(msec) milliseconds.
Reset sum This maps directly to bit 2 of the EQ field of the point
record.
SOE:
SOE point This field is used to establish that the point is an SOE
point.
SOE 1 shot algorithm
This field maps directly to bit 3 of the EQ field.
SOE reporting option
This maps directly to the bits 5 and 6 of the EQ field of
the point record.
Status checking type N = no status checking.
0 = alarm on 0.
1= alarm on 1.
2 = state change only.
3 = alarm in transition from 0 to1.
4 = alarm in transition from 1 to 0.
Tunable This field defines whether or not the algorithm is
tunable.

OW240_60 173
11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Tuning diagram This field defines the number of the applicable tuning
diagram.

11.3.17 D ISPLAY T AB

Display Tab

Tab Field Description

Display Bit (0-15):

Set description (0-15) This field is the text description of the set state
of each bit of a packed point.
Packed points Reset This field is the text description of the reset state
description (0-15) of each bit of a packed point.

Packed points These fields are the text description of the

Description (0-15) individual bits.
Set description (Digital points) This field is the text description of the set state.

Reset description (Digital This field is the text description of the reset
points) state.
Digits Displayed This field represents the number of significant
digits to display for standard format.
Display Type This field represents the type of display
(standard, exponential, technical).
Engineering Units This is the text description of the engineering
units.
Maximum Scale This field scales the value of the point for
displays.
Minimum Scale This field scales the value of the point for
displays.
Signal Diagram This field defines the signal diagram number.
Summary Diagram This field defines the applicable summary
diagram which is sent to the process diagram
system.

174 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3.18 H ARDWARE T AB

Hardware Tab

Tab Field Description

Hardware Contact Type This is a labeling field for those who wire the system, the
information has no bearing on operation.
Ground This field is a label for those wiring the system; the information
See the
has no bearing on operation.
appropriate
“Controller Half Shell This field is a label for those wiring the system; the information
User Guide” has no bearing on operation.
for your I/O Access Text field for generic use of configuration on 3rd party devices.
system for Path the format is specific to the device type. For example,
more
information. AB PLC5 2 IN N7:02
Where:
AB = Allen Bradley TCP/IP driver, PLC5 = PLC5 communication
protocol, 2 = Connect to hostname “plc5-2”, IN = Read AB
register to process point, N7:02 = A-B register address.
Third party devices include:
Allen Bradley TCP/IP, RTP I/O, MHI, Modbus, GE Mark V
(described in WIN57), GE Mark VI (described in WIN57),
Toshiba, GE Genius
I/O Channel Used to specify the channel of the applicable I/O module.
I/O Module This field indicates which specific I/O card the point is attached
to.
I/O Task Index This field represents the processing task index used by the
Controller. Points which are assigned to a Digital Output module
must have an identical task index value for every point on the
same module.
I/O Type This field determines the I/O type of the point:
Q-Line, Ovation (R-Line), Third-Party (device), Null if the point is
not an I/O point.
Power Source This field is a label for those wiring the system; the information
has no bearing on operation.
Relay Module This field is a label for those wiring the system; the information
has no bearing on operation.
Terminal 1-6 This field is a label for those wiring the system; the information
has no bearing on operation.
Termination This field is a label for those wiring the system; the information
Type has no bearing on operation.
Register to Checking this box allows the entire 16 bits of a packed point to
Register be assigned to all 16 bits of a digital I/O module register.
Mapping

OW240_60 175
11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Point Name This field is the name of the point from where the data is being
(GE, MHI, retrieved, for example, L41BKRC_CPB.
Toshiba)
Type (GE, See Building a Points Folder for valid types.
MHI, Toshiba)
Point Index Read only field for internal use only.
(GE)
Controller This field is the name of GE Controller, for example, GA.
Name (GE)
Node Index This field is the number of the Node.
(GE)
Host Index Hostname index that was defined in the New Device Numbers
(AB, Modbus, window.
RTP I/O)
Datatype (GE, Used to interpret the data type, common types are Signed or
AB, Modbus) Unsigned.
Input or Output Indicates whether the slave value is read into a process point or
(AB, Modbus) written from a point.
Register In logical ASCII format for the Allen-Bradley driver.
Address (AB)
Slave Address Node address of the Modbus slave.
(Modbus)
Register Modbus coil or register number.
Number
(Modbus)
Byte Order Keywords that allow register byte order to be changed.
(Modbus)
Card Type RTP IO card type keyword.
(RTP I/O)
Device Device address of RTP card cage.
Address (RTP
I/O)
Card Slot For digital cards, this is the slot number for the card.
(RTP I/O)
For analog cards, this is the AD converter address of the card.
Channel Analog channel number. This field is only used for packed
Number (RTP points.
I/O)
Gain Code RTP gain code.
(RTP I/O)
Gate Card Slot For digital cards, it is the bit number of the card.
(RTP I/O)
For analog cards, it is the gate slot address of the card.

176 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3.19 E DB T AB

eDB Tab

Tab Field Description

eDB Collection:
Collection Specifies if a point will be collected by eDB.
enabled
(See eDB Frequency (in milliseconds) at which specific point will
Historian Scan Frequency be scanned by the eDB on the Highway to determine if
User Guide.) (milliseconds) it meets collection criteria.
Designates the rule that will be applied to an analog
Deadband point to determine how and if it will be stored. Valid
algorithm choices are FLOW, LOG, PCT_RANGE, POWER,
RADIATION, RATIO, and STANDARD. The rule
provides the formula that will be used in the collection
process.
Defined range that an analog point must exceed in
DEADBAND order to be collected by the eDB.
VALUE
Values that apply when a deadband algorithm of Flow,
Power, Radiation, and Log is chosen.
DB_K_VAL value
Values that apply when a deadband algorithm of Flow
or Log is chosen.
DB_N_VAL value
N Value for Power is set at 0.5.
N Value for Radiation is set at 10.
SOE:
Enabled This parameter specifies that the point is to be collected
by the SOE subsystem.

11.3.20 I NITIAL T AB

Initial Tab

Tab Field Description

Initial Initial Conditions:

Value This field establishes the initial first pass value of the point.

OW240_60 177
11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Initial status:
Periodic save This field represents whether or not the value of the point
should be periodically saved to flash.
Tagout This field establishes the initial tagout state of each bit (0-15) for
the point. Also valid for analog and digital points.
This field establishes the uncommissioned state of each bit (0-
Uncommissioned
15) for the point. Also valid for analog and digital points.

11.3.21 I NSTRUMENTATION T AB

Instrumentation Tab

Tab Field Description

Instru- Cold Junction

mentation Compensation:
CJ Compensation name This field identifies the cold-junction
compensation to be performed for the point.
CJC temperature units This field is used for cold-junction
compensation conversion.
CJC conversion These fields map directly to fields 7V and 8V of
coefficient 1-2 the point record and are used for cold junction
compensation.
Conversion Coefficient These values are specified in units of volts. If
1-6 the field _transmitter_ type and
thermocouple_units fields are specified, these
conversion coefficient fields are assigned
automatically based on a table lookup.
Otherwise, the fields can be specified
individually.

178 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Conversion:
Field transmitter type This field identifies the field transmitter type for
B or TB= use in standard thermocouple conversions. If
70% Platinum + 30% this field is specified, and the individual
Rhodium or conversion coefficient fields are not specified,
94% Platinum + 6% the conversion coefficient fields will be
Rhodium automatically assigned based on the
E or TE = thermocouple_units. The conversion type is set
Chromel/Constantan to the P5 field. If this field is not specified, the
J or TJ = Iron/Constantan conversion type must be specified individually.
K or TK = Chromel/Alumel
R or TR = Platinum+13%
Rhodium
S or TS = Platinum+10%
Rhodium
T or TT =
Copper/Constantan
HZ = Hertz
PU = Pulse
MV = Millivolts
MA = Milliamps
VT = Volts
RP = Platinum
RC = Copper
RN = Nickel
Transmitter temperature This field identifies the temperature units
units (Fahrenheit or Celsius) used for conversion
coefficient calculation based on known field
transmitter types.
This field identifies the type of equation
Conversion Type (0-5) to be used for conversion to engineering
units.(See Notes.)
Scaling:
Bottom output scale This field is used to linearly convert the value to
the card output level.
Top output scale This field is used to linearly convert the value to
the card output level.

OW240_60 179
11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Sensor:
Low sensor limit This field indicates the low limit of the signal’s
operating range
High sensor limit This field indicates the high limit of the signal’s
operating range.
Low sensor deadband This field maps to the BL field of the point
range record.
High sensor deadband This field maps to the BH field of the point
range record.
This field performs conversion coefficient
Low operating range
calculation and checking.
This field performs conversion coefficient
High operating range
calculation and checking.
This field indicates the low limit of the
Field transmitter low value
transmitter’s operating range
This field indicates the high limit of the
Field transmitter high value
transmitter’s operating range.
This field defines a signal conditioner value that
Signal conditioner value
can be used to allow milliamp type sensors to
be read by volt cards.
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
Polynomial

The variables used in the equations are defined as follows:

X = Original input value, which is converted to Y (engineering units) by the specified type of
conversion.
Y = Final, converted value of the analog input.
C1 - C6 = Conversion coefficients.

180 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

11.3.22 I NT P ARAMS T AB

Int Params Tab

Tab Field Description

Int Params 1 through 60 Represent the integer parameters of an LC (algorithm) record.

Only apply to the algorithms selected in the config tab. This
allows you to see what fields apply to the algorithm. Only the
algorithms that need to be tuned will be tuned.

11.3.23 L IMITS T AB

Limits Tab

Tab Field Description

Limits Deadbands:

Note: Low alarm This field maps directly to the DJ field of the point record.
Calculated deadband
This field maps directly to the DB field of the point record.
limits can
High alarm
exist for
deadband
low/high

OW240_60 181
11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

High Limits:
High clamp limit This field maps directly to the VH field of the point record.
High engineering This field maps directly to EH field of the point record.
limit
This field maps directly to the RV field of the point record.
High reasonability Analog points can have a high/low Engineering Range limit
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.
These fields map directly to the HL, ZH, 3Y, and 4Y fields of
the point record.
High alarm limit 1 -
4 This field maps directly to the ZI field of the point record.
Analog points can have up to 4 different high alarm limits and
4 different low alarm limits. The limits may be either a Value
High alarm limit or the name of another analog point in the system (called a
incremental variable alarm).
Alarms are processed from limit 4 down to limit 1. The first
limit found causes an alarm message. The limits should
increase in value for High limits 1 to 4 (for example, if High
Limit 1 = 100.0, High Limit 2 should be of greater value).
Exceeding an alarm limit will generate an alarm message.
An alarm priority can be assigned to each of the 4 high and
each of the 4 low alarm limits to differentiate the critically of
the alarm situation.
One High and one Low deadband can be defined to prevent
the point from toggling in and out of alarm situation.
One High and one Low incremental limit may be defined. The
incremental limits take effect when the value of the point
passes the LAST defined alarm limit.
Alarm fields do not apply to record type SA.
High alarm limit
user This field maps directly to the UH field of the point record.
Analog points can have 2 user defined alarms: 1 high and 1
low. The limits may be either a Value or the name of another
valid analog point in the system. These alarms are
independent of the 4 high and 4 low alarms. The high/low
deadbands defined for the 4 high/low alarms apply to these
user limits also. Exceeding these alarms will generate an
alarm message.

A separate alarm priority can be defined for the high and low
user defined alarms.

182 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Low Limits:
Low clamp limit This field maps directly to the VL field of the point record.
Low engineering This field maps directly to the EL field of the point record.
limit
These fields map directly to the RW field of the point record
Low reasonability
Analog points can have a high/low Engineering Range limit
limit
and a high/low Reasonability limit. Theses limits can be
defined as a value only.
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
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
Low alarm limit 1 -
point record.
4
This field maps directly to the ZM field of the point record.
Low alarm limit Analog points can have up to 4 different high alarm limits and
incremental 4 different low alarm limits. The limits may either be a Value
or the name of another analog point in the system (called a
variable alarm).
This field maps directly to the UL field of the point record.
Analog points can have 2 user defined alarms; one high and
Low alarm limit one low. The limits may be either a Value or the name of
user another analog point in the system. These alarms are
independent of the 4 high and 4 low alarms. The high/low
deadbands defined for the 4 high/low alarms apply to these
user limits also. Exceeding these alarms will generate an
alarm message.

A separate alarm priority can be defined for the high and low
user defined alarms.

OW240_60 183
11.3 Point Types and Dialog Box Tab Descriptions

11.3.24 P LANT M ODE T AB

Plant Mode Tab

Tab Field Description

Plant Plant Mode (1-6):

Modes
Auto reset These fields are the same as those previously
(1 to 6)
described in this appendix but each one must
Auto acknowledge
be defined for each Plant Mode (1-6) used in
Alarm priority the system.
Alarm cutout name
Alarm cutout delay time
Alarm cutout bit
Alarm group mask
Alarm group bit sense
High alarm limit 1- 4
High alarm limit incremental
High alarm priority 1 -4
High reasonability limit
Low alarm limit incremental
Low alarm priority 1 - 4
Low reasonability limit
Status Checking Type
(Digitals)

11.3.25 P OINT T AB

Point Tab

Tab Field Description

Point Characteristics This 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 8 alphanumeric characters can be used. The first character
must be a letter (A-Z).
Description This maps directly to the ED field of the point record.

184 OW240_60
 11.3 Point Types and Dialog Box Tab Descriptions

Tab Field Description

Frequency This field represents the broadcast frequency of the point. The
choices are:
S (S)low
F (F)ast
A (A)periodic
Note:
Aperiodic points will be broadcast in special aperiodic DDBs.
These will be broadcast on the highway by subscription. When a
point’s dynamic data is accessed from another drop, that drop will
send a request to the originator to start broadcasting (once a
second) the DDB containing the point. These subscriptions are
renewed with the subsequent accesses. Once the subscription
runs out, the point (DDB) will no longer be broadcast.
OPP Rate This 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
Point Alias Sixteen character alias for the point name.

11.3.26 R EAL P ARAMS T AB

Real Params Tab

Tab Field Description

Real Up to Labels are dependent on the algorithm name chosen on the

Params 30 config tab. Only apply to the algorithms selected in the Config
tab. This allows you to see what fields apply to the algorithm.
Only the algorithms that need to be tuned will be tuned.

11.3.27 S ECURITY T AB

Security Tab

Tab Field Description

Security Security Security groups created in the Security subfolder of the Systems
group (1-32) folder appear in this dialog box. If no security groups are specified
in the Systems folder, no fields appear. See Building a Systems
Folder for more information regarding security settings.

OW240_60 185
11.4 Configuring Complex Points

11.4 C O N F I G U R I N G C O M P L E X P O I N T S
All points are created using the procedures previously outlined in To Create a Point (see page
156), but the points discussed are complex and require special attention. When creating the
following points, ensure that the fields indicated are configured. All other fields can accept the
defaults or be edited as needed.

11.4.1 A NALOG I NPUT P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined as a module/card which contains analog input channels.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined.
In the Instrumentation tab:
ƒ Conversion Type must be defined.
Conversion Coefficient 1-6 can be assigned, via the coefficient The coefficient calculation
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 Insturment Tab of an analog point edit dialog. A
typical coefficient will be generated creating 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's in degrees F or C. The values of the 8
conversion coefficients will be inserted. In addition, the Thermocouple will be linked 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, and the
interface will calculate all coefficients., and can be tweaked using the engineering tools.

186 OW240_60
 11.4 Configuring Complex Points

11.4.2 A NALOG O UTPUT P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined as a module/card which contains analog output channels.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined.
In the Instrumentation tab:
ƒ Bottom Output Scale must be defined.
ƒ Top Output Scale must be defined.

11.4.3 A NALOG /T HERMOCOUPLE P OINTS

In the Hardware tab:

ƒ I/O Module must be set as a temperature sensor.
In the Instrumentation tab:
ƒ Field Transmitter Type must be TB, TE, TJ, TK, TR, TS, TT or B, E, J, K, R, S, T and
match the configuration module for that channel.
ƒ Field Transmitter Temperature Units Type must be set to either F or C.
ƒ All Conversion fields, CJ Compensation Name, and a default CJC conversion coefficient
will be assigned.
ƒ Conversion type 2 (5th polynomial) must be set.
ƒ A default Conversion Coefficient will be assigned, and can be tweaked using the engineering
tools.
ƒ Match Operating Range for channel. The Operating Range should be the temperature values
and Field Transmitter values are the mv values.
ƒ A ninth channel is provided. This ninth point is needed for the CJ Compensation field when
defining the eight other thermocouple points.

11.4.4 D IGITAL I NPUT P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined as Digital Input.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined and should be identical for all points assigned to the same
module.

OW240_60 187
11.5 Third Party Points

11.4.5 D IGITAL O UTPUT P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined and must be identical for all points assigned to the same
module.

11.4.6 P ULSE A CCUMULATOR P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined as Digital Input.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined.

11.4.7 RTD P OINTS

In the Hardware tab:

ƒ I/O Type must be defined.
ƒ I/O Module must be defined as an RTD.
ƒ I/O Channel must be defined.
ƒ I/O Task Index must be defined.
In the Instrumentation tab:
ƒ Field Transmitter Type must be RN, RC, or RP and match the configuration module for that
channel.
ƒ Field Transmitter Temperature Units Type must be set to either F or C.
ƒ Conversion type 2 (5th polynomial) must be set.
ƒ A default Conversion Coefficient will be assigned, and can be tweaked using the
engineering tools (must be correct for RTD).
ƒ Match Operating Range for channel. The Operating Range should be the temperature values
and Field Transmitter values are the ohm values.

11.5 T H I R D P A R T Y P O I N T S
A third party point is a point that originates from an Ovation Controller and is updated by a third
party driver.

Note: There must be a corresponding configuration device defined for all third party I/O drivers.
It is defined under the Drops/Configuration/Controller/Devices folder. (See Ovation Controller
User Guide.)

188 OW240_60
 11.6 Modifying a Point

11.6 M O D I F Y I N G A POINT
In some cased it may be desirable to modify a point already loaded into the database.

11.6.1 T O M ODIFY A P OINT

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the appropriate Drops folder and open the Points folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
4. Right click on the point to be changed and select Open. The Point dialog box appears.
5. Make the necessary changes.
6. Select Ok or Apply to add the point changes to the database.
7. Load the drop by using the Right-click menu.

OW240_60 189
S E C T I O N 12

BUILDING POINT GROUPS

In This Section

Point Groups Philosophy.................................................................................... 191

To Access the Point Groups Folder ................................................................... 191
To Add a Trend Point Group .............................................................................. 192
To Add a New PDS Point Group........................................................................ 199
To Add a New eDB Point Group ........................................................................ 203

12.1 P O I N T G R O U P S P H I L O S O P H Y
Point Groups are various points grouped together for monitoring and trending and process
diagram purposes. Point Groups can be added through the Developer Studio or through an
Ovation 1.x or 2.x import file from an existing Ovation 1.x system. Points included in the Point
Group are called members.

The Point Group folder is located under the System object in the System Tree. Point Groups are
distribute to all Ovation Windows type drops.

There are three types of Point Groups: eDB Point Groups, Trend Point Groups and PDS Point
Groups. Trend Point Groups associate a commonly used set of points and track them over time.
eDB Point Groups used for PDS Point Groups allow generic graphics to be created that do not
hard code points, but rather reference points via the point group. Point Groups have configurable
items at the group level and the member level.

The new point groups or members are added (or edited) on-line; 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 Building Points (see page 153).

12.2 T O A C C E S S THE POINT GROUPS FOLDER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the System object and locate the Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
4. Open the Point Groups folder to reveal the three subfolders: Trend Point Groups, PDS Point
Groups and eDB Point Groups.

OW240_60 191
12.3 To Add a Trend Point Group

12.3 T O A D D A TREND POINT GROUP

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the System object and locate the Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
Trend Point Groups
4. Open the Point Groups folder to reveal the three subfolders.
5. Right click the Trend Point Groups folder and select Insert New. The Insert New Trend
Point Group Wizard appears (see Typical Wizard Dialog Box (see page 31)).
6. Enter the trend group name in the Group Name field, using up to 30 characters.
7. 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 will appear when you try to add the point to
the database.

8. Select Finish and the New Trend Point Groups dialog box appears.

Figure 56: Trend Point Group Dialog Box

192 OW240_60
 12.3 To Add a Trend Point Group

Trend Point Group Dialog Box Fields

Field Description

Group Number Used to identify the group information.

Group Title Title of the trend group (up to 30 characters)
Layout Layout of the trend graph
(Horizontal, Vertical, X, Y Plot)
Grid Selects grid lines on the trend graph.
(Enable, Disable)
Live Trend Duration The interval unit is specified as minutes, hours, or days. All points in a
single window use the same collection interval.
(10, 30, 100 min, 5, 10, 30, 100, 200 Hrs, 25, 33.3 Days)
Historical type Allows the user to specify which type of point data to retrieve, high
fidelity, or aggregate.
Continuous - obtains data from the high fidelity table.
Aggregate - obtain data from high fidelity table (future)
Range The time range format of a historical request.
Start/Interval - allows the start time and processing period of the
trend request to be defined. (The end time can not be changed).
When selected, the Historical Period field is grayed-out.
Start/Period - allows the definitive start time to be defined. When
selected, Historical Interval/ Units and Historical Interval/Value fields
are grayed-out.
Historical period Allows the user to specify the length of the historical trend. This field
is grayed-out if the Start/Interval field is selected. (Entry field.)
Historical Interval Allows the user to specify the spacing between the historical trend. An
(Value) Integer input plus the Historical Interval (units) field makes a complete
interval. (Numerical entry field.)
Historical Interval Allows the user to interpret the interval specified above.
(Units)
(Minutes, Hours, Days)
Historical start time The Start Time Offset specifies the relative start time offset from the
offset (Value) current time of the historical interval. (Numerical entry field.)
Historical start time The Start Time Offset specifies how to interpret the offset specified
offset (Units) above.
(Minutes, Hours, Days)
Historical start time A forced start time of the historical trend. (Entry field, HH:MM format.)
9. Fill in and select the appropriate values.
10. Select OK or Apply to add the Point Group. A subfolder will appear under the Trend Point
Group folder in the System Tree.

OW240_60 193
12.3 To Add a Trend Point Group

12.3.1 T O M ODIFY A T REND P OINT G ROUP

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the System object and locate the Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
Trend Point Groups
4. In the System object, open the Point Group folder and select the Trend Point Groups
folder. Objects for all existing trend point groups appear under the Trend Point Groups folder.
5. Right click the trend points group folder that you wish to modify and select Open. The Trend
Point Group dialog box appears, similar to To Add a Trend Point Group (see page 192).
6. Make necessary changes and select Ok.

12.3.2 T O A DD A T REND P OINT G ROUP M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the eDB Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
Trend Point Groups
4. In the System object, open the Point Groups folder and select the Trend Point Groups
folder. Objects for all existing trend point groups appear under the Trend Point Groups folder.
5. Open the point group folder in which you want to add a member, and the Trend Group
Members subfolder appears. Right click the Trend Point Groups and select Insert New. The
Insert New Trend Group Members Wizard appears (see Typical Wizard Dialog Box (see
page 31)).
6. Enter the name of the point that will be added to the Trend Group in the Point Name entry
field.
7. Use the spin arrows (or type it in) to select a Rank. Rank is a number that corresponds to the
point and the value can be 0 to 7, with zero being the highest rank and seven being the
lowest rank.
à Higher ranked members appear at the top of the trend graphic.
à The lower rank members are placed toward the bottom of the trend graphic.

194 OW240_60
 12.3 To Add a Trend Point Group

8. Select Finish and the New Trend Group Members dialog box appears. Information added to
the Insert New Trend Group Members Wizard now appears in the Configure tab.

Figure 57: Add a Trend Point Group Member

Trend Point Group Member Dialog Box Fields

Field Description

Point name The Trend Point name can use up o 30 characters.

Rank Title of the trend group (up to 30 characters)
Bit number For a packed point, enter the bit number in the Bit Number field.
Leave the field empty if the point is not a packed point.
Scale limits Enables view of a trend line in lesser or greater detail. Each trend
point has its own set of temporary high and low scales.
The Default selection indicates that the points defined by default as
“minimum” and “maximum” defined in Scale high and Scale low.
(Default, User Entered)
Scale high Represents the top boundary of the trend. The high scale must be
represented as a positive or negative integer, floating point, or in
scientific or technical notation. (For example, scientific (1.0e2, -
1.0E+2, 1.0E-2) technical (100e0, 10e3, 10E6).
Scale low Represents the bottom boundary of the trend. The low scale must be
represented as a positive or negative integer, floating point, or in
scientific or technical notation. (For example, scientific (1.0e2, -
1.0E+2, 1.0E-2) technical (100e0, 10e3, 10E6)
Shading Will shade the area between the baseline and the trend line.
(Enable, Disable)

OW240_60 195
12.3 To Add a Trend Point Group

Field Description

Baseline value The baseline value can be up to 8 digits. The Scale high limit
becomes the baseline when the baseline value is greater, and Scale
low becomes the baseline when baseline value is low. For
logarithmic points, the baseline value must be greater than zero.
Transient Selecting Yes causes the second digital average value (0 or 1) of any
3 consecutive values in the trend data that are the same to be
changed to the opposite state if the second digital average value was
not in the same state for its entire processing period.
The transient option does not show true data, and is meant to bring
out digital state changes that would otherwise remain hidden on
trends of digital points for processing periods greater than 1 second.
A trend around the time of the digital activity should be performed,
with the processing period decreased and the transient option
disabled to show the true digital states. (This option is applicable only
when the processing type is Average Value.) (Yes, No)
Summary Select Yes to include a summary section or No to exclude a summary
section. The summary consists of data for each point, such as
averages, maximums, and minimums.

196 OW240_60
 12.3 To Add a Trend Point Group

Field Description

Processing type Actual Value displays the actual value of the specified process point
at the end of each individual processing period.
Average displays the average value of the specified process point
over each individual processing period.
Integration displays the integral of the specified process point with
respect to seconds, multiplied by the specified integration constant,
over each individual processing period.
Minimum Value displays the minimum value of the specified process
point over each individual processing period.
Maximum Value displays the maximum value of the specified
process point over each individual processing period.
Time Set Mins displays the number of minutes which the specified
digital process point, or selected bit of a packed process point, spent
in the Set state over each individual processing period.
Time Reset Mins displays the number of minutes which the specified
digital process point, or selected bit of a packed process point, spent
in the Reset state over each individual processing period.
Time Set Hours displays the number of hours which the specified
digital process point, or selected bit of a packed process point, spent
in the Set state over each individual processing period.
Time Reset Hours displays the number of hours which the specified
digital process point, or selected bit of a packed process point, spent
in the Reset state over each individual processing period.
Toggle displays the number of state changes for the specified digital
process point, or selected bit of a packed process point, which
occurred over each individual processing period.
Toggle Set displays the number of state changes to the Set state for
the specified digital process point, or selected bit of a packed process
point, which occurred over each individual processing period.
Toggle Reset displays the number of state changes to the Reset
state for the specified digital process point, or selected bit of a packed
process point, which occurred over each individual processing period.
Unpacked Bit Value displays the actual value of a selected bit of the
specified process point at the end of each individual processing
period.
Integration value This field is only applicable when the processing type is Integration.

Historical start time A forced start time of the historical trend. (Entry field, HH:MM format.)

OW240_60 197
12.3 To Add a Trend Point Group

Note: If Default scales are used, the scales defined in the trend_defaults_file are used. If the
point is not defined in the trend_defaults_file, the trend will use TV (maximum scale value) and
BV (minimum scale value) for analog points. (See Ovation Record Types Reference Manual.)
The trend will use the values defined by Digital Default High Scale and Digital Default Low Scale
for digital points.
Digital points differ from analog points in that digital points always have a value of 0 (off) or 1
(on). The high and low scale values specified for digital points indicate the position of the trend
line on the window and the height of the trend.

9. Enter the integration constant in the Integration Value field. Select OK or Apply to add the
modified or created Point Group to the Group List.

12.3.3 T O M ODIFY A T REND P OINT G ROUP M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Open the System object and locate the Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
Trend Point Groups
4. In the System object, open the Point Group folder and select the Trend Point Groups
folder. Objects for all existing trend point groups appear under the Trend Point Groups folder.
5. Open the trend point group folder that contains the group member that you wish to modify and
the Trend Group Members folder appears.
6. Double click the Trend Group Members folder and the members of the group appear in the
WorkPad window.
7. Open the trend point group member that you wish to modify and the Trend Point Group
Member dialog box appears, similar to To Add a Trend Point Group (see page 192).
8. Make necessary changes and select Ok to add the modified member to the database.

198 OW240_60
 12.4 To Add a New PDS Point Group

12.4 T O A D D A N E W PDS P O I N T G R O U P
1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
PDS Point Groups
4. Right click the PDS Point Groups folder and select Insert New. The Insert New PDS Point
Groups Wizard appears (see Typical Wizard Dialog Box (see page 31)).
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 will appear when you try to add the point to
the database.

7. Select Finish and the New PDS Point Groups dialog box appears.

Figure 58: The New PDS Point Group Dialog Box

OW240_60 199
12.4 To Add a New PDS Point Group

8. The Group Number defaults from information entered in the New PDS Point Groups Wizard.
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.
10. The Text Group Number field allows you to attach additional text strings to the Point Group
when displaying a diagram. The valid range is 1 to 5000. Each Text Group may contain up to
100 text strings.
11. The Diag Number field displays the number of the diagram to be loaded when this point group
is loaded. If this field is left blank or set equal to zero, then the requested group is displayed
with the current diagram. If this field is non-zero, then the diagram of that number will be
displayed with the requested group.
12. The Group Paging fields (Up Group, Down Group, Right Group, Left Group) allow you to
enter the group numbers associated with this 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
5,000. If the value is outside this 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.

12.4.1 T O M ODIFY PDS P OINT G ROUPS

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the Point Group folder and select the PDS Point Groups folder.
Objects for all existing PDS point groups appear under the PDS Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
Trend Point Groups
4. Right click the PDS points group folder that you wish to modify and select Open. The PDS
Point Group dialog box appears, similar to the one in To Add a New PDS Point Group (see
page 199).
5. Make necessary changes and select Ok.

200 OW240_60
 12.4 To Add a New PDS Point Group

12.4.2 T O A DD A PDS P OINT G ROUP M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the Point Group folder and select the PDS Point Groups folder.
Objects for all existing PDS point groups appear under the PDS Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
PDS Point Groups
4. Open the point group folder in which you want to add a member and the PDS Point Groups
subfolder appears.
5. Right click the PDS Point Group Member folder and select Insert New. The Insert New PDS
Group Members Wizard appears (see Typical Wizard Dialog Box (see page 31)).
6. Enter the point name in the Point Name entry field.
7. Use the arrows (or type it in) to select a Rank. Rank is a reference number that corresponds
to the point, and the value can be 1 to 249. Rank is the reference that the graphic will use to
retrieve the information to display.
8. Select Finish and the New PDS Group Members dialog box appears. Information provided in
the Insert New PDS Group Members Wizard is displayed in the dialog box.

Figure 59: New PDS Group Member Dialog Box

9. Select Ok to activate the PDS point group member. The new PDS point folder appears in the
System Tree.

OW240_60 201
12.4 To Add a New PDS Point Group

12.4.3 T O M ODIFY PDS P OINT G ROUPS M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the PDS Point Groups folder.
<HardwareRoot>
[Systems]
Unique System Name
[Point Groups]
PDS Point Groups
4. In the System object, open the Point Group folder and select the PDS Point Groups folder.
Objects for all existing PDS point groups appear under the PDS Point Groups folder.
5. Open the point group folder that you wish to modify and the PDS Point Groups subfolder
appears.
6. Double click the PDS Group Members folder and the members of the group appear in the
WorkPad window.
7. Open the PDS point group member that you wish to modify and the PDS Point Group
Member dialog box appears, similar to To Add a Point Group Member to a PDS Point
Group (see page 201).
8. Make necessary changes and select Ok to add the modified member to the database.

202 OW240_60
 12.5 To Add a New eDB Point Group

12.5 T O A D D A N E W E DB P O I N T G R O U P
1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the eDB Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
eDB Point Groups
4. Right click the eDB Point Groups folder and select Insert New. The Insert New eDB Point
Groups Wizard appears (see Typical Wizard Dialog Box (see page 31)).
5. Enter the eDB 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 will appear when you try to add the point to
the database.

7. Select Finish and the New eDB Point Groups dialog box appears.

Figure 60: New eDB Point Groups Dialog Box

8. The Group number defaults from information entered in the New eDB Point Groups Wizard.
Enter the title of the eDB group in the Group Title field, using up to 30 characters.
9. Select Ok to activate the new point group. A sub folder with the new eDB group name is
added to the eDB Point Groups folder.

OW240_60 203
12.5 To Add a New eDB Point Group

12.5.1 T O M ODIFY E DB P OINT G ROUPS

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the eDB Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
eDB Point Groups
4. In the System object, open the Point Group folder and select the eDB Point Groups folder.
Objects for all existing eDB point groups appear under the eDB Point Groups folder.
5. Right click the eDB points group folder that you wish to modify and select Open. The eDB
Point Group dialog box appears, similar to To Add a Point Group Member to a PDS Point
Group (see page 201).
6. Make necessary changes and select Ok.

12.5.2 T O A DD A E DB P OINT G ROUP M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. In the System object, open the eDB Point Group folder and select the eDB Point Groups
folder. Objects for all existing eDB point groups appear under the eDB Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
eDB Point Groups
4. Open the point group folder in which you want to add a member and the eDB Point Groups
subfolder appears.
5. Right click the eDB Group Members folder and select Insert New. The Insert New eDB
Group Members Wizard appears (see Typical Wizard Dialog Box (see page 31)).
6. Enter the point name in the Point name entry field.
7. Use the spin button (or type it in) to select a Rank. Rank is a reference number that
corresponds to the point, and the value can be 0 to 19. Rank is the reference that the graphic
will use to retrieve the information to display.
8. Select Finish and the New eDB Group Members dialog box appears, similar to To Add a
Point Group Member to a PDS Point Group (see page 201). Information provided in the
Insert New eDB Group Members Wizard is displayed in the dialog box.
9. Select Ok to activate the eDB point group member. The new eDB point folder appears in the
System Tree.

204 OW240_60
 12.5 To Add a New eDB Point Group

12.5.3 T O M ODIFY E DB P OINT G ROUPS M EMBER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the eDB Point Groups folder.
[Systems]
Unique System Name
[Point Groups]
eDB Point Groups
4. In the System object, open the Point Group folder and select the eDB Point Groups folder.
Objects for all existing eDB point groups appear under the eDB Point Groups folder.
5. Open the point group folder that you wish to modify and the eDB Point Groups subfolder
appears.
6. Double click the eDB Group Members folder and the members of the group appear in the
WorkPad window.
7. Open the eDB point group member that you wish to modify and the eDB Point Group Member
dialog box appears.
8. Make necessary changes and select Ok to add the modified member to the database.

OW240_60 205
S E C T I O N 13

ADDING HOLDING REGISTERS

In This Section

Holding Register Philosophy .............................................................................. 207

To Insert a New Holding Register ...................................................................... 208
To Open an Existing Holding Register............................................................... 209
Holding Register Editor Dialog Box.................................................................... 211

13.1 H O L D I N G R E G I S T E R P H I L O S O P H Y
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.

OW240_60 207
13.2 To Insert a New Holding Register

13.2 T O I N S E R T A NEW HOLDING REGISTER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Controller Drop where you want to insert a Holding Register,
and access the Holding Register folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Configuration]
Holding Register
4. Open the Holding Register folder to reveal the Holding Register subfolder.
5. 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 (described in To Open an Existing
Holding Register (see page 209)).
6. If no Holding Register exists for the desired drop, right click the Holding Register folder and
choose Insert New. The Insert New Holding Register Wizard appears.

Figure 61: Holding Register Wizard

208 OW240_60
 13.3 To Open an Existing Holding Register

7. Select a Value between zero and 9,999 for the holding register by entering the value or using
the arrows.

Note: The value selected becomes the value of the new holding register created.

8. Select the Finish button and the Holding Register Editor dialog box appears already open to
the selected Register value, and the Register icon appears in the WorkPad window, see
Holding Register Editor Dialog Box (see page 211).

13.3 T O O P E N AN EXISTING HOLDING REGISTER

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Expand the system tree to the Controller drop (which contains the register to be edited) and
open it to reveal the Holding Register folder.
[Systems]
Unique System Name
[Networks]
Unique Network Name
[Units]
Unique Unit Name
[Drops]
Unique Drops Name
[Configuration]
Holding Register
4. Open the Holding Register folder to reveal the Holding Register subfolder.
5. Double click the Holding Register subfolder to display a list of Holding Registers in the
WorkPad Window.
6. Right click the appropriate holding register object and select Open. The Holding Register
Editor appears. See Holding Register Editor Dialog Box (see page 211) for a description of
how to use the Editor.

Note: There is a holding register object assigned (with that registers value as part of the object
title) for every register that contains a value. The Holding Register object selected in the
WorkPad window determines the first register displayed in the Holding Register Editor's Register
column. All registers from zero to 9,999 are available once in the editor.

OW240_60 209
13.3 To Open an Existing Holding Register

13.3.1 T O C HANGE A S INGLE H OLDING R EGISTER V ALUE

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the desired existing Holding Register (as described in To Open an Existing Holding
Register (see page 209)).
4. Select the register number to be changed and click in its Data Entry field.

Note: The Data Entry field is only available if a “Permit Changes” box is checked (described in
Holding Register Editor Functions (see page 212)), otherwise the entry field will be grayed
out (not available for input).

5. Type in the new value and select the Apply button. The value is added to the writable fields.

13.3.2 T O C HANGE M ULTIPLE H OLDING R EGISTER V ALUES

1. Launch the Ovation Developer Studio by double clicking its icon located on the Windows
desktop.
2. Select the Hardware Function Bar, the Hardware Root object will appear to display the
System Tree within the Developer Studio Overview Window.
3. Access the desired existing Holding Register (as described in To Open an Existing Holding
Register (see page 209)).
4. Select the register number to be changed and select in its Data Entry field.

Note: The Data Entry field is only available if a “Permit Changes” box is checked (described in
Holding Register Editor Functions (see page 212)), otherwise the entry field will be grayed
out (not available for input).

5. Type in the new value.

6. Enter a new value for each register being changed in the current set.
7. Select the Apply Page button to apply all the new values.

Note: Values must be applied for each current register set before moving to another set. If you
add a value to the Data Entry field and move to another set of Register numbers, a message
appears asking “Do you want to apply the changes on this page?
Select Yes to apply the changes and move to the next set of registers. Select No to discard the
changes and move to the next set of registers.

210 OW240_60
 13.4 Holding Register Editor Dialog Box

13.4 H O L D I N G R E G I S T E R E D I T O R D I A L O G B O X

Figure 62: Holding Register Editor

Notes: The table part of the dialog box will not be displayed until a controller is assigned.
The "Apply" and "Data Entry" columns will not be displayed until one or both of the "Permit
Changes" boxes are check (described in Holding Register Editor Functions (see page 212)).
Only one Holding Register Editor can be opened at a time in order to avoid confusion while
creating new Registers.

1. Once the Editor dialog box is open, you can also insert a new Holding Register by entering a
value in the "Data Entry" field of an unused Register, and selecting the corresponding "Apply"
arrow button.

Note: The Data will only be applied to the values that have their “Permit Changes” box is
checked , otherwise the value field will be grayed out (not available for input).

2. Close and open the Holding Register folder.

Note: A new Holding Register will be created but will NOT appear in the WorkPad window until
the Holding Register folder is closed and reopened (Data Entry field is only available if a “Permit
Changes” box in the Preferences dialog box is checked (described in Holding Register Editor
Functions (see page 212))).

OW240_60 211
13.4 Holding Register Editor Dialog Box

13.4.1 H OLDING R EGISTER E DITOR F UNCTIONS

The Menu bar provides access to the same functionality as the Toolbar buttons with the exception
of an Undo function that can be accessed through the pull-down Edit menu.

Undo reverses the last data entry in the Data Entry column, but will NOT undo any value that has
been applied.

Holding Register Editor Toolbar Buttons

Button Function

Cut - Cuts the selected value.

Copy - Copies the selected value.

Paste - Pastes the contents of the clipboard into the selected field.

Display Decimal - Displays all values in the Holding Register Editor as decimals
values.
Display Hexadecimal - Displays all values in the Holding Register Editor as
hexadecimals values.
Display Real Value - Displays all values in the Holding Register Editor as real
numbers. Only the even numbered register will contain a value. The real value
displayed is the data in the even numbered register appended to the next odd
numbered register.
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 Box (see page 214).
Print - Opens the Print dialog box. See Holding Register Print Dialog Box (see
page 215).
About - Provides the Holding Register Editor application version number.

Holding Register Dialog Box Functions

Button Function

Server Input Box Server where the Drop resides.

Used to disconnect from the server, allowing you to enter and

go to a new server. Selecting disconnect allows you to enter a
new server in the Server Input Box.
Controller Drop Down Box Allows the selection of any controller in the selected server.

First Register Input Box Allows the selection of any register (0-9,999). Select Refresh
to go to that register.
Selecting Refresh will cause the register chosen in the First
Register Input box to appear at the top of the listing.

212 OW240_60
 13.4 Holding Register Editor Dialog Box

Button Function

Moves to the next set of Holding Registers.

Moves to the previous set of Holding Registers.

Applies all newly entered data in the Data Entry column to the
writable value columns. Only data in the current set is applied.
Clears all newly entered data from the Data Entry column.
Only data in the current set is removed.
Copies Database values to the current set of Holding
Registers.
Copies the current set of Holding Registers to the database.

Permit Changes To When checked will allow data entry to the Database Value
Database Check Box column.
Permit Changes to When checked will allow data entry to the Drop Value column.
Database Check Box
Column displays the registers 90-9,999).

Column displays the value of the corresponding register.

Column(s) displays the value of the corresponding register.

Only one column will be displayed for non-redundant drops.
Columns will be displayed if one or both of the "Permit
Changes" boxes is checked. Enter the data to be applied to
the corresponding register(s) in the Data Entry column and
select the corresponding Apply arrow to place the data in
those fields.

OW240_60 213
13.4 Holding Register Editor Dialog Box

13.4.2 H OLDING R EGISTER E DITOR P REFERENCES D IALOG B OX

Use the Preferences dialog box to change settings for the Holding Register Editor dialog box. See
the table below for descriptions of the Preferences settings.

Access the Preference dialog box by selecting File in the Menu bar and choose Preferences, or
by selecting the Preferences button.

Figure 63: Holding Register Preferences Dialog Box

Holding Register Dialog Box Preference Settings

Field Description

Number of Rows Defines the number of visible rows in the Holding

Register Editor dialog box.
Entry Column Text Color Defines the color of the text in the Data Entry column.
Initially Permit Changes When checked, you can write to the database, and the
to Database Apply and Data Entry columns will appear in the Holding
Register Editor dialog box.
Initially Permit Changes When checked, you can write to the Controller(s), and the
to Controller(s) Apply and Data Entry columns will appear in the Holding
Register Editor dialog box.
OK Applies changes to the Holding Register Editor dialog
box.
Cancel Cancels changes make in the current session.

214 OW240_60
 13.4 Holding Register Editor Dialog Box

13.4.3 H OLDING R EGISTER P RINT D IALOG B OX

The Holding Register Print dialog box operates exactly like the windows print dialog box.

Figure 64: Holding Registers Print Dialog Box

13.4.4 H OLDING R EGISTER P RINT P REVIEW D IALOG B OX

The Holding Register Print Preview dialog box operates exactly like the windows print preview
dialog box.

Figure 65: Holding Register Print Preview Dialog Box

OW240_60 215
13.4 Holding Register Editor Dialog Box

13.4.5 H OLDING R EGISTER P RINT S ETUP D IALOG B OX

The Holding Register Print Setup dialog box (a selection found under the File Menu) operates
exactly like the windows print setup dialog box.

Figure 66: Holding Register Print Setup Dialog Box

216 OW240_60
S E C T I O N 14

OVATION I/O MODULE DIALOG BOXES

In This Section

Defining and Configuring Ovation I/O Modules.................................................. 217

14.1 D E F I N I N G AND C O N F I G U R I N G O V A T I O N I/O M O D U L E S

The Module tab on the Ovation Module dialog boxes, must be defined and configured for each
different type of Ovation Modules. We have provided examples of the Ovation module
configuration dialog boxes and tables that describe the fields in the dialog boxes.

14.1.1 A NALOG I NPUT C ONFIGURATION

Analog Input Dialog Box Fields

Field Description

A/C Line Defines the type of AC used in the system (50 Hz or 60Hz).
Frequency
Input sampling rate is 80ms at 50Hz, and 83.3ms at 60Hz.
Default is 60Hz.
A/D Conversion Defines the speed at which the A/D conversion is performed by the
Rate I/O module - Normal or High Speed. Default is Normal.
Suppress Point This attribute permits the RM Point Module point from going into
Fault Module alarm if one or more of the analog inputs are in an alarm/sensor
Alarm condition. For example, if one or more channel(s) of a 4-20mA card
were unused (and left open), setting this attribute would prevent the
RM Module Point from going into alarm. The default is to NOT
suppress the Point Fault Module Alarm.

14.1.2 A NALOG O UTPUT C ONFIGURATION

Analog Output Dialog Box Fields

Field Description

Timeout Action Reset = After the timeout period, output goes to 0.

Latch = After the timeout period, the last output will
be held.

OW240_60 217
14.1 Defining and Configuring Ovation I/O Modules

Field Description

Timeout Pull-down menu used to define the timeout period:

Selection
16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
125 milliseconds
62.6 milliseconds

14.1.3 C OMPACT C ONTACT I NPUT C ONFIGURATION

Compact Contact Input Dialog Box Fields

Field Description

Disable Points on When set, the module will report an error when an input
Ground Fault line or return line is shorted to earth ground, and will light
the “E” LED.

14.1.4 C ONTACT I NPUT C ONFIGURATION

Contact Input Dialog Box Fields

Field Description

Disable Points on When set, the module will report an error when an input line
Ground Fault or return line is shorted to earth ground, and will light the
“E” LED.

14.1.5 C OMPACT D IGITAL I NPUT C ONFIGURATION

Compact Digital Input Dialog Box Fields

Field Description

Blown Fuse Detection When set, if an auxiliary power supply fuse is blown, the
module will report an error and will light the “E” LED.
(Single-Ended
Versions)

218 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

Field Description

No Fields No fields necessary in the Compact Digital Input Module

tab.
(All Other Versions)

14.1.6 D IGITAL I NPUT C ONFIGURATION

Digital Input Dialog Box Fields

Field Description

Blown Fuse Detection When set, if an auxiliary power supply fuse is blown, the
module will report an error and will light the “E” LED.
(Single-Ended
Versions)
No Fields No fields necessary in the Compact Digital Input Module
tab.
(All Other Versions)

14.1.7 D IGITAL O UTPUT C ONFIGURATION

Digital Output Dialog Box Fields

Field Description

Timeout Action Reset = After the timeout period, output is cleared (output transistor is
shut off).
Latch = After the timeout period, the last output will be held.
Timeout Selection Pull-down menu used to define the timeout period:
16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
125 milliseconds
62.6 milliseconds
Blown Fuse When set, if a fuse is blown, the module will report an error and will light
Detection the “E” LED.

OW240_60 219
14.1 Defining and Configuring Ovation I/O Modules

14.1.8 HART A NALOG I NPUT C ONFIGURATION

HART Analog Input Dialog Box Fields

Field Description

HART Device on Indicates if a HART device is attached to the channel.

Channel
Scan HART Variables Indicates that HART multi variable support is enabled for the
on Channel channel.

14.1.9 HART A NALOG H IGH P ERFORMANCE I NPUT C ONFIGURATION

HART Analog Input Dialog Box Fields

Field Description

A/C Line Frequency Defines the type of AC used in the system (50 Hz or 60Hz).
Input sampling rate is 80ms at 50Hz, and 83.3ms at 60Hz.
Default is 60Hz.
HART Device on Indicates if a HART device is attached to the channel.
Channel
Scan HART Indicates that HART multi variable support is enabled for the
Variables on channel. Only those devises that were chosen above can be used.
Channel
Suppress Point This attribute permits the RM Point Module point from going into
Fault Module Alarm alarm if one or more of the analog inputs are in an alarm/sensor
condition. For example, if one or more channel(s) of a 4-20mA card
were unused (and left open), setting this attribute would prevent the
RM Module Point from going into alarm. The default is to NOT
suppress the Point Fault Module Alarm.

14.1.10 HART A NALOG O UTPUT C ONFIGURATION

HART Analog Output Dialog Box Fields

Field Description

Timeout Action Reset = After the timeout period, output goes to 0.

Latch = After the timeout period, the last output will be held.

220 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

Field Description

Timeout Selection Pull-down menu used to define the timeout period:

16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
125 milliseconds
62.6 milliseconds
HART Device on Channel Indicates if a HART device is attached to the channel.
Scan HART Variables on Indicates that HART multi variable support is enabled for the
Channel channel.

14.1.11 L OOP I NTERFACE C ONFIGURATION

Loop Interface Dialog Box Fields

Field Description

A/C Line Frequency Defines the type of AC used in the system (50 Hz or 60Hz). Input
sampling rate is 80ms at 50Hz, and 83.3ms at 60Hz. Default is
60Hz.
Blown Fuse Detection When set, if a fuse is blown, the module will report the appropriate
Enabled (inputs) error and will light the “4 Fuse” LED.
Blown Fuse Detection When set, if a fuse is blown, the module will report the appropriate
Enabled (outputs) error and will light the “4 Fuse” LED.
Digital Outputs on Shutoff = After the timeout period, output is cleared (output
Controller Timeout transistor is shut off).
Hold = After the timeout period, the last output will be held.
Communications Pull-down menu used to define the timeout period:
Timeout Selection
16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
125 milliseconds
62.5 milliseconds

OW240_60 221
14.1 Defining and Configuring Ovation I/O Modules

Field Description

Controller Defined When set, 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, indicates that the Controller is defining the setpoint. The
Setpoint 1 process variable can then be configured as the analog point
assigned to analog channel 8.

1 This field is only valid if the Electronics module firmware is at Version 5 or later.

14.1.12 L OOP I NTERFACE D IALOG B OX (E LECTRIC D RIVE M ODE )

Loop Interface Dialog Box Fields (Electric Drive Mode)

Field Description

A/C Line Frequency Defines the type of AC used in the system (50 Hz or 60Hz).
Input sampling rate is 80ms at 50Hz, and 83.3ms at 60Hz.
Default is 60Hz.
Blown Fuse When set, if a fuse is blown, the module will report the
Detection Enabled appropriate error and will light the “4 Fuse” LED.
(inputs)
Blown Fuse When set, if a fuse is blown, the module will report the
Detection Enabled appropriate error and will light the “4 Fuse” LED.
(outputs)
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 choices for modes:
Mode 1 (normal) = 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 a hard lower.
Controller Defined When set, 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, indicates that the Controller is defining the setpoint.
Setpoint 1 The process variable can then be configured as the analog point
assigned to analog channel 8.

1 This field is only valid if the Electronics module firmware is at Version 5 or later.

222 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

14.1.13 P ULSE A CCUMULATOR C ONFIGURATION

Pulse Accumulator Dialog Box Fields

Field Description

All field descriptions are applicable for Channel 1 or Channel 2.

Count Type Field input voltage range. Defines different terminal block
connections:
+5V (high speed).
+5/12V (medium speed).
24/48V.
Configuration Style A = count pulses till reset by Controller.
B = count pulses and reset.
See the table below C = measure width of long pulse.
for matrix of
D = measure width of last pulse.
parameters to set for
each style. E = measure total width of several pulses since last read.
F = measure period of repetitive pulses.
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).
Configuration styles can be mixed on a card, except Styles G and H.
Count Select Selects input to the counter through bits 15 and 14 in register D:
00 = External count input
01 = 1 Khz
10 = 10 Khz
11 = 100Khz
Disable De-bounce When set, will disable the de-bounce (chattering or noise) on Enable
on ENABLE and and Snapshot inputs.
SNAPSHOT
ENABLE for OFF When set, open time of ENABLE input will be measured.
Input
When not set, closed time of ENABLE input will be measured.
Snapshot Count on Select “Leading” to snapshot on the leading edge of input pulse.
Pulse Edge
Select “Trailing” to snapshot on the trailing edge of input pulse.
Measure Close Time = Closed time of ENABLE input will be measured.
Open Time = Open time of ENABLE input will be measured.

OW240_60 223
14.1 Defining and Configuring Ovation I/O Modules

Field Description

Increment Count on Select “Leading” to increment count on the leading edge of input
Pulse Edge pulse. Select “Trailing” to increment count on the trailing edge of input
pulse.
Reset on Read When set, the counter goes back to zero (0) after the pulse is read.
De-bounce Count When set, will de-bounce (reject chatter or noise) the input count.
Input
Compare and Only set for Configuration H.
Snapshot
Reset on Snapshot When set, the counter goes back to zero (0) after the snapshot
occurs.
Enable command When set, counter has been enabled to count and does not need the
external ENABLE signal.

Fields to Configure for Configuration Styles

Field 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 De-bounce on X X X X X X X
ENABLE and SNAPSHOT
ENABLE for OFF input X X

Snapshot Count on Pulse X X

Edge
Measure X X X

Increment Count on Pulse X X

Edge
Reset on Read X X

De-bounce Count Input X X X

Compare and Snapshot X

Reset on Snapshot X X X X

Enable command X X X X X

224 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

14.1.14 RTD C ONFIGURATION

RTD Dialog Box Fields

Field Description

A/C Line Defines the type of AC used in the system (50 Hz or 60Hz). Input
Frequency sampling rate is 80ms at 50Hz, and 83.3ms at 60Hz. Default is 60Hz.
Channel 1 Scale See the table below for descriptions of the items in the menu.
Channel 2 Scale See the table below for descriptions of the items in the menu.
Channel 3 Scale See the table below for descriptions of the items in the menu.
Channel 4 Scale See the table below for descriptions of the items in the menu.
Suppress Point This attribute permits the RM Point Module point from going into alarm
Fault Mode Alarm if one or more of the analog inputs are in an alarm/sensor condition.
For example, if one or more channel(s) of a 4-20mA card were unused
(and left open), setting this attribute would prevent the RM Module
Point from going into alarm. The default is to NOT suppress the Point
Fault Module Alarm.

RTD Scrolling List Values

Scale Wires Type Temp Temp Rcol Rhot Excitation Accuracy Accuracy
# oF oC d (ohm) current (ma) counts % of
(HEX) (ohm SPAN
)

1 3 PL 0 to -18 to 6 106.3 0.1556 9 0.22

1200 649
2 3 CU 0 to -18 to 8.5 16.5 1.51 13 2.32
302 150
D 11 CU 32 to 0 to 50 80 1.0756 11 0.27
284 140
11 3 CU 32 to 0 to 53 78 1.1291 12 0.30
230 110
19 3 PL -4 to -16 to 92 163.67 0.5121 11 0.27
334 168
22 3 PL 32 to 0 to 100 200 0.4087 10 0.25
520 269
23 3 PL 32 to 0 to 100 301 0.2554 10 0.25
1040 561
25 3 NI 12 to -11 to 109 360 0.2104 10 0.25
464 240
26 3 NI 32 to 0 to 120 170 0.5240 13 0.32
150 70
28 3 NI 32 to 0 to 120 225 0.3682 11 0.27
278 122

OW240_60 225
14.1 Defining and Configuring Ovation I/O Modules

80 4 PL 32 to 0 to 100 208 0.3921 10 0.25

544 290
81 4 PL 356 to 180 to 168 186 0.5240 30 0.74
446 230
82 4 PL 32 to 0 to 200 473 0.1675 12 0.30
698 370
83 4 PL 514 to 268 to 402 452 0.2142 29 0.71
648 342
84 4 PL 32 to 0 to 100 120 0.7860 19 0.47
124 51
85 4 PL 32 to 0 to 100 140 0.6386 13 0.32
217 103
86 4 PL 32 to 0 to 100 180 0.4644 11 0.27
412 211
87 4 PL 32 to 0 to 100 240 0.3296 10 0.25
714 379
88 4 PL 511 to 266 to 200 230 0.4170 24 0.59
662 350

14.1.15 R ELAY O UTPUT M ODULE G2R C ONFIGURATION

Relay Output Module G2R Dialog Box Fields

Field Description

Timeout Action Reset = After the timeout period, output is cleared (output
transistor is shut off).
Latch = After the timeout period, the last output will be held.
Timeout Selection Pull-down menu used to define the timeout period:
16 seconds
4 seconds
2 seconds
1 seconds
500 milliseconds
250 milliseconds
125 milliseconds
62.6 milliseconds
Blown Fuse Should be set, module will report a blown fuse and will light the
Detection “E” LED.

226 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

14.1.16 R ELAY O UTPUT M ODULE KUEP C ONFIGURATION

Relay Output Module KUEP Dialog Box Fields

Field Description

Timeout Action Reset = After the timeout period, output is cleared (output
transistor is shut off).
Latch = After the timeout period, the last output will be held.
Timeout Selection Pull-down menu used to define the timeout period:
16 seconds
4 seconds
2 seconds
1 seconds
500 milliseconds
250 milliseconds
125 milliseconds
62.6 milliseconds
Blown Fuse Should be set, module will report a blown fuse and will light the
Detection “E” LED.

14.1.17 S EQUENCE OF E VENTS C ONFIGURATION

Sequence of Events Dialog Box Fields (24VDC/48VDC/125VDC single-ended)

Field Description

Chatter Control Action Chatter control counter is reset or it is decremented every 100 ms.
Reset setting is recommended.
Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Detection Should not be set.
Contact Wetting Should not be set.
Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an associated
digital point configured for that channel.
Blown Fuse Detection Should be set, module will report a blown fuse and will light the “E”
LED.

OW240_60 227
14.1 Defining and Configuring Ovation I/O Modules

Sequence of Events Dialog Box Fields (24VDC/48VDC/125VDC differential)

Field Description

Chatter Control Action Chatter control counter is reset or is decremented every 100 ms.
Reset setting is recommended.
Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Detection User can set as needed.
Contact Wetting Should not be set.
Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an associated
digital point configured for that channel.

Sequence of Events Dialog Box Fields (48VDC contact input)

Field Description

Chatter Control Action Chatter control counter is reset or is decremented every 100 ms.
Reset setting is recommended.
Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Detection Should be set.
Contact Wetting Should be set.
Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an associated
digital point configured for that channel.
Blown Fuse Detection When set, the module will report a blown fuse and will light the “E” LED.

14.1.18 C OMPACT S EQUENCE OF E VENTS C ONFIGURATION

Compact Sequence of Events Fields (24VDC/48VDC/125VDC single-ended)

Field Description

Chatter Control Action Chatter control counter is reset or it is decremented every 100 ms.
Reset setting is recommended.

228 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

Field Description

Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Should not be set.
Detection
Contact Wetting Should not be set.
Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an
associated digital point configured for that channel.
Blown Fuse Detection Should be set, module will report a blown fuse and will light the “E”
LED.

Compact Sequence of Events Fields (24VDC/48VDC/125VDC differential)

Field Description

Chatter Control Action Chatter control counter is reset or it is decremented every 100 ms.
Reset setting is recommended.
Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Should not be set.
Detection
Contact Wetting Should not be set.
Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an
associated digital point configured for that channel.

Compact Sequence of Events Dialog Box Fields (48VDC contact input)

Field Description

Chatter Control Action Chatter control counter is reset or is decremented every 100 ms.
Reset setting is recommended.
Chatter Control It is recommended that this not be set and chatter control will be
Disable enabled.
Ground Fault Should be set.
Detection

OW240_60 229
14.1 Defining and Configuring Ovation I/O Modules

Field Description

Contact Wetting Should be set.

Voltage Failure
Detection
Event Tagging Enable Channels that are set will enable the event tagging mask for that
channel.
Note: All channels enabled for event tagging MUST have an
associated digital point configured for that channel.
Blown Fuse Detection When set, the module will report a blown fuse and will light the “E”
LED.

14.1.19 S ERIAL L INK C ONTROLLER C ONFIGURATION

The Serial Link Controller does not need to be configured.

14.1.20 S ERVO D RIVER C ONFIGURATION

Servo Driver Dialog Box Fields

Field Description

I/O Bus Timeout Pull-down menu used to define the timeout

Bits period:
16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
120 milliseconds
60 milliseconds

14.1.21 S PEED D ETECTOR C ONFIGURATION

Speed Detector Dialog Box Fields

Field Description

Number of Teeth Number of teeth on output gear (that is, pulses per revolution)
Gear Ratio Ratio between motor/device and the output gear.

230 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

Field Description

Overspeed Limit Overspeed limit at the motor.

(RPM)
Overspeed Limit (PPS) Read-only information field.
at module
Nominal Speed (RPM) Nominal speed at the motor.
Requested Update Maximum time in microseconds for the speed calculation requested for
Period (misc.) at high resolution reading. When motor operates at nominal speed or
Nominal Speed faster, the update period is guaranteed to be less than this requested
update period.
Pulse Count per This is a read-only information field. It displays the number of pulses
Update used for high revolution speed calculation.
Open Wire Test Enable this option if the module will check for broken wire, and if the
Enabled source resistor is below 1000 ohms.
Overspeed Mode Mode 1 - Controller command or card overspeed trip.
(there are four different Relay is energized by the Controller or by the module when an
modes for energizing overspeed condition is detected.
the relay’s outputs
Mode 2 - Card overspeed trip only.
when an overspeed
condition exists) Relay is energized by the module when an overspeed 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.
Mode 4 is the recommended default mode.

OW240_60 231
14.1 Defining and Configuring Ovation I/O Modules

14.1.22 V ALVE P OSITIONER C ONFIGURATION

Valve Positioner Dialog Box Fields

Field Description

I/O Bus Timeout Bits Pull-down menu used to define the timeout period:
16 seconds
4 seconds
2 seconds
1 second
500 milliseconds
250 milliseconds
120 milliseconds
60 milliseconds
Ignore shutdown If selected, the Valve Positioner module will ignore the input
input in Normal mode.
If not selected, the Valve Positioner module will close the
valve when shutdown input is activated.

232 OW240_60
A P P E N D I X A

DIOB TESTING FOR Q-LINE MODULES

A.1 How is Q-Line Testing Accomplished?

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). (See Ovation DPU Introduction and Configuration Manual.)

Initializing the DIOB test addresses will enable 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 will do a “conditional” fail over.
This means that the partner or backup Controller will assume control of the system until the fault
is cleared. This will only occur 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 will go into alarm and will continue 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.

OW240_60 233
14.1 Defining and Configuring Ovation I/O Modules

A.2 Addressing the Q-Line I/O Modules

Q-Line QBO modules are used to perform the DIOB test. This assumes your system already
contains Q-Line cards that are configured and addressed. The QBO card is addressed by
entering it in hexadecimal format into a dialog box. This box appears when a Q-Line module is
defined and configured by the Ovation Developer Studio (described in Building a Points Folder).

Figure 67: Q-Line Module Address Dialog Box

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 used to determine the jumper settings. (See
Ovation Q-Line Installation Manual.)

234 OW240_60
 14.1 Defining and Configuring Ovation I/O Modules

A.2.1 T O P ERFORM DIOB T ESTING

Perform the following steps to install the DIOB test function.

1. Be sure that QBO cards are installed in each Q-Crate that will be used to complete the test
function. Typically, two QBO cards will be needed to perform the DIOB test. (See Ovation
DPU Introduction and Configuration Manual.)
2. Using the Developer Studio, select the slot for the QBO card that is designated for DIOB
testing and define it as “QBO DIOB Testing.”
3. In the pop-up window, enter the address for the card.
4. Create a digital DIOB Test point at the Controller where the test will be conducted. Assign the
point to Channel 1 of the QBO module.
5. Load the Controller.

Note: Normal operation is indicated by an alternating pattern of flashing LEDs. The LEDs on the
QBO card will alternate between 5555H and AAAAH during normal operation.

OW240_60 235
INDEX

Developer Studio Philosophy • 5

A Drops Function • 8
Analog Input Configuration • 221 Network Folder • 7
Analog Input Points (config) • 190 Points Folder • 8
Analog Output Configuration • 221 Right-Click Menu • 16
Ancillary Labels, Defining • 80 Systems Folder • 6
Ancillary Objects, Creating • 81 Units Folder • 7
Ancillary Objects, Modifying • 82 Developer Studio Components • 12
Dialog Box, Typical • 30
B Hardware View Bar • 12, 21
Menu Bar • 14
Base Station and Operator, Adding Drops •
Menu Bar Options • 12, 14
126
Overview Window • 12, 20
Browse Command bar • 19
Right-Click Menu • 12, 16
C Status Bar • 12
Tool Bars • 12, 16
Clear Function • 33 View Buttons • 12
Command bar, Customizing the • 20 WorkPad Window • 12, 26
Compact Contact Input module • 222 Workspace Window • 12
Compact Digital Input module • 222 Dialog Box, Typical • 30
Compact Sequence of Events module • 232 Digital Input Configuration • 223
Complex Points (config) • 190 Digital Input Points (config) • 191
Analog Input Points • 190 Digital Output module • 223
Analog/Thermocouple Points • 191 Digital Output Points (config) • 192
Digital Input Points • 191 DIOB Testing • 237
Digital Output Points • 192 Download Function • 39
Pulse Accumulator Points • 192 Download Preview window • 39
RTD Points • 192 Downloading • 38
Configuration Folder • 85 Downloading to a Drop • 39
Configuration Folder (Units) Downloading to Multiple Drops • 40
DDB, To Modify • 89 Drop point
Plant Mode • 106 inserting • 138
Plant Mode, Adding • 107 Drop Type folders • 114
Consistency Checking • 37 Drop Types • 114
Contact Input Module • 222 Adding a Advanced Controller Drop • 125
Control Builder • 84 Adding a Base Station Drop • 126
Control Tasks • 84 Adding a Controller Drop • 119
Creating PDS point groups • 203, 207 Adding a Sim Controller • 121
D Adding a Sim Operator Station • 130
adding an NT Station • 128
DDB (Dynamic Data Blocks), Modifying • 88 Drops Folder
Defaults View Bar • 23 adding NT Station drop • 126
Deleting items • 42 control tasks • 84
Dictionary, Deletion from • 97 holding registers • 211
Purge Function • 48 I/O devices folder • 141
TrashCan Bar, Deletion from • 26 inserting a drop point • 138
Undelete Function • 59 SNMP • 98
Developer Studio • 1 types of drops • 113, 114
Dynamic Data Blocks (DDB) • 88
Dynamic Status Feature • 43

OW240_60 237
Ovation I/O Module Dialog Boxes

creating local devices • 154

E I/O Hardware
eDB Point Group Member, Adding • 208 address example for Controller cabinet •
Export Function • 45 147
External Networks Connections • 91 address example for Extended I/O
External Systems Interface • 85 cabinet • 147
address example for relay output
F modules • 147
address example for Remote Node
features • 37
cabinet • 147
Find Function • 45
addressing for I/O modules • 144
Foundation Fieldbus • 155
addressing for Q-Line modules • 153
Function bars • 12, 21
guidelines for positioning modules • 153
hardware • 21
I/O and relay output config example • 144
trashcan bar • 25
I/O elements • 142
Functions, Developer Studio • 33
PCI card • 142
Clear Function • 33
planning I/O in a system • 142
Consistency Checking • 37
relay output base • 144
Download Function • 39
standard I/O base • 143
Downloading to Multiple Drops • 40
I/O modules
Dynamic Status Function • 43
addressing Q-Line • 238
Export Function • 45
I/O modules, Addressing • 144
find function • 45
I/O point hardware mapping • 157
import function • 46
Image Builder • 92
load function • 47
adding icon to dictionary • 96
reboot function • 48
adding icon/class • 95
reconcile function • 49
changing icon in dictionary • 97
search function • 53
deleting icon from dictionary • 97
where used function • 60
inserting new dictionary • 93
G opening existing dictionary • 94
removing icon/class • 95
GBNT • 82 Import function • 46
See Graphics Builder • 82 Inserting a drop point • 138
Graphics Builder • 82
Graphics folder (systems) • 82 L
H Licenses • 74
Commuter License, Workiing with
Hardware bar • 21
Laptop License Check- In • 73
Hardware View Bars • 21
HART Analog Input module • 224 License Code Key • 77
HART Analog Output module • 224 License Manager Operations Area • 76
Holding Register Editor • 215 License Manager, Accessing • 75
Holding Registers License Warning Boxes • 75
Holding Register Editor • 215 Load function • 47
Holding Register Values, Changing Local I/O devices • 154
Multiple • 214 Locking code for licenses • 77
Holding Register Values, Changing Loop Interface module • 225
Single • 214
Holding Register, Inserting a New • 212
M
Holding Register, Opening an Existing • Manager (licenses) • 73, 75
213 Menu bar • 12, 14
Modifying a Point Trend Group • 198
I Modifying a system • 67
I/O Devices folder • 141

238 OW240_60
 Ovation I/O Module Dialog Boxes

adding points to groups • 205, 208

N modifying (at group level) • 204, 208
Naming points • 158 modifying (at member level) • 206, 209
Network Time Protocol (NTP) • 104 Plant Mode • 106
Networks Folder Plant Mode to a Unit, Adding • 107
creating • 68 Point Dialog Box • 161
Modifiying a Network • 69 Point Dialog Box Tabs • 161
NTP • 104 alarm • 161
NT Station drop (adding) • 126 ancillary • 161
NTP (Network Time Protocol) • 104 byte params • 161
config • 161
O descriptions • 163
display • 161
Operation Command bar • 16
eDB • 161
Operator and Base Station, Adding Drops •
hardware • 161
126
initial • 161
OPP
instrumentation • 161
See also Point Processing. • 108
int params • 161
Ovation Modules
limits • 161
analog input configuration • 221
plant mode • 161
analog output configuration • 221
point • 161
compact contact input • 222
real params • 161
compact digital input configuration • 222
security • 161
compact sequence of events
Point Groups folder • 195
configuration • 232
adding points to PDS point groups • 205,
configuring • 221
208
contact input configuration • 222
adding points to point groups • 198
defining • 221
adding trend point groups • 196
digital input configuration • 223
creating PDS point groups • 203, 207
digital output configuration • 223
modifying trend point groups • 198
HART analog input configuration • 224
Point names • 158
HART analog output configuration • 224
reserved characters • 158
loop interface configuration • 225
valid characters • 158
pulse accumulator configuration • 227
Point Processing • 108
relay output G2R configuration • 230
Point Types • 157
relay output KUEP configuration • 231
Points
RTD configuration • 229
See Points folder • 72
sequence of events configuration • 231
Points folder • 72
serial link controller configuration • 234
configuring complex points • 190
servo driver • 234
creating points • 157
speed detector configuration • 234
I/O hardware mapping • 157
Ovation NT Developer Studio
names • 158
See Developer Studio • 1
point dialog box • 161
Overview • 1
point types • 157
Overview window • 12
reserved point name characters • 158
P third-party points • 192
valid point name characters • 158
PCI card • 142 Points, Building • 157
PCQL • 142 Pulse Accumulator module • 227
PCRL • 142 Pulse Accumulator Points (config) • 192
PCRR • 142 Purge items • 48
PDS Point Group Member, Adding • 205
PDS point groups • 203, 207 Q
QBO card • 238
Q-Line modules

OW240_60 239
Ovation I/O Module Dialog Boxes

addressing • 238 Browse Tool Bar • 19

Customizing the Tool Bar • 20
R Operation Tool Bar • 17
Reboot Function • 48 Standard Tool Bar • 16
Reconcile Function • 49 Window Tool Bar • 19
Relay Output Base • 144 TrashCan bar • 25
Relay Output module G2R • 230 deleting items • 42
Relay Output module KUEP • 231 purging deleted items • 48
remote networks • 85 restoring deleted items • 59
Restore a deleted item • 60 Trend Point Group Member, Adding • 198
Right-click menu • 16 Trend Point Groups • 196
RTD module • 229 adding a point • 198
RTD points (config) • 192 modifying point trend group (member
level) • 202
S Types of drops available • 113, 114
Types of points • 157
Search function • 53
Sequence of Events module • 231 U
Serial Link module • 234
Servo Driver module • 234 Undelete Function • 59
Simple Network Management Protocol Units Folder
(SNMP) • 98 adding plant mode to a unit • 107
SNMP • 98 creating • 70
modifying • 103 plant mode • 106
parameter settings • 103
V
using • 98
Speed Detector module • 234 View Buttons • 12
Standard Command bar • 16
Standard I/O Base • 143 W
Status bar • 12 Warning boxes for licenses • 75
System Tree Where Used function • 60
creating networks folder • 68 Window Command bar • 19
creating systems folder • 66 WorkPad window • 12
creating units folder • 70 Workspace window • 12
points folder • 72
System, Inserting a New • 66
Systems folder
Ancillary folder • 80
creating • 66
graphics folder • 82
licenses folder • 73
modifying • 67
point groups folder • 195
point processing • 108
security folder • 79
T
Thermocouple Points (config) • 191
Third-party points • 192
Time for system • 104
Tool Bars • 12, 16

240 OW240_60