You are on page 1of 211

Controller (OCR400) User Guide for Ovation 3.3.

1
OW331_54

(Includes Controller Diagnostics)


July 2010
Copyright Notice

Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.

The text, illustrations, charts, and examples included in this manual are intended solely to explain
®
the use and application of the 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 and WEStation are registered trademarks of Emerson Process Management. All other
trademarks or registered trademarks 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@EmersonProcess.com
Website: https://www.ovationusers.com
Contents

1 Introduction to the OCR400 Ovation Controller 1


1.1 What is the Ovation OCR400 Controller? ........................................................................... 2
1.2 What are the OCR400 Controller features?........................................................................ 3
1.3 What is automatic failover control? ..................................................................................... 5
1.4 Converting from an OCR161 Controller to an OCR400 Controller ..................................... 5

2 Ovation Controller hardware 7


2.1 What are the OCR400 Controller I/O interfaces? ............................................................... 7
2.2 What is the process for planning the I/O for your system? ............................................... 10
2.3 What are the Ovation I/O module base types? ................................................................. 11
2.3.1 What is a standard I/O module base?............................................................. 11
2.3.2 What is a relay output module base?.............................................................. 11
2.4 OCR 400 Controller Modules ............................................................................................ 12
2.4.1 To replace OCR400 Controller modules ......................................................... 12
2.4.2 To open OCR400 Controller module covers ................................................... 12
2.4.3 To replace OCR400 Controller module covers ............................................... 12
2.5 Adding OCR400 Controllers to WDPF Q-Line I/O ............................................................ 13

3 Defining and addressing the I/O devices 15


3.1 What is an Ovation I/O module address? ......................................................................... 15
3.1.1 What is the addressing format for I/O modules?............................................. 15
3.1.2 Examples of Controller cabinet I/O module addresses ................................... 17
3.1.3 Examples of extended I/O cabinet module addresses.................................... 18
3.1.4 Examples of remote node I/O cabinet module addresses .............................. 19
3.1.5 Examples of Relay Output module addresses ................................................ 20
3.2 Q-Line I/O module addressing .......................................................................................... 21
3.3 What are the guidelines for positioning I/O modules in cabinets? .................................... 21
3.4 What types of I/O modules can an OCR400 Controller support? ..................................... 23
3.5 What changes can you make to an I/O device? ............................................................... 23
3.5.1 To modify an I/O device .................................................................................. 23
3.5.2 To modify an external Ovation networks device ............................................. 24

4 Starting the OCR400 Controller 25


4.1 Verifying Controller hardware and power status ............................................................... 25
4.1.1 To verify OCR400 Controller Hardware .......................................................... 25
4.1.2 To power up the Controller.............................................................................. 26
4.2 Monitoring OCR400 Controller Status .............................................................................. 26
4.2.1 What are the processor module status LEDs for the OCR400 Controller? .... 27
4.2.2 What are the I/O Interface module status LEDs for the OCR400 Controller? 29

OW331_54 i
Table of Contents

4.3 What procedures are needed after configuration changes to the Controller? .................. 31
4.3.1 To download Controller drop configuration ..................................................... 31
4.3.2 To reboot a Controller drop ............................................................................. 33
4.3.3 To load a Controller drop................................................................................. 33

5 Configuring the Controller 35


5.1 Configuring the Controller software .................................................................................. 35
5.2 What is the IP address of a Controller? ............................................................................ 35
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 using the one assigned to the Controller ....... 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............................................................................... 40
5.4.3 To set Controller parameters........................................................................... 42
5.4.4 To set existing control tasks ............................................................................ 44
5.4.5 To insert new control tasks.............................................................................. 46
5.4.6 To confirm Controller networking (network item) ............................................ 46
5.4.7 To modify Controller networking (drop item) ................................................... 48
5.5 Online Controller Restore Mode ....................................................................................... 50
5.6 What are the Restore mode functions? ............................................................................ 51
5.7 What are the Restore mode performance issues? ........................................................... 51
5.8 What are the Restore mode engineering limitations?....................................................... 52
5.9 What are the Restore mode point information issues?..................................................... 52
5.9.1 To configure the online Controller restore mode............................................. 52
5.10 What additional software configurations are needed for Controllers? .............................. 54
5.10.1 To configure alarm timestamping to the millisecond level .............................. 54
5.10.2 To map a 16-bit PLC register to a 16-bit packed point ................................... 55

6 Initial steps to configuring drivers 57


6.1 What is a Controller driver?............................................................................................... 57
6.2 Configuring device drivers in the Controller ...................................................................... 57
6.2.1 To configure Ovation and Q-Line devices....................................................... 57
6.2.2 To configure third-party devices ...................................................................... 58

ii OW331_54
Table of Contents

7 Configuring local Ovation I/O drivers 59


7.1 To insert new device numbers .......................................................................................... 59
7.2 To set Ovation device number parameters....................................................................... 59
7.3 To insert local Ovation I/O devices ................................................................................... 61
7.4 To insert a new local Ovation I/O branch.......................................................................... 63
7.5 To insert a local Ovation I/O module................................................................................. 64

8 Configuring remote Ovation I/O drivers 67


8.1 To insert new device numbers .......................................................................................... 67
8.2 To set Ovation device number parameters....................................................................... 67
8.3 To insert remote Ovation I/O devices ............................................................................... 69
8.4 To insert remote Ovation I/O new nodes .......................................................................... 71
8.5 To insert a remote Ovation I/O new branch ...................................................................... 72
8.6 To insert a remote Ovation I/O module............................................................................. 72

9 Configuring local Q-Line drivers 77


9.1 To insert new device numbers .......................................................................................... 77
9.2 To set Ovation device number parameters....................................................................... 77
9.3 To insert local Q-Line devices........................................................................................... 79
9.4 To insert a new local Q-line crate ..................................................................................... 81
9.5 To insert a new local Q-line module.................................................................................. 81

10 Configuring remote Q-Line drivers 85


10.1 To insert new device numbers .......................................................................................... 85
10.2 To set Ovation device number parameters....................................................................... 85
10.3 To insert remote Q-line devices ........................................................................................ 87
10.4 To insert new remote Q-line nodes................................................................................... 89
10.5 To insert a new remote Q-Line crate ................................................................................ 89
10.6 To insert a new remote Q-line module.............................................................................. 90

11 Configuring Allen-Bradley drivers 93


11.1 What is an Allen-Bradley driver?....................................................................................... 93
11.2 To insert new device numbers .......................................................................................... 93
11.3 To set Allen-Bradley device number parameters.............................................................. 94
11.4 To insert an Allen-Bradley device ..................................................................................... 96
11.5 To configure Allen-Bradley points ..................................................................................... 97
11.6 What are the Allen-Bradley DF-1 commands supported by Ovation? ............................ 100
11.7 What are I/O access path examples for Allen-Bradley? ................................................. 101
11.8 Allen-Bradley analog input cards .................................................................................... 102
11.9 Allen-Bradley digital input cards...................................................................................... 102

OW331_54 iii
Table of Contents

12 Configuring Foundation Fieldbus first generation (Gateway) drivers


103
12.1 What is a Foundation Fieldbus first generation (Gateway) device? ............................... 103
12.2 To insert new device numbers ........................................................................................ 103
12.3 To set Foundation Fieldbus (Gateway) device number parameters............................... 104
12.4 To insert a Foundation Fieldbus (Gateway) device ........................................................ 105
12.5 What are I/O access path examples for Foundation Fieldbus (Gateway)? .................... 113

13 Configuring Foundation Fieldbus second generation (I/O modules)


drivers 115
13.1 To insert new device numbers ........................................................................................ 115
13.2 To set Foundation Fieldbus (I/O module) parameters .................................................... 116
13.3 To insert a Foundation Fieldbus I/O module in the Developer Studio ............................ 117
13.4 To add a module record point name ............................................................................... 119
13.5 To add a Foundation Fieldbus (I/O module) device........................................................ 120
13.6 To assign a node record to each of your ports ............................................................... 123

14 Configuring GE Genius drivers 125


14.1 To insert new device numbers ........................................................................................ 125
14.2 To set GE Genius device number parameters................................................................ 125
14.3 To insert a GE Genius device ......................................................................................... 126
14.4 What are I/O access path examples for GE Genius? ..................................................... 129

15 Configuring GE Mark V/VI/Ve drivers 131


15.1 To insert new device numbers ........................................................................................ 131
15.2 To set GE Mark V/VI/Ve device number parameters...................................................... 131
15.3 To insert a GE Mark V/VI device..................................................................................... 133
15.4 To configure GE Mark V/VI/Ve points ............................................................................. 134
15.5 What are I/O access path examples for GE Mark V and VI?.......................................... 138

16 Configuring MHI drivers 141


16.1 To insert new device numbers ........................................................................................ 141
16.2 To set MHI device number parameters........................................................................... 141
16.3 To insert an MHI device .................................................................................................. 143
16.4 To configure MHI points .................................................................................................. 143
16.5 What are I/O access path examples for MHI? ................................................................ 145

17 Configuring Modbus drivers 147


17.1 To insert new device numbers ........................................................................................ 147
17.2 To set Modbus device number parameters .................................................................... 147

iv OW331_54
Table of Contents

17.3 To insert a Modbus device .............................................................................................. 149


17.4 To configure Modbus points............................................................................................ 150
17.5 What are I/O access path examples for Modbus? .......................................................... 153

18 Configuring Profibus device drivers 155


18.1 To use Developer Studio to add a new Ovation I/O device number to the Controller .... 155
18.2 To insert a Profibus I/O module in the Developer Studio................................................ 157
18.3 To add a module record point name ............................................................................... 158
18.4 To assign a node record to each of your ports ............................................................... 160

19 Configuring RTP I/O drivers 163


19.1 To insert new device numbers ........................................................................................ 163
19.2 To set RTP I/O device number parameters .................................................................... 163
19.3 To insert an RTP I/O device............................................................................................ 165
19.4 To configure RTP I/O points............................................................................................ 165
19.5 What are I/O access path examples for RTP I/O?.......................................................... 168

20 Configuring Toshiba drivers 169


20.1 To insert new device numbers ........................................................................................ 169
20.2 To set Toshiba device number parameters .................................................................... 169
20.3 To insert a Toshiba device .............................................................................................. 171
20.4 To configure Toshiba points............................................................................................ 171
20.5 What are I/O access path examples for Toshiba? .......................................................... 173

21 Configuring external Ovation network drivers 175


21.1 What are external Ovation network devices? ................................................................. 175
21.2 To insert new device numbers ........................................................................................ 175
21.3 To set external Ovation network device number parameters ......................................... 176
21.4 To insert external Ovation network I/O devices .............................................................. 177
21.5 To map external Ovation network points ........................................................................ 177
21.6 To reconfigure an external Ovation network driver......................................................... 179

22 Using the Controller Diagnostics tool 181


22.1 What is the Controller Diagnostics tool? ......................................................................... 181
22.2 What are the software platforms that Controller Diagnostics supports?......................... 182
22.3 What is the Controller Diagnostics window?................................................................... 183
22.3.1 To access the Controller Diagnostics tool in a Windows-based Ovation system
184
22.3.2 To access the Controller Diagnostics tool in a Solaris-based Ovation system
185
22.3.3 Controller Diagnostics menu bar ................................................................... 186
22.3.4 Controller Diagnostics toolbar ....................................................................... 186

OW331_54 v
Table of Contents

22.4 What is the Controller List in the Controller Diagnostics window?.................................. 187
22.4.1 To select a Controller in the Controller Diagnostics window......................... 187
22.5 What is the Controller Overview panel in the Controller Diagnostics window? .............. 188
22.6 What is the Controller Diagnostics Update Backup function? ........................................ 190
22.6.1 To update your backup Controller in the Controller Diagnostics window ..... 190
22.7 What is the Control Task Information tab in the Controller Diagnostics window? .......... 191
22.8 What is the I/O Information tab in the Controller Diagnostics window?.......................... 193
22.8.1 What firmware can be downloaded to the I/O modules through the Controller
Diagnostics window......................................................................................................... 195
22.8.2 To download firmware revisions to the I/O modules through the Controller
Diagnostics window......................................................................................................... 195
22.8.3 To reboot an I/O module ............................................................................... 197
22.9 What is the Software Versions tab in the Controller Diagnostics window? .................... 197
22.10 What is the Point Details tab in the Controller Diagnostics window?.............................. 198
22.11 What is the Sheet Information tab in the Controller Diagnostics window? ..................... 199
22.12 What is the Refresh function for the Controller Diagnostics window? ............................ 200

Index 201

vi OW331_54
S E C T I O N 1

Introduction to the OCR400 Ovation Controller

IN THIS SECTION

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


What are the OCR400 Controller features?........................................................................ 3
What is automatic failover control? ..................................................................................... 5
Converting from an OCR161 Controller to an OCR400 Controller ..................................... 5

OW331_54 1
1.1 What is the Ovation OCR400 Controller?

1.1 What is the Ovation OCR400 Controller?


The Controller in the plant is typically one or more cabinets containing input and output modules
connected to field devices by wires. These modules monitor each device for changes in the
device's condition. The Ovation Controller communicates with both 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.) 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.

This action has been programmed into the Controller by control sheets (also known as functional
drawings) that are created in the Ovation Control Builder. The Control Builder sheets consist of
building blocks (algorithms) arranged in a logical pattern that define in detail what action to take
when certain events occur in a device. These algorithms, linked by signals, represent a simple
two-step process or a complex process made up of many algorithms contained on many sheets.

The Ovation Controller is based on the Intel Pentium 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: OCR400 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.

2 OW331_54
1.2 What are the OCR400 Controller features?

1.2 What are the OCR400 Controller features?


The Ovation Controller has the following features:
„ Flash memory:
… Reduces maintenance
… Stores algorithms, logic, and operating system
… Eliminates PROMS
… Eliminates batteries
… Scalable size (128 Mb)
„ Single back plane in cabinet:
… No active components
… Fewer connections for higher reliability
… Reduced costs
„ Simplified algorithm set:
… Tracking option on algorithms
… Ladder and SAMA representation for digital logic
„ 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
¾ Foundation Fieldbus
¾ External Ovation Network
… Minimizes costs of upgrades
… 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 highway configuration utilizing the onboard NIC ports
… Redundant powering
… I/O bus failure isolation
… Watchdog functions
… Configurable auto-restart function

