OW350 - R1007 维护

Maintaining Your Ovation System
OW350_R1007
(For use with Ovation 3.5 systems)

March 2013
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
TM
the use and application of the Ovation Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@Emerson.com
Web site: https://www.ovationusers.com
Summary of Changes
Maintaining Your Ovation System
OW350_R1007
March 2013
This version of Maintaining Your Ovation System contains the following new information.
 Electrical information for Ovation equipment. (see page 26)
 Guidelines for protecting your Ovation equipment (see page 57).
 Grounding guidelines for clustered cabinets. (see page 74)
 Backing up system software. (see page 95)
 Updated information regarding Replacement Parts. (see page 263)
 Troubleshooting modules. (see page 287)
Contents
1 Introduction to Maintaining your Ovation System 1

1.1 What is an Ovation system? ............................................................................................... 1
1.2 Maintaining your Ovation System ....................................................................................... 2
1.3 System redundancy ............................................................................................................ 2
2 Recommendations for operation and maintenance technicians 3

2.1 Skill level recommendations ................................................................................................ 3
2.2 Software expertise recommendations ................................................................................. 4
2.3 Test equipment familiarity recommendations ..................................................................... 4
2.4 Safety and Tag-out procedures........................................................................................... 4
2.4.1 To execute a normal cabinet power-down sequence for maintenance
or repairs ................................................................................................................ 5
2.4.2 Handling static sensitive devices ........................................................................... 5
2.4.3 To execute a normal cabinet power-up sequence following maintenance
or repairs ................................................................................................................ 6
3 Ovation installation general maintenance 7

3.1 Controller cabinet components (Remote I/O) (OCR400 Controller and
OCR1100 Controller) .......................................................................................................... 7
3.2 Performing inspection and routine maintenance tasks ....................................................... 9
3.2.1 Cleaning and general maintenance guidelines .................................................... 10
3.3 How do I perform a system checkout? .............................................................................. 10
3.3.1 Testing the electrical systems .............................................................................. 10
3.3.2 How is power distributed in an Ovation system? ................................................. 18
3.3.3 Electrical information for Ovation equipment ....................................................... 26
3.3.4 Monitoring power supply status ........................................................................... 50
3.3.5 Fieldbus segment monitoring ............................................................................... 52
3.3.6 To perform a Foundation Fieldbus wiring check .................................................. 53
3.3.7 To perform a Foundation Fieldbus voltage check ................................................ 54
3.3.8 Perform a Foundation Fieldbus signal check ....................................................... 54
3.3.9 Using signal waveforms ....................................................................................... 56
3.4 General DCU/RIO operational checks .............................................................................. 57
3.5 Protecting the Ovation equipment ..................................................................................... 57
3.5.1 Environmental information for Ovation equipment ............................................... 58
3.5.2 Workstations and peripherals (weight, dimensions, and temperatures) .............. 58
3.5.3 Workstations and peripherals (humidity, shock, and vibration) ........................... 61
3.5.4 Workstations and peripherals (altitude and noise) ............................................... 63
3.5.5 Cabinets (weight, dimensions, and temperatures) .............................................. 65
3.5.6 Cabinets (altitude, humidity, and ingress protection) ........................................... 70
3.5.7 Cabinet components (weight, dimensions, and temperatures) ............................ 72
OW350_R1007 i
Table of Contents
3.6 Grounding guidelines for clustered cabinet arrangements ............................................... 74

3.6.1 To remove the shorting bar from an Ovation cabinet .......................................... 75
3.7 Performing outage maintenance ....................................................................................... 76
4 Ovation system maintenance 77

4.1 Hardware preventative maintenance checklist ................................................................. 77
4.2 Periodic Human Machine Interface (HMI) checks............................................................. 78
4.2.1 To review the Windows Event Viewer for warnings and errors ........................... 78
4.2.2 To review system performance ............................................................................ 78
4.3 Ovation Error Log window at the Operator Station ........................................................... 78
4.3.1 To access the Error Log window at the Operator Station .................................... 79
4.3.2 Live Error Log window at the Operator Station .................................................... 80
4.3.3 Historical Error Log window at the Operator Station ............................................ 81
4.3.4 Error Log window menu bar at the Operator Station ........................................... 82
4.3.5 Error Log window toolbar at the Operator Station ............................................... 82
4.3.6 Error Log window columns at the Operator Station ............................................. 83
4.3.7 To use the Choose Columns dialog box at the Operator Station ........................ 86
4.3.8 Priority levels of Error Log messages at the Operator Station ............................. 86
4.3.9 To use the Select Priority Level dialog box at the Operator Station .................... 87
4.3.10 To print Error Log messages at the Operator Station .......................................... 87
4.4 User profile options for Windows domains ........................................................................ 88
4.4.1 To Implement Roaming Profiles ........................................................................... 88
4.4.2 To Implement Mandatory Profiles ........................................................................ 89
4.5 Ovation AntiVirus Upkeep ................................................................................................. 89
4.5.1 Kaspersky troubleshooting tools .......................................................................... 90
4.6 Switch and Router Configuration and Internet Operating System (IOS) .......................... 90
4.6.1 Troubleshooting Routed Network problems......................................................... 91
4.7 Technical tips and best practices ...................................................................................... 91
4.7.1 System Offline Mode ............................................................................................ 91
4.7.2 Setting the Online/Offline mode ........................................................................... 92
4.7.3 Enabled Offline mode attributes ........................................................................... 92
4.7.4 Disabled Offline mode attributes .......................................................................... 92
4.7.5 Fragmentation of a Hard Disk Drive (HDD) ......................................................... 93
4.7.6 To Defragment a hard disk................................................................................... 94
4.7.7 Checking NTP synchronization issues ................................................................. 94
4.7.8 Network Time Protocol (NTP) (Networks folder).................................................. 94
4.7.9 Backing up the operating system and Ovation software ...................................... 95
4.7.10 Backing up the database files .............................................................................. 95
4.7.11 To backup the complete database ....................................................................... 96
4.7.12 To backup the database files ............................................................................... 96
4.7.13 To backup the partial database ............................................................................ 97
4.7.14 To restore a complete database .......................................................................... 97
4.7.15 To restore a partial database ............................................................................... 98
4.7.16 To backup your domain controller ........................................................................ 98
4.7.17 Media, patch, and license management ............................................................ 100
4.7.18 To access the License Manager ........................................................................ 101
ii OW350_R1007
Table of Contents
5 Diagnostic tools and troubleshooting 103

5.1 Ovation diagnostic services ............................................................................................ 103
5.1.1 Field engineering services ................................................................................. 104
5.1.2 SureService Customer Support Programs......................................................... 104
5.2 Ovation system diagnostics tools .................................................................................... 105
5.3 Controller Diagnostics tool .............................................................................................. 105
5.3.1 Software platforms that Controller Diagnostics supports ................................... 106
5.3.2 Controller Diagnostics window ........................................................................... 107
5.3.3 Controller List in the Controller Diagnostics window .......................................... 109
5.3.4 To select a Controller in the Controller Diagnostics window .............................. 110
5.3.5 Controller Overview panel in the Controller Diagnostics window ...................... 111
5.3.6 Controller Diagnostics Update Backup function................................................. 113
5.3.7 To update your backup Controller in the Controller Diagnostics window .......... 113
5.3.8 Control Task Information tab in the Controller Diagnostics window .................. 114
5.3.9 I/O Information tab in the Controller Diagnostics window .................................. 116
5.3.10 What firmware can be downloaded to the I/O modules through
the Controller Diagnostics window? ................................................................... 117
5.3.11 To download firmware revisions to the I/O modules through
the Controller Diagnostics window ..................................................................... 118
5.3.12 To reboot an I/O module .................................................................................... 119
5.3.13 Software Versions tab in the Controller Diagnostics window ............................. 119
5.3.14 Point Details tab in the Controller Diagnostics window ...................................... 120
5.3.15 Sheet Information tab in the Controller Diagnostics window ............................. 121
5.3.16 Refresh function for the Controller Diagnostics window .................................... 122
5.4 What is the Control Logic Navigator utility? .................................................................... 123
5.5 Engineering Tools Audit .................................................................................................. 124
5.5.1 What is the Engineering Tools Audit function? .................................................. 124
5.5.2 What Ovation applications are audited with the Engineering Audit Tools function?
........................................................................................................................... 125
5.5.3 To set the Engineering Audit level ..................................................................... 127
5.5.4 Auditing examples .............................................................................................. 128
5.5.5 Using the Ovation Audit Viewer ......................................................................... 131
5.5.6 What is the Audit log archive? ........................................................................... 140
5.5.7 Audit Log storage ............................................................................................... 141
5.6 System Diagnostic algorithms ......................................................................................... 142
5.6.1 DROPSTATUS ................................................................................................... 143
5.6.2 HEARTBEAT ...................................................................................................... 145
5.6.3 LATCHQUAL ...................................................................................................... 148
5.6.4 PNTSTATUS ...................................................................................................... 150
5.7 Status Information Diagrams........................................................................................... 151
5.8 Non-Ovation diagnostics tools ........................................................................................ 151
5.8.1 AMS suite for use with HART field devices or Foundation field bus devices .... 152
5.8.2 SmartProcess suite of Plant Optimization software ........................................... 152
5.8.3 High Side Digital Output (HSDO) diagnostics .................................................... 154
5.8.4 Wave Web Viewer .............................................................................................. 154
5.8.5 LC/EHC Turbine Controller interface diagnostics .............................................. 156
5.8.6 GE Genius Gateway diagnostics ....................................................................... 156
5.9 SIS operations and maintenance practices .................................................................... 157
5.9.1 Bypasses and other overrides ........................................................................... 157
5.9.2 Fault detection, system response, and repair procedures ................................. 160
5.9.3 Proof testing the Logic Solver ............................................................................ 166
5.9.4 Making online scaling changes in HART transmitters ....................................... 168
OW350_R1007 iii
Table of Contents
5.10 Resolving common installation problems ........................................................................ 169

5.10.1 To determine if Ovation is running ..................................................................... 170
5.10.2 To check for errors that occurred during the installation .................................... 170
5.10.3 To determine if communication has failed (load and downloads) ...................... 171
5.10.4 If the Ovation Developer Studio does not start and connect to the
Local Database Server ....................................................................................... 172
5.10.5 Examples of security related errors ................................................................... 173
5.11 What are the processor module status LEDs for the Controller? ................................... 174
5.12 What are the I/O Interface module status LEDs for the Controller? ............................... 176
5.13 Troubleshooting Routed Network problems .................................................................... 178
5.14 I/O module troubleshooting ............................................................................................. 178
5.14.1 Analog Input modules ........................................................................................ 181
5.14.2 Analog Output modules ...................................................................................... 190
5.14.3 Digital Input modules .......................................................................................... 194
5.14.4 Digital Output modules ....................................................................................... 204
5.14.5 Specialty Modules .............................................................................................. 209
5.15 Bus interface modules ..................................................................................................... 222
5.15.1 How do I troubleshoot Profibus? ........................................................................ 223
5.15.2 How do I troubleshoot DeviceNet? .................................................................... 237
5.15.3 How do I diagnose Foundation Fieldbus device errors? .................................... 244
5.16 Distributed Component Object Model (DCOM) system .................................................. 259
5.17 Optimization package troubleshooting information (Linux OS) ....................................... 260
6 Replacement Parts 263

6.1 Ordering spare parts ....................................................................................................... 263
6.1.1 Determining a spare part number ...................................................................... 263
6.1.2 Determining a spare part price ........................................................................... 264
6.2 Returning parts to Emerson for repair service ................................................................ 264
6.2.1 Obtaining a Material Return Tracking (MRT) number ........................................ 265
6.2.2 Handling in-warranty and non-warranty part repairs .......................................... 266
6.3 Part failure during project startup .................................................................................... 266
6.4 Determining repair prices ................................................................................................ 266
6.5 Tracking part repairs ....................................................................................................... 267
6.6 What is involved in the Replacement of User Serviceable Fuses? ................................ 267
6.6.1 Electronics Module Fuses .................................................................................. 267
6.6.2 Personality module fuses ................................................................................... 268
6.6.3 Ovation Cabinet Fuses ....................................................................................... 269
6.7 Controller Compact Flash disk replacement ................................................................... 269
6.8 Redundant power supply replacement ........................................................................... 270
6.8.1 Power supply replacement cautions .................................................................. 271
6.8.2 To replace redundant power supplies ................................................................ 271
6.8.3 Power supply drawing views .............................................................................. 272
6.8.4 Power supply locking mechanism ...................................................................... 273
6.8.5 1X00024H01 and 1X00024H07 Power supply front view .................................. 274
6.8.6 1X00024H04 and 1X00024H08 Power supply front view .................................. 275
6.8.7 Power supply front view ..................................................................................... 276
6.9 Replacing an online Valve Positioner (RVP) ................................................................... 277
6.9.1 Replacement precautions - (RVP) ..................................................................... 277
iv OW350_R1007
Table of Contents
6.10 Installing Ovation standard I/O modules ......................................................................... 278

6.10.1 To hot swap standard I/O modules .................................................................... 278
6.10.2 To add new standard I/O modules ..................................................................... 279
6.10.3 Installing Ovation Relay Output modules ........................................................... 279
6.10.4 To hot swap Relay Output Electronics modules ................................................ 280
6.10.5 To add new Relay Output I/O modules .............................................................. 280
7 Shipping and Storage of Ovation equipment 281

7.1 Guidelines for shipping Ovation equipment .................................................................... 281
7.2 Guidelines for lifting Ovation equipment ......................................................................... 283
7.3 Guidelines for off-loading and unpacking Ovation equipment ........................................ 284
7.4 Guidelines for repacking and returning Ovation equipment ............................................ 285
7.5 Guidelines for repacking third-party products ................................................................. 285
7.6 Guidelines for transporting Ovation equipment to the specific installation location ........ 285
7.7 Guidelines for storing Ovation equipment ....................................................................... 286
8 Maintenance Training 287

8.1 Maintenance training courses ......................................................................................... 287
Index 289
OW350_R1007 v
S E C T I O N 1
1 Introduction to Maintaining your Ovation System
IN THIS SECTION
What is an Ovation system? ............................................................................................... 1

Maintaining your Ovation System ....................................................................................... 2
System redundancy ............................................................................................................ 2
1.1 What is an Ovation system?

Ovation is a Distributed Control System (DCS) whose modular design permits you to configure
your process management system exactly as it is needed. You can expand a small installation to
include as many as 254 intelligent modules (referred to as drops). Each drop is a separate
module that can perform various functions. Ovation systems use commercially available hardware
platforms, operating systems, and open network technology.
You should consider the following elements when you plan and configure your Ovation system:
 Redundant high-speed network that uses Fast Ethernet standards to send input and output
data to all the stations and Controllers connected to the network.
 Workstations (Windows-based computers) that receive and send data in order to perform
any operations needed to run a process. These workstations are typically connected to a
switch, which is, in turn, connected to the network.
 A Controller that executes modulating and sequential control strategies and interfaces to
input and output modules. The Controller is the drop containing the modules (I/O) that are
attached to sensors on the actual plant equipment. These sensors measure the point values
that are then broadcast onto the Ovation Network.
 Hardware such as cabinets, cables, and grounding equipment.
 Input/Output (I/O) modules that interface field signals (temperature, pressure, and so forth)
from the actual plant processes to the Controller. The Controller sends the information over
the network to the workstations. In turn, messages are sent from the workstations to the
Controller, so that adjustments can be made, as needed, by the Controller.
 Software packages that run on Ovation workstations and perform the tasks needed to
configure, manage, and operate an Ovation system.
Note: Contact your project manager for answers to any questions you might have about your
specific system.
OW350_R1007 1
1.2 Maintaining your Ovation System
1.2 Maintaining your Ovation S ystem
Easy system maintenance begins with correct up-front planning and placement of the system
components. The Planning your Ovation System manual will assist in the correct system layout of
cabinets, workstations, cabling, and grounding so that maintenance is quick and easy.
Emerson has several built-in as well as add-on systems and tools to help with maintenance and
troubleshooting. This manual will try to provide various ways to quickly and easily manage
maintenance and troubleshooting tasks. Some of the more comprehensive tools are:
 Ovation System Diagnostics (see page 105).
 System redundancy (see page 2).
 Intuitive Diagnostics.
 Status Information Diagrams (see page 151).
 Additional System Diagnostics tools (see page 151).
 Ovation Fault Information can be obtained from Ovation System Viewer. Please refer to
Ovation Operator Station User Guide.
 AMS Suite (see page 152).
 SureService Customer Support Program (see page 104).
 SmartProcess suite of Plant Optimization software (see page 152).
It is important to keep a set of Replacement parts. This will ensure that your system can always
function at peak performance levels.
Emerson provides Training (see page 287) for your maintenance personnel as well as a multitude
of SureService Customer Support Program (see page 104) to fit any system. The SureService
Customer Support Programs also provide a quick response to any system disruptions, and will
help reduce the overall maintenance budget. In addition, the SmartProcess suite of Plant
Optimization software (see page 152) helps reduce maintenance costs by promoting better plant
efficiency.
1.3 System redundancy
All critical control, operational, and data management operations are provided with either
redundant components or an independent backup path. Redundancy is not provided at an
individual signal level (transmitter, wiring, I/O interface). However, good control system design
(including control output fail in place or fail to zero) and proper partitioning prevent a single failure
at that level from having a significant impact on continuing operations. Therefore, the entire
Ovation system is extremely fault tolerant.
2 OW350_R1007
S E C T I O N 2
2 Recommendations for operation and maintenance

technicians
IN THIS SECTION
Skill level recommendations ................................................................................................ 3

Software expertise recommendations ................................................................................. 4
Test equipment familiarity recommendations ..................................................................... 4
Safety and Tag-out procedures........................................................................................... 4
2.1 Skill level recommendations

It is recommended that technicians working on the Ovation system should meet the
following skill levels:
 General knowledge of working on and maintaining large scale Distributed Control Systems
(DCS).
 General knowledge of working on and maintaining a DCS down to components in the
Distributed Control Unit (DCU) and the Remote I/O (RIO) cabinet.
 General knowledge of how to work with field devices in order to troubleshoot inputs and
outputs to a DCU/RIO.
Installation
Emerson recommends that installation, and power-up be supervised by qualified Ovation field
engineers. A skill level of journeyman electrician is recommended to place and wire the
Distributed Control Systems, drops, Controller and I/O, and field device terminations.
Maintenance
A skill level of journeyman electronics or instrumentation technician is recommended to maintain

and/or test the DCS to the DCU.
Maintenance and/or testing requires competence with Microsoft Windows. It is suggested that
maintenance personal attend applicable Ovation Training Courses to become more competent
and efficient in their maintenance tasks on the Ovation system.
OW350_R1007 3
2.2 Software expertise recommendations
2.2 Softw are expertise recommendations

It is recommended that technicians working on the Ovation system should possess the
following software expertise:
 General knowledge in the use of Microsoft Windows (Windows 7 Professional SP1 and
higher) and/or Solaris (UNIX) operating systems.
 Background and training in the use of applicable Ovation software.
 Knowledge of special software needed to maintain the system (requires specific Ovation
Training).
 Experience with any network diagnostic software provided by Emerson (requires specific
Ovation Training).
 Where applicable, a knowledge of printer manager software.
2.3 Test equipment familiarity recommendations

It is recommended that technicians working on the Ovation system should be familiar with
any of the following test equipment that will be used on their system:
 Working knowledge of a Voltmeter in order to check the output of the Ovation Power Supply
to the I/O branches.
 The use of a signal injection device in order to check input points to the DCU/RIO and for loop
checks.
 An ohmmeter to ensure grounding measurements are at or below Ovation standard
requirements.
 Special test equipment including a network analyzer.
 A multi-function calibrator to simulate analog inputs or record analog outputs to/from the
DCU/RIO when troubleshooting analog I/O signals.
2.4 Safety and Tag -out procedures

It is recommended that technicians working on the Ovation system should be familiar with
the following procedures:
 The use of a grounding strap is required when working in Ovation DCU/RIO cabinets.
 When working in all cabinets, ensure that the I/O terminals are not contacted directly by any
personnel.
 Lock out and/or Tag out any device being worked on, according to the plant operations
guidelines.
 Ensure that when a device is tagged out in the field, it is also indicated on the Ovation system
graphics.
WARNING! Be aware that High Voltage could still be present in the cabinet due to the
powering of I/O from external field devices, or cabinet distributed high voltage.
Note: For additional information, see the Planning Your Ovation System manual.
4 OW350_R1007
2.4 Safety and Tag-out procedures
2.4.1 To execute a normal cabinet power-down sequence for maintenance or

repairs
1. Assure that the power-down of one or more DCSs/RIOs inputs and outputs (and assumption
of default values) will leave the plant processes in a safe condition.
2. Turn off the Controller supplying information to the DCUs/RIOs in question.
3. Turn off power supplies in any of the DCUs/RIOs in question.
4. Turn off all circuit breakers to the DCU/RIO in question.
Note: Some digital inputs are wetted (powered from) 120 VAC UPS power. Digital input power
is fused on an individual branch basis. A removable 3.1A 120VAC fuse is provided for each
branch.
2.4.2 Handling static sensitive devices
When handling static sensitive devices, follow the guidelines below to prevent damage that can
be caused by static electricity:
 Treat all printed circuit cards as static-sensitive devices.
Many printed circuit cards contain static-sensitive devices. These devices vary in their
sensitivity to static electricity.
 Handle printed circuit cards as little as possible. Handling boards, for example, removing
them from card files, transporting them, or storing them, entails the greatest risk of
electrostatic damage.
 Wear a grounded wrist strap whenever you handle printed circuit cards. Each enclosure
should have a grounded wrist strap with a protective resistor. Connect the wrist strap to a
point in the enclosure, which is connected to an AC ground bus or isolated local or master
ground bus. Before removing a card from a file, attach the wrist strap snugly to your wrist and
wait about 10 seconds before touching the card. Pull back shirt sleeves so that they do not
touch the card. Hold a card only by its edges; never touch components, the printed circuit, or
the edge connectors.
 Transport and store printed circuit cards in static shielding (not merely anti-static) containers.
As long as the container is sealed, electrostatic damage normally does not occur. Use static
shielding bags or boxes for storage and shipping of printed circuit cards. The factory ships
printed circuit cards in boxes with conductive liners. Labels on these boxes identify the
contents as static sensitive.
 Do not put static generating material inside a static shielding container with printed circuit
cards. Such action negates the reason for using the static shielding container.
 Ground static shielding containers before removing printed circuit cards. Before removing
cards from shipping containers, ground yourself and the box conductive liner. Save such
boxes for storage and future shipping of cards. Only use anti-static or static shielding packing
material.
 Work on or examine printed circuit cards only at a static-controlled work area with a grounded
wrist strap and a grounded table mat or table surface.
 Keep all static producing materials well away from the work area. Ground all test equipment
at the work area.
OW350_R1007 5
2.4 Safety and Tag-out procedures
2.4.3 To execute a normal cabinet power-up sequence following maintenance or

repairs
1. Ensure that power-up of the DCS/RIO inputs and outputs, and activation of DCS command
values will leave the plant processes in a safe condition.
2. Turn on the all circuit breakers to DCU/RIO in question.
3. Turn on power supplies in any of the DCUs/RIOs in question.
4. Turn on the Controller supplying information to the DCUs/RIOs in question.
Note: Some digital inputs are wetted (powered from) 120 VAC UPS power. Digital input power
is fused on an individual branch basis. A removable 3.1A 120VAC fuse is provided for each
branch.
6 OW350_R1007
S E C T I O N 3
3 Ovation installation general maintenance
IN THIS SECTION
Controller cabinet components (Remote I/O) (OCR400 Controller and OCR1100 Controller)
............................................................................................................................................. 7
Performing inspection and routine maintenance tasks ....................................................... 9
How do I perform a system checkout? .............................................................................. 10
General DCU/RIO operational checks .............................................................................. 57
Protecting the Ovation equipment ..................................................................................... 57
Grounding guidelines for clustered cabinet arrangements ............................................... 74
Performing outage maintenance ....................................................................................... 76
3.1 Controller cabinet components (Remote I/O) (OCR400 Controller

and OCR1100 Controller)
The Ovation Remote I/O Controller cabinet contains the following:

 Redundant Controller Chassis - This rack in the Controller cabinet provides the backplane for
two separate Controllers. For each Controller, the backplane interconnects the following
components:
 CPU module. Includes Fast Ethernet network interface.
 IOIC module - I/O interface Controller module serving as the master of the remote I/O
bus. Refer to the Q-Line Installation Manual for remote Q-Line I/O installation information
(only 850 nm optics, with 2 km Maximum length, are available for remote Q-Line
applications).
An IOIC module has two Attachment Unit Interface (AUI) ports each of which may
connect to an Attachment Unit module using an AUI cable. Together, the two ports
typically serve as the primary I/O bus master with another IOIC providing the redundant
pair.
The IOIC module provides local power for itself and the CPU module.
 Power Supply - DIN Rail Mounted. Generates +24V to power the electronics in the I/O
Controller Cabinet, as well as +24V auxiliary power. Two are required for redundancy. An
optional separate +48V auxiliary power supply is also available.
 Power Distribution module (5X000489G01) - Provides connectors for cables used to distribute
+24V to the Redundant Controller Chassis, and +24V and auxiliary power to branches of local
I/O.
 Standard I/O modules and bases - Standard Ovation I/O modules which interface to field
devices.
 Relay Output module and bases - Relay module base, 1.5 times larger than a standard I/O
base unit, containing Electronics module and relays to control field devices).
OW350_R1007 7
3.1 Controller cabinet components (Remote I/O) (OCR400 Controller and OCR1100 Controller)
 I/O Dual Branch Transition Panel (ROP - 4D33922) - Connects to two branches of I/O,
providing a point to bring in +24V redundant power, auxiliary power, and the local I/O
communications bus.
Connections are provided on the I/O Transition Panel to daisy-chain the local
I/O communications bus from one ROP to the next (up to eight I/O branches Maximum may
be daisy-chained together).
 I/O Branch Terminator (1B30023) - Connects to the A or B-side of a standard
I/O base at the end of a branch having no Attachment Unit module to terminate the local I/O
bus.
CAUTION! The I/O addressing for the Ovation database is determined from the positions of
the bases installed in the cabinets.
Emerson recommends that all possible bases (typically four) be installed in the right-most
branch of each side of a cabinet, even if they are not all filled with I/O modules. This prevents
disruption of the database if additional I/O modules are installed in the future.
I/O modules should be installed in the right-most branch of each side of a cabinet from the
BOTTOM UP. I/O modules should be installed in the left-most branch of each side of a cabinet
from the TOP DOWN.
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 position on the branch
(positions 1/2, 3/4, 5/6, or 7/8).
 Media Attachment Unit (MAU) - This module provides a point of attachment for fiber optic
cables used to transfer messages over long distances between the IOIC and up to four
remote nodes. The module directs messages between the IOIC and one of the four remote
nodes at a time as selected, converting signals readable by the IOIC to signals compatible
with the fiber optic media and vice versa. The following components comprise the MAU:
 Electronics module (1C31179) - Houses the Attachment Unit Logic Board (LAU) which
provides power for the module and displays LED indication that the fiber optic cables are
connected and the Remote Node Controller module has power.
 Personality module (1C31181) - Houses the Attachment Unit Personality Board (PAU)
which translates signals between the PCRR and the fiber optic media and provides
connectors for the fiber optic cables.
8 OW350_R1007
3.2 Performing inspection and routine maintenance tasks
MAU Subsystem
ELECTRONICS PERSONALITY 1 CHANNELS OPTICS

LENGTH OF OPTICAL LINK
MODULE MODULE
1C31179G01 1C31181G01 Up to 2 kilometers (6,560 ft) 2 850 nm

1
In order not to be required to select extended IOIC time-out periods, it is recommended that you do NOT
exceed an optical length of 3.7 km.
2
An Ovation Controller cabinet MAU MUST use the same type of optics (850 nm or 1300 nm) for each of
the remote nodes that it interfaces. An MAU cannot interface both 850 nm remote nodes (using
1C1204G01 Personality modules) and 1300 nm remote nodes (using 1C31204G03 Personality modules.)
 Media Attachment Unit Base (1C31206) - This base holds a Maximum of two modules
and provides a connector for the AUI Cable which interconnects the IOIC and Attachment
Unit module. The backplane routes +24V to the Attachment Unit modules for power. It
also provides local I/O bus termination.
Therefore, I/O branch terminator boards are not required at the end of branches where Media
Attachment Unit modules are placed.
3.2 Performing inspection and routine maintenance tasks
The following tasks should be performed quarterly by a qualified Instrument Technician. The total
estimated time for all tasks is two hours, with no deficiencies noted.
 Cleaning (also see Cleaning and maintenance guidelines (see page 10))
 Door air filter (clean and/or replace)
 Any other filters (clean and/or replace)
 Cabinet floor
 Controller compartment
 I/O modules
 Inspection
 Corrosion
 Physical damage
 Fuses
 Ground cables
 All cooling fans
 Voltage and status readings (see To perform a voltage check (see page 53))
 24 VDC power supplies
 120 VAC inputs
 LED indications on Controller
OW350_R1007 9
3.3 How do I perform a system checkout?
 Equipment manuals - Refer to the following Ovation system documents

 Planning Your Ovation System
 Ovation I/O Reference Manual
3.2.1 Cleaning and general maintenance guidelines
Use the following guidelines for best performance and appearance of your Controllers:
 To ensure optimum air flow, it is recommended that the air filters on the ventilated cabinets be
checked on a regular basis and replaced if necessary.
 The air filters can be accessed by removing the snap-on filter grills on the top and bottom of
each ventilated cabinet door. Replacement filters can be ordered using Emerson part number
5A26317H03.
Note: Air filters should be checked and replaced by qualified service personnel only.
 Routine cleaning can be done with a damp (water only) cloth. Ensure that no water is
splashed or spilled on the equipment. DO NOT use cleaning agents.
 The standard Ovation cabinets are not watertight. Suitable measures should be taken to
ensure that liquids are not splashed onto or spilled into the equipment.
After installation is complete, perform a checkout to ensure a successful startup. Checkout

generally includes testing both the wiring and the communications signal using standard tools
such as a multimeter, capacitance meter, and scope meter.
3.3.1 Testing the electrical systems
Startup testing consists mostly of verifying:

 Power supplies (see page 10).
 Communications (see page 15).
 Redundancy checks during an installation or outage process (see page 16).
 Electrical interference (see page 17).
 Fieldbus segment monitoring (see page 52).
Power supplies
Visually inspect power supplies, DCUs/RIOs and I/O modules for correct power indications.
Power supplies should display green lights, to indicate that power is on for the device
10 OW350_R1007
Power supply features
Ovation power supplies provide the following features:

 Wide range inputs.
 85 - 264 VAC
 88 - 187 VDC
 47 - 63 Hz, AC Models.
 AC Input Power Supply.
 Input Inrush Current = 10A Max, 100VAC, 120VAC
5A typical 100VAC
4A peak 120VAC
7A peak 230VAC
 Input Current = 2.65 A rms, Vin = 100VAC @24VDC, 10A
1.22 A rms, Vin = 230VAC @24VDC, 10A
 DC Input Power Supply.
 Input Current = 2.37 A DC, Vin = 110VDC @24VDC, 10A
 Reverse polarity and Improper Lead Connection.
 You should always make proper connections to the power distribution module which
provides power to the Ovation power supplies. This ensures proper operation and safety
to the Ovation cabinet and associated electronics. The power supply units are tolerant of
a reversal at the inputs, but proper terminations are important in maintaining the overall
integrity and safety of the system.
 Improper voltage level and/or frequency.
 You should always maintain proper input voltage and frequency ranges for the applicable
power supply unit. Failure to do so could cause the power supply output to go beyond the
specification limits or cause the output to shut off which could result in a system upset.
 Recommended Power Supply Replacement Procedure.
 If a failure occurs in the redundant Ovation Powering scheme, Emerson recommends that
you follow the power supply replacement procedure outlined in Ovation I/O Reference
Manual.
 Main power supply and auxiliary power supply are individual DIN rail power supply units.
 24 VDC auxiliary output.
 Power factor corrected
 Hot swap capability (online replacement in redundant configurations)
 26 mS @ 100VAC, 28 mS @ 230 VAC Hold-up (Full load).
OW350_R1007 11
 LEDs on the front panel indicate conditions of input/output voltages.
Figure 1: Typical power supply front panel
12 OW350_R1007
Power supply module
There are Ovation power supply modules available for AC or DC input voltage.
 AC/DC module 1X00781H01L
 Uses 85 to 265 VAC or 88 to 187VDC
There is one type of power supply module available (for AC or DC input):

 Auxiliary power supplies provide power only to field items (such as analog input current loops
and relay coils).
 Main power supplies provide power to the Controller and I/O modules.
AC/DC Power Supply Modules (1X00781H01L)
MODULE OUTPUT DESCRIPTION
1X00781H01L 240 Watt - 24 Volt Single output
Power supply limits
The following limits are given per power supply:
Main Power Supply
The Main portion of the power supply module supplies +24 VDC to the Controller and the I/O
modules.
The sum of the Controller power and the total I/O power MUST be less than the 240 watt capacity
of the Main power supply.
Auxiliary Power Supply
The Auxiliary portion of the power supply module typically powers the relay panels, field
transmitters, and single-ended 24/48 Volt Digital Input modules.
The sum of the relay panels, transmitter, and Digital Input power MUST be less than the 240 watt
capacity of the Auxiliary power supply.
OW350_R1007 13
Controller Cabinet On/Off Controls
Cabinets contain the following switches:

 Cabinet circuit breaker/on/off switch (see page 14).
 Controller power switch (see page 15).
Cabinet circuit breaker/on/off switch
Each cabinet provides a cabinet circuit breaker/on/off switch for the primary and backup input
power feeds. The two power supply sets form a redundant (auctioneered) pair.
Switching off power to the first set of power supplies (or losing the first set of power supplies),
while the second set of power supplies are working, will NOT cause loss of power to the
Controller, I/O, or field devices using power supply voltage.
Switching off power to both sets of power supplies (or losing both sets of power supplies) powers
down the entire cabinet, as well as any field devices that are powered from the cabinet.
Switching on power to either set of power supplies in the redundant pair provides power to the
Controller, energizes the I/O modules, and energizes any field devices using power supply
voltage. For correct operation of the redundant powering scheme, both cabinet circuit
breakers/on/off switches must be energized. Each set of power supplies (primary and backup)
has an independent switch in order to power up these units independently.
14 OW350_R1007
Controller power switch
Each redundant Ovation Controller has a Controller on/off power switch. Switching off a
redundant Controller powers down the processor card, the IOIC card(s), and the NIC card
associated with the Controller. However, this will NOT power down the partner Controller or any
of the I/O and field devices associated with the cabinet.
Even if both redundant partner Controllers are switched off, this will NOT power down the I/O or
any field devices associated with the cabinet.
Once the cabinet circuit breaker on/off switch is energized for the redundant powering scheme,
the Controller power switch will energize the Controller. Once energized, the Controller performs
its startup routine and begins executing application code if the Controller was previously
programmed with application code. Each Controller has an independent power switch. Both
Controllers must be energized for proper operation in a redundant Controller scheme.
Figure 2: Ovation OCR400 or OCR1100 Controller Cabinet Configuration (illustrating

controls)
OW350_R1007 15
Communications
Visually inspect each I/O module for a green C (communications) light. Monitor the System Status
screen to verify that the DCU/RIO is communicating on the network.
Redundancy checks during an installation or outage process
CAUTION! All plant processes controlled or monitored by Ovation should be shut down with
appropriate lockout/tagout in place when redundancy checks are performed.
Redundancy checks should never be performed during normal plant operation or for routine
maintenance.
Power supplies
 Turn each power supply off one at a time. Verify that DCUs/RIOs stay online by using the
System Status screen and Alarm Window.
 Verify that power supply alarms are indicated. Make sure that one power supply is on at all
times.
DCUs/RIOs
 Turn off the backup DCU/RIO.
 Use the System Status screen and Alarm Window to verify that the remaining DCU/RIO is
working.
 Turn on the backup DCU/RIO.
 Once the DCU/RIO has started up, turn off the primary DCU/RIO.
 Verify that the backup DCU/RIO has assumed control and is operating correctly.
 Turn on the primary DCU/RIO.
 Once the primary DCU/RIO is up, turn off the backup DCU/RIO.
 Verify that the primary DCU/RIO is once again in control.
Network
 Disconnect Ethernet cables from DCUs/RIOs.
 Monitor system status screen for connectivity indications.
 DCUs/RIOs are dual homed and loss of one feed should not result in any action.
A complete loss of communication will cause the DCU/RIO to go into failed mode.
 If the failed DCU/RIO was in control, the backup DCU/RIO will assume control.
16 OW350_R1007
Checking for electrical interference
An oscilloscope can be used to observe electrical interference on control signals and grounding
systems. A 200 MHz or higher bandwidth oscilloscope with storage capability is preferred. There
are several brands available, and most use PC interface software to perform trace data captures.
A usable scope for this purpose is the Fluke 199, 200 MHz Scopemeter, or equivalent.
WARNING! Improper use of an oscilloscope can lead to electrical shock, and may affect the
normal operation of the manufacturing process. Be extremely careful when connecting to high
voltage power cables and process signals. Read and follow the directions provided by the
oscilloscope manufacturer prior to its use.
If you are using an AC-powered oscilloscope, it must use a floating input signal ground to obtain
correct readings. However, a floating input signal ground may be hazardous, as noted in the
warning above.
Monitor the following signals to determine the presence of electrical interference:

 Analog Input and Output Signals: Electrical noise on analog-only signals usually does not
cause faults because the unwanted electrical noise is filtered out.
 Digital Communications: Electrical noise can cause faults in digital communication signals by
adding spikes and other noise that the communication system interprets as part of the digital
signal.
 Power Supply Ground to +24 VDC: Electrical noise will be present. However, the noise spikes
should be less than one volt peak to peak. If the noise spikes are greater than 1-volt peak to
peak, the noise source should be located and remedial action taken.
 Power Supply Ground to Enclosure Ground: Electrical noise will be present. However, the
noise spikes should be less than one volt peak to peak. If the noise spikes are greater than
one volt peak to peak, the noise source should be located and remedial action taken.
OW350_R1007 17
3.3.2 How is power distributed in an Ovation system?
Note: Ovation Equipment is designed for installation in an Overvoltage Category II environment

per IEC 60664. Overvoltage Category II Equipment is designed for connection to the permanent
electrical installation of a building.
Power for Ovation systems is distributed in the following methods:

2
 The primary and backup input power cables (maximum size = 10 AWG (4 mm )) are
connected to the AC input DIN rail.
 There is a single wiring harness from the input DIN rail components (mains power) to each
power supply.
 There is a single wiring harness between the PDM and each power supply. This harness
routes DC power (main and auxiliary) to the PDM.
 Ovation systems can use AC or DC cabinet power supplies, or a combination of both. The
type used is dependent upon the needs of the system application. (AC power supplies and
AC mains are supported in CE Mark certified systems.)
 The PDM distributes power from cabinet power supplies to the following components:
 I/O transition panels (ROP, RRP, and RRB) (see page 23).
 Remote node transition panel (TND) (see page 23).
 OCR400 Controller chassis (see page 25).
 Additional cabinets.
 The IOIC module in the Controller chassis picks up 24 VDC main from the Controller
backplane and converts it to +5 VDC and +3.3 VDC for use by the Controller boards. The
Controller contains two IOIC modules (one for the left Controller and one for the right
Controller).
 Redundant main and auxiliary power is supplied to the CBO backplane and transition panels
through a harness and then passed through the Two Way Interface (TWI) connectors to I/O
modules.
 Fuses are provided on the Controller backplane (CBO), and I/O transition panels (ROP, RRP,
RRB, and TND) for the auxiliary power supplies.
 Each I/O electronics module is equipped with auctioneering diodes for regulating redundant
main power.
18 OW350_R1007
Example of OCR400 Controller/Marshalling cabinet (with local and remote cabling)
Note: For the power distribution scheme, refer to the Power distribution scheme for Ovation 3.5
section.
Figure 3: OCR400 Controller/Marshalling cabinet
OW350_R1007 19
Example of extended I/O cabinet (illustrating cables and standard I/O)
section.
Line Filter Primary AC/DC Line *

(CE Mark certified
Input (external)
+24V main, +24V system only)
AUX (internal)
Backup AC/DC Line
Input (external)
P1 P2
Power
Local I/O Communications Distribution
+24V main, +24V P5 P7
Cable from Controller or Remote Module
P ow er S upply
P ow er S upply
Node Cabinet (external) Br "n-1" AUX, and AC/DC
P rim ary
B ackup
line (internal)
+24V to Cabinet Fans

+24V main, +24V (internal)
AUX (internal)
P12 To extended Local

I/O Cabinet
P13 (external) Br "n+4"
P1 P2
P7 P8
P1 P2
Local I/O
Transition Panel
(ROP)
Local I/O
Transition Panel Local I/O
(ROP) Communications
Cable (internal)
I/O
Base and
Modules
I/O
Base and
Modules
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
do not exit cabinet.
External cables
exit cabinet.
Earth ground
cables not shown.
Br "n" Br "n + 1" Br "n + 2" Br "n + 3" Local I/O

Bus
Terminators
Cabinet Cabinet
Front Back
* AC Power Supplies are applicable for CE Mark Certified systems.
Figure 4: Extended I/O cabinet (illustrating cables and standard I/O)
20 OW350_R1007
Example of extended I/O cabinet (illustrating cables and relay output modules)
section.
Local I/O Communications Line Filter Primary AC/DC Line *

Cable from Controller or Remote (CE Mark certified
Input (external)
Node Cabinet Branch "n-1" (external) +24V main, system only)
+24V aux (internal)
Backup AC/DC Line
P1 P7 P8 P2 Input (external)
Relay Base
Transition Panel P1 P2
Power
(RRP)
P5 P7 Distribution
+24V main,
Module
P ow er S upply
P ow er S upply
+24V aux, and
AC/DC line (internal)
P rim ary
B ackup
+24V to DC Fans
+24V main, (internal)
+24V aux (internal)
P12 To extended Local

P13 I/O Cabinet
Branch "n+3"
(external)
P7 P8
P1 P2
Local I/O
Transition Panel
Local I/O (ROP)
Communications
Cable (internal)
"n+1"
Standard I/O
Base and
Modules
Relay Output
Base and
Module *
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
External cables
exit cabinet.
Earth ground
cables not shown. Local I/O
Bus
Terminators
Relay Base
Transition Panel Branch "n" ** Branch "n+1" Branch "n+2"
(RRB)
Cabinet Cabinet
Front Back
* AC Power Supplies and Relay Output modules/bases are applicable for CE Mark Certified systems.
** With the RRP/RRB, one branch in the addressing scheme (containing 8 Relay Output modules) uses both the left and right side din rails.
Figure 5: Extended I/O cabinet (illustrating cables and relay output modules)
OW350_R1007 21
Example of Ovation Remote Node cabinet (illustrating cables)
section.
Line Filter Primary AC/DC Line *

(CE Mark certified Input (external)
Cabinet system only)
Back
Backup AC/DC Line
Remote Node Controller (RNC) Input (external)
Base and Modules
P1 P2
+24V main, +24V Power
AUX (internal) Distribution
P5 P7
Module
P ow er Su pply
P ow er Su pply
Primary
P rim ary
B ackup
Fiber-Optic
Cable +24V to DC Fans
+24V main, +24V
(internal)
AUX, and AC/DC
J7
line (internal)
Backup P12
Fiber-Optic To extended Local
P13
Cable I/O Cabinet
+24V main, +24V (external) Br 5
AUX (internal) P1 P7 P8 P2
Remote Node Local I/O

Transition Panel Transition Panel
(TND) (ROP)
Local I/O
Communications
Cable
I/O Base
and
Modules
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
External cables
exit cabinet.
Earth ground
cables not shown.
Br 1 Br 2 Br 3 Br 4
Local I/O
Bus
Terminators
* AC Power Supplies are applicable for CE Mark Certified systems.
Figure 6: Ovation Remote Node cabinet (illustrating cables)
22 OW350_R1007
Example of Ovation Power Distribution Module (PDM)
Figure 7: Ovation Power Distribution Module (PDM)
Examples of transition panels
Figure 8: Ovation I/O Transition Panel (ROP)
OW350_R1007 23
Figure 9: Ovation Remote Node Transition Panel (TND)
+24V and AUX Power Connectors

Local I/O Bus Cable from Branch "n-1" Local I/O Bus Cable to Branch "n+1"
(P7 supplies power to P8, to +24V fans, and to (if existing)
the left side of Branch "n")
IN OUT
AUX Supply Fuses for
left side of Branch "n" P7 P8
Bus Termination for Branch "n"
+24V Power Connectors
for Cabinet Fans
F1 F2
PGND PGND
TWI Connector to left side of Local Branch "n" TWI Connector to right side of Local Branch "n"
(starting point of branch addressing)
Note
The RRP is typically used in conjunction with the RRB.
Figure 10: Relay Base Transition Panel (RRP at top of branch)
24 OW350_R1007
Figure 11: Relay Base Transition Panel (RRB at bottom of branch)
Example of Controller OCR400 and Controller OCR1100 backplane
Figure 12: Controller OCR400 and Controller OCR1100 backplane
OW350_R1007 25
3.3.3 Electrical information for Ovation equipment
The following sections provide tables containing electrical information for the Ovation equipment:
 I/O cabinets (main/aux power and main/aux heat dissipation (drawn from AC/DC Mains
power) (see page 30).
 Example of calculating power requirements for OCR400 and OCR1100 Controllers (see
page 49).
 Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Mains power) (see page 32).
 Bus interface modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
 Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
 Specialty I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
 Remote function modules (main/aux power and main/aux heat dissipation (drawn from AC/DC
You can also refer to Ovation equipment spec sheets.
Note: All devices are subject to change as technology improves and evolves.
26 OW350_R1007
Workstations and peripherals (input voltage and input frequency)
DEVICE EMERSON PART INPUT VOLTAGE INPUT

NUMBER V AC FREQUENCY HZ
Engineering Station or Database 5X00628 100 to 240 VAC 50 to 60 Hz

Server
Workstation (Dell T3500)
Engineer Client, Operator, or Virtual 5X00628 100 to 240 VAC 50 to 60 Hz
Controller Workstation
(Dell Optiplex 9010)
Domain Controller 5X00487 100 to 240 VAC 50 to 60 Hz
or Terminal Server Host Workstation
(Dell T310)
Ovation Process Historian 5X00488 100 to 240 VAC 50 to 60 Hz
(Dell T310)
EDS Workstation Linux 5X00567 100 to 240 VAC 50 to 60 Hz
EDS Workstation Windows 7 5X00569

(Dell T5500)
EDS Workstation Linux Rack Mounted 5X00568 100 to 240 VAC 50 to 60 Hz
EDS Workstation Windows 7 Rack 5X00570
Mounted
(Dell R710)
Rack Mount Operator Station 5X00461 90 to 240 VAC 50 to 60 Hz
(Dell R5400) 5X00559
Rack Mount Server Domain Controller 5X00462 90 to 264 VAC 47 to 63 Hz
(Dell R710)
Rack Mount Server 5X00463 90 to 264 VAC 47 to 63 Hz
Ovation Process Historian (OPH)
(Dell R710)
19" Dell 190S FP Monitor 5X00473 100 to 240 VAC 47 or 63 HZ
20" Dell 2007FP Monitor 5X00310 100 to 240 VAC 47 or 63 Hz
24" Dell U2410WFP Monitor 5X00474 100 to 240 VAC 50/60 Hz
32" NEC LCD V321 5X00493 100 to 120 VAC or 50/60 Hz
220 to 240 VAC
40' LCD NEC P401 Monitor 5X00494 100 to 120 VAC or 50/60 Hz
220 to 240 VAC
46' LCD NEC P461 Monitor 5X00495 100 to 120 VAC or 50/60 Hz
220 to 240 VAC
Ovation Keyboard 4D33935 90 to 264 VAC 47 to 63 Hz
OKIDATA Microline 395C Printer 5X00445 90 to 132 VAC or 50 to 60 Hz
(Alarms) 180 to 254 VAC
HP B/W Laserjet 5200 Printer 5X00328 90 to 140 VAC H01 or 48 to 62 Hz
OW350_R1007 27
DEVICE EMERSON PART INPUT VOLTAGE INPUT

NUMBER V AC FREQUENCY HZ
198 to 264 VAC H02
HP Thermal/Inkjet 2800TDN Printer 5X00243 90 to 264 VAC 48 to 62 Hz
HP Color Laserjet Enterprise 5X00520 110 to 127 VAC or 50 to 60 Hz
CP4525n/4525dn 220 to 240 VAC
HP Color Laserjet 5525 5X00550 110 to 127 VAC or 50 to 60 Hz
220 to 240 VAC
Breeze-Hill TMT7-9100 Optical Device 5X00367 100 to 240 VAC 50 to 60 Hz
RAID SATA to iSCSI Media 5X00523 Not Available Not Available
Workstations and peripherals (input current, power consumption, and heat dissipation)
DEVICE EMERSON INPUT CURRENT POWER HEAT

PART NUMBE R CONSUMPTION DISSIPATION
Engineering Station or 5X00557 6A at 115V 350 watts 1194 BTUs

Database Server per hour
Workstation 3A at 230V
(Dell T3500)
Engineer Client, Operator, 5X00628 5.0A max. (low AC 76 watts 260 BTUs per
or Virtual Controller range) hour
Workstation
2.5A max. (hight
(Dell Optiplex 9101) AC range)
Domain Controller 5X00487 8A at 115V 666 watts 2275 BTUs
or Terminal Server Host per hour
Workstation 4.5A at 230V
(Dell T310)
Ovation Process Historian 5X00488 8A at 115V 666 watts 2275 BTUs
(Dell T310) per hour
4.5A at 230V
EDS Workstation Linux 5X00567 Not available 201 watts 689 BTUs per
hour
EDS Workstation Windows 7
5X00569
(Dell T5500)
EDS Workstation Linux Rack 5X00568 3.1A at 115V 329 watts 1123 BTUs
Mounted per hour
1.5A at 230V
EDS Workstation Windows 7
Rack Mounted 5X00570
(Dell R710)
Rack Mount Operator 5X00461 Not available 311 watts 1062 BTUs
Station per hour
5X00559
(Dell R5400)
Rack Mount Server Domain 5X00462 7A at 115V 570 watts 1945 BTUs
Controller per hour
3A at 230V
(Dell R710)
28 OW350_R1007
DEVICE EMERSON INPUT CURRENT POWER HEAT

PART NUMBE R CONSUMPTION DISSIPATION
Rack Mount Server 5X00463 7A at 115V 570 watts 1945 BTUs

per hour
Ovation Process Historian 3A at 230V
(OPH)
(Dell R710)
19" Dell 190S FP Monitor 5X00473 0.3A 35 watts 119.5 BTUs
per hour
20" Dell 2007FP Monitor 5X00310 0.5A 55 watts 187.6 BTUs
per hour
24" Dell U2410WFP Monitor 5X00474 2A 110 Watts 375 BTUs per
hour
32" NEC LCD V321 5X00493 1.4A at 140 watts 341 BTUs per
100-120V hour
0.6A at
220-240V
40' LCD NEC P401 Monitor 5X00494 3.5A at 175 watts 597 BTU per
100-120V hour
1.45A at
220-240V
46' LCD NEC P461 Monitor 5X00495 3.9A at 210 watts 717 BTUs per
100-120V hour
1.6A at
220-240V
Ovation Keyboard 4D33935 Not available Not available Not available
OKIDATA Microline 395C 5X00445 Not available Not available Not available
Printer (Alarms)
HP B/W Laserjet 5200 5X00328 10A at 550 watts H01 1875 BTUs
Printer 120 VAC H01 per hour H01
600 watts H02
5A at 2046 BTUs
230 VAC H02 per hour H02
HP Thermal/Inkjet 2800TDN 5X00243 2.2 A 67 watts 228 BTUs per
Printer hour
HP Color Laserjet Enterprise 5X00520 Not available 720 watts 246 BTUs per
CP4525n/4525dn hour
HP Color Laserjet 5525 5X00550 Not available 620 watts 2116 BTUs
per hour
Breeze-Hill TMT7-9100 5X00367 Not available Not available Not available
Optical Device
RAID SATA to iSCSI Media 5X00523 Not available Not available Not available
OW350_R1007 29
I/O cabinets (main/aux power and main/aux heat dissipation) (drawn from AC/DC Mains
power)
All Ovation I/O cabinet styles have the following voltage and frequency specifications:
 Input voltages:
 85 - 264 VAC (Line-Neutral configuration only) (CE Mark Certified).
 90 -250 VDC .
 Input frequency: 47 - 63 Hz.
The following table lists the power a component draws from the cabinet’s AC or DC Mains power
supply when the component is installed within the cabinet. Refer to Calculating Ovation main
power requirements (see page 49) in Planning your Ovation System for instructions on using
these values to calculate power requirements for populated Ovation I/O cabinets.
Refer to the applicable I/O module table for module power requirements.
Do NOT use the following table to determine the power drawn from the +24V Power Supply.
Refer to Calculating Ovation power supply requirements in Planning your Ovation System.
CAUTION! Limit access to the inside of an Ovation cabinet to qualified, trained personnel only.
Electrical Specifications for Ovation I/O Cabinet Components

(power supply efficiency is included)
COMPONENT EMERSO MAIN +24 AUX POWER MAIN AUX

N PART POWER (W) AND HEAT HEAT
NUMBER (W) AND 2 DISSIPATION DISSIPATION
VA
VA (TYPICAL)
(TYPICAL)
Controller Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A

(cabinet + power supply
fans)
OCR1100 or
OCR400 Controller
Marshalling Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A
fans)
Extended I/O Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A
fans)
Remote I/O Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A
(ventilated) (cabinet +
power supply fans)
Remote I/O Cabinet N/A 32 W/VA N/A 109.2 N/A
(sealed) (cabinet + power
BTUs/hr
supply fans)
EMC Controller Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A
fans)
30 OW350_R1007
COMPONENT EMERSO MAIN +24 AUX POWER MAIN AUX

N PART POWER (W) AND HEAT HEAT
NUMBER (W) AND 2 DISSIPATION DISSIPATION
VA
VA (TYPICAL)
(TYPICAL)
EMC Extended I/O N/A 24 W/VA N/A 82 BTUs/hr N/A

Cabinet (cabinet + power
supply fans)
EMC Remote I/O Cabinet N/A 24 W/VA N/A 82 BTUs/hr N/A
(ventilated) (cabinet +
power supply fans)
EMC Remote I/O Cabinet N/A 32 W/VA N/A 109.2 N/A
(sealed) (cabinet + power BTUs/hr
supply fans)
Single OCR 400 5X00127 25 W/VA N/A 85.4 BTUs/hr N/A
Controller:
1 Processor card
1 IOIC card
1 Fan
Dual OCR 400 Controller: 5X00127 50 W/VA N/A 170.8 N/A
BTUs/hr
2 Processor cards
2 IOIC cards
2 Fans
Single OCR 1100 5X00481 25 W/VA N/A 85.4 BTUs/hr N/A
Controller:
1 Processor card
1 IOIC card
1 Fan
Dual OCR 1100 5X00481 50 W/VA N/A 170.8 N/A
Controller: BTUs/hr
2 Processor cards
2 IOIC cards
2 Fans
Redundant Remote Node 1C31203 16 W/VA N/A 54.6 BTUs/hr N/A
Controller module (in (E)
Remote Node Cabinet)
1C31204
G01, G03
(P)
Redundant MAU module 1C31179 17.6 W/VA N/A 60 BTUs/hr N/A
(Controller cabinet) (E)
1C31181
G01-G04
(P)
OW350_R1007 31
Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Mains power)
The following table lists the power a module draws from the cabinet’s AC or DC Mains power
supply when the component is installed within the cabinet. Refer to Calculating Ovation Main
Power Requirements (see page 49) for instructions on using these values to calculate power
requirements for populated Ovation I/O cabinets.
Note that (E) designates an Electronics module and (P) designates a Personality module.
Refer to Calculating Ovation Power Supply Requirements (drawn from +24V Main or Auxiliary
Power Supply) in Planning you Ovation System.
1
Electrical Information for Ovation Analog I/O Modules
(A 75% power supply efficiency is included)
COMPONENT EMERSON MAIN +24 AUX POWER MAIN HEAT AUX HEAT
PART NUMBE R POWER (W) AND DISSIPATION DISSIPATION
(W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
Analog Input (13- 1C31113 3.4 W/VA N/A 11.6 BTUs/hr N/A for voltage
bit) G01-G06 (E) input channels.
T/C, Volts and 1C31116G01, 4
0.41 BTUs/hr
Field Powered mA G02, G04 (P) per field
powered mA
channel.
Analog Input (13- 1C31113G05 (E) 3.4 W/VA 3 11.6 BTUs/hr 3
0.64 W/VA 0.96 BTUs/hr
bit) per locally per locally
1C31116G03 (P)
Local Powered powered powered mA
mA channel channel
Analog Input (14- 1C31224G02 (E) 3.2 W/VA Not 10.9 BTUs/hr N/A
bit) Applicable
1C31227G02 (P)
Volts (+/- 1 Volt)
Analog Input (14- 1C31224G01 (E) 3.2 W/VA 3 10.9 BTUs/hr 3,
bit) per locally 4
1C31227G01 (P)
Field and Local powered per field
Powered mA channel. Not powered
applicable for channel
field-powered
channels. 3
0.96 BTUs/hr
per locally
powered
channel
Analog Input (14- 5X00070G02 (E) 3.2 W/VA Not 10.9 BTUs/hr N/A
bit) (High Speed) Applicable
32 OW350_R1007
(W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
(± 100mV, ± 1C31227G02 (P)

250mV, ± 1V Volt)
Analog Input (14- 5X00070G03 (E) 3.2 W/VA Not 10.9 BTUs/hr N/A
bit) (High Speed) Applicable
1C31227G02 (P)
(± 5V, ± 10V Volt)
Analog Input (14- 5X00070G01 (E) 3.2 W/VA 3 10.9 BTUs/hr 3,
bit) (High Speed) per locally 4
1C31227G01 (P)
Field and Local powered per field
Powered mA channel. Not powered
applicable for channel
field-powered
channels. 3
0.96 BTUs/hr
per locally
powered
channel
Analog Input (14- 5X00070G04 (E) 3.2 W/VA Not 10.9 BTUs/hr Not Applicable
bit) (Medium Applicable
Speed) 1C31116G04 (P)
(± 20mV, ± 50mV,
± 100V)
(Thermocouple)
Speed) 1C31116G04 (P)
(± 20mV, ± 50mV,
± 100V)
(Thermocouple)
Speed) 1C31116G01 (P)
(± 20mV, ± 50mV,
± 100V)
Analog Input (14- 5X00070G02 (E) 3.2 W/VA 0.032 W/VA 10.9 BTUs/hr 0.028
bit) (High Speed) per channel 3
1C31116G03 (P) BTUs/hr
(± 1mA 2 wire per channel
local powered)
Analog Input (14- 5X00070G02 (E) 3.2 W/VA Not 10.9 BTUs/hr 0.001
bit) (High Speed) Applicable 4
(± 1mA 4 wire field per channel
powered)
HART Analog 5X00058G01 (E) 1.6 W/VA 2.4 W/VA 5.5 BTUs/hr 8.2 BTUs/hr
Input plus 0.64 plus 0.41
5X00059G01 (P) 3 3, 4
W/VA per BTUs/hr
locally per field
powered powered
OW350_R1007 33
(W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
channel. channel
and
3
1.27 BTUs/hr
per locally
powered
channel
HART High 5X00106G01 (E) 5.5 W/VA 0.64 W/VA 18.77 BTUs/hr 3,
0.41 BTUs/hr
Performance per locally 4
Analog Input 5X00109G01 (P) powered
channel. Not per field
applicable for powered
field powered channel
channels. 3
0.96 BTUs/hr
per locally
powered
channel
HART High 5X00106G02 (E) 5.5 W/VA 0.64 W/VA 18.77 BTUs/hr 3,
0.41 BTUs/hr
Performance per locally 4
Analog Input 5X00109G01 (P) powered
channel. Not per field
applicable for powered
field powered channel
channels. 3
0.96 BTUs/hr
per locally
powered
channel
Analog Output 1C31129G01, 2.7 W/VA Not 9.2 BTUs/hr Not Applicable
G02 (E) Applicable
(Voltage)
1C31129G05 (E)
(0 to 20MA
Redundant)
1C31132G01 (P)
Analog Output 1C31129G03, 5.4 W/VA Not 18.4 BTUs/hr Not Applicable
G04 (E) Applicable
(Current)
1C31132G01 (P)
HART Analog 5X00062G01 (E) 1.6 W/VA 8 W/VA 5.5 BTUs/hr 27.2 BTUs/hr
Output
5X00063G01 (P)
HART High 5X00167G01 (E) 6.08 W/VA Not 20.74 BTUs/hr Not Applicable
Performance Applicable
Analog Output 1X00188H01
(cavity insert)
RTD Input 1C31161G01 (E) 4.8 W/VA Not 16.4 BTUs/hr Not Applicable
Applicable
(4 channels) 1C31164G01 (P)
RTD Input 1C31161G02 (E) 4.8 W/VA Not 16.4 BTUs/hr Not Applicable
Applicable
(50Hz/60Hz 1C31164G02 (P)
34 OW350_R1007
(W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
filtered inputs)
(4 channels)
RTD Input 5X00119G01 (E) 4.8 W/VA Not 16.4 BTUs/hr Not Applicable
Applicable
(8 channels) 5X00121G01 (P)
RTD Input 5X00119G02 (E) 4.8 W/VA Not 16.4 BTUs/hr Not Applicable
Applicable
(8 channels) 5X00121G01 (P)
1
Refer to Q-Line Installation Manual for power consumption for Q-Line modules.
2
Due to power factor correction in Ovation power supplies, Power and VA are the same.
3
24V Aux power supply. Heat dissipated by the AI input transmitters is outside the cabinet and is not
included.
4
For Field Powered Channels. The heat dissipation is not due to the 24V Aux power supply, but to the
externally sourced input current. Heat dissipated by the field powered AI input transmitters is outside the
cabinet and is not included.
OW350_R1007 35
Bus interface modules
Note: For detailed information about bus interface modules, refer to the Ovation I/O Reference
Manual.
Power Supply in Planning you Ovation System.
Electrical Specifications for Ovation Bus Interface modules

PART POWER (W) 2 DISSIPATION DISSIPATION
(W) AND VA
NUMBER AND VA
(TYPICAL)
(TYPICAL)
Foundation 5X00301G01 2.4 W/VA 0.55 W/VA per 8.16 BTUs/hr Fieldbus heat
Fieldbus (E) channel dissipation
5X00327G01 1.88 BTUs/hr per
(P) channel
Foundation 1X00418H01 N/A 2.4 W/VA per N/A 8.16 BTUs/hr per
Fieldbus segment segment
Power
Conditioner
Profibus 5X00300G01, 5.1 W/VA N/A 17.3 BTUs/hr N/A
G01 (E)
5X00321G01
(P)
DeviceNet 5X00376G01 3.84 W/VA 0.77 W/VA per 13.1 BTUs/hr 2.63 BTUs/hr per
(E) channel channel
5X00375G01
(P)
Ethernet Link 5X00419 (E) 2.2 W/VA N/A 7.51 BTUs/hr N/A
Controller
1X00569
(Cavity insert)
36 OW350_R1007
Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Mains power)
Note that (E) designates an Electronics module, (P) designates a Personality module, and (R)
designates a Relay panel.
1
Electrical Information for Ovation Digital I/O Modules
COMPONENT EMERSON PART MAIN +24 AUX MAIN HEAT AUX HEAT
NUMBER POWER POWER DISSIPATION DISSIPATION
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
Contact Input 1C31142G01 (E) 6.1 W/VA Not 20.8 BTUs/hr Not Applicable
1C31110G03 (P) Applicable
Compact Contact 1C31234G01 (E) 6.1 W/VA Not 20.8 BTUs/hr Not Applicable
Input 1C31238H01 Applicable
(Cavity Insert)
Digital Input 1C31107G01 (E) 1.5 W/VA 1.0 W/VA 5.1 BTUs/hr 3.4 BTUs/hr
(24V) (24V)
24VDC/48VDC
6.8 BTUs/hr
1C31110G01, G02 (48V)
(P) 2.0 W/VA
(48V)
Digital Input 1C31107G02 (E) 1.5 W/VA Not 5.1 BTUs/hr 11.26
125VDC 1C31110G01, G02 4 5
Applicable BTUs/hr
(P)
Compact Digital 1C31232G01 (E) 1.5 W/VA 0.87 W.VA 5.1 BTUs/hr 2.98BTUs/hr
Input (24V) (24V)
24/48VDC single- 1C31238H01 2.33 W/VA 7.95 BTUs/hr
ended inputs with (cavity insert) (48V) (48V)
common return
Compact Digital 1C31232G02 (E) 1.5 W/VA 0.92 W/VA 5.1 BTUs/hr 3.14 BTUs/hr
Input (24V) (24V)
24/48VAC/VDC 1C31238H01 2.33 W/VA 7.95 BTUs/hr
isolated (cavity insert) (48V) (48V)
differential inputs
OW350_R1007 37
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
Compact Digital 1C31232G02 (E) 1.5 W/VA 0.92 W/VA 5.1 BTUs/hr 3.14 BTUs/hr
Input (24V) (24V)
24/48VAC/VDC 5X00034G01 (P) 2.33 W/VA 7.95 BTUs/hr
individually fused (48V) (48V)
inputs with
common power
supply
Compact Digital 1C31232G03 (E) 1.5 W/VA Not 5.1 BTUs/hr 5
17.4 BTUs/hr
Input 4
Applicable
125VAC/VDC 1C31238H01
isolated (cavity insert)
differential inputs
Compact Digital 1C31232G03 (E) 1.5 W/VA Not 5.1 BTUs/hr 5
17.4 BTUs/hr
Input 4
Applicable
125VAC/VDC 5X00034G01 (P)
individually fused
inputs with
common power
supply
Digital Output 1C31122G01 (E) 3.0 W/VA 3 10.3 BTUs/hr 22.38
25.6 W/VA
3
(no relay panel) 1C31125G01 (P) (24V Aux) BTUs/hr
3 (24V Aux)
51.2 W/VA
(48V Aux) 44.56
3
BTUs/hr
(48V Aux)
Digital Output plus 1C31122G01 (E) 3.0 W/VA 7.87 W/VA 10.3 BTUs/hr 8
26.8 BTUs/hr
(16 outputs
Solid State Relay 1C31125G02 (P) on) (24V Aux)
Panel (16 relays)
5A22410G01 (R) 9
AC contacts 6.9 BTUs/hr
or (24V Aux)
5A22410G02 (R)
DC contacts
Digital Output plus 1C31122G01 (E) 3.0 W/VA Not 10.3 BTUs/hr 8
20.3 BTUs/hr
applicable
Solid State Relay 1C31125G03 (P) (16 outputs (24V Aux)
Panel (16 relays) on)
5A22410G01 (R) 9
AC contacts 0.18 BTUs/hr
or (24V Aux)
5A22410G02 (R)
DC contacts
Digital Output plus 1C31122G01 (E) 3.0 W/VA 14.5 W/VA 10.3 BTUs/hr 49.47
(16 outputs 8
G2R Style Panel 1C31125G02 (P) BTUs/hr
on)
(16 relays)
38 OW350_R1007
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
5A22411G01 (R) (24V Aux)

12.72
9
BTUs/hr
(24V Aux)
Digital Output plus 1C31122G01 (E) 3.0 W/VA Not 10.3 BTUs/hr 37.43
applicable 8
G2R Style Panel 1C31125G03 (P) BTUs/hr
(16 outputs
(16 relays) on) (24V Aux)
5A22411G01 (R)
9
0.34 BTUs/hr
(24V Aux)
(8 outputs 8
KUEP Style Panel 1C31125G02 (P) BTUs/hr
on)
(8 Form C relays) (24V Aux)
5A22412G01 (R)
18.53
9
BTUs/hr
(24V Aux)
applicable (8 8
outputs on)
(8 Form C relays) (24V Aux)
5A22412G01 (R)
9
0.51 BTUs/hr
(24V Aux)
two (16 outputs 8
on)
KUEP Style (24V Aux)
Panels (2 x 8 5A22412G01 (R)
Form C relays) 37.16
9
BTUs/hr
(24V Aux)
two applicable 8
(16 outputs
KUEP Style on) (24V Aux)
Panels (2 x 8 5A22412G01 (R)
Form C relays) 9
1.12 BTUs/hr
(24V Aux)
(8 outputs 8
on)
(8 Form X relays) (24V Aux)
5A22412G02 (R)
13.18
9
BTUs/hr
OW350_R1007 39
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
(24V Aux)
applicable (8 8
outputs on)
(8 Form X relays) (24V Aux)
5A22412G02 (R)
9
0.35 BTUs/hr
(24V Aux)
two (16 outputs 8
on)
KUEP Style (24V Aux)
Panels (2 x 8 5A22412G02 (R)
Form X relays) 9
26.4 BTUs/hr
(24V Aux)
two applicable 8
(16 outputs
KUEP Style on) (24V Aux)
Panels (2 x 8 5A22412G02 (R)
Form X relays) 9
0.75 BTUs/hr
(24V Aux)
5X00270G01 (E) 2.88 W/VA 7 9.83 BTUs/hr 13.65 BTUs/hr
64W/VA
7
High Side Digital 5X00273G01 (P)
6
Output
1C31219G01 (E) 2.54 W/VA 0.39 W/VA 8.66 BTUs/hr 1.33 BTUs/hr
(E) (E) (E)
Relay Output 1C31223G01
module (E) plus (Base) Base not + 12.3 W/VA + 42 BTUs/hr
base with applicable
(base + 16 (base + 16
16 G2R relays relays) relays)
---------------- ----------------
= 12.69 = 43.33 W/VA
W/VA
Relay Output 1C31219G01 (E) 2.54 W/VA 0.39 W/VA 8.66 BTUs/hr 1.33 BTUs/hr
module (E) plus (E) (E) (E)
base with 12 1C31222G01
KUEP Form C (Base) Base not + 31.66 + 108 BTUs/hr
Relays added applicable W/VA
(base + 12
(base + 12 relays)
relays)
----------------
----------------
= 109.33
= 32.05 W/VA
W/VA
Relay Output 1C31219G01 (E) 2.54 W/VA 0.39 W/VA 8.66 BTUs/hr 1.33 BTUs/hr
module (E) plus (E) (E) (E)
40 OW350_R1007
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
base with 12 1C31222G01 Base not + 21.46 + 73.22
KUEP Form X (Base) applicable W/VA BTUs/hr
Relays added
(base + 12 (base + 12
relays) relays)
---------------- ----------------
= 21.85 = 74.55 W/VA
W/VA
Relay Output with 1C31219G01 (E) 2.54 W/VA 0.39 W/VA 8.66 BTUs/hr 1.33 BTUs/hr
Contact (E) (E) (E)
Monitoring 5X00564G01, G02
(Base) Base not + 14.3 W/VA + 48.75
applicable BTUs/hr
(base + 8
relays) (base + 8
relays) + 61.1
---------------- 10
BTUs/hr
= 14.69
W/VA ----------------
= 111.18
W/VA
Sequence of 1C31157G01 (E) 2.0 W/VA 1.5 W/VA (E) 6.8 BTUs/hr 5.1 BTUs/hr
Events
(24V) (24V)
24VDC/48VDC 1C31110G01, G02
(P) 3.0 W/VA 10.2 BTUs/hr
Digital Input
(48V) (48V)
Sequence of 1C31157G02 (E) 2.0 W/VA Not 6.8 BTUs/hr 5
11.26
Events 4
1C31110G01, G02 Applicable BTUs/hr
125VDC Digital (P)
Input
Sequence of 1C31157G03 (E) 6.1 W/VA Not 20.8 BTUs/hr Not Applicable
Events 1C31110G03 (P) Applicable
48V Contact Input
On-card
Compact Seq. of 1C31233G01 (E) 2.0 W/VA 0.88 W/VA 6.8 BTUs/hr 3.0 BTUs/hr
Events (24V) (24V)
24/48VDC single- 1C31238H01 2.27 W/VA 7.74 BTUs/hr
ended digital (cavity insert) (48V) (48V)
inputs with
common return
Events (24V) (24V)
1C31238H01
24/48VDC (cavity insert) 2.27 W/VA 7.74 BTUs/hr
isolated (48V) (48V)
differential digital
inputs
Events (24V) (24V)
OW350_R1007 41
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
24/48 VDC 5X00034G01 (P) 2.27 W/VA 7.74 BTUs/hr

individually fused (48V) (48V)
digital inputs with
common power
supply
Compact Seq. of 1C31233G03 (E) 2.0 W/VA Not 6.8 BTUs/hr 5
14.5 BTUs/hr
Events 4
1C31238H01 Applicable
125VDC isolated (cavity insert)
inputs
Compact Seq. of 1C31233G03 (E) 2.0 W/VA Not 6.8 BTUs/hr 5
14.5 BTUs/hr
Events 4
5X00034G01 (P) Applicable
125VDC
individually fused
digital inputs with
common power
supply
Compact Seq. of 1C31233G04 (E) 6.1 W/VA Not 20.8 BTUs/hr Not Applicable
Events Applicable
1C31238H01
Contact Input (cavity insert)
Enhanced 5X00357G01 (E) 2.47 W/VA 0.93 W/VA 8.43 BTUs/hr 3.17 BTUs/hr
Compact Seq. of (24V) (24V)
Events 1C31238H01
(cavity insert) 1.86 W/VA 6.35 BTUs/hr
24/48 VDC single- (48V) (48V)
ended digital
inputs with
common return
Events 1C31238H01
(cavity insert) 1.73 W/VA 5.94 BTUs/hr
24/48VDC (48V) (48V)
isolated
inputs
Events 5X00034G01 (P)
24/48 VDC single (48V) (48V)
ended individually
fused digital
inputs with
common power
supply
Enhanced 5X00357G03 (E) 1.99 W/VA Not 6.78 BTUs/hr 5
6.4 BTUs/hr
Compact Seq. of 4
1C31238H01 Applicable
Events
(cavity insert)
125 VDC isolated
42 OW350_R1007
(W) AND (W) AND
VA 2
VA
(TYPICAL) (TYPICAL)
inputs
Enhanced 5X00357G03 (E) 1.99 W/VA Not 6.78 BTUs/hr 5
6.4 BTUs/hr
Compact Seq. of 4
5X00034G01 (P) Applicable
Events
125 VDC single
ended individually
fused digital
inputs with
common power
supply
Enhanced 5X00357G04 (E) 5.51 W/VA Not 18.79 Not Applicable
Compact Seq. of Applicable BTUs/hr
Events 1C31238H01
(cavity insert)
48 VDC contact
input
Compact Seq. of
Events 1C31238H01
(cavity insert)
24 VDC isolated
inputs
Compact Seq. of
Events 5X00034G01 (P)
24 VDC single
ended individually
fused digital
inputs with
common power
supply
1
2
3
Loads are located outside the cabinet. Their heat dissipation is not included. Eight outputs on @ 100
mA per output.
4
Assumes that the 125VAC or 125VDC power source is located outside the Ovation I/O cabinet.
5
Heat dissipation is due solely to the I/O module front-end circuit external power consumption.
6
Module standard configuration employs an external +24 VDC power supply for field power and does not
use auxiliary power. You may optionally use auxiliary power to provide module field power, but then the
module allowable maximum total load current is reduced to 2 A.
7
Assume eight outputs on and eight outputs off with the on outputs supplying 250 mA each.
8
Relay panels located inside Ovation I/O cabinet.
9
Relay panel located outside Ovation I/O cabinet and its heat dissipation is not included.
10
Heat dissipation from 16 monitor circuits is supplied by an external source not by the auxiliary power
supply.
OW350_R1007 43
Specialty I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Mains power)
1
Electrical Information for Ovation Specialty I/O Modules
PART POWER (W) AND DISSIPATION DISSIPATION
NUMBER (W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
Link Controller For RS232: 3.9 W/VA Not 13.3 BTUs/hr Not Applicable
Applicable
1C31166G01
(E)
1C31169G01
(P)
For RS485/422:
1C31166G01
(E)
1C31169G02
(P)
Loop Interface 1C31174GX1, 3.6 W/VA When used: 12.3 BTUs/hr When used:
GX2 (E)
13-bit Voltage AI
1C31177G01
(E) GX1 = 0 to Digital Inputs Digital Inputs
(P)
10V
(X = 0 or 2) 0.18W/VA 0.6 BTUs/hr
(E) GX2 = 0 to 5 (24V) (24V)
V
0.36W/VA 1.2 BTUs/hr
(48V) (48V)
12-bit Voltage Digital 4
Digital Output
AO Outputs
(100mA per
0 to 10V (100mA per output)
output)
(X = 0 or 2) 5.6 BTUs/hr
6.4 W/VA (24V)
(24V)
44 OW350_R1007
NUMBER (W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
12.8W/VA 11BTUs/hr (48V)

(48V) Not
applicable for Not applicable
voltage for voltage
analog inputs analog inputs
Loop Interface 1C31174GX3, 3.6 W/VA When used: 12.3 BTUs/h When used:
GX4 (E)
13-bit 4-20mA
Current AI 1C31177G02,
Digital Inputs Digital Inputs
G03 (P)
(P) G02 = local
power (X = 0 or 2) 0.18W/VA 0.6 BTUs/hr
(24V) (24V)
(P) G03 = field
power 0.36W/VA 1.2 BTUs/hr
(48V) (48V)
Digital 4
Digital Output
12-bit 4-20mA Outputs
Current AO (100mA per
(100mA per output)
(E) GX3 output)
5.6 BTUs/hr
No AO 6.4 W/VA (24V)
(24V)
(E) GX4 11 BTUs/hr
12.8 W/VA (48V)
(X = 0 or 2) (48V)
Local Powered
Local Current Analog
Powered 3
Current Inputs
Analog (2 inputs @
Inputs Only 20mA per input)
(20mA per 1.91BTUs/hr
input) (24V)
1.28W/VA Field Powered
(24V) Current Analog
7
Inputs
(2 inputs @
20mA per input)
0.82 BTUs/hr
(24V)
Pulse 1C31147G01 2.2 W/VA When used: 7.51 BTUs/hr When used:
Accumulator (E)
Both count Both count inputs
24/48 VDC 1C31150G01- inputs = 50% = 50% duty cycle
Count Inputs G02 (P) duty cycle
0.78 BTUs/hr
0.23 W/VA (24V)
(24V)
1.6 BTUs/hr
0.47 W/VA (48V)
(48V)
Not applicable
for 12V/5V
OW350_R1007 45
NUMBER (W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
count inputs
Pulse 1C31147G01 2.2 W/VA Not 7.51 BTUs/hr When used: Both
Accumulator (E) Applicable count inputs =
50% duty cycle
24/48 VDC 1C31150G03
Count Inputs (P) 0.58 BTUs/hr
8
(24V)
1.19 BTUs/hr
8
(48V)
Pulse 1C31147G02 2.2 W/VA Not 7.51 BTUs/hr 8

0.68 BTUs/hr
Accumulator (E) Applicable
Both high speed
High Speed 1C31150G01- count inputs =
G03 (P) 50% duty cycle
+5V Count
Inputs
Servo Driver 1C31199G01, 9.0 W/VA Not 30.7 BTUs/hr Not Applicable
G04 (E) Applicable
DC LVDT
1C31201G01
(P)
Servo Driver 1C31199G02, 7.1 W/VA Not 24.2 BTUs/hr Not Applicable
G03, G05, and Applicable
AC LVT G06 (E)
1C31201G02
(P)
5 4D33741G01- 4.8 W/VA Not 16.4 BTUs/hr Not Applicable
SLIM
G03 Applicable
Speed Detector 1C31189G01, 6.4 W/VA Not 21.8 BTUs/hr Not Applicable
G03 (E) Applicable
1C31192G01
(P)
Valve Positioner 1C31194G01, 5.8 W/VA Digital Input 19.8 BTUs/hr Digital Input
G02 (E)
1C31197G01- (24VDC) (24V)
G04 (P)
(48VDC) (48V)
Digital 6
Digital Output
Output
2.79 BTUs/hr
(100mA load) (24V)
(24VDC) (48V)
6.4W/VA
46 OW350_R1007
NUMBER (W) AND 2
VA
VA (TYPICAL)
(TYPICAL)
(48VDC)
Enhanced Valve 1C31194G03, 7.68 W/VA Digital Input 26.21 BTUs/hr Digital Input
Positioner G04 (E)
1C31197G01- (24VDC) (24V)
G05(P)
(48VDC) (48V)
Digital 6
Digital Output
Output
2.79 BTUs/hr
(100mA load) (24V)
(24VDC) (48V)
6.4W/VA
(48VDC)
1
2
3
24V Aux power supply. Heat dissipated by the AI input transmitters is outside the cabinet and is not
included.
4
Loads are located outside the cabinet. Their head dissipation is not included. Two outputs on @100 mA
per output.
5
SLIM is not located in the Ovation I/O cabinet and is not powered by an Ovation power supply. It is listed
here as a convenience for determining system power requirements.
6
The load is located outside the cabinet and its heat dissipation is not included.
7
For Field Powered Channels. The heat dissipation is not due to the 24V Aux power supply, but to the
externally sourced input current. Heat dissipated by the field powered AI input transmitters is outside the
cabinet and is not included.
8
Heat dissipation is due solely to the I/O module front-end circuit external power consumption.
OW350_R1007 47
Remote function modules (main/aux power and main/aux heat dissipation) (drawn from
AC/DC Mains power)
1
Electrical Specifications for Ovation Remote Function Modules
COMPONENT EMERSON MAIN +24 AUX MAIN HEAT AUX HEAT

PART NUMBE R POWER (W) POWER DISSIPATION DISSIPATION
AND VA (W) AND
(TYPICAL) 2
VA
(TYPICAL)
Redundant 1C31203 (E) 16 W/VA Not 54.6 BTUs/hr Not Applicable

Remote Node Applicable
Controller module 1C31204G01,
(in Remote Node G03 (P)
Cabinet)
Redundant MAU 1C31179 (E) 17.6 W/VA Not 60 BTUs/hr Not Applicable
module Applicable
(in Controller 1C31181G01-
cabinet) G04 (P)
48 OW350_R1007
Calculating Ovation main power requirements for OCR400 or OCR1100 Controller
You can calculate the Power (VA) requirements for a specific Ovation cabinet by adding the
Power (VA) values for the cabinet components (such as Controller (see page 30) and modules),
plus the Power (VA) values for the Auxiliary (AUX) supplies.
In this example, the Ovation I/O cabinet configuration consists of the following:
 Controller Cabinet (Main: 24 W).
 Dual Controller (Main: 50 W).
 16 Analog Input T/C modules (Main: 3.4 W per module).
 16 Analog Input modules - System Powered 4-20 mA (Main:3.4 W per module;
AUX: 5.2 W per module).
Refer to the following table for the figures used in the calculation:
1. Add the Main (182.8 W/VA) and AUX (83.2 W/VA) Power totals = 266 W/VA total power
needed from the AC or DC Mains.
2. Add the Main (624.6 BTU) and AUX (113.6 BTU) Heat Dissipation = 636.2 BTUs/hr heat
dissipation inside the cabinet.
1
Power Calculation Example
I/O CABINET MAIN AUX MAIN HEAT AUX HEAT COLD START
COMPONENT 2 POWER DISSIPATION DISSIPATION INRUSH
POWER
3
CURRENT
Cabinet 24 W/VA N/A 82 BTUs/hr N/A N/A
Dual Controller 50 W/VA N/A 170.8 BTUs/hr N/A 65 amps (230

VAC)
33 amps (115
VAC)
25 amps (125
VDC)
16 AI modules 54.4 W/VA N/A 185.6 BTUs/hr N/A N/A
- T/C
16 AI modules 54.4 W/VA 83.2 W/VA 185.6 BTUs/hr 113.6 BTUs/hr N/A
- 4-20 mA
Total 182.8 W/VA 83.2 W/VA 624.6 113.6 BTUs/hr N/A

BTUs/hr
1
The values used in this table are taken from Electrical Information for Ovation Equipment (see page 26)
(drawn from AC or DC Mains power).
2
The VA rating is the same as the Watts due to the Ovation power supply power correction.
3
These values assume a 60 second minimum delay after powering down the Controller before power-up.
OW350_R1007 49
3.3.4 Monitoring power supply status
Each Ovation Controller IOIC card and each Remote Node has the capability to monitor up to two
sets of redundant Ovation power supply modules (one set contains four redundant power
supplies).
A healthy status indicates the presence of output voltage on the power supplies. An unhealthy
status indicates the lack of one or both output voltages on the power supplies and that the power
supply should be replaced. Power supply LEDs indicate which input/output voltage is bad. A
green LED indicates a healthy voltage status, and a red LED indicates an unhealthy voltage
status.
The status is reflected in Node (RN) Point Records which are assigned to IOIC and Remote Node
addresses through the I/O Builder. When a power supply fails, this status is displayed at the
Operator Station in the Point Information window and in the Base Alarm window.
Monitoring one set of redundant power supplies
No additional cabling is required to monitor one set of redundant power supplies. The first
redundant power supply set being monitored is contained in the Ovation Controller or in the
Remote Node Controller cabinet.
50 OW350_R1007
Monitoring two sets of redundant power supplies
Monitoring a second set of redundant power supplies for a Controller or a Remote Node
Controller requires an additional power supply status cable connection.
To have the Controller monitor a second set of local power supplies, install cable 5A26467
between connector P9, P10, or P11 on the Power Distribution Module (PDM) and the
Supplementary Status Connector J26 on the Controller Backplane Panel (CBK).
To have the Remote Node Controller monitor a second set of remote power supplies, install
cable 5A26467 between connector P9, P10, or P11 on the Power Distribution Module (PDM) and
the Supplementary Status Connector P6 on the Remote Transition Panel (TND).
Note: Cable 5A26467 is available in lengths from 102 cm (40 in) to 914 cm (360 in).
Figure 13: Monitoring local power supplies
OW350_R1007 51
Figure 14: Monitoring remote node power supplies
3.3.5 Fieldbus segment monitoring
A Fluke 123 oscilloscope, or equivalent, may be used for monitoring signals on a Fieldbus
segment. However, electrical noise caused by oscilloscope connections (not by noise on the
segment) may show on the trace. To minimize noise caused by the connections, use the ground-
clip lead included on the probe. Do not use the common ground lead connection, which can be
susceptible to electromagnetic noise in the plant and, thus, introduce electrical noise on the trace.
Note: A Fluke 123 oscilloscope is a good scope to use for general checkout. If segment faults
are indicated, a Fluke 199 Scopemeter is preferred for troubleshooting.
52 OW350_R1007
3.3.6 To perform a Foundation Fieldbus wiring check
A wiring check involves checking resistance and capacitance for the following:
 Conductor to conductor
 Conductor to shield
 Conductor to ground
 Shield to ground
Before you begin, make sure all the parts of the segment are connected. That includes all wiring,
terminators, and field devices. DO NOT connect the segment power connector during the
wiring check.
1. With a multimeter, check the following resistance levels:

 + Signal to -signal >50 K ohms
 + Signal to shield >20 M ohms
 - Signal to shield >20 M ohms
 + Signal to instrument ground >20 M ohms
 - Signal to instrument ground >20 M ohms
 Shield to instrument ground >20 M ohms
2. You should also lift the shield from the ground and check the isolation between the shield and
the ground. The value should be greater than 20 M ohms.
3. Check the capacitance wherever you have long wire runs or where Fieldbus is installed on old
wiring. Capacitance values should be:
 + Signal to - signal ~ 1 F
 + Signal to shield < 300 nF
 - Signal to shield < 300 nF
 + Signal to instrument ground < 300 nF
 - Signal to instrument ground < 300 nF
 Shield to instrument ground < 300 nF
If everything checks out to be within these limits, the basic wiring for your segment is good.
OW350_R1007 53
3.3.7 To perform a Foundation Fieldbus voltage check

1. After ensuring that the segment wiring checks out, examine the segment power.
Note: Remember that the power connector was disconnected for the wiring check. Re-attach it
for the voltage check.
2. Check voltage at the power supply, the H1 interface card, and the individual field devices. The
voltage level between all the positive (+) and negative (-) signal wires must be between 9 and
32 VDC.
Note: Emerson recommends that the lowest voltage on the segment be at least 1 - 2 VDC
higher than the minimum 9 VDC. This gives some buffer for low voltage conditions.
Generally, as the distance increases between devices on the segment and the power supply,
the voltage on the bus drops. Any device whose voltage varies significantly from other
devices and any significant voltage drop that is not associated specifically with the distance to
the power supply indicates a possible wiring problem.
If you anticipate a segment extending long distances beyond the current end point, you
should either plan for a higher level of power at the current end point or make provisions for a
powered repeater.
3.3.8 Perform a Foundation Fieldbus signal check
Foundation Fieldbus is very robust. Many segments can operate despite the presence of
waveform error conditions, but the overall reliability of the segment is reduced. These errors
commonly appear as an excess number of message retries.
Many of these errors can be diagnosed by using a scopemeter to check the communication
waveforms. Some third-party manufacturers also make specialized diagnostic equipment for
Foundation Fieldbus.
Some common errors are:

 Missing terminator (see page 54).
 Too many terminators (see page 55).
 Excessive spur or segment length (see page 55).
Missing terminator
If the waveform shows peak-to-peak signal strength that is twice as large as the normal 0.8 to 1.2
volt, you may be missing a terminator on the segment. There are two common reasons for
missing terminators:
1. Many Fieldbus components such as power conditioners have built-in terminators that can be
switched in or out. Often a terminator that is intended to be switched in, is in fact, switched
out. This frequently happens after a repair or maintenance activity where the component with
the terminator is replaced.
2. A segment is extended beyond its original end point. The terminator at the old end point is
removed, but the terminator is not installed at the new end point.
Note: Less common reasons for missing terminators include failing to terminate after an
isolating safety barrier or failing to secure the terminator sufficiently and having it fall out.
54 OW350_R1007
Too many terminators
If the waveform peaks are shorter than normal, there may be extra terminators somewhere on the
segment. This problem can occur if a technician does not realize that a Fieldbus component, such
as a power conditioner, has a terminator in it and then adds another terminator. It also happens
when someone extends a segment, adds a terminator at the new segment end, and forgets to
remove the terminator at the old end location.
Excessive spur or segment length
A waveform with rounded peaks, rather than flat, horizontal areas at the top and bottom, may
indicate that a spur or segment is too long. The most common causes of excessive length are:
1. Using conduit and cable tray routes that are much longer than line of sight.
2. Mixing wire types without considering the different maximum length specifications for different
wire types.
3. Using wire that is very old and in poor condition.
OW350_R1007 55
3.3.9 Using signal waveforms
Signals have easily recognizable signatures, or waveforms, that you can use to quickly identify
the signal and any problems associated with it.
1. A normal signal has wave shapes that are well formed and defined by the following:
 Linear up-slope
 Well-defined wave top
 Linear down-slope
 Well-defined wave bottom
2. The up and down slopes are symmetrical, and the top and bottom are relatively flat and free
from spikes.
3. A good waveform also has a nominal pear-to-peak voltage of 0.8 to 1.2 volts.
In the following example:

 Waveform A shows how a good waveform appears close to the transmitter.
 Waveform B shows how the same waveform changes over distance on the wire. Despite the
“rounded” tops, it is still a good signal.
Figure 15: Waveform examples
At first glance, some good waveforms may be perceived as bad. For this reason, Emerson
recommends that both an FBT-3 Fieldbus Monitor and an FBT-5 Fieldbus Wiring Validator be
used when determining the quality of Fieldbus wiring and communications signals.
56 OW350_R1007
3.4 General DCU/RIO operational checks
3.4 General DCU/RIO operational checks
Use the system status screen for day-to-day operational status of a DCU/RIO. Any malfunctions
will be indicated by a DCU/RIO alarm. Specific information is provided with the system status
screen, detailing any specific malfunction. Normal color coding (green for DCU/RIO in control and
yellow for DCU/RIO in backup) of redundant DCU/RIO pairs indicates optimum DCU/RIO
operation.
Longer term, specific performance information is available via software using the Controller
Diagnostics program at an Ovation workstation (refer to the applicable Ovation Controller and
Controller Diagnostics user guides).
 Actual processing time of the DCU/RIO can be monitored and recorded.
 Total number of originated points in the DCU/RIO can be found and recorded.
 Actual amount of memory used can be found and recorded.
 Total number of control sheets can be found and recorded.
3.5 Protecting the Ovation equipment
You must be able to monitor and control temperature and humidity at storage sites and at the
equipment’s permanent location. Select or modify the equipment location to meet the following
criteria:
 Make provisions to protect the Ovation equipment from the following:
 Direct sunlight.
 Weather (rain, snow, and so forth).
 Lightning.
 Dust.
 ESD (Electrostatic Discharge).
 EMI/RFI (Electro-Magnetic Interference/Radio Frequency Interference).
 If harsh environmental conditions will be present, plan to use the optional sealed NEMA
enclosures (refer to ISA S71.04 for specifics on NEMA usage).
 If combustible airborne material (such as gases, dust, or fibers) is present, plan installation in
accordance with process safety analysis and hazardous area classification. Assure a source
of clean air for ventilated cabinets.
 If temperatures above those specified for a particular piece of equipment may occur, plan to
install auxiliary cooling or air conditioning. Optional enclosures are available with self-
contained air conditioning units.
The Ovation system requires a reliable power source with minimal voltage and frequency
fluctuations. Install wiring that is in accordance with accepted practices, as defined in the National
Electric Code.
OW350_R1007 57
3.5.1 Environmental information for Ovation equipment
These sections provide tables containing environmental information for the Ovation equipment:
 Workstations and peripherals (weight, dimensions, and temperatures) (see page 58).
 Workstations and peripherals (humidity, shock, and vibration) (see page 60).
 Workstations and peripherals (altitude and noise) (see page 62).
 Cabinets (weight, dimensions, and temperatures) (see page 65).
 Cabinets (altitude, humidity, and ingress protection) (see page 69).
 Cabinet components (weight, dimensions, and temperatures) (see page 71).
 I/O modules (weight, dimensions, temperatures, and humidity).
You can also refer to Ovation equipment spec sheets.
Note: All devices are subject to change as new technology is constantly improving and evolving.
3.5.2 Workstations and peripherals (weight, dimensions, and temperatures)
DEVICE EMERSON WEIGHT DIMENSIONS OPERATING STORAGE

PART H X W X D TEMP TEMP
NUMBER (ROUNDED TO
NEAREST INCH)
Engineering 5X00628 9.4 kg 360 x 175 x 417 10 to 35º C -40 to 65ºC

Station or mm
Database Server (50 to 95º F) (-40 to 149ºF)
(20.72 lbs) (14.17 x 6.89 x
Workstation
16.42 in)
(Dell Precision
9010)
Engineer Client, 5X00628 9.4 kg 360 x 175 x 417 10 to 35º C -40 to 65ºC
Operator, or mm
Virtual Controller (50 to 95º F) (-40 to 149ºF)
(20.72 lbs) (14.17 x 6.89 x
Workstation
16.42 in)
(Dell Optiplex
9010)
Domain Controller 5X00487 23.5 KG 440 x 218 x 522 10 to 35º C -40 to 65º C
or Terminal Server (51.8 lbs) mm
Host Workstation Windows (17.3 x 8.6 x 20.5 (50 to 95ºF) (-40 to 149º F)
Server 2008 in)
(Dell Poweredge
T310)
Ovation Process 5X00488 23.5 KG 440 x 218 x 522 10 to 35º C -40 to 65º C
Historian (OPH) (51.8 lbs) mm
Windows (17.3 x 8.6 x 20.5 (50 to 95ºF) (-40 to 149º F)
(Dell Poweredge Server 2008 in)
T310)
EDS Workstation 5X00567 17 kg 448 x 173 x 468 10 to 35º C -40 to 65ºC
Linux mm
(38 lbs) (50 to 95º F) (-40 to 149º F)
EDS Workstation 5X00569 (18 x 7 x 18 in)
Windows 7
(Dell Precision 64
bit T5500)
58 OW350_R1007

NUMBER (ROUNDED TO
NEAREST INCH)
EDS Workstation 5X00568 26 kg 864 x 482 x 720 10 to 35º C -40 to 65ºC

Linux Rack mm
Mounted (57.5 lbs) (50 to 95º F) (-40 to 149º F)
5X00570 (3.4 x 19 x 28.4 in)
EDS Workstation
Rack Mounted Windows
Server 2008
(Dell Poweredge Windows 7
R710)
Rack Mount 5X00574 23.91 kg 86.3 x 440.6 x 10 to 35º C -40 to 65ºC
Operator Station 792.7 mm
(52.6 lbs) (50 to 95º F) (-40 to 149º F)
(Dell Precision (3.4 x 17.35.x
R5500) 31.21 in)
Rack Mount 5X00462 26 kg 864 x 482 x 720 10 to 35º C -40 to 65ºC
Server Domain mm
Controller Windows (57.5 lbs) (50 to 95º F) (-40 to 149º F)
Server 2008 (3.4 x 19.x 28.4 in)
(Dell Poweredge
R710)
Rack Mount 5X00463 26 kg 864 x 482 x 10 to 35º C -40 to 65ºC
Server 720mm
Ovation Process Windows (57.5 lbs) (50 to 95º F) (-40 to 149º F)
Historian (OPH) Server 2008 (3.4 x 19.x 28.4 in)
(Dell Poweredge
R710)
19" Dell 190S FP 5X00473 (14 lbs) 493 x 410 x 182 5 to 35º C -20 to 60º C
Monitor mm
(41 to 95ºF) (-4 to 140ºF)
(19 x 16.5 x 7 in)
(extended)
20" Dell 2007FP 5X00310 6.9 kg 547 x 445 x 194 5 to 35º C 0 to 60º C
Monitor mm
15.2 lbs) (41 to 95ºF) (32 to 140ºF)
(22 x 17.5 x 8 in)
(extended)
24" Dell U2410 5X00474 9.57 kg 493 x 560 x 202 0 to 40º C 0 to 60º C
WFP Monitor mm
(20 lb) (32 to 104ºF) (32 to 140ºF)
(19.4 x 22 x 8 in)
32" LCD NEC 5X00493 14.3 KG 476 x 789 x 133 5 to 35 C -20 to 60 C
V321 Monitor (31.5 LB) mm (41 to 95 F) (-4 to 140 F)
(18.8 x 31.3 x 5.3
in)
40" LCD NEC 5X00494 24.0 KG 532.2 x 919.7 x 5 to 40 C -20 to 60 C
P401 Monitor 140.0 mm (41 to 104 F) (-4 to 140 F)
(53 LB) (21.0 x 36.2 x 5.5
in)
46" LCD NEC 5X00495 29.0 KG 608 x 1055 x 140 5 to 40 C -20 to 60 C
P461 Monitor mm (41 to 104 F) (-4 to 140 F)
(64 LB) (24.0 x 41.6 x 5.5
in)
OW350_R1007 59

NUMBER (ROUNDED TO
NEAREST INCH)
Ovation Keyboard 4D33935 2.3 kg 42 x 508 x 229 mm 0 to 70º C Not available

(5.3 lbs) (2 x 20 x 9 in) (32 to 158ºF)
OKIDATA 5X00445 16.8 kg 180 x 569 x 417 5 to 40º C Not available
Microline 395C mm
Printer (Alarms) (37 lbs) (41 to 104ºF)
(7.3 x 22.4 x 16.4
in)
HP B/W Laserjet 5X00328 30.2 kg 404 x 490 x 599 10 to 32º C 0 to 40º C
5200 Printer mm
110 VAC only (66.5 lbs) (50 to 91ºF) (-32 to 104º F)
(11 x 19 x 22 in)
HP Thermal/Inkjet 5X00243 19 kg 263 x 676 x 588 15 to 35º C -40 to 60º C
2800DTN Color mm
Printer (42 lbs) (59 to 95º F) (-40 to 140º F)
(10 x 26 x 23 in)
HP Color Laserjet 5X00520 38.5 kg 419 x 541 x 524 15 to 27º C 0 to 35º C
Enterprise mm
CP4525n/4525dn (85 lbs) (59 to 81º F) (32 to 95ºF)
(17 x 22 x 21 in)
HP Color Laserjet 5X00550 53.3 kg 465 x 544 x 586 15 to 27º C 0 to 35º C
5525 (110 VAC) H01,H02,H04 mm
(118 lbs) (59 to 81º F) (32 to 95ºF)
(18 x 22 x 23)
(220 VAC) 5X00550 84 kg
H03 885 x 745 x 688
(185 lbs) mm
(35 x 29 x 27 in)
RAID SATA to 5X00523 11.8 kg Not Available Not Available Not Available
iSCSI Media
(26 lbs)
(Without
drives)
60 OW350_R1007
3.5.3 Workstations and peripherals (humidity, shock, and vibration)
DEVICE EMERSON OPERATING OPERATING OPERATING

PART NUMBE R HUMIDITY SHOCK VIBRATION
(STORAGE (STORAGE (STORAGE
HUMIDITY) SHOCK) VIBRATION)
Engineering Station or 5X00628 20 to 80% 105 G 2.2 G

Database Server
Workstation
Engineer Client, Operator, 5X00628 20 to 80% 105 G 2.2 G
or Virtual Controller
Workstation
Domain Controller 5X00487 20 to 85% 31 G 0.26 G
or Terminal Server Host
Workstation Windows (5 to 95%) (71 G) (1.54 G)
Server 2008
(Dell Poweredge T310)
Ovation Process Historian 5X00488 20 to 80% 31 G 0.26 G
(Dell Poweredge T310) Windows (5 to 95%) (71 G) (1.54 G)
Server 2008
EDS Workstation Linux 5X00567 20 to 80% 40 G Not available
(5 to 95%) (105 G) (Not available)
EDS Workstation Windows 5X00569
7
(Dell Precision T5500)
EDS Workstation Linux 5X00568 20 to 80% 40 G Not available
Rack Mounted
(5 to 95%) (105 G) (Not available)
EDS Workstation Windows
7 Rack Mounted 5X00570
(Dell Poweredge R710)

Rack Mount Operator 5X00461 20 to 98% 40 G 0.25 G
Station
5X00559 (5 to 95%) (105 G) (0.5 G)
(Dell Precision R5400)
Rack Mount Server Domain 5X00462 20 to 80% 31 G 0.26 G
Controller
(5 to 95%) (71 G) (1.54 G)
(Dell Poweredge R710)
Rack Mount Server 5X00463 20 to 80% 31 G 0.26 G
Ovation Process Historian
(OPH) (5 to 95%) (71 G) (1.54 G)
19" Dell 190S FP Monitor 5X00473 10 to 80% Not available Not available
(5 to 90%) (Not available) (Not available)
20" Dell UltraSharp 2007FP 5X00310 5 to 95% Not available Not available
Monitor
(Not (Not available) (Not available)
available)
24 " Dell U2410 WFP 5X00474 10 to 80% Not available Not available
Monitor
OW350_R1007 61
DEVICE EMERSON OPERATING OPERATING OPERATING

PART NUMBE R HUMIDITY SHOCK VIBRATION
(STORAGE (STORAGE (STORAGE
HUMIDITY) SHOCK) VIBRATION)

32" NEC LCD 5X00493 20 to 80% Not available Not available
V321 Monitor (10 to 90%) (Not available) (Not available)
40" NEC LCD P401 Monitor 5X00494 20 to 80% Not available Not available
46" NEC LCD P461 Monitor 5X00495 20 to 80% Not available Not available
Ovation Keyboard 4D33935 95% Not available Not available
maximum
(Not available) (Not available)
(Not
available)
OKIDATA Microline 395C 5X00445 30 to 80% Not available Not available
Printer (Alarms)
HP B/W Laserjet 5200 5X00328 20 to 80% Not available Not available
Printer
HP Thermal/Inkjet 5X00243 15 to 80% Not available Not available
2800TDN Printer
available)
HP Color Laserjet 5X00520 30 to 70% Not available Not available
Enterprise
CP4525n/4525dn (10 to 90%) (Not available) (Not available)
HP Color Laserjet 5525 5X00550 30 to 70% Not available Not available

Breeze-Hill TMT7-9100 5X00367 10 to 90% Not available Not available
Optical Device
RAID SATA to iSCSI Media 5X00523 0 to 85% Not available Not available
available)
62 OW350_R1007
3.5.4 Workstations and peripherals (altitude and noise)
DEVICE EMERSON OPERATING STORAGE ACOUSTICAL

PART ALTITUDE ALTITUDE NOISE
NUMBER
Engineering 5X00557 -15.2 to 3048 m -15.2 to 10,668m Not available

Station or
Database Server (-50 to 10,000 ft) (-50 to 35,000 ft)
Workstation
(Dell T3500)
Engineer Client, 5X00628 -15.2 to 3,048 m -15.2 to 10,670m Not available
Operator, or
Virtual Controller (-50 to 10,000 ft) (-50 to 35,000 ft)
Workstation
(Dell Optiplex 990)
Domain Controller 5X00487 -16 to 3,048 m -16 to 10,670m Not available
or Terminal Server
Host Workstation (-50 to 10,000 ft) (-50 to 35,000 ft)
(Dell T310)
Ovation Process 5X00488 -16 to 3,048 m -16 to 10,670 meters Not available
Historian (-50 to 35,000 ft)
(-50 to 10,000 ft)
(Dell T310)
EDS Workstation 5X00567 -15.2 to 3,048 m -15.2 to 10,670m Not available
Linux
(-50 to 10,000 ft) (-50 to 35,000 ft)
EDS Workstation
Windows 7 5X00569
(Dell T5500)
EDS Workstation 5X00568 -16 to 3,048 m -16 to 10,670m Not available
Linux Rack
Mounted (-50 to 10,000 ft) (-50 to 35,000 ft)
EDS Workstation 5X00570

Windows 7 Rack
Mounted
(Dell R710)
Rack Mount 5X00461 -16 to 3,048 m -16 to 10,600 meters Not available
Operator Station (-50 to 35,000 ft)
5X00559 (-50 to 10,000 ft)
(Dell R5400)
Server Domain (-50 to 35,000 ft)
Controller (-50 to 10,000 ft)
(Dell R710)
Server (-50 to 35,000 ft)
(-50 to 10,000 ft)
Ovation Process
Historian (OPH)
(Dell R710)
19" Dell 190S FP 5X00473 3.7 km max 12.2 km max Not available
OW350_R1007 63
DEVICE EMERSON OPERATING STORAGE ACOUSTICAL

PART ALTITUDE ALTITUDE NOISE
NUMBER
Engineering 5X00557 -15.2 to 3048 m -15.2 to 10,668m Not available

Station or
Database Server (-50 to 10,000 ft) (-50 to 35,000 ft)
Workstation
(Dell T3500)
Monitor (12,000 ft max) (40,000 ft max)
20" Dell 2007FP 5X00310 3.7 km max 12.2 km max Not available
Monitor
(12,000 ft) (40,000 ft)
24" Dell U2410 5X00474 3658 m max 12192 m Not available
WFP Monitor
(12,000 ft) (40,000 ft)
32" NEC LCD 5X00493 3 km max Not available Not available
V321 Monitor (9840 ft max)
P401 Monitor
(9840 ft max)
P461 Monitor
(9840 ft max)
Ovation Keyboard 4D33935 2 km max 12.5 km max (41,010 Not available
ft max )
(6,562 ft max)
OKIDATA 5X00445 Not available Not available Less than 54 dBA
Microline 395C
Printer (Alarms)
HP B/W Laserjet 5X00328 Not available Not available 54 dBA Printing:
5200 Printer
31 dBA Idle
HP Thermal/Inkjet 5X00243 3.1 km max Not available 6.2 dBA
2800TDN Printer
(10,000 ft max)
HP Color Laserjet 5X00520 0 to 3000 meters Not available 6.9 dBA
Enterprise
CP4525n/4525dn (0 to 9,842 ft
max)
HP Color Laserjet 5X00550 0 to 3000 meters Not available 51 dBA operating
5525
(0 to 9,842 ft
max)
Breeze-Hill TMT7- 5X00367 Not available Not available Not available
9100 Optical
Device
RAID SATA to 5X00523 Not available Not available Not available
iSCSI Media
64 OW350_R1007
3.5.5 Cabinets (weight, dimensions, and temperatures)
CABINE T P ART WEIGHT DIMENSIONS OPERATING STORAGE

TYPE NUMBER (EMPTY (H X W X D) TEMP TEMP
CABINE T)
Ovation 1X00518 183 kg 2083x601x890 mm Not Not

Workstation applicable applicable
Cabinet: (403 lb) (82x24x35 in)
Vented
(Holds up to 6
Dell Tower
workstations
with 150 lb load
rating per shelf)
Ovation Server 1X00545 161 kg 2083x601x890 mm Not Not
Cabinet Vented applicable applicable
(354 lb) (82x24x35 in)
Can also hold
Ovation Static load
Security Center rating of 680
(OSC) kg (1500 lb)
Ovation 5X00482 Not Available 78.76 x 42.18 x 10 to 30 C -40 to 65 C

Security Center 23.82mm (50 to 86 F) (-40 to 149 F)
Cabinet Kit
EMC Cabinet: 1X00520H01 155 kg 2000x600x600 mm See Note 1. -25 to 70º C
Vented
NEMA12, Rittal (replaces (341lb) (78x24x24 in) ------------------ (-13 to 158º
4D33947H01) - F) for
Controller
0 to 60º C cabinets
(32 to 140º F) which must
for vented I/O be vented
cabinets ------------------
-
-25 to 85º C
(-13 to 185º
F) for vented
I/O cabinets
EMC Cabinet: 1X00520H02 155 kg 2000x600x600 mm 0 to 60º C -25 to 85º C
Sealed
NEMA12, Rittal (replaces (341lb) (78x24x24 in) (32 to 140º F) (-13 to 185º
4D33947H02) @175 W max F)
internal load
for sealed I/O
cabinet.
------------------
-
0 to 50º C
(32 to 122º F)
@225 W max
internal load
for sealed I/O
cabinet.
Cabinet 5X00018H01 136 kg 2000x600x500 mm See Note 1. -25 to 70º C
Vented,
OW350_R1007 65

CABINE T)

Vented
(Holds up to 6
Dell Tower
workstations
with 150 lb load
rating per shelf)
NEMA12 (300 lb) (78x24x20 in) ------------------ (-13 to 158º
F) for
0 to 60º C Controller
(32 to 140º F) cabinets
for vented I/O which must
cabinets be vented
------------------
-
-25 to 85º C
(-13 to 185º
F) for vented
I/O cabinets
Cabinet Sealed 5X00019H01 131 kg 2000x600x500 mm 0 to 60º C -25 to 85º C
NEMA12
or (290 lb) (78x24x20 in) 32 to 140º F) (-13 to 185º
or @175 W max F)
5X00019H02 internal load
NEMA4 for sealed I/O for I/O
cabinet. cabinets
------------------ ------------------
-
See Note 2.
-25 to 70º C
------------------
(-13 to 158º
0 to 50º C F) for
Controller
@225 W max which must
internal load have AC
for sealed I/O
cabinet.
Cabinet Vented 5X00020 115.6 kg 2000x600x600 mm See Note 1. -25 to 70º C
NEMA12
(without (255 lb) (78x24x24 in) ------------------ (-13 to 158º
mounting plate) F) for
cabinets be vented
------------------
-25 to 85º C
(-13 to 185º
F) for vented
66 OW350_R1007

CABINE T)

Vented
(Holds up to 6
Dell Tower
workstations
with 150 lb load
rating per shelf)
I/O cabinets
Cabinet Vented 5X00127 147 kg 2000x600x600 mm See Note 1. -25 to 70º C
NEMA12 (with
mounting plate) (325 lb) (78x24x24 in) ------------------ (-13 to 158º
F) for
cabinets be vented
------------------
-25 to 85º C
(-13 to 185º
F) for vented
I/O cabinets
Cabinet 1X00454H01 191 kg 2000x914x600 mm See Note 1 -25 to 70º C
Vented, for Controller
NEMA12 or (420 lb) (78x36x24 in) cabinets. (-13 to 158º
(Marshalling F) for
plate) ------------------ Controller
- cabinets
or which must
0 to 60º C be vented
Cabinet 1X00454H02
Vented, (32 to 140º F) ------------------
NEMA12 for vented I/O -
(Standard cabinets
plate) -25 to 85º C
(-13 to 185º
F) for vented
I/O cabinets
Cabinet 5X00021H01 173 kg 2000x800x600 mm See Note 1 -25 to 70º C
Vented, for Controller
NEMA12 or (380 lb) (78x32x24 in) cabinets. (-13 to 158º
(Marshalling F) for
plate) ------------------ Controller
- cabinets
or which must
0 to 60º C be vented
Cabinet 5X00021H02
Vented, (32 to 140º F) ------------------
NEMA12 for vented I/O -
(Standard cabinets
plate) -25 to 85º C
(-13 to 185º
F) for vented
I/O cabinets
OW350_R1007 67

CABINE T)

Vented
(Holds up to 6
Dell Tower
workstations
with 150 lb load
rating per shelf)
Cabinet Sealed, 1X00455H01 186 kg 2000x914x600 mm 0 to 60º C -25 to 85º C
NEMA12
(Marshalling (410 lb) (78x36x24 in) (32 to 140º F) (-13 to 185º
plate) @175 W max F) for I/O
internal load cabinets
or for sealed I/O
cabinet. ------------------
NEMA12 1X00455H02
(Standard ------------------ -25 to 70º C
plate) - (-13 to 158º
or See Note 2 F) for
for Controller Controller
NEMA4 1X00455H03 cabinets
cabinet.
(Marshalling which must
plate) ------------------ have AC
-
or
1X00455H04 0 to 50º C
NEMA4
(Standard (32 to 122º F)
plate) @225 W max
internal load
for sealed I/O
cabinet.
Cabinet Sealed, 5X00035H01 168 kg 2000x800x600 mm 0 to 60º C -25 to 85º C
NEMA12
(Marshalling (370 lb) (78x32x24 in) (32 to 140º F) (-13 to 185º
plate) @175 W max F) for I/O
internal load cabinets
or for sealed I/O
cabinet. ------------------
NEMA4 5X00035H02
(Marshalling ------------------ -25 to 70º C
plate) - (-13 to 158º
or See Note 2 F) for
for Controller Controller
NEMA12 5X00035H03 cabinets
cabinets.
(Standard which must
plate) ------------------ have AC
-
or
5X00035H04 0 to 50º C
NEMA4
(Standard (32 to 122º F)
plate) @225 W max
internal load
for sealed I/O
cabinet.
Cabinet Sealed, 5X00046H01 159 kg 2000x600x600 mm Same as Same as
68 OW350_R1007

CABINE T)

Vented
(Holds up to 6
Dell Tower
workstations
with 150 lb load
rating per shelf)
NEMA12 (350 lb) (78x24x24 in) above above
Cabinet Sealed, 5X00046H02 161 kg 2000x600x600 mm Same as Same as

NEMA4 above above
(355 lb) (78x24x24 in)
Cabinet 5X00068H01 127 kg 2000x600x400 mm See Note 1. -25 to 70º C
Vented,
NEMA12 (Front (280 lb) (78x24x16 in) (-13 to 158º
Access only) F)
for Controller
cabinets
which must
be vented
-25 to 85º C
for vented I/O
1
The maximum ambient temperature for an Ovation OCR400 Controller cabinet is 50º C. The Controller
cabinet must be ventilated with fans mounted in both the front and rear doors. Reference Ovation
ventilated cabinet 5X00127.
The use of third-party devices such as fiber-optic media converters and Profibus gateways necessitate
lower maximum operating temperatures. Based on a 5º C internal rise, the maximum ambient
temperature for an OCR400 Controller cabinet that contains fiber-optic media converters is 35º C. The
maximum ambient temperature for an OCR400 Controller cabinet that contains a Profibus gateway is 45º
C.
2
In the event that environmental conditions dictate that an OCR400 Controller needs to be mounted in a
sealed cabinet, a properly-sized AC unit must be used to maintain the specified operating temperatures
for all of the internal components. The use of internally mounted circulatory fans is required to eliminate
hot spots and provide a more-uniform internal temperature.
OW350_R1007 69
3.5.6 Cabinets (altitude, humidity, and ingress protection)
CABINE T TYPE PART NUMBE R OPERATING RELATIVE INGRESS

ALTITUDE HUMIDITY PROTECTION (IP)
1
RATING
Ovation Workstation 1X00518 Not applicable Not applicable Not applicable

Cabinet: Vented
(Holds up to 6 Dell Tower
workstations with 150 lb
load rating per shelf)
Ovation Server Cabinet 1X00545 Not applicable Not applicable Not applicable
Vented
Can also hold Ovation
Security Center (OSC)
EMC Cabinet: 1X00520H01 2 km max 0 to 90% 53
Sealed NEMA12, Rital
(replaces (6561 ft max)
4D33947H01)
EMC Cabinet: 1X00520H02 2 km max 0 to 90% 55
Sealed NEMA12, Rital
(replaces (6561 ft max)
4D33947H02)
Cabinet Vented NEMA 12 5X00018 2 km max 0 to 95% 53
(6561 ft max)
Cabinet Sealed NEMA 12 5X00019H01 2 km max 0 to 95% 55 (NEMA 12)
or or (6561 ft max) 66 (NEMA 4)
NEMA 4 5X00019H02
Cabinet Vented NEMA 12 5X00020H02 2 km ma 0 to 95% 53
(without mounting plate)
(6561 ft max)
Cabinet Vented NEMA 12 5X00127H02 2 km max 0 to 95% 53
(with mounting plate)
(6561 ft max)
(Marshalling plate)
or (6561 ft max)
or
Cabinet Vented NEMA 12 1X00454H02
(standard plate)
Cabinet Vented NEMA 5X00021H03 2 km max 0 to 95% 53
12
(Marshalling plate) or (6561 ft max)
or
5X00021H04
Cabinet Vented NEMA 12
(standard plate)
(Marshalling plate)
(6561 ft max) 66 (NEMA 4)
or
NEMA 12
(Standard plate) 1X00455H02
70 OW350_R1007
CABINE T TYPE PART NUMBE R OPERATING RELATIVE INGRESS

ALTITUDE HUMIDITY PROTECTION (IP)
1
RATING
or
NEMA 4
(Marshalling plate)
1X00455H03
or
NEMA 4
(Standard plate)
1X00455H04
(Marshalling plate)
(6561 ft max) 66 (NEMA 4)
or
NEMA 4
(Marshalling plate) 5X00035H06
or
NEMA 12
(Standard plate) 5X00035H07
or
NEMA 4 5X00035H08
(Standard plate)
Cabinet Sealed NEMA 12 5X00046H03 2 km max 0 to 95% 55
(6561 ft max)
Cabinet Sealed NEMA 4 5X00046H04 2 km max 0 to 95% 66
(6561 ft max)
(6561 ft max
OW350_R1007 71
3.5.7 Cabinet components (weight, dimensions, and temperatures)
COMPONENT EMERSON WEIGHT DIMENSIONS OPERATING STORAGE

NUMBER
OCR400 Controller 5X00247 2.5 kg 206 x 343 x 188 mm See Note 1. -25 to 70ºC
chassis (loaded)
(5.5 lbs) (8 x 13.5 x 7.4 in) (-13 to 158ºF)
Standard Electronic N/A 0.340 kg 155 x 127 x 55 mm 0 to 60ºC -40 to 85ºC

(E) module
(0.75 lbs) (6.1 x 5 x 2.15 in) (32 to 140ºF) (-40 to 185ºF)
Standard Personality N/A 0.133 kg 88 x 119 x 28 mm 0 to 60ºC -40 to 85ºC
(P) module
(0.25 lbs) (3.5 x 4.7 x 1.1 in) (32 to 140ºF) (-40 to 185ºF)
Relay Output 1C31219 0.140 kg 87 x 158 x 18 mm 0 to 60ºC -25 to 85ºC
module
Standard I/O Base 1B30035 0.907 kg 292 x 127 x 64 mm 0 to 60ºC -25 to 85ºC
(2 lbs) (11.5 x 5 x 2.5 in) (32 to 140ºF) (-13 to 185ºF)
Standard I/O 1X00014 0.907 kg 292 x 127 x 64 mm 0 to 60ºC -25 to 85ºC
Marshalling Base
(2 lbs) (11.5 x 5 x 2.5 in) (32 to 140ºF) (-13 to 185ºF)
Secured Marshalling 5X00334G01 0.907 kg 292 x 137 x 64 mm 0 to 60ºC -25 to 85ºC
Base
(2 lbs) (11.5 x 5.4 x 2.5 in) (32 to 140ºF) (-13 to 185ºF)
Terminator 1B30023 0.113 kg 38 x 108 x 38 mm 0 to 60ºC -25 to 85ºC
assembly
ROP Transition 3A99266 0.218 kg 70 x 252 x 28 mm 0 to 60ºC -25 to 85ºC
Panel
Remote Node 4D33924 0.45 kg 76 x 307 x 28 mm 0 to 60ºC -25 to 85ºC
Transition Panel
(TND) CE Mark (1.0 lbs) (3 x 12.1 x 1.1 in) (32 to 140ºF) (-13 to 185ºF)
(with cover)
Remote Node 1P00028 0.245 kg 76 x 307 x 28 mm 0 to 60ºC -25 to 85ºC
Transition Panel
(TND) (0.54 lbs) (3 x 12.1 x 1.1 in) (32 to 140ºF) (-13 to 185ºF)
(without cover)
RRP Top Transition 3A99252 0.218 kg 70 x 252 x 28 mm 0 to 60ºC -25 to 85ºC
Panel
RRB Bottom 3A99253 0.177 kg 70 x 252 x 28 mm 0 to 60ºC -25 to 85ºC
Transition Panel
(0.39 lbs) (2.8 x 9.9 x 1.1 in) (32 to 140ºF) (-13 to 185ºF
Relay Output Base 1C31223 1.05 kg 114 x 422 x 125 mm 0 to 60ºC N/A
(16 G2R relays)
(2.31 lbs) (4.5 x 16.6 x 4.9 in) (32 to 140ºF)
(12 KUEP relays)
Form C (3.62 lbs) (4.5 x 16.6 x 4.9 in) (32 to 140ºF)
(12 KUEP relays)
Form X (3.81 lbs) (4.5 x 16.6 x 4.9 in) (32 to 140ºF)
72 OW350_R1007
COMPONENT EMERSON WEIGHT DIMENSIONS OPERATING STORAGE

NUMBER
DIN rail power 4D33900 3.8 kg 406 x 108 x 178 mm 5 to 60ºC -40 to 85ºC
supply
(8.5 lbs) (16 x 4.25 x 7 in) (41 to 140ºF) (-40 to 185ºF)
DIN rail power 1X00416 3.2 kg 401 x 106 x 179 mm 5 to 60ºC -40 to 85ºC
supply
(7 lbs) (15.8 x 4.17 x 7 in) (41 to 140ºF) (-40 to 185ºF)
Power Distribution 5A26304 0.680 kg 279 x 76 x 108 mm 0 to 60ºC -40 to 85ºC
Module
(1.5 lbs) (11 x 3 x 4.25 in) (32 to 140ºF) (-40 to 185ºF)
Power Distribution 1X00102 N/A 315 x 76 x 108 mm 0 to 60ºC -40 to 85ºC
Module
(12.4 x 3 x 4.25 in) (32 to 140ºF) (-40 to 185ºF)
Remote I/O MAU 1C31206 0.53 kg 292 x 127 x 64 mm 0 to 60ºC -40 to 85ºC
base assembly
(1.16 lbs) (11.5 x 5 x 2.5 in) (32 to 140ºF) (-40 to 185ºF)
electronics module
(.59 lbs) (6.1 x 5 x 2.15 in) (32 to 140ºF) (-40 to 185ºF)
personality module
Remote Node 1C31205 0.58 kg 292 x 127 x 64 mm 0 to 60ºC -25 to 85ºC
Controller (RNC)
base assembly (1.28 lbs) (11.5 x 5 x 2.5 in) (32 to 140ºF) (-13 to 185ºF)

Controller (RNC)
electronics module (0.73 lbs) (6.1 x 5 x 2.12in) (32 to 140ºF) (-40 to 185ºF)

Controller (RNC)
personality module (0.28 lbs) (3.5 x 4.7 x 1.1 in) (32 to 140ºF) (-40 to 185ºF)
1
The maximum ambient temperature for an Ovation OCR400 Controller cabinet is 50º C. The Controller
cabinet must be ventilated with fans mounted in both the front and rear doors. Reference Ovation
ventilated cabinet 5X00127.
The use of third-party devices such as fiber-optic media converters and Profibus gateways necessitate
lower maximum operating temperatures. Based on a 5º C internal rise, the maximum ambient
temperature for an OCR400 Controller cabinet that contains fiber-optic media converters is 35º C. The
maximum ambient temperature for an OCR400 Controller cabinet that contains a Profibus gateway is 45º
C.
OW350_R1007 73
3.6 Grounding guidelines for clustered cabinet arrangements
It is acceptable to cluster cabinets to simplify the EMC grounding. The following guidelines apply:
 Examples of clustered cabinet arrangements are shown in the figures in To remove the
shorting bar from an Ovation cabinet (see page 75). Designate Cabinet #1 as the focal
cabinet. The focal cabinet is the cabinet in which the EMC ground connection is made.
Designate the other cabinets as the adjacent cabinets. In all systems, it is mandatory that no
adjacent cabinet be more than 10 meters from the central cabinet and it is recommended that
no more than five cabinets be part of a cluster.
In CE Mark Certified systems, the clustered cabinets MUST be suited (the sideskins are
removed between adjacent cabinets and the adjacent cabinets are bolted together with EMC
gasketing that is approved for the cabinets). Alternatively, it is permissible to wave the suited
cabinet requirement if all electrical cabling between cabinets within the cluster (with the
exception of the EMC grounding cable) is run in grounded metal conduit that is continuous
with the cabinets.
 Make the EMC earth ground connections from the focal cabinet within the cluster using a
minimum of 4 AWG cable (preferably 0000 AWG) to the earth grounding point. Use the
dedicated studs on the bottom left and right of the mounting plate within the cabinet to make
this connection. Make certain that the DC resistance from the cabinet to the earth grounding
point is less than 1 ohm.
Additionally, all cabinets in the cluster must have their EMC grounds daisy chained together
from the focal cabinet using #4 AWG minimum cable. Make certain that the total length of the
ground cable from the ground point to the last cabinet in the cluster is minimized.
 To minimize the chance of ground loops, ensure that the protective earth is grounded at a
location that is electrically common with the EMC ground point or at least within one ohm of
this point. Ground the protective earth conductor only at the distribution source. Avoid
connections to earth at the intermediate load centers.
 The Digital Power Ground (PGND) is tied to the cabinet by a factory-installed shorting bar on
the Power Distribution Panel. When installing cabinet clusters, remove this shorting bar (see
page 75) on all cabinets except the focal cabinet.
 Every cabinet has a factory installed strap between a PGND stud on the distribution panel
and a PGND stud on the CBO backplane or transition panel (transition panels include ROP,
RRP, RRB, and TND). To connect the PGNDs in clustered cabinets, do the following:
 Connect an 8AWG strap from a PGND stud on the Power Distribution Panel of the focal
cabinet to a PGND stud on the backplane or transition panel on the adjacent cluster
cabinets.
Note: In the event that an adjacent cabinet in the cluster has multiple backplanes or panels,
connect the strap to only one backplane or panel. All transition panels within a cabinet should
have the PGND points connected.
 In the event that there are multiple adjacent cabinets on one side of the focal cabinet,
place a PGND strap between each of these cabinets or directly to the focal cabinet as
appropriate. You can connect the strap to any available PGND stud found on a
distribution panel, a backplane, or transition panel in each cabinet.
74 OW350_R1007
3.6.1 To remove the shorting bar from an Ovation cabinet
The Digital Power Ground (PGND) is tied to the cabinet by a factory-installed shorting bar on the
Power Distribution Panel. When you install cabinets in clusters (see page 74), remove this
shorting bar on all cabinets except the focal cabinet (as shown in the following figures).
Perform the following steps to remove the shorting bar from an Ovation cabinet:
1. Turn off the power to the cabinet.

2. Remove the four thumb screws holding the cover on the Power Distribution Module.
3. Remove the nuts and lock washer attaching the shorting bar to the distribution panel. Remove
the cable strap connected to the mounting plate and the shorting bar. Discard the shorting
bar.
4. Reattach the cable strap (using the nut and lock washer previously removed) to the stud
referenced by the circled ground symbol (the upper left most stud).
5. Reattach the cover using the four thumb screws.
Figure 16: OCR400 or OCR1100 Controller and cabinet grounding cluster
OW350_R1007 75
3.7 Performing outage maintenance
3.7 Performing outage maintenance

Perform the following tasks during a planned outage:
 Use the Cleaning and maintenance guidelines (see page 10) to perform the system checks
found in Inspection and routine maintenance tasks (see page 9).
 Run a 24 hour load test on each power supply, with the other power supply shutdown.
 If required, make sure to replace the flash drives in each Controller.
 Reset each Controller.
76 OW350_R1007
S E C T I O N 4
4 Ovation system maintenance
IN THIS SECTION
Hardware preventative maintenance checklist ................................................................. 77

Periodic Human Machine Interface (HMI) checks ............................................................. 77
Ovation Error Log window at the Operator Station ........................................................... 78
User profile options for Windows domains ........................................................................ 88
Ovation AntiVirus Upkeep ................................................................................................. 89
Switch and Router Configuration and Internet Operating System (IOS) .......................... 90
Technical tips and best practices ...................................................................................... 91
4.1 Hardw are preventative maintenance checklist
The following checks can be used as preventative maintenance as well as corrective

maintenance.
1. Ensure that power on the rear of the cabinet is on (primary and secondary).
2. Check that the voltage outputs from the power supply are 24V from both the Auxiliary and
Main (Primary and secondary).
3. Make sure that all the processor LEDs (see page 174) are functional and readable.
4. Make sure that all the I/O LEDs (see page 176) on the processor are functional and readable.
5. Make sure that the DCU/RIO is on and scanning the I/O modules.
6. Check to make sure that the Ethernet card’s status light is green.
7. Check to make sure that cabinet wiring and cabling (interior and exterior) are neatly bundled,
not frayed or resting on any sharp surfaces, and properly secured.
8. Make sure that all wiring and cabling is properly connected and/or terminated.
9. Ensure that all fans are running, this includes door fans and power supply fans.
 Listen for any noise that may indicate bearing problems.
 This may involve cleaning any filters and blowing out any dust.
Note: If any portion of the system is determined to be inoperable, refer to What is Involved in
the Replacement of User Serviceable Fuses? (see page 267).
OW350_R1007 77
4.2 Periodic Human Machine Interface (HMI) checks
4.2 Periodic Human Machine Interface (HMI) checks

 Review the Windows Event Viewer (see page 78) for warnings and errors.
 Review the Ovation Error Log (see page 78).
 Review system performance (see page 78).
 Defragment Hard Disk Drives (see page 93) (HDDs).
4.2.1 To review the Windows Event Viewer for warnings and errors
1. Select Start -> Control Panel -> Administrative Tools -> Event Viewer.
2. View the System and Application logs which are typically the most applicable for HMIs.
 Ovation typically logs status of Ovation security propagation.
4.2.2 To review system performance

1. Open the Performance Manager by accessing Ctrl-Alt-Delete -> Windows Task Manager ->
Performance Manager.
2. Review disk space utilization.
3. Review physical and virtual memory usage, settings and location.
4. Check the Performance Monitor.
4.3 Ovation Error Log w indow at the Operator Station
An Ovation Error Log window contains error, warning, and informational messages generated by
the various Ovation services and applications.
The Error Log window displays system messages in a standard Windows list view using up to five
columns of information. When first displayed, error messages appear in the window in
chronological order from oldest to newest. You can define the number of columns (see page 85)
that appear and the priority of the messages (see page 86) in the columns.
This information displays in two different modes, Live (see page 80) and Historical (see page 81).
You can toggle between the two modes in order to view current as well as older error messages.
A filtering function allows you to search for error messages based on dates or priority (see page
86).
You can use the Ovation Developer Studio to define the following Error Log functions (refer to
Ovation Operator Station Configuration Guide):
 Send error messages to another Ovation workstation for storage and display. The messages
are also available on the local workstation.
 Archive older error messages.
 Configure the size of the active Error Log file (Live) so that as it reaches its maximum size,
part of the file (oldest Live messages) is archived in the Historical file.
 Configure the size of the archival Historical file so that as it reaches its maximum size, part of
the file (oldest Historical messages) is deleted. This process maintains a consistent size for
both the Live and Historical Error Log files.
78 OW350_R1007
4.3 Ovation Error Log window at the Operator Station
4.3.1 To access the Error Log window at the Operator Station

1. Open the Ovation Applications folder at the Operator Station and double-click on the Error
Log icon.
OR
If the Error Log application is already running, double click on the Error Log icon located on
the system tray.
OR
Select Start -> Ovation -> Error Log.
2. The Ovation Error Log window appears and displays error, warning, and informational
messages generated by the various Ovation services and applications.
Figure 17: Ovation Error Log window (Live mode)
OW350_R1007 79
4.3.2 Live Error Log window at the Operator Station
The Live Error Log window displays Live mode messages and contains the following elements:
 Menu bar elements (see page 82)
 Toolbar elements (see page 82)
 Columns (see page 83)
You can select the Historical button to switch to the Historical Error Log window (see page 81).
The Total Rows field at the bottom of the window displays the total number of live reports (rows).
Figure 18: Ovation Error Log window (Live mode)
80 OW350_R1007
4.3.3 Historical Error Log window at the Operator Station
The Historical Error Log window displays Historical mode messages and contains the following
elements:
 Menu bar elements (see page 82)
 Toolbar elements (see page 82)
 Columns (see page 83)
When you are viewing the Error Log in Historical mode, you can filter the messages based on
selected time periods, message priority, and/or originating drop:
 Use the Start Date and End Date pull-down menus to pick the beginning and ending dates
and times for the messages you want to display in the Historical Error Log window. This
means you can filter and display messages that are in the Live mode as well as in the
Historical mode and display them at the same time.
 Use the Priority Level pull-down menu to select the minimum priority level for the messages
you want to display in the Historical Error Log window.
 Use the Source entry field to enter the specific drop name of the originating drop whose
messages you want to display in the Historical Error Log window.
 Use the Search/Cancel button to start a search or cancel a search that is in progress.
 Note that the Total Rows field at the bottom of the window displays the total number of
events (rows) in the Search result.
You can select the Live button to switch to the Live Error Log window (see page 80).
Figure 19: Ovation Error Log window (Historical mode)
OW350_R1007 81
4.3.4 Error Log window menu bar at the Operator Station
The menu bar contains four pull-down menus. The following table lists and describes the menu
options.
Error Log menu bar elements
MENU DESCRIPTION
File Print – sends the error list to the printer.

Print Preview – displays a preview of the error list on the screen before printing.
Print Setup – displays a dialog box to define the printer properties.
Save as – saves the list to another location or to another name.
Exit – ends the program.
Edit Delete – permanently removes all selected items from the Error Log.
Live - displays the current Error Log messages.
Historical - displays the older Error Log messages.
View Toolbar – makes the toolbar visible or not visible.
Status Bar – indicates how much time is left to complete the Search.
Select Columns - displays a dialog box (Choose Columns (see page 85)) that allows you to
select the columns you want to display in the Error Log window.
Refresh – displays the screen after the Error Log messages are reread.
Priority Level – displays a dialog box (Select Priority Level (see page 86)) that allows you to
choose a new minimum priority level for displayed messages.
Auto Refresh – toggles the auto refresh function on and off. By default, the display
automatically refreshes when an application logs a message.
Help Help Topics – displays the online help menu.
About Error Log – displays a dialog box with the application name and version number.
4.3.5 Error Log window toolbar at the Operator Station
The Error Log toolbar is typically located below the Menu bar. The toolbar objects display from left
to right and are described in the following table.
Figure 20: Error Log toolbar when displaying Live data
Figure 21: Error Log toolbar when displaying Historical data
82 OW350_R1007
Error Log toolbar elements
ICON DESCRIPTION
Historical error log messages display when you select this icon.
Live error log messages display when you select this icon.
Delete Delete items – deletes the selected error message from the Error Log.
Print – prints the current error log.
Help – displays the online help.
4.3.6 Error Log window columns at the Operator Station
The data about the error messages displays in a standard Windows list view that contains up to
five columns. You can define what columns appear in the window and you can resize the columns
by adjusting the headers at the top of each column. Click on a column header to sort the list in
alphabetical order based on that column's data. Click again to sort the list in reverse alphabetical
order. By default, the messages appear in chronological order.
Messages that appear in the Error Log window (see page 78) have five components of
information. This information appears in the columns that you selected from the Choose Columns
dialog box (see page 85).
 Date Time – indicates the date and time the message was generated and added to the Error
Log.
 Source – indicates the workstation that first logged this message. If you see this message at
a workstation that has been configured as a Logging Host, this column lists the workstation
that sent the message. (See Ovation Operator Station Configuration Guide for information on
configuring the Error Log.)
 Priority – displays a value ranging from 0 to 7. The value 0 represents an extremely severe
condition; the value 7 represents benign information or a debugging message. By default,
only priorities 0 through 6 display.
 Identifier – displays a string showing which Ovation program or drop generated the message.
 Description – contains a description of the error message. Some error messages may
contain a series of hex numbers. These are typically Fault Codes from the Controller and
have the following format:
<Fault Code>: <Fault ID>: <Fault Parameter1>... <Fault Parameter5>.
For Ovation 3.5 and later releases, fault codes are part of Ovation software and are displayed
in the Ovation System Viewer application. Refer to the Ovation Operator Station User Guide
for additional information.
OW350_R1007 83
Additional Information on Fault Code: Hardware Address and I/O Status Values
For Ovation 3.5 and later releases, the Fault Codes are part of the Ovation System Viewer
application.
The following tables apply to the hardware address and I/O Status values for Fault Code 66 (Fault
ID B).
Note: All fields are 0 based. This table only applies to IOIC Devices.
Hardware Address Decoding
MODULE ACCESS (BIT 13:0)
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 Node Branch Module Offset
N O D E A C C E S S ( B I T 1 3 :1 , B I T 7 :1 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 Node 1 Offset
GROUP WRITE TO M O D U L E S ( B I T 1 3 :1 , B I T 7 : 0 , B I T 8 :0 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 0 0 Offset
GROUP WRITE TO N O D E S ( B I T 1 3 :1 , B I T 7 : 0 , B I T 8 : 1 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 1 0 Offset
I/O Status Values
BIT DEFINITION
0x0000 Local: No response from module

0x0800 Remote: Echo: No response
0x0a00 Remote: Node: No response
0x0e00 1
Remote: Transmit collision
0x2000 Local: Bad CRC
0x2800 1
Remote: Echo: Bad CRC
0x2a00 Remote: Node: Bad CRC
0x2e00 Remote: I/O control register changed
0x4000 Local: Module in attention
0x4c00 Remote: Node in attention
84 OW350_R1007
BIT DEFINITION
0x4e00 Remote: PCRR internal error

0x6000 Success
0x6200 1
Remote: Echo: Wrong SRC
0x6400 Remote: Node: Wrong SRC
0x6800 1
Remote: Echo: Wrong DST
0x6a00 Remote: Node: Wrong DST
0x6c00 Remote: Node: Invalid response
0x0180 IOIC board not in control
0x0190 Q-line DIOB volts bad
0x00a0 Illegal access type
0x00b0 Illegal hardware address
0x00c0 Point not scanned yet
0x00d0 I/O cycle hung
0x00e0 Remote I/O type unknown
0x01f0 Third-party I/O Driver Error (for example, invalid GE Mark V/VI tables)
0x6010 Error checking for SOE Events
0x6020 Readback failed or Card OK Bit not set
0x6130 DIOB test failed
1
Consider updating PCRR (3A99190G01) Board to Revision 14 (per DEO 57211).
Note: Bit 0x8000 could also be set in any of these codes.
Local I/O statuses indicate a problem in the local R-Line I/O bus. For local I/O, the problem is
between the PCRL and the module. For remote I/O, the problem is between the remote node
Controller and the module.
Remote I/O statuses indicate a problem in the remote R-Line I/O bus. The problem is between the
PCRR and the remote node Controller.
OW350_R1007 85
4.3.7 To use the Choose Columns dialog box at the Operator Station
The Choose Columns dialog box allows you to select what information you want to display in the
Error Log window. Use the following procedure to select the desired columns:
1. Access the Error Log window (see page 78).

2. Select the View drop-down menu and pick Select Columns. The Choose Columns window
appears.
Figure 22: Choose Columns dialog box
3. Select the desired columns and select the OK button. The columns that you have checked
now appear in the Error Log window.
4.3.8 Priority levels of Error Log messages at the Operator Station
Error Log messages have eight different priority levels:

 0 - Emergency Condition/Severe Error
 1 - Alert Message
 2 - Critical Situation
 3 - Errors
 4 - Warnings
 5 - Normal but Significant Condition
 6 - Informational Messages
 7 - Debug Messages
These priority levels are defined during program development and are permanently fixed. The
most severe message level is 0 and the least severe message level is 7.
The Select Priority Level dialog box allows you to select the least severe priority level of the error
messages that you want to display in the Error Log window.
86 OW350_R1007
4.3.9 To use the Select Priority Level dialog box at the Operator Station
1. Access the Error Log window.
2. Select the View drop-down menu and pick Priority Level. The Select Priority Level dialog
box appears.
Figure 23: Error Log Select Priority Level dialog box
3. Select the base priority level of the error messages that you want to appear in the Error Log
window and select OK. All messages containing that priority level and any priority levels
above that level will appear in the Error Log window.
For example, if you select level 3, all messages with priority levels 3, 2, 1, or 0 display in the
window.
4.3.10 To print Error Log messages at the Operator Station
You can print the Error Log message information that appears in the Error Log window. There are
various print methods you can use:
1. Access the Error Log window (see page 78).

2. Select the File pull-down menu:
 Select Print and the standard Windows Print window opens. Make the desired choices
and print the messages.
 Select Print Preview and the standard Windows Print Preview window opens. This
provides a preview of how the printed messages will appear. Select Close to close the
Print Preview window and return to the Error Log window or proceed with the desired
printing.
 Select Print Setup and the standard Windows Page Setup window opens. This provides
the opportunity to modify how the printed messages will look on the page. If the page
layout is satisfactory, proceed with the printing.
3. You can also select the Print icon from the Error Log toolbar. The standard Windows Print
window opens. Make the desired choices and print the messages.
OW350_R1007 87
4.4 User profile options for Windows domains
4.4 User profile options for Window s domains
Local profile (used prior to Ovation 2.4)

 Profile settings stored on and used only on local machine
 Requires customizing desktop and user environment for each user on each HMI
 Default profile implementation
Roaming profile (see page 88) (Ovation 2.4 and above)
 Profile settings are stored on central server and are applied to whichever computer on the
domain where user logs on
 Profile settings are subsequently updated on central server when user logs off
 Useful when individualized user accounts are used and generally not “locked down”
 Can get messy otherwise, improper login / logoff sequence will result in profile changes being
overwritten
Mandatory profile (see page 88) (Ovation 2.4 and above)
 Profile settings are stored on central server and are applied to whichever computer on the
domain where user logs on
 Profile settings are never updated
 Implicitly a roaming profile
 Useful for both individualized and general-use login accounts
4.4.1 To Implement Roaming Profiles
Create and configure user accounts in Ovation Security Manager:
1. Log in to Domain Controller as Administrator-level user.

2. Make sure Show Hidden Files and Folders is enabled in Windows Explorer.
3. Create and configure a Profile directory:
 Create a C:\Profiles directory on the Domain Controller.
 Share the new directory as Profiles.
 Configure share caching for …will not be available offline.
 Create a folder underneath named to match each user account .
 Configure Share and NTFS Security permissions appropriately.
4. Open Start -> Administrative Tools -> Active Directory Users and Computers:
 Go to <DOMAIN_NAME> -> Ovation -> Global User Policies (find the account name in
folders underneath, and open.)
 Select the Profile tab, and enter \\<DOMAIN_CONTROLLER>\Profiles\%USERNAME%
in the Profile Path.
88 OW350_R1007
4.5 Ovation AntiVirus Upkeep
4.4.2 To Implement Mandatory Profiles

1. Follow steps in To Implement Roaming Profiles (see page 88).
2. Login as user account on any HMI and customize desktop environment and settings.
3. On Domain Controller:
 Rename C:\Profiles\%USERNAME%\ntuser.dat to ntuser.man.
 Secure NTFS security permissions on C:\Profiles\%USERNAME% appropriately.
4.5 Ovation AntiVirus Upkeep
Confirm appropriate group (“wave”) assignment, based upon HMI function/role.

 Lower-numbered groups get newest definitions first.
Check Ovation AV Management Station to verify proper client scan and definition update
activities.
 Can use integrated reporting capabilities.
Update definitions as they become available.
 Emerson-validated definitions typically made available on the user website every Wednesday.
 Update definitions by first deleting contents of c:\InetPub\wwwroot\virusdefs, then extracting
contents of downloaded compressed file into this directory.
 Periodically review the Ovation AntiVirus Report Server for reports for health and status of
client HMIs.
Figure 24: Ovation AntiVirus Upkeep
OW350_R1007 89
4.6 Switch and Router Configuration and Internet Operating System (IOS)
4.5.1 Kaspersky troubleshooting tools
Undiagnosed problems with antivirus software can leave your system vulnerable to virus attacks.
Having the proper tools to diagnose and fix problems early will save time and money. With the
Kaspersky antivirus software and technical support site, several utilities can be accessed to help
with maintenance and troubleshooting.
 GetSystemInfo.
 Kaspersky Lab Remote Diagnostic Utility.
 Trace file generation.
 Kaspersky Rescue CD.
 Kaspersky Virus Removal Tool.
 RipRep System Preparation Utility.
 Kaspersky Backup and Restore Utility.
Note: Refer to Using Kaspersky antivirus software with Ovation (CON_038) for detailed
information on using these tools. More detailed information can be found in the Kaspersky Lab
articles that pertain to the tool. Contact Kaspersky Lab Technical Support for questions that are
not addressed in the articles.
4.6 Sw itch and Router Configuration and Internet Operating S ystem

(IOS)
The following recommendations apply to network standards and security concerns:

 When working with third party I/O over Ethernet, Emerson recommends the use of secure
Field LAN router and switch implementations, rather than connecting directly to Ovation
switches, controllers’ or HMIs’ NICs.
 When working with connectivity products, Emerson recommends the use of secure DMZ
router and switch implementations, rather than dual-homing an Ovation HMI, connectivity
server, etc. to both Ovation highway and customer’s enterprise LAN.
Always make sure that the switch configuration revision matches IOS (Internet Operating
System).
 Older IOSes may not recognize commands and configuration parameters used by newer
switch configurations and can thus drastically change behavior of the network.
Advantages of newer switch IOSes and configuration files.
 Storm control on non-uplink ports.
 Greater port flap control and recovery.
 Greater security.
 Greater fault tolerance to network problems, user error, cabling problems, and so forth.
90 OW350_R1007
4.7 Technical tips and best practices
4.6.1 Troubleshooting Routed Network problems
Troubleshooting connectivity problems in a routed network can be intimidating. If a device on

network A (one side of the router) cannot communicate with a device on network B (the other side
of the router) the following basic steps are suggested:
1. From the router, ping the IP address of the network A device. If this does not work, check
network connections, IP address and subnet mask assignment of the network A device
adapters.
2. From the router, ping the IP address of the network B device. If this does not work check
network connections, IP address and subnet mask assignment of the network B device
adapters.
3. From the network A device, ping the IP address of the network B interface of the router. If
there is no response, check to make sure the network A device has a default or static route
configured (this can normally be done via the "netstat -rn" command). If Steps 1 and 2 are
successful, and Step 3 fails, it is probable that the default/static route was not properly added
to the network A device.
4. From the network B device, ping the IP address of the network A interface of the router. If
there is no response, check to make sure the network B device has a default or static route
configured. If Steps 1, 2, and 3 are successful, and Step 4 fails, it is probable that the
default/static route was not properly added to the network B device.
The following sections discuss system best practices.
4.7.1 System Offline Mode
WARNING! Make sure that all plant processes and procedures are followed prior to setting the
Offline Mode.
 Setting the System Offline mode enables the ability to move points between originating drops
through drag and drop.
 Any drop-dependent configuration (that is: hardware associations and control sheet
origination) must be broken prior to moving.
 Requires clearing/reloading original originating drop, as well as any drops receiving points
being moved.
 Allows for the changing of point broadcast frequency.
 Requires clearing/reloading originating drop.
 Enables the ability to move control sheets between task areas of the same Controller through
drag and drop.
 Requires clearing/reloading originating drop.
 System is flagged in Developer Studio to indicate Offline Mode.
 Should be kept in Online Mode except when there are changes that require other modes
to perform.
OW350_R1007 91
4.7.2 Setting the Online/Offline mode
Setting the Online/Offline Mode function permits engineering changes in an Offline Mode of
operation. This may be useful when testing a change that you do not want to take effect
immediately in the online (operational) system. The Offline Mode permits the changes of an
Ovation point’s originator or broadcast frequency and the movement of a control sheet between
control areas under certain conditions, and enforces the clear/load sequence for affected Ovation
drops.
Offline mode is enabled through the checkbox attribute on the System folder. This attribute is
labeled Offline Mode and has an import/export reference of OFFLINE_MODE. By default, this
attribute is not enabled (that is, by default, operation of the Ovation Engineering Tools restricts
you from making changes, which disrupt the system).
4.7.3 Enabled Offline mode attributes
Enabling the Offline Mode attribute causes the following to occur:
1. A dynamic status entry is created in the Ovation database that identifies the system as being
in Offline mode. This causes the red flag to show next to the System folder in the Developer
Studio.
2. A message is logged in the Ovation Error Log (on the Ovation Database Server) indicating
that the system has been placed into Offline mode.
3. The moving of Ovation points (with restrictions), the moving of a control sheet between
control areas of the same Ovation Controller, and the changing of an Ovation point’s
broadcast frequency are enabled.
4.7.4 Disabled Offline mode attributes
Disabling the Offline Mode attribute causes the following to occur:
1. The dynamic status entry for the Systems folder is removed from the Ovation database. This
causes the red flag to disappear from the Systems folder in the Developer Studio.
2. A message is logged in the Ovation Error Log (on the Ovation Database Server) indicating
that the system is no longer in Offline mode.
3. The changing of an Ovation point’s broadcast frequency and the moving of Ovation points
and control sheets are all disabled.
92 OW350_R1007
4.7.5 Fragmentation of a Hard Disk Drive (HDD)
Fragmentation
When Windows is writing a file to the disk, it looks for a suitable piece of free space in which to
store it.
What happens, then, when you copy a 40M database or file to the disk and the biggest slice of
free space is only 30M? Alternatively, if you modify an existing file, appending data so the file now
takes up more space on the disk. To accommodate the files, Windows writes the first part of the
file in one section of the disk and then searches for other places to store the rest of the file. The
end result is that a single file may be stored in several chunks scattered about the disk.
The system would then keep a record of where the different parts of the file are stored, this is
achieved through the use of a File Allocation Table (FAT) or similar file system such as NTFS.
Then, when the operating system requires the file again, it will query the file system
(FAT/NTFS/or other) to find out where the different parts of the file are located on the partition
(drive).
Over time, as you create and then delete documents or un-install programs, once-filled locations
are left empty and you end up with files dotted all over the disk.
Defragmentation
Defragmentation is the term given to the process of scanning the file system and rejoining the
split files back into consecutive pieces. The process of defragmenting can be time consuming, but
it is one of the easiest ways to increase the performance of your PC. The frequency of which a
PC should be defragmented will directly depend on the amount of usage.
OW350_R1007 93
4.7.6 To Defragment a hard disk
Note: Since there should be very little adding and deleting programs or large files on an Ovation
drop, defragmentation should only be used when it is noticed that the performance of your PC is
noticeable decreased.
1. Make sure you have enough time to complete the defragmentation, the amount of time will
depend on how much use your PC has had since the last defragmentation.
2. Close all programs; e-mail, communications programs, virus scanners, or any other
applications that periodically access the hard drive will force the defrag process to start over.
CAUTION! It is important to close all programs when optimizing your system. Check your
system tray on your desktop's Start menu bar and close all programs other than those
essential to running Windows. Some programs require you to open the Close Program dialog
box (press Ctrl-Alt-Del once).
3. Click Start, then Programs, then Accessories, then System Tools, and then Disk
Defragmenter.
4. The next step is to highlight the drive you wish to defragment (one left click on the drive), then
click on the Analyze button, this will check the selected drive for fragmentation, the utility will
then tell you whether the drive needs defragmenting or not.
5. If the drive needs defragmenting simply click the Defragment button, once clicked the utility
will begin defragmentation of the drive, it may take a few hours depending on the size of the
drive.
6. Once it is complete, simply close the defrag utility.
4.7.7 Checking NTP synchronization issues

 Determining Network Time Protocol (NTP) client/server time offsets
 Run “w32tm /stripchart /computer:<HOSTNAME_OR_IP_ADDRESS> /samples:5
/dataonly” from command prompt
 For Ovation 2.4 – 3.1
 Run “ntpq” from command prompt and run “peers” command
 For Ovation 2.0 – 2.3
 If HMIs, controllers, switches and/or routers not synchronizing
 Verify that
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalC
lockDispersion is set to 0 on both client and server (where appropriate)
 Restart “Windows Time” service
4.7.8 Network Time Protocol (NTP) (Networks folder)
Network Time Protocol (NTP) identifies the drop or external server that is providing the time base
for the Ovation system. NTP is automatically created when a Network is inserted.
94 OW350_R1007
4.7.9 Backing up the operating system and Ovation software
WARNING! Restoration of the database should only be performed by qualified personnel.
 Required media and files:

 Operating System and Service Pack CD (if applicable).
 Have applicable Microsoft Product Key Code available (typically found on sticker on
the PC).
 Required drivers for networking, video, audio, and so forth.
 More of a concern for the older OSs (NT and W2K).
Note: Adaptec, Znyx and OHI network drivers are on Ovation CD.
 Microsoft Security Patches CD.

 Ovation CD set.
Note: Make sure the server is connected to the network before loading Ovation.
 Ovation packages (if applicable).

 Complete System backup for database and system restore.
 Be prepared to obtain:
 New Ovation licensing (Locking code changes with reload).
 New AutoCAD licensing (pre-Ovation 3.1.x).
Note: Ovation supports optional Disk Imaging Backup Software by Acronis. For more
information, refer to: Ovation Backup and Restore User Guide.
4.7.10 Backing up the database files
Note: These programs may be used for backing up the database, but the recommended
system backup procedures are described in the Ovation installation instructions (See Ovation
Software Installation Manual.)
There are two programs available for backing up the database:

 Oracle export program (exp (see page 96)).
This tool saves the entire database, all of the structure, and all of the content; alternately, it
can also be used to save selected portions. Existing point SIDs and network addressing
assignments are retained. Following a restoration, the state of the database (structure and
contents) is exactly what it was when the export was taken.
This tool should be used to back up the database so that it could be completely restored in
case there is a system disruption, such as disk crash or operating system reload.
This type of backup is generally not portable from one Ovation job to the next. It should not be
used to copy a database between a Master Database and an External Database.
For more information on the use of the Oracle export program, refer to the Oracle
documentation that was supplied with your system.
OW350_R1007 95
 Ovation Export program (OvPtExport).

This tool saves all of the database configuration and point information into an ASCII file. None
of the database structure is saved.
This tool should be used when an Ovation software upgrade of the server requires a
complete reload of that drop.
If necessary, the database schema is changed during a software upgrade procedure and no
restore operations are needed.
However, if for any reason the Database Server is completely reloaded, the database must be
populated with the export file, re-execution of Control Builder scripts (to load control sheet
information into the database), and a re-import of all the custom diagrams.
4.7.11 To backup the complete database

1. Export the contents of the Oracle database with the following command:
exp USERID=’/ as sysdba’ FILE=<exportfile> FULL=Y
COMPRESS=N LOG=<logfile>
where:
<exportfile> = User-defined filename for the backup file. This will create a file
named <exportfile>.
<logfile> = User-defined filename for the log file. This will create a file named
<logfile>.
2. Compress the file using any of the various compress programs available on Windows (such
as WinZip or another third-party package may be used). See applicable operating system
documentation.
3. Save the backup file using some type of backup medium (tape, CD, and so forth). See
applicable operating system documentation.
4.7.12 To backup the database files
Use the following procedure to perform a backup:
1. Start the Backup/Restore program by going to its location on the “C” drive and double-clicking
C:\Ovation\OvationBase\OvPtBackup.exe. The Ovation Backup/Restore window opens.
2. Press the Backup Now button. The program backs up the files to the defined directory. A
screen shows the progress of the backup as well as an approximate time for each process.
Note: The program will backup and verify the files.
96 OW350_R1007
4.7.13 To backup the partial database

1. Run the OvPtExport program:
OvPtExport -u ptadmin@ptdb -o <exportfile>
where:
<exportfile> = User-defined filename for the backup file. This will create a file
named <exportfile>.
2. Compress the file using any of the various compress programs available on Windows (such
as WinZip or another third-party package may be used). See applicable operating system
documentation.
3. Save the backup file using some type of backup medium (tape, CD, and so forth). See
applicable operating system documentation.
4.7.14 To restore a complete database
Use the following procedure to restore the complete database (including structure) from the
backup that was created (see page 96). An example of when this would be necessary includes
recovery from a catastrophic failure (such as a hard disk failure).
1. If the Software Server functions must be restored, refer to the Ovation software installation
instructions. (See Ovation Software Installation Manual.) Procedures are dependent on
individual systems and cannot all be described in this manual.
2. Insert the database backup tape/CD into the appropriate drive.
3. Uncompress the tape/CD.
4. Enter the following batch command to restore the backup (it can be executed from any
directory):
do_ptadmin_import.bat <exportfile>
OR
do_ptadmin_import.bat <exportfile> AUDIT

to include audit information from the backup file.
5. Remove the backup file from the system to conserve space.
6. Reboot the Database Server drop.
7. Using the Ovation Developer Studio, import custom graphic files and Control Builder sheets.
(See Ovation Graphics Builder User Guide and Ovation Control Builder User Guide.)
Note: After restoring the database, the password for the ptadmin and SCADA Oracle users (and
the ptaudit Oracle user if they used the AUDIT option during import) will be reset to the release
default values. If you had previously modified these Oracle user passwords from the release
defaults, they need to be changed again (or at least reset to some other value) in order to
operate the Ovation Engineering Tools (for example, Ovation Developer Studio). You can
perform this operation by executing the Ovation Security Manager application
(OvSecManUI.exe), found in the \Ovation\Security folder.
OW350_R1007 97
4.7.15 To restore a partial database
Use the following procedure to restore the partial database (none of the structure) from the
backup that was created (see page 96).
1. If the Software Server functions must be restored, refer to the Ovation software installation
instructions. (See Ovation Software Installation Manual.) Procedures are dependent on
individual systems and cannot all be described in this manual.
2. Run the import program:
OvPtImport -u ptadmin@ptdb -f <exportfile>
3. Restore the custom graphic files and Control Builder sheets via the Import function on the
Ovation Developer Studio. (See Ovation Graphics Builder User Guide and Ovation Control
Builder User Guide.)
4. Clear and reload each drop in the system with the Load function. A clear and reload of each
drop in the system is required when the -f option is used in the import operation (see Step 2).
If the -f option is not used, simply reload each drop. (See Ovation Developer Studio User
Guide.)
4.7.16 To backup your domain controller
Backup of Active Directory Domain Services (AD DS) must be incorporated into your day-to-day
operations schedule. The recommended practice is that at least two domain controllers, the
Primary Domain Controller and a Redundant Domain Controller, be included in the routine
scheduled backup.
Windows Server backup (wbadmin) tool supports three types of backup:

 System state, which includes all the files that are required to recover Active Directory. The
system state backup includes at least the following data:
 Registry data.
 Boot files.
 Active Directory database and log files.
 SYSVOL directory.
 Critical operating system files.
 Critical-volumes, which includes all the volumes that contain system state files. The critical-
volumes backup includes all the data that resides on the following volume:
 The volume that hosts the boot files.
 The volume that hosts the operating system and registry.
 The volume that hosts the SYSVOL directory.
 The volume that hosts the Active Directory database and log files.
 Full server, which includes all the volumes on the machine, including the USB drives.
Windows Server backup (wbadmin) tool consists of two components:
 Wbadmin.msc, a graphical user interface (GUI) tool that can be used to perform critical-
volumes and full server backups. System state backups are not supported by this tool.
 Wbadmin.exe, a command-line tool that can be used to perform all types of backups,
including the system state backups.
98 OW350_R1007
You can schedule the critical-volumes and full server backups by using the wbadmin.msc or
wbadmin.exe tool. You cannot schedule system state backups by using the wbadim.exe tool,
but you can create a task to run a system state backup by using the Task Scheduler.
CAUTION! Do not use unapproved third-party imaging software to backup domain controllers.
Refer to: Backup and Recovery software installation. The Active Directory database on a
domain controller will not be able to recover properly if it is restored using any imaging
software, and may result in a condition known as USN rollbacks. When USN rollback occurs, a
restored domain controller will not be able to receive replication updates from other domain
controllers and may become out-of-sync permanently.
When objects are deleted in the Active Directory database, they are not immediately removed.
Instead, they are moved to a special folder called Deleted objects and marked as tomb stoned.
The tombstone state indicates that the object has been deleted but not removed from the
database. The amount of time that the deleted objects will be in this state before it is permanently
purged from the database is called the tombstone lifetime.
The primary requirement for recovering Active Directory from the backup is that the backup must
not be older than the tombstone lifetime, which is the number of days the Active Directory
preserves knowledge of deleted objects.
If the first domain controller (Primary Domain Controller) is created with Windows Server 2008 R2
SP1, the default tombstone lifetime is 60 days. If the Primary Domain Controller is created with
Windows Server 2008 or Windows Server 2008 R2 SP1, the default tombstone lifetime is 180
days.
To ensure proper recovery of Active Directory, it is important to understand that backups older
than the tombstone lifetime should never be used.
It is recommended that you include in your day-to-day operations schedule to identify the backups
that are older than the tombstone lifetime and delete them from the backup set.
The frequency at which backup should be performed depends on your Active Directory
environment. In general, during the Ovation security configuration phase, a large amount of
changes occur to the Active Directory database; and Emerson recommends that you create
backups daily.
During the normal operation phase, only minimal changes occur to the Active Directory database;
therefore, Emerson recommends that you create backups at least weekly.
Apart from manual changes, some automatic changes occur to the Active Directory database at
regular intervals. For example, computer accounts, including domain controller accounts, change
their passwords every 30 days by default. Also, user account passwords can change at regular
intervals depending on password policies. Rolling back these password changes to a former state
affects authentication and replication. Generally, no external record of these changes exists
outside the Active Directory database. Therefore, the more frequently you back up the domain
controllers, the fewer problems you will encounter if you need to recover from a failure.
OW350_R1007 99
4.7.17 Media, patch, and license management

 Software Licensing Binder
 Maintain up-to-date software CDs that reflect appropriate versions of software installed on
your system.
 Emerson-provided software media.
 Third party software media (OS, Dell driver CDs, pcAnywhere, and so forth.)
 Maintain software patch CDs that reflect any patches applied to your system.
 Track which patches are applied on your system.
 Verify that you have CDs for patches (for HMI reload contingencies).
 Licensing certificates and license keys.
 Patch Management
 Minimal patch approach is recommended.
 Do not install Ovation patches for software or features that are not being used.
 Track Emerson-issued patches being applied to your system.
 Only apply OS patches, service packs and hotfixes that have been validated to work with
Emerson software.
 Base OS patches provided by Emerson Software Licensing on CD.
 Additional OS patches tested by Emerson are listed at Users’ Group website
(www.ovationusers.com).
100 OW350_R1007
4.7.18 To access the License Manager

1. Access the Developer Studio.
2. Use the system tree to navigate to the Systems folder.
3. Right-click the Licenses folder.
4. Select Insert New from the menu. The Insert New License Wizard appears.
5. Select Finish. A new License icon appears in the WorkPad Window.
6. Right-click Licensing from the WorkPad window. Select Open. The License Manager dialog
box appears.
Figure 25: License Manager window
OW350_R1007 101
S E C T I O N 5
5 Diagnostic tools and troubleshooting
IN THIS SECTION
Ovation diagnostic services ............................................................................................ 103

Ovation system diagnostics tools .................................................................................... 105
Controller Diagnostics tool .............................................................................................. 105
What is the Control Logic Navigator utility? .................................................................... 123
Engineering Tools Audit .................................................................................................. 124
System Diagnostic algorithms ......................................................................................... 142
Status Information Diagrams ........................................................................................... 151
Non-Ovation diagnostics tools ........................................................................................ 151
SIS operations and maintenance practices .................................................................... 157
Resolving common installation problems ........................................................................ 168
What are the processor module status LEDs for the Controller? ................................... 174
What are the I/O Interface module status LEDs for the Controller? ............................... 176
Troubleshooting Routed Network problems .................................................................... 178
I/O module troubleshooting ............................................................................................. 178
Bus interface modules ..................................................................................................... 222
Distributed Component Object Model (DCOM) system .................................................. 259
Optimization package troubleshooting information (Linux OS) ....................................... 260
5.1 Ovation diagnostic services
Ovation provides the following diagnostics services:
1. Field engineering services (see page 104)

2. SureService Customer Support Programs (see page 104)
OW350_R1007 103
5.1 Ovation diagnostic services
5.1.1 Field engineering services
Emerson field engineers are process management experts that travel to customer plants to
perform the following services:
 Project design and management.
 Installation and startup of system software and hardware.
 Routine maintenance.
 System tuning.
 Troubleshooting system problems.
The support resources available to the field engineers are:
 Test bed facilities.
 Remote diagnostic facilities.
 Internet-support tools.
 Extensive troubleshooting database.
 Over 100 hours of training per year.
 Support from regional offices, other field engineers, and design engineers.
5.1.2 SureService Customer Support Programs
SureService customer support programs by Emerson enable utilities to customize the right
maintenance package for the unique needs of the power generation and water/wastewater
treatment industries.
SureService modules
1. Expert Telephone Support

2. Remote System Diagnostics
3. Emergency On-Site Service
4. Scheduled On-site Service
5. Internet Information Access
6. Software Update Program
7. Component Coverage
8. Classic System Component Support
9. Software Archiving
10. Software Updating
11. Online Tutoring
12. Application Enrichment
13. Training Programs
14. SmartProcess Optimization Service
104 OW350_R1007
5.2 Ovation system diagnostics tools
SureService Support Methodology
Emerson is committed to the quality of SureService. Our customer service methodology is

designed to enable customers to reach their set maintenance objectives. Emerson partners with
our customers to ensure top-quality support and customer satisfaction. A SureService contract
controls plant maintenance costs by bundling various modules into one fixed contract price.
Select modules à la carte or bundle multiple modules together to take advantage of maximum
savings.
5.2 Ovation s ystem diagnostics tools
Maintenance of the Ovation® system is kept to a minimum by built-in fault tolerance and
diagnostics that are provided through:
 Illuminated colored status indicators on system components.
 An audible alarming system.
 Status graphics readily available to the system operator.
 Fault Code information can be obtained from the Ovation System viewer application. Please
refer to Ovation Operator Station User Guide.
When a component fails, a local red LED in the component module will illuminate while
simultaneously sending a message to the alarm management system at the system workstations.
If the audible function is chosen by the operator to be implemented in their system, a sound will
occur when a certain level alarm has been reached. The failed component will be shown in the
alarm list as well as shown on the system status display. The system provides continuous checks
for bad sensors and process point values that exceed their alarm limits.
5.3 Controller Diagnostics tool
The Controller Diagnostics function is a diagnostic tool that displays information about the
Controller. You can select the Controller that you want to query from a drop hierarchy tree or from
a dialog box. The information about the selected Controller appears in a user-friendly Controller
Diagnostics window (see page 107). You can use the Controller Diagnostics window to perform
the following functions on the selected Controller:
 Select and display information about that Controller (see page 109).
 Update data in a backup Controller to match the data in the primary Controller (see page
112).
 Display information about the control tasks for that Controller (see page 114).
 Display information about I/O modules that interface to the selected Controller (see page
116).
 Download firmware to intelligent I/O modules that interface to the selected Controller (see
page 118).
The Controller Diagnostics tool has an online help system that provides information on the
Controller Diagnostics application. You can access this help in the following ways:
 By pulling down the Help menu on the main Controller Diagnostics window.
 By pressing the F1 key on the keyboard while the cursor is located in one of the Controller
Diagnostics window tabs or in one of the window sections (Controller List or Controller
Overview).
OW350_R1007 105
5.3.1 Software platforms that Controller Diagnostics supports
The Controller Diagnostics function is designed to run on both Windows-based and Solaris-based
Ovation systems. In general, functionality remains the same for both platforms. However, where
differences exist between the platforms, information is specifically labeled "for Window-based
systems" or "for Solaris-based systems." The Controller Diagnostics Tool is applicable to Ovation
OCR400 and OCR1100 Controllers.
Note: Where functionality is the same for both platforms, this document uses Windows-based
graphics.
To access the Controller Diagnostics tool in a Windows-based Ovation system

1. From an Ovation workstation select Start > Ovation > Ovation Utilities > Diagnostics.
The Controller Diagnostics window appears.
Figure 26: Controller Diagnostics window
To access the Controller Diagnostics tool in a Solaris-based Ovation system

1. Log in to the Engineering Station.
2. Select Drop Functions from the top-level Engineering Station menu. The Drop Functions
menu appears.
3. Select Controller from the Drop Functions menu. The Controller menu appears.
4. Select Controller Diagnostics from the Controller menu. The Controller Diagnostics window
appears.
106 OW350_R1007
5.3.2 Controller Diagnostics window
After you have accessed the Controller Diagnostics window, you can use it to diagnose all the
Controllers in a network.
The Controller Diagnostics window contains a menu bar and a toolbar (see page 108).
The left portion of the Controller Diagnostics window contains a Controller Overview section (see
page 111) that provides internal information about the selected Controller. This section also
contains an Update Backup button (see page 112) that can update the data in a backup
Controller to match the data in the primary Controller.
Below the Controller Overview is the Controller List (see page 109) that displays all the
Controllers in the Ovation system. Select a Controller from the list and information about that
Controller appears in the Controller Overview section and in the window tabs.
The Controller Diagnostics window contains five tabs that provide different types of information
about a Primary Controller and its Partner Controller:
 Use the Control Task Information tab (see page 114) to display information about the control
tasks for a selected Controller.
 Use the I/O Information tab to display information about I/O modules that interface to the
selected Controller and to download firmware to the modules.
 Use the Software Versions tab (see page 119) to identify the software version of each
software package that is installed on the selected Controller.
 Use the Point Details tab (see page 120) to list the points originated and received by the
selected Controller.
 Use the Sheet Information tab (see page 121) to provide information about the elements on
control sheets for the selected Controller.
Figure 27: Controller Diagnostics window
OW350_R1007 107
Controller Diagnostics menu bar
The Controller Diagnostics window contains a menu bar that provides three drop-down menus:
Figure 28: Controller Diagnostics menu bar
Controller Diagnostics menus
MENU DESCRIPTION
File  Select a Controller - Displays the Select a Controller window (see page 109).
 Exit - Closes the Controller Diagnostics window.
View Contains a list of window components that you can check or uncheck to display or close:
 Controller List
 I/O Module
 Algorithm Point List
 Algorithm Template
You can also refresh the window from this menu.
Help  Contents and Index - Displays the online Help.
 What's This - Click this and select a window component. This displays a description of the
selected component.
 About Controller Diagnostics - Displays the version number of the software.
Controller Diagnostics toolbar
The Controller Diagnostics window provides a toolbar. Drag the mouse over the toolbar icons to
identify each icon.
Figure 29: Controller Diagnostics toolbar
The toolbar icons (left to right) perform the following functions:

 The window icon displays the Select a Controller window (see page 109).
 The arrow icon refreshes the information in the Controller Diagnostics window with current
data.
 The book icon displays the online product Help in a Content and Index format.
 The question mark can be used to click and select a window component. This displays a
description of the selected component.
108 OW350_R1007
5.3.3 Controller List in the Controller Diagnostics window
All the Controllers in your network are listed in a hierarchal tree that begins with the network and
ends with the Controller drops. This Controller List appears beneath the Controller Overview
information panel. An example is shown in the following figure:
 Network = FE221
 Unit = UNIT0
 Controller drops = DROP11/DROP61
Figure 30: Controller List
Select the Controller whose information you want to display. Double-click the desired Controller
and the data for the first Controller listed in a redundant pair displays (Drop11 in the preceding
figure). Right-click the desired Controller and a menu appears listing the names of the redundant
Controllers so you can select the desired Controller.
Note: You can also select a Controller from the File menu or in the toolbar.
OW350_R1007 109
5.3.4 To select a Controller in the Controller Diagnostics window

1. Access the Controller Diagnostic window, select Start > Ovation > Ovation Utilities >
Diagnostics.
2. Select a Controller from the system tree in the Controller List (see page 109) window
(located beneath the Controller Overview panel).
OR
3. Select the Select a Controller item from the File menu or from the toolbar. A pop-up window
appears. Enter a Controller name or IP address in the pop-up window. Information about that
Controller now appears in the Controller Diagnostics window.
Figure 31: Select a Controller Drop dialog box
110 OW350_R1007
5.3.5 Controller Overview panel in the Controller Diagnostics window
The left panel of the Controller Diagnostics window provides internal information about the
Controller you have selected and the associated Partner Controller. This information applies to
OCR400 and OCR1100 Controllers and appears along with each tab that you select.
Figure 32: Controller Overview panel
OW350_R1007 111
Fields in Controller Overview panel (Primary and Partner Controllers)
FIELD FIELD DESCRIPTION
Drop Name Drop number for the Controller drop that you highlight in the Select a Controller
Drop section of the Controller Diagnostics window. Right-click the drop name to
display the Point Menu for the Drop Point (DU record).
IP Address Internet Protocol (IP) address for the selected Controller drop.
Ethernet Address Unique hardware address for each Ethernet port for the selected Controller drop.
Controller Type Displays the type of Ovation Controller:

 OCR1100
 OCR400
Processor Unique hardware CPU type for the selected Controller drop (for example,
Pentium).
Mode Displays the mode of the Controller:
 Control
 Backup
Fault ID Displays the Fault Code number (66) if the Controller is in fault, or 0 if the
Controller is not in fault.
OS Version Version of the Operating System running on the selected Controller.
Kernel Version Version of the internal Ovation Controller software.
Controller Version Version of the Ovation Controller software.
Total Ram Total amount of memory available in the Controller's RAM disk (kbytes).
Sheet Count Number of Control Builder sheets processed by the selected Controller.
Originated Points Number of originated points in the Controller.
Received Points Number of received points in the Controller.
Update Backup Updates data in the backup Controller to match data in the primary Controller.
button (see page
112)
112 OW350_R1007
5.3.6 Controller Diagnostics Update Backup function
You can use the Update Backup function when a Drop Load function for a Controller has failed
and you have to clear and reload the Controller. This puts the Controller into backup, but since it
has been cleared, a mismatch may now exist between this backup Controller and the primary
Controller.
Note: You can use the Drop Details diagram to determine if a mismatch exists for your
Controller.
After determining the cause of the failure (by analyzing the messages and fault codes) and
correcting the problem, you can reconcile the mismatch smoothly (without “bumps”) by using the
Update Backup function (see page 113).
For Ovation 3.5 and later software releases, fault code information is part of Ovation software and
is displayed on the Ovation System Viewer application. Refer to the Ovation Operator Station
User Guide for additional information of the System Viewer.
5.3.7 To update your backup Controller in the Controller Diagnostics window

1. Access the Controller Diagnostics window, select Start > Ovation > Ovation Utilities >
Diagnostics
2. Select the backup Controller that you want to update. The drop name of the backup
Controller appears at the top of the Controller Overview section of the window.
3. Select the Update Backup button. The data is loaded from the Controller that is “in control” to
the backup Controller.
4. A Diagnostics window appears displaying the number of points that updated and advises you
to reboot the Controller. If you want this drop to become the drop in control you must reboot
the Controller that is in control through the Developer Studio:
5. Use the system tree to navigate to the Drops folder:
Systems > Networks > Units > Drops
a) Right-click the folder of the drop you want to reboot.
b) Select Reboot from the right-click pop-up menu. The right-click menu only displays items
that are applicable for that drop.
c) For non-redundant drops, skip to Step 7.
d) For redundant drops, the Select a drop to reboot dialog box appears.
 Select the drop you want to reboot.
 Select Ok.
6. A confirmation dialog box appears.
7. Select Yes to close the window and execute the reboot process.
OW350_R1007 113
5.3.8 Control Task Information tab in the Controller Diagnostics window
The Control Task Information tab provides information about the control tasks used by the
Controller. A control task (also known as a process task) is a specific Controller area where all the
control sheets in that area are scanned at the same frequency. You can define up to five control
tasks.
The control task rate is set during Controller configuration in the Developer Studio.
Control task 1 = 100 msec (0.1 second) Fast time
Control task 2 = 1000 msec (1 second) Slow time
Control tasks 3, 4, and 5 are user configurable and you should select scan rates that are
appropriate for your system applications.
Figure 33: Control Task Information tab
114 OW350_R1007
Control Task Information tab fields
FIELD DESCRIPTION
The following fields appear for each task Area (1 - 5).

There is also a total field that displays the sum of each memory type and the sum of each point type for all
five tasks.
Status Status of the task area.
Total Control Displays the total available space for a control task.
Memory
Used Control Displays the total actual space used for a control task.
Memory
Capacity of Percentage of memory that is used for a control task.
Memory
Configured Displays the execution time (in milliseconds) that is configured for a control task.
cycle Time
(msec)
Average cycle Displays the average execution time (in milliseconds) that is actually used for a control
Time (msec) task.
Worst cycle Displays the longest execution time (in milliseconds) that is actually used for a control
Time (msec) task.
Analog Input Total number of analog input points in the task area.
Points
Digital Input Total number of digital input points in the task area.
Points
Packed Input Total number of packed input points in the task area.
Points
Analog Output Total number of analog output points in the task area.
Points
Digital Output Total number of digital output points in the task area.
Points
Packed Output Total number of packed output points in the task area.
Points
Total I/O Total number of analog, digital, and packed points in the task area.
Points
OW350_R1007 115
5.3.9 I/O Information tab in the Controller Diagnostics window
The I/O Information tab provides information about the I/O modules that interface with the
selected Controller. You can select a Controller drop and the associated modules appear in the
I/O Information tab along with the descriptions of those modules.
Some intelligent modules contain firmware that can be updated. The Module Firmware Download
window describes what revision of the firmware the module contains (Module Version) as well as
the latest firmware that is available on the Controller (Controller Version) for the module. If there is
a difference between the Module Version and the Controller Version, you can select the
Download button to download the latest firmware to the module from the Controller.
You can also download older firmware, if desired. A warning message appears and you are
required to verify the choice to re-download.
WARNING! Downloading firmware to an I/O module may cause the module to reset, so
your plant must be in a safe condition or must be shut down for at least five minutes
during the download process.
I/O points for a module are undefined during the reset process (30 seconds or more).
Therefore, communications priority is lowered during the firmware download process,
and may cause communication failures with the AMS Device Manager and/or multi-
variable messaging.
Figure 34: I/O Information tab
116 OW350_R1007
I/O Information tab fields
FIELD DESCRIPTION
Module Type Type of I/O module that is selected.
EID Serial Serial number of I/O module that is selected. This number is a single 10-digit decimal
number number representing when and where the module was manufactured.
Address Device number and hardware address of module. For example, 1:4800 is device
number 1: hardware address 0x4800. Redundant modules are separated by a slash (/).
EID Index The index number provides a description of the types and revisions of the two cards
(Logic and Field) that make up an Ovation Electronics module. This number is a series
of eight decimal numbers (separated by dots) that identifies the type of module and the
revisions of the cards.
Download Button that accesses the Module Firmware Download window.
Available
Firmware
button
5.3.10 What firmware can be downloaded to the I/O modules through the
Controller Diagnostics window?
The firmware for certain I/O modules is provided on the Ovation release CD and is installed on
the Ovation Software Server during the Ovation software installation process (see Ovation
Software Installation Manual). The firmware is downloaded to the Controller when
Query/Download is used. This firmware might differ from the firmware that is currently on your I/O
module and you might want to download the latest available firmware to your module.
If the module you have selected is not the type of module that can be downloaded with firmware,
the Download Available Firmware button is not activated.
Examples of I/O modules that contain firmware are:

 HART
 High Side Digital Output
 Ovation I/O Profibus
 Ovation I/O Fieldbus
 Ovation I/O DeviceNet
variable messaging.
OW350_R1007 117
5.3.11 To download firmware revisions to the I/O modules through the Controller
Diagnostics window
If there is a difference between the latest available firmware and the firmware on your I/O module,
and you desire to update your I/O module, use the following procedure:
1. Access the Controller Diagnostics utility (see page 106) at an Ovation workstation.
2. Select the I/O Information tab (see page 116).
3. Select the Download Available Firmware button. The Module Firmware Download window
appears. Below is an example of a firmware download for an Ovation bus module.
Figure 35: Module Firmware Download window
4. Compare the firmware in the Controller Version field to the firmware in the Module Version
field to determine if you have the latest firmware on your I/O module.
5. If you do not have the latest firmware and you want to update the firmware, confirm that the
plant is in a safe condition before you perform the actual download.
variable messaging.
6. Highlight the files you want to download.

7. Select the Download button to load the latest firmware onto your I/O module.
8. If you need to reboot the selected I/O module (see page 119) after download, the Reboot
Module button is enabled.
118 OW350_R1007
5.3.12 To reboot an I/O module
If the selected I/O module is rebootable, the Reboot Module button will be enabled. To reboot the
module, select the Reboot Module button and confirm the request. If the module responds to the
request, a success message will be displayed.
The reboot function requires that the module be running the 312 patch version or later of
RFTP.out and contain the RESTART.SCR script. The Controller should be running the 312 patch
version or later of diagsrvr. Reboot request failures may indicate that the latest software is not
loaded or is not running (module was not power cycled after download).
5.3.13 Software Versions tab in the Controller Diagnostics window
The Software Versions tab identifies the software version of each software package that is
installed on the Controller. This information is useful during troubleshooting to determine if you
have the latest software.
Figure 36: Software Versions tab
OW350_R1007 119
5.3.14 Point Details tab in the Controller Diagnostics window
The Point Details tab lists the name and SID for the points originated and received by the
selected Controller. Right-click the SID or the name of a point, and the Point Menu for the
selected point appears. You can also right-click a point to access the Point Menu.
Figure 37: Point Details tab
Point Details tab fields
FIELD DESCRIPTION
Originated Points Lists the originated point names and system IDs (SID) in the selected
Controller.
Received Points Lists the received point names and system IDs (SID) in the selected Controller.
120 OW350_R1007
5.3.15 Sheet Information tab in the Controller Diagnostics window
The Sheet Information tab provides information for the selected Controller about the control tasks,
control sheets, algorithm points, and algorithms on the sheets. You can resize the columns and
also use the scroll bars to locate information.
Figure 38: Sheet Information tab
OW350_R1007 121
Sheet Information tab fields
FIELD DESCRIPTION
Hierarchy Tree Displays a Controller drop, associated control sheets, control tasks, and
algorithms.
Algorithm Point Information
Name Name of the selected algorithm. Right-click the name to display the Point Menu
for the algorithm point.
SID System ID of the selected algorithm.
Description Description, generated by the Control Builder, of the selected algorithm.
Value Value of the selected algorithm.
Type Record type of the algorithm point. Always LC.
Row Internal algorithm information.
Bit Internal algorithm information.
Algorithm Template Information
Name Name of the algorithm parameter.
Description Description of the algorithm parameter.

Record Type Input/output points of the algorithm. If this field is blank, there is no point.
Record Field Field in the algorithm point where information is stored.
Data Type Used internally by the Controller.
Flags Used internally by the Control Builder.
Default Default value set by the algorithm.
Min Minimum defined value of the input/output point.
Max Maximum defined value of the input/output point.
Enum Count The amount of enumerations an algorithm parameter can have. For example, if
a parameter can be ON or OFF (two choices), the Enum Count is two.
Right-click the Enum Count and the possible choices display.
First Bit First bit number in the record field; used to store enumerated information.
Bit Mask Internal use only.
5.3.16 Refresh function for the Controller Diagnostics window
Use the refresh function to refresh the Controller Diagnostics window with current data. There are
two refresh methods available:
 Select Refresh from the View menu.
 Select the Refresh icon from the toolbar.
122 OW350_R1007
5.4 What is the Control Logic Navigator utility?
5.4 What is the Control Logic Navigator utility?
The Control Logic Navigation tool searches the control sheets on one or more of the active
Controllers on the local network for a user-specified point.
Primarily, this tool is designed for troubleshooting control logic. In particular, it is designed to
troubleshoot the control logic in migrated WDPF control systems.
This tool allows you to query the control system for specific points in currently loaded control
sheets. The Control Logic Navigator tool searches all control sheets in selected drops and
displays control diagrams using the graphics display program.
A list of control sheets where a specified point is used appears. The drop number, sheet number,
and sheet description are displayed for each sheet in the list. You can expand each sheet in the
list to view a sublist of each instance where the point is used on that sheet.
For each instance, the algorithm name is displayed along with data specific to the algorithm. For
example, if the algorithm is a BOOLEANSOLVER, the named output is also displayed. If the
algorithm is a LADDERSOLVER, the parameter type and the parameter row and column are
displayed.
For all other algorithms, both the parameter pin name and the associated LC point are displayed.
Clicking on any list entry displays the associated control sheet in the active graphics window.
Where possible, the graphics program highlights the algorithm or algorithms where the point is
used.
When searching for a packed point, the Control Logic Navigator tool gives you an option to limit
your search by selecting a bit number in the Bit field.
You may search on all occurrences of the point on control sheets, or you may limit the search to
sheets where a specific bit is used (bits 0 to 15). If you select the blank option in the Bit field, the
option searches for sheets where any of the 16 bits are used. The bit option is ignored if the input
point is not a Packed Point.
When you begin a search for a point, this tool creates a drops list of the drop where the point
originates and any of the drops where it is received. The originating drop is tagged with an
asterisk ( * ). If there is more than one drop in the list, an All option is added to the drops list.
By default, the initial search always searches the originating drop from the drop list. After the
initial search is performed, you can select any other drop from the drops list, or select the All item
and then re-run the search to begin searching the other drops.
The tool provides the capability to save the search output to a file and to print the search output.
OW350_R1007 123
5.5 Engineering Tools Audit
5.5.1 What is the Engineering Tools Audit function?
The Ovation Engineering Tools Audit (Audit Trail) provides an automated way to log engineering
events. It provides an extra tool to help troubleshoot and quickly identify the root cause of
abnormal conditions that can translate into loss of operation and resources.
Not only does the Engineering Tools Audit reduce troubleshooting time, but it also complies with
more stringent security requirements imposed by NERC (North American Electric Reliability
Council.) NERC specifies mechanisms to protect the cyber assets of a plant and provide
auditable records of all control system changes to achieve compliance.
The Engineering Tools Audit enables a Distributed Control System (DCS) to be self-documented.
The DCS system keeps track of all changes performed and provides a record of those activities
when requested at a future time. The Engineering Tools Audit eliminates the time consuming
paper trail documentation of actions taken. It also presents properly Controlled electronic records
that are both reliable and easily available. The Engineering Tools Audit eliminates readability
problems and the possibility of errors that may occur with manual paper trail audits.
The electronic Engineering Tools Audit activities normally require some type of information
storage in a database or control memory. The more information that the Engineering Tools Audit
is asked to save, the more media space it uses, which could result in a loss of system speed.
This function captures (audits) and views Ovation Engineering Tool actions/operations, including:
 Changes made to the Ovation database by Engineering Tool applications such as the
Developer Studio, Control Builder, and Graphics Builder.
 Changes made to Ovation configurations.
 Operations performed by Engineering Tool applications such as the loading, clearing,
query/downloading, and rebooting of Ovation drops.
 Database import operations logged (as well as the name of the import file.)
124 OW350_R1007
5.5.2 What Ovation applications are audited with the Engineering Audit Tools
function?
The following table lists the Ovation applications that can use the Audit Tool and the auditing
levels that can be applied.
For a description of auditing levels, see To set the Engineering Tools Audit level (see page 126).
Ovation applications and auditing levels
APPLICATION AUDITING LEVELS
Control Builder Note: The addition and deletion of Control Builder default points are NOT audited.
High Level (1)
Reconciling a control sheet to the current database point values.
Medium Level (2)
Addition, modification, and deletion of an Ovation control sheet.
Addition, modification, and deletion of named (that is, non-default) Ovation process
points. In this context, the captured data simply identifies the point by name.
Low Level (3)
Modification of Ovation process points. This includes non-default points, as it may be
related to algorithm set points, and so forth. The amount of information captured in this
context is equivalent to that captured by the Developer Studio during low-level auditing
of an Ovation point.
Graphics Medium Level (2)
Builder
Addition of new diagrams or macros. Note that this also includes the first-time
compilation of a new diagram or macro.
Modification of a diagram or macro when performed by the UI version of the Ovation
Graphics Builder (that is, not when running in the non-UI Compilation mode.) No
additional information concerning the specific changes made to a diagram or macro is
captured.
Deletion of a diagram or macro (only with the Windows Engineering Tool Suite.)
Holding Medium Level (2)
Register
Builder/Editor Addition, modification, and deletion of Holding Registers. In this context, the data
captured simply identifies the Holding Register number. No additional information
based on specific values is captured.
Low Level (3)
Modification of Holding Registers. Additional information is captured to indicate the
previous and new values of the Holding Register. One entry is generated per modified
field. Note that since the ultimate storage of holding registers consists of 16-bit words,
the values captured are based on this data format.
OW350_R1007 125
APPLICATION AUDITING LEVELS
Database Since an Ovation import operation has the potential to update or create a vast amount
Import of data, you are warned if the current Auditing Level is "too low." If such a state is
Application detected, the Ovation Import application temporarily raises the auditing level to a
"recommended level." In all cases, the recommended auditing level is a high-level
configuration. (Essentially, this results in an entry being captured at the start of the
import operation and an entry being captured at the conclusion of the import
operation).
You have the ability to override any "automatically-adjusted" configuration settings at
the time of the import operation. For example, if the Auditing Level at the time of import
is "Low-level," you will be prompted to either:
1) Permit the temporary change to the recommended level.
2) Override the recommendation and permit the import operation at the lower level.
3) Abort the import operation.
High Level (1)
An entry is captured at the start of the import operation and includes the specified
command-line parameters.
An entry is captured at the conclusion of the import operation and indicates if errors
and/or warnings were encountered.
Medium Level (2)
In this context, additions and modifications of objects are captured.
Low Level (3)
Additional information is captured to indicate the previous and new values of the data
base object. One entry is generated per modified field.
126 OW350_R1007
5.5.3 To set the Engineering Audit level

2. Use the system tree (in the Hardware view bar) to navigate to the Engineering Tools Audit
folder:
Systems
Configuration
Engineering Tools Audit
3. Right-click on the Engineering Tools Audit item.
4. Select Insert New. The Engineering Tool Audit dialog box appears. The following figure and
table describe the fields of the Engineering Tool Audit dialog box.
Note: If the Engineering Tool Audit already exists in the system, it will appear in the WorkPad
area when you right-click on the Engineering Tools Audit item in the system tree. To open the
window, right-click on the Engineering Tool Audit item in the WorkPad window and select Open.
The Engineering Tool Audit window appears. You can then adjust the audit level as you choose.
Figure 39: Engineering Tool Audit dialog box
5. Set the Audit Configuration Level using the pull-down menu. Auditing the Engineering
tools/operations might influence their overall performance. Therefore, different auditing levels
are available that depend on your needs and the required response of your system. The
choices are:
 OFF
 High-Level Auditing
 Medium-Level Auditing
 Low-Level Auditing
6. Select Ok/Apply to apply the desired audit level.
OW350_R1007 127
The following table describes the auditing levels.
Audit level descriptions
LEVEL DESCRIPTION
OFF Auditing is disabled. Modifications to the Ovation database, Ovation configurations, and
engineering tool operations are not captured.
High User operations are captured. For example, the audit function captures the clear and load of
Ovation drops, initiation and completion of import operations, and reconciliation of tuning
changes to the database.
Medium All functions performed in the High audit state are captured. Also captured are changes
including identification of added and deleted items (such as points) and a simple indication
that a point has been modified (not including the values of the modified fields). Import
operations indicate affected database objects.
Low All functions performed in the High and Medium audit states are captured, including the old
and new values of each field of a modified database object. The same is true for Ovation
import operations.
5.5.4 Auditing examples
The following topics provide examples of high-, medium-, and low-level auditing.
High-level auditing example
High-level auditing captures events such as operations. If you perform modifications of database
items during high-level auditing, there is only one entry associated with the event. No additional
information, such as which fields were modified or what the old and new values are, is included.
The following table is an example of a high-level audit entry.
ITEM VALUE
Time 08-Jan-2006 10:21:42.

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

OS User Engineer1.
Machine drop148.
Action Insert.
Object Type LA Point.
Object Name LA001S001.UNIT1@W3.
Audited modification of an Ovation point
ITEM VALUE
Time 08-Jan-2006 10:17:15.

OS User Engineer1.
Machine drop148.
Action Modify.
OW350_R1007 129
Low-level auditing example
Low-level auditing provides additional information about events such as which fields were
modified and what the old and new values are. If multiple fields of an object are modified by an
Engineering Tool, multiple audit log entries are created (one for each field that was modified.) The
following table is an example of low-level audit data of an Ovation point.
ITEM VALUE
Time 08-Jan-2006 14:17:03.

OS User Engineer1.
Machine drop148.
Action Update.
Parameter DESCRIPTION.
Old Value Initial Description.
New Value Test I/O Point.
130 OW350_R1007
5.5.5 Using the Ovation Audit Viewer
The Ovation Audit Viewer is used to view, filter, and sort the current contents of the Engineering
Station Audit logs.
You can perform searches as well as sort and filter audit log entries on the interface. Your actions
do not change the information stored in the audit database.
In addition to specifying a time frame for the retrieval of the audit log entries, you can filter on
other items such as Audit Level, Action, Object Type, Object Name, Parameter, OS User
(Operating System User), and Machine.
To access the Ovation Audit Viewer
Use the following procedure to access the AuditView window.
1. Select Start -> Ovation -> Ovation Engineering Tools -> Ovation Audit Viewer.
The Ovation AuditView window appears. Since you can configure which columns to show or
hide (see page 137), not all of the possible columns may appear at start up.
Figure 40: AuditView window
OW350_R1007 131
AuditView menu bar
The following table describes the AuditView menu items.
AuditView menu descriptions
MENU PULL-DOWN MENU ITEMS AND DESCRIPTION
File Open — Open a saved Audit.

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

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

active document.
Search — Searches for audit

information (see page 134).
Date/Time Retrieval — Displays

information from a particular date and
time.
OW350_R1007 133
To view current Engineering Tool audits
Use the following procedure to view current audit information:
1. Access the Ovation Audit Viewer (see To access the Audit Ovation Viewer (see page 131)).
2. Specify the time range from which you want to extract information by updating the date and
time fields on the toolbar (see AuditView toolbar (see page 133)). To do this:
 Select the date pull-down menus to access a calendar and select a day.
OR
 Type the date into the fields. (You can also use the increment/decrement buttons to
advance the date, forward or backward, one day at a time.)
3. Enter the appropriate time into the date field.
4. Choose one of the following options:
 Select the Date/Time Retrieval icon on the toolbar.
OR
 Select Date/Time Retrieval from the Data menu. The following window appears:
Figure 41: Audit View Estimated Entries
5. Select Continue to get a listing of the entries.
134 OW350_R1007
To define search criteria for an audit report
Use the following procedure to define specific search criteria to view audit logs.
1. Access the Ovation Audit Viewer (see To access the Ovation Audit Viewer (see page 131)).
2. Select the Search icon on the toolbar, or select Data -> Search from the Ovation Audit
Viewer menu.
The Audit View: Search dialog box appears.
Figure 42: Audit View: Search dialog box
3. Choose a time range from the Date/Time Range drop-down menu. Choosing Custom Time
enables the Begin and End fields.
Note: Leaving the Date/Time Range set to "All Times available" could create long drop-down
lists in the search selections which could include items not available. It also lengthens the
search time available.
4. If you choose Custom Date/Time, choose a Begin and End time frame for the search.
5. Select the appropriate criteria from the drop-down menus (see the following table for more
information).
OW350_R1007 135
Audit View: Search dialog box fields
DATA CHOICES
Date/Time The Choices are:

Range  All Times available
 Last 1 hour
 Last 8 hours
 Last 24 hours
 Last 1 week
 Last 2 weeks
 Last 1 month
 Custom Date/Time
Audit Level 1, 2, 3 (depending on the database). See What Ovation applications are audited with
the Engineering Audit Tools function? (see page 125).
Action Blank, Clear, Delete, Engineer, Insert, Load, Reboot, and so forth.
Status Blank, Begin, Initiate, Initiated, Success, and so forth.
Object Type Blank, AnalogPoint, Audit level status, Audit status, Drop, ProfibusPort, and so forth.
Object Name Blank, "Drop name", Alarm Display, Audit Status, and so forth.
OS User Blank, Administrator, System, and so forth.
Machine Blank, Name of machine.
Program Blank, db_xmit_server.exe, Developer Studio, OvPtTest.exe, SQLLDR.exe, and so
forth.
Parameter Blank, Alarm Display Number, Audit_Level, Display Diagram In, , Position 1, and so
forth.
Old Value Blank, 1 (High-Level Auditing), 3 (Low level auditing), -4, and so forth.
New Value Blank, 0, 1 (High-Level Auditing), 3 (Low level auditing), -4, Enabled, Group1, and so
forth.
Data Blank, Clear operation to "Drop1" complete..., Load operation to "Drop100", and so
forth.
6. Select the Search button on the AuditView toolbar (see page 133).
7. A pop-up dialog box appears stating the number of items found and asking if you want to
proceed. Click Continue to display the items or Cancel to quit the search. If you select
Continue, the Audit View window populates with information.
136 OW350_R1007
To view individual event information
Once you have searched and displayed audit results in the Audit View window, you can display
information on a single entry. To do this:
1. Double-click on any item in the Audit View window. The Audit View: Entry Properties window
appears displaying all of the information on the item you selected.
2. Use the Next button to advance to the next item on the Audit View window. Use the Previous
button to navigate back to the item that appears before the selected item on the Audit View
window.
Figure 43: Audit View:Entry Properties
OW350_R1007 137
To show or hide columns using the menus
You can configure which columns will appear on the Audit View window. Use the following
procedure to use this feature:
1. Access the Ovation Audit Viewer (see page 131).

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

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

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

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

 Provide a mechanism to monitor system status and initiate actions in the control system.
Commonly used algorithms of this type

 DROPSTATUS (see page 143) - drop status record monitor.
 HEARTBEAT (see page 145) - generates heartbeat signals that can be received by other
drops.
 LATCHQUAL (see page 148) - latches and unlatches the quality of an input analog or digital
point.
 PNTSTATUS (see page 149) - point status.
For more information refer to Ovation Algorithms Reference Manual.
142 OW350_R1007
5.6.1 DROPSTATUS
Description
The DROPSTATUS algorithm accesses and outputs the contents of any record field in the Drop
Status Record (DU) for a particular Controller. To access the contents of a record field, the field
number must be specified. If an invalid field number is entered, zero is written to the AOUT and
POUT output points.
The data in the DU record field is output as a packed point. If specified, the contents of the record
field can also be output as an analog value. (See Ovation Record Types Reference Manual.)
Note: For Ovation 3.2 systems and later, the DROPSTATUS algorithm will allow any DU record
to be used as an input into the drop status.
Functional Symbol
Field Numbers
FIELD NUMBER FIELD NAME
1 FA
2 FB
3 FC
4 FK
5 FS
6 FO
7 HC
8 TA
9 CT
10 RT
11 LN
12 E5
13 E6
14 GD
15 GL
16 GI
17 GG
18 GH
OW350_R1007 143
FIELD NUMBER FIELD NAME
19 NC
20 FF
21 JU
22 U4
23 U5
24 U6
25 U7
26 KM
27 VE
28 K0
29 K1
30 TR
31 NE
32 IS
33 IE
34 OP
35 OE
Algorithm Record Type = LC
Algorithm Definitions
NAME LC ALG. TYPE REQUIRED/ DEFAULT DESCRIPTION MIN.

RECORD OPTIONAL VALUE POINT
FIELD RECORD
RECD G0 - Data Init. Required 0 The field number in -

Integer the drop record.
AOUT - Variable Optional - Output (analog); LA

contents of the DU
record field.
POUT - Variable Required - Output (packed); LP
contents of the DU
record field.
DUID - Variable Optional - Input DU record DU
144 OW350_R1007
5.6.2 HEARTBEAT
Description
The HEARTBEAT algorithm is designed to generate heartbeat signals that can be received by
other drops for use in safety critical applications. The algorithm can also be utilized to monitor up
to five heartbeat signals generated from heartbeat algorithms in other Controllers. If the algorithm
detects that a heartbeat signal being monitored has ceased, it sets the corresponding output to
one. It has a value of zero when it is communicating.
A heartbeat signal is a continuously changing signal that is generated and broadcast from an
Ovation Controller. A heartbeat signal that is continuously changing is an explicit indication that
the Controller generating the heartbeat signal is functioning properly.
Typically, the heartbeat signal allows a control strategy to monitor other heartbeat signals (ones
that are broadcast from other Controller drops) and take appropriate actions if the heartbeat
signals cease. It is common in power generation applications to have the loss of a heartbeat
signal from one or more Controllers generate a Master Fuel Trip (MFT) in the Controller that is
monitoring the heartbeat signals.
Functional Symbol
OW350_R1007 145
Overview
The value of a heartbeat signal output (HTBT) is a continuously changing analog value. The
HTBT output is updated each loop time to a new number. The actual value of the heartbeat signal
is not important - it is important that the heartbeat signal updates each loop time by the originating
Controller and that the receiving Controller records a different value each loop time.
If any input heartbeat signals are connected to the HEARTBEAT algorithm, they are monitored to
ensure that the value changes on each successive loop. During each execution loop, the value of
each connected input is read and compared to that point's value that was read on the previous
loop. Under normal conditions, these two successive values should be different - that is, the
changing signal is being received from the originating drop(s) successfully. If the value of any of
the input points is unchanging for the user-entered timeout period (TIME1 - 5), the corresponding
trip output OUT1 - 5 is set to true.
Note that if the user-entered timeout period is not an exact multiple of the control task period in
which the algorithm is executing, then the algorithm rounds the user-entered value to the next
higher integer multiple of the task period. When this occurs, the resulting actual timeout is the
user-entered timeout plus the control task period. This action ensures that the tuning fields of the
algorithm always reflect the exact timeout period.
Emerson recommends that when the algorithm is used to generate a heartbeat signal, it be
executed in a 0.1 second control task. When the algorithm is used to monitor other heartbeat
signals, Emerson recommends that it be executed in a 0.1 second control task.
Also, note that the algorithm ensures that the user-entered timeout cannot be set to a value less
than the time that it takes the Ovation Network to detect a loss of communication on a primary
Controller and to initiate a failover. This time is typically five seconds.

FIELD REC.
DIAG LU - Data Init Optional - Tuning diagram -

Integer number
TIME1 R1 - Real Tuning Required - Timeout value for -

Constant heartbeat input 1*
IN1 Input Variable Optional - Input Heartbeat signal LA
1
2
146 OW350_R1007

FIELD REC.

3
4
5
HTBT Output Variable Required - Heartbeat Output LA
Note: It is
recommended that
the Heartbeat output
(HTBT) points be built
with a broadcast
frequency of
100msec instead of 1
second.
OUT1 - Variable Optional - Fail Output for LD, LP

Heartbeat input signal
1
2
3
4
5
* Note that the algorithm sets the parameter to a minimum value required for the Ovation network
subsystem to detect a timeout. You only have the option to extend the timeout value. Also, if the user-
entered timeout is not an integer multiple of the control task period, the algorithm rounds up to the user-
entered value to the next highest integer multiple of the control task period.
OW350_R1007 147
5.6.3 LATCHQUAL
Description
The LATCHQUAL algorithm latches and unlatches the quality of an input analog or digital point.
The algorithm sets or clears the “Latched Quality” bit of the IN1 point, depending on SET and
RSET points. Bit 14 of the 2W (second status word) of the analog point or bit 11 of the 2W
(second status word) of the digital point is the “Latched Quality” bit for the point.
Functional Symbol
If RSET is TRUE and the latched quality bit of IN1 is set, the Latched Quality bit is cleared.
If RSET is FALSE and SET is TRUE, then depending on the value of QUAL, the IN1 point sets its
Latched Quality bit and quality as follows:
 If QUAL = 0 and Latched Quality of IN1 is not set, then Latched quality bit is set at its current
state.
 If QUAL = 1 and Latched Quality of IN1 is not set or the Quality of IN1 is not GOOD, then the
Quality is set (latched) to GOOD.
 If QUAL = 2 and Latched Quality of IN1 is not set or the Quality of IN1 is not FAIR, then the
Quality is set (latched) to FAIR.
 If QUAL = 3 and Latched Quality of IN1 is not set or the Quality of IN1 is not POOR, then the
Quality is set (latched) to POOR.
 If QUAL is greater than or equal to 4 and Latched Quality of IN1 is not set or the Quality of
IN1 is not BAD, then the Quality is set (latched) to BAD.
RSET overrides SET. If both are TRUE, then the Latched Quality bit of IN1 is cleared.
Note: IN1 can be a digital or analog point, with the minimum point record being LD or LA. If a
smaller point record is used, then no action is taken.
Algorithm Record Type = None
148 OW350_R1007

FIELD RECORD
SET - Variable Required - Digital input. Set LD, LP

Latched Quality bit
flag.
IN1 - Variable Required - Analog/Digital input LD, LA
QUAL - Variable Required - Packed input. LP

Indicates the quality to
which IN1 is to be set.
RSET - Variable Required - Digital input. Clear LD, LP

Latched Quality bit
flag.
OW350_R1007 149
5.6.4 PNTSTATUS
Description
The PNTSTATUS algorithm outputs the states of two specified bits of the point record's status
word. When the ENBL input is TRUE, the states of BITA and BITB of the point record's status
word are output to OUTA and OUTB, respectively. For example, if the bit specified by BITA is a
one, then OUTA is TRUE. Conversely, if the bit specified by BITA is a zero, then OUTA is FALSE.
This example also holds TRUE for BITB and OUTB.
For analog and digital records, the valid range for BITA and BITB is 0 through 31.
When the ENBL input is TRUE and either the BITA or BITB operand contains an invalid bit
number, no operation occurs and the BITA and BITB outputs are FALSE.
Functional Symbol

FIELD RECORD
DIAG LU-Integer Data Init. Required 86 Tuning Diagram -

number
STAT X1-Byte Data Init. Required 1W Status word 1W, -
2W, 3W
BITA X2-Byte Data Init. Optional 0 Which bit in the point -
record's status word
is output to OUTA
BITB X3-Byte Data Init. Optional 0 Which bit in the point -

record's status word
is output to OUTB
ENBL - Variable Required - Enable Input Flag LD, LP
(digital)
IN1 - Variable Required - Input LA, LD
OUTA - Variable Optional - When the ENBL LD, LP
input is TRUE, this
output reflects the
state of the bit
specified by BITA.
150 OW350_R1007
5.7 Status Information Diagrams

FIELD RECORD
OUTB - Variable Optional - When the ENBL LD, LP

input is TRUE, this
output reflects the
state of the bit
specified by BITB.
5.7 Status Information Diagrams
One of the most intuitive methods of system diagnostics is through the use of graphics. One such
graphic is the System Status Display diagram. Status diagrams provide the operator with a
graphical representation of Ovation system status. Some diagrams provide general information on
the entire Ovation system, while others provide specific information for a particular system drop.
Color variations on the monitor allows for easy and quick identification of abnormal system
conditions and acknowledged alarms. One such graphic is the System Status Display diagram.
The System Status Display diagram, representative of the system configuration, displays the
Ovation Network and drop configurations on the network. Status information is displayed by color
coding each drop, and the colors can be customized.
Functions available from the system status display includes:

 Access to the drop details diagram
 Access to a customized system overview diagram
 System alarm acknowledgment
 Clearing a designated drop in alarm
5.8 Non-Ovation diagnostics tools
Maintenance of the Ovation system is kept to a minimum by built-in fault tolerance and
diagnostics that are provided through several tools to help keep your system healthy:
 AMS Suite (see page 152)
 SmartProcess suite of Plant Optimization software (see page 152)
 Diagnostics for HSDO modules (see page 154)
 Wave Web Viewer (see page 154)
 LC/EHC Turbine Controller interface diagnostics
 GE Genius Gateway Diagnostics
 Engineering Tools Audit (see page 124)
 SureService Customer Support Programs (see page 104)
 Using the Controller Diagnostics tool
 Control Logic Navigator (see page 123)
 System diagnostic algorithms (see page 142)
 Software version tab in the Controller Diagnostics (see page 119)
OW350_R1007 151
5.8.1 AMS suite for use with HART field devices or Foundation field bus devices
The AMS™ Suite (Asset Management System), is a comprehensive and integrated family of
applications from Emerson developed for predictive maintenance, performance monitoring, and
economic optimization. AMS Suite applications are industry-leading applications that optimize
economic performance and enable predictive and proactive maintenance of a plant’s production
assets. These applications include:
 Asset Portal - Decision support, reporting and analysis on the health and performance of your
production assets.
 Intelligent Device Manager - Predictive and proactive maintenance of instruments and valves.
 Machinery Health Manager - Predictive and proactive maintenance of mechanical equipment.
 Equipment Performance Monitor - Predictive and proactive maintenance of process and
mechanical equipment.
See the AMS documentation for more details.
5.8.2 SmartProcess suite of Plant Optimization software
The SmartProcess line of Plant Optimization software reduces maintenance costs by promoting
better plant efficiency. The various software products consider a plant's specific operating
constraints and respond to a variety of economic factors, optimizing and enhancing plant
processes, regardless of boiler size or firing type. SmartProcess even helps plants to balance
conflicting objectives -- for example, achieving lower NOx levels while improving boiler efficiency.
And, because it is system-independent, SmartProcess can dramatically boost your plant's
performance no matter what control system is installed.
Some of the more popular Plant Optimization software products are:
Combustion Optimizer - Increases boiler efficiency while maintaining emissions, loss on ignition
(LOI), and a number of other cost-impacting factors.
Cyclone Boiler Optimizer - Dynamically optimizes the boiler and combustion process to produce
heat rate improvements.
Economic Plant Optimization - Implements the load dispatch at any given moment or for a
future period of time. Allows plants to optimize power generation across several generating units
in a networked region, based on a number of factors, including operating costs, unit efficiencies,
maintenance schedules, and operational constraints.
Economic Optimizer for the Water/Wastewater Industry - Highly scalable application that
manages water treatment and wastewater treatment processes to minimize costs, reduce
equipment wear and tear, and balance tradeoffs such as low and high flow and pump usage.
FGD Optimizer - Improves SO2 removal efficiency and lowers operating costs by reducing
liquid/gas in wet scrubbers, power consumption by slurry pumps, limestone consumption, as well
as scaling and plugging.
Fleet Optimizer - Uses data from multiple areas of the plant to achieve industry objectives such
as environmental compliance, decreased operational costs, and increased profitability.
152 OW350_R1007
Fluidized Bed Optimizer - Considers such variables as boiler efficiency, fuel flow, heat losses,
combustion air flow, and flue gas flows, and collects, analyzes, and reports accurate performance
data of these applications. It then uses the performance data to predict future performance and
determine the most efficient and cost-effective balance of system conditions.
Global Performance Advisor (GPA) for the Power Industry - Allows operators to identify
controllable losses, track equipment performance against design specifications, and quickly
identify problematic process areas to reduce operating costs.
Global Performance Advisor (GPA) for the Water/Wastewater Industry - Provides plant
personnel with the ability to continuously monitor the performance of major plant equipment and
compare it to expected performance criteria.
Precipitator Optimizer - Enhances electrostatic precipitator efficiency by optimizing the cleaning

sequences and cell voltage bias to ensure that ash is optimally collected in all locations.
SCR Optimizer - Drastically improves SCR technology by controlling temperature, reducing

ammonia usage, and minimizing pressure loss.
Sootblower Optimizer - Delivers sequenced sootblowing control that efficiently manages steam
and energy while avoiding opacity spikes.
Steam Temperature Optimizer - Provides the most stable and accurate model for power
generation which permits faster ramp rates, improved turbine life, and reduced stress on boiler
pressure parts.
Global Performance Advisor (GPA) Function Block Diagrams (FBDs)
FBDs provide a visual method of designing process control logic in your GPA projects. The ability
to program and view the control project in the GPA graphical environment speeds development
and facilitates troubleshooting.
GPA gives FBD documents top priority in the execution order during Run or Debug mode. This
ensures the integrity of the control system.
GPA contains hundreds of pre-defined algorithms for use in your FBD documents. In addition,
custom algorithms can be created to extend the algorithm set.
FBD documents are configured by placing algorithm function blocks in the document window,
defining their properties, and connecting their signals.
You can add HMI interface objects to FBD documents by using the drawing and display tools.
There is a limit of 32 FBD's. This is a machine-wide limit, regardless of the number of projects
and/or workspaces defined, or of the number of instances of GPA that may be currently executing
on that machine.
OW350_R1007 153
5.8.3 High Side Digital Output (HSDO) diagnostics
For both stand-alone and redundant High Side Digital Output module configurations, power switch
diagnostic bits are accessed every 25 milliseconds. If a digital output fault is detected on a
channel, the corresponding Module Channel Fault register fault bit is set. When any bit in the
Module Channel Fault register is set, the Module Status register (register 0xD) Digital Output fault
bit (Bit 14) is also set.
These digital output fault conditions can be detected and reported:

 Power switch output short circuit to ground.
 Power switch output short circuit to +24V (switch cannot be turned off).
 Power switch power supply under-voltage.
 Power switch open circuit (switch cannot be turned on).
When HSDO modules operate in a redundant module configuration, a dynamic power switch turn-
off test is performed periodically. By communicating over the cross-connect cable serial link, the
two HSDO modules coordinate their dynamic power switch turn-off testing so that both modules
do not shut off their power switch outputs at the same time.
Upon module insertion, after communication between modules is established, and after 12
additional seconds have elapsed, the HSDO module performs the dynamic power switch turn-off
test. The HSDO module will then performs test periodically at a time interval ranging from 15
minutes to 24 hours. This time interval is selected by the values of Module Configuration register
bits 10, 9 and 8.
5.8.4 Wave Web Viewer
Wave Web Viewer is a connectivity tool that allows you to view live Ovation data via your internet
browser.
Wave can:
 Convert and display your Ovation process diagrams, point information, and simple trends in
your internet browser.
 Display dynamic, real-time process point data.
 Give you continuous access to plant data from any location.
 Reduce support costs and response time by allowing on-call support professionals to
troubleshoot your plant control system(s) from any location.
 Uphold your security needs with read-only access to plant information and disabled control
functions.
 Supply graphics similar to those on an Ovation Workstation or WDPF WEStation to provide
you with a familiar point of reference.
154 OW350_R1007
How can I use Wave?
Scenarios of Wave usage:

 You want to see each of your plant's actual outputs at a glance. Instead of calling each plant
individually, you can access Wave from your desktop PC to see your generating capacity at a
network level.
 You are on the East Coast but your plant is on the West Coast. Wave provides access to your
plant's real-time point information through familiar plant workstation graphics. With Wave, you
can maximize your efficiency even when you are away from the plant.
 Your plant operator is unable to diagnose a problem. Rather than having your operator come
to your workstation, you can troubleshoot remotely using Wave.
How does Wave work?
To use Wave, you must install a Wave server and a web server. There are two ways that you can
install and use Wave:
 Wave server and web server on two separate workstations.
 Wave server and web server on the same workstation.
Figure 47: Web server and wave server
OW350_R1007 155
It is important to decide whether you want to place your servers on the same or on separate
workstations, and whether you want to purchase a new workstation for Wave or use an existing
workstation. The following table lists the advantages and disadvantages of each configuration.
INSTALLATION ADVANTAGES DISADVANTAGES
Pre-existing  Uses existing hardware  You might need to add additional

workstation  Least expensive disk space
New, dedicated  Provides dedicated disk space  Requires additional hardware

workstation  Allows you to disable file transfer  More expensive
protocol (ftp) and remote login
services to provide greater security
Separate Wave  Provides dedicated disk space  Requires additional hardware
server and web  Allows you to isolate your web server  You must copy graphic files from
server so that only process data is retrieved your Wave server to your web server
from inside your firewall to provide the  Most expensive
greatest security
Installing your Wave server behind your firewall increases security, but requires you to use two
separate workstations. Weigh your security needs against your budget and choose the installation
that works best for you.
Note: It is not recommended that you load Wave on a Windows Database Server because it
conflicts with the Oracle Web Server.
5.8.5 LC/EHC Turbine Controller interface diagnostics
The following diagnostic information is available during the operation of the LC/EHC Turbine
Controller interface:
 The interface generates values for use with the SLCSTATUS algorithm.
 The external host PC displays diagnostic information, if configured to do so.
 The LC module LEDs display status information.
5.8.6 GE Genius Gateway diagnostics
A node Record (RN) can be created for each redundant or simplex GE Genius Gateway. Status
values regarding the GE Genius Gateways are written to the A2 field of the node record. Bits 0
and 1 are used to monitor the health of the GE Genius Gateway which is in primary mode. The
node record is configured to alarm on a true condition for either bit 0 or 1.
The A2 field of the node record for the GE Genius Gateway contains the following status
information:
BIT ERROR CONDITION ALARM CONDITION
0 1 - Loss of communication with primary GE Genius Gateway 1

1 1 - System error returned from primary GE Genius Gateway 1
156 OW350_R1007
5.9 SIS operations and maintenance practices
5.9.1 Bypasses and other overrides
It is often necessary to force an output value to remain at the Normal value during plant startup to
prevent a trip caused by inputs that have not yet stabilized at their normal operating values. You
may also want to bypass inputs to allow for sensor maintenance.
Ovation SIS has built-in capability for creating applications that follow guidelines set forth in the
IEC 61511 standards. Ovation SIS does not limit you to using its built-in bypass capability. You
are free to create custom logic and interfaces for this purpose.
The following subsections describe the built-in bypass capability in Ovation SIS.
Override types
Maintenance bypass
During a maintenance activity such as calibration, proof testing, or repair of a transmitter, a

maintenance bypass temporarily prevents the process value on the input channel from
contributing to a potential trip. The Analog Voter (LSAVTR) and Digital Voter (LSDVTR)
algorithms provide the built-in maintenance bypass capability. When an individual input is
bypassed for maintenance, its vote to trip is not considered in voting logic. A maintenance bypass
is set and cleared by an operator or maintenance technician using an SIS Write operation from a
workstation or a physical key switch, but the bypass could be cleared by the voter algorithm itself
based upon a configurable timeout.
Startup bypass
While a process is starting up, a startup bypass temporarily overrides a process value to allow
time for it to reach a value that does not initiate a trip. The Analog Voter and Digital Voter
algorithms provide the built-in startup bypass capability. The algorithm output maintains the
normal operating value while the startup bypass is active. A startup bypass is initiated by an
operator using an SIS Write operation or by the voter algorithm detecting a process startup
condition. The startup bypass is cleared after a configurable time period or optionally when the
voter algorithm detects a process condition.
Parameter force
This override uses Control Studio Debug mode to force an input parameter on an algorithm
diagram to have a value other than the source value. The use of parameter forces is intended for
functional testing, not when the SIF is providing its protection function unsupervised.
LSEM effect force
This override forces an Effect output on a LSCEM algorithm to the normal or tripped value,
thereby forcing the output channel value. The LSCEM Effect force is intended for testing or to
manipulate final elements while the process is not running. It should not be used as a
maintenance bypass; individual inputs should be bypassed for maintenance purposes.
OW350_R1007 157
Configuration of bypasses
The configurer of SIS module logic uses the BOPn (Bypass Opt n) parameters in the voter
algorithms to determine which maintenance and startup bypass options apply for the algorithm
usage. Refer to the Analog Voter and Digital Voter algorithms topics for details on the available
bypass options.
The configurer must provide a means to annunciate to the operator when a maintenance bypass
or force condition is active. The built-in capability is provided through the SIS_DEFAULT module
template, which has an alarm parameter, BYPASS_ALM, referencing bits in the SIF_ALERTS
bitstring parameter found in all SIS modules. The referenced bits roll up the state of override
conditions in the SIS module and in the voter and LSCEM algorithms in the module. BYPASS
_ALM is active when a maintenance bypass is active in any voter algorithm in the module, an
Effect is being forced in any LSCEM algorithm, or an input is being forced using Control Studio
Debug. Startup bypasses are not annunciated by default, but can be configured to do so using a
check box.
The ability to set and clear maintenance bypasses in voter algorithms at runtime can be
configured using dynamos for the voter algorithms in Ovation Operate configure mode.
Operation of bypasses
A Maintenance bypass is typically used in either of two situations.
1. There is a planned maintenance activity on a transmitter or other sensor. A single input is

bypassed to prevent that input from causing a spurious trip during the activity.
2. A failure occurs in a transmitter, the field wiring, or the input circuitry of the Logic Solver
during normal operation. A maintenance bypass is used to prevent BAD status from causing a
trip in the output algorithm (if the failure itself did not already cause a trip).
The bypass is set from a process display in Ovation Operate, for example, by clicking on an input
check box of the voter algorithm dynamo and then confirming the selection. A set bypass is
cleared using the same procedure. While the bypass is set, BYPASS_ALM remains active and
the toolbar button for the SIS Alarm List is visible in the Ovation Operate toolbar, meaning there is
at least one active, unacknowledged, or suppressed SIS alarm in the list. A click on the toolbar
button opens the SIS Alarm List display.
Operators should be aware of all alarms visible on this display. The handoff at shift change should
include a review of the SIS Alarm List. You can create other alarms related to bypasses by
referencing alarm conditions determined in the voter algorithms. These alarms include a reminder
that the expiration of a bypass is imminent and whether a bypassed input is voting to trip.
The history of bypass activity is available in the Event Chronicle of Ovation Process History View.
No special configuration is required. The setting and clearing of bypasses and bypass permits are
recorded whether they are done using SIS Writes from workstations or physical switches. An
event record is also created whenever the algorithm removes a bypass due to a timeout.
Refer to the example (see page 159) of a scenario where a maintenance bypass is used following
a failure.
158 OW350_R1007
Maintenance bypass example
The Failure
A HART transmitter fails, resulting in a Field Device Malfunction HART error and a down-scale
output value as configured in the device.
How the Logic Responds
Bad status enters the SIS module logic in the Logic Solver because the input channel was
configured to not ignore the Field Device Malfunction error. The Analog Voter algorithm in the SIS
module has a “Greater Than” input detection type (DTYPE) and a 1oo1 voting arrangement. Bad
status propagates through the voter algorithm, but the down-scale value does not cause a trip
value on the output of the algorithm. Bad status continues to propagate through the LSCEM
algorithm and causes the fault state timer to start in the Digital Output algorithm, but no trip occurs
on the output.
How the Operator Responds
The BAD status has caused IO_ALM in the SIS module to become active and appear on the
alarm banner in Ovation Operate. The operator clicks the module button in the alarm banner,
which changes the main display to the interlock display created for the SIF and pops up the SIS
module faceplate. The operator assesses the impact of the failure by looking at the interlock
display, which was created with algorithm dynamos. It is clear that a trip has not occurred, but the
operator sees on the DO algorithm dynamo that the fault state timer value is incrementing and
sees the time value at which the output algorithm initiates a trip.
The operator clicks the bypass check box for the transmitter and confirms the “set bypass.” The
fault state timer stops incrementing and retains its value. The operator initiates the repair activity
for the transmitter, knowing that manual supervision of the SIF is necessary while the bypass is
active because the Logic Solver is not able to respond to a demand if one occurs. Manual
supervision implies that a local measurement is available for the process value and the operator
can be notified if a demand occurs and has a means to manually initiate a trip.
There are several variations to this scenario to consider.
1. Suppose the voting arrangement is 1oo2. In this case the BAD status does not propagate.
Manual supervision is not necessary. The SIF is still able to respond to a demand based on
the other transmitter. The operator bypasses the BAD input so a trip does not occur when the
transmitter is replaced.
2. Suppose the voting is 2oo3. In this case the operator merely follows up on repair for the
transmitter. No maintenance bypass is needed. The other two transmitters are providing the
protection and there is no concern that a trip might occur when the transmitter is replaced.
3. Suppose the transmitter failure results in an up-scale output value. With a 1oo1 or 1oo2
voting arrangement, a false trip occurs. A 2oo3 voting arrangement has the same result as a
down-scale output value. But 2oo2 voting starts the fault state timer in the output algorithm
because there are not enough good inputs to ensure a proper response to a potential
demand.
Whenever BAD status enters an SIS module and a determination is made that a repair is
required, the repair should be completed within the allowed repair time for the SIF to prevent the
PFDavg or PFH from exceeding the SIL verification value.
OW350_R1007 159
5.9.2 Fault detection, system response, and repair procedures
The Logic Solver executes extensive self-testing on a continuous basis to detect potential faults.
This section presents an overview of fault detection, how the Logic Solver and Ovation SIS
respond to a detected fault, and what you should do if a fault occurs. Although the presence of a
fault is expected to be uncommon, it is important to have a fundamental understanding of the
topic.
Faults detected by Logic Solver diagnostics are generally related to hardware failures in the Logic
Solver, but can also be associated with field devices and field wiring, or other conditions not
related to hardware. Some faults have the potential to prevent the appropriate response to a
process demand, some do not. The Logic Solver’s response and the recommended action
depend on the type of fault detected.
The terms fault and error are used interchangeably. Not all diagnostic conditions detected and
annunciated by the Logic Solver are faults or errors. Some merely cause an advisory alert such
as a reminder that a proof test of the Logic Solver is due soon.
Ovation SIS responds to faults detected in the Logic Solver in one of three ways:
1. The Logic Solver responds to a detected fault by initiating a shutdown; an Ovation SIS alarm
occurs.
The Logic Solver has detected a fatal error, which results in a reset and the de-energizing of
all output channels on this Logic Solver. Reasons for a fatal error include, among others, a
processor has failed and does not arm the hardware watchdog, a processor has detected that
a critical task did not complete in a timely fashion, or the main processors have calculated
different output values. An alarm occurs following a fatal error, but the particular alarm
depends on whether the Logic Solver is simplex or redundant.
2. An Ovation SIS alarm occurs when the Logic Solver detects a fault; the Logic Solver
continues providing its protection function.
The Logic Solver has detected a non-fatal condition. An alarm occurs because the condition
requires an operator action such as initiating maintenance or taking steps to clear the
condition. When a non-fatal condition is active, the Logic Solver is still able to respond to a
process demand. In some cases, a demand results in a reset of the Logic Solver if an error
condition is already present, for example, an output channel is stuck On.
3. Ovation SIS logs an event record when the Logic Solver detects a fault; the Logic Solver
continues providing its protection function.
The Logic Solver has detected a non-fatal condition, but no alarm occurs because immediate
action is not required. An event record is added to Event Chronicle, which may be of interest
in a future investigation. Ovation SIS creates event records for all annunciated conditions in
addition to these event-only conditions.
160 OW350_R1007
How Ovation SIS annunciates faults
Ovation SIS provides standard alarms to annunciate, in Ovation Operate, faults detected by the
Logic Solver. No special configuration is required. At runtime the alarms are part of a container
with the Logic Solver name. When a Logic Solver alarm appears on the alarm banner in Ovation
Operate and is clicked by the operator, the Logic Solver faceplate opens. The faceplate shows
the active alarm(s): FAILED_ALM, MAINT_ALM, ADVISE_ALM, or COMM_ALM. It also shows
the text for the active condition or “Multiple conditions” if more than one alert condition is active for
the particular alarm.
A button on the faceplate toolbar opens Diagnostics Explorer in the context of the Logic Solver.
The Logic Solver container has a number of diagnostic parameters accessible at runtime by the
Logic Solver path. There is also a container for the Logic Solver itself, accessible at runtime by
the controller path using the leftmost slot number of the card, for example, CTLR1 /IO1
/C05/param_name.
A redundant Logic Solver pair has diagnostic parameters for each Logic Solver and for the
redundant pair. The figure below is an example of Diagnostics Explorer showing the diagnostic
parameters for the highlighted Logic Solver. There is an “alerts” bitstring parameter associated
with the Failed, Maint, and Advise alarms. The alarm is active if any bit is set in the corresponding
alerts parameter. The Comm alarm is active if the SIS Data Server cannot communicate with the
Logic Solver (or either, if redundant).
The figure below is an example of the Diagnostics Explorer showing the diagnostic parameters of
the left Logic Solver of a redundant pair. The right Logic Solver has the same parameters. There
is a bitstring parameter for the status of each subsystem. The bits in these subsystem status
parameters map into bits of the alerts parameters in the Logic Solver container. A simplex Logic
Solver has direct mapping, but a redundant Logic Solver combines the subsystem status
conditions into the alerts parameters. If the subsystem status condition is active in either Logic
Solver card, the mapped alert condition is active.
Refer to the SLS Diagnostic Parameters topic in the Ovation SIS book of Ovation Books Online
for details on the subsystem status and alert bitstring parameters.
The topic describes:

 The text and meaning of each condition
 How subsystem status bits map into alert bits
 What action to take when an alert condition becomes active
 Which conditions annunciate and impact device integrity
 Which conditions are event-only and do not impact device integrity
You can change the priority of the Failed, Maint, Advise, and Comm alarms. Because certain
error conditions can exist momentarily, avoid alarm priorities that are auto- acknowledging.
OW350_R1007 161
Evaluating and responding to annunciated faults
When a fault or other annunciated condition occurs, there are multiple sources of information to
be evaluated prior to taking action. The evidence left by the condition is a function of the type of
fault and whether the Logic Solver is simplex or redundant.
The first step in the evaluation is determining whether the condition is fatal or non-fatal.
 A fatal error in a simplex Logic Solver generally results in a process shutdown because output
channels of the Logic Solver card are de-energized. An active Comm alarm occurs
immediately.
 A non-fatal error in a simplex Logic Solver does not impact the process. There is no Comm
alarm, but there is a Maint or Advise alarm depending on the condition.
 A fatal error in one of a redundant pair of Logic Solvers does not impact the process because
the other Logic Solver continues to drive outputs. An active Maint alarm occurs immediately
because the partner card with the fatal error is not available.
 A non-fatal error in a redundant Logic Solver results in an active Maint or Advise alarm. The
evidence differs from a fatal error in that the partner card has not gone through reset, so it
continues to be available to the Logic Solver without the error condition.
The next step is determining whether the error condition is still present. Typically detected faults
are persistent, that is, they are caused by a hardware failure and require that the Logic Solver be
replaced. But some conditions are momentary, clearing after being active briefly. In this case an
inactive, unacknowledged alarm is present. Diagnostic parameters do not indicate the cause of
the alarm because the condition is no longer active. Event Chronicle must be used to determine
which condition caused the alarm when the alarm is no longer active.
162 OW350_R1007
Evaluating fatal errors
Fatal errors result in a reset of the affected Logic Solver. The evidence of a fatal error changes
based on the time since the fatal error occurred. Immediately after a fatal error the Logic Solver
resets and begins its power-up testing, this completes in about two minutes. During this time the
Logic Solver is not reporting diagnostic information to the SIS Data Server. A redundant partner of
this Logic Solver indicates that its partner is not available while it is power-up testing. If the fatal
error is momentary, the “partner not available” condition clears when power-up testing is
complete. But if the fatal error is persistent, the “partner not available” condition remains.
The Logic Solver stores the reason for a fatal error in a diagnostic parameter called
PAST_ERROR (PastError in Diagnostics Explorer). The value of PastError is updated when the
Logic Solver finishes power-up testing following a fatal error. Persistent fatal errors are expected
to cause the same condition to be detected when the Logic Solver begins running its continuous
diagnostic tests. The outcome is another reset. When a Logic Solver detects the same fatal error
on two back-to-back resets, it enters a reduced startup state where SIS modules do not execute
and outputs cannot be powered On. The Logic Solver’s Status is “Not Operational” and
DiagStatus is “Persistent Fatal Error After Powerup.”
A simplex Logic Solver copies its diagnostic parameter PastError into its parameter FailedAlerts
when the fatal error persists after power-up tests complete. Immediately after the fatal error is
detected a Comm error occurs, which becomes inactive when power-up tests complete. At this
time the Failed alarm becomes active.
A redundant Logic Solver behaves differently. PastError is not copied from the Standby Logic
Solver into FailedAlerts because the Active Logic Solver continues to operate. The Logic Solver
has not failed; only the Standby has failed. Note that the Standby may have been the Active Logic
Solver at the time the error occurred. A redundant Logic Solver has a Maint alarm due to the
Standby partner not being available. The Maint alarm occurs immediately after the fatal error.
Note: Persistent fatal errors generally require a hardware repair. The hardware must be
returned to Emerson for repair. Before returning the hardware, perform a manual reset of the
affected Logic Solver using Diagnostics Explorer. If the error continues to be present after
power-up tests complete, which is expected, please contact the Global Service Center (GSC)
for technical support prior to contacting Customer Service for a Material Return Tracking (MRT)
number. The GSC will help determine the necessary action and forward the call to Customer
Service if needed. For contact information, visit:
http://www.emersonprocess.com/systems/support/ratecard.htm
The PastError parameter retains the reason for the most recent fatal error. PastError clears
(returns to GOOD) the next time a reset occurs that is not due to an error condition, for example,
a manual reset is done.
The following table summarizes the evidence and action required when the various classes of
errors occur in simplex and redundant Logic Solvers. The table shows the state of alarm and
diagnostic parameters approximately five minutes after the error is detected.
OW350_R1007 163
Summary of the Evidence of Logic Solver Errors and the Action Required
SIMPLEX LOGIC SOLVER REDUNDANT LOGIC SOLVER
ERROR EVIDENCE ACTION EVIDENCE ACTION

TYPE
Non-Fatal, Inact-Unack Check Event Chronicle Inact-Unack alarm Check Event Chronicle
Momentary alarm (MAINT records to determine (MAINT or records to determine
or error condition. ADVISE) error condition and
ADVISE) Record error affected Logic Solver.
occurrence; report to Record error
Emerson if there is a occurrence; report to
repeat occurrence. Emerson if there is a
repeat occurrence.
Non-Fatal, Act-Unack Check _ALERTS Act-Unack alarm Check _ALERTS
alarm (MAINT parameter associated (MAINT or
Persistent or with alarm to determine ADVISE) parameter associated
ADVISE) error condition. with alarm to determine
Report error to error condition.
Emerson. Check _STATUS
parameters on both
Logic Solver to
determine the affected
Logic Solver.
Report error to
Emerson.
Fatal, Inact-Unack Restart the process at Inact-Unack Check PAST_ERROR
Momentary COMM _ALM the appropriate time. MAINT_ALM on Standby Logic
Solver to determine
Check PAST_ERROR error condition.
on Logic Solver to
determine error Report error to
condition. Emerson.
Report error to
Emerson.
Fatal, Act-Unack Check Act-Unack Check PAST_ERROR
Persistent FAILED_ALM on Standby card to
FAILED _ALERTS on MAINT _ALM, determine error
Act-Unack SLS or PAST _ERROR MAINT _ALERTS condition.
MAINT_ALM, on Logic Solver to
MAI NT_ALE determine error includes “Partner Do a manual reset of
RTS includes condition. Not Available” and Standby card; replace
'”Card Not Fully “Card Not Fully card if necessary.
Operational.” Do a manual reset of
Logic Solver, replace if Operational.” Report error to
STATUS (Logic necessary. STATUS Emerson.
Solver) is (Standby card) is
Report error to
“Not Emerson. “Not Operational.”
Operational.” DIAG _STATUS
DIAG_STATUS on Standby card
on Logic Solver includes
includes “Persistent Fatal
“Persistent Error After
Fatal Error After Powerup.”
Powerup.”
164 OW350_R1007
Explanation of Terms in the preceding table
Non-Fatal – The error is not safety-critical and results in a notification action only.
Fatal – The error causes a reset of the Logic Solver to de-energize outputs on that unit. For a
simplex Logic Solver, final elements in the field are commanded to the tripped state. For a
redundant Logic Solver, the affected unit resets, which results in the partner being the Active unit,
but final elements in the field are not affected.
Momentary – The error condition is active briefly, then clears.
Persistent – The error condition remains active indefinitely.
Inact-Unack – The alarm condition is inactive, but the alarm has not been acknowledged.
Act-Unack – The alarm has not been acknowledged and the alarm condition is still active.
Report the error to Emerson – Most, but not all, errors should be reported to Emerson. Some
conditions are not errors but advisory alerts and can be cleared by an action such as a
configuration change or reconcile/load. Refer to the "Logic Solver Diagnostic Parameters” topic in
the Ovation SIS User Guide prior to reporting a diagnostic condition. Momentary, non-fatal
conditions should be reported only when the same condition has occurred multiple times.
Please report actual errors by contacting technical support at:

http://www.emersonprocess.com/systems/support/ratecard.htm
Maximum fault detection time
The cycle time for continuous diagnostics varies. Some faults are detected within one millisecond
of occurrence. Some are detected at a 50-millisecond diagnostic cycle time, which is independent
of the configured Logic Solver scan rate for SIS modules; others require the condition to be
present for multiple 50-millisecond cycle times.
The maximum fault detection time for a fatal error is eight diagnostic scan cycles or 400
milliseconds. This means the input to output response time of the SIF can increase no more than
400 milliseconds due to the presence of a fault.
Fault detection time using main processor comparison diagnostics is a function of the configured
Logic Solver scan rate for SIS modules. At the slowest scan rate of 200 milliseconds, detection
time is still within 400 milliseconds.
The longest diagnostic cycle times in the Logic Solver are related to memory testing. A failed
memory test results in a fatal error within one hour of the memory error occurrence. However, if a
process demand occurs after a memory failure but before detection of the memory failure,
another diagnostic, such as the task checkpoint monitor or main processor comparison test,
indirectly detects the memory error within the 400 milliseconds.
OW350_R1007 165
5.9.3 Proof testing the Logic Solver
Logic Solvers must be proof tested periodically to ensure there are no dangerous faults present
that are not being detected by continuous runtime diagnostics. A manual proof test for a Logic
Solver is initiated from an Ovation workstation and causes the Logic Solver to go through reset
and power-up testing. Proof testing of Logic Solvers can also be done automatically.
Immediately following successful power-up testing there are no known dangerous faults present.
Choose the proof test interval for a Logic Solver based on the associated SIF requiring the
shortest proof test period to achieve the required probability of dangerous failure for its Logic
Solver subsystem.
The Logic Solver proof test timer automatically counts the number of days since the last reset
occurred. The Logic Solver properties dialog in Ovation Studio has a Proof Testing tab for
entering the required proof testing interval and a reminder time value.
The Logic Solver provides an alert when the number of days since the last reset exceeds the
configured time. A reminder alert occurs a configured number of days before the “exceeds” alert
to assist maintenance personnel in the planning of manual tests.
There is an event record for the setting and clearing of proof test alerts. The proof test timer for a
redundant Logic Solver indicates the number of days since the last reset of the Active unit, which
always occurs earlier than the last reset of the Standby.
Automatic Tests
Automatic proof testing is available for redundant Logic Solvers only. The Proof Testing tab of the
Logic Solver properties dialog has an “Enable automatic proof test to run at reminder time” check
box (this check box is grayed-out for simplex Logic Solvers). When checked, the Logic Solver
performs the proof test when the number of days since the last reset reaches the configured time.
The test begins five minutes after the Logic Solver sets the reminder alert. In this case the
reminder alert informs the operator that a test will occur soon so that the Partner Not Available
alerts can be ignored after the test begins. At the time of automatic proof test:
 The Active Logic Solver starts the test by initiating a switchover to the Standby Logic Solver. If
the Standby Logic Solver is not available, the Active Logic Solver tries again in five minutes.
 After switchover the Standby card becomes Active and the new Standby card goes through
reset and begins power-up testing. There is no adverse impact to the running process. An
event record confirms successful power-up testing.
 The new Active Logic Solver still has a proof test due, so it waits for its partner to become
available then initiates a switchover. When the partner has become the Active Logic Solver,
the new Standby Logic Solver goes through reset and power-up testing. An event record
confirms successful power-up testing of the Logic Solver.
166 OW350_R1007
Manual Tests
The following procedure should be used for manual proof testing of the Logic Solver.
Simplex Logic Solver

1. Initiating a manual reset on a simplex Logic Solver results in all outputs being de-energized. If
you must proof test a simplex Logic Solver online, you need to temporarily bypass or block
final elements and provide manual supervision.
2. The Logic Solver must be Unlocked to initiate a manual reset. Select the Logic Solver under
SIS Network in Diagnostics Explorer. If the value of the Locked parameter is Yes in the
contents pane, right-click on the Logic Solver and select Unlock. Click Confirm on the SIS
Write confirmation dialog.
3. Right-click on the Logic Solver and select “Force Reset on Active.” Clicking Confirm on the
confirmation dialog results in all outputs being deenergized.
4. The Logic Solver goes through power-up testing and returns to the configured state. The
proof test timer resets to 0. There are two event records, one for the user reset command and
one from the Logic Solver confirming that power-up tests completed successfully.
Redundant Logic Solver
The procedure for a redundant Logic Solver allows the proof test to be done online without
adversely affecting the running process.
1. The Logic Solver must be Unlocked to initiate a manual reset. Select the Logic Solver under
SIS Network in Diagnostics Explorer. If the value of the Locked parameter is Yes in the
contents pane, right-click on the Logic Solver and select Unlock. Click Confirm on the SIS
Write confirmation dialog.
2. Right-click on the Logic Solver and select “Force Reset on Standby.” Click Confirm on the
confirmation dialog.
3. Wait several minutes for the Standby Logic Solver to complete power-up tests and become
configured by the Active Logic Solver. The Partner Not Available maintenance alert goes
inactive when the Standby Logic Solver is fully configured.
4. Right-click on the Logic Solver and select “Switchover.” Click Confirm on the confirmation
dialog.
5. The previously reset Standby Logic Solver becomes the new Active Logic Solver and the new
Standby Logic Solver goes through power-up tests and is configured by the new Active Logic
Solver. The proof test timer is 0. There are four event records, two for the user reset and
switchover commands and two for the Logic Solvers, confirming that power-up tests
completed successfully.
OW350_R1007 167
5.9.4 Making online scaling changes in HART transmitters
A special procedure is recommended if you need to make an online change to the upper or lower
range value in a HART transmitter connected to a channel of the Logic Solver. The Logic Solver
does not automatically synchronize the scaling between the HART device and the associated
LSAI algorithm in the SIS module. Scaling must be configured independently.
In the SIS module, scaling is set using the TPSC and BTSC parameters in the LSAI algorithm. To
change the scaling in the HART device you must use AMS or a HART Communicator. Loading
the Logic Solver or changing the scaling in the LSAI algorithm at runtime does not affect scaling in
the HART device. Similarly, changing the upper or lower range value in the HART device does
not cause a change to TPSC and BTSC parameters in the LSAI algorithm.
If an online scaling change is made in the HART device, there is a step change in the OUT
parameter of the associated LSAI algorithm, and the value is incorrect until an equivalent manual
change is made to the scaling parameters of the LSAI algorithm. When making online scaling
changes, a standard procedure should be followed to prevent spurious trips and to ensure that
matching scaling is achieved. The recommended procedure is as follows.
1. Bypass the LSAVTR algorithm input connection from the OUT parameter of the AI algorithm
assigned to the HART device’s channel using the LSAVTR dynamo on the process display in
Ovation Operate. If the TRSTS parameter of the LSAVTR algorithm becomes “Trip Inhibited”
as a result of the bypass, manually monitor the SIF while the input is bypassed.
2. Make the scaling change in the HART transmitter using AMS.
3. Use Control Studio Online to make the equivalent change to the TPSC and BTSC parameters
of the associated LSAI algorithm.
4. Check to see that the OUT parameter of the LSAI algorithm has the expected online
engineering units value.
5. Remove the bypass.
6. Reconcile the change in the TPSC and BTSC parameters to the configuration database.
168 OW350_R1007
5.10 Resolving common installation problems
This table identifies common installation problems, their causes, and what you can do to resolve
these issues.
Common installation problems
PROBLEM POSSIBLE SOLUTION
Ovation does not start. Determine if Ovation is running.

Check for errors that occurred during the installation.
During installation, a download was not performed or a download
failed.
Verify that the firewall is not causing problems.
Verify that the DDB protocols are properly configured.
Ovation Developer Studio cannot Ensure that the administrator controls the Ovation power tools service
connect to the local database. for the server.
Determine that the Ovation Developer Studio is properly licensed.
System is showing security Check the System Event Viewer.
related errors.
Verify that the appropriate messaging queues are present.
OW350_R1007 169
5.10.1 To determine if Ovation is running
If Ovation fails to start after it has been installed, determine if Ovation is running.
1. Right-click the task bar and select Task Manager.

2. Verify that OvationStartup.exe and init_shc.exe are running.
5.10.2 To check for errors that occurred during the installation

1. Open Windows Explorer.
2. Navigate to the Ovation install directory, typically C:\ovation.
3. Navigate to the logs directory.
4. Search the folder corresponding to the date you installed Ovation.
5. Double-click to open the appropriate log files to check for errors.
Log files
STANDALONE SECURITY DATABASE SERVER BASE STATION AND OPERATOR

SERVER STATION
SECURITY.INSTALL.ON DATABASE.INSTALL.ON BASE.INSTALL.ONINSTALL.htm

INSTALL.htm INSTALL.htm
SECURITY.UPDATE.ON DATABASE.UPDATE.ON BASE.UPDATE.ONREBOOTED.htm
REBOOTED.htm INSTALL.htm
DATABASE.UPDATE.ON STATION.INSTALL.ONREBOOTED.htm
REBOOTED.htm
DATABASE.INSTALL.ON STATION.INSTALL.ONINSTALL.htm
REBOOTED.htm
ORACLE.INSTALL.ON
INSTALL.htm
ORACLE.UPDATE.ON
REBOOTEd.htm
6. Check for errors and verify that the last log entry is labeled Done.
170 OW350_R1007
5.10.3 To determine if communication has failed (load and downloads)
Ovation may not start if a download was not performed or the download failed during the
installation.
1. Verify that ssquery is running on the computer that you want to download the software to.
If it is not running, enter the following at the Command Prompt:
C:\ovation\ovationbase\ssquery.exe
2. Verify that the portsrv process is installed and running on the computer that you want to
download the software to.
3. Select Start > Administrative Tools > Services. This path may be different on a Windows
2008 server system.
4. Double-click NobelNet Portmapper for TCP.
5. Change the Startup Type to Automatic.
6. Press the Start button.
7. Press OK.
8. Try the Download function again. If Ovation is not installed, enter the following at the
Command Prompt:
C:\ovation\ovationbase\portinst.exe rogui install auto tcp
9. Reboot the computer.
OW350_R1007 171
To verify the firewall configuration

1. On the Database Server machine that you are downloading to, choose Start > Control Panel
> Windows Firewall.
Note: Paths may differ on Windows 7 systems and on Windows 2008 Server systems.
2. To test, set the firewall to Off. Choose OK and download again.

3. If it still fails, it is not a firewall problem. Turn the firewall back On.
4. If the download succeeds, you need to determine what to add to the firewall exception list.
Contact your Emerson Customer Service Representative.
To verify the DDB Protocols configuration

1. Select Start > Control Panel.
2. Right-click Network Connections and select Open. This path may be different on a Windows
2008 server system.
3. Select the Network Interface that communicated with your Ovation Network.
4. Select DDB Protocol > Properties.
5. Verify that there are no zero values in the fields.
6. If there are zero values, go to the Database Server. Download the drop and reboot the drop.
5.10.4 If the Ovation Developer Studio does not start and connect to the Local
Database Server
1. Ensure that the Administrator controls the Ovation Power Tools Service for the Server.
2. Select Start > Administrative Tools.
3. Double-click the Services icon. The Services window appears.

4. Check to see if OvPtSvr is running. If it is not, perform the following:
a) Select OvPtSvr.
b) Right-click and select Start.
The Ovation Server is now ready to run.
5. Check to determine if the Developer Studio is properly licensed. (See Ovation Developer
Studio User Guide.)
172 OW350_R1007
5.10.5 Examples of security related errors
To verify that the HMI is logging on to the domain:
1. Select Start > Administrative Tools > Event Viewer.
2. Scan the Application, Security, and System logs for errors related to DNS.
3. Verify DNS settings for the network card connected to the Ovation network.
4. Select Start > Run > cmd.exe.
5. Type ipconfig /all and select Enter.
6. A list appears for each card. Scan to the card connected to the Ovation network. Verify that
the DNS servers are set to the Primary Domain Controller and optionally, to the Redundant
Domain Controller.
7. If the DNS Server is set incorrectly, refer to To Reconfigure DNS Client Settings.
To verify the presence of appropriate messaging queues:

1. On the Primary Domain Controller, select Start > Administrative Tools > Computer
Management.
2. If the drop is a Base Station, Operator Station, or Database Server, verify that you have an
Ovation item.
If the drop is a Primary Domain Controller, verify that you have the ovrecvadmin and
ovsyncadmin items.
3. If you do not have these items, re-install Ovation.
OW350_R1007 173
5.11 What are the processor module status LEDs for the Controller?
The Controller processor module (left side of Controller) provides nine indicator LEDs that display
status information about the interface between the Controller and the Ovation network.
There is a green power indicator (labeled P) and a pair of green and amber LEDs for each
Ethernet port (labeled N1, N2, N3, and N4). The green power indicator lights when the Processor
module is powered. Each Ethernet network port has two indicator LEDs (green and amber).
The green indicator is the Link Integrity/Power LED and lights when the port is receiving power
and flashes slowly when the module is linked with the network through that port.
The amber indicator displays Link Activity status and flashes when the module is receiving or
transmitting data on that port.
Controller Module IOIC Module
Figure 48: Processor module status LEDs
174 OW350_R1007
Processor module status LEDs
LED ME ANING ON OFF BLINKING
P Power Lights green when Unlit when module N/A

module is powered. is not powered.
N1 Ethernet port Port is receiving Port is not receiving Module is linked to
green LED power. power. network through the
(Link Integrity/Power LED) port.
Ethernet port N/A N/A Module is receiving or
amber LED transmitting data on
(Link activity status) the port.
Ethernet port Port is receiving Port is not receiving Module is linked to
N2
OW350_R1007 175
5.12 What are the I/O Interface module status LEDs for the Controller?
5.12 What are the I/O Interface module status LEDs for the
Controller?
The Controller I/O interface module (right side of the Controller) provides 10 indicator LEDs that
display status information about the interface between the Controller and the I/O devices.
The indicators can be continually lit, blinking, or off. All of the I/O status indicators are green, with
the exception of the Error indicator. The Error indicator is red.
Controller Module IOIC Module
Figure 49: I/O Interface module status
176 OW350_R1007
5.12 What are the I/O Interface module status LEDs for the Controller?
I/O interface module LED descriptions
STATUS
LABE L ME ANING ON (SOLID) OFF BLINKING
P Power Controller Controller not N/A

powered. powered.
Cm Comm. Communications No commands being Commands being received from
hung. received from the the Processor module.
Processor module.
Ct Control Controller acting Controller not Controller acting as secondary.
as primary. operational, in boot-
up, or cleared.
A Alive Alive Alive timer timed out. N/A
(under hardware
control).
E Error Performing Application firmware An error is indicated. Read error
diagnostics running. No errors. code from node LEDs or GMD.
during boot
sequence.
Node LED
O1 local Ovation All I/O cycles No I/O cycles are Some or all I/O cycles are failing
#1 (port L1) succeeding (with being attempted (with (with "E" LED off).
"E" LED off). "E" LED off).
O2 local Ovation All I/O cycles No I/O cycles are Some or all I/O cycles are failing
#2 (port L2) succeeding (with being attempted (with (with "E" LED off).
R3 Port R3 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
succeeding (with being attempted (with (with "E" LED off).
R4 Port R4 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
Q5 Port Q5 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
A Controller fault is indicated when the red E LED is blinking. In this state, the Node LEDs (01, 02,
R3, R4, and Q5) blink the actual error code as two separate binary numbers followed by a 3-
second pause (all node LEDs off, 00000). This sequence repeats as long as the error state
persists. Open the GMD (General Message Display) for an actual readout of the error code in
hexadecimal.
For Ovation 3.5 and later releases, the fault codes are part of Ovation software and are displayed
in the Ovation System Viewer application. Refer to the Operator Station User Guide for additional
information.
OW350_R1007 177
5.13 Troubleshooting Routed Network problems
5.13 Troubleshooting Routed Netw ork problems
Troubleshooting connectivity problems in a routed network can be intimidating. If a device on

network A (one side of the router) cannot communicate with a device on network B (the other side
of the router) the following basic steps are suggested:
1. From the router, ping the IP address of the network A device. If this does not work, check
network connections, IP address and subnet mask assignment of the network A device
adapters.
2. From the router, ping the IP address of the network B device. If this does not work check
network connections, IP address and subnet mask assignment of the network B device
adapters.
3. From the network A device, ping the IP address of the network B interface of the router. If
there is no response, check to make sure the network A device has a default or static route
configured (this can normally be done via the "netstat -rn" command). If Steps 1 and 2 are
successful, and Step 3 fails, it is probable that the default/static route was not properly added
to the network A device.
4. From the network B device, ping the IP address of the network A interface of the router. If
there is no response, check to make sure the network B device has a default or static route
configured. If Steps 1, 2, and 3 are successful, and Step 4 fails, it is probable that the
default/static route was not properly added to the network B device.
5.14 I/O module troubleshooting
Testing to terminations or the field is a two-person process: one person for the termination/field
side to apply inputs or observe outputs, and another person on the system operator/engineer
work-stations.
Analog Input modules
1. Analog Input (1C31113), l4-Bit Analog Input (1C31224) and High Speed Analog Input
(5X00070) (see page 185).
 Diagnostic LEDs for the Analog Input module (13-Bit) (see page 185).
 Diagnostic LEDs for the Analog Input module (14-Bit) (see page 186).
 Diagnostic LEDs for the High Speed Analog Input module (14-Bit) (see page 186).
2. HART Analog Input (5X00058) and Isolated HART Analog Input (5X00106) (see page 187).
 Diagnostic LEDs for HART Analog Input modules (see page 187).
 Diagnostic LEDs for HART High Performance Analog Input modules (see page 188).
3. RTD Input (1C31161) and 8-Channel RTD Input (5X00119) (see page 189).
 Diagnostic LEDs for the RTD module (4 Channel) (see page 189).
 Diagnostic LEDs for the RTD module (8-channel) (see page 189).
178 OW350_R1007
Analog Output modules
1. Analog Output (1C31129) (see page 191).

 Diagnostic LEDs for Analog Output modules (see page 191).
2. HART Analog Output (5X00062) and HART High Performance Analog Output (5X00167) (see
page 192).
 Diagnostic LEDs for the HART Analog Output module (see page 192).
 Diagnostic LEDs for the HART High Performance Analog Output module (see page 193).
Digital Input modules
1. Digital Input (1C31107) and Compact Digital Input (1C31232) (see page 198).
 Diagnostic LEDs for Digital Input modules (see page 199).
 Diagnostic LEDs for Compact Digital Input modules (see page 199).
2. Contact Input (1C31142) and Compact Contact Input (1C31234) (see page 199).
 Diagnostic LEDs for Contact Input modules (see page 199).
 Diagnostic LEDs for Compact Contact Input modules (see page 200).
3. Sequence of Events (1C31157) and Compact Sequence of Events (1C31233) (see page
200).
 Diagnostic LEDs for the Sequence of Events Contact Input field interface module (see
page 201).
 Diagnostic LEDs for the Compact Sequence of Events Digital Input module (see page
201).
 Diagnostic LEDs for Enhanced Compact Sequence of Events input module 5X00357 (see
page 202).
Digital Output modules
1. Digital Output (1C31122) (see page 206).

 Diagnostic LEDs for Digital Output modules (see page 206).
 Diagnostic LEDs for the 24VDC HSDO module (see page 207).
2. Relay Output Electronics Module (1C31219) (see page 208).
 Diagnostic LEDs for the Relay Output module (see page 208).
OW350_R1007 179
Specialty modules
1. Loop Interface Controller (1C31174) (see page 213).

 Diagnostic LEDs for the Loop Interface module (see page 213).
2. Pulse Accumulator (1C31147) (see page 214).
 Diagnostic LEDs for the Pulse Accumulator module (see page 214).
3. Servo Driver (1C31199) (see page 215).
 Diagnostic LEDs for the Servo Driver module (see page 215).
4. Speed Detector (1C31189) (see page 216).
 Diagnostic LEDs for the Speed Detector module (see page 216).
5. Valve Positioner (1C31194) (see page 217).
 Diagnostic LEDs for the Valve Positioner module (see page 217).
 Diagnostics for the Valve Positioner module (see page 218).
6. Serial Link Controller (lC3ll66) (see page 221).
7. Media Attachment unit and Remote Node Controller (see page 221).
180 OW350_R1007
5.14.1 Analog Input modules
Analog Input module (13 bits) - (Legacy product) - provides an interface to eight galvanically
isolated analog inputs with sampling rates of approximately 10 time/sec. Several voltage and
current configurations are available including cold junction compensation for thermocouple inputs.
1
Analog Input subsystems (13-bit)
RANGE CHNLS ELECTRONICS PERSONALITY

MODULE MODULE
± 20mV 8 1 1C31116G01
1C31113G01
±50mV 8 1 1C31116G01
1C31113G02
± 100mV 8 1 1C31116G01
1C31113G03
± 20mV Compensated (Thermocouple) 3 1 1C31116G04
8 1C31113G01
8 1C31113G02

8 1C31113G03
± 1 VDC 8 1 1C31116G01
1C31113G04
± 5 VDC 8 1 1C31116G01
1C31113G05
± 10 VDC 8 1 1C31116G01
1C31113G06
0-20 mA Field powered 8 1, 2 1C31116G02

1C31113G05
(4-20 mA Field powered can also be selected in the
I/O Builder for Solaris applications; card is
configured appropriately)
0-20 mA Locally powered 8 1, 2 1C31116G03
1C31113G05
(4-20 mA Locally powered can also be selected in
the I/O Builder for Solaris applications; card is
configured appropriately)
1
This module configurations is CE Mark Certified.
3
This module configurations is CE Mark Certified (Non-EMC Cabinet).
3
A ninth logical channel (does not connect to a device) is provided when using the Analog Input module
with temperature sensor. This ninth point is needed for the CJ Compensation field of the Point Builder
Instrumentation Tab when defining the eight other thermocouple points for the AI module. (See Ovation
Developer Studio User Guide (for Windows).
OW350_R1007 181
Analog Input module (14 bits) - provides an interface to eight galvanically isolated analog inputs
with a minimum sampling rate of 10 time/sec. A low cost 4-20 mA current input is available along
with a 1V voltage input (legacy) configuration.
Analog Input subsystems (14-bit)
RANGE CHANNELS ELECTRONICS PERSONALITY

MODULE MODULE
1 8 1 1C31227G01
4 - 20mA, Field or Locally powered 1C31224G01
± 1 VDC 8 1 1C31227G02
1C31224G02
1
The 4-20mA Configuration is CE Mark certified.
Analog Input High Speed module (14-Bit) - provides an interface to eight galvanically isolated
analog inputs with sampling rates of medium speed (16/20 time/sec.) or high speed (50/60
times/sec.). Several voltage and current input configurations are available including cold junction
compensation for thermocouple inputs.
High Speed Analog Input subsystems (14-bit )

MODULE MODULE
4 - 20mA, Field or Locally powered 8 1,2 1C31227G01

5X00070G01
± 100mV, ± 250mV, ± 1V 8 1,2 1C31227G02
5X00070G02
± 5V, ± 10V 8 1,2 1C31227G02
5X00070G03
± 1mA 2 wire local powered 8 1,2 1C31116G03
5X00070G02
± 1mA 4wire field powered 8 1,2 1C31116G02

5X00070G02
± 20mV,  50mV,  100 (Thermocouple) 8 1 1C31116G04

5X00070G04
± 20mV,  50mV,  100 (Thermocouple) 8 2 1C31116G04

5X00070G05
1
This module configuration is CE Mark Certified.
2
This module configuration is CE Mark Certified (Non-EMC Cabinet).
182 OW350_R1007
HART Analog Input module - provides an interface for eight galvanically isolated HART field
devices with 4-20 mA current loop analog inputs (common reference). In addition to the analog
inputs, digital information can be exchanged between HART compliant devices and the Controller.
1
HART Analog Input subsystems (16-bit)

MODULE MODULE
4-20 mA loop powered (2 wire) or active source 8 1 5X00059G01

5X00058G01
(4 wire)
1
HART High Performance Analog Input module - provides an interface for eight galvanically
isolated HART field devices with 4-20 mA current loop analog inputs. In addition to the analog
inputs, digital information can be exchanged between HART compliant devices and the Controller.
HART High Performance Analog Input subsystems (14-bit)

MODULE MODULE
1 8 5X00106G01 5X00109G01
4-20 mA
or
5X00109G02
(Ovation
releases 3.4 and
later)
2 8 5X00106G02 5X00109G01
4-20 mA (Reduced radiated emissions).
or
5X00109G02
(Ovation
releases 3.4 and
later)
1
2
This module configuration is CE Mark Certified (Non-EMC Cabinet).
OW350_R1007 183
RTD module (4 Channel) - provides an interface to four galvanically isolated Resistance

Temperature Detectors. Several 3 and 4 wire RTD types are supported. A 50/60 Hz filtered
configuration is available for CE Mark applications.
RTD (4 Channel) module subsystems
RANGE CHANNELS ELECTRONICS PERSONALIT

MODULE Y MODULE
All 4 1C31161G01 1C31164G01

All (for 50/60 Hz filtered inputs and CE Mark certified 4 1 1C31164G02
1C31161G02
systems) 1
1
Configuration 1C3116G02 / 1C31164G02 is CE Mark Certified.
RTD module (8 Channel) - provides an interface to eight galvanically isolated Resistance

Temperature Detectors. Several 3 and 4 wire RTD types are supported.
1
RTD module (8-Channel) subsystems
CHANNELS ELECTRONICS MODULE PERSONALITY MODULE
8 1 5X00121G01
5X00119G01
8 2 5X00121G01
5X00119G02
1
2
This module configuration is CE Mark Certified (Non-EMC cabinet).
16 Channel 4-20mA Analog Input module - provides an interface between the Ovation
Controller and 16 field devices that use a 4-20mA current loop. Up to 16 4-20mA (2-wire or 4-
wire) transmitters can be connected per module.
16 Channel 4-20mA Analog Input subsystems
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY

MODULE MODULE
16 Channel 4-20mA Analog Input, 2- 16 5X00501G01 5X00502G01

wire and 4-wire
16 Channel 4-20mA Analog Input, 2- 16 5X00501G01 1X00692H01
wire only
184 OW350_R1007
Analog Input modules testing
13-Bit Analog Input (1C31113), l4-Bit Analog Input (1C31224) and High Speed Analog Input
(5X00070):
Apply input signal with current loop (either self or field powered) or voltage source and verify at
min, mid, and max scale (per database, via termination list)by monitoring value in system
graphics or engineering station.
Diagnostic LEDs - (AI-13)
Logic card LED indications
LED DESCRIPTION
P (green) Power OK LED. Lit when the +5V power is OK.

C (green) Communication OK LED. Lit when the Ovation Controller is communicating with the
module.
E No LED.
I (Red) Internal Error LED. Lit whenever there is any type of error with the module except for a
loss of power. Possible causes are:
 Module is initialization.
 I/O Bus timeout has occurred.
 EPROM checksum error or static RAM error.
 PSD generator malfunction.
 Module reset.
 Module input power (+24V) not OK.
 Module is uncalibrated.
 Forced error has been issued by the Controller.
1 (Green) Channel error. Lit whenever there is an error associated with a channel or channels.
Possible causes are:
 Positive overrange: Input voltage greater than +125% of full scale value.
 Negative overrange: Input voltage less than -125% of full scale value.
 Broken current loop input or blown fuse for module configured as current input.
 Auto calibration readings out of range.
2 (Green) Same as LED # 1.
9 No LED.
10 No LED.
11 No LED.
12 No LED.
OW350_R1007 185
LED DESCRIPTION
13 No LED.
14 No LED.
15 No LED.
16 No LED.
Diagnostic Logic card LEDs - (AI-13, AI-14 & HSAI)
LED DESCRIPTION

C (green) Communication OK LED. Lit when the Ovation Controller is communicating with the module.
E No LED.
I (Red) Internal Error LED. Lit whenever there is any type of error with the module except for a loss
of power. Possible causes are:
 Module initialization is in progress.
 Internal hardware error.
 Module reset
 Forced error has been received from the Controller.
 Communication between the Field and Logic boards failed.
1 - 8 (Red) Channel error. Lit whenever there is an error associated with a channel or channels.
 Positive overrange: Input voltage greater than +121% of full scale value (for modules
configured as voltage input).
 Negative overrange: Input voltage less than -121% of full scale value (for modules
 Current loop out of range
 Calibration readings out of range.
9 - 16 No LED.
Diagnostic LEDs - (HSAI)
LED DESCRIPTION

module.
E No LED.
I (Red) Internal Error LED. Lit whenever there is any type of error with the module except for a
186 OW350_R1007
LED DESCRIPTION
 Register, static RAM, or FLASH checksum error.
 Module reset
1 (Green) Channel error. Lit whenever there is an error associated with a channel or channels.
 Positive overrange: Input voltage greater than +121% of full scale value (for modules
 Negative overrange: Input voltage less than -121% of full scale value (for modules
 Input current less than 2.5mA or blown fuse (for module configured as current input).
 An overrange (greater than 24.6mA) of full scale is present (for modules configured
as current input).
 Self calibration readings out of range.
9 No LED.
10 No LED.
11 No LED.
12 No LED.
13 No LED.
14 No LED.
15 No LED.
16 No LED.
HART Analog Input modules testing
HART Analog Input (5X00058) and Isolated HART Analog Input (5X00106):
Apply input signal with current loop (either self or field powered) or voltage source and verify at
min, mid, and max scale (per database, via termination list).
OW350_R1007 187
Diagnostic Logic card LEDs - (HAI)
LED DESCRIPTION

C (green) Communication OK LED. Lit when the Ovation Controller is communicating with the module.
E (Red) External Error LED. Illuminated upon loss of external auxiliary (field) power, as indicated by
the loss of normal transitions of the EOC (end-of-convert) signal.
I (Red) Internal Error LED. Lit whenever there is any type of error with the module except for a loss
of power. Possible causes are:
 Module reset.
1 -8 (Red) LEDs 1 through 8 are used to indicate HART communication activity.
When a HART message is sent, the LED for that particular channel is illuminated.
When the HART response is received correctly, the LED is extinguished.
When all is normal, that is, messages and responses are properly exchanged, a single LED
blink is observed on the module’s front cap.
 If a HART message is sent and no response is received, the HART Analog Input module
exclusive-OR’s the channel LED display with hex code 0xFF, resulting in all channel LEDs
being illuminated except for the selected channel. For example, if the HART Analog Input
module sent a HART message to device on channel 2, but the device was not connected
to channel 2, the module would first illuminate LED 2 (all seven other channel LEDs
extinguished). The module would then extinguish LED 2 and flash the other seven channel
LEDs. This status indicates that the module sent a HART message on channel 2 and did
not receive a valid response message after the initial message attempt or after any of the
subsequent message retries.
9 - 16 No LED.
188 OW350_R1007
Diagnostic Logic card LEDs - (HHPAI)
LED DESCRIPTION

module.
E No LED.
I (Red) Internal Error LED. Illuminated whenever there is any type of error within the module
except for a loss of external auxiliary power. Possible causes are:
 The Controller sets the module’s Force Error bit.
 Communications with the Controller is lost.
 The module is not calibrated.
 Flash memory, EE memory or RAM diagnostic failure.
1 - 8 (Red) The eight channel LEDs serve two functions. LEDs 1-8 are used to indicate the
firmware state during module startup and are then used to indicate HART
communications activity and analog input health during normal module operation.
After module configuration, the bank of eight channel LEDs (LEDs 1-8) is used to
indicate HART communications activity and the health of the analog input. If the
Analog Input for the associated analog input channel is healthy (bit 15 set in the point
data word), then the LED is on. If the analog input channel is bad, then the LED is off.
When a HART message is sent and received correctly, the LED blinks off for 100
msec if the analog input is healthy. When a HART message is sent and received
incorrectly, the LED blinks off for 400 msec if the analog input is unhealthy.
9 - 16 No LED.
RTD Input modules testing
RTD Input (1C31161) and 8-Channel RTD Input (5X00119):
Decade resistor is attached in 2, 3 or 4-wire configuration (per point configuration). Decade box is
used to apply inputs at min, mid, and max scale (per database, via termination list).
Diagnostic Logic card LEDs - (RTD-4)
LED DESCRIPTION

module.
E No LED.
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1) of the Configuration Register is
set, or when a timeout of the watchdog timer occurs when the Controller stops
communicating with the module.
Also lit when the IMOK signal is false (0) indicating failures of part or all of the logic
common to the input channels.
1 - 4 (Red) Channel #1 - 4 error. Lit whenever there is an error associated with Channel 1 - 4.
5 - 16 No LED.
OW350_R1007 189
Diagnostic Logic card LEDs - (RTD-8)
LED DESCRIPTION

module.
E No LED.
I (Red) Internal Fault LED. Lit whenever there is any type of error with the module except to a
 I/O Bus time-out has occurred.
 Module reset.
1 - 8 (Red) Channel #1 - 8 error. Lit whenever there is an error associated with a channel or
channels. Possible causes are:
 Positive overrange.
 Negative overrange.
 Communication with the channel has failed.
9 - 16 No LED.
5.14.2 Analog Output modules
Analog Output module - provides an interface to four galvanically isolated analog outputs using
12-bit digital-to-analog converters.
Analog Output subsystems

MODULE MODULE
0-5 Volts DC 4 1 1C31132G01

1C31129G01
0-10 Volts DC 4 1 1C31132G01
1C31129G02
0-20 mA with Diagnostics 4 1 1C31132G01
1C31129G03
(4-20 mA with Diagnostics can also be selected in
the I/O Builder for Solaris applications; card will be
configured appropriately).
0-20 mA without Diagnostics 4 1 1C31132G01
1C31129G04
(4-20 mA without Diagnostics can also be
selected in the I/O Builder for Solaris applications;
card will be configured appropriately).
4-20 mA with Diagnostics (For Redundant 4 2 1C31132G02
1C31129G05
applications).
1
This module configurations is CE Mark Certified.
2
For Redundant applications using Windows Ovation 3.2 and above.
190 OW350_R1007
HART Analog Output module - provides an interface for eight galvanically isolated HART field
devices using 4-20 mA current loop analog outputs (common reference). In addition to the analog
outputs, digital information can be exchanged between HART compliant devices and the
Controller.
1
HART Analog Output subsystems (14 bit)
RANGE CHANNELS ELECTRONICS MODULE PERSONALITY MODULE
4-20 mA 8 1 5X00063G01
5X00062G01
1
This module configuration is CE Mark certified.
HART High Performance Analog Output module - provides an interface for four galvanically
isolated HART field devices using 4-20 mA current loop analog outputs. In addition to the analog
outputs, digital information can be exchanged between HART compliant devices and the
Controller.
1
HART High Performance Analog Output subsystems (14-bit)
RANGE CHANNELS ELECTRONICS PERSONALITY MODULE

MODULE
4-20 mA 4 1 1X00188H01 (molded plastic cavity insert)

5X00167G01
4-20 mA 4 5X00167G01 5X00211G03 (Q-line migration)

1
Analog Output module testing
Analog Output (1C31129):
Monitor output with voltmeter or ammeter to verify at min, mid, and max scale (per database, via
termination list).
Analog Output modules
1. Analog Output (1C31129) (see page 191)

 Diagnostic LEDs for Analog Output modules (see page 191)
2. HART Analog Output (5X00062) and HART High Performance Analog Output (5X00167) (see
page 192)
 Diagnostic LEDs for the HART Analog Output module (see page 192)
 Diagnostic LEDs for the HART High Performance Analog Output module (see page 193)
OW350_R1007 191
Diagnostic Logic card LEDs - (AO)
LED DESCRIPTION

module.
E No LED.
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1) of the Configuration Register
is set.
Also lit when a timeout of the watchdog timer occurs when Controller stops
communicating with module.
1 - 4 (Red) Channel 1 - 4 error. Over-current or undercurrent indication.
 On groups 1, 2, 3, and 5, the LEDs are ON after power up until the module is
configured.
 On groups 1 and 2, the LED is ON for over-current output or loss of output D/A power.
 On group 3, and 5, the LED is ON for over-current/undercurrent output or loss of output
D/A power.
 Group 4 does not have diagnostic LEDs.
5 - 16 No LED.
HART Analog Output modules testing
HART Analog Output (5X00062) and HART High Performance Analog Output (5X00167)
Monitor output with voltmeter or ammeter to verify at min, mid, and max scale (per database, via
termination list).
192 OW350_R1007
Diagnostic Logic card LEDs - (HAO)
LED DESCRIPTION

module.
E (Red) External Error LED. Illuminated upon loss of external auxiliary (field) power, as indicated
by the loss of normal transitions of the EOC (end-of-convert) signal.
 EPROM, EE memory or RAM diagnostic failure.
1 - 8 (Green) After module configuration, the bank of eight channel LEDs (LEDs 1 through 8) is used to
indicate HART communication activity. When a HART message is sent, the LED for that
particular channel is illuminated. When the HART response is received correctly, the LED
is extinguished. Therefore, when all is normal, that is, messages and responses are
properly exchanged, a single LED blink is observed on the module’s front cap.
If a HART message is sent and no response is received, the HART Analog Output module
exclusive-OR’s the channel LED display with hex code 0xFF. This results in all channel
LEDs being illuminated except for the selected channel. For example, if the HART Analog
Output module sent a HART message to a device on channel 2, but the device was not
connected to channel 2, the module would first illuminate LED 2 (all seven other channel
LEDs extinguished). The module would then extinguish LED 2 and flash the other seven
channel LEDs. This status indicates that the module sent a HART message on channel 2
and did not receive a valid response message after the initial message attempt or after
any of the subsequent message retries.
9 - 16 No LED.
Diagnostic Logic card LEDs - (HHPAO)
LED DESCRIPTION

module.
E No LED.
 EPROM, EE memory or RAM diagnostic failure.
1 - 4 (Green) After module configuration, the bank of four channel LEDs (LEDs 1 through 4) is used
to indicate HART communication activity and the health of the analog outputs. If the
analog output for the associated analog output channel is healthy (no overcurrent or
undercurrent condition), then the channel LED will be ON. If the analog output channel
is bad (an overcurrent or undercurrent is present), then the channel LED will be off.
When a HART message is sent and received correctly, the channel LED blinks off for
100 msec if the analog output is healthy. When a HART message is sent and received
incorrectly, the channel LED blinks off for 400 msec if the analog output is healthy.
5 - 16 No LED.
OW350_R1007 193
5.14.3 Digital Input modules
Digital Input module - provides an interface for 16 current-sinking digital inputs using a
Personality module. Various input configurations are available.
1
Digital Input subsystems

MODULE MODULE
24/48 VAC/VDC Single-ended 16 1C31107G01 1C31110G01

Differential 16 1C31107G01 1C31110G02
125 VAC/VDC Single-ended 16 1C31107G02 1C31110G01

Differential 16 1C31107G02 1C31110G02
1
All module configurations listed in the table are CE Mark Certified.
Redundant Digital Input module – provides 16 digital channels to monitor the states (“0” or “1”)
of 16 field digital inputs. The module contains two voltage sensing circuits for each of the 16 I/O
channels located on the module. Redundant power for all 16 digital input channels is either
supplied by the Ovation auxiliary power supply or by an external 24V auxiliary power source. In
either situation, the redundant pair module shares a common 24VDC auxiliary power source.
Redundant Digital Input subsystems

MODULE MODULE
24 V (Single Ended) Digital Input current 16 5X00411G01 5X00414G01

sinking, IEC 61131-2 Compliant Type 1
digital Inputs.
Compact Digital Input module - provides a low cost interface for 16 current-sinking digital inputs
without requiring a personality module.
Compact Digital Input subsystems
1 CHANNELS ELECTRONICS PERSONALITY

RANGE
MODULE MODULE OR CAV ITY
2
INSERT
24/48 VDC Single-ended 16 1C31232G01 1C31238H01 (molded

plastic cavity insert)
24 VAC/VDC Differential 16 1C31232G02 5X00034G01(Fused
Pmod)
48 VDC Differential
1C31238H01 (molded
194 OW350_R1007

RANGE
MODULE MODULE OR CAV ITY
2
INSERT
125 VAC/VDC 16 1C31232G03 5X00034G01 (Fused

Single-ended Pmod)
1C31238H01(molded
1
2
This is an insert that fits into the Personality module position and provides a wiring schematic label for
the module.
Contact Digital Input module – provides an interface for 16 current-sourcing digital (contact)
inputs using a personality module. The following input configuration is available: 48 VDC (single-
ended – channels have a common return, which is the return for the on-module 48 VDC current
limited contact wetting power supply).
1
Contact Digital Input subsystems

MODULE MODULE
48 VDC On-Card Auxiliary (Legacy) 16 1C31142G01 1C31110G03

1
This module configuration is CE Mark certified.
Compact Contact Digital Input module – provides a low cost interface for 16 current-sourcing
digital (contact) inputs without requiring a personality module. The following input configuration is
available: 48 VDC (single-ended – channels have a common return, which is the return for the on-
module 48 VDC current limited contact wetting power supply).
1
Compact Contact Digital Input subsystems
RANGE CHANNELS ELECTRONICS MOLDE D PLAS TIC

MODULE 2
CAV ITY INS ERT
Compact Contact with 48 VDC On-Card 16 1C31234G01 1C31238H01

Auxiliary
1
2
This is an insert that fits into the Personality module position and provides a wiring schematic label for
the module.
OW350_R1007 195
Sequence of Events Digital Input module – provides an interface for 16 digital inputs using a
personality module. The Sequence of Events module monitors the states of the 16 digital inputs
and uses digital filtering to reject state changes less than 4 msec. It performs event tagging and
chatter control for each digital input.
Sequence of Events Digital Input subsystems

MODULE MODULE
24/48 VDC Single-ended (Legacy) 16 1C31157G01 1C31110G01

Differential (Legacy) 16 1C31157G01 1C31110G02
125 VDC Single-ended (Legacy) 1C31157G02 1C31110G01
Differential (Legacy) 16 1C31157G02 1C31110G02
All module configurations listed in the table are CE Mark certified unless they contain a 5FDI.
Sequence of Events Contact Digital Input Field Interface module - provides 16 contact input
current detecting channels with common returns.
Sequence of Events Contact Digital Input Field interface subsystems

MODULE MODULE
Contact Input w/ 48 VDC On-Card auxiliary 16 1C31157G03 1C31110G03

(Legacy)
All module configurations listed in the table are CE Mark certified unless they contain a 5FDI.
Sequence of Events Compact Digital Input Field module – provides a low cost interface for 16
digital inputs without requiring a personality module. The Compact Sequence of Events module
monitors the states of the 16 digital inputs and uses digital filtering to reject state changes less
than 4 msec. It performs event tagging and chatter control for each digital input.
1
Sequence of Events Compact Digital Input Field subsystems

MODULE MODULE OR
1
CAV ITY INS ERT
Compact 24/48 VDC SOE Single-ended 16 1C31233G01 2

1C31238H01
digital input (molded plastic
cavity insert)
Compact 24/48 VDC SOE Differential 16 1C31233G02 2
1C31238H01
cavity insert)
Compact 24/48 VDC SOE Single Ended 16 1C31233G02 5X00034G01
digital input (Fused Pmod)
196 OW350_R1007

MODULE MODULE OR
1
CAV ITY INS ERT
Compact 125 VDC SOE Differential 16 1C31233G03 2

1C31238H01
cavity insert)
Compact 125 VDC SOE Single Ended 16 1C31233G03 5X00034G01
digital input (Fused Pmod)
Compact 48 VDC SOE On-card 16 1C31233G04 2
1C31238H01
auxiliary Contact Input w/48V wetting (molded plastic
cavity insert)
1
All module configurations listed in this table are CE Mark Certified.
2
This is a cavity insert that fits into the Personality module position and provides a wiring schematic label
for the module.
Enhanced Compact Sequence of Events Digital Input module – provides a low cost interface
for 16 digital inputs without requiring a personality module. The Enhanced Compact Sequence of
Events module monitors the states of the 16 digital inputs and uses digital filtering to reject state
changes less than 4 msec. It performs event tagging and chatter control for each digital input.
Unlike other Ovation Sequence of Events (SOE) modules, the Enhanced Compact Sequence of
Events module also offers a field digital input state change detection feature (SOE One Shot).
Enhanced Compact Sequence of Events Digital Input subsystems
RANGE CHANNELS ELECTRONIC PERSONALITY

MODULE MODULE OR
CAV ITY INS ERT
24/48 VDC Single-ended Digital Input - Current 16 5X00357G01 1

1C31238H01
Sinking
24/48 VDC Differential Digital Input - Current 16 5X00357G02 1
1C31238H01
Sinking
24/48 VDC (Individually Fused Channels with 16 5X00357G02 5X00034G01
Common power supply) Single-Ended Digital
Input - Current Sinking
125 VDC Differential Digital Input - Current 16 5X00357G03 1
1C31238H01
Sinking
125 VDC (Individually Fused Channels with 16 5X00357G03 5X00034G01
Input - Current Sinking
48 VDC Single-ended Digital Input - Current 16 5X00357G04 1
1C31238H01
Sourcing (Contact input) with On-Card 48 VDC
power supply
24 VDC (Differential) Digital Input - Current 16 5X00357G05 1
1C31238H01
Sinking, IEC61131-2 Compliant Type 1 Digital
Inputs
OW350_R1007 197
RANGE CHANNELS ELECTRONIC PERSONALITY

MODULE MODULE OR
CAV ITY INS ERT
24 VDC (Individually Fused Channels with 16 5X00357G05 5X00034G01

Input - Current Sinking, IEC61131-2 Compliant
Type 1 Digital Inputs
1
This is a plastic insert that fits into the base unit’s Personality module cavity and provides a base unit
terminal block wiring label for the module.
32 Channel 24V DC Single-Ended Digital Input module - monitors the state ("0" or "1") of 32
single-ended field digital inputs. The 32 Channel 24V DC Single-Ended Digital Input module is
designed to meet IEC 61131-2 type 3 characteristics for 24VDC digital inputs in industrial
automation.
32 Channel 24V DC Single-Ended Digital Input Subsystems

MODULE MODULE
32 Channel 24V DC Single-Ended Digital 32 5X00499G01 1X00690H01

Input
Digital Input modules testing
Digital Input (1C31107) and Compact Digital Input (1C31232):
Apply specified signal (per database) and verify individual point activation. Apply "every other"
point simultaneously to verify no cross-talk occurs.
Digital Input modules
1. Digital Input (1C31107) and Compact Digital Input (1C31232) (see page 198)
 Diagnostic LEDs for Digital Input modules (see page 199)
 Diagnostic LEDs for Compact Digital Input modules (see page 199)
2. Contact Input (1C31142) and Compact Contact Input (1C31234) (see page 199)
 Diagnostic LEDs for Contact Input modules (see page 199)
 Diagnostic LEDs for Compact Contact Input modules (see page 200)
3. Sequence of Events (1C31157) and Compact Sequence of Events (1C31233) (see page 200)
 Diagnostic LEDs for the Sequence of Events Contact Input field interface module (see
page 201)
 Diagnostic LEDs for the Compact Sequence of Events Digital Input module (see page
201)
 Diagnostic LEDs for Enhanced Compact Sequence of Events input module 5X00357 (see
page 202)
198 OW350_R1007
Diagnostic Logic card LEDs - (DI)
LED
DESCRIPTION

module.
E No LED.
I (Red) External Fault LED. Lit when the Blown Fuse bit (Bit 7) of the Status Register is set. This
indicates the field supply fuse is blown or the auxiliary power supply is not present. This
LED should never light if the Digital Input module is installed since the Blown Fuse Enable
bit (Bit 6) of the Status Register should be set to the inactive state by the Controller.
1 - 16 Point Status LED. Lit when the input voltage of the LED’s corresponding channel is greater
(Green) than the channel’s minimum On Input Voltage.
Diagnostic Logic card LEDs - (CompactDI)
LED DESCRIPTION

module.
E (Red) External Fault LED is Lit when:
 The Blown Fuse bit (Bit-7) of the Module Status Register (see Register
configuration/address information - (Compact DI)) is set. This indicates that the
auxiliary supply fuse has blown or the auxiliary supply is not present or below its
acceptable threshold.
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1) of the (see Register
configuration/address information - (Compact DI)) is active or when a timeout of the
watchdog timer occurs when the Controller stops communicating with the module.
1 - 16 (Green) Point Status LEDs 1-16. Lit when the input voltage of the LED’s corresponding channel
is greater than the channel’s minimum On Input Voltage.
Contact Input modules testing
Contact Input (1C31142) and Compact Contact Input (1C31234):
Apply individual inputs using a switch. Verify at system graphic. If possible, apply "every other"
point simultaneously to verify that no crosstalk occurs.
OW350_R1007 199
Diagnostic Logic card LEDs - (ContactDI)
LED DESCRIPTION

module.
E (Red) External Fault LED. Lit when GND Fault bit (Bit 10) of the Status Register is set. This
indicates that a ground fault has occurred in the field wiring. An attention status is
generated when the External Fault LED is lit only if the GND Fault Attention Enable bit (Bit
9) is set.
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1) of the Configuration Register is
set or when the on-board +48V/+10/V wetting power supply fails.
communicating with module.
An attention status is always generated when the LED is lit.
1 (Green) Point Status LEDs 1-16. Lit when the input contact of the LED’s corresponding channel is
closed.
Diagnostic Logic card LEDs - (CCDI)
LED DESCRIPTION

module.
E (Red) External Fault LED. Lit when GND Fault bit (Bit 10) of the Status Register is set. This
indicates that a ground fault has occurred in the field wiring. An attention status is
generated when the External Fault LED is lit only if the GND Fault Attention Enable bit
(Bit 9) is set.
is set or when the on-board +48V/+10/V wetting power supply fails. Also lit when a
timeout of the watchdog timer occurs when Controller stops communicating with
module. An attention status is always generated when the LED is lit.
1 - 16 (Green) Point Status LEDs 1-16. Lit when the input contact of the LED’s corresponding channel
is closed.
Sequence of Events modules testing
Sequence of Events (1C31157) and Compact Sequence of Events (1C31233):
Input is activated using a switch or jumper and verified at an engineering station or control
graphic. If a historian drop is present, and all required SOE sub-system configuration with the
database is completed, check the SOE report that shows the sequential activation of SOE points.
200 OW350_R1007
Diagnostic LEDs - (SEContactDI)
LED DESCRIPTION

module.
E (Red) External fault. Lit when a ground fault occurs in the field wiring. Ground fault is also
indicated in bit 12 (GND fault) of the Status register.
I (Red) Internal fault. Lit when the internal on-card +48V/+10V contact auxiliary power supply
has failed. Only lit if Bit 8 of the Configuration register is set.
1 (Green) Lit when the input contact of the LED’s corresponding channel is closed.
OW350_R1007 201
Diagnostic Logic card LEDs - (SECompactDI)
LED DESCRIPTION

module.
E (Red) For Single-ended Digital Input: Lit when fuse blows or there is a loss of the auxiliary
power supply (Only when Bit 6 of Configuration register is set. Then Bit 7 of the Status
register is set.)
For Differential Digital Input: Not lit since the configuration bit is not set, and the blown
fuse signal from the field card is ignored.
is set, or when a timeout of the watchdog timer occurs when the Controller stops
Also lit when Controller stops communicating with the module.
1 - 16 (Green) Lit when the input voltage of the LED’s corresponding channel is greater than the
channel’s minimum “On Input Voltage.”
Diagnostic Logic card LEDs - (ECSOEDI)
LED DESCRIPTION

module.
E (Red) The External Error LED is illuminated when faults external to the module are present.
 For Group 1 modules, the External Error LED is illuminated only when the field card
Auxiliary power supply fuse opens or the Auxiliary power supply voltage level is low
(BLOWN FUSE = 1) and the Module Configuration register bit 6 is set. Module
Configuration bit 6 must be cleared for all other module groups.
 For Group 2, 3 or 5 modules, the External Error LED should not be illuminated. The
Module Configuration register bit 6 should be cleared and the field card BLOWN
FUSE signal is ignored. The Module Configuration register bit 8 should also be
cleared.
 For Group 4 modules (contact input), the External Error LED is illuminated only when
the field card detects a ground fault in the field wiring (GND FAULT/ = 0) and the
Module Configuration register bit 8 is set.
I (Red) The Internal Error LED is illuminated to indicate internal electronics module faults.
 The Internal Error LED is illuminated when Module Configuration Register bit 1
(Force Error) is set.
 The Internal Error LED is illuminated for Group 4 electronics modules when the field
card's internal 48V/10V contact wetting voltage power supply fails (WETVOLTOK/ =
1) and the Module Configuration Register bit 8 has been set. Module Configuration
bit 8 must be cleared for all other module groups.
 The Internal Error LED is illuminated when the I/O Bus Controller has not accessed
the electronics module for at least a period of 2 seconds.
202 OW350_R1007
LED DESCRIPTION
1 - 16 (Green) Digital Input Channel State LEDs

 For any Group 1, 2, 3 or 5 electronics module current-sinking digital input channel,
the channel's digital input state LED is guaranteed to illuminate when the digital input
channel's input voltage exceeds the minimum required input voltage for a "1" signal.
For any Group 4 electronics module, the channel's digital input state LED is
guaranteed to illuminate when the channel's field contact is closed, the sum of the
field wiring resistance and contact resistance is less than 100 ohms and the field
card's internal 48V/10V wetting power supply is functioning correctly.
 Each digital input channel state LED is located on the LSW logic card. The field
card's opto-coupler output transistor interfaces a voltage comparator via a pull-up
resistor connected to the logic card's VCC voltage bus through a series pull-up
resistor. The voltage comparator compares the opto-coupler's output voltage to a
fixed reference voltage in order to determine the digital input channel's state. The
voltage comparator output transistor's uncommitted collector terminal is routed to the
LSW logic card where it is connected to the logic card VCC voltage bus via a pull-up
resistor and the digital input channel state LED.
Note: The logic card's I/O Bus communications watchdog timer turns off the Communications
OK LED and illuminates the module I LED if the I/O Controller fails to access the Enhanced
Compact Sequence of Events Module within 2 seconds.
Upon a timeout, the watchdog timer will clear the Event Mask register, clear the event buffers
and clear Module Configuration Register.
A watchdog timer for one shot registers would clear the one shot registers if no reads occur to
Positive Transition Latched Register or Negative Transition Latched Register within a period of 5
seconds. After a timeout, the collection of one shot information is prevented until the Controller
resumes reading either Positive Transition Latched Register or Negative Transition Latched
Register. The first read would be a throw away which would re-activate the watchdog timer. The
second read would yield valid register data.
OW350_R1007 203
5.14.4 Digital Output modules
Digital Output module - provides a means to switch up to 60 VDC at moderate currents (for
example, relay coils and lamps). The Digital Output module contains 16 current sinking transistor
outputs capable of switching 60 VDC loads at up to 500mA.
1
Digital Output subsystems

DESCRIPTION
MODULE OR MODULE
PANE L KIT
5-60 VDC Single ended Direct 16 1C31122G01 1C31125G01
Relay Panel Interface:

Local Power Supply 16 1C31122G01 1C31125G02
Field Power Supply 16 1C31122G01 1C31125G03
Relay Panels: Solid State Relay Panel (AC) 16 5A22410G01
Solid State Relay Panel (DC) 16 5A22410G02
G2R Relay Panel (Low Power Electro- 16 5A22411G01
mechanical)
2 16 5A22412G01 - G03
KU Relay Panel (High Power Electro-
mechanical)
1
All configurations listed in the table are CE Mark certified, unless they use AC/DC solid state relay
panels.
2
Two panels (8 relays each) are included in the KU Relay Panel kit 5A22412G01, G02, and G03.
204 OW350_R1007
High Side Digital Output (24 VDC) module - an intelligent microcontroller-based digital output
module. The HSDO consists of two modules, (electronics and personality), that are inserted into
an Ovation I/O module base unit. The HSDO module contains sixteen optically isolated digital
output channels. Each digital output channel is capable of sourcing up to 500 mA of output
current.
High Side Digital Output (24VDC) subsystems
RANGE CHANNELS ELECTRONICS PERSONALITY MODULE

MODULE
24VDC 16 5X00270G01 5X00273G01
Relay Output module - consists of an Electronics module, a base assembly, and relays. The
Relay Output module provides a means to switch high AC voltages at high currents to field
devices. There are two versions of the Relay Output base assembly which contain either 12 or 16
relays within each base.
The Relay Output base assembly does not incorporate a Personality module. For more
information about module configuration, refer to the following topics: Electronics modules (Emod)
- (RO), Base assemblies - (RO), and Panel kits - (RO) in the Ovation I/O Reference manual.
Relay Output with Contact Monitoring module - consists of an Electronics module, a base
assembly, and relays. The Relay Output module provides a means to switch high AC voltages at
high currents to field devices. It provides a single FORM X relay contact to drive the field devices.
In addition, the module has two monitoring circuits per channel, which provide a feedback to the
standard Ovation Contact Input module or Digital Input Module to indicate the contact state of the
relay.
The Relay Output base assembly does not incorporate a Personality module. For more
- (ROCM) and Base assemblies - (ROCM) in the Ovation I/O Reference manual.
Fused Relay Output module - provides a means to switch high current and voltage devices
located in the field. You have a choice between a fused low power relay output assembly and a
fused high power relay output assembly for differing applications.
The Fused Relay Output base assembly does not incorporate a Personality module. For more
- FRO and Base assemblies - (FRO) in the Ovation I/O Reference manual.
OW350_R1007 205
32 Channel 24 VDC Single-Ended Digital Output module - contains 32 24-volt single-ended

digital output channels. Each digital output channel is capable of sourcing up to 500 mA of output
current with a 2A maximum total output current limit per module.
32 Channel 24V DC Single-Ended Digital Output subsystems
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY

MODULE OR PANEL MODULE
KIT
32 Channel 24V DC High-Side, Single- 32 5X00500G01 1X00691H01

Ended Digital Output
Digital Output modules testing
Digital Output (1C31122):
Activate individual points via the system graphic faceplates, and verify by checking continuity of
activated relay contacts (verified at open and closed state). If module is not terminated to relay
panel, point is verified using a test light for standard terminations or voltmeter for custom
terminations.
Digital Output modules
1. Digital Output (1C31122) (see page 206)

 Diagnostic LEDs for Digital Output modules (see page 206)
 Diagnostic LEDs for the 24VDC HSDO module (see page 207)
2. Relay Output Electronics Module (1C31219) (see page 208)
 Diagnostic LEDs for the Relay Output module (see page 208)
Diagnostic Logic card LEDs - (DO)
LED DESCRIPTION

module.
E (Red) External Fault LED. Lit when the field supply fuse is blown and the blown fuse
detection circuit is enabled. Blown Fuse bit (Bit 7) of the Configuration Register
enables or disables the fuse detection circuit (high enabled).
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1 of the Configuration
Register) is active, or the Controller stops communicating with the module.
1 - 16 (Green) If the LED is lit, this indicates that the output is in the ON state.
If the LED is not lit, this indicates that the output is in the OFF state.
206 OW350_R1007
Diagnostics - (HSDO)
For both stand-alone and redundant High Side Digital Output module configurations, power switch
diagnostic bits are accessed every 25 milliseconds. If a digital output fault is detected on a
channel, the corresponding Module Channel Fault register fault bit is set. When any bit in the
Module Channel Fault register is set, the Module Status register (register 0xD) Digital Output fault
bit (Bit 14) is also set.
These digital output fault conditions can be detected and reported:

 Power switch output short circuit to ground.
 Power switch output short circuit to +24V (switch cannot be turned off).
 Power switch power supply under-voltage.
 Power switch open circuit (switch cannot be turned on).
When HSDO modules operate in a redundant module configuration, a dynamic power switch turn-
off test is performed periodically. By communicating over the cross-connect cable serial link, the
two HSDO modules coordinate their dynamic power switch turn-off testing so that both modules
do not shut off their power switch outputs at the same time.
Upon module insertion, after communication between modules is established, and after 12
additional seconds have elapsed, the HSDO module performs the dynamic power switch turn-off
test. The HSDO module will then performs test periodically at a time interval ranging from 15
minutes to 24 hours. This time interval is selected by the values of Module Configuration register
bits 10, 9 and 8.
The Ovation 24VDC High Side Digital Output LDH logic card contains 20 LEDs to display module
status. The following figure illustrates the LED array:
Figure 50: LED Configuration for the24VDC High Side Digital Output Electronics Module
The following table lists the module LEDs and describes what each indicates.
24VDC High Side Digital Output
LED DESCRIPTION
P - (green ) Power OK LED. This LED is lit when the Electronics module card 5VDC power is okay.
C - (green) Communications OK LED, which is lit when the Controller is communicating with the
module.
E - (red) External Error LED - This LED is lit when both of the following conditions are true:
Field power is absent
 Module Configuration register Bit 7 is set.
I - (red) Internal Error LED - This LED is lit when one or more of the following conditions are true:
Controller is not communicating with the module.
Internal microcontroller sets its internal error bit.
 Module Configuration Error Bit 1 is set.
1 - 16 (green) Channel 1 - 16 Status - Lit when the Channel 1 power switch is turned on and not lit
when the Channel 1 - 16 power switch is turned off.
OW350_R1007 207
Note: All switches are turned off when dynamic testing occurs. The LEDs which were on,
indicate that the output switch is active, and blink off for 25 mSec, or 50 mSec during the test.
Relay Output module testing
Relay Output (1C31219):
Individual relays are activated via the control graphic. Outputs are verified via continuity check of
the relay contact (verified at open and closed state).
Diagnostic LEDs - (RO)
LED DESCRIPTION

module.
E (Red) External Fault LED. Lit when the field supply fuse is blown and the blown fuse
detection circuit is enabled. Blown Fuse bit (Bit 7) of the Configuration Register
enables or disables the fuse detection circuit (high enabled).
I (Red) Internal Fault LED. Lit whenever the Force Error bit (Bit 1 of the Configuration
Register) is active or the Controller stops communicating with the module.
1 (Green) If the LED is lit, this indicates that the output is in the ON state.
If the LED is not lit, this indicates that the output is in the OFF state.
208 OW350_R1007
5.14.5 Specialty Modules
Link Controller module – provides a serial RS232, RS422, or RS485 data communications link
to a third-party device or system. To use this module, the appropriate SLC algorithm must reside
in the Ovation Controller.
1
Link Controller subsystems

MODULE MODULE
RS232 One (1) Serial Port (Able to handle 2 1C31169G01

1C31166G01
many points) or
1C31166G02
RS485/RS422 Four One (1) Serial Port (Able to handle 2 1C31169G02
1C31166G01
wire many points) or
1C31166G02
1
All module configurations listed in the table are CE Mark Certified. 1C31166G02 pending CE Mark
Certification.
2
Not for new projects. Used for spares and replacements only.
To use this module, the appropriate SLC algorithm must reside in the Ovation Controller. (See Ovation
Algorithm Reference Manual.)
Loop Interface module – provides an interface to the analog and digital I/O needed to control a
single process loop (up to 2 AI, 1 AO, 2 DI, 2 DO). In addition, the loop interface can display the
process information and provide for manual control via a local operator interface station (SLIM).
1, 4
Loop Interface subsystems

MODULE MODULE
Normal (Non-electric) Drive modules

0-10V Analog Inputs/Output 6 1C31174G01 1C31177G01
2 6 1C31174G21 1C31177G01
0-10V AI/AO - user defined Digital Inputs
0-5V Analog Inputs, 0-10V Analog Output 6 1C31174G02 1C31177G01
2 6 1C31174G22 1C31177G01
0-5V AI, 0-10V AO - user defined Digital Inputs
4-20mA AI/AO Locally powered analog inputs 6 1C31174G03 1C31177G02

4-20mA AI/AO Field powered analog inputs 6 1C31174G03 1C31177G03
2 6 1C31174G23 1C31177G02
4-20mA AI/AO - user defined Digital Inputs
Locally powered analog inputs
2 6 1C31174G23 1C31177G03
4-20mA AI/AO - user defined Digital Inputs
Field powered analog inputs
OW350_R1007 209

MODULE MODULE
1
This module controls ONE process loop. To use this module, the MASTATION algorithm must reside in
the Ovation Controller. (See the Ovation Algorithm Reference Manual.)
2
Priority Raise and Lower inputs can be disabled and used as user-defined input points. Configuration
instructions are included in Kit 1C31174G20.
3
This output may not appear on the termination list, but must be terminated for proper operation.
4
Pulse Accumulator module – counts pulse for up to two input channels and provides the
information to the Controller. The Pulse accumulator may be used to count over a defined time
period to measure speed (frequency), count until instructed to stop, or can be used to measure
the duration of a pulse.
1
Pulse Accumulator subsystems

MODULE MODULE
Field count: +5/12V (medium speed) 2 1C31147G01 1C31150G01

+ 24/48V (medium speed)
Field controls: +24/48V
+ 24/48V (medium speed)
+24/48V (medium speed)
Field count: +5V (high speed) 2 1C31147G02 1C31150G01
1
+24/48V medium-speed configurations are CE Mark Certified.
Servo Driver module – provides an interface to an electro-hydraulic servo actuator (servo-motor)

used to control a steam turbine.
1
Servo Driver subsystems

MODULE MODULE
±16 Volts DC to a DC LVDT 6 1C31199G01 1C31201G01

60 mA into a 60 ohm coil (CD1) or
40 mA into an 80 ohm coil (CD2) or
40 mA into a 40 ohm (CD3) coil
19 Volts AC peak-to-peak 1 KHz to an AC 6 1C31199G02 1C31201G02
LVT
8 mA into two 1000 ohm coils
210 OW350_R1007

MODULE MODULE

LVT
±16 Volts DC to a DC LVDT (I/O Bus 6 1C31199G04 1C31201G01
Firmware updates)
60 mA into a 60 ohm coil (CD1) or
40 mA into an 80 ohm coil (CD2) or
40 mA into a 40 ohm (CD3) coil
LVT (I/O Bus Firmware updates)
LVT (I/O Bus Firmware updates)
1
This module interfaces to, and provides position control for two Electro-Hydraulic (EH) actuators in the
field.
Small Loop Interface module – contains displays and keyboard inputs needed for an operator to
monitor and control the I/O functions of the Ovation Loop Interface or Valve Positioner module.
The SLIM is located external to the Ovation I/O cabinet and connected to the Loop Interface or
Valve Positioner via cable.
For more information about module configurations, refer to Assemblies - SLIM section of the
Ovation I/O Reference Manual.
Speed Detector module – provides the Controller with frequency measurements of a sinusoidal
or pulse train input signal. A 16-bit speed output is updated at a rate of 5 ms for over-speed
detection (G01 only), and a 32-bit speed output is updated at a variable rate for speed regulation
(G01 and G03). G03 Speed Detector modules also provide a 16-bit acceleration output that is
updated at the same rate as the 32-bit speed output.
Speed Detector has the G01 and the G03 subsystems. For more information, refer to Subsystems
G01 - (SD) and Subsystems G03 - (SD) sections of the Ovation I/O Reference Manual.
Valve Positioner module – provides an interface to an electro-hydraulic servo actuator.

Governor valves, interceptor valves, extraction valves, and bypass valves can be controlled. The
module provides closed loop valve positioning control and also interfaces to a local operator
interface station (SLIM).
1
Valve Positioner Subsystems

MODULE MODULE
Valve Positioner Controller

17 Volts AC LVDT: 24.9 mA 8 1C31194G01 1C31197G01
OW350_R1007 211

MODULE MODULE
17 Volts AC LVDT: 36 mA 8 1C31194G01 1C31197G04

24 Volts Fused DC LVDT: 50 mA 8 1C31194G01 1C31197G05
23.75 Volts AC LVDT: 24.9mA 8 1C31194G02 1C31197G01
23.75 Volts AC LVDT: 16.8 mA 8 1C31194G02 1C31197G02
23.75 Volts AC LVDT: 36 mA 8 1C31194G02 1C31197G04
1
This module provides an interface between an Ovation Controller and ONE Electro-Hydraulic (EH)
servo-valve actuator in the field. To use this module, the MASTATION algorithm must reside in the
Ovation Controller. (See the Ovation Algorithm Reference Manual.)
Enhanced Valve Positioner module – provides an interface to an electro-hydraulic servo

actuator. Governor valves, interceptor valves, extraction valves, and bypass valves can be
controlled. The module provides closed loop valve positioning control and also interfaces to a
local operator interface station (SLIM).
Enhanced Valve Positioner Subsystems

MODULE MODULE
Enhanced Valve Positioner Controller

17 Volts AC LVDT: 36 mA 8 1C31194G03 1C31197G04
23.75 Volts AC LVDT: 24.9mA 8 1C31194G04 1C31197G01
23.75 Volts AC LVDT: 36 mA 8 1C31194G04 1C31197G04
212 OW350_R1007
Numalogic Fast Ethernet Remote Node - is a remote I/O subsystem which provides an
interface to the Numalogic PC700 series Remote I/O. The NFE-RN is comprised of a base
assembly, power supplies, and redundant Numalogic Fast Ethernet Remote Node Controllers
(NFE-RNCs). The NFE-RNCs contain four Ethernet ports.
Numalogic Fast Ethernet Remote Node
PART NUMBER
Numalogic Remote I/O Kit 5X00512

Numalogic Remote Node Controller 5X00467
PWSN Power Supply Assembly 5X00522
Numalogic Remote I/O Backplane Assembly 5X00468
Loop Interface Controller modules testing
Loop Interface Controller (1C31174):
This module requires a functional process loop and operator interface for operation. For analog
LIC, project-specific algorithms and functional logic, including a configured soft MA station and/or
SLIM are required. At this point, the technician can demonstrate the modules ability to switch
between modes and to increase/decrease the set point/output functions. There is currently no
procedure for the testing of the electric drive LIC.
Diagnostic Logic Card LEDs - (LI)
LED DESCRIPTION
P (Green) Power OK LED. Lit when the +5V power is OK.

C (Green) Communications OK LED. Lit when the Controller is communicating with the module.
I (Red) Internal Error LED. Lit whenever there is any type of error with the module. Possible
causes are:
 I/O bus communications watchdog timeout.
 Forced error issued by the Controller.
 Initialization error (SRAM error, invalid group, and so forth).
 Microcontroller watchdog timer timeout or module reset.
1 AO (Red) Analog Output Error. Lit whenever there is an over current or undercurrent condition on
the analog output section (Group 3 and 4 only).
2 AI1,(Red) Analog Input Error. Lit whenever there is an input error. Possible causes are:
 Input voltage over-range for 10 seconds.
 Broken current loop input/blown fuse for module configured as current input.
 Offset calibration voltage out of range for five consecutive calibrations (40 seconds).
3 AI2 (Red) same as LED # 2.
4 Fuse (Red) Blown Fuse Error. Lit if the auxiliary supply voltage for either the digital inputs or digital
outputs is not present and blown fuse detection is enabled for either the digital outputs
or the digital inputs.
5 SLIM (Red) SLIM Communication Error. Lit if there is a SLIM serial port communications error.
6 DO1 (Green) Digital Output Status. Lit when digital output 1 is active.
OW350_R1007 213
LED DESCRIPTION
7 DO2 (Green) Digital Output Status. Lit when digital output 2 is active.
8 DI1 (Green) Digital Input Status. Lit when digital input 1 is active.
9 DI2 (Green) Digital Input Status. Lit when digital input 2 is active.
10 No LED.
11 No LED.
12 No LED.
13 No LED.
14 No LED.
15 No LED.
16 No LED.
Pulse Accumulator modules testing
Pulse Accumulator (1C31147):
Random pulse is applied at input. The engineering station or control graphics are read to verify
number of accumulated pulses. Project-specific pulse accumulator logic sheets are required for
this test.
Diagnostic Logic card LEDs - (PA)
LED DESCRIPTION

module.
E (Red) 1
External Fault LED. Lit when the field supply fuse is blown. (Bit 6) of the Status Register
is set.
I (Red) 1
Internal Fault LED. Lit whenever the Force Error bit (Bit 1) of the Configuration Register
is set or when a timeout of the watchdog timer occurs when the Controller stops
1 (Green) Lit when the Channel external ENABLE input is active.
2 (Green) Lit when the Channel external ENABLE input is active.
3 - 16 No LED.
1
The logical OR of the Internal Fault LED and External Fault LED indication is input to the I/O Slave
Controller as an ERROR flag. This forces an attention status.
214 OW350_R1007
Servo Driver modules testing
Servo Driver (1C31199):
This module requires connection to the servo. Use the control loops and graphics to interface the
servo and demonstrate the ability to control movement.
Diagnostic Logic card LEDs - (SVD)
Diagnostic Logic card LEDs - (SVD) (1C31199G01 - G03)
LED DESCRIPTION

C (green) Communications OK LED. Lit when the Controller is
communicating with the module. Successful completion of
sequence resets the watchdog timer.
E (Red) External Fault LED.
I (Red) Internal Fault LED. Possible causes:
 Force Error bit (Bit 1) of the Configuration Register is set.
 Also lit when a timeout of the watchdog timer occurs when
Controller stops communicating with module.
1 MODE (Green) Channel 1 Lit whenever the module is operating in Normal mode.
Not lit whenever the module is operating in local manual mode.
2 CONTINGCY (Red) Channel 1 Lit to indicate Contingency Condition.
3 BACKSEAT (Green) Channel 1 Lit whenever seating or backseating is in effect.
4 PI DETUNE (Green) Channel 1 Lit whenever PI is detuned.
9 - 16 No LED.
OW350_R1007 215
Diagnostic Logic card LEDs - (SVD) (1C31199G04 - G06)
LED DESCRIPTION

C (green) Communications OK LED. Lit when the Controller is
communicating with the module. Successful completion of
sequence resets the watchdog timer.
E (Red) External Fault LED.
I (Red) Internal Fault LED. Possible causes:
 Force Error bit (Bit 1) of the Configuration Register is set.
 Also lit when a timeout of the watchdog timer occurs when
Controller stops communicating with module.
1-8 No LED.
Speed Detector modules testing
Speed Detector (1C31189):
Apply signal at valid frequencies. Verify at mid, min, and max scale (per database, via termination
list).
Diagnostic Logic card LEDs - (SD)
LED DESCRIPTION
P (green) Power OK LED. Lit when the +5V power is OK (above min required operating level).
module at least once every two seconds.
E (Red) External Error LED. Lit when the Open Wire (Bit 6 of module reply status register) is
detected.
I (Red) Internal Error LED. Lit when the Force Error bit (Bit 1 of register D) is detected.
communicating with module for two seconds.
1 (Green) Lit when overspeed is detected.
2 (Green) Lit when relays are energized.
216 OW350_R1007
LED DESCRIPTION
3 - 16 No LED.
Valve Positioner modules testing
Valve Positioner (1C31194):
This module requires connection to a valve. Project-specific control logic and graphics to interface
the module to the valve are required to verify the ability to move a valve.
Diagnostic Logic card LEDs - (RVP)
LED DESCRIPTION

C (green) Communication OK LED. Lit when the Ovation Controller is communicating
with the module at least once every two seconds.
E (Red) The "E" LED is illuminated if:
 The SLIM address is not zero AND there is no valid response from a
SLIM.
OR
 The "Ignore Shutdown" configuration bit is not set AND the wetting
voltage for the shutdown input is not present.
I (Red) Internal Error LED. Lit when the Force Error bit (Bit 1 of register D) is
detected.
communicating with module for two seconds.
1 - MANUAL (Green) Lit whenever the module is operating in Local Manual mode.
2 - SERVO OK (Green) Lit to indicate the servo coil diagnostics have passed. Only diagnostics for
the number of coils specified by “coilCount” are executed.
The coil open/short bits reported to the controller are delayed by a timer.
The value is set in 100 mSec increments by the tuning constant
“diagtime=xx”. However, the LED is extinguished immediately when the
diagnostic has failed and the timer is counting towards expiration.
Therefore, if the LED is blinking, the tuning constants kServo, kServoDb,
and/or diagtime may be too tightly defined. If the LED blinks off during rapid
valve movement, but the associated module status bit does not become
active, then those three tuning constants are properly set.
3 - NORMAL (Green) Lit whenever the module is operating in Normal mode.
Blinks if it is the Primary in a redundant configuration.
4 - PI DETUNE (Green) Lit whenever PI is detuned. The PI is detuned ( more sluggish ) when the
valve is at setpoint. Please refer to definitions of errorDbS, errorDbF,
piGainDb, and piResetTdb.
In a redundant RVP configuration this LED is unconditionally extinguished
on the backup RVP because this condition is associated with the PI loop
running on the primary RVP.
This LED will blink upon rapid valve movement or when the tuning
parameters mentioned above are not set properly.
5 - CALIBRATE (Green) Lit whenever the module is calibrating.
OW350_R1007 217
LED DESCRIPTION
6 - BACKSEAT (Green) Lit whenever seating or backseating is in effect. This LED is extinguished on
the backup RVP of a redundant RVP pair because the condition is
associated with the PI control of the primary RVP.
7 - CONTINGENCY (Red) Lit whenever the module is operating in contingency condition. This LED will
blink when the diagnostic detects position error greater than “contingency”
during rapid valve movement, or if the valve is actually oscillating around the
setpoint. The status bit reported to the controller is delayed by a timer set by
“contingencyTime”.
8 - SHUTDOWN (Red) Lit when the module is driving the valve fully closed due to the module
shutdown digital input.
9 No LED.
10 No LED.
11 No LED.
12 No LED.
13 No LED.
14 No LED.
15 No LED.
16 No LED.
Diagnostics - (RVP)
One important feature of the servo valve is an adjustable mechanical bias mechanism. This
mechanism creates a slight deflection in the valve spool so that a small amount of hydraulic fluid
can escape the actuator and close the valve. Therefore, if there is no voltage applied to the servo
valve, the actuator slowly moves toward the closed position. This deflection is typically overcome
by -200 millivolts, so that when the valve is positioned and steady, this small voltage is seen on
the servo valve.
The servo valve has two voltage coils, either of which can deflect the spool when excited.
The combination of these features provide the following:

 Redundancy feature that protects against broken wires or shorted coils
 Ability to be diagnosed
 A predictable shutdown mechanism for the following:
 In the event the firmware diagnoses a catastrophic error and executes a shutdown
OR
 An error mode occurs that allows a hardware watchdog timer to expire and de-power the
Electronics module’s FVP field card.
218 OW350_R1007
The Valve Positioner continuously runs diagnostics to ensure that the circuit is operating properly.
Certain conditions can cause the Valve Positioner to dive, essentially removing the output signal
and allowing the valve to drift shut.
As a general rule, the card views error conditions on start up as no-go or fatal errors. This means
that the Valve Positioner does not generate an output to the valve. See the following error
descriptions for specifics.
DA readback error - (RVP)
The Valve Positioner has the ability to read and convert the coil drive D/A converter output signal
that drives the valve. If the value readback (converted by the A/D converter) and the value that
was output do not match within a deadband, and for a pre-defined period of time, a severe fatal
error is assumed. In this case, the Valve Positioner is “flying blind.” It cannot confidently
determine valve position or control the output. The Valve Positioner removes drive power (dive)
from the entire Electronics module’s FVP field card and go through a reset sequence. The coil
drive D/A converter readback check is a diagnostic that runs continuously.
EPROM Checksum Error - (RVP)
The EPROM checksum runs continuously as a low priority function. Failure of the checksum
diagnostic is considered a severe fatal error.
Contingency Check Error - (RVP)
Contingency is defined as the difference between a target position and the actual position, when
that difference is greater than a defined limit. In the Valve Positioner, the contingency bit is set if
the difference exceeds a programmable limit (default value is 5%) for a programmable time period
(default value is 10 seconds). Contingency is not a fatal condition.
Memory Read/Write Check Error - (RVP)
A failure of any memory to read back correctly is considered a severe fatal error.
OW350_R1007 219
Open coil diagnostic error - (RVP)
An open coil is detected by measuring voltage across the current limiting resistors on the servo
output. When zero volts are detected, either the coil is open, the servo output is at zero, or the
mechanical bias on the servo valve has been adjusted to yield that result. When an error
condition is detected, an internal “open” bit is set.
For firmware revisions prior to 0F, the diagnostic works as described below. For later revisions,
servo coil voltage is measured and compared to a model described by tuning constants “kServo”
and “kServoDb.” If the voltage does not fit into the model, due to being too large, open coil is
attributed and the internal diagnostic bit is set. Then the timing sequence described below is used
to post the error bit to the Controller.
Typically, the servo coil voltage is -200 mV when the valve is in a stable, controlled position and
the servo valve mechanical bias is properly adjusted. If the servo output amplifier voltage
amplitude falls below 100 mV, the internal bit is cleared, as though no error condition exists. If
servo output voltage is greater than 100 mV, the difference between servo output voltage and coil
voltage is compared to 50 mV, and if it is less, the ‘open’ bit is set.
If the open bit stays set for five seconds, the error condition is reported to the Controller in the
module status register.
Shorted coil diagnostic - (RVP)
For each of the three coil outputs, an internal shorted bit is set if the converted value of terminal
voltage is near 0 volts. Behavior of this diagnostic changes when servo output amplifier voltage is
near zero.
For firmware revisions prior to 0F, the diagnostic works as described below. For later revisions
servo coil voltage is measured and compared to a model described by tuning constants “kServo”
and “kServoDb”. If the voltage does not fit into the model, due to being too large, open coil is
attributed and the internal diagnostic bit is set. Then the timing sequence is described in the
following section and is used to post the error bit to the Controller.
Typically, the servo output coil is -200 mV when the valve is in a stable, controlled position and
the servo valve mechanical bias is properly adjusted. If the servo output amplifier voltage falls
below 50 mV, the internal bit is cleared, as though no error condition exists.
For servo output voltages greater in amplitude than 400 mV, the module status register voltage is
compared to 50 mV, and a shorted bit is set if it is less. If the shorted coil bit remains active for
five seconds, the condition is reported to the Controller in status word 1.
For servo amplifier voltage values between 50 and 400 mV, the comparison value is calculated as
the servo amplifier voltage divided by eight. The timing described above is used. When the
shorted bit becomes inactive, the corresponding bit in status word 1 is cleared immediately.
220 OW350_R1007
Diagnostics of LVDT problems (redundant) - (RVP)
Diagnosing an LVDT failure is complex. Depending on the failure, the valve may open, close, or
go to a different intermediated position, which can be above or below the target position. If the
valve is positioned at the LVDT null point, an oscillator failure would not be detected because the
position feedback would continue to be equal to zero (0) volts.
 If (Position Feedback - Previous Position Feedback) < MAXDELTA, and
POSITIONERRORFLAG is not set, all conditions are considered normal, and the
REDUNDANCY STATE is set to NORMAL. Previous Position Feedback is set equal to
Position Feedback prior to exiting the PI routine.
 If (Position Feedback - Previous Position Feedback) > MIN2NDRY and the backup is OK, the
VP executes the failover.
 If (Position Feedback - Previous Position Feedback) > MAXDELTA, a problem is suspected.
VP firmware refuses to accept the new position feedback value, and does not update
Previous Position Feedback or run the PI loop. If REDUNDANCY STATE is NORMAL, it is
updated to POOR. If it is POOR, it is updated to BAD. If it is BAD, and the backup is OK, the
VP executes the failover. This means that it can take 30 msec for the VP to determine that it
should execute its failover.
 If POSITION ERROR FLAG is set, and the partner’s reported position is within
LVDTTRACKING of Position Feedback, the condition is not due to a failed LVDT, but for
another reason. No action to fail over is taken.
 If POSITION ERROR FLAG is set, and both Position Feedback voltage and Previous Position
Feedback voltage are equal or close to zero volts, the problem is suspected to be a failed
oscillator, or broken oscillator wire, and the failover is executed as long as the Backup is OK.
 If POSITION ERROR FLAG is set, and Position Feedback differs from Partner’s Position
Feedback by more than LVDTTRACKING, and the Backup is OK, an LVDT problem is
suspected and the failover is executed.
Serial Link Controller modules testing
Serial Link Controller (1C31166):
There is no Ovation I/O points associated with this module. Please note that the link cannot be
verified unless the third party PLC device is available. As a result, most links are loaded and
configured in the field.
Testing Media Attachment units and Remote Node Controllers
Media Attachment unit {1C31179} and Remote Node Controller (1C31203):
There are no hard I/O points associated with these modules. The ability to access and test I/O
that is located on the remote nodes, is verification of functionality.
OW350_R1007 221
5.15 Bus interface modules

Profibus module – Profibus (Process Field Bus) DP (decentralized periphery) is an all digital,
two-way communication system that links devices (also known as slaves) and automation
systems. A decentralized periphery uses a network bus (in this instance, Profibus) between the
Controller (Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as
compared to a programmable logic Controller (PLC) that has its I/O arranged centrally. At the
base level in the hierarchy of plant networks, Profibus serves as a Local Area Network (LAN) for
instruments.
Profibus subsystems
2 5X00300GO1 or 5X00300GO2 5X00321G01
DeviceNet module – The Ovation DeviceNet Module provides an interface with one or two
DeviceNet networks, respectively. The DeviceNet has an associated Personality Module.
DeviceNet offers robust, efficient data handling based on Producer/Consumer technology that
allows you to determine effectively what information is needed and when.
DeviceNet subsystems
2 5X00376G01 5X00375G01
Foundation Fieldbus module – The Ovation Foundation Fieldbus module provides a means to
interface the Ovation system to industry standard Foundation Fieldbus devices. The interface to
the module is through the Ovation I/O bus; therefore, this module is native to Ovation as opposed
to an add-on or linking approach.
The Ovation Foundation Fieldbus module interfaces with one or two networks. The module
supports redundancy and can be installed on each network. Only one module can be the master
at any given time. Inter-module redundancy communication is handled through a private RS232
communication link between the redundant pair. The communication cable is connected to a
RJ45 jack on the Pmod.
Foundation Fieldbus subsystems
2 (non-redundant) 5X00301G01 1C31238H01 (cavity insert)

2 (redundant) 5X00301G01 5X00327G01
222 OW350_R1007
Ethernet Link Controller – The Ethernet Link Controller provides an interface with a single
Ethernet link. This module uses a straight RJ45 connector which allows the port to be accessed
outside of the Electronics module.
Ethernet Link Controller subsystems
2 5X00419GO1 1X000569H01
5.15.1 How do I troubleshoot Profibus?
There are three different ways that you can diagnose Profibus health: through the module itself,
through the slave devices, and by visually inspecting the module LED lights in your Controller.
Diagnostic information for each is accessed differently:
 Module information displays in the module (RM) and node (RN) records status value.
 Slave device information displays in the Controller Diagnostics utility.
Refer to the Ovation Controller User Guide for more information about the Controller
Diagnostics utility.
 LED information is found on the front of the module device in your Controller cabinet.
Some general symptoms and suggested solutions for Profibus troubleshooting include:
SYMPTOM POSSIBLE CAUSE SOLUTION
The module never takes Software has been incorrectly Use the Controller Diagnostics utility to
control and data does not loaded or not loaded at all on the verify that the proper software is loaded
update. module. There is no Profibus on the modules. Update if necessary.
configuration file (.DBM) loaded.
Check the module configuration. Check
the segment and device configuration
(in the A2 field of the node records).
Perform a drop load if necessary.
Module and node record Software has been incorrectly Use the Controller Diagnostics utility to
points periodically go to loaded or not loaded at all on the verify that the proper software is loaded
bad quality or into sensor module. on the modules. Update if necessary.
alarm.
For a redundant module, it is If this is a simplex module, verify that the
possible that both modules think module is in control (for each configured
they are in control. segment).
If this is a redundant module, check to
see that both modules are not in control.
During a redundant The Profibus watchdog timer Adjust the watchdog times in the
module failover, one of expired and the devices think that Profibus Engineering window.
these situations occurs: they have lost connection to the Depending on the Profibus and Ovation
 Bus fault lights bus. traffic (number of modules, segments,
illuminate on Profibus devices, and I/O), a failover takes
devices. anywhere from 100ms to 400ms. It is
recommended that the Profibus network
 Points go into bad watchdog time be set to at least 1,000
quality. ms.
The module failed An internal fault caused a module Reboot the module (remove and
(general). to fail. reinstall). If the problem persists with
this module, it is possible the hardware
OW350_R1007 223

is bad.
All devices on a simplex Profibus lost communication with Check that the cabling on the failed
segment go into alarm the segment. segment is intact and connections are
properly secured.
A redundant module Profibus lost communication with Check that the cabling on the failed
failed over due to a an entire segment (indicated by segment is intact and connections are
communication fault on a bits 8 and 9 in the node record). properly secured. Reboot the module
segment. (remove and reinstall).
Troubleshooting the bus using the LEDs
You can examine the physical LED lights on the front of the bus module. The module displays
seven LEDs (on the right side, from top to bottom, position 6-12):
 ACT: lights when the card is on.
 FDX: lights when the Ethernet is on.
 S4: lights when the backup bus module is detecting activity on the bus.
 S2: lights when the module is active and running.
 S1: lights when the Controller is actively exchanging information with the bus module.
224 OW350_R1007
Logic card diagnostic LEDs - Profibus (DP)
LED DESCRIPTION
P (green) Power OK LED. Lit when the logic board's +5V and +3.3V digital supply voltage level
is OK.
module.
E No LED.
I (red) Internal Fault LED. Lit when the forced error bit (bit 1) of the configuration register is
set, or when the Ovation Controller is not communicating with the module.
1-5 No LED.
6 ACT (green) Ethernet activity.
7 FDX (yellow) Full duplex Ethernet communication.
8-12 S4 - S0 General purpose red LEDs. Lit under firmware control of the ARM9 processor.
(red)
13 - 16 No LED.
What are Profibus online diagnostics?
The Profibus Online Diagnostics tool provides live diagnostics information from a selected
Profibus network. When connected to the Profibus network, you are able to see the status of
slaves on the network along with diagnostic and running state information for the slaves and the
master. While not a complete set of diagnostics, the information can be used when
troubleshooting slave failures and detecting certain communication problems.
What is the best way to troubleshoot redundant module pairs?
The following tables describe common operating scenarios and failures for a redundant Profibus
module pair. The operating state for the primary and secondary modules is included along with
the corresponding RM record status values (A2 field).
It is important to remember that once a module fails over, it stays failed until it is rebooted. Before
rebooting a failed module, you should investigate the cause of the problem and correct the
problem. A failover can only occur to a healthy backup module. Paying attention to the status
values in the port node (RN) records and the module (RM) records should help narrow down the
cause of a failover.
OW350_R1007 225
Scenario 1: Loss and restoration of communication to segment 1 (assuming both

segments are in use)
In this scenario, communication is lost to a port. This situation could be caused by either a failure
of the module hardware associated with the port or, more likely, a cable failure (for example, if a
cable is removed). Once communication is lost to a segment, the module remains in a
communication failure state until the module is rebooted.
ACTION PRIMARY SECONDARY DESCRIPTION

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module is

(0x45C5) (0x4AC5) operating in control and the other is in backup.
Loss of Comm Fail Control When communication is lost to port 1, and
communication on (0x4005) (0x45C5) there is a healthy backup module, the
port 1 (for controller fails over. The secondary module is
example, a cable now in control and the primary is in a
pulled from The port node communication fail state. The port node record
primary module record will be in for the primary module port 1 is in alarm and
port 1) alarm. indicated a failure on port one (bits 7 and 8 =
01).
Loss of Comm Fail Control No failover occurs because there is not a
communication on (0x4005) (0x4585) healthy backup. The Comm 1 ok bit is clear in
port 1 of the the Secondary RM record status. All of the
secondary (for points on the port will be in bad quality and
example, cable stop updating.
pulled )
Communication Comm Fail Control The Comm ok bit returns. With communication
restored on port 1 (0x4005) (0x45C5) restored, the points associated with the port
of the secondary will no longer be in bad quality. The primary
module still remains failed.
Reboot primary Backup Control The primary module will bootup in backup
module (0x4AC5) (0x45C5) whether or not the cable has been reinstalled.
It is critical when rebooting a module to
troubleshoot and fix the issue that caused the
problem.
226 OW350_R1007
Scenario 2: Sudden loss of the in-control module (assuming both segments are in use)
In this scenario, the primary module is removed and a failover occurs to the secondary. The
secondary module is now in control but cannot failover until the primary is reinstalled and enters
the backup operating state.

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module is

(0x45C5) (0x4AC5) operating in control and the other is in backup.
Sudden loss of No module Control Module failover occurs (100ms to 400ms) and
the in-control (0x0) (0x45C5) the secondary module takes control.
module (for
example, removal
of the primary
module)
Loss of No module Control There is a communication failure on the
communication on (0x0) (0x4585) secondary module.
Port 1 of the
secondary module Because there is no healthy backup, the
module cannot failover.
Because communication was lost, all points
assigned to Port 1 will go into alarm.
Primary module Backup Control Primary module reboots, sees its partner is in
reboots (0x4AC5) (0x45C5) control, and goes into backup.
To troubleshoot using the module and node records

1. Access Point Information from your Ovation Applications folder at the Operator Station to view
the module or node record. Refer to the Ovation Operator Station User Guide for more
information about the Point Information function.
2. Navigate to the Value/Status tab in the module or node record (the value used for the module
and node record is the A2 field).
3. Review the collected bit information about the module or node.
Node record information
You can use the segment node records and the device node records to troubleshoot. Module bits
for each record type and their descriptions are listed in the following table:
Note: The items in bold only apply to Ports configured for Profibus Port redundancy and are not
used for Module redundancy or regular simplex Profibus configuration.
OW350_R1007 227
Segment/Port Node Record Bit Definitions
BIT ALARM DESCRIPTION SET RESET NOTES

STATE
0 REDUND CHA 1 0 Profibus Only. Port is part

of redundant pair (Channel
A).
1 REDUND CHB 1 0 Profibus Only. Port is part
of redundant pair (Channel
B).
2 0 PORT STATUS NORMAL ALARM
3 RDP STATUS ON OFF

4 0 MODULE STATUS NORMAL ALARM
5 OP MODE 00-OFF 1 0
01-CTRL 10-BK
6 OP MODE 00-OFF 1 0
01-CTRL 10-BK
7 1 FAIL 00-NO 01-P1 1 0 Profibus only.
10-P2 11-GEN
8 1 FAIL 00-NO 01-P1 1 0 Profibus only.
10-P2 11-GEN
9
10 CONTROL TASK 1 0 0-based same as in RM
IDX (BIT 0) record.
IDX (BIT 1) record.
IDX (BIT 2) record.
13
14 1 BKP LOST COMM 1 0 Profibus Only
TO MASTER
15 FAILOVER IN YES NO Profibus only (NOT alarmed
PROGRESS as in previous version).
228 OW350_R1007
When a segment record goes into bad quality (point is not functioning properly), all of the devices
and I/O points assigned to the segment also go into bad quality. The segment record goes into
bad quality when Bit 4 is clear.
Note: The items in bold only apply to Ports configured for Profibus Port redundancy and are not
used for Module redundancy or regular simplex Profibus configuration.
Device Node Record Bit Definitions

STATE
0 0 DEVICE YES NO For redundant ports, applies

CONFIGURED to Channel A or Channel B
as indicated by bits 14 and
15.
1 0 DEVICE STATE NORMAL ALARM For redundant ports, applies

to Channel A or Channel B
15.
2 ADDITIONAL DIAG YES NO For redundant ports, applies

STATUS to Channel A or Channel B
15.
3 0 PORT STATUS NORMAL ALARM For redundant ports, applies
to Channel A or Channel B
15.
4
5
6 PORT 1 YES NO
7 PORT 2 YES NO
8
9 DEVICE YES NO Profibus only. For
CONFIGURED redundant ports, applies to
Channel A or Channel B as
indicated by bits 14 and
15.
10 DEVICE STATE NORMAL ALARM Profibus only. For
redundant ports, applies to
15.
11 ADDITIONAL YES NO Profibus only. For
DIAG STATUS redundant ports, applies to
15.
OW350_R1007 229

STATE
0 0 DEVICE YES NO For redundant ports, applies

CONFIGURED to Channel A or Channel B
15.
12 PORT STATUS NORMAL ALARM Profibus only. For

redundant ports, applies to
15.
13 PORT REDUND YES NO Profibus only. Indicates if
the device is part of a
redundant pair. Profibus
port redundancy only.
14 CH A Used YES NO Profibus only. Indicates
the data from Channel A
being written to the
Ovation network. This
follows the same logic as
presented in the Ovation
Native Profibus Port
Redundancy. For more
information refer to:
Ovation Native Profibus Port
Redundancy.
15 CH B Used YES NO Profibus only. Indicates
the data from Channel A
being written to the
Ovation network. This
follows the same logic as
presented in the Ovation
Native Profibus Port
Redundancy. For more
information refer to:
Ovation Native Profibus Port
Redundancy.
When a device record goes into bad quality, all of the points assigned to the device also go into
bad quality. A module is considered to be in bad quality in the following cases:
 Bit 0 clear (the device is not configured on the Profibus network).
 Bit 1 clear (the device state is bad on the Profibus network).
 Bit 3 clear (the associated segment is in a bad state).
Bit 2 is an indication that additional diagnostics are available. It is not an indication of health or
status of a device. Typically, this bit is set. However, if it is not set, it does not indicate an issue
with the device.
230 OW350_R1007
Module record information
The Profibus-related module record values are:
MODULE R E C O R D ( A2 FIELD) DESCRIPTION

BIT
0 Module configured on the bus.
1 (Not applicable)
2 Redundant Indication
0 = Simplex module
1 = Redundant (Module acknowledges redundancy)
3 (Not applicable)
4 (Not applicable)
5 Internal Module Fault (Failover Request)
6 Bus Communication Status (Segment 1)
8,9 Segment 1 Operating Mode (00 = Off, 01 = Primary, 10 = Backup)
12 (Not applicable)
13 (Not applicable)
14 System Up
15 (Not applicable)
OW350_R1007 231
Each nibble (4-bits) can be analyzed to determine the operating state of the module. The
following is an example of a status value for a redundant module:
Figure 51: Status value diagram
Typically, for a non-redundant (simplex) module, the status value should equal something like
0x45C1 (assuming both segments are in use). For a redundant module typical status values
would be 0x45C5 (redundant, online, both segments communicating) for the in control module
and 0x4AC5 for the backup. The second nibble (which includes bits 6 and 7) indicates the
communication status of each segment. If only one segment is configured, only the bit
corresponding to that segment (bit 6 if segment 1 and bit 7 for segment 2) is considered by the
Controller in evaluating the overall module health.
232 OW350_R1007
Simplex module information
Simplex modules refer to non-redundant Profibus modules. The only valid operating states are
online and off (no backup).
In the following tables, if a value is indicated by “X” it means the exact value is not important for
the purpose of describing that case. Common record values for a simplex module are:
PRIMARY DESCRIPTION
VALUE
0x45C1 The module is healthy and running and has control of the Profibus network. Both
segments are healthy and should be communicating.
0x4001 The module is configured but both segments are in the off mode. It is possible that the
module has either failed (for example, lost communication to a segment) or is in the
process of booting up.
0xXAXX The module is operating in backup mode. This should never occur for a simplex
module. If this does occur for a simplex module, check the configuration of the module
and reboot the module.
0xXXX5 The module is configured as redundant.
0xXXX4 In this case, the module is configured as redundant but is not attached to the bus. Verify
the module configuration and reboot the module.
OW350_R1007 233
Redundant module information
In the following tables, if a value is indicated by “X” it means the exact value is not important for
the purpose of describing that case. Redundant modules operate as part of a pair. Their operating
state can be Off, Control, or Backup.
Common record values for a redundant module pair are:
PRIMARY SECONDARY DESCRIPTION

VALUE VALUE
0x45C5 0x4AC5 Both modules are running and healthy. The primary module is in
control. The secondary module is in backup.
0xX5XX 0xX5XX Both modules are in control. This causes faults on the Profibus
network. Devices on the Profibus network will begin to go from
configured (healthy) to unconfigured (unhealthy). This also causes
the segment and device node records to go into and out of bad
quality (along with the points associated with those
segments/devices).
Reboot the Profibus modules.
0xXAXX 0xXAXX Both modules are in backup. No I/O can be exchanged. Reboot both
modules.
0xXXX1 0xXXXX There is a configuration error. The module is expected to be
redundant but the redundant bit (bit 2 of the module record) is not set.
Check the module configuration. Clear and reload the Controller. If
the problem persists, reboot the module (remove and reinstall).
0xXXXX 0xXXX1 There is a configuration error. The module is expected to be
redundant but the redundant bit (bit 2 of the module record) is not set.
Check the module configuration. Clear and reload the Controller. If
the problem persists, reboot the module (remove and reinstall).
0xX6XX 0xXXXX There is a mismatch in the segment operating state. If both segments
are in use, the operating mode of both segments should be the same
0xX9XX (both backup or both control).
Reboot the module (remove and reinstall). If the problem persists,
reboot both modules.
0xXXXX 0xX6XX There is a mismatch in the segment operating state. If both segments
are in use, the operating mode of both segments should be the same
0xX9XX (both backup or both control).
Reboot the module (remove and reinstall). If the problem persists,
reboot both modules.
0xX100 0xXXXX Only one segment is in control or backup and the other is in the off
state. If the segment is not in use, it should be in the off state. If a
0xX200 segment is off but is in use and the other segment is in control or
0xX400 backup, then there is an error. Reboot the modules and the
Controller.
0xX800
0xXXXX 0xX100 Only one segment is in control or backup and the other is in the off
state. If the segment is not in use, it should be in the off state. If a
0xX200 segment is off but is in use and the other segment is in control or
0xX400 backup, then there is an error. Reboot the modules and the
Controller.
0xX800
234 OW350_R1007
What is the best way to troubleshoot redundant module pairs?
The following tables describe common operating scenarios and failures for a redundant Profibus
module pair. The operating state for the primary and secondary modules is included along with
the corresponding RM record status values (A2 field).
It is important to remember that once a module fails over, it stays failed until it is rebooted. Before
rebooting a failed module, you should investigate the cause of the problem and correct the
problem. A failover can only occur to a healthy backup module. Paying attention to the status
values in the port node (RN) records and the module (RM) records should help narrow down the
cause of a failover.
Scenario 1: Loss and restoration of communication to segment 1 (assuming both

segments are in use)
In this scenario, communication is lost to a port. This situation could be caused by either a failure
of the module hardware associated with the port or, more likely, a cable failure (for example, if a
cable is removed). Once communication is lost to a segment, the module remains in a
communication failure state until the module is rebooted.

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module

(0x45C5) (0x4AC5) is operating in control and the other is in
backup.
Loss of Comm Fail Control When communication is lost to port 1, and
communication (0x4005) (0x45C5) there is a healthy backup module, the
on port 1 (for controller fails over. The secondary module
example, a cable is now in control and the primary is in a
pulled from The port node communication fail state. The port node
primary module record will be record for the primary module port 1 is in
port 1) in alarm. alarm and indicated a failure on port one
(bits 7 and 8 = 01).
Loss of Comm Fail Control No failover occurs because there is not a
communication (0x4005) (0x4585) healthy backup. The Comm 1 ok bit is clear
on port 1 of the in the Secondary RM record status. All of the
secondary (for points on the port will be in bad quality and
example, cable stop updating.
pulled )
Communication Comm Fail Control The Comm ok bit returns. With
restored on port 1 (0x4005) (0x45C5) communication restored, the points
of the secondary associated with the port will no longer be in
bad quality. The primary module still remains
failed.
Reboot primary Backup Control The primary module will bootup in backup
module (0x4AC5) (0x45C5) whether or not the cable has been
reinstalled. It is critical when rebooting a
module to troubleshoot and fix the issue that
caused the problem.
OW350_R1007 235
Scenario 2: Sudden loss of the in-control module (assuming both segments are in use)
In this scenario, the primary module is removed and a failover occurs to the secondary. The
secondary module is now in control but cannot failover until the primary is reinstalled and enters
the backup operating state.

MODULE MODULE
STATE STATE
No fault Control Backup Everything is working properly - one module

(0x45C5) (0x4AC5) is operating in control and the other is in
backup.
Sudden loss of No module Control Module failover occurs (100ms to 400ms) and
the in-control (0x0) (0x45C5) the secondary module takes control.
module (for
example, removal
of the primary
module)
Loss of No module Control There is a communication failure on the
communication (0x0) (0x4585) secondary module.
on Port 1 of the
secondary Because there is no healthy backup, the
module module cannot failover.
Because communication was lost, all points
assigned to Port 1 will go into alarm.
Primary module Backup Control Primary module reboots, sees its partner is in
reboots (0x4AC5) (0x45C5) control, and goes into backup.
Resolving a slave alarm
If a slave device detects an abnormal situation, it can raise a high priority alarm.
There are two different information bits that the slave device can communicate for diagnostic
purposes: slave configured and slave active bits. You can implement a monitoring scheme to
compare these values and alert you to potential problems.
Investigating a Profibus fault code
Profibus generates fault codes and error messages, which are reported to the Error Log and the
System Status diagram. Error codes and messages can be used to diagnose drop and system
problems.
Some error messages may contain a series of hex numbers. These are typically Fault Codes from
the Controller and have the following format:
Profibus uses the Fault Code - 66, Fault ID - B.
You can diagnose most Fault Codes that appear by accessing the System Viewer application. For
more information on fault codes for the 3.5 release please refer to the Ovation Operator Station
User Guide.
236 OW350_R1007
5.15.2 How do I troubleshoot DeviceNet?
There are three different ways that you can diagnose DeviceNet health: through the module itself,
through the slave devices, and by visually inspecting the module LED lights in your Controller.
Diagnostic information for each is accessed differently:
 Module information displays in the module (RM) and node (RN) records status value.
 Slave device information displays in the Controller Diagnostics utility.
Refer to the Ovation Controller User Guide for more information about the Controller
Diagnostics utility.
 LED information is found on the front of the module device in your Controller cabinet.
Some general symptoms and suggested solutions for DeviceNet troubleshooting include:
The module never takes Software has been incorrectly Use the Controller Diagnostics utility to
control and data does not loaded or not loaded at all on verify that the proper software is
update. the module. There is no loaded on the modules. Update if
DeviceNet configuration file necessary.
(.DBM) loaded.
Check the module configuration.
Check the segment and device
configuration (in the A2 field of the
node records). Perform a drop load if
necessary.
Module and node record Software has been incorrectly Use the Controller Diagnostics utility to
points periodically go to loaded or not loaded at all on verify that the proper software is
bad quality or into sensor the module. loaded on the modules. Update if
alarm. necessary.
The module failed An internal fault caused a Reboot the module (remove and
(general). module to fail. reinstall). If the problem persists with
this module, it is possible the hardware
is bad.
All devices on a segment DeviceNet lost communication Check that the cabling on the failed
go into alarm with the segment. segment is intact and connections are
properly secured.
OW350_R1007 237
Diagnostic LEDs - DeviceNet
LED DESCRIPTION
P (green) Power OK LED. Lit when the logic board's +5V and +3.3V digital supply voltage level is
OK.
module.
E No LED.
I (red) Internal Fault LED. Lit when the forced error bit (bit 1) of the configuration register is set,
or when the Ovation Controller is not communicating with the module.
1-5 No LED.
8-12 S4 - S0 General purpose red LEDs. Lit under firmware control of the ARM9 processor.
(red)
13 - 16 No LED.
Field card LED indications Channels 1 and 2
LED LED STATE ME ANING
RDY (red) ON Device is ready.

5 Hz Flashing Firmware Download in progress.
1Hz Flashing Device in Bootloader mode and is awaiting firmware download.
Non-Cyclic Flashing Hardware or runtime error.
OFF Device has no power or hardware defect.
RUN (green) ON Communication is established with at least one field device.
5 Hz Flashing If MNS LED is GREEN then Device is established, but
communication is stopped, If MNS LED is flashing RED then NO
slave has been found.
Non-Cyclic Flashing At power up it indicates configuration missing, at runtime it
indicates watchdog timeout.
OFF No Communication.
MNS OFF Device is not on-line
Module/  The device has not completed the Dup
Network Status
 MAC_ID test yet.
(Combined  The device may not be powered
red/green)
Steady Green The device is operating in a normal condition and the device is
on-line with connections in the established state.
Flashing Green The device is operating in a normal condition and the device is
on-line with no connections in the established state.
238 OW350_R1007
LED LED STATE ME ANING
Flashing Red Any one or more of the following conditions:

 Recoverable fault
 One or more I/O connections has timed out
 No network power present.
Steady Red Device has an unrecoverable fault and may need replacing
What are DeviceNet online diagnostics?
The DeviceNet Online Diagnostics tool provides live diagnostics information from a selected
DeviceNet network.
When connected to the DeviceNet network, you are able to see the status of slaves on the
network along with diagnostic and running state information for the slaves and the master.
While not a complete set of diagnostics, the information can be used when troubleshooting slave
failures and detecting certain communication problems.
Interface - DeviceNet
Two DeviceNet Interfaces are provided on the Profibus/DeviceNet field card. Each Interface is
based on a communication processor with a communication interface for the DeviceNet network
and an integral dual port memory for communication with the host processor.
Communication between the dual port memory and the host processor on the logic card is
through an 8-bit parallel interface mapped into the memory space of the host processor. The
circuitry includes a galvanically isolated CAN interface for connection to the DeviceNet network.
Each connection to the network is through a female 5-pin connector or through the Ovation base.
These two connectors (one for each interface) are available on a personality module. Line
termination and biasing are part of the network mating connector per standard.
The EC1 processor provides an RS232 port for troubleshooting purposes. These ports (one for
each interface) are made available through a 5-pin header and can only be accessed with the
module cap removed.
Main Features
1. DeviceNet field cards provide 2 independent galvanically isolated DeviceNet channels. Each
channel uses a galvanically isolated 5W switching regulator to convert 24 VDC DeviceNet
network power to 5VDC to power DeviceNet field side components. This provides galvanic
isolation between the DeviceNet field network and the Ovation module. Additionally, the
personality card uses individual channel isolated ground and power planes to achieve channel
to channel isolation.
2. Each DeviceNet channel uses an EC-1 ASIC microcontroller, to act as a DeviceNet master
Controller.
3. Each EC-1 provides CMOS level CAN differential signals to and from the galvanically isolated
DeviceNet transceiver chip PCA82C251. The PCA82C251 then translates them to CAN level
differential signal for DeviceNet communication.
OW350_R1007 239
4. Two DeviceNet standard 5-pin Combicon connectors are located on the DeviceNet
personality module and require standardized DeviceNet cabling.
5. The DeviceNet personality also routes the 5 standard DeviceNet signals from the Combicon
connectors to the Ovation base to provide Maximum DeviceNet cabling flexibility.
Figure 52: DeviceNet EMOD and PMOD block diagram
To troubleshoot using the module and node records

1. Access Point Information from your Ovation Applications folder at the Operator Station to view
the module or node record. Refer to the Operator Station User Guide for more information
about the Point Information function.
2. Navigate to the Value/Status tab in the module or node record (the value used for the module
and node record is the A2 field).
3. Review the collected bit information about the module or node.
240 OW350_R1007
To use the module record
The DeviceNet-related module record values are:
MODULE R E C O R D ( A2 FIELD) DESCRIPTION

BIT
0 Module configured on the bus.
1 (Not applicable)
2 Redundant Indication
0 = Simplex module
1 = Redundant (Module acknowledges redundancy)
3 (Not applicable)
4 (Not applicable)
5 Internal Module Fault (Failover Request)
12 (Not applicable)
13 (Not applicable)
14 System Up
15 (Not applicable)
OW350_R1007 241
Each nibble (4-bits) can be analyzed to determine the operating state of the module.
In the following tables, if a value is indicated by “X”, it means the exact value is not important for
the purpose of describing that case. Common record values for a module are:
PRIMARY DESCRIPTION
VALUE
0x45C1 The module is healthy and running and has control of the DeviceNet network. Both
segments are healthy and should be communicating.
0x4001 The module is configured but both segments are in the off mode. It is possible that the
module has either failed (for example, lost communication to a segment) or in the
process of booting up.
0xXAXX The module is operating in backup mode. This should never occur for a simplex
module. If this does occur for a simplex module, check the configuration of the module
and reboot the module.
0xXXX5 The module is configured as redundant (does not apply for DeviceNet).
0xXXX4 In this case, the module is configured as redundant but is not attached to the bus.
Verify the module configuration and reboot the module.
To use the node record
You can use port node records and device node records to troubleshoot. Module bits for each
record type and their descriptions are:
Port Node Record (A2 Field)
MODULE DESCRIPTION
BIT
0 (Not applicable)
1 (Not applicable)
2 Port Health
3 RDP Status (R-Line Communication Status)
4 Module Status
5,6 Operating Mode (00=OFF, 01=CONTROL)
7,8 (Not applicable)
9 (Not applicable)
10,11,12 Control task index (0-based)
13,14 (Not applicable)
15 (Not applicable)
242 OW350_R1007
When a segment record goes into bad quality, so do all the devices and I/O points assigned to the
port. The port record goes into bad quality when Bit 4 is clear (module is in bad health).
Device Node Record (A2 Field)
MODULE DESCRIPTION
BIT
0 Configured Configuration
1 State Configuration
2 Additional Diagnostics
3 Segment Status
4 (Not applicable)
5 (Not applicable)
6,7 Port Number (1 or 2)
8-15 (Not applicable)
When a device record goes into bad quality, so do all the points assigned to the device. A module
is considered to be in bad quality in the following cases:
 Bit 0 clear (the device is not configured on the DeviceNet network)
 Bit 1 clear (the device state is bad on the DeviceNet network)
 Bit 3 clear (the associated segment is in a bad state)
Bit 2 is an indication that additional diagnostics are available. It is not an indication of health or
status of a device. Typically, this bit is set. However, if it is not set, it does not indicate an issue
with the device.
To resolve a slave alarm
If a slave device detects an abnormal situation, it can raise a high priority alarm.
There are two different information bits that the slave device can communicate for diagnostic
purposes: slave configured and slave active bits. You can implement a monitoring scheme to
compare these values and alert you to potential problems.
OW350_R1007 243
To investigate a DeviceNet fault code
DeviceNet generates fault codes and error messages which are reported to the Error Log and the
System Status diagram. Error codes and messages can be used to diagnose drop and system
problems.
Some error messages may contain a series of hex numbers. These are typically Fault Codes from
the Controller and have the following format:
Profibus uses the Fault Code - 66, Fault ID - B.
For Ovation 3.5 and later releases, fault codes are part of Ovation software and are displayed in
the Ovation System Viewer application. Refer to the Ovation Operator Station User Guide for
additional information
5.15.3 How do I diagnose Foundation Fieldbus device errors?
The Developer Studio system tree provides diagnostic information about your Fieldbus devices.
Click on a Fieldbus device to see its properties displayed in the right side of the window, or use
the right-click menu to interact with the device.
Diagnostic Logic card LEDs - Foundation Fieldbus
LED DESCRIPTION
P (green) Power OK LED. Lit when the logic board's +5V and +3.3V digital supply voltage
level is OK.
C (green) Communication OK LED. Lit when Ovation Controller is communicating with
module.
E, I, 1 - 5 No LED.
8 - 12 S4 - S1 (red) General purpose red LEDs. Lit under firmware control of the ARM9 processor.
13 - 16 No LED.
244 OW350_R1007
Interface - Foundation Fieldbus
Two Foundation Fieldbus interfaces are provided on the Foundation Fieldbus field card. Each
interface provides an ARM7 processor for stack management, Fieldbus Interface Chip (FINCH)
and a Media Attachment Unit (Shortbow MAU). Communication between the ARM7 processor
and the host processor on the logic card is through an asynchronous serial interface running at up
to 38.4 Kbaud.
The connection to the Fieldbus network is via the base unit's terminal block. Foundation Fieldbus
Power conditioners and Power supplies must be provided externally. A Personality Module is
provided that includes an RJ45 jack for the redundancy cable as well as two 9-pin D connectors
(one per channel) to access a second serial port on the ARM7 processor. The second serial port
is intended for troubleshooting purposes; however, the fact that the interface is present does not
imply software support.
Additionally, a JTAG port is available to support emulation and firmware development. This port is
only available with the modules removed from the case. Note that the JTAG port is not available
for boundary scan testing.
Main features
1. Each Foundation Fieldbus Field Card contains two independent galvanically isolated Fieldbus
channels. Each channel provides galvanic isolation between the Fieldbus field power and the
main 24VDC power supply. Additionally, the Foundation Fieldbus Field Card employs signal
separation to achieve channel to channel isolation.
2. Foundation Fieldbus Field cards use a Foundation Fieldbus approved H1 host Controller
stack and are in compliance with IEC standard 61158.
3. Each Fieldbus channel uses an ARM7 microcontroller to control the Fieldbus data
communications. Each ARM7 uses a 38.4 kbaud UART interface to interface data with the
Ovation module logic card. This allows the logic card to have positive control over the
Fieldbus network traffic.
4. Each Fieldbus channel uses a Shortbow Media Attachment Unit (MAU) application specific
integrated circuit (ASIC) to translate CMOS level logic to current modulated (+ and - 10 mA)
Fieldbus signals. The Shortbow derives its power from the 9 - 32 VDC (typically 24VDC)
Fieldbus network.
5. Fieldbus signals coming from the MAU are optically coupled and translated to CMOS logic
prior to the FINCH and microprocessor to maintain galvanic isolation.
OW350_R1007 245
6. Each Fieldbus channel uses a Fieldbus Interface Chip ASIC or FINCH to translate
Manchester encoded CMOS logic level signals coming from the MAU into 8-bit register values
to be passed to the microcontroller.
Figure 53: Fieldbus interface network chip (FINCH)
Checking port integrity
If a Fieldbus card has an integrity problem, expand the card to see which port has the problem.
Select each port and look at the port's status. Possible port status values are:
 Good: Good basic communications with all devices on this port.
 No Termination on Link: This port is not terminated. Check attached cable.
 Link Error: PCMCIA Card problem exists. Replace the H1 card.
 Duplicate Address on Link: Another device is currently communicating at this port's
address.
 H1 Card Problem: Replace the H1 card.
 One or more function block problems on link or device problem: Expand the port and
check the state of each Fieldbus device on the port. Any state other than commissioned
indicates a potential problem with that Fieldbus device.
Using the ports statistics tab
The overall port statistics (see page 249) and detailed port statistics (see page 252) tabs provide
a broad view of communication activity on the port. To access these statistics:

2. Navigate to the port you are checking:
Card
Port
246 OW350_R1007
3. Right-click on the Port and click Statistics.

4. Click the Ports tab on the Statistics window to view the overall port and detailed port
statistics. The Fieldbus Statistics window opens up.
Figure 54: To open statistic window
OW350_R1007 247
5. Click on Port Statistics tab and notice the following:

 Click Reset to refresh the Port Statistics window.
 Select check-box: Automatically update every and enter the desired number of
seconds in the seconds field so that the Port Statistics tab refreshes itself automatically
after a defined interval.
 Click Close to close the window.
Figure 55: Ports Statistics tab
248 OW350_R1007
Overall segment statistics
Once you access the Fieldbus Statistics window, click on Port Statistics tab.
Figure 56: Overall Segment Statistics section
Overall Port Statistics include:

Invalid responses
Stack errors
Timeouts
Retries
OW350_R1007 249
 Click Reset to refresh the Port Statistics window.

seconds in the seconds field so that the Port Statistics tab refreshes itself automatically
Note: If any of the port statistics and communication statistics are continually increasing, a
potential communications problem could exist on this port. To isolate the problem, investigate
the communication statistics on each Fieldbus device.
The following table provides error messages and descriptions.
Overall segment statistics
MESSAGE DESCRIPTION
Total Dll FCS Failures The total number of frames that the H1 card receives with a Frame Check
Sequence (FCS) error. If this statistic is steadily increasing, a network
problem might exist.
Total Dll Fragments The total number of frame fragments that the H1 card has received on
Received this port. Possible causes are that the H1 card received an invalid data
link packet or that the H1card did not have a buffer to receive the packet.
(This could also cause the Total Dll Receive Q Full to increment.) If this
statistic is steadily increasing, a network problem might exist or the H1
card may be operating at capacity.
Total Dll Good PDUs The total number of data link packets that the H1 card has received on
Received this port.
Total Dll PDUs Transmitted The total number of data link packets that the H1 card has sent on this
port.
Total Dll Receive Q Full The total number of data link packets that the H1 card could not receive
because it did not have a buffer to receive the packet. If this statistic is
steadily increasing, the H1 card might be operating at capacity.
Total Dll Retries The total number of data link packets that the H1 card had to retry. If this
statistic is steadily increasing, check the communication statistics for each
device to see which device is causing the problem. To check
communication statistics on a device, right-click on the device and select
Display Communication Statistics. The number of retries to a Fieldbus
device generally should be much less than 1 percent of the total requests
sent to the device. If this is not the case, either the device is bad or there
is a network problem.
Total Dll Time Disc Changes The total number of data link time discontinuous changes.
Total Indications The total number of Fieldbus indications received from this port. Data
published by a Fieldbus device causes this statistic to steadily increment.
Total Invalid Response The total number of Fieldbus requests that failed due to a Fieldbus device
returning an error. If the total number of invalid responses is continually
incremented, first check to see if any devices on the port need to be
downloaded. If any devices need to be downloaded, then download the
devices and reset the port statistics.
250 OW350_R1007
MESSAGE DESCRIPTION
Total Local Stack Errors The total number of Fieldbus requests that failed because the local
communication stack returned a response that indicated an error. The H1
card might need to be replaced if this statistic is steadily increasing.
Total Publish Errors The total number of publishing updates received from the Controller that
were in error. A steadily increasing number could indicate that either the
Controller or the card needs to be downloaded.
Total Request Sent The total number of Fieldbus requests that have been sent on this port.
Total Request TimeOut The total number of Fieldbus requests that failed because the Fieldbus
device did not return a response. If this statistic is steadily increasing,
check the communication statistics for each device to see which device is
causing the problem. To check communication statistics on a device,
right-click on the device and select Display Communication Statistics.
Total Stack Rejected The total number of Fieldbus requests that failed because the local
Request communication stack did not accept the request. The H1 card might need
to be replaced if this statistic is steadily increasing.
Total Subscribe Errors The total number of subscriber updates received from a Fieldbus device
that were in error. A steadily increasing number could indicate that a
device may have a problem.
Total Valid Responses The total number of successful Fieldbus requests that have been sent on
this port.
OW350_R1007 251
Detailed port statistics
Once you access the Fieldbus Statistics window, click on Port Statistics tab.
Figure 57: Detailed Ports Statistics section
Detailed Port Statistics include:
 Initiates
 Aborts
 Identifies
252 OW350_R1007
The following table provides error messages and descriptions.
Detailed port statistics
MESSAGE DESCRIPTION
FMS Aborts The number of Fieldbus disconnection requests that were sent on this port. If
this statistic steadily increments after all devices are commissioned and
downloaded, either the Fieldbus network is noisy or a problem exists with a
Fieldbus device. To isolate the problem, check the communication statistics
on each Fieldbus device attached to this port. To check communication
statistics on a device, right-click on the device and select Display
Communication Statistics.
FMS AckEvents This message is generated when an event generated by an attached Fieldbus
device is being acknowledged.
FMS Downloads This message is generated when a Fieldbus domain is downloaded to either
the local stack or to an attached Fieldbus device. A Fieldbus domain contains
programs or data. For example, a Fieldbus domain can load the LAS
schedule.
FMS GetOds The number of Fieldbus get object description requests that were sent on this
port.
FMS Identifies The number of Fieldbus FMS (Fieldbus Message Service) identify requests
that were sent on this port.
FMS InfoReports The number of Fieldbus information reports that were sent on this port. These
requests are sent as the result of data that is published by the H1 Card.
FMS InitDownloads The number of Fieldbus initiate domain download requests that were sent on
this port. These requests are sent whenever the LAS (Link Active Scheduler)
schedule is downloaded to this port. The LAS is a centralized bus scheduler
that manages the communication on the Fieldbus and maintains the live list (a
list of Fieldbus devices that are responding to the LAS). The H1 card functions
as the LAS.
FMS Initiates The number of Fieldbus connection requests that were sent on this port. If this
statistic steadily increments after all devices are commissioned and
downloaded, either the Fieldbus network is noisy or a problem exists with a
Fieldbus device. To isolate the problem, check the communication statistics
on each Fieldbus device attached to this port. To check communication
statistics on a device, right-click on the device and select Display
Communication Statistics.
FMS Reads The number of Fieldbus read requests that were sent on this port.
FMS Rejects This message indicates that the H1 card is sending an FMS Reject message.
FMS Statuses The number of Fieldbus status requests that were sent on this port.
FMS TermDownloads This is the number of Fieldbus terminate domain download requests that were
sent on this port. These requests are sent whenever the LAS schedule is
downloaded to this port.
FMS Writes The number of Fieldbus write requests that were sent on this port.
SM ClearAddress The number of Fieldbus requests that were sent to clear the address of a
Fieldbus device.
SM ClearPdTags The number of Fieldbus requests that were sent to clear the tag of a Fieldbus
device.
OW350_R1007 253
MESSAGE DESCRIPTION
SM Identifies The number of Fieldbus requests that were sent to identify a field device. This
request is sent whenever a device has either been attached to this port or has
changed addresses. If this statistic is incrementing after all field devices on
this port have been commissioned then this could indicate either a network or
a field device problem. To isolate the problem, view the communication
statistic on each field device on this port.
SM SetAddress The number of Fieldbus requests that were sent to set the address of a
Fieldbus device. This request is sent whenever a Fieldbus device is
commissioned. A network or Fieldbus device problem might exist if this
statistic is incrementing after all Fieldbus devices on the port have been
commissioned. To isolate the problem, check the communication statistics on
each Fieldbus device on this port. To check communication statistics on a
device, right-click on the device and select Display Communication Statistics.
SM SetPDTags The number of Fieldbus requests that were sent to the tag of a Fieldbus
device.
Using the Device statistics tab
The card statistics provide a broad view of communication activity on the device. To access the
device statistics:

2. Navigate to the port you are checking:
Card
Port
3. Right-click on the Port and click Statistics to view Device Statistics.
254 OW350_R1007
Figure 58: To open statistic window
OW350_R1007 255
4. Once you access the Fieldbus Statistics window, click on the Device Statistics tab.
5. The Device Statistics tab displays communications information including:
 Aborts received and sent.
 Initiates received and sent.
 Pcr Timeouts.
 Livelist appearances - the number of times the device showed up as new.
Figure 59: Device Statistics tab
 Click Reset All Devices to refresh all the devices on the Device Statistics window.
 Select Reset on the individual device column to refresh devices separately.
seconds in the seconds field so that the device statistics tab refreshes itself automatically
Notes:
 Rows highlighted in red indicate the errors and retries made on each device, this highlights
those devices that need attention.
 Rows that are grayed out display the device information such as device id, device type,
device state, and so forth.
256 OW350_R1007
The following table lists error messages and descriptions that appear in the Name column:
Device statistics
MESSAGE DESCRIPTION
RequestsSent The total number of Fieldbus requests that have been sent to the function
blocks in this device.
AbortsRxd The total number of disconnects received from the function blocks in this
device. If this statistic is steadily increasing for this field device only, the
device could have a problem. If this statistic is steadily increasing with
several field devices, a network problem could exist.
InitsSent The total number of connects sent to the function blocks in this device. If
this statistic is steadily increasing for this field device only, the field
device could have a problem. If this statistic is steadily increasing for
several field devices, a network problem could exist.
InitPosConRxd The total number of positive confirmations to connection requests sent to
the function blocks in the field device.
InitNegConRxd The total number of negative confirmations to connection requests sent

to the function blocks in the field device.
AbortsSent The total number of disconnects sent to the function blocks in this device.
If this statistic is steadily increasing for this field device only, the device
could have a problem. If this statistic is steadily increasing for several
field devices, a network problem could exist.
AbortPosConRxd The total number of local positive responses to disconnects sent by the
H1 card.
AbortNegConRxd The total number of local negative responses to disconnects sent by the
H1 card. The H1 card might need to be replaced if this statistic is steadily
increasing.
PcrTimeoutsRxd The total number of Fieldbus requests sent to the function blocks that
failed because the field device did not return a response. The device
might have a problem if this statistic is steadily increasing.
RejectsRxd The total number of requests that were rejected by this field device.
NumFasAborts The total number of disconnects that have occurred while communicating
with the function blocks in the field device at this address.
LastAbortLocal The number 255 indicates that the last disconnect was generated by the
H1 card, and 0 indicates that the last disconnect was generated by the
field device.
LastAbortReason Displays the code that shows the reason for the last disconnect.
NumDllDtPdusSent The total number of data link packets that have been sent to the function
block application VCR in the field device.
NumDllDtPdusReceived The total number of data link packets that have been sent from the
function block application VCR to the H1 card.
NumDllDtTransferTimeouts The total number of data link requests that could not be delivered to the
function block application VCR in the field device.
OW350_R1007 257
MESSAGE DESCRIPTION
NumStackReceiveQFulls The total number of data link packets that the H1 card could not receive
from this field device because the H1 card did not have a buffer to
receive the packet. The H1 card could be operating at capacity if this
statistic is steadily increasing.
NumDllRetrys The total number of data link packets that had to be retried by the H1
card while sending the packets to the function block application VCR in
this field device. The number of retries to the field device should
generally be much less than one percent of the total requests sent to that
field device. If this is not the case, either the device is bad or there is a
network problem.
NumDllTokenPassTimeouts One of the following has occurred: the Fieldbus device did not see the
token, the Link Active Scheduler (LAS) did not see the token return, or
the Fieldbus device held the token too long.
NegativeConf The total number of Fieldbus requests that were sent to the function
block application VCR that failed because this field device returned an
error. The device could have a problem if this statistic is steadily
increasing.
LocalStackErr The total number of Fieldbus requests that were sent to the function
block application VCR in the device that failed because the
communication stack returned a response that indicated an error. The H1
card might need to be replaced if this statistic is steadily increasing.
MissedViewListScan The total number of view list requests for this device that could not be
sent as often as the corresponding module’s execution rates. If this
statistic is incrementing, the H1 card is trying to scan the function blocks
in this device at a rate that is faster than the Fieldbus can support. Slow
down the execution rate of the module that contains these Fieldbus
function blocks to improve this number.
NumLiveListAppearances The number of times the device has started communicating on the
Fieldbus. If this statistic is incrementing, there is either a problem with
this device or a network problem.
258 OW350_R1007
5.16 Distributed Component Object Model (DCOM) system
5.16 Distributed Component Object Model (DCOM) s ystem
When troubleshooting remote communication, one of the first areas to consider is DCOM. DCOM
is a proprietary Microsoft technology for communication among software components distributed
across networked computers. Using DCOM, you can give certain users access to an OPC server,
while excluding others from that server.
When applying DCOM settings, you should be aware of the following:
DCOM settings are set on both the server machine and the client machine. The following items
must have DCOM configured for them:
 The OPC Server on the server machine.
 The Default DCOM settings on both machines.
 The DCOM settings for OPCEnum on both machines.
It may be necessary to install the OPC server on the client machine. This is strictly to update the
registry in the client machine.
DCOM settings may not clear communications problems, if the server and client machines are on
different domains or in different workgroups.
You must shutdown and restart the OPC Server before the new security settings take effect.
If the OPC Server is running as a service, you will have to stop and restart the OPC Server via the
Services utility in Windows. This can be accomplished by selecting Run from the start menu in
Windows and typing in services.msc.
The DCOM setup is a system administration task. The tool used to administer the DCOM
configuration is the DCOMCnfg.exe utility that is provided by Microsoft and shipped with every
version of Windows.
DCOM can be configured in numerous ways.
The following topics describe the simplest configuration by which the DCOM feature may be used.
Note: These settings ignore security issues. However, you should be able to access the OPC
Server from a remote computer with these settings.
More information regarding DCOM can be found on Microsoft’s website. Distributed Componet
Object Model
OW350_R1007 259
5.17 Optimization package troubleshooting information (Linux OS)
The optimization package is composed of several applications which work together

simultaneously. If any of the applications stop working, you will not be able to switch the
optimization on.
Reading and writing data links are installed on the Ovation Station, customarily on drop211 They
are responsible for transferring data between the system and the optimization system. All
applications start automatically when the Ovation Station starts.
Aggregates and Combustion Optimizer applications are installed on the Linux machine.
If all applications are working properly, the operator should see a READY indication of both
optimizers and aggregates status on the optimizer graphic.
Data links (reading and writing) should be running permanently in order to run the Optimization
System. Users can verify if the links are running correctly by:
 Checking digital flags Reading data link OK and Writing data link OK on the Statuses screen.
The aggregates application should run to generate those flags.
 Checking values of two points in MySQL database (MySQL2Ovation_status,
Ovation2MySQL_status). The values of “pulse” parameters of all points must increment every
time step of links applications.
 Checking Aggregates pulse point value - 3NN-AGRWD and Optimizer pulse point value -
3NN-IVYWD. If reading data link from Ovation to MySQL is stopped, then Aggregates pulse
amplitude will be set to +/- 5 (reading link failure) and digital flag Aggregates READY
(3NN-AGR-OK) will be set to 0. If both data links are stopped, then Aggregates pulse and
Optimizer pulse signals are set to constant value +10 or -10. Digital flag Aggregates READY
(3NN-AGR-OK) and digital flag Optimizer READY (3NN-OK) will be set to 0.
If links are not running correctly, they should be restarted. This can be done by rebooting the
Ovation station HMI drop211 or restarting the service called “IVYControl service” using
Administrative Tools.
260 OW350_R1007
The following table contains a list of things to do to verify what causes a NOT READY status:
PROBLEM SOLUTION
Check the application status, (refer to Checking optimization software

status). If aggregates do not run, try to reboot the Linux station. Wait
approximately 10 to 15 minutes after rebooting and check READY
signals.
Aggregates NOT READY Check the applications status, (refer to Checking optimization software
status). If applications are running, check links applications on drop211
(AGR NOT READY) (refer to Checking software status). If the data links do not run, try to
reboot drop211.
If none of the solutions above help to fix the problem, restore the
optimizer database (refer to Combustion optimization database
restoration).

status). If the Optimizer application does not run, try to reboot the Linux
station. Wait approximately 10 to 15 minutes after rebooting and check
READY signals.
Optimizer NOT READY Check the application status, (refer to Checking optimization software
status). If all applications are running, check the links applications on
(OPT NOT READY)
drop211 (refer to Checking software status). If the data links do not run,
try to reboot drop211.
If none of the solutions above help to fix the problem, restore the
optimizer database (refer to Combustion optimization database
restoration).

status). If none of the applications run, try to reboot the Linux station.
Wait approximately 10 to 15 minutes after rebooting and check the
Aggregates NOT READY READY signals.
(AGR NOT READY)
Check the links applications on drop211, (refer to Checking software
Optimizer NOT READY status). If none of the data links are running, try to reboot drop211 to
bring the communication up.
(OPT NOT READY)
If none of solutions above help to fix the problem, restore the optimizer
database (refer to Combustion optimization database restoration).
Note: After start-up the Combustion Optimizer needs approximately ten minutes before it starts
generating a pulse signal.
Before rebooting the Linux machine, verify the software status - refer to Checking optimization
software status.
Before rebooting the Ovation Station (customarily drop211) machine, try to verify the software
status - refer to Checking software status.
Do not reboot the Linux machine by using the POWER OFF button. It must be restarted with the
init 6 command executed by the root user.
OW350_R1007 261
S E C T I O N 6
6 Replacement Parts
IN THIS SECTION
Ordering spare parts ....................................................................................................... 263

Returning parts to Emerson for repair service ................................................................ 264
Part failure during project startup .................................................................................... 266
Determining repair prices ................................................................................................ 266
Tracking part repairs ....................................................................................................... 267
What is involved in the Replacement of User Serviceable Fuses? ................................ 267
Controller Compact Flash disk replacement ................................................................... 269
Redundant power supply replacement ........................................................................... 270
Replacing an online Valve Positioner (RVP) ................................................................... 276
Installing Ovation standard I/O modules ......................................................................... 278
6.1 Ordering spare parts
Spare parts for any of the main components of an Ovation system are available from the Renewal
Parts Department of Emerson Process Management Power and Water Solutions (hereafter
known as Emerson). Many Ovation parts are maintained for immediate shipment from the factory.
Make sure you have the correct part number (see page 263) for any part you order. You might
also want to know the price of a part (see page 264) before you order it.
Emerson provides several methods that you can use to order parts, including the Ovation &
WDPF Users Web site. This free Web site is provided to all Ovation and WDPF customers.
Contact your Emerson representative to register for Web site access.
The Web site URL is https://www.ovationusers.com.
If you do not have access to the Web site, you can contact your local regional office. You can also
contact the Renewal Parts Department at 412-963-4247 or fax your request to 412-963-4245.
6.1.1 Determining a spare part number
Before you place a parts order, you need to determine the part numbers of the desired parts. You
can determine part numbers from applicable instruction books or drawings that are supplied with
your Ovation system. The part number is also typically marked on each part.
When ordering replacement parts or components, use the assigned Emerson ten-character,
alphanumeric assembly or style number (for example, 5X00070G01), which consists of the
following:
 First seven characters are the main drawing number of the item.
 Last three characters describe a variation of the main drawing.
OW350_R1007 263
6.2 Returning parts to Emerson for repair service
6.1.2 Determining a spare part price
You can determine the price of a part by using the Ovation & WDPF Users web site,
www.ovationusers.com.
If you do not have access to the web site, you can contact your local regional office. You can also
contact the Renewal Parts Department at 412-963-4247 or fax your request to 412-963-4245.
Emerson requests your cooperation in adhering to the following procedures when returning parts
for repair. Your cooperation will enable us to process returned material safely and efficiently.
1. Obtain Material Return Tracking (MRT) number (see page 265) from Emerson.
2. Mark the MRT Number on all material returned to our Repair Department. Shipments
delivered to the Emerson dock that do not have an MRT Number clearly marked on each
carton will be refused and returned to the sender at his/her expense.
3. Include a phone or fax number for a person to be contacted in case of problems or questions.
4. For small electronic components being returned, document the MRT Number on the outside
of the anti-static container. DO NOT attach anything directly to PC boards. Although CRTs
and other bulky materials do not need anti-static containers, make sure that the MRT number
is visible on these items.
5. Use the following shipping instructions:
Note: No collect shipments will be accepted.
CUSTOMER ADDRESS METHOD COMMENTS EMERSON CARRIERS
US Emerson Process Prepaid Provide shipment Utilize the following

Customers Management information (airway carriers:
Power & Water Solutions bill number) via
200 Beta Drive telephone, fax,
Pittsburgh, PA 15238 email, or mail. FedEx for Domestic
Small Packages
ATTENTION:
Repair Department
FedEx Freight for
MRT NUMBER: Domestic Over 150 Lbs
___________*
*Note: At least one of the
assigned MRT Numbers
must be shown.
Non-US Emerson Process Prepaid Prior to shipping, Utilize the following
Customers Management the returnee must carriers:
Power & Water Solutions provide shipment
UPS
200 Beta Drive information to the
Pittsburgh, PA 15238 Emerson Repair DHL
Department via
ATTENTION: telephone, fax, FedEx
Repair Department email, or mail. This
information should
MRT NUMBER: include airway bill
___________ number, method of
shipment, weights
Contact upon arrival: and dimensions,
264 OW350_R1007
CUSTOMER ADDRESS METHOD COMMENTS EMERSON CARRIERS

and a copy of the
For DHL or UPS Supply proforma or
Chain Solutions commercial invoice.
(866) 955-6591
Email: Returns of repaired
UPSEmersonBrokerageT parts from Emerson
eam@ups.com are prepaid only to
the US port of
export.
For FedEx shipments:
Contact Upon Arrival
FedEX Trade Networks
(716) 871-3529
*Note: At least one of the
assigned MRT Numbers
must be shown.
Note: Customs Values and Inco terms will be provided with the MRT number.
6.2.1 Obtaining a Material Return Tracking (MRT) number
Before returning a component to Emerson Process Management Power & Water Solutions for
repair, you must obtain a Material Return Tracking (MRT) number (see page 265).
You must mark the Material Return Tracking (MRT) number (see page 265) on all material
returned to our Repair Department. Shipments delivered to the Emerson dock that do not have an
MRT Number clearly marked on each carton will be refused and returned to the sender at his/her
expense.
1. If for any reason you need to return an Emerson product for repair, please contact us to
obtain an MRT number before shipping the defective material to Emerson. You may contact
us to obtain an MRT number through one of the following methods:
 Via email at PWS.Aftermarket@emersonprocess.com
 Via the Ovation & WDPF Users Web site (https://www.ovationusers.com)
 Via FAX at (412) 963-4245 during normal work hours.
 Via telephone at (800) 397-9767 or
(412) 963-4244 during normal work hours.
 In case of an emergency, call the Technical Support phone at (800) 445-9723.
2. When you contact Emerson to obtain an MRT number, please be prepared to provide the
following information:
 Company name
 Site name
 Shipping address
 Your name, telephone number, email, and fax number
 Purchase order number (if system is no longer under warranty)
 Project number (if system is under warranty)
OW350_R1007 265
6.3 Part failure during project startup
 Quantity of items being returned

 Drawing numbers
 Mnemonic of items
 Detailed description of the problem or update request
6.2.2 Handling in-warranty and non-warranty part repairs
When you return a part to Emerson for repair service, refer to the following table for directions on
sending in-warranty parts and non-warranty parts.
PART REQUIREMENTS SHIPPING SHIPPING GUID ELINES

STATUS METHOD
In-warranty - MRT number (see page 265) Prepaid Refer to Returning parts to
parts (provided by Emerson) Emerson for repair service. (see
page 264)
- Contact person (at customer site)
- Emerson Project number
Non-warranty - MRT number (see page 265) Prepaid Refer to Returning parts to
parts (provided by Emerson) Emerson for repair service (see
page 264).
- Contact person (at customer site)
- PO (provided by customer via
email or faxed to Emerson 412-
963-4245)
- PO should reference part number
and associated MRT number.
6.3 Part failure during project startup
If you experience a part failure during the startup of your Ovation project, you should contact your
onsite Emerson field engineer (where applicable) or your Emerson regional field office.
They will coordinate with Emerson Pittsburgh for the provision of rapid turnaround replacement
parts and provide you with instructions for returning the defective parts.
6.4 Determining repair prices
You can determine the price of part repair (non-warranty) by using the Ovation & WDPF Users
Web site:
1. Log on to the Web site (https://www.ovationusers.com).

2. Select Spare Parts & Repairs.
3. Select Repair Pricing.
4. Use the form that appears to locate the part you want to repair and the price of making that
repair.
266 OW350_R1007
6.5 Tracking part repairs
6.5 Tracking part repairs
You can track the progress of a part repair by using the Ovation & WDPF Users Web site:
1. Log on to the Web site (https://www.ovationusers.com).

2. Select Spare Parts & Repairs.
3. Select Track Repairs.
4. Enter the MRT number of the part and press Submit.
5. A window appears informing you of the progress of the repair status.
6.6 What is involved in the Replacement of User Serviceable Fuses?
Some Electronics modules (Emods) and Personality modules (Pmods) may contain fuses. These
fuses are typically 5 x 20 mm micro-fuses, and are conveniently located for easy replacement.
6.6.1 Electronics Module Fuses
If a fuse needs to be replaced, push the fuse cap in, turn it one-quarter turn counter-clockwise,
and the fuse pops up. Replace the blown fuse with an exact replacement fuse. Fuse sizes are
indicated on the Electronics module label. Refer to the following table for descriptions of fuses
used by Ovation Electronics modules.
Note: In CE Mark Certified systems, the project drawings MUST include any fuses and their
ratings, if they are replaceable by a qualified technician.
TYPE RATING MODEL PART #
5 x 20 mm cartridge 0.50A; 250V; Compact Digital Input Emod (1C31232G01) EX06100

Fast acting Compact Sequence of Events Emod
(1C31233G01)
OW350_R1007 267
6.6 What is involved in the Replacement of User Serviceable Fuses?
6.6.2 Personality module fuses
If a 5x20 mm cartridge fuse needs to be replaced, push the fuse cap in, turn it one-quarter turn
counter-clockwise, and the fuse pops up. Replace the blown fuse with an exact replacement fuse.
Fuse sizes are indicated on the Personality module label. Refer to the following table for
descriptions of fuses used by Ovation Personality modules.
If the fuse is a micro fuse, pull the blown fuse out of its holder and plug the replacement fuse into
the vacated holder.
Note: In CE Mark Certified systems, the project drawings MUST include any fuses and their
ratings, if they are replaceable by a qualified technician.
TYPE RATING MODEL PART #

2 1 Digital Input Pmods Sequence of Events EX06100
a5 x 20 mm 0.50A; 250V
(1C31110G01)
2 0.063A; 250V Analog Input Pmods 1C31116G02 - G03 EX06102
5 x 20 mm
1 Loop Interface Pmods 1C31177G02 - G03
2 1 Pulse Accum. Pmods 1C31150G01 - G03 EX06071
5 x 20 mm 0.63A; 250V
2 1 Relay Base 16 G2R - 1C31223G01 EX06104
5 x 20 mm 1.0A; 250V
2 1 Loop Interface Pmods1C31177G01 - G03 EX06098
5 x 20 mm 1.25A; 250V
Digital Output Pmods - 1C31125G01
Valve Positioner Pmods 1C31197G01 - G04
Relay Panels (Solid State) 5A22410H01 - H02
Relay Panels (16 G2R) - 5A22411H01
2 1 Relay Panels (8 KU) - 5A22412H01 EX06105
5 x 20 mm 2.0A; 250V
Relay Base (12 KUEP) - 1C31222G01
2 1 Digital Output Pmods - 1C31125G02 EX06101
5 x 20 mm 3.15A;250V
3 1 16 Point Individually fused, 1X00030H02
Micro-Fuse 0.5A;125V
Digital Input Pmod - 5X00034G01
HART Analog Input Pmods 5X00063G01
3 0.063A;125V HART Analog Input Pmods 1X00030H01
Micro-Fuse
1 Analog Inputs - 5X00059G01
3 1 HART Analog Output Pmods 5X00063G01 1X00030H05
Micro-Fuse 0.6A;125V
1
Fast Acting
2
Cartridge
3
Plug-in
268 OW350_R1007
6.7 Controller Compact Flash disk replacement
6.6.3 Ovation Cabinet Fuses
In addition to Personality module fuses, there are other fuses that can also be serviced by users.
Refer to the following table for descriptions of fuses used in Ovation cabinets.
TYPE RATING MODEL PART # NOTES
Micro-Fuse 5.0A; 250V; CBO Backplane 4A00120H01 Auxiliary power Branch fuses
Fast acting 3A99200G01 - G02 CBO: F1 -F4
ROP Panel ROP: F1, F2, F7, F8
4D33922G01 TND: F1, F2, F6, F7
TND Panel 4D33924G01 RRP: F1, F2
RRP Panel 3A99252G01 RRB: F1, F2
RRB Panel 3A99253G01
0001.2515 12.5A; 5x20; Power Distribution 1X00728H01 AUX Power Fuse
250VAC; Panel L
Schurter 125VDC 5X00489G01 F1
Type T
6.7 Controller Compact Flash disk replacement
The following information can be useful if the Controller enters a state where it cannot be
successfully cleared or loaded and the Online Restore feature is not configured.
Compact flash disks use the following formatting command on Windows-based operating
systems:
format X: /A:XXXX /FS:XXX
Where:
X = Drive letter of the removable disk. (This letter will differ based upon your system.)
XXXX = Unit size
XXX = File system
Example:
format B: /A:8192 /FS:FAT
Flash disk formatting properties
FLASH DISK SIZE UNIT SIZE FILE SYSTEM
Less than 128 MB 4096 FAT

128 MB 8192 FAT
1GB 16K FAT
OW350_R1007 269
6.8 Redundant power supply replacement
To format Compact Flash discs:
1. Format the Compact Flash disks using a flash card reader.

2. Insert Flash Disk into Controller and power ON.
3. Once the ethers addresses is recognized by the database server:
Solaris - The system will automatically download upon rebooting the system.
Windows - The database server will send initialization files to the controller. This can be seen
in the error log. Once complete, query download the Controller
4. Reboot the Controller.
5. Load the Controller:
Solaris - Perform a clear-load function.
Windows - Perform a load function.
Note: A standard commercial Flash Card Reader can be purchased to read the information on
the Compact Flash disk.
6.8 Redundant pow er suppl y replacement
CAUTION! It is recommended that a certified electrical technician perform the replacement

procedure when you are replacing power supplies while your system is powered and on-line.
When replacing both primary and secondary power supply units, begin by replacing the
secondary power supply first. After the secondary unit is re-installed and turned ON, indicator
lights illuminate indicating that you have power on the power supply. Make sure the secondary
power supply unit is on-line before removal of the primary unit.
Proceed by turning the power OFF of the primary power supply. The primary power supply fails
over to the secondary power supply allowing replacement of both power supplies to be
accomplished without taking the system off-line. Install the replacement power supply and reapply
power to the power supply unit.
Note: Emerson uses rigorous and innovative design, coupled with the use of high quality
components to all areas of the Ovation product line. However, some components, such as the
electrolytic capacitors used in power supplies deteriorate based on time and environment. With
this in mind, Emerson strongly recommends that the power supplies used to power Ovation
Controllers and remote I/O be replaced every 10 years to ensure reliable uninterrupted service.
Both primary and secondary power supply units can be replaced by using the following
procedure.
270 OW350_R1007
6.8.1 Power supply replacement cautions
CAUTION! It is recommended that a certified electrical technician perform the replacement

procedure when you are replacing power supplies while your system is powered and on-line.
When replacing both primary and secondary power supply units, begin by replacing the
secondary power supplies first. After the secondary unit is re-installed and turned ON, indicator
lights illuminate indicating that you have power on the secondary power supplies. Make sure the
secondary power supply units are on-line before removal of the primary units.
Proceed by turning the power OFF of the primary power supplies. The primary power supplies fail
over to the secondary power supplies allowing replacement of both power supplies to be
accomplished without taking the system off-line. Install the replacement power supplies and
reapply power to the primary power supply unit.
Both primary and secondary power supply units can be replaced by using the following
procedure.
6.8.2 To replace redundant power supplies

1. Turn the power OFF at the power supply by switching the circuit breaker on the DIN rail to the
OFF position.
2. Remove the power cable from the bottom of the power supply by releasing the terminal block
levers, then pull the cable downward from the power supply terminal block. Repeat this Step
for the output cable.
3. Loosen the power supply locking mechanism which is located at the bottom of the power
supply (see Power Supply Locking Mechanism (see page 273)).
Note: A medium size slotted head screwdriver is necessary to loosen the locking mechanism.
4. After the locking mechanism has been loosened, lift the power supply from the rail assembly.
5. Install the replacement power supply on the power supply DIN rail.
6. Make sure the replacement power supply is fitted securely on the DIN rail assembly by
checking that the locking mechanism is engaged.
7. Make sure the circuit breaker is in the OFF position before attaching power cabling to the
power supply.
8. Re-attach the power cables by inserting the power supply cables into the connector terminals
of the power supply.
Note: Ensure that the color coding is maintained on the power supplies. Refer to the redundant
power supplies for the color coding.
9. Make sure that the cable connector secures the cables from falling out of the terminals. Also,
make sure that lever arms are engaged.
10. If all wires are tight, you can re-apply power by switching the circuit breaker of the power
supply to the ON position. This completes the power supply replacement process.
OW350_R1007 271
6.8.3 Power supply drawing views
The figure below illustrates the back, side, and front views of a Redundant Power Supply.
Figure 60: Power Supply Views
272 OW350_R1007
6.8.4 Power supply locking mechanism
A locking mechanism, located at the bottom on the power supply, holds the power supply firmly to
the DIN rail. Use a slotted head screwdriver to pull down the lever arm to release the power
supply from the rail assembly. Lift the unit from the rail assembly while the lever arm is pulled
down.
To re-attach the power supply, engage the top the power supply to the rail and push the bottom of
the power supply onto the rail.
Figure 61: Power Supply Locking Mechanism
OW350_R1007 273
6.8.5 1X00024H01 and 1X00024H07 Power supply front view
The following figure illustrates the front of the 1X00024H01 and 1X0002H07 power supply.
Note: The power switch to turn off the power to the power supply is located in the upper left
corner of the unit.
Figure 62: Power Supply Front View
Note: The 1X0002H07 Aux output is 48VDC.
274 OW350_R1007
6.8.6 1X00024H04 and 1X00024H08 Power supply front view
The following figure illustrates the front of the 1X00024H04 and 1X00024H08 power supply.
Note: The power switch to turn off the power to the power supply is located in the upper left
corner of the unit.
Figure 63: 1X00024H04 and 1X00024H08 Power Supply Front View
Note: The 1X00024H08 Aux output is 48VDC.
OW350_R1007 275
6.8.7 Power supply front view
The following figure illustrates the front view of the power supply:
Figure 64: Power Supply Front View
276 OW350_R1007
6.9 Replacing an online Valve Positioner (RVP)
6.9 Replacing an online Valve Positioner (RVP)
A Valve Positioner module can be replaced online when the module fails. Use the following
procedure to remove a Valve Positioner module and safely install a replacement module.
CAUTION! Observe all the precautions and then modify the procedure steps to suit your
particular situation.
1. Once the valve is closed and in a safe condition, remove the bad VP.
2. Insert the replacement VP into the base unit.
3. Download constants using the Valve Positioner Upload/Download/Calibrate graphic.
4. View the reported feedback position. It should be close to 0%. If it is, the valve can be
operated without calibration.
5. View the servo voltage at terminal screws 14B and C, and 13B and C. Note that if the servo
voltage has integrated to a few volts negative, and hydraulic fluid is applied suddenly, the
valve pops, and the onboard PI responds and bring the valve back to the target position of
0%. If the target position of 0% is less than ‘seatLimit’, servo voltage is positive, thus forcing
the valve closed.
6. With the valve closed, you can execute the 0% calibration sequence to find the exact reading
for the 0% position. If you believe the 100% calibration is close, the valve can then be
operated without calibrating the 100% position, since there is little flow change when the valve
is fully opened.
7. Verify that the VP is in the normal operating mode as indicated by the card edge LED.
8. When you determine that it is time to operate the valve, un-isolate the valve hydraulically,
drive the target position of the MA to the desired position, and then switch the MA back to
‘auto.’
6.9.1 Replacement precautions - (RVP)
Observe the following precautions when replacing an RVP:

 If the valve is closed, isolate it hydraulically to prevent any bump when inserting the new VP.
 Switch the MA driving the VP position to manual, and move the target position to zero. This is
done to avoid jostling the valve when the new VP is inserted.
 For large machines, switch the valves to ‘single’ or ‘full arc’ mode from ‘sequential’ or ‘partial
arc’ mode.
 Keep first stage, or impulse pressure, control loops in service to respond to any upset during
the maintenance.
 If the replacement is due to a suspected or intermittent problem that can only be corrected by
replacement, but the VP is operating, first close the valve by switching the MA to manual,
driving the valve to 0%, and then isolate it hydraulically.
OW350_R1007 277
6.10 Installing Ovation standard I/O modules
You install Ovation standard modules (except Relay Output modules) in Base Units mounted on
DIN rails in Ovation cabinets. Each Base Unit can contain two I/O modules. Even if you only use
one I/O module, you must still use a Base Unit that contains two terminal blocks.
DIN rails and modules are typically installed at the factory according to system requirements.
Note: For CE Mark certified systems:
Any Base Unit that contains a 125VAC/DC Digital Input Electronics module (1C31107G02) and
interfaces to hazardous voltage (>30 V RMS, 42.4 V peak, or 60 VDC) must include a
hazardous voltage warning label (1B30025H01).
Place this label in a visible location on the Base Unit, preferably above the spare fuse location.
The project drawings must indicate this.
6.10.1 To hot swap standard I/O modules
CAUTION! Before hot swapping Ovation I/O modules, you must have a thorough
understanding of the control process, the control logic, field device signals, control power
failure modes, and the settings for Ovation I/O modules as well as any other related control
hardware settings.
If you decide that hot swapping a module is feasible, make sure that you maintain the
appropriate settings for forced point values and/or field power jumpers in order to maintain the
system in a safe condition during the time period of the module hot-swap procedure.
Be sure to properly document forced point values and jumpers according to plant safety
procedures.
You can replace standard Ovation I/O modules quickly and easily without shutting down the
cabinet power supplies or reconfiguring the modules. Ovation I/O modules can be hot swapped
with no harm to the control system hardware; however, you are responsible for the I/O module
hardware settings and an analysis of process safety effects.
1. Determine what module needs to be replaced in the cabinet. Be sure you are using exact
replacements for both the Electronics and Personality modules.
2. Evaluate whether affected plant processes can be maintained in a safe state during the
module hot swap, or whether a shutdown is required:
 Identify all field equipment (inputs/outputs) terminated on the module.
 Evaluate any possible effects on field equipment and control logic due to the loss of
signals and control power during the module replacement. Note that the signal quality
propagation in the logic scheme could be affected.
 Evaluate whether the replacement I/O module requires a hardware setup.
3. Remove the old module by unlatching the blue corner latches on the Electronics module,
removing the Electronics module, and then removing the Personality module.
4. Install the new Personality module in the Base Unit first.
5. Then, install the new Electronics module next to the Personality module.
278 OW350_R1007
6. Use the blue corner latches on the Electronics module to secure both modules into the Base
Unit.
The module is immediately functional.
7. After an I/O module has been swapped out, evaluate the current state of inputs and outputs
and the effect of current "real values" in order to perform safe removal of jumpers or forced
point values.
6.10.2 To add new standard I/O modules
Sometimes, during factory installation, not all of the available slots on a branch in a cabinet are
filled with modules. Typically, empty Base Units are installed to fill the available slot positions.
This is done to ensure that the module addressing is not disrupted if additional modules are
added later.
Use the following procedure to add additional modules to the existing Base Units:
1. Determine what modules are to be installed in the existing Base Units in the cabinet.
2. Install the Personality module in the Base Unit first. Then, install the Electronics module next
to the Personality module.
3. Use the blue corner latches on the Electronics module to secure both modules into the Base
Unit.
4. Connect the wires from the field devices to the terminal block in the Base Unit.
The wiring connections to the terminal block for each combination of Electronics module and
Personality module are printed on each Personality module.
Note: Be sure that each wire opening in the terminal block is fully open before inserting the
wire. This ensures that the wire is clamped securely when the screw is tightened.
6.10.3 Installing Ovation Relay Output modules
You install Ovation Relay Output modules in Relay Output Base Units mounted on DIN rails in
Ovation cabinets. DIN rails and modules are typically installed at the factory according to system
requirements.
There are two styles of Relay Output Base Units:

 1C31222 (12 KUEP relays).
 1C31223 (16 G2R relays).
Each base unit can contain one Relay Output Electronic module and the appropriate relays.
OW350_R1007 279
6.10.4 To hot swap Relay Output Electronics modules
You can replace Ovation Relay Output Electronics modules quickly and easily without shutting
down the cabinet power supplies or reconfiguring the modules.
1. Determine what module needs to be replaced in the cabinet. Be sure you are using an exact
replacement for the Relay Output Electronics module.
2. Remove the old module by sliding the two latches, located on the card guides, to the open
position (a diagram is located on the module cover).
3. Remove the old Relay Output Electronics module.
4. Install the new Relay Output Electronics module and slide the two latches into the locked
position.
The module is immediately functional.
6.10.5 To add new Relay Output I/O modules
Sometimes, during factory installation, not all of the available slots on a branch in a cabinet are
filled with modules. Typically, on the right side of the cabinet, empty Base Units are installed to
fill the available slot positions. This is done to ensure that the module addressing is not disrupted
if additional modules are added later.
Use the following procedure to add additional modules to the existing Base Units:
1. Determine what modules are to be installed in the existing Base Units in the cabinet.
2. Install the new Relay Output Electronics module and slide the two latches into the locked
position. Snap the Relay Output Base unit onto the desired branch position.
3. Connect the wires from the field devices to the terminal block in the Base Unit.
Note: Be sure that each wire opening in the terminal block is fully open before inserting the
wire. This ensures that the wire is clamped securely when the screw is tightened.
4. Note that the following wiring options are provided on the Base Unit. Select the appropriate
wiring option for each relay:
 Normally Closed (NC).
 Normally Open (NO).
 Common (C).
Note: When wiring to the KUEP Base Unit (with Form X relays installed), wire between NO and
C. Do not connect any wiring to the NC terminal.
280 OW350_R1007
S E C T I O N 7
7 Shipping and Storage of Ovation equipment
IN THIS SECTION
Guidelines for shipping Ovation equipment .................................................................... 281

Guidelines for lifting Ovation equipment ......................................................................... 282
Guidelines for off-loading and unpacking Ovation equipment ........................................ 284
Guidelines for repacking and returning Ovation equipment ............................................ 284
Guidelines for repacking third-party products ................................................................. 285
Guidelines for transporting Ovation equipment to the specific installation location ........ 285
Guidelines for storing Ovation equipment ....................................................................... 285
7.1 Guidelines for shipping Ovation equipment
Use the following general guidelines for shipping equipment.
1. Since many pieces of an Ovation system are large and heavy, provide adequate off-loading
equipment (along with experienced personnel to operate the equipment) at the site.
2. Plan in advance the best manner and route to transport the equipment (after it is off-loaded).
Consider any problem obstacles, such as stairways, doorways, or difficult turns.
3. Ship any components that are contained in the main housing of a drop (that is, an I/O cabinet)
fully assembled.
4. Connect, prior to shipment, any cables connected entirely within the main housings.
5. Pack in a separate package, any cables used to connect external components together, and
ship them along with the main enclosure.
6. Mount cabinet housings on pallets.
7. Secure all internal cables to prevent rubbing or chafing, and relieve stress with cable ties.
8. Secure all internal components or lock them in place by anchoring the devices.
9. Remove all temporary cushioning, blocking, bracing, and anchoring material before powering
up the system.
10. Wrap the housings in heavy-duty plastic wrap.
11. Route shipments, if possible, by air-ride electronic vans directly to the point of destination, to
eliminate any unnecessary unloading and reloading.
12. Prepare shipments for possible shock and vibration encountered during shipment by utilizing
internal bracing and suitable anchoring.
13. Mark shipping containers to identify the following:
 Front and back.
 Destination.
 Return address.
OW350_R1007 281
7.1 Guidelines for shipping Ovation equipment
 Package numbers showing the purchase order number, followed by the package number
and the total number of packages.
 Material identification number.
 Handling instructions (for example, Fragile, Center of Gravity, Keep Dry, This Side Up,
Sling Here, Do Not Freeze, and stacking limitations if appropriate).
 Weight and dimensions (as applicable).
 Special instructions (for example, Desiccant Inside; special inspections; storage or
unpacking restrictions, as appropriate).
14. Ship cabinets in an upright position or placed on the front or back door, heavy side down,
then on a heavy-duty pallet and covered with heavy-duty plastic. Cover the cabinet with
styrofoam and plywood on all four sides, and band the covered cabinets with high-strength
banding. Use either a skid or a crate.
15. For shipments by air and ocean, use waterproof paper, as needed.
16. For shipments by ocean, place a desiccant in the sealed container. Encase the sealed
enclosure in a military-type plywood crate. If required, mark the crate to indicate the center of
balance, fork lift and sling handling points, and use cautioning marks and symbols.
17. For spare parts and/or kits:
 By Land: Mobile wrap boxes and use pallets.
 By Air: Mobile wrap waterproof boxes and use cable crates.
 By Ocean: Vapor pack boxes, wrap them in waterproof paper, and place them in plywood
crates.
282 OW350_R1007
7.2 Guidelines for lifting Ovation equipment
7.2 Guidelines for lifting Ovation equipment
Observe the following guidelines for safe lifting.
1. If it is necessary to lift equipment by crane or other hoisting devices, Emerson can provide
this service at an additional cost.
2. Emerson can provide rigging and rigging supervision to ensure a complete and safe
off-loading. For more information, contact your Emerson representative.
3. If eye bolt lugs are provided at the top corners of the cabinets for lifting, make certain that all
four eyebolts are fastened to ensure safe load distribution.
Ovation I/O cabinet weights and dimensions
CABINE T TYPE 1 DIMENSIONS (H X W X D)

WEIGHT
Ovation Workstation Cabinet: Vented 183 kg 2083x601x890 mm

1X00518 (403 lb) (82x24x35 in)
Ovation Server Cabinet Vented 161 kg 2083x601x890 mm
1X00545 (354 lb) (82x24x35 in)
Static load rating of 680 kg
(1500 lb)
OCR400 Controller 211.71 kg 2000 x 600 x 600 mm
5X00293 (466.75 lbs) (78 x 24 x 24 in)
CE Mark Certified
Extended I/O 208.14 kg 2000 x 600 x 600 mm
CE Mark Certified (458.86 lbs) (78 x 24 x 24 in)
Remote I/O 209.48 kg 2000 x 600 x 600 mm
Sealed (461.83 lbs) (78 x 24 x 24 in)
CE Mark Certified
Remote I/O 209.48 kg 2000 x 600 x 600 mm
Ventilated (461.83 lbs) (78 x 24 x 24 in)
CE Mark Certified
OCR400 Controller 198.56 kg 2000 x 600 x 600 mm
(437.75 lbs) (78 x 24 x 24 in)
Marshalling 283.6 kg 2000 x 800 x 600 mm
(624 lbs) (78 x 32 x 24 in)
Marshalling 301 kg 2000 x 914 x 600 mm
(664 lbs)
(78 x 36 x 24 in)
Extended I/O 178.65 kg 2000 x 600 x 600 mm
(393.86 lbs) (78 x 24 x 24 in)
Remote I/O 180.0 kg 2000 x 600 x 600 mm
Sealed (396.83 lbs) (78 x 24 x 24 in)
OW350_R1007 283
7.3 Guidelines for off-loading and unpacking Ovation equipment
CABINE T TYPE 1 DIMENSIONS (H X W X D)

WEIGHT
Remote I/O 180.0 kg 2000 x 600 x 600 mm

Ventilated (396.83 lbs) (78 x 24 x 24 in)
1
Assumes Controller cabinet is populated with 16 I/O base assemblies (32 Electronic modules and 32
Personality modules).
7.3 Guidelines for off-loading and unpacking Ovation equipment

1. Off-load all shipments of Ovation equipment with Roll-A-Lift jacks, hydraulic lift trucks, or
four-wheel dollies. Do not hoist domestic shipments, but you may hoist overseas shipments at
the center-of-gravity marks, shown on the container.
2. Locate a packing list for all shipments. Check the shipment against the list to be sure that all
items have been delivered. If any of the shipment is missing, notify the carrier of the shortage,
and obtain proof of the shortage.
3. Inspect the complete shipment for visible damage to any of the packing containers, and verify
any damage with the carrier.
4. Unpack the equipment by cutting any banding and removing all exterior packaging such as
cardboard and plastic wrap. Place any drops that were shipped on their side in an upright
position. Inspect the shipment again for visible damage such as dents, scrapes, and severely
scratched paint work. Verify any damage with the carrier.
5. Save all reusable packing material (that is, pallets, containers, and so on) in case you need to
return the shipment.
6. Open all cabinet doors and remove all shipping materials. Inspect the interior of all drop
enclosures for obvious mechanical damage.
WARNING! Do not allow, under any circumstances, any equipment to sit in an area exposed
to the weather.
284 OW350_R1007
7.4 Guidelines for repacking and returning Ovation equipment
7.4 Guidelines for repacking and returning Ovation equipment

1. If you must return an Ovation component to the factory, repackage it in a manner similar to
the way it was shipped.
In general, package the equipment so that no damage will occur during transportation. This
means that you must protect exteriors and secure interior devices.
2. Before returning any equipment to Emerson, contact an Emerson representative for return
approval.
3. Attach documentation, which states the reason for the return, to the returned equipment.
7.5 Guidelines for repacking third -party products
Since Ovation is an open system, many components of your Ovation system are third-party
products (such as switches, monitors, and workstations). Use the following guidelines when
dealing with third-party products:
 Save the product’s original shipping containers in case it would need to be returned to
Emerson or to the manufacturer for repairs.
 Save the documentation that is provided with the product. This includes User Guides,
warranty information, and so forth.
7.6 Guidelines for transporting Ovation equipment to the specific

installation location
1. Transport equipment to the final installation location with Roll-A-Lift jacks, hydraulic lift trucks,
or four-wheeled dollies.
2. Do not hoist equipment for final installation. Only certain cabinet enclosures are designed with
holes to attach eye bolts.
OW350_R1007 285
7.7 Guidelines for storing Ovation equipment
7.7 Guidelines for storing Ovation equipment
You may need to store an Ovation system before you can install the system.
1. Storage temperatures for Ovation components are listed in Specifications for Ovation
Equipment.
2. Verify that the storage area will be:
 Rodent and pest-free.
 Insect controlled.
 Equipped with a fire prevention system and a fire sensing and alarm system.
 Located in a key-lock-controlled area.
 Located in a personnel-controlled area.
 Kept free of all combustible material except essential packing materials.
 Protected from airborne dust.
 Free from water leaks and water accumulation.
 Free of corrosive gasses.
 Free of excessive vibration.
 Stored in the non-energized state with desiccant bags in each enclosure.
 Stored with the cabinet doors locked.
 Stored with dust covers intact.
 Stored in a “last in/first out” manner to avoid rehandling.
3. Stack cables on two-inch-by-four-inch lumber to a maximum height of three feet.
286 OW350_R1007
S E C T I O N 8
8 Maintenance Training
IN THIS SECTION
Maintenance training courses ......................................................................................... 287
8.1 Maintenance training courses
Emerson offers a full line of troubleshooting and maintenance courses to assist you with your
Ovation System. For more information on the training courses offered, refer to the Ovation User
website https://www.ovationusers.com or contact your Emerson representative.
OW350_R1007 287
Index
Cleaning and general maintenance

1 guidelines • 10
1X00024H01 and 1X00024H07 Power Communications • 16
supply front view • 274 Configuration of bypasses • 158
1X00024H04 and 1X00024H08 Power Contact Input modules testing • 199
supply front view • 275 Contingency Check Error - (RVP) • 219
Control Task Information tab in the
A Controller Diagnostics window • 114
Controller cabinet components (Remote I/O)
Accessing the Error Log window at the
(OCR400 Controller and OCR1100
Operator Station • 79
Controller) • 7
Additional Information on Fault Code
Controller Cabinet On/Off Controls • 14
Hardware Address and I/O Status Values
Controller Compact Flash disk replacement •
• 84
269
AMS suite for use with HART field devices
Controller Diagnostics menu bar • 108
or Foundation field bus devices • 152
Controller Diagnostics tool • 105
Analog I/O modules (main/aux power and
Controller Diagnostics toolbar • 108
main/aux heat dissipation) (drawn from
Controller Diagnostics Update Backup
AC/DC Mains power) • 32
function • 113
Analog Input modules • 181
Controller Diagnostics window • 107
Analog Input modules testing • 185
Controller List in the Controller Diagnostics
Analog Output module testing • 191
window • 109
Analog Output modules • 190
Controller Overview panel in the Controller
Audit Log storage • 141
Diagnostics window • 111
Auditing examples • 128
Controller power switch • 15
AuditView menu bar • 132
Copyright Notice • 2
AuditView toolbar • 133
Automatic Tests • 166 D
B DA readback error - (RVP) • 219
database files backup • 95
Backing up the operating system and
DDB Protocols configuration • 172
Ovation software • 95
Diagnostic LEDs - (AI-13) • 185
backup the complete database • 96
Diagnostic LEDs - (HSAI) • 186
backup the database files • 96
Diagnostic LEDs - (RO) • 208
backup the partial database • 97
Diagnostic LEDs - (SEContactDI) • 201
Bus interface modules • 36, 222
Diagnostic LEDs - DeviceNet • 238
Bypasses and other overrides • 157
Diagnostic Logic card LEDs - (AI-13, AI-14 &
C HSAI) • 186
Diagnostic Logic card LEDs - (AO) • 192
Cabinet circuit breaker/on/off switch • 14 Diagnostic Logic card LEDs - (CCDI) • 200
Cabinet components (weight, dimensions, Diagnostic Logic card LEDs - (CompactDI) •
and temperatures) • 72 199
Cabinets (altitude, humidity, and ingress Diagnostic Logic card LEDs - (ContactDI) •
protection) • 70 200
Cabinets (weight, dimensions, and Diagnostic Logic card LEDs - (DI) • 199
temperatures) • 65 Diagnostic Logic card LEDs - (DO) • 206
Calculating Ovation main power Diagnostic Logic card LEDs - (ECSOEDI) •
requirements for OCR400 or OCR1100 202
Controller • 49 Diagnostic Logic card LEDs - (HAI) • 188
Checking for electrical interference • 17 Diagnostic Logic card LEDs - (HAO) • 193
Checking NTP synchronization issues • 94 Diagnostic Logic card LEDs - (HHPAI) • 189
OW350_R1007 289
Index
Diagnostic Logic card LEDs - (HHPAO) • Fieldbus segment monitoring • 52

193 firewall configuration • 172
Diagnostic Logic Card LEDs - (LI) • 213 Fragmentation of a Hard Disk Drive (HDD) •
Diagnostic Logic card LEDs - (PA) • 214 93
Diagnostic Logic card LEDs - (RTD-4) • 189
Diagnostic Logic card LEDs - (RTD-8) • 190 G
Diagnostic Logic card LEDs - (RVP) • 217 GE Genius Gateway diagnostics • 156
Diagnostic Logic card LEDs - (SD) • 216 General DCU/RIO operational checks • 57
Diagnostic Logic card LEDs - Global Performance Advisor (GPA) Function
(SECompactDI) • 202 Block Diagrams (FBDs) • 153
Diagnostic Logic card LEDs - (SVD) • 215 Grounding guidelines for clustered cabinet
Diagnostic Logic card LEDs - Foundation arrangements • 74
Fieldbus • 244
Diagnostic tools and troubleshooting • 103 H
Diagnostics - (HSDO) • 207
Handling static sensitive devices • 5
Diagnostics - (RVP) • 218
Hardware preventative maintenance
Diagnostics of LVDT problems (redundant) -
checklist • 77
(RVP) • 221
HART Analog Input modules testing • 187
Digital I/O modules (main/aux power and
HART Analog Output modules testing • 192
main/aux heat dissipation) (drawn from
HEARTBEAT • 145
AC/DC Mains power) • 37
High Side Digital Output (HSDO) diagnostics
Digital Input modules • 194
• 154
Digital Input modules testing • 198
High-level auditing example • 128
Digital Output modules • 204
Historical Error Log window at the Operator
Digital Output modules testing • 206
Station • 81
Disabled Offline mode attributes • 92
How can I use Wave? • 155
Distributed Component Object Model
How do I diagnose Foundation Fieldbus
(DCOM) system • 259
device errors? • 244
DROPSTATUS • 143
How do I troubleshoot DeviceNet? • 237
E How do I troubleshoot Profibus? • 223
How does Wave work? • 155
Electrical information for Ovation equipment How Ovation SIS annunciates faults • 161
• 26
Electronics Module Fuses • 267 I
Enabled Offline mode attributes • 92
I/O cabinets (main/aux power and main/aux
Engineering Tools Audit • 124
heat dissipation) (drawn from AC/DC
Environmental information for Ovation
Mains power) • 30
equipment • 58
I/O Information tab in the Controller
EPROM Checksum Error - (RVP) • 219
Diagnostics window • 116
Equipment protection • 57
I/O module troubleshooting • 178
Error Log window columns at the Operator
I/O modules (add new) • 279
Station • 83
I/O modules (hot swap) • 278
Error Log window menu bar at the Operator
I/O modules installation • 278
Station • 82
If the Ovation Developer Studio does not
Error Log window toolbar at the Operator
start and connect to the Local Database
Station • 82
Server • 172
Evaluating and responding to annunciated
installation errors • 170
faults • 162
Interface - DeviceNet • 239
Evaluating fatal errors • 163
Interface - Foundation Fieldbus • 245
Example of Controller OCR400 and
Introduction to Maintaining your Ovation
Controller OCR1100 backplane • 25
System • 1
Extended I/O cabinet illustration • 20, 21
Investigating a Profibus fault code • 236
F L
Fault detection, system response, and repair
LATCHQUAL • 148
procedures • 160
Field engineering services • 104
290 OW350_R1007
Index
LC/EHC Turbine Controller interface Ovation system definition • 1

diagnostics • 156 Ovation system diagnostics tools • 105
Live Error Log window at the Operator Ovation system maintenance • 77
Station • 80 Overall segment statistics • 249
Logic card diagnostic LEDs - Profibus (DP) • Override types • 157
225
Loop Interface Controller modules testing • P
213 Part failure during project startup • 266
Low-level auditing example • 130 Part repairs (tracking) • 267
Parts repairs (handling) • 266
M
Parts return • 264
Maintaining your Ovation System • 2 Performing inspection and routine
Maintenance bypass example • 159 maintenance tasks • 9
Maintenance Training • 287 Performing outage maintenance • 76
Maintenance training courses • 287 Periodic Human Machine Interface (HMI)
Making online scaling changes in HART checks • 78
transmitters • 168 Personality module fuses • 268
Manual Tests • 167 PNTSTATUS • 150
Maximum fault detection time • 165 Point Details tab in the Controller
Media, patch, and license management • Diagnostics window • 120
100 Port integrity • 246
Medium-level auditing example • 129 Port statistics (detailed) • 252
Memory Read/Write Check Error - (RVP) • Power Distribution Module (PDM) illustration
219 • 23
Module record information • 231 Power supplies • 10
Power supply drawing views • 272
N Power supply features • 11
Network Time Protocol (NTP) (Networks Power supply front view • 276
folder) • 94 Power supply limits • 13
Node record information • 227 Power supply locking mechanism • 273
Non-Ovation diagnostics tools • 151 Power supply module • 13
Power supply replacement cautions • 271
O Power supply status monitoring • 50
Ppower distribution in an Ovation system •
Obtaining a Material Return Tracking (MRT)
18
number • 265
Printing Error Log messages at the Operator
OCR400 Controller/Marshalling cabinet
Station • 87
illustration • 19
Priority levels of Error Log messages at the
Open coil diagnostic error - (RVP) • 220
Operation of bypasses • 158
Proof testing the Logic Solver • 166
Optimization package troubleshooting
Pulse Accumulator modules testing • 214
information (Linux OS) • 260
Ovation AntiVirus Upkeep • 89 R
Ovation Cabinet Fuses • 269
Ovation diagnostic services • 103 Recommendations for operation and
Ovation equipment lifting guidelines • 283 maintenance technicians • 3
Ovation equipment off-loading and Redundancy checks during an installation or
unpacking guidelines • 284 outage process • 16
Ovation equipment repacking and returning Redundant module information • 234
guidelines • 285 Redundant power supplies (monitoring one
Ovation equipment shipping guidelines • 281 set) • 50
Ovation equipment storage guidelines • 286 Redundant power supplies (monitoring two
Ovation equipment transportation guidelines sets) • 51
• 285 Redundant power supply replacement • 270
Ovation Error Log window at the Operator Refresh function for the Controller
Station • 78 Diagnostics window • 122
Ovation installation general maintenance • 7 Relay Output Electronics modules (hot
swap) • 280
OW350_R1007 291
Index
Relay Output I/O modules (add new) • 280 SureService Customer Support Programs •
Relay Output module installation • 279 104
Relay Output module testing • 208 Switch and Router Configuration and
Remote function modules (main/aux power Internet Operating System (IOS) • 90
and main/aux heat dissipation) (drawn System checkout • 10
from AC/DC Mains power) • 48 System Diagnostic algorithms • 142
Remote Node cabinet illustration • 22 System Offline Mode • 91
Repair prices • 266 System redundancy • 2
Replacement Parts • 263
Replacement precautions - (RVP) • 277 T
Replacing an online Valve Positioner (RVP) Technical tips and best practices • 91
• 277 Terminators (missing) • 54
Resolving a slave alarm • 236 Terminators (too many) • 55
Resolving common installation problems • Test equipment familiarity recommendations
169 •4
restore a complete database • 97 Testing Media Attachment units and Remote
restore a partial database • 98 Node Controllers • 221
RTD Input modules testing • 189 Testing the electrical systems • 10
Third-party product repacking guidelines •
S
285
Safety and Tag-out procedures • 4 To access the Controller Diagnostics tool in
security related errors • 173 a Solaris-based Ovation system • 106
Sequence of Events modules testing • 200 To access the Controller Diagnostics tool in
Serial Link Controller modules testing • 221 a Windows-based Ovation system • 106
Servo Driver modules testing • 215 To access the License Manager • 101
Setting the Online/Offline mode • 92 To access the Ovation Audit Viewer • 131
Sheet Information tab in the Controller To adjust columns using the right-click menu
Diagnostics window • 121 • 139
Shipping and Storage of Ovation equipment To archive audit data • 140
• 281 To backup your domain controller • 98
Shorted coil diagnostic - (RVP) • 220 To define search criteria for an audit report •
Shorting bar removal • 75 135
Signal check (performing) • 54 To Defragment a hard disk • 94
Signal waveforms • 56 To determine if communication has failed
Simplex module information • 233 (load and downloads) • 171
SIS operations and maintenance practices • To determine if Ovation is running • 170
157 To download firmware revisions to the I/O
Skill level recommendations • 3 modules through the Controller
SmartProcess suite of Plant Optimization Diagnostics window • 118
software • 152 To execute a normal cabinet power-down
Software expertise recommendations • 4 sequence for maintenance or repairs • 5
Software platforms that Controller To execute a normal cabinet power-up
Diagnostics supports • 106 sequence following maintenance or
Software Versions tab in the Controller repairs • 6
Diagnostics window • 119 To Implement Mandatory Profiles • 89
Spare part number • 263 To Implement Roaming Profiles • 88
Spare part price • 264 To investigate a DeviceNet fault code • 244
Spare parts ordering • 263 To perform a Foundation Fieldbus voltage
Specialty I/O modules (main/aux power and check • 54
main/aux heat dissipation) (drawn from To perform a Foundation Fieldbus wiring
AC/DC Mains power) • 44 check • 53
Specialty Modules • 209 To reboot an I/O module • 119
Speed Detector modules testing • 216 To replace redundant power supplies • 271
Spur or segment length (excessive) • 55 To resolve a slave alarm • 243
Status Information Diagrams • 151 To review system performance • 78
Summary of Changes • 3 To review the Windows Event Viewer for
warnings and errors • 78
292 OW350_R1007
Index
To select a Controller in the Controller What is the Control Logic Navigator utility? •
Diagnostics window • 110 123
To set the Engineering Audit level • 127 What is the Engineering Tools Audit
To show or hide columns using the menus • function? • 124
138 What Ovation applications are audited with
To troubleshoot using the module and node the Engineering Audit Tools function? •
records • 227, 240 125
To update your backup Controller in the Workstations and peripherals (altitude and
Controller Diagnostics window • 113 noise) • 63
To use the module record • 241 Workstations and peripherals (humidity,
To use the node record • 242 shock, and vibration) • 61
To view current Engineering Tool audits • Workstations and peripherals (input current,
134 power consumption, and heat dissipation)
To view individual event information • 137 • 28
Transition panel illustration • 23 Workstations and peripherals (input voltage
Troubleshooting Routed Network problems • and input frequency) • 27
91, 178 Workstations and peripherals (weight,
Troubleshooting the bus using the LEDs • dimensions, and temperatures) • 58
224, 237, 244
Troubleshooting tools • 90
U
User profile options for Windows domains •
88
Using the Choose Columns dialog box at the
Using the Device statistics tab • 254
Using the Ovation Audit Viewer • 131
Using the ports statistics tab • 246
Using the Select Priority Level dialog box at
the Operator Station • 87
V
Valve Positioner modules testing • 217
W
Wave Web Viewer • 154
What are DeviceNet online diagnostics? •
239
What are Profibus online diagnostics? • 225
What are the I/O Interface module status
LEDs for the Controller? • 176
What are the processor module status LEDs
for the Controller? • 174
What are the storage limits? • 141
What firmware can be downloaded to the I/O
modules through the Controller
Diagnostics window? • 117
What if the storage limits are exceeded? •
141
What is involved in the Replacement of User
Serviceable Fuses? • 267
What is the Audit log archive? • 140
What is the best way to troubleshoot
redundant module pairs? • 225, 235
OW350_R1007 293

OW350 - R1007 维护

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OW350 - R1007 维护

Uploaded by

Copyright:

Available Formats

Maintaining Your Ovation System

(For use with Ovation 3.5 systems)

1 Introduction to Maintaining your Ovation System 1

2 Recommendations for operation and maintenance technicians 3

3 Ovation installation general maintenance 7

3.6 Grounding guidelines for clustered cabinet arrangements ............................................... 74

4 Ovation system maintenance 77

5 Diagnostic tools and troubleshooting 103

5.10 Resolving common installation problems ........................................................................ 169

6 Replacement Parts 263

6.10 Installing Ovation standard I/O modules ......................................................................... 278

7 Shipping and Storage of Ovation equipment 281

8 Maintenance Training 287

1 Introduction to Maintaining your Ovation System

What is an Ovation system? ............................................................................................... 1

1.1 What is an Ovation system?

1.2 Maintaining your Ovation S ystem

1.3 System redundancy

2 Recommendations for operation and maintenance

Skill level recommendations ................................................................................................ 3

2.1 Skill level recommendations

A skill level of journeyman electronics or instrumentation technician is recommended to maintain

2.2 Softw are expertise recommendations

2.3 Test equipment familiarity recommendations

2.4 Safety and Tag -out procedures

2.4.1 To execute a normal cabinet power-down sequence for maintenance or

2.4.2 Handling static sensitive devices

2.4.3 To execute a normal cabinet power-up sequence following maintenance or

3 Ovation installation general maintenance

3.1 Controller cabinet components (Remote I/O) (OCR400 Controller

The Ovation Remote I/O Controller cabinet contains the following:

ELECTRONICS PERSONALITY 1 CHANNELS OPTICS

1C31179G01 1C31181G01 Up to 2 kilometers (6,560 ft) 2 850 nm

1C31179G02 1C31181G02 Up to 2 kilometers (6,560 ft) 4 850 nm

3.2 Performing inspection and routine maintenance tasks

 Equipment manuals - Refer to the following Ovation system documents

3.2.1 Cleaning and general maintenance guidelines

3.3 How do I perform a system checkout?

After installation is complete, perform a checkout to ensure a successful startup. Checkout

3.3.1 Testing the electrical systems

Startup testing consists mostly of verifying:

Power supply features

Ovation power supplies provide the following features:

 LEDs on the front panel indicate conditions of input/output voltages.

Figure 1: Typical power supply front panel

Power supply module

There is one type of power supply module available (for AC or DC input):

AC/DC Power Supply Modules (1X00781H01L)

MODULE OUTPUT DESCRIPTION

1X00781H01L 240 Watt - 24 Volt Single output

Power supply limits

The following limits are given per power supply:

Main Power Supply

Auxiliary Power Supply

Controller Cabinet On/Off Controls

Cabinets contain the following switches:

Cabinet circuit breaker/on/off switch

Controller power switch

Figure 2: Ovation OCR400 or OCR1100 Controller Cabinet Configuration (illustrating

Redundancy checks during an installation or outage process

Checking for electrical interference

Monitor the following signals to determine the presence of electrical interference:

3.3.2 How is power distributed in an Ovation system?