Compact Controller (OCC100) User Guide For Ovation 3.6.0 and Feature Pack 4 OW360 - 50

Compact Controller (OCC100) User Guide for Ovation
3.6.0 and Feature Pack 4

OW360_50
Version 3
November 2018
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management Power & Water Solutions, Inc. (Emerson) be responsible or liable for any damage,
including indirect or consequential losses resulting from the use, misuse, or application of this
equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
the use and application of the OvationTM Unit. Due to the many variables associated with specific
uses or applications, Emerson cannot assume responsibility or liability for actual use based upon
the data provided in this manual.
No patent liability is assumed by Emerson 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.
The document is the property of and contains Proprietary Information owned by Emerson 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. 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, Inc.

200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@Emerson.com
Web site: https://www.ovationusers.com
Summary of Changes
Compact Controller (OCC100) User Guide for use with Ovation 3.6.0 and Feature Pack 4
OW360_50
November 2018
Version 3
This version of the Compact Controller (OCC100) User Guide for Ovation 3.6.0 and Feature Pack
4 includes the following new information:
 Clarified licensing information (see page 34).
 Updated the information on supported protocols to include (see page 92):
 Using the OPC UA Protocols with Ovation
 Using the Winteligence Slave Protocol with Ovation
 Using the IEC 60870-5-103 Controlling and Controlled Protocols with Ovation
 Made miscellaneous clarifications and corrections.
Contents
1 Introduction to the Ovation Compact Controller 1

1.1 What is the Ovation Compact Controller? ........................................................................... 2
1.2 Features of the Ovation Compact Controller ...................................................................... 3
1.2.1 Automatic failover control ....................................................................................... 4
1.2.2 Slot mismatch detection ......................................................................................... 4
1.3 How is the Ovation Compact Controller similar to a standard Ovation Controller? ............ 5
1.4 Definition of Terms for the Ovation Compact Controller ..................................................... 5
1.5 Reference documentation ................................................................................................... 8
2 Hardware and software requirements for the Ovation Compact

Controller 9
2.1 Ovation Compact Controller components ........................................................................... 9
2.1.1 Controller base assembly..................................................................................... 11
2.1.2 Ovation Compact Controller module .................................................................... 13
2.1.3 Two-slot horizontal I/O Marshalling base ............................................................. 15
2.1.4 Four-slot horizontal I/O base with standard terminations .................................... 17
2.1.5 Network interface ports ........................................................................................ 19
2.2 Pin assignments for power connectors ............................................................................. 19
2.2.1 Power connectors for OCC base ......................................................................... 20
2.2.2 Power connector for two-slot Marshalling base ................................................... 21
2.2.3 Power status connector for four-slot Standard base ............................................ 22
2.3 Diagnostic LEDs for Ovation Compact Controller ............................................................. 23
2.4 Specifications for the Ovation Compact Controller ........................................................... 23
2.5 Power supply options for the Ovation Compact Controller ............................................... 25
2.5.1 OCC power supply specifications ........................................................................ 27
2.5.2 OCC power supply LED status conditions ........................................................... 29
2.6 Hardware installation guidelines and best practices ......................................................... 30
2.7 Using the Ovation Compact Controller in a Wide Area Network (WAN)........................... 33
2.8 Minimum software requirements for Ovation Compact Controller .................................... 34
2.9 What licensing is required for the Ovation Compact Controller? ...................................... 34
3 Defining system addresses for the Ovation Compact Controller 37

3.1 What is an Ovation I/O module address? ......................................................................... 37
3.2 Determining the Internet Protocol (IP) address of an Ovation Compact Controller .......... 39
3.3 Determining the Network Ethers address (MAC address) ................................................ 39
3.3.1 To determine the Network Ethers address from the label ................................... 40
3.3.2 To determine the Network Ethers address from the Ovation Error Log application
............................................................................................................................. 41
OW360_50 i
Table of Contents
4 Adding and configuring an Ovation Compact Controller 43

4.1 Overview of adding an Ovation Compact Controller drop to the Developer Studio .......... 43
4.2 Accessing the Ovation Developer Studio .......................................................................... 44
4.3 To insert a new OCC drop in the Ovation Developer Studio ............................................ 44
4.4 To create a drop point for the OCC ................................................................................... 50
4.5 To set Controller parameters for the OCC ........................................................................ 52
4.6 To configure default control tasks ..................................................................................... 55
4.7 To insert a new control task for the OCC .......................................................................... 57
4.8 To confirm the Controller Networking settings .................................................................. 58
4.9 To modify Controller Networking settings for the OCC drop only ..................................... 61
4.10 Custom Controller Networking .......................................................................................... 61
4.11 What additional software configurations are needed for Ovation Compact Controllers? . 62
4.11.1 To add Module (RM) points.................................................................................. 62
4.11.2 Adding Node (RN) points ..................................................................................... 65
4.11.3 To insert a Node point .......................................................................................... 66
4.11.4 Node (RN) point assignments for OCC Local Ovation ........................................ 68
4.11.5 Defining Controller devices and drivers ............................................................... 69
4.12 Download, reboot, and load the OCC ............................................................................... 70
4.12.1 To download a Controller drop configuration ....................................................... 70
4.12.2 To reboot a Controller drop .................................................................................. 73
4.12.3 To load a Controller drop ..................................................................................... 74
5 Configuring the OCC to use local Ovation I/O 75

5.1 Overview of configuring OCC for Local Ovation I/O modules ........................................... 75
5.2 To insert a new device number and I/O driver type for local Ovation ............................... 75
5.3 To insert the device type for local Ovation ........................................................................ 78
5.4 To insert a branch for local Ovation .................................................................................. 80
5.5 To insert an I/O module in a branch .................................................................................. 82
6 Configuring the OCC to use embedded protocols 85

6.1 Overview of configuring OCC to use embedded protocols ............................................... 85
6.2 To install the Communication Protocol software on a Database Server........................... 85
6.2.1 To uninstall the Communication Protocol software .............................................. 86
6.3 To insert a new device number and I/O driver type for OCC embedded protocols .......... 87
6.4 To insert the device type for embedded OCC protocols ................................................... 89
6.5 To add OCC embedded protocols .................................................................................... 91
6.6 To configure protocols for OCC ........................................................................................ 92
ii OW360_50
Table of Contents
7 Configuring the OCC to use the ELC module 95

7.1 Overview of configuring OCC for use with ELC modules ................................................. 95
7.2 To insert a new device number and I/O driver type for ELC ............................................. 95
7.3 To insert the device type used for ELC modules .............................................................. 98
7.4 To insert an ELC module in branch ................................................................................ 100
7.5 To add protocols to the ELC module .............................................................................. 103
7.6 To configure protocols for ELC ....................................................................................... 105
8 Configuring the OCC to use the Fieldbus module 107

8.1 Overview of configuring OCC for use with Fieldbus modules ......................................... 107
8.2 To insert a new device number and I/O driver type for Fieldbus modules ..................... 107
8.3 To insert the device type for Fieldbus modules .............................................................. 110
8.4 To insert a Fieldbus module in a branch ......................................................................... 112
9 Configuring the OCC to use the Profibus module 115

9.1 Overview of configuring OCC for use with Profibus modules ......................................... 115
9.2 To insert a new device number and I/O driver type for Profibus modules ...................... 115
9.3 To insert the device type for Profibus modules ............................................................... 117
9.4 To insert a Profibus module in a branch ......................................................................... 119
10 Configuring the OCC to use the Ethernet Remote Node

Interface (RNI) 121
10.1 Overview of configuring OCC for use with Ethernet Remote Node Interface modules .. 121
10.2 To insert a new device number and I/O driver type for Ethernet Remote Node
Interface .......................................................................................................................... 121
10.3 To insert the device type used for Ethernet Remote Node Interface .............................. 123
10.4 To insert a new node for Ethernet Remote Node Interface ............................................ 125
10.5 To insert a branch in a node ........................................................................................... 128
11 Configuring the OCC to use the DeviceNet module 131

11.1 Overview of configuring OCC for use with DeviceNet modules ...................................... 131
11.2 To insert a new device number and I/O driver type for DeviceNet ................................. 131
11.3 To insert the device type used for DeviceNet ................................................................. 134
11.4 To insert a DeviceNet module in a branch ...................................................................... 135
12 Configuring the OCC to use the Machinery Health Monitor module 137
12.1 Overview of configuring OCC for use with Machinery Health Monitor modules ............. 137
12.2 To insert a new device number and I/O driver type for MHM ......................................... 137
12.3 To insert the device type used for MHM ......................................................................... 140
12.4 To insert an MHM module in a branch ............................................................................ 141
OW360_50 iii
Table of Contents
13 Configuring the OCC to use the Digital Excitation Controller

module 143
13.1 Overview of configuring OCC for use with Digital Excitation Controller modules ........... 143
13.2 To insert a new device number and I/O driver type for DEC .......................................... 143
13.3 To insert the device type used for DEC .......................................................................... 145
13.4 To insert a DEC module in a branch ............................................................................... 147
14 Using Restore mode 149

14.1 What is the online Restore Mode function? .................................................................... 149
14.2 Restore mode functions .................................................................................................. 150
14.2.1 Restore mode disabled (Default) ....................................................................... 150
14.2.2 Restore mode enabled (all drops) ...................................................................... 150
14.2.3 Restore mode enabled (redundant drops only) ................................................. 151
14.3 Restore mode performance issues ................................................................................. 151
14.4 Restore mode engineering limitations ............................................................................. 152
14.5 Restore mode point information issues ........................................................................... 152
14.5.1 To set the online Controller Restore Mode ........................................................ 153
15 Using the Controller Diagnostics tool 155

15.1 What is the Controller Diagnostics tool? ......................................................................... 156
15.2 Software platforms that Controller Diagnostics supports ................................................ 156
15.3 What firmware can be downloaded to the I/O modules through the Controller
Diagnostics window? ....................................................................................................... 157
15.3.1 To download firmware revisions to the I/O modules through the Controller
Diagnostics window ............................................................................................ 157
15.3.2 To reboot an I/O module .................................................................................... 159
15.4 Controller Diagnostics window ........................................................................................ 160
15.4.1 To access the Controller Diagnostics tool .......................................................... 161
15.4.2 Controller Diagnostics menu bar ........................................................................ 162
15.4.3 Controller Diagnostics toolbar ............................................................................ 162
15.5 Controller List in the Controller Diagnostics window ....................................................... 163
15.5.1 To select a Controller in the Controller Diagnostics window .............................. 164
15.6 Controller Overview panel in the Controller Diagnostics window ................................... 165
15.7 Controller Diagnostics Update Backup function .............................................................. 167
15.7.1 To update your partner Controller in the Controller Diagnostics window .......... 167
15.8 Control Task Information tab in the Controller Diagnostics window ............................... 168
15.9 I/O Information tab in the Controller Diagnostics window ............................................... 170
15.10 Software Versions tab in the Controller Diagnostics window .......................................... 171
15.11 Point Details tab in the Controller Diagnostics window ................................................... 172
15.12 Sheet Information tab in the Controller Diagnostics window .......................................... 173
15.13 Process Information tab in the Controller Diagnostics window ....................................... 175
15.14 Refresh function for the Controller Diagnostics window ................................................. 176
iv OW360_50
Table of Contents
16 Troubleshooting and Maintenance 177

16.1 What troubleshooting and maintenance procedures are needed for OCC? ................... 177
16.2 To replace Ovation Compact Controller Electronics modules ........................................ 178
16.3 To recover from a Controller failure during a drop load operation .................................. 178
16.4 To reformat the flash ....................................................................................................... 179
16.5 To reboot the OCC .......................................................................................................... 180
16.6 To access the System Viewer to obtain fault code information ...................................... 180
16.6.1 I/O Status values for Fault Code 66 ................................................................... 181
Index 183
OW360_50 v
S E C T I O N 1
1 Introduction to the Ovation Compact Controller
IN THIS SECTION
What is the Ovation Compact Controller? ........................................................................... 2

Features of the Ovation Compact Controller ...................................................................... 3
How is the Ovation Compact Controller similar to a standard Ovation Controller? ............ 5
Definition of Terms for the Ovation Compact Controller ..................................................... 5
Reference documentation ................................................................................................... 8
OW360_50 1
1.1 What is the Ovation Compact Controller?
1.1 What is the Ovation Compact Controller?

Emerson's Ovation Distributed Control System (DCS) is a highly reliable and responsive, real-
time, plant monitoring and process control system. At the heart of the Ovation system is the
Ovation Controller, a drop that executes modulating and sequential control strategies. The
Controller connects to the input and output (I/O) modules that are attached to sensors on the
actual plant equipment. These sensors measure the point values that are broadcast onto the
Ovation Network. When a change (input) is detected, the Controller reads the change and tells
the device (output) to perform an appropriate action as determined by the Controller.
The Ovation Compact Controller (OCC) builds on the long, successful history of the Ovation
Controller series. The Ovation Compact Controller provides many of the same features of
standard Ovation Controllers, but performs these functions using a small, modular configuration,
designed for flexible placement in areas where space is limited. The small footprint is suitable for
installing into an existing cabinet or mounted on a plate or wall. This compact design cost-
effectively extends the Ovation platform to small-scale or highly distributed applications that
require secure, reliable, and direct control close to field devices or plant equipment.
Figure 1: Ovation Compact Controller
While traditional Ovation Controllers are typically located in control rooms away from the devices
they control, the Ovation Compact Controller is used for applications that require direct control
near plant equipment. Placing an Ovation Compact Controller next to field devices significantly
reduces costs associated with field wiring, terminations, and circuit checking compared to
traditional Controllers located in a control room. In addition to operating outside of a control room,
the Ovation Compact Controller supports a wide operating temperature range that allows the
Compact Controller to safely operate in challenging environments.
2 OW360_50
1.2 Features of the Ovation Compact Controller
An added feature of the OCC is the embedded datalink protocol suite, which allows the Ovation
Compact Controller to directly interface to third-party I/O or other devices, such as programmable
logic controllers (PLCs), without the need for extra hardware.
In addition to standard Ovation local area network connections, the Ovation Compact Controller
can communicate through a Wide Area Network (WAN). This option allows an Ovation Compact
Controller to be placed in an area that cannot easily access a local Ovation network. The
Controller communicates securely through an internet protocol (IP) connection using a wide
variety of wired and wireless media options. Process control continues even if the connection to
the host system is lost. When paired with an Ovation Remote Station and a WAN, the Ovation
Compact Controller can operate as a standalone control system.
1.2 Features of the Ovation Comp act Controller

The Ovation Compact Controller offers the following features and benefits:
 Uses modular I/O bases for flexible placement within space-constrained areas.
 Horizontal I/O mounting for space optimization.
 Available in redundant and non-redundant configurations. Dedicated Low Voltage Differential
Signaling (LVDS) data lines connect Primary and Partner through the backplane.
 Optional stand-alone system architecture.
 Operating characteristics include:
 Low power requirements.
 Expanded temperature range (operating temperature range from -20 degrees to +70
degrees Centigrade).
 Supports up to three local R-Line branches.
 Configured and maintained using standard Ovation engineering tools.
 Can execute more than 1,000 control sheets.
 Supports up to three control tasks. Like the standard Ovation Controller, the first two tasks are
required and fixed in their task periods (100 and 1000 milliseconds respectively). The third
task is user configurable to execute on periods from 10 milliseconds to 30 seconds.
 Supports up to 10,000 Ovation points.
 Provides "bumpless" automatic failover between redundant Controllers.
 Wide Area Network capability for intermittent, small bandwidth communication.
 Provides continuous operation if disconnected from the host system.
 Compatible with all Ovation I/O modules*:
 Standard Ovation I/O (analog, digital, SOE).
 Specialty Ovation I/O (Machinery Health Monitor, Digital Excitation Controller, digital bus
interface, and turbine I/O).
 Third-party devices (Ethernet I/O, devices with embedded controllers).
Note: *The OCC supports Relay panels 5A22410, 5A22411, and 5A22412 when used in
conjunction with an Ovation Digital Output (DO) module (1C31122). Other Ovation relay bases
are not supported.
OW360_50 3
1.2 Features of the Ovation Compact Controller
1.2.1 Automatic failover control
Ovation Controllers are equipped with automatic failover capabilities for redundant applications.
This means that if the processor that is in control mode fails, watchdog detection circuitry disables
the I/O interface of the primary processor and informs the partner processor of the failure. The
partner processor then takes control of the I/O bus and begins to execute the process control
application program and broadcasts information over the Ovation Network.
Algorithms track the output values, pass the information upstream, and apply the data during the
first pass of execution. The result is a bumpless failover, even in the case of a malfunction. A full
range of events can trigger automatic failover, including:
 Control processor failure.
 Network failure.
 Removal of power from the control processor.
 Control processor reset.
Once the control is passed to the partner processor, the failed processor may be powered down,
repaired, and powered back up with no harmful effects on executing control strategy. On restart,
the repaired processor detects that its partner is in control and assumes the partner role. The
processor in control detects the presence of the partner processor and adjusts for redundant
operation.
1.2.2 Slot mismatch detection
The OCC provides a slot mismatch detection feature to protect against unknown behavior and
provide a way to clear the Controller's file system.
The Media Access Address (MAC Address or Ethers address) is stored in a nonvolatile memory
on the backplane. A unique MAC address is associated with each slot. When a new (blank
memory) Compact Controller boots, the MAC address provided by the nonvolitile memory on the
backplane is stored on the card. On subsequent boots, the application verifies that the MAC
address stored on the card matches the MAC address on the backplane. If a mismatch is
detected, the Compact Controller's file system is reformatted and the Compact Controller is
rebooted.
The slot mismatch detection feature protects against an OCC card with an existing configuration
being inserted in a different based with unknown I/O points.
4 OW360_50
1.3 How is the Ovation Compact Controller similar to a standard Ovation Controller?
1.3 How is the Ovation Compact Controller similar to a standard

Ovation Controller?
The Ovation Compact Controller provides many of the same powerful and reliable features of
standard Ovation Controllers (OCR1100 and OCR400 modules) but does so in a flexible, modular
design. Like OCR Controllers, the OCC performs the following tasks:
 Executes simple to complex modulating, discrete, and sequential control strategies, and
performs data acquisition and monitoring functions.
 Reads I/O modules and converts data to process points.
 Reads process points and writes data to I/O modules.
 Originates and receives process points.
 Provides alarming and command word processing for originated points.
 Functionality is defined by control sheets created from standard and advanced Ovation
algorithms.
Note: You can only create Ladder logic for the Ovation Compact Controller with Ladder
Elements. The 7x9 Ladder algorithm is currently not supported.
 Supports non-redundant and fully redundant layouts.

 Redundant configurations feature completely “bumpless” fail-over from the primary Controller
to the partner Controller.
 Supports all Ovation I/O module styles.
Note: The OCC supports Relay panels 5A22410, 5A22411, and 5A22412 when used in
conjunction with an Ovation Digital Output (DO) module (1C31122). Other Ovation relay bases
are not supported.
 Supports standard I/O terminations and Marshalling terminations.

 Easily interfaces to third-party devices.
 Supports remotely located Ovation I/O modules.
 Complies with IEC61131-2 and CE Mark standards.
1.4 Definition of Terms for the Ovation Compact Controller

The following terms and descriptions may be helpful while using this manual.
Terms used with the Ovation Compact Controller
TERM DESCRIPTION
AC Mains Cables that carry the main AC current into the I/O cabinets.
AWG American wire gauge is used in the United States as a standard method of denoting
wire diameter. Increasing gauge numbers give decreasing wire diameters. Outside
of North America, wire sizes for electrical purposes are usually given as the cross-
sectional area in square millimeters.
Baud rate Number of bits-per-second a modem can send or receive.
OW360_50 5
TERM DESCRIPTION
Branch Any combination of two- and/or four-slot OCC-style I/O bases connected so as to
result in a minimum of two, and a maximum of eight, slots for connection of I/O
modules. I/O bases are daisy-chained together. They include integral bus
terminators, switched in or out with a slide switch on each base.
Bridge Device that connects two or more network components and transmits data with
source and destination addresses on different network components.
Broadcast Data packet delivery system where copies of the packet are delivered to all
destinations on the network.
CE Mark Manufacturers' declaration that the product complies with the essential requirements
of the relevant European health, safety, and environmental protection legislation.
Compact Controller An Ovation Controller with a smaller footprint than the standard Ovation Controllers.
Control Task A defined segment of the Controller software configuration. Within a given control
task, inputs are scanned, control sheets are executed, and outputs are generated
and transmitted, all at the frequency defined for the control task. Up to three control
tasks can be configured for the Ovation Compact Controller.
DCS Distributed Control System.
Drop A term used to refer to a Controller, Workstation, or Database Server that is a

member of an Ovation network and is defined as a drop by the Ovation Developer
Studio.
Drop point Refers to a point configured to be updated or originated by a particular drop on the
Ovation system.
Dual attachment Connection to two different network switches. A Dual Attached Station (DAS) is a
node that is connected to two different switches.
EID Electronic identification number.
Electronics module A plastic housing containing the necessary electronic circuitry and associated lenses
and labeling to interface between field devices and the Ovation I/O bus. Electronics
modules are inserted directly into an Ovation I/O base unit and are typically (but, not
always) paired with an associated Personality module.
Ethernet Remote An interface module that uses an Ethernet-based protocol to connect the local
Interface Controller to I/O modules in remote locations. The choices are the Remote Node
Interface module that can be used with all Ovation I/O and Numalogic for connection
to the Numalogic PC700 series remote I/O.
Fast Ethernet Local area network (LAN) transmission standard that provides a data rate of 100
megabits per second.
Gigabit Ethernet Transmission technology based on the Ethernet frame format and protocol used in
local area networks (LANs) that provides a data rate of 1 billion bits per second (one
gigabit). Gigabit Ethernet is defined in the IEEE 802.3 standard.
Field Programmable A standard, off-the-shelf, user-configured integrated circuit that is used to implement
Gate Array (FPGA) custom logic functions.
Hot swappable Provides the capability of removing and installing the I/O module or Controller from
the base unit with power applied.
I/O Module Provides the interface between Ovation Controllers and field devices.
Note: In this manual, the term "module" refers to an I/O module unless otherwise
specified as a specific type of module, such as a Controller module.
6 OW360_50
TERM DESCRIPTION
LAN Local Area Network. A computer network limited to the immediate area, usually the
same building.
License A necessary permission to use certain Emerson Process Management software
products.
Load function Ovation function that is used to transfer data from the Master Database and
distribute it to control drops and those drops that originate points.
LVDS Low Voltage Differential Signaling. A high speed, low power general purpose
interface standard that provides the redundancy capabilities in the OCC.
MAC address Media access control (MAC) address is an address used by network interfaces to
uniquely identify themselves on a network.
Master Database Contains the entire process database. It is used for creating, modifying, and
verifying control strategies and process points. At runtime, it supports queries of the
process database, captures changes made to control and point attributes, and
propagates those changes to the distributed database.
Network The communication link used to transfer time-critical information between drops or
stations.
NIC A Network Interface Card (NIC) is required in each of the end stations, Controller or
HMI. NICs are available in two configurations, Single Attach Station (SAS) or Dual
Attach Station (DAS) with copper connections. Within a system, it is NOT necessary
that all stations have like modes of attachment. SAS and DAS may be mixed as
economics, function, and redundancy dictate.
Node Active element on a Fast Ethernet network that has an address. Can be a station or
a switch. Up to 1000 nodes are permitted per network.
OCC Ovation Compact Controller (OCC) is a member of the Ovation Controller family, but
provides many of the standard Controller features using a small, module
configuration, designed for flexible placement in areas where space is limited.
Point A record in the global database containing a value (such as an input or output) and
related data. Refer to Ovation Record Types Reference Manual for more
information.
Point name Alphanumeric identifier associated with a point on the Ovation network (up to 24
characters for Windows).
Port Entry/exit mechanism in a node that can connect to the network cable and can
connect to another node.
Record The set of data associated with a point, including the point name, System ID, value,
status, and various other fields, depending on the point record type.
Remote I/O A configuration where the I/O is located remotely from the Controller.
Remote Node A grouping of I/O modules that communicates with the Controller through media that
can carry control signals over a long distance (for example, fiber-optic).
RNI Remote Node Interface (RNI) consists of a Remote Node Interface Base assembly
and the associated Remote Node Interface modules.
Provides an integral remote access mechanism for communicating through a 100
Mbps Ethernet protocol between the Ovation Controllers (OCR400, OCR1100,
OCC100 or later) and remotely located standard Ovation I/O modules.
Router A hardware or software set-up that routes information between two or more
networks.
OW360_50 7
1.5 Reference documentation
TERM DESCRIPTION
SoC System on a Chip. An integrated circuit that integrates all components of a computer
or other electronic systems. It may contain digital, analog, mixed-signal, and often
radio-frequency functions, all on a single substrate.
System ID System Identification number. The network reference number for each point which
may be transmitted.
Switch Connects stations and/or LAN segments. Operates at Data Link Layer.
TCP/IP Transmission Control Protocol / Internet Protocol, a set of communication protocols
that allows dissimilar computers to share information over a network.
UTP Unshielded Twisted Pair. A common Ethernet connection medium utilized for high
speed communications that contains twists in individual signal pairs but does not
contain an overall cable shield for electromagnetic purposes.
Watchdog Timer A timer that, if allowed to expire, resets the microprocessor.
1.5 Reference documentation

