Virtual Controller User Guide for Ovation 3.6.

0
OW360_57

Version 1
May 2016
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@EmersonProcess.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.1.1 Who uses Virtual Controller technology? ............................................................... 2
1.1.2 Why use Virtual Controllers?.................................................................................. 3
1.2 What is an Ovation Virtual Controller? ................................................................................ 4
1.3 What is an Ovation Virtual Controller Host? ....................................................................... 4
1.4 What are the Virtual Controller commands? ....................................................................... 5
1.5 What is the operation of the Virtual Controller? .................................................................. 6
1.6 Virtual Controller terminology .............................................................................................. 7
1.7 What are the architecture types of Ovation Virtual Controllers? ......................................... 8
1.7.1 What is the Virtual Controller single-machine architecture? .................................. 9
1.7.2 What is the Virtual Controller networked architecture? ........................................ 10

2 Hardware and software requirements for an Ovation Virtual

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

3 Licensing Ovation Virtual Controllers 13

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

4 Configuring Ovation Virtual Controllers 15

4.1 Accessing the Ovation Developer Studio .......................................................................... 15
4.2 Before starting your Virtual Controller software configuration .......................................... 16
4.3 Configuring network switch settings for Virtual Controllers ............................................... 16
4.3.1 What are different port types in Ovation networks? ............................................. 17
4.3.2 To configure an Ovation VCH drop port ............................................................... 18
4.4 Configuring a Virtual Controller software .......................................................................... 21
4.4.1 To create an environment variable for the Vxsim license .................................... 22
4.4.2 To install the WRTap network driver and setup the network bridge .................... 26
4.4.3 To configure the WRTap adapter maximum buffer number ................................ 29
4.4.4 To add a new Virtual Controller Host ................................................................... 33
4.4.5 To add a new Ovation Virtual Controller .............................................................. 38
4.4.6 To install virtual controller services ...................................................................... 44
4.4.7 To complete the Virtual Controller software configuration using the
Developer Studio .................................................................................................. 44

OW360_57 i
Table of Contents

4.5 Upgrading the Virtual Controller Hosts ............................................................................. 45

4.5.1 To remove the bridge ........................................................................................... 45
4.5.2 To create a bridge ................................................................................................ 46
4.5.3 To configure the bridge ........................................................................................ 46

5 Programming and using Ovation Virtual Controllers 47

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

6 Using the Virtual Controller Manager 49

6.1 What is the Virtual Controller Manager? ........................................................................... 49
6.1.1 To display the Virtual Controller Manager ............................................................ 51

Index 53

ii OW360_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 an Ovation Virtual Controller? ................................................................................ 4
What is an Ovation Virtual Controller Host? ....................................................................... 4
What are the Virtual Controller commands? ....................................................................... 5
What is the operation of the Virtual Controller? .................................................................. 6
Virtual Controller terminology .............................................................................................. 7
What are the architecture types of Ovation Virtual Controllers? ......................................... 8

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.

OW360_57 1
1.1 What is Ovation Virtual Controller simulation?

1.1.1 Who uses Virtual Controller technology?

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.

2 OW360_57
 1.1 What is Ovation Virtual Controller simulation?

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

OW360_57 3
1.2 What is an Ovation Virtual Controller?

1.2 What is an Ovation Virtual Controller?

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

1.3 What is an Ovation 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.

4 OW360_57
 1.4 What are the Virtual Controller commands?

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.

1.4 What are the Virtual Controller commands?

The Virtual Controller Host software package has a user interface that allows Virtual Controllers to
be managed and to operate in a PC environment. The 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.

OW360_57 5
1.5 What is the operation of the Virtual Controller?

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

6 OW360_57
 1.6 Virtual Controller terminology

1.6 Virtual Controller terminology

Virtual Controller terminology

TERM DESCRIPTION

DDB Dynamic data is a portion of a point record. It is broadcast on the Ovation Network in
Dynamic Data Blocks or DDBs.
License file Required to run the VxWorks simulation.
MAC address Media access control (MAC) address is an address used by network interfaces to
uniquely identify themselves on a network.
Model A recreation of a computer design. A model is the software representing the
operation of the physical plant.
Ovation An Ovation drop type that provides the capability to define the Ovation database and
Database engineering capabilities for the complete system.
Server
Ovation HMI An Ovation drop type that provides operator interface functionality. HMIs can be any
Ovation Operator Station. An Ovation HMI with sufficient memory can perform as a
Virtual Controller Host.
Ovation Plant A collection of Ovation Controllers with I/O and HMI drops in a network configured
Control System according to the requirements for control of a specific plant.
Ovation An Ovation SimController is a Controller in which the I/O interface hardware and
SimController software driver can be used with, or replaced by, a Simulation I/O software driver.
Use of the Simulation I/O driver allows points that 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 A collection of Ovation drops that provides the same functionality as an Ovation
Simulator plant control system without using real Ovation I/O. The addition of a plant
simulation model replaces the I/O functions.
Ovation Virtual Software-based Controllers executing in a Windows operating system are
Controller configurable using 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
Controller Host capable of supporting 1 to 20 Virtual Controllers, providing Virtual Controller
coordination.
Ovation Virtual A combination of the attributes of the Ovation SimController with Simulated I/O
SimController driver but running on a Windows operating system.
Port security Restricts input to a network interface by limiting and identifying MAC addresses of
the workstations that are allowed to access a switch port.
Real or Actual A Controller having the capability to connect to the actual plant I/O and perform plant
Controller control. Actual Controllers run on the VxWorks operating system.
Storm control A traffic storm occurs when a large number of data packets are transmitted through
a network, creating excessive traffic and degrading network performance. The storm
control feature monitors and compares the incoming traffic levels with the configured
storm control level.

