Controller OCR1100 User Guide For Ovation 3.5

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

1.1 What is the OCR1100 Controller? ...................................................................................... 2
1.2 Features of the OCR1100 Controller .................................................................................. 3
1.3 Converting to the OCR1100 Controller ............................................................................... 4
1.4 What is automatic failover control? ..................................................................................... 5
2 Ovation Controller hardware 7

2.1 What are the Ovation Controller I/O interfaces? ................................................................. 7
2.1.1 Network Interface ports .......................................................................................... 7
2.1.2 I/O interface ports ................................................................................................... 9
2.1.3 What are Small Form-factor Pluggable transceivers (SFPs)? ............................. 10
2.2 Controller module components ......................................................................................... 10
2.2.1 What are the processor module status LEDs for the Controller? ........................ 11
2.2.2 What are the I/O Interface module status LEDs for the Controller? .................... 13
2.2.3 To open the Controller module front cover .......................................................... 14
2.2.4 To replace Ovation Controller module covers ...................................................... 15
2.2.5 To replace Controller modules ............................................................................. 15
2.3 Adding Ovation Controllers to WDPF Q-line I/O ............................................................... 16
3 Defining and addressing the I/O devices 17

3.1 What is an Ovation I/O module address? ......................................................................... 17
3.1.1 What is the addressing format for I/O modules?.................................................. 17
3.1.2 Examples of extended I/O cabinet module addresses ........................................ 19
3.1.3 Examples of Relay Output module addresses ..................................................... 20
3.1.4 Examples of remote node I/O cabinet module addresses ................................... 21
3.2 Q-Line I/O module addressing .......................................................................................... 22
3.3 What are the guidelines for positioning I/O modules in cabinets? .................................... 22
3.4 What types of I/O modules does an OCR1100 Controller support? ................................. 24
3.5 What changes can you make to an I/O device? ............................................................... 24
3.5.1 To modify an I/O device ....................................................................................... 24
3.5.2 To modify an external Ovation networks device .................................................. 25
3.6 Hardware address and I/O status values for Fault Code 66 ............................................. 25
3.7 I/O Status values for Fault Code 66 .................................................................................. 25
4 Starting the Controller 27

4.1 Verifying Controller hardware and power status ............................................................... 27
4.1.1 To verify Controller Hardware .............................................................................. 27
4.1.2 To power-up the Controller .................................................................................. 28
4.2 What procedures are needed after configuration changes to the Controller? .................. 29
4.2.1 To download Controller drop configuration .......................................................... 29
OW350_58 i
Table of Contents
4.2.2 To reboot a Controller drop .................................................................................. 31

4.2.3 To load a Controller drop ..................................................................................... 31
4.3 What is the process for planning the I/O for your system? ............................................... 32
4.4 What are the Ovation I/O module base types? ................................................................. 33
4.4.1 What is a standard I/O module base? .................................................................. 33
4.4.2 What is a relay output module base? ................................................................... 33
5 Configuring the Controller 35

5.1 Configuring the Controller software................................................................................... 35
5.2 What is the IP address of a Controller? ............................................................................ 36
5.2.1 To determine the IP address of a machine/drop .................................................. 36
5.3 Determining the NIC (network ethers) address of a drop ................................................. 36
5.3.1 To determine the NIC hardware address from the card label .............................. 36
5.3.2 To determine the NIC address from the error log ................................................ 36
5.4 What should a new Controller drop item contain? ............................................................ 37
5.4.1 To insert a new Controller drop ............................................................................ 37
5.4.2 To insert a new drop point.................................................................................... 42
5.4.3 To set Controller parameters ............................................................................... 44
5.4.4 To set existing control tasks ................................................................................. 46
5.4.5 To insert new control tasks .................................................................................. 48
5.4.6 To confirm Controller Networking (network item)................................................. 48
5.4.7 To modify Controller Networking (drop item) ....................................................... 50
5.4.8 To configure the Controller for Ethernet Remote Interface .................................. 52
5.5 Custom Controller Networking .......................................................................................... 54
5.6 Online Controller restore mode ......................................................................................... 55
5.7 Restore mode functions .................................................................................................... 56
5.7.1 Restore mode disabled (Default) ......................................................................... 56
5.7.2 Restore mode enabled (all drops) ........................................................................ 56
5.7.3 Restore mode enabled (redundant drops only) ................................................... 56
5.8 Restore mode performance issues ................................................................................... 57
5.9 Restore mode engineering limitations ............................................................................... 57
5.10 Restore mode point information issues ............................................................................. 58
5.10.1 To set the online Controller Restore Mode .......................................................... 58
5.11 What additional software configurations are needed for Controllers? .............................. 59
5.11.1 To configure alarm timestamping to the millisecond level ................................... 60
5.11.2 To map a 16-bit PLC register to a 16-bit packed point ........................................ 60
5.12 RADIUS Server ................................................................................................................. 61
6 Configuring Controller drivers 63

6.1 Controller driver overview ................................................................................................. 63
6.2 Configuring device drivers in the Controller ...................................................................... 63
6.2.1 To configure Ovation and Q-Line devices ............................................................ 63
6.2.2 To configure third-party devices ........................................................................... 64
ii OW350_58
Table of Contents
7 Local Ovation I/O drivers configuration 65

7.1 To insert new device numbers .......................................................................................... 65
7.2 To set Ovation device number parameters ....................................................................... 66
7.3 To insert local Ovation I/O devices ................................................................................... 67
7.4 To insert a new local Ovation I/O branch .......................................................................... 69
7.5 To insert a local Ovation I/O module ................................................................................. 69
8 Remote Ovation I/O drivers configuration 71

8.3 To insert remote Ovation I/O devices ............................................................................... 73
8.4 To insert remote Ovation I/O new nodes .......................................................................... 75
8.5 To insert a remote Ovation I/O new branch ...................................................................... 76
8.6 To insert a remote Ovation I/O module ............................................................................. 77
9 Local Q-Line drivers configuration 81

9.3 To insert local Q-Line devices ........................................................................................... 83
9.4 To insert a new local Q-line crate...................................................................................... 85
9.5 To insert a new local Q-line module .................................................................................. 85
10 Remote Q-Line driver configuration 89

10.3 To insert remote Q-line devices ........................................................................................ 91
10.4 To insert new remote Q-line nodes ................................................................................... 93
10.5 To insert a new remote Q-Line crate ................................................................................ 93
10.6 To insert a new remote Q-line module .............................................................................. 94
11 Allen-Bradley driver overview 97

11.1 What is an Allen-Bradley driver? ....................................................................................... 97
11.1.1 To insert new device numbers ............................................................................. 97
11.1.2 To insert an Allen-Bradley device ........................................................................ 98
11.1.3 To set Allen-Bradley device number parameters ................................................. 99
11.1.4 To configure Allen-Bradley points ...................................................................... 100
OW350_58 iii
Table of Contents
11.2 Allen-Bradley DF-1 commands supported by Ovation .................................................... 103

11.3 I/O access path examples for Allen-Bradley ................................................................... 104
11.4 Allen-Bradley analog input cards .................................................................................... 105
11.5 Allen-Bradley digital input cards ...................................................................................... 105
12 Foundation Fieldbus second generation (I/O modules) driver

configuration 107
12.1 To insert new device numbers ........................................................................................ 107
12.2 To set Foundation Fieldbus (I/O module) parameters .................................................... 107
12.3 To insert a Foundation Fieldbus I/O module in the Developer Studio ............................ 109
12.4 To add a module record point name ............................................................................... 110
12.5 To add a Foundation Fieldbus (I/O module) device ........................................................ 112
12.6 To assign a node record to each of your ports ............................................................... 115
13 GE Genius driver configuration 117

13.2 To set GE Genius device number parameters................................................................ 118
13.3 To insert a GE Genius device ......................................................................................... 119
13.4 What are I/O access path examples for GE Genius? ..................................................... 121
14 GE Mark V/VI/Ve driver configuration 123

14.2 To set GE Mark V/VI/Ve device number parameters ...................................................... 124
14.3 To insert a GE Mark V/VI/Ve device ............................................................................... 125
14.4 To configure GE Mark V/VI/Ve points ............................................................................. 126
14.5 What are I/O access path examples for GE Mark V/VI? ................................................. 130
15 MHI driver configuration 133

15.1 MHI driver overview ........................................................................................................ 133
15.1.1 To insert new device numbers ........................................................................... 133
15.1.2 To set MHI device number parameters .............................................................. 133
15.1.3 To insert an MHI device ..................................................................................... 135
15.1.4 To configure MHI points ..................................................................................... 135
15.2 I/O access path examples for MHI .................................................................................. 137
16 Modbus driver configuration 139

16.1 Modbus overview ............................................................................................................ 139
16.1.2 To set Modbus device number parameters ....................................................... 140
16.1.3 To insert a Modbus device ................................................................................. 141
16.1.4 To configure Modbus points ............................................................................... 142
iv OW350_58
Table of Contents
16.2 I/O access path examples for Modbus ............................................................................ 144
17 Profibus device driver configuration 147

17.1 Profibus overview ............................................................................................................ 147
17.1.1 To add a new I/O device number to the Controller using the Developer Studio 147
17.1.2 To insert a Profibus I/O module in the Developer Studio ................................... 149
17.1.3 To add a module record point name .................................................................. 152
17.1.4 To assign a node record to each of your ports .................................................. 154
18 RTP I/O driver configuration 157

18.2 To set RTP I/O device number parameters .................................................................... 157
18.3 To insert an RTP I/O device ............................................................................................ 159
18.4 To configure RTP I/O points............................................................................................ 159
18.5 I/O access path examples for RTP I/O ........................................................................... 162
19 Toshiba driver configuration 163

19.1 Toshiba driver overview .................................................................................................. 163
19.1.2 To set Toshiba device number parameters ....................................................... 163
19.1.3 To insert a Toshiba device ................................................................................. 165
19.1.4 To configure Toshiba points ............................................................................... 165
19.2 I/O access path examples for Toshiba ............................................................................ 167
20 External Ovation network driver configuration 169

20.1 External Ovation network devices overview ................................................................... 169
20.1.2 To set external Ovation network device number parameters ............................ 170
20.1.3 To insert external Ovation network I/O devices ................................................. 170
20.1.4 To map external Ovation network points ........................................................... 171
20.1.5 To reconfigure an external Ovation network driver ............................................ 172
21 Using the Controller Diagnostics tool 175

21.1 Controller Diagnostics tool .............................................................................................. 175
21.2 Software platforms that Controller Diagnostics supports ................................................ 176
21.3 Controller Diagnostics window ........................................................................................ 177
21.3.1 To access the Controller Diagnostics tool in a
Windows-based Ovation system ........................................................................ 178
21.3.2 To access the Controller Diagnostics tool in a
Solaris-based Ovation system ........................................................................... 178
21.3.3 Controller Diagnostics menu bar ........................................................................ 178
21.3.4 Controller Diagnostics toolbar ............................................................................ 179
21.4 Controller List in the Controller Diagnostics window ....................................................... 180
21.4.1 To select a Controller in the Controller Diagnostics window .............................. 180
OW350_58 v
Table of Contents
21.5 Controller Overview panel in the Controller Diagnostics window ................................... 182
21.6 Controller Diagnostics Update Backup function .............................................................. 183
21.6.1 To update your backup Controller in the Controller Diagnostics window .......... 183
21.7 Control Task Information tab in the Controller Diagnostics window ............................... 185
21.8 I/O Information tab in the Controller Diagnostics window ............................................... 187
21.9 What firmware can be downloaded to the I/O modules through the
Controller Diagnostics window? ...................................................................................... 188
21.9.1 To download firmware revisions to the I/O modules through the Controller
Diagnostics window ............................................................................................ 189
21.9.2 To reboot an I/O module .................................................................................... 190
21.10 Software Versions tab in the Controller Diagnostics window .......................................... 190
21.11 Point Details tab in the Controller Diagnostics window ................................................... 191
21.12 Sheet Information tab in the Controller Diagnostics window .......................................... 192
21.13 Refresh function for the Controller Diagnostics window ................................................. 193
Index 195
vi OW350_58
S E C T I O N 1
1 Introduction to the OCR1100 Controller
IN THIS SECTION
What is the OCR1100 Controller?....................................................................................... 2

Features of the OCR1100 Controller .................................................................................. 3
Converting to the OCR1100 Controller ............................................................................... 4
What is automatic failover control? ..................................................................................... 5
OW350_58 1
1.1 What is the OCR1100 Controller?
1.1 What is the OCR1100 Controller?
The Ovation Controller is a digital computer that is used in various industries for automated
process control. The Ovation Controller is a robust, sophisticated Controller that can handle
multiple inputs and outputs in real time.
Ovation Controllers can operate independently or paired with a partner or a redundant backup
Controller. Controllers are typically housed inside industrial cabinets and are typically part of a
control system comprised of several Controllers and several cabinets. Controllers communicate
with input / output modules (referred to as I/O modules) which are connected to field devices.
I/O modules monitor devices for changes that occur in the device's condition. The Controller
communicates with the I/O modules and when detecting a change (input), the Controller reads the
change and tells the device (output) to perform an appropriate action as determined by the
Controller. The Ovation Controller communicates with Q-Line I/O and Ovation I/O, as well as
select third-party I/O. (See the Q-Line Installation Manual and Ovation I/O Reference Manual.)
Controller actions are programmed into the Controller by control sheets (also known as functional
drawings) which are created in the Ovation Control Builder. Control sheets consist of building
blocks (algorithms) arranged in a logical pattern that defines in detail what action to take when
certain events occur in a device. These algorithms, linked by signals, can represent a simple two-
step process or can be a complex process made up of many algorithms contained on many
sheets.
The Ovation Controller is based on the Intel Atom processor and runs on a commercially available
operating system. The Controller uses an off-the-shelf interface to connect it to the Ovation
network.
Figure 1: Ovation Controller
2 OW350_58
1.2 Features of the OCR1100 Controller
The Controller executes modulating and sequential control strategies and supports the following
functions:
 Originates and receives process points.
 Adds, deletes, and modifies points on-line.
 Provides alarming and command word processing for originated points.
 Reads I/O modules and converts data to process points.
 Reads process points and writes data to I/O modules.
 Executes control algorithms.
 Adds, deletes, and modifies control online.
1.2 Features of the OCR1100 Controller
The Ovation Controller has the following features:

 Performance:
 OCR1100
 1100 Mhz Intel Atom Z510 processor.
 Serial and parallel I/O scanning options.
 Five control areas, each with selectable speeds (10ms — 30000ms or 30 seconds).
 256 MB DRAM memory (expandable to 1GB).
 128 MB (expandable to 2 GB) Compact Flash supports Western Digitals SiSmart
technology.
 Total point capacity of up to 32,000 points (depending upon your hardware and software
configuration):
 Total I/O point capacity of up to 4,778 originated points with full records.
These 4,778 I/O points can be any combination of the following:
 Direct-wired analog points.
 Direct-wired digital points.
 Direct-wired SOE points (maximum 1,024 SOE points per Controller).
Up to 8,192 virtual I/O points (2,048 X 4) for third party support.
Up to a maximum of 100 periodically assigned points per Controller.
 Meets industry standards:
 Portable software between hardware platforms.
 Easy to interface to third-party devices, such as:
 Allen-Bradley
 GE Mark V/VI
 Modbus
 RTP I/O
 Toshiba
 MHI
 GE Genius
OW350_58 3
1.3 Converting to the OCR1100 Controller
 Foundation Fieldbus
 External Ovation Network
 Easy to address technology obsolescence.
 Ability to quickly track advances in technology.
 Redundancy in case of failover:
 Redundancy for Controller cards.
 Controller supports a dual attached network configuration utilizing the onboard NIC ports.
 Redundant powering.
 I/O bus failure isolation.
 Watchdog functions.
 Configurable auto-restart function.
 Bumpless failover (secured by tracking algorithms).
1.3 Converting to the OCR1100 Controller
Transitioning to the OCR1100 Controller can be performed on any Ovation system.
The OCR1100 Controller is available on Ovation systems that are 3.5 and later. If you are
converting from an Ovation system with OCR161 or OCR400 Controllers, you must first upgrade
your system to the 3.5 Ovation software release.
Once upgraded to Ovation 3.5, the only hardware changes required to upgrade your OCR400
Controller to an OCR1100 is the actual replacement of the Controller. When converting from an
OCR161 controller to an OCR1100 controller additional hardware and software changes are
required.
Note: You can have a mix of OCR400 and OCR1100 Controllers on your 3.5 system; however,
the primary and partner Controllers must be matched with same type of Controller.
4 OW350_58
1.4 What is automatic failover control?
1.4 What is 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 backup processor of the failure. The
backup 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 Controller failure.
 I/O interface failure.
 Removal of power from the control processor.
 Control processor reset.
Once the control is passed to the backup 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 backup role. The
processor in control detects the presence of the backup processor and adjusts for redundant
operation.
CAUTION! To ensure failover capabilities in a pair of redundant Controllers, do the following:
You must configure the IOIC device driver.

You can then add up to seven additional devices to each Controller.
OW350_58 5
S E C T I O N 2
2 Ovation Controller hardware
IN THIS SECTION
What are the Ovation Controller I/O interfaces? ................................................................. 7

Controller module components ......................................................................................... 10
Adding Ovation Controllers to WDPF Q-line I/O ............................................................... 16
2.1 What are the Ovation Controller I/O interfaces?

Ovation Controllers provide various types of interfaces to communicate with the Ovation system
and other devices. These interfaces include:
 Ovation network
 Dedicated backup
 I/O devices
2.1.1 Network Interface ports
The Controller's processor module provides four network interface ports, labeled N1, N2, N3, and
N4. These ports are located at the top of the module housing.
Network interface ports
PORT SUPPORTS
N1 Used for third-party devices. This is an additional Ethernet interface for other uses, such as
third-party links, if necessary.
N2 Typically used for single attached networking to the Ovation network.
N3 Provides an additional Ethernet interface for dual attached networking.
N4 This is the default Ethernet interface for dedicated control synchronization or third-party
device.
OW350_58 7
PORT SUPPORTS
Note: When using direct connection (Port N4 to N4) control synchronization, make sure both
Controllers have control synchronization enabled and that the cable is attached before
performing a download, reboot, and load.
If a pair of redundant Controllers has been running with control synchronization enabled and
control synchronization is then disabled, disconnect the dedicated cable from the Controllers
before rebooting the Controllers with the new configuration.
Conversely, if a pair of redundant Controllers has been running with control synchronization
disabled and control synchronization is then enabled, connect the dedicated cable between the
Controllers after they have been running with the new configuration.
Note:
OCR400 Controllers are available in the following two groups:
G01 (64MB) implements N1, N2, N3, and N4 as the RJ-45 connectors.
G02 (128 MB) implements N1, N2, N3, and N4 as the RJ-45 connectors.
OCR1100 Controllers are available in the following two groups:
G01 (128 MB) implements N1, N2, N3, and N4 as the RJ-45 connectors.
G02 (128 MB) implements N1, N2, and N3 as the Small Form Factor Pluggable (SFP)
transceivers and N4 as a RJ-45 connector.
Only approved SFPs can be installed in the OCR1100 G02. Approved SFPs are listed in the
following Ovation drawing - 1X00832.
8 OW350_58
2.1.2 I/O interface ports
The Controller's I/O interface module supports up to 16 branches of local Ovation I/O, using ports
L1 and L2, physically located on the Controller Base Assembly, below the Controller. The
Controller also provides three RJ-45 interface ports to support additional local and remote I/O.
These ports are located at the top of the module housing and are labeled Q5, R4, and R3. The
port labeled Q5 supports up to four crates of local Q-Line I/O. Ports R3 and R4 are configured as
a pair. They can support three different options:
 Remote Ovation (R3/R4)
 Remote Q-Line (R3/R4)
 Local Q-Line (R4 only)
When configured for Ovation I/O, up to four nodes of remote Ovation I/O can be supported on
each port. Local Ovation I/O is not supported on either port.
When ports R3/R4 are configured for remote Q-Line, each port can support up to four nodes each
with four crates per node.
When configured for local Q-Line, R4 can support up to four crates (1 node) of local Q-Line, but
R3 must be unoccupied.
Note: Ports R3 and R4 can be configured as a pair to support either Ovation I/O or Q-Line I/O,
but not a mixture of the two. Port Q5 supports only local Q-Line I/O. Ports L1 and L2 only
support local Ovation I/O.
The following list shows the configuration options:

 Port L1 supports up to 8 local branches of local Ovation I/O.
 Port L2 supports up to 8 local branches of local Ovation I/O.
 Port Q5 supports up to 4 crates of local Q-Line I/O (1 node).
 Port R3 supports one of the following:
 Up to 4 nodes of remote Ovation I/O.
 Up to 4 nodes of remote Q-Line I/O.
 Port R4 supports one of the following:
 Up to 4 nodes of remote Ovation I/O.
 Up to 4 nodes of remote Q-Line I/O.
 1 node of local Q-Line I/O.
