Virtual Controller User Guide for Ovation 3.

5
OW350_57

Version 1
February 2013
Copyright Notice

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

The text, illustrations, charts, and examples included in this manual are intended solely to explain
TM
the use and application of the Ovation Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.

No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.

No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.

The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.

This manual is printed in the USA and is subject to change without notice.

Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.

Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA

E-Mail: Technical.Communications@Emerson.com
Web site: https://www.ovationusers.com
 Contents

1 Introduction to Ovation Virtual Controllers 1

1.1 What is Ovation Virtual Controller simulation? .................................................................... 1
1.2 What is a Virtual Controller? ............................................................................................... 2
1.3 What are the Virtual Controller commands? ....................................................................... 2
1.4 What is a Virtual Controller Host? ....................................................................................... 3
1.5 Who uses Ovation Virtual Controllers? ............................................................................... 4
1.6 Why use Virtual Controllers?............................................................................................... 5
1.7 What is the operation of the Virtual Controller? .................................................................. 6
1.8 Virtual Controller terminology .............................................................................................. 6
1.9 What are the architecture types of Ovation Virtual Controllers? ......................................... 7
1.9.1 What is the Virtual Controller single-machine architecture? .................................. 8
1.9.2 What is the Virtual Controller networked architecture? .......................................... 9

2 Requirements for Ovation Virtual Controllers 11

2.1 What are the requirements for Ovation Virtual Controllers? ............................................. 11
2.2 What are the hardware requirements for the Ovation Virtual Controller host? ................. 11
2.3 What are the software requirements for the Ovation Virtual Controller host? .................. 12
2.4 What are the licensing requirements for Ovation Virtual Controllers? .............................. 12

3 Licensing Ovation Virtual Controllers 13

3.1 General licensing information............................................................................................ 14
3.2 What are the Virtual Controller license types? .................................................................. 15
3.2.1 What is needed to license the Virtual Controller Host? ....................................... 15
3.2.2 What is needed to license the Virtual Controller? ................................................ 15

4 Configuring Ovation Virtual Controllers 17

4.1 Loading the Virtual Controller Host with Virtual Controller software ................................. 17
4.1.1 To add a new Virtual Controller host .................................................................... 17
4.1.2 New Drops dialog box fields and descriptions ..................................................... 20
4.1.3 To add a new Ovation Virtual Controller .............................................................. 22
4.2 Virtual Controller software configuration ........................................................................... 27
4.2.1 To install driver services ....................................................................................... 28
4.2.2 Network configuration .......................................................................................... 28
4.2.3 To configure the bridge ........................................................................................ 28
4.2.4 To configure the Developer Studio ...................................................................... 29

OW350_57 i
Table of Contents

5 Programming and using Ovation Virtual Controllers 31

5.1 What is needed to program and use Virtual Controllers? ................................................. 31
5.2 Building control in Virtual Controllers ................................................................................ 31
5.3 Simulating control in Virtual Controllers ............................................................................ 32

6 Using the Virtual Controller Manager 33

6.1 What is the Virtual Controller Manager? ........................................................................... 33
6.1.1 To display the Virtual Controller Manager ............................................................ 34

Index 35

ii OW350_57
 S E C T I O N 1

1 Introduction to Ovation Virtual Controllers

IN THIS SECTION

What is Ovation Virtual Controller simulation? .................................................................... 1

What is a Virtual Controller? ............................................................................................... 2
What are the Virtual Controller commands? ....................................................................... 2
What is a Virtual Controller Host? ....................................................................................... 3
Who uses Ovation Virtual Controllers? ............................................................................... 4
Why use Virtual Controllers? ............................................................................................... 5
What is the operation of the Virtual Controller? .................................................................. 6
Virtual Controller terminology .............................................................................................. 6
What are the architecture types of Ovation Virtual Controllers? ......................................... 7

1.1 What is Ovation Virtual Controller simulation?

Ovation Virtual Controller simulation is a simulation of an actual Ovation Control system, except
that Virtual Controllers do not have actual plant control capabilities. Essentially, an Ovation Virtual
Controller is an Ovation Controller within a software package.

The Ovation Virtual Controller simulates the processes of your plant's control system. Virtual
Controllers emulate plant conditions with full modeling capabilities but with less hardware
requirements than standard Ovation control systems.

Ovation Virtual Controllers operate within a Windows operating system under the Wind River
VxWorks simulator. Virtual Controllers perform identically to actual Ovation Controllers. The
difference between the operation of actual Ovation Controllers and Virtual Controllers is that
Virtual Controllers do not have I/O interface capability; therefore, they cannot connect and
perform actual control functions.

Simulation of advanced control systems plays an important role in reducing time, cost, and risk in
plant operations. Since Ovation Virtual Controllers provide an exact simulation of your Ovation
control system, they allow operators and engineers to evaluate and analyze plant conditions
without interrupting the day-to-day operation of the plant.

OW350_57 1
1.2 What is a Virtual Controller?

1.2 What is a Virtual Controller?

A Virtual Controller is a software representation of a real Ovation Controller, but no Controller

hardware is required.

Virtual Controllers have all the same functionality as real Controllers but do not actually connect to
the plant I/O. A Virtual Controller replicates the operation of an actual Ovation Controller and
provides an identical representation of an actual Ovation Controller.

A Virtual Controller is:

 A software version of an Ovation Controller.
 A replica of a real or actual Ovation Controller in a software package.
 Actual Ovation Controller software, running under the Wind River VxWorks simulator.
Virtual Controllers execute under the control and guidance of a Virtual Controller Host software
package.