The following manuals provide more information about various topics in this manual:
 Ovation Developer Studio User Guide
 Ovation Digital Excitation Controller User Guide
 Ethernet Link Controller User Guide
 Machinery Health Monitor User Guide
 Planning Your Ovation System
 Ovation Profibus User Guide
 Ovation DeviceNet User Guide
 Remote Node Interface User Guide
 Ovation I/O Reference Manual
8 OW360_50
S E C T I O N 2
2 Hardware and software requirements for the Ovation

Compact Controller
IN THIS SECTION
Ovation Compact Controller components ........................................................................... 9

Pin assignments for power connectors ............................................................................. 19
Diagnostic LEDs for Ovation Compact Controller ............................................................. 23
Specifications for the Ovation Compact Controller ........................................................... 23
Power supply options for the Ovation Compact Controller ............................................... 25
Hardware installation guidelines and best practices ......................................................... 29
Using the Ovation Compact Controller in a Wide Area Network (WAN) ........................... 33
Minimum software requirements for Ovation Compact Controller .................................... 34
What licensing is required for the Ovation Compact Controller? ...................................... 34
2.1 Ovation Compact Controller components

The Ovation Compact Controller is comprised of the following parts (Ovation part numbers are
listed in parentheses):
 Controller Base (5X00791G01)
 Controller module (5X00790)
 Two-Slot Horizontal Marshalling Base (5X00807)
 Four-Slot Horizontal Standard Termination Base (5X00809)
In addition, the OCC system provides the following items:
 Single Bus I/O cable (5X00817 - Group specific lengths up to 30 ft.)
 Power distribution scheme
 Simplex Main (5X00825)
 Redundant Main (5X00826)
 Simplex Main/Aux (5X00827)
 Redundant Main/Aux with Power Distribution Panel (5X00828)
 Redundant Main/Aux (5X00829)
OW360_50 9
The OCC base (also known as the backplane) provides connections for three branches of local
I/O. The I/O is interfaced through two I/O base options, each providing a horizontal I/O
arrangement. The first horizontal I/O arrangement is a four-slot I/O base with fixed compression
terminals. The second option is a two-slot I/O base with removable compression connectors for
external cable marshalling applications. Each base can be cascaded (daisy-chained) to provide a
full complement of eight I/O modules per branch.
The following figure shows an example of the Ovation Compact Controller base configurations
and their connections.
Figure 2: Example Ovation Compact Controller base configurations and connections
10 OW360_50
2.1.1 Controller base assembly
The controller base assembly (5X00791G01) provides the interface for a redundant pair of OCC
controller modules, an integral power/status connector, and three local I/O branch connectors. It
is designed with a small footprint that is suitable for installing into an existing cabinet, on a plate,
or on a wall. Cabled connections to I/O base assemblies provide I/O placement flexibility.
The Controller Base assembly can accommodate up to two OCC controller modules. This can be
either two (redundant) controller modules or one (simplex) controller module and a cavity insert.
The modules are inserted into the base units and latched into place.
Figure 3: Controller Base drawing showing top and bottom view
OW360_50 11
The controller base assembly also incorporates the necessary redundancy connections between
the controller modules. Unlike standard Ovation Controllers that use Ethernet ports to exchange
data, the OCC uses Low Voltage Differential Signaling (LVDS) to provide redundancy between
the Primary and Partner Controller. The LVDS executes the copy-to-backup functionality between
redundant OCCs.
The controller base assembly also interfaces to two (one for each controller module), non-volatile
storage modules for Network Ethers address (also called MAC address) identification. Remove
the blue Ovation caps from the base, to reveal a chip with a QR code and a partial Network
Ethers address number. The first six numbers are always the same so they are not shown on the
sticker. These numbers are 00:40:03. The numbers that are shown on the sticker are unique to
your module.
The controller base assembly provides the following features:

 No mounting clamp. Mounting support is provided by four mounting flanges in the plastic
housing.
 Redundant controller module support (A simplex configuration involves one controller module
and one cavity insert.)
 Local I/O branch connectors for three branches (separate 9-pin D connectors for each
branch):
 Power connector
 20-pin terminal block for flexibility in interfacing power and power supply status (2 x 10
terminal, dual row compression connector).
 14 AWG maximum.
 Interface for 24VA, 24VB and Common. Pass through terminals are also provided for
daisy chain power interface to the I/O bases(s).
 Earth Ground terminal (short connection to the mounting plate is necessary since there is
no mounting clamp).
 Power supply status terminals for up to four power supplies.
 Auxiliary Power pass through terminals provided to optionally daisy chain Aux power to
the I/O base(s). Aux power is not used by this base.
12 OW360_50
2.1.2 Ovation Compact Controller module
The Ovation Compact Controller module (5X00790G01) (also referred to as controller module)
consists of a single printed circuit board enclosed in a plastic housing.
The host process is based on the Xilinx Zynq7000 All Programmable SoC (System on a chip)
architecture. The processor integrates a dual-core ARM® Cortex™-A9 based, 667 MHz
processing system (PS) and programmable logic (PL) in a single device.
The controller module is “hot swappable,” which means it can be removed and replaced without
interrupting system power or using mechanical tools.
The controller module includes:

 Two Ethernet ports that support 1 Gigabit per second (1Gbps) and/or 100 Megabits per
second (100 Mbps) speeds, UTP copper RJ45 connectors at the top of the module.
 USB to UART port, and a USB HOST interface for flash extension. This interfaces to a
removable 1 Gbyte, 10-pin Flash module.
 32 Mbytes Quad SPI Flash (16MB each).
 256 Mbytes DDR3 DRAM.
 Ovation Electronic ID support.
 RS485 interface to support the three branches of local I/O supported by the OCC.
 LVDS channels for communication between redundant OCC modules.
 Field Programmable Gate Array (FPGA), which is integral to the SoC, performs various
functions such as redundancy logic and I/O interface control.
OW360_50 13
Figure 4: OCC module front and top views
14 OW360_50
2.1.3 Two-slot horizontal I/O Marshalling base
The OCC two-slot I/O base provides slot positions for two Ovation I/O modules in a compact
footprint. Each base provides a mechanism for connecting field signal wiring to the Ovation I/O.
The Two-slot base also provides the interface for power, the I/O bus (an input D connector from
the Controller backplane and an output D connector for cascading to additional I/O bases on the
branch), and a serial communications bus terminator selection switch. The base provides
mounting flanges for cabinet, plate, or wall mounting.
The functionality of the Two-Slot Horizontal Marshalling base unit is the same as the four-slot
base (see page 17) except that the field termination terminal blocks are replaced with 17-pin
connector headers. The headers are mated with 17-position connectors. This arrangement allows
for the use of pre-terminated cable connectors for field wiring. After the connectors are
terminated, they can be inserted into the Marshalling base.
The two-slot base can be cascaded to provide a full complement of eight I/O modules. A series of
base units can be connected to form a “branch” of Ovation I/O. The OCC supports three local I/O
branch connectors, so you can have up to 24 modules per OCC. If you already have one two-slot
base, you can add the following configurations to get the maximum number of modules:
 Three additional 2-slot bases.
 One additional 2-slot base and one additional 4-slot base.
These configurations can be placed side-by-side or in other configurations to fit into an existing
cabinet.
A Termination Selection switch is located at the top of the base. This two-position slide switch is
provided to either route the I/O bus to a terminator at the end of the branch or to the output “D”
connector for cascading to additional bases. If the I/O base is the last base on the branch, the
switch must be in the Terminator “ON” Position; otherwise, it should be in the Terminator “OFF”
position.
Note: Cabling and pinout information is typically specified at the project level in the project
wiring diagrams and cable lists.
OW360_50 15
Figure 5: Two-slot horizontally mounted I/O base showing front and top view
The OCC two-slot I/O base has the following features:

housing.
 I/O branches interface:
 9-pin male D connector to receive the I/O bus from the Controller backplane or an up
stream I/O backplane.
 9-pin female D connector to distribute the I/O bus from the two-slot I/O backplane to
cascaded I/O backplanes or an up stream I/O backplane.
 Power connector:
 2 x 10 terminal, dual row compression connector.
 14 AWG maximum.
 Interface for two 24V direct current supply connections and a common neutral. Pass
through terminals are also provided for daisy chain power interface to the I/O bases(s).
 Earth Ground terminal (short connection to the mounting plate is necessary as there is no
mounting clamp).
 Interface for Auxiliary Power. Pass through terminals are also provided for daisy chain
power interface to the I/O bases(s).
 Fused Auxiliary Power terminals. Used to distribute fused Auxiliary power to cascaded I/O
bases.
 Four rows of 17-position headers (5X00807G01 comes without connectors; 5X00807G02 has
connectors included). Support provided for standard and high density I/O modules.
 Auxiliary power fuse and associated blown fuse LED.
 Integrated I/O bus Terminator
 User accessible terminator bypass switch to disconnect the integral terminator if
cascaded I/O backplanes are employed.
16 OW360_50
2.1.4 Four-slot horizontal I/O base with standard terminations
The OCC four-slot I/O base provides slot positions for four Ovation Electronics (Emod) and
Personality (Pmod) modules in a compact footprint. Each base provides a mechanism for field
wiring and connecting field signals to the Ovation I/O. The OCC also provides the interface for
power, and the local I/O bus (an input D connector from the Controller backplane and an output D
connector for cascading to additional I/O bases on the branch), and a terminator selection switch.
The base provides mounting flanges for cabinet, plate, or wall mounting.
The four-slot base houses up to four standard Ovation I/O modules. Standard Ovation Emods and
Pmods fit securely into the base. Each standard I/O module is assigned a logical address. A four-
slot base has four logical module addresses, one address is assigned for each module housed
within the base unit.
The four-slot base can be cascaded to provide a full complement of eight I/O modules. A series of
base units can be connected to form a “branch” of Ovation I/O. The OCC supports three local I/O
branch connectors, so you can have up to 24 modules per OCC. If you already have one four-slot
base, you can add the following configurations to get the maximum number of modules:
 One additional 4-slot base.
 Two additional 2-slot bases.
These configurations can be placed side-by-side or in other configurations to fit into an existing
cabinet.
A Termination Selection switch is located at the top of the base. This two-position slide switch is
provided to either route the I/O bus to an end of the branch terminator or to the output “D”
connector for cascading to additional bases. If the I/O base is the last base on the branch, the
switch must be in the Terminator “ON” Position; otherwise, it should be in the Terminator “OFF”
position.
OW360_50 17
Figure 6: Four-slot horizontally mounted I/O base showing front and top view
The OCC four-slot I/O base has the following features:

housing.
 I/O branches interface:
 9-pin male D connector to receive the I/O bus from the Controller backplane or an up-
stream I/O backplane.
 9-pin female D connector to distribute the I/O bus from the four-slot I/O backplane to
cascaded I/O backplanes or an up-stream I/O backplane.
18 OW360_50
2.2 Pin assignments for power connectors
 Power connector:
 2 x 10 terminal, dual row compression connector.
 14 AWG maximum.
 Interface for two 24V direct current supply connections and a common neutral. Pass
through terminals are also provided for daisy chain power interface to the I/O bases(s).
 Earth Ground terminal (short connection to the mounting plate is necessary as there is no
mounting clamp).
 Interface for Auxiliary Power. Pass through terminals are also provided for daisy chain
power interface to the I/O bases(s).
 Fused Auxiliary Power terminals. Used to distribute fused Auxiliary power to cascaded I/O
bases.
 Four rows of 17-terminal compression cage terminal block for interfacing to field wiring.
Support provided for standard and high density I/O modules.
 Auxiliary power fuse and associated blown fuse LED.
 Integrated I/O bus Terminator:
 User accessible terminator bypass switch to disconnect the integral terminator if
cascaded I/O backplanes are employed.
2.1.5 Network interface ports
The Ovation Compact Controller has two Ethernet ports that support 1 Gigabit per second
(1Gbps) and/or 100 Megabits per second (100 Mbps) speeds. They are UTP copper RJ45
connectors. These ports are located at the top of the each Controller and are labeled E1 and E2.
The E2 port is always used as the connection for Ovation. The E1 port can be used as a
redundant Ovation connection, or it can be used for a third-party Ethernet protocol (for example,
Modbus).
The OCC has a built-in datalink protocol suite that enables direct interface to third-party I/O or
other controllers. When using the protocols that are native to the OCC, make the connection
through the E1 port. If you are using an Ethernet Link Controller module to communicate to
various protocols, use the ELC connections as defined in Ethernet Link Controller User Guide.
Note: The Ethernet ports are copper only. Fiber connections require media converters.
The Ovation Compact Controller also supports the Remote Node Interface (RNI) module. The
RNI provides an integral remote access mechanism for communicating between the Ovation
Controller and remotely located Ovation I/O modules through a 100Mbps Ethernet protocol. Each
Ovation Compact Controller can support up to 16 pairs of Remote Node Interfaces. Each Remote
Node Interface can support up to eight branches of I/O with up to eight I/O modules per branch.
There are various options for implementing the network infrastructure between an Ovation
Controller and a Remote Node Interface. For more information, refer to Remote Node Interface
User Guide.
2.2 Pin assignments for pow er connectors

The OCC base, two-slot, and four-slot bases provide an interface for power/status. The following
sections give the pin assignments for these connectors.
OW360_50 19
2.2.1 Power connectors for OCC base
The OCC base power/status connector is a 20-pin (2 rows x 10) terminal block. It accepts 14
AWG maximum wire.
The following table lists the pin assignments.
Pin assignments for 20-pin terminal block on Base
PIN NO. SIGNAL PIN NO. SIGNAL

TOP ROW BOTTOM ROW
1 24 VA 1 24 VA
2 24 VB 2 24 VB
3 COM 3 COM
4 COM 4 COM
5 EARTH GROUND 5 RSV
6 COM 6 RSV
7 AUX+ 7 AUX+
8 AUX- 8 AUX-
9 PS STATUS 1A OK/ 9 PS STATUS 1B OK/

10 PS STATUS 2A OK/ 10 PS STATUS 2B OK/
1. Pins 1-4 top row: 24VA, 24V, COM, COM are the interface to the redundant 24V main power
supplies. The equivalent pins on the bottom row are for cascading these same connections to
a down-stream I/O base.
2. Pin 5 top row: EARTH GROUND. A short earth grounding wire is required between this
terminal and the mounting plate.
3. Pin 6 top row: COM. Equivalent to the PG connection in a standard Ovation Controller. Used
to provide a good ground reference between the OCC backplane and downstream I/O base.
4. Pins 7-8 top row. AUX+, AUX- Connection to the pre-auctioneered 24 Volt Auxiliary power.
Auxiliary power is not used by this base. The connections provide a convenient landing point
to allow distribution of Auxiliary power to downstream I/O bases through the same named pins
on the bottom row.
5. Pins 9 of the top row interfaces to a series connection of the status relays associated with the
Primary Main and Auxiliary power supplies. A failure of either power supply indicates a failed
status. Likewise, pin 9 of the bottom row indicates the status of the Secondary Main/Auxiliary
power supply.
6. Pins 10 top and bottom row PS STATUS 2AOK/, PS STATUS 2BOK/. These pins interface to
power supply status relay of an optional second set of primary and secondary Auxiliary power
supplies.
20 OW360_50
2.2.2 Power connector for two-slot Marshalling base
The two-slot I/O Marshalling base has a 20-pin (2 rows x 10) terminal block for power/status
connection. It accepts 14 AWG maximum wire.
Pin assignments for 20-pin terminal block on Two-Slot Marshalling Base

TOP ROW BOTTOM ROW
1 24 VA 1 24 VA
2 24 VB 2 24 VB
3 COM 3 COM
4 COM 4 COM
6 COM 6 RSV
7 AUX+ 7 AUX+
8 AUX- 8 AUX-
9 EXPANSION AUX IN+ 9 EXPANSION AUX OUT+

10 EXPANSION AUX IN- 10 EXPANSION AUX OUT-
4. Pins 7-8 top row. AUX+, AUX- . Connection to the pre-auctioneered 24 Volt Auxiliary power.
The 24V Aux power is fused with a 5 amp fuse on the backplane. A blown fuse LED is also
provided.
5. Pins 9-10 top row. EXPANSION AUX IN+, EXPANSION AUX IN-. These terminals are used
to interface to an auxiliary power supply that is not 24V (see note), or they are used if
receiving auxiliary power in a daisy chain fashion from an upstream I/O base. These terminals
bypass the fuse and indicator LED associated with the 24V Aux terminals.
Note: If the branch interfaces to Auxiliary power that is not 24V by a separate power source,
the power source must be interfaced to the EXPANSION AUX IN+, EXPANSION AUX IN-
TERMINALS and must be fused with an external 5 amp, 250 volt fast acting fuse.
6. Pins 9-10 bottom row. EXPANSION AUX OUT+, EXPANSION AUX OUT-. These terminals
are used to cascade (daisy chain) Auxiliary power to a downstream I/O base. They would
interface to the downstream I/O base terminals EXPANSION AUX IN+, EXPANSION AUX IN-
.
OW360_50 21
2.2.3 Power status connector for four-slot Standard base
The four-slot I/O Standard base has a 20-pin (2 rows x 10) terminal block for power/status
connection. It accepts 14 AWG maximum wire.
Pin assignments for 20-pin terminal block on Four-Slot Standard Base

TOP ROW BOTTOM ROW
1 24 VA 1 24 VA
2 24 VB 2 24 VB
3 COM 3 COM
4 COM 4 COM
6 COM 6 RSV
7 AUX+ 7 AUX+
8 AUX- 8 AUX-
9 EXPANSION AUX IN+ 9 EXPANSION AUX OUT+

10 EXPANSION AUX IN- 10 EXPANSION AUX OUT-
4. Pins 7-8 top row. AUX+, AUX- . Connection to the pre-auctioneered 24 Volt auxiliary power.
The 24V Aux power is the fused with a 5 amp fuse on the backplane. A blown fuse LED is
also provided.
5. Pins 9-10 top row. EXPANSION AUX IN+, EXPANSION AUX IN-. These terminals are used
to interface to an auxiliary power supply that is not 24V (see note), or they are used if
receiving auxiliary power in a daisy chain fashion from an upstream I/O base. These terminals
bypass the fuse and indicator LED associated with the 24V Aux terminals.
Note: If the branch interfaces to Auxiliary power that is not 24V by a separate power source,
the power source must be interfaced to the EXPANSION AUX IN+, EXPANSION AUX IN-
TERMINALS and must be fused with an external 5 amp, 250 volt fast acting fuse.
6. Pins 9-10 bottom row. EXPANSION AUX OUT+, EXPANSION AUX OUT-. These terminals
are used to cascade (daisy chain) auxiliary power to a downstream I/O base. They would
interface to the downstream I/O base terminals EXPANSION AUX IN+, EXPANSION AUX IN-
.
22 OW360_50
2.3 Diagnostic LEDs for Ovation Compact Controller
2.3 Diagnostic LEDs for Ovation Compact Controller

The Ovation Compact Controller Electronics module contains following LEDs to display status.
Diagnostic LEDs
LED DESCRIPTION
P (Green) Power OK LED. Lit when the logic board’s +5V,+3.3V,2.5V, 1V, and 1.8V digital
supply voltage level is OK and the processor is configured correctly.
C (Green) Communication OK LED. Lit when the Ovation Compact Controller is communicating
with the module.
E (Red) External Fault LED. Lit to indicate that the Ovation Compact Controller is not
communicating with the module. Set by Bit 14 of the LED Register by the firmware.
I (Red) Internal Error LED. Lit whenever there is any type of internal module error. Set by Bit
7 of the LED Register by the firmware.
Possible causes include:
▪ Module initialization is in progress.
▪ Internal hardware error.
▪ Module reset.
▪ Forced error has been received from the OCC.
1-7 (Red) General purpose LEDs under firmware control by the Zynq processor. Be aware of
the following patterns:
▪ A single lit LED moving up and down the seven LEDs once a second indicates that
the OCC is in backup mode.
▪ Each LED lighting sequentially and then each LED going dark sequentially indicates
that the OCC is in control mode.
A1, A2 (Green) Indicates Ethernet activity on Ethernet ports 1 and 2 respectively. Blinking indicates
activity. Off indicates no activity.
L1, L2 (Green) Indicates Ethernet Link activity on Ethernet ports 1 and 2 respectively. Lit solid if the
link is up (connected). Off indicates the link is down.
2.4 Specifications for the Ovation Compact Controller

The following table lists the OCC's electrical and environmental specifications.
Ovation Compact Controller specifications
DESCRIPTION VALUE
Controller Electronics module 240 mA typical.

+24V Main Current
265 mA maximum
Controller Electronics module 5.8 W typical
+24V Main Power
6.4 W maximum
Input Under voltage Lockout 18.3v volts typical
Input Overvoltage Crowbar 35 volts typical
OW360_50 23
2.4 Specifications for the Ovation Compact Controller
DESCRIPTION VALUE
Holdup time (loss of 24V to 12msec typ

system reset)
10/100 Mbps UTP Ethernet Port Quantity - 2
Distance - 100m maximum
Auto negotiation support - Configurable
MDIX support - Yes
Zynq 7000 Diagnostic Port USB UART interface.