OW360_57 7
1.7 What are the architecture types of Ovation Virtual Controllers?

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

8 OW360_57
 1.7 What are the architecture types of Ovation Virtual Controllers?

1.7.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 depicts the Ovation single-machine architecture.

Figure 1: Single-machine architecture illustration

OW360_57 9
1.7 What are the architecture types of Ovation Virtual Controllers?

1.7.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 depicts an Ovation Networked system.

Figure 2: Networked architecture illustration

10 OW360_57
 S E C T I O N 2

2 Hardware and software requirements for an Ovation

Virtual Controller system

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

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 workstations. 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, has a unique IP
address. 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 requirements to operate one Virtual Controller Host are as follows:
 A Windows-based PC (Windows 7 / Server 2008 operating system / Server 2012 R2
(64-bit) operating system).
 4-GB 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.

OW360_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 following minimum requirements are necessary for software installation of a Virtual
Controller:
 One Windows-based PC (Windows 7 / Server 2008 / Server 2012 R2 (64-bit)
operating system).
 4-GB Memory.
 Standard Ovation software DVD.

12 OW360_57
 S E C T I O N 3

3 Licensing Ovation Virtual Controllers

IN THIS SECTION

General Ovation licensing information .............................................................................. 13

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

3.1 General Ovation licensing information

When planning to install Ovation software on your control system, ensure 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 Emerson.

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.

For more information on general Ovation licensing, refer to the Ovation Developer Studio User
Guide.

3.2 What are the Virtual Controller license types?

Two licenses are required for a Virtual Controller system:

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

OW360_57 13
3.2 What are the Virtual Controller license types?

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. Once you
receive the license file, copy it to the Virtual Controller Host machine and configure the
environment variable for the Vxsim license (see page 22).

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 (see page 22).

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.

14 OW360_57
 S E C T I O N 4

4 Configuring Ovation Virtual Controllers

IN THIS SECTION

Accessing the Ovation Developer Studio .......................................................................... 15

Before starting your Virtual Controller software configuration .......................................... 16
Configuring network switch settings for Virtual Controllers ............................................... 16
Configuring a Virtual Controller software .......................................................................... 21
Upgrading the Virtual Controller Hosts ............................................................................. 45

4.1 Accessing the Ovation Developer Studio

When your Ovation system is loaded, the Developer Studio icon appears on your desktop.
Double-click the icon and the Developer Studio window appears. Refer to the Ovation Developer
Studio User Guide.

You can also access the Developer Studio from the context menu of the Operator Station
applications, such as Point Information. For more information, refer to the Ovation Operator
Station User Guide.

Note: Much of the setup and configuration of the Developer Studio contents and hierarchy is
performed by an Emerson representative before the system is installed in your plant.

OW360_57 15
4.2 Before starting your Virtual Controller software configuration

4.2 Before starting your Virtual Controller softw are configuration

Check the following items before configuring the Virtual Controller software:
 Obtain the appropriate licenses for the following:
 Virtual Controllers. For more information, see What is needed to license the Virtual
Controller? (see page 14).
 Virtual Controller Hosts (VCHs). For more information, see What is needed to license the
Virtual Controller Host? (see page 14).
 Know if your system uses the Ovation Highway Interface (OHI).

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
from the Virtual Controller Host.

 Understand your 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
becomes disabled. See Configuring network switch settings for Virtual Controllers
(see page 16) for more information.
 Configure Controller Networking.
Refer to the applicable Ovation Controller User Guide for more information.

4.3 Configuring network sw itch settings for Virtual Controllers

Switch ports in Ovation networks are assigned roles through configuration of the switch.
Equipment is connected to specific ports on the switch based on the role that has been assigned
to the port. Within restrictions, you can change the assigned role of an individual port from the
defaults by modifying the configuration of the switch.

See the following sections for more information about switch configuration for Virtual Controllers:
 What are different port types in Ovation networks (see page 17)?
 To configure an Ovation VCH drop port (see page 18).