The operator interface to an Ovation Virtual Controller is identical to the operator interface of
actual Ovation Controllers.

For more details on the Virtual Controller, refer to Virtual Controller User Guide for Ovation 3.5.

1.3 What are the Virtual Controller command s?

The Virtual Controller Host software package has a user interface which allows Virtual Controllers
to be managed and to operate in a PC environment. Available commands include the following:
 Run
Begins Controller scan execution. Virtual Controllers execute with real-time speeds, similar to
real or actual Controller standards of one scan every second. When running simulation in real
time, the Virtual Controller software ensures that the perceived performance is not faster or
slower than real time.
 Freeze
Suspends scan execution. This state causes all Virtual Controllers and their associated
models to stop execution. When Virtual Controllers are in this state, they remain frozen until
the operator takes action to change the state.
 Save
Takes a snapshot or image of the Virtual Controller's relevant data, such as the Controller's
current operating state of all models and control schemes. The following information is saved
for each Virtual Controller:
 Local Memory.
 Network Shared Memory.
 All I/O tables.
 Load
Restores a previously saved image of the Virtual Controller. Loading a previously saved state
of the Virtual Controller causes the initial conditions to be in the exact state as when the save
occurred.

2 OW350_57
 1.4 What is a Virtual Controller Host?

1.4 What is a Virtual Controller Host?

The Ovation Virtual Controller Host software package permits Virtual Controllers to run in the PC
environment. The Virtual Controller Host manages Virtual Controllers and coordinates their
operation. The Host machine can coordinate the activity of one or several Virtual Controllers.

Host machines can be any Windows HMI (Human Machine Interface) that has the required
amount of memory. Hosts can handle up to 20 Virtual Controllers on each Windows PC,
depending on the amount of memory installed on your computer.

The Virtual Controller Host has the capability to stop and start Virtual Controllers and support their
control execution timing and Ovation network interface. Therefore, the simulation of an Ovation
Controller is accomplished exclusively by a Virtual Controller.

A Virtual Controller Host is:

 A Windows-based PC, licensed as an Ovation Windows HMI.
 Any HMI designated as a Virtual Controller Host must be equipped with sufficient memory:
 4GB Memory.
 An HMI could be one of the following:
 Operator Station.
 Engineering Station.
 Database Server.
 Base Station.

The functions of Virtual Controller Hosts are:

 To house Virtual Controllers.
 To enable Virtual Controllers to operate.
 To coordinate the operation of Virtual Controllers.

OW350_57 3
1.5 Who uses Ovation Virtual Controllers?

1.5 Who uses Ovation Virtual Controllers?

Virtual Controller technology can be used by any Ovation control system user. The use of Ovation
Virtual Controllers on your control system depends on how you would like to apply virtual
technology.

As a control system operator, you need to know what to expect when operating your Ovation
control system and how to react to conditions and situations as they occur. Every Ovation
simulated system with Virtual Controllers is designed to imitate your plant control system and
provide operators and technicians with an opportunity to learn how to react to problems if they
arise.

Virtual Controllers can be used in various ways. For example, Emerson uses Virtual Controllers to
build simulator systems, plant modeling, operator training, event handling, and proof testing of
new control schemes and control strategies. You may also want to use your Virtual Controllers for
the same type of applications, or you may choose to design your own custom strategies for your
control system. Typically, the following plant personnel use Virtual Controllers:
 Plant technicians
Virtual Controllers provide many advantages for technicians during system testing and
startup. Using Virtual Controllers minimizes the amount of down time plant technicians
experience during system changes and system set up. In addition, technicians gain
knowledge and experience of how Ovation control systems operate.
 Control system operators
Control room operators use Virtual Controllers to become more familiar with the Ovation
System and gain confidence and understanding of the function of an Ovation system.
 Plant engineers
Plant engineers use simulator systems with Virtual Controllers to test and verify
engineering upgrades and to help plan future changes. Engineers also use Virtual
Controllers for analysis of plant operations.
Virtual Controllers provide an exact imitation of the plant control system, allowing
engineers to use Virtual Controllers to evaluate almost any aspect of the control system
and plant performance. Engineers can test control strategies on Virtual Controllers prior
to actual implementation.
 Trainers
Instructors use Virtual Controller simulation in training programs to improve the skills of
operators, engineers, and technicians by simulating plant conditions. The experience
gained through training helps reduce start time and minimizes operator error.

4 OW350_57
 1.6 Why use Virtual Controllers?

1.6 Why use Virtual Controllers?

Simulation using Ovation Virtual Controllers can improve plant efficiency and save your
organization time and money. There are many applications for using Virtual Controllers.

When used as a training tool, Ovation Virtual Controllers teach operators to fully understand plant
control prior to plant startup. Operators have an opportunity to practice on a simulated control
system without the concern of tripping or upsetting the operation of the plant. Operators develop a
thorough understanding of how their actions impact plant operation and overall plant efficiency by
operating control equipment identical to the actual plant control system.

When system changes or equipment upgrades are planned, operators use Ovation Virtual
Controllers to become more proficient with their skills by observing system reactions in various
conditions. The overall result of this type of custom training is an operator who has an in-depth
knowledge of plant equipment and plant processes before they begin actual plant control.

Virtual Controllers act as powerful diagnostic tools for engineering analysis. By simulating various
plant operating conditions, engineers can quickly identify areas in need of improvement.
Engineers can use Virtual Controllers to develop and re-engineer control system logic, allowing
them to observe the effect of plant changes prior to implementation without affecting the normal
day-to-day operation of the plant.