(Refer to the Q-Line Installation Manual and the Q-Line card types section in the Ovation I/O
Reference Manual for information about Q-Line modules.)
OW350_58 9
2.2 Controller module components
2.1.3 What are Small Form-factor Pluggable transceivers (SFPs)?
Small Form-factor Pluggable transceivers (SFPs) are compact pluggable transceivers used for
telecommunication and data communications. SFPs are used on the G02 OCR1100 Controller.
SFPs are inserted into designated Ethernet ports on the OCR1100 Controller.
There are 3 SFP Ethernet ports on the OCR1100 Controller and one copper RJ45 port.
Currently, there is only one approved SFP 100Base-FX unit. Refer to 1X00832 for additional
information on approved SFPs.
Note: Use of non-approved SFPs is not permitted on the Ovation system.
The OCR1100 G02 Controller ports are protected by factory installed dust covers. Dust covers
are removed prior to usage.
Replacement dust covers can be ordered as a separate item using the following part numbers:
 SFP dust cover - 1X00828H04
 RJ45 dust cover - 5A26371H95
The Ovation Controller is comprised of two main modules:
Processor Module
IOIC Module
Processor Module: This module communicates with the Ovation network and provides nine
indicator LEDs that display information about the status of network communication.
The OCR1100 processor has two Groups:

 5X00481G01 - Offers four copper RJ45 Ethernet ports. The Group 1 processor is used to
provide a copper network interface to the Controller.
 5X00481G02 - Offers one copper RJ45 and three Small Form factor Pluggable (SFP)
Ethernet ports. The G02 processor is used to provide a fiberoptic network interface to the
Controller.
IOIC Module: This module communicates with I/O devices and provides ten indicator LEDs that
display information about the status of I/O communication.
 5X00228G01 - The IOIC module is paired with the Processor module.
You can monitor the OCR1100 Controller by observing the LEDs on the Controller modules.
These LEDs indicate if the Controller is communicating successfully with the Ovation network and
with the I/O devices.
The Controller uses a processor module to communicate with the Ovation network and an I/O
interface module to communicate with the I/O devices.
10 OW350_58
2.2.1 What are the processor module status LEDs for the Controller?
The Controller processor module (left side of Controller) provides nine indicator LEDs that display
status information about the interface between the Controller and the Ovation network.
There is a green power indicator (labeled P) and a pair of green and amber LEDs for each
Ethernet port (labeled N1, N2, N3, and N4). The green power indicator lights when the Processor
module is powered. Each Ethernet network port has two indicator LEDs (green and amber).
The green indicator is the Link Integrity/Power LED and lights when the port is receiving power
and flashes slowly when the module is linked with the network through that port.
The amber indicator displays Link Activity status and flashes when the module is receiving or
transmitting data on that port.
Controller Module IOIC Module
Figure 2: Processor module status LEDs
Processor module status LEDs
LED ME ANING ON OFF BLINKING
P Power Lights green when Unlit when module N/A

module is powered is not powered
N1 Ethernet port Port is receiving Port is not receiving Module is linked to
green LED power power network through the
(Link Integrity/Power LED) port
OW350_58 11
LED ME ANING ON OFF BLINKING
Ethernet port N/A N/A Module is receiving or

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

powered powered
Cm Comm. Communications No commands being Commands being received from
hung received from the the Processor module
Processor module
Ct Control Controller acting Controller not Controller acting as secondary
as primary operational, in boot-
up, or cleared
A Alive Alive Alive timer timed out N/A
(under hardware
control)
OW350_58 13
STATUS
LABE L ME ANING ON (SOLID) OFF BLINKING
E Error Performing Application firmware An error is indicated. Read error

diagnostics running. No errors. code from node LEDs or GMD.
during boot
sequence
Node LED
O1 local Ovation All I/O cycles No I/O cycles are Some or all I/O cycles are failing
#1 (port L1) succeeding (with being attempted (with (with "E" LED off)
"E" LED off) "E" LED off)
O2 local Ovation All I/O cycles No I/O cycles are Some or all I/O cycles are failing
#2 (port L2) succeeding (with being attempted (with (with "E" LED off)
R3 Port R3 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
succeeding (with being attempted (with (with "E" LED off)
R4 Port R4 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
Q5 Port Q5 All I/O cycles No I/O cycles are Some or all I/O cycles are failing
A Controller fault is indicated when the red E LED is blinking. In this state, the Node LEDs (01, 02,
R3, R4, and Q5) blink the actual error code as two separate binary numbers followed by a 3-
second pause (all node LEDs off, 00000). This sequence repeats as long as the error state
persists. Open the GMD (General Message Display) for an actual readout of the error code in
hexadecimal.
For Ovation 3.5 and later releases, the fault codes are part of Ovation software and are displayed
in the Ovation System Viewer application. Refer to the Operator Station User Guide for additional
information.
2.2.3 To open the Controller module front cover
WARNING! Ovation Controller modules have front covers that protect the Controller internal
components. The Controller module cover must remain in place to protect the internal
electronics from accidental damage. Only qualified technicians should open these modules.
Power-down the Controller before opening module covers.
Occasionally, you may need to open a Controller Processor module cover to replace the flash
disk.
1. Power-down the Controller before opening the module cover.

2. Place your fingertips on top of the Processor module cover (since the IOIC module overlaps
the Processor module, you might need to remove the IOIC module first).
14 OW350_58
3. Push down slightly to release the plastic latches from their stops in the top of the Processor
module case.
Note: The blue corner latches secure the module to the backplane. They are not used to
release the module covers.
4. Pivot the cover back and remove it from the Processor module case.
5. Perform the desired operation and replace the Processor module cover.
2.2.4 To replace Ovation Controller module covers
Note: Since the IOIC module overlaps the Processor module, you need to re-install the
Processor module cover first.
1. Power-down the Controller before replacing module covers.

2. Position the bottom latches of the Processor module cover into the module case.
3. Pivot the top of the cover into position while applying slight downward pressure so the top
module cover latches engage with the module body.
Note: The blue corner latches secure the module to the backplane. They are not used to
release the module covers.
4. Push the top of the cover in toward the module body until the latches snap into their locking
position.
5. Repeat these steps for the IOIC module cover, if necessary.
2.2.5 To replace Controller modules
Note: If you need to replace a module in the Controller, you must remove the IOIC module first.
When you re-install the modules, you must install the Processor module first.
1. Determine what Controller module needs to be replaced (Processor or IOIC module).

2. Power-down the Controller before replacing modules.
CAUTION! Controllers must be powered down before removing or replacing modules.
3. Unlatch the blue corner latches on the module case.

4. Remove the old module from the Controller backplane.
5. Install the new module in the Controller backplane.
6. Use the blue corner latches on the module to secure it to the Controller backplane.
OW350_58 15
2.3 Adding Ovation Controllers to WDPF Q-line I/O
2.3 Adding Ovation Controllers to WDPF Q -line I/O
When OCR400 or OCR1100 Controllers are added to a WDPF control system that utilizes Q-Line
I/O, two QOL cards are required to provide connectivity, one QOL connected to each Controller.
On Q-line systems, connections were previously done by the QBE or the QOR card. QOL cards
typically occupy the QBE slot or the 13th slot in the upper and lower Q-crates in a standard
WDPF "A" or extended "A" cabinet. QOL cards replace the first and last QBE cards in the Q-
Crates. Refer to drawing number 5X00252 for additional information.
The Controller treats local Q-Line as if it were remote Q-Line without the conversion to fiber-optic
media. The 13V power supply voltages are not directly connected to the Controller. The QOL
monitors the 13V power supplies and provides a status bit to the Controller. This is similar to the
way Remote Q-Line and the QOR card provide status for remote Q-Line. Both provide status bits
in board registers which are read by the Controller.
The QOL makes local Q-Line into remote Q-Line but only provides a short distance copper
connection instead of fiber optic so the Controller does not notice this minor difference.
The migration kit wiring diagram 4D33960 shows a 2-connector cable connected to the PCQL
module which was where the 13V power was monitored and status provided for the Controller.
The I/O interface on the Controller does not have this 13V connection capability so instead the
status is read from the QOL.
Two QOL cards (5X00230) are used for local Q Line I/O.
 QOL combines MAU and QOR functionality while eliminating the FO cable that is “Local
Remote” Q-Line.
 Replaces QBEs in Q1 and Q4 Q-Crate 13th slots.
 For single Q-crate applications, both QOL's are housed in the same Q-crate.
16 OW350_58
S E C T I O N 3
3 Defining and addressing the I/O devices
IN THIS SECTION
What is an Ovation I/O module address? ......................................................................... 17

Q-Line I/O module addressing .......................................................................................... 22
What are the guidelines for positioning I/O modules in cabinets? .................................... 22
What types of I/O modules does an OCR1100 Controller support? ................................. 24
What changes can you make to an I/O device? ............................................................... 24
Hardware address and I/O status values for Fault Code 66 ............................................. 25
I/O Status values for Fault Code 66 .................................................................................. 25
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 Controller and is used by the Ovation Developer Studio to configure the hardware
information for a point.
A standard I/O base consists of two logical modules; and a relay output base has one logical
module.
3.1.1 What is the addressing format for I/O modules?
The logical I/O address is composed of three numbers (four when remote I/O is used) separated
by decimals and in the following format:
 D.N.B.S where:
D = Device number assigned to the Controller's IOIC
N = Node (only used in Remote I/O; 1 through 8).
B = Branch (1 through 8).
S = Slot where module is located (1 through 8 for Ovation I/O).
(1 through 12 for Q-Line I/O).
OW350_58 17
 Standard I/O base assemblies

The I/O addressing for the Ovation database is determined from the positions of the bases
installed in the cabinets. Installation of standard I/O bases requires at least two I/O module
addresses on a branch. Their I/O module position must always start on odd positions.
I/O modules should always be installed in the left-most branch of each side of a cabinet from the
TOP down to the BOTTOM. I/O modules in the right-most branch of each side of a cabinet are
addressed from the BOTTOM up to the TOP.
Emerson Process Management recommends that all bases (typically four) be installed in the right
side of a cabinet, even if the bases are not all filled with I/O modules. This prevents disruption of
the database if additional I/O modules are installed in the future.
 Relay output base assemblies
Relay Output bases can be located before or after standard I/O bases. Installation of relay output
bases requires one I/O module address on a branch and can begin on an odd or even position.
Note: Physical cabinet space may limit the maximum number of bases in a given cabinet style.
When a relay output base is used before a standard I/O base, an even number of relay output
bases must be used so the I/O base starts at an odd position. If a standard I/O base follows an
odd number of relay output bases, the configuration is incorrect and does not work (see the
following figure for examples).
Figure 4: I/O and Relay Output module configuration examples
18 OW350_58
3.1.2 Examples of extended I/O cabinet module addresses
Note: ROP transition panel is used when configuring cabinets (front of cabinet).
Figure 5: I/O Address examples, modules D, E, F (extended I/O cabinet)

 Module D address = 1.5.6.
 Module E address = 1.6.1.
 Module F address = 1.8.8.
OW350_58 19
3.1.3 Examples of Relay Output module addresses
Figure 6: I/O address examples, modules I , J, K (Relay Output modules)
Note: ROP transition panel is used when configuring cabinets (front of cabinet). Branch 7 (back
of cabinet) is composed solely of relay panels using RRP and RRB transition panels. (See
Ovation I/O Reference Manual.)
IOIC module for the Controller.

 Module I address = 1.5.3.
 Module J address = 1.6.2.
 Module K address = 1.7.6.
Note: The back of the extended cabinet contains only one branch of Relay Output modules due
to physical limitations.
The Relay Output modules can also be used with the RRP and RRB transition panels (instead of
the ROP or TND panel). Using the RRP and RRB transition panel allows one “branch” of up to
eight relay bases to be housed in a single side of an Ovation ventilated extended cabinet in two
columns of four bases.
20 OW350_58
3.1.4 Examples of remote node I/O cabinet module addresses
The Node address (1 through 8) for Ovation remote I/O is determined by where the node is
connected to the MAU Attachment Unit (located in the Controller cabinet). The Node Selector
Switch in the Remote Node Cabinet is then set to match the connection position. See the Ovation
I/O module addressing (see page 17) section of the Ovation I/O Reference Manual for details
about addresses for remote nodes.
The Node is in MAU position 1 for the following examples:

 Module G address = 1.1.1.3.
 Module H address = 1.1.3.5.
OW350_58 21
3.2 Q-Line I/O module addressing
3.2 Q-Line I/O module addressing
The address for Ovation modules is determined by the location of the module in the I/O cabinet.
However, the address for a Q-Line card is determined by the jumper settings on the actual Q-Line
card. A visual inspection of the card should be performed to determine the jumper settings. (See
Q-Line Installation Manual.)
Q-Line QBO modules are used to perform DIOB testing. The QBO card is addressed by entering
it in hexadecimal format into a dialog box. The box appears when a Q-Line module is defined and
configured through the Developer Studio.
Figure 7: Insert New Q-Line Module Wizard
3.3 What are the guidelines for positioning I/O modules in cabinets?
When selecting module positions, observe the following guidelines:
 The position of the module in the cabinet determines the address of the module.
 Placement of I/O modules are from top to bottom on the left side of a cabinet and from
bottom to top on the right side of a cabinet.
 If Relay Output modules are mixed with standard I/O modules on the same branch, always
start the standard I/O module base in an odd-numbered module position on the branch
(positions 1/2, 3/4, 5/6, or 7/8).
Relay Output modules can be placed in odd or even numbered positions. For example,
modules can begin in 1, 2, 3, 4, 5, 6, 7, or 8 slots.
22 OW350_58
3.3 What are the guidelines for positioning I/O modules in cabinets?
 Physical cabinet size and branch power requirements may limit the number of modules that
can be configured in a branch.
Figure 8: Examples of cabinet with standard I/O and relay modules
OW350_58 23
3.4 What types of I/O modules does an OCR1100 Controller support?
3.4 What types of I/O modules does an OCR1100 Controller support?
The Ovation OCR1100 Controller contains one IOIC module. This module provides ports that
connect to and support the following I/O module locations:
 Local Ovation I/O connects through ports L1 and L2.
 Remote Ovation I/O connects through IOIC ports R3 (nodes 0 through 3) and R4 (nodes 4
through 7).
 Local Q-line I/O connects through IOIC ports Q5 (DIOB 0) and R4 (DIOB 1).
 Remote Q-line I/O connects through IOIC ports R3 (nodes 0 through 3) and R4 (nodes 4
through 7).
One OCR1100 Controller can support the following I/O modules in various combinations:
 Maximum of 128 local Ovation I/O modules.
 Maximum of 512 remote Ovation I/O modules.
 Maximum of 96 local Q-line I/O cards.
 Maximum of 384 remote Q-line I/O cards.
Observe the following combination rules:
 If you connect to remote Q-line I/O, you cannot connect to remote Ovation I/O. You can
connect to local Q-line through port Q5 (DIOB 0).
 If you connect to remote Ovation I/O, you cannot connect to remote Q-line I/O. You can
connect to local Q-line through port Q5 (DIOB 0).
 If you use both ports Q5 and R4 to connect to local Q-line I/O, you cannot connect to any
remote I/O. You can always connect to local Ovation I/O.
Note: Refer to the Planning Your Ovation System manual for more information.)
3.5 What changes can you make to an I/O device?
After an I/O device has been created and loaded to the target drop, it may be necessary to make
changes.
You can make changes to the following:

 I/O devices (see page 24).
 External network devices (see page 25).
3.5.1 To modify an I/O device
After an I/O device has been created and loaded to the target drop, it may be necessary to make
changes.
1. Launch the Ovation Developer Studio.

2. Use the system tree to navigate to the I/O Devices folder:
Systems > Networks > Units > Drops > I/O Devices
3. Right-click the appropriate item.
4. Select Open.
5. Make necessary changes in the dialog box and select Ok or Apply.
24 OW350_58
3.6 Hardware address and I/O status values for Fault Code 66
3.5.2 To modify an external Ovation networks device
For external networks modification information, see Ovation Multiple Networks User Guide.
3.6 Hardw are address and I/O status values for Fault Code 66
The following tables apply to the hardware addresses for Fault Code 66 (Fault ID B).
Note: All fields are 0 based. These tables only apply to IOIC Devices.
Hardware address decoding tables
MODULE ACCESS (BIT 13:0)
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 Node Branch Module Offset
N O D E A C C E S S ( B I T 1 3 :1 , B I T 7 :1 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 Node 1 Offset
GROUP WRITE TO M O D U L E S ( B I T 1 3 :1 , B I T 7 :0 , B I T 8 :0 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 0 0 Offset
GROUP WRITE TO N O D E S ( B I T 1 3 :1 , B I T 7 :0 , B I T 8 : 1 )
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
1 1 0 Offset
3.7 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).
I/O Status values
BIT DEFINITION
0x0000 Local: No response from module
OW350_58 25
3.7 I/O Status values for Fault Code 66
BIT DEFINITION
0x0800 Remote: Echo: No response

0x0a00 Remote: Node: No response
0x0e00 1
Remote: Transmit collision
0x2000 Local: Bad CRC
0x2800 1
Remote: Echo: Bad CRC
0x2a00 Remote: Node: Bad CRC
0x2e00 Remote: I/O control register changed
0x4000 Local: Module in attention
0x4c00 Remote: Node in attention
0x4e00 Remote: PCRR internal error
0x6000 Success
0x6200 1
Remote: Echo: Wrong SRC
0x6400 Remote: Node: Wrong SRC
0x6800 1
Remote: Echo: Wrong DST
0x6a00 Remote: Node: Wrong DST
0x6c00 Remote: Node: Invalid response
0x0180 IOIC board not in control
0x0190 Q-line DIOB volts bad
0x00a0 Illegal access type
0x00b0 Illegal hardware address
0x00c0 Point not scanned yet
0x00d0 I/O cycle hung
0x00e0 Remote I/O type unknown
0x01f0 Third-party I/O Driver error (for example, invalid GE Mark V/VI tables)
0x6010 Error checking for SOE Events
0x6020 Readback failed or Card OK Bit not set
0x6130 DIOB test failed
1
Consider updating PCRR board (3A99190G01) to Revision 14 (per DEO 57211).
Note: Bit 0x8000 could also be set in any of these codes.
Local I/O statuses indicate a problem in the local 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.
26 OW350_58
S E C T I O N 4
4 Starting the Controller
IN THIS SECTION
Verifying Controller hardware and power status ............................................................... 27

What procedures are needed after configuration changes to the Controller? .................. 29
What is the process for planning the I/O for your system? ............................................... 32
What are the Ovation I/O module base types? ................................................................. 33
4.1 Verifying Controller hardw are and power status
Use the following procedures to start an Ovation Controller:

 Verify that the hardware is installed properly.
 Apply power to start the Controller (see page 28).
Note: If desired, you can cut off power to the entire cabinet by shutting off both circuit breaker
switches on the power supply modules in the back of the cabinet. If the Controller has Q-line
I/O, the power supplies are accessed from the front of the cabinet. Locate the power supplies,
and shut off the circuit breakers.
4.1.1 To verify Controller Hardware

1. Confirm that the power switch on the Controller is in the OFF (0) position. This shuts off
power to the Controller cards.
OW350_58 27
4.1 Verifying Controller hardware and power status
2. Confirm that the power cable is attached to the power plug connector.
Figure 9: Controller modules
3. If applicable, confirm that network cables are properly connected between the I/O Interface
module and any off-cabinet I/O devices.
4.1.2 To power-up the Controller

1. Turn on the power supplies by placing the ON/OFF breaker switches to the ON (1) position.
Verify that the LED indicator on the Controller power supply module lights.
Note: Power-up redundant Controllers one at a time. The first one powered takes control.
2. Turn on the Controllers by placing the ON/OFF power switches to the ON (1) position.
28 OW350_58
4.2 What procedures are needed after configuration changes to the Controller?
4.2 What procedures are needed after configuration changes to the

Controller?
You must perform the following procedures after any configuration changes are made to the
Controller.
Use the Developer Studio to perform these procedures:
 Download changes to the Controller (see page 29).
 Reboot the Controller (see page 31).
 Load the Controller (see page 31).
Note: When using the direct connection (Port N4 to N4) Control Synchronization for the
Controller, make sure that both Controllers have Control Synchronization enabled and that the
cable is attached before performing a download, reboot, and load.
If a pair of redundant Controllers has been running with Control Synchronization enabled and
Control Synchronization is then disabled, disconnect the dedicated cable from the Controllers
before rebooting the Controllers with the new configuration.
Conversely, if a pair of redundant Controllers has been running with Control Synchronization
disabled and Control Synchronization is then enabled, connect the dedicated cable between the
Controllers after they have been running with the new configuration.
4.2.1 To download Controller drop configuration
Note: The Download command must be performed any time configuration and software
changes have been made to a Controller drop.
1. Access the Ovation Developer Studio.

2. Use the system tree to navigate to the Drops folder:
Systems > Networks > Units > Drops
3. Right-click the appropriate Controller drop item.
4. Select Download from the pop-up menu.
Note: The Download function can also be executed on a System, Network, and Unit item when
multiple drops are to be downloaded (Refer to the Ovation Developer Studio User Guide.)
5. For redundant Controller drop configurations, the Download Wizard appears.

6. Select a drop from the window. The Download Preview dialog box appears and lists any files
that may have been altered during drop configuration and software changes.
OW350_58 29
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.
7. Select which files should be included in the Download process. The following figure illustrates
an example of the files included in the download process.
Figure 10: Download preview dialog box
8. Place a check next to the Download option and click Ok.
Download preview dialog box descriptions
SELECTION DESCRIPTION
Query Results The top left check box selects or deselects all of the files in the preview list.
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, check

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.
9. Reboot the Controller drop.
30 OW350_58
4.2.2 To reboot a Controller drop
Note: In most cases, the Reboot command should be executed immediately following the
completion of the Download command. This may not always be completely necessary, but it is a
safe and recommended practice.

2. Use the system tree to navigate to the Drops item:
3. Right-click the appropriate Controller Drop item.
4. Select Reboot from the pop-up menu.
5. For redundant Controller drop configurations, the Reboot Wizard appears.
6. Select the same Controller drop that was chosen for the download. A confirmation dialog box
appears.
Figure 11: Reboot confirmation dialog box
7. Click Yes to close the window and execute the reboot process.
4.2.3 To load a Controller drop
The Load function is necessary anytime changes have been made relating to points or control. If
a new drop point was inserted in you should execute the load command immediately following the
completion of the Reboot command.
Note: The Load function is also required when Controller device drivers (Configuring Ovation
Drivers (see page 63)), that have been configured with I/O points, are either deleted or changed.
This would also require the deletion of the existing points and execution of the Clear command
as well. (Refer to the Ovation Developer Studio User Guide.)

3. Right-click the appropriate Controller Drop item.
4. Select Load from the pop-up menu.
5. For redundant Controller drop configurations, the Select a drop to load dialog box appears.
6. Select the same Controller drop that was rebooted. The load process executes.
OW350_58 31
4.3 What is the process for planning the I/O for your system?
Note: You can choose to see a Load Preview window before you load. Refer to the Ovation
Developer Studio User Guide for more information.
7. Repeat the Download, Reboot, and Load procedures for the partner drop in redundant
Controller drop configurations.
4.3 What is the process for planning the I/O for your s ystem?
The Ovation Distributed Control System provides modulating control, sequential control, and data
acquisition for a variety of system applications. This system consists of a configurable mix of
functional input/output (I/O) modules that communicate on the I/O bus to the Ovation Controller.
I/O modules provide an interface between the Ovation Controller and the processes in the plant.
Ovation I/O modules are “plug-in” components with built-in fault tolerance and diagnostics. They
are able to operate on a wide range of signals and perform a multitude of functions.
The Developers Studio I/O (input/output) Devices folder contains tools used to define the I/O
modules for the Ovation system. The I/O Device folders contain Setup Wizards and dialog boxes
that provide visual representation of the I/O devices for an Ovation system.
Before the I/O devices folder can be used to define the I/O hardware, you need to secure the I/O
plan for your Ovation system.
After securing the plan, the information is entered into the I/O Devices portion of the system
hierarchy to define the I/O for your Ovation system. I/O Devices are defined individually for each
drop.
During configuration, the following elements are assigned point names by the system to identify
the elements to the Ovation database:
 Each remote node is assigned a Node (RN) record type point name. The RN record type is
used because it contains bits that are used to monitor the node power supply.
 Each Ovation I/O module is given a Module (RM) record type point name. The RM point is
used to configure the I/O module and to provide status/alarm information about the I/O
module. Points can then be assigned to each module by using the Hardware tab in the Points
folder. Refer to the Ovation Record Types Reference Manual for additional information.
32 OW350_58
4.4 What are the Ovation I/O module base types?
4.4 What are the Ovat ion I/O module base types?
Ovation I/O bases house the Ovation I/O modules and provide a mechanism for you to run field
wiring and connect field signals to the Ovation I/O. Series of bases can be connected together to
form a “branch” of Ovation I/O.
The Ovation system supports two different types of bases:

 Standard I/O base.
 Relay Output base.
Bases can be mixed within a given I/O branch and cabinet. There are restrictions as to how these
bases can be mixed. (See Planning Your Ovation System.)
Figure 12: Standard I/O and relay output bases
4.4.1 What is a standard I/O module base?
A standard Ovation I/O base houses up to two standard Ovation I/O modules. Standard Ovation
I/O modules are designed to fit securely into the standard I/O bases.
Each standard I/O module is assigned a logical address. Since each standard I/O base can house
two Ovation I/O modules, a standard I/O base occupies two logical module addresses.
4.4.2 What is a relay output module base?
The relay output base houses one module and requires one I/O address. Although the relay
output base only contains one module, it is 1.5 times longer than the standard I/O module base
to allow additional space to house the relays.
OW350_58 33
S E C T I O N 5
5 Configuring the Controller
IN THIS SECTION
Configuring the Controller software ................................................................................... 35

What is the IP address of a Controller? ............................................................................ 36
Determining the NIC (network ethers) address of a drop ................................................. 36
What should a new Controller drop item contain? ............................................................ 37
Custom Controller Networking .......................................................................................... 54
Online Controller restore mode ......................................................................................... 55
Restore mode functions .................................................................................................... 56
Restore mode performance issues ................................................................................... 57
Restore mode engineering limitations ............................................................................... 57
Restore mode point information issues ............................................................................. 58
What additional software configurations are needed for Controllers? .............................. 59
RADIUS Server ................................................................................................................. 61
5.1 Configuring the Controller softw are
Use the following steps to set up a new Controller or pair of Controllers:
1. Determine the IP address of a machine/drop (see page 36).

2. Determining the NIC (network ethers) address (see page 36).
3. Insert a new Controller drop (see page 37).
4. Insert a new drop point (see page 42).
5. Set Controller parameters (see page 44).
6. Set existing control tasks (see page 46).
7. Insert new control tasks (see page 48).
8. Confirm Controller networking (network item) (see page 48).
9. Configure Online Controller Restore Mode (see page 55), when using the Online Controller
Restore Mode function.
OW350_58 35
5.2 What is the IP address of a Controller?
5.2 What is the IP address of a 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 Internet has a unique IP address.
You need to determine and record the IP address that is assigned to the Controller. These
numbers are needed for the configuration (when inserting a drop).
The system administrator typically assigns these addresses. The addresses can also be assigned
to be any valid range as long as the network is isolated from any other networks, such as the
Internet.
5.2.1 To determine the IP address of a machine/drop

1. Click Start.
2. Open the Programs icon.
3. Double-click the Command Prompt icon.
4. Enter ipconfig in the dialog box.
5. Press Enter.
6. Copy the IP address needed for the configuration.
5.3 Determining the NIC (netw ork ethers) address of a drop
A NIC (Network Interface Card) resides in the cabinet of a Controller or workstation. You need to
obtain and record the NIC address (either from the card or as assigned) for proper Ovation
Controller software configuration.
Note: The Controller supports a dual attached network configuration utilizing the onboard NIC
ports.
5.3.1 To determine the NIC hardware address from the card label
1. The OCR1100 controller has a label containing the complete NIC hardware address. Obtain
the address from this label.
2. The address consists of six hexadecimal octets separated by colons as shown in the following
example:
xx:xx:xx:xx:xx:xx
3. Record this address – it is needed for Controller configuration.
5.3.2 To determine the NIC address from the error log

1. Confirm that the power switch on the Controller is in the Off (0) position.
2. Check that all the network cables are connected.
3. Ensure that the Power Supply is ON.
4. Turn the power switch to the ON position (1) for the Controller whose NIC card address is
needed. The LED on the Controller Power Supply module lights steadily. If more than one
Controller is turned on, the addresses display in the order that the Controllers are turned on.
36 OW350_58
5.4 What should a new Controller drop item contain?
5. To view the hardware addresses, look at the Ovation Error Log by selecting Start > Ovation
> Error Log.
6. Begin with the bottom of the list (most recent entries) and scroll backwards until you locate
the following message:
Hardware Address not found xx:xx:xx:xx:xx:xx.
7. Record the address that is displayed in the message; this address is needed for Controller
configuration.
5.4 What should a ne w Controller drop item contain?
A new <DROP#> item appears under the Drops item of the Ovation Developer Studio system
tree. Since the newly created drop has been designated for a Controller, it should contain the
following items:
Configuration > Points > I/O Devices > Control Components > Control Tasks > Holding
Registers
Figure 13: New Controller <Drop#> item
5.4.1 To insert a new Controller drop
Note: Verify that the software is properly configured before starting the Ovation Controller.

3. Right-click Drops.
4. Select Insert New from the resulting pop-up menu. The Insert New Drops Wizard appears.
5. Provide the following information:
a) Enter the new drop number in the Drop ID field.
b) Enter the partner (drop) ID (if applicable).
c) Select the Controller option from the Drop type pull-down menu.
Insert new drops wizard
FIELD DESCRIPTION
Drop Id Controller drop number. Valid entries are 1-254.
Partner Id Identifies the drop ID of the partner drop.
OW350_58 37
FIELD DESCRIPTION
Drop Type Allows the choice of drops: Controller, SimController, Advanced Controller,
Advanced SimController, Virtual Controller, or Advanced Virtual Controller.
38 OW350_58
6. After the required information is provided, press the Finish button. The New Drops dialog
appears showing the Config tab.
Figure 14: New Drops dialog box
OW350_58 39
New Drops dialog box descriptions
FIELD DESCRIPTION
Drop Type Deals specifically with the Controller selection from the pull-down menu.
Choices are: Controller, SimController, Advanced Controller, Advanced
SimController, Virtual Controller, or Advanced Virtual Controller.
Controller Type Choose the correct Controller type. - (OCR400 or OCR1100)
Control Available when a primary and partner Controller are inserted and allows both
Synchronization Controllers to be automatically synchronized.
You can choose whether to have information sent over a dedicated cable or over the
Ovation network by making one of the following selections:
 Ovation Network
 Dedicated Cable