Notes:

 These sections are applicable to Ovation networks built with Emerson part numbers
1X00507, 1X00508, 1X00459, 1X00927, 5X00400, and 5X00700. These networks are built
with Cisco 2960, 2960+, 3750, 3750V2, and 3750X switches. Previous versions of the
network (1X00036 and 1X00093) must be evaluated on a case-by-case basis for
modification. These networks are built with Cisco 2924 and 2950 switches. Changes to
those networks should be done using the Emerson CCL or TPNF process.
 Only end station access ports can be modified using this section. You should not modify any
switch-to-switch ports. The ports that should not be modified include all root or fan-out
connections and all cross connections – both between root area switches and between
fan-out area switches. Any change to these connections should be done using the standard
Emerson switch configuration tools or using the Emerson CCL or TPNF process.
 Neither fiber optic ports nor ports with SFP modules should be modified using this section.

16 OW360_57
 4.3 Configuring network switch settings for Virtual Controllers

4.3.1 What are different port types in Ovation networks?

An Ovation network can contain the following types of switch ports:

 Ovation drop port: An Ovation drop port connects to an Ovation drop. The speed and duplex
are set to 100 Mbps with full duplex. The traffic parameters are tuned to allow the maximum
multicast traffic expected from one drop.
 Ovation drop/router port: An Ovation drop/router port allows connections to either an
Ovation drop or a router, such as a field LAN or multinetwork router. This type only exists for
third-generation Ovation networks (networks built with Emerson part number 5X00400 or
5X00700). It is not applicable to other Ovation networks. It is identical to an Ovation drop port
except that it relaxes the restriction on the number of MAC addresses permitted to allow a
redundant router to be connected.
 Ovation VCH drop port: An Ovation VCH drop port allows connections to Ovation Virtual
Controller Hosts. It is similar to an Ovation drop port but relaxes constraints on the number of
MAC addresses, the amount of multicast traffic, and other parameters in order to allow the
multiple controllers within a VCH to connect to the Ovation system. See To configure an
Ovation VCH drop port (see page 18) for more information about configuring an Ovation VCH
drop port.
 Ovation IP only port: An Ovation IP only port allows connections to non-Ovation devices,
such as printers and time servers. The speed and duplex are set to auto-negotiate. Dynamic
point data is not forwarded to the device.

Note: Only the Ovation VCH drop port type is discussed in this manual. It is beyond the scope
of this manual to discuss other port types.

The port types available on an Ovation network switch depend on when the base configuration
was created. The following table summarizes the availability of port types.

Availability of port types

PORT TYPE SECOND-GENERATION THIRD-GENERATION AVAILABIL ITY

AVAILABILITY (5X00400 AND 5 X00700
(1X00507, 1X00508, AND SWITCHES)
1X00927 SWITCHES)

Ovation drop port Available Available

Ovation drop/router Not needed Available
port
Ovation VCH drop port Can be added Can be added
Ovation IP only port Available Available

OW360_57 17
4.3 Configuring network switch settings for Virtual Controllers

4.3.2 To configure an Ovation VCH drop port

Notes:

 Before changing the switch configuration, carefully identify which switches and switch ports
each Virtual Controller is connected to.
 This procedure assumes you are familiar with using the Cisco switch command line
interface, its syntax, and editing features.

This procedure describes conversion of an Ovation drop port to an Ovation VCH drop port. Use
the following steps to adjust the switch configuration for a port that is used to connect a VCH to
the Ovation network:

1. Telnet to the switch or connect serially using the CONSOLE port. If using Telnet, log on to the
switch to access the command shell.

Note: To Telnet to the switch, add the switch to the Radius Client table.

2. The Command Prompt window appears. Type the enable command and then the
password.
3. The command prompt changes from > to #. For each switch port identified as a Virtual
Controller Host connection, type the following command:
show running int fa0/<n>
Where, <n> is the port number of the Virtual Controller Host’s network connection.
If the switch is a 5X00400G2xx or 5X00700G2xx, the interface name will be either
gi<m>/0/<n> or fa<m>/0/<n>. For example, gi is gigabit and <m> is the switch
number (1, 2, or 3).

18 OW360_57
 4.3 Configuring network switch settings for Virtual Controllers

4. The switch responds with the following output. Review the output. Verify that the interface
description is Ovation Highway Drop Only and check the storm control and port security
settings.
interface FastEthernet0/8
description Ovation Highway Drop Only
switchport mode access
switchport nonegotiate
load-interval 30
speed 100
duplex full
macro description Ovation-Drop-Port
storm-control broadcast level pps 300 150
storm-control multicast level 15.00 10.00
storm-control action trap
spanning-tree portfast
end
In networks with 5X00400 and 5X00700 switches, a port configuration appears as follows:
interface GigabitEthernet1/0/13
description Ovation Highway Drop Only
switchport mode access
switchport nonegotiate
switchport port-security
switchport port-security aging time 2
switchport port-security violation restrict
switchport port-security aging type inactivity
load-interval 30
speed auto 100
duplex full
macro description cisco-desktop | Ovation-Drop-Port
no mdix auto
storm-control broadcast level pps 300 150
storm-control multicast level 15.00 10.00
storm-control action trap
keepalive 1
spanning-tree portfast
spanning-tree bpduguard enable
spanning-tree link-type point-to-point
end
5. Type conf t to access the configuration mode.