Simulation using Virtual Controllers provides an interactive method for training new operators and
can be used as a tool to solve plant problems. Ovation Virtual Controllers allow you to practice
operating your control system before you actually begin real plant control. As you become more
familiar with Ovation, you will want to use Virtual Controllers to aid in future decisions regarding
plant operations.

Ovation Virtual Controllers are designed for the following reasons:

 Offer customers a portable simulation system.
 Provide a simulation system with less hardware and hardware expense.
 Provide full simulation functionality with greater flexibility.
 Improve performance of plant technicians and operators through training.
 Provide a thorough engineering analysis tool.
 Increase cost savings through operator efficiency.
 Reduce down time and risk of plant tripping.
 Improve efficiency and reduce cost of plant startup and shutdown.
 Enhance operator's ability to identify and correct plant upset.
 Decrease system and equipment failures.

OW350_57 5
1.7 What is the operation of the Virtual Controller?

1.7 What is the operation of the Virtual Controller?

The Ovation Virtual Controller software package replicates the operation and the functionality of a
real or actual Ovation Controller. Virtual Controller software offers all standard VxWorks Ovation
Controller capabilities plus the benefit of operating in a Microsoft Windows operating environment.

Ovation Virtual Controller Hosts are loaded with Virtual Controller software on a Windows-based
PC. The Host Controller permits Virtual Controllers to operate on desktop workstations thus
providing portability for use throughout the facility. One Virtual Controller for every actual Ovation
Controller is necessary to fully simulate your control system.

An Ovation Simulator using Virtual Controller technology replicates a full scope simulator. Each
unit's specific Controller configuration and graphics are loaded along with the plant's model to
make the desktops replicate the plant's controls exactly.

Virtual Controllers use the same internal processes as actual Ovation Controllers. The following
processes are identical to actual Ovation control systems, except Virtual Controllers run on a
Windows PC:
 Point origination.
 Point naming and alarming.
 Control sheet execution.
 Control areas and timing.
 Algorithm execution.
Plant operators use standard Ovation configuration tools to access, configure, and load Virtual
Controllers. The configuration files for each Controller are maintained and available for
modification on the Simulator Database Server.

A user interface on the Ovation Virtual Controller Host allows the operator to control the operation
of individual Virtual Controllers.

1.8 Virtual Controller terminology

Virtual Controller terminology

TERM DESCRIPTION

License file Required to run the VxWorks simulation.

Model A recreation of a computer design. A model is the software representing the operation of the
physical plant.
Ovation Plant A collection of Ovation Controllers with I/O and HMI drops in a network configured according to
Control System the requirements for control of a specific plant.
Ovation Virtual Software-based Controllers executing in a Windows operating system are configurable using
Controller the same tools as the Ovation Controller. Virtual Controllers execute all of the Controller
functionality including the same algorithm sets as the Ovation Controller but do not require any
of the Ovation I/O hardware interfaces.

Ovation Virtual An Ovation personal computer running on a Windows operating system. A Host is capable of
Controller Host supporting 1 to 20 Virtual Controllers, providing Virtual Controller coordination.

6 OW350_57
 1.9 What are the architecture types of Ovation Virtual Controllers?

TERM DESCRIPTION

Ovation An Ovation SimController is a Controller in which the I/O interface hardware and software driver
SimController can be used with, or replaced by, a Simulation I/O software driver. Use of the Simulation I/O
driver allows points which are normally accessed by their hardware addresses to be re-directed
to the Ovation network. A modeling function on the network provides the data rather than
accessing data through the field I/O interface.
Ovation Virtual A combination of the attributes of the Ovation SimController with Simulated I/O driver but
SimController running on a Windows operating system.
Ovation A collection of Ovation drops that provides the same functionality as an Ovation plant control
Simulator system without using real Ovation I/O. The addition of a plant simulation model replaces the I/O
functions.
Ovation An Ovation drop type which provides the capability to define the Ovation database and
Database engineering capabilities for the complete system.
Server
Ovation HMI An Ovation drop type which provides operator interface functionality. HMI's can be any Ovation
Operator Station. An Ovation HMI with sufficient memory can perform as a Virtual Controller
Host.
Real or Actual A Controller having the capability to connect to the actual plant I/O and perform plant control.
Controller Actual Controllers run on the VxWorks operating system.

1.9 What are the architecture types of Ovation Virtual Controllers?

Ovation Virtual Controllers offer a choice of two configurations:

 Single-machine architecture.
 Networked architecture.
The Ovation Virtual Controller architecture executes standard Ovation Controller functionality on a
Microsoft Windows-based workstation, referred to as the Ovation Virtual Controller Host. Virtual
Controllers reside on the host machine and identically simulate the functionality of actual Ovation
Controllers and the plant control system network. Therefore, to fully simulate the entire control
system, one Virtual Controller is required for each real Controller installed on your system.

An algorithm library, built from the Ovation Controller algorithm library, provides the tools
necessary to build plant responses.

OW350_57 7
1.9 What are the architecture types of Ovation Virtual Controllers?

1.9.1 What is the Virtual Controller single-machine architecture?

Single machine architecture mimics the behavior of the Ovation control system on a single
Windows-based PC. The single-machine architecture can consist of up to 20 Ovation Virtual
Controllers and a combination of Operator or Engineer Stations, Database Server, or Base
Station functions executing on the same Windows-based machine.

Note: The number of Virtual Controllers that can be run is dependent on the processor and
amount of installed memory.

The single machine architecture can be used for offline control building, database testing, and
control strategies without requiring an actual Ovation control system. Ovation Virtual Controllers
use the same source code that actual Controllers use.

The following figure illustrates the Ovation single-machine architecture:

Figure 1: Single Machine Architecture Illustration

