Professional Documents
Culture Documents
1
OW331_54
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
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
ii OW331_54
Table of Contents
OW331_54 iii
Table of Contents
iv OW331_54
Table of Contents
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
IN THIS SECTION
OW331_54 1
1.1 What is the Ovation OCR400 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.
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?
OW331_54 3
1.2 What are the OCR400 Controller features?
4 OW331_54
1.3 What is automatic failover control?
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.
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.
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
IN THIS SECTION
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.
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.
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?
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.
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
Note: Fan assemblies are not required for OCR 400 Controllers.
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.
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.
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.
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
IN THIS SECTION
A standard I/O base consists of two logical modules; and a relay output base has one logical
module.
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?
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?
Note: PCI Cards 1 and 2 for the OCR161, IOIC module for the OCR400.
OW331_54 17
3.1 What is an Ovation I/O module address?
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.
18 OW331_54
3.1 What is an Ovation I/O module address?
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.
OW331_54 19
3.1 What is an Ovation I/O module address?
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.
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
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.
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.
22 OW331_54
3.4 What types of I/O modules can an OCR400 Controller support?
Note: Refer to the Planning Your Ovation System manual for more information.)
After an I/O device has been created and loaded to the target drop, it may be necessary to make
changes.
OW331_54 23
3.5 What changes can you make to an I/O device?
For external networks modification information, see Ovation Multiple Networks User Guide.
24 OW331_54
S E C T I O N 4
IN THIS SECTION
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.
OW331_54 25
4.2 Monitoring OCR400 Controller Status
2. Confirm that the power cable is attached to the power plug connector.
3. If applicable, confirm that network cables are properly connected between the I/O Interface
module and any off-cabinet I/O devices.
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.
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.
OW331_54 27
4.2 Monitoring OCR400 Controller 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.
STATUS
OW331_54 29
4.2 Monitoring OCR400 Controller Status
STATUS
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?
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.
Note: The Download command must be performed any time configuration and software
changes have been made to a Controller drop.
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.)
OW331_54 31
4.3 What procedures are needed after configuration changes to the Controller?
SELECTION DESCRIPTION
Query Results The top left check box selects or deselects all of the files in the
preview list.
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?
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.
7. Click Yes to close the window and execute the reboot process.
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.)
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
IN THIS SECTION
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
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?
Configuration
Points
I/O Devices
Control Components
Control Tasks
Holding Registers
Note: Verify that the software is properly configured before starting the Ovation Controller.
FIELD DESCRIPTION
Drop Id This is the new Controller drop number. Valid entries are 1-254.
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.
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.
OW331_54 39
5.4 What should a new Controller drop item contain?
FIELD DESCRIPTION
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.
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).
40 OW331_54
5.4 What should a new Controller drop item contain?
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.
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.
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.
42 OW331_54
5.4 What should a new Controller drop item contain?
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.
Note: By default, the first two of a possible five Control Tasks are assigned to a new Controller
drop upon insertion.
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.
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
OW331_54 45
5.4 What should a new Controller drop item contain?
9. Repeat this procedure for each Control Task object before proceeding.
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.
OW331_54 47
5.4 What should a new Controller drop item contain?
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).
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.
5. Complete any desired changes to the default field values (see To Confirm Controller
Networking (Network Folder) (see page 46)).
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.
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.
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?
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).
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.
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?
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).
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.)
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.
OW331_54 53
5.10 What additional software configurations are needed for Controllers?
The OCR400 Controller can timestamp alarming to the 1 millisecond level when the Controller is
enabled for that function.
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.)
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.
56 OW331_54
S E C T I O N 6
IN THIS SECTION
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.
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.
The following is an overview of the steps used to create a local Ovation device or Q-Line device:
OW331_54 57
6.2 Configuring device drivers in the Controller
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.
58 OW331_54
S E C T I O N 7
IN THIS SECTION
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.
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.
OW331_54 59
7.2 To set Ovation device number parameters
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices).
Default = Ovation
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.
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.
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.
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.
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.
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.)
OW331_54 65
S E C T I O N 8
IN THIS SECTION
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.
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.
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.
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices).
Default = Ovation
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.
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
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
72 OW331_54
8.6 To insert a remote Ovation I/O module
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.
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.)
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
OW331_54 75
S E C T I O N 9
IN THIS SECTION
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.
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.
OW331_54 77
9.2 To set Ovation device number parameters
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices).
Default = Ovation
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.
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
80 OW331_54
9.4 To insert a new local Q-line crate
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.
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.
OW331_54 81
9.5 To insert a new local Q-line module
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
IN THIS SECTION
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.
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.
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.
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device. (Ovation, plus all third- party
devices).
Default = Ovation
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.
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
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.
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.
90 OW331_54
10.6 To insert a new remote Q-line module
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
92 OW331_54
S E C T I O N 11
IN THIS SECTION
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.
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.
OW331_54 93
11.3 To set Allen-Bradley 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.
94 OW331_54
11.3 To set Allen-Bradley device number parameters
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.
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
96 OW331_54
11.5 To configure Allen-Bradley points
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.
OW331_54 97
11.5 To configure Allen-Bradley points
7. Press the Finish button. The New <Point Type> Points dialog appears.
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).
FIELD DESCRIPTION
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 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?
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?
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:
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
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:
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.
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
IN THIS SECTION
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.
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.
OW331_54 103
12.3 To set Foundation Fieldbus (Gateway) 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.
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
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
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.
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 46: New Fieldbus Gateway dialog box - data update rates tab
FIELD DESCRIPTION
108 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device
FIELD DESCRIPTION
OW331_54 109
12.4 To insert a Foundation Fieldbus (Gateway) 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
110 OW331_54
12.4 To insert a Foundation Fieldbus (Gateway) device
OW331_54 111
12.4 To insert a Foundation Fieldbus (Gateway) device
Figure 50: New Fieldbus Devices dialog box - Plant Web Alerts tab
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
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:
INPUT Type
Additional Example:
HTRAISE:20 OUTPUT
where:
20 is the point offset supplied by MHI and is only needed for OUTPUT point types.
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)?
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
IN THIS SECTION
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.
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.
OW331_54 115
13.2 To set Foundation Fieldbus (I/O module) parameters
Note: You only have to perform this task once for each Controller that utilizes Foundation
Fieldbus.
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
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:
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.
OW331_54 119
13.5 To add a Foundation Fieldbus (I/O module) device
Note: You must perform this task for each Foundation Fieldbus I/O module that you add.
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:
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.
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
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.
Note: For each port that you want to use, you must open the port and assign it a node record.
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:
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
IN THIS SECTION
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.
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.
OW331_54 125
14.3 To insert a GE Genius device
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
126 OW331_54
14.3 To insert a GE Genius device
OW331_54 127
14.3 To insert a GE Genius device
13. Select finish, the New GE Genius Gateway dialog box appears.
FIELD DESCRIPTION
128 OW331_54
14.4 What are I/O access path examples for GE Genius?
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)
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:
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
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
IN THIS SECTION
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.
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.
OW331_54 131
15.2 To set GE Mark V/VI/Ve device number parameters
FIELD DESCRIPTION
I/O Driver Type Selects the I/O Driver for the selected device.
Default = 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.
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.
OW331_54 133
15.4 To configure GE Mark V/VI/Ve 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).
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.
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
FIELD DESCRIPTION
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.
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.
IO access path This field is active when third-party is selected for the I/O type.
GE Point Name Name of the GE point from where the data is being retrieved, for
example, L41BKRC_CPB
GE Node Index 1
136 OW331_54
15.4 To configure GE Mark V/VI/Ve points
FIELD DESCRIPTION
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:
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
GA GE Controller Name
PUSHBUTTON GE Type
1 GE Node Index
REAL GE Data Type
Valid GE Types
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?
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
IN THIS SECTION
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.
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.
OW331_54 141
16.2 To set MHI device number parameters
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
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).
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
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).
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.)
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).
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:
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?
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
IN THIS SECTION
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.
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.
OW331_54 147
17.2 To set Modbus device number parameters
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.
Note: The host names specified in the I/O access path are in the form PLC_1, PLC_2,
and so forth.
148 OW331_54
17.3 To insert a Modbus device
FIELD DESCRIPTION
OW331_54 149
17.4 To configure Modbus 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).
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.
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.
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
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
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.
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:
where:
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
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
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:
5. From the Value drop-down menu, select an unused number (for example, you might start
with 5, and continue numbering successive devices sequentially).
6. Click Finish. The New Device Numbers window appears:
7. From the I/O Driver Type drop-down menu, select PROFIBUS MODULE.
8. Click OK.
9. Use the Developer Studio system tree to navigate to I/O Devices:
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.
OW331_54 157
18.3 To add a module record point name
Note: You must perform this task for each Profibus I/O module that you add.
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:
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
Note: You must open each port that you want to use and assign it a node record.
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
IN THIS SECTION
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.
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.
OW331_54 163
19.2 To set RTP I/O device number parameters
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
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).
Note: The following figure shows an example of the Insert New Analog Points Wizard.
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.
FIELD DESCRIPTION
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
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:
1 Host Index
3 Device Address
4 Card Slot
2 Gain code.
168 OW331_54
S E C T I O N 20
IN THIS SECTION
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.
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.
OW331_54 169
20.2 To set Toshiba device number parameters
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
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).
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
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).
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).
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
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?
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
IN THIS SECTION
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.
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.
Figure 81: General Controller Driver Parameters tab - 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
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.
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.
OW331_54 179
S E C T I O N 22
IN THIS SECTION
OW331_54 181
22.2 What are the software platforms that Controller Diagnostics supports?
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?
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?
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.
OW331_54 185
22.3 What is the Controller Diagnostics window?
The Controller Diagnostics window contains a menu bar that provides three drop-down 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.
The Controller Diagnostics window provides a toolbar. Drag the mouse over the toolbar icons to
identify each icon.
186 OW331_54
22.4 What is the Controller List in the Controller Diagnostics window?
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.
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.
188 OW331_54
22.5 What is the Controller Overview panel in the Controller Diagnostics window?
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?
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
190 OW331_54
22.7 What is the Control Task Information tab in the Controller Diagnostics window?
The control task rate is set during Controller configuration in the Developer Studio (see page 44).
Control tasks 3, 4, and 5 are user configurable and you should select scan rates that are
appropriate for your system applications.
OW331_54 191
22.7 What is the Control Task Information tab in the Controller Diagnostics window?
FIELD DESCRIPTION
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?
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?
FIELD DESCRIPTION
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.
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.
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.
196 OW331_54
22.9 What is the Software Versions tab in the Controller Diagnostics window?
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).
OW331_54 197
22.10 What is the Point Details tab in the Controller Diagnostics window?
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?
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
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
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