OW331_54 3
1.2 What are the OCR400 Controller features?

… Bumpless failover (secured by tracking algorithms)


„ Total point capacity of up to 32,000 points (depending upon your hardware and software
configuration):
… Total I/O points 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.
„ Performance:
… OCR400
¾ 400 Mhz Celeron processor
¾ Serial and parallel I/O scanning options
¾ 64 Mb DRAM memory
¾ Five control areas, each with selectable speeds (10ms - 30s)

4 OW331_54
1.3 What is automatic failover control?

1.3 What is automatic failover control?


The redundancy function of the Ovation Controller is equipped with automatic failover control. If
the processor 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
broadcast 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 the 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! In order to ensure failover in a pair of redundant Controllers, do the following:

For OCR161 Controllers, you must install and configure an IOIC card (PCRL, PCRR, or
PCQL) in each redundant Controller.

For OCR400 Controllers, you must configure the IOIC device in each redundant Controller.

For both Controllers, you can then add up to four additional devices to each Controller.

1.4 Converting from an OCR161 Controller to an OCR400 Controller


The transition from an OCR161 to an OCR400 does not require points to be rebuilt. There are a
few things that the system cannot convert and must be done as a final clean-up after changing
Controllers.

Note: The system can convert from an OCR400 to the OCR161 Controller if there is a need.
You will have similar clean-up issues.

Because there are differences in the way the two Controllers handle the I/O devices, you will have
to check and make any changes to the device drivers, especially third-party devices.

Also it is important to know that the system will not make any changes, additions or deletions to
the node records. The node records must be cleaned up (especially the status and diagnostics)
prior to placing the system back on line.

OW331_54 5
S E C T I O N 2

Ovation Controller hardware

IN THIS SECTION

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


What is the process for planning the I/O for your system? ............................................... 10
What are the Ovation I/O module base types? ................................................................. 11
OCR 400 Controller Modules ............................................................................................ 12
Adding OCR400 Controllers to WDPF Q-Line I/O ............................................................ 13

2.1 What are the OCR400 Controller I/O interfaces?


The Ovation Controller provides various types of interfaces to communicate with the system and
other devices. These interfaces include:
„ Ovation network.
„ Dedicated backup.
„ I/O devices.

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. Port N2 is typically used for single
attached networking to the Ovation network. Port N3 provides an additional Ethernet interface for
dual attached networking. N4 is the default Ethernet interface for dedicated control
synchronization. Port N1 is an additional Ethernet interface for other uses, such as third-party
links, if necessary.

PORT SUPPORTS

N1 Third-party devices.
N2 Single attached network interface.
N3 Dual attached network interface or third-party device.
N4 Dedicated control synchronization or third-party device.

OW331_54 7
2.1 What are the OCR400 Controller I/O interfaces?

Note: In the OCR400, 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, 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.

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

8 OW331_54
2.1 What are the OCR400 Controller I/O interfaces?

(See 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.)

The following figure shows the physical locations of the interface ports and their uses:

OW331_54 9
2.2 What is the process for planning the I/O for your system?

2.2 What is the process for planning the I/O for your system?
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
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.

10 OW331_54
2.3 What are the Ovation I/O module base types?

2.3 What are the Ovation 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.
The different bases can be mixed within a given I/O branch and cabinet. There are restrictions as
to how these bases can be mixed. (See Planning Your Ovation System.)

Figure 2: Standard I/O and relay output bases

2.3.1 What is a standard I/O module base?

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

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

2.3.2 What is a relay output module base?

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

OW331_54 11
2.4 OCR 400 Controller Modules

2.4 OCR 400 Controller Modules


The OCR 400 Controller contains two main modules:
„ Processer Module: This module communicates with the Ovation network and provides nine
indicator LED's that display information about the status of network communication.
„ IOIC Module: This module communicates with I/O devices and provides ten indicator LED's
that display information about the status of I/O communication.

Note: Fan assemblies are not required for OCR 400 Controllers.

2.4.1 To replace OCR400 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. Unlatch the blue corner latches on the module case.
3. Remove the old module from the Controller backplane.
4. Install the new module in the Controller backplane.
5. Use the blue corner latches on the module to secure it to the Controller backplane.

2.4.2 To open OCR400 Controller module covers

WARNING: The Ovation Controller modules have front panel covers that protect the Controller
internals. The Controller module covers should remain in place to protect the internal
electronics from accidental damage. Only qualified technicians should open these modules.

Occasionally, you might need to open a Controller Processor module cover to replace the flash
disk.

1. 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).
2. 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.

3. Pivot the cover back and remove it from the Processor module case.
4. Perform the desired operation and replace the Processor module cover.

2.4.3 To replace OCR400 Controller module covers

Note: Since the IOIC module overlaps the Processor module, you need to re-install the
Processor module cover first.

1. Position the bottom latches of the Processor module cover into the module case.

12 OW331_54
2.5 Adding OCR400 Controllers to WDPF Q-Line I/O

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

3. Push the top of the cover in toward the module body until the latches snap into their locking
position.
4. Repeat these steps for the IOIC module cover, if necessary.

2.5 Adding OCR400 Controllers to WDPF Q-Line I/O


When OCR400 Controllers are added to a WDPF control system using Q-Line I/O, two QOL
cards, one connected to each Controller are necessary to provide the connections previously
done by the QBE or the QOR card. QOLs typically occupy the QBE slot or the 13th slot in the
upper and lower Q-crates in a WDPF A or extended A cabinet.

QOL cards are typically used when OCR400 Controllers are installed and utilize Q-line I/O. Refer
to drawing number 5X00252 for additional information.

The OCR400 treats local Q-line differently than the OCR161. The OCR400 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 OCR400 Controller as they were on the OCR161
Controller. Instead, QOL cards replace the first and last QBE cards in the Q-Crates.

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.

Remember that the QOL is really making local Q-Line into remote Q-Line but only providing 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 OCR400 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.

OW331_54 13
S E C T I O N 3

Defining and addressing the I/O devices

IN THIS SECTION

What is an Ovation I/O module address? ......................................................................... 15


Q-Line I/O module addressing .......................................................................................... 21
What are the guidelines for positioning I/O modules in cabinets? .................................... 21
What types of I/O modules can an OCR400 Controller support? ..................................... 23
What changes can you make to an I/O device? ............................................................... 23

3.1 What is an Ovation I/O module address?


The 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 OCR400 IOIC or the OCR161 PCI card (1-5).
N = Node (only used in Remote I/O; 1 through 8).
B = Branch (1 through 8).
S = Slot where module is located (1 through 8 for Ovation I/O)
(1 through 12 for Q-Line I/O).

OW331_54 15
3.1 What is an Ovation I/O module address?

„ Standard I/O base assemblies


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

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

Emerson Process Management recommends that all bases (typically four) be installed in the right
side of a cabinet, even if 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).

16 OW331_54
3.1 What is an Ovation I/O module address?

3.1.2 Examples of Controller cabinet I/O module addresses

Figure 3: I/O Address examples, modules A, B, C (Controller cabinet)

Note: PCI Cards 1 and 2 for the OCR161, IOIC module for the OCR400.

„ Module A address = 1.1.2.


„ Module B address = 1.2.4.
„ Module C address = 1.3.6.

OW331_54 17
3.1 What is an Ovation I/O module address?

3.1.3 Examples of extended I/O cabinet module addresses

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

Note: PCI Cards 1 and 2 for the OCR161, IOIC module for the OCR400.

„ Module D address = 1.5.6.


„ Module E address = 1.6.1.
„ Module F address = 1.8.8.

18 OW331_54
3.1 What is an Ovation I/O module address?

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 15) section in the Ovation I/O Reference Manual for details
about addresses for remote nodes.

Note: Assume the PCRR card is in position 1 for the OCR161

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.

OW331_54 19
3.1 What is an Ovation I/O module address?

3.1.5 Examples of Relay Output module addresses

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

Note: PCI Cards 1 and 2 for the OCR161, IOIC module for the OCR400. For OCR161
applications assume the PCRL card is in position 1, and the cable is connected from Branch 4
of PCI Card 1 card.

„ Module I address = 1.5.3.


„ Module J address = 1.6.2.
„ Module K address = 1.7.6.

Note: The back of 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 OW331_54
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 used 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 4: 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.

OW331_54 21
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 5: Examples of cabinets with standard I/O and relay modules

22 OW331_54
3.4 What types of I/O modules can an OCR400 Controller support?

3.4 What types of I/O modules can an OCR400 Controller support?


The Ovation OCR400 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 OCR400 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 23)
„ External network devices (see page 24)

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

OW331_54 23
3.5 What changes can you make to an I/O device?

3. Right-click the appropriate item.


4. Select Open.
5. Make necessary changes in the dialog box and select Ok or Apply.

3.5.2 To modify an external Ovation networks device

For external networks modification information, see Ovation Multiple Networks User Guide.

24 OW331_54
S E C T I O N 4

Starting the OCR400 Controller

IN THIS SECTION

Verifying Controller hardware and power status ............................................................... 25


Monitoring OCR400 Controller Status .............................................................................. 26
What procedures are needed after configuration changes to the Controller? .................. 31

4.1 Verifying Controller hardware 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 26).

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

OW331_54 25
4.2 Monitoring OCR400 Controller Status

2. Confirm that the power cable is attached to the power plug connector.

Figure 6: 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 blue 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.

4.2 Monitoring OCR400 Controller Status


You can monitor the OCR400 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 (see page 27) to communicate with the Ovation network
and an I/O interface module (see page 29) to communicate with the I/O devices.

26 OW331_54
4.2 Monitoring OCR400 Controller Status

4.2.1 What are the processor module status LEDs for the OCR400 Controller?

The Controller processor module 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. It 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.

Figure 7: Processor module status LEDs

Processor module status LEDs

LED ME ANING ON OFF BLINKING

P Power Lights green when Unlit when N/A


module is powered module is not
powered
N1 Ethernet port Port is receiving Port is not Module is linked to
power receiving power network through the
green LED port
(Link Integrity/
Power LED)
Ethernet port N/A N/A Module is receiving or
transmitting data on
amber LED the port
(Link activity status)

OW331_54 27
4.2 Monitoring OCR400 Controller Status

LED ME ANING ON OFF BLINKING

Ethernet port Port is receiving Port is not Module is linked to


power receiving power network through the
N2 green LED port
(Link Integrity/
Power LED)
Ethernet port N/A N/A Module is receiving or
transmitting data on
amber LED the port
(Link activity status)
N3 Ethernet port Port is receiving Port is not Module is linked to
power receiving power network through the
green LED port
(Link Integrity/
Power LED)
Ethernet port N/A N/A Module is receiving or
transmitting data on
amber LED the port
(Link activity status)
N4 Ethernet port Port is receiving Port is not Module is linked to
power receiving power network through the
green LED port
(Link Integrity/
Power LED)
Ethernet port N/A N/A Module is receiving or
transmitting data on
amber LED the port
(Link activity status)

28 OW331_54
4.2 Monitoring OCR400 Controller Status

4.2.2 What are the I/O Interface module status LEDs for the OCR400 Controller?

The Controller I/O interface module provides ten indicator LEDs that display status information
about the interface between the Controller and the I/O devices.

The indicators can be lit solid, blinking, or off. All of the I/O status indicators, with the exception of
the Error indicator, are green. The Error indicator is red.

Figure 8: I/O Interface module status

I/O interface module LED descriptions

STATUS

L ABEL 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)

OW331_54 29
4.2 Monitoring OCR400 Controller Status

STATUS

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)
"E" LED off) "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)
"E" LED off) "E" LED off)
R4 Port R4 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)
"E" LED off) "E" LED off)
Q5 Port Q5 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)
"E" LED off) "E" LED off)