8 OW350_57
 1.9 What are the architecture types of Ovation Virtual Controllers?

1.9.2 What is the Virtual Controller networked architecture?

The networked system configuration allows for a number of actual Ovation drops to exist with
Ovation Virtual Controllers on an actual Ovation Fast Ethernet network. Virtual Controllers can be
hosted on a single host machine or can be distributed across multiple machines.

Networked architecture includes the Ovation Virtual Controller Host with Virtual Controllers along
with other Ovation drops, such as Ovation Operator, Engineer, Database workstations, and
Controllers, all connected to an Ovation network.

The networked configuration allows any type of Ovation drop to coexist on the network with
Virtual Controllers, including actual VxWorks-based Controllers. Networked configurations are
designed to accommodate multiple workstations as well as allow for system expansion while
reducing the amount of hardware.

The following figure illustrates an Ovation Networked system:

Figure 2: Networked Architecture Illustration

OW350_57 9
 S E C T I O N 2

2 Requirements for Ovation Virtual Controllers

IN THIS SECTION

What are the requirements for Ovation Virtual Controllers? ............................................. 11

What are the hardware requirements for the Ovation Virtual Controller host? ................. 11
What are the software requirements for the Ovation Virtual Controller host? .................. 12
What are the licensing requirements for Ovation Virtual Controllers? .............................. 12

2.1 What are the requirements for Ovation Virtual Controllers?

A Virtual Controller Host is a Windows-based PC running Virtual Controller software. A minimum

of one Virtual Controller must be loaded on the Virtual Controller Host. You can load a maximum
of 20 Virtual Controllers on a Virtual Controller Host before a second host is needed.

Note: The number of Virtual Controllers that can be run is dependent on the processor and
amount of installed memory.

The host software has the ability to coexist with other Ovation MMIs. Host machines can be any
HMI listed below:
 Operator Station
 Engineering Station
 Database Server
 Base Station
Each Ovation drop type, including the host and up to 20 Virtual Controllers, have unique IP
addresses. Therefore, each drop has its own individual drop identity on the Ovation network.

2.2 What are the hardware requirements for the Ovation Virtual
Controller host?

The minimum hardware requirement to operate one Virtual Controller Host is:
 A Windows-based PC (Windows 7 / Server 2008 operating system)
 4GB Memory
 3.1 GHz Pentium 4
The amount of hardware necessary for more than one Virtual Controller depends on the size of
your control system and the amount of available memory on the Virtual Controller Host PC.

OW350_57 11
2.3 What are the software requirements for the Ovation Virtual Controller host?

2.3 What are the software requirements for the Ovation Virtual
Controller host?

The minimum requirements are necessary for software installation of a Virtual Controller:
 One Windows-based PC (Windows 7 / Server 2008 operating system)
 4GB Memory
 Standard Ovation software DVD

2.4 What are the licensing requirements for Ovation Virtual

Controllers?

Two licenses are required for Virtual Controllers.

 Virtual Controller Host software license (includes required license file).
 Virtual Controller software license.

12 OW350_57
 S E C T I O N 3

3 Licensing Ovation Virtual Controllers

IN THIS SECTION

General licensing information ............................................................................................ 14

What are the Virtual Controller license types? .................................................................. 15

OW350_57 13
3.1 General licensing information

3.1 General licensing information

When planning to install Ovation software on your control system, make sure you have the proper
key codes or license files readily available prior to installation. Licenses are available from
Software Licensing or from your project representative, project engineer, after market
representative, or field service engineer. In the event of an emergency, a reload, or other
licensing concerns, call 800-445-9723.

When calling for licensing help, have your name, project or company name, and your installation
needs available. Your call receives a response as soon as possible.

The License folder is only located at the System level in the Ovation Developer Studio. When the
License folder is opened, the Ovation License Manager is started. The Ovation Database Server
is also defined as a System License Server.

Licenses are stored on the License Server and manage the access to the Ovation Developer
Studio. As you log into the Studio, licenses are retrieved from the License Server. When a license
is accessed, that license becomes locked so no other user can access it. Licenses remain locked
as long as they are in use. If all licenses are in use, you must wait until a license becomes
available.

There are two basic types of licenses in Ovation:

 Fixed, or hard licenses.
 Floating licenses.
Fixed licenses provide limitations on the size of an Ovation System, such as the number of certain
types of drops in the system. The Developer Studio prevents you from adding or configuring any
Ovation drops when the licensed limit has been reached.

Note: The Base station drop uses the Operator Station drop licenses. Licenses are also
required for remote networks and/or Data Servers.

Floating licenses limit the number of each type of Ovation engineering applications that can be
executed concurrently on the Ovation system. The Ovation engineering applications that are
bound by floating licenses are:
 Ovation Developer Studio.
 Ovation Control Builder.
 Ovation Graphics Builder.
The License Manager displays the details of the Ovation license. For example, it reports the
quantity of each Ovation drop type, remote network, and Data Server that can be configured and
utilized. For floating licenses, the License Manager reports the total number of users who may
simultaneously execute an Ovation engineering application, as well as by whom the applications
are being executed, such as User: administrator@host:drop 210.

Note: If your system was initially loaded at the Emerson plant, the license codes that were used
for the load procedures are provided in your Software and Licensing Kit binder. However, if you
are upgrading the Windows Operating System, a new Microsoft product key code is required.

14 OW350_57
 3.2 What are the Virtual Controller license types?

3.2 What are the Virtual Controller license types?

Two license types are associated with Virtual Controllers:

 Virtual Controller Host license (includes required license file).
 Virtual Controller license.