OW360_57 19
4.3 Configuring network switch settings for Virtual Controllers

6. The command prompt changes to switchname(config)#. Type the following commands in

the configuration mode.
macro name Ovation-VCH-Drop
description Ovation VCH Drop
no spanning-tree bpduguard enable
spanning-tree bpdufilter enable
no storm-control multicast level
switchport port-security maximum 24
@

Note: The @ symbol terminates the macro definition.

7. Type interface fa0/<n> or interface gi<m>/0/<n>, where the interface name

specified is the switch port identified as the Virtual Controller connection.
8. The command prompt changes to switchname(config-if)#. Type the following commands at
this prompt.
macro apply Ovation-VCH-Drop
exit
9. Repeat Steps 7 and 8 for each Virtual Controller Host port connection.
10. Type end to exit the configuration mode and return to the command shell.
11. The command prompt should now be switchname#. Type show run.
12. Carefully review the interface configurations modified above to verify that multicast storm
control levels are removed and the port security address has a maximum value of 24.

Note: If no port security was previously configured, the maximum is listed but without the
additional port security configuration.

13. To save the configuration changes to the non-volatile configuration, type write mem at the
switchname# prompt. The switch responds with the following output.
Building configuration...
[OK]
14. Repeat Steps 1 to 13 for each switch that has Virtual Controller connections.

20 OW360_57
 4.4 Configuring a Virtual Controller software

4.4 Configuring a Virtual Controller software

All Ovation 2.4.1 and later systems have the Virtual Controller option available. You can utilize the
Virtual Controller option by activating the Virtual Controller software. Activating the Virtual
Controller software involves configuring at least one Virtual Control Host and up to 20 Virtual
Controllers in each host.

Note: For Ovation 3.1.2 and later systems, the number of supported Virtual Controllers per
Virtual Controller Host has been increased from 5 to 20.

You can use a Virtual Controller in place of an actual Controller in a non-simulator environment.
However, consider the following points before proceeding with this setup:
 Virtual Controller do not support Ovation I/O.
 Virtual Controllers do not guarantee a real-time performance.
 Logic execution time in a Virtual Controller will not be the same as it is in an actual
OCR400/OCR1100 Controller.
The following steps provide an overview of the Virtual Controller software configuration:

1. Ensure that you meet the prerequisites before starting your Virtual Controller software
configuration (see page 16).
2. Create an environment variable for the Vxsim license (see page 22).
3. Install the WRTap network driver and set up the network bridge (see page 26).
4. Configure the WRTap adapter maximum buffer number (see page 29).
5. Install Ovation on the Virtual Contoller Host machines. For more information, refer to the
Ovation Software Installation Manual.

Note: During the Ovation installation, select the Bridge option as the network interface.

6. Add and configure a drop as your new Virtual Controller Host (see page 33).
7. Add and configure each new Ovation Virtual Controller (see page 38).

Note: You may define up to 20 Virtual Controllers for each host. After you define your Virtual
Controllers, you must assign each Virtual Controller to a Virtual Controller Host.

8. Install Virtual Controller services in each Virtual Controller Host (see page 44).
9. Complete the Virtual Controller software configuration using the Developer Studio
(see page 44).

OW360_57 21
4.4 Configuring a Virtual Controller software

4.4.1 To create an environment variable for the Vxsim license

Perform the following steps to create an environment variable for the Vxsim license:

1. Go to Windows Start ->Control Panel->System.

2. The System window appears. On the left pane of the System window, select Advanced
system settings.

Figure 3: System window--Advanced system settings

3. The System Properties dialog box appears. Select the Advanced tab.

22 OW360_57
 4.4 Configuring a Virtual Controller software

4. On the Advanced tab, select Environment Variables.

Figure 4: Advanced tab--Environment variables

OW360_57 23
4.4 Configuring a Virtual Controller software

5. The Environment Variables dialog box appears. Click New.

Figure 5: Environment variables dialog box

6. The New System Variable dialog box appears. Perform the following steps:
a) Enter the variable name as LM_LICENSE_FILE.

Note: The variable value is the path and the filename where you have placed the license file
(.lic).

b) Enter the variable value in the entry field.

c) Click OK.

Figure 6: New System Variable dialog box

24 OW360_57
 4.4 Configuring a Virtual Controller software