A Controller fault is indicated when the red E LED is blinking. In this state, the Node LEDs (O1,
O2, 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.

You can diagnose most Fault Codes that appear by accessing the Ovation Fault Information Tool.
To access the tool, log on to the Ovation/WDPF Users site, and click the Fault Information Tool in
the left hand menu. Or, you can also enter the following URL to log on to the Fault Information
Tool directly:

https://www.ovationusers.com/FIT/index.asp

For help using the Ovation Fault Information Tool, click the Help button in the tool.

30 OW331_54
4.3 What procedures are needed after configuration changes to the Controller?

4.3 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. These procedures are done through the Developer Studio.
„ Download changes to the Controller (see page 31)
„ Reboot the Controller (see page 33)
„ Load the Controller (see page 33)

Note: In the OCR400, 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, 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.3.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 on 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 (See 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.

OW331_54 31
4.3 What procedures are needed after configuration changes to the Controller?

7. Select which files should be included in the Download process.

Figure 9: 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.

32 OW331_54
4.3 What procedures are needed after configuration changes to the Controller?

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

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to the Drops item:
Systems
Networks
Units
Drops
3. Right-click on 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 10: Reboot confirmation dialog box

7. Click Yes to close the window and execute the reboot process.

4.3.3 To load a Controller drop

The Load function is necessary anytime changes have been made relating to points or control.
Since a new drop point was inserted in Configuring Controller Software (see page 35), the Load
command should be executed immediately following the completion of the Reboot command.

Note: The Load function is also required when Controller device drivers (Configuring Ovation
Drivers (see page 57)), 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. (See Ovation Developer Studio User Guide.)

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to the Drops item:
Systems
Networks
Units
Drops
3. Right-click on 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.

OW331_54 33
4.3 What procedures are needed after configuration changes to the Controller?

6. Select the same Controller drop that was rebooted. The load process executes.
7. Repeat the Download, Reboot and Load procedures for the partner drop in redundant
Controller drop configurations.

34 OW331_54
S E C T I O N 5

Configuring the Controller

IN THIS SECTION

Configuring the Controller software................................................................................... 35


What is the IP address of a Controller? ............................................................................ 35
Determining the NIC (network ethers) address of a drop ................................................. 36
What should a new Controller drop item contain? ............................................................ 37
Online Controller Restore Mode........................................................................................ 50
What are the Restore mode functions? ............................................................................ 51
What are the Restore mode performance issues? ........................................................... 51
What are the Restore mode engineering limitations? ....................................................... 52
What are the Restore mode point information issues? ..................................................... 52
What additional software configurations are needed for Controllers? .............................. 54

5.1 Configuring the Controller software


Use the following steps to set up a new Controller or pair of Controllers:
„ To determine the IP address of a machine/drop (see page 36).
„ Determining the NIC (network ethers) address (see page 37).
„ To insert a new Controller drop (see page 37).
„ To insert a new drop point (see page 40).
„ To set Controller parameters (see page 42).
„ To set existing control tasks (see page 44).
„ To insert new control tasks (see page 46).
„ To confirm Controller networking (network item) (see page 46).
„ Configure Online Controller Restore Mode (see page 50), when using the Online Controller
Restore Mode function.

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.

OW331_54 35
5.3 Determining the NIC (network ethers) address of a drop

5.2.1 To determine the IP address of a machine/drop


1. Left-click the Start button on the lower left of the monitor.
2. Open up the Programs icon.
3. Find and double-click the Command Prompt icon.
4. Type ipconfig in the dialog box.
5. Press the Return or Enter key.
6. Copy the IP address needed for the configuration.

5.3 Determining the NIC (network 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 can support a dual attached highway configuration utilizing the onboard
NIC ports. The Controller now supports a dual attached highway configuration utilizing the
onboard NIC ports.

5.3.1 To determine the NIC hardware address from the card label
1. Some earlier NIC cards have a label containing the hardware address. Obtain the address
from the NIC card in the Controller.
2. Determine and record the NIC hardware address. The hardware address has the following
format:

xx:xx:xx:xx:xx:xx
(where the last four numbers (xx:xx) are located on a label on the NIC).
3. Record the address; this address is needed for the Controller configuration.

5.3.2 To determine the NIC address using the one assigned to the Controller
1. Confirm that the blue 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 blue power switch to the ON position (1) for the Controller whose NIC card address
is needed. The LED on the Controller Power Supply module lights steadily. If more than one
Controller is turned on, the addresses display in the order that the Controllers are turned on.
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 the Controller
configuration.

36 OW331_54
5.4 What should a new Controller drop item contain?

5.4 What should a new Controller drop item contain?


A new <DROP#> item appears under the Drops item of the 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 11: 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.

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to the Drops item:
Systems
Networks
Units
Drops
3. Right-click on 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 This is the new Controller drop number. Valid entries are 1-254.

Partner Id This field identifies the drop ID of the partner drop.


Drop Type Allows the choice of drops: Controller, SimController, Advanced Controller,
Advanced SimController, or Virtual Controller.

OW331_54 37
5.4 What should a new Controller drop item contain?

6. After the required information is provided, press the Finish button. The New Drops dialog
appears showing the Config tab.

Figure 12: New drops dialog box

New Drops dialog box descriptions

FIELD DESCRIPTION

Drop Type This procedure deals specifically with the Controller selection from the pull-down
menu.
Choices are: Controller, SimController, Advanced Controller, Advanced
SimController, Virtual Controller.
Controller Type Choose the correct Controller type. - (OCR400, OCR161)

38 OW331_54
5.4 What should a new Controller drop item contain?

FIELD DESCRIPTION

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 highway by making one of the following selections:
ƒ Ovation Highway
ƒ Dedicated Cable
By default, the Dedicated Cable option is enabled. When possible, the Dedicated
Cable option is recommended to alleviate network traffic on the Ovation Highway.
Maximum Point This radio button selects the maximum number of points that the Controller can be
Limit configured to monitor.
Normal handles up to 6000 points.
Expanded handles up to 16,000 points.
32000 handles up to 32,000 points. Note: additional shared memory may be
required to accommodate additional points.
Primary & Partner When the primary/partner configuration is not used, no information input is
Section required in the partner section.

Drop ID Drop number of the originating drop of the point.


(1-254)
Ovation Network IP The IP address consists of four groups of decimal numbers and the format is:
Address
xxx.xxx.xxx.xxx
The System Administrator typically assigns these addresses. They can also be
assigned to be any valid range if the network is isolated from other networks (such
as, the Internet).
Ovation Network 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 Highway.
Interface
(Automatically selected for the OCR400.)
(ZNYX, Onboard)
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)
NIC Interface Automatically selected by the system. Name of physical port that the Ethernet
cable is connected.
(OCR400) - (OCR161)
(N2) - (fei0) - used for Single Ethernet
(N3) - (fei1) - used for Dual or third-party Ethernet interfaces
(N1) - (fei2) - used for third-party Ethernet interface
(N4) - (fei3) - used for Dedicated control synchronization cable or third-party
Ethernet interfaces)

OW331_54 39
5.4 What should a new Controller drop item contain?

FIELD DESCRIPTION

Backup NIC Automatically selected by the system.


Interface
(OCR400) - (OCR161)
(Available if a
backup NIC is (N1 - N4) - (fei0 - fei4)
used.)
Control The Controller software is configured to automatically run control synchronization
Synchronization of redundant controllers over the network.
Interface
(OCR400) - (OCR161)
(N1 - N4) - (fei0 - fei4)

Note: In the OCR400 Controller:

The OCR400 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.

Restore
Restore Mode Read only field for catastrophic failure.
(Appears if Online (Enable, Disable)
Controller Restore
Mode (see page
50) is selected.)

1. 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.
2. A new <DROP#> item appears under the Drops item of the Developer Studio system tree
refer to New Controller drop item in system tree (see page 37).

5.4.2 To insert a new drop point


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Drop Point item:
Systems
Networks
Units
Drops
Points
Drop Point

40 OW331_54
5.4 What should a new Controller drop item contain?

3. Right-click on 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 (see page 37)).
b) Select the appropriate drop number to correspond with the Point Name entry.
6. After the required information is provided, click Finish. The New Drop Point dialog box
appears containing default values for the attributes.

Figure 13: 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, eDB, Alarm, and Display tabs.

New Drop Point dialog box descriptions

T AB 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.

OW331_54 41
5.4 What should a new Controller drop item contain?

T AB FIELD DESCRIPTION

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.

eDB Collection Enabled Check box that specifies if a point is collected by the eDB.
Scan Frequency Frequency (in seconds) at which a specific point is scanned by the
eDB on the network to determine if it meets collection criteria.
Alarm Alarm Priority Sets the various alarm priority fields (1-8).

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
button to save the settings and close the window.
9. Repeat this procedure for the partner drop in a redundant Controller drop configurations.

5.4.3 To set Controller parameters


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Controller item:
Systems
Networks
Units
Drops
Configuration
Controller
3. Right-click on Controller.
4. Select Open from the resulting pop-up menu. The Controller dialog box appears showing the
Controller tab.

42 OW331_54
5.4 What should a new Controller drop item contain?

5. Complete any desired changes to the default field values.

Figure 14: Controller dialog box — Controller Parameters tab

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

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 messages is sent.
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 Ovation Developer Studio User Guide.)
Drop specific value

OW331_54 43
5.4 What should a new Controller drop item contain?

FIELD DESCRIPTION

TimeKeeper Selects the device that synchronizes time for the Controller:
(Default, 1, 2, 3, 4, 5)
If Default is selected:
OCR400 - The software uses the IOIC.
OCR161 - The software selects one of the IOIC cards (PCQL, PCRL, or PCRR).
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. It is recommended 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.
(OCR400 Only) (Remote R-Line, Remote Q-Line, Local Q-Line)
Default = Remote R-Line
6. 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.

5.4.4 To set existing control tasks


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Control Tasks item:
Systems
Networks
Units
Drops
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.

44 OW331_54
5.4 What should a new Controller drop item contain?

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 15: 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.


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

OW331_54 45
5.4 What should a new Controller drop item contain?

9. Repeat this procedure for each Control Task object before proceeding.

5.4.5 To insert new control tasks


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Control Tasks item:
Systems
Networks
Units
Drops
Configuration
Controller
Control
Control Tasks
3. Right-click on the 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 again.
7. Repeat this procedure for each newly created Control Task before proceeding.

5.4.6 To confirm Controller networking (network item)


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Controller Networking (Network item):
Systems
Networks
Configuration
Controller Networking
3. Select the Controller Networking.
4. Observe the Controller Networking object listed in the WorkPad window.
5. Right-click the Controller Networking object.

46 OW331_54
5.4 What should a new Controller drop item contain?

6. Select Open from the resulting pop-up menu. The Controller Networking dialog box appears
showing the Networking Configuration tab.

Figure 16: Controller networking dialog box

OW331_54 47
5.4 What should a new Controller drop item contain?

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.

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 54).
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 48).

5.4.7 To modify Controller networking (drop item)


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Controller Networking (Drop item):
Systems
Networks
Units
Drops
Configuration
Controller Networking
3. Right-click on the desired Controller Networking icon in the WorkPad Window.

48 OW331_54
5.4 What should a new Controller drop item contain?

4. Select Open from the pop-up menu. The New Controller Networking dialog box appears.

Figure 17: New Controller networking dialog box

5. Complete any desired changes to the default field values (see To Confirm Controller
Networking (Network Folder) (see page 46)).

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.

OW331_54 49
5.5 Online Controller Restore Mode

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

5.5 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 this mode is to provide a mechanism to restore a redundant
drop to its former fully matched condition after undesirable and/or catastrophic control behavior is
observed following the load of new application data to one half of a pair of redundant Ovation
drops/Controllers. The Restore Mode provides the ability to back-out the engineering changes
made to the drop so it can be reloaded with the same application data that its partner contains.

You must decide 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! The Restore Mode is intended to recover from a failed load that may result in a
partner mismatch between redundant Controllers. It is NOT intended to “undo” programming
mistakes. Restore should NOT be used casually since the process is time-consuming and
requires operator action (including a drop reload) to ensure a complete drop restore.

The following items are included in Restore Mode images:


„ Database tables associated with the drop (including point and control information, hardware
configuration and holding registers.)
„ 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 eDB historian, the PIC file must be imported into the eDB.)

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

50 OW331_54
5.6 What are the Restore mode functions?

5.6 What are the Restore mode functions?


There are three basic modes of operation:

Restore mode disabled (Default)

This mode of operation is equivalent to the traditional operation of Ovation. Specifically, no


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

Restore mode enabled (all drops)

In this mode of operation, restore 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).

Restore mode enabled (redundant drops only)

In this mode of operation restore images are created automatically by the system immediately
following the full (and successful) load of redundant Ovation drops. Restore 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.

5.7 What are the Restore mode performance issues?


When the Ovation System is configured for operation in Restore mode, there are performance
and disk space issues that should be considered.

Typically, the overall load operation is slower.

Note: The additional time required to capture the restore 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 Restore 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).

OW331_54 51
5.8 What are the Restore mode engineering limitations?

5.8 What are the Restore mode engineering limitations?


Certain engineering operations are limited if the applicable drop is in 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 restore image. For example, if Drop1 is originating the point
D100, Drop2 cannot reference D100 in any of its control unless D100 exists in Drop1's
restore 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 restore image. For example, a drop may
receive a point not currently in a restore 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 are 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 restore image.
For example, assume Drop1 is fully loaded (and a valid Restore 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 checks 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 Limitation 3).

5.9 What are the Restore mode point information issues?


An additional feature of the restore operation concerns the handling of the 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.

In other words, 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.9.1 To configure the online Controller restore mode


1. Launch the Developer Studio.

52 OW331_54
5.9 What are the Restore mode point information issues?

2. Use the system tree (in the Hardware view bar) to navigate to and open the Systems folder.
Systems
3. Right-click the System 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.)
5. Find Restore Mode in the Attributes column and choose the appropriate function from the
pull-down menu.

Figure 18: Online Restore mode

OW331_54 53
5.10 What additional software configurations are needed for Controllers?

5.10 What additional software configurations are needed for


Controllers?
The following list contains additional item locations and settings that you should 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 Ovation Developer Studio User Guide.)
„ The DDB Configuration item settings. (See Ovation Developer Studio User Guide.)
„ The Point Processing item settings. (See Ovation Developer Studio User Guide.)
„ The Event Log Configuration item settings. (See applicable Ovation Historian User Guide.)
Proceed to the configuring drivers sections of this manual for steps on configuring the Controller
Drivers.

5.10.1 To configure alarm timestamping to the millisecond level

The OCR400 Controller can timestamp alarming to the 1 millisecond level when the Controller is
enabled for that function.

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to the Point Processing (Drop item):
Systems
Networks
Units
Drops
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.

54 OW331_54
5.10 What additional software configurations are needed for Controllers?

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.10.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 checkbox on the Hardware view tab. If you
do not check this box, you must configure each bit separately.

OW331_54 55
5.10 What additional software configurations are needed for Controllers?

3. After you have made the changes, download (see page 31), reboot (see page 33), and load
(see page 33) the Controller.

Figure 19: 16-Bit packed points

56 OW331_54
S E C T I O N 6

Initial steps to configuring drivers

IN THIS SECTION

What is a Controller driver?............................................................................................... 57


Configuring device drivers in the Controller ...................................................................... 57

6.1 What is a Controller driver?


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), then configure the I/O drivers.

The steps to configure device drivers for the OCR400 are slightly different than that of the
OCR161 controller.

Only one device number needs to be set up (number 1) for any Ovation or Q-Line device with the
OCR400, whereas the OCR161 must have a device number for each PCI card.

When an I/O Driver is set for Ovation/Q-Line devices, the OCR400 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:


„ 1-4 (OCR161)
„ 5-9 (OCR400)

6.2.1 To configure Ovation and Q-Line devices

The following is an overview of the steps used to create a local Ovation device or Q-Line device:

1. Insert a new device number.


2. Set the device number parameters.
3. Configure the device.
4. Insert a new branch and/or crate.