Each host requires a software license. Each Virtual Controller added to the host machine also
requires a software license. Both licenses are fixed licenses.

3.2.1 What is needed to license the Virtual Controller Host?

Before a Virtual Controller can be installed, a Virtual Controller Host is required. Hosts are
licensed to accommodate up to 20 Virtual Controllers on each host machine. In addition to the
Host license, each Virtual Controller residing on the host also requires a license to operate.

Hosts are configured and maintained using standard Ovation Developer Studio tools. All Ovation
drops included within the Host machine have a unique drop IP address giving them individual
drop identity on the Ovation network. Software coordinators start and control operation of all
Virtual Controllers residing on the Host machine.

A license file is necessary for each Virtual Controller Host and is also required to run the VxWorks
simulation. Software Licensing will supply you with a license file upon license request.

Additional information is required for Software Licensing to generate this license. When
requesting a Virtual Controller Host license, the following information is required:
 Computer name of each Virtual Controller Host.
 Disk volume serial number of primary disk.

To retrieve the disk serial number

1. Open a Windows command prompt.
2. Enter vol and select Enter.
3. The following information will be returned:
 Volume in drive C in HP.
 Volume Serial Number is 3E63-B641 (this is the number required by Software Licensing).

Note: Configuring a Virtual Controller can be done without a license file; however, you cannot
run a Virtual Controller without the required license file.

3.2.2 What is needed to license the Virtual Controller?

Each Virtual Controller loaded on your system requires a license to become active. A maximum of
20 Virtual Controllers can be licensed to each host. Virtual Controllers reside within host
machines and are configured and loaded using standard Ovation Developer Studio tools.

The configuration files for each Virtual Controller are maintained and available for modification on
the system Database Server.

OW350_57 15
 S E C T I O N 4

4 Configuring Ovation Virtual Controllers

IN THIS SECTION

Loading the Virtual Controller Host with Virtual Controller software ................................. 17
Virtual Controller software configuration ........................................................................... 27

4.1 Loading the Virtual Controller Host w ith Virtual Controller

softw are

All Ovation 3.0 and later systems are programmed with the Virtual Controller option. Utilization of
the Virtual Controller option is accomplished by activation of the Virtual Controller software. The
process of activating and loading Virtual Controller software begins with obtaining a software
license for both the Virtual Controller Host and for each Virtual Controller.

Licenses can be obtained through the standard Emerson licensing procedures listed in the
Developer Studio. Once licensed, Virtual Controller software can be loaded. Refer to: Licensing
Ovation Virtual Controllers (see page 13).

To activate Virtual Controller software:

 Obtain a license for the Virtual Controller Host.
This includes a Wind River VxWorks Simulator license. Refer to: What is needed to license
the Virtual Controller host? (see page 15).
 Obtain a license for each Virtual Controller Host or Advanced Virtual Controller.
Configuring a new Virtual Controller Host is necessary before installation of new Virtual
Controllers.

The following is an overview of the Virtual Controller configuration procedures:

1. Add and configure the Virtual Controller Host in the Developer Studio.
2. Add and configure each Virtual Controller and assign each to a Virtual Controller Host.
3. Download each Virtual Controller Host.

Note: You must configure the drop type as a Virtual Controller Host in order to load and
configure Virtual Controller software.

4.1.1 To add a new Virtual Controller Host

1. Access the Ovation Developer Studio, refer to the Ovation Developer Studio User Guide for
more information:
2. Use the system tree to navigate to the Drops folder.
Systems > Networks > Units > Drops

OW350_57 17
4.1 Loading the Virtual Controller Host with Virtual Controller software

3. Right-click the Drops folder. Select Insert New from the pop-up menu.

Figure 3: Developer Studio system tree

18 OW350_57
 4.1 Loading the Virtual Controller Host with Virtual Controller software

4. The Insert New Drops Wizard window appears.

Figure 4: Insert New Drops Wizard

5. Select Virtual Controller Host from the drop-down menu to designate the PC as the Host
Controller. Enter the drop type and drop ID number in the applicable entry fields. Enter a
partner ID applicable. Click Finish.

Note: All Ovation 3.0 and later control systems have Virtual Controller capabilities. Virtual
Controllers must be licensed to become active. Once licensed, Virtual Controller Hosts are
configured by selecting Virtual Controller Host from the drop down-menu. This action does not
prevent the drop type from using other functionality previously loaded on the drop.

Hosts can be located on any Operator Station, Sim Operator Station, Base Station, Engineering
Station, or Database Server.

Selecting a Virtual Controller Host as a drop type adds this host into the list of SimStations
available for Virtual or SimController.

Insert New Drops Wizard window fields

FIELD DESCRIPTION

Drop Id New Virtual Controller drop number. Valid entries are 1-254.

Partner Id Identifies the drop ID of the partner drop.

Drop Type Select Virtual Controller Host.

6. The New Drops dialog box appears. Enter the drop type, drop ID, computer name, and the
Ovation network IP address in the appropriate fields. Make desired selections in all other
fields or use the preset default selections. After all information is entered, click Ok.

OW350_57 19
4.1 Loading the Virtual Controller Host with Virtual Controller software

4.1.2 New Drops dialog box fields and descriptions

The following figure illustrates the dialog boxes and fields for the New Drops window:

Figure 5: New Drops dialog box fields

New Drops dialog box field descriptions

FIELD ATTRIBUTE VALUE DESCRIPTION

Drop Type Drop-down menu with drop type selections (Virtual Controller Host).

Maximum Point Limit Selects the maximum number of points that the SimController can be configured
to monitor.
Normal handles up to 32,000 points.
Expanded handles up to 48,000 points.