7. Verify that the added license file appears on the Environment Variables dialog box under the
System variables pane.

Figure 7: Environment Variables dialog box showing new license file

8. Click OK.

OW360_57 25
4.4 Configuring a Virtual Controller software

4.4.2 To install the WRTap network driver and setup the network bridge

Note: Remember the following points while installing WRTap network driver.

 If you must install Virtual Controllers (WRTap) on a machine that is configured as a Virtual
Controller Host (VCH), then you must remove the bridge (see page 45). Next, you must
verify that all of the bindings and configuration parameters are present on the Ovation NIC.
If they are not present, then, you must reconfigure the Ovation NIC.
 If you must install Virtual Controllers (WRTap) on a machine with a history of unsuccessful
WRTap installation attempts, then you must remove the extra WRTap devices from the
Device Manager. After successful installation, you must have only one WRTap device.

Use the Ovation Installation DVD to install the WRTap driver. The file location is as follows:
 For Windows Server 2012 operating system, the location is
<DVD>\WRTapDriver\Serv2012
 For Windows Server 2008 or Windows 7 operating system, the location is
<DVD>\WRTapDriver\Win7_Serv2008
Perform the following steps to install the WRTap network driver and set up the network bridge:

1. Establish the static IP Address, Speed - 100 MB Full Duplex for the physical NIC that
attaches to the Ovation network.
2. Ensure that the Virtual Controller Host is joined to the Domain.
3. To remove the existing WRTap dirivers, access the Command Prompt window as an
Administrator. Navigate to the appropriate directory on the Ovation Installation DVD and type
the following at the command prompt:
wrtapInstaller.exe remove wrtap

Note: If there are no existing WRTap drivers, the message, No devices were removed
appears.

4. On the Command Prompt window, type the following:

wrtapInstaller.exe Install wrtap
5. If a driver installation message box appears, click Install.
Verify that the command output reads as follows:
Device node created. Install is complete when drivers are installed…
Updating drivers for wrtap from <directory>\wrtap.inf.
Drivers installed successfully.
6. Verify that the WRTap appears in the Network Connections window.
7. Configure the WRTap adapter maximum buffer number (see page 29).

26 OW360_57
 4.4 Configuring a Virtual Controller software

8. On the Network Connections window. Perform the following steps:

a) Click Advanced from the menu bar.
b) Select the Advanced Settings tab. The Advance Settings window appears.
c) Move the physical NIC to arrange it above of the WRTap driver.
d) Click OK.

Figure 8: Advanced Settings – Connections

OW360_57 27
4.4 Configuring a Virtual Controller software

9. Restart the machine.

10. In the Network Connections window, perform the following steps:
a) Hold down the Ctrl key to select the WRTap driver and the physical NIC, which connects
to the Ovation network.
b) Right-click Bridge Connections. This process takes a few minutes to complete.
11. Verify that the Bridge appears in the Network Connections window.
12. Right-click the Bridge and select Properties.
13. Configure the following Bridge TCP/IPV4 attributes to match the Ovation NIC attributes:
 IP address.
 Subnet Mask.
 Default Gateway.
 DNS Server.
14. Close the Properties window.
15. On the Network Connections window. Perform the following steps:
a) Click Advanced from the menu bar.
b) Select the Advanced Settings tab. The Advance Settings window appears.
c) Ensure that the Bridge is listed at the top of the Adapter connection window.
d) Move the Ovation NIC item to position it second in the list.
e) Click OK.

Figure 9: Advanced Settings -- Connections

28 OW360_57
 4.4 Configuring a Virtual Controller software

16. Restart the machine.

Notes:

 During the Ovation installation, select the Bridge (Microsoft Multiplexor Adapter or Microsoft
Miniport Adapter) option as the network interface.
 Do NOT modify the WRTap driver settings after it is installed.

4.4.3 To configure the WRTap adapter maximum buffer number

Perform the following steps to configure the WRTap adapter maximum buffer number:

1. Navigate to Windows Start->Control Panel->Network and Sharing Center.

Figure 10: Network and Sharing Center

OW360_57 29
4.4 Configuring a Virtual Controller software

2. On the left pane of the window, select Change adapter settings.

Figure 11: Change adapter settings

3. On the window, right-click WRTAP and select Properties.

Figure 12: WRTAP--Properties

30 OW360_57
 4.4 Configuring a Virtual Controller software

4. The WRTAP Properties dialog box appears. Click Configure.

Figure 13: WRTAP properties dialog box

OW360_57 31
4.4 Configuring a Virtual Controller software

5. The WindRiver WRTAP Properties dialog box appears. Perform the following steps:
a) Select the Advanced tab.
b) Click Maximum Buffer Number.

Figure 14: WindRiver WRTAP properties dialog box

32 OW360_57
 4.4 Configuring a Virtual Controller software

c) Under the Value field, enter 2000.