OW331_54 57
6.2 Configuring device drivers in the Controller

5. Insert the I/O module.


6. Download, reboot, and load.

Note: The OCR400 only needs one device number to be configured for any Ovation or Q-Line
device. The OCR400 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 a third-party device:

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.

58 OW331_54
S E C T I O N 7

Configuring local Ovation I/O drivers

IN THIS SECTION

To insert new device numbers .......................................................................................... 59


To set Ovation device number parameters....................................................................... 59
To insert local Ovation I/O devices ................................................................................... 61
To insert a new local Ovation I/O branch.......................................................................... 63
To insert a local Ovation I/O module................................................................................. 64

7.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.2 To set Ovation device number parameters


1. Select Ovation in the I/O Driver Type field in the New Device Numbers dialog box.
2. Make the appropriate choices for the other fields in the New Device Numbers dialog box.

OW331_54 59
7.2 To set Ovation device number parameters

3. Select the Ok or Apply button.

Figure 20: 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.

I/O Driver Type = None


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.

I/O Driver Type = Ovation (or applicable third-party devices)


Simulator Driver = Ovation where all points are either real or simulated and go
through one of the drivers. The simulated points do change values.

Simulator Driver Type Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
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).

60 OW331_54
7.3 To insert local Ovation I/O devices

FIELD DESCRIPTION

Slot Order Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
(This field is
automatically filled in Default = One
for the OCR400.)
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 amount of points available.

7.3 To insert local Ovation I/O devices


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. 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:
OCR400 - Use the default settings.
OCR161 - Select the same I/O Device Number that you selected when you first configured
the device number.
I/O Device Type value:
OCR400 - Use the default settings.
OCR161 - Select Local Ovation from the I/O Device Type pull-down menu.
5. 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.

OW331_54 61
7.3 To insert local Ovation I/O devices

62 OW331_54
7.4 To insert a new local Ovation I/O branch

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 on OCR400 applications.
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).
6. 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.
7. 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.

7.4 To insert a new local Ovation I/O branch


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Branch item:
Systems
Networks
Units
Drops
I/O Devices
I/O Device # Local Ovation
Branch

OW331_54 63
7.5 To insert a local Ovation I/O module

The Branch item is established by default because Local Ovation was selected in the Insert
New I/O Device Wizard.
3. Right-click on 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 21: New Branch dialog box

7. Ensure that the Branch number is correct and select the Ok or Apply button. A Branch item
with Slot subitems numbered 1-8 is added to the system tree.

7.5 To insert a local Ovation I/O module


1. Access the Ovation Developer Studio.
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 on the Ovation Module subfolder (in the Slot folder that you want to configure).
5. Select Insert New. The Insert New Ovation Module Wizard appears.

64 OW331_54
7.5 To insert a local Ovation I/O module

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.

Figure 22: New Ovation Module dialog box - Config tab

9. Enter a module point name in the Module Record Point Name field. The module point must
be created before it can be used in an I/O slot. (See Ovation Developer Studio User Guide.)
10. Select the Module Type tab on the New Ovation Module dialog box and make appropriate
entries according to the module type. (See Ovation Developer Studio User Guide.)
11. 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 an I/O point, go to the
appropriate point type folder in the Points folder, select the Hardware tab, and configure the
point channel. (See Ovation Developer Studio User Guide.)

12. Select Apply or Ok to enter the changes into the database.


13. Refer to the Download, Reboot, and Load (see page 31) sections for information on
downloading, rebooting, and loading

OW331_54 65
S E C T I O N 8

Configuring remote Ovation I/O drivers

IN THIS SECTION

To insert new device numbers .......................................................................................... 67


To set Ovation device number parameters....................................................................... 67
To insert remote Ovation I/O devices ............................................................................... 69
To insert remote Ovation I/O new nodes .......................................................................... 71
To insert a remote Ovation I/O new branch ...................................................................... 72
To insert a remote Ovation I/O module............................................................................. 72

8.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

8.2 To set Ovation device number parameters


1. Select Ovation in the I/O Driver Type field in the New Device Numbers dialog box.

OW331_54 67
8.2 To set Ovation device number parameters

2. Make the appropriate choices for the other fields in the New Device Numbers dialog box.
3. Select the Ok or Apply button.

Figure 23: 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.

I/O Driver Type = None


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.

I/O Driver Type = Ovation (or applicable third-party devices)


Simulator Driver = Ovation where all points are either real or simulated and go
through one of the drivers. The simulated points do change values.

Simulator Driver Type Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
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).

68 OW331_54
8.3 To insert remote Ovation I/O devices

FIELD DESCRIPTION

Slot Order Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
(This field is
automatically filled in Default = One
for the OCR400.)
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 amount of points available.

8.3 To insert remote Ovation I/O devices


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. 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:
OCR400 - leave the I/O Device Number at 0.
OCR161 - Select the same I/O Device Number that you selected when you first configured
the device number.
I/O Device Type value:
OCR400 - Select IOIC
OCR161 - Remote Ovation from the I/O Device Type pull-down menu.

OW331_54 69
8.3 To insert remote Ovation I/O devices

5. Select the Finish button. The New I/O Devices dialog box appears. The dialog box contains
the I/O device number and the device type.

Figure 24: 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 1 is reserved for IOIC on OCR400 applications.
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).
6. 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.
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
contains the device number and type.

70 OW331_54
8.4 To insert remote Ovation I/O new nodes

8.4 To insert remote Ovation I/O new nodes


1. Access the Ovation Developer Studio.
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 on 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 25: 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
subitems appear in the System Tree under the I/O Device Remote Ovation item.

OW331_54 71
8.5 To insert a remote Ovation I/O new branch

8.5 To insert a remote Ovation I/O new branch


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Branch item:
Systems
Networks
Units
Drops
I/O Devices
I/O Device # Remote Ovation
Branch
(The Branch item is established by default because Remote Ovation was selected in the
Insert New I/O Device Wizard.)
3. Right-click on 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 26: New Branch dialog box

7. Ensure that the branch number is correct.


8. Select the Ok or Apply button. A Branch item with Slot subitems numbered 1-8 is added to
the system tree.

8.6 To insert a remote Ovation I/O module


1. Access the Ovation Developer Studio.

72 OW331_54
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 subitem.
4. Right-click on the Ovation Module subitem (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 27: New Ovation Module dialog box - Config tab

9. Enter a module point name in the Module Record Point Name field. The module point must be
created before it can be used in an I/O slot. (See Ovation Developer Studio User Guide.)

OW331_54 73
8.6 To insert a remote Ovation I/O module

10. Select the Module tab on the New Ovation Module dialog box and make the appropriate
entries according to the Module type. (See Ovation Developer Studio User Guide.)

Figure 28: New Ovation Module - Module tab

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

74 OW331_54
8.6 To insert a remote Ovation I/O module

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 Ovation Developer Studio User Guide.)

Figure 29: New Ovation Module dialog box - Digital Channels tab

12. Select Apply or Ok to enter the changes into the database.


13. Refer to the Download, Reboot, and Load (see page 31) sections for information on
downloading, rebooting, and loading

OW331_54 75
S E C T I O N 9

Configuring local Q-Line drivers

IN THIS SECTION

To insert new device numbers .......................................................................................... 77


To set Ovation device number parameters....................................................................... 77
To insert local Q-Line devices........................................................................................... 79
To insert a new local Q-line crate...................................................................................... 81
To insert a new local Q-line module.................................................................................. 81

9.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

9.2 To set Ovation device number parameters


1. Select Ovation in the I/O Driver Type field in the New Device Numbers dialog box.
2. Make the appropriate choices for the other fields in the New Device Numbers dialog box.

OW331_54 77
9.2 To set Ovation device number parameters

3. Select the Ok or Apply button.

Figure 30: 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.

I/O Driver Type = None


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.

I/O Driver Type = Ovation (or applicable third-party devices)


Simulator Driver = Ovation where all points are either real or simulated and go
through one of the drivers. The simulated points do change values.

Simulator Driver Type Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
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).

78 OW331_54
9.3 To insert local Q-Line devices

FIELD DESCRIPTION

Slot Order Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
(This field is
automatically filled in Default = One
for the OCR400.)
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 amount of points available.

9.3 To insert local Q-Line devices


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears. Make the following choices.
I/O Device Number value:
OCR400 - Use the default settings.
OCR161 - Select the same I/O Device Number that you selected when you first configured
the device number.
I/O Device Type value:
OCR400 - Use the default settings.
OCR161 - Select Local Q-Line from the I/O Device Type pull-down menu.

OW331_54 79
9.3 To insert local Q-Line devices

5. 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 31: 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 OCR400 - Selected by controller software.


OCR161 - As selected in the Wizard.
I/O Device Type Selects the I/O Driver for the device.
OCR400 - Software controlling the Ovation devices.
OCR 161 - As selected in the Wizard.
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).
6. 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.
7. 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.

80 OW331_54
9.4 To insert a new local Q-line crate

9.4 To insert a new local Q-line crate


1. Access the Ovation Developer Studio.
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 on 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 32: 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 subitems is added to the system tree.

9.5 To insert a new local Q-line module


1. Access the Ovation Developer Studio.

OW331_54 81
9.5 To insert a new local Q-line module

2. Use the system tree to navigate to the Slot item:


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 subitem.
4. Right-click on the Q-Line Module subitem (in the Slot item you want to configure).
5. Select Insert New. The Insert New Local 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.
9. Select the Config tab.

Figure 33: 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 with the Analog Channels tab selected.

82 OW331_54
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
Ovation Developer Studio User Guide.)

Figure 34: 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 31) sections for information on downloading, rebooting, and loading.

OW331_54 83
S E C T I O N 10

Configuring remote Q-Line drivers

IN THIS SECTION

To insert new device numbers .......................................................................................... 85


To set Ovation device number parameters....................................................................... 85
To insert remote Q-line devices ........................................................................................ 87
To insert new remote Q-line nodes ................................................................................... 89
To insert a new remote Q-Line crate................................................................................. 89
To insert a new remote Q-line module.............................................................................. 90

10.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

10.2 To set Ovation device number parameters


1. Select Ovation in the I/O Driver Type field in the New Device Numbers dialog box.

OW331_54 85
10.2 To set Ovation device number parameters

2. Make the appropriate choices for the other fields in the New Device Numbers dialog box.
3. Select the Ok or Apply button.

Figure 35: 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.

I/O Driver Type = None


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.

I/O Driver Type = Ovation (or applicable third-party devices)


Simulator Driver = Ovation where all points are either real or simulated and go
through one of the drivers. The simulated points do change values.

Simulator Driver Type Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
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).

86 OW331_54
10.3 To insert remote Q-line devices

FIELD DESCRIPTION

Slot Order Selects the card slot (one or two) in the Controller chassis associated with the
selected device (None, One, Two).
(This field is
automatically filled in Default = One
for the OCR400.)
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 amount of points available.

10.3 To insert remote Q-line devices


1. Use the system tree to navigate to the I/O Devices item.
Systems
Networks
Units
Drops
I/O Devices
2. Right-click on the I/O Devices item.
3. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
I/O Device Number value:
OCR400 - Use the default settings.
OCR161 - Select the same I/O Device Number that you selected when you first configured
the device number.
I/O Device Type value:
OCR400 - Use the default settings.
OCR161 - Select Remote Q-Line from the I/O Device Type pull-down menu.

OW331_54 87
10.3 To insert remote Q-line devices

4. Select the Finish button. The New I/O Devices dialog box appears. The dialog contains the
type and number assigned to the PCRR card.

Figure 36: 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 on OCR400 applications.
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).
5. 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.
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
contains the device number and type.

88 OW331_54
10.4 To insert new remote Q-line nodes

10.4 To insert new remote Q-line nodes


1. Access the Ovation Developer Studio.
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
(The Node item is established by default because Remote Q-Line was selected in the Insert
New I/O Devices Wizard.)
3. Right-click on 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


1. Access the Ovation Developer Studio.
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
(The Crate item is established by default when Remote Q-Line is selected in the Insert New
I/O Device Wizard.)
3. Right-click on the Crate item.
4. Select Insert New. The Insert New Crate Wizard appears.

OW331_54 89
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 37: 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 subitems is added to the system tree.

10.6 To insert a new remote Q-line module


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Slot item:
Systems
Networks
Units
Drops
I/O Devices
Slot
3. Open the Slot item to reveal a Q-Line Module subfolder.
4. Right-click on the Q-Line Module subitem (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.

90 OW331_54
10.6 To insert a new remote Q-line module

9. Select the Config tab.

Figure 38: New Q-Line Module dialog box - Config tab

10. Ensure that the card type and card address values are correct.
11. 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 with the Analog Channels tab selected.

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
Ovation Developer Studio User Guide.)

Figure 39: New Q-Line Module dialog box - Analog Channels tab example

OW331_54 91
10.6 To insert a new remote Q-line module

12. Select Ok or Apply to add the settings to the database.


13. Refer to the Download, Reboot, and Load (see page 31) sections for information on
downloading, rebooting, and loading

92 OW331_54
S E C T I O N 11

Configuring Allen-Bradley drivers

IN THIS SECTION

What is an Allen-Bradley driver?....................................................................................... 93


To insert new device numbers .......................................................................................... 93
To set Allen-Bradley device number parameters.............................................................. 94
To insert an Allen-Bradley device ..................................................................................... 96
To configure Allen-Bradley points ..................................................................................... 97
What are the Allen-Bradley DF-1 commands supported by Ovation? ............................ 100
What are I/O access path examples for Allen-Bradley? ................................................. 101
Allen-Bradley analog input cards .................................................................................... 102
Allen-Bradley digital input cards...................................................................................... 102

11.1 What is an Allen-Bradley driver?


Allen-Bradley manufactures programmable automation 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, ControLogic, and MicroLogic 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.2 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers

OW331_54 93
11.3 To set Allen-Bradley device number parameters

3. Right-click on 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.

11.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 40: Controller Driver Parameters tab (Allen-Bradley)

94 OW331_54
11.3 To set Allen-Bradley device number parameters

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
Scan Point Entries Displays the amount of points available.

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 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
Drop) Allen-Bradley PLC, typically used in redundant configurations only.