20 OW350_57
 4.1 Loading the Virtual Controller Host with Virtual Controller software

FIELD ATTRIBUTE VALUE DESCRIPTION

Local Data Server Read-only field which tells if the drop has been defined as a local data server (No,
Yes).
Local Alarm Collector Read-only field which tells if the drop has been defined as a local alarm collector
(No, Primary, Partner, Both). See the Ovation Multiple Networks User Guide for
more information on alarm collectors.
Primary

Drop ID New Virtual Controller host drop number. Valid entries are 1-254.

Computer Name Name of a new machine or computer.

Computer Sid ID for domain name server. Read-only field added by the system.

Computer Sid (cont.) ID for domain name server. Read-only field added by the system.

Ovation Network IP Address The Internet Protocol (IP) address for a drop is typically assigned by the system
administrator. The IP address consists of four groups of decimal numbers and the
format is:
xxx.xxx.xxx.xxx
If the network is isolated from other networks (such as, the Internet), the IP
address can be any valid range.
Ovation Network Ethers The format for the hardware address (for Windows machines only) is:
Address
xx:xx:xx:xx:xx:xx (where the last four numbers (xx:xx) are typically located on a
label on the NIC).
If the hardware address cannot be located on the NIC, see To Determine NIC
Address in the Simulation User Guide for Ovation.
Partner

Partner ID This field identifies the drop ID of the partner drop. Enter only if applicable.

Virtual Controller Host

Port TCP port used for communication to Virtual Controllers (Default - 6010).

Master Virtual Controller Host Pull-down list of all configured Virtual Controller Hosts. One host is designated as
the Master Host to coordinate timing between all other hosts on the Network.
Necessary on systems with more than one host.
Master Virtual Controller Host TCP port used for communication to Virtual Controllers (Default - 6001).
Port
Virtual Controller Host Virtual Controller Host Drop name (DropXXX).
Virtual Controller 1

Virtual Controller at Index 1 Read-only field, specifies drop name configuration for this index.

Port TCP port used for communication to Virtual Controllers (Default - 6001).
Virtual Controller 2

Virtual Controller at Index 2 - Read-only field, specifies drop name configuration for this index.
20

OW350_57 21
4.1 Loading the Virtual Controller Host with Virtual Controller software

FIELD ATTRIBUTE VALUE DESCRIPTION

Port TCP port used for communication to Virtual Controllers (Default - 6001).

4.1.3 To add a new Ovation Virtual Controller

1. Launch the Ovation Developer Studio by double-clicking the Ovation Developer Studio icon
located on the Windows desktop.
2. Select the Hardware bar to display the system tree within the Ovation Developer Studio
overview window.
3. Use the system tree to navigate to the Drops folder:
Systems > Networks > Units > Drops

22 OW350_57
 4.1 Loading the Virtual Controller Host with Virtual Controller software

4. Right-click the Drop item. Select Insert New from the pop-up menu.

Figure 6: Developer Studio system tree

OW350_57 23
4.1 Loading the Virtual Controller Host with Virtual Controller software

5. The Insert New Drops Wizard window appears. From the drop-down menu, select Virtual
Controller or Advanced Virtual Controller to enable the Virtual Controller software.

Figure 7: Insert New Drops Wizard

6. Enter the Drop ID and the Partner ID, if applicable. Select Finish.

Insert new drops wizard window fields

FIELD DESCRIPTION

Drop Id Drop number of the new drop. Valid entries are 1-254.

Partner Id Identifies the drop ID of the partner drop. Enter only if applicable.
Drop Type Select Virtual Controller.

24 OW350_57
 4.1 Loading the Virtual Controller Host with Virtual Controller software

7. The New Drops dialog box appears. Enter the drop type, drop ID, computer name, and the
network IP address in the appropriate fields. Make the desired selections in all other fields or
use the default selections. After all information is entered, click Ok.

Figure 8: New Drops dialog box

New Drops dialog box field descriptions

FIELD DESCRIPTION

Drop Type This procedure deals specifically with the Virtual Controller selection from the pull-down
menu.

OW350_57 25
4.1 Loading the Virtual Controller Host with Virtual Controller software

FIELD DESCRIPTION

Controller Type Choose the correct Controller type.

(OCR1100, OCR400)
Control Available when a primary and a partner Controller are inserted and allow both Controllers to
Synchronization be automatically synchronized.
You can choose whether to have information sent over a dedicated cable or over the
Ovation network by making one of the following selections:
Ovation 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 Network.
Maximum Point Selects the maximum number of points that the Controller can be configured to monitor.
Limit
Due to the way points are indexed, the actual point number is the maximum point count
minus 1.
Normal handles up to 6000 points. (Actual limit = 5,999)
Expanded handles up to 16,000 points. (Actual limit = 15,999)
32000 handles up to 32,000 points. (Actual limit = 31,999)
Note: Additional shared memory may be required to accommodate additional points.
Radius Server Not used for Virtual Controllers.
Primary & When the primary/partner configuration is not used, no information input is required in the
Partner Sections partner section.
Drop ID Drop number of the originating drop of the point.
(1-254)
Ovation Network The IP address consists of four groups of decimal numbers and the format is:
IP Address
xxx.xxx.xxx.xxx
The System Administrator typically assigns these addresses. They can also be assigned to
be any valid range if the network is isolated from other networks (such as the Internet).
Ovation Network The format for the hardware address is:
Ethers Address
xx:xx:xx:xx:xx:xx (where the last four numbers (xx:xx) are typically located on a label on
the NIC).
If the hardware address cannot be located on the NIC, see Determining NIC Addresses in
the applicable Ovation Controller User Guide.
Ovation Highway Ethernet interface that connects the Controller to the Ovation Network.
Interface Mode
Ovation Highway Type of NIC card connection.
Connection
(Single, Dual)
NIC Interface Automatically selected by the system. Name of the physical port that the Ethernet cable is
connected to.
(N1) - (fei2) - used for third-party Ethernet interfaces.
(N2) - (fei0) - used for Single Ethernet.
(N3) - (fei1) - used for Dual or third-party Ethernet interfaces.
(N4) - (fei3) - used for dedicated control synchronization cable or third-party Ethernet
interfaces).