d) Click OK.

Figure 15: WindRiver WRTAP properties dialog box -- Maximum Buffer Number

4.4.4 To add a new Virtual Controller Host

Use the following steps to add a new Virtual Controller Host:

1. Access the Ovation Developer Studio (see page 15).

2. Use the system tree to navigate to the Drops folder:
Systems -> Networks -> Units -> Drops

OW360_57 33
4.4 Configuring a Virtual Controller software

3. Right-click the Drops folder and click Insert New.

Figure 16: Drops folder in the Developer Studio

34 OW360_57
 4.4 Configuring a Virtual Controller software

The Insert New Drops Wizard appears:

Figure 17: Insert New Drops Wizard

4. Enter a drop ID for the Virtual Controller Host in the Drop Id field. Valid entries are 1-254.
5. Enter the partner drop ID, if applicable, in the Partner Id field.
6. Select Virtual Controller Host from the Drop Type drop-down list to designate the drop as
the Host Controller.
7. Click Finish.

Note: All Ovation 2.4.1 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 list. 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 to the list of SimStations
available for Virtual or SimControllers.

OW360_57 35
4.4 Configuring a Virtual Controller software

8. 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 as necessary or use the default selections. After you enter all the required information,
click Apply and then Ok.

Figure 18: New Drops dialog box fields

36 OW360_57
 4.4 Configuring a Virtual Controller software

New Drops dialog box field descriptions

FIELD DESCRIPTION