Slot This number defines the slot where the Ethernet module is located in the
Allen-Bradley chassis.
This parameter is only active when Communication Protocol is set to
ControlLogix 5000. The slot number refers to the physical location of the
Allen-Bradley Logix processor card.

Node This number is the 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.

OW331_54 95
11.4 To insert an Allen-Bradley device

FIELD DESCRIPTION

Communication Protocol Specifies the communication protocol required by the target device. The
available communication protocols include, PLC5/SLC500, Pyramid
Integrator, ControLogix 5000, and MicroLogix w/NIT-EN1.
Default = PLC5/SLC500

11.4 To insert an Allen-Bradley device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9).
OCR161 - same as the Device number (1-4).
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 41: New I/O Devices window - Allen-Bradley

96 OW331_54
11.5 To configure Allen-Bradley points

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.5 To configure Allen-Bradley points


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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).

OW331_54 97
11.5 To configure Allen-Bradley points

7. Press the Finish button. The New <Point Type> Points dialog appears.

Figure 42: New Analog Points - Allen-Bradley

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 55).

8. Select Third-party from the I/O Type drop down menu.


9. Select Allen-Bradley from the I/O module pull down menu. The New <Point Type> Points
window appears with additional parameters.
10. 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
101) provides examples of I/O access paths for Allen-Bradley.
11. 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
Load (see page 31) sections for information on downloading, rebooting, and loading.

Hardware tab field descriptions — Allen-Bradley

FIELD DESCRIPTION

IO type This is set to Third-party to indicate a third-party point.

98 OW331_54
11.5 To configure Allen-Bradley points

FIELD DESCRIPTION

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
(Control Task) Configuration Parameters 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.
It is recommended 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. This information may also be imported
from DBID files. (See Ovation Database User Guide.)
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the
Register to Register Mapping checkbox 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 101).
Data Type Used to interpret the data type of the Allen-Bradley register.
The choices are: Signed or Unsigned.

OW331_54 99
11.6 What are the Allen-Bradley DF-1 commands supported by Ovation?

11.6 What are the Allen-Bradley 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 9 9 7-4
Type read 0F 68 9 9 9 9 9 7-28
Type write 0F 67 9 9 9 9 9 7-30
Ovation Protocol Selection – PLC2 (PCCC)
Protected bit 02 # 9 9 9 9 9 7-15
write
Protected 00 9 9 9 9 7-19
write
Unprotected 01 # 9 9 9 9 9 9 9 9 9 7-31
read
Ovation Protocol Selection – MicroLogic w/NET-ENI
Logical Read 0F a2 9
Logical Write 0F aa 9
# This command has no FNC byte.
@ Receive only. Processors with this note cannot send the command; they receive the command from a
computer.
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.

100 OW331_54
11.7 What are I/O access path examples for Allen-Bradley?

11.7 What are I/O access path examples for Allen-Bradley?


The I/O Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files. (See Ovation Database User Guide.)

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

OW331_54 101
11.8 Allen-Bradley analog input cards

11.8 Allen-Bradley 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
N7:16 channel 3 value
N7:17 channel 4 value
N7:18 channel 5 value
N7:19 channel 6 value
N7:20 channel 7 value
N7:21 channel 8 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.9 Allen-Bradley 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.

102 OW331_54
S E C T I O N 12

Configuring Foundation Fieldbus first generation


(Gateway) drivers

IN THIS SECTION

What is a Foundation Fieldbus first generation (Gateway) device? ............................... 103


To insert new device numbers ........................................................................................103
To set Foundation Fieldbus (Gateway) device number parameters............................... 104
To insert a Foundation Fieldbus (Gateway) device ........................................................ 105
What are I/O access path examples for Foundation Fieldbus (Gateway)? .................... 113

12.1 What is a Foundation Fieldbus first generation (Gateway)


device?
Fieldbus is an all-digital, two-way, multi-drop communication protocol that interconnects intelligent
devices such as actuators, sensors, discrete devices, and Controllers in the field. At the lowest
level in the hierarchy of plant networks, it is a Local Area Network (LAN) for instruments that
enables basic control and I/O to be moved from the Distributed Control System (DCS) to the field
devices.

The first generation Ovation implementation of Foundation Fieldbus uses hardware and software
components to integrate Fieldbus devices with Ovation technology through a gateway module.
The gateway may reside in an Ovation Controller cabinet or it may be located up to 100 meters
from the Controller.

12.2 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers

OW331_54 103
12.3 To set Foundation Fieldbus (Gateway) device number parameters

3. Right-click on 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.

12.3 To set Foundation Fieldbus (Gateway) device number


parameters
1. Make the appropriate choices in the New Device Numbers dialog box.
2. Select the Ok or Apply button.

Figure 43: Controller Driver Parameters fields (Fieldbus)

Controller Driver Parameters field descriptions (Fieldbus)

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third-party
devices)
Default = Ovation

104 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device

FIELD DESCRIPTION

Scan Point Entries Displays the amount of points available.

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

12.4 To insert a Foundation Fieldbus (Gateway) device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New [I/O Devices] Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select Fieldbus from the I/O Device Type pull-down menu.

OW331_54 105
12.4 To insert a Foundation Fieldbus (Gateway) device

7. Select the Finish button. The New [I/O Devices] dialog box appears.

Figure 44: I/O Device # Foundation Fieldbus

New I/O Devices dialog box - remote Q-Line device type

FIELD DESCRIPTION

I/O Device Number Automatically entered as defined by the system. Used internally to identify
the group information.
I/O Device Type Selects the I/O Driver for the selected device.
Network Port Specifies the ethernet port on the controller to be used.
Primary Drop IP Address Address of the ethernet interface on the primary controller.
Partner Drop IP Address Address of the ethernet interface on the backup controller.
Subnet Mask Used on the primary and backup controller ethernet interface.
Interface Mode (Primary Speed and duplexity of the selected ethernet interface for the primary
Drop) controller.
Interface Mode (Partner Speed and duplexity of the selected ethernet interface for the backup
Drop) controller.
DHCP Enabled Allows you to enable or disable auto addressing to the Fieldbus gateway.
DHCP Start IP Address Selects the IP address the DHCP server will assign.
DHCP End IP Address Last IP address in the range the DHCP server will assign.
Router IP Address IP address of the router between Ovation and the assigned Fieldbus
gateway.
Router Subnet Mask The subnet mask of the router between Ovation and the Fieldbus gateway.
8. Change the Network Port number (OCR400 - N1-N5) (OCR161 - fei0-fei4) if needed.

106 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device

9. Select the Apply then the OK buttons. Notice that the new I/O Device X Foundation Fieldbus
item now appears in the system tree. The title of the I/O Device item contains the device
number and type.
10. Expand the Fieldbus device item, a Fieldbus Gateway item appears.
11. Right-click on the Fieldbus Gateway item.
12. Select Insert New from the resulting pop-up menu. The Insert New Fieldbus Gateway Wizard
appears.
13. Fill in the Fieldbus Gateway Name.

OW331_54 107
12.4 To insert a Foundation Fieldbus (Gateway) device

14. Select Finish, the New Fieldbus Gateway dialog box appears.

Figure 45: New Fieldbus Gateway dialog box - Config tab

Figure 46: New Fieldbus Gateway dialog box - data update rates tab

New Fieldbus Gateway dialog box field descriptions

FIELD DESCRIPTION

Gateway Number Automatically entered as defined by the system. Used


internally to identify the group information.

108 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device

FIELD DESCRIPTION

Gateway Name User defined.


Enable Name Change Allows a name change to be administered, after following all
proper load procedures.
Ovation Point Name Name of the point from where the data is being retrieved.
Link Data Scan Rate (msec) Transfer rate between Ovation and the Fieldbus.
Dynamic Data Scan Rate (msec) Transfer rate between Ovation and the Fieldbus.

15. Make any necessary changes in the two tabs.


16. Select OK, the Fieldbus Gateway item name changes to the Gateway Name added above
(Test), and the item tree fills out under the Fieldbus Gateway item.
17. Expand the new (Test) item to reveal the items under it, see the following example tree.

Figure 47: Fieldbus tree items

18. Right-click on the C01 item.


19. Select Open..
20. Make the appropriate changes in the dialog box.
21. Select OK.
22. Right-click on the P01 item.
23. Select Open, a dialog box opens.
24. Make the appropriate changes in the dialog box.
25. Select OK.
26. Fully expand the Fieldbus (Test) tree.
27. Right-click on the Fieldbus Devices item.

OW331_54 109
12.4 To insert a Foundation Fieldbus (Gateway) device

28. Select Insert New, a dialog box opens.

Figure 48: Choosing the Fieldbus Device

Choosing the Fieldbus device

FIELD DESCRIPTION

Device Name Must be a unique name not used anywhere else in the
system. The system automatically provides a unique name,
but can be changed.
Manufacturer Drop-down list of accepted manufacturers
Device Type Drop-down list of accepted devices from the manufacturer
Device Revision Revision of the Device

29. Make the appropriate changes.

110 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device

30. Select OK, the following dialog box opens.

Figure 49: New Fieldbus Devices dialog box - Config tab

OW331_54 111
12.4 To insert a Foundation Fieldbus (Gateway) device

Figure 50: New Fieldbus Devices dialog box - Plant Web Alerts tab

New Fieldbus Devices dialog box descriptions

FIELD DESCRIPTION

Config Tab
Device Name Must be a unique name not used anywhere else in the
system. The system automatically provides a unique name,
but can be changed.
Manufacturer Drop-down list of accepted manufacturers
Device Type Drop-down list of accepted devices from the manufacturer
Device Revision Revision of the Device
Device Class Class of the Device
Ovation Point Name Ovation point name relating to the device. Should be different

112 OW331_54
12.5 What are I/O access path examples for Foundation Fieldbus (Gateway)?

FIELD DESCRIPTION
for the XXX (C01) and XXX (P01) items

Plant Web Alerts Tab


Device Supports Alarms Check Box to allow alarms
Enable Plant Web Alerts Check Box to allow Web alerts
Device Supports Advisory Alarms Check Box to allow support of advisory alarms
Device Supports Maintenance Check Box to allow support of maintenance alarms
Alarms
Device Supports Communication Check Box to allow support of maintenance alarms
Alarms
Enable Check Box to enable Ovation alarm priority
Ovation alarm priority Ovation alarm priority 1-8, 8 being the highest
Device Supports Failed Alarms Check Box
Device Supports Abnormal Alarms Check Box to allow support of failed alarms
Enable Check Box to enabling abnormal alarm support

31. Make the appropriate changes.


32. Select OK to finish building the device driver.

12.5 What are I/O access path examples for Foundation Fieldbus
(Gateway)?
The IO Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files (See Ovation Database User Guide.)

The following is an example of the format that is used in the Hardware tab IO access path field for
a Toshiba 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

POINT TYPE RECORD TYPE NOTES

INPUT Analog (LA) and Digital Point (LD) Records Data received from the MHI system.

OW331_54 113
12.5 What are I/O access path examples for Foundation Fieldbus (Gateway)?

POINT TYPE RECORD TYPE NOTES

OUTPUT Analog (LA) and Digital Point (LD) Records Control commands and setpoints from the
Ovation System.

Note: Deluxe records are not supported for any point types.

114 OW331_54
S E C T I O N 13

Configuring Foundation Fieldbus second generation


(I/O modules) drivers

IN THIS SECTION

To insert new device numbers ........................................................................................115


To set Foundation Fieldbus (I/O module) parameters .................................................... 116
To insert a Foundation Fieldbus I/O module in the Developer Studio ............................ 117
To add a module record point name ............................................................................... 119
To add a Foundation Fieldbus (I/O module) device........................................................ 120
To assign a node record to each of your ports ............................................................... 123

13.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

OW331_54 115
13.2 To set Foundation Fieldbus (I/O module) parameters

13.2 To set Foundation Fieldbus (I/O module) parameters


1. From the I/O Driver Type dropdown menu, select FIELDBUS MODULE.
2. Click OK.

Note: You only have to perform this task once for each Controller that utilizes Foundation
Fieldbus.

Figure 51: New Device Numbers window

Controller Driver Parameters field descriptions (Fieldbus)

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third-party
devices)
Default = Ovation
Scan Point Entries Displays the amount of points available.

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

116 OW331_54
13.3 To insert a Foundation Fieldbus I/O module in the Developer Studio

13.3 To insert a Foundation Fieldbus I/O module in the Developer


Studio
1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
Networks
Units
Drops
I/O Devices
IO Interfaces
Branch
Slot
3. Select the Ovation module in that empty slot:

Figure 52: Ovation Module in tree

OW331_54 117
13.3 To insert a Foundation Fieldbus I/O module in the Developer Studio

4. Right-click to select Insert New. The Insert New Ovation Module wizard appears:

Figure 53: Insert New Ovation Module wizard

5. Select Foundation Fieldbus BusModule.


6. Click Finish. The New Ovation Module window appears:

Figure 54: New Ovation Module window

It is recommended 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.

118 OW331_54
13.4 To add a module record point name

Note: You must perform this task for each Foundation Fieldbus I/O module that you add.

13.4 To add a module record point name


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to Module Points:
System
Networks
Units
Drops
Points
Module Points
3. Right-click on Module Points to select Insert New. The Insert New Module Points wizard
appears:

Figure 55: Insert New Module Points wizard

4. Type a point name.


5. Pick a frequency.

OW331_54 119
13.5 To add a Foundation Fieldbus (I/O module) device

6. Click Finish. The New Module Points window appears:

Figure 56: New Module Points window

7. Navigate to the 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 Open/Refresh, you will see the fully qualified
module record point name (for example, TEST.UNIT@FB).

Note: You must perform this task for each Foundation Fieldbus I/O module that you add.

13.5 To add a Foundation Fieldbus (I/O module) device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to Fieldbus Devices:
System
Networks
Units
Drops
I/O Devices
Fieldbus Devices

120 OW331_54
13.5 To add a Foundation Fieldbus (I/O module) device