1 Mbps Maximum
5 pin micro USB header on the logic card
Access through the module top side
Dielectric Isolation +/- 1,000 V DC or peak AC for one minute, Ethernet ports to logic or earth
ground
I/O interface Three branches of I/O bus controllers supporting standard I/O. Extended
Read cycles, standard block transfer cycles as well as Variable payload
block transfer cycles.
Memory DDR3 – 256Mbyte
QSPI Flash (Boot) - 32 Mbyte
USB Flash – Up to 1Gbyte, wear leveling, ECC, Removable
EEPROM for Electronic ID – 1Kbyte I2C located on controller module
EEPROM for MAC address storage 1Kbyte I2C located on the controller
backplane
Processor System Number of cores: 2
Operating frequency: 667MHz
Processor: ARM Cortex A9
Power Supply Voltage Minimum Nominal Maximum
Main Primary Voltage: 21.0V 24.0V 25.0V
Main Secondary Voltage: 21.0V 24.0V 25.0V
Note: The two main supply voltages are the redundant power feeds to the
controller module and are diode auctioneered on the controller module's
logic board.
Auxiliary Power Supply Voltage Maximum Minimum Nominal

22.8V 24.0V 25.5V
Air temperatures The operating ambient air temperature range is from:
-20 to 70 degrees C
-4 to 158 degrees F
Humidity From 0% to 95% relative humidity, non-condensing, through an ambient air
temperature range of:
-20 to 70 degrees C
-4 to 158 degrees F, but with a maximum wet bulb temperature not over 35
degrees C (95 degrees F).
24 OW360_50
2.5 Power supply options for the Ovation Compact Controller
2.5 Pow er supply options for the Ovation Compact Controller

The Ovation system requires a reliable power source with minimal voltage and frequency
fluctuations. Ovation systems can use AC or DC cabinet power supplies, or a combination of
both. The type used is dependent on the needs of the system application. (AC power supplies
and AC mains are supported in CE Mark certified systems.)
The Ovation Compact Controller uses the Industrial 24VDC, 5A power supply series, which
provides up to 120 Watts of output power with high efficiency, which saves energy and lowers the
amount of heat generated. In addition, the compact packaging saves space on a DIN Rail, on a
wall, or in a cabinet. The power supply case consists of a fully enclosed metal housing with fine
ventilation grid to keep out small parts. The power supply features input and output diagnostic
LEDs, adjustable output voltage, sag immunity, active power factor correction and universal
voltage (85-264Vac, 50/60 Hz) inputs. The Power Boost overload capability starts high inrush
loads without folding or shutdown.
Ovation power supplies are classified as either Main or Auxiliary. Main power supplies provide
power to the Compact Controller and I/O modules. Auxiliary power supplies provide power only to
field items. In addition, some Ovation I/O modules require an auxiliary power supply in addition to
the main power supply.
Currently, there are five possible power distribution schemes for the Ovation Compact Controller:
 Simplex Main (5X00825G01-G04)
 Redundant Main (5X00826G01 - G08)
 Simplex Main/Aux (5X00827G01 - G04)
 Redundant Main/Aux with Power Distribution Panel (5X00828G01- G08)
 Redundant Main/Aux (5X00829G01 - G08)
The power supply configuration selection depends on several factors:
 Space in the cabinet or area where the Ovation Compact Controller power distribution
scheme is located.
 Whether the powering scheme consists of either Main and/or Auxiliary power supplies in a
redundant or non-redundant configuration.
 Placement of the AC or DC circuit breakers, which depends on the placement of the
customer's input power feed connections.
 Whether the AC and DC input power supply cable assembly is for United States or European
wiring code standards.
OW360_50 25
The following figure shows an example of a Simplex Main power supply.
Figure 7: Simplex main power supply configuration
Power supply attributes
ITEM DESCRIPTION
+ Output terminal - Positive 24VDC output screw connection terminal of the power
supply.
See OCC power supply specifications (see page 27) for DC output rating
specifications.
- Output terminal - Negative (return) output screw connection terminal of the power
supply.
See OCC power supply specifications (see page 27) for DC output rating
specifications.
Output terminals - DC OK relay contact output screw connection terminals of the
power supply.
LED diagnostics The LEDs on the power supply are:
▪ Input power
▪ Output power
▪ Alarm condition
See OCC power supply LED status conditions (see page 29) for more information.
22.5 - 28.5 Vdc Output Voltage Potentiometer - Turn the phillips screw to adjust the output voltage.
26 OW360_50
ITEM DESCRIPTION
Single/Parallel Set to Single only for all Ovation applications.

switch
L/+ Input terminal - Positive input screw connection terminal of the power supply where
the "L" label represents the positive AC power feed connection and the "+" represents
the positive DC power feed connection.
See OCC power supply specifications (see page 27) for AC and DC input rating
specifications.
N/- Input terminal - Negative (return) input screw connection terminal of the power supply
where the "N" label represents the positive AC power feed connection and the "-"
represents the positive DC power feed connection.
See OCC power supply specifications (see page 27) for AC and DC input rating
specifications.
Input terminal - Potential earth ground input screw connection terminal of the power
supply.
See OCC power supply specifications (see page 27) for AC and DC Input Rating
Specifications.
For general information on power supplies, refer to the Ovation I/O Reference Manual and the
Planning Your Ovation System manual.
2.5.1 OCC power supply specifications
The following table lists specifications for the 24 VDC power supply.
Power supply specifications
DESCRIPTION SPECIFICATIONS
Mechanical specifications
Dimensions (H x W x D) 4.85 in. x 1.97 in. x 4.36 in.
123.3 mm x 50 mm x 110.8 mm)
Free space 25 mm above and below, 10 mm left and right, 15 mm in front
AC and DC Inputs
Nominal Voltage 100 - 240 Vac
AC Range 85 - 264 Vac
DC Range1 90 - 375 Vdc
Frequency 43 - 67 Hz
Nominal Current2 1.75 - 0.55 A
Inrush current maximum Typical < 15 A
Efficiency (Losses3) > 88% typical (14 W)
Power Factor Correction Active power factor correction to better than 0.92
OW360_50 27
Voltage Phase Type Single Phase (AC Voltage)

DC Outputs
Power Supply Switch Setting Single (Default for Ovation applications)
Nominal Voltage 24 V (23.5 ~ 28.5 Vdc Adj.)
Tolerance4 < +/- 2% overall (combination line, load, time, and temperature related
changes)
Initial Voltage Setting 24.5 V +/- 1%
Ripple5 < 50 mVpp
PARD Periodic and Random Deviation (PARD) = 100 mV peak-peak max.

Overvoltage Protection >30.5 but < 33 Vdc, auto recover
Power Back Immunity < 35 V
Nominal Current 5A (120 W)
Peak Current6 1.5 x Nominal Current at near zero volts at short circuit condition
(Power Boost)
Current Limit Power PowerBoostTM 120W
Parallel Operation Switch selectable single unit or parallel unit operation. Units will not be
damaged by parallel operation (regardless of switch position setting).
Holdup Time > 20 ms (Full load, 100 Vac Input @ T amb = +25o to 95% output
voltage
Tolerance > +2.0% overall
Voltage Fall Time < 150 mS from 95% to 10% rated voltage @ full load
(T amb = +25 oC (+77 oF)
Line and Load Regulation < 0.5%
Time and Temperature Drift <1.0%
Connections - use only one copper wire per terminal for input and output.
Input Screw terminal, connector size range: 16 - 10 AWG (1.5 - 6 mm2) for
solid conductors
Wire Strip length 7.5 - 8 mm
Screw torque (Min./Max.) 4.4 lb-inch (~ 50 N-cm) to 7 lb-inch (~ 80 N-cm)
Output Two terminals per output, connector size range: 16 - 10 AWG (1.5 - 6
mm2) for solid conductors
Environment
Storage temperature -40o C to +85o C (-40o F to + 185o F)
28 OW360_50
Operating temperature -25o C to +60o C (-13o F + 140o F) to full power, with linear derating
to half power from +60o C to +70o C (+140o F to +158o F) (Convection
cooling, no forced air required). Operation up to 50% load permissible
with sideways or front side up mounting orientation.
Derate 120 W by 6 W per oC to 120 W from +60o C to +70o C

1 Not UL listed for DC input.
2 Input current ratings are conservatively specified with low input, worst case efficiency, and power
factor.
3 Losses are heat dissipation in watts at full load, nominal input line.
4 24-28 Vdc adjustable guaranteed at full load.
5 Ripple/noise is stated as typical values when measured with a 20 MHz bandwidth scope and 50 Ohm
resistor.
6 Peak current is calculated at 24 Volt levels.
2.5.2 OCC power supply LED status conditions
The diagnostic LEDs on the front of the power supply are defined in the following table.
Power supply diagnostic LEDs
AC POWER AC HIGH HOT TOO

LEDS NORMAL LOSS INPUT NO LOAD OVERLOAD HOT
LOW DC
Input Green -- Yellow Green Green Green Green Green

Output Green -- Green -- Yellow Yellow Green --
Alarm -- -- -- Red Yellow Red Yellow Yellow
OW360_50 29
2.6 Hardware installation guidelines and best practices
2.6 Hardw are installation guidelines and best practices
Power Wiring
1. Use 14AWG for all power wiring.
2. The power terminal connections (24A, 24B, AX+, AX-, EX+, EX-) on the Controller bases and
I/O bases are 5A rated.
3. Main power wiring can be installed in one of the following ways:
a) May be daisy chained between bases. This includes 24A, 24B, and COM. For
consistency, the top row of the power connector should be used for incoming power, and
the bottom row should be used for outgoing power.
OR
b) May be radially wired from the power source to the bases. This includes 24A, 24B,
and COM. For consistency, the top row of the power connector should be used for
incoming power. The power source may be directly connected to the I/O bases by
individual radial feeds to the respective bases.
Note: At least one 14AWG COM wire must be connected between all bases on a branch to
ensure a good ground reference between base assemblies regardless of whether or not power
daisy chaining is used.
4. Aux power wiring can be installed in one of the following ways:

a) May be daisy chained between bases. This includes AX+ and AX- and EX+ and EX-.
For consistency, the top row of the power connector should be used for incoming
power, and the bottom row should be used for outgoing power. The following
considerations apply:
➢ The Controller base has provisions to interface AUX power, incoming on the top row
and outgoing on the bottom row. This is for convenience only. Aux power is not used
by the Controller base, and it is not required to be distributed through the Controller
base. Alternatively, the AUX power may be radially wired from the power source to
the respective I/O bases.
➢ If the standard Ovation 24V power supply is utilized to provide the Ovation Aux
power and is daisy chained to downstream bases on any given branch: The first
I/O base (two-slot or four-slot) should receive incoming Aux power on the AX+ and
AX- terminals on the top row and distribute to a downstream base from EX+ and EX-
on the bottom row. *Important: All downstream bases to which Aux power is daisy
chained from an upstream base on the branch will interface incoming Aux power to
EX+ and EX– on the top row and distribute to further downstream bases (if needed)
through the EX+ and EX- on the bottom row. This permits the branch to be fused only
at the first base.
30 OW360_50
➢ If the standard 24V Ovation power supply is not utilized to provide the Ovation
Aux Power on any given branch: The I/O base (two-slot or four-slot) should
receive incoming Aux power on the EX+ and EX– on the top row in a daisy chain
configuration. External fusing (5 amp, fast acting, 250v) must be provided on the
externally sourced Aux power feed prior to landing to the top row EX+ terminal block
of the first I/O base. If it is necessary to daisy chain to downstream bases, the bottom
row EX+ and EX- terminals will connect to the top row EX+ and EX- terminals on the
downstream base assembly and distribute to further downstream bases (if needed)
through the EX+ and EX- connections on the bottom row. Additionally, external fusing
(5 amp, fast acting, 250v) must be provided for this externally sourced Aux power
feed into the top row of the first I/O base in the daisy-chain.
b) May be radially wired form the power source or distribution blocks to each of the
respective I/O bases.
➢ If the standard Ovation 24V power supply is utilized to provide the Ovation Aux
Power and is not daisy chained to downstream bases on any given branch: The
respective I/O bases (two-slot or four-slot) should receive incoming Aux power on the
AX+ and AX- terminals on the top row. This is a radial power configuration in which
the power source may be directly connected to the I/O bases by individual radial
feeds to the respective bases.
➢ If the standard 24V Ovation power supply is not utilized to provide the Ovation
Aux Power on any given branch: The I/O base (two-slot or four-slot) should
receive incoming Aux power on the EX+ and EX– on the top row in a radial
configuration. External fusing (5 amp, fast acting, 250v) must be provided on the
externally sourced Aux power feed prior to landing to the top row EX+ terminal block
for all base assemblies in the radial configuration.
5. Earth Grounding: All bases provide a grounding wire. This must be attached to a grounded
metal plate to which the bases are mounted.
Base Combinations
1. A branch consists of up to eight I/O modules.
2. Each Ovation Compact Controller base provides three independent I/O bus connections for
up to three branches.
3. A maximum branch configuration can consist of one of the following base combinations of
two-slot and four-slot bases:
 4, 4
 4, 2, 2
 2, 4, 2
 2, 2, 4
 2, 2, 2, 2
4. For each branch, the I/O bus originates from the Controller base. It is then routed to an
incoming (left most) I/O bus connector of the first I/O base on the branch. The outgoing (right
most) connector then distributes the I/O bus to the incoming (left most) connector on the next
downstream base.
5. The last base on the branch must provide I/O bus termination. To facilitate this, a terminator
selector switch is located on the I/O base. For the last base on the branch, the switch must be
in the “on” position. For all others, it must be in the “off” position.
6. The total I/O bus cable length for a branch must not exceed 10 meters.
OW360_50 31
Cabinet and Environmental Guidelines

1. A suitably rated (NEMA/IP) enclosure should be specified depending on the environmental
conditions.
2. A light-colored enclosure (preferably white or light gray) should be used when placed
outdoors to reduce solar energy absorption.
3. A solar shield should be used if the enclosure if subjected to direct or indirect (reflected)
sunlight.
4. An internal circulatory fan assembly (Emerson part number 5X00805) must be used if a
sealed enclosure is required. The fan should be positioned as close as possible to the top of
the enclosure with the airflow directed towards the electronics. The internal power dissipation
was baselined at 125W inside a typical small Compact Controller enclosure. Larger cabinets
with more internal power dissipation may require an additional internal fan to maintain proper
internal air circulation.
Note: Most extreme conditions may warrant additional heating or cooling devices located within
the cabinet assembly to be determined on a project basis.
5. Ovation Compact Controller bases and I/O bases (two-slot and four-slot) are designed to be
utilized in a horizontal mounted position. Ensure that there is adequate spacing located
between I/O bases to permit adequate horizontal cable routing to the field termination
connections.
The Ovation Compact Controller was tested and characterized for -20 to 70 degrees C
operation specified directly outside the Compact Controller electronics assembly case. In
addition, common Ovation I/O module styles were also tested and characterized when
installed in the horizontal I/O carriers for -20 to 70 degrees C directly outside the respective
module assembly case. This baseline was conducted within a typical small Compact
Controller cabinet (6.25 ft3) with a 125W internal power dissipation. More extreme
environmental conditions and additional power dissipation may need further consideration
regarding internal fans and may warrant additional environmental devices to be determined
on a project basis.
6. Note that the application must allow for internal temperature rise from the outside cabinet
ambient. This is based on the internal fans, power, and overall cabinet size.
32 OW360_50
2.7 Using the Ovation Compact Controller in a Wide Area Network (WAN)
2.7 Using the Ovation Compact Controller in a Wide Area Netw ork
(W AN)
In addition to standard Ovation local area network connections, the Ovation Compact Controller
can communicate through a Wide Area Network (WAN). This allows an OCC to be placed in an
area that cannot easily access an Ovation network. The Compact Controller communicates
securely through an internet protocol (IP) connection over a wide variety of wired and wireless
media options. Process control continues even if the connection to the host system is lost. When
paired with an Ovation remote station, the Ovation Compact Controller can operate as a
standalone control system.
Some environments that benefit from WAN communications include, but are not limited to:
 Pumping stations
 Remote solar sites
 Small, remote hydro sites
The method for connecting to a WAN depends on the type of networking infrastructure you have
and the options you have for connecting to it. Wide area networks can be private, public, or semi-
public. For private WANs, many businesses use dedicated telecommunication leased lines such
as a T-1 or OC-3 channel. Businesses may lease private telecom "pipes" to each site they want to
connect. A business pays a fixed monthly fee for a minimum guaranteed bandwidth from the
telecommunications provider. The bandwidth is based on connection type and distance. Emerson
recommends that the bandwidth provides at least 512 Kbits per second to each site. This
recommendation is for normal plant operations. Performing backups and patching usually
requires more bandwidth.
For businesses that have an existing transmission infrastructure in place, Emerson connects to
the infrastructure by way of a router and creates an encrypted "tunnel" between the sites,
providing a level of security that is essential for connections. A separate, secured tunnel extends
from one router to the cloud and then from the cloud to another router at the other site. Each VPN
router can communicate securely with all other VPN routers. Multiple secured tunnels extend from
each site to all other sites.
When planning your Ovation WAN network, consider the following:

 IP addressing - the OCC must be configured on a different subnet from the main Ovation
network.
 Type of service agreement from your telecommunications provider since bandwidth
considerations are important.
 Number remote locations and how you plan to connect to them.
 Network infrastructure used. Knowing whether your network utilizes Layer 2, Layer 3, or
Multiprotocol Label Switching (MPLS) determines how the routers and network will be
configured.
For more information on Ovation over WAN, refer to the Ovation over WAN Reference Manual.
OW360_50 33
2.8 Minimum software requirements for Ovation Compact Controller
2.8 Minimum softw are requirements for Ovation Compact Controller

The Ovation Compact Controller has the following minimum software requirements:
 Ovation 3.6.0 Feature Pack 4 or later.
To use the Ovation Compact Controller with the Embedded Ethernet Link protocols or with an
Ethernet Link Controller module, you must obtain the Communication Protocol Software Version
1.5 for use on Ovation ELC and OCC Controllers disk and load it on the Database Server (see
page 85).
2.9 What licensing is required for the Ovation Compact Controller?

The Ovation system uses licensing to grant permission to enable certain software applications
and processes. Licenses are stored on a License Server and are accessed through the Ovation
Developer Studio. Since the Ovation Developer Studio can be customized to meet the needs of
large or small systems, licensing allows the ability to easily scale the size of a system or
Controller to accommodate the needs of small and large systems and to provide for growth over
time.
The Ovation Compact Controller utilizes a tiered license system based on the number of I/O
points originated by each Controller and whether the Controller is configured as a simplex (non-
redundant) or a redundant OCC unit. I/O points are classified as hardware points and datalink
points. There are six different license types for the OCC. The following table discusses the I/O
point limits and redundancy configuration.
OCC Licensing Tier
TIER OCC TYPE
Simplex Redundant
Tier 1 Limit of 100 I/O points Limit of 100 I/O points

Tier 2 Limit of 250 I/O points Limit of 250 I/O points
Tier 3 Unlimited I/O points Unlimited I/O points
Note: A Controller can have a maximum of 10,000 total points. Total points includes I/O
points (hardware and datalink points), user-defined points, Control Builder-generated
points, and received points.
Note: To verify that you have not exceeded the I/O point limit for a tier, run a consistency check
on the newly added OCC. If you exceed the I/O point limit for a tier, a warning or error message
appears. Refer to Ovation Developer Studio User Guide for information on consistency checks.
In addition to the tier licenses, if you choose to use the Ovation Compact Controller with the
Embedded Ethernet Link protocols, you must license each protocol installed on the Ovation
system. If you have a simplex (non-redundant) OCC running DNP and redundant OCCs running
Modbus protocols, you must purchase one DNP license and two Modbus licenses.
Protocol licenses are installed on the Database Server using the License Manager. The License
Manager is accessed from the Ovation Developer Studio and allows you to add protocols defined
by a license key. The key defines how many protocols of each type are allowed in the system.
34 OW360_50
2.9 What licensing is required for the Ovation Compact Controller?
The Protocol Configuration Tool and the Protocol Analyzer Tool do not require a license to
operate. When the Protocol Configuration Tool starts, the system submits a license query call to
determine the number and type of protocols available. You are prevented from configuring a
protocol that is not licensed. The database configuration is rechecked before each RTU is
inserted.
To obtain a license key, access the License Manager on the Developer Studio and record the
locking code. Then, contact your Emerson representative during normal work hours (8 am to 4
pm Eastern local time). Depending on your situation, this contact might be your project engineer,
after-market representative, or Field Service engineer. Contact Emerson prior to any installation
or upgrade to ensure the availability of required key codes or licenses. Once the license key is
obtained, enter it into the License Manager. Refer to the Ovation Developer Studio User Guide
for information on the License Manager.
OW360_50 35
S E C T I O N 3
3 Defining system addresses for the Ovation Compact

Controller
IN THIS SECTION
What is an Ovation I/O module address? ......................................................................... 37

Determining the Internet Protocol (IP) address of an Ovation Compact Controller .......... 39
Determining the Network Ethers address (MAC address) ................................................ 39
3.1 What is an Ovation I/O module address?

The Ovation System assigns an address to each Ovation module defined by the Ovation
Developer Studio. This address is based on the logical location of the module with respect to the
Ovation Compact Controller and is used by the Ovation Developer Studio to configure the
hardware information for a point.
The I/O address for local I/O is composed of three numbers, separated by decimals, in the
following format:
 D. B. S. where:
D = Device number assigned to the OCC.
B = Branch (1 through 3)
S = Slot where module is located (1 through 8)
For standard Ovation Controllers (OCR400 and OCR1100), the addressing is determined from
the positions of the bases installed in the cabinets. However, Ovation Compact Controllers are
designed to be placed in non-traditional locations and may not be placed in a cabinet.
OW360_50 37
3.1 What is an Ovation I/O module address?
Regardless of where you place the OCC, the method for determining logical I/O addresses
remains the same. First, you must determine the amount of I/O that you need based on your
control applications. The base configurations you select are largely dependent on the physical
space you have to work with in a defined area. The OCC supports a two-slot and a four-slot base.
These bases can be cascaded to provide a full complement of up to eight I/O modules per
branch. The OCC base supports three local I/O branches. Therefore, with eight modules per
branch, and a maximum of three branches, you can have up to 24 modules per OCC. The
cascade can consist of the following base configurations:
 Four two-slot bases.
 Two four-slot bases.
 One four-slot base and two two-slot bases.
Based on the various branch configurations and the method for assigning I/O addresses, the
following figure shows an example of how modules would be addressed:
Figure 8: Example of module addressing for the Ovation Compact Controller
From the example above, if you use the D.B.S. format and assume these three branches of I/O
are used and assigned to Device number 1, the addresses of modules, A, B, and C would be:
 Module A = 1.1.7
 Module B = 1.2.4
 Module C = 1.3.5
38 OW360_50
3.2 Determining the Internet Protocol (IP) address of an Ovation Compact Controller
3.2 Determining the Internet Protocol (IP) address of an Ovation

Compact Controller
An IP (Internet Protocol) address is a unique number consisting of four parts separated by dots,
(for example, 129.228.36.38). Every computer that is on the network has a unique IP address.
You must determine and record the IP address that is to be assigned to the Ovation Compact
Controller. These numbers are needed when inserting a new OCC drop in the Developer Studio
(see page 44).
The system administrator typically assigns these addresses. The addresses can also be assigned
to be any valid range if the network is isolated from any other networks, such as the Internet.
Note: If you plan to use OCC with a wide area network, make sure that the OCC's IP address is
on a different subnet from the main Ovation network.
3.3 Determining the Netw ork Ethers address (MAC address)