Drop Type Drop-down menu showing drop type selections (select a 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.
Local Data Server Read-only field that indicates if the drop has been defined as a local
data server (No, Yes).
Local Alarm Collector Read-only field that indicates if the drop has been defined as a local
alarm collector (No, Primary, Partner, Both). Refer to 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 as follows:
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 as follows:
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, you need to
determine the NIC address. Refer to the Simulation User Guide for
Ovation for more information.
Ovation Highway Interface Displays speed in Mbps (megabits per second) at which the Virtual
Mode Controller connects to the network.
Backup Ovation Highway Displays speed in Mbps (megabits per second) at which the redundant
Interface Mode Virtual Controller, if available, connects to the network.
Restore
Restore Mode Online Controller Restore Mode. Reloads mismatched Controllers to a
prior matched state. The choices are:
 Restore Mode Disable
 Restore Mode Enable All Drops
 Restore Mode Enable Redundant Drops
(Default - Restore Mode Disabled.)

OW360_57 37
4.4 Configuring a Virtual Controller software

FIELD DESCRIPTION

Partner
Partner ID This field indicates the drop ID of the partner drop. Enter information if
applicable.
Virtual Controller Host

Port TCP port used for communication with Virtual Controllers. The default
value is 6001.
Master Virtual Controller Host This field indicates the configured Master Virtual Controller Host, which
coordinates timing between all other hosts on the network.
Master Virtual Controller Host TCP port used for communication with Virtual Controllers. The default
Port value is 6001.
Virtual Controller Host Virtual Controller Host Drop name (DropXXX).

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

Port TCP port used for communication with Virtual Controllers. The default
value is 6010.
Virtual Controller 2 - 20
Virtual Controller at Index 2 - Read-only field, specifies the drop name configuration for this index.
20
Port TCP port used for communication with Virtual Controllers. The default
value is 6010.

4.4.5 To add a new Ovation Virtual Controller

Note: You must define a Virtual Controller Host (see page 33) before adding Virtual Controllers
to your system.

Use the following steps to add a new Ovation Virtual Controller:

1. Access the Ovation Developer Studio (see page 15).

2. Use the system tree to navigate to the Drops folder:
Systems -> Networks -> Units -> Drops

38 OW360_57
 4.4 Configuring a Virtual Controller software

3. Right-click the Drops folder and click Insert New.

Figure 19: Developer Studio system tree

OW360_57 39
4.4 Configuring a Virtual Controller software

The Insert New Drops Wizard appears:

Figure 20: Insert New Drops Wizard

4. Enter a drop ID for the Virtual Controller in the Drop Id field. Valid entries are 1-254.
5. Enter the partner drop ID, if applicable, in the Partner Id field.
6. Select Virtual Controller or Advanced Virtual Controller from the Drop Type drop-down
list to enable the Virtual Controller software.
7. Click Finish.

40 OW360_57
 4.4 Configuring a Virtual Controller software

8. 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 you enter all the required information, click Apply and then
Ok.

Figure 21: New Drops dialog box

OW360_57 41
4.4 Configuring a Virtual Controller software

New Drops dialog box field descriptions

FIELD DESCRIPTION

Drop Type This procedure deals specifically with the Virtual Controller selection from the
drop-down menu.
Controller Type Choose the correct Controller type from the following options:
 OCR1100
 OCR400
Control Available when a primary and a partner Controller are inserted and allow both
Synchronization Controllers to be automatically synchronized.
You can choose whether to have information sent over a dedicated cable or over
the Ovation network by selecting one of the following options:
 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
Limit monitor.
Due to the way points are indexed, the actual point number is the maximum point
count minus 1.
You can select from the following options:
 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.

Simulation Speed Sets the speed control for Virtual Controllers by selecting one of the following
Control options:
 TASK: This option changes the execution time of the control task and alarm
task.
 OPERATING SYSTEM: This option changes the interrupt rate of the Virtual
Controller.
Primary and When the primary/partner configuration is not used, no information input is
Partner Sections required in the 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. The format is as
IP Address follows:
xxx.xxx.xxx.xxx
The System Administrator typically assigns these addresses. They can also be
assigned in any valid range if the network is isolated from other networks, such
as the Internet.

42 OW360_57
 4.4 Configuring a Virtual Controller software

FIELD DESCRIPTION

Ovation Network The format of the hardware address is as follows:

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, refer to the applicable
Ovation Controller User Guide.
Ovation Highway Displays speed in Mbps (megabits per second) at which the Virtual Controller
Interface Mode connects to the network.
Backup Ovation Displays speed in Mbps (megabits per second) at which the redundant Virtual
Highway Interface Controller, if available, connects to the network.
Mode
Control The Controller software is configured to automatically run control synchronization
Synchronization of redundant Controllers over the network.
Interface
For a redundant Virtual Controller, this is always over the network.
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 is available.
Host

Notes:

 After the addition of an Ovation Virtual Controller drop (or drops), you must query download
all drops on the network.
 The Virtual Controller supports the following third party drivers:
1. Ovation Toshiba Interface
2. Ovation MHI Turbine Control Interface
3. Redundant Modbus
 Set the fail controller if comm error configuration to FALSE, when configuring the drivers for
a Virtual Controller. This step enables the driver to attempt to reconnect to the remote
device.

OW360_57 43
4.4 Configuring a Virtual Controller software

4.4.6 To install virtual controller services

Note: Ensure that Ovation is installed before you install virtual controller services (vxsimnetd
and vcoordinator) in a Virtual Controller.

Use the following steps to install virtual controller services (vxsimnetd and vcoordinator) in a
Virtual Controller Host:

1. Open the Command Prompt window.

2. At the command prompt, type cd C:\Ovation\OvationVirtual.
3. Type wrtap64 and press Enter.
4. Exit the window.
5. Restart the machine.

4.4.7 To complete the Virtual Controller software configuration using the

Developer Studio

Use the following steps to complete the Virtual Controller software configuration using the
Developer Studio:

1. Access the Ovation Developer Studio (see page 15).

2. Configure the Virtual Controller Hosts and each Virtual Controller. (If not already
configured, see Configuring Virtual Controller software.)
3. Download the Virtual Controller Host machine.
4. Verify that the Vxsim license file is installed on the machine (see page 14).
5. Restart the Virtual Controller Host.

44 OW360_57
 4.5 Upgrading the Virtual Controller Hosts

4.5 Upgrading the Virtual Controller Hosts

Notes:

 Due to security reasons, an IP address in an Ovation manual is shown with "127" as the first
octet. These IP addresses are for example purposes only and should not be used in an
actual Ovation system. Contact your Emerson project representative for assistance in
obtaining the IP addresses for your system.
 Virtual Controller Hosts require IP addresses with a last octet of 254 within the address
range assigned to the Ovation network for internal purposes. As an example, in a system
that has an address of 127.168.2.0/23 (subnet mask 255.255.254.0), the 127.168.2.254
address is transparently utilized by the Virtual Controller Host software and configuration, in
addition to the machine’s user-assignable IP address for the Ovation interface. This address
is utilized locally and automatically and does not have the potential to conflict with
addressing elsewhere on the Ovation network. Therefore, it may be simultaneously used by
multiple Virtual Controller Hosts on the same Ovation system without any adverse effect.
However, because of its use, this same address should not be assigned as the
user-configurable IP address of such a machine for its Ovation interface. In addition, this
same address should not be assigned to any other drop or device on the Ovation network.
 The subnet mask and addressing planned for the Ovation system must be such that
communication is possible from the VCH to the .254 address. This means that the .254
address must be part of the subnet that is used on the Ovation network. As an example, a
system with 127.168.2.0 with a subnet mask of 255.255.255.128 does not include the .254
address and cannot be used with a Virtual Controller Host. Note that such addressing is
rare.

The following steps provide an overview of upgrading pre-Ovation 3.5.0 Virtual Controller Hosts to
Ovation 3.5.0 (or later) Virtual Controller Hosts:

1. Remove the additional IP addresses of each Virtual Controller from the NIC1 configuration by
using the Advanced button in the Network Configuration tool.
2. If the network bridge already exists, remove the bridge (see page 45).
3. Create a bridge (see page 46).
4. Configure the bridge (see page 46).
5. Complete the Virtual Controller software configuration using the Developer Studio
(see page 44).

4.5.1 To remove the bridge

Use the following steps 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.

OW360_57 45
4.5 Upgrading the Virtual Controller Hosts

4.5.2 To create a bridge

Note: You MUST remove the DDB protocol from the physical NIC before creating a bridge and
assigning a DDB protocol to the created bridge.

Continue with the network configuration by performing the following steps:

1. Access the Network Configuration tool.

2. Create a bridge between the WRTap adapter and the Ovation NIC.
3. Configure the bridge (see page 46).

4.5.3 To configure the bridge

Use the following steps to configure the bridge:

1. Access 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:
 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.

46 OW360_57
 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? ................................................. 47

Building control in Virtual Controllers ................................................................................ 48
Simulating control in Virtual Controllers ............................................................................ 48

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.

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.
Refer to 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.
Refer to the Ovation Controller User Guide to perform the following operations:
 Download configurations.
 Drop load.

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

OW360_57 47
5.2 Building control in Virtual Controllers

5.2 Building control in Virtual Controllers

The approach and procedure used to build control in Ovation Virtual Controllers are the same
approach and procedure used to build control on actual Ovation Controllers. Refer to the Ovation
Control Builder User Guide for information about control building.

5.3 Simulating control in V irtual Controllers

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

Refer to the following manuals for information and procedures to simulate control:
 Ovation Simulation User Guide.
 Ovation Controller User Guide.

48 OW360_57
 S E C T I O N 6

6 Using the Virtual Controller Manager

IN THIS SECTION

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

6.1 What is the Virtual Controller 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 depicts the Ovation Controller Manager window.

Figure 22: Ovation Virtual Controller Manager

OW360_57 49
6.1 What is the 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.
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.

50 OW360_57
 6.1 What is the Virtual Controller Manager?

6.1.1 To display the Virtual Controller Manager

Use the following steps to display the Virtual Controller Manager:

1. Open Windows Explorer.

 Navigate to C:\Ovation\Ovationbase.
 Locate VCoordManager.exe.
 Double-click VCoordManager.exe. The Ovation Virtual Controller Manager window
displays.

Figure 23: Ovation Virtual Controller Manager

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

Note: Do not copy the file directly to the desktop. This application must run in the
\ovation\ovationbase directory. Therefore, ensure that a shortcut is created to the application.

OW360_57 51
Index

To create an environment variable for the

A Vxsim license • 21
Accessing the Ovation Developer To display the Virtual Controller Manager •
Studio • 15 51
To install the WRTap network driver and
B setup the network bridge • 25
To install virtual controller services • 43
Before starting your Virtual Controller
To remove the bridge • 44
software configuration • 15
Building control in Virtual Controllers • 48 U
C Upgrading the Virtual Controller Hosts • 44
Using the Virtual Controller Manager • 49
Configuring a Virtual Controller software • 21
Configuring network switch settings for V
Virtual Controllers • 16
Configuring Ovation Virtual Controllers • 15 Virtual Controller terminology • 6
Copyright Notice • 2 Virtual Controllers usage • 3

G W
General Ovation licensing information • 13 What are different port types in Ovation
networks? • 17
H What are the architecture types of Ovation
Virtual Controllers? • 8
Hardware and software requirements for an
What are the hardware requirements for the
Ovation Virtual Controller system • 11
Ovation Virtual Controller host? • 11
I What are the requirements for Ovation
Virtual Controllers? • 11
Introduction to Ovation Virtual Controllers • 1 What are the software requirements for the
L Ovation Virtual Controller host? • 12
What are the Virtual Controller
Licensing Ovation Virtual Controllers • 13 commands? • 5
What are the Virtual Controller license
P types? • 13
Programming and using Ovation Virtual What is an Ovation Virtual Controller
Controllers • 47 Host? • 4
What is an Ovation Virtual Controller? • 4
S What is needed to license the Virtual
Controller Host? • 14
Simulating control in Virtual Controllers • 48
What is needed to license the Virtual
T Controller? • 14
What is needed to program and use Virtual
To add a new Ovation Virtual Controller • 37 Controllers? • 47
To add a new Virtual Controller Host • 32 What is Ovation Virtual Controller
To complete the Virtual Controller software simulation? • 1
configuration using the Developer
Studio • 43
To configure an Ovation VCH drop port • 18
To configure the bridge • 45
To configure the WRTap adapter maximum
buffer number • 28
To create a bridge • 45

OW360_57 53
Index

What is the operation of the Virtual

Controller? • 6
What is the Virtual Controller Manager? • 49
What is the Virtual Controller networked
architecture? • 10
What is the Virtual Controller single-machine
architecture? • 9
Who uses Virtual Controller technology? • 2

54 OW360_57