By default, the Dedicated Cable option is enabled. When possible, the Dedicated
Cable option is recommended to alleviate network traffic.
Maximum Point Selects the maximum number of points that the Controller can be configured to
Limit monitor.
Due to the way points are indexed, the actual point number is the maximum point
count minus 1.
Normal handles up to 6000 points. (Actual limit = 5,999)
Expanded handles up to 16,000 points. (Actual limit = 15,999)
32000 handles up to 32,000 points. (Actual limit = 31,999)
Note: Additional shared memory may be required to accommodate additional points.
Radius Server Provides user authentication and authorization. Refer to the Managing Security User
Guide for more information.
Primary & Partner When the primary/partner configuration is not used, no information input is required in
Section the partner section.
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. They can also be
assigned to be any valid range if the network is isolated from other networks (such
as, the Internet).
Ovation Network The format for the hardware address is:
Ethers Address
xx:xx:xx:xx:xx:xx (where the last four numbers (xx:xx) are typically located on a
label on the NIC).
If the hardware address cannot be located on the NIC, see Determining NIC
Addresses.
Ovation Highway Ethernet interface that connects the Controller to the Ovation Network.
Interface
(Automatically selected)
(Znyx, Onboard)
40 OW350_58
FIELD DESCRIPTION
Ovation Highway Type of NIC card connection.

Connection
(Single, Dual)
NIC Interface Automatically selected by the system. Name of physical port that the Ethernet cable
is connected.
(N1) - used for third-party Ethernet interface
(N2) - used for Single Ethernet
(N3) - used for Dual or third-party Ethernet interfaces
(N4) - used for Dedicated control synchronization cable or third-party Ethernet
interfaces)
Ovation Highway Displays speed in (Mbps megabits per second) at which the Controller connects to
Interface Mode the network.
100 Mbps / full duplex
Backup NIC Automatically selected by the system.
Interface
(N1 - N4)
(Available if a
backup NIC is
used.)
Control The Controller software is configured to automatically run control synchronization of
Synchronization redundant Controllers over the network.
Interface
(N1 - N4)
Note: The Controller allows direct connection (port N4 to N4) and synchronization of
redundant Controllers. This connection allows for faster and safer Controller
synchronization.
When using the direct connection (Port N4 to N4) Control Synchronization, make
sure that both Controllers have Control Synchronization enabled and that the cable
is attached before performing a download, reboot and load.
If a pair of redundant Controllers has been running with Control Synchronization

enabled and Control Synchronization is then disabled, the dedicated cable should be
disconnected from the Controllers before rebooting the Controllers with the new
configuration.
Conversely, if a pair of redundant Controllers has been running with Control

Synchronization disabled and Control Synchronization is then enabled, the
dedicated cable should be connected between the Controllers after they have been
running with the new configuration.
Control Displays speed in (Mbps megabits per second) at which the Controller connects to
Synchronization the network.
Interface Mode 10 Mbps / half duplex
100 Mbps / half duplex
auto-negotiate
Control Automatically entered by the system.
Synchronization
Interface IP
Address
OW350_58 41
FIELD DESCRIPTION
Ethernet Remote Typically used for NumaLogic I/O. See To configure the Controller for Ethernet
Interface Remote Interface (see page 52).
Network Port (N1 - N4) Specifies the port where the Controller will be physically connected the
Ethernet I/O network.
IP Address Displays the IP Address associated with the selected port.
DHCP Enabled Yes / No Allows you to enable or disable auto addressing. This is set to Yes by
default.
Subnet Mask Automatically entered by the system. Used on the primary and backup Controller
Ethernet interface.
Interface Mode Speed and duplexity of the selected ethernet interface for the primary Controller.
(Primary Drop) Displays speed in (Mbps megabits per second).
Interface Mode Speed and duplexity of the selected ethernet interface for the partner Controller.
(Partner Drop) Displays speed in (Mbps megabits per second).
Restore
Restore Mode Read only field for catastrophic failure.
(Appears if Online (Enable, Disable)
Controller Restore
Mode (see page
55) is selected.)
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.
5.4.2 To insert a new drop point

2. Use the system tree to navigate to the Drop Point item:
Systems > Networks > Units > Drops > Points > Drop Point
3. Right-click Drop Point.
4. Select Insert New from the resulting pop-up menu. The Insert New Drop Point Wizard
appears.
5. Provide 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) defined in To Insert a New
Controller Drop).
b) Select the appropriate drop number to correspond with the Point Name entry.
42 OW350_58
6. After the required information is provided, click Finish. The New Drop Point dialog box
appears containing default values for the attributes.
Figure 15: New Drop Point dialog box
7. 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.
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 30
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 8 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 selected to allow Point

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

Alarm Alarm Priority Sets the various alarm priority fields (1-8).
OW350_58 43
TAB FIELD DESCRIPTION
Display Summary Diagram Defines the applicable summary diagram that is sent to the Graphics
Display System.
Signal Diagram Defines the signal diagram number.
8. Click the Apply button to save these settings without closing the window, or click the Ok
9. Repeat this procedure for the partner drop in a redundant Controller drop configurations.
5.4.3 To set Controller parameters

2. Use the system tree to navigate to the Controller item:
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller
3. Right-click Controller.
4. Select Open from the resulting pop-up menu. The Controller dialog box appears showing the
Controller parameters tab.
5. Complete any desired changes to the default field values.
44 OW350_58
Controller dialog box descriptions
FIELD DESCRIPTION
System Memory Selects the size to the Controller configuration including RAM and Flash:
Normal: requires a minimum 16MB of RAM and a 10MB Flash.
Expanded: requires a minimum 32MB of RAM and a 20MB Flash.
Send Messages To Selects Workstation drop where Controller messages (error and informational) are
sent.
Default = None
Security Logger Used to log security related events.
SOE Logger 1 Selects the first Scanner Workstation drop where SOE messages are sent. (See
the applicable Ovation Historian User Guide.)
Default = None
SOE Logger 2 Selects the second Scanner Workstation drop where SOE message is sent. (See
the applicable Ovation Historian User Guide.)
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.
(See the Ovation Developer Studio User Guide.)
Drop-specific value
TimeKeeper Selects the device that synchronizes time for the Controller:
(Default, 1, 2, 3, 4, 5)
If Default is selected: The software uses the IOIC.
Note: All SOE modules in a Controller must be connected to the IOIC card that is
configured as the Time Keeper.
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
(MB) points to store internal information.
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
IOIC Alive Timeout Adjusting the Alive Timer is not supported for the 3.5 software release.
(IOIC G04 and above)
SIS Safety Instrumented System. The Ovation Historian must reside on the system
before SIS Loggers can function. SIS loggers must be configured in the system to
enable SIS events functionality.
Use SIS Loggers Used for SIS events functionality. To configure SIS Loggers, refer to the SIS User
Guide for Ovation 3.5 (OW350_47).
OW350_58 45
FIELD DESCRIPTION
SIS Logger 1 IP Displays IP address of the first SIS Logger, if configured. Must be configured to be
Address active.
SIS Logger 2 IP Displays IP address of the second SIS Logger, if configured. Must be configured to
Address be active.
5.4.4 To set existing control tasks

2. Use the system tree to navigate to the Control Tasks item:
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller > Control
> Control Tasks
3. Select the Control Tasks.
4. Observe Control Task 1 and Control Task 2 listed in the WorkPad window.
Note: By default, the first two of a possible five Control Tasks are assigned to a new Controller
drop upon insertion.
5. Right-click one of the Control Task objects in the Workpad Window.

6. Select Open from the resulting pop-up menu. The Control Task dialog box appears showing
the Control Task Parameters tab.
46 OW350_58
Note: Control Tasks are five areas in a Controller used to designate different scan times for
points. Control Task 1 contains points scanned every 100 milliseconds (0.1 second), Task 2
contains points scanned every 1000 milliseconds (1 second) and Tasks 3, 4, and 5 are user
configurable.
Figure 16: Control Task dialog box — Control Task 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.
Default = 65,000
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
7. Complete any desired changes to the default field values.

9. Repeat this procedure for each Control Task object before proceeding.
OW350_58 47
5.4.5 To insert new control tasks

2. Use the system tree to navigate to the Control Tasks item:
> Control Tasks
3. Right-click Control Tasks.
4. Select Insert New from the resulting pop-up menu. The Insert New Control Tasks Wizard
appears.
5. Change the default field value for the new Control Task Number to any unused number
sequentially starting at 3 to a maximum of 5. An example would be if two additional Control
Tasks are to be configured; their Control Task Numbers would be 3 and 4, not 3 and 5, or 4
and 5.
6. After completing the appropriate change, click Finish. The Control Task dialog box (showing
the Control Task Parameters tab) appears.
7. Repeat this procedure for each newly created Control Task before proceeding.
5.4.6 To confirm Controller Networking (network item)

2. Use the system tree to navigate to the Controller Networking (Network item):
Systems > Networks > Configuration > Controller Networking
3. Select Controller Networking.
4. Observe the Controller Networking object listed in the WorkPad window.
5. Right-click the Controller Networking object.
48 OW350_58
6. Select Open from the resulting pop-up menu. The Controller Networking dialog box appears
showing the Networking Configuration tab.
Figure 17: Controller Networking dialog box
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 or if the network is being submitted, see your System Administrator.
OW350_58 49
FIELD DESCRIPTION
Default Router IP Address The Router IP Address for connecting to an external network.
(Default = Blank)
Destination IP/Subnet The IP address of a device on another network.
Address (X)
Route (X) The IP address of the device that routes the packets to the proper destination.
Note: 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.
7. If the network level values are satisfactory for the new Controller drop, click the Cancel button
to exit without making changes and skip to Verifying Additional Software Configurations (see
page 59).
OR
If different values are desired for all the drops within the network branch, then complete
changes to the parameters on the Controller Networking dialog box (Default Router IP
Address and Controller Net Mask parameters) at the current Network item. 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.
OR
If conditions require the Controller drop to have values different than that of its network, click
the Cancel button to exit without making changes and proceed to the To Modify Controller
Networking (Drop Item) (see page 50).
5.4.7 To modify Controller Networking (drop item)