The Network Interface Card (NIC) provides the hardware interface between a computer and a
network. The NIC card has an address that allows it to be identified to the rest of the Ovation
system. The Network Ethers Address (also referred to as the Media Access Control (MAC)
address) is an address used by network interfaces to uniquely identify themselves on a network.
Note: The Ovation Compact Controller supports a dual attached network configuration utilizing
the onboard NIC ports.
The Network Ethers address is needed when you add a new OCC drop to the Developer Studio.
There are two ways to find the address:
 Determine the Network Ethers address from a label on the base (see page 40).
 Determine the Network Ethers address from the Ovation Error Log application (see page 40).
OW360_50 39
3.3 Determining the Network Ethers address (MAC address)
3.3.1 To determine the Network Ethers address from the label
Remove the blue Ovation caps from the OCC base to reveal a chip with a QR code and a partial
Network Ethers address number. Refer to the following figure.
Note: The first six numbers are 00:40:03. These numbers are not shown on the label.
Figure 9: Ovation Compact Controller base showing location of Network Ethers Address
label
The numbers shown on the label represent the unique Network Ethers address for your OCC.
Record the number on the label. You will need it when you add a new OCC to the Ovation
Developer Studio. Repeat this procedure for redundant OCC modules.
40 OW360_50
3.3 Determining the Network Ethers address (MAC address)
3.3.2 To determine the Network Ethers address from the Ovation Error Log
application
1. Unlatch the blue corner latches on the OCC Electronics module case.
2. Pull the module out of the base.
3. Put the module back in the base and secure the latches. The OCC reboots.
4. Ensure that the Power Supply is ON.
5. The P LED on the OCC Electronics module lights steadily.
6. To view the hardware addresses, access at the Ovation Error Log on the Database Server by
selecting Start > Ovation > Error Log.
7. Begin with the bottom of the list (most recent entries) and scroll backwards until you locate
the following message:
Hardware Address not found 00:40:03:xx:xx:xx.
Note: If more than one Compact Controller is turned on, the addresses display in the order that
the Controllers are turned on.
8. Record the address that appears in the message. You will need it when you add a new OCC
to the Ovation Developer Studio.
9. Repeat Steps 1 through 8 if you have redundant modules.
OW360_50 41
S E C T I O N 4
4 Adding and configuring an Ovation Compact

Controller
IN THIS SECTION
Overview of adding an Ovation Compact Controller drop to the Developer Studio .......... 43
Accessing the Ovation Developer Studio .......................................................................... 44
To insert a new OCC drop in the Ovation Developer Studio ............................................ 44
To create a drop point for the OCC ................................................................................... 49
To set Controller parameters for the OCC ........................................................................ 52
To configure default control tasks ..................................................................................... 55
To insert a new control task for the OCC .......................................................................... 56
To confirm the Controller Networking settings .................................................................. 58
To modify Controller Networking settings for the OCC drop only ..................................... 61
Custom Controller Networking .......................................................................................... 61
What additional software configurations are needed for Ovation Compact Controllers? . 62
Download, reboot, and load the OCC ............................................................................... 70
4.1 Overview of adding an Ovation Compact Controller drop to the

Developer Studio
The following steps provide an overview of adding a new OCC drop to an Ovation system. Refer
to the specific topics for detailed instructions.
1. Determine the IP address of the OCC (see page 39).

2. Determine the Network Ethers address of the OCC (see page 39).
3. Access the Ovation Developer Studio (see page 44).
4. Insert a new OCC drop in the Developer Studio (see page 44).
5. Create a drop (DU) point (see page 49).
6. Set Controller parameters (see page 52).
7. Configure default control tasks (see page 55).
8. Insert a new control task (if desired) (see page 56).
9. Confirm Controller Networking settings (see page 58).
Note: In addition to adding a new Controller drop to the Developer Studio, there are other
configuration settings for the OCC. See What additional software configurations are needed for
Ovation Compact Controllers? (see page 62) for additional configuration requirements.
OW360_50 43
4.2 Accessing the Ovation Developer Studio
4.2 Accessing the Ovation Developer Studio

When the Ovation system is loaded, the Developer Studio icon appears on the desktop. Double-
click the icon to access the Developer Studio. For more information, refer to the Ovation
Developer Studio User Guide.
You can also access the Developer Studio from the context menu of the Operator Station
applications, such as Point Information. For more information, refer to the Ovation Operator
Station User Guide.
Note: Much of the setup and configuration of the Developer Studio contents and hierarchy is
typically performed by an Emerson representative before the system is installed.
4.3 To insert a new OCC drop in the Ovation Developer Studio

2. Use the system tree to navigate to the Drops item:
Systems > Networks > Units > Drops
3. Right-click Drops and select Insert New from the pop-up menu.
Figure 10: Developer Studio system tree showing Drops node
4. The Insert New Drops Wizard appears. Enter the following information:
a) Enter a new drop number in the Drop ID field.
b) Enter the partner (drop) ID (if configuring a redundant Compact Controller).
c) Select Compact Controller from the Drop Type drop-down list.
d) Click Finish.
Figure 11: Insert New [Drops] Wizard with Compact Controller selected on Drop Type menu
44 OW360_50
Note: You can use the OCC to run advanced algorithms if you have the APC Toolkit. However,
set the drop type to OCC and not Advanced Controller.
5. The New Drops dialog box appears showing the Config tab. Notice that certain fields are
already prefilled based on your selections in the Insert New Drops Wizard.
Figure 12: New [Drops] window for Compact Controller
OW360_50 45
6. Complete the entries in the New Drops dialog box for the fields that are not grayed out. See
the following table for descriptions.
New Drops dialog box descriptions
FIELD DESCRIPTION
Drop Type Lists the drop type. Compact Controller appears in the field.
Controller Type Shows the type of Controller selected. OCC100 appears in the field.
License Tier Determines the type of licensing (see page 34). The choices are:
▪ Tier 1
▪ Tier 2
▪ Tier 3
Maximum Point Selects the maximum number of points that the Controller can be configured to
Limit monitor.
Ovation Compact Controllers can handle up to 10,000 points.
Fast DDB Mode Selects the mode/speed for the fast broadcast rate of point values to the rest of the
Ovation system.
▪ Normal – Fast broadcast rate for points is set to 100 milliseconds.
▪ Faster – Fast broadcast rate for points is set to 40 milliseconds.
Note: The higher speed gives a higher resolution that can be used for higher speed
received points between Controllers.
Radius Server Provides user authentication and authorization. This field is grayed out for all
Controller types.
Refer to the Managing Security for Ovation User Guide for more information.
Ovation Network Displays the IP address that is shared by the Controller pair. This field is currently
Shared IP Address only required for Ethernet Remote Interface configurations where the Controller is
configured for the Network Connectivity field as "Direct" and the name of the
physical port to which the remote Ethernet cable is connected is specified in the
Network Port field.
Note: The Controller that is in control responds to this IP address.
Primary
Drop ID Drop number of the originating drop of the point.

(1-254)
Ovation Network IP IP address consists of four groups of decimal numbers and the format is:
Address
xxx.xxx.xxx.xxx
The System Administrator typically assigns these addresses.
Ovation Network Displays the address used by the Database Server to boot the Ovation Controller
Ethers Address when the Controller has a blank or newly formatted compact flash card.
The format for the hardware address is:
00:40:03:xx:xx:xx (where the last four numbers (xx:xx) are typically located on a
label on the NIC).
If the hardware address cannot be located on the NIC, see Determining the Network
Ethers address (see page 39).
46 OW360_50
FIELD DESCRIPTION
Ovation Highway Ethernet interface that connects the Controller to the Ovation Network.
Interface
(Automatically selected)
(Znyx, Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)
NIC Interface Automatically selected by the system. Name of the physical port that the Ethernet
cable connects to.
▪ E2 - Used for simplex (non-redundant) OCCs. Always used as the primary
connection for Ovation in redundant configurations.
Ovation Highway Displays speed in (Mbps megabits per second) at which the Controller connects to
Interface Mode the network.
▪ 100 Mbps / full duplex
▪ 1 Gb / auto-negotiate
Backup NIC Automatically selected by the system.
Interface ▪ E1 - Used as a redundant Ovation connection or for a third-party Ethernet protocol
(Available if a (for example, Modbus).
backup NIC is
used.)
Control The OCC software implicitly supports Control Synchronization for redundant OCCs.
Synchronization For OCCs, this is not a user configurable parameter.
Interface ▪ LVDS
Control Parameter generated by the system. This is not user configurable.
Synchronization
Interface Mode
Control Automatically selected by the system. This hard-coded address is used to
Synchronization communicate with the partner OCC. This parameter is not user configurable.
Interface IP
Address
Partner - The Primary fields are repeated if a Partner OCC is used. The field descriptions are the same as
for the Primary OCC, but the entries apply to the partner Controller.
Ethernet Remote Interface - The following fields are used for the type of Ethernet Remote Interface you
select. Since the OCC does not support Numalogic, These fields apply to the Ovation Remote Node
Interface (RNI). Refer to Remote Node Interface User Guide for more information.
Redundancy Mode Configures the Redundancy Mode to be used for the Ethernet Remote Interface.
The available options are:
▪ Legacy (used for a Direct network connection, which means that each half of the
Ovation Controller communicates with only one half of the redundant remote node.
This mode is used in network topologies that prevent Controllers from
communicating with both the Primary and Partner halves of a node.)
▪ Standard (used for a Dedicated network connection and an Across the Network
connection. This means that the Controller continuously communicates with all
Remote Node Interfaces.)
OW360_50 47
FIELD DESCRIPTION
Network Defines the Network connectivity for the Ethernet Remote Interface. The available
Connectivity options are:
▪ Direct (used with a Dedicated network connection, which requires at least pair of
Ethernet switches to aggregate the Ethernet I/O nodes.)
▪ Ovation Network (used with an Across the Network connection, which uses a
routers in addition to switches.)
Note: If you Legacy for the Redundancy Mode parameter, the Network
Connectivity is set to Direct by default and cannot be changed.
Remote Node Type Defines the type of Ovation Node. The available options are:
▪ Numalogic (not used for Compact Controllers.)
▪ Ovation (used for Remote Node Interface and Ovation I/O)
Note: If you select Standard for the Redundancy Mode parameter, the Remote
Node Type is set to Ovation by default and and cannot be changed..
Network Port Defines the OCC port that is used to communicate with the Ethernet Remote
Interface.
▪ If Network Connectivity is set to Direct, this must be set to E1.
▪ If Network Connectivity is set to Ovation Network, this must be blank.
IP Address Displays the IP Address of the primary drop’s interface to the Ethernet Remote
Interface (for the selected network port).
IP Address Displays the IP Address of the partner drop’s interface to the Ethernet Remote
(Partner) Interface (for the selected network port).
IP Address Displays the shared IP Address of the OCC drop’s interface to the Ethernet Remote
(Shared) Interface (for the selected network port). This is applicable only if the Controller is
configured for the Network Connectivity field as Direct and the Redundancy Mode
field is specified as Standard.
DHCP Enabled Generated by the system. This field is enabled only if you set the Remote Node
Type to Numalogic. Compact Controllers do not support Numalogic.
Ethernet Remote Displays the Gateway IP Address that is used for all the Ovation Ethernet nodes.
Node Gateway IP This is applicable only if the Controller is configured for the Network Connectivity
Address field as Ovation.
Subnet Mask Generated by the system and set to 255.255.255.0.
Interface Mode Displays the speed and duplexity of the selected Ethernet interface for the primary
(Primary Drop) Controller.
▪ 10 Mbps / half duplex
▪ Auto-negotiate
48 OW360_50
FIELD DESCRIPTION
Interface Mode Displays the speed and duplexity of the selected Ethernet interface for the partner
(Partner Drop) Controller.
▪ Auto-negotiate
Note: This is a read-only field that mirrors the configuration of the primary drop.
WAN Client Data
Point Count Maximum number of points that a drop can receive at one time from all of the
remote subnets in the WAN. Must be greater than zero (0). Default = 2048.
Refresh Period Amount of time (in seconds) between data requests that are sent to the WAN data
server (typically, the OCC). If an application is requesting data, refresh messages
are sent from the client application to the WAN server. If a WAN server does not
receive a request for data for 15 seconds, it stops sending updates for the data.
Must be less than 15. Default = 8.
Data Lifetime Amount of time (in seconds) that a piece of data will be held in memory after the last
request for this data from an application. After the defined amount of time expires
without an application reading, the data is purged.
Must be greater than zero (0). Default = 15.
WAN Server Data
Update Period Determines how often the WAN server can send out updates of the dynamic data.
Number of Clients Maximum number of clients that the WAN server can communicate with at one time.
Valid range is 1 to 256.
Maximum Number Maximum number of points per client that the WAN server can return the dynamic
of Points per Client. data for at one time. The WAN server maintains up to this maximum number of
points for each client that it is servicing.
7. Click the Apply button to save these settings without closing the window, or click the OK
button to save the settings and close the window.
8. A new <DROP#> item appears under the Drops item of the Developer Studio system tree.
Note: After the addition of an Ovation Controller drop (or drops), you must query download all
drops on the network (see page 70).
OW360_50 49
4.4 To create a drop point for the OCC
Note: You must repeat this procedure for the partner OCC in a redundant configuration.
1. Access the Developer Studio (see page 44).

2. Use the system tree to navigate to the Drop Point item:
Systems > Networks > Units > Drops > Points > Drop Point
3. Right-click Drop Point and select Insert New from the pop-up menu.
Figure 13: Developer Studio system tree showing Drop Point node
4. The Insert New Drop Point Wizard appears. Enter the following information:
a) Define a name for the drop point in the Point Name field (the name must be the word
Drop immediately followed by the drop number(s) as defined in To Insert a new OCC
drop (see page 44)).
b) Select the appropriate drop number to correspond with the Point Name entry.
c) Click Finish.
Figure 14: Insert New Drop Point Wizard
50 OW360_50
5. The New Drop Point dialog box appears containing default values for certain attributes. Tab
through the New Drop Point dialog box and complete any desired changes to the default field
values for the Point, Security, Ancillary, Alarm, and Display tabs. When you are finished, click
Ok to save the changes and close the window. Repeat this procedure for a partner Controller.
Figure 15: New Drop Point dialog box
The following table lists and describes the New Drop Point dialog box tabs and fields.
New Drop Point dialog box descriptions
TAB FIELD DESCRIPTION
Point Point Alias Sixteen-character alias for the point name.

Description Maps directly to the ED field of the point record and can be up to 50
characters.
Characteristics Maps directly to the KR field of the point record, with the first
character mapping directly to the AY field (destination) of the point
record.
Up to eight alphanumeric characters can be used.
Drop Number Drop number of the originating drop of the point (or partner). Valid
entries are 1-254.
Partner Drop Identifies the drop number of the drop or of the partner drop.
Security Security Group Represents the defined security groups for each point in the
system.
Note: At least one Security Group must be entered to allow Point

modification. Refer to the Managing Security for Ovation manual
for more information on security groups.
Ancillary Attribute Value Provides additional user-defined information about the points.
OW360_50 51
4.5 To set Controller parameters for the OCC
TAB FIELD DESCRIPTION
Alarm Alarm Priority Sets the various alarm priority fields (1-8).
Alarm Annunciator This text identifies the point that is in alarm, the alarm message
Text boxes in the Alarm Annunciator alarm bands display two lines of
(only appropriate if text (up to 12 characters per line), for a total of 24 characters.
Alarm Annunciator You can separate the two lines of text by using a vertical bar ("|")
is used) as a line delimiter, this bar does not count toward the 12 characters
in the line.
For example, if you enter FD FAN AA|AIR FLOW, it
appears in the alarm message box as:
FD FAN AA
AIR FLOW
If you do not use the line delimiter, the first 12 characters are used
for line one and any additional characters are used for line two.
Alarm Description A text description of the alarm (maximum string of 45 characters.)
Alarm Guidance This field has five Alarm Guidance fields, which can accommodate
80 bytes per field, contain the alarm guidance information. In these
fields, you can provide a description of possible corrective actions
or causes of the situation. These fields are optional and can be left
blank.
Display Summary Diagram Defines the applicable summary diagram that is sent to the
Graphics Display System.
Signal Diagram Defines the signal diagram number.

2. Use the system tree to navigate to the Controller item:
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller
3. Right-click Controller and select Open from the pop-up menu.
Figure 16: Developer Studio system tree showing Controller folder selected
52 OW360_50
4. The Controller dialog box appears showing the Controller Parameters tab. Make any desired
changes to the default field values. When you are finished, click Ok to save the changes and
close the window.
Figure 17: Controller dialog box — Controller Parameters tab for OCC
The following table lists and describes the Controller dialog box tabs and fields.
Controller dialog box (Controller Parameters tab) descriptions
FIELD DESCRIPTION
System Memory System selects the size of the Controller configuration including RAM and Flash. For
the OCC, the system sets this to Expanded.
Send Messages To Selects Workstation drop where Controller messages (error and informational) are
sent.
Default = None
Security Logger Identifies the Ovation workstation where the Controller sends security-related log
messages. The field displays a list of Ovation workstations and an additional entry
named “External Logger.” If you select “External Logger,” an additional field
appears where you enter an IP address.
SOE Logger 1 Selects the first Scanner Workstation drop where SOE messages are sent. (Refer to
the applicable Ovation Process Historian User Guide.) This field is not applicable if
the system does not include a Sequence of Events I/O module.
Default = None
SOE Logger 2 Selects the second Scanner Workstation drop where SOE messages are sent.
(Refer to the applicable Ovation Process Historian User Guide.) This field is not
applicable if the system does not include a Sequence of Events I/O module.
Default = None
SOE Logger 3 Selects the third Scanner Workstation drop where SOE messages are sent. It
supports redundant historian scanners. (Refer to the applicable Ovation Process
Historian User Guide.) This field is not applicable if the system does not include a
Sequence of Events I/O module.
Default = None
OW360_50 53
FIELD DESCRIPTION
SOE Logger 4 Selects the Ovation OPC Alarm and Event Server (workstation drop) where the
SOE message is sent. (Refer to the applicable Ovation Process Historian User
Guide.) This field is not applicable if the system does not include a Sequence of
Events I/O module.
Note: The same workstation cannot be used as both the OPC Alarcm and Event
Server (AES) and the OPH SOE scanner for SOE configuration. For more
information on OPC AES, refer to the OPC Tools User Guide.
Triggered Event Selects the first Scanner Workstation drop where Triggered Events are sent. This is
Logger 1 applicable to OCR 1100 Controllers only.
Default = None
Triggered Event Selects the second Scanner Workstation drop where Triggered Events are sent.
Logger 2 This is applicable to OCR 1100 Controllers only. Keep the default value of None for
Ovation Compact Controllers.
Default = None
Save Variables @ Text entry field that indicates the time period (in seconds) that variable point values
Interval (min.) are saved. The saved value is then used as the initial value of the point on restarts.
(Refer to the Ovation Developer Studio User Guide.)
Drop-specific value
TimeKeeper This parameter is not used for Ovation Compact Controllers.
I/O Priority Selection Selects which priority is used, either the VXWorks task priority or the command
priority. Emerson recommends that the I/O priority be configured as task. This
configuration does not allow a slow task, which may have related I/O algorithms, to
cause another task to be starved for processing time.
(Task, Command)
Default = task
Shared Memory Size Select the size of shared memory. Shared memory is used by algorithms and points
(MB) to store internal information.
For OCR 400, the default value is 2MB with a maximum limit of 6MB.
For OCC100 and OCR 1100, the default value is 32 MB.
R3/R4 I/O Connection Allows the selection of the type of I/O to be assigned to connections R3/R4.
(Remote R-Line, Remote Q-Line, Local Q-Line)
Default = Remote R-Line
SIS -- Safety Instrumented System. The Ovation Historian must reside on the system before SIS Loggers can
function. SIS loggers must be configured to enable SIS events functionality.
Use SIS Loggers Used for SIS events functionality. Refer to the SIS User Guide.
SIS Logger 1 IP Displays the IP address of the first SIS Logger, if configured. Must be configured to
Address be active.
SIS Logger 2 IP Displays the IP address of the second SIS Logger, if configured. Must be configured
Address to be active.
54 OW360_50
4.6 To configure default control tasks

Control tasks are areas in a Controller used to designate different scan times for points. The OCC
supports three control tasks. Control Task 1 contains points scanned every 100 milliseconds (0.1
second). Control Task 2 contains points scanned every 1000 milliseconds (1 second). Control
Task 3 is user configurable. When you create a new OCC drop, Task 1 and Task 2 are created
automatically. The following procedure discusses configuring the default control tasks. If you
need more than two control tasks, create a third control task using the procedure in To insert new
control tasks for the OCC (see page 56).

2. Use the system tree to navigate to the Control Tasks item:
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller > Control
> Control Tasks
3. Select Control Tasks and notice that Control Task 1 and Control Task 2 have been created
and are listed in the WorkPad window.
Figure 18: Developer Studio showing Control Task 1 and 2 in the WordPad area
4. Right-click Control Task 1 in the Workpad window and select Open from the pop-up menu.
Figure 19: Control Task 1 opened with right-click menu
OW360_50 55
5. The Control Task dialog box appears showing the Control Task Parameters tab. Complete
any desired changes to the default field values. When you are finished, click Ok to save the
changes and close the window.
Figure 20: Control Task dialog box showing Control Task Parameters tab for OCC
The following table lists and describes the Control Task dialog box parameters.
Control Task dialog box descriptions
FIELD DESCRIPTION
Sheet Set Size Text entry field that indicates the sheet set size in bytes for the selected control
task. For OCCs, the default value is 1048576.
Period (milliseconds) Text entry field that indicates the period in milliseconds that the selected
control task executes.
Note: Control Task 1 and Control Task 2 are not configurable and are by
default 100 milliseconds and 1000 milliseconds, respectively.
I/O Scan Type Parallel - Scan function and control run at the same time. If a large amount of
point information needs to be sent to I/O, Parallel can be used. Even though it
is a faster method, control would be one scan behind.
Serial - Scan function runs, then control, and then sends control to the I/O. If
scan and control fit into one selected time period, then Serial can be used.
Default = Serial
6. Repeat this procedure for Control Task 2 before adding any new control tasks.
56 OW360_50
4.7 To insert a new control task for the OCC
4.7 To insert a new control task for the OCC
Note: Control Tasks 1 and 2 are added to the system automatically when you insert a new OCC
drop. You must configure Control Task 1 and 2 (see page 55) before adding a new control task.

2. Use the system tree to navigate to the Control Tasks item:
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller > Control
> Control Tasks
3. Right-click Control Tasks and select Insert New from the pop-up menu.
4. The Insert New Control Tasks Wizard appears. Change the default field value for the new
Control Task Number to 3. Click Finish.
Figure 21: Insert New Control Tasks Wizard
OW360_50 57
4.8 To confirm the Controller Networking settings
5. The New Control Task dialog box appears. Complete any desired changes to the default field
values. When you are finished, click Ok to save the changes and close the window. (See To
configure default control tasks (see page 55) for a description of each attribute.)
Figure 22: New Control Tasks dialog box
4.8 To confirm the Controller Netw orking settings