3. Right-click Fieldbus Devices to select Insert New. The Insert New Fieldbus Devices wizard
appears:

Figure 57: 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.

OW331_54 121
13.5 To add a Foundation Fieldbus (I/O module) device

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 58: 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.

122 OW331_54
13.6 To assign a node record to each of your ports

8. Navigate to the PlantWeb Alerts tab:

Figure 59: New Fieldbus Devices window (Plant Web Alerts tab with no PlantWeb Alerts)

9. Note the Enable PlantWeb Alerts checkbox, 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.

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

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to a port:

OW331_54 123
13.6 To assign a node record to each of your ports

System
Networks
Units
Drops
I/O Devices
I/O Interfaces
Branch
Slot
Port
3. Right-click on the port that you want to update (for example, P01 or P02) to select Open. A
port configuration window appears:

Figure 60: 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.

Note: You must perform this task for each Foundation Fieldbus I/O module that you add.

124 OW331_54
S E C T I O N 14

Configuring GE Genius drivers

IN THIS SECTION

To insert new device numbers ........................................................................................125


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

14.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

14.2 To set GE Genius device number parameters


1. Make the appropriate choices in the New Device Numbers dialog box.

OW331_54 125
14.3 To insert a GE Genius device

2. Select the Ok or Apply button.

Figure 61: Controller Driver Parameters fields (Fieldbus)

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
Scan Point Entries Displays the amount of points available.

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

14.3 To insert a GE Genius device


1. Access the Ovation Developer Studio.

126 OW331_54
14.3 To insert a GE Genius device

2. Use the system tree to navigate to the I/O Devices item:


Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New [I/O Devices] Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
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 then the OK buttons. 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 on 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).

OW331_54 127
14.3 To insert a GE Genius device

13. Select finish, the New GE Genius Gateway dialog box appears.

Figure 62: New GE Genius Gateway dialog box

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
(Test), and the items tree fills out under the GE-Device item.
16. Expand the item to revel the GE Genius I/O Blocks item.
17. Right-click on 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.

128 OW331_54
14.4 What are I/O access path examples for GE Genius?

20. Select OK.

Figure 63: 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
Module Input Base Address (word) Revision of the device
Module Output Base Address Class of the device
(word)

14.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
from the information imported from DBID files (See Ovation Database User Guide.)

The following is an example of the format that is used in the Hardware tab IO access path field for
a third-party point:

L45BRKC INPUT

where:

L45BRKC Point Name

INPUT Type

Additional Example:

HTRAISE:20 OUTPUT

OW331_54 129
14.4 What are I/O access path examples for GE Genius?

where:
20 is the point offset supplied by GE and is only needed for OUTPUT point types.

Valid types

POINT TYPE RECORD TYPE NOTES

INPUT Analog (LA) and Digital Point Data received from the GE system.
(LD) Records
OUTPUT Analog (LA) and Digital Point Control commands and setpoints from the
(LD) Records Ovation system.

Note: Deluxe records are not supported for any point types.

130 OW331_54
S E C T I O N 15

Configuring GE Mark V/VI/Ve drivers

IN THIS SECTION

To insert new device numbers ........................................................................................131


To set GE Mark V/VI/Ve device number parameters...................................................... 131
To insert a GE Mark V/VI device..................................................................................... 133
To configure GE Mark V/VI/Ve points ............................................................................. 134
What are I/O access path examples for GE Mark V and VI?.......................................... 138

15.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

15.2 To set GE Mark V/VI/Ve device number parameters


1. Make the appropriate choices in the New Device Numbers dialog box.

OW331_54 131
15.2 To set GE Mark V/VI/Ve device number parameters

2. Select the Ok or Apply button.

Figure 64: 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.
Simulator Driver Type Selects the Simulator Driver for the selected device.
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.

132 OW331_54
15.3 To insert a GE Mark V/VI 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
Scan Point Entries Displays the amount of points available.

15.3 To insert a GE Mark V/VI device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select GE Mark V/VI 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. 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.

OW331_54 133
15.4 To configure GE Mark V/VI/Ve points

15.4 To configure GE Mark V/VI/Ve points


1. Access the Ovation Developer Studio.
2. Use the following path to access the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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 appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.

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 55).

9. Select third-party from the I/O Type dropdown 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.

134 OW331_54
15.4 To configure GE Mark V/VI/Ve points

Note: The following figure shows an example of the Insert New Analog Points Wizard.

Figure 65: Hardware tab for GE Point name

11. Complete the information in the window as it pertains to the GE Mark V/VI/Ve driver. The
table below discusses the parameters that are common to all drivers and also to those that
pertain to GE Mark specifically. I/O Access Path Examples for GE Mark V/VI/Ve (see page
138) provides examples of I/O access paths for GE Mark V/VI/Ve.
12. After completing the information in the window, 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 31) sections for information on downloading, rebooting, and loading

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.

OW331_54 135
15.4 To configure GE Mark V/VI/Ve points

FIELD DESCRIPTION

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.

It is recommended that devices 1 and 2 be reserved for Qline 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,


it is recommended 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
(Control Task) Controller Configuration Parameters dialog box.

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.

It is recommended 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.


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 the information provided from DBID files. 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

136 OW331_54
15.4 To configure GE Mark V/VI/Ve points

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

OW331_54 137
15.5 What are I/O access path examples for GE Mark V and VI?

15.5 What are I/O access path examples for GE Mark V and VI?
The IO Access path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files (See Ovation Database User Guide.)

The following are examples of the format that appears in the Hardware tab IO access path field
for a General Electric V and VI 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,
Records select 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,
Records select 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
Records for at least two seconds to ensure being sent to GE.
SETPOINT Analog Point (LA, DA) For scaling of setpoints, use Top Output Scale and Bottom
Records Output Scale for INT and UINT. For other data types, (USINT,
SINT, UDINT, DINT, REAL), scaling is always one to one.

138 OW331_54
15.5 What are I/O access path examples for GE Mark V and VI?

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
Records. information 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

OW331_54 139
S E C T I O N 16

Configuring MHI drivers

IN THIS SECTION

To insert new device numbers ........................................................................................141


To set MHI device number parameters........................................................................... 141
To insert an MHI device ..................................................................................................143
To configure MHI points ..................................................................................................143
What are I/O access path examples for MHI? ................................................................ 145

16.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

16.2 To set MHI device number parameters


1. Make the appropriate choices in the New Device Numbers dialog box.

OW331_54 141
16.2 To set MHI device number parameters

2. Select the Ok or Apply button.

Figure 66: Controller Driver Parameters fields (MHI)

Controller Driver Parameters field descriptions (MHI)

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices)
Default = Ovation
Scan Point Entries Displays the amount of points available.

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
Drop) this is not a redundant drop, this field is not active.
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

142 OW331_54
16.3 To insert an MHI device

FIELD DESCRIPTION
limit (set in the Timeout parameter) is exceeded.
(False, True) Default = True

16.3 To insert an MHI device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select MHI 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. 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.

16.4 To configure MHI points


1. Access the Ovation Developer Studio.
2. Use the following path to access the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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 appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.

OW331_54 143
16.4 To configure MHI points

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 55).

9. Select Third-Party from the I/O Type dropdown menu.


10. Select MHI from the I/O module pull-down menu. The New <Point Type> Points window
appears with additional parameters.

Figure 67: 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 145) provides examples of I/O
access paths for MHI.
12. After completing the information in the window, select the Ok or Apply button. Continue using
the mapping points procedure for every point you want to map. Refer to the Download,
Reboot, and Load (see page 31) 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.

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 is disabled for MHI third-party points.

144 OW331_54
16.5 What are I/O access path examples for MHI?

FIELD DESCRIPTION

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 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.
It is recommended 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 MHI. This information may also be imported from DBID
files (See Ovation Database User Guide.)

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 145).

16.5 What are I/O access path examples for MHI?


The I/O Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files. (See Ovation Database User Guide.)

The following is an example of the format that is used in the Hardware tab IO access path field for
a Toshiba 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.

OW331_54 145
16.5 What are I/O access path examples for MHI?

Valid MHI types

POINT TYPE RECORD TYPE NOTES

INPUT Analog (LA) and Digital Point Data received from the MHI system.
(LD) Records
OUTPUT Analog (LA) and Digital Point Control commands and setpoints from the Ovation
(LD) Records System.

Note: Deluxe records are not supported for any point types.

146 OW331_54
S E C T I O N 17

Configuring Modbus drivers

IN THIS SECTION

To insert new device numbers ........................................................................................147


To set Modbus device number parameters .................................................................... 147
To insert a Modbus device ..............................................................................................149
To configure Modbus points............................................................................................ 150
What are I/O access path examples for Modbus? .......................................................... 153

17.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

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

OW331_54 147
17.2 To set Modbus device number parameters

2. Select the Ok or Apply button.

Figure 68: 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
Scan Point Entries Displays the amount of points available.

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

PLC Selects the communication protocol for the selected hostname.


Communication
Protocol „ Reserved 1 = Unused.
„ 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

148 OW331_54
17.3 To insert a Modbus device

FIELD DESCRIPTION

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

17.3 To insert a Modbus device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select Modbus 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 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.

OW331_54 149
17.4 To configure Modbus points

17.4 To configure Modbus points


1. Access the Developer Studio.
2. Use the system tree to navigate to the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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 appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.

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 55).

9. Select Third Party from the I/O Type dropdown menu.

150 OW331_54
17.4 To configure Modbus points

10. Select Modbus from the I/O module pull-down menu. The New <Point Type> Points window
appears with additional parameters.

Figure 69: New Analog Points - Modbus

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 153) provides
examples of I/O access paths for Modbus.
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
Load (see page 31) sections for information on downloading, rebooting, and loading.

Hardware tab fields descriptions — Modbus

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

OW331_54 151
17.4 To configure Modbus points

FIELD DESCRIPTION
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.
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.
It is recommended 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 Modbus. This information may also be imported from
DBID files (See Ovation Database User Guide.)
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the
Register-to-Register Mapping checkbox 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.
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.

152 OW331_54
17.5 What are I/O access path examples for Modbus?

FIELD DESCRIPTION

Byte Order Key words that allow register byte order to be changed.
The choices are: Swap Bytes, Swap Words, and Swap Bytes and Words.

17.5 What are I/O access path examples for Modbus?


The IO Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files (See Ovation Database User Guide.)

The following is an example of the format that is used in the Hardware tab IO access path field for
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

Additional Examples:
„ 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
„ Read holding registers 40001 and 40002 as a float from plc_1.
MODBUS 1 IN 40001 FLOAT PLC_1

OW331_54 153
S E C T I O N 18

Configuring Profibus device drivers

IN THIS SECTION

To use Developer Studio to add a new Ovation I/O device number to the Controller .... 155
To insert a Profibus I/O module in the Developer Studio................................................ 157
To add a module record point name ............................................................................... 158
To assign a node record to each of your ports ............................................................... 160

18.1 To use Developer Studio to add a new Ovation I/O device


number to the Controller
1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Device Number item:
Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Number
3. Right-click Device Number.

OW331_54 155
18.1 To use Developer Studio to add a new Ovation I/O device number to the Controller

4. Select Insert New. The Insert New Device Numbers Wizard appears:

Figure 70: 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:

Figure 71: New Device Numbers window

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:

156 OW331_54
18.2 To insert a Profibus I/O module in the Developer Studio

Systems
Networks
Units
Drops
I/O Devices
10. Right-click I/O Devices to select Insert New. The Insert New I/O Devices wizard appears.
11. From the I/O Device Number dropdown 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.

18.2 To insert a Profibus I/O module in the Developer Studio


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to an empty slot under your Ovation IOIC branch:
Networks
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 to select Insert New. The Insert New Ovation Module wizard appears:

Figure 72: Insert New Ovation Module wizard

OW331_54 157
18.3 To add a module record point name

5. Select Profibus BusModule.


6. Click Finish. The New Ovation Module window appears.
7. It is recommended that you leave the Module Record Point Name in the Value column
empty.
8. Click the Module tab.
9. Choose simplex (the standard configuration) or redundant (if you are using redundant
modules). If you choose simplex, click OK to finish. If you choose redundant, you must also
select a redundant partner from the drop-down menu, which must already be added.
10. Click OK.
11. Click OK. Two ports (P01 and P02) are automatically created in the slot.

Note: You must perform this task for each Profibus I/O module that you add.

18.3 To add a module record point name


1. Access the Ovation Developer Studio.
2. Navigate to Module Points:
Systems
Networks
Units
Drops
Points
Module Points
3. Right-click on Module Points to select Insert New. The Insert New Module Points wizard
appears:

Figure 73: Insert New Module Points wizard

4. Type a point name.

158 OW331_54
18.3 To add a module record point name

5. Pick a frequency.
6. Click Finish. The New Module Points window appears:

Figure 74: New Module Points window

7. Navigate to the Hardware tab:

Figure 75: 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.

OW331_54 159
18.4 To assign a node record to each of your ports

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

1. Access the Ovation Developer Studio.


2. Use the system tree to navigate to a port:
System
Networks
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 to select Open. A port configuration window appears:

Figure 76: 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.
6. Select an I/O task index number.
7. Click OK.

160 OW331_54
18.4 To assign a node record to each of your ports

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.

OW331_54 161
S E C T I O N 19

Configuring RTP I/O drivers

IN THIS SECTION

To insert new device numbers ........................................................................................163


To set RTP I/O device number parameters .................................................................... 163
To insert an RTP I/O device............................................................................................ 165
To configure RTP I/O points............................................................................................ 165
What are I/O access path examples for RTP I/O?.......................................................... 168

19.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

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

OW331_54 163
19.2 To set RTP I/O device number parameters

2. Select the Ok or Apply button.

Figure 77: Controller Driver Parameters field (RTP I/O)

Controller Driver Parameters field descriptions (RTP I/O)

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices)
Default = Ovation
Scan Point Entries Displays the amount of points available.
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 (See Ovation Developer Studio User Guide.)
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
(seconds) connection.

164 OW331_54
19.3 To insert an RTP I/O device

FIELD DESCRIPTION