2. Use the system tree to navigate to the Controller Networking (Drop item):
Systems > Networks > Units > Drops > (DROP#) > Configuration > Controller
Networking
3. Right-click the desired Controller Networking icon in the WorkPad Window.
50 OW350_58
4. Select Open from the pop-up menu. The New Controller Networking dialog box appears.
Figure 18: New Controller networking dialog box
5. Complete any desired changes to the default field values (see To Confirm Controller
Networking (Network Folder) (see page 48).
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 or if the network is being submitted, see your System Administrator.
(Default = 255.255.255.255)
Default Router IP Address The Router IP Address for connecting to an external network.
(Default = Blank)
Destination IP/Subnet The IP address of a device on another network.
Address (X)
Route (X) The IP address of the device that routes the packets to the proper destination.
OW350_58 51
5.4.8 To configure the Controller for Ethernet Remote Interface

1. Access the Ovation Developer Studio
2. Use the system tree to navigate to the drop number.
3. Right-click the drop number and select Open.
52 OW350_58
4. In the Config tab, scroll down to the Ethernet Remote Interface and select a Controller
Network Port. This will be the port where the Controller will be physically connected the
Ethernet I/O network.
Figure 19: Ethernet Remote Interface - Config tab
OW350_58 53
5.5 Custom Controller Networking
5.5 Custom Controller Netw orking
Custom Controller networking allows special approved custom applications to operate. For
example, SIS and GE Genius are approved Ovation custom applications. Any custom network
application should be approved by Emerson before they can be used on your system.
54 OW350_58
5.6 Online Controller restore mode
5.6 Online Controller restore mode
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 the following items must be
considered:
 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.
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).
OW350_58 55
5.7 Restore mode functions
CAUTION! Arbitrarily switching between Restore Mode functions is NOT encouraged. 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).
5.7 Restore mode functions
Restore mode has three basic modes of operation:
1. Restore mode disabled (Default) (see page 56).

2. Restore mode enabled (all drops) (see page 56).
3. Restore mode enabled (redundant drops only) (see page 56).
5.7.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.
5.7.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).
5.7.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.
56 OW350_58
5.8 Restore mode performance issues
5.8 Restore mode performance 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).
5.9 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).
OW350_58 57
5.10 Restore mode point information issues
5.10 Restore mode point information issues
An additional feature of the restore operation concerns 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 illustrates 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 just
one 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.)
5.10.1 To set the online Controller Restore Mode

1. Launch the Ovation Developer Studio.
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 (see To
insert a system for a description of the options).
58 OW350_58
5.11 What additional software configurations are needed for Controllers?
5. Find Restore Mode in the Attributes column and choose the appropriate function from the
pull-down menu.
5.11 What additional softw are configurations are needed for

Controllers?
The following list contains additional item locations and settings that you must address to ensure
a complete Ovation Controller Software Configuration. See the associated manuals for item
locations and configuration information.
The Network Time Protocol (NTP) item settings. (See the Ovation Developer Studio User Guide.)
 The DDB Configuration item settings. (See the Ovation Developer Studio User Guide.)
 The Point Processing item settings. (See the Ovation Developer Studio User Guide.)
 The Event Log Configuration item settings. (See the applicable Ovation Process Historian
User Guide.)
Proceed to the configuring drivers sections of this manual for steps on configuring the Controller
drivers.
OW350_58 59
5.11 What additional software configurations are needed for Controllers?
5.11.1 To configure alarm timestamping to the millisecond level
The Controller can timestamp alarming to the 1 millisecond level when the Controller is enabled
for that function.

2. Use the system tree to navigate to the Point Processing (Drop item):
Systems > Networks > Units > Drops > (DROP#) > Configuration > Point Processing
3. Double-click the Point Process Configuration folder in the WorkPad window.
4. The New Point Processing window appears. Select the Enabled selection in the millisecond
resolution section.
5. Enter the desired changes and select Apply or OK to accept the changes.
6. The changes must be downloaded and the drop must be rebooted before the new settings
take effect.
Note: You must also select the millisecond format in the Alarm Display tab to allow for
millisecond timestamping. (See Ovation Operator Station Configuration Guide.)
5.11.2 To map a 16-bit PLC register to a 16-bit packed point

1. Access the New Deluxe Packed Points dialog window.
2. Put a check in the Register-to-Register Mapping check box on the Hardware view tab. If you
do not check this box, you must configure each bit separately.
60 OW350_58
5.12 RADIUS Server
3. After you have made the changes, download (see page 29), reboot (see page 31), and load
(see page 31) the Controller.
Figure 20: 16-Bit packed points
5.12 RADIUS Server
The RADIUS Server is used in Ovation for user authentication and authorization. RADIUS is an
acronym for Remote Authentication Dial In User Service. RADIUS is a client-server protocol and
software.
The Radius Server enables remote access clients to communicate with a central server to
authenticate dial-in users and to authorize their access to the requested system or service. Refer
to the Managing Security User Guide for information on configuring the Radius Server.
OW350_58 61
S E C T I O N 6
6 Configuring Controller drivers
IN THIS SECTION
Controller driver overview ................................................................................................. 63

Configuring device drivers in the Controller ...................................................................... 63
6.1 Controller driver overview
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.
6.2 Configuring device drivers in the Controller
To simplify the task of assigning device numbers, it is suggested that you configure the device
number first (starting with any Ovation/Q-Line devices), and then configure the I/O drivers.
Only one device number needs to be set up (number 1) for any Ovation or Q-Line device.
When an I/O Driver is set for Ovation/Q-Line devices, the Controller configures the first three
device items automatically. A fourth Ovation/Q-Line device can be added to accommodate any
remote Ovation or Q-Line devices.
Third-party devices must be added individually with a separate device number:

 0 - 4 reserved for IOIC
 5 - 11 (OCR400) and (OCR1100)
Note: The Controller can only sustain a certain number of remote connections. The maximum is
40 RTUs (remote terminal units), However, this value is a guide, not necessarily a hard
maximum or minimum. This value could vary depending on the dynamics of the specific
Controller being configured, (for example, external Ovation networks, ELCs, control tasks
(number and speed), network traffic, and so forth).
6.2.1 To configure Ovation and Q-Line devices
The following is an overview of the steps used to create Ovation devices or Q-Line devices. Refer
to the applicable sections for instructions on configuring specific Ovation and Q-Line drivers:
1. Insert a new device number.
OW350_58 63
6.2 Configuring device drivers in the Controller
2. Set the device number parameters.

3. Configure the device.
4. Insert a new branch and/or crate.
5. Insert the I/O module.
6. Download, reboot, and load. Refer to: What procedures are needed after configuration
changes to the Controller? (see page 29).
Note: The Controller only needs one device number to be configured for any Ovation or Q-Line
device. The Controller does not use individual hardware cards to control Ovation or Q-Line
devices. They are built in and controlled directly from the motherboard (IOIC). Therefore, the
driver number is (0).
Only one driver needs to be built for all of the Ovation and Q-Line devices. The system
automatically adds two local Ovation drivers and one Q-Line driver items. If remote Ovation or
Q-Line devices are to be configured, a fourth driver item must be added.
6.2.2 To configure third-party devices
The following is an overview of the steps used to create third-party devices. Refer to the
applicable sections for instructions on configuring specific third-party devices:
1. Insert a new device number.

2. Set the device number parameters.
3. Insert the device.
4. Configure the device.
5. Configure the device interface points.
6. Download, reboot, and load. Refer to: What procedures are needed after configuration
changes to the Controller? (see page 29).
64 OW350_58
S E C T I O N 7
7 Local Ovation I/O drivers configuration
IN THIS SECTION
To insert new device numbers .......................................................................................... 65

To set Ovation device number parameters ....................................................................... 66
To insert local Ovation I/O devices ................................................................................... 67
To insert a new local Ovation I/O branch .......................................................................... 69
To insert a local Ovation I/O module ................................................................................. 69
7.1 To insert new device numbers

Note: The Controller only requires the building of one driver for all local Ovation and local Q-
Line devices. The system automatically adds two local Ovation drivers and one Q-Line driver. If
remote Ovation, remote Q-Line, or extra local Q-Line devices are required, you must add a
fourth driver item.
2. Use the system tree to navigate to the Device Numbers item:

> Devices > Device Numbers
3. Right-click the Device Numbers item.
4. Select Insert New from the pop-up menu. The Insert New Device Numbers Wizard appears.
Note: If you need to change a driver on a previously configured device, or anytime a new device
is added, perform a clear/load function on the Controller. The Device Number represents the
physical devices that can communicate with the Controller.
5. Select a number sequentially, starting at 1 to a maximum of 8. An example would be if two

devices were to be configured; their device numbers would be 1 and 2, not 1 and 3, or 1 and
4, or 1 and 5.
6. Select Finish. The New Device Numbers dialog box appears showing the Controller Driver
Parameters tab.
7. Continue by setting device number parameters, see: To set Ovation device number
parameters (see page 66).
OW350_58 65
7.2 To set Ovation device number parameters
7.2 To set Ovation device number param eters

1. Select Ovation in the I/O Driver Type field in the New Device Numbers dialog box then make
the appropriate choices for the other fields in the New Device Numbers dialog box.
2. Select the OK or Apply button as shown in the following illustration.
Figure 21: Controller Driver Parameters tab (default)
Controller driver parameters tab descriptions (default)
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device (Ovation, plus all third-party devices).
Default = Ovation
Note: Choices for selecting driver types:
I/O Driver Type = None

Simulator Driver = FAKE where all points are simulated, go through the FAKE Simulator
driver, and do not change values.

Simulator Driver = Ovation where all points are simulated, go through the Ovation
Simulator driver, and do change values.
I/O Driver Type = Ovation (or applicable third-party devices)

Simulator Driver = None where all points are real and go through the I/O driver.

Simulator Driver = Ovation where all points are either real or simulated and go through
one of the drivers. The simulated points do change values.
66 OW350_58
7.3 To insert local Ovation I/O devices
FIELD DESCRIPTION
Simulator Driver Type Selects the Simulator Driver for the selected device.
 Fake
 Ovation
Note: For SimControllers and Virtual Controllers, this should be set to Ovation.
Slot Order Selects the card slot (one or two) in the Controller chassis associated with the selected
device (None, One, or Two).
(This field is
automatically filled in) Default = One
The parameter is grayed out if the device selected is not an IOIC card and has an
external connection (for example, Allen Bradley).
Scan Point Entries Displays the number of points available.

2. Use the system tree to navigate to the I/O Devices item:
3. Systems > Networks > Units > Drops > I/O Devices
4. Right-click the I/O Devices item.
5. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears. Make the following selections:
I/O Device Number value: Use the default settings.
I/O Device Type value: Use the default settings.
OW350_58 67
6. Select the Finish button. The New I/O Devices dialog box appears. The dialog box contains
the I/O device type and the I/O device number.
Figure 22: New I/O devices dialog box - local Ovation device type
New I/O devices dialog box - local Ovation device type field descriptions
FIELD DESCRIPTION I
I/O Device Number Defines I/O device number 1 through 8. Typically, device number 1 is
reserved for IOIC.
I/O Device Type Displays a list of all available I/O drivers. Select the desired I/O driver
from the drop-down menu.
Node Record Point Name Name assigned to the node record point.
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).
7. Configure the device by selecting which of the power supplies are to be monitored by the
associated Node record (RN). Select the “1” radio button beside each power supply you want
to monitor.
8. Select the Apply button. (See Ovation I/O Reference Manual.) Notice that the new Local
Ovation I/O Device item now appears in the system tree. The title of the I/O Device item
contains the device number and type.
68 OW350_58
7.4 To insert a new local Ovation I/O branch
7.4 To insert a new local Ovation I/O branch

2. Use the system tree to navigate to the Branch item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Local Ovation >
Branch
Note: The Branch item is established by default because Local Ovation was selected in the
Insert New I/O Device Wizard.
3. Right-click the Branch item.

4. Select Insert New. The Insert New Branch Wizard appears.
5. Select the Branch Number in the Value column. Up to eight branches can be defined.
Uneven branch numbers represent the slots on the left side of cabinet. Even branch numbers
represent the slots on the right side of the cabinet.
6. Select the Finish button. The New Branch dialog box appears.
Figure 23: New Branch dialog box
7. Ensure that the Branch number is correct and select the OK or Apply button. A Branch item
with Slot sub-items numbered 1-8 is added to the system tree.
7.5 To insert a local Ovation I/O module

2. Use the system tree to navigate to the Slot item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Local Ovation >
Branch > Slot
3. Open a Slot item to reveal an Ovation Module subfolder.
4. Right-click the Ovation Module subfolder (in the Slot folder that you want to configure).
OW350_58 69
7.5 To insert a local Ovation I/O module
5. Select Insert New. The Insert New Ovation Module Wizard appears.
6. Pull down the Module Type menu and select a module type.
7. Select the Finish button. The New Ovation Module dialog box appears, and contains four
tabs:
Config
Module
Digital Channels
Analog Channels
Options and fields that appear in the New Ovation Module dialog box are dependent upon
which module type has been selected in the Wizard.
Note: For additional information regarding Ovation Modules, see the Ovation I/O Reference
Manual.
8. Select the Config tab in the New Ovation Module dialog box.
Figure 24: New Ovation Module dialog box - Config tab
Enter a module point name in the Module Record Point Name field. You must create the module
point before it can be used in an I/O slot. (See the Ovation Developer Studio User Guide.)
1. Select the Module Type tab on the New Ovation Module dialog box and make appropriate
entries according to the module type. (See the Ovation Developer Studio User Guide.)
2. Depending on the module type, check either the Digital Channels tab or Analog Channels tab
for 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, select the Hardware tab, and configure the
point channel. (See the Ovation Developer Studio User Guide.)
3. Select Apply or OK to enter the changes into the database.

4. Refer to the Download, Reboot, and Load (see page 29) sections for information on
downloading, rebooting, and loading.
70 OW350_58
S E C T I O N 8
8 Remote Ovation I/O drivers configuration
IN THIS SECTION

To insert remote Ovation I/O devices ............................................................................... 73
To insert remote Ovation I/O new nodes .......................................................................... 75
To insert a remote Ovation I/O new branch ...................................................................... 75
To insert a remote Ovation I/O module ............................................................................. 77

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 71

FIELD DESCRIPTION
Default = Ovation




72 OW350_58
8.3 To insert remote Ovation I/O devices
FIELD DESCRIPTION
 Fake
 Ovation