Controller Networking parameters specify network routing information for the Ovation network.
The parameters defined in the Controller Networking window are defined at the Network level of
the Developer Studio system tree. Configuration at this level filters down through the rest of the
system. However, changes made at a lower level (Units or Drops) overrides the System
configuration for everything defined in its level and below it. Refer to Ovation Developer Studio
User Guide for more information on system hierarchy and folder structure.
For example, when you add an OCC drop at the Network level, the settings defined for the
Controller Networking object at the Network level are applied to the OCC drop that you added at
the Drops level. By default, a new drop inherits the same values for Controller Net Mask and
Default Router IP Address as the entire network branch into which it has been inserted.
Before performing additional OCC configuration, verify that the defined network values are
satisfactory to the new OCC drop.

2. Use the system tree to navigate to the Controller Networking (Network item):
Systems > Networks > Configuration > Controller Networking
58 OW360_50
3. Select Controller Networking and notice the Controller Networking object listed in the
WorkPad window.
Figure 23: Controller Networking item selected at the Network level in the hierarchy tree
4. Right-click the Controller Networking object in the WorkPad window and select Open from
the pop-up menu.
OW360_50 59
5. The Controller Networking dialog box appears showing the Networking Configuration tab.
Depending on your needs, choose from the following three options: refer to Steps 6, 7, or 8.
Figure 24: Controller Networking dialog box with network settings defined
6. If the Controller Net Mask and Default Router IP Addresses match what is required for the
new OCC drop, click the Cancel button to exit without making changes.
For example, if the new OCC drop is on the main Ovation network, the settings will typically
match since the settings have been defined for the rest of the network. However, if the new
OCC drop is connected over a Wide Area Network or if it has another custom network
requirement, then the settings must be changed for this drop (see Step 7).
7. If you want this OCC drop to have different values than the other drops in the network, click
the Cancel button to exit without making changes. See To modify Controller Networking
settings for the OCC drop only (see page 61).
60 OW360_50
4.9 To modify Controller Networking settings for the OCC drop only
4.9 To modify Controller Netw orking settings for the OCC drop onl y
When the OCC is connected over a WAN, it is important that the Net Mask and Default Router IP
Addresses are set correctly before you start the drop.
If conditions require the OCC drop to have different values than the rest of the drops on the
network, perform the following steps:

2. Use the system tree to navigate to Controller Networking (at the Drop level):
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller
Networking (where DROP# is the drop number of the OCC drop)
3. Select Controller Networking and notice the Controller Networking object listed in the
WorkPad window.
4. Right-click the Controller Networking item in the WorkPad window and select Open from
the pop-up menu. The Controller Networking dialog box appears.
5. Use the following table to complete any desired changes to the default field values.
Partial Controller Networking dialog box descriptions
FIELD DESCRIPTION
Controller Net Mask Typically, the network-assigned value can be used. If your system
is a special case, see your System Administrator.
(Default = 255.255.255.255)
Default Router IP Address Router IP Address for connecting to an external network.

(Default = Blank)
Destination IP/Subnet Address (X) Subnet address or IP address of a device on another network.
Route (X) IP address of the device that routes the packets to the proper
destination.
6. Click the OK button to save the settings and close the window.
4.10 Custom Controller Netw ork ing

Custom Controller networking allows special approved custom applications to operate. Any
custom network application should be approved by Emerson before they can be used on your
system.
OW360_50 61
4.11 What additional software configurations are needed for Ovation Compact Controllers?
4.11 What additional softw are configurations are needed for Ovation
Compact Controllers?
The following list contains additional configuration tasks that you must address to ensure a
complete set up of the Ovation Compact Controller software.
 Add a Module (RM) point for every hardware module you add to the OCC drop (see page 62).
 Add a Node (RN) point for certain items (such as Local Ovation, Foundation Fieldbus,
Profibus, DeviceNet, and Remote Node Interface device types) (see page 65).
 Configure drivers for the device types that you define (see page 69).
 Download, reboot, and load the Ovation Compact Controller (see page 70).
Note: Download, reboot, and load should be done after all configuration settings are complete.
You may also want to check the following configuration settings. See the associated manuals for
item locations and configuration information.
 Network Time Protocol (NTP) item settings. Refer to the Ovation Developer Studio User
Guide.
 DDB Configuration item settings. Refer to the Ovation Developer Studio User Guide.
 Point Processing item settings. Refer to the Ovation Developer Studio User Guide.
 Event Log Configuration item settings. Refer to the applicable Ovation Process Historian User
Guide.
4.11.1 To add Module (RM) points
Each Ovation I/O module associated with a Controller must have a Module point record in the
database. The information in a module point record tells the Controller what to expect from the I/O
module and how to interface with it.
Note: Refer to Ovation Record Types Reference Manual for more information on point types
and record fields.

2. Use the system tree to navigate to the Points folder:
Systems > Networks > Units > Drops > Drop # > Points >Module Points
62 OW360_50
3. Right-click Module Points and select Insert New.
Figure 25: Right-click menu showing Insert New option from Module Points
4. The Insert New Module Points Wizard appears. Perform the following steps:
a) Enter the point name in the Point Name Value field.
b) Select the frequency from the drop-down menu.
➢ S - Slow (1 second).
➢ F - Fast (0.1 second).
➢ A - Aperiodic (as needed).
c) Click Finish.
Figure 26: Insert New Module Points Wizard
OW360_50 63
5. The New Module Point dialog box appears. This dialog box has several tabs that appear at
the bottom of the window. When the dialog box first appears, the Point tab appears by default.
Some tabs may have fields that are grayed out because the system enters the information,
and it cannot be changed. If a required field is left blank, a warning box appears prompting
you to complete the necessary information. Refer to the Ovation Developer Studio User
Guide for information on completing the tabs and fields for a Module point. When finished,
click Apply or Ok.
Figure 27: New Module Point dialog box
6. To assign the Module point to an I/O item, click the Hardware tab at the bottom of the New
Module Points dialog box.
Figure 28: New Module Points dialog box with Hardware tab selected
64 OW360_50
a) Click the IO module drop-down menu and choose the specific I/O module to assign to
the module point.
Figure 29: New Module Points dialog box showing IO module drop-down menu
b) The IO task index represents the processing task index used by the Controller. Points
that are assigned to a digital output module must have an identical task index value for
every point on the same module.
c) Click Ok or Apply.
Note: A point is not available on the Ovation network until it is loaded. If you modify, add, or
delete a point, the Load flag displays on the point originator. Occasionally, the system event that
notifies the Ovation Developer Studio to display its flags may not be detected. Use the Refresh
operation to redisplay the Studio and confirm the flag status.
For more information on Module points, refer to Ovation Record Types Reference Manual and
Ovation Developer Studio User Guide.
4.11.2 Adding Node (RN) points
Nodes points are used to provide diagnostic information for the devices they are assigned to. For
example, Node points can be used to monitor the power supply of the OCC Electronics module.
For an Ovation Compact Controller project, node points are assigned to the following items:
 Local OCC Ovation device type
 Embedded Ethernet Link device type
 Ethernet Remote Nodes
 Foundation Fieldbus devices
 Profibus slaves
 DeviceNet slaves
 Ethernet Link protocols
 Embedded Ethernet Link protocols
OW360_50 65
4.11.3 To insert a Node point

2. Use the system tree to navigate to Node Points:
System > Networks > Units > Drops > Drop# > Points > Node Points
3. Right-click Node Points and select Insert New.
4. The Insert New Node Points wizard appears. Perform the following steps:
a) Enter a point name in the Point Name field.
b) Select a frequency (S = Slow (1 second), F = Fast (0.1 second), or A = As needed).
c) Click Finish.
Figure 30: Insert New Node Points Wizard
5. The New Node Points dialog box appears. This dialog box has several tabs that appear at the
bottom of the window. When the dialog box first appears, the Point tab appears by default.
66 OW360_50
Some tabs may have fields that are grayed out because the system enters the information,
and it cannot be changed. If a required field is left blank, a warning box appears prompting
you to complete the necessary information. Refer to the Ovation Developer Studio User
Guide for information on completing the tabs and fields for a Node point. When finished, click
Apply or Ok.
Figure 31: New Node Points dialog box
6. To assign the Node point to an I/O item, click the Hardware tab at the bottom of the dialog
box.
Figure 32: New Node Points dialog box with Hardware tab selected
OW360_50 67
a) Click the IO module drop-down menu and choose the specific I/O item (module, device,
or protocol) where the point is attached.
Figure 33: New Node Points dialog box showing the IO module drop-down menu
b) The IO task index represents the processing task index used by the Controller. Points
that are assigned to a digital output module must have an identical task index value for
every point on the same module.
c) Click Ok or Apply.
Note: A point is not available on the Ovation network until it is loaded. If you modify, add, or
delete a point, the Load flag displays on the point originator. Occasionally, the system event that
notifies the Ovation Developer Studio to display its flags may not be detected. The Refresh
operation may be used to redisplay and confirm the flag status.
For more information on Node points, refer to Ovation Record Types Reference Manual and
Ovation Developer Studio User Guide.
4.11.4 Node (RN) point assignments for OCC Local Ovation
The following table shows the definition of the status bits for the RN point assigned to monitor the
power supply for the OCC Electronics module:
Status bit definitions for RN point
BIT DEFINITION ALARM ON
0 +24VAOK/ Status of +24VA PS 1

1 +24VBOK/ Status of +24VB PS 1
2 AUX1AOK/ Aux 1 PS A present & ok 1
3 AUX1BOK/ Aux 1 PS B present & ok 1
68 OW360_50
BIT DEFINITION ALARM ON

8 Legacy Redundancy: I/O Communications ok N/A
9 Legacy Redundancy: In control N/A
10 Junction temperature high 1
11 Unused N/A
12 Unused N/A
13 Unused N/A
14 Unused N/A
15 Unused N/A
4.11.5 Defining Controller devices and drivers
A Controller driver is a software program that acts as a translator between a hardware device and
the applications that use the device. Every version of a hardware device, such as a printer,
requires its own specialized commands.
In contrast, most software applications access devices (such as sending a file to a printer) by
using high-level, generic commands. The driver accepts these high-level generic statements and
converts them into the low-level commands required by the device.
To configure the OCC, you must define device numbers, I/O driver types, and device types.
Assign the device number first and then add the I/O driver. Device 1 should be set to an I/O
Driver Type of OCC Ovation. For standard Ovation I/O, the corresponding device type for the
OCC Ovation is OCC Local Ovation.
You can define up to eight device numbers for the Ovation Compact Controller. Only one device
number should be defined for local Ovation I/O, and should be defined as Device 1. Third-party
devices must be added individually with a separate device number, device type, and I/O driver.
Refer to the following sections for adding device types and drivers:
 Configuring OCC for local Ovation I/O (see page 75).
 Configuring OCC to use embedded protocols (see page 85).
 Configuring the OCC to use ELC module (see page 95).
 Configuring the OCC to use the Fieldbus module (see page 107).
 Configuring OCC to use the Profibus module (see page 115).
 Configuring the OCC with the RNI module (Ethernet Remote) (see page 121).
 Configuring the OCC to use the DeviceNet module (see page 131).
 Configuring OCC to use the Machinery Health Monitor module (see page 137).
 Configuring the OCC to use the Digital Excitation Controller module (see page 143).
OW360_50 69
4.12 Download, reboot, and load the OCC
4.12 Dow nload, reboot, and load the OCC

For additions and changes to take effect in the Ovation Compact Controller, you must perform a
Download, Reboot, and Load operation.
Perform a Download function (see page 70) when changes are made to Controller software.
Execute a Reboot function (see page 72) immediately following the completion of any Download
command involving configuration changes. Even though this may not always be necessary, it is a
safe and recommended practice to reboot a drop after it has been downloaded.
Perform a Load function (see page 74) after a drop is rebooted to load control sheets, points, and
holding registers onto the system.
The Ovation system periodically checks for consistency throughout different levels of the system.
One example of a consistency check would be if the system gives you an error message because
you entered an invalid character in a window field. Other consistency checks are run
automatically before you run a Load or a Download function. This is done to preserve the integrity
of the Ovation system.
However, the Developer Studio allows you to manually run a consistency check any time you
make any additions, corrections, or deletions to the system. If you run a consistency check and
errors are detected, a report displays which allows you to correct the errors before performing a
load or a download. Refer to Ovation Developer Studio User Guide for more information on the
Consistency Check function.
4.12.1 To download a Controller drop configuration
Note: Perform the Download command any time configuration and software changes have been
made to a Controller drop.

2. Use the system tree to navigate to the Drops folder:
3. Right-click the appropriate Controller drop item and select Download from the pop-up menu.
Note: Execute the Download function on a System, Network, or Unit item when multiple drops
are to be downloaded. (Refer to the Ovation Developer Studio User Guide.)
70 OW360_50
4. For redundant Controller drop configurations, the Download Wizard appears. Select the drop
you want to download and click Finish.
Figure 34: Download Wizard
5. The Download Preview dialog box appears and lists any files that may have been altered
during drop configuration and software changes. Select the files to be included in the
Download process. The following figure illustrates an example of the files included in the
download process.
Note: You can choose to bypass a Download Preview by configuring it to be disabled. Refer to
the Ovation Developer Studio User Guide for more information.
Figure 35: Download Preview dialog box
OW360_50 71
6. Select the Download option and click the Ok button.
Download preview dialog box descriptions
SELECTION DESCRIPTION
Query Results Selects or deselects all the files in the preview list. This is the check box located at
the top left corner of the dialog box.
Download When this action is checked, a download of all selected previewed files is executed
after pressing the OK button.
Reboot When this action is checked, a reboot is executed on the drop currently selected
after pressing the OK button.
Note: To automatically reboot after completing the Download command, select

both Download and Reboot before clicking Ok.
Abort Cancels the Download Preview and returns you to the Ovation Developer Studio
interface without executing any commands.
Ok Executes the settings and closes the window.
Skip to Next Drop When downloading to System, Network, or Unit items, this button advances to the
next drop for file preview.
7. Reboot the Controller drop (see page 72).

8. Return to the Developer Studio system tree and navigate to the Drops item:
9. Right-click the appropriate Controller and select Load from the pop-up menu (see page 74).
72 OW360_50
4.12.2 To reboot a Controller drop
Note: Reboot immediately following the completion of the Download command. This is a safe
and recommended practice.

3. Right-click the appropriate Controller Drop item and select Reboot from the pop-up menu.
4. For redundant Controller drop configurations, the Reboot Wizard appears. Select the same
Controller drop that was selected for the download.
Figure 36: Reboot Wizard
5. A confirmation dialog box appears. Click Yes to close the window and execute the reboot
process.
Figure 37: Reboot confirmation dialog box
OW360_50 73
4.12.3 To load a Controller drop
The Load function is necessary anytime changes have been made related to points or control. If a
new drop point was inserted, execute the load command immediately following the completion of
the Reboot command (see page 72).
Note: The Load function is required when Controller device drivers that have been configured
with I/O points, are either deleted or changed. This would also require deleting existing points
and executing the Clear command. (Refer to the Ovation Developer Studio User Guide.)

3. Right-click the appropriate Controller Drop and select Load from the pop-up menu.
4. For redundant Controller drop configurations, the Load Wizard appears. Select the drop to
load and click Finish.
Note: Always load the Controller drop that is in control first.
Figure 38: Load Wizard
74 OW360_50
S E C T I O N 5
5 Configuring the OCC to use local Ovation I/O
IN THIS SECTION
Overview of configuring OCC for Local Ovation I/O modules ........................................... 75

To insert a new device number and I/O driver type for local Ovation ............................... 75
To insert the device type for local Ovation ........................................................................ 77
To insert a branch for local Ovation .................................................................................. 80
To insert an I/O module in a branch .................................................................................. 81
5.1 Overview of configuring OCC for Local Ovation I/O modules

The Ovation Compact Controller only supports one local I/O interface. The local I/O interface
supports three branches of local Ovation I/O. The following steps provide an overview of adding
local Ovation device type. Refer to the specific topics for detailed instructions.
1. Insert a new device number, and I/O driver type for local Ovation.
2. Insert the device type for local Ovation (see page 77).
3. Insert a new branch for local Ovation (see page 80).
Note: You can add up to three branches for each OCC. When you add a branch, eight empty
slots are added to the branch.
4. Insert an I/O module (see page 81).

5. Add a module point (see page 62).
6. Add a node point (see page 65).
7. Download, reboot, and load the OCC (see page 70).
5.2 To insert a new device number and I/O driver type for local
Ovation
Note: The OCC only supports one local I/O interface. The OCC local I/O interface supports
three branches of local Ovation I/O.
2. Use the system tree to navigate to the Device Numbers item:

Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller > Devices
> Device Numbers
OW360_50 75
5.2 To insert a new device number and I/O driver type for local Ovation
3. Right-click the Device Numbers item and select Insert New from the pop-up menu.
Figure 39: Right-click menu showing Insert New option
4. The Insert New Device Numbers Wizard appears. Select a number starting at 1 to a
maximum of 8. Enter numbers sequentially. For example, if two devices are to be configured;
their device numbers would be 1 and 2, not 1 and 3, or 1 and 4, or 1 and 5. After you select a
number, click the Finish button.
Note: Typically, device number 1 is used for the OCC Ovation driver type (see Step 5a) and the
Local Ovation device type (see page 77).
Figure 40: Insert New Device Numbers Wizard
76 OW360_50
5.2 To insert a new device number and I/O driver type for local Ovation
5. The New Device Numbers dialog box appears showing the Controller Driver Parameters tab.
Perform the following steps:
a) Select OCC OVATION from the I/O Driver Type drop-down menu.
b) Select OVATION for the Simulator Driver Type drop-down menu.
c) When you select OCC OVATION, the values for Slot Order and Scan Point Entries prefill
from the system. They appear grayed out and cannot be changed.
d) Click Ok to save the changes and exit the window.
OW360_50 77
5.3 To insert the device type for local Ovation

2. Use the system tree to navigate to the I/O Devices item:
Systems > Networks > Units > Drops > DROP# > I/O Devices
3. Right-click the I/O Devices item and select Insert New from the pop-up menu.
Figure 41: I/O Devices folder and right-click menu
4. The Insert New I/O Devices Wizard appears. Make the following selections:
 Select the I/O Device Number that you selected in the Insert New Device Numbers
Wizard. This device number was paired to the OCC Ovation driver type the New Device
Numbers dialog box.
 Select OCC LocalOvation from the I/O Device Type drop-down list.
 Click Finish.
Figure 42: Insert New I/O Devices Wizard
78 OW360_50
5. The New I/O Devices dialog box appears. The dialog box contains the I/O device type and the
I/O device number you selected in the wizard (Step 4).
a) Configure the device by selecting which of the power supplies are to be monitored by the
associated Node record (RN) (see page 65). Select the “1” beside each power supply
you want to monitor. (Refer to the Ovation I/O Reference Manual for information on
power supplies.)
Note: Remember to add and assign a Node point for the OCC LocalOvation device type (see
page 65) before you perform a download, reboot, and load.
Figure 43: New I/O Devices dialog box
The following table lists and describes the New I/O Devices dialog box fields.
New I/O Devices dialog box - OCC LocalOvation device type field descriptions
FIELD DESCRIPTION
I/O Device Number Defined in the Insert New I/O Devices Wizard (see Step 4).
I/O Device Type Defined in the Insert New I/O Devices Wizard (see Step 4).
Node Record Point Name Name assigned to the node point (see page 65). The node
point is used to monitor the power supply status of the OCC
Electronics module.
24 Volt Primary (and Secondary) Supply Select the Power Supply used (0 - not used, 1 - used).
Auxiliary (1-3) Primary Power Supply Select the Power Supply used (0 - not used, 1 - used).
Auxiliary (1-3) Secondary Power Supply Select the Power Supply used (0 - not used, 1 - used).
Junction Temperature Point Specifies the analog point that reports the internal
temperature of the OCC.
OW360_50 79
5.4 To insert a branch for local Ovation
b) When you are finished, click Ok to save the changes and close the New I/O Devices
dialog box. The new OCC LocalOvation item appears in the system tree.
Figure 44: I/O Device 1 OCC LocalOvation item in Studio tree

When you select Local Ovation as the device type, the Branch item is established by default in
the Developer Studio system tree.

2. Use the system tree to navigate to the Branch item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # OCC Local Ovation >
Branch
3. Right-click the Branch item and select Insert New.
Figure 45: Insert a new branch for OCC LocalOvation device
80 OW360_50
4. The Insert New Branch Wizard appears.

a) Select the Branch Number in the Value column. Up to three branches can be defined for
the OCC.
b) Click Finish.
Figure 46: Insert New Branch Wizard
5. The New Branch dialog box appears. The Branch Number and Branch Type (OCC100 Style)
are automatically filled in by the system. Click Ok.
Figure 47: New Branch dialog box
OW360_50 81
5.5 To insert an I/O module in a branch

2. Use the system tree to navigate to the Slot item:
Systems > Networks > Units > Drops > Drop # > I/O Devices > I/O Device # OCC Local
Ovation > Branch # > Slot #
3. Expand the applicable Slot item to reveal an Ovation Module subfolder.
4. Right-click the Ovation Module subfolder (in the Slot folder that you want to configure) and
select Insert New.
Figure 48: Ovation Module item in Slot 1 subfolder
5. The Insert New Ovation Module Wizard appears. Perform the following steps:
a) Select the desired module from the Module Type drop-down menu.
b) Once you select a module, the applicable Module EMOD/PMOD part number appears
below the Module Type field.
c) Click Finish.
Figure 49: Insert New Ovation Module Wizard
82 OW360_50
6. The New Ovation Module dialog box appears and contains four tabs: Config, Module, Digital
Channels, and Analog Channels. Select the Config tab.
a) The Module Type and Module EMOD/PMOD fields are prefilled from your selections in
the Insert New Ovation Module Wizard.
b) Click Apply.
Note: Remember to add a module point (see page 62) during the module configuration.
Figure 50: New Ovation Module dialog box showing Config tab
7. The options and fields that appear in the New Ovation Module dialog box change depending
on the type of module you selected in the Insert New Ovation Module Wizard. Depending on
the module you are adding, you may have to configure parameters on the other tabs:
a) Click the Module tab and make appropriate entries according to the module type. Refer
to Ovation Developer Studio User Guide for information on the Module tab
parameters.
b) Depending on the module type, click either the Digital Channels tab or the Analog
Channels tab to view the point names that are assigned to each channel.
Note: For a point name to appear in the Value column of either the Digital Channel or Analog
Channel tab, it must be defined as an I/O point for this module. To define I/O points, go to the
appropriate point type folder in the Points folder, create or open an existing point, select the
Hardware tab, and configure the point channel. (Refer to the Ovation Developer Studio User
Guide.)
8. Click the Apply or OK button to enter the changes into the database.
Note: For additional information regarding Ovation modules, refer to the Ovation I/O Reference
Manual and Ovation Bus and Specialty I/O Reference Manual.
9. When the configuration is complete, download, reboot, and load the OCC (see page 70).
OW360_50 83
S E C T I O N 6
6 Configuring the OCC to use embedded protocols
IN THIS SECTION
Overview of configuring OCC to use embedded protocols ............................................... 85

To install the Communication Protocol software on a Database Server ........................... 85
To insert a new device number and I/O driver type for OCC embedded protocols .......... 86
To insert the device type for embedded OCC protocols ................................................... 88
To add OCC embedded protocols .................................................................................... 90
To configure protocols for OCC ........................................................................................ 92
6.1 Overview of configuring OCC to use embedded protocols