Default = 30

19.3 To insert an RTP I/O device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select RTP I/O 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. 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.

19.4 To configure RTP I/O points


1. Access the Ovation Developer Studio.
2. Use the following path to access the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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 appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.

OW331_54 165
19.4 To configure RTP I/O points

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 55).

9. Select Third-Party from the I/O Type drop down menu.


10. Select RTP from the I/O module pull down menu. The New <Point Type> Points window
appears with additional parameters.

Note: The following figure shows an example of the Insert New Analog Points Wizard.

Figure 78: 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 168) provides examples of I/O
access paths for RTP.
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
Load (see page 31) sections for information on downloading, rebooting, and loading.

Hardware Tab fields entries — RTP I/O

FIELD DESCRIPTION

IO type This is set to Third-Party to indicate a third-party point.

166 OW331_54
19.4 To configure RTP I/O points

FIELD DESCRIPTION

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 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 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.
It is recommended 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 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 RTP I/O. This information may also be imported from
DBID files. (See Ovation Database User Guide.)
Packed points (LP) have 16 IO Access paths, one for each bit. The use of the
Register-to-Register Mapping checkbox 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.

OW331_54 167
19.5 What are I/O access path examples for RTP I/O?

FIELD DESCRIPTION

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.
The choices are: 0 through 15.
Channel Number Analog channel number.
The choices are: 0 through 15.
Gain Code RTP gain code.
The choices are: 0 through 15.
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.
The choices are: 0 through 15.

19.5 What are I/O access path examples for RTP I/O?
The IO Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files. (See Ovation Database User Guide.)

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.

The following is an example of the format that is used in the Hardware tab IO access path field for
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.

168 OW331_54
S E C T I O N 20

Configuring Toshiba drivers

IN THIS SECTION

To insert new device numbers ........................................................................................169


To set Toshiba device number parameters .................................................................... 169
To insert a Toshiba device .............................................................................................. 171
To configure Toshiba points............................................................................................ 171
What are I/O access path examples for Toshiba? ..........................................................173

20.1 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on 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.

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

OW331_54 169
20.2 To set Toshiba device number parameters

2. Select the Ok or Apply button.

Figure 79: Controller Driver Parameters fields (Toshiba)

Controller Driver Parameters field descriptions (Toshiba)

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices)
Default = Ovation
Scan Point Entries Displays the amount of points available.

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
Drop) this is not a redundant drop, this field is not active.
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 Allows you to determine if this interface can fail the Controller when an error
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 does fail over to Backup when the response

170 OW331_54
20.3 To insert a Toshiba device

FIELD DESCRIPTION
time limit (set in the Timeout parameter) is exceeded.
(False, True) Default = True

20.3 To insert a Toshiba device


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
6. Select Toshiba 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. 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.

20.4 To configure Toshiba points


1. Access the Ovation Developer Studio.
2. Use the following path to access the Points item:
Systems
Networks
Units
Drops
Points
3. Under the Points item, select either an Analog, Digital, or Packed point to configure.
4. Right-click on 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 appears.
8. Select the Hardware tab on the New <Point Type> Points dialog.

OW331_54 171
20.4 To configure Toshiba points

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 55).

9. Select Third-Party from the I/O Type dropdown menu.


10. Select Toshiba from the I/O module pull-down menu. The New <Point Type> Points window
appears with additional parameters.

Figure 80: New Analog Points - Toshiba

11. Complete the information in the window as it pertains to the Toshiba driver. The table below
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 173) provides
examples of I/O access paths for Toshiba.
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
Load (see page 31) 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 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 is disabled for Toshiba third-party points.

172 OW331_54
20.5 What are I/O access path examples for Toshiba?

FIELD DESCRIPTION

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 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.
It is recommended 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 Toshiba. This information may also be imported from
DBID files (See Ovation Database User Guide.)
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 173).

20.5 What are I/O access path examples for Toshiba?


The IO Access Path is filled in automatically from the information entered in the Hardware tab or
from the information imported from DBID files (See Ovation Database User Guide.)

The following is an example of the format that is used in the Hardware tab IO access path field for
a Toshiba third-party point:

L45BRKC INPUT

where:
L45BRKC Point Name

INPUT Type

Additional Examples:
„ HTRAISE OUTPUT
„ ALM1HI ALARM

Valid Toshiba Types

POINT TYPE RECORD TYPE NOTES

INPUT Analog (LA) and Digital Point (LD) Records Data received from the Toshiba
system.

OW331_54 173
20.5 What are I/O access path examples for Toshiba?

POINT TYPE RECORD TYPE NOTES

OUTPUT Analog (LA) and Digital Point (LD) Records Control commands and setpoints from
the Ovation System.

ALARM Digital (LD) Point Records Alarms received from the Toshiba
system.

Note: Deluxe records are not supported for any point types.

174 OW331_54
S E C T I O N 21

Configuring external Ovation network drivers

IN THIS SECTION

What are external Ovation network devices? ................................................................. 175


To insert new device numbers ........................................................................................175
To set external Ovation network device number parameters ......................................... 176
To insert external Ovation network I/O devices .............................................................. 177
To map external Ovation network points ........................................................................ 177
To reconfigure an external Ovation network driver ......................................................... 179

21.1 What are external Ovation network devices?


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
Developer Studio User Guide.) Make sure you have completed To Insert New Device Numbers
(see page 59) before continuing.

21.2 To insert new device numbers


1. Access the Ovation Developer Studio.

Note: The OCR400 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:


Systems
Networks
Units
Drops
Configuration
Controller
Devices
Device Numbers
3. Right-click on the Device Numbers item.
4. Select Insert New from the pop-up menu. The Insert New Device Numbers Wizard appears.

OW331_54 175
21.3 To set external Ovation network device number parameters

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.

21.3 To set external Ovation netw ork device number parameters


1. Make the appropriate choices in the New Device Numbers dialog box.
2. Select the Ok or Apply button.

Figure 81: General Controller Driver Parameters tab - driver specific fields

General Controller Driver Parameters tab descriptions - driver specific fields

FIELD DESCRIPTION

I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third-party
devices).
Default = Ovation
Scan Point Entries Displays the amount of points available.

Fail Control 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

176 OW331_54
21.4 To insert external Ovation network I/O devices

FIELD DESCRIPTION
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

21.4 To insert external Ovation network I/O devices


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
3. Right-click on the I/O Devices item.
4. Select Insert New from the resulting pop-up menu. The Insert New I/O Devices Wizard
appears.
5. Pull down the I/O Device Number menu.
6. Select the I/O Device Number:
OCR400 - first available (5-9)
OCR161 - same as the Device number (1-4).
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 appears, showing the information you
just entered.
10. Select the Ok or Apply button.

21.5 To map external Ovation network points


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the Points item:
Systems
Networks
Units
Drops
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
Type> = Analog, Digital, or Packed).

OW331_54 177
21.5 To map external Ovation network points

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.

Figure 82: New Packed Points window

Note: The following figure shows an example of the Insert New Analog Points Wizard.

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

178 OW331_54
21.6 To reconfigure an external Ovation network driver

8. Select the Hardware tab on the New <Point Type> Points dialog.

Figure 83: New Analog Points — Hardware tab

21.6 To reconfigure an external Ovation network driver


1. Access the Ovation Developer Studio.
2. Use the system tree to navigate to the I/O Devices item:
Systems
Networks
Units
Drops
I/O Devices
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 (OCR400 - first available) (OCR161 - same as the device
number).
5. Select External Ovation Network from the I/O device Type pull-down menu.
6. Select the Finish button. The New I/O Devices dialog box appears.
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.

OW331_54 179
S E C T I O N 22

Using the Controller Diagnostics tool

IN THIS SECTION

What is the Controller Diagnostics tool? .........................................................................181


What are the software platforms that Controller Diagnostics supports?......................... 182
What is the Controller Diagnostics window?................................................................... 183
What is the Controller List in the Controller Diagnostics window?.................................. 187
What is the Controller Overview panel in the Controller Diagnostics window? .............. 188
What is the Controller Diagnostics Update Backup function? ........................................ 190
What is the Control Task Information tab in the Controller Diagnostics window? .......... 191
What is the I/O Information tab in the Controller Diagnostics window? .......................... 193
What is the Software Versions tab in the Controller Diagnostics window?..................... 197
What is the Point Details tab in the Controller Diagnostics window?.............................. 198
What is the Sheet Information tab in the Controller Diagnostics window? ..................... 199
What is the Refresh function for the Controller Diagnostics window? ............................ 200

22.1 What is the Controller Diagnostics tool?


The Controller Diagnostics function is a diagnostic tool that displays information about the
Controller. You can select the Controller that you want to query from a drop hierarchy tree or from
a dialog box. The information about the selected Controller appears in a user-friendly Controller
Diagnostics window (see page 183). 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 187).
„ Update data in a backup Controller to match the data in the primary Controller (see page
190).
„ Display information about the control tasks for that Controller (see page 191).
„ Display information about I/O modules that interface to the selected Controller (see page
193).
„ Download firmware to intelligent I/O modules that interface to the selected Controller (see
page 195).
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).

OW331_54 181
22.2 What are the software platforms that Controller Diagnostics supports?

22.2 What are the software platforms that Controller Diagnostics


supports?
The Controller Diagnostics function is designed to run on both Windows-based and Solaris-based
Ovation systems. In general, functionality remains the same for both platforms. However, where
differences exist between the platforms, information is specifically labeled "for Window-based
systems" or "for Solaris-based systems."

Note: Where functionality is the same for both platforms, this document uses Windows-based
graphics.

182 OW331_54
22.3 What is the Controller Diagnostics window?

22.3 What is the Controller Diagnostics window?


After you have accessed the Controller Diagnostics window, you can use it to diagnose all the
Controllers in a network.

The Controller Diagnostics window contains a menu bar (see page 186) and a toolbar (see page
186).

The left portion of the Controller Diagnostics window contains a Controller Overview section (see
page 188) that provides internal information about the selected Controller. This section also
contains an Update Backup button (see page 190) 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 187) 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 191) 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 197) to identify the software version of each
software package that is installed on the selected Controller.
„ Use the Point Details tab (see page 198) to list the points originated and received by the
selected Controller.
„ Use the Sheet Information tab (see page 199) to provide information about the elements on
control sheets for the selected Controller.

OW331_54 183
22.3 What is the Controller Diagnostics window?

Figure 84: Controller Diagnostics window

22.3.1 To access the Controller Diagnostics tool in a Windows-based Ovation


system
1. Access an Ovation workstation.

184 OW331_54
22.3 What is the Controller Diagnostics window?

2. At the workstation, select Start -> Ovation -> Ovation Utilities -> Diagnostics.
The Controller Diagnostics window appears.

Figure 85: Controller Diagnostics window

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

OW331_54 185
22.3 What is the Controller Diagnostics window?

22.3.3 Controller Diagnostics menu bar

The Controller Diagnostics window contains a menu bar that provides three drop-down menus:

Figure 86: Controller Diagnostics menu bar

Controller Diagnostics menus

MENU DESCRIPTION

File ƒ Select a Controller - Displays the Select a Controller window (see page 187).
ƒ 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.

22.3.4 Controller Diagnostics toolbar

The Controller Diagnostics window provides a toolbar. Drag the mouse over the toolbar icons to
identify each icon.

Figure 87: Controller Diagnostics toolbar

The toolbar icons (left to right) perform the following functions:


„ The window icon displays the Select a Controller window (see page 187).
„ 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.

186 OW331_54
22.4 What is the Controller List in the Controller Diagnostics window?

22.4 What is the Controller List in the Controller Diagnostics


window?
All the Controllers in your network are listed in a hierarchal tree that begins with the network and
ends with the Controller drops. This Controller List appears beneath the Controller Overview
information panel. An example is shown in the following figure:
„ Network = FE221
„ Unit = UNIT0
„ Controller drops = DROP11/DROP61

Figure 88: Controller List

Select the Controller whose information you want to display. Double-click on the desired
Controller and the data for the first Controller listed in a redundant pair displays (Drop11 in the
preceding figure). Right-click on 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.

22.4.1 To select a Controller in the Controller Diagnostics window


1. Select a Controller from the system tree in the Controller List (see page 187) window
(located beneath the Controller Overview panel).
OR

OW331_54 187
22.5 What is the Controller Overview panel in the Controller Diagnostics window?

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 89: Select a Controller Drop dialog box

22.5 What is the Controller Overview panel in the Controller


Diagnostics window?
The left panel of the Controller Diagnostics window provides internal information about the
Controller you have selected and its Partner Controller. This information appears along with each
tab that you select.

Figure 90: Controller overview panel

188 OW331_54
22.5 What is the Controller Overview panel in the Controller Diagnostics window?

Fields in Controller Overview panel (Primary and Partner Controllers)

FIELD FIELD DESCRIPTION

Drop Name Drop number for the Controller drop that you highlight in the Select
a Controller Drop section of the Controller Diagnostics window.
Right-click on 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.
Comm Services Displays whether or not the Controller is able to communicate on
the system. Double-click on the Primary or Partner cell to display a
pull-down menu. Use the menu to enable or disable the
communication tasks (telnet, remote login, and FTP) on the
Controller. Disabling these tasks prevents unauthorized logins and
file transfers to the Controller.
Controller Type Displays the type of Controller:
ƒ OCR161
ƒ OCR400
Processor Unique hardware CPU type for the selected Controller drop (for
example, Pentium).
Mode Displays the mode of the Controller:
ƒ Control
ƒ Backup
Fault Code 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.
Controller Version Version of the Ovation Controller software.
Kernel Version Version of the internal 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 Amount of originated points in the Controller.
Received Points Amount of received points in the Controller.
Update Backup button Updates data in the backup Controller to match data in the primary
(see page 190) Controller.

OW331_54 189
22.6 What is the Controller Diagnostics Update Backup function?

22.6 What is the Controller Diagnostics Update Backup function?


You can use the Update Backup function when a Drop Load function for a Controller has failed
and you have to clear and reload the Controller. This puts the Controller into backup, but since it
has been cleared, a mismatch may now exist between this backup Controller and the primary
Controller.