(This field is

appears. Make the following selections:
 I/O Device Number value: Leave the I/O Device Number at 0.
 I/O Device Type value: Select IOIC
OW350_58 73
the I/O device number and the device type.
Figure 26: New I/O Devices dialog box - remote Ovation device type
New I/O Devices dialog box - remote Ovation device type field description
FIELD DESCRIPTION I
I/O Device Number Defines I/O device number 1 through 8. Typically, device number 0 -
4 is reserved for IOIC.
I/O Device Type Displays a list of all available I/O drivers. Select the desired I/O driver
from the drop-down menu.
to monitor.
7. Select the Apply button. (See Ovation I/O Reference Manual.) Notice that the new Remote
Ovation I/O Device item now appears in the system tree. The title of the I/O Device item
74 OW350_58
8.4 To insert remote Ovation I/O new nodes
8.4 To insert remote Ovation I/O new nodes

2. Use the system tree to navigate to the Remote I/O Node item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Remote Ovation >
Remote I/O Node
The Node item is established by default because Remote Ovation was selected in the Insert
New I/O Devices Wizard.
3. Right-click the Remote I/O Node item.
4. Select Insert New. The Insert New Remote I/O Node Wizard appears.
5. Select the node number and then choose the Finish button. (See Ovation I/O Reference
Manual.) The New Node dialog box appears.
Figure 27: New Node dialog box
6. Select the appropriate Power Supply and Secondary Power Supply. Select the “1” radio
button beside each power supply you want to monitor.
7. Select the Apply button. (See Ovation I/O Reference Manual.) The Node and Branch sub-
items appear in the system tree under the I/O Device Remote Ovation item.
OW350_58 75
8.5 To insert a remote Ovation I/O new branch
8.5 To insert a remote Ovation I/O new branch

2. Use the system tree to navigate to the Branch item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Remote Ovation
>Branch
Note: The Branch item is established by default because Remote Ovation was selected in the
Insert New I/O Device Wizard.
3. Right-click the Branch item.

4. Select Insert New. The Insert New Branch Wizard appears.
5. Select the branch number in the Value column. Up to eight branches can be defined. Uneven
branch numbers represent the slots on the left side of cabinet. Even branch numbers
represent the slots on the right side of the cabinet.
6. Select the Finish button. The New Branch dialog box appears.
Figure 28: New Branch dialog box
7. Ensure that the branch number is correct.

8. Select the OK or Apply button. A Branch item with Slot sub-items numbered 1-8 is added to
the system tree.
76 OW350_58
8.6 To insert a remote Ovation I/O module

2. Use the system tree to navigate to the Slot item.
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Remote Ovation >
Branch > Slot
3. Open a Slot item to reveal an Ovation Module sub-item.
4. Right-click the Ovation Module sub-item (in the Slot folder that you want to configure).
5. Select Insert New. The Insert New Ovation Module Wizard appears.
6. Pull down the Module Type menu, and select a module type.
7. Select the Finish button. The New Ovation Module dialog box appears and contains four
tabs: Config, Module, Digital Channels, and Analog Channels. Options and fields that appear
in the New Ovation Module dialog box are dependent upon which module type has been
selected in the Wizard.
Note: For additional information regarding Ovation modules, see the Ovation I/O Reference
Manual.
8. Select the Config tab in the New Ovation Module dialog box as shown.
Figure 29: New Ovation Module dialog box - Config tab
9. Enter a module point name in the Module Record Point Name field. You must create the
module point before it can be used in an I/O slot. (See the Ovation Developer Studio User
Guide.)
10. Select the Module tab on the New Ovation Module dialog box and make the appropriate
entries according to the Module type. (See the Ovation Developer Studio User Guide.)
OW350_58 77
Figure 30: New Ovation Module - Module tab
for the point names that are assigned to each channel.
78 OW350_58
Note: For a point name to appear in the Value column of either the Digital Channel or Analog
Channel tabs, it must be defined as an I/O point for this module. To define an I/O point, go to the
appropriate point type item in the Points item, select the hardware tab, and configure the point
channel. (See the Ovation Developer Studio User Guide.)
Figure 31: New Ovation Module dialog box - Digital Channels tab
12. Select Apply or OK to enter the changes into the database.

downloading, rebooting, and loading.
OW350_58 79
S E C T I O N 9
9 Local Q-Line drivers configuration
IN THIS SECTION

To insert local Q-Line devices ........................................................................................... 83
To insert a new local Q-line crate...................................................................................... 85
To insert a new local Q-line module .................................................................................. 85

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 81

FIELD DESCRIPTION
Default = Ovation




82 OW350_58
9.3 To insert local Q-Line devices
FIELD DESCRIPTION
 Fake
 Ovation
(This field is
9.3 To insert local Q -Line devices

appears. Make the following choices.
5. I/O Device Number value: Use the default settings.
OW350_58 83
9.3 To insert local Q-Line devices
the I/O device type and the I/O device number.
Figure 33: New I/O Devices dialog box - local Q-line device type
New I/O devices dialog box - local Q-line device type descriptions
FIELD DESCRIPTION
I/O Device Number Selected by Controller software.

I/O Device Type Selects the I/O Driver for the device.
Software controlling the Ovation devices.
Node Record Point Name Defines the Node Record Point name.
associated node record (RN). Select the “1” radio button beside each power supply you want
to monitor.
8. Select the Apply button. (See Ovation I/O Reference Manual.) Notice that the new Local Q-
Line I/O Device item now appears in the system tree. The title of the I/O Device item contains
the device number and type.
84 OW350_58
9.4 To insert a new local Q-line crate
9.4 To insert a new local Q -line crate

2. Use the system tree to navigate to the Crate item.
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Local Q-Line > Crate
(The Crate item is established by default when Local Q-Line is selected in the Insert New I/O
Device Wizard.)
3. Right-click the Crate item.
4. Select Insert New. The Insert New Crate Wizard appears.
Note: You can define up to four crates for each PCQL card. Each crate automatically contains
12 slots for Q-Line modules.
5. Select the Crate Number and then choose the Finish button. The New Crate dialog box
appears.
Figure 34: New Crate dialog box
6. Ensure that the crate number is correct and select the Ok or Apply button. A Crate item
containing 12 Slot sub-items is added to the system tree.
9.5 To insert a new local Q -line module

Systems > Networks > Units > Drops > I/O Devices I/O Device # Local Q-line > Crate >
Slot
3. Open the Slot item to reveal a Q-Line Module sub-item.
4. Right-click the Q-Line Module sub-item (in the Slot item you want to configure).
5. Select Insert New. The Insert New Local Q-line Wizard appears.
OW350_58 85
9.5 To insert a new local Q-line module
6. Enter the Card Address. (See Q-Line Installation Manual.)

7. Select the card type from the pull-down menu. (See Q-Line Installation Manual.)
8. Select the Finish button. The New Q-line Module dialog box appears.
9. Select the Config tab.
Figure 35: New Q-Line Module dialog box - Config tab
10. Ensure that the card type and card address values are correct.
Depending on the module type, check either the Digital Channels tab or Analog Channels tab
for the point names that are assigned to each channel. The following figure is an example of
the New Q-Line Module dialog box with the Analog Channels tab selected.
86 OW350_58
9.5 To insert a new local Q-line module
Note: For a point name to appear in the Value column of either the Digital or Analog tab, it must
be defined as an I/O point for this module. To define an I/O point, go to the appropriate point
type item in the Points item, select the Hardware tab, and configure the point channel. (See the
Ovation Developer Studio User Guide.)
Figure 36: New Q-Line Module dialog box - Analog Channels tab example
11. Select Ok or Apply to add the settings to the database. Refer to the Download, Reboot, and
Load (see page 29) sections for information on downloading, rebooting, and loading.
OW350_58 87
S E C T I O N 10
10 Remote Q-Line driver configuration
IN THIS SECTION

To insert remote Q-line devices ........................................................................................ 91
To insert new remote Q-line nodes ................................................................................... 93
To insert a new remote Q-Line crate................................................................................. 93
To insert a new remote Q-line module .............................................................................. 94

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 89

FIELD DESCRIPTION
Default = Ovation




90 OW350_58
10.3 To insert remote Q-line devices
FIELD DESCRIPTION
 Fake
 Ovation
(This field is
10.3 To insert remote Q -line devices

1. Use the system tree to navigate to the I/O Devices item.
appears.
I/O Device Number value: Use the default settings.
OW350_58 91
10.3 To insert remote Q-line devices
the type and number assigned to the PCRR card.
Figure 38: New I/O Devices dialog box - remote Q-Line device type
New I/O Devices dialog box - remote Q-Line device type descriptions
FIELD DESCRIPTION
I/O Device Number Defines I/O device number 1 through 8. Typically, device
number 1 is reserved for IOIC.
I/O Device Type Displays a list of all available I/O drivers. Select the desired I/O
driver from the drop-down menu.
to monitor.
6. Select the Apply button. (See Ovation I/O Reference Manual.) Notice that the new Remote
Q-Line I/O Device item now appears in the system tree. The title of the I/O Device item
92 OW350_58
10.4 To insert new remote Q-line nodes
10.4 To insert new remote Q -line nodes

2. Use the following path to access the Remote Q-Line I/O Node item.
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Remote Q-Line >
Remote Q-Line I/O Node
Note: The Node item is established by default because Remote Q-Line was selected in the
Insert New I/O Devices Wizard.
3. Right-click the Remote Q-Line I/O Node item and select Insert New. The Insert New Remote
Q-Line Node Wizard appears.
4. Select the appropriate node number and then choose the Finish button. The New Remote Q-
Line I/O Node dialog box appears.
5. Select the appropriate DIOB Primary Power Supply and the DIOB Secondary Power
Supply.
6. Select the Apply or Ok button. The Node item and Crate sub-item appears in the system tree
under the I/O Device# Remote Q-Line item.
10.5 To insert a new remote Q -Line crate

2. Use the system tree to navigate to the Crate item:
Systems > Networks > Units > Drops > I/O Devices > I/O Device # Remote Q-Line >
Crate item
Note: The Crate item is established by default when Remote Q-Line is selected in the Insert
New I/O Device Wizard.
3. Right-click the Crate item.

4. Select Insert New. The Insert New Crate Wizard appears.
OW350_58 93
10.6 To insert a new remote Q-line module
Note: You can define up to four crates for each PCQL card. Each crate automatically contains
12 slots for Q-Line modules.
5. Select the crate number and then choose the Finish button. The New Crate dialog box
appears.
Figure 39: New Crate dialog box
6. Ensure that the Crate number is correct and select the Ok or Apply button. A Crate item
containing 12 Slot sub-items is added to the system tree.
10.6 To insert a new remote Q -line module

Systems > Networks > Units > Drops > I/O Devices > Slot
3. Open the Slot item to reveal a Q-Line Module subfolder.
4. Right-click the Q-Line Module sub-item (in the Slot item you want to configure).
5. Select Insert New. The Insert New Remote Q-Line Wizard appears.
6. Enter the card address. (See Q-Line Installation Manual.)
7. Select the card type from the pull-down menu. (See Q-Line Installation Manual.)
8. Select the Finish button. The New Q-Line Module dialog box appears.
94 OW350_58
9. Select the Config tab.
Figure 40: New Q-Line Module dialog box - Config tab
10. Ensure that the card type and card address values are correct.
for the point names that are assigned to each channel. The following figure is an example of
the New Q-Line Module dialog window with the Analog Channels tab selected.
Note: For a point name to appear in the Value column of either the Digital or Analog tab, you
must define it as an I/O point for this module. To define an I/O point, go to the appropriate point
type item in the Points item, select the Hardware tab, and configure the point channel. (See the
Ovation Developer Studio User Guide.)
Figure 41: New Q-Line Module dialog box - Analog Channels tab example
OW350_58 95
12. Select Ok or Apply to add the settings to the database.

downloading, rebooting, and loading
96 OW350_58
S E C T I O N 11
11 Allen-Bradley driver overview
IN THIS SECTION
What is an Allen-Bradley driver? ....................................................................................... 97

Allen-Bradley DF-1 commands supported by Ovation .................................................... 103
I/O access path examples for Allen-Bradley ................................................................... 104
Allen-Bradley analog input cards .................................................................................... 105
Allen-Bradley digital input cards ...................................................................................... 105
11.1 What is an Allen-Bradle y driver?
Allen-Bradley manufactures programmable logic Controllers (PLC), human-machine interfaces,

sensors, safety components and systems, software, drives and drive systems, contactors, motor
control centers, and systems made of these and similar products.
The Ovation Controller supports communication with various types of Allen-Bradley PLCs
including PLC5, SLC500, ControlLogix, and MicroLogix with NET-ENI, and so forth.
You can configure Allen-Bradley drivers to fail the Controller on communication error. This means
communication can be configured to support redundancy. In a redundant setup, the primary and
backup Controllers can be configured to communicate to the same or unique PLCs, allowing for
greater redundancy. If the Controller is configured for failover, the failover occurs within the user-
defined message timeout, anytime communication is lost for any reason.
11.1.1 To insert new device numbers

fourth driver item.

OW350_58 97
11.1 What is an Allen-Bradley driver?

4, or 1 and 5.
Parameters tab.
11.1.2 To insert an Allen-Bradley device

appears.
5. Select the I/O Device Number: Use the first available (5-11).
6. Select Allen-Bradley from the I/O Device Type pull-down menu.
7. Select the Finish button. The New I/O Devices dialog box appears.
Figure 42: New I/O Devices window - Allen-Bradley
98 OW350_58
New I/O Devices descriptions - Allen-Bradley
FIELD DESCRIPTION
I/O Device Number Automatically entered as defined by the system. Used internally to identify the
information.
I/O Device Type Selects the I/O Driver for the selected device.
8. Select the Ok or Apply button. Notice that the new Allen-Bradley I/O Device item now
appears in the system tree. The title of the I/O Device item contains the device number and
type.
11.1.3 To set Allen-Bradley device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box. Refer to the following
figure and table.
2. Select the Ok or Apply button.
Figure 43: Controller Driver Parameters tab (Allen-Bradley)
Controller Driver Parameters field descriptions (Allen-Bradley)
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device, (Ovation, plus all third-party
devices).
Default = Ovation
OW350_58 99
FIELD DESCRIPTION

A-B PLC5 Hostname plc5-1, plc5-2, plc5-3, plc5-4, or plc5-5
Assigns a hostname to the Allen-Bradley PLC. One driver can monitor up to five
PLCs. This is used in the I/O access to associate points to an IP address.
For example, a third-party A-B point with hostname index 2 in its “IO access
path” field accesses data in plc5-2 (See the Ovation Developer Studio User
Guide.)
PLC IP Address (Primary Assigns an IP address for the selected hostname. This address must be
Drop) programmed into the PLC using A-B loader software, and is used to
communicate to the Allen-Bradley PLC.
Address 255.255.255.255 disables the hostname
PLC IP Address (Partner The IP address for the partner controller used to communicate to the Allen-
Drop) Bradley PLC, typically used in redundant configurations only.
Slot Defines the slot where the Ethernet module is located in the Allen-Bradley
chassis.
The slot number refers to the physical location of the Allen-Bradley Logix
processor card.
Node Number of the PCL, and is similar to the slave address.

Socket Number The socket number used by the PCL is automatically calculated based on
communications protocol, slot and node. This parameter is not configurable by
the user.
Note: A socket number of 3333 indicates to the driver that the target is a
Pyramid Integrator.
Timeout (milliseconds) Defines the message response timeout in milliseconds, and is the length of time
the driver waits for a response before declaring an error and failing over if
configured to do so.
This is the amount of time the driver waits for a response from the PLC before
setting the points to bad quality.
Default =1000 milliseconds
Reconnect Timeout (Sec.) Defines the amount of time the driver waits before trying to re-establish a
connection and is the length of time the driver waits after losing a connection
before trying to reconnect to the end device.
Default = 30
Fail Controller on Error True means that the Controller fails over to the backup if communication is lost.
False means the Controller does not failover.
Communication Protocol Specifies the communication protocol required by the target device. The
available communication protocols include, PLC5/SLC500, Pyramid Integrator,
ControlLogix 5000, and MicroLogix w/NIT-EN1.
Default = PLC5/SLC500
11.1.4 To configure Allen-Bradley points

2. Use the system tree to navigate to the Points item:
Systems > Networks > Units > Drops > Points
100 OW350_58
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click the applicable Points item.
5. Select Insert New. The Insert New <Point Type> Points Wizard appears (where <Point
Type> = Analog, Digital, or Packed).
6. Fill in the Point Name and Frequency (S-Slow (1 sec.), F-Fast (0.1 sec.), or A-Aperiodic (as
needed).
7. Press the Finish button. The New <Point Type> Points dialog window appears.
Figure 44: New Analog Points - Allen-Bradley
8. Select the Hardware tab on the New <Point Type> Points dialog.
Note: See To map a 16-bit PLC Register to a 16-bit Packed Point (see page 60) for more
information.
9. Select Third-party from the I/O Type drop-down menu.

10. Select Allen-Bradley from the I/O module pull down menu. The New <Point Type> Points
window appears with additional parameters.
11. Complete the information in the window as it pertains to the Allen-Bradley driver. The
following table discusses the parameters that are common to all drivers and also those that
pertain to Allen-Bradley specifically. I/O Access Path Examples for Allen-Bradley (see page
104) provides some examples.
12. After completing the information in the window, select the Ok or Apply button. Continue using
this procedure for every point you want to configure. Refer to the Download, Reboot, and
OW350_58 101
Hardware tab field descriptions — Allen-Bradley
FIELD DESCRIPTION
IO type This is set to Third-party to indicate a third-party point.
IO module The third-party driver is assigned a device number in the Insert New Device Numbers
Wizard. This field is used to match the point with the device number.
Note: There can be no gaps in the assigned device numbers. For example, if only one
PCI slot number is needed, then device 1 is reserved for that card, and any third-party
driver would be assigned as device 2 (not 3, 4, or 5).
IO channel This field is only used for packed points.

IO task index Points are grouped by the Control task index so that they can be updated (scanned) at
different rates. The Control task rate is set in the Controller Configuration Parameters
(Control Task) dialog box (shown in Configuring Controller Software (see page 35)).
Control Task 1 = 100 msec
Control Task 2 = 1000 msec (1 second)
Control Tasks 3, 4, and 5 are user configurable and the scan rate should be appropriate
for the application and system needs.
Emerson recommends that third-party points be given their own task area. The scan rate
should be no faster than one second because of the communication overhead.
No more than 2000 points can be assigned to a task area.
IO module units Not Applicable for this application.
IO access path This field is filled automatically from the information entered in the Hardware tab fields
that are specific to Allen-Bradley or from imported information.
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the Register to
Register Mapping check box is recommended so that all IO access paths are identical.
This minimizes memory usage in the Controller.
PLC Host Index Hostname index that was defined in the New Device Numbers window (Controller Driver
Parameters tab, set for Allen-Bradley).
The choices are: PLC1 - PLC5.
Input or Output Indicates whether the PLC value is read into the process point or if the process point
value is written out to the PLC.
The choices are: Input from PLC or Output to PLC.
Register Address Register address in logical ASCII format for the Allen-Bradley driver. This address is
comprised of the Allen-Bradley file type, the file number, the register number and the bit
number. See the example in I/O Access Path Examples for Allen-Bradley (see page
104).
Data Type Used to interpret the data type of the Allen-Bradley register.
The choices are: Signed or Unsigned.
102 OW350_58
11.2 Allen-Bradley DF-1 commands supported by Ovation
11.2 Allen-Bradle y DF -1 commands supported by Ovation
The following table contains the Allen-Bradley DF-1 commands supported by the Ovation
Controller Allen-Bradley Protocols PCCC and CIP/EthernetIP.
Allen-Bradley DF-1 commands supported by Ovation
C C F Processors Pg
o M N
m D C Micro- S S S 1 P P P P P Pub
m Logix L L L 7 L L L L L 17706-5-16
a 1000 C C C 7 C C C C C
n 5 5/ 5/ 4 2 3 5 5/ 5/
d 0 03 04 P 2 V
0 L 5 M
C 0 E
Ovation Protocol Selection – PLC5, PLC-2, SLC-500 (PCCC) ControlLogix (CIP/EthernetIP)
Bit write 0F 02   7-4
Type read 0F 68      7-28
Type write 0F 67      7-30
Ovation Protocol Selection – PLC2 (PCCC)
Protected bit 02 #      7-15
write
Protected 00     7-19
write
Unprotected 01 #          7-31
read
Ovation Protocol Selection – MicroLogix w/NET-ENI
Logical Read 0F a2 
Logical Write 0F aa 
# This command has no FNC byte.
Attention: Using command codes not listed produces unpredictable results.
Note: To send digital output points to either a MicroLogix or SLC500, you must use a packed
point. This is due to a limitation of the command set supported by these devices.
OW350_58 103
11.3 I/O access path examples for Allen-Bradley
11.3 I/O access path examples for Allen -Bradle y
The I/O Access Path is filled in automatically from the information entered in the Hardware tab or
from imported information.
The following is an example of the format that is used in the Hardware tab IO access path field for
an Allen-Bradley third-party point:
AB PLC5 2 IN FFYYY:NNN/BBB
where:
AB PLCS Identifies the third-party driver type.
2 PLC Host Index field.

IN Input or Output field
FF Part of the Register Address.
Allen-Bradley file type. Choices are:
O, I, N, F, S, B
YYY Part of the Register Address.

File Number: (0 - 1023)
NNN Part of the Register Address.

Register Number (0 -1023)
Note: Register numbers that begin with a zero (0) are

interpreted as octal numbers.
Address F011:020 is equivalent to F9:16.
BBB Part of the Register Address.

Bit Number (0 - 15)
Note: The Allen-Bradley protocol allows for two styles of addressing when accessing the binary
“B” files: The first style of bit addressing is B3:12/0. The second style of bit addressing is
B:3/192 (same as B3:12/0). This driver uses the first style of addressing.
Additional examples:
 Read a floating point value F8:20 from a SLC500 with hostname plc5-3.
AB PLC5 3 IN F8:20
 Write the point value to 16-bit register N7:10 at plc5-1.
AB PLC5 1 OUT N7:20
 Read digital input register I:014 bit 12 from plc5-2 into a digital point.
AB PLC5 2 IN I:014/12
104 OW350_58
11.4 Allen-Bradley analog input cards
11.4 Allen-Bradle y analog input cards
The Ovation Controller Allen-Bradley PLC5 driver maps process points to PLC5 registers via an
Ethernet link. Normally, if the PLC register value was successfully read or written, then the point
quality is set to GOOD.
An additional feature allows the process point quality to reflect the status of the Allen-Bradley
input card, where the register value originated. This means that if a rack of analog input cards
loses power, then the process points for those inputs go to BAD quality.
To read an analog input card, a PLC5 must contain a Block Transfer Read in its ladder program.
This reads the card values and status and writes them to a specified set of N registers.
For example, if an eight channel analog input card is moved to N7:10, then the structure is:
N7:10 card diagnostic - should be all zeros

N7:11 underrange - bit 0 is for channel 1
N7:12 overrange bit 0 is for channel 1
N7:13 data polarity
N7:14 channel 1 value - 12 bit unsigned integer value
N7:15 channel 2 value
To read the value of the channel 4 into an analog process point, the IO_ACCESS string would be
AB PLC5 1 N7:17/4. A bit number specified for an analog point is interpreted as a channel
number. The Controller treats this as a Q-Line analog input. The polarity register (N7:13) is used
to determine the sign of the value. The quality is set to BAD if the card diagnostic (N7:10) is non-
zero, or if the underrange or overrange bit is set.
Note: The driver expects the card diagnostic register values to be returned in the same
message as the channel value. For this reason, it may be necessary to read the card diagnostic
(N7:10) register into a dummy point to cause the driver to access the entire array.
11.5 Allen-Bradle y digital input cards
Discrete input values from digital input cards appear in the input (I) file. The I/O rack address is
determined from the register address. For example, I:014/12 is the input from rack 01 group 4 bit
12. The status of racks is found in the status file S:7. The status of rack 2 is in S:7 bit 2.
The Allen-Bradley PLC5 driver monitors the addresses it is asked to read. If it reads register S:7,
then it saves the value. The driver sets the quality of a digital process point mapped to an input (I)
bit based on the value from the S:7 register, if available.
Note: It is necessary to read S:7 into a dummy point to allow its use for point quality.
OW350_58 105
S E C T I O N 12
12 Foundation Fieldbus second generation (I/O

modules) driver configuration
IN THIS SECTION
To insert new device numbers ........................................................................................ 107

To set Foundation Fieldbus (I/O module) parameters .................................................... 107
To insert a Foundation Fieldbus I/O module in the Developer Studio ............................ 108
To add a module record point name ............................................................................... 110
To add a Foundation Fieldbus (I/O module) device ........................................................ 112
To assign a node record to each of your ports ............................................................... 114

fourth driver item.


4, or 1 and 5.
Parameters tab.
12.2 To set Foundation Fieldbus (I/O module) parameters

1. From the I/O Driver Type drop-down menu, select FIELDBUS MODULE.
2. Click OK.
OW350_58 107
12.2 To set Foundation Fieldbus (I/O module) parameters
Note: You only have to perform this task once for each Controller that utilizes Foundation
Fieldbus.
Figure 45: New Device Numbers window
Controller Driver Parameters field descriptions (Fieldbus)
FIELD DESCRIPTION
Default = Ovation
Timeout (msec) Length of time in msec the Controller waits for a response from the client before
declaring an error and/or failing over.
If the drop is not redundant, it is the time the Controller waits before reporting an error
and faulting the drop.
Default = 10,000
Fail Controller on Error Allows you to determine if this interface can fail the Controller when an error occurs.
If False is selected, the Controller does NOT fail over to Backup when the response
time limit (set in the Timeout parameter) is exceeded.
If True is selected, the Controller fails over to Backup when the response time limit (set
in the Timeout parameter) is exceeded.
(False, True) Default = True
108 OW350_58
12.3 To insert a Foundation Fieldbus I/O module in the Developer Studio
12.3 To insert a Foundation Fieldbus I/O module in the Developer

Studio
2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
System > Networks > Units > Drops > I/O Devices > IO Interfaces > Branch > Slot
3. Select the Ovation module in that empty slot:
Figure 46: Ovation Module in tree
4. Right-click to select Insert New. The Insert New Ovation Module wizard appears:
Figure 47: Insert New Ovation Module wizard
OW350_58 109
12.4 To add a module record point name
5. Select Foundation Fieldbus BusModule.

6. Click Finish. The New Ovation Module window appears:
Figure 48: New Ovation Module window
Emerson recommends that you leave the Module Record Point Name in the Value column
empty.
7. Click Ok. Two ports (P01 and P02) are automatically created in the slot.
Note: You must perform this task for each Foundation Fieldbus I/O module that you add.

2. Use the system tree to navigate to Module Points:
Systems > Networks > Units > Drops > Points > Module Points
110 OW350_58
3. Right-click Module Points to select Insert New. The Insert New Module Points wizard
appears:
Figure 49: Insert New Module Points Wizard
4. Type a point name.

5. Pick a frequency.
6. Click Finish. The New Module Points window appears:
Figure 50: New Module Points window
7. Navigate to the Hardware tab.
OW350_58 111
12.5 To add a Foundation Fieldbus (I/O module) device
8. Choose the I/O module from the location where you added it.
9. Click Ok. If you navigate to your card and Open/Refresh, you will see the fully qualified
module record point name (for example, TEST.UNIT@FB).
12.5 To add a Foundation Fieldbus (I/O module) de vice

2. Use the system tree to navigate to Fieldbus Devices:
Systems > Networks > Units > Drops > I/O Devices > Fieldbus Devices
3. Right-click Fieldbus Devices to select Insert New. The Insert New Fieldbus Devices wizard
appears:
Figure 51: Insert New Fieldbus Devices wizard
4. Pick a unique name that is not used anywhere else in your system.
5. Identify the manufacturer, device type, and revision of your device.
112 OW350_58
Note: You cannot change the name of a device after it is used in control.
The manufacturer, device type, and device revision information is supplied in a file and resides
in the Ovation Database. The file lists the information for all approved Fieldbus devices.
6. Click Finish. The New Fieldbus Devices window appears:
Figure 52: New Fieldbus Devices window (Config tab)
7. Type a name for your RN-type node point (this is used for device alarms) in the Ovation
Point Name field. Do not fully qualify the point name (for example, type TEST, not
TEST.UNIT@FB). If this name currently does not exist in your system, it will be added when
you click OK.
OW350_58 113
8. Navigate to the PlantWeb Alerts tab:
Figure 53: New Fieldbus Devices window (Plant Web Alerts tab with no PlantWeb Alerts)
9. Note the Enable PlantWeb Alerts check box, which is checked by default. If you keep this
option checked, you must have an RN point assigned to it. The gray boxes in this window
indicate which options the device's manufacturer supports for each of the five alarm types.
10. Click Ok.
114 OW350_58
12.6 To assign a node record to each of your ports
12.6 To assign a node record to each of your ports
Note: For each port that you want to use, you must open the port and assign it a node record.

2. Use the system tree to navigate to a port:
Systems > Networks > Units > Drops > I/O Devices > I/O Interfaces > Branch > Slot >
Port
3. Right-click the port that you want to update (for example, P01 or P02) to select Open. A port
configuration window appears:
Figure 54: Port configuration window
4. Type an Ovation Point Name. Do not fully qualify the point name (for example, type
TESTNAME, not TESTNAME.UNIT@FB). If this name currently does not exist in your
system, it will be added when you click OK.
5. Click OK.
OW350_58 115
S E C T I O N 13
13 GE Genius driver configuration
IN THIS SECTION

To set GE Genius device number parameters ................................................................ 118
To insert a GE Genius device ......................................................................................... 118
What are I/O access path examples for GE Genius? ..................................................... 121

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 117
13.2 To set GE Genius device number parameters
13.2 To set GE Genius device num ber parameters

1. Make the appropriate choices in the New Device Numbers dialog box then select the Ok or
Apply button.
Figure 55: Controller Driver Parameters fields (GE Genius)
Controller Driver Parameters field descriptions (GE Genius)
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device (Ovation, plus all third- party devices).
Default = Ovation
If True is selected, the Controller fails over to Backup when the response time limit
(set in the Timeout parameter) is exceeded.
118 OW350_58
13.3 To insert a GE Genius device

4. Select Insert New from the resulting pop-up menu. The Insert New [I/O Devices] Wizard
appears.
6. Select GE Genius from the I/O Device Type pull-down menu.
7. Select the Finish button. The New [I/O Devices] dialog box appears.
8. Select the Apply button then click OK. Notice that the new I/O Devices X GE Genius item
now appears in the system tree. The title of the I/O Device item contains the device number
and type.
9. Expand the GE Genius device item, a GE Genius Gateway item appears.
10. Right-click the GE Genius Gateway item.
11. Select Insert New from the resulting pop-up menu. The Insert New GE Genius Gateway
Wizard appears.
12. Fill in the name of the Gateway (GE-Device in this example).
13. Select finish, the New GE Genius Gateway dialog box appears.
Figure 56: New GE Genius Gateway dialog box
OW350_58 119
New GE Genius Gateway dialog box descriptions
FIELD DESCRIPTION
Name User provided

Gateway Number Automatically entered as defined by the system. Used internally to identify
the information.
Ovation Point Name Name of the point from where the data is being retrieved.
Redundancy Non-redundant and Redundant (Simplex, Redundant)
IP Address (Primary and Address of the Ethernet interface on the primary and secondary units
Secondary Units)
Scan Rate (msec) Transfer rate between Ovation and the GE Genius.
Message Timeout (sec) Amount of time the system waits for a response from GE Genius.
14. Make any necessary changes.
15. Select OK. The GE Genius Gateway item name changes to the Gateway Name added above
(GE-Test), and the items in the tree fills in under the GE-Device item.
16. Expand the item to revel the GE Genius I/O Blocks item.
17. Right-click the GE Genius I/O Blocks item.
18. Select Insert New, the following dialog box opens.
19. Make the appropriate changes. See the GE Genius manual for a listing of I/O Blocks.
20. Select OK.
Figure 57: New GE Genius I/O Blocks
New GE Genius I/O blocks dialog box descriptions
FIELD DESCRIPTION
Block Number Must be a unique name not used anywhere else in the system. The
system automatically provides a unique name, but can be changed.
Block Type Drop-down list of accepted devices from the manufacturer.
120 OW350_58
13.4 What are I/O access path examples for GE Genius?
FIELD DESCRIPTION
Module Input Base Address (word) Revision of the device.

Module Output Base Address Class of the device.
(word)
13.4 What are I/O access path examples for GE Genius?
The IO Access Path is filled in automatically from the information entered in the Hardware tab or
a third-party point:
L45BRKC INPUT
where:
L45BRKC Point Name
INPUT
Additional Example:
HTRAISE:20 OUTPUT
where:
20 is the point offset supplied by GE and is only needed for OUTPUT point types.
Valid point types
POINT TYPE RECORD TYPE NOTES
INPUT Analog (LA) and Digital point (LD) Data received from the GE system.
records.
OUTPUT Analog (LA) and Digital point (LD) Control commands and setpoints from the
records. Ovation system.
Note: Deluxe records are not supported for any point types.
OW350_58 121
S E C T I O N 14
14 GE Mark V/VI/Ve driver configuration
IN THIS SECTION

To set GE Mark V/VI/Ve device number parameters ...................................................... 123
To insert a GE Mark V/VI/Ve device ............................................................................... 125
To configure GE Mark V/VI/Ve points ............................................................................. 126
What are I/O access path examples for GE Mark V/VI? ................................................. 130
14.1 To insert new devi ce numbers

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 123
14.2 To set GE Mark V/VI/Ve device number parameters
14.2 To set GE Mark V/VI/Ve device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box.
Figure 58: Controller Driver Parameters fields (GE Mark V/VI/Ve)
Controller Driver Parameters field descriptions (GE Mark V/VI/Ve)
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device.
Default = None
Choices for selecting Driver Types:

I/O Driver Type = GE Mark V/VI/Ve
Simulator Driver = None
Note: A maximum of one GE PCI device per Controller is allowed.

You must have an Ovation I/O Driver Type and an associated IOIC card defined.
Default = None
Typical Ovation systems do not have a Simulator function.
If your system does have a Simulator, refer to the appropriate Ovation Simulator
User Guide for information.
124 OW350_58
14.3 To insert a GE Mark V/VI/Ve device
FIELD DESCRIPTION
Slot Order Selects the card slot (one or two) in the Controller chassis associated with the
selected device.
Parameter is grayed out if device selected is not an I/OIC card and has an external
connection (for example, Allen Bradley).
Default = One
14.3 To insert a GE Mark V/VI/Ve device

Use the system tree to navigate to the I/O Devices item:
appears.
5. Select GE Mark V/VI/Ve from the I/O Device Type pull-down menu.
7. Select the Apply button. Notice that the new GE Mark V/VI/Ve I/O Device item now appears
in the system tree. The title of the I/O Device item contains the device number and type.
OW350_58 125
14.4 To configure GE Mark V/VI/Ve points

2. Use the following path to access the Points item:
needed).
8. Select the Hardware tab on the New <Point Type> Points dialog window.
Note: To map a 16-bit PLC register to a 16-bit packed point, see Mapping a 16-bit PLC Register
to a 16-bit Packed Point (see page 60).
9. Select third-party from the I/O Type drop-down menu.

10. Select one of the GE Mark options from the I/O module pull-down menu. The New <Point
Type> Points window appears with additional parameters.
126 OW350_58
Note: The following figure shows an example of the Insert New Analog Points window.
Figure 59: Hardware tab for GE Point name
11. Complete the information in the window as it pertains to the GE Mark V/VI/Ve driver then,
select the Ok or Apply button.
Continue using this V/VI/Ve procedure for every point you want to configure. Refer to the
Download, Reboot, and Load (see page 29) sections for information on downloading,
rebooting, and loading. I/O Access Path Examples for GE Mark V/VI/Ve (see page 130)
provides examples of I/O access paths for GE Mark V/VI/Ve. The following table discusses
the parameters that are common to all drivers and also to those that pertain to GE Mark
specifically.
Hardware tab field entries - GE Mark V/VI/Ve
FIELD DESCRIPTION
IO type This is set to Third Party to indicate a third-party point.
OW350_58 127
FIELD DESCRIPTION
Emerson recommends that devices 1 and 2 be reserved for Q-line and Ovation I/O
since these devices correspond to actual PCI slot numbers.
Since there is typically no hardware associated with a third-party driver, Emerson

recommends that third-party drivers be assigned to devices 3, 4, or 5. Otherwise, if a
third-party driver were assigned to device 1 or 2, then PCI slot 1 or 2 could not be
used.
IO channel This is disabled for third-party points.
IO task index Points are grouped by the Control task index so that they can be updated (scanned)
at different rates. The Control task rate is set in the Controller Configuration
(Control Task) Parameters dialog box.

Control Tasks 3, 4, and 5 are user-configurable and the scan rate should be
appropriate for the application and system needs.
Emerson recommends that third-party points be given their own task area. The scan
rate should be no faster than one second because of the communication overhead.
I/O module units Not Applicable for this application.
IO access path This field is active when third-party is selected for the I/O type.
This field is automatically filled in from the information entered in the Hardware tab or
from imported information. Refer to Access Path Examples for Mark V and for Mark
VI.
GE Point Name Name of the GE point from where the data is being retrieved, for example,
L41BKRC_CPB
GE Controller Name Name of GE Controller, for example, GA
GE Type Refer to Valid record types for GE points.

GE Node Index 1
128 OW350_58
FIELD DESCRIPTION
GE Datatype GE Mark V Analog

Signed or Unsigned
GE Mark VI/Ve Analog
Short Integer = Signed 8-bit integer
Unsigned Short Integer = Unsigned 8-bit integer
Integer = Signed 16-bit integer
Unsigned Integer = Unsigned 16-bit integer
Double Word = Signed 32-bit integer
Unsigned Double Word = Unsigned 32-bit integer
GE Mark V/VI/Ve Digital
No Datatype column; Datatype is automatically set to Boolean
GE Point Index Read-only field for internal use only
OW350_58 129
14.5 What are I/O access path examples for GE Mark V/VI?
The IO Access path is filled in automatically from the information entered in the Hardware tab or
The following are examples of the format that appears in the Hardware tab IO access path field
for General Electric third-party points:
Example for GE Mark V
L41BKRC_CPB PUSHBUTTON GA 1 S
where:
L41BKRC_CPB GE Point Name
GA GE Controller Name
PUSHBUTTON GE Type
1 GE Node Index
S GE Data Type
Example for GE Mark VI
L41BKRC_CPB PUSHBUTTON GA 1 REAL

where:
L41BKRC_CPB GE Point Name
GA GE Controller Name
PUSHBUTTON GE Type
1 GE Node Index
REAL GE Data Type
Valid GE Types
POINT TYPE RECORD TYPE NOTES:
ALARM Digital Point (LD, DD) Default point is not SOE. To define the point as an SOE point, select
Records the SOE box under the Config tab in the Point dialog box.
EVENT Digital Point (LD, DD) Default point is not SOE. To define the point as an SOE point, select
Records the SOE box under the Config tab in the Point dialog box.
SWEVENT Digital Point (LD, DD) Mark V only.

Records
PUSHBUTTON Digital Point (LD, DD) For both Mark V and Mark VI, the digital values must be true for at
Records least two seconds to ensure being sent to GE.
SETPOINT Analog Point (LA, DA) For scaling of setpoints, use Top Output Scale and Bottom Output
Records Scale for INT and UINT. For other data types, (USINT, SINT, UDINT,
DINT, REAL), scaling is always one to one.
130 OW350_58
POINT TYPE RECORD TYPE NOTES:
PERIODIC Analog (LA, DA) and For Gain and Bias on the Analog points, use the Conversion
Digital (LD, DD) Coefficients (under the Instrumentation tab) to assign the information
Records. to the point.
For Analog points, the incoming value can be interpreted as either
signed two’s complement values or unsigned values. If the sign is not
signified, then the default is signed
OW350_58 131
S E C T I O N 15
15 MHI driver configuration
IN THIS SECTION
MHI driver overview......................................................................................................... 133

I/O access path examples for MHI .................................................................................. 137
15.1 MHI driver overview
The Mitsubishi Heavy Industries MHI driver enables communication between the MHI and the
Ovation DCS. Data is exchanged through a combination of TCP/IP and a proprietary MHI
protocol. The MHI Interface allows an exchange of data between the Ovation Network and the
MHI Control.

fourth driver item.


4, or 1 and 5.
Parameters tab.
15.1.2 To set MHI device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box.
OW350_58 133
Figure 60: Controller Driver Parameters fields (MHI)
Controller Driver Parameters field descriptions (MHI)
FIELD DESCRIPTION
Default = Ovation
IP Address (Primary Assigns an IP address to the primary drop for the MHI interface.
Drop)
Default = 255.255.255.255
IP Address (Partner Assigns an IP address to the partner drop for the MHI interface. Note that if this is not
Drop) a redundant drop, this field is not active.
Default = 10,000
134 OW350_58
15.1.3 To insert an MHI device

appears.
6. Select MHI from the I/O Device Type pull-down menu.
8. Select the Apply button. Notice that the new MHI I/O Device item now appears in the system
tree. The title of the I/O Device item contains the device number and type.
15.1.4 To configure MHI points

needed).
9. Select Third-Party from the I/O Type drop-down menu.
OW350_58 135
10. Select MHI from the I/O module pull-down menu. The New <Point Type> Points window
appears with additional parameters.
Figure 61: New Analog Points - MHI
11. Complete the information in the window as it pertains to the MHI driver. The following table
discusses the parameters that are common to all drivers and also to those that pertain to MHI
specifically. I/O Access Path Examples for MHI (see page 137) provides examples of I/O
access paths for MHI.
the mapping points procedure for every point you want to map. Refer to the Download,
Reboot, and Load (see page 29) sections for information on downloading, rebooting, and
loading
Hardware Tab fields entries — MHI
FIELD DESCRIPTION
IO type This is set to Third-Party to indicate a third-party point.
PCI slot number is needed. Then device 1 is reserved for that card, and any third-party
IO channel This is disabled for MHI third-party points.
136 OW350_58
15.2 I/O access path examples for MHI
FIELD DESCRIPTION
IO access path Filled automatically from the information entered in the Hardware tab fields that are
specific to MHI or from imported information.
Termination fields Not applicable for third-party points.
Point Name Name of the MHI point from where the data is being retrieved.
Type See I/O Access Path Examples for MHI (see page 137).
The I/O Access Path is filled in automatically from the information entered in the Hardware tab or
a third-party point:
L45BRKC INPUT
where:
L45BRKC Point Name
INPUT Type
Additional Example:
HTRAISE:20 OUTPUT
where:
20 is the point offset supplied by MHI and is only needed for OUTPUT point types.
Valid MHI types
INPUT Analog (LA) and Digital point Data received from the MHI system.
(LD) records
OW350_58 137
OUTPUT Analog (LA) and Digital point Control commands and setpoints from the Ovation
(LD) records System.
138 OW350_58
S E C T I O N 16
16 Modbus driver configuration
IN THIS SECTION
Modbus overview ............................................................................................................ 139

I/O access path examples for Modbus ............................................................................ 144
16.1 Modbus overview
Modbus is an open protocol which is used by many manufacturers of industrial controls. The
Ovation Link Controller Modbus Interface provides communication between an Ovation Link
Controller (LC) module (also known as an RLC module) and one or more external devices.
The LC Modbus Interface software interprets a configuration file which defines messages
between Modbus registers, coils, inputs, and Link Controller (LC) module memory locations. The
interface then sends requests to the Modbus slaves to read and write Modbus data.

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 139
16.1.2 To set Modbus device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box; refer to the following
figure and table.
Figure 62: Controller Driver Parameters window (Modbus)
Controller Driver Parameters fields descriptions (Modbus)
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third-party devices)
Default = Ovation
Modbus PLC PLC-1, PLC-2, PLC-3, PLC-4, or PLC-5
Assigns a hostname to each Modbus slave. This hostname is included in the “IO
access path” field of a Modbus third-party point to match the point with a slave
device. (See the Ovation Developer Studio User Guide).
Note: The host names specified in the I/O access path are in the form PLC_1, PLC_2, and
so forth.
140 OW350_58
FIELD DESCRIPTION
PLC Selects the communication protocol for the selected hostname.

Communication  Reserved 1 = Unused.
Protocol
 RTU on TCP = RTU Modbus messages are sent to the slave over a TCP/IP socket
connection.
 Open Modbus TCP = Open Modbus TCP protocol. Similar to the RTU protocol. RTU
message structure with a 6 byte header added in front of each message and CRC is
removed. For use on TCP/IP.
 Reserved 4 = Unused.
 RTU on TCP (write by exception) = RTU Modbus messages are sent to the slave over a
TCP/IP socket connection. Write requests are sent when a change is detected in the point
value.
 Open Modbus on TCP (write by exception) = Open Modbus TCP protocol. Similar to the
RTU protocol. Write requests are sent when a change is detected in the point value.
 Reserved 7 = Unused.
Baud Rate This is used only by the serial protocol for the selected hostname.
Default = 9600
Response Timeout Defines the message response timeout in milliseconds for the selected hostname. This is
(milliseconds) the amount of time the driver waits for a response from the slave before setting the point to
bad quality.
Default = 1000 milliseconds
Reconnect Defines the amount of time the driver waits before trying to re-establish a connection.
Timeout Default = 30
(seconds)
PLC IP Address Assigns an IP address for the selected hostname. This address must be programmed into
the Modbus slave using its loader software.
Address 255.255.255.255 disables the hostname
Socket Number Assigns the socket number for the selected hostname used by the Modbus slave. This is
only required for a TCP/IP protocol.
Default = 502
16.1.3 To insert a Modbus device

appears.
6. Select Modbus from the I/O Device Type pull-down menu.
8. Select the Ok or Apply button. Notice that the new Modbus I/O Device item now appears in
the System Tree. The title of the I/O Device item contains the device number and type.
OW350_58 141
16.1.4 To configure Modbus points

1. Access the Developer Studio.
needed).
9. Select Third Party from the I/O Type drop-down menu.