The OCC supports an embedded protocol suite, which allows you to directly interface to third-
party I/O or other devices without the need for extra hardware. The Embedded Ethernet Link
device type is used for an OCC running embedded protocols.
The following steps provide an overview of adding the Embedded Ethernet Link device type.
Refer to the specific topics for detailed instructions.
1. Install the Communications Protocol software on the Database Server (see page 85).
2. Insert a new device number and I/O driver type for embedded protocols (see page 86).
3. Insert the device type for embedded protocols (see page 88).
4. Add embedded protocols (see page 90).
5. Add a Node point (see page 65).
7. Configure protocols in the Protocol Configuration Tool (see page 92).
Note: See the applicable protocol manual for information on the Protocol Configuration Tool.
6.2 To install the Communication Protocol softw are on a Database

Server
The Communication Protocol Software Version 1.5 CD provides the Protocol Configuration Tool,
Protocol Analyzer, firmware for the Ovation Compact Controller and firmware for the Ethernet Link
Controller module.
Note: Make sure Ovation is installed on the machine before you install the Communication
Protocol Software Version 1.5 software.
1. Obtain the CD, Communication Protocol Software Version 1.5 for use on Ovation ELC
and OCC Controllers, from Emerson's Software Licensing department.
OW360_50 85
6.2 To install the Communication Protocol software on a Database Server
2. From a Database Server machine, insert the CD into the disk drive and access the drive.
3. Right-click the setup file (*.exe) and select Run. The installation program starts.
4. The Welcome window appears. Click Next.
5. The Service License Agreement window appears. Accept the terms of the licensing
agreement to continue and click Next.
6. The Setup Type window appears. Select one of the following options, and click Next:
 Complete - Installs the communication line drivers, the shared libraries, Protocol
Configuration Tool, and Protocol Analyzer.
 Custom - Installs the components that you choose to install. (The installation procedures
are the same no matter what choice is made.)
7. The Choose Destination Location window appears. This window asks you where to install the
Communication Protocol software. The default is C:\Ovation. Emerson recommends that you
use the default. Click Next.
8. The Ready to install the program window appears. Click Install.
9. The setup status window appears showing the installation progress.
10. The Installation Wizard Complete window appears. Click Finish. (Rebooting the machine is
not necessary.)
11. Perform a download function (see page 70).
6.2.1 To uninstall the Communication Protocol software
To uninstall the Communication Protocol software, perform the following steps:
1. Access Start > Control Panel > Programs and Features. The Uninstall or change a
program window appears.
2. Search for the Communication Protocol software from the list that appears.
3. Select the program, right-click, and click Uninstall.
4. A window appears asking if you want to confirm the remove operation. Click Yes. Several
windows appear as the system removes the program. Do not dismiss any windows that
appear during the remove operation.
5. When the operation is finished, the Uninstall Complete window appears. Click Finish.
6. Reboot your machine to permanently delete the files after the uninstallation process
completes.
86 OW360_50
6.3 To insert a new device number and I/O driver type for OCC embedded protocols
6.3 To insert a new device number and I/O driver type for OCC
embedded protocols
> Device Numbers
For example purposes in this manual, the device number for this procedure is set to 2 since
Local Ovation was set to 1.
OW360_50 87
6.3 To insert a new device number and I/O driver type for OCC embedded protocols
5. The New Device Numbers dialog box appears. Perform the following steps:
a) Select Ethernet Link from the I/O Driver Type drop-down menu.
c) When you select Ethernet Link, the value for Slot Order prefills from the system. The field
appears grayed out and cannot be changed.
d) The Scan Point Entries field defines the number of points that are being scanned by the
Ovation Compact Controller. The default is 2048. However, this number can be
configured up to 10,000.
e) Click Ok to save the changes and exit the window.
Figure 53: New Device Numbers dialog box with entries completed
88 OW360_50
6.4 To insert the device type for embedded OCC protocols

Systems > Networks > Units > Drops >Drop # > I/O Devices
 Select the I/O Device Number that you set in the Insert New Device Numbers Wizard.
This device number was paired to Ethernet Link in the New Device Numbers dialog box.
(For example purposes, the figure shows I/O Device Number set to 2.)
 Select Embedded Ethernet Link from the I/O Device Type drop-down menu.
 Click Finish.
OW360_50 89
5. The New I/O Devices dialog box appears. The dialog box contains the I/O device number and
the I/O device type that you selected in the wizard (Step 4). Perform the following steps:
Note: Remember to assign a Node point for the Embedded Ethernet Link device type (see page
65).
a) Enter a scan rate in milliseconds. This determines how fast the Compact Controller reads
the I/O data from the protocol.
b) The OCC can monitor the status of the NIC, and the Developer Studio can generate an
alarm when the NIC status is in an error state. Select the Suppress NIC Status Alarm
check box to mask or suppress the NIC status alarm.
c) When you finish, click Ok to save the changes and close the window.
6. Notice that the new Embedded Ethernet Link item now appears in the system tree along with
a placeholder for Embedded Ethernet Link Protocols.
Figure 57: New Embedded Ethernet Link item in Studio tree
90 OW360_50
6.5 To add OCC embedded protocols
6.5 To add OCC embedded protocols

The OCC supports an embedded protocol suite to be run directly on the Controller or in ELC
modules. The OCC supports up to two communication protocols from the Embedded Ethernet
Link suite and up to 1,500 points. If more protocols or points are desired, then ELC modules can
be used.

2. Use the system tree to navigate to the Embedded Ethernet Link Protocols item:
Systems > Networks > Units > Drops > Drop # > I/O Devices > I/O Device # Embedded
Ethernet Link > Embedded Ethernet Link Protocols
3. Right-click the Embedded Ethernet Link Protocols item and select Insert New from the
pop-up menu.
Figure 58: Embedded Ethernet Link Protocols item shown in Studio tree
4. The Insert New Embedded Ethernet Link Protocols Wizard appears. Perform the following
steps:
a) Enter a protocol number in the entry field. Each OCC supports two protocols.
b) Pull down the Protocol Name menu and selected the desired protocol.
c) Click Finish.
Figure 59: Insert New Embedded Ethernet Link Protocols Wizard
OW360_50 91
6.6 To configure protocols for OCC
5. The New Embedded Ethernet Link Protocols dialog box appears. The information in the
window is prefilled by the system. Click Ok.
Figure 60: New Embedded Ethernet Link Protocols dialog box

2. Use the system tree to navigate to the I/O Device # Embedded Ethernet Link item:
Ethernet Link
3. Right-click the I/O Device # Embedded Ethernet Link item and select Engineer from the
pop-up menu
Figure 61: Engineer menu item selected from Embedded Ethernet Link item
92 OW360_50
4. The Protocol Configuration Tool window appears. The Protocol Configuration Tool is
described in the various protocol manuals. The following protocol manuals are available to
use:
 Using the Allen-Bradley protocol with Ovation
 Using the DNP3 protocol with Ovation
 Using the GE Mark GSM Client configuration protocol with Ovation
 Using the IEC60870-5-101 Controlling and Controlled protocol with Ovation
 Using the IEC 61850 MMS Client protocol with Ovation
 Using the Turbine Control Interface protocol with Ovation
 Using the Modbus protocol with Ovation
 Using the LoggerNet protocol with Ovation
 Using Motorola ACE IP Gateway Protocol with Ovation
Figure 62: Protocol Configuration Tool window for OCC
OW360_50 93
S E C T I O N 7
7 Configuring the OCC to use the ELC module
IN THIS SECTION
Overview of configuring OCC for use with ELC modules ................................................. 95

To insert a new device number and I/O driver type for ELC ............................................. 95
To insert the device type used for ELC modules .............................................................. 97
To insert an ELC module in branch................................................................................... 99
To add protocols to the ELC module .............................................................................. 102
To configure protocols for ELC ....................................................................................... 105
7.1 Overview of configuring OCC for use w ith ELC modules

The following steps provide an overview of adding an Ethernet Link Controller module to an OCC.
Refer to the specific topics for detailed instructions.
1. Insert a new device number and I/O driver type for ELC modules (see page 95).
2. Insert the device type for ELC modules (see page 97).
3. Insert an ELC module in a branch (see page 99).
5. Add protocols to the ELC module (see page 102).
7. Configure protocols in the Protocol Configuration Tool (see page 105).
You must also Install the Communications Protocol software on the Database Server (see page
85) and configure the protocols you add. See Ethernet Link Controller User Guide for more
information on the ELC module. See the applicable protocol manuals for information on
configuring protocols in the Protocol Configuration Tool.
7.2 To insert a new device number and I/O driver type for ELC
Note: Unlike standard Controllers, the Ovation Compact Controller only supports one local I/O
interface. The OCC local I/O interface supports three branches of local Ovation I/O.

> Device Numbers
OW360_50 95
For example purposes in this manual, the device number for this procedure is set to 3
indicating that device numbers 1 and 2 have already been used.
96 OW360_50
a) Select Ethernet Link from the I/O Driver Type drop-down menu.
c) When you select Ethernet Link, the values for Slot Order prefills from the system. It
appears grayed out and cannot be changed.
d) The Scan Point Entries field defines the number of points that are being moved between
the Ethernet Link Controller module and the Ovation Controller. The default is 2048.
However, this number can be configured up to 10,000
OW360_50 97
7.3 To insert the device type used for ELC modules
7.3 To insert the device type used for EL C modules

This device number was paired to Ethernet Link in the New Device Numbers dialog box.
(For example purposes, the figure shows I/O Device Number set to 3.)
 Select Embedded Ethernet Link from the I/O Device Type drop-down list.
 Click Finish.
98 OW360_50
7.3 To insert the device type used for ELC modules
the I/O device type that you selected in the wizard (Step 4). Perform the following steps:
Note: Remember to assign a Node point for Embedded Ethernet Link device type (see page
65).
a) Enter a scan rate in milliseconds. This determines how fast the Compact Controller reads
the I/O data from the module.
b) The ELC can monitor the status of the NIC and the Developer Studio can generate an
alarm when the NIC status is in the error state. Select the Suppress NIC Status Alarm
check box to mask or suppress the NIC status alarm.
c) When you are finished, click Ok to save the changes and close the window.
OW360_50 99
7.4 To insert an ELC module in branch

Systems > Networks > Units > Drops > Drop # I/O Devices > I/O Device # OCC Local
Ovation > Branch > Slot #
select Insert New.
Figure 69: Ovation Module item in Slot 2 subfolder
100 OW360_50
a) Pull down the Module Type menu to display a list of all the possible Ovation I/O modules
you can add. Select Ethernet Link BusModule.
b) Once you select a module type, the applicable part number appears in the Module
EMOD/PMOD field.
c) Click Finish.
Figure 70: Insert New Ovation Module Wizard with Ethernet Link BusModule selected
b) Click Apply.
Note: Remember to add a module point (see page 62) during the module configuration. Module
points are required for every hardware module you add to your Ovation system.
Figure 71: New Ovation Module dialog box showing Config tab selected
OW360_50 101
7. The options and fields that appear in the New Ovation Module dialog box change depending
on the type of module you selected in the Insert New Ovation Module Wizard. Depending on
the module you are adding, you may have to configure parameters on the other tabs:
a) Click the Module tab and enter the appropriate information based on the module type.
Refer to Ovation Developer Studio User Guide for information on Module tab
parameters.
b) Depending on the module type, click either the Digital Channels tab or the Analog
Channels tab to view the point names that are assigned to each channel.
Note: For a point name to appear in the Value column of either the Digital Channel or Analog
Channel tab, it must be defined as an I/O point for this module. To define I/O points, go to the
appropriate point type folder in the Points folder, create or open an existing point, select the
Hardware tab, and configure the point channel. (Refer to the Ovation Developer Studio User
Guide.)
8. Click the Apply or OK button to enter the changes into the database.
Note: For additional information regarding Ovation modules, refer to the Ovation I/O Reference
Manual and Ovation Bus and Specialty I/O Reference Manual.
9. The Developer Studio tree updates with the new ELC module.
Figure 72: New Ethernet Link BusModule added to Studio tree
102 OW360_50
7.5 To add protocols to the ELC module

2. Use the system tree to navigate to the Slot # item:
Systems > Networks > Units > Drops > Drop # > I/O Devices > I/O Device # OCC
LocalOvation > Branch # > Slot #.
3. Expand the applicable Slot number to reveal the Ethernet Link BusModule.
4. Select the Ethernet Link BusModule and notice that two entries appear in the WordPad
window: Ethernet Link Configuration and Ethernet Link Protocols. Right-click Ethernet Link
Protocols, and select Insert New.
Figure 73: Ethernet Link Protocols item shown in the WorkPad window
OW360_50 103
5. The Insert New Embedded Ethernet Link Protocols Wizard appears. Perform the following
steps:
a) Enter a protocol number in the Protocol Number field.
b) Pull down the Protocol Name menu and selected the desired protocol.
c) Click Finish.
Note: Unlike the Ovation Compact Controller, the ELC module can have up to four protocols
assigned per module.
Figure 74: Insert New Embedded Ethernet Link Protocols Wizard
6. The New Embedded Ethernet Link Protocols dialog box appears. Click Ok.
Figure 75: New Embedded Ethernet Link Protocols dialog box
104 OW360_50
7.6 To configure protocols for ELC
7. The Studio tree updates to show the new protocol added to the WorkPad area.
Figure 76: Studio tree showing new Modbus Master protocol in WorkPad area
8. When configuration is complete, download, reboot, and load the OCC (see page 70).

2. Use the system tree to navigate to the I/O Device # Embedded Ethernet Link item:
Ethernet Link
3. Right-click the I/O Device # Embedded Ethernet Link item and select Engineer from the
pop-up menu.
4. The Protocol Configuration Tool window appears. The Protocol Configuration Tool is
described in the various protocol manuals. The following protocol manuals are available:
 Using the Allen-Bradley protocol with Ovation
 Using the DNP3 protocol with Ovation
 Using the GE Mark GSM Client configuration protocol with Ovation
 Using the IEC 61850 MMS Client protocol with Ovation
 Using the Turbine Control Interface protocol with Ovation
 Using the Modbus protocol with Ovation
OW360_50 105
 Using the LoggerNet protocol with Ovation

 Using Motorola ACE IP Gateway Protocol with Ovation
Note: Remember to add Node points (see page 65) for Embedded Ethernet Link protocols.
Figure 77: Protocol Configuration Tool window for OCC
106 OW360_50
S E C T I O N 8
8 Configuring the OCC to use the Fieldbus module
IN THIS SECTION
Overview of configuring OCC for use with Fieldbus modules ......................................... 107
To insert a new device number and I/O driver type for Fieldbus modules...................... 107
To insert the device type for Fieldbus modules .............................................................. 109
To insert a Fieldbus module in a branch ......................................................................... 111
8.1 Overview of configuring OCC for use w ith Fieldbus modules

The following steps provide an overview of configuring an OCC to use the Fieldbus module. Refer
to the specific topics for detailed instructions.
1. Insert a new device number and I/O driver type for Fieldbus modules (see page 107).
2. Insert the device type for Fieldbus modules (see page 109).
3. Insert a Fieldbus module into a branch (see page 111).
Additional configuration is required for Fieldbus modules (such as adding node points, Fieldbus
devices, and so forth). Refer to Ovation Foundation Fieldbus User Guide for more information on
configuring the Fieldbus module.
8.2 To insert a new device number and I/O driver type for Fieldbus
modules

> Device Numbers
OW360_50 107
8.2 To insert a new device number and I/O driver type for Fieldbus modules
For example purposes, the Device Number is set to 4 in the following figure. This indicates
that Devices Numbers 1, 2, and 3 have already been used.
108 OW360_50
8.2 To insert a new device number and I/O driver type for Fieldbus modules
a) Select FIELDBUS MODULE from the I/O Driver Type drop-down menu.
b) When you select FIELDBUS MODULE as the I/O Driver Type, the values for Scan Point
Entries value prefills from the system. It appears grayed out and cannot be changed.
c) Enter an amount of time in milliseconds for the Timeout (msec) entry field. This option
defines the message response timeout (in milliseconds). It is the amount of time the
driver waits for a response from the Fieldbus module before setting the point to BAD
quality. The default is 10000.
d) Select an option for Fail Controller on Error. This parameter allows you to determine if the
Fieldbus interface can fail the Compact Controller if an error occurs. The default is False.
Figure 80: New Device Numbers dialog box with FIELDBUS MODULE selected
OW360_50 109
8.3 To insert the device type for Fieldbus modules

This device number was paired to Fieldbus Module in the New Device Numbers dialog
box. (For example purposes, the figure shows I/O Device Number set to 4.)
 Select Foundation Fieldbus Module from the I/O Device Type drop-down list.
 Click Finish.
Figure 82: Insert New I/O Devices Wizard with Foundation Fieldbus Module selected
110 OW360_50
the I/O device type that you selected in the wizard (Step 4). Click Ok to close the window.
OW360_50 111
8.4 To insert a Fieldbus module in a branch

Branch # > Slot #
select Insert New.
a) Select Foundation Fieldbus BusModule from the Module Type drop-down menu.
b) Once you select the module type, the applicable part number appears in the Module
EMOD/PMOD entry field.
c) Click Finish.
112 OW360_50
b) Click Apply.
Figure 85: New Ovation Module dialog box
7. After you add a Fieldbus module to a branch and slot in the Developer Studio tree, you must
perform more configurations (add node points, slaves, and so forth). Refer to Ovation
Foundation Fieldbus User Guide for information on completing the configuration.
OW360_50 113
S E C T I O N 9
9 Configuring the OCC to use the Profibus module
IN THIS SECTION
Overview of configuring OCC for use with Profibus modules ......................................... 115
To insert a new device number and I/O driver type for Profibus modules ...................... 115
To insert the device type for Profibus modules ............................................................... 117
To insert a Profibus module in a branch ......................................................................... 118
9.1 Overview of configuring OCC for use w ith Profibus modules

The following steps provide an overview of adding a Profibus module to an OCC. Refer to the
specific topics for detailed instructions.
1. Insert a new device number and I/O driver type for Profibus modules (see page 115).
2. Insert the device type for Profibus modules (see page 117).
3. Insert a Profibus module into a branch (see page 118).
Additional configuration is required for Profibus modules (such as adding node points, Profibus
slaves, and so forth). Refer to Ovation Profibus User Guide for more information on configuring
the Profibus module.
9.2 To insert a new device number and I/O driver type for Profibus
modules

> Device Numbers
OW360_50 115
9.2 To insert a new device number and I/O driver type for Profibus modules
that Devices Numbers 1, 2, and 3 have already been used.
a) Select Profibus Module from the I/O Driver Type drop-down menu.
c) When you select Profibus Module as the I/O Driver Type, the values for Scan Point
Entries value prefills from the system. It appears grayed out and cannot be changed.
116 OW360_50
9.3 To insert the device type for Profibus modules
d) The Fail Controller on Error attribute allows you to determine if the Profibus interface can
fail the Compact Controller if an error occurs. The default is False.
Figure 88: New Device Numbers dialog box with Profibus Module selected

3. Right-click the I/O Devices item and select Insert New from the resulting pop-up menu.
OW360_50 117
This device number was paired to Profibus Module in the New Device Numbers dialog
 Select Profibus Module from the I/O Device Type drop-down list.
 Click Finish.
Figure 90: Insert New I/O Devices Wizard with Profibus selected
118 OW360_50
9.4 To insert a Profibus module in a branch

Branch # > Slot #
select Insert New
a) Select Profibus BusModule from the Module Type drop-down menu.
EMOD/PMOD entry field.
c) Click Finish.
OW360_50 119
b) Click Apply.
7. After you add a Profibus module to a branch and slot in the Developer Studio tree, you must
perform more configurations (add node points, slaves, and so forth). Refer to Ovation Profibus
User Guide for information on completing the configuration.
120 OW360_50
S E C T I O N 10
10 Configuring the OCC to use the Ethernet Remote

Node Interface (RNI)
IN THIS SECTION
Overview of configuring OCC for use with Ethernet Remote Node Interface modules .. 121
To insert a new device number and I/O driver type for Ethernet Remote Node Interface121
To insert the device type used for Ethernet Remote Node Interface .............................. 123
To insert a new node for Ethernet Remote Node Interface ............................................ 125
To insert a branch in a node ........................................................................................... 128
10.1 Overview of configuring OCC for use w ith Ethernet Remote Node
Interface modules
The following steps provide an overview of adding an Ethernet Remote Node Interface to an
OCC. Refer to the specific topics for detailed instructions.
1. Insert a new device number and I/O driver type for the Remote Node Interface (see page
121).
2. Insert the device type for the Remote Node Interface (see page 123).
3. Insert a new node for the Ethernet Remote Node Interface (see page 125).
4. Insert a branch in a node (see page 128).
5. Insert an I/O module (see page 81).
7. Add node points (see page 65).
Refer to Ethernet Remote Node Interface User Guide for more information.
10.2 To insert a new device number and I/O driver type for Ethernet
Remote Node Interface
Systems > Networks > Units > Drops > DROP# > Configuration > Controller > Devices >
Device Numbers
OW360_50 121
10.2 To insert a new device number and I/O driver type for Ethernet Remote Node Interface
For example purposes in this manual, the Device Number for this procedure is set to 5 in the
following figure. This indicates that Devices Numbers 1 through 4 have already been used.
122 OW360_50
10.3 To insert the device type used for Ethernet Remote Node Interface
a) Select Ethernet Remote from the I/O Driver Type drop-down menu.
c) When you select Ethernet Remote, the value Scan Point Entries prefills from the system.
It appears grayed out and cannot be changed.
d) Click Ok to save the changes and exit the window.
10.3 To insert the device type used for Ethernet Remote Node
Interface
OW360_50 123
10.3 To insert the device type used for Ethernet Remote Node Interface
This device number was paired to Ethernet Remote in the New Device Numbers dialog
 Select Ethernet Remote from the I/O Device Type drop-down list.
 Click Finish.
Figure 98: Insert New I/O Devices Wizard with Ethernet Remote selected
124 OW360_50
10.4 To insert a new node for Ethernet Remote Node Interface

For the Ethernet Remote Node Interface, you can have 16 nodes, 8 branches per node, and 8
slots per branch.

Systems > Networks > Units > Drops > Drop# > I/O Devices > I/O Device # Ethernet
Remote > Ethernet Remote Nodes
3. Right-click the Ethernet Remote Nodes subfolder and select Insert New.
Figure 100: Insert a new node in Developer Studio system tree
4. The Insert New Ethernet Remote Nodes Wizard appears. Perform the following steps:
a) Select the applicable node number.
b) Pull down the IO type menu and select Ovation.
c) Click Finish.
Figure 101: Insert New Ethernet Remote Nodes Wizard
OW360_50 125
5. The New Ethernet Remote Nodes dialog box appears. Refer to the table following the figure
for configuration information.
Note: Remember to add and assign a Node point for the Ethernet Remote device type (see
page 65).
a) When you are finished, click Ok to save the changes and close the window.
Figure 102: New Ethernet Remote Nodes dialog box
126 OW360_50
New Ethernet Remote Node fields description
FIELDS DESCRIPTION
Node Number Defines the node number 1 through 16.