26 OW350_57
 4.2 Virtual Controller software configuration

FIELD DESCRIPTION

Backup NIC Automatically selected by the system.

Interface
(Available if a
(N1 - N4) - (fei0 - fei4)
backup NIC is
used.)
Control The Controller software is configured to automatically run control synchronization of
Synchronization redundant Controllers over the network.
Interface
For a redundant Virtual Controller, this is always over the network.
Restore Read only field for catastrophic failure.
Restore Mode (Enable, Disable)
(Appears if Online
Controller Restore
Mode is selected.)
Virtual Controller Drop-down list of Host machines.
Host
Virtual Controller Drop-down list of available indexes.
Index
Partner Virtual Drop-down list of Partner Host machines.
Controller Host
Partner Virtual Drop-down list of available indexes on partner machines.
Controller Index
Failure Tied to Checked by default if Redundant Virtual Controller Host.
Host

4.2 Virtual Controller softw are configuration

Prior to installation, check the following items:

 OHI (Ovation Highway Interface)
CAUTION! OHI (Ovation Highway Interface) software is not compatible with the software
necessary for the Virtual Controller Host. If OHI is installed the software must be removed.
 Network Switch configuration
Appropriate switch configuration is required to accommodate Virtual Controller Hosts. When
using the standard Ovation network switch configuration, the Virtual Controller Host port will
become disabled.

Continue software installation using the following procedures:

1. Install Driver services (see page 28).

2. Network connectivity (see page 28).
3. Configure the bridge (see page 28).
4. Configure the Developer Studio (see page 29).

OW350_57 27
4.2 Virtual Controller software configuration

4.2.1 To install driver services

1. Open a Command Tool using the following path:
Select Start > Run > type CMD in the dialog field and select <Enter>.
2. Enter cd C:\Ovation\OvationVirtual.
3. Enter wrtap32 (for 32-bit applications).
OR
Enter wrtap64 (for 64-bit applications).
4. Select <Enter>.

4.2.2 Network configuration

 For upgrading pre-Ovation Virtual Controller Hosts to Ovation 3.5 Virtual Controller
Hosts - The additional IP addresses of each Virtual Controller must be removed from the
NIC1 configuration. This is accessed by using the Advanced button in the Network
Configuration tool.
 For an upgrade to an existing Ovation 3.5 Virtual Controller Host - If the network bridge
already exists, remove the bridge first using the following procedure then continue with the
network configuration.
Use the following procedure to remove the bridge by using the Network Configuration tool:

1. Access the Network Configuration tool.

2. Select the Bridge.
3. Right-click and select properties.
4. De-select all Adapters in the list.
5. De-select the DDB protocol.
6. Select Bridge, then right-click and select Delete.
7. Select Yes when prompted.

Continue by using the following procedure.

1. Access the Network Configuration tool.

2. Create a bridge between the WRTap adapter and the Ovation NIC for 32-bit applications.
3. Create a bridge between the TAP-Win32 adapter and the Ovation NIC for 64-bit
applications.
4. Configure the bridge. See To configure the bridge (see page 28).

4.2.3 To configure the bridge

1. From the Network Configuration tool.
2. Control-click to select both the Ovation and the WRTap interfaces.
3. Right-click and select Bridge Connection.
4. Right-click Network Bridge and select Properties.
5. For TCP/IPV4 protocol, configure the bridge in the same way the local Ovation NIC1 is
configured with the following:

28 OW350_57
 4.2 Virtual Controller software configuration

 IP address
 netmask
 Default Gateway
 DNS Server
6. Select the DDB Protocol for the bridge.
7. If a warning displays, click Ok.
8. Ensure that the Ovation NIC1 is set to the top of the Adapter connection order in the Network
Configuration tool under Advanced > Advanced Settings.

Note: If the Advanced option is not visible, press the ALT key.

4.2.4 To configure the Developer Studio

1. Launch the Ovation Developer Studio by double-clicking the Windows desktop icon.
2. Configure the Virtual Controller Hosts and each Virtual Controller (If not already
configured see Loading the Virtual Controller Host with Virtual Controller software (see page
17).)
3. Download the Virtual Controller Host machine.
4. Reboot the Virtual Controller Host.

Note: If this is an upgrade to an existing Ovation 3.5 VCH, you can skip steps 5 through 10.

5. If this is a new installation: After reboot, you should have a request (or multiple requests
depending on the number of Virtual Controllers configured) for a license file. If you do not
already have a license file, you must request one.

Note: To obtain a license file, you must have the hostname and the disk volume serial
number of the host machine.

6. Open a command tool and type the following command:

vol
7. Select Enter.
8. Copy the license file to the machine.
9. Select the license file option in the license GUI, then navigate to, and select the license file.
You only need to do this for one of the GUIs if there are multiple.
10. Reboot the host machine. Upon reboot, the Virtual Controller(s) will be running.
11. Download and reboot the Virtual Controller(s).

OW350_57 29
 S E C T I O N 5