10. Select Modbus from the I/O module pull-down menu. The New <Point Type> Points window
Figure 63: New Analog Points - Modbus
142 OW350_58
11. Complete the information in the window as it pertains to the Modbus driver. The following
table discusses the parameters that are common to all drivers and also those that pertain to
Modbus specifically. I/O Access Path Examples for Modbus (see page 144) provides
examples of I/O access paths for Modbus.
Hardware tab fields descriptions — Modbus
FIELD DESCRIPTION
IO type This is set to Third-party to indicate a third-party point.
IO channel This is disabled for analog points. Separate points that have the identical I/O access
paths shares the same 16-bit value field in the Controller. For digital and packed points,
the I/O channel determines which bit of the 16-bit value each point uses.
(Control Task) dialog box.
IO access path Filled in automatically from the information entered in the Hardware tab fields that are
specific to Modbus or from imported information.
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the Register-
to-Register Mapping check box is recommended so that all IO access paths are
identical. This minimizes memory usage in the Controller.
Termination fields Not applicable for third-party points. Fields do not appear on the dialog box.
PLC Host Index Identifies the slave hostname for TCP/IP communication (optional and not order
dependent). This was defined in the New Device Numbers window.
The choices are: PLC-1 - PLC-5.
Input or Output Indicates whether the Modbus slave value is read into a process point or written from a
point.
The choices are: Input from PLC or Output to PLC.
Slave Address Node address of the Modbus slave.
OW350_58 143
16.2 I/O access path examples for Modbus
FIELD DESCRIPTION
Register Number Modbus coil or register number:

Number
Address
1 - 9999
Discrete Coils 0 - 9998
10001 - 19999
Input Coils 0 - 9998
30001 - 39999
Input Registers 0 - 9998
40001 - 49999
Holding Registers 0 - 9998
Data Type Used to interpret the data type of the Modbus register (optional and not order
dependent).
Choices are: Signed Short, Unsigned Short, Signed Long, Unsigned Long, and Float
Default = Unsigned Short
Note: Floating-point values are stored in two contiguous 16-bit registers.
Byte Order Key words that allow register byte order to be changed.
The choices are: Swap Bytes, Swap Words, and Swap Bytes and Words.
a Modbus third-party point:
MODBUS 3 IN NNNNN SHORT PLC_4
where:
MODBUS Identifies a Modbus driver point.
3 Modbus slave address.

IN Input or Output field
NNNNN Register number.
SHORT Data Type
PLC_4 Host Index
 Set discrete coil number 10 (address 9) at plc_3. Slave addresses are usually ignored by
TCP/IP devices.
MODBUS 2 OUT 10 PLC_3
 Read input register 30008 (address 7) at plc_1 as a signed short.
MODBUS 4 IN 30008 SHORT PLC_1
144 OW350_58
 Read holding registers 40001 and 40002 as a float from plc_1.

MODBUS 1 IN 40001 FLOAT PLC_1
OW350_58 145
S E C T I O N 17
17 Profibus device driver configuration
IN THIS SECTION
Profibus overview ............................................................................................................ 147
17.1 Profibus overview
Profibus (Process Field Bus) DP (decentralized periphery) is an all-digital, two-way

communication system that links devices (also known as slaves) and automation systems. A
decentralized periphery uses a network bus (in this instance, Profibus) between the Controller
(Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as compared to a
programmable logic Controller (PLC) that has its I/O arranged centrally. At the base level in the
hierarchy of plant networks, Profibus serves as a Local Area Network (LAN) for instruments.
The Ovation implementation of Profibus DP uses hardware and software components to integrate
Profibus devices with Ovation technology through a Profibus I/O module that resides in a
Controller cabinet. Each Profibus I/O module provides two ports (where each port acts as an
independent Profibus DP network). Ovation can support redundant Profibus masters on two
different Profibus segments and eliminates the need for an Ethernet switch and a gateway
module.
17.1.1 To add a new I/O device number to the Controller using the Developer
Studio
2. Use the system tree to navigate to the Device Number item:
Systems > Network > Units > Drops > Configuration > Controller > Devices > Device
Number
3. Right-click on the Device Number.
OW350_58 147
4. Select Insert New. The Insert New Device Numbers Wizard appears.
Figure 64: Insert New Device Numbers wizard
5. From the Value drop-down menu, select an unused number (for example, you might start
with 5, and continue numbering successive devices sequentially).
6. Click Finish. The New Device Numbers window appears:
7. From the I/O Driver Type drop-down menu, select PROFIBUS MODULE.
8. Click OK.
9. Use the Developer Studio system tree to navigate to I/O Devices:
10. Right-click on the I/O Devices to select Insert New. The Insert New I/O Devices wizard
appears.
148 OW350_58
11. From the I/O Device Number drop-down menu, select an unused number greater than 1 (for
example, you might start with 2 and continue numbering sequentially).
12. Click Finish.
13. Select PROFIBUS from the I/O Device Type drop-down menu.
14. Click Finish. The New I/O Device window appears.
15. Click OK.
Note: You only have to perform this task once for each Controller that utilizes Profibus.
17.1.2 To insert a Profibus I/O module in the Developer Studio

2. Use the system tree to navigate to an empty slot under your Ovation I/O Interface:
Systems > Network > Units > Drops > I/O Devices > IOIC > I/O Interfaces > Branch >
Slot
3. Select the Ovation module in the slot that you want to modify.
4. Right-click on the Ovation module and select Insert New. The Insert New Ovation Module
wizard appears.
Figure 65: Insert New Ovation Module wizard
5. Select Profibus BusModule.

6. Click Finish. The New Ovation Module window appears.
7. Emerson recommends that you leave the Module Record Point Name in the Value column
empty.
OW350_58 149
8. Navigate to the Module tab.
Figure 66: Module tab
9. Select radio button: Simplex/Port Redundancy (the standard configuration).

10. Click OK to finish.
150 OW350_58
11. The following figure shows the two ports (P01 and P02) that have been automatically created
in the appropriate slot in the Developer Studio.
Figure 67: P01 and P02
OW350_58 151
Notes:
If Ovation Profibus Port Redundancy is going to be used for ports on this module, the user must
select Simplex/Port Redundancy.
You must perform this task for each Profibus I/O module that you add.
17.1.3 To add a module record point name

2. Use the system tree to navigate to the appropriate Module Points:
Systems > Network > Units > Drops > Points > Module Points
3. Right-click on the Module Points and select Insert New. The Insert New Module Points
wizard appears.
Figure 68: Insert New Module Points wizard
4. Type a point name.

5. Pick a frequency.
152 OW350_58
6. Click Finish. The New Module Points window appears.
Figure 69: New Module Points window
7. Navigate to the Hardware tab.
Figure 70: New Module Points Hardware tab
8. Choose the I/O module from the location where you added it.
9. Click OK. If you navigate to your card and Refresh, you will see the fully-qualified module
record point name (for example, TEST.UNIT@PB).
Note: You must perform this task for each Profibus I/O module that you add.
OW350_58 153
17.1.4 To assign a node record to each of your ports
Note: You must open each port that you want to use and assign it a node record.

2. Use the system tree to navigate to a port:
Systems > Network > Units > Drops > I/O Devices > I/O Interfaces > Branch > Slot >
Port
3. Select the port that you want to update (for example, P01 or P02).
4. Right-click the port and select Open. A port configuration window appears:
Figure 71: Port configuration window
5. Type an Ovation Point Name. Do not fully qualify the point name (for example, type TEST,
not TEST.UNIT@PB). If this name currently does not exist in your system, it is added when
you click OK.
154 OW350_58
Note:
Module Redundancy must be Simplex.
Channel must be set to Channel A or Channel B.
6. Enter an I/O task index number in the I/O task index field.
7. Click Ok.
Note:
You must perform this task for each Profibus I/O module that you add.
All points assigned to a port must be assigned to the same control task or you will receive an
error when you attempt to load.
OW350_58 155
S E C T I O N 18
18 RTP I/O driver configuration
IN THIS SECTION

To set RTP I/O device number parameters .................................................................... 157
To insert an RTP I/O device ............................................................................................ 159
To configure RTP I/O points ............................................................................................ 159
I/O access path examples for RTP I/O............................................................................ 162

fourth driver item.


4, or 1 and 5.
Parameters tab.
18.2 To set RTP I/O device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box, see the following figure
and table.
OW350_58 157
18.2 To set RTP I/O device number parameters
Figure 72: Controller Driver Parameters field (RTP I/O)
Controller Driver Parameters field descriptions (RTP I/O)
FIELD DESCRIPTION
Default = Ovation
IOBC Hostname iobc-1, iobc-2, iobc-3, iobc-4, or iobc-5
Assigns a hostname to a RTP IOBC6700. One driver can monitor up to five IOBCs.
For example, a third-party point with hostname index 1 in its “IO access path” field
accesses data in iobc-1.
IP Address Assigns an IP address for the selected hostname. This address must be programmed
into the IOBC6700 using its loader software.
Address 255.255.255.255 disables the hostname.
Socket Number Assigns the socket number used by the IOBC.
Default = 2004
Timeout (milliseconds) Defines the message response timeout in milliseconds.
This is the amount of time the driver waits for a response from the RTP before setting
the point to bad quality.
Default = 500
Reconnect Timeout Defines the amount of time the driver waits before trying to re-establish a connection.
(seconds)
Default = 30
158 OW350_58
18.3 To insert an RTP I/O device
18.3 To insert an RTP I/O device

appears.
6. Select RTP I/O from the I/O Device Type pull-down menu.
8. Select the Apply button. Notice that the new RPT I/O Device item now appears in the System
Tree. The title of the I/O Device item contains the device number and type.
18.4 To configure RTP I/O points

needed).

10. Select RTP from the I/O module pull down menu. The New <Point Type> Points window
OW350_58 159
Note: The following figure shows an example of the Insert New Analog Points Window.
Figure 73: New Analog Points - RTP
11. Complete the information in the window as it pertains to the RTP driver. The table below
discusses the parameters that are common to all drivers and to those that pertain to RTP
specifically. I/O Access Path Examples for RTP I/O (see page 162) provides examples of I/O
access paths for RTP.
Hardware Tab fields entries — RTP I/O
FIELD DESCRIPTION
IO type This is set to Third-Party to indicate a third-party point.
IO module The third-party driver is assigned a device number in the Insert New Device
Numbers Wizard. This field is used to match the point with the device number.
Note: There can be no gaps in the assigned device numbers. For example, if
only one PCI slot number is needed. Then device 1 is reserved for that card,
and any third-party driver would be assigned as device 2 (not 3, 4, or 5).
160 OW350_58
FIELD DESCRIPTION
IO channel This is disabled for analog points. Separate points that have the identical I/O
access paths shares the same 16-bit value field in the Controller. For digital and
packed points, the I/O channel determines which bit of the 16-bit value each
point uses.
IO task index Points are grouped by the Control task index so that they can be updated
(scanned) at different rates. The Control task rate is set in the Controller
(Control Task) Configuration Parameters dialog box (shown in the Configuring Controller
Software section of this manual).
Control Tasks 3, 4, and 5 are user configurable and the scan rate should be
appropriate for the application and system needs.
Emerson recommends that third-party points be given their own task area. The
scan rate should be no faster than one second because of the communication
overhead.
No more than 2,000 points can be assigned to a task area.
IO access path Automatically from the information entered in the Hardware tab fields that are
specific to RTP I/O or from imported information.
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the
Register-to-Register Mapping check box is recommended so that all IO access
paths are identical. This minimizes memory usage in the Controller.
Termination fields Not applicable for third-party points. Fields do not appear on the dialog box.
IOBC Host Index Hostname index that was defined in the New Device Numbers window
(Controller Driver Parameters tab, set for Allen-Bradley).
The choices are: IOBC-1 - IOBC-5.
Card Type RTP IO card type keyword. Choices are:
Analog Input
Unsigned Analog Input
Analog Output
Unsigned Analog Output
Analog Pulse Train Output
Analog Wide Range Input
Unsigned Analog Wide
Unsigned 16-bit Analog Input
Digital Input
Digital Output
Digital Pulse Train Input
Device Address Device address of RTP card cage.

The choices are: 0 through 15.
Card Slot For digital cards, this is the slot number for the card.
For analog cards, this is the AD converter address of the card.
Channel Number Analog channel number.
OW350_58 161
18.5 I/O access path examples for RTP I/O
FIELD DESCRIPTION
Gain Code RTP gain code.

Gate Card Slot For digital cards, it is the bit number of the card.
For analog cards, it is the gate slot address of the card.
18.5 I/O access path examples for RTP I/O
The IOBC driver interfaces to an RTP IOBC 6700 over a TCP/IP Ethernet link. The messages that
the driver sends to the IOBC contain a command word. The information that appears in the IO
access path field is used to encode this command word and the command word for each type of
RTP IO is different. Therefore, RTP IO card documentation is required in order to configure this
field.
an IOBC third-party point:
IOBC 1 AOUT 3 4 6 0 2
where:
IOBC Identifies an RTP IOBC driver point.
1 Host Index
AOUT Card Type
3 Device Address
4 Card Slot
6 Gate Card Slot
0 Analog channel number.
2 Gain code.
162 OW350_58
S E C T I O N 19
19 Toshiba driver configuration
IN THIS SECTION
Toshiba driver overview .................................................................................................. 163

I/O access path examples for Toshiba ............................................................................ 167
19.1 Toshiba driver overview
The Toshiba driver is a communication interface between an Ovation Controller (LC) module and
a Toshiba Controller. The interface maps process point data between an Ovation Controller and
the Toshiba Controller.

fourth driver item.


4, or 1 and 5.
Parameters tab.
19.1.2 To set Toshiba device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box, see the figure and
table below.
OW350_58 163
Figure 74: Controller Driver Parameters fields (Toshiba)
Controller Driver Parameters field descriptions (Toshiba)
FIELD DESCRIPTION
Default = Ovation
IP Address (Primary Assigns an IP address to the primary drop for the Toshiba interface.
Drop)
Default = 255.255.255.255
IP Address (Partner Assigns an IP address to the partner drop for the Toshiba interface. Note that if this is not
Drop) a redundant drop, this field is not active.
Default = 10,000
Fail Controller on Allows you to determine if this interface can fail the Controller when an error occurs.
Error
If False is selected, the Controller does NOT fail over to Backup when the response time
limit (set in the Timeout parameter) is exceeded.
If True is selected, the Controller does fail over to Backup when the response time limit
(set in the Timeout parameter) is exceeded.
164 OW350_58
19.1.3 To insert a Toshiba device

appears.
6. Select Toshiba from the I/O Device Type pull-down menu.
8. Select the Apply button. Notice that the new Toshiba I/O Device item now appears in the
system tree. The title of the I/O Device item contains the device number and type.
19.1.4 To configure Toshiba points

needed).
7. Press the Finish button. The New <Point Type> Points dialog box appears.
8. Select the Hardware tab on the New <Point Type> Points dialog box.
Note: To map a 16-bit PLC register to a 16-bit packed point, see To Map a 16-bit PLC Register
OW350_58 165
10. Select Toshiba from the I/O module pull-down menu. The New <Point Type> Points window
Figure 75: New Analog Points - Toshiba
11. Complete the information in the window as it pertains to the Toshiba driver. The following
table discusses the parameters that are common to all drivers and also to those that pertain to
Toshiba specifically. I/O Access Path Examples for Toshiba (see page 167) provides
examples of I/O access paths for Toshiba.
Load (see page 29) sections for information on downloading, rebooting, and loading
Hardware tab fields entries — Toshiba
FIELD DESCRIPTION
IO type This is set to third-party to indicate a third-party point.
IO channel This is disabled for Toshiba third-party points.
166 OW350_58
19.2 I/O access path examples for Toshiba
FIELD DESCRIPTION

IO access path This field is filled automatically from the information entered in the Hardware tab fields
that are specific to Toshiba or from imported information.
Termination fields Not applicable for third-party points. Fields do not appear in the dialog box.
Point Name Name of the Toshiba point from where the data is being retrieved.
Type See I/O Access Path Examples for Toshiba (see page 167).
a Toshiba third-party point:
L45BRKC INPUT
where:
L45BRKC Point Name
INPUT Type
 HTRAISE OUTPUT
 ALM1HI ALARM
Valid Toshiba Types
INPUT Analog (LA) and Digital point (LD) records Data received from the Toshiba system.
OUTPUT Analog (LA) and Digital point (LD) records Control commands and setpoints from the
Ovation System.
OW350_58 167
ALARM Digital (LD) Point Records Alarms received from the Toshiba system.
168 OW350_58
S E C T I O N 20
20 External Ovation network driver configuration
IN THIS SECTION
External Ovation network devices overview ................................................................... 169
20.1 External Ova tion netw ork devices overview
The External Ovation Network Driver allows you to map a local point to a point on an external
network. A local point must be mapped to a remote point in order to use the remote point in
control on the local system. This procedure explains the configuration of the device driver and the
mapping of the points. However, the remote system must be previously defined. (See Ovation
Multiple Networks User Guide.) Make sure you have completed the procedures in To Insert New
Device Numbers (see page 65) before continuing.

fourth driver item.


4, or 1 and 5.
Parameters tab.
OW350_58 169
20.1 External Ovation network devices overview
20.1.2 To set external Ovation network device number parameters

1. Make the appropriate choices in the New Device Numbers dialog box as illustrated in the
following table then, select the Ok or Apply button.
Figure 76: Controller Driver Parameters tab - driver-specific fields
Controller Driver Parameters tab descriptions - driver-specific fields
FIELD DESCRIPTION
Default = Ovation
Fail Control on Error Allows you to determine if this interface can fail the Controller when an error occurs.
20.1.3 To insert external Ovation network I/O devices

170 OW350_58

appears.
5. Pull down the I/O Device Number menu.
7. Pull down the I/O Device Type menu.
8. Select External Ovation Network.
9. Click the Finish button. The New I/O Devices dialog box appears, showing the information
you just entered.
20.1.4 To map external Ovation network points

3. Select either an Analog, Digital, or Packed point to map.
4. Right-click on the applicable Points item.
5. Select Insert New. The Insert New <Point Type > Points Wizard appears (where <Point
Figure 77: New Packed Points window
OW350_58 171
needed).
7. Press the Finish button. The New <Point Type> Points dialog appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.
Note: The following figure shows an example of the Insert New Analog Points Wizard.
Figure 78: New Analog Points — Hardware tab
Note: For packed points, you may configure all 16-bits of the point for different I/O modules.
However, when configuring these points for External Ovation Network, you must select the
Register to Register Mapping checkbox on the New Packed Points window (this window
appears after completing the Insert New Packed Points Wizard). This parameter indicates that
all of the bits should be configured for the same module.
20.1.5 To reconfigure an external Ovation network driver

3. Right-click on the I/O Devices item and select Insert New from the resulting pop-up menu.
The Insert New I/O Devices Wizard appears.
4. Select the I/O Device Number (use the first available 5-11).
5. Select External Ovation Network from the I/O device Type pull-down menu.
172 OW350_58
7. Select the Apply button. Notice that the new External Ovation Network I/O device item now
appears in the system tree. The title of the I/O device item contains the device number and
type.
OW350_58 173
S E C T I O N 21
21 Using the Controller Diagnostics tool
IN THIS SECTION
Controller Diagnostics tool .............................................................................................. 175

Software platforms that Controller Diagnostics supports ................................................ 176
Controller Diagnostics window ........................................................................................ 177
Controller List in the Controller Diagnostics window ....................................................... 180
Controller Overview panel in the Controller Diagnostics window ................................... 182
Controller Diagnostics Update Backup function .............................................................. 183
Control Task Information tab in the Controller Diagnostics window ............................... 185
I/O Information tab in the Controller Diagnostics window ............................................... 187
What firmware can be downloaded to the I/O modules through the
Controller Diagnostics window? ...................................................................................... 188
Software Versions tab in the Controller Diagnostics window .......................................... 190
Point Details tab in the Controller Diagnostics window ................................................... 191
Sheet Information tab in the Controller Diagnostics window .......................................... 192
Refresh function for the Controller Diagnostics window ................................................. 193
21.1 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 177). 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 180).
 Update data in a backup Controller to match the data in the primary Controller (see page
183).
 Display information about the control tasks for that Controller (see page 185).
 Display information about I/O modules that interface to the selected Controller (see page
187).
 Download firmware to intelligent I/O modules that interface to the selected Controller (see
page 189).
The Controller Diagnostics tool has an online help system that provides information on the
Controller Diagnostics application. You can access this help in the following ways:
 By pulling down the Help menu on the main Controller Diagnostics window.
 By pressing the F1 key on the keyboard while the cursor is located in one of the Controller