Redundancy Mode Specifies the redundancy mode in the Controller. The options are:
▪ Legacy: Each half of the Ovation Controller communicates with only
one half of the redundant remote node.
▪ Standard: Each half of the Ovation Controller communicates with
both redundant remote nodes.
IO type Specifies the type of I/O. The only valid type for Ethernet I/O is
Ovation.
Node Record Point Name Indicates the node point (see page 65) that is configured to provide
status/diagnostic information about the node.
Fail Controller On Error Only applies to Legacy redundancy mode.
True: If communications are lost to the RNI then the Controller will
failover if the partner Controller is healthy. Otherwise, the points will be
set to bad quality/sensor alarm.
False: If communications are lost to the RNI then the points will be set
to bad quality/sensor alarm.
Default = False
Primary Node Ethers Address Identifies the MAC address of the primary half of the Ethernet Remote
Node.
Partner Node Ethers Address Identifies the MAC address of the partner half of the Ethernet Remote
Node.
Primary Node IP Address Specifies the IP address of the primary half of the redundant remote
node.
Partner Node IP Address Specifies the IP address of the partner half of the redundant remote
node.
Database Machine Specifies the IP address of the Database Server.
Junction Temperature Point Specifies the analog point that reports the internal temperature of the
(Primary) primary node.
Junction Temperature Point Specifies the analog point that reports the internal temperature of the
(Partner) partner node.
Ovation P S Status Alarming Enables the user to suppress the alarming of the various power supply
statuses.
24 Volt Primary (and Secondary) Selects the power supply used.
Power Supply
(0 - not used, 1 - used)
Auxiliary (1-3) Primary Power Selects the power supply used.
Supply
Auxiliary (1-3) Secondary Power Selects the power supply used.
Supply
OW360_50 127
10.5 To insert a branch in a node
6. The Ethernet Remote Node item updates in the Developer Studio tree showing the added
node and branch.
Figure 103: New Ethernet Remote Node added to Studio tree

The Branch item is established by default because Ethernet Remote was selected in the Insert
New I/O Device Wizard.

Systems > Networks > Units > Drops > Drop# > I/O Devices > I/O Device # Ethernet
Remote > Ethernet Remote Nodes >Node # Ovation > Branch
3. Right-click Branch and select Insert New.
Figure 104: Insert a new branch for Ethernet Remote Node Interface
128 OW360_50
4. The Insert New Branch Wizard appears. Select a Branch Number and click Finish.
Figure 105: Insert New Branch Wizard
5. The New Branch dialog box appears. The Branch Number and Branch Type are set and
cannot be changed in this window. Click Apply or Ok.
Figure 106: New Branch dialog box
OW360_50 129
6. The Developer Studio tree updates with the new branch and eight slots in the branch.
Figure 107: Developer Studio tree updates with the new branch
7. After you add branches, you can add modules to the slots. Modules are added to the Remote
Node Interface in the same way that you add them to a local Ovation device type. In addition,
you must add a module point for every module you add and a node point for every node that
you add.
 To insert an I/O module (see page 81).
 To add module points (see page 62).
 To insert a node point (see page 65).
Note: Refer to Ovation Ethernet Remote Node Interface User Guide for more information on
completing the configuration.
130 OW360_50
S E C T I O N 11
11 Configuring the OCC to use the DeviceNet module
IN THIS SECTION
Overview of configuring OCC for use with DeviceNet modules ...................................... 131
To insert a new device number and I/O driver type for DeviceNet ................................. 131
To insert the device type used for DeviceNet ................................................................. 133
To insert a DeviceNet module in a branch ...................................................................... 135
11.1 Overview of configuring OCC for use w ith DeviceNet modules

The following steps provide an overview of adding a DeviceNet module to an OCC. Refer to the
specific topics for detailed instructions.
1. Insert a new device number and I/O driver type for DeviceNet modules (see page 131).
2. Insert the device type for DeviceNet modules (see page 133).
3. Insert a DeviceNet module into a branch (see page 135).
Additional configuration is required for DeviceNet modules (such as adding node points and
DeviceNet slaves). Refer to Ovation DeviceNet User Guide for more information on configuring
the DeviceNet module.
11.2 To insert a new device number and I/O driver type for DeviceNet

> Device Numbers
OW360_50 131
that Devices Numbers 1 through 5 have already been used.
132 OW360_50
a) Select DEVICENET MODULE from the I/O Driver Type drop-down menu.
c) When you select DeviceNet Module, the value for Scan Point Entries prefills from the
system. It appears grayed out and cannot be changed.
d) The Fail Controller on Error attribute allows you to determine if the DeviceNet interface
can fail the Compact Controller if an error occurs. The default is False.
Figure 110: New Device Numbers dialog box with DeviceNet Module selected
OW360_50 133
11.3 To insert the device type used for DeviceNet
11.3 To insert the device type used for DeviceNet

This device number was paired to Profibus Module in the New Device Numbers dialog
 Select DeviceNet Module from the I/O Device Type drop-down list.
 Click Finish.
Figure 112: Insert New I/O Devices Wizard with DeviceNet Module selected
134 OW360_50
11.4 To insert a DeviceNet module in a branch

Branch # > Slot #
select Insert New
a) Click the Module Type dropdown menu to display a list of all the possible Ovation I/O
modules you can add. Select DeviceNet BusModule.
b) Once you select a module, the module type, the applicable part number appears below
the Module Type field.
c) Click Finish.
OW360_50 135
b) Click Apply.
7. After you add a DeviceNet module to a branch and slot in the Developer Studio tree, you
must perform more configurations (add node points, slaves, and so forth). Refer to Ovation
DeviceNet User Guide for information on completing the configuration.
136 OW360_50
S E C T I O N 12
12 Configuring the OCC to use the Machinery Health

Monitor module
IN THIS SECTION
Overview of configuring OCC for use with Machinery Health Monitor modules ............. 137
To insert a new device number and I/O driver type for MHM ......................................... 137
To insert the device type used for MHM ......................................................................... 139
To insert an MHM module in a branch ............................................................................ 141
12.1 Overview of configuring OCC for use w ith Mach inery Health
Monitor modules
The following steps provide an overview of adding Machinery Health Monitor (MHM) module to an
1. Insert a new device number and I/O driver type for MHM modules (see page 137).
2. Insert the device type for MHM modules (see page 139).
3. Insert an MHM module into a branch (see page 141).
Additional configuration may be needed for MHM modules, Refer to Machinery Health Monitor
User Guide for more information.
12.2 To insert a new device number and I/O driver type for MHM

> Device Numbers
OW360_50 137
138 OW360_50
a) Select Machinery Health Monitor from the I/O Driver Type drop-down menu.
b) The Scan Point Entries field defines the number of points that are being scanned by the
configurable up to 10,000.
driver waits for a response from the MHM module before setting the point to BAD quality.
The default is 10000.
d) Select an option for Fail Controller on Error. This parameter allows you to determine if this
interface can fail the Compact Controller if an error occurs. The default is False.
OW360_50 139
12.3 To insert the device type used for MHM
12.3 To insert the device type used for MHM

This device number was paired to Machinery Health Monitor in the New Device
Numbers dialog box. (For example purposes, the figure shows I/O Device Number set to
7.)
 Select Machinery Health Monitor from the I/O Device Type drop-down list.
 Click Finish.
Figure 120: Insert New I/O Devices Wizard with Machinery Health Monitor selected
140 OW360_50
12.4 To insert an MHM module in a branch

Branch # > Slot #
select Insert New
a) Select Machinery Health Monitor from the Module Type drop-down menu.
EMOD/PMOD field.
c) Click Finish.
OW360_50 141
b) Click Apply.
7. After you add an MHM module to a branch and slot in the Developer Studio tree, you must
perform more configurations (add points, download firmware and so forth). Refer to Ovation
Machinery Health Monitor User Guide for information on completing the configuration.
142 OW360_50
S E C T I O N 13
13 Configuring the OCC to use the Digital Excitation

Controller module
IN THIS SECTION
Overview of configuring OCC for use with Digital Excitation Controller modules ........... 143
To insert a new device number and I/O driver type for DEC .......................................... 143
To insert the device type used for DEC .......................................................................... 145
To insert a DEC module in a branch ............................................................................... 147
13.1 Overview of configuring OCC for use w ith Digital Excitation

Controller modules
The following steps provide an overview of adding an Ethernet Remote Node Interface to an
1. Insert a new device number and I/O driver type for DEC modules (see page 143).
2. Insert the device type for DEC modules (see page 145).
3. Insert a DEC module into a branch (see page 147).
Additional configuration may be needed for MHM modules, Refer to Digital Excitation Controller
User Guide for more information.
13.2 To insert a new device number and I/O driver type for DEC

> Device Numbers
OW360_50 143
13.2 To insert a new device number and I/O driver type for DEC
144 OW360_50
13.3 To insert the device type used for DEC
a) Select Digital Excitation Control from the I/O Driver Type drop-down menu.
b) The Scan Point Entries field defines the number of points that are being scanned by the
configurable up to 10,000.
driver waits for a response from the DEC module before setting the point to BAD quality.
The default is 10000.
d) Select an option for Fail Controller on Error. This parameter allows you to determine if this
interface can fail the Controller if an error occurs. The default is False.

OW360_50 145
This device number was paired to Digital Excitation Control in the New Device
Numbers dialog box. (For example purposes, the figure shows I/O Device Number set to
8.)
 Select Digital Excitation Control from the I/O Device Type dropdown list.
 Click Finish.
Figure 128: Insert New I/O Devices Wizard with Digital Excitation Control selected
146 OW360_50
13.4 To insert a DEC module in a branch

Branch # > Slot #
select Insert New
a) Pull down the Module Type menu to display a list of all the possible Ovation I/O modules
you can add. Select Digital Excitation Controller.
b) Once you select the module, the module type, the applicable part number appears below
the Module Type field.
c) Click Finish.
OW360_50 147
6. The New Ovation Module window appears and contains four tabs: Config, Module, Digital
b) Click Apply.
7. After you add a DEC module to a branch and slot in the Developer Studio tree, you must
perform additional configurations (add points, download firmware and so forth). Refer to
Ovation Digital Excitation Controller User Guide for information on completing the
configuration.
148 OW360_50
S E C T I O N 14
14 Using Restore mode
IN THIS SECTION
What is the online Restore Mode function? .................................................................... 149

Restore mode functions .................................................................................................. 150
Restore mode performance issues ................................................................................. 151
Restore mode engineering limitations ............................................................................. 152
Restore mode point information issues ........................................................................... 152
14.1 What is the online Restore Mode function?

The Ovation System contains an optional Online Controller Restore Mode which captures images
of an Ovation drop’s application data (Ovation originated points and control) and associated
system files.
The primary purpose of restore mode is to provide a mechanism to restore a redundant drop to its
former fully matched condition after undesirable and/or catastrophic control behavior is observed
following the load of new application data to one half of a pair of redundant Ovation
workstations/Controllers.
Restore Mode provides the ability to back-out the engineering changes made to the drop so it can
be reloaded with the same application data that its partner contains.
You must decide if you want to operate the Ovation Online Controller Restore Mode. No special
user interactions are required when operating in Restore Mode, but consider the following items:
 System performance and disk space issues.
 Engineering limitations.
 Point Information.
CAUTION! Restore Mode is intended to recover information from a failed load that may result
in a partner mismatch between redundant Controllers. It is NOT intended to “undo”
programming mistakes. Restore should NOT be used casually since the process is time-
consuming and requires operator action (including a drop reload) to ensure a complete drop
restore.
OW360_50 149
14.2 Restore mode functions
The following items are included in Restore Mode images:

 Database tables associated with the drop (including point and control information, hardware
configuration, and holding registers).
 Signal Diagrams created by the Control Builder.
 Control information (Control Builder drawing files).
 Data not included in restore images.
The following items are NOT included in Restore Mode images and must be regenerated
manually:
 Ovation configuration information.
 Custom graphics (built by the Graphics Builder).
 Reports.
 Reference information generated by the Graphics Builder and the Report Builder (information
required to support the Where Used function for a point).
 Reference information can be regenerated by recompiling any effected graphics and reports.
 Any applicable HSR PIC files must be regenerated and query/downloaded to the appropriate
drop (if the system is utilizing an Ovation historian, the PIC file must be imported into the
historian).
CAUTION! Arbitrarily switching between Restore Mode functions is NOT recommended.

When the system is taken out of Restore Mode, any existing restored images are marked as
invalid and can never be used again. When the system is placed into a Restore Mode, you
have the option of immediately taking restored images. However, the system only takes a
restored image if a drop is fully loaded and matched with its partner (if redundant).
14.2 Restore mode functions

Restore mode has three basic modes of operation:
1. Restore mode disabled (Default) (see page 150).

2. Restore mode enabled (all drops) (see page 150).
3. Restore mode enabled (redundant drops only) (see page 151).
14.2.1 Restore mode disabled (Default)
This mode of operation is equivalent to the traditional operation of Ovation. Specifically, no

restored images are created. Operation in this mode is encouraged during initial system
development/engineering and whenever substantial engineering changes are required in
situations where immediate failure recovery (to matched redundant states) is not required.
14.2.2 Restore mode enabled (all drops)
In this mode of operation, restored images are created automatically by the system immediately
following the full (and successful) load of an Ovation drop. In the case of a redundant drop, this
means that the image is created after both halves have been fully loaded (that is, the drop is
completely matched with its partner and with the Ovation database). In the case of a non-
redundant drop, this means that the image is created after it has been fully loaded (that is, the
drop is completely matched with the Ovation database).
150 OW360_50
14.3 Restore mode performance issues
14.2.3 Restore mode enabled (redundant drops only)
In this mode of operation, restored images are created automatically by the system immediately
following the full (and successful) load of redundant Ovation drops. Restored images are NOT
taken for non-redundant drops.
The Ovation Drop Loader application provides the mechanism to place the Ovation System into
(and out of) Restore Mode. The selections under the Properties pull-down menu indicate the
actions that are available to switch between these modes of operation and work in conjunction
with the message box at the bottom of the dialog box.
14.3 Restore mode performanc e issues

When the Ovation System is configured for operation in Restore mode, there are performance
and disk space issues that must be considered. Typically, the overall load operation is slower.
Note: The additional time required to capture the restored images occurs after the successful
load of the applicable drop. While the Ovation application data load-time is not affected, your
ability to immediately perform additional operations (for example, load another drop) is affected.
Additional disk space is required to maintain the files associated with a drop’s restored image.
When the system is operated in Restore Mode, the required disk space is expanded as follows:
 Approximately three times the amount of disk space is required for Control Builder drawing
files.
 Approximately two times the amount of disk space is required for control signal diagram files
(source and compiled object copies).
 Approximately two times the amount of disk space is required for the export files which are in
Oracle binary format (that is, full export).
OW360_50 151
14.4 Restore mode engineering limitations
14.4 Restore mode engineering limitations

Certain engineering operations are limited if the applicable drop is in the Restore function:
 When the system is in Restore mode, you cannot reference a point in another drop's control if
the point in question is not in a restored image. For example, if Drop1 is originating point
D100, Drop2 cannot reference D100 in any of its control unless D100 exists in Drop1's
restored image. This implies that D100 is already loaded into Drop 1 (and if redundant, into
Drop1’s partner).
 When in Restore mode, you may still reference a point (for example, D100) with a point in
another drop even if D100 is not in another drop’s restored image. For example, a drop may
receive a point not currently in a restored image for reasons such as alarm cutout or as an
alarmable point limit. The ability to do this is consistent with (and a natural extension of) the
current use of these types of point references.
Note: The above implies that a Restore operation may cause another drop to be mismatched
with respect to the database if one or more points in another drop reference a point that has
been removed from the database as a direct result of the Restore operation. The operating
integrity of these other (newly and automatically mismatched) drops is not compromised,
however, and only results in SID-type alarms being generated for the referencing point.
 When in Restore mode, a point cannot be added if it exists in another drop's restored image.
For example, assume Drop1 is fully loaded (and a valid restored image exists for the drop). If
you delete a point from Drop1 (for example, D100), a point with the same name (D100)
cannot be added to another drop in the same unit until Drop1 (and its partner if redundant) is
fully loaded. Both the Point Builder and the Import programs check for this condition.
 When in Restore mode, a point's originator cannot be changed. Explicit delete and add
operations are required. Note that the point must also be deleted from its originator by fully
loading the drop before the add operation can be performed (see the preceding Limitation).
14.5 Restore mode point information issues

An additional feature of the restore operation is the handling of point information distributed by the
Database Server to the Ovation Operator Stations. Specifically, a restore operation must handle
any points whose HMI data has changed or that have been added or deleted while the drop was
in a mismatched state. The following is an example of one type of situation, which is handled
during a Restore operation:
When a point is added to the database and subsequently loaded to its originator (even if only
half of a redundant drop), information about the point is distributed to the Ovation Operator
Stations via the Ovation Database Distribution mechanism. The point is then available for use
by the normal Operator Station programs (for example, Point Information, Point Review, and
so on).
If a point is added to the database, loaded to only one-half of its originator and subsequently
removed because you performed a Restore operation, the Ovation Database Distribution
mechanism handles the deleting of this point from the Ovation Operator Stations.
Therefore, after the Restore operation, the point is removed from the Ovation Operator
Station's internal data files. (Note that the normal Ovation Database Distribution mechanism
is utilized for this, so the Ovation Operator Stations may not immediately process any
distributed changes.)
152 OW360_50
14.5.1 To set the online Controller Restore Mode

2. Use the system tree (in the Hardware view bar) to navigate to and open the Systems folder.
3. Right-click the Systems item object in the Workpad window.
4. Select Open from the resulting pop-up menu; the System item dialog box appears.
5. Select Restore Mode in the Attributes column and select the appropriate option from the
drop-down list.
Figure 132: System dialog box
OW360_50 153
System dialog box fields description
FIELDS DESCRIPTION
System Name Can be 1 - 8 characters in length. Invalid characters are period (.), dollar sign
($), percent sign (%), pound sign (#), at sign (@), and space.
System Value Value of your choice.
Database Machine Used internally by Ovation applications to talk to other computers (for
informational purposes only).
Offline Mode Permits certain changes to be made off line (Refer to the Online/Offline mode
section of the Ovation Developer Studio user guide).
(Default - Not Checked.)
Restore Mode Online Controller Restore Mode. Reload mismatched Controllers to a prior
matched state. The choices are:
▪ Restore Mode Disable
▪ Restore Mode Enable All Drops
▪ Restore Mode Enable Redundant Drops
(Default - Restore Mode Disabled.)
Disable Deluxe Points Allows systems not using deluxe points to hide those folders to reduce screen
clutter. You cannot insert through the Developer Studio or an input operation
while this box is checked.
(Default - Not Checked.)
Alarm Cutout Specifies the operation of alarm cutout for the system:
▪ Inhibit alarms generation.
▪ Inhibit alarms display cutout, but alarming is still enable.
154 OW360_50
S E C T I O N 15
15 Using the Controller Diagnostics tool
IN THIS SECTION
What is the Controller Diagnostics tool? ......................................................................... 156

Software platforms that Controller Diagnostics supports ................................................ 156
What firmware can be downloaded to the I/O modules through the Controller
Diagnostics window? ....................................................................................................... 157
Controller Diagnostics window ........................................................................................ 160
Controller List in the Controller Diagnostics window ....................................................... 163
Controller Overview panel in the Controller Diagnostics window ................................... 165
Controller Diagnostics Update Backup function .............................................................. 167
Control Task Information tab in the Controller Diagnostics window ............................... 168
I/O Information tab in the Controller Diagnostics window ............................................... 170
Software Versions tab in the Controller Diagnostics window .......................................... 171
Point Details tab in the Controller Diagnostics window ................................................... 172
Sheet Information tab in the Controller Diagnostics window .......................................... 173
Process Information tab in the Controller Diagnostics window ....................................... 175
Refresh function for the Controller Diagnostics window ................................................. 176
OW360_50 155
15.1 What is the Controller Diagnostics tool?
15.1 What is the 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 160).
You can also access the Controller Diagnostics window using Ovation Utilities. To use the
Diagnostics utility, click the Start menu -> All Programs -> Ovation -> Ovation Utilities ->
Diagnostics.
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 163).
 Update data in a partner Controller to match the data in the primary Controller (see page
167).
 Display information about the control tasks for that Controller (see page 168).
 Display information about I/O modules that interface to the selected Controller (see page
170).
 Download firmware to intelligent I/O modules that interface to the selected Controller (see
page 157).
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 on one of the Controller
Diagnostics window tabs or in one of the window sections (Controller List or Controller
Overview).
15.2 Softw are platforms that Controller Diagnostics supports

The Controller Diagnostics function is designed to run on Windows-based systems. The
Controller Diagnostics tool is applicable on the Ovation Compact Controller, OCR400, and
OCR1100 Controllers.
156 OW360_50
15.3 What firmware can be downloaded to the I/O modules through the Controller Diagnostics window?
15.3 What firmw are can be dow nloaded to the I/O modules through
the Controller Diagnostics w indow ?
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 be different from the firmware that is currently on
your I/O module. 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
 Profibus
 Fieldbus
 DeviceNet
 Machinery Health Monitor
 Digital Excitation Controller
 Ethernet Link Controller
WARNING! Downloading firmware to an I/O module may cause the module to reset. Make
sure your plant is in a safe condition or 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, communication priority is lowered during the firmware download process, and may
cause communication failures with the AMS Device Manager and/or multi-variable messaging.
15.3.1 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 at an Ovation workstation.

2. Double-click the module and select the I/O Information tab (see page 170).
OW360_50 157
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 133: 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.
process.
Therefore, communications priority is lowered during the firmware download process, and may
6. Select the files you want to download.

7. Click 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 159) after download, the Reboot
Module button is enabled.
CAUTION! The reboot process for the MHM may take 15 minutes or more to complete. During
this time, the MHM module updates one of its FPGAs. DO NOT power off the module or
remove it from its I/O base. Interruption of the reboot process during this time may render the
module inoperable, which may require you to return the module to Emerson for RMA repair. A
progress bar displays the estimated percentage of process completion.
158 OW360_50
The following figure illustrates the progress bar for the rebooting process:
Figure 134: Progress bar for the MHM reboot process
15.3.2 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 appears.
OW360_50 159
15.4 Controller Diagnostics window
15.4 Controller Diagnostics w indow

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 162).
The left portion of the Controller Diagnostics window contains a Controller Overview section (see
page 165) that provides internal information about the selected Controller. This section also
contains an Update Backup button (see page 167) that can update the data in a partner Controller
to match the data in the primary Controller.
Below the Controller Overview section is the Controller List (see page 163) 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 168) 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 171) to identify the software version of each
software package that is installed on the selected Controller.
 Use the Point Details tab (see page 172) to list the points originated and received by the
selected Controller.
 Use the Sheet Information tab (see page 173) to provide information about the elements on
control sheets for the selected Controller.
 Use the Process Information tab (see page 175) to provide information about the tasks that
are currently running.
160 OW360_50
15.4.1 To access the Controller Diagnostics tool

1. From an Ovation workstation, select Start > Ovation > Ovation Utilities > Diagnostics.
The Controller Diagnostics window appears.
Figure 135: Controller Diagnostics window
OW360_50 161
15.4.2 Controller Diagnostics menu bar
The Controller Diagnostics window contains a menu bar that provides three drop-down menus:
Figure 136: Controller Diagnostics menu bar
Controller Diagnostics menus
MENU DESCRIPTION
File ▪ Select a Controller - Displays the Select a Controller window (see page 163).
▪ 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.
15.4.3 Controller Diagnostics toolbar
The Controller Diagnostics window provides a toolbar. Drag the mouse over the toolbar icons to
identify each icon.
Figure 137: Controller Diagnostics toolbar
The toolbar icons (left to right) perform the following functions:

 The window icon displays the Select a Controller window (see page 163).
 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.