Note: You can use the Drop Details diagram to determine if a mismatch exists for your
Controller.

After determining the cause of the failure (by analyzing the messages and fault codes) and
correcting the problem, you can reconcile the mismatch smoothly (without “bumps”) by using the
Update Backup function (see page 190).

Refer to the Fault Information Tool for information on the error codes.

You can diagnose any fault codes that appear by accessing the Ovation Fault Information Tool,
logging on to the Ovation/WDPF Users site, and clicking the Fault Information Tool in the left
hand menu.

You can also, enter the following URL to log on to the Fault Information Tool directly:

https://www.ovationusers.com/FIT/index.asp

22.6.1 To update your backup Controller in the Controller Diagnostics window


1. Access the Controller Diagnostics window.
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:
a) Use the system tree to navigate to the Drops folder:
Systems
Networks
Units
Drops
b) Right-click on the folder of the drop you want to reboot.
c) Select Reboot from the right-click pop-up menu. The right-click menu only displays items
that are applicable for that drop.
d) For non-redundant drops, skip to Step 5.
e) For redundant drops, the “Select a drop to reboot” dialog box appears.
¾ Select the drop you want to reboot.
¾ Select Ok.
5. A confirmation dialog box appears.
6. Select Yes to close the window and execute the reboot process.

190 OW331_54
22.7 What is the Control Task Information tab in the Controller Diagnostics window?

22.7 What is the 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 44).

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 91: Control Task Information tab

OW331_54 191
22.7 What is the 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
cycle Time task.
(msec)
Average cycle Displays the average execution time (in milliseconds) that is actually used for a
Time (msec) control task.
Worst cycle Displays the longest execution time (in milliseconds) that is actually used for a
Time (msec) control 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.

192 OW331_54
22.8 What is the I/O Information tab in the Controller Diagnostics window?

22.8 What is the I/O Information tab in the Controller Diagnostics


window?
The I/O Information tab provides information about the I/O modules that interface with the
selected Controller. You can select a Controller drop and the associated modules appear in the
I/O Information tab along with the descriptions of those modules.

Some intelligent modules contain firmware that can be updated. The Module Firmware Download
window describes what revision of the firmware the module contains (Module Version) as well as
the latest firmware that is available on the Controller (Controller Version) for the module. If there is
a difference between the Module Version and the Controller Version, you can select the
Download button to download the latest firmware to the module from the Controller.

You can also download older firmware, if desired. A warning message appears and you are
required to verify the choice to re-download.

CAUTION: 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.

OW331_54 193
22.8 What is the I/O Information tab in the Controller Diagnostics window?

Figure 92: I/O Information tab

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
number decimal 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

194 OW331_54
22.8 What is the I/O Information tab in the Controller Diagnostics window?

22.8.1 What firmware can be downloaded to the I/O modules through the
Controller Diagnostics window

The firmware for certain I/O modules is provided on the Ovation release CD and is installed on
the Ovation Software Server during the Ovation software installation process (see Ovation
Software Installation Manual). The firmware is downloaded to the Controller when
Query/Download is used. This firmware might differ from the firmware that is currently on your I/O
module and you might desire 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 - applicable with OCR400 controllers.
„ Ovation I/O Fieldbus - applicable with OCR400 controllers.
„ Ovation I/O DeviceNet - applicable with OCR400 controllers.

CAUTION: 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.

22.8.2 To download firmware revisions to the I/O modules through the Controller
Diagnostics window

If there is a difference between the latest available firmware and the firmware on your I/O module,
and you desire to update your I/O module, use the following procedure:

1. Access the Controller Diagnostics utility (see page 184) at an Ovation workstation.
2. Select the I/O Information tab (see page 193).

OW331_54 195
22.8 What is the I/O Information tab in the Controller Diagnostics window?

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 93: 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.

CAUTION: 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.

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 197) after download, the Reboot
Module button is enabled.

196 OW331_54
22.9 What is the Software Versions tab in the Controller Diagnostics window?

22.8.3 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).

22.9 What is the Software Versions tab in the Controller Diagnostics


window?
The Software Versions tab identifies the software version of each software package that is
installed on the Controller. This information is useful during troubleshooting to determine if you
have the latest software.

Figure 94: Software Versions tab

OW331_54 197
22.10 What is the Point Details tab in the Controller Diagnostics window?

22.10 What is the Point Details tab in the Controller Diagnostics


window?
The Point Details tab lists the name and SID for the points originated and received by the
selected Controller. Right-click on the SID or the name of a point, and the Point Menu for the
selected point appears. You can also right-click on a point to access the Point Menu.

Figure 95: 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.

198 OW331_54
22.11 What is the Sheet Information tab in the Controller Diagnostics window?

22.11 What is the Sheet Information tab in the Controller Diagnostics


window?
The Sheet Information tab provides information for the selected Controller about the control tasks,
control sheets, algorithm points, and algorithms on the sheets. You can resize the columns and
also use the scroll bars to locate information.

Figure 96: 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 on 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.

OW331_54 199
22.12 What is the Refresh function for the Controller Diagnostics window?

FIELD DESCRIPTION

Row Internal algorithm information.


Bit Internal algorithm information.
Algorithm Template Information

Name Name of the algorithm parameter.

Description Description of the algorithm parameter.


Record Type Input/output points of the algorithm. If this field is blank, there is no point.
Record Field Field in the algorithm point where information is stored.
Data Type Used internally by the Controller.
Flags Used internally by the Control Builder.
Default Default value set by the algorithm.
Min Minimum defined value of the input/output point.
Max Maximum defined value of the input/output point.
Enum Count The amount of enumerations an algorithm parameter can have. For example, if a
parameter can be "on" or "off" (two choices), the Enum Count is two.
Right-click on 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.

22.12 What is the Refresh function for the Controller Diagnostics


window?
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.

200 OW331_54
Index

A I
Adding OCR400 Controllers to WDPF Q- Initial steps to configuring drivers • 57
Line I/O • 13 Introduction to the OCR400 Ovation
Allen-Bradley analog input cards • 103 Controller • 1
Allen-Bradley digital input cards • 103
M
C
Monitoring OCR400 Controller Status • 26
Configuring Allen-Bradley drivers • 93
Configuring device drivers in the Controller • O
57 OCR 400 Controller Modules • 12
Configuring external Ovation network drivers OCR400 Controller definition • 2
• 177 OCR400 Controller I/O interfaces • 7
Configuring Foundation Fieldbus first OCR400 Controller module replacement • 12
generation (Gateway) drivers • 105 Online Controller Restore Mode • 50
Configuring Foundation Fieldbus second Ovation Controller hardware • 7
generation (I/O modules) drivers • 117
Configuring GE Genius drivers • 127 Q
Configuring GE Mark V/VI/Ve drivers • 133
Q-Line I/O module addressing • 21
Configuring local Ovation I/O drivers • 59
Configuring local Q-Line drivers • 77 S
Configuring MHI drivers • 143
Configuring Modbus drivers • 149 Starting the OCR400 Controller • 25
Configuring Profibus device drivers • 157 T
Configuring remote Ovation I/O drivers • 67
Configuring remote Q-Line drivers • 85 To access the Controller Diagnostics tool in
Configuring RTP I/O drivers • 165 a Solaris-based Ovation system • 187
Configuring the Controller • 35 To access the Controller Diagnostics tool in
Configuring the Controller software • 35 a Windows-based Ovation system • 186
Configuring Toshiba drivers • 171 To add a Foundation Fieldbus (I/O module)
Controller Diagnostics menu bar • 188 device • 122
Controller Diagnostics toolbar • 188 To add a module record point name • 121,
Converting from an OCR161 Controller to an 160
OCR400 Controller • 5 To assign a node record to each of your
Copyright Notice • 2 ports • 125, 162
To configure alarm timestamping to the
D millisecond level • 54
Defining and addressing the I/O devices • 15 To configure Allen-Bradley points • 97
Determining the NIC (network ethers) To configure GE Mark V/VI/Ve points • 136
address of a drop • 36 To configure MHI points • 145
To configure Modbus points • 152
E To configure Ovation and Q-Line devices •
57
Examples of Controller cabinet I/O module
To configure RTP I/O points • 167
addresses • 17
To configure the online Controller restore
Examples of extended I/O cabinet module
mode • 52
addresses • 18
To configure third-party devices • 58
Examples of Relay Output module
To configure Toshiba points • 173
addresses • 20
To confirm Controller networking (network
Examples of remote node I/O cabinet
item) • 46
module addresses • 19

OW331_54 201
Index

To determine the IP address of a To open OCR400 Controller module covers •


machine/drop • 36 12
To determine the NIC address using the one To power up the Controller • 26
assigned to the Controller • 36 To reboot a Controller drop • 33
To determine the NIC hardware address To reboot an I/O module • 199
from the card label • 36 To reconfigure an external Ovation network
To download Controller drop configuration • driver • 181
31 To replace OCR400 Controller module
To download firmware revisions to the I/O covers • 12
modules through the Controller To select a Controller in the Controller
Diagnostics window • 197 Diagnostics window • 189
To insert a Foundation Fieldbus (Gateway) To set Allen-Bradley device number
device • 107 parameters • 94
To insert a Foundation Fieldbus I/O module To set Controller parameters • 42
in the Developer Studio • 119 To set existing control tasks • 44
To insert a GE Genius device • 128 To set external Ovation network device
To insert a GE Mark V/VI device • 135 number parameters • 178
To insert a local Ovation I/O module • 64 To set Foundation Fieldbus (Gateway)
To insert a Modbus device • 151 device number parameters • 106
To insert a new Controller drop • 37 To set Foundation Fieldbus (I/O module)
To insert a new drop point • 40 parameters • 118
To insert a new local Ovation I/O branch • 63 To set GE Genius device number
To insert a new local Q-line crate • 81 parameters • 127
To insert a new local Q-line module • 81 To set GE Mark V/VI/Ve device number
To insert a new remote Q-Line crate • 89 parameters • 133
To insert a new remote Q-line module • 90 To set MHI device number parameters • 143
To insert a Profibus I/O module in the To set Modbus device number parameters •
Developer Studio • 159 149
To insert a remote Ovation I/O module • 72 To set Ovation device number parameters •
To insert a remote Ovation I/O new branch • 59, 67, 77, 85
72 To set RTP I/O device number parameters •
To insert a Toshiba device • 173 165
To insert an Allen-Bradley device • 96 To set Toshiba device number parameters •
To insert an MHI device • 145 171
To insert an RTP I/O device • 167 To update your backup Controller in the
To insert external Ovation network I/O Controller Diagnostics window • 192
devices • 179 To use Developer Studio to add a new
To insert local Ovation I/O devices • 61 Ovation I/O device number to the
To insert local Q-Line devices • 79 Controller • 157
To insert new control tasks • 46 To verify OCR400 Controller Hardware • 25
To insert new device numbers • 59, 67, 77,
85, 93, 105, 117, 127, 133, 143, 149, 165, U
171, 177 Using the Controller Diagnostics tool • 183
To insert new remote Q-line nodes • 89
To insert remote Ovation I/O devices • 69 V
To insert remote Ovation I/O new nodes • 71
Verifying Controller hardware and power
To insert remote Q-line devices • 87
status • 25
To load a Controller drop • 33
To map a 16-bit PLC register to a 16-bit W
packed point • 55
To map external Ovation network points • What additional software configurations are
179 needed for Controllers? • 54
To modify an external Ovation networks What are external Ovation network devices?
device • 24 • 177
To modify an I/O device • 23 What are I/O access path examples for
To modify Controller networking (drop item) • Allen-Bradley? • 102
48

202 OW331_54
Index

What are I/O access path examples for What is the Controller Diagnostics window? •
Foundation Fieldbus (Gateway)? • 115 185
What are I/O access path examples for GE What is the Controller List in the Controller
Genius? • 131 Diagnostics window? • 189
What are I/O access path examples for GE What is the Controller Overview panel in the
Mark V and VI? • 140 Controller Diagnostics window? • 190
What are I/O access path examples for What is the I/O Information tab in the
MHI? • 147 Controller Diagnostics window? • 195
What are I/O access path examples for What is the IP address of a Controller? • 35
Modbus? • 155 What is the Point Details tab in the
What are I/O access path examples for RTP Controller Diagnostics window? • 200
I/O? • 170 What is the process for planning the I/O for
What are I/O access path examples for your system? • 10
Toshiba? • 175 What is the Refresh function for the
What are the Allen-Bradley DF-1 commands Controller Diagnostics window? • 202
supported by Ovation? • 100 What is the Sheet Information tab in the
What are the guidelines for positioning I/O Controller Diagnostics window? • 201
modules in cabinets? • 21 What is the Software Versions tab in the
What are the I/O Interface module status Controller Diagnostics window? • 199
LEDs for the OCR400 Controller? • 29 What procedures are needed after
What are the OCR400 Controller features? • configuration changes to the Controller? •
3 31
What are the Ovation I/O module base What should a new Controller drop item
types? • 11 contain? • 37
What are the processor module status LEDs What types of I/O modules can an OCR400
for the OCR400 Controller? • 27 Controller support? • 23
What are the Restore mode engineering
limitations? • 52
What are the Restore mode functions? • 51
What are the Restore mode performance
issues? • 51
What are the Restore mode point
information issues? • 52
What are the software platforms that
Controller Diagnostics supports? • 184
What changes can you make to an I/O
device? • 23
What firmware can be downloaded to the I/O
modules through the Controller
Diagnostics window • 197
What is a Controller driver? • 57
What is a Foundation Fieldbus first
generation (Gateway) device? • 105
What is a relay output module base? • 11
What is a standard I/O module base? • 11
What is an Allen-Bradley driver? • 93
What is an Ovation I/O module address? •
15
What is automatic failover control? • 5
What is the addressing format for I/O
modules? • 15
What is the Control Task Information tab in
the Controller Diagnostics window? • 193
What is the Controller Diagnostics tool? •
183
What is the Controller Diagnostics Update
Backup function? • 192

OW331_54 203