Diagnostics window tabs or in one of the window sections (Controller List or Controller
Overview).
OW350_58 175
21.2 Software platforms that Controller Diagnostics supports
21.2 Softw are platforms that Controller Diagnostics supports
The Controller Diagnostics function is designed to run on both Windows-based and Solaris-based
Ovation systems. In general, functionality remains the same for both platforms. However, where
differences exist between the platforms, information is specifically labeled "for Window-based
systems" or "for Solaris-based systems."
Note: Where functionality is the same for both platforms, this document uses Windows-based
graphics.
176 OW350_58
21.3 Controller Diagnostics window
21.3 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 179).
The left portion of the Controller Diagnostics window contains a Controller Overview section (see
page 182) that provides internal information about the selected Controller. This section also
contains an Update Backup button (see page 183) that can update the data in a backup
Controller to match the data in the primary Controller.
Below the Controller Overview is the Controller List (see page 180) 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 185) 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 190) to identify the software version of each
software package that is installed on the selected Controller.
 Use the Point Details tab (see page 191) to list the points originated and received by the
selected Controller.
 Use the Sheet Information tab (see page 192) to provide information about the elements on
control sheets for the selected Controller.
Figure 79: Controller Diagnostics window
OW350_58 177
21.3.1 To access the Controller Diagnostics tool in a Windows -based Ovation

system
1. Access an Ovation workstation.
2. At the workstation, select Start > Ovation > Ovation Utilities > Diagnostics.
The Controller Diagnostics window appears.
Figure 80: Controller Diagnostics window
21.3.2 To access the Controller Diagnostics tool in a Solaris-based Ovation

system
1. Log in to the Engineering Station.
2. Select Drop Functions from the top-level Engineering Station menu. The Drop Functions
menu appears.
3. Select Controller from the Drop Functions menu. The Controller menu appears.
4. Select Controller Diagnostics from the Controller menu. The Controller Diagnostics window
appears.
21.3.3 Controller Diagnostics menu bar
The Controller Diagnostics window contains a menu bar that provides three drop-down menus:
Figure 81: Controller Diagnostics menu bar
178 OW350_58
Controller Diagnostics menus
MENU DESCRIPTION
File  Select a Controller - Displays the Select a Controller window (see page 180).
 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.
21.3.4 Controller Diagnostics toolbar
The Controller Diagnostics window provides a toolbar. Drag the mouse over the toolbar icons to
identify each icon.
Figure 82: Controller Diagnostics toolbar
The toolbar icons (left to right) perform the following functions:

 The window icon displays the Select a Controller window (see page 180).
 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.
OW350_58 179
21.4 Controller List in the Controller Diagnostics window
21.4 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 83: Controller List
Select the Controller whose information you want to display. Double-click the desired Controller
and the data for the first Controller listed in a redundant pair displays (Drop11 in the preceding
figure). Right-click the desired Controller and a menu appears listing the names of the redundant
Controllers so you can select the desired Controller.
Note: You can also select a Controller from the File menu or in the toolbar.
21.4.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 180) window
(located beneath the Controller Overview panel).
OR
180 OW350_58
21.4 Controller List in the Controller Diagnostics window
3. Select the Select a Controller item from the File menu or from the toolbar. A pop-up window
appears. Enter a Controller name or IP address in the pop-up window. Information about that
Controller now appears in the Controller Diagnostics window.
Figure 84: Select a Controller Drop dialog box
OW350_58 181
21.5 Controller Overview panel in the Controller Diagnostics window
21.5 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. This information appears
along with each tab that you select.
Figure 85: Controller Overview panel
Fields in Controller Overview panel (Primary and Partner Controllers)
FIELD FIELD DESCRIPTION
Drop Name Drop number for the Controller drop that you highlight in the Select a Controller
Drop section of the Controller Diagnostics window. Right-click the drop name to
display the Point Menu for the Drop Point (DU record).
IP Address Internet Protocol (IP) address for the selected Controller drop.
Ethernet Address Unique hardware address for each Ethernet port for the selected Controller drop.
Controller Type Displays the type of Ovation Controller:

 OCR1100
 OCR400
Processor Unique hardware CPU type for the selected Controller drop (for example, Pentium).
182 OW350_58
21.6 Controller Diagnostics Update Backup function
FIELD FIELD DESCRIPTION
Mode Displays the mode of the Controller:

 Control
 Backup
Fault ID Displays the Fault Code number (66) if the Controller is in fault, or 0 if the
Controller is not in fault.
OS Version Version of the Operating System running on the selected Controller.
Kernel Version Version of the internal Ovation Controller software.
Controller Version Version of the Ovation Controller software.
Total Ram Total amount of memory available in the Controller's RAM disk (kbytes).
Sheet Count Number of Control Builder sheets processed by the selected Controller.
Originated Points Number of originated points in the Controller.
Received Points Number of received points in the Controller.
Update Backup button Updates data in the backup Controller to match data in the primary Controller.
(see page 183)
21.6 Controller Diagno stics Update Backup function
You can use the Update Backup function when a Drop Load function for a Controller has failed
and you have to clear and reload the Controller. This puts the Controller into backup, but since it
has been cleared, a mismatch may now exist between this backup Controller and the primary
Controller.
Note: You can use the Drop Details diagram to determine if a mismatch exists for your
Controller.
After determining the cause of the failure (by analyzing the messages and fault codes) and
correcting the problem, you can reconcile the mismatch smoothly (without “bumps”) by using the
Update Backup function (see page 183).
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.
21.6.1 To update your backup Controller in the Controller Diagnostics window

1. Access the Controller Diagnostics window, select Start > Ovation > Ovation Utilities >
Diagnostics
2. Select the backup Controller that you want to update. The drop name of the backup
Controller appears at the top of the Controller Overview section of the window.
3. Select the Update Backup button. The data is loaded from the Controller that is “in control” to
the backup Controller.
4. A Diagnostics window appears displaying the number of points that updated and advises you
to reboot the Controller. If you want this drop to become the drop in control you must reboot
the Controller that is in control through the Developer Studio:
OW350_58 183
21.6 Controller Diagnostics Update Backup function
5. 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 7.
d) For redundant drops, the Select a drop to reboot dialog box appears.
 Select the drop you want to reboot.
 Select Ok.
6. A confirmation dialog box appears.
7. Select Yes to close the window and execute the reboot process.
184 OW350_58
21.7 Control Task Information tab in the Controller Diagnostics window
21.7 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 (see page 46).
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 86: Control Task Information tab
OW350_58 185
21.7 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).

There is also a total field that displays the sum of each memory type and the sum of each point type for all
five tasks.
Status Status of the task area.
Total Control Displays the total available space for a control task.
Memory
Used Control Displays the total actual space used for a control task.
Memory
Capacity of Percentage of memory that is used for a control task.
Memory
Configured Displays the execution time (in milliseconds) that is configured for a control task.
cycle Time
(msec)
Average cycle Displays the average execution time (in milliseconds) that is actually used for a control
Time (msec) task.
Worst cycle Displays the longest execution time (in milliseconds) that is actually used for a control
Time (msec) task.
Analog Input Total number of analog input points in the task area.
Points
Digital Input Total number of digital input points in the task area.
Points
Packed Input Total number of packed input points in the task area.
Points
Analog Output Total number of analog output points in the task area.
Points
Digital Output Total number of digital output points in the task area.
Points
Packed Output Total number of packed output points in the task area.
Points
Total I/O Points Total number of analog, digital, and packed points in the task area.
186 OW350_58
21.8 I/O Information tab in the Controller Diagnostics window
21.8 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.
WARNING! Downloading firmware to an I/O module may cause the module to reset, so
your plant must be in a safe condition or must be shut down for at least five minutes
during the download process.
I/O points for a module are undefined during the reset process (30 seconds or more).
Therefore, communications priority is lowered during the firmware download process,
and may cause communication failures with the AMS Device Manager and/or multi-
variable messaging.
Figure 87: I/O Information tab
OW350_58 187
21.9 What firmware can be downloaded to the I/O modules through 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
21.9 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 differ from the firmware that is currently on your I/O
module and you might want to download the latest available firmware to your module.
If the module you have selected is not the type of module that can be downloaded with firmware,
the Download Available Firmware button is not activated.
Examples of I/O modules that contain firmware are:

 HART
 High Side Digital Output
 Ovation I/O Profibus
 Ovation I/O Fieldbus
 Ovation I/O DeviceNet
variable messaging.
188 OW350_58
21.9 What firmware can be downloaded to the I/O modules through the Controller Diagnostics window?
21.9.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. Select the I/O Information tab (see page 187).
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 88: Module Firmware Download window
4. Compare the firmware in the Controller Version field to the firmware in the Module Version
field to determine if you have the latest firmware on your I/O module.
5. If you do not have the latest firmware and you want to update the firmware, confirm that the
plant is in a safe condition before you perform the actual download.
variable messaging.
6. Highlight the files you want to download.

7. Select the Download button to load the latest firmware onto your I/O module.
8. If you need to reboot the selected I/O module (see page 190) after download, the Reboot
Module button is enabled.
OW350_58 189
21.10 Software Versions tab in the Controller Diagnostics window
21.9.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 will be displayed.
The reboot function requires that the module be running the 312 patch version or later of
RFTP.out and contain the RESTART.SCR script. The Controller should be running the 312 patch
version or later of diagsrvr. Reboot request failures may indicate that the latest software is not
loaded or is not running (module was not power cycled after download).
21.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 89: Software Versions tab
190 OW350_58
21.11 Point Details tab in the Controller Diagnostics window
21.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 90: 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.
OW350_58 191
21.12 Sheet Information tab in the Controller Diagnostics window
21.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
also use the scroll bars to locate information.
Figure 91: 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.
Type Record type of the algorithm point. Always LC.
Row Internal algorithm information.
192 OW350_58
21.13 Refresh function for the Controller Diagnostics window
FIELD DESCRIPTION
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.
21.13 Refresh function for the C ontroller Diagnostics w indow
Use this 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.
OW350_58 193
Index
A F
Adding Ovation Controllers to WDPF Q-line Features of the OCR1100 Controller • 3
I/O • 16 Foundation Fieldbus second generation (I/O
Allen-Bradley analog input cards • 105 modules) driver configuration • 107
Allen-Bradley DF-1 commands supported by
Ovation • 103 G
Allen-Bradley digital input cards • 105 GE Genius driver configuration • 117
Allen-Bradley driver overview • 97 GE Mark V/VI/Ve driver configuration • 123
C H
Configuring Controller drivers • 63 Hardware address and I/O status values for
Configuring device drivers in the Controller • Fault Code 66 • 25
63
Configuring the Controller • 35 I
Configuring the Controller software • 35
I/O access path examples for Allen-Bradley •
Control Task Information tab in the
104
Controller Diagnostics window • 185
I/O access path examples for MHI • 137
Controller Diagnostics menu bar • 179
I/O access path examples for Modbus • 144
Controller Diagnostics tool • 175
I/O access path examples for RTP I/O • 162
Controller Diagnostics toolbar • 179
I/O access path examples for Toshiba • 167
Controller Diagnostics Update Backup
I/O Information tab in the Controller
function • 183
Diagnostics window • 187
I/O interface ports • 9
Controller driver overview • 63
I/O Status values for Fault Code 66 • 25
Controller List in the Controller Diagnostics
Introduction to the OCR1100 Controller • 1
window • 180
Controller module components • 10 L
Controller Overview panel in the Controller
Diagnostics window • 182 Local Ovation I/O drivers configuration • 65
Converting to the OCR1100 Controller • 4 Local Q-Line drivers configuration • 81
Copyright Notice • 2 M
Custom Controller Networking • 54
MHI driver configuration • 133
D MHI driver overview • 133
Defining and addressing the I/O devices • 17 Modbus driver configuration • 139
Determining the NIC (network ethers) Modbus overview • 139
address of a drop • 36 N
E Network Interface ports • 7
Examples of extended I/O cabinet module O
addresses • 19
Examples of Relay Output module Online Controller restore mode • 55
addresses • 20 Ovation Controller hardware • 7
Examples of remote node I/O cabinet
module addresses • 21 P
External Ovation network devices overview • Point Details tab in the Controller
169 Diagnostics window • 191
External Ovation network driver Profibus device driver configuration • 147
configuration • 169 Profibus overview • 147
OW350_58 195
Index
To configure Toshiba points • 165

Q To confirm Controller Networking (network
Q-Line I/O module addressing • 22 item) • 48
To determine the IP address of a
R machine/drop • 36
To determine the NIC address from the error
RADIUS Server • 61
log • 36
Refresh function for the Controller
To determine the NIC hardware address
from the card label • 36
Remote Ovation I/O drivers configuration •
To download Controller drop configuration •
71
29
Remote Q-Line driver configuration • 89
To download firmware revisions to the I/O
Restore mode disabled (Default) • 56
modules through the Controller
Restore mode enabled (all drops) • 56
Restore mode enabled (redundant drops
To insert a Foundation Fieldbus I/O module
only) • 56
in the Developer Studio • 109
Restore mode engineering limitations • 57
To insert a GE Genius device • 119
Restore mode functions • 56
To insert a GE Mark V/VI/Ve device • 125
Restore mode performance issues • 57
To insert a local Ovation I/O module • 69
Restore mode point information issues • 58
To insert a Modbus device • 141
RTP I/O driver configuration • 157
To insert a new Controller drop • 37
S To insert a new drop point • 42
To insert a new local Ovation I/O branch • 69
Sheet Information tab in the Controller To insert a new local Q-line crate • 85
Diagnostics window • 192 To insert a new local Q-line module • 85
Software platforms that Controller To insert a new remote Q-Line crate • 93
Diagnostics supports • 176 To insert a new remote Q-line module • 94
Software Versions tab in the Controller To insert a Profibus I/O module in the
Diagnostics window • 190 Developer Studio • 149
Starting the Controller • 27 To insert a remote Ovation I/O module • 77
T To insert a remote Ovation I/O new branch •
76
To access the Controller Diagnostics tool in To insert a Toshiba device • 165
a Solaris-based Ovation system • 178 To insert an Allen-Bradley device • 98
To access the Controller Diagnostics tool in To insert an MHI device • 135
a Windows-based Ovation system • 178 To insert an RTP I/O device • 159
To add a Foundation Fieldbus (I/O module) To insert external Ovation network I/O
device • 112 devices • 170
To add a module record point name • 110, To insert local Ovation I/O devices • 67
152 To insert local Q-Line devices • 83
To add a new I/O device number to the To insert new control tasks • 48
Controller using the Developer Studio • To insert new device numbers • 65, 71, 81,
147 89, 97, 107, 117, 123, 133, 139, 157, 163,
To assign a node record to each of your 169
ports • 115, 154 To insert new remote Q-line nodes • 93
To configure alarm timestamping to the To insert remote Ovation I/O devices • 73
millisecond level • 60 To insert remote Ovation I/O new nodes • 75
To configure Allen-Bradley points • 100 To insert remote Q-line devices • 91
To configure GE Mark V/VI/Ve points • 126 To load a Controller drop • 31
To configure MHI points • 135 To map a 16-bit PLC register to a 16-bit
To configure Modbus points • 142 packed point • 60
To configure Ovation and Q-Line devices • To map external Ovation network points •
63 171
To configure RTP I/O points • 159 To modify an external Ovation networks
To configure the Controller for Ethernet device • 25
Remote Interface • 52 To modify an I/O device • 24
To configure third-party devices • 64
196 OW350_58
Index
To modify Controller Networking (drop item) What are I/O access path examples for GE
• 50 Mark V/VI? • 130
To open the Controller module front cover • What are Small Form-factor Pluggable
14 transceivers (SFPs)? • 10
To power-up the Controller • 28 What are the guidelines for positioning I/O
To reboot a Controller drop • 31 modules in cabinets? • 22
To reboot an I/O module • 190 What are the I/O Interface module status
To reconfigure an external Ovation network LEDs for the Controller? • 13
driver • 172 What are the Ovation Controller I/O
To replace Controller modules • 15 interfaces? • 7
To replace Ovation Controller module covers What are the Ovation I/O module base
• 15 types? • 33
To select a Controller in the Controller What are the processor module status LEDs
Diagnostics window • 180 for the Controller? • 11
To set Allen-Bradley device number What changes can you make to an I/O
parameters • 99 device? • 24
To set Controller parameters • 44 What firmware can be downloaded to the I/O
To set existing control tasks • 46 modules through the Controller
To set external Ovation network device Diagnostics window? • 188
number parameters • 170 What is a relay output module base? • 33
To set Foundation Fieldbus (I/O module) What is a standard I/O module base? • 33
parameters • 107 What is an Allen-Bradley driver? • 97
To set GE Genius device number What is an Ovation I/O module address? •
parameters • 118 17
To set GE Mark V/VI/Ve device number What is automatic failover control? • 5
parameters • 124 What is the addressing format for I/O
To set MHI device number parameters • 133 modules? • 17
To set Modbus device number parameters • What is the IP address of a Controller? • 36
140 What is the OCR1100 Controller? • 2
To set Ovation device number parameters • What is the process for planning the I/O for
66, 72, 82, 90 your system? • 32
To set RTP I/O device number parameters • What procedures are needed after
157 configuration changes to the Controller? •
To set the online Controller Restore Mode • 29
58 What should a new Controller drop item
To set Toshiba device number parameters • contain? • 37
163 What types of I/O modules does an
To update your backup Controller in the OCR1100 Controller support? • 24
To verify Controller Hardware • 27
Toshiba driver configuration • 163
Toshiba driver overview • 163
U
Using the Controller Diagnostics tool • 175
V
Verifying Controller hardware and power
status • 27
W
What additional software configurations are
needed for Controllers? • 59
What are I/O access path examples for GE
Genius? • 121
OW350_58 197

Controller OCR1100 User Guide For Ovation 3.5

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

Controller OCR1100 User Guide For Ovation 3.5

Uploaded by

Copyright:

Available Formats

Controller (OCR1100) User Guide for Ovation 3.

1 Introduction to the OCR1100 Controller 1

2 Ovation Controller hardware 7

3 Defining and addressing the I/O devices 17

4 Starting the Controller 27

4.2.2 To reboot a Controller drop .................................................................................. 31

5 Configuring the Controller 35

6 Configuring Controller drivers 63

7 Local Ovation I/O drivers configuration 65

8 Remote Ovation I/O drivers configuration 71

9 Local Q-Line drivers configuration 81

10 Remote Q-Line driver configuration 89

11 Allen-Bradley driver overview 97

11.2 Allen-Bradley DF-1 commands supported by Ovation .................................................... 103

12 Foundation Fieldbus second generation (I/O modules) driver

13 GE Genius driver configuration 117

14 GE Mark V/VI/Ve driver configuration 123

15 MHI driver configuration 133

16 Modbus driver configuration 139

16.2 I/O access path examples for Modbus ............................................................................ 144

17 Profibus device driver configuration 147

18 RTP I/O driver configuration 157

19 Toshiba driver configuration 163

20 External Ovation network driver configuration 169

21 Using the Controller Diagnostics tool 175

1 Introduction to the OCR1100 Controller

What is the OCR1100 Controller?....................................................................................... 2

1.1 What is the OCR1100 Controller?

Figure 1: Ovation Controller

1.2 Features of the OCR1100 Controller

The Ovation Controller has the following features:

1.3 Converting to the OCR1100 Controller

Transitioning to the OCR1100 Controller can be performed on any Ovation system.

1.4 What is automatic failover control?

CAUTION! To ensure failover capabilities in a pair of redundant Controllers, do the following:

You must configure the IOIC device driver.

2 Ovation Controller hardware

What are the Ovation Controller I/O interfaces? ................................................................. 7

2.1 What are the Ovation Controller I/O interfaces?

2.1.1 Network Interface ports

Network interface ports

OCR1100 Controllers are available in the following two groups:

2.1.2 I/O interface ports

The following list shows the configuration options:

2.1.3 What are Small Form-factor Pluggable transceivers (SFPs)?

Note: Use of non-approved SFPs is not permitted on the Ovation system.

2.2 Controller module components

The Ovation Controller is comprised of two main modules:

The OCR1100 processor has two Groups:

Figure 2: Processor module status LEDs

Processor module status LEDs

LED ME ANING ON OFF BLINKING

P Power Lights green when Unlit when module N/A

LED ME ANING ON OFF BLINKING

Ethernet port N/A N/A Module is receiving or

Figure 3: I/O Interface module status

I/O interface module LED descriptions

LABE L ME ANING ON (SOLID) OFF BLINKING

P Power Controller Controller not N/A

LABE L ME ANING ON (SOLID) OFF BLINKING

E Error Performing Application firmware An error is indicated. Read error

2.2.3 To open the Controller module front cover

1. Power-down the Controller before opening the module cover.