5 Programming and using Ovation Virtual Controllers

IN THIS SECTION

What is needed to program and use Virtual Controllers? ................................................. 31

Building control in Virtual Controllers ................................................................................ 31
Simulating control in Virtual Controllers ............................................................................ 32

5.1 What is needed to program and use Virtual Controllers?

Using a Virtual Controller is the same as using an actual Ovation Controller. All functionality of
Ovation Virtual Controllers is exactly the same as actual Ovation Controllers. Therefore, all of the
standard Ovation Developer Studio tools are used to configure and run Ovation Virtual
Controllers.

Information on the operation of Virtual Controllers is identical to the information for actual
Controllers; therefore, procedures to load, license, and run Virtual Controllers are all found in the
standard Ovation User Guides.

Depending on how you want to use your Virtual Controllers, additional programming may be
required. For example, building control and simulating control requires additional programming.

5.2 Building control in Virtual Controllers

The approach and procedure used to build control in Ovation Virtual Controllers is the same
approach and procedure used to build control on actual Ovation Controllers. Information on
control building is found in the Ovation Control Builder User Guide.

To understand the operation of Ovation Controllers, refer to the following Ovation user guides.
 Ovation Developer Studio User Guide.
 Ovation Controller User Guide.
 Ovation Control Builder User Guide.
 Ovation Software Installation Manual.
 Ovation Simulation User Guide.
Reference the Ovation Database User Guide for information on the following:
 Exporting the database from the plant Database Server.
 Importing the plant database into the Simulator Database Server.
Reference the Ovation Controller User Guide to perform the following:
 Download configurations.
 Drop load.

OW350_57 31
5.3 Simulating control in Virtual Controllers

5.3 Simulating control in Virtual Controllers

The approach and procedure used to simulate control on Ovation Virtual Controllers is the same
approach and procedure used to simulate control on actual Ovation Controllers.

Information and procedures to simulate control can be found in the following manuals:
 Ovation Simulation User Guide.
 Ovation Controller User Guide.

32 OW350_57
 S E C T I O N 6

6 Using the Virtual Controller Manager

IN THIS SECTION

What is the Virtual Controller Manager? ........................................................................... 33

6.1 What is the Virtual Controlle r Manager?

The Virtual Controller manager is a graphical user interface that displays information regarding
your Virtual Controller. The manager displays a list of the Virtual Controllers that are configured to
run on the local machine. It also displays a status for each of the Virtual Controllers. There is a
control section for each Virtual Controller that allows you to start or stop each Virtual Controller
individually.

The following figure illustrates the Ovation Controller Manager window:

Figure 9: Ovation Virtual Controller Manager

Virtual Controller Status descriptions

STATUS DESCRIPTION

Stopped Virtual Controller is not running.

Running Virtual Controller is running.
In Alarm Virtual Controller is running, in alarm state.

OW350_57 33
6.1 What is the Virtual Controller Manager?

STATUS DESCRIPTION

Failed Virtual Controller is in Fault mode.

Virtual Controller Control options

CONTROL DESCRIPTION

Stop Displayed when a Virtual Controller is running. This action will stop the Virtual
Controller.
Start Displayed when a Virtual Controller is stopped. This action will start the Virtual
Controller.

6.1.1 To display the Virtual Controller Manager

1. Open Windows explorer.
2. Navigate to C:\Ovation\Ovationbase.
3. Locate VCoordManager.exe.
4. Double-click VCoordManager.exe.

Figure 10: Ovation Virtual Controller Manager

You may want to create a shortcut on the desktop for easier access to this application.

Note: Do not copy the file directly to the desktop. This application must run in the
\ovation\ovationbase directory; therefore, make sure a shortcut is created to the application.

34 OW350_57
Index

Virtual Controllers usage • 5

B
W
Building control in Virtual Controllers • 31
What are the architecture types of Ovation
C Virtual Controllers? • 7
Configuring Ovation Virtual Controllers • 17 What are the hardware requirements for the
Copyright Notice • 2 Ovation Virtual Controller host? • 11
What are the licensing requirements for
G Ovation Virtual Controllers? • 12
What are the requirements for Ovation
General licensing information • 14
Virtual Controllers? • 11
I What are the software requirements for the
Ovation Virtual Controller host? • 12
Introduction to Ovation Virtual Controllers • 1 What are the Virtual Controller commands? •
L 2
What are the Virtual Controller license
Licensing Ovation Virtual Controllers • 13 types? • 15
Loading the Virtual Controller Host with What is a Virtual Controller Host? • 3
Virtual Controller software • 17 What is needed to license the Virtual
Controller Host? • 15
N What is needed to license the Virtual
Network configuration • 28 Controller? • 15
New Drops dialog box fields and What is needed to program and use Virtual
descriptions • 20 Controllers? • 31
What is Ovation Virtual Controller
P simulation? • 1
What is the operation of the Virtual
Programming and using Ovation Virtual
Controller? • 6
Controllers • 31
What is the Virtual Controller Manager? • 33
S What is the Virtual Controller networked
architecture? • 9
Simulating control in Virtual Controllers • 32 What is the Virtual Controller single-machine
T architecture? • 8
Who uses Ovation Virtual Controllers? • 4
To add a new Ovation Virtual Controller • 22
To add a new Virtual Controller host • 17
To configure the bridge • 28
To configure the Developer Studio • 29
To display the Virtual Controller Manager •
34
To install driver services • 28
U
Using the Virtual Controller Manager • 33
V
Virtual Controller definition • 2
Virtual Controller requirements • 11
Virtual Controller software configuration • 27
Virtual Controller terminology • 6

OW350_57 35