162 OW360_50
15.5 Controller List in the Controller Diagnostics window
15.5 Controller List in the Controller Diagnostics w indow

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 138: Controller List
Select the Controller with the 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.
OW360_50 163
15.5 Controller List in the Controller Diagnostics window
15.5.1 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 163) window
(located beneath the Controller Overview panel).
OR
Select the Select a Controller item from the File menu or from the toolbar. A pop-up window
appears.
3. Enter a Controller name or IP address in the pop-up window. Information about that Controller
now appears in the Controller Diagnostics window.
Figure 139: Select a Controller Drop dialog box
164 OW360_50
15.6 Controller Overview panel in the Controller Diagnostics window
15.6 Controller Overview panel in the Controller Diagnostics w indow

The left panel of the Controller Diagnostics window provides internal information about the
Controller you have selected and the associated Partner Controller. The following example
illustrates an OCR1100 Controller; however, the information applies to both the Ovation Compact
Controller and the OCR400 Controller.
Figure 140: Controller Overview panel
OW360_50 165
15.6 Controller Overview panel in the Controller Diagnostics window
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
▪ OCC100
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 ID.
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.
CPU Load Controller CPU utilization.
Worst CPU Load Maximum length of time the Controller could take to execute a task.
IOIC Load Displays the IOIC duty cycle.
Memory Total Total amount of memory available in the Controller's RAM disk (Kbytes).
Memory Used Total amount of memory used in the Controller's RAM disk (Kbytes).
Flash Capacity Total amount of flash memory available in the Controller.
Flash Free Total amount of flash memory free in the Controller.
Flash Health Condition of the compact flash disk used in the Controller.
Used File Descriptors Number of file descriptors available and the state of IP buffers.
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.
Controller Patch Patch name of the Controller software.
Kernel Patch Patch name of the kernel.
Controller Change Set Deployed version number of the Controller software.
Kernel Change Set Deployed version number of the kernel.

Update Backup button Updates data in the partner Controller to match data in the primary Controller.
(see page 167)
166 OW360_50
15.7 Controller Diagnostics Update Backup function
15.7 Controller Diagnostics Update Backup function

Use the Update Backup function when a Drop Load function for a Controller has failed and you
must clear and reload the Controller. This puts the Controller into backup mode, but since it has
been cleared, a mismatch may now exist between this partner 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 167).
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.
15.7.1 To update your partner Controller in the Controller Diagnostics window

1. Access the Controller Diagnostics window, select Start > Ovation > Ovation Utilities >
Diagnostics
2. Select the partner Controller that you want to update. The drop name of the partner
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 partner Controller.
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. Refer to the Developer Studio User
Guide.
To reboot the Controller that is in control:

1. Use the system tree to navigate to the Drops folder:
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 2.
d) For redundant drops, the Select a drop to reboot dialog box appears.
➢ Select the drop you want to reboot.
➢ Click the Ok button.
2. A confirmation dialog box appears. Click the Yes button to close the window and execute the
reboot process.
OW360_50 167
15.8 Control Task Information tab in the Controller Diagnostics window
15.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 141: Control Task Information tab
168 OW360_50
15.8 Control Task Information tab in the Controller Diagnostics window
Control Task Information tab fields
FIELD DESCRIPTION
The following fields appear for each task Area (1 - 5).

The Total column 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 Memory Displays the total available space for a control task.
Used Control Memory Displays the total actual space used for a control task.
Capacity of Memory Percentage of memory that is used for a control task.
Configured Cycle Time Displays the execution time (in milliseconds) that is configured for a
(msec) control task.
Average Cycle Time (msec) Displays the average execution time (in milliseconds) that is used for a
control task.
Worst Cycle Time (msec) Displays the longest execution time (in milliseconds) that is used for a
control task.
Standard Deviation Displays the standard deviation of total CPU usage. It also displays the
standard deviation of task execution time for each control task and how
many times loops fall outside of the standard deviation.
Analog Input Points Total number of analog input points in the task area.
Digital Input Points Total number of digital input points in the task area.
Packed Input Points Total number of packed input points in the task area.
Analog Output Points Total number of analog output points in the task area.
Digital Output Points Total number of digital output points in the task area.
Packed Output Points Total number of packed output points in the task area.
Total I/O Points Total number of analog, digital, and packed points in the task area.
OW360_50 169
15.9 I/O Information tab in the Controller Diagnostics window
15.9 I/O Information tab in the Controller Diagnostics w indow

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.
process.
Therefore, communications priority is lowered during the firmware download process, and may
Figure 142: I/O Information tab
170 OW360_50
15.10 Software Versions tab in the Controller Diagnostics window
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
15.10 Softw are Versions tab in the Controller Diagnostics w indow

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 143: Software Versions tab
OW360_50 171
15.11 Point Details tab in the Controller Diagnostics window
15.11 Point Details tab in the Controller Diagnostics w indow

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 144: 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.
172 OW360_50
15.12 Sheet Information tab in the Controller Diagnostics window
15.12 Sheet Information tab in the Controller Diagnostics w indow

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
use the scroll bars to locate information.
Figure 145: Sheet Information tab
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.
OW360_50 173
15.12 Sheet Information tab in the Controller Diagnostics window
FIELD DESCRIPTION
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.
174 OW360_50
15.13 Process Information tab in the Controller Diagnostics window
15.13 Process Information tab in the Controller Diagnostics w indow

The Process Information tab provides information on tasks that are currently running. You can
resize the columns and use the scroll bars to locate information.
Figure 146: Process Information tab
Process Information tab fields
FIELD DESCRIPTION
Task Name Name of the currently running task.

CPU Load CPU utilization by a particular task.
State State of the currently running task (for example, Pending, Delay, and so forth).
OW360_50 175
15.14 Refresh function for the Controller Diagnostics window
15.14 Refresh function for the Controller Diagnostics w indow

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.
176 OW360_50
S E C T I O N 16
16 Troubleshooting and Maintenance
IN THIS SECTION
What troubleshooting and maintenance procedures are needed for OCC? ................... 177
To replace Ovation Compact Controller Electronics modules ........................................ 178
To recover from a Controller failure during a drop load operation .................................. 178
To reformat the flash ....................................................................................................... 179
To reboot the OCC .......................................................................................................... 179
To access the System Viewer to obtain fault code information ...................................... 180
16.1 What troubleshooting and mainte nance procedures are needed

for OCC?
Emerson provides several built-in tools to help with maintenance and troubleshooting of the OCC.
These tools include:
 Error Log (refer to Ovation Operator Station User Guide for more information).
 Diagnostic LEDs (see page 23).
 Fault Codes (see page 181).
In addition, the following topics provide maintenance information specific to the OCC:
 Replacing Ovation Compact Controller Electronics modules (see page 178).
 Recovering from a Controller failure during a drop load operation (see page 178).
 Reformating the flash (see page 179).
 Rebooting the OCC (see page 179).
OW360_50 177
16.2 To replace Ovation Compact Controller Electronics modules
16.2 To replace Ovation Compact Controller Electronics modules

You can replace OCC Electronic modules quickly and easily without shutting down the power
supplies or reconfiguring the modules. OCC Electronics 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.
CAUTION! Before hot swapping OCC Electronics 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, ensure that you maintain the appropriate
settings for forced point values and/or field power jumpers 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.
1. If using redundant OCC Electronics modules, determine which module should be replaced.
2. If replacing both modules, start with partner (backup) OCC first.
3. Unlatch the blue corner latches on the module case.
4. Remove the faulty module from the base assembly.
5. Insert the new module in the base assembly.
6. Use the blue corner latches on the module to secure it in place in the base.
7. The module comes up in a cleared state. Perform a download, reboot, and load operation on
the Controller.
8. Repeat Steps 3 through 7 for the second module if replacing both.
16.3 To recover from a Controller failure during a drop load operation

A drop load is necessary anytime there is a modification relating to points, holding registers, and
control sheets in a Controller. While running the control application in control, the Controller may
fail during the drop load operation. The reason for the failure may be a complex memory
modification that cannot be performed properly.
CAUTION! Resolve the error(s) before loading the partner Controller drop that is currently in
control. Rebooting the failed Controller without a subsequent clear and load will not resolve the
failed Controller. Make sure that you clear and load the failed Controller before loading the
partner Controller that is in control.
Perform the following steps to recover from a Controller failure during a drop load operation.
1. Download the failed Controller (see page 70).

2. Clear the failed Controller to clear the current memory for the control application within the
Controller.
178 OW360_50
16.4 To reformat the flash
3. Check the Ovation Error Log to verify that the Controller is completely booted and running in
the backup mode.
a) To access Ovation Error Log, select Start > Ovation Applications > Error Log.
4. Load the Controller (see page 74) to load and build a new memory for the control application
within the Controller.
Note: If there are errors, verify the Controller changes.
5. After the Controller successfully loads, a mismatch exists between the partner Controller and
the primary Controller. This may cause a bump during the Controller failover, as part of the
recovery of the partner Controller.
6. Load the partner Controller that is in control with the current control application. The load of
this control in turn also fails the Controller.
7. To successfully fail the Controller across a mismatch condition, perform the following steps:
a) Access the Controller Diagnostics (see page 161).
b) Select the Controller pair you want to update.
c) Click the Update Backup button to copy all the point values from the current Controller in
the Control Mode to the Controller in the Backup Mode.
8. Reboot the Controller (see page 72) immediately that is currently in control mode to transfer
control to the recovered (backup/partner) Controller.
the backup mode.
10. Clear the Controller to clear the current memory build for the control application within the
Controller.
the backup mode.
12. Load the Controller to load and build a new memory for the control.
13. The Drop Load is complete and the Controller pair is loaded with the current control
application and a mismatch condition does not exist.
Note: If the above procedure does not work, there may be a flash issue. Emerson recommends
formatting the flash card from the Failed Controller.
16.4 To reformat the flash
CAUTION! The OCC flash can be reformatted when you are directly connected to a serial
console connection by using an internal command. Emerson recommends that only qualified
people attempt to reformat the flash. Reformatting the flash should not be performed regularly
since it is not needed for normal maintenance. If you suspect a problem contact your Emerson
service representative.
Reformatting the flash happens automatically when the OCC Electronics module is moved to
different slot on the base.
OW360_50 179
16.5 To reboot the OCC
16.5 To reboot the OCC

1. Unlatch the blue corner latches on the OCC Electronics module case.
2. Remove the module from the base assembly.
3. Insert the new module in the same slot in the base assembly.
Note: Placing an OCC Electronics module in a different slot reformats the flash.
4. Use the blue corner latches on the module to secure it in place.

5. The module comes up in a cleared state. Perform a download, reboot, and load operation on
the Compact Controller.
6. Repeat Steps 1 through 5 for the second module if rebooting both.
16.6 To access the S ystem View er to obtain fault code information

The Ovation System Viewer application allows you to view the overall health of your Ovation
system as well as the health of individual Ovation components. With the System Viewer, you can
navigate through the various levels of an Ovation system, from the System level to the drop level,
to view drop status, point, and I/O information, as well as fault code information.
1. Open the Ovation Applications folder at the Operator Station and double-click the System
Viewer icon.
OR
Select Start -> All Programs -> Ovation -> Ovation Applications -> System Viewer.
2. The System Viewer window appears. The first time the System Viewer window appears, it
displays the top-level view of the entire Ovation system.
Figure 147: System Viewer window - top-level view
Refer to Ovation Operator Station User Guide for more information on the System Viewer
application.
180 OW360_50
16.6 To access the System Viewer to obtain fault code information
16.6.1 I/O Status values for Fault Code 66

The following table lists the I/O Status values that are applicable for Fault Code 66 (Fault ID B).
These values are the I/O status values for fault parameter 5 (FP5) of Controller Error:
FC=66 Controller, FID=B I/O Subsystem, FP1=2 Redundant I/O Error, FP2=X, FP3=Device
Number, FP4=Hardware Address, FP5=I/O Status
I/O Status values
BIT DEFINITION
0x0000 Local: No response from module

0x0800 Remote: Echo: No response
0x0a00 Remote: Node: No response
0x0e00 Remote: Transmit collision1
0x2000 Local: Bad CRC
0x2800 Remote: Echo: Bad CRC1
0x2a00 Remote: Node: Bad CRC
0x2e00 Remote: I/O control register changed
0x4000 Local: Module in attention
0x4c00 Remote: Node in attention
0x4e00 Remote: PCRR internal error
0x6000 Success
0x6200 Remote: Echo: Wrong SRC1
0x6400 Remote: Node: Wrong SRC
0x6800 Remote: Echo: Wrong DST1
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
1Consider updating PCRR board (3A99190G01) to Revision 14 (per DEO 57211).
OW360_50 181
16.6 To access the System Viewer to obtain fault code information
Note: Bit 0x8000 could also be set in any of these codes.
Local I/O statuses indicate a problem in the local Ovation 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 Ovation I/O bus. The problem is between
the PCRR and the remote node Controller.
182 OW360_50
Index
Determining the Internet Protocol (IP)

A address of an Ovation Compact Controller
Accessing the Ovation Developer Studio • • 39
44 Determining the Network Ethers address
Adding and configuring an Ovation Compact (MAC address) • 39
Controller • 43 Diagnostic LEDs for Ovation Compact
Adding Node (RN) points • 65 Controller • 23
Automatic failover control • 4 Download, reboot, and load the OCC • 70
C F
Configuring the OCC to use embedded Features of the Ovation Compact Controller
protocols • 85 •3
Configuring the OCC to use local Ovation Four-slot horizontal I/O base with standard
I/O • 75 terminations • 17
Configuring the OCC to use the DeviceNet
H
module • 131
Configuring the OCC to use the Digital Hardware and software requirements for the
Excitation Controller module • 143 Ovation Compact Controller • 9
Configuring the OCC to use the ELC module Hardware installation guidelines and best
• 95 practices • 30
Configuring the OCC to use the Ethernet How is the Ovation Compact Controller
Remote Node Interface (RNI) • 121 similar to a standard Ovation Controller? •
Configuring the OCC to use the Fieldbus 5
module • 107
Configuring the OCC to use the Machinery I
Health Monitor module • 137 I/O Information tab in the Controller
Configuring the OCC to use the Profibus Diagnostics window • 170
module • 115 I/O Status values for Fault Code 66 • 181
Control Task Information tab in the Introduction to the Ovation Compact
Controller Diagnostics window • 168 Controller • 1
Controller base assembly • 11
Controller Diagnostics menu bar • 162 M
Controller Diagnostics toolbar • 162
Minimum software requirements for Ovation
Controller Diagnostics Update Backup
Compact Controller • 34
function • 167
Controller Diagnostics window • 160 N
Controller List in the Controller Diagnostics
window • 163 Network interface ports • 19
Controller Overview panel in the Controller Node (RN) point assignments for OCC Local
Diagnostics window • 165 Ovation • 68
Copyright Notice • 2 O
Custom Controller Networking • 61
OCC power supply LED status conditions •
D 29
Defining Controller devices and drivers • 69 OCC power supply specifications • 27
Defining system addresses for the Ovation Ovation Compact Controller components • 9
Compact Controller • 37 Ovation Compact Controller module • 13
Definition of Terms for the Ovation Compact Overview of adding an Ovation Compact
Controller • 5 Controller drop to the Developer Studio •
43
OW360_50 183
Index
Overview of configuring OCC for Local Specifications for the Ovation Compact
Ovation I/O modules • 75 Controller • 23
Overview of configuring OCC for use with Summary of Changes • 3
DeviceNet modules • 131
Overview of configuring OCC for use with T
Digital Excitation Controller modules • 143 To access the Controller Diagnostics tool •
Overview of configuring OCC for use with 161
ELC modules • 95 To access the System Viewer to obtain fault
Overview of configuring OCC for use with code information • 180
Ethernet Remote Node Interface modules To add Module (RM) points • 62
• 121 To add OCC embedded protocols • 91
Overview of configuring OCC for use with To add protocols to the ELC module • 103
Fieldbus modules • 107 To configure default control tasks • 55
Overview of configuring OCC for use with To configure protocols for ELC • 105
Machinery Health Monitor modules • 137 To configure protocols for OCC • 92
Overview of configuring OCC for use with To confirm the Controller Networking
Profibus modules • 115 settings • 58
Overview of configuring OCC to use To create a drop point for the OCC • 50
embedded protocols • 85 To determine the Network Ethers address
from the label • 40
P
To determine the Network Ethers address
Pin assignments for power connectors • 19 from the Ovation Error Log application •
Point Details tab in the Controller 41
Diagnostics window • 172 To download a Controller drop configuration
Power connector for two-slot Marshalling • 70
base • 21 To download firmware revisions to the I/O
Power connectors for OCC base • 20 modules through the Controller
Power status connector for four-slot Diagnostics window • 157
Standard base • 22 To insert a branch for local Ovation • 80
Power supply options for the Ovation To insert a branch in a node • 128
Compact Controller • 25 To insert a DEC module in a branch • 147
Process Information tab in the Controller To insert a DeviceNet module in a branch •
Diagnostics window • 175 135
To insert a Fieldbus module in a branch •
R 112
Reference documentation • 8 To insert a new control task for the OCC • 57
Refresh function for the Controller To insert a new device number and I/O
Diagnostics window • 176 driver type for DEC • 143
Restore mode disabled (Default) • 150 To insert a new device number and I/O
Restore mode enabled (all drops) • 150 driver type for DeviceNet • 131
Restore mode enabled (redundant drops To insert a new device number and I/O
only) • 151 driver type for ELC • 95
Restore mode engineering limitations • 152 To insert a new device number and I/O
Restore mode functions • 150 driver type for Ethernet Remote Node
Restore mode performance issues • 151 Interface • 121
Restore mode point information issues • 152 To insert a new device number and I/O
driver type for Fieldbus modules • 107
S To insert a new device number and I/O
driver type for local Ovation • 75
Sheet Information tab in the Controller
To insert a new device number and I/O
Diagnostics window • 173
driver type for MHM • 137
Slot mismatch detection • 4
Software platforms that Controller
driver type for OCC embedded protocols •
Diagnostics supports • 156
87
Software Versions tab in the Controller
driver type for Profibus modules • 115
184 OW360_50
Index
To insert a new node for Ethernet Remote Using the Ovation Compact Controller in a
Node Interface • 125 Wide Area Network (WAN) • 33
To insert a new OCC drop in the Ovation
Developer Studio • 44 W
To insert a Node point • 66 What additional software configurations are
To insert a Profibus module in a branch • needed for Ovation Compact Controllers?
119 • 62
To insert an ELC module in branch • 100 What firmware can be downloaded to the I/O
To insert an I/O module in a branch • 82 modules through the Controller
To insert an MHM module in a branch • 141 Diagnostics window? • 157
To insert the device type for embedded OCC What is an Ovation I/O module address? •
protocols • 89 37
To insert the device type for Fieldbus What is the Controller Diagnostics tool? •
modules • 110 156
To insert the device type for local Ovation • What is the online Restore Mode function? •
78 149
To insert the device type for Profibus What is the Ovation Compact Controller? • 2
modules • 117 What licensing is required for the Ovation
To insert the device type used for DEC • 145 Compact Controller? • 34
To insert the device type used for DeviceNet What troubleshooting and maintenance
• 134 procedures are needed for OCC? • 177
To insert the device type used for ELC
modules • 98
To insert the device type used for Ethernet
Remote Node Interface • 123
To insert the device type used for MHM •
140
To install the Communication Protocol
software on a Database Server • 85
To load a Controller drop • 74
To modify Controller Networking settings for
the OCC drop only • 61
To reboot a Controller drop • 73
To reboot an I/O module • 159
To reboot the OCC • 180
To recover from a Controller failure during a
drop load operation • 178
To reformat the flash • 179
To replace Ovation Compact Controller
Electronics modules • 178
To select a Controller in the Controller
To set Controller parameters for the OCC •
52
To set the online Controller Restore Mode •
153
To uninstall the Communication Protocol
software • 86
To update your partner Controller in the
Controller Diagnostics window • 167
Troubleshooting and Maintenance • 177
Two-slot horizontal I/O Marshalling base • 15
U
Using Restore mode • 149
Using the Controller Diagnostics tool • 155
OW360_50 185

Compact Controller (OCC100) User Guide For Ovation 3.6.0 and Feature Pack 4 OW360 - 50

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Compact Controller (OCC100) User Guide For Ovation 3.6.0 and Feature Pack 4 OW360 - 50

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

Compact Controller (OCC100) User Guide For Ovation 3.6.0 and Feature Pack 4 OW360 - 50

Uploaded by

Copyright:

Available Formats

Compact Controller (OCC100) User Guide for Ovation

3.6.0 and Feature Pack 4

Emerson Process Management Power & Water Solutions, Inc.

1 Introduction to the Ovation Compact Controller 1

2 Hardware and software requirements for the Ovation Compact

3 Defining system addresses for the Ovation Compact Controller 37

4 Adding and configuring an Ovation Compact Controller 43

5 Configuring the OCC to use local Ovation I/O 75

6 Configuring the OCC to use embedded protocols 85

7 Configuring the OCC to use the ELC module 95

8 Configuring the OCC to use the Fieldbus module 107

9 Configuring the OCC to use the Profibus module 115

10 Configuring the OCC to use the Ethernet Remote Node

11 Configuring the OCC to use the DeviceNet module 131

13 Configuring the OCC to use the Digital Excitation Controller

14 Using Restore mode 149

15 Using the Controller Diagnostics tool 155

16 Troubleshooting and Maintenance 177

1 Introduction to the Ovation Compact Controller

What is the Ovation Compact Controller? ........................................................................... 2

1.1 What is the Ovation Compact Controller?

Figure 1: Ovation Compact Controller

1.2 Features of the Ovation Comp act Controller

1.2.1 Automatic failover control

1.2.2 Slot mismatch detection

1.3 How is the Ovation Compact Controller similar to a standard

 Supports non-redundant and fully redundant layouts.

 Supports standard I/O terminations and Marshalling terminations.

1.4 Definition of Terms for the Ovation Compact Controller

Terms used with the Ovation Compact Controller

Drop A term used to refer to a Controller, Workstation, or Database Server that is a

1.5 Reference documentation

2 Hardware and software requirements for the Ovation

Ovation Compact Controller components ........................................................................... 9

2.1 Ovation Compact Controller components

Figure 2: Example Ovation Compact Controller base configurations and connections

2.1.1 Controller base assembly

Figure 3: Controller Base drawing showing top and bottom view

The controller base assembly provides the following features:

2.1.2 Ovation Compact Controller module

The controller module includes:

Figure 4: OCC module front and top views

2.1.3 Two-slot horizontal I/O Marshalling base

The OCC two-slot I/O base has the following features:

2.1.4 Four-slot horizontal I/O base with standard terminations

The OCC four-slot I/O base has the following features:

2.1.5 Network interface ports

2.2 Pin assignments for pow er connectors

2.2.1 Power connectors for OCC base

The following table lists the pin assignments.

Pin assignments for 20-pin terminal block on Base

PIN NO. SIGNAL PIN NO. SIGNAL

9 PS STATUS 1A OK/ 9 PS STATUS 1B OK/

2.2.2 Power connector for two-slot Marshalling base

The following table lists the pin assignments.

Pin assignments for 20-pin terminal block on Two-Slot Marshalling Base

PIN NO. SIGNAL PIN NO. SIGNAL