002 Getting Started PDF

D3P01861802
May 2010
Getting Started With

DeltaV Operate for PROVOX Consoles
1996 - 2010 Fisher-Rosemount Systems, Inc. All rights reserved. Unauthorized duplication, in whole or in part,
is prohibited.
Printed in the Republic of Singapore.
Emerson, Emerson Process Management, the Emerson Process Management Design, DeltaV, the DeltaV design,
and PlantWeb are marks of one of the Emerson Process Management group of companies. All other marks are
property of their respective owners. The contents of this publication are presented for informational purposes
only, and while every effort has been made to ensure their accuracy, they are not to be construed as warranties or
guarantees, expressed or implied, regarding the products or services described herein or their use or applicability.
All sales are governed by our terms and conditions, which are available on request. We reserve the right to modify
or improve the design or specification of such products at any time without notice.
Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Differences between Operator Workplace and DeltaV Operate for PROVOX Software. . . . . . . . . . . . . . . . . . 1-4
DeltaV Operate for PROVOX Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Intended Audiences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Installation and Upgrade Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Manual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Warnings, Cautions, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Structure of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Printed Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Where to Find Answers for Product and Document Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Chapter 2 Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware and Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Equipment List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Operator Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Communications Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type DH6032 Highway Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Switch (Twisted Pair) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1
2-1
2-3
2-4
2-4
2-4
2-5
2-6
Chapter 3 Initial Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Hardware Variations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Setting Up Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Setting Up Console Data Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Equipping the Server Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Cabling for the Server Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Power-up Test Sequence: Server Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Interconnecting Server Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Connecting DeltaV Operator Stations to Ethernet Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Contents
iii
System Configuration: Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changing the Windows Administrator Account Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting the Console Data Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting DeltaV Operator Station Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test the Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Up Primary/Secondary Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-17
3-18
3-19
3-23
3-31
3-33
3-34
Chapter 4 Saving Console Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Properties to Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Data Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Operator Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-2
4-3
4-5
Chapter 5 Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Supported Console Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Single Logons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Single Secure Logons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Changing the PROVOX Account Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Add DeltaV Users to the PROVOX21 Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Setting Up Users in a Workgroup Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Setting Up Users in a Domain Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
On the Windows Server Domain Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
On each DeltaV Operate for PROVOX Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Disable Web Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Set DeltaV-Style Alarm Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Initialize PROVOX Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Define Operator Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Uninitializing the HDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Defining the HDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Set or Verify POC Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
About the PROVOX21Admin Account Password in the Service Dialog . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Configure DCOM Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Verify Software Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
DeltaV Operate for PROVOX Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
Operator Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Setting Internet Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24
Setting Acrobat Reader Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Cleaning Up the \POC\Programs Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26
Removing the Master License Popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
iv
Getting Started with DeltaV Operate for PROVOX Consoles
Other Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting IA and Trend Window Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable PROVOX Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create PROVOX Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create Settings and Layout Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Settings and Layout Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Settings Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Layout Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Defining Primary and Secondary Servers and Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Unsolicited Data Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tag and Display Tag Substitutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Valid Tags in ENVOX Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Substitution Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example Substitutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Logging On to the Operator Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Convert Existing Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-27
5-27
5-29
5-32
5-34
5-35
5-36
5-38
5-39
5-39
5-40
5-41
5-41
5-42
5-42
5-43
5-44
5-45
Chapter 6 Database Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Device Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Clock List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Shift Table Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trend Set Definition and Trend Trace Definition Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Display List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PMA List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Access List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pen Recorder List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report List Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Report Header Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Preferences Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Horn Tone Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Limits Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedures Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Color Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Text Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
6-1
6-2
6-3
6-3
6-4
6-4
6-4
6-5
6-6
6-6
6-6
6-6
6-7
6-7
6-7
6-7
6-7
6-7
6-8
6-8
6-8
PMA Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

PPA Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Alarm Priority Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
User Definitions Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
User Application List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
User UDK List Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Application Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
User Defined Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
User Palette . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Highway Access Control List Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Display Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Console Points. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Targeting Points to a Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Target Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Console Target Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Extended Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Chapter 7 Display Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Display Names in the ENVOX Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Display Names in DeltaV Operate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Display Elements and Link Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Alarm Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Using the Expression Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Datalink Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Expression Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Selecting A Tag and Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Editing Occurrence Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Entering Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Display Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Calculation Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Entering Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Calculation Expression Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Example Calculation Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Calculation Attribute Expression Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
THISUSER Display Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Using Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
frsPocTasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
frsPOCIntegrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
frsInputAnyModuleNameFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
vi
frsInputAnyModuleNameDT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
frsInputAnyModuleNamePD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accessing DDP Values from Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
#Current. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Writing Attributes from Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Entry Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Writable Display Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FST Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-22
7-22
7-23
7-23
7-23
7-23
7-24
7-25
7-26
7-26
Chapter 8 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Supported Console Hardware and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Console Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Default User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Console Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Horn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Stale Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Instrument Area and DDP Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Instrument Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
DDP Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Starting and Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Popup Faceplates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Message Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Viewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Connecting to a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Event Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Status Summaries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Reports Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Document Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Alarm Banner Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Disk Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
PROVOX Trend Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Trace Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Trend Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Opening and Positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
The Trend Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Contents
vii
Importing Configured Trend Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding Trace Data Sets to Trend Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Trace Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing Trace Data Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Trace Data Set Definition Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Trend Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting and Recovering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Data Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundancy Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual and Automatic Switchovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console-Resident Point Redundancy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Pairing for Console Point Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual and Automatic Switchovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Redundancy in Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Console Data Server Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Replacing an Ethernet Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database Download and Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-16
8-18
8-19
8-21
8-21
8-22
8-23
8-23
8-24
8-25
8-28
8-28
8-28
8-33
8-34
8-35
8-37
8-38
8-38
8-39
Appendix A Installing the Operator Console Software . . . . . . . . . . . . . . . . . . . . . A-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
PROVUE or Operator Workplace Console Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Installing Software on Console Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Installing the Network Time Protocol Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Install DeltaV Operate for PROVOX Software on DeltaV Operator Stations . . . . . . . . . . . . . . . . . . . . . . A-6
Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
PROVOX Operator Console Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Converting Existing Console Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Planning And Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Saving Console Data Server Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Install Windows Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Install The Console Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Checkout, Setup, and Restore Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Converting PROVOX Operator Console Workstations to DeltaV Operator Stations. . . . . . . . . . . . . . . . A-15
Installing DeltaV Operate for PROVOX Software on DeltaV Operator Stations . . . . . . . . . . . . . . . . . . . A-15
Creating Migration Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15
Post-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
Install Adobe Acrobat Reader Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17
viii
Appendix B Restoring Windows Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Preliminary Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Additional Windows Server 2008 Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Adding an Application Server Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Disabling Internet Protocol Version 6 (TCP/IPv6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Disabling User Account Control (UAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Disabling Windows Time Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Appendix C Upgrading Consoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Upgrading Console Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Adding Operator Stations to Existing Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Adding Unsolicited Data Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Adding Event Journal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Uninstalling Software from Console Data Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Upgrading from a Previous Software Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
DeltaV Operate for PROVOX Network Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Component Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Appendix D Other Network Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Plant Network Connection with Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Remote Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Redundant Remote Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Contents
ix
Figures
Figure 1-1
Figure 1-2
Figure 2-1
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 3-7
Figure 3-8
Figure 3-9
Figure 5-1
Figure 5-2
Figure 7-1
Figure 7-2
Figure 7-3
Figure 8-1
Figure 8-2
Figure 8-3
Figure 8-4
Figure 8-5
Figure 8-6
Figure 8-7
Figure 8-8
Figure 8-9
Figure 8-10
Figure 8-11
Figure C-1
Figure D-1
Figure D-2
Figure D-3
Figures
DeltaV Operate for PROVOX Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Typical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Typical Console Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
DeltaV Operate for PROVOX Network Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Typical Console System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Ground Connections: Server Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Power Connections: Server Cabinet with Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Server/HDL Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Server/Switch Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
HDL/PROVOX Highway Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
DeltaV Operator Station/Switch Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Typical Primary/Secondary Console System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Positioning Tab of DeltaV Operate for PROVOX Properties Dialog . . . . . . . . . . . . . . . . . . . . 5-28
Unsolicited Reporting Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Datalink Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Expression Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Point Calculation Attribute Expressions Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Viewer Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Server Setup Dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Importing Configured Trend Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Trace Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Adding Trace Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Console Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Integrity Detail -- Console Data Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30
Redundancy Application Console Data Server Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32
Integrity Faceplate -- Console Point Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35
Redundancy: Console-Resident Points Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36
Console Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Upgrade Example System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Connecting Process Networks to A Plant Network without A Central Switch. . . . . . . . . . . . . . . D-2
Using Fiber Optic Cables to Connect Remote Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
Primary/Secondary Console Data Servers with Remote Operator Stations . . . . . . . . . . . . . . . . . D-4
xi
xii
Tables
Table 1-1
Table 1-2
Table 3-1
Table 4-1
Table 5-1
Table 5-2
Table 7-1
Table 7-2
Table 7-3
Table 7-4
Table 8-1
Table 8-2
Table 8-3
Table 8-4
Table 8-5
Table 8-6
Table 8-7
Table 8-8
Table C-1
Tables
Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Type Style Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Naming and IP Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Console Information to Back Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
DeltaV and ENVOX Password Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
User Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Renamed Display Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Attributes That are in DeltaV Operate for PROVOX Software but not in Operator Workplace 7-11
Operator Workplace Attributes Not Implemented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Writable Display Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Instrument Area Command Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Pixel Dimensions of an Instrument Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Report Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Number of Trend Traces That Can Be Defined Versus Sample Interval and Duration . . . . . . . 8-14
Trend Viewer Command Line Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Durations for Imported Trend Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Effect of Restart on Console Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Console Redundancy Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Actions Required for Various Console Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
xiii
xiv
Chapter 1
Introduction
The following figure is a schematic drawing of a DeltaV Operate for PROVOX
implementation in a plant.
Figure 1-1
DeltaV Operate for PROVOX Console
Overview
The DeltaV Operate for PROVOX Console is the combination of DeltaV and
PROVOX hardware and software that allows an operator to operate both DeltaV and
PROVOX controllers from a single DeltaV Operator Station. The PROVOX
components of the software have evolved from PROVOX Operator Console
software.
Introduction
1-1
Note that some of the terminology is different between the two equipment types and
that some special operator training may be required.
The entire installation consisting of DeltaV Operate for PROVOX Data Servers (also
known as Console Data Servers) and DeltaV Operator Stations with DeltaV Operate
for PROVOX software installed is referred to as the DeltaV Operate for PROVOX
Console. The following list explains the major components that make up the console:
PROVOX Control Network (HDLs, controllers, I/O, and so on)

This is standard PROVOX equipment. No changes or modifications are required.
DeltaV Operate for PROVOX Data Server

The DeltaV Operate for PROVOX Data Server supports display of PROVOX
data on DeltaV Operator Stations.
PROVOX Operator Console Migration Station (not shown)

A migration station is a standard PROVOX Operator Console Operator Station
at the P3.x revision level with the DeltaV Operate for PROVOX update installed.
Migration stations are not required, but if you are migrating from a PROVOX
Operator Console, you can use migration stations to compare original displays to
converted displays to make sure they work as intended.
DeltaV Operator Stations

These are standard DeltaV Operator Stations that have the DeltaV Operate for
PROVOX update installed to support display of PROVOX data.
ProfessionalPLUS station
This is a standard DeltaV ProfessionalPLUS station. ProfessionalPLUS stations
are used as DeltaV engineering workstations. You can optionally install the
DeltaV Operate for PROVOX update on it, but it is not required.
DeltaV Control Network (controllers, I/O, and so on)

This is standard DeltaV equipment. No changes or modifications are required.
Note
Migration workstations are supported only for use when migrating to DeltaV Operate
for PROVOX software and are not supported for plant operation.
Note
In this manual the term operator station refers to both migration stations and DeltaV
Operator Stations.
As the schematic figure shows, DeltaV Operate for PROVOX Consoles integrate
the operation of PROVOX and DeltaV equipment at the operator station. The two
1-2
control networks remain separate. Data does not move between the networks. For
example, you cannot add a PROVOX parameter to the DeltaV Data Historian or view
DeltaV events in the PROVOX Event Viewer.
Conceptually, a DeltaV Operate for PROVOX console combines the functions of
both a standard DeltaV Operator Station controlling a DeltaV network and a
PROVOX Operator Console Workstation controlling a PROVOX system in one PC
workstation.
The DeltaV Operate for PROVOX update adds PROVOX operator interface
functionality to your DeltaV Operator Stations so that you can include links to data
from PROVOX controllers and links to data from DeltaV controllers on the same
display. DeltaV Operate for PROVOX software also installs several PROVOX
operator interface applications on the DeltaV Operator Stations that let you view and
manipulate process information in your PROVOX controllers.
Experienced DeltaV users will see no difference when operating DeltaV control
equipment. Experienced PROVOX console users operating PROVOX control
equipment will see the advanced graphics capabilities provided by DeltaV Operate.
DeltaV Operate for PROVOX software does not support the graphics used in
previous PROVOX consoles, but those graphics can be converted by Emerson
Process Management.
The remainder of this manual and the other DeltaV Operate for PROVOX system
documentation use the trademarks DeltaV and PROVOX to indicate which
components are being described.
Requirements
DeltaV ProfessionalPLUS station running DeltaV software with the DeltaV Operate
graphics. (The DeltaV Operator Interface graphics are not supported.)
The DeltaV Operate for PROVOX Data Server running DeltaV Operate for
PROVOX software.
Introduction
1-3
Differences between Operator Workplace and DeltaV

Operate for PROVOX Software
In addition to the differences in hardware and software platforms, there are several
functional differences between the two console products. Relative to Operator
Workplace the following can be said about DeltaV Operate for PROVOX:
Activity Points are not redundant, but they support warm standby.
PROVOX historical trends are not supported (DeltaV Operate for PROVOX
software is not compatible with historical trending devices such as the Trend Unit
and Console Trend Display).
ENVOX graphics configuration is not supported (DeltaV graphics are used

instead).
Complex conditionals must be reconfigured with the new Calculation Attribute

Expressions editor.
Reports are generated as HTML files that can be viewed and printed from a
browser.
Real-time trending has different features.
PROVOX System Clock is not supported.
User login uses DeltaV username and password as one layer of security.
Alarms and Events are reported to the Event Journal.
Limited compatibility with Batch Data Manager.
No logging printer (use the Event Journal to query and print desired
information).
DeltaV Operate for PROVOX Interface

The following figure and text explains the differences between the DeltaV Operate
for PROVOX user interface and the DeltaV and PROVOX Operator Console user
interface. If you are using DeltaV Operate for PROVOX Consoles to operate both
DeltaV and PROVOX controllers, Emerson Process Management strongly
recommends that the consoles use dual monitor workstations. The dual monitors
ensure that operators have access to all pertinent information and controls for both
systems.
1-4
Figure 1-2
Typical User Interface
The user interface includes the following:
The main window which can consist of:
Introduction
Two main pictures.

Two toolbars, one on each screen
Two alarm banners, one on each screen.
DeltaV and PROVOX integrity indicators.
Alarm Acknowledge buttons on each alarm banner.
1-5
PROVOX-related applications that are available are:
Instrument Area (includes the DDP area)
Trend Viewer
Event Journal
Summaries (Point Status and Communications Failure)
Document Viewer
Reports Viewer
The Main window combines the main graphics display, the toolbar, and the alarm
banner into an integrated layout whose size and relative position are fixed. The
Instrument Area, Trend Viewer, Event Journal, Summaries, Document Viewer, and
Report Viewer are separate applications in separate windows that can be moved
around the screen.
Intended Audiences
There are several intended audiences for this manual:
Persons responsible for installing, upgrading, and managing DeltaV Operate for
PROVOX Consoles
Persons who create the configuration and operator pictures for the DeltaV
Operator Stations.
Persons responsible for training operators how to use the software.
Persons in the first group should be familiar with Windows workstation and Windows
Server software installation and user account management. Persons in the second
group should be familiar with the ENVOX configuration software and the issues
involved in creating a configuration for an operator console.
Assumptions
This manual assumes the following:
1-6
Your plant has both DeltaV and PROVOX controllers installed and you want
operators to be able to control both types of equipment from one user interface
or your plant has only a PROVOX system installed and you want to use the
advanced graphics capabilities of DeltaV Operate. Note that in the DeltaV
Operate for PROVOX software, DeltaV terminology is used when required

instead of PROVOX terminology.
The DeltaV equipment is running with DeltaV Operate graphics. (Refer to the
section Installing Your DeltaV System in the DeltaV Books Online for instructions
on installing and setting up DeltaV systems).
The PROVOX equipment is installed and operating. The PROVOX system can
have PROVUE, Operator Workplace, or PROVOX Operator Consoles. This
manual explains how to move from any of these consoles to the DeltaV Operate
for PROVOX console.
Installation and Upgrade Scenarios

The tasks you must perform to install your DeltaV Operate for PROVOX Data
Server and DeltaV Operate workstations depend on your starting point. Appendix A
and Appendix C of this manual explain several installation and upgrade scenarios
including:
Installing DeltaV Operate for PROVOX software in a system that has PROVUE
or Operator Workplace consoles
Installing DeltaV Operate for PROVOX software in a system that has PROVOX
Operator Consoles.
Upgrading to a new version of DeltaV Operate for PROVOX software.
Manual Conventions
This manual uses the following conventions:
Introduction
Acronyms and Abbreviations Terms are spelled out the first time they
appear in text. Thereafter, only the acronym or abbreviation is used.
Revision Control The title page lists the part number and date of the manual.
When the manual is revised, the part number and date are changed.
References References to other documents give the document name and

number (and catalog number for Emerson Process Management manuals).
Commands Command lines shown in this manual include the operating

system prompt. The operating system prompts you see can be different than
shown. Enter commands at the system prompt on your screen.
1-7
Most operating system commands require that you press the Return or Enter key
after entering the command. This manual does not show these keys in command
lines and assumes you use them when necessary.
Long Command Lines Some commands may be too long to fit on one
line in this manual because of margin restrictions. However, you normally
enter such commands as a single line.
Mouse Conventions You can use either a two-button mouse or multibutton mouse. Since you can swap use of the left and right buttons, this
manual refers to the primary button (the left button) as the one used for most
actions and the right mouse button for specific actions. The following table
lists terms describing actions you take with the mouse.
Table 1-1 Using the Mouse
Term
1-8
Meaning
Point
Move the pointer (arrow or other shape) until the tip

rests on the object or area to which you want to point.
Click or Select
Point to the item you want to select, then press and

release the primary button without moving the mouse.
If you want to select several items for deletion, hold
down the Shift key and click the items to be deleted.
Double-click
Point to the item you want to select, then click the

primary button twice rapidly without moving the mouse.
Drag and Drop
Press and hold down the primary button while you

move the mouse. When you have moved the mouse
pointer to the position you want, release the primary
button.
Typographic Conventions The following table describes the type styles this
manual uses to distinguish different types of information.
Table 1-2 Type Style Conventions
When Text Appears This Way...
It Is...
ENVOX Technical Reference
The title of a manual.
BACKUP
An operating mode, alarm state, status,

operand, keyword, or key function
(used instead of a specific keyboard
key).
Select File | View from...
Menu options you select (in the order

given)
Press the Enter key
A named keyboard key. The key name

is shown as it appears on the keyboard.
An explanation of the keys acronym or
function immediately follows the first
reference to the key, if required.
Press the F12 key

Press the Ctrl V key
combination
For key combinations, press and hold

down the first key, press the second
key, then release both keys.
Username:
Database
$ Write SYS$OUTPUT
Text in a source file or a system prompt

or that appears on a screen.
example3.txt
A command you enter at a system

prompt or text you enter in response to
a program prompt.
my_data
Text you replace with your own text or

values when issuing commands. For
example, you would replace my_data
with an appropriate value.
An object is...
A new term being introduced.
Do not set...
A word or term given special emphasis

so that you do not miss the idea being
presented.
Warnings, Cautions, and Notes

Warnings, Cautions, and Notes attract attention to essential or critical information in
this manual. The types of information included in each are explained in the following:
Introduction
1-9
Warning
All warnings have this form and symbol. Do not disregard warnings. They are
installation, operation, or maintenance procedures, practices, conditions,
statements, and so forth, which if not strictly observed, may result in personal
injury or loss of life.
Caution
All cautions have this form and symbol. Do not disregard cautions. They are
installation, operation, or maintenance procedures, practices, conditions,
statements, and so forth, which if not strictly observed, may result in damage
to, or destruction of, equipment or may cause a long term health hazard.
Note
Notes have this form and symbol. Notes contain installation, operation, or maintenance
procedures, practices, conditions, statements, and so forth, that alert you to important
information which may make your task easier or increase your understanding.
Structure of this Manual

This document provides information on installing, configuring, and using the DeltaV
Operate for PROVOX console.
This document contains the following chapters:
1-10
Chapter 1: Introduction An overview of this manual, the intended audience,

the stylistic and typographical conventions used, and a list of related documents.
Chapter 2: Product Overview Discussion of the hardware and software

components that make up a DeltaV Operate for PROVOX systems
implementation.
Chapter 3: Initial Hardware Setup Describes the procedures of installing

the console hardware and performing initial setup tests.
Chapter 4: Saving Console Information An overview of the types and

locations of console information you may want to back up periodically.
Chapter 5: Software Setup Contains the tasks that tailor the software and
implement console security.
Chapter 6: Database Configuration Explains differences between Operator

Workplace and PROVUE console and DeltaV Operate for PROVOX database
configuration. This chapter outlines what you have to know to create a
configuration database in ENVOX or Control Desktop software to use with the

DeltaV Operate for PROVOX software.
Chapter 7: Display Configuration Contains an introduction to creating

graphics displays for the console using DeltaV Operate in Configure mode. This
chapter includes hints and tips on how to accomplish effects similar to what can
be done with ENVOX or Control Desktop software.
Chapter 8: Operating Environment This chapter, aimed at configuration

engineers and persons who train operators, explains how operating a PROVOX
system from the DeltaV Operator Station is different compared to Operator
Workplace Consoles and PROVUE consoles.
Appendix A: Installing the Operator Console Software This appendix

explains how to install the DeltaV Operate for PROVOX software on PROVOX
Console Data Servers and DeltaV Operator Stations.
Appendix B: Installing Windows Software Introductory information on

installing Windows software.
Appendix C: Upgrading Consoles This appendix explains common

console upgrades.
Appendix D: Other Network Solutions Shows several supported

alternative network configurations.
Index Contains an index of the information in this manual.
Take the time to read through this document before attempting to install, configure,
or use the hardware or software.
Related Documents
Other PROVOX documents that may be helpful are listed below. See your Emerson
Process Management representative or sales office for a complete list of available
documents.
Note
Introduction
Retain all of your PROVOX Operator Console P3.x documentation, even after
converting to DeltaV Operate for PROVOX software. Under some circumstances you
may need to refer to it after conversion.
1-11
Online Documentation
All of the DeltaV Operate for PROVOX Console documentation is available online
from any operator station or Console Data Server. The Books Online are accessible
from the Start menu on both Console Data Servers and DeltaV Operator Stations.
The Books Online that support DeltaV Operate for PROVOX systems included with
the software are:
Getting Started With DeltaV Operate for PROVOX Consoles

The online version of the printed getting started manual. It contains information
on modifying Operator Workplace configurations for use with the console,
differences in operation between Operator Workplace and the Console, and
installing the console software and Windows software.
Configuring PROVOX Operator Console Software

The configuration manual that supports this release of the console.
Using DeltaV Operate for PROVOX Consoles

The user manual for the console.
In addition, the DeltaV Operator Stations have the complete DeltaV Books Online
available. For information on creating displays and using DeltaV Operate, refer to the
DeltaV documentation.
Printed Documentation
Printed copies of DeltaV and DeltaV Operate for PROVOX manuals are available
from your sales representative:
Configuring PROVOX Operator Console Software (CE:NT2100) (Part number

D2C01691002)
This revision of the DeltaV Operate for PROVOX software is supported by the
PROVOX Operator Console configuration manual. This manual explains the
database configuration differences between Operator Workplace and PROVUE
consoles and PROVOX Operator Consoles.
The changes to a PROVOX Operator Console configuration required to be
compatible with the DeltaV Operate for PROVOX software are detailed in
1-12
Chapter 6, Database Configuration, of the Getting Started with DeltaV Operate for
PROVOX Consoles manual.
Getting Started with DeltaV Operate for PROVOX Consoles (Part number
D3P01861802)
This Manual
Using DeltaV Operate for PROVOX Consoles (Part number D4U01861802)

The user manual for the console explains the user interface of the console
software and how you operate a plant using the controls and applications
included in the console.
Where to Find Answers for Product and Document Questions

If you believe that this product is not performing as expected, or if you have
comments about this manual, please contact your Emerson Process Management
representative or sales office.
We also appreciate your suggestions on ways to improve any page of the manual.
Please mark your suggestions on a copy of the page. Thank you for providing this
information.
Introduction
1-13
1-14
Chapter 2
Product Overview
Introduction
This section provides an overview of the components of the DeltaV Operate for
PROVOX Console.
Hardware and Software Components

The console consists of a DeltaV Operate for PROVOX Data Server and as many as
six DeltaV Operate Stations or PROVOX Operator Console Migration Stations. If
you are using DeltaV Operate for PROVOX Consoles to operate both DeltaV and
PROVOX controllers, Emerson Process Management strongly recommends that the
consoles use dual monitor workstations. The dual monitors ensure that operators
have sufficient display area to access to all pertinent information and controls for
both systems simultaneously.
Console Equipment List

The DeltaV Operate for PROVOX Console provides connections from the Console
Data Server through an Ethernet Switch to as many as six DeltaV Operator Stations.
The Console Data Server is linked to the PROVOX highway system through the
Type DH6032 Highway Data Link (HDL).
Each Console Data Server consists of the following components:
Product Overview
Server Computer (with network interface controller (NIC) cards installed) with
Microsoft Server, Microsoft Internet Explorer, and console software installed.
Includes mouse and keyboard.
One Type DH6032 Highway Data Link (HDL)
One License Module
One Ethernet Switch (Refer to the DeltaV documentation for information on the
switch types available)
One Type NT7301 1000 VA Uninterruptible Power Supply (UPS) with slide rails
for mounting in a standard 19-inch rack-mount equipment cabinet (optional;
recommended)
Category 5 screened cables with twisted pair connectors

(one for each of the following connections: HDL/Server, Server/switch)
2-1
Serial cable for the Ethernet Switch (included with switch)
One color monitor
Each Console Data Server can support one to six DeltaV Operator Stations.
The following figure shows a typical layout for a console.
Note
2-2
The figures in this manual are conceptual only. Your systems hardware may appear
different than that shown.
Figure 2-1
Typical Console Connections

The DeltaV Operate for PROVOX consoles use standard DeltaV Operator Stations.
The only differences are that the operator stations use the integrated network
Product Overview
2-3
interface port to support the connection to the DeltaV Operate for PROVOX Data
Server and they have the DeltaV Operate for PROVOX Upgrade installed.
For information on installing and setting up standard DeltaV Operator Stations, refer
to the section Installing the DeltaV Workstation in the DeltaV manual Installing your
DeltaV Automation System.
For information on installing the DeltaV Operate for PROVOX software on DeltaV
Operator Stations, refer to Appendix A of this manual.
Console Software
The Console Data Server software includes the following components:
Microsoft Windows Server software installation disks
DeltaV Operate for PROVOX Software installation disk
DeltaV Operate for PROVOX License media
Microsoft Internet Information Server (IIS)
Microsoft Internet Explorer (with appropriate Service Pack)
Driver software
Adobe Acrobat Reader
Note that some of the software may be on its own separate media or included on the
console software installation disk.
Communications Equipment
The communications equipment permits the servers and workstations to
communicate with each other and to connect to the data highway. There are two types
of communications devices associated with the DeltaV Operate for PROVOX
Console:
Type DH6032 Highway Data Link (HDL)
Ethernet Switch
Type DH6032 Highway Data Link

The Type DH6032 HDL is a microprocessor-based communications device that
provides a secure interface to the PROVOX Highway.
2-4
The HDL provides a dedicated Ethernet connection that is not shared with other
non-console or non-host computer-related network traffic. This allows the console
computer to communicate with PROVOX control devices in a reliable and responsive
fashion.
Each self-contained Type DH6032 HDL includes a:
32-bit microprocessor unit (MPU)
Redundant assembly for the PROVOX Highway
Ethernet interface assembly
The HDL contains a local operator interface composed of a four-character

alphanumeric LED status display and five pushbuttons. You can use the pushbuttons
and status display to verify locally the status of the HDL.
The HDL uses standard 19-inch (483 mm) mounting rails. It requires 3.25 inches
(82.88 mm) of vertical space. The HDL chassis requires front access for servicing.
Ethernet Switch (Twisted Pair)

The Ethernet Switch equipment includes:
One 24-Port Twisted Pair Ethernet Switch with shielded RJ45 connectors.
Power cable
Rack mount kit
A shielded twisted pair (10BaseT) cable assembly, up to 328 feet (100 m), can be
attached to each of these connectors on the switch. The twisted pair cable assembly
must be category 5 screened twisted pair cable that is ground isolated on one end. The
standard cable lengths from 20 ft. (6.1 m) to 100 ft. (30.6 m) are available from
Emerson Process Management.
The switch provides a bridge-like function that is necessary to keep individual console
area Ethernet traffic isolated from other console areas to maintain low, stable, traffic
levels within each console area.
Manage IP addresses in the switch over the network or from a serial terminal
connected to the switch. See DeltaV Books Online for examples of switch
management. Note that DeltaV Operate for PROVOX network IP addresses are
different than DeltaV network IP addresses.
Product Overview
2-5
Note
Do not connect the DeltaV Operate for PROVOX network switch to the DeltaV
network switch or mix IP addresses between the two networks.
Ethernet Cables
DeltaV Operate for PROVOX consoles use Category 5 shielded (screened) twisted
pair Ethernet cables in a number of places. There are two types of cables available:
straight through and crossover.
Straight through cables are used for most connections. Crossover cables are required
to connect two switches.
The standard length cable is 30 feet (9.15 m). Optional assembled cable lengths
available are 20, 40, 50, 75, and 100 ft. (6.1, 12.2, 15.25, 22.87, and 30.6 m).
See DeltaV Books Online for more information on cables.
2-6
Chapter 3
Initial Hardware Setup

This section explains how to install the hardware for DeltaV Operate for PROVOX
Data Servers (also known as Console Data Servers) and connect the servers to DeltaV
Operator Stations. If you already have a PROVOX Operator Console installed, you
may want to review this section to ensure that your servers are installed as described.
This section does not discuss migration stations (PROVOX Operator Console
Operator Stations upgraded with DeltaV Operate for PROVOX software). The
hardware setup for these workstations is identical to the setup described in the
PROVOX Operator Console P3.0 installation manual.
Refer to the section Installing the DeltaV Workstation in the DeltaV Books Online for
instructions on setting up DeltaV Operator Stations. The only additional information
in this manual about DeltaV Operator Stations is the network interface controller
(NIC) binding order.
This section does not explain how to install and set up the DeltaV Operate for
PROVOX software. Refer to Appendix A and Chapter 5 of this manual for that
information.
This section assumes your DeltaV network is installed and operating correctly and
that you are installing DeltaV Operate for PROVOX for the first time. If you already
have PROVOX Operator Console P3.0 installed, modify these instructions
accordingly.
Hardware Variations
The DeltaV Operate for PROVOX Data Server has evolved from the PROVOX
Operator Console Data Server. Since the initial release of the PROVOX Operator
Console, the hardware platform for the servers has changed and will continue to
change. It is therefore important that you install, set up hardware, install software (as
needed), and set up the software as required by your particular hardware.
Servers
The network interface controller (NIC) card and video hardware have changed several
times.
Refer to DeltaV documentation for information on DeltaV Operator Stations.
3-1
support.dell.com
For information on your specific hardware, visit the Dell support web site,
support.dell.com. Each Dell computer has a System Service Tag. Enter this tag
number in the Dell support web site to see information specific for your computer,
including drivers and utilities available.
Note
The instructions in this section are specific for the hardware and software being shipped
when this manual was created. If console hardware or software changes subsequently, you
may need to modify these instructions accordingly.
Pay particular attention to network interface and video hardware and drivers. These
cards and drivers have changed from the previous release and will continue to change.
The instructions in this section apply generally to NIC hardware and drivers, but do not
apply directly to hardware and software of earlier releases of PROVOX Operator
Console that you may be upgrading for use with a DeltaV Operate for PROVOX
console.
System Setup
The Microsoft Windows based DeltaV Operate for PROVOX Console is
implemented with a networked architecture. The following figure is a schematic of a
combined DeltaV Operate and DeltaV Operate for PROVOX installation.
3-2
Figure 3-1
Note
DeltaV Operate for PROVOX Network Schematic
To simplify the figure, redundant DeltaV and PROVOX control schemes are not
shown.
The console consists of a Windows-based Console Data Server connected to as many
as six DeltaV Operator Stations (including a DeltaV ProfessionalPLUS workstation)
through a dedicated Ethernet. The Console Data Server is connected to the
PROVOX Data Highway through a dedicated Ethernet connection to the Highway
Data Link (HDL).
The console can be part of a Primary/Secondary solution that consists of two
consoles linked by either a twisted pair or fiber optic Ethernet connection. Refer to
Appendix D of this manual for more information on other network configurations.
3-3
The Console Data Server and the DeltaV Operator Stations include Windows
software and DeltaV Operate for PROVOX software.
The following subsections provide the steps for setting up the console.
Note
Setting Up Consoles
The console components that make up a DeltaV Operate for PROVOX console
consist of a Data Server, an HDL, an Ethernet switch, and one to six DeltaV
Operator Stations. The server contains two Ethernet network interface controller
(NIC) cards: one connects to the HDL and the other connects to the switch. The
following figure represents a typical console installation.
3-4
Figure 3-2
Typical Console System Configuration
To set up the hardware for a console, perform the following steps:

1. Install the equipment (refer to Equipping the Server Cabinet on page 3-7).
3-5
2. Connect the power and ground cables inside the server cabinet (refer to Cabling
for the Server Cabinet on page 3-8).
3. Perform a power-up test of the server cabinet (refer to Power-up Test Sequence:
Server Cabinet on page 3-12).
4. Interconnect the server equipment (refer to Interconnecting Server Equipment
on page 3-13).
5. Change the Windows Administrator Account Password on all servers (refer to
Changing the Windows Administrator Account Password on page 3-18).
6. Set the network parameters for the Console Data Server (refer to Setting the
Console Data Server Parameters on page 3-19).
7. Configure the Ethernet switch (refer to Configuring the Ethernet Switch on
page 3-23).
8. Test the network connections between the Console Data Server and the DeltaV
Operator Stations (refer to Test the Network Connections on page 3-33).
Setting Up Console Data Servers

Note
The optional Type NT7210 Server Cabinet has been discontinued. Use the following
sections as a guide when installing PROVOX server components in a custom cabinet.
Modify these instructions to fit your installation requirements. Consult with your cabinet
manufacturer to ensure your cabinet meets all physical, electrical, safety, and
environmental specifications for the equipment to be installed.
Note
Rack-mountable server computer options now provided by Emerson Process

Management are not compatible with the discontinued Type NT7210 Server Cabinet.
Do not use this cabinet for these server computer options.
This subsection explains how to set up the hardware for tower Console Data Servers
in cabinets that were available with PROVOX Operator Consoles. If you do not have
cabinets or tower Console Data Servers, modify the instructions to fit your
installation. The tasks covered are:
3-6
Equipping the server cabinet
Power cabling the server cabinet
Power up testing the server cabinet
Interconnecting the server hardware

Equipping the Server Cabinet

Equipment is installed in the optional server cabinet in the following order:
1. (Optional) 1000 VA Uninterruptible Power Supply (UPS) - topmost position
2. Type DH6032 Highway Data Link (HDL) second from top
3. Ethernet switch third from top
4. Server Computer bottom position
The following explains each of these in detail.
Perform the following procedure to install the console equipment in each server
cabinet.
Installing the Server UPS
Note
If your equipment does not include the optional UPS, connect the system to protected
plant power. Refer to Cabling for the Server Cabinet on page 3-8 for more information.
1. Attach the device portion of the slide rail kit to the UPS per the instructions with
the kit.
2. Attach the cabinet-portion of the slide rail kit to the cabinet rails. The top side of
the rail brackets should be installed in the fifth screw-hole location down from
the top of the vertical rails in the cabinet on front and rear rails.
Note
The UPS is heavy (approximately 60 pounds), so a second person is required to help

position the UPS on the slide rails in the cabinet.
3. Install the UPS on the slide rails and push the UPS all the way into the cabinet
until seated.
4. Secure the front panel of the UPS to the front cabinet rails with the four screws
provided.
Installing the HDL
5. Position the HDL directly under the UPS. Secure the HDL to the cabinet rails
with the four screws provided.
6. Attach the rack-mount brackets to the switch with the screws provided.
7. Position the switch directly under the HDL. Secure the switch to the cabinet rails
with the four screws provided.
3-7
Installing the Server Computer

8. Raise the clamp lever on the server brace over the sliding shelf directly under the
switch (at the bottom of the cabinet).
9. Position the server on the sliding shelf in the retention pan.
10. Lower the clamp lever to secure the server to the brace.
Cabling for the Server Cabinet

Use the following procedure to connect the power and peripheral cables for the
server cabinet and the installed equipment. For more information on this procedure,
see the manual AC and DC Power and Ground Wiring (PN1:003).
Caution
Verify that power is turned off for all installed equipment. Do not plug in any power cords
or attach building power to the cabinet until the following items are complete.
Attaching Ground Wires To the Server Cabinet

1. Attach the ground wires as shown in the following figure.
3-8
Figure 3-3
Ground Connections: Server Cabinet
Power Cabling the Server Cabinet

Use the following procedure to connect power cables to the server cabinet.
3-9
Note
Verify that power is not turned on for your input power cable before you attach it to the
cabinet input terminal block.
Caution
When working with the UPS be sure to shut off battery power during installation. Refer to
the UPS manual for specific instructions.
2. Attach the input power cord from the breaker panel to the terminal block of the
cabinet be sure to follow the labels on the terminal block for proper
orientation of LINE, NEUTRAL, and GROUND connections. Be sure to
replace the protective cover on the input power terminal block.
Note
Cabinets for 230 VAC installations have two five-outlet power strips. This requires
two input power connections to the cabinet.
3. Verify that all devices containing a power switch are set to the OFF position,
including the UPS. The Ethernet switch does not have a power switch.
3-10
Figure 3-4
Power Connections: Server Cabinet with Monitor
4. If you are installing the optional UPS in the cabinet, verify that the power selection switch
located on the rear of the UPS is set to the proper input voltage for your plant site. Then
connect all power cords (including the fan power cords and monitor power cord)
to the output sockets of the UPS.
If you are not installing the optional UPS in the cabinet, proceed by connecting all
power cords (including the fan power cords) to the power strip.
5. Leave enough slack in the power cable to allow the server to slide fully out on the
shelf. Secure the power cord to the sliding shelf with the wire ties provided while
the shelf is fully extended so that the cord will not become disconnected when
the shelf is pulled out. Secure all other power cords to the cabinet support rails
with the wire ties provided.
3-11
6. Verify that if the server monitor you are using has a voltage select switch that it is
set to the proper input voltage and frequency for your plant site. Route the
monitor power cable through one of the openings in the top of the cabinet.
Note
There are two openings in the top of the server cabinet. When routing cables, route the
monitor power cable through one opening. Route the video, keyboard, and mouse cables
through the other opening.
7. Attach the power cord supplied with the UPS to the UPS input power socket and
then to the cabinet power strip. If you are installing the optional UPS, it should
be the only device directly connected to the power strip.
Attaching Monitor, Keyboard, and Mouse Cables
8. Attach the video cable to the monitor and route this cable, the keyboard cable,
and mouse cable through the other opening in the top of the cabinet. Securely
fasten these cables to the sliding shelf of the server so that when the shelf is fully
extended, the cables do not become unplugged from the server.
Power-up Test Sequence: Server Cabinet

Perform the following procedure to check the server cabinet power system. This is
necessary before attaching the remaining inter-cabinet wiring (such as twisted pair and
Highway cables).
1. Perform the following checklist to ensure operator safety and prevent equipment
damage.
Is the ground wire securely fastened to the PROVOX Instrumentation
Ground and to the ground lug of the server cabinet?
Is the input power wire attached to a properly wired circuit breaker of your
building power?
Is the input power wire correctly attached to the LINE, NEUTRAL, and
GROUND tabs on the input terminal block?
Is the UPS rear panel input voltage select switch set to your plant voltage?
Are all the power cords securely fastened to the cabinets support rails?
Are power switches on all devices in the cabinet, including the monitor on top
of the cabinet, set to the OFF position?
After you have verified all the previous conditions, perform the following:
2. Power up the breaker panel.
3-12
3. Turn on the 1000 VA UPS. The Ethernet switch powers up and performs a self
test.
Note
If no LED is illuminated, there is a power problem or self test failure of the device.
Check the power cord connections and breaker panel. The switch user manual contains
information about power-up LED status.
4. Inspect the cabinet fan operation. Both fans should be free running. Filters
should be installed and clean.
5. Turn on the HDL. The display panel on front of the HDL and the power LED
on the rear of the HDL will illuminate. Because Ethernet and Highway cables are
not attached yet, error indications may appear. For this power up test, ignore any
error indications.
6. Turn on the Console Data Server monitor. Depending on the monitor type used
either an amber or green LED will illuminate indicating that the monitor is
powered. There will not be any display because the server has not been powered
up yet this is OK, this test is a quick check of power to the monitor.
7. Turn on the server. In a few seconds power-up information will start to appear
on the monitor. Since the Ethernet and Highway cables are not yet installed,
some error information may appear. This is OK. Let the system complete the
power up sequence. When complete, do an orderly shut down of the server.
8. Turn off the server monitor and the HDL.
The 1000 VA UPS will still be providing power to the Ethernet switches and
cabinet fans because these devices do not have power switches.
Interconnecting Server Equipment

Use the following procedure to interconnect the server equipment: Console Data
Servers, Highway Data Links, and Ethernet switches.
Note
Make sure the HDL is turned off before cabling it. It is OK to connect/disconnect
Ethernet cables to the switch while it is turned on.
Connecting the HDL
1. Insert the black metal connector of a Category 5 screened (shielded) twisted pair
cable in the twisted pair port marked LAN on the front left of the HDL.
2. Insert the blue plastic connector of the cable in the twisted pair port in the top
network interface controller (NIC) card on the server.
3-13
The following figure shows the proper connections.
Figure 3-5
Server/HDL Connection
Connecting the Switch

3. Insert the blue plastic connector of a Category 5 screened (shielded) twisted pair
cable in the twisted pair port in the bottom NIC on the server.
4. Insert the black metal connector of the cable in a twisted pair port of the switch.
3-14
Figure 3-6
Server/Switch Connection
Connecting the HDL to the Highway

5. Connect the data highway cables to the HDL at the ports titled Primary Comm
and Secondary Comm.
Connect the other ends to the Highway taps.
3-15
Figure 3-7
Note
HDL/PROVOX Highway Connection
If a torque wrench is not available, first finger-tighten all Highway II connectors, then
place a six inch open end wrench on the hex nut and rotate wrench one inch.
Connecting DeltaV Operator Stations to Ethernet Switches
Use the following procedure to connect DeltaV Operator Stations to the Ethernet
switch.
For each DeltaV Operator Station:
1. Insert the black metal connector of a Category 5 screened (shielded) twisted pair
cable in the switch twisted pair port.
2. Insert the blue plastic connector of the cable into the twisted pair port of the
integrated Ethernet NIC port of the DeltaV Operator Station.
3-16
Figure 3-8
DeltaV Operator Station/Switch Connection
System Configuration: Console

The following table shows a suggested naming and IP addressing scheme used for the
PROVOX network.
3-17
Table 3-1 Naming and IP Addressing

Setup Parameter
First
Second
Console Data Server

Name
PBASE10
PBASE11
Ethernet card [1] (connected to HDL)
192.168.22.10
192.168.22.11
HDL
192.168.22.2
192.168.22.3
Ethernet card [2] (connected to switch)
192.168.21.10
192.168.21.11

Name
Set up by DeltaV Installation
Ethernet card [3]
192.168.21.30
Ethernet card [2]
Ethernet card [1]
192.168.21.31
The First and Second columns illustrate how the naming and numbering of multiple
servers and operator stations are implemented.
Note
All of the IP addresses and node names used in this manual follow the above scheme and
are from the addresses set aside for private networks (networks that do not communicate
with other networks). If your plant uses a different addressing scheme, change the IP
addresses and node names accordingly.
The following subsections explain how to set the required values.
The Windows installation includes a default administrator account with the name and
password Administrator. This account provides access to the consoles even if Emerson
Process Management software is removed from the hard disk. The Administrator account
is a superuser and you should use this account only if you need its access.
Changing the Windows Administrator Account Password

Perform the following steps to change the default password for the Windows
Administrator account:
Note
Perform the following steps on every Console Data Server.

1. Log on to Windows as Administrator.
3-18
2. Press Ctrl Alt Del.

The Windows Security dialog appears.
3. Click on the Change Password button.
The Change Password dialog appears.
4. Change the password and click OK.
Note
Remember this password. If you forget this password you will be unable to log on as
Administrator.
The Windows Security dialog appears.
5. Click on Cancel.
The Windows Desktop appears.
Setting the Console Data Server Parameters

You must ensure that network parameters are set correctly for all Console Data
Servers and DeltaV Operator Stations. This section explains the settings for the two
network connections in the server.
Configuring the Computer Name
1. Log on to Windows using the Administrator account.
2. Open the System Properties dialog.
3. Select the Computer Name tab.
4. Click the Change button.
The Computer Name Changes dialog appears.
3-19
5. Change the name of the computer as required.

6. Click OK to accept your changes.
7. Click OK on the System properties dialog to close it.
Configuring the HDL Network Connection
8. Open the Network Connections dialog.
9. Temporarily disconnect the network cable at the HDL.
An indication that the network cable is unplugged appears in the Network
Connections dialog. Note which connection is affected. This is the network
connection to the HDL.
10. Reconnect the network cable at the HDL.
3-20
11. Select the HDL network connection in the Network Connections dialog, then
select Properties from the right click menu.
The connection Properties dialog appears.
12. Highlight the internet protocol in the list.
In Windows Server 2008 -- Internet Protocol Version 4 (TCP/IPv4).
13. Click Properties.
The internet protocol Properties dialog appears.
Verify the IP Address
14. Select Use the following IP address.
15. If this is the first Console Data Server, set the IP address to 192.168.22.10. For
each additional Console Data Server in your installation increment the IP
address by one (192.168.22.11, 192.168.22.12, and so on).
Note
The IP addresses used in this section are in the range of addresses reserved for private
networks (that is, networks that are not accessible from other networks). If you are using
a different addressing scheme, adjust the IP addresses accordingly.
Whether you use the address scheme shown in the examples or your own address scheme,
you must make sure that you do not use the same address for more than one piece of
equipment.
16. Set the Subnet Mask to 255.255.255.0.
17. Leave the DNS server fields blank.
18. Click the Advanced button.
The Advanced TCP/IP Settings dialog appears.
19. Select the DNS tab.
Verify the DNS tab is blank
20. Select the WINS tab.
21. Make sure Enable LMHOSTS and the default NetBIOS setting are selected.
Leave other fields blank
22. Click OK on the Advanced TCP/IP Settings dialog to accept your changes and
close the dialog.
3-21
23. Click OK on the internet protocol Properties dialog to accept your changes and
close the dialog.
24. Click OK or Close on the connection Properties dialog to accept your changes
and close the dialog.
Configuring the Ethernet Switch Network Connection
You have set all the parameters for the HDL network connection. Now you must set
the parameters for the Ethernet switch connection.
25. From the Network Connections window, select the other network connection,
then select Properties from the right click menu.
Internet Protocol Version 4 (TCP/IPv4).
29. If your installation has multiple Console Data Servers, set the IP address of the
second connection for the first one to 192.168.21.10. Increment the IP addresses
of subsequent servers by one (192.168.21.11, 192.168.21.12, and so on).
30. Set the subnet mask to 255.255.255.0.
Leave other fields blank.
3-22
close the dialog.
close the dialog.
Setting the NIC Binding Order
39. With the Network Connections dialog open, if the menu bar is not visible press
and release the Alt key.
The menu bar appears
40. From the menu select Advanced | Advanced Settings.
The Advanced Settings dialog appears.
41. Set the binding order for your installation according to the following.
No Plant LAN
With Plant LAN
HDL Connection
PROVOX (switch) connection
HDL Connection
Plant LAN

43. Close the Network Connections dialog.
Configuring the Ethernet Switch

DeltaV systems support a specific version of switch software and a specific switch
configuration. Other versions of the switch software or an improperly configured
switch could cause serious operating problems with the DeltaV system.
Note
Switches ordered from Emerson Process Management are shipped with the supported
software version and are configured at the Emerson factory to operate properly with the
DeltaV system. To ensure proper switch configuration and the correct switch software for
your DeltaV system, purchase the switch through normal Emerson channels. The
DeltaV-supported software version of the switch may not be the version that is currently
shipping on switches obtained from other vendors.
3-23
To verify the configuration of a switch supplied by Emerson Process management,

refer to the System Administration and Maintenance manual in the DeltaV Books
Online. This documentation includes examples of correct DeltaV-specific switch
configuration for the supported revision level of the switch software. Emerson
Process Management does not provide the switch operating software separately for
field configuration. If you purchase switches from sources other than Emerson
Process Management, you must configure them to DeltaV specifications after
verifying with your supplier that the switch software is at the supported revision level.
See the DeltaV Books Online section titled Administration and Maintenance for
information about connecting to and managing switch software. No additional switch
configuration is required for Emerson-supplied switches to operate properly.
However, if other Ethernet equipment beyond what is shown in this manual is
connected to the switch, such as DeltaV qualified fiber optic media converters, or if
redundant or "Etherchannel" links are needed, or if network diagnostics are used for
troubleshooting purposes, some additional configuration is required. Additionally, the
IP addressing scheme (address range and network numbers) for regular DeltaV
Operator Stations is different than the address range and network numbers for
DeltaV Operate for PROVOX equipment. Do not mix addresses or connect the
switches between these two systems.
In addition to switch configuration examples in DeltaV Books Online, the DeltaV
Operate for PROVOX system allows an additional switch configuration for using
redundant links between the Ethernet switches to set up redundant Console Data
Servers. This is referred to in switch documentation as Etherchannel links. Use the
following procedure to configure a redundant Etherchannel link between two
switches:
Configuring Redundant Load-Sharing Links between Switches (Configuring
Etherchannels)
3-24
Caution
You must perform this procedure before connecting redundant cables between switches or the
result will be an Ethernet loop, causing the network to become unusable. Perform this
procedure on both switches in the link before connecting the redundant cables between them.
Note
Perform this procedure using a serial terminal and serial cable connection between a PC's
Com 1 port and the serial Console Port of the switch, or if the switch already has an IP
address assigned to it, use a Telnet session to the switch IP address.
The following is an example using the serial terminal method. The serial terminal is
referred to as a management PC in DeltaV documentation. See the DeltaV Books
Online for information on verifying the Emerson factory configuration defaults for
the switches and serial terminal management PC setup.
1. Connect the serial cable between the switch's Console port and the management
PC's Com 1 port.
2. Open a HyperTerminal session.
3. Press Enter a few times on the keyboard until the switch responds with the
Switch > prompt.
4. Enter enable at the > prompt. The following prompt appears:
Switch#
5. Enter configure terminal at the prompt. The following appears:
Enter configuration commands, one per line.
CNTL/Z.
End with
Switch(config)#
Note
This example assumes ports 23 and 24 are used for a redundant link between switches.
6. Enter interface range fastethernet0/23 -24 at the prompt. The following appears:
Switch(config-if-range)#
7. Enter channel-group 1 mode desirable at the prompt. The following appears:
Creating a port-channel interface Port-channel 1
8. Enter end at the prompt. The following appears:
Switch#
2d20h: %SYS-5-CONFIG_I: Configured from console by
console
9. Press Enter. The following appears:
Switch#
3-25
Caution
You must save this configuration or the next time the switch reboots, it returns to the default
configuration. If redundant cables are attached, the reboot results in an Ethernet loop causing
unpredictable operation and network failure.
10. At the Switch# prompt, enter write memory. The following appears:
Building configuration...
[OK]
Switch#
11. To verify that the Etherchannel is configured properly, at the Switch# prompt
enter show configuration. Verify that near the beginning of the configuration file
these lines are displayed:
interface Port-channel1
no ip address
12. Continue to press Enter until the Etherchannel ports that were configured, in
this case ports 23 and 24, each display this line as part of their port configuration:
channel-group 1 mode desirable
The following is an actual port example:
!
interface FastEthernet0/23
switchport mode access
switchport nonegotiate
no ip address
no cdp enable
!
3-26
no ip address
no cdp enable
13. When verification is complete, continue to press Enter until the Switch# prompt
is displayed:
Switch#
Caution
Repeat this process for the switch on the opposite side of the link before connecting the two
switches with redundant cables. If you do not, unpredictable operation and network failure
occurs.
14. This completes the Etherchannel configuration for the first switch. Repeat steps
1 through 14 for the remaining switch in this pair.
If you are using the Cisco 2960-24TC-L switch with the GLC-GE-100FX fiber optic
SFP module for fiber optic Etherchannel, some additional switch port configuration
is required when using a 100BASE FX SFP module in a gigabit slot. The port number
listed below (interface gigabitethernet0/1) is an example only. This entry should
reflect the actual port number to be configured. For the 2960-24-TC-L this could be
0/1 or 0/2.
Once the GLC-GE-100FX SFP module has been configured for use in a giga-bit slot
then the same previously documented steps for Redundant Load-Sharing ports
applies to these ports:
Switch>enable
*****
Switch#config t
Switch(config)# interface gigabitethernet0/1
Switch(config-if)#
At the Switch(config-if)# prompt enter the following two commands
media-type sfp
duplex full
3-27
Switch(Config-if)#end
System displays the following:
Switch#
xx:xx:xx: %SYS-5-CONFIG_I: Configured from console
by console
press enter
Switch#write mem
Building configuration. . .
[OK]
Switch#
Removing Redundant Load-sharing Links Between Switches (Removing
Etherchannels)
Caution
You must disconnect the redundant cables between switches before performing these steps or
the result will be an Ethernet loop, causing the network to become unusable. Perform this
procedure on both switches in the link before reconnecting any cable between the two switches.
1. Connect the serial cable between the switch's Console port and the management
PC's Com 1 port.
2. Open a HyperTerminal session.
3. Press Enter a few times on the keyboard, until the switch responds with the
switch > prompt.
4. Enter enable at the prompt. The following appears:
Switch#
Enter configuration commands, one per line. End with
CNTL/Z.
Switch(config)#
6. Enter interface range fastethernet0/23 -24 at the prompt. The following appears:
3-28
7. Enter no channel-group 1 at the prompt. The following appears:
Switch#
console
Switch#
Switch(config)#
11. Enter interface vlan 1 at the prompt. The following appears:
Switch(config-if)#
12. Enter no interface port-channel 1 at the prompt. The following appears:
Switch(config)#
Switch#
console
Switch#
Caution
You must save this configuration to remove the Etherchannel configuration or the next time
the switch reboots, the Etherchannel configuration is loaded, which is an invalid configuration
that results in an Ethernet loop causing unpredictable operation and network failure.
3-29
15. At the Switch# prompt, enter write memory. The following appears:
Building configuration...
[OK]
Switch#
16. To verify that the Etherchannel configuration has been removed, at the Switch#
prompt enter show configuration, Verify that near the beginning of the
configuration file the following lines have been removed:
interface Port-channel1
no ip address
17. Continue to press Enter until the Etherchannel ports that were originally
configured for Etherchannel, in this case ports 23 and 24, each show that the
following line has been removed from their port configuration:
The following is an actual port example:
!
no ip address
no cdp enable
!
no ip address
no cdp enable
18. When verification is complete, continue to press Enter until the Switch#
prompt appears:
Switch#
3-30
Caution
Repeat this Etherchannel removal process for the switch on the opposite end of the link before
using the ports again for any other purpose.
19. This completes removing the Etherchannel configuration for the first switch.
Repeat steps 1 through 18 for the remaining switch in this pair.
Follow the procedure in the DeltaV Books Online for entering IP addresses, but use
the DeltaV Operate for PROVOX addressing scheme
Setting DeltaV Operator Station Parameters

At each DeltaV Operator Station, perform the following to verify and set (if
necessary) the network parameters:
1. Log on to Windows using the Administrator account.
2. Open the NetworkConnections dialog.
DeltaV Operator Stations should have three network connections enabled. Two
are used in the DeltaV network.
3. Select the network connection that is not being used by the DeltaV network (this
connection may be labeled Plant LAN), then select Properties from the right
click menu.
Internet Protocol Version 4 (TCP/IPv4).
Note
Make sure you do not disturb the settings for the adapters used to connect the DeltaV
Operator Station to the DeltaV network.
3-31
7. For the first operator station enter the IP address 192.168.21.30. If you are
setting up additional operator stations, increment the IP address by one for each
subsequent operator station.
8. Enter a subnet mask of 255.255.255.0.
Leave other fields blank.
close the dialog.
close the dialog.
Setting the NIC Binding Order
17. With the Network Connections dialog open, if the menu bar is not visible press
and release the Alt key.
The menu bar appears
18. From the menu select Advanced | Advanced Settings.
The Advanced Settings dialog appears.
3-32
19. Set the binding order for your installation according to the following.
No Plant LAN
DeltaV Secondary connection
DeltaV Primary connection
With Plant LAN

DeltaV Secondary connection
Plant LAN
DeltaV Primary connection

21. Close the Network Connections dialog.
Test the Network Connections

Note
After setting the network parameters on all the DeltaV Operator Stations, return to the
Console Data Server to test the network connections to the operator stations.
1. Log on to the server as Administrator.
2. Open a Command Prompt window by selecting Start | Programs | Accessories
| Command Prompt.
3. From the Command Prompt enter the following command:
C:> ping DeltaV_Operator_Station_name
4. If the server and DeltaV Operator Station are communicating, messages similar
to the following appear:
Pinging nodename [nnn.nnn.nnn.nnn] with 32 bytes of
data:
Reply from nnn.nnn.nnn.nnn: bytes=nn time=nn TTL=nnn
The messages you see will have actual values in place of nodename and the
numbers.
3-33
Note
If the system displays the message Request timed out for every operator station, the
HDL and switch may be connected to the wrong NIC cards at the back of the server.
Switch the connections and try again.
If the system displays the message Request timed out for some operator stations,
review the Network parameters in the problem station(s) and try again.
Now that you have the console hardware installed, connected, and tested, you can
proceed to Appendix A of this manual for information on installing the console
software.
Setting Up Primary/Secondary Consoles

The primary/secondary console configuration consists of two consoles connected at
their switches by an Ethernet cable. The following figure represents a typical Ethernet
primary/secondary console installation that uses redundant Etherchannel links
between the two switches.
3-34
Figure 3-9
Typical Primary/Secondary Console System
3-35
To set up the primary and secondary consoles, perform the following steps:
1. Perform the installation procedure for consoles to install the Primary Server.
2. Repeat step 1 to install the Secondary Server.
3. Connect a Category 5 twisted pair cable to the 100mb port in the front of the
switch on the primary console. Connect the opposite end of the twisted pair
cable to the 100mb port in the front of the switch on the secondary console.
4. After configuring the Etherchannel on both switches, connect two Category 5
twisted pair cables between the two Etherchannel ports on the switches.
3-36
Chapter 4
Saving Console Information
Introduction
This section provides an overview of the types and locations of information you
should consider backing up periodically to ensure that you can restore your consoles
should you need to replace console hardware or re-install console software. If you are
upgrading to DeltaV Operate for PROVOX consoles from PROVOX Operator
Consoles, refer to the PROVOX Operator Console documentation for information
on saving console information before you upgrade.
The table describes information that is used in several ways, such as for regulatory
purposes, in disaster recovery procedures, and for operations.
Save the information listed in the following table using the backup method you prefer.
You should consider the simple backup for one-time saves and the complex backup
for day-in and day-out operations.
Table 4-1 Console Information to Back Up
Information
Directory
Server/
operator
station
Extensions
Simple
Backup
Complex
Backup
Source
Console
Properties
Both
--
--
Paper
documentation
of Network
addresses
--
Originally
entered at
installation
License Info
Both
--
--
Diskette
--
Contact Rep or
FSO
Device
Drivers
Server1
--
--
Diskette
Dell
Accessories
Program Disk
Maker
Tape Backup
after installation
Contact Rep or
FSO
Operating
System with
extensions
Server1
--
--
Install disks
Dell
Accessories
Program
Repair Disk
Tape Backup
after installation
Contact Rep
DeltaV
Operate for
PROVOX
Software
Server1
--
--
Install disks
Tape Backup
after installation
Contact Rep
4-1
Table 4-1 Console Information to Back Up

Information
Server/
operator
station
Directory
Extensions
Simple
Backup
Complex
Backup
Source
Event Journal
Server
C:\POC\spooler
CSV
copy files to
another
machine
Daily or periodic
backup to tape
Information
about the live
process. This is
unique
information that
needs to be
managed
locally.
Trend Views
operator
station
C:\POC\trendpic
PTV
save files to
server
Daily or periodic
backup to tape
User created.
Notes:
1. Refer to the DeltaV Maintenance manual for information on saving this information for DeltaV Operator
Stations
Console Properties to Save

Settings for the Console Data Server and operator stations are defaults that are used
when the software is installed for the first time. If you are reinstalling the software and
are using customized operator console settings, be sure to back up the settings so that
you can restore the custom settings at the end of your software installation.
4-2
Console Data Server

Examine the following Console Data Server window tabs to collect information that
you should save:
Highway Interface Tab
HDL IP Address: _____._____._____._____

Port A Baud Rate: ______
Port B Baud Rate: ______
Network Index: ______
Highway: ______
Device: ______
Enable Primary: yes no
Enable Secondary: yes no
Enable Maintenance port: yes no
CDS IP Address [1]: _____._____._____._____
CDS IP Address [2]: _____._____._____._____
Subnet Mask _____._____._____._____
Initialize an uninitialized HDL at next restart: yes no
Workstations Tab
Primary Node Names: ___________ ___________

__________ _________ __________ __________
Secondary Node Names: ___________ ___________
__________ _________ __________ __________
Message Spooler Tab
Message Files Location: _______________________

Max Disk Space: __________
Keep messages for: __________
Event Journal Tab
Min Records Retained: __________

Max Records Retained: __________
Enable Event Journaling: yes no
4-3
Calculation Expressions Tab
Calculation Expressions Files Location: ___________________

Master Preference: Current Master
Number of Calculation Expressions: __________
Reports Tab
Reports File Location: _______________________

Number of Reports Saved: __________
Keep reports for: __________
Trend Tab
Files Location: _______________________

Alarms Tab
DeltaV-style Alarm Processing: Yes No

Tags Tab
Tag Character Substitution Enable: Yes No

Tag Substitutions Log File Location: _____________________
Point tag replacement area
Comma replaced by ___

Period replaced by ___
Slash replaced by ___
Space replaced by ___
Display tag replacement area
4-4
Insert for invalid leading character ___

Comma replaced by ___
Dash replaced by ___
Period replaced by ___
Slash replaced by ___
Space replaced by ___

Examine the following tabs on the DeltaV Operate for PROVOX Properties dialogs
to collect information that you should save:
Console Data Servers Tab
Primary CDS________________
Secondary CDS________________
Auto Switchover Enabled Disabled
Instrument Areas Tab
Input Timeout________________
Session Timeout________________
Station Number________________
Identification________________
Window 1
Always On Top: checked unchecked

Toolbar Visible: checked unchecked
Tag Bar Visible: checked unchecked
Status Bar Visible: checked unchecked
DDP Visibility: None Local Remote
Window 2

Toolbar Visible: checked unchecked
Tag Bar Visible: checked unchecked
Status Bar Visible: checked unchecked
DDP Visibility: None Local Remote
Trend Tab
Files Location________________
Window 1

Horizontal Grid Visible: checked unchecked
Cursor Visible: checked unchecked
Vertical Grid Visible: checked unchecked
Legend Visible: checked unchecked
4-5
Horizontal Grid Spacing: ___________

Vertical Grid Spacing: ___________
Time Units: Minutes Hours
Time Span: ___________________________
Window 2

Horizontal Grid Visible: checked unchecked
Cursor Visible: checked unchecked
Vertical Grid Visible: checked unchecked
Legend Visible: checked unchecked
Horizontal Grid Spacing: ___________
Vertical Grid Spacing: ___________
Time Units: Minutes Hours
Time Span: ___________________________
Positioning Tab
Position A
IA 1
Position B
Position C
Position D
Home
X
Y
IA 2
X
Y
Trend 1
X
Y
Width
Height
Trend 2
X
Y
Width
Height
4-6
Chapter 5
Software Setup
After you have installed the DeltaV Operate for PROVOX hardware as described in
Chapter 3 of this manual and installed the software as described in Appendix A of this
manual, there are some additional setup tasks required to make the DeltaV Operate
for PROVOX Console work as intended. This section explains those tasks.
Note
Depending on the settings on your computer, the Start menu paths and other commands
required to complete the tasks in this section may be different than described.
Supported Console Hardware and Software

The hardware and software components of the DeltaV Operate for PROVOX
Console have been chosen and designed to work together as units. It is important that
you do not use unsupported hardware and software.
Caution
The Console Data Server is a mission-critical component of the control system

that is intended to run only Emerson Process Management supplied software.
Do not install or run any other software applications on the Console Data
Server.
Caution
The DeltaV Operator Stations are intended to run only Emerson Process
Management supplied software. We recommend not installing any software
applications other than the DeltaV Operate for PROVOX software on the
operator stations.
Running other software applications on the Console Data Server or DeltaV Operator
Stations may negatively impact console operation. Emerson Process Management
does not support installations that disregard this policy.
Software Setup
5-1
Caution
The DeltaV Operate for PROVOX software is intended for operation only on
server and workstation hardware supplied by or approved by Emerson Process
Management. Do not install or run the software on other hardware.
Running DeltaV Operate for PROVOX software on other than Emerson Process
Management supplied or approved hardware may negatively impact the operation of
the control system. Emerson Process Management does not support installations that
disregard this policy.
Introduction
A DeltaV Operate for PROVOX Console includes DeltaV Operate for PROVOX
Data Servers (also known as Console Data Servers), migration stations (PROVOX
Operator Console Operator Workstations with DeltaV Operate for PROVOX
software installed), and DeltaV Operator Stations with the DeltaV Operate for
PROVOX software installed. The following is a list of the tasks required to set up a
DeltaV Operate for PROVOX system after the initial hardware and software
installation:
1. Change the PROVOX Account Passwords
2. Configure secure logons
3. Add DeltaV users to the PROVOX21 group
4. Disable Web Site log
5. Set DeltaV-Style Alarm Processing
6. Initialize PROVOX Communications
7. Set or Verify POC Services
8. Configure DCOM servers
9. Verify Software Startup
10. Start DeltaV Operate
11. Set Internet Options
5-2
12. Set Acrobat Reader Options

13. Clean Up the \POC\programs Folder
14. Remove the Master License Popup
15. Set IA and Trend Window Positions
16. Enable PROVOX Communications
17. Create PROVOX toolbars
18. Create user settings and layout files
19. Define Primary And Secondary Servers And Workstations
20. Set Unsolicited Transmit Method
21. Log On To the operator station
22. If you have PROVOX Operator Console pictures, convert them to DeltaV
Operate pictures.
Note
In most cases, the instructions in this section are specific for the hardware and software
being shipped when this manual was created. If console hardware or software changed
subsequently, you may need to modify these instructions accordingly.
cards and drivers change often.
The instructions in this section apply generally to NIC and sound hardware and drivers,
but except as noted, do not apply directly to specific hardware and software.
Other Useful Information
In addition to the installation and setup steps outlined above, there are several other
things you need to know:
The practical limit for the number of datalinks depends only on the level of
performance that you require.
To change console settings on servers and workstations, you must log on as a user
with Windows administrator privileges.
Software Setup
Configure the maximum number of online trend traces in the ENVOX

database, even if you do not download trend sets.
In the console software, you cannot have more than 12 trend traces on any point.
5-3
If you run the Event Journal from other remote PCs, you may degrade the
performance of the Console Data Server.
The HDL connection to the Console Data Server differs from the connection to
Operator Workplace Consoles. Operator Workplace consoles use the dual port
mode of the HDL. The Console Data Server uses the single port mode and
connects to the LAN port of the HDL.
The DeltaV Operate for PROVOX Console Data Server must be in a workgroup.
The DeltaV Operator Stations connected to the Console Data Server can be in a
workgroup or a domain.
You should take care when setting up your network addressing, subnets, IP
addressing, and other network changes.
The remainder of this section explains the software setup tasks.
Single Logons
All PROVOX users must have at least two user accounts. On servers, they must be
able to log on to the Windows software as well as the PROVOX software. On
operator stations PROVOX users must have DeltaV accounts, and depending on how
your DeltaV system is set up, may have Windows accounts as well.
Users whose accounts have the same user name in Windows, DeltaV, and PROVOX
software can log on once. On operator stations logging in to DeltaV Operate logs
users in to DeltaV Operate for PROVOX software automatically. However, another
user can log on to DeltaV Operate for PROVOX without logging in to DeltaV
Operate.
Similarly, a user logged on to Windows on a server can access PROVOX functionality
by clicking the WinUser button on a login dialog. Clicking the WinUser button verifies
that the user currently logged on to Windows is also a PROVOX user and logs the
user in to PROVOX functionality. Again, however another user can log on to
PROVOX functionality without logging in to Windows.
Single Secure Logons

To ensure that the same user is logged on to Windows and PROVOX software (on
servers) or DeltaV and PROVOX software (on operator stations) you can implement
single secure logons.
5-4
To implement single secure logons:
Users need the same user name for their Windows, DeltaV, and PROVOX
accounts.
All PROVOX user and operator station node accounts must have secure
passwords.
Secure passwords include either DELTAV or STATION. Users with secure

passwords cannot log on to PROVOX functionality without logging in to the
underlying software (Windows on servers, DeltaV software on operator stations),
hence the term single secure login.
Note
To ensure security, all user names and node names configured in the ENVOX database
must have secure passwords. Anyone who knows a PROVOX account that has a nonsecure password can log on to PROVOX functionality interactively.
The ENVOX software requires unique passwords for all users. Therefore, each user
must have a unique valid PROVOX password that looks like XYZDELTAV123,
DELTAVXYZ, AAADELTAV, and so on, as long as the password is 16 or fewer
characters.
Note
The passwords configured in the ENVOX software do not have to be the same as the
passwords configured in Windows or DeltaV software.
The only exception is during transition from a PROVOX Operator Console system to
a DeltaV Operate for PROVOX system. You will need at least one standard
PROVOX account and password to perform display checkout on the PROVOX
Operator Console System.
Note that you can use passwords containing the DELTAV and STATION strings for
either nodes or users. However, you may find it useful to limit user accounts to
passwords containing DELTAV and limit node accounts to passwords containing
STATION.
There are three functions in DeltaV Operate for PROVOX software that require a
PROVOX user to log on:
DeltaV Operate
Redundancy
Database Update
The three functions use PROVOX accounts and passwords differently.
Software Setup
5-5
DeltaV Operate
When a PROVOX user with a secure PROVOX password logs on to DeltaV Operate
he is automatically logged on to the DeltaV Operate for PROVOX software as well
because he has the same user name in both accounts. However, another PROVOX
user with a secure PROVOX password cannot use the PROVOX Change Console
User dialog to log on to the DeltaV Operate for PROVOX software. He can only log
on from the DeltaV Login dialog.
The following table illustrates the effect of several ENVOX and DeltaV password
combinations on operator stations. The first two rows show how the single secure
login setup works for a user and an operator station. The remaining rows show the
effects of several non-secure account setups.
Table 5-1 DeltaV and ENVOX Password Combinations
Username
ENVOX
Password
DeltaV
Password
When logging in to
DeltaV software
When logging OUT

of DeltaV software
When using
Change
Console User
SMITH
*DELTAV*
abc
Full configured
DeltaV access,
Auto login to
PROVOX system
with configured
access
DeltaV log off

completes
successfully,
PROVOX log off
completes
successfully
Not allowed to
log on
NODE1
*STATION*
(user not
configured in
DeltaV)
Not allowed to log

on to DeltaV
software,
Does not log on to
PROVOX system
N/A
Not allowed to
log on
SMITH
xyz
abc
Full configured
DeltaV access,
Auto login to
PROVOX system
with configured
access
DeltaV log off

completes
successfully,
PROVOX log off
completes
successfully
Full configured
PROVOX
access
SMITH
abc
abc
Full configured
DeltaV access,
Auto login to
PROVOX system
with configured
access
DeltaV log off

completes
successfully,
PROVOX log off
completes
successfully
Full configured
PROVOX
access
5-6
Table 5-1 DeltaV and ENVOX Password Combinations

Username
ENVOX
Password
DeltaV
Password
When logging in to
DeltaV software
When logging OUT

of DeltaV software
When using
Change
Console User
SMITH
User not
defined in
ENVOX
database
abc
Full configured
DeltaV access,
Auto login to
PROVOX system
fails
DeltaV log off

completes
successfully,
Attempts to log off of
PROVOX system
no error reported
Not allowed to
log on
SMITH
abc
(user not
configured in
DeltaV)
Not allowed to log

on to DeltaV
software,
Does not auto login
to PROVOX system
N/A
Full configured
PROVOX
access
Notes:
1. When the user logs off of Windows before logging out of DeltaV, user is logged off of the DeltaV and PROVOX systems
automatically.
2. If a user logs on to both the DeltaV and PROVOX systems, then uses the Change Console User application to log on as a
different user, the next time DeltaV log off is requested, the current PROVOX user is logged off
3. *DELTAV* and *STATION* indicate valid ENVOX passwords of up to 16 characters that contain the string DELTAV or
STATION.
Redundancy
The Redundancy dialog can be opened from servers from the Start menu by
navigating to DeltaV Operate for PROVOX | Engineering | Redundancy.
To log on to the PROVOX software from the dialog a user clicks the Logon button.
The Change Console User dialog appears. If the user currently logged on to Windows
(on servers) or DeltaV Operate (on operator stations) also has a PROVOX account
with a secure password, he need only click the WinUser button to log on. The user
name field on the Redundancy dialog updates.
If another user with a PROVOX account with a secure password attempts to log on
by entering his name and password in the Change Console User dialog, an error
message appears.
Database Update
The Shared Database Update dialog can be opened from servers and operator
stations from the Start menu by navigating to DeltaV Operate for PROVOX |
Engineering | Database Update.
On servers, the dialog can also be opened by clicking the Database Update button on
the Redundancy dialog. On operator stations the dialog can also be opened from the
Software Setup
5-7
Instrument Areas File menu or by clicking the Database Update toolbar button, if the
button has been added to the toolbar and the user has DOWNLOAD privilege.
If the user currently logged on to Windows (on servers) or DeltaV Operate (on
operator stations) also has a PROVOX account with a secure password and
DOWNLOAD privilege, all he need do is click the Change User Account button,
then click the WinUser button on the Validate User Name & Password dialog. If the
user does not have DOWNLOAD privilege an error message appears.
If another user with a PROVOX account with DOWNLOAD privilege and a secure
password attempts to log on by clicking the Change User Account button to open the
Validate User Name & Password dialog, then enters his name and password in the
Validate User Name & Password dialog, an error message appears.
Note that logging in to the Shared Database Update dialog does not log a user in to
the Redundancy dialog. The login for the Shared Database Update dialog applies only
to that dialog and only while the dialog is open.
Changing the PROVOX Account Passwords

Perform on:
Using account:
Console Data Servers
PROVOX21Admin
Operator Stations
Administrator
Installing the DeltaV Operate for PROVOX software creates the PROVOX21 user
group on both Console Data Servers and operator stations. In addition, the software
creates user accounts in that group. The accounts created are:
On Console Data Servers PROVOX21Admin and PROVOX21pints.
On operator stations PROVOX21Admin.
The PROVOX21 group already exists on migration stations. On migrations stations

two additional accounts exist: The PROVOX21Eng and PROVOX21User accounts.
The following table shows the user names and initial passwords for the accounts and
summarizes information about these users.
5-8
Table 5-2 User Access Levels

User Name
Default Password
PROVOX21Admin
Assigned during
installation
Administrator
Total system access on servers, operator stations,

and migration stations INCLUDING Registry and
System files. (The same as the default Windows
Administrator Account.)
PROVOX21Eng
PROVOX21Eng
Engineer
Total system access on migration stations

INCLUDING Registry and System files. No access
to the servers.
PROVOX21User
PROVOX21User
Operator
Access only to the PROVOX Operator Interface on

migration stations. No access to servers.
PROVOX21pints
The password is
encrypted
NA
This is not a user account. It is an internal account

the software uses to run the web servers for the
viewers.
Caution
Access Level
System Access
If you change the password of the PROVOX21pints account, or make any

other changes to the account, you will have to re-install the console software.
The PROVOX21Admin account is a superuser account. Use this account only when you
need its access to the system. The PROVOX21Admin account is used by the DeltaV
Operate for PROVOX software.
Note
The PROVOX21Admin account on DeltaV Operator Stations is used internally by

the DeltaV Operate for PROVOX software and should not be used to log on to
DeltaV Operator Stations. Users logging in to DeltaV Operator stations using this
account will have no DeltaV privileges.
The PROVOX21Admin account has Windows Administrator privileges and is used
to start console services. The PROVOX21Admin account must have the same
password on all connected Console Data Servers, DeltaV Operator Stations, and
migration stations (if they exist). In addition, the current PROVOX21Admin account
password must be used when setting up the start options for the PROVOX POC
services on both Console Data Servers and DeltaV Operator Stations and for DCOM
services on DeltaV Operator stations.
On migration stations, the PROVOX21User account is intended to be the account
that all operators at PROVOX Operator Consoles use to log on to Windows. The
PROVOX21User accounts access to Windows is severely limited and controlled by a
Software Setup
5-9
system policy file. For more information on security on migration stations, refer to the
PROVOX Operator Console P3.0 documentation. DeltaV Operator Stations use a
different method to control security that is discussed in the DeltaV documentation.
To ensure console security you should change the user account passwords for each
default user on every Console Data Server and operator station.
Note
The PROVOX21Admin account default privileges are the same privileges as the
Administrator account.
Add DeltaV Users to the PROVOX21 Group

Perform on:
Using account:
Operator Stations
Administrator
How you set up users depends on whether your DeltaV Operator Stations are in a
Workgroup or a Domain. If they are in a workgroup environment, follow the
instructions in the section Setting Up Users in a Workgroup Environment. If they are in a
domain environment, skip to the section Setting Up Users in a Domain Environment.
Setting Up Users in a Workgroup Environment

The instructions for setting up users in a workgroup is nearly identical on both
Windows Server machines and Windows workstation machines. The only difference
is the name of one dialog as noted in the instructions.
To set up users, on every DeltaV Operate for PROVOX station, including the
ProfessionalPLUS workstation on Windows Workstation and Windows Server
machines, perform the following steps:
1. Open the Computer Management application (select Start | Settings | Control
Panel | Administrative Tools | Computer Management).
2. Open the Local Users and Groups folder.
3. Open the Groups folder.
4. Double click the PROVOX21 group.
5. On the PROVOX21 Properties dialog, click the Add button.
5-10
6. On the Select Users dialog (on Windows workstation) or select Users,

Computers or Groups dialog (on Windows Server), click the Advanced button.
A second Select Users or Select Users, Computers, or Groups dialog opens.
7. Click the Find Now button to populate the name list in the dialog.
8. Click, Shift Click, and Ctrl Click to highlight all the users you want to add to the
PROVOX21 group.
9. Click OK to accept your selections and close the first Select Users or Select
Users, Computers, or Groups dialog.
10. Click OK to confirm your changes and close the second Select Users or Select
Users, Computers, or Groups dialog.
11. Click OK to close the PROVOX21 Properties dialog.
12. Close the Computer Management window (select File | Exit).
13. Restart the computer.
Note
You must restart the computer to ensure that the DCOM servers are restarted with the
correct security settings.
Setting Up Users in a Domain Environment

To set up users in a domain environment requires that you perform tasks on the
Windows Server domain controller and each individual DeltaV Operate for
PROVOX station.
On the Windows Server Domain Controller

To set up users on the domain controller:
1. Start the Active Directory Users and Computers application (select Start |
Settings | Control Panel | Administrative Tools | Active Directory Users and
Computers).
2. Open the Users folder.
Software Setup
5-11
3. For each user you want to have access to the DeltaV Operate for PROVOX
functionality:
Open the user Properties dialog.
On the Member Of tab add the groups Domain DeltaV and Domain Users if
they are not already there.
Close the user Properties dialog.
4. Close the Active Directory Users and Computers application.
On each DeltaV Operate for PROVOX Station

To set up users:
1. Open the Computer Management application (select Start | Settings | Control
Panel | Administrative Tools | Computer Management).
2. Open the Local Users and Groups folder.
3. Open the Groups folder.
4. Double click on the PROVOX21 group.
If you want all domain users to have access to DeltaV Operate for PROVOX
software, proceed to the next step. If you want only specific users to have access
to DeltaV Operate for PROVOX software, skip to step 8.
To Allow All Domain Users Access to DeltaV Operate for PROVOX Software
5. Click the Add button.
The Select Users, Computers, or Groups dialog opens.
6. Enter yourdomain\Domain Users in the dialog.
7. Skip to Step 12.
To Allow Only Specific Users Access to DeltaV Operate for PROVOX Software
To allow only specific users access to DeltaV Operate for PROVOX software,
perform the following steps:
8. On the Select Users, Computers or Groups dialog, click the Advanced button.
A second Select Users, Computers, or Groups dialog opens.
9. Click the Find Now button to populate the name list in the dialog.
5-12
10. Click, Shift Click, and Ctrl Click to highlight all the users you want to add to the
PROVOX21 group.
11. Click OK to accept your selections and close the Select Users, Computers, or
Groups dialog that is on top.
12. Click OK to confirm your changes and close the Select Users, Computers, or
Groups dialog.
13. Click OK to close the PROVOX21 Properties dialog.
14. Close the Computer Management window (select File | Exit).
15. Restart the computer.
Note
You must restart the computer to ensure that the DCOM servers are restarted with the
correct security settings.
Disable Web Server Log

Perform on:
Using account:
Administrator
Installing the software on the Console Data Server creates the POC Web Site. There is
one setting you must make for this web site to ensure that server disk space is not
consumed by web events. The following are instructions for Windows Server 2008.
1. Open the Internet Information Server (IIS) Manager.
2. In the Connections pane open the Console Data Server, then select Sites |POC
Web Site.
3. In the POC Web Site Home pane, double click Logging.
4. In the Actions pane, select Disable.
5. Close the Internet Information Services Manager.
Software Setup
5-13
Set DeltaV-Style Alarm Processing

Perform on:
Using account:
PROVOX21Admin
If you are going to use a combined alarm banner, you must set the Console Data
Server to process PROVOX alarms in the DeltaV style so the priority order of alarms
in the combined alarm banner is correct. To set DeltaV-style alarm processing:
1. From the Start menu navigate to DeltaV Operate for PROVOX | Settings |
Console Properties.
The console properties dialog appears.
2. Select the Alarms tab.
3. Select the DeltaV style alarm processing check box
Leave the dialog open if you are going to continue setup, otherwise, click OK to close
the dialog.
Note
After any change to alarm processing behavior you must either perform a total download
or stop and start the POC services on the Console Data Server for the change to become
effective.
Setting DeltaV-style alarm processing affects alarm colors only in the alarm banner.
PROVOX faceplates, the PROVOX Alarm Summary, and the Instrument Area
continue to use PROVOX alarm colors.
Initialize PROVOX Communications

This section explains the tasks required to ensure the Console Data Server is
communicating with the DeltaV Operator Stations and the HDL.
Note
5-14
If you defined DeltaV Operator Stations and established communications from the
server to the HDL during software installation, you can skip to Set or Verify POC
Services on page 5-18.
Define Operator Stations

Perform on:
Using account:
PROVOX21Admin
1. If the PROVOX Operator Console Properties dialog is not already open, from
the Start menu navigate to DeltaV Operate for PROVOX | Settings | Console
Properties.
The console properties dialog appears.
2. Select the Workstations tab.
3. Enter the node name of each DeltaV Operator Station in the Primary Node
Names field and click Add.
4. If applicable, enter the node names of the secondary DeltaV Operator Stations
in the Secondary Node Names field.
5. Leave the PROVOX Operator Console Properties dialog open as you will return
to it after uninitializing the HDL.
Uninitializing the HDL

Perform on:
Note
Using account:
PROVOX21Admin
The console only supports the single port connection to the HDL.
For the console to connect to and communicate with the process network the HDL
must be properly uninitialized and defined in Console Properties so that it can be
initialized by the console software.
The steps required to uninitialize the HDL depend on its state:
If the STATUS LEDs currently display CONN:

The HDL is currently initialized, connected and in use.
1. Make sure this HDL is connected to the server whose properties you are
changing.
2. On the Console Data Server, stop the POC Base service.
Software Setup
5-15
3. Press and release the RESET button on the HDL. Wait 10 seconds.
The STATUS LEDs display DISC.
4. Press the DEFAULT CONFIG button.
The STATUS LEDs display UNIN.
5. On the Console Data Server, start the POC Base service.
If the STATUS LEDs currently display DISC:

The HDL has been initialized and connected, but it is currently not connected.
If the STATUS LEDs currently display INIT:

The HDL has been initialized but is currently not connected.
If the STATUS LEDs currently display UNIN:

The HDL is already uninitialized. No further action is required.
You can now define the HDL.
Defining the HDL

Perform on:
Using account:
PROVOX21Admin
Define the HDL using the Console Properties utility. You may want to refer to the
Ethernet NIC card setup for IP address information. From the server perform the
following steps:
1. From the DeltaV Operate for PROVOX Console Properties dialog select the
Highway Interface tab.
2. Open a Command Prompt window by selecting Start | Programs | Accessories
| Command Prompt.
5-16
3. From the Command Prompt enter ipconfig/all.

The Windows IP configuration and adapter information appears.
4. Ensure that the IP address in the Console Data Server area of the Highway
Interface tab is the IP address of the NIC card connected to the HDL.
5. Close the Command Prompt window.
6. In the Highway Data Link area of the tab, set the HDL's IP Address:
If you are using the default addressing scheme, set the HDL's IP address to
192.168.22.2.
If you are using other addresses, the HDL IP address and the address of the
Ethernet NIC card in the server connected to the HDL must be on the same
subnet. The network between the server and the HDL is a private network
and traffic should not be routed to or from this network. You may need to
consult your network administrator for more information.
7. If the plant has only one process network, set the PROVOX Network Index to 0
(zero). If your plant has multiple process networks, refer to the HDL
documentation for information on setting the PROVOX Network Index.
8. Set the PROVOX Highway and PROVOX Device values.
9. If you have made any changes make sure the HDL Initialization check box is
selected.
10. See your site supervisor for information for the other values in the Highway
Data Link area.
11. In the Enable HDL area, select all the options.
Note
If there is no secondary highway, deselect Enable Secondary Data Highway.

12. Click OK to close the Console Properties dialog.
If the Console Data Server software is running or the next time Console Data
Server software is started, the software attempts to set the HDL parameters every
couple of minutes until successful.
13. Restart the system.
You must restart so that changes you made take effect and the HDL is initialized.
Software Setup
5-17
Set or Verify POC Services

Perform on:
Using account:
PROVOX21Admin
Operator Stations
Administrator
A service is a software process that performs a specific function that supports one or
more applications. DeltaV Operate for PROVOX Consoles are supported by services
that support the underlying console functionality.
The services settings for the console services determine whether the services start
automatically when the Console Data Server or operator station starts, or if you start
them manually. The affected services depend on whether you are setting up a Console
Data Server or an operator station:
Console Data Servers are supported by the POC Base service and POC
TimeWatch service.
Operator stations running the DeltaV Operate for PROVOX software are
supported by the POC Station service.
To set or verify the console services (POC Base on Console Data Servers, POC
Station on operator stations) follow these steps:
1. Select Start | Settings | Control Panel | Administrative Tools | Services.
The Services dialog opens.
2. Double click the POC service in the list: POC Base service (on Console Data
Servers) or POC Station (on DeltaV Operator Stations).
The POC Properties dialog opens.
3. On the General tab select the desired Startup Type:
If this is a Console Data Server, select Automatic. This ensures that the POC
Base service starts when the computer is started.
If this is a DeltaV Operate for PROVOX Workstation used as a dedicated
operator station, select Automatic. This ensures that the POC Station service
that supports console operations are started when the computer is started.
If this workstation is used as an engineering workstation and not used for
process control, you may want to select Manual. When you are using the
console you can start and stop the POC console service from the Services
dialog.
Note that it requires Windows administrator privileges to start and stop services.
5-18
4. On the Log On tab, select Log On As This Account and enter

PROVOX21Admin.
5. In the Password entry field enter the current password for the
PROVOX21Admin account. Re-enter the password in the Confirm Password
entry field.
6. Click OK to exit the POC properties dialog.
7. On Console Data Servers only, double click the POC TimeWatch service.
The service properties dialog opens.
8. Verify the following:
Startup type is Automatic
Log on as Local System Account is selected
Allow service to interact with desktop is checked
9. Click OK to exit from the dialog.
10. Close the Services dialog.
Note
The system verifies POC Service passwords only on system startup. Therefore, any
disagreements in passwords, either account passwords or the POC Service password, are
not detected until the console restarts.
Note
Do not start, stop, or change the startup options for the FIX service from the Services
dialog.
Note
If you have set the POC Base service to start automatically, be sure to set the HDL
information correctly in the console properties dialog from the Console Data Server before
you restart it. Otherwise, the HDL may not be initialized correctly.
If the HDL is not initialized correctly, the console will have problems communicating
with other PROVOX devices on the data highway.
For more information refer to Initialize PROVOX Communications on page 5-14.
About the PROVOX21Admin Account Password in the

Service Dialog
When you enter the PROVOX21Admin account password in the Service dialog you
are not setting or changing the password. You are authenticating the
Software Setup
5-19
PROVOX21Admin accounts authority to run the service. The password you enter
must be the current password for the PROVOX21Admin account. If you enter an
incorrect password, the console software will not function. If you change the
PROVOX21Admin account password later, you must change the password in this
dialog as well.
There are two things to remember about the PROVOX21Admin account password:
Note
The PROVOX21Admin account password must be the same on all connected

Console Data Servers and operator stations. If it is different, workstations will not
be able to connect to Console Data Servers.
The PROVOX21Admin account must have the same password on all connected
Console Data Servers and operator stations.
The PROVOX21Admin password you enter in the Service dialog must be the
correct PROVOX21Admin account password the next time the computer
restarts or the POC service will not run and the console will not function
correctly.
Configure DCOM Servers

Perform on:
Operator Stations
Using account:
Administrator
There are several DCOM servers (components of the DeltaV Operate for PROVOX
software) that must be properly configured. The servers must be configured to run
under the correct account:
POPC
POCLogin
POPCperf
PAlmBnr
Access the DCOM servers from the Component Services management tool:
1. From a Command Prompt or the Run dialog, enter the command dcomcnfg.
2. In the left pane of the Component Services dialog select Component Services |
Computer | My Computer | DCOM Config.
Icons representing the DCOM servers appear.
5-20
Configure POPC and POCLogin

POPC and POCLogin run under the PROVOX21Admin account. The accounts
password must be set to the current PROVOX21Admin account password. If you
change the accounts password you must enter the new password in the DCOM
servers properties dialog for these servers or the software will not function correctly.
3. Select the POPC icon, then select Properties from the context menu.
The POPC properties dialog appears.
4. On the Identity tab, verify the following:
This user is selected
User is set to PROVOX21Admin
In the Password and Confirm password fields of the dialog enter the
PROVOX21Admin account password
5. Click the OK button to accept the change and close the server Properties dialog.
6. Select the POCLogin icon, then select Properties from the context menu.
7. Repeat steps 4 and 5.
Configure POPCperf and PAlmBnr
These servers must be set to run under the account of the user who started the
program.
8. Select the POPCperf icon, then select Properties from the context menu.
9. On the Identity tab, make sure The launching user is selected.
10. Click the OK button to accept the change and close the server Properties dialog.
11. Select the PAlmBnr icon, then select Properties from the context menu.
12. Repeat steps 9 and 10.
13. Close the Component Services dialog.
Note
Software Setup
Do not make any other changes in these dialogs.
5-21
Verify Software Startup

Perform on:
Using account:
PROVOX21Admin
Operator Stations
Administrator
Verify that the console software starts without errors on both Console Data Servers
and operator stations using the Windows Event Viewer.
To verify startup:
1. Select Start | Control Panel | Administrative Tools | Event Viewer.
2. Open the Windows Application log.
The steps to do this depend on the operating system.
What you see depends on whether you are at a Console Data Server or a DeltaV
Operator Station.
DeltaV Operate for PROVOX Data Servers

On DeltaV Operate for PROVOX Data Servers (Console Data Servers) you should
see the following events. Note that the text below each event is the message that
appears if you double click on an event in the list.
For example, the following shows the messages that appear in the Event Viewer
Application Log of a Console Data Server named MOWER connected to an operator
station named ZINFANDEL.
5-22
Date
5/13/10
Time
Source
6:15:33 PM
POC
Category
BasePort
Event
8
User
Computer
N/A
MOWER
Console Workstation on ZINFANDEL requested a connection, and is now connected/validated to the

Console Data Server.
Connection = 1 = 0x00000001
5/13/10
6:15:30 PM
POC
Grand
63
N/A
MOWER
HwyIf
35
N/A
MOWER
OPCON
85
N/A
MOWER
Valid License Module connected to HDL

5/13/10
6:15:27 PM
POC
Connected to the HDL

5/13/10
6:15:01 PM
POC
POC Base service started.
Operator Stations
Similar messages appear in the Event Viewer on operator stations.
For example, the following table shows the messages that appear in the Event Viewer
Application Log on an operator station named ZINFANDEL that is connected to a
Console Data Server named MOWER.
Date
5/13/10
Time
6:17:45 PM
Source
IntellutionFIX
Category
None
Event
User
Computer
201
N/A
ZINFANDEL
N/A
ZINFANDEL
The Fix service software is currently running.

5/13/10
6:17:33 PM
POC
StationPort
Console Workstation connected/validated to the Console Data Server MOWER.

5/13/10
6:17:23 PM
POC
StationPort
N/A
ZINFANDEL
85
N/A
ZINFANDEL
Requesting connection to the Console Data Server MOWER.

5/13/10
6:17:01 PM
POC
OPCON
POC Station service started.
Software Setup
5-23
Setting Internet Options

Perform on:
Note
Using account:
PROVOX21Admin
Operator Stations
All DeltaV accounts
The settings you make in this section are by user. That is, each Windows user account
has its own copy of the settings. It is therefore necessary that the settings explained in this
subsection be made from each user account.
The console software uses Internet Explorer functionality in several of the viewers. It
is important that you make the following settings for the viewers to work as expected:
1. Select Start | Settings | Control Panel | Internet Options.
The Internet Properties dialog appears.
2. Select the General tab.
3. Change Home page address by clicking on Use Blank.
4. Click the Settings button in the Browsing History area.
The Temporary Internet Files and History Settings dialog opens.
5. In the Temporary Internet Files area:
Select the Automatically option button.
Set the Amount of disk space to use to 10 Mbytes.
6. Click OK to close the dialog.
7. Select the Security tab.
8. Set the Web content zone to Local Intranet.
9. Click the Default Level button
10. In the Security level area, set the slider to Medium.
11. Set the Web content zone to Trusted Sites.
12. Click the Sites button
On Operator Stations only, a popup may appear. If it does, click the Advanced
button on the popup.
5-24
The Trusted sites dialog appears.

13. In the Add this Web site to the zone field, enter the node name of the Console
Data Server supplying information to this computer in the form
http://nodename.
You may have to clear the check box Require server verification (https:) for all
sites in this zone.
14. Click the Add button to add the nodename to the Web sites list.
15. Repeat steps 13 and 14 to add all other local intranet sites required, for example,
redundant servers.
16. Close the Trusted Sites dialog.
17. Select the Connections tab.
18. Click the LAN Settings button.
The Local Area Network (LAN) Settings dialog opens.
Make sure none of the check boxes on this dialog is selected.
19. Click OK to accept the settings and close the dialog
20. Click OK to accept the settings and close the Internet Explorer Properties
dialog.
You do not need to set anything on the Privacy, Content, Programs, and Advanced
tabs.
Setting Acrobat Reader Options

Perform on:
Using account:
PROVOX21Admin
Operator Stations
All DeltaV accounts
There are a couple of things to set in Acrobat Reader.

1. Log on.
2. Start Acrobat Reader.
3. If a license agreement appears, acknowledge it by clicking Accept.
Software Setup
5-25
The license agreement appears only the first time a user starts the reader. It will
not appear again.
4. After Acrobat Reader opens, select Edit | Preferences.
5. Select General in the Categories pane.
6. In the Application Startup area, deselect Show splash screen.
7. Select Updater in the Categories area.
8. In the Check for updates area, select Do not download or install updates
automatically.
9. Click Ok to accept the changes and close the Preferences dialog.
10. Exit the Acrobat Reader software.
You can repeat these steps for other users if desired.
Cleaning Up the \POC\Programs Folder

Perform on:
Using account:
PROVOX21Admin
Operator Stations
Administrator
Installing Microsoft Internet Explorer during software installation can put a couple of
extra files in the \POC\Programs directory. Programs in the \POC\Programs
directory appear in the start menu of the desktop. Remove the unnecessary files:
1. Start Windows Explorer
2. Navigate to the \POC\Programs directory
3. Leave the shortcut PROVOX Logon (on operator stations) and delete everything
else.
It is possible (but beyond the scope of this manual to explain) to add programs to the
start menu of the desktop. If you desire to do so, refer to the Windows
documentation.
5-26
Removing the Master License Popup

Perform on:
Using account:
PROVOX21Admin
Operator Stations
Administrator
As installed, the console software presents a master license agreement every time an
operator station or Console Data Server is restarted. To prevent this from occurring:
1. Navigate to Start | Programs | Startup.
2. Right click on View License and select Delete.
Other Settings
In addition to the software settings made during console hardware installation and
setup and software installation, there are several software settings that affect console
security and the operating environment. There are several settings you must make to
ensure that console security is implemented as intended. There are other settings you
should verify and possibly change, depending on how you are using the console and
the type of console you have. These settings include:
Setting Window Positions
Customizing the Operate Environment
Using The Disk Administrator
Setting IA and Trend Window Positions

Perform on:
Operator Stations
Using account:
Administrator
The initial positions of the Instrument Area and Trend window will probably be
satisfactory. However, if you want to set the initial location of these applications when
they are started from the toolbar, the console software provides a way to do so.
Define initial positions for the windows in the Console Properties dialog (from the
Start menu navigate to DeltaV Operate for PROVOX | Settings | Console
Properties). The Positioning tab of this dialog contains a grid of values.
Software Setup
5-27
Figure 5-1
Positioning Tab of DeltaV Operate for PROVOX Properties Dialog
The Positioning tab has columns for five possible alternate positions for the windows
(A, B, C, D, and Home).
The tab is laid out as a grid so that you can easily see all the settings for Instrument
Areas and Trend windows for every position defined. Each square in the grid is a
number that represents either the x or y coordinate of the upper left corner of a
window in pixels, and for Trend windows, the width or height of the window in pixels.
5-28
Enable PROVOX Communication

Perform on:
Operator Stations
Note
Using account:
Administrator
If Version Control for DeltaV Displays is enabled, before you start DeltaV Operate
you must first check out the file FrsVariables.fxg from DeltaV Explorer so it can be
modified. After you have completed this section and saved the file, you must check it back
in. DeltaV Operate cannot be running while you are checking the FrsVariables.fxg file
out or in.
To enable PROVOX components in the DeltaV Operate interface, do the following:
1. If Version Control for DeltaV Displays is enabled, from DeltaV Explorer, check
out FrsVariables.fxg (in the System Configuration\DeltaV Displays\Pic folder).
2. Start DeltaV Operate and go to Configure mode.
3. Open the DeltaV User Settings by clicking the
toolbar.
button on the Configure
The DeltaV User Settings dialog opens.
Software Setup
5-29
4. Select the PROVOX check box as shown to enable communication with the
PROVOX system.
For information on the other check boxes, refer to the section Using the DeltaV
User Settings Dialog in the DeltaV Operator Graphics manual.
5. Click the Add files button.
6. Acknowledge the popup dialogs that appear.
7. Click OK to close the DeltaV User Settings dialog.
8. Close DeltaV Operate.
9. Click Yes on the Workspace popup that appears to save the changes to
frsVariables.fxg
10. Wait 30 seconds, then open DeltaV Operate to refresh the file list.
The Add files button copies a number of PROVOX-specific files to the DeltaV
directory structure. These files include dynamo sets, alarm banners, alarm summaries,
5-30
and toolbars that support PROVOX systems. These files are visible in DeltaV
Operate (configure mode) so you can use them when you create pictures.
Note
If Version Control for DeltaV Displays was enabled while you enabled PROVOX
communication, perform the following additional steps to check the added files in to the
VCAT database. Otherwise skip to Create PROVOX Toolbars.
The files must exist on the ProfessionalPLUS workstation to add them to the VCAT
database. Therefore, if you have installed DeltaV Operate for PROVOX on an
Operator workstation, you must first upload the files to the ProfessionalPLUS. Refer
to the section in the DeltaV Books Online named Downloading and Uploading Operator
Pictures for more information.
To add a file to the VCAT database:
1. Open the file in DeltaV Operate.
2. Close the file.
This adds the file but does not check it in to the VCAT database.
To check the file in to the VCAT database:
Note
VCAT Auto Check Out/In feature must be enabled during this process.
1. From DeltaV Operate in Configure mode, open and close the file a second time.
The following shows the directory structure in DeltaV Operate of the files that
need to be added to the VCAT database. Only the files that need to be added are
shown.
THISNODE
Dynamo Sets
frsPOCAnalog.fds
frsPOCChip.fds
frsPOCDiscrete.fds
frsPOCLoop.fds
frsPOCProvue.fds
frsPOCUoc.fds
Pictures
ZPALMSUM.grf
ZPOARSUM.grf
Help
TlbarhpPROVOX.grf
Software Setup
5-31
Standard
ABdvp1.grf
ABdvp1_1680x1050.grf
ABdvp2.grf
ABdvp2_1680x1050.grf
ABPInfo.grf
ABPInfo_1680x1050.grf
ABPOAR.grf
ABPOAR_1680x1050.grf
PROVOXTOOLBAR1.grf
PROVOXTOOLBAR1_1680x1050.grf
PROVOXTOOLBAR2.grf
PROVOXTOOLBAR2_1680x1050.grf
User_Ref_Provox.grf
2. Close DeltaV Operate.
Note
You can also check these files in and out of VCAT from DeltaV Explorer, but the file
structure in Explorer is different than that shown here.
3. From DeltaV Explorer, check in the file FrsVariables.fxg.
Create PROVOX Toolbars

Perform on:
Using account:
Operator Stations
Administrator
You must create one or more PROVOX toolbars for operators to have access to
PROVOX functionality. The number and style of toolbars you create depend on your
installation: the number of monitors on your operator stations and whether your
system is PROVOX system only or a combination of DeltaV and PROVOX systems.
The DeltaV Operate software includes a Toolbar Picture Builder Expert. This section
does not explain in general how to use the Toolbar Picture Builder. For that
information, refer to the section Using the DeltaV Toolbar Builder Utility in the DeltaV
Books Online. This section explains only the items of the builder that are specific to
PROVOX systems.
To create a PROVOX toolbar:
1. Start DeltaV Operate and go to Configure mode.
5-32
2. Open the DeltaV Utilities toolbar (Select Workspace | Toolbars, then check the
box for DeltaV_Utilities).
3. Close the Toolbars dialog by clicking Close.
4. Open the Toolbar Picture Builder Expert by clicking the
Configure toolbar.
button on the
The Toolbar Picture Builder Expert dialog opens.
5. When you select a toolbar template explanatory text appears in the field below
the selection. Note that you must create toolbars from a template. You cannot
edit an existing toolbar.
The TBPROVOXTemplatePRIM Toolbar template is selected in the figure.
6. Enter a name for your toolbar in the New Toolbar Name field. Note that you
must use a new name. You cannot overwrite existing toolbar names.
Software Setup
5-33
7. The Tool Button Sets field is a dropdown list. There are several sets of buttons.
Three that you will probably need are:
TBEDeltaVAllUI Common Tools for any Toolbar
TBEDeltaVTools DeltaV Specific Tools
TBEsys2Provox PROVOX Specific Tools
There may be others depending on the DeltaV options you have installed. You
can add buttons from any or all of these sets to your toolbar.
8. Select the Common Tools for any Toolbar set.
You should probably include the following buttons on any toolbar you create.
Print Main Window

Open Picture
Swap Main Displays
The figure shows the wizard with the PROVOX Specific Tools button set
selected after adding buttons from the Common Tools set. Include any other
buttons your operators need from any of the tool sets.
9. Move buttons between your toolbar and the button set using the left and right
arrow buttons.
10. Set the order of the buttons on your toolbar by selecting a button and using the
up and down arrow buttons.
11. After you have selected all the buttons you want and arranged them in the order
you want, click OK to save the new toolbar in the \Standard directory.
Refer to the following section for information on creating and editing a settings or
layout file so the toolbar you created appears in DeltaV Operate.
Create Settings and Layout Files

DeltaV Operate for PROVOX software includes settings and layout files you can use
to tailor the appearance of the software to your needs. You can define the alarm
banners, toolbars, and other pictures that appear and on which monitor or monitors
they appear (if you have dual or multi-monitor operator stations).
This section explains the PROVOX-specific tasks to create settings files and layout
files.
5-34
For general information on setting up DeltaV Operate, refer to DeltaV Books Online,
in particular the topics Customizing the DeltaV Operate Environment and Working
with Pictures on Multiple Monitors.
Note
DeltaV Operate for PROVOX software supports multiple monitors, but does not
support Operator Keyboard.
Settings and Layout Files Overview
The files you use as a starting point to create your settings and layout files are:
Note
User_Ref_Provox.grf (in \DeltaV\DVData\Graphics-iFix\Pic\Standard)
DeltaVPicture.Template (in \DeltaV\DVData\Graphics-iFix\Local)
Every operator station with DeltaV Operate for PROVOX software installed must
have a settings file based on User_Ref_Provox.grf applied to it to enable the PROVOX
scheduler.
You do not have to use DeltaVPicture.Template unless you want to change the size,
shape, or number of the pictures that appear on your monitors.
If the default layout of windows on monitors fits your needs and you need only to
change the initial pictures that appear, you need only use the User_Ref_PROVOX.grf
picture.
You control whether the files you create apply to all operator stations or a single
operator station by how you name the files:
If the default arrangement and size of windows on the operator station monitors is
satisfactory and all you need to do is change the initial pictures that appear, you need
only create settings files. If you want to change the size, shape, or number of windows
that appear, use layout files.
To create settings files, save User_Ref_PROVOX.grf as:
UserSettings.grf to create a settings file that applies to all operator stations
computername_Settings.grf to create a settings file that applies only to the specific

operator station computername.
To create layout files, save DeltaVPicture.Template as:
Software Setup
DeltaVPicture.Layout to create a layout file that applies to all operator stations
computername_Picture.Layout to create a layout file that applies to the specific

operator station computername.
5-35
Note
Both the user settings and layout files must follow the naming conventions for picture files.
Operator stations can have multiple settings and layout files installed on them. If an
operator station has more than one file installed, the files are applied in the following
order:
1. If UserSettings.grf exists, it is applied first.
2. If computername_Settings.grf exists, it is applied.
3. If computername_Picture.Layout exists, it is applied and no other files are applied
even if DeltaVPicture.Layout exists. If only DeltaVPicture.Layout exists, it is
applied.
This hierarchy of application provides flexibility in setting up your system. You can
have different numbers of monitors, different initial pictures, and different layouts on
each operator station if your situation requires it.
Note
Both the user settings and layout files include sections for setting alarm banners, toolbars,
and initial pictures. If you use both file types, there is no point in specifying alarm
banners, toolbars, and initial pictures in the user settings files. Any of these items
specified there are overridden by settings in the layout files.
Creating Settings Files
For DeltaV Operate for PROVOX software to operate properly, you must create a
UserSettings.grf file for all workstations or a computername_Settings.grf file from the
User_ref_PROVOX.grf file as described in the following steps. From DeltaV Operate
Configure mode:
1. If your DeltaV Operator Station already has a UserSettings.grf file, save it to
another name.
2. Open \Pictures\Standard\User_ref_PROVOX.grf.
3. Save the file in the \Standard subdirectory as UserSettings.grf or
computername_Settings.grf.
4. Click the right mouse button and select Edit Script.
The Microsoft Visual Basic editor opens and a number of project files appear.
5. If the code for the settings file you just saved is not visible, you can select
Windows | Cascade and navigate through the code windows to find the settings
file.
5-36
Settings files are copied to an operator stations hard drive when the operator station is
downloaded.
If the console does not work properly after you edit the settings file you can recover
by renaming the settings file and restarting the console software. You can then correct
the settings file as required.
User_Ref_Provox.grf is extensively commented. The comments explain what each
section of the file does and how to use the section if you need it. A few of the required
or more complex sections of the file are explained in more detail below.
Enabling the PROVOX Scheduler
As stated earlier, DeltaV Operate for PROVOX workstations require that the
PROVOX scheduler to be running. Scroll to the Opening Scheduler section and make
sure the code lines in that section are uncommented.
Assigning Toolbar Pictures to Screens
Use the TOOLBAR WINDOW INITIALIZATION section of the file to specify the
toolbar pictures you defined earlier (and toolbar help pictures, if desired) for each
monitor.
This section has two parts you can use to define different pictures for two types of
operator stations: Those with only DeltaV software and those with both PROVOX
and DeltaV software.
In the DeltaV-only workstation settings part define the toolbar and toolbar help
pictures that appear on operator stations that are not connected to a PROVOX
system. The PROVOX/DeltaV workstation settings section applies to operator
stations that have DeltaV Operate for PROVOX software installed.
Main Window Initialization
Use the MAIN WINDOW INITIALIZATION section to define the main operator
pictures that open on each monitor when the DeltaV software is started or the Reset
Layout toolbar button is clicked. You can also define the picture opened on each
monitor by the Display Overview toolbar button.
Setting Up Alarm Banners
The ALARM BANNER WINDOW INITIALIZATION section is similar to the
TOOLBAR WINDOW INITIALIZATION section. You can specify two sets of
alarm banner pictures and alarm banner help pictures: For DeltaV-only operator
stations and for operator stations that have DeltaV Operate for PROVOX software
installed.
Software Setup
5-37
Restoring Changes from a Previous UserSettings file

If you had a previous version of the DeltaV Operate for PROVOX software installed
and want to retain the settings in it, open or print the previous version of the
UserSettings.grf file. Compare the contents of that file with the settings.grf file you
just created. If there are changes to the previous file that you want to include in the
new file, edit the new settings file to make the changes.
Do not copy the previous UserSettings.grf file over the new file.
Other User Settings Variables
The user settings file contains comments that explain how to modify the variables to
accomplish changes. Follow the instructions in the file. For example, using the
variables in the user settings file you can do the following:
Set whether DeltaV Operate uses the standard alarm banner or alarm and OAR
banner or custom alarm banner you create.
Set the behavior of alarm direct access when an alarm button in the alarm banner
is clicked.
Set whether the alarm banner is always on top of other windows or not.
Change the default toolbar.
Set whether operators can browse other directories and files when opening
pictures in the main window.
Initialize the display history list.
Prevent changes to the display history list.
Set the picture that is opened by the display directory toolbar button.
Creating Layout Files

Use layout files if you want to change the appearance of your operator station
pictures. With layout files you can change the size, location, and number of windows
that appear on each monitor. To create layout files:
1. From Windows Explorer, navigate to \DeltaV\DVData\Graphics-iFix\Local.
2. Open DeltaVPicture.Template in a text editor (Notepad, for example).
3. Save the file in the \Local subdirectory as DeltaVPicture.Layout or
computername_Picture.Layout.
4. Edit the file as required.
5-38
DeltaVPicture.Template is extensively commented. The comments explain how to

specify the pictures that make up your screens, and how to size and position them as
well.
Note that the number of pictures you specify must equal the number specified in
Count. In addition, every Picture1 through Picturen named must have a
corresponding picture definition for the operator station to successfully load the
layout file.
Defining Primary and Secondary Servers and Workstations

If you did not define the primary and secondary Console Data Servers for each
operator station, or define the primary and secondary operator stations for each
Console Data Server, do that now.
From each operator station and Console Data Server, from the Start menu navigate to
DeltaV Operate for PROVOX | Settings | Console Properties. For each workstation,
on the Console Data Server tab, enter the Primary and Secondary Console Data
Server. For each Console Data Server, on the Workstations Tab, enter the
workstations whose primary and secondary connections are to the Console Data
Server.
Setting Unsolicited Data Reporting

If your PROVOX system includes devices that use pre-1984 device programming
(pre-ADR), you may need to enable Standard Unsolicited data reporting. This is a
licensed option that does not appear unless you have installed the server with the
appropriate license.
Do not enable Standard Unsolicited data reporting unless you know you need it. If you
are unsure, consult with your Emerson Process Management service representative.
Note
Enabling Standard Unsolicited data reporting on systems can cause undesirable side
effects under some circumstances. Enable Standard Unsolicited data reporting only if
necessary.
To see the current state of Standard Unsolicited data reporting, on Console Data
Servers from the Start menu navigate to DeltaV Operate for PROVOX | Settings |
Standard Unsolicited. An informational popup appears. Click OK. The Unsolicited
Reporting Control appears as shown in the figure.
Software Setup
5-39
Figure 5-2
Unsolicited Reporting Control
When opened, the dialog indicates the current state of Standard Unsolicited data
reporting. For example, in the figure data reporting is set to the default: Standard
Unsolicited data reporting is disabled.
Tag and Display Tag Substitutions

If you have an existing PROVOX configuration that you are going to use with DeltaV
Operate for PROVOX consoles, it is possible that some of the point tags, PPA tags,
PMA tags, and display tags in the configuration are invalid for use in DeltaV Operate.
It is recommended that you change the tags in the configuration to valid tags and
display names for DeltaV Operate.
However, to ease the transition to DeltaV Operate for PROVOX Consoles, you can
enable Tag Substitution. If it is enabled the console software translates invalid point
tags and display tags to valid DeltaV tags when they are downloaded to the server. .
Note
PPA and PMA tags are not translated. You must ensure that PMA and PPA tags
in the ENVOX configuration are valid for use in DeltaV Operate.
If you choose to not use Tag Substitution you must make sure all tags configured in
the ENVOX software are valid DeltaV tags
5-40
Using Valid Tags in ENVOX Software

Point tags, PPA tags, and PMA tags in the ENVOX software for use on the DeltaV
Operate for PROVOX Console should:
Contain at least one letter
Contain only letters, numbers, and dashes (these are the only characters that are
valid for ENVOX point tags that are also valid in DeltaV Operate)
Be no more than 12 characters long.
Display tags in the ENVOX software for use on the DeltaV Operate for PROVOX
Console should:
Start with a letter
Contain only letters and numbers (these are the only characters that are valid for
ENVOX display tags that are also valid in DeltaV Operate)
Setting Substitution Options

If you are using Tag Substitution set the substitution options on Console Data
Servers. From the Start menu navigate to DeltaV Operate for PROVOX | Settings |
Console Properties. Select the Tags tab.
Note
Any change on this tab forces the next download to be a total download of the console from the
ENVOX database. If you make a change, the software prompts you for confirmation. If you
confirm the change there is no way to undo it.
The tab contains the following fields and areas:
Tag Character Substitution Enable check box: Turns the tag substitutions feature
on and off.
Tag Substitutions Log File Location: Specifies where tag substitution log files are
created.
Point tag replacement area
Comma replaced by
Period replaced by
Slash replaced by
Space replaced by
In each of these fields select a substitution character from the drop-down list. The
default substitution character is $.
Software Setup
5-41
Display tag replacement area
Insert for invalid leading character

In this field select the letter to insert as the leading character for display names
that have an invalid leading character in the ENVOX configuration. The default
letter is P.
Comma replaced by
Dash replaced by
Period replaced by
Slash replaced by
Space replaced by
In each of these fields select a substitution character from the drop-down list. The
default substitution character is _ (underscore).
Example Substitutions
The following table illustrates how the conversion works when using the default
character substitutions:
In the ENVOX Configuration
After Conversion
Point Tags
AI,201
AI$201
AI.301
AI$301
AI/401
AI$401
AI 501
AI$501
Display Tags
DSP,123
DSP_123
12345
P12345
The Log File

The translations are reported in the file TagSubstitutions.csv. This file is created (or
overwritten) by a total download. Partial downloads append information to the file.
The file is in the location specified on the Tags tab.
5-42
The file is created whether tag character substitution is enabled or not. You can use
this feature to determine which point tags and display tags in the ENVOX
configuration are invalid for DeltaV Operate. (Remember that the conversion does
not affect PPA and PMA tags.)
To view the file, open it in Excel. The log file contains only the point tags and display
tags that are invalid, and shows what the converted tags would be using the currently
selected substitution characters. The file has several columns but those of most
interest are:
InputTag The tag as it is configured in the ENVOX database.
SubstTag How the tag would appear if translated with the currently selected
substitutions.
OutputTag The tag used in the console. If tag character substitution is

enabled, this column is identical to the SubstTag column. If substitution is
disabled, this column is identical to the InputTag column.
ErrorText Not all tags can be translated. This column contains error messages
generated during translation. Note that one tag can have several error messages.
Errors
Substitution error messages during tag substitution include:
Disallowed character found in tag
Warning: cannot prepend required alpha string to display name (too long),
original tag =
Applies only to display tags. The software cannot insert a letter at the beginning of the
display tag because display tags can be no longer than 12 characters.
Logging On to the Operator Station

Note
Before beginning this procedure download the Console Data Server database from the
ENVOX configuration software with a minimum set of definitions for the operator
station and users.
The download must at least include:
The operator station defined as a user or the ANYNODE user defined with
sufficient privilege
The DeltaV users.
If you have defined security and set up accounts in the ENVOX software and the
operator station as described in Chapter 3 and Chapter 5 of this manual, log on as
Software Setup
5-43
described in the DeltaV documentation. Entering the DeltaV Operate user name and
password in the DeltaV Logon dialog logs you in to both the DeltaV system and the
PROVOX system.
If you have not set up the accounts as described in the sections referenced above,
when you log on to DeltaV Operator Station an error message appears saying the user
name does not exist.
If this message appears you can log on to the PROVOX system in the following
manner if you have accounts that do not have secure PROVOX passwords:
1. On the Start menu, navigate to DeltaV Operate for PROVOX |Operate |
Change User.
The Change Console User dialog box appears.
Note
If the Change Console User dialog does not appear, check the security settings.
2. Enter a user name and password that are in the ENVOX download to the
console data server.
If you have not downloaded a configuration and you attempt to log on, a message
appears saying The database is unavailable for logon.
Click on the PROVOX Integrity button in the alarm banner and view the Integrity
display. Make sure the indicators that apply are green (indicating good integrity).
Convert Existing Pictures

If you have operator pictures from PROVOX Operator Console 3.0 software, the
DeltaV software includes two utilities to help you convert them into DeltaV Operate
graphics.
First, convert from the PROVOX Operator Console 3.0 graphics to DeltaV Operate
for PROVOX graphics using the Picture Converter utility. Note that Command
Language scripts associated with pictures are converted into comments in VBA
subroutines. You will have to convert the scripts by hand.
Second, use the Make a Main picture utility to change references to data servers from
THISNODE and FIX32.THISNODE to POC.
For information on these utilities refer to the DeltaV Release Notes KBA.
Note
5-44
The amount of manual editing required after you convert pictures depends on the
complexity of your pictures.
Troubleshooting
There are a number of things needed to get the DeltaV Operate for PROVOX
software working with DeltaV Operate. Here is a list of things to check if your system
is not working as expected:
Are the DeltaV users members of the PROVOX21 Group?

One symptom of this problem is that none of the DeltaV Operate for PROVOX
applications run for the currently logged on user.
See Add DeltaV Users to the PROVOX21 Group on page 5-10.
Are the DeltaV user names in the ENVOX download?

See Chapter 6 of this manual.
Does the ENVOX download have an ANYNODE user defined or the operator
station defined as a user?
If a user cannot log on to the PROVOX system, does the account have DELTAV
or STATION defined as the password configured in the ENVOX download?
Do all connected servers and operator stations have the same password for the
PROVOX21Admin account?
See Changing the PROVOX Account Passwords on page 5-8.
Are the POC services passwords set to the current PROVOX21Admin account
password on all connected servers, applicable COM servers, and operator
stations?
See Set or Verify POC Services on page 5-18.
Have you selected the PROVOX check box and added files in the DeltaV User
Settings dialog?
Have you built a PROVOX toolbar and updated UserSettings.grf with the
filename?
See Create PROVOX Toolbars on page 5-32.
Have you edited User_ref_PROVOX.grf to create a UserSettings.grf picture and

edited the script as required?
See Create Settings and Layout Files on page 5-34.
Software Setup
5-45
Have you installed the DeltaV Network Time Protocol service on the Console
Data Server?
See Appendix A of this manual.
Have you checked all the network cables and IP address assignments?
Have you downloaded the DeltaV Operator Station from the ProfessionalPLUS
station?
See the DeltaV documentation.
Is the Console Data Server processing alarms using the PROVOX or DeltaV
rules?
See Set DeltaV-Style Alarm Processing on page 5-14 of this manual and Chapter
8 of the User Manual
If you cannot start a PROVOX application, is it running on the other Flexlock

desktop?
See the DeltaV documentation.
Are you using the correct alarm banner file for the alarm settings on the Console
Data Server?
See Set DeltaV-Style Alarm Processing on page 5-14 and Create Settings and
Layout Files on page 5-34 of this manual.
Have you disabled Internet Protocol Version 6 (TCP/IPv6) on the Console Data
Server network connections (Windows Server 2008 only)?
See Disabling Internet Protocol Version 6 (TCP/IPv6) on page B-7 of this
manual.
5-46
Chapter 6
Database Configuration
Introduction
To create the database configuration (point information, PPAs, and so on) use the
ENVOX configuration software or the Control Desktop software. The DeltaV
Operate for PROVOX Console accepts a database download created for an
Operator Workplace Console, though some parts, including displays, are not used.
However, there are some requirements that the database configuration must meet to
be accepted by the console.
Note
Make sure that there are no duplicate names or tags in the ENVOX configuration and
the DeltaV configuration. All tags and names must be unique across both databases.
Duplicate names or tags can cause unpredictable behavior.
This section outlines the differences in configuration between an Operator Workplace
Console and a DeltaV Operate for PROVOX Console. The information in this
section applies directly to the ENVOX configuration software, but applies to the
Control Desktop software as well. The two configuration software applications are
organized differently, but require the same information to configure a console.
You create a console configuration using the configuration software by entering
information on a number of related forms. To create a configuration for the DeltaV
Operate for PROVOX Console you do not need some of the forms and you may have
to do something different on one or more forms.
Note
Tags you configure in the ENVOX software for use on the DeltaV Operate for
PROVOX Console must be valid PROVOX tag names.
PROVOX tag names must:
Contain at least one letter.
Contain only letters, numbers, and dashes (). (These are the only characters valid
in ENVOX configurations that are also valid in DeltaV Operate.)
It is recommended that you change your ENVOX configuration to make all tags and
display names valid for DeltaV Operate. However, the Tags tab of the DeltaV
Operate for PROVOX Properties dialog provides character substitution for tagnames
and display names. This tab is intended only to ease the transition from earlier
PROVOX consoles to DeltaV Operate for PROVOX Consoles.
6-1
For more information on the Tags tab refer to its online help and Chapter 5 of this
manual.
This release of the console software supports configuration of console-resident
points:
Activity points
Discrete control device points (DCDs)
Extended pulse count input points (EPCIs)
Integrity points
Accumulation points.
Maintenance points
Single-bit discrete points
All of these support console-resident point redundancy except maintenance points

and single-bit discrete points.
In addition, console-resident points in PROVUE or Operator Workplace consoles
can be targeted to and operated from DeltaV Operate for PROVOX Consoles. (When
operating a point hosted on another console the commands are sent to and the
functions are performed on the source console.)
Note
The DeltaV Operate for PROVOX Console is compatible with existing PROVOX
devices that use ADR (Advanced Data Reporting) or Background Reporting.
Ensure that any existing DCU, MUX, or PCIU devices have been upgraded to
support ADR or background reporting.
Console Configuration
If you have an existing Operator Workplace configuration you want to use for the
DeltaV Operate for PROVOX Console you will need to review this subsection for
items you must change in your configuration.
If you have an existing PROVUE configuration you want to use you must first update
the configuration to an Operator Workplace configuration, then make the
configuration compatible with the DeltaV Operate for PROVOX Console.
If you are starting a new configuration, this subsection tells you which forms are not
required for the console and which forms require specific information to result in a
download compatible with the console.
6-2
The following subsections explain how to use ENVOX software console

configuration forms to create a configuration for the console. Note that some forms,
though not required for configuration, may have to be at least partially completed for
the configuration to generate without errors.
If you are using the Control Desktop configuration software, the configuration
information required is organized differently than explained in the following
subsections, but the same information is required.
Console Device Definition Form

Open the form by selecting Add | DEVICES | WPCON from the ENVOX Top
Level form. Configure the Revision as 2.0. Unless you are configuring redundant
console-resident points, set the Redundancy Status as SIMPLEX.
If you are configuring redundant console-resident points, the redundant console for a
DeltaV Operate for PROVOX Console cannot be a PROVUE console or an
Operator Workplace Console.
You can clone the configuration of another console if desired.
In the Standard Options field, select YES.
In the Database Size field, enter 10,000.
Setting Batch to YES is valid if you will have console-resident UNIT or Activity
points or will be targeting UNIT or Activity points sourced in a PROVUE or
Operator Workplace console to this console. The batch control software option must
be present on your console if you select YES.
Anything you enter in the Help Display, Detail Display, Trend Display, and Maint
Display fields is ignored by the console.
Note
Even though the Help and Maint displays are ignored by the console, you must configure
something in these fields or the configuration will not generate.
The Printer configuration fields are ignored by the console.
Option Definition Form

The Auto Point Select field is ignored by the console.
The Ack Selected Point is currently ignored by the console. In the DeltaV Operate for
PROVOX Console the ACK button in the Instrument Area acknowledges only
alarms on that point while the ACK button in the Alarm Banner area acknowledges
alarms for all points on the current display.
6-3
In the No. Alarm History Records field, enter 100. This field is not used by the
console but you must enter something or the configuration will not generate.
Note
If you make any changes to the No. Alarm History Records field you must perform a
total console download from the ENVOX software.
The Ack All Station Horns setting affects PROVOX alarm horns only and does not
affect horn acknowledgement behavior for DeltaV alarms.
For the three Percent of fields, calculate a value to enter by dividing the number of
points configured by the number of points specified in the Database Size field of the
Console Device Definition, then add five percent. For example, if you set the database
size to 10,000 points and your configuration includes 3000 points, enter 35.
(3000/10000 + 5 = 35).
System Clock List Form

This form is not used by the DeltaV Operate for PROVOX Console.
DeltaV Operate for PROVOX consoles use the Network Time Protocol service to
synchronize time. Refer to Chapter 8 of this manual for more information.
Shift Table Form

This form is used by the console as is.
Trend Set Definition and Trend Trace Definition Forms

In the Number Added Online field of the Trend Set Definition form specify the
number of trend traces you want the operator to be able to add on-line. The total
number of trend traces (those you configure plus those the operator adds on-line)
cannot exceed 1200 traces.
Note
Changing the number of trend traces the operator can add on-line requires a total
download. Size this field as large as possible, while keeping the total number of traces
below the console maximum.
The console uses all other configured trend information as is. However, there are
some differences in how trend data is stored, manipulated, and viewed from the
DeltaV Operator Station. In the console there are two parts to trending: trace data
sets and trend views.
6-4
Trace Data Sets

Each trace data set is a combination of tag, attribute (and occurrence, if necessary),
sample interval, and duration. Trace data sets are created in two ways:
Created from configured trend trace information downloaded to the console
Defined online from the operator station
Each point can have a maximum of 12 trace data sets in any combination of
configured or defined online.
Trace data sets created from the download cannot be deleted online. The only way to
delete them is to remove them from the configuration and download the console.
If the download contains more than 12 trend traces for a point, only 12 of these traces
are converted into trace data sets. The download order determines which trace
definitions are converted to trace data sets. The download order cannot be
determined and may vary from download to download.
Trend Views
Operators create trend views, either by importing configured trend sets or by creating
new views. Trend views include information on the appearance of the trend
information at the console. Operators save the trend views as .ptv files on the DeltaV
Operator Station and can reopen files as desired.
Make sure downloaded trace definitions are suitable for your process and operator
needs. Operators will not be able to delete or modify trace data sets for point and
attribute combinations that already exist in the download.
Operator Display List Form

The DeltaV Operate for PROVOX Console uses this form a bit differently than the
Operator Workplace or PROVUE consoles. For those consoles this form established
the list of displays that were downloaded to an Operator Workplace or PROVUE
console. Any displays not in the list were not available.
Use this form to list the displays that are defined as alarm displays when configuring
points. Alarm displays are the displays that appear when an operator clicks a button in
the Alarm Banner. Every alarm display must be in this list. (Displays that are not
defined as alarm displays do not need to be in this list.)
Note
Display names you configure in the ENVOX software for use on the DeltaV Operate
for PROVOX Console must be valid PROVOX display names.
6-5
PROVOX display names must:
Start with a letter
Contain only letters and numbers (these are the only characters valid in ENVOX
configurations that are also valid in DeltaV Operate)
If you create only the one required dummy display and enter other display names in
the Operator Display List the configuration software reports warnings when
generating the configuration. You can ignore the warnings. If you want to eliminate
the warnings you can create a dummy display for every display listed in the Operator
Display List.
Note
The Display No. (number), Display Forward, Display Backward, and Overview fields
are not used by the console, but must be completed for a valid generate.
The maximum number of displays a DeltaV Operate for PROVOX Console can
contain is limited only by the disk space available and allocated on the console hard
disk.
However, the number of alarm displays for points still depends on the configuration
software limits: The 500 point console allows 77 alarm displays, the 2000 point
console allows 212 alarm displays, and the 10,000 point console allows 1050 alarm
displays.
PMA List Form

The console uses this form as is.
User Access List Form

Pen Recorder List Form

The console does not use this form.
Report List Definition Form

6-6
Report Header Definition Form

Equipment List Form

Configuring Reports
Use the Language Editor of the configuration software to create reports. Note that
the display attributes you can use when configuring reports are the Operator
Workplace display attributes, not the DeltaV Operate for PROVOX Console display
attributes. In most cases these are the same, but there are some attributes named
differently and some attributes that are available for console displays that are not
available for reports.
To see the attributes available for reports, refer to the PROVOX online book
Reference Tables. It contains a pointer to the help files for report attributes.
Some attribute values are reported differently in the console than in Operator
Workplace or PROVUE consoles. Refer to the online help for attributes for
information on the values returned.
Console Preferences Form

You can set the Session Timeout and Input Timeout from the DeltaV Operator
Station. To set either or both times, at the console Start menu navigate to DeltaV
Operate for PROVOX | Settings | Console Properties. When the dialog opens, select
the Instrument Areas tab. If the console software is already running, you must close
and re-open the instrument area for the new values to take effect.
Horn Tone Definition Form

Display Limits Form

6-7
Procedures Forms
The console uses the Procedures forms to establish procedure names, process names,
and so on. If you are going to be operating procedures, you must configure the
appropriate forms and fields.
Conditional Color Editor

The console does not use the Conditional Color editor.
The console implements conditional color on display objects by applying dynamic
color and visibility to multiple display objects in the Configure mode of DeltaV
Operate.
For example, to have a valve appear in one color if a pump is off and in other colors
depending on flow rate if a pump is on, you would create two or more pump graphics
and stack them. One valve would be visible if the pump was off and one of the others
would be visible if the pump was on.
Refer to the section Animating Object Properties in the DeltaV Books Online for more
information on using dynamic color and visibility.
Conditional Text Editor

The console does not use the Conditional Text editor.
The console implements conditional color by applying dynamic color and visibility to
multiple text objects in the Configure mode of DeltaV Operate.
Refer to the section Animating Object Properties in the DeltaV Books Online for more
information on using dynamic color and visibility.
PMA Definition Form

Note
6-8
The default SYSTEM PMA that the ENVOX software creates is not a valid name
for the DeltaV Operate for PROVOX software. You must rename the PMA to use
it. For example SYSTEM-PMA.
PPA Definition Form

Note
The default SYSTEM PPA that the ENVOX software creates is not a valid name
for the DeltaV Operate for PROVOX software. You must rename the PPA to use it.
For example, SYSTEM-PPA
Alarm Priority Definition Form

Note
The console support for the extended PROVUE alarm colors depends on where the
alarm indication appears.
In some places the console supports only colors 0 through 15. In other places the
console supports the full PROVUE alarm color set:
Display faceplates, the alarm banner, and the alarm summary support only colors
0 through 15. Alarms that use either foreground or background colors with an
index greater than 15 are set to Yellow Blink foreground and Red background.
The Instrument Area supports the full set of PROVUE alarm colors except that
the gray color is mapped to a salmon pink. The alarm gray does not provide
enough contrast against the gray background the console uses.
If it is important for alarm indicators to always appear in the same colors, use colors
with color indexes from 0 through 15.
Alternatively, you can specify that PROVOX alarms be processed in DeltaV style for
use in an alarm banner that combines both PROVOX and DeltaV alarms. The alarm
colors in the alarm banner will be DeltaV colors. Alarm colors in PROVOX
faceplates, the PROVOX Alarm Summary, and the Instrument Area remain
PROVOX alarm colors.
User Definitions Form

The console uses this form as is. However, there are a couple of things you must do to
implement a secure environment.
First, as part of the way PROVOX security is implemented in the console, DeltaV
Operator Stations are considered users and must be defined as such. An operator's
access to the PROVOX process is determined both by the operator's privilege
6-9
configured in the ENVOX download and the configured privilege level of the DeltaV
Operator Station.
The recommended procedure is to configure each DeltaV Operator Station that is a
dedicated operator station as a user in the configuration software. Define these users
with privileges consistent with the requirements of each console and your plant's
security policy.
To allow access to other users who log on from operator stations that are not
dedicated operator stationsmanagers and engineers, for exampleconfigure the
special user ANYNODE in the configuration software. The ANYNODE user sets
the privilege for any DeltaV Operator Station that is not explicitly configured as a
user. Set the ANYNODE user's privileges consistent with your plant's security
strategy.
Note
You must define DeltaV Operator Stations as users or define the ANYNODE user
in configurations downloaded to DeltaV Operate for PROVOX Consoles or users will
not have any privileges after logging in to the console software.
Second, if you want users configured in the DeltaV Operator Station User Manager to
have access to the PROVOX system you must add their user names to the ENVOX
download.
When you define the DeltaV users, DeltaV Operator Stations, and ANYNODE
users, define passwords for them as well. Use secure PROVOX passwords to ensure
console security. Secure passwords include the string DELTAV or STATION. Refer
to Chapter 5 of this manual for more information on secure passwords and single
secure logons. If your installation has DeltaV Operator stations that do not have
secure PROVOX passwords, users who know the password of an Operator Station
can log on to any DeltaV Operator Station.
PROVOX Privilege Example
An operator's access to the PROVOX process is the most restrictive of the operator's
configured privilege and the DeltaV Operator Station's privilege in the ENVOX
download. For example, operator Sam with a base privilege of OPERATE is logged
on to the DeltaV Operator Station CONSOLE2. CONSOLE2 is configured as a user
with TUNE privilege. However, operator Sam has only OPERATE privilege so he
cannot tune any points.
Engineer Joe, whose base privilege is TUNE, needs to tune a point. He logs on to
CONSOLE2. Because both Joe and CONSOLE2 have TUNE privilege, Joe can tune
the point.
6-10
The plant also has a DeltaV Operator Station named DEMO1 that is not configured
as a user. The ANYNODE user has been configured with OPERATE privilege,
however, so that privilege applies to DEMO1. If engineer Joe had logged onto
DEMO1, he would not be able to tune the point as his TUNE privilege would not be
able to overcome the more restricted access of the ANYNODE user definition.
User Application List Form

User UDK List Form

Application Definition
User Defined Key

User Palette
Highway Access Control List Form

Display Editor
The console does not use displays created by the Display Editor. However, you must
use the Display Editor to create a single empty display. The configuration must
contain at least one display for it to generate. Also note that every display listed in the
Operator Display List and configured during targeting as a point's Alarm Display that
does not exist in the configuration causes a warning during generation. You can
ignore the warnings. To eliminate the warnings you must create a dummy display for
every display listed in the Operator Display List.
6-11
Console Points
The console can host any of the console-based points:
Accumulation Point
Activity Point
Console DCD Point
Maintenance Point
Console EPCI Point
Integrity Point
Single-Bit Discrete Point.
In addition, the console can be a target for console-based points and operate those
points that originate in a PROVUE or Operator Workplace console as long as the
source PROVUE or Operator Workplace console is running.
Targeting Points to a Console

Targeting PROVOX points to the console is accomplished the same way as for
PROVUE and Operator Workplace consoles. The following subsections list the
forms involved.
Target Data
Console Target Data

The console uses this form as is. The displays configured as Alarm Displays for each
point must also exist in the database to prevent generation warnings.
Extended Alarms
6-12
Chapter 7
Display Configuration
Introduction
One of the most useful features of the DeltaV Operate for PROVOX console is its
ability to display graphical representations of your process. These displays can help
operators understand and control the process.
For general information on creating displays for the DeltaV Operate environment,
refer to Creating Pictures in the DeltaV Books Online.
This section explains only PROVOX-specific information you need to create displays
that reference data from the DeltaV Operate for PROVOX Data Server (also known
as Console Data Server).
This section also discusses using DeltaV Operate to create displays and explains some
of the ways to provide display functionality that is similar to that of PROVUE and
Operator Workplace displays.
Display Names in the ENVOX Configuration

Though you use the DeltaV Operate software to create displays for the operator
stations, there are a couple of places in the ENVOX software you need to create or
name displays.
The ENVOX configuration must contain at least one display (it can be blank) for the
configuration software to successfully generate and download the configuration. If
your configuration uses alarm displays (a particular display opens when an operator
clicks on an alarm button in the alarm banner), you must include the alarm display
names in the Operator Display List and the displays must exist in the ENVOX
database.
Note
Alarm displays (displays that are configured as alarm displays for points, PPAs, and
PMAs) must be included in the Operator Display List for the console.
See the subsection Operator Display List Form for more information on configuring
the Operator Display List.
7-1
The display names you configure in the ENVOX software are limited to 12 characters.
To ensure that the names you configure in the ENVOX software are compatible with
DeltaV Operate display names, begin each name with a letter and complete the name
with letters and numbers only. There are more characters that are valid in the ENVOX
software but these characters are not valid in DeltaV Operate.
Note
Display names you configure in the ENVOX software for use on the DeltaV Operate
for PROVOX Console must be valid PROVOX display names.
PROVOX display names must:
Start with a letter
Contain only letters and numbers (these are the only characters valid in ENVOX
configurations that are also valid in DeltaV Operate)
It is recommended that you change your ENVOX configuration to make all tags and
display names valid for DeltaV Operate. However, the Tags tab of the Console
Properties dialog provides character substitution for tagnames and display names.
This tab is intended only to ease the transition from earlier PROVOX consoles to
DeltaV Operate for PROVOX Consoles.
For more information on the Tags tab refer to its online help and Chapter 5 of this
manual.
Display Names in DeltaV Operate

In DeltaV Operate each display is a file with a .GRF extension. Display files are in the
directory \DeltaV\DVData\Graphics-iFIX\PIC. The display name and file name
are the same and the display name is stored within the display. Display names must
follow the DeltaV Operate rules. The name must:
7-2
Start with a letter
Contain only letters, numbers, and underscores (_)
Display Elements and Link Limits

Displays are made up of static and dynamic elements. Static elements include lines,
circles, bitmaps, and text. Dynamic elements include information fields that report
data, as well as static elements to which dynamic properties have been applied to
control the element's size, visibility, color, and so on.
Dynamic elements use tagnames to link to attributes in the console database. Example
attributes include common attributes such as setpoint and point mode, as well as
attributes such as alarm status and critical level.
Console resources are required to process each link to the database and therefore a
large number of dynamic elements on displays can affect console performance.
Alarm Colors
If you create objects in pictures and assign alarm colors to them you have the option
of using DeltaV alarm colors or PROVOX alarm colors. You might want to use the
DeltaV alarm colors if you are using the combined alarm banner and DeltaV-Style
alarm processing. If you do, alarm colors in your displays match the alarm colors in
the alarm banner.
To set an object's colors:
1. Double click an object in the display to open the Basic Animation Dialog.
2. In the Color area of the dialog select what to apply color to, Foreground for
example.
The Foreground Color Expert opens
3. In the Data Source field select or browse to a parameter
4. Select the Use Shared Threshold Table check box.
5. In the Shared Table field, click the browse button.
The Expression Builder opens.
6. Select the Globals tab.
7. Open frsVariables.
7-3
8. To use DeltaV alarm colors select Alarm_Color_Table.

To use PROVOX alarm colors select PROVOX_Color_Table.
9. Click OK to close the Expression Builder.
10. Click OK to close the Foreground Color Expert.
11. Click OK to close the Basic Animation Dialog.
Note that PROVOX faceplates, the Instrument Area, and the PROVOX alarm
summary use the colors configured in the ENVOX software. If you want the alarm
colors in these items to match the alarm banner, you must reconfigure the alarm
colors in the ENVOX software.
Using the Expression Builder

The Expression Builder is a tabbed dialog. Each tab contains information about one
type of data source. For DeltaV Operate for PROVOX systems the primary tab of
interest is the Data Servers tab. This tab contains a hierarchical browser list of PMAs,
PPAs, Points, and users on the Console Data Server the operator station is connected
to. Using the browser you can navigate through the list to find and select an attribute
reference (tagname). You can access the Expression Builder from most dialogs that
use tagnames.
Datalink Dialog
For example, when you insert a data link in a display, the Datalink dialog appears as
shown in the figure.
Note
7-4
The example uses the Datalink dialog, but most dialogs that require or use tagnames
work the same way.
Figure 7-1
Datalink Dialog
Expression Builder
Clicking the button on the Datalink dialog opens the Expression Builder. Select
the Data Servers tab as shown in the figure.
7-5
Figure 7-2
Expression Builder
You can use the Filter area and button to reduce the amount of information shown. A
different filter can be applied at each level. For example, in the figure the filter T* was
applied at the point level and the filter P* was applied at the attribute level.
For more information on using the Expression Builder, click on the Help button. For
help on PROVOX attributes, click on the link from the help for the dialog.
7-6
Selecting A Tag and Attribute

Start by opening the POC branch of the hierarchy. The Console Data Server this
operator station is connected to appears. Four items appear under the data server:
Plant Management Areas (PMAs), PROVOX points, Plant Process Areas (PPAs), and
users. Open Points to see a list of all points configured for that server. Open a point to
see all the attributes associated with that point.
Navigate through the hierarchy by clicking items and using the scroll bar as necessary.
After you have navigated to and selected the desired combination of tag and attribute
(and occurrence, if necessary), the selected tag and attribute and a valid default field
appear in the expression box. For example, in the figure the expression is:
POC.TIC101/PCTINTSP.F_CV
Click the OK button to transfer the attribute reference to the Datalink dialog Source
field.
Note that there are four field types:
A_CV ASCII text
F_CV Floating-point number
I_CV Integer
B_CV Boolean value
You can change the I_CV and B_CV fields to F_CV if you desire.
If you are going to compare Boolean values, change them to floating-point numbers
and compare them numerically. False = 0 and True is any non-zero value.
Editing Occurrence Numbers

If you select an attribute that has multiple occurrencesfor example, the DDPLD
attributethe value that appears in the expression box of the Expression Builder
looks like:
POC.TIC101/DDPLD[0..1023][0..63].A_CV
You must edit the occurrence numbers to valid values. You can edit the occurrence
number in the expression box of the Expression Builder or in the Datalink dialog.
7-7
If you have not edited the occurrence values and click OK on the Datalink dialog the
following message appears:
To edit the occurrence numbers click Use Anyway, then double click the data link to
re-open the Datalink dialog.
Tagnames
The term tagname usually refers to the specifier for a PROVOX point attribute. A
tagname consists of the node name, point tag, field, attribute name, and occurrence, if
any.
There are a few things to be aware of when specifying tagnames (attribute references)
while creating displays. The recommended method to specify a tagname is to use the
Expression Builder that opens if you click the button in a Source field of a dialog.
Some dialogs and circumstances may require that you edit the tagname after selecting
and inserting it into a dialog.
If you use tagnames in scripts or enter tagnames rather than use the Expression
Builder, there are a few things to be aware of:
7-8
Your PROVOX configuration database tags must be valid DeltaV Operate

tagnames (contain only letters, numbers, and dashes ()).
If you enter tags rather than use the Expression Builder, there is a recommended
syntax to use in most cases.
Entering tagnames in dynamos may require that you edit the tagname after you
insert it.
Entering Tagnames
The recommended method for entering tagnames is to use the Expression Builder to
find and select a tag and attribute. However, you can enter tagnames directly.
Note
This discussion applies only to tagnames referring to PROVOX points and attributes.
References to DeltaV data begin with DVSYS and have a different syntax. Refer to
the DeltaV documentation for more information.
Recommended Syntax
If you enter tagnames directly without using the browser, this recommended syntax
most closely matches the DeltaV syntax:
POC.tag/attribute[occurrence].field
where
POC specifies that the reference is to PROVOX data
tag is the point tag
attribute is a PROVOX attribute valid for that point type.
occurrence may be required depending on the attribute and specifies the number of the
occurrence you want to use. If you do not enter an occurrence, zero (0) is the default.
field is one of the following:
Note
A_CV ASCII format. Displays text and numeric data as ASCII strings.
F_CV Floating Point Format. Displays numeric data as floating-point

numbers.
I_CV Integer
B_CV Boolean value
CV in this context refers to "the current value" of the attribute and is not related to
configured variables.
If you enter a tagname (attribute reference) that does not exist in the Console Data
Server database, the following appears:
7-9
Select the Use Anyway button if you are sure you want to use this tagname. For
example, if you entered a tagname that is not currently downloaded but will be later.
Select Cancel to return to the Datalink dialog to edit the tagname you entered.
Display Attributes
The attributes available to create displays are identical in most cases to the display
attributes available for the Operator Workplace console. Some of the Operator
Workplace attributes no longer apply, some are implemented differently, and some
have been renamed. In addition, some new attributes have been added.
Online help for display attributes is available from the Expression Builder. To access
the help, click the Help button on the browser, then click the link to PROVOX
attribute help.
The following table shows the attributes that have been renamed.
Table 7-1 Renamed Display Attribute
Operator Workplace Attribute
7-10
New Attribute Name
%BI
BIASPCT
%INTSP
PCTINTSP
%OUTPUT
OUTPUTPCT
%PV
PVPCT
%SP
SPPCT
MVPCV1 through MVPCV9
MVP%CV1 through MVP%CV12
MVPPCTCV01 through MVPPCTCV12
RA
RATIO
The following table lists the attributes that are not available in Operator Workplace
Table 7-2 Attributes That are in DeltaV Operate for PROVOX Software but not in Operator Workplace
Attribute
Meaning
ALMPRIODV
DeltaV-style alarm priority
BVAR
Unit point boolean variable
CALCEXPR
Calculation expression
CALCVAL
Calculation expression value
CDISPLAY
Control display for current point in Instrument Area
CHAL
Highway access list number of point in Instrument Area
CPPA
Plant Process Area for point in Instrument Area
CTAG
Point tag of point in Instrument Area
DECPT
Number of decimal points configured
EALMDBND
Extended alarm deadband
EALMLMT
Extended alarm limit
EALMTYP
Extended alarm type
FSTADV
Advance an LCP FST (Function Sequence Table)
FSTSTART
Start an LCP FST
FSTSTOP
Stop an LCP FST
GTAG
Graphics tag
HOPER
Unit Point Operation
HOPERTIME
Unit Point Operation Timer
HUNIT
Unit Point Tag for Operation
HUNITDSCR
Unit Point Description for Operation
NUMGRD
Number of grades configured for the procedure
NUMOPSTATE
Number of operational states configured for this PPA
NUMPDR
Number of procedures in the activity point
NUMPHS
Number of phases configured for the operation.
NUMPNTSET
Number of point sets configured for the procedure
NUMPRS
Number of processes configured for the procedure
7-11
Table 7-2 Attributes That are in DeltaV Operate for PROVOX Software but not in Operator Workplace
Attribute
Meaning
NUMSP
Number of setpoints for this DCD or Group point
OARMSGP
OAR message pending
PNTSLCTD
Point selected (in an Instrument Area)
PPANAME
Plant Process Area name
PVEQSP
PV equal Setpoint (DCD and Group points only)
STALE
Stale data
STALEDEVICE
Stale device
STALEPOINT
Stale point
TIME
Time function
ZALMBG
Alarm background color in priority order
ZALMFG
Alarm foreground color in priority order
ZALMPR
PROVOX alarm priority in priority order
ZALMPRDV
Adds 3 to the PROVOX alarm priority so you can map to

DeltaV alarm priorities and colors in priority order
ZALMSTR
Alarm word in priority order
ZALMVIS
Alarm visibility (of active alarms) in priority order
ZSTATBG
Point status background color in priority order
ZSTATFG
Point status foreground color in priority order
ZSTATSTR
Current point status in priority order
ZSTATVIS
Status visibility (of active statuses) in priority order
The occurrence numbers for the attributes that begin with Z are the current relative
priority. For example, ZALMSTR[2] displays the configured alarm word for the alarm
that currently has the second highest priority of all alarms at the console.
For more information on display attributes and their use, refer to the PROVOX
online book Reference Tables, which provides a link to the online help for display
attributes.
7-12
The following table shows the Operator Workplace console attributes that are not
available in DeltaV Operate for PROVOX software.
Table 7-3 Operator Workplace Attributes Not Implemented
Operator Workplace Attribute
Equivalent
ACOLINV
Implemented with dynamic properties
ACOLNOR
Implemented with dynamic properties
STATUSER
None
Calculation Attributes
Use the calculation attributes, CALCEXPR and CALCVAL, to create expressions
containing point attributes and use the results of the expressions in displays, either by
reporting the result directly or using the result to set the appearance of a display
element.
Note
The Calculation Expressions Editor is included in the software to maintain backward

compatibility with earlier versions of PROVOX Operator Console software. Use the
editor to access previously configured expressions.
If you are creating new expressions it is recommended that you use the Mathematical
Functions available in the Expression Builder.
Use CALCEXPR to display the expression. Use CALCVAL to return the value of an
expression. The CALCEXPR and CALCVAL attributes appear in the Expression
Builder, but do not necessarily need to refer to the point used to navigate to them.
Entering Expressions
To enter and use expressions:
1. From the Start menu navigate to DeltaV Operate for PROVOX | Engineering |
Calculation Expressions Editor.
You can also add a Calculation Expressions Editor button to the DeltaV Operate
configure mode toolbar from the ComConTools button palette.
2. In the browser, navigate to and select a point.
3. Click the Edit Calc Attr Exprs button to open the Point Calculations
Expressions Editor
7-13
4. Edit the CALCEXPR expressions for the point.

5. Use DeltaV Operate in configure mode to add data links referencing the
CALCVAL (and CALCEXPR if desired) attributes for the point.
The Point Calculation Attributes Expressions dialog appears as shown in the figure.
Figure 7-3
Point Calculation Attribute Expressions Dialog
The read-only field in the upper left corner indicates the point you are creating
CALCEXPR attributes for. The dialog contains five Expressions fields, one for each
expression you can create for this point. Calculation expressions are not case sensitive
or space sensitive. The fields are free form and syntax checking is not performed until
input focus moves to another part of the dialog.
Each expression can be as long as 80 characters and can refer to other attributes and
occurrences. The attributes and occurrences can refer to other points.
The value returned by CALCVAL is a floating-point number. The Values field
contains the current value of the corresponding expression. The software updates the
Values field periodically.
Calculation Expression Syntax

Each calculation expression has the following syntax:
argument operator argument
7-14
In each expression, argument can be one of the following:
Another expression
A number
A function
A constant
A point attribute reference
For more information on these refer to the online help for calculation attributes. You
can get to the help by pressing F1 from the Point Calculation Attribute Expressions
dialog or from the online book Reference Tables. This online book contains a link to the
online help for display attributes. From that help you can navigate to information on
the calculation attributes.
Example Calculation Expressions

The operators, functions, and constants available to calculation expressions make it
possible to create powerful expressions. The ability to refer to other calculations, even
for other points, extends the functionality.
Refer to the following examples:
time(1)
Returns the current number of milliseconds past the last second.
({|PV}+{COMP3LP1|PV})
Add the PV of the point this calculation attribute is configured for to the PV of
point COMP3LP1.
ABS({COMP2LP2|PV}-{COMP4LP2|PV})
The absolute value of the difference of two point PVs.
ABS({|PV}-{|SP})
Returns the absolute value of the difference between this point's PV and SP.
ABS({|PV} {|SP}) > 10 ? 3 : 11

If the absolute value of the difference between the PV and SP of this point is
greater than 10, return 3. Otherwise, return 11.
{|PV}>{FIC-31|PV}) ? {|PV} : {FIC-31|PV}

Returns the PV of this point if it is greater than the PV of point FIC-31.
Otherwise, returns the PV of point FIC-31.
7-15
ABS({|PV}{|SP})>10?ABS({|PV}{|SP})>20?3:2):1
Returns 3 if the deviation is greater than 20. Returns 2 if the deviation is greater
than 10 but less than or equal to 20. Returns 1 otherwise.
{|PNTSLCTD[0]}
This expression shows the syntax to refer to occurrences of an attribute.
Calculation Attribute Expression Files

The console software uses three files on the Console Data Server to store calculation
attribute expressions:
CalcAttrs_Master.csv
You create and maintain this master file of calculation attribute expressions. You
can use this file to ensure that all Console Data Servers have the same calculation
attribute definitions available. This file is not modified by any changes you make
and save online.
CalcAttrs_Current.csv
The console software creates and maintains this file as you define calculation
attributes. If your system has redundant Console Data Servers, changes and
additions to expressions are saved in the CalcAttrs_Current.csv file on the
currently active Console Data Server. Note that there can be multiple versions of
the CalcAttrs_Current.csv file, one on each Console Data Server of a redundant
pair.
CalcAttrs_Previous.csv
This file is created at the start of a database update. The expressions in use are
saved in this file on the currently active Console Data Server.
The default directory for expression files is the \cfg directory under the console
software installation directory, but you can change this from the Calculation
Expression tab of the Console Properties dialog (from the Start menu navigate to
DeltaV Operate for PROVOX | Settings | Console Properties) on the Console Data
Server Properties dialog.
After a database update the console software loads the definitions in the files
CalcAttrs_Master.csv (if it exists) and CalcAttrs_Current.csv. If both the master file
and the current file define expressions for the same combinations of point and
calculation attribute occurrence, use the Console Properties dialog to set which file
the console uses to define the attributes.
7-16
The format of a calculation expression in one of the calculation attribute files is:
TAG,occurrence,expression
The tag and expression are in double quotes and the occurrence value is a single digit
from 1 to 5. Note that the double quotes are optional in the input files.
For example, the expression defined for one point that returns the absolute value of
the difference of the PV of two other points looks like the following in an expression
file:
"COMP4LP1",1,"ABS({COMP2LP2|PV}-{COMP4LP2|PV})"
THISUSER Display Attributes

Four display attributes, CDISPLAY, CHAL, CPPA, and CTAG, are not point
attributes, but provide information on more general aspects of the current operator
session. Therefore, these attributes are not found in the Expression Builder. To use
them you must enter them in the Datalink dialog.
Note
CDISPLAY, CHAL, CPPA, and CTAG do not appear in the Expression Builder
because they are not point attributes.
To use the CDISPLAY, CHAL, CPPA, and CTAG attributes the correct syntax is:
POC.THISUSER.field_attribute[occurrence]
POC and THISUSER are required.
field_ will be one of the four listed in Selecting A Tag and Attribute on page 7-7
depending on what the attribute returns.
attribute will be one of the four THISUSER attributes.
occurrence corresponds to a particular instance of the Instrument Area. Occurrence

1 corresponds to the first Instrument Area.
For example, to display the point tag of the point in the instrument area, use the
following:
POC.THISUSER.A_CTAG[1]
The A_ is required because CTAG returns a text string.
7-17
Using Scripts
The DeltaV Operate environment includes a Visual Basic for Applications (VBA)
scripting language available from the displays you create. You can write scripts that
perform a number of functions, both general to displays (changing colors, animating
graphics, and so on) and specific to PROVOX and DeltaV systems (opening
PROVOX applications, acknowledging the horn, and so on). For general information
on using scripts refer to the section Getting Started with DeltaV Operate and VBA in the
DeltaV Books Online.
The DeltaV Operate for PROVOX software includes several Visual Basic functions
you can use to access DeltaV and PROVOX functionality from scripts. Two
commands are PROVOX specific:
frsPocTasks "command", "optional param1",_

"optional param2", "optional param3"
frsPOCIntegrity "IntegrityFaceplate",_
"server", object
Three other commands are useful for both DeltaV and PROVOX functions:
frsInputAnyModuleNameFP
frsInputAnyModuleNameDT
frsInputAnyModuleNamePD
Refer to the DeltaV Automation help in DeltaV operate for complete information on
these commands. This document explains the PROVOX use of these functions.
frsPocTasks
Use frsPOCTasks to access a number of PROVOX functions.
PROVOX Instrument Area
To open an instrument area use frsPocTasks in the following ways:
frsPocTasks "IA1", "TAG", "POSITION"
Opens point TAG in Instrument Area 1 at the specified position where POSITION is
A, B, C, D, or Home as defined in the Console Properties dialog.
7-18
Example:
frsPocTasks "IA1", "LOOP707-001", "B"
To open Instrument Area 2 use the command in the form:
frsPocTasks "IA2", "TAG", "POSITION"
PROVOX Trend Application
To open the PROVOX Trend application, use frsPocTasks in the following way:
frsPocTasks "Trend1", , "POSITION"
To open Trend Window 1 at the home position:
frsPocTasks "Trend1", , "HOME
To open Trend Window 2 in position B:
frsPocTasks "Trend2", , "B"
Note that the two commas are required. POSITION has the same meaning and use as
for the Instrument Area task.
After a trend window is open an operator can load configured trend sets, open saved
trend view (*.ptv) files, and add traces to trends.
To open a trend window and load a trend view or configured trend set from a script,
use the DeltaV frsRunTask Visual Basic subroutine to call the DeltaV Operate for
PROVOX PTV (PROVOX Trend View) application. For more information refer to
Chapter 8 of manual.
PROVOX Horn and alarm
There are two ways to use frsPocTasks to access the PROVOX horn and alarm
functionality:
To silence the PROVOX horn (does not silence the DeltaV horn):
frsPocTasks "HornSilence"
To acknowledge the alarms on a particular point:
frsPocTasks "AckAlarm", "TAG"
7-19
Example:
frsPOCTasks "AckAlarm", "LOOP707-001"
Console Data Server Redundancy
There are several forms of the frsPocTasks routine that access Console Data Server
Redundancy:
To switch to the Primary Server:
frsPocTasks "ServerSwitchPrimary"
To Switch to the Secondary Server:
frsPocTasks "ServerSwitchSecondary"
To enable Auto Switchover
frsPocTasks "ServerAutoSwitchEnable"
To disable Auto Switchover:
frsPocTasks "ServerAutoSwitchDisable"
Console Resident Point Redundancy
There are several forms of frsPocTasks that access console-resident point
redundancy:
To manually switch control to the standby server:
frsPocTasks "PointManualSwitch"
To enable automatic switchover of console resident point redundancy:
frsPocTasks "PointAutoSwitchEnable"
To disable automatic switchover of console resident point redundancy:
frsPocTasks "PointAutoSwitchDisable"
Other PROVOX Tools
To open the PROVOX Event Journal and point and press a particular server button:
frsPocTasks "ViewJournal", "BUTTON"
7-20
Example:
frsPOCTasks "ViewJournal", "2"
To open the PROVOX Status Summary viewer and press a particular server button:
frsPocTasks "ViewSummary", "BUTTON"
To open the PROVOX Report viewer and press a particular server button:
frsPocTasks "ViewReport", "BUTTON"
To open the PROVOX Documentation viewer and press a particular server button:
frsPocTasks "ViewDocumentation", "BUTTON"
To perform a PROVOX Database Update on the console:
frsPocTasks "DatabaseUpdate"
To open the PROVOX Change User dialog:
frsPocTasks "ChangeUser"
To open the Calculation Attribute Editor:
frsPocTasks "CalculationAttributeEdit"
frsPOCIntegrity
Use the frsPOCIntegrity routine to open the PROVOX integrity display. The form of
the command to use is:
frsPOCIntegrity "IntegrityFaceplate", , _ optional
object
object is the picture that contains the script--usually Me. (Me is a VBA keyword that
refers to the object containing the function. For this function, Me refers to the picture
from which the function was run.) Note that the two commas are required.
For example, to open the Integrity on the screen containing the current picture:
frsPOCIntegrity "IntegrityFaceplate", , Me
7-21
frsInputAnyModuleNameFP
Use frsInputAnyModuleNameFP to open the faceplate for any PROVOX point or
DeltaV module. The form of the command to use is:
Public Sub frsInputAnyModuleNameFP(Optional objPic As Object, _
Optional strModPassed As String = "", _
Optional lngMonOverride As Long = 0, _
Optional blnDoNotAsk As Boolean = False, _
Optional strServerHint As String = "")
objpic is the picture that contains the script--usually Me
strModPassed is a valid PROVOX point tag or DeltaV module name
lngMonOverride is which monitor to bring it up upon.
blnDoNotAsk is true to ignore errors and not bring up a dialog to request a tag.
strServerHint is "DVSYS" for DeltaV modules and "POC" for PROVOX points.
For example, to open the faceplate for the PROVOX point
LOOP707-001 on the current picture:
frsInputAnyModuleNameFP Me, "LOOP707-001"
If you leave the tag or module name parameter blank a dialog appears when the
command is invoked to prompt the operator for a tag or module name.
frsInputAnyModuleNameDT
This command works exactly like frsInputAnyModuleNameFP except that it opens
the detail display for the PROVOX point or DeltaV module. Note that the detail
display for PROVOX points is the PROVOX Instrument Area.
frsInputAnyModuleNamePD
This command works exactly like frsInputAnyModuleNameFP except that it opens
the configured primary control display for the PROVOX point or DeltaV module.
7-22
Accessing DDP Values from Scripts

You can read and change DDP values from scripts. For the DDP value to be available
to the script, the DDP must be on the display from which the script is called.
Note
Under some circumstances the DDP value may be stale. You can write your scripts to
check for stale data and wait for the DDP value to be refreshed before the script uses the
value.
#Current
The DeltaV Operate for PROVOX Console does not support #Current functionality.
See the documentation on tag group substitution of the scripting language for
functionality that is similar to #Current.
Writing Attributes from Displays

There are a couple of things to be aware of when configuring displays that contain
data entry fields for operators to enter values.
Entry fields on displays do not trap or report errors generated in field devices. For
example, if you have an input field configured to accept a point mode and an operator
attempts to change the point's mode to an invalid mode, or attempts to change the
setpoint when the point is not in an appropriate mode, no message appears. In
contrast, if the operator attempts to change the point's mode from the Instrument
Area an error message does appear.
Field Types
When you add an attribute to a display the DeltaV Operate software assigns it the
default field type for the attribute. You can change the I_ and B_ fields to F_ fields if
you desire.
You can also change F_ fields to A_ fields. For example, if your console has a loop
point and you configure an input field for the setpoint, you can leave it as F_ or
change it to A_. There are advantages and disadvantages to both entry types.
How the console software interprets a field in a display depends on the field type.
7-23
ASCII Fields (A_)

The console software attempts to interpret ASCII input as something appropriate for
the attribute. The console software does not perform range checking on ASCII input
fields. The software attempts to process whatever is entered. If the value entered is
not appropriate (entering ABC for a loop output value, for example), nothing
happens. No error message appears and the value does not change.
For entry fields for attributes that have both ASCII and numeric values, MODE for
example, an ASCII entry field accepts either the ASCII string or the numeric value
MAN or 1, for example.
Floating-point Fields (F_)
If the input field is configured as a floating-point field, the software performs some
checking at the console. If the operator enters something that is not a number, the
console reports an error.
The software also performs range checking on fields configured for floating-point
input. The range checked depends on how you configure the entry field.
Integer Fields (I_)
If the input field is configured as an integer field, the software performs some
checking at the console. If the operator enters something that is not a number, the
console reports an error.
The software also performs range checking on fields configured for integer input.
The range checked depends on how you configure the entry field.
Boolean Fields (B_)
If the input field is configured as a boolean field, the valid entries are 0 (zero) or false
for False, and any non-zero number or true for True.
If you are going to compare Boolean values, change them to floating-point numbers
and compare them numerically. False = 0 and True is any non-zero value.
Configuring Entry Fields

Use the Data entry area of the Datalink dialog to create fields that operators can use to
directly input values from graphics displays. To configure a field for entry, select In
7-24
Place in the Type field. To have DeltaV Operate request confirmation when an
operator changes a value, select the Confirm check box.
The DeltaV Operate software also includes the Data Entry expert you can use to
customize the entry field. Refer to the topic DeltaV Data Entry Expert in the DeltaV
Books Online for more information.
Writable Display Attributes

The table shows the PROVOX display attributes that are currently writable and how
they can be written.
Table 7-4 Writable Display Attributes
Attribute
Writable As
ASCIIMSG
ASCII string
BIASPCT
ASCII string, Floating-point
CRITLVL
DDPLOV
DDPLV
DDPROV
DDPRV
FSTADV
ASCII string
FSTSTART
ASCII string
FSTSTOP
ASCII string
MODE
MVPPCTCV01 through
MVPPVTCV12
ASCII string, Floating point
MVPSTATE
ASCII string
OPSTATE
OUTPUTPCT
PMAMODE
PV
7-25
Table 7-4 Writable Display Attributes

Attribute
Writable As
PVPCT
RATIO
SP
SPPCT
FST Attributes
The three FST attributes, FSTADV, FSTSTART, and FSTSTOP, are used a bit
differently than most other attributes. Though these attributes have display and
compare values (all three attributes provide information on the state of an LCP), their
primary purpose is to allow controlling FSTs from graphics displays.
Writing any ASCII value to one of the attributes has an effect on the LCP FST:
FSTADV Advances the FST
FSTSTART Starts the FST
FSTSTOP Stops the FST
To make it easier for operators to control FSTs from a display, you can create buttons
that have scripts attached that write to the attributes.
Managing Displays
Displays for PROVUE and Operator Workplace consoles are created centrally during
console configuration and downloaded from the configuration software to the
consoles. Displays for the DeltaV Operator Station can be created on one or more
configuration stations using DeltaV Operate in Configure mode.
Each operator station must have a copy of every display it uses in the
\DeltaV\DVData\Graphics-iFIX\Pic directory on the workstation hard disk. Refer
to the section in the DeltaV Books Online named Downloading and Uploading Operator
Pictures for more information.
7-26
Chapter 8
Operating Environment
Introduction
Though the DeltaV Operate for PROVOX Console and the Operator Workplace
Console can control the same PROVOX process control system, there are some
differences in the operator interface, primarily due to the differences between
hardware and software operating platforms. This section outlines and explains the
differences thought to be the most likely to cause confusion.
Note
The console software uses the standard Windows desktop. If you need to reinstall
Windows for some reason, do not install or enable the Internet Explorer Active
Desktop.
This section also explains how to tailor the operating environment security and how
to modify the appearance of some console features, where possible.
Supported Console Hardware and Software

The hardware and software components of the DeltaV Operate for PROVOX
Console have been chosen and designed to work together as units. It is important that
you do not use unsupported hardware and software.
Caution
The Console Data Server is a mission critical component of the control system
that is intended to run only Emerson Process Management supplied DeltaV
Operate for PROVOX software. Do not install or run any other software
applications on the Console Data Server.
Caution
DeltaV Operator Stations with the DeltaV Operate for PROVOX software
installed are intended for use only with the DeltaV Operate for PROVOX
Data Server and the DeltaV network, and are intended to run only Emerson
Process Management software. Emerson Process Management recommends
not installing any software applications other than the DeltaV Operate for
PROVOX software on the DeltaV Operator Stations.
8-1
Running other software applications on the Console Data Server or operator station
may negatively impact console operation. Emerson Process Management does not
support installations that disregard this policy.
Caution
The DeltaV Operate for PROVOX software is intended for operation only on
server and workstation hardware supplied by Emerson Process Management.
Do not install or run DeltaV Operate for PROVOX software on other
hardware.
Running DeltaV Operate for PROVOX software on other than Emerson Process
Management supplied hardware may negatively impact the operation of the DeltaV
Operate for PROVOX Console. Emerson Process Management does not support
installations that disregard this policy.
Console Security
Console security is one of the more important considerations when setting up a
console. For the DeltaV Operate for PROVOX Console there are several components
that combine to define console security:
Physical security
Console security
Operator Interface security
Process security
Physical security is accomplished by installing Console Data Server computers,

operator station computers, and other hardware into secure cabinets or equipment
rooms.
Console security is implemented at the Windows level and defines user accounts and
access for these accounts to Windows on both Console Data Servers and operator
stations. At this level users are granted access to the Windows desktop.
Operator Interface security defines the access users have to the operating
environment of the DeltaV Operate for PROVOX Console. At this level you can
define whether users have access to the DeltaV Operate main menu, title bar, popup
menus, and other functions.
8-2
Process security defines the users and operator stations that can access the Operator
Interface and the privileges users have at the process level. These privileges are
defined in the ENVOX software. Users are defined and assigned privileges exactly
the same as for PROVUE and Operator Workplace Consoles with one exception:
operator stations must be defined as users (or the ANYNODE user must be defined)
for users to be able to make process changes.
Refer to Chapter 5 of this manual for more information on implementing security.
Default User Accounts

On data servers, the default console software installation creates the Windows user
group PROVOX21 and the following accounts in that group:
Caution
PROVOX21Admina user with administrator privileges, including access to the

Windows desktop.
PROVOX21pintsan account on data servers that runs the web site for the
viewers. Do not delete, disable, or change the password of this account. This
account is created only on data servers.
If you change the password of the PROVOX21pints account, or make any

other changes to the account, you must re-install the console software.
You only need the PROVOX21Admin and PROVOX21pints accounts on data
servers and the PROVOX21Admin account on operator stations.

The software installation does not alter or remove the default Windows Administrator
account. That account is still available.
The PROVOX21Admin account is a normal Windows account. The
PROVOX21Admin account has Windows administrator privileges. Operators do not
use this account and they are therefore not a part of the following discussion.
On migration stations, the PROVOX21User account is created. This is a user without
administrator privileges that is subject to a system policy to restrict access to the
Windows desktop The PROVOX21User account is intended to be the account that all
operators at PROVOX Operator Consoles use to log on to Windows. The
PROVOX21User accounts access to Windows is severely limited and controlled by a
system policy file. For more information on security on migration stations, refer to the
8-3
PROVOX Operator Console P3.0 documentation. DeltaV Operator Stations use a

different method to control security that is discussed in the DeltaV documentation.
If you install the software as described in the installation or upgrade instructions, most
of the setup is complete. There are only a few things you must do after installation to
complete the setup of the console environment. If you have not already done so, refer
to Chapter 5 of this manual for more information on software setup.
Console Startup
If you have not altered the default installation, several services start automatically on
both the Console Data Server and operator station when they are started.
Console Data Servers open to the Windows login prompt and can be left as is. All the
Console Data Server services run without user intervention.
How operator stations start depends on their setup.
Horn
Refer to the DeltaV Books Online for general information on the horn.
If you are running the DeltaV Operate for PROVOX software and you exit the
Instrument Area and DeltaV Operate, the console services are still running on the
workstation. The PROVOX horn can still sound but you will be unable to silence it.
To avoid this be sure to log off of the PROVOX system by clicking the Logoff button
on the PROVOX Change Console User dialog.
To silence the horn, use the Silence Horn button on the DeltaV alarm banner. (Note
that the ack horn button on the PROVOX Instrument Area does not silence the horn.)
Time
In DeltaV Operate for PROVOX Consoles, the DeltaV Operate for PROVOX Data
Server maintains time synchronization only with migration stations (PROVOX
Operator Console Operator Workstations upgraded to communicate with DeltaV
Operate for PROVOX Data Servers). Note that PROVOX time synchronization
updates time only when the time difference between two machines is greater than 5
seconds.
Network Time Protocol
DeltaV Operate for PROVOX Operator Stations rely on the Network Time Protocol
(NTP) service for time synchronization. Refer to Appendix A of this manual for more
8-4
information on installing the NTP service on Console Data Servers. (The NTP
service is installed on operator stations as a part of the DeltaV software installation.)
Time Zone
Be sure to set the time and time zone consistently for all Console Data Servers and
operator stations. Select Start | Settings | Control Panel, then double click the Date
and Time icon to open the Date and Time dialog. You must be logged on with
Administrator privileges to set the date and time.
On the Date and Time tab of the dialog click the Change time zone button. The Time
Zone Settings dialog appears. Use the drop down list in the Time zone filed to select
the time zone. Select the check box that sets the operating system to automatically
adjust the clock for daylight saving time. Note that you may have to exit the dialog and
re-open the dialog to see your changes.
Note
The settings on the Time Zone Settings dialog (Time Zone and the Automatically adjust
clock for daylight saving changes check box) must be the same on all Console Data
Servers and operator stations in your PROVOX system.
If the time zone and daylight saving settings are not the same on all Console Data
Servers and operator stations, consoles may be unable to synchronize the time or may
stop synchronizing the time between the Console Data Servers and operator stations
when a daylight saving time rollover occurs.
Stale Data
PROVOX Point information is shown with a magenta background when the point
status is DUPDWT (Data Update Wait). On DeltaV Operate for PROVOX consoles
two additional conditions cause point data to appear with a magenta background:
The connection between the operator station and the Console Data Server is
severed.
A download merge or database coalesce is being performed on the Console Data

Server the operator station is connected to.
Instrument Area and DDP Area

In the DeltaV Operate for PROVOX Console these two functions are combined in
one dialog. To select a point to load in the control you use the Tags browser, which
contains a hierarchical list of points, PPAs, PMAs, and users. The Tags browser does
not contain a match facility, but if you click in the list area, pressing a key takes you to
the first tag that starts with that character.
8-5
Instrument Area
The instrument area looks and works much like the Operator Workplace instrument
area. As you change the points loaded in the instrument area, the controls in the
dialog change.
DDP Area
The DDP area is similar in appearance and function to the Operator Workplace DDP
window. To change a DDP's value, click on the DDP's information to open a dialog.
Enter or select a new value and click Apply or OK. DDP reference information is
available in the online help. To open the help, click the Help button.
Note that if you do not have TUNE privilege and attempt to change a DDP, nothing
happens. There is no other indication that you do not have TUNE privilege.
For some DDPs that have multiple occurrences, only the configured occurrences
appear in the DDP area (EALMLMT and EALMDBND).
Starting and Positioning

Instrument Areas can be opened from a batch file by running the application PIA.
The following table shows the command line switches available when starting the
Instrument Area application.
8-6
Table 8-1 Instrument Area Command Line Switches

Switch
Effect
-WIN n
Specifies which Instrument Area to affect. n is 1 or 2.
-TAG <tag name>
Opens the Instrument Area and loads a tag in it.
-DDP NONE | LOCAL

| REMOTE
Affects if and how the DDP pane appears. Use NONE to open the IA without opening the
DDP pane. Use LOCAL or REMOTE to open the IA and display local or remote DDPs.
-POS keyword
Positions the Instrument Area at one of the positions defined in the Positioning tab. Keywords
are HOME, A, B, C, and D. If no keyword is specified, the IA appears in the HOME position.
-POS TL <x y bx by>
Positions the Instrument Area in a location defined by pixel coordinates. The first parameter
for this switch (TL) is the anchor point, top left. The second set of parameters contains two
pairs of numbers. The first pair is the offsets from the anchor point for the IA. If no offsets are
specified, the IA appears in the top left corner of the screen. The second pair of numbers is
the offset from the anchor point for the IA's tag browser.
-SILENCE
Silences the alarm horn.
Define the pixel values for the positioning keywords in the Positioning tab of the
Console Properties dialog.
To help you position the Instrument Area accurately from Command Language
scripts or batch files, the following table shows the pixel dimensions of the
Instrument Areas in the various combinations of features turned on and off.
Table 8-2 Pixel Dimensions of an Instrument Area
Features
Without DDP Area

Width
Height
With DDP Area

Width
Height
With everything
205
612
835
617
Without statusbar
205
594
835
599
Without toolbar
205
582
835
587
Without tagbar
205
576
835
581
With toolbar only
205
558
835
563
With tagbar only
205
564
835
569
With statusbar only
205
546
835
551
With nothing extra
205
528
835
533
8-7
Examples
This subsection shows several examples of how to start an Instrument Area.
PIA
Opens the first Instrument Area. If this is the first time the Instrument area is opened,
it opens at the default location (top left corner at 820, 100). If the Instrument Area has
already been opened, it appears in its previous location.
PIA -POS
Opens or moves the first Instrument Area to the HOME position.
PIA -WIN 2 -TAG FIC-101 -POS TL 100 100 200 200
Opens (or moves) the second Instrument Area so that its top left corner is at screen
coordinates 100,100 and loads the point FIC-101. The Instrument Area's tag browser
opens with its top left corner at screen coordinates 200, 200.
Popup Faceplates
The DeltaV Operate for PROVOX software includes popup faceplate pictures for
PROVOX points. When an operator clicks on a PROVOX point in the alarm banner
the point's faceplate picture appears.
Many of the normal point operation tasks can be performed from the popup
faceplate pictures. If you need to open the instrument area for the point, click on the
Detail button in the faceplate.
Message Logging
The DeltaV Operate for PROVOX Console does not have a logging printer. The
console has a Message Spooler that stores records of eventsincluding alarms,
OARs, operator changes, and system eventsin .csv (comma separated value files) in
the \POC\Spooler directory on the Console Data Server. The files have names in the
form:
2010-03-21-14.csv
In the file name the 2010-03-21 is the date (in year-month-day format) and the 14 is
the number of hours past midnight UTC (Coordinated Universal Time) at which the
file was created. The server creates a new file every hour.
The first line in each file contains header text for all the columns in the file. This line is
useful if you import the .csv file into a spreadsheet.
8-8
Each remaining line in the .csv file is a record corresponding to a console event. The
records are logged in the order received.
Note
Under some circumstances it is possible for operator change messages to be logged after
the message verifying the operator change.
Each record has a unique identifying number and contains more than 200 fields,
though most records use a small subset of the fields. The second column of the .csv
file is the MsgId column. Each message type has a different Message ID. You can use
the information in the Message ID column to search for specific types of information
in .csv files.
The Message Spooler files reside on the Console Data Server. You can view the .csv
files from the server or copy them to other machines for further processing or
analysis.
The Message Spooler also provides records of these console events to the Event
Journal Database.
Viewers
There are four viewers in the DeltaV Operate for PROVOX Console software that
share a similar look and feel:
Event Journaldisplays console and system events stored by the message

spooler.
Status Summariesdisplays point status and communications failure status.
Document Viewerdisplays the online manuals for the DeltaV Operate for
PROVOX Console.
Reportsgenerates and displays configured reports.
To open a viewer from the Start menu navigate to DeltaV Operate for PROVOX |
Viewers to open the Viewer Selector shown in the following figure.
8-9
Figure 8-1
Viewer Selector
Open a viewer by clicking on a button.
Connecting to a Server
The viewers automatically configure their buttons 1 and 2 to connect to the primary
and secondary servers of the operator station. To set up connections to other servers,
use the viewer's Setup button. Click the button to open the Server Setup dialog as
shown in the figure.
Figure 8-2
Server Setup Dialog
The dialog automates connections to the primary and secondary Console Data
Servers for an operator station and simplifies connections to other Console Data
Servers.
To connect to the primary and secondary servers, select the Server Setup check box.
A Server Setup button appears in the middle of the dialog. The button label is
different for the different viewers, but for all of them the button automates the
connection to the workstation's primary and secondary servers. Click the button and
8-10
the dialog fills in the fields for Button 1 and Button 2 and creates buttons. Note that
you do not need to enter anything in any of the fields on the dialog.
To connect to other Console Data Servers, select Auto Complete. The Auto
Complete button appears. The button label is different for the different viewers, but
for all of them the button automates connections to other servers. Enter text in the
Button Label fields and enter a server name in the Server name field. Click on the
button and the dialog completes the Server Name field.
Click Apply to save the information and keep working. A button labeled with the text
you entered appears at the bottom of the Viewer. Click Close to close the dialog.
You can specify as many as six servers at one time. If you have more servers in your
installation and want to change the server connections, edit the server connections in
the Server Setup dialog.
Event Journal
Use the Event Journal to view console and system events stored by the message
spooler. You can view, filter, and query the events in a variety of ways from the Event
Journal. You can print the results of queries.
The Event Journal provides two interfaces to view and query the stored events:
The CSV view
The optional database view
The standard CSV view opens a selected CSV file in the Event Journal. You can
navigate through the file to view specific events and messages.
The optional database view adds a database engine that creates a database from the
CSV files and Event Journal enhancements you can use to view and query the
database in a number of ways.
For more information on the Event Journal, see the online manual Using DeltaV
Operate for PROVOX Console Software.
Status Summaries
Use the Status Summaries application to view Point Status and Communications
Failure summaries. You can also view the combined information of these two
summaries. You can print summary information.
For more information on the Status Summaries viewer, see the online manual Using
DeltaV Operate for PROVOX Console Software.
8-11
Reports Viewer
Use the Report Viewer to generate, view, and print configured reports.
Note
Even though reports are saved as HTML files, do not edit the saved report files.
Modifying the files can result in unintended appearance when the files are displayed.
Emerson Process Management does not support modifying saved report files.
The color of text, data, and other information in reports has meaning as shown in the
following table.
Table 8-3 Report Colors
Color
Meaning
Black
Normal report text and data
Green
Title information at the top of the report, time and date at

the bottom of the report.
Red
Number of points referenced in the report that did not

respond before the report was produced.
Blue
The data was truncated to fit the field. For example, the
value 100 in a two-character field appears as 10.
Magenta
Stale data or (if the field contains question marks) the

point referenced is not available in the database.
For more information on the Reports Viewer, see the online manual Using DeltaV
Document Viewer
Use the Document Viewer to view Books Online, the collection of user
documentation for the DeltaV Operate for PROVOX Console. The Books Online are
installed on Console Data Servers when you install the console software. Installing the
console software on operator stations installs a Books Online viewer that contains
embedded Adobe Acrobat Reader software. The viewer is accessible from the Start
menu.
Note
The document viewer toolbar contains links that open the Adobe corporation web site in
Internet Explorer if the computer is connected to the Internet. These links cannot be
disabled or removed.
For more information on the Document Viewer, see the online manual Using DeltaV
8-12
Alarm Banner Access

If an operator has an operator interface dialog openthe Replace Main Picture dialog
for examplethat dialog has focus and the operator cannot change focus to (select)
the alarm banner or an alarm button or silence the horn until the dialog is closed.
Disk Space
It is important to ensure that operator stations have adequate disk space to operate
properly. If available disk space becomes too low, operators may be unable to open the
Instrument Area or other console applications.
PROVOX Trend Viewer

Although configuring trend sets and traces is no different than in PROVUE Consoles
or Operator Workplace consoles, PROVOX trend information is stored, processed,
and viewed differently in the DeltaV Operate for PROVOX Console. Trend data has
two major components in the DeltaV Operate for PROVOX Console: trace data sets
and trend views.
Trace Data Set

The configured trend sets are downloaded to the Console Data Server. On the server,
each configured trace becomes a trace data set, the collection of information about a
trend tracepoint, attribute and occurrence (if applicable), sample interval, and
duration (the length of time for which data is stored).
If a point and attribute combination is defined multiple times at more than one
sample interval in more than one downloaded trend set, only one trace definition per
sample interval is converted into a trace data set. The download order determines
which trace definitions are converted to trace data sets. The download order cannot
be determined and may vary from download to download.
In other words, if a download contains multiple trace definitions for a point and
attribute combination that have different sample intervals and durations, there is no
way to tell which definitions will be converted to trace data sets.
Configured (downloaded) trace data sets cannot be removed from the data collection.
Trace data sets that operators add from a console session can be removed.
The Console Data Server reserves 30 Mbytes of disk space to store trace data sets.
The number of trace data sets that can be stored depends on their sample interval and
duration, and is limited to no more than 1200. The following table shows the number
8-13
of trend traces that can be stored for several combinations of sample interval and
duration.
Table 8-4 Number of Trend Traces That Can Be Defined Versus Sample Interval and Duration
Duration
(Hours)
Sample Interval (Seconds)

2
15
30
60
120
240
480
72
48
121
363
727
1200
1200
1200
1200
24
145
363
1091
1200
1200
1200
1200
1200
12
291
727
1200
1200
1200
1200
1200
1200
Trace data sets added online are volatile. That is, subsequent downloads that affect
trend sets may delete trace data sets. Also, updating the console software deletes all
trace data sets (though downloading creates trace data sets for all trend traces
configured in the download).
Trend Views
From the operator stations operators import downloaded trend sets into trend views
or create new trend views. Operators can manipulate these trend views (stored as .ptv
files on the operator stations), adding and deleting traces in the views. Each trend
view can contain as many as six traces. Note that manipulating the trend views (.ptv
files) has no effect on the underlying trace data sets.
Opening and Positioning

Trend windows can be opened from a batch file or a command window by running
the application PTV. You can also use the DeltaV frsRunTask Visual Basic subroutine
to open a trend window.
The following table shows the command line switches available when starting the
Trend viewer application.
8-14
Table 8-5 Trend Viewer Command Line Switches

Switch
Effect
-FILE <file name>1

-TSET <trend set
Loads a previously saved ptv file in the trend viewer.
name>1
Imports the configured trend set into the trend viewer.
-WIN n
Specifies which Trend window to affect. n is 1 or 2.
-POS keyword
Positions and sizes the Trend window by one of the positions defined in the Positioning
tab. Keywords are HOME, A, B, C, and D. If no keyword is specified, the Trend window
opens in the HOME position.
-POS TL <x y bx by>
Positions the Trend window in a location defined by pixel coordinates. The first parameter
for this switch is the anchor point, top left. The second set of parameters contains two
pairs of numbers. The first pair is the offsets from the anchor point for the Trend window.
If no offsets are specified, the Trend window appears at the top left corner of the screen.
The second pair of numbers is the offset from the anchor point for the Trend window's
browser.
-SIZE <w h>
Sets the initial size of the Trend window in pixels. Ignored if -POS keyword is used. Valid
ranges are:
150 to 1010 pixels wide
200 to 768 pixels high
-SPAN <t>
Sets the time span shown in the Trend window to the interval specified. Valid values are:
15 or 30 (minutes) or 1, 2, 4, 8, 12, 16, 24, 48, or 72 (hours).
-LEGEND ON | OFF
Sets whether the trend view legend appears.
Notes:
1. The switches FILE and TSET are mutually exclusive. Only one can be used in each command line. If both are present only
the second switch in the command line is implemented.
Define the pixel values for the positioning keywords in the Positioning tab of the
Console Properties dialog.
Examples
This subsection shows several examples of how to start a Trend window.
From the command line or a batch file:
PTV
Opens the first Trend window. If this is the first time the window is opened, it opens
at the default location (top left corner at 100, 247) and size (800 pixels wide by 625
8-15
pixels tall). If the Trend window has already been opened, it appears in its previous
location.
PTV -POS
Opens or moves the first Trend window to the HOME position.
PTV -WIN 2 -FILE MYTRND.PTV -POS TL 100 100 200 200 -LEGEND
OFF
Opens (or moves) the second Trend window so that its top left corner is at screen
coordinates 100, 100, positions the browser windows top left corner at offset of 200,
200 from the Trend window position, loads the trend view file MYTRND.PTV, and
turns the trend legend off.
From a script:
To open the same trend window from a button, create a button on a display, then edit
the script for that button to read:
frsRunTask PTV, -WIN 2 -FILE MYTRND.PTV -POS TL 100 100
200 200 -LEGEND OFF
Note that all of the command line parameters for the PTV application are within one
set of quote marks.
The Trend Viewer

This subsection explains how to setup and use the Trend viewer.
Importing Configured Trend Sets

To import a configured trend set, select File | Import from the Trend Viewer. The
Trend Sets dialog opens. After you select a server and trend set, the dialog looks
similar to the figure.
8-16
Figure 8-3
Importing Configured Trend Sets
The Traces pane of the dialog shows the trend traces in the selected trend set. Click
OK to import the trend set and the software prompts you to save the set as a trend
view (.ptv file). You must save the trend set as a .ptv file to be able to view it.
Imported trend traces are assigned a duration based on the sample interval. The
following table summarizes how the configured sample intervals are assigned
durations and how the durations compare with the duration available on Operator
Workplace consoles.
8-17
Table 8-6 Durations for Imported Trend Traces

Configured Sample
Interval
Operator Workplace
Duration
Note
Duration Stored In
DeltaV Operate for
PROVOX Console
2 seconds
8 minutes
3 hours
---
5 seconds
20 minutes
6 hours
---
15 seconds
1 hour
18 hours
---
30 seconds
2 hours
36 hours
---
1 minute
4 hours
72 hours
---
2 minutes
NA
72 hours
New
4 minutes
16 hours
72 hours
---
8 minutes
32 hours
72 hours
---
24 minutes
4 days
72 hours at 8
minute sample
rate
NA
72 minutes
12 days
72 hours at 8
minute sample
rate
NA
In all cases except the 24 minute and 72 minute sample interval the assigned durations
contain significantly more than 240 samples, the standard in Operator Workplace and
PROVUE consoles. If you want to store trace data for a different duration, you must
remove all instances of the trace from the ENVOX configuration and add the trace
online.
Adding Trace Data Sets to Trend Views

With an empty trace field selected in the Trend Viewer, select Edit | Add. The point
Trace Data Sets dialog appears as shown in the figure.
8-18
Figure 8-4
Trace Data Sets
In the figure the point IACLP8 is selected. The text in the Traces pane of the dialog
(DVAD @ 15 Seconds ^ 4 Hours) indicates that for this point a trace data set for the
PV attribute already exists. This could be a configured trace data set or it could have
been added online. To add this trace data set to the trend view, select the trace
information in the Traces pane and click the OK button.
Creating Trace Data Sets

To add a new trace data set to the trace data collection click the New button on the
Point Trace Data Sets dialog. The Add Trend Trace to Point dialog appears as shown
in the figure.
8-19
Figure 8-5
Adding Trace Data Sets
The pane at the right of the dialog contains the valid trendable attributes for the
currently selected point. As you select an attribute it appears in the field above the list.
If an attribute has multiple occurrences, you must edit the occurrence in that field if
you want to use anything other than occurrence 0.
After you edit the occurrence, if necessary, set the duration and sample interval and
click OK to transfer the tag, attribute, occurrence, duration, and interval to the Traces
pane of the Point Trace Data Sets dialog. Note that attributes with multiple
occurrence numbers do not include the occurrence number for occurrence 0. For
8-20
example, the following is a list of all three TRACKING occurrences as they appear in
the traces list:
TRACKING @ 15 Seconds ^ 4 Hours
TRACKING[1] @ 15 Seconds ^ 4 Hours
TRACKING[2] @ 15 Seconds ^ 4 Hours
You can add a trace to a trend view by selecting it in the Point Trace Data Sets dialog
and clicking the OK button.
Each point can have as many as 12 trace data sets defined for it. They can be any
combination of configured traces and trace data sets added online.
You can create more than one trace for a point, attribute, and occurrence
combination.
Removing Trace Data Sets

To remove a trace data set, select it in the Traces pane of the Point Trace Data Sets
dialog and click the Remove button. A confirmation dialog appears. Click OK to
remove the trace data set. If the trace data set is from a configured trend set, an error
message appears.
Note
You cannot remove a configured trace data set from the list of traces for a point.
Viewing Trends
After you create a trend view, you can open it by selecting File | Open from the Trend
Viewer. The software presents a dialog from which you can select an existing trend
view (.ptv file).
After the view files is open you can manipulate the view in a variety of ways: adding
grids, adding a legend, and so on.
Note
Viewing trace data sets collected at small sample intervals with the time span set at a
large duration may mask some short duration events.
The Trend Viewer creates a trace view by computing an interval at which to extract
trace values from the trace data. The computed interval is based on the trace data set's
sample interval and the trend view's time span. If the duration of an event is less than
the computed interval, it is possible that the event will not appear in the view.
8-21
Trace Data Set Definition Files

The console software uses three files on the Console Data Server to store trace data
set definitions. Use these files to define which online trend trace definitions are
restored after a console download.
Note
Trend data is not preserved through a download.

The three files are:
TrendTraces_Current.txt
The console software creates and maintains this file. The file contains trace data
set definitions downloaded from the ENVOX software and definitions added
online. The definitions for traces added online are flagged with a trailing asterisk
(*).
If your system has redundant Console Data Servers, changes and additions to
trace data set definitions are saved in the TrendTraces_Current.txt file on the
currently active Console Data Server. Note that there can be multiple versions of
the TrendTraces_Current.txt file, one on each Console Data Server of a
redundant pair.
TrendTraces_Previous.txt
This file is created at the start of a database update. The trace data set definitions
in use (downloaded and added online) are saved in this file on the currently active
TrendTraces_Master.txt
You create and maintain this master file of trace data set definitions. You can use
this file to ensure that all Console Data Servers have the same trace data set
definitions available. This file is not modified by any definitions you make and
save online from the Trend application.
An easy way to create TrendTraces_Master.txt is to copy and edit
TrendTraces_Current.txt.
The default directory for these files is the \cfg directory under the console software
installation directory, but you can change this from the Trend tab of the Console
Properties dialog (from the Start menu navigate to DeltaV Operate for PROVOX |
Settings | Console Properties). You also set which file, TrendTraces_Master.txt or
TrendTraces_Current.txt is loaded first after a console download.
8-22
After a database update the console software loads the definition files in the order you
specify in the Console Properties dialog, either TrendTraces_Master.txt first or
TrendTraces_Current.txt first.
The format of a trend trace definition is:
ACCUM1 | MVPCV02 @ 15 Seconds ^ 4 Hours *
From left to right the information in the definition is:
Point tag, attribute, and occurrence, if any (ACCUM1 | MVPCV02)

The pipe symbol (|) is required to separate the point tag and attribute. If the
attribute has occurrence numbers specify the occurrence by inserting it in
brackets. For example, DVAD[2].
Data sample rate (@ 15 Seconds)

The ampersand (@) is required
Trend duration (^ 4 Hours)

The caret (^) is required
Asterisk (*) to indicate this trend trace definition should be restored

The trailing asterisk is important because after a download the console software
restores only the online trace definitions (those flagged with an asterisk).
Note that only the first definition of a unique trace is loaded into the database. A
unique trace is defined by the combination of point tag, attribute, occurrence number,
and sample rate.
Other Trend Issues

If data becomes unavailable for a trace data set, there are some indications in the
Trend Viewer. If a point becomes unavailable (UNAV), the trace continues at the last
available value. If you use the cursor to check the trace value, the last value is displayed
on a magenta background.
Troubleshooting and Recovering

If the console begins to behave in an unexpected manner, the quickest way to reestablish normal operations is to perform an orderly shutdown and restart of
Windows. Do not reboot the computer by cycling the power while the console software or Windows is
starting or running.
8-23
Caution
It is possible (though rare) for cycling the power while Windows is starting or
running to damage the file system and make it necessary to re-install the
Windows operating system.
Damaging the file system is more likely if you cycle the power while Windows is
starting.
To perform an orderly shutdown and restart:
1. Close all open applications, including any components of the console software
that are running.
2. Select Start | Shutdown.
3. Select Restart the computer.
After a few moments the computer shuts down and restarts. The console software
may restart automatically depending on how the software is installed and set up.
Restarts
The DeltaV Operate for PROVOX Console is designed to retain as much of the
current console state as possible if a power failure or restart occurs. Depending on
whether an operator station or Console Data Server is restarted, most or all operating
data may be preserved.
Operator Station
Shutting down and restarting an operator station has very little effect on operations as
most operating data is kept on the Console Data Server. After the console software
restarts and the operator logs on, operations should continue without interruption.
Trending, event logging (message spooling), and local DDP changes are all unaffected
by restarting an operator station.
Console Data Server
Restarting a Console Data Server causes some interruptions. Trend data and event log
entries are lost for the duration of the outage. The alarm history (alarm instance
records) and OAR history are lost as well, but are rebuilt from current field device
information after recovery. Other console functions are unaffected.
8-24
Note
The alarm and OAR histories (as reflected in the alarm and OAR summaries) are
rebuilt in the order in which the information becomes available to the console, not in the
original order.
The following table summarizes the effect of restarting the Console Data Server and
the operator station on console operations.
Table 8-7 Effect of Restart on Console Operations
Effect of Restarting
Console Function
Console Data Server
Operator Station
Local DDP value changes
No effect
No effect
PMA mode
No effect
No effect
Trend data
Lost for duration of outage
No effect
Trend traces added by operator
No effect
No effect
Trend views
No effect
No effect
PPA operating state
No effect
No effect
PPA critical level
No effect
No effect
Event log
Events during outage are lost
No effect
Console Redundancy
Redundancy in process control means that more than one hardware or software
component is capable of performing important control functions. There are two
different types of console redundancy implemented in the DeltaV Operate for
PROVOX Console:
Console Data Server redundancy Operator stations can connect to two

Console Data Servers, Primary and Secondary, one of which is Active and the
other is Standby. During normal operation the workstation receives process data
from the Active Server. If the Active server fails the workstation can switch to the
Standby server.
The Primary and Secondary Console Data Servers are defined during software
setup.
Console-resident point redundancy Point processing for console-resident

points that support point redundancy can be done in a pair of Console Data
Servers, a Primary and a Secondary. One of these is Active, reporting point
information to the operator stations and other devices. The other server is
8-25
Standby. If the Active server fails, the Standby Console Data Server detects the
failure and takes over reporting point information.
The Primary and Secondary Console Data Servers are defined during console
configuration and can be redefined only through a total download.
The following figure is a block diagram that shows the recommended way to
configure and set up a redundant pair of DeltaV Operate for PROVOX Consoles for
both types of redundancy.
Figure 8-6
8-26
Console Redundancy
Note that the two types of redundancy use similar terminology and under many
circumstances can have the same effecttransferring some aspect of process control
from one Console Data Server to another if the currently active server fails or is
otherwise unable to function. However, the two redundancy types are not related and
do not depend on each other. It is possible to have either type of redundancy without
the other.
Understanding the two types of redundancy can help you create and maintain a more
robust control system that is less likely to be adversely affected by hardware or
configuration maintenance or equipment problems.
The following subsections explain the two redundancy types and how to use them in
the DeltaV Operate for PROVOX Console environment. For more information on
the theory behind how redundancy is implemented in the console, refer to the
manual, Configuring PROVOX Operator Console Software (CE:NT2100).
For reference, the following table contains abbreviated definitions for terms used to
describe both redundancy types. The table emphasizes that the two redundancy types
are distinct and not related.
Table 8-8 Console Redundancy Terms
Redundancy
Term
Defined For Console Data Server Redundancy
Defined For Console Point Redundancy
Active
Active Server The Console Data Server

currently providing data to the operator station.
Active Console The console of a redundant

pair whose Console Data Server is currently
computing console-resident point data.
Standby
Standby Server The Console Data Server

of a redundant pair that is not currently sending
data to the operator station.
Standby Console The console of a redundant

pair whose Console Data Server is not currently
computing console-resident point data
Primary
Primary Server The Console Data Server

that usually provides data to the operator
station (is usually Active).
Primary Console The console whose Console

Data Server is usually active.
Secondary
Secondary Server The Console Data

Server that is usually on standby.
Secondary Console The console whose

Console Data Server is usually on standby.
Switchover
Switchover An operator station's transition

from receiving data from one Console Data
Server to receiving data from another Console
Data Server.
Switchover A consoles transition from active

to standby or from standby to active. The Console
Data Server of the console going to standby stops
computing console-resident point data and the
Console Data Server of the console going active
begins computing console-resident point data.
Simplex
No term defined
Simplex Console A console that is not part of

a redundant console pair.
8-27

Console Data Server redundancy refers to the ability of an operator station to receive
operating data from either of two Console Data Servers. Console Data Server
redundancy is defined from operator stations, not during configuration. For example,
the connection between the switches in the figure means that all four workstations
can connect to both servers.
Console Data Server redundancy is defined for each workstation in the Console
Properties dialog. Figure 8-9: Console Redundancy indicates that server S1 is defined
as the primary Console Data Server and server S2 is defined as the secondary server for
workstations W1 and W2. Similarly, workstations W3 and W4 have server S2 defined
as primary and S1 defined as secondary.
This is the recommended way to define primary and secondary servers. If one of the
servers fails or otherwise becomes unavailable, at least two of the workstations are
unaffected. For example, if server S1 fails, workstations W3 and W4 still receive data
from server S2. W1 and W2 cannot be used unless they are switched to use S2 as their
active server.
Emerson Process Management recommends that the primary and secondary data
servers have the same configuration so that the same data is available from both
servers. Note that the DeltaV Operate for PROVOX software does not check that the
downloads are the same.
The workstation attempts to establish communication with both the primary and
secondary Console Data Server when the workstation services start.
Redundancy Event Logging

Changes in Console Data Server redundancy are logged when:
The workstation switches over to the standby server.
The automatic switchover function is enabled or disabled.
Manual and Automatic Switchovers

Switchovers can be performed automatically or manually. An operator must have
OPERATE or TUNE privilege to perform manual switchovers or disable automatic
switchovers. To enable automatic switchovers operators must have ACCESS,
OPERATE, or TUNE privilege.
8-28
Caution
Emerson Process Management recommends that you attempt manual

switchovers only if the standby Console Data Server status is Ready.
Because the workstation allows a manual switchover even if the status of the
standby server is Unknown, you may lose data if you attempt a switchover
when the standby server is unavailable. You must ensure that the standby
server is available to become active before requesting a manual switchover.
An operator can switch a workstation to its redundant server manually from the
workstation's integrity faceplate. To navigate to the Console Data Server Redundancy
faceplate click on the PROVOX Diagnostics button in the toolbar or the PROVOX
Integrity buttons in the PROVOX alarm banner. Click the Data Server field in the
integrity faceplate and the POC Integrity Detail picture including Console Data
Server Redundancy controls appears as shown.
8-29
Figure 8-7
Integrity Detail -- Console Data Server Redundancy
From the faceplate the operator can enable and disable Console Data Server Auto
Switchover, or manually switch servers. The word Active and a border around the
green box indicate which server is currently active.
8-30
The colored boxes and indicators on the integrity faceplates have the following
meaning:
Red The integrity of the hardware this indicator represents is bad. You cannot
operate the process.
Yellow You can operate the process but the integrity of the hardware this
indicator represents is questionable.
Green The console is operating normally and the integrity of the hardware
this indicator represents is good.
Magenta The data displayed is stale. The integrity of the hardware this
indicator represents is unknown.
No color or hidden This indicator does not represent any hardware because
the hardware is not configured.
From the faceplate the operator can view information on the state of the workstation
and its servers and enable or disable automatic switchover on the workstation or
manually switch over to the desired server.
An engineer can switch the servers for one or more workstations from the
Redundancy application on the Console Data Server (from the Start menu navigate to
DeltaV Operate for PROVOX | Engineering | Redundancy) as shown in the
following figure.
8-31
Figure 8-8
Redundancy Application Console Data Server Tab
The dialog shows the current switchover state of all workstations defined for this
server: whether Auto Switchover is enabled or disabled and the Console Data Server
the operator station is currently receiving data from (the active server). From the
dialog you can enable and disable automatic switchover and manually switch between
the primary and secondary Console Data Servers for all operator stations connected
to the server.
You can perform a manual switchover when the standby server is Ready, Unknown,
or Idle (not downloaded). Automatic switchovers occur when the active Console Data
Server has a critical failure, such as a power loss. When either a manual or automatic
switchover occurs, the workstation disables automatic switchover.
8-32
Caution
Emerson Process Management recommends that you attempt manual

switchovers only if the Console Data Server state is Standby.
Because the workstation allows a manual switchover even if the status of the
standby server is Unknown, you may lose data if you attempt a switchover
when the server state is Unavailable or Unknown. You must ensure that the
server is available to become active before requesting a manual switchover.
When the primary Console Data Server is available again you can re-enable automatic
switchover and manually switch back to the primary server.
Console-Resident Point Redundancy

Console-resident point redundancy, also known as console point redundancy, refers
to console-resident points that reside in a pair of consoles in the same PROVOX area.
Console point redundancy provides for continued operation of console-resident
points (that support redundancy) in the event a console fails or becomes unavailable.
The redundant pairs of consoles are defined during configuration and cannot be
changed except through a total download.
There are five console-resident point types that support redundancy:
Activity points
Discrete control device points (DCDs)
Extended pulse count input points (EPCIs)
Integrity points
Accumulation points.
The two other console-resident point types do not support redundancy: maintenance
and single-bit discrete points.
During configuration, one console of the redundant pair is configured as the primary
console and the other is configured as the secondary console. The currently active
console performs point processing for console-resident points and reports the
information to operator stations and other PROVOX devices along with the standby
console.
The figure at the beginning of this subsection indicates the initial state of consoles
paired for console point redundancy immediately after a download. Note that both
8-33
servers, S1 and S2, show the same information: S1 is the active server and S2 is the
standby server. For console point redundancy both servers of a pair of consoles
always have the same active and standby servers.
Console point processing can switch from the currently active server to the standby
server either through operator action or automatically, if auto switchover (of consoleresident point redundancy) is enabled.
The configuration for the console-resident points must be identical in both paired
consoles. However, targeted points, displays, and other non-source information may
be different between redundant consoles.
The active console computes console point data and communicates it to the standby
console. If the active console fails and auto switchover is enabled between the
redundant consoles, the standby console becomes active and continues computing
point data for the redundant console-resident points.
Because all devices obtaining information from the pair must know how to locate the
active device, console redundancy is not transparent to all other devices in the system.
Only consoles, CHIP VAX version P3.0 and later, CHIP IBM version P1.0 and later,
and all newer versions of CHIP can transparently manage information processing and
switchovers from a redundant console pair.
Console Pairing for Console Point Redundancy

As you configure consoles, you define redundant pairs of console. In creating the
partnerships, you also configure the primary and secondary assignments and identify
the highway addresses of the consoles.
A primary console is the master in the redundant pairs communications. It becomes
active following any disagreement about which console of the pair should be active.
A secondary console is the slave in the redundant pair. It becomes the standby
console following any disagreement about which console should be active.
The standby console tracks the active console, so that if the active console fails, the
standby console accepts control of the process (becomes the active console).
In redundant pairs, if the active console fails, the standby console becomes active and
resumes operation. By configuring the consoles this way, the console resident points
remain operable even if one of the consoles fails.
However, if a console-resident point is in a simplex console and targeted to other
consoles, an operator can operate the point from any of the other consoles as long as
the points source console is operating. If the console where the point is resident fails,
8-34
though, the other consoles show UNAVL (unavailable) for the point, and it is no
longer available for operation.
Manual and Automatic Switchovers

Switchovers can be performed automatically or manually. An operator must have
OPERATE or TUNE privilege to perform manual switchovers or disable automatic
switchovers. To enable automatic switchovers operators must have ACCESS,
OPERATE, or TUNE privilege.
An operator can switch console-resident points to their redundant server manually
from the workstation's integrity faceplate. To navigate to the Console Data Server
Redundancy faceplate click on the PROVOX Diagnostics button in the toolbar or the
PROVOX Integrity buttons in the PROVOX alarm banner. Click the Console Point
Redundancy field in the integrity faceplate and the POC Integrity Detail picture
including Console-Resident Point Redundancy controls appears as shown.
Figure 8-9
Integrity Faceplate -- Console Point Redundancy
8-35
From the faceplate the operator can view information on the state of the workstation
and its servers and enable or disable automatic switchover on the workstation or
manually switch over to the desired server.
An engineer can switch servers from the Redundancy application on the Console
Data Server (from the Start menu navigate to DeltaV Operate for PROVOX |
Engineering | Redundancy) as shown in the following figure.
Figure 8-10 Redundancy: Console-Resident Points Tab
The application shows information on the redundant servers and provides controls to
enable and disable Auto Switchover and manually switch over to a desired server.
Effects of Console-resident Points
Console redundancy rejects a manual switchover request while the points are not
synchronized and the console can communicate with its partner. Disallowing manual
switchovers prevents failures caused by switchovers while console-resident points are
not synchronized.
8-36
Normally, console-resident points are ready for manual switchover within three
minutes of establishing communications after download.
Changing Paired Consoles Relationships
To change a redundant consoles pair assignment, you must do a total download. You
must change and download the affected consoles so they become simplex (nonredundant) before you can create new redundant pairs. Otherwise, you end up with a
disagreement caused by the newly paired consoles both behaving as the primary
console or both acting as the secondary console.
Downloading Devices after Changing Pairs
If you change the pairing assignments for a pair of consoles, you must also do a partial
download to all devices that obtain data from the original pair. Items contained in this
download generally consist of all points that get their data from the pair and the
redundant console pairing table.
Redundant Pair Downloading
If you are doing a partial download configuration update on a standby console, the
configuration update has no affect on any console that obtains data from the pair. If
you send a partial download to an active console, either as part of a redundant pair or
as a simplex console, other devices that get point information from that console
display an unavailable status until the configuration update ends. Follow the
procedures for total and partial downloads outlined in the documentation for the
configuration software you are using.
Redundancy in Action
This subsection uses examples to explain how both types of redundancy work. The
examples are:
A power failure on a Console Data Server
Replacing an Ethernet cable between a switch and Console Data Server
Database download and update.
The figure at the beginning of this section indicates the system setup for both
examples. Also, auto switchover is enabled for both Console Data Server redundancy
and console point redundancy.
8-37
Console Data Server Power Failure

This example shows how auto switchover works for both types of redundancy. The
system is operating normally when Console Data Server S1 loses power. Both types of
redundancy are involved in recovering from the power loss.
Workstations W1 and W2 detect bad integrity on server S1 and automatically
switchover to connect to server S2 (make it the active server). Both workstations set
S1 to standby and disable auto switchover. The workstations continue to function
because they are now receiving data from server S2.
Server S2 remains the active server for both workstations until S1 is manually
switched back to be their active server.
Console Point Redundancy
After the power loss Console Data Server S2 detects a fault with server S1. S2
becomes active, sets S1 to standby, disables auto switchover, and begins processing
console resident point data.
Server S2 remains the active server for console point redundancy until S1 is manually
switched back to be the active server.
Replacing an Ethernet Cable

For this example, the Ethernet cable between server S1 and its switch needs to be
repaired or replaced. This interrupts the data flow from the server to workstations
W1 and W2.
In anticipation of the disruption, the operator performs a manual switchover in
workstations W1 and W2, setting server S2 to be the active server. The operator also
disables automatic switchover. The Ethernet cable can now be disconnected without
affecting control from workstations W1 and W2.
After the cable is reconnected, the operator manually switches S1 back to active for
both workstations and re-enables auto switchover.
Console Point Redundancy
Console point redundancy is not affected by disconnecting the cable so no action is
required. Server S1 continues to process console point data and sends it over the data
highway to S2. S2 sends the data to workstations W1 and W2 over the cable
connecting the two switches. Throughout the cable repair or replace, S1 continues to
be the active server for console point redundancy.
8-38
Database Download and Update

A process network consists of a pair of Console Data Servers connecting to several
operator stations as shown in the following figure.
Figure 8-11 Console Redundancy
8-39
The process network uses both console-resident point redundancy and Console Data
Server redundancy. The engineer needs to update the configuration on the pair of
servers, starting with S2. To do so, he would use the following steps:
1. Log on to Console Data Server S2 with DOWNLOAD privilege.
2. Open the Redundancy application (from the Start menu navigate to DeltaV
Operate for PROVOX | Engineering | Redundancy)
3. Select the Console Data Server tab
The list in the tab shows all operator stations that can be connected to Console Data
Server S2 (the workstations listed in the Console Properties dialog of the server) and
their relationship to S2:
Node Name
Switchover
State
Type
W1
Disabled
Standby
Secondary
W2
Disabled
Standby
Secondary
W3
Disabled
Active
Primary
W4
Disabled
Active
Primary
4. Select workstations W3 and W4 in the list, then click the Secondary button (in
the Switch to area).
The list changes to show workstations W3 and W4 are now in Standby State with
respect to this server (S2). No workstations are currently connected to the server
so the database update can be performed without disturbing operation.
5. Select the Console-Resident Points tab. The list reflects the current state of
console point redundancy for the pair of servers:
Node Name
Switchover
State
Type
S1
Disabled
Active
Primary
S2
Disabled
Standby
Secondary
Ensure that this server (S2) is in Standby State. In this example it is so no action is
necessary.
6. Click the Database Update button. The Shared Database Update dialog appears.
Perform the actions required then close the dialog.
8-40
7. Log on to server S1 and perform the equivalent steps to update its database.
First, make sure all the workstations are in Standby State with respect to S1. Then
manually switch over the console point redundancy to S2. Then update the
database on S1.
8. Restore the network to its original state.
Make S1 the active server for W1 and W2. Make S2 the active server for W3 and
W4. Make S1 the active server for console point redundancy.
8-41
8-42
Appendix A Installing the Operator Console Software

Introduction
The assumptions made in this section of the manual are:
You have a DeltaV control system installed and running in your plant.
You have a PROVOX control system installed and running in your plant.
You want to control and monitor the PROVOX system from DeltaV Operator
Stations using DeltaV Operate for PROVOX software.
The tasks required to install the software depend on whether your PROVOX system
includes PROVOX Operator Consoles or Operator Workplace or PROVUE
consoles. The remainder of this section is divided into two subsections:
PROVUE or Operator Workplace Console Systems Explains how to upgrade

Operator Workplace and PROVUE consoles to DeltaV Operate for PROVOX
systems.
PROVOX Operator Console Systems Explains how to upgrade a PROVOX

Operator Console System to a DeltaV Operate for PROVOX system.
PROVUE or Operator Workplace Console Systems

If your PROVOX system has only PROVUE or Operator Workplace consoles, you
must perform the following tasks:
1. Obtain and install the DeltaV Operate for PROVOX Data Server (Console Data
Server) hardware and software.
2. Connect the server to your DeltaV network as described in this manual.
3. Install the DeltaV Operate for PROVOX software on the DeltaV Operator
Stations connected to the Console Data Server.
4. Perform some additional setup tasks on both Console Data Servers and DeltaV
Operator Stations.
5. Create displays.
Installing Software on Console Data Servers

These instruction apply to Windows Server 2008.
Installing the Operator Console Software
A-1
Note
Before you install the software on Console Data Servers you must have installed the
Windows Server software and performed the additional Windows Server setup required.
Refer to Appendix B for information on installing the Windows Server software and
performing additional Windows Server setup.
Note
Install only the DeltaV Operate for PROVOX software on console data servers. Do
not install DeltaV software on console data servers.
To install the DeltaV Operate for PROVOX software on the Console Data Server:
1. Start the server and log on under the Administrator account.
2. Verify that it is running Windows Server software.
3. Insert the DeltaV Operate for PROVOX software installation disk into the drive.
4. Open the Windows Explorer.
5. In the Explorer window, click on the root level directory of the installation disk.
6. Select and double click the Setup.exe program to start the installation.
You may see a message that says:
Installation had to update one or more system files.
If you see this message, acknowledge it. If the computer does not automatically
restart after you acknowledge the message, restart it manually.
After the computer restarts, resume the installation at step 3.
The second time you start the installation, the Welcome dialog appears.
7. Click Next
The Refer to the Getting Started documentation popup appears.
8. Click OK to acknowledge the popup
The Software License Agreement appears.
9. Click Yes to accept the license.
The DeltaV Operate for PROVOX License dialog appears.
10. Insert the correct license media in the appropriate drive.
11. Click OK.
The Setup Type dialog appears
12. Select DeltaV Operate for PROVOX Data Server and click Next.
The Installation Folder dialog appears.
A-2
13. Select a folder and click Next.

The Console Data Server Installation Requirements dialog appears. There is
additional software that must be installed before you install the Console Data
Server. Refer to Additional Windows Server 2008 Setup on page B-3 for
information on installing this software.
14. Acknowledge the popup.
The Service Startup Type dialog appears.
15. Select Automatic.
16. Click Next.
The PROVOX21Admin account password dialog appears.
17. Enter the PROVOX21Admin accounts current password in both the Password
and Confirm fields. The default password for this account is PROVOX21Admin.
The console software runs the POC Base service from the PROVOX21Admin
account so you must enter the current password or the service will not start
correctly when you restart the system.
The installation software does not validate the password you enter. If you enter an
incorrect password, you can correct it from the User Administration program and
the Services dialog after you complete the installation. Refer to Chapter 5 of this
manual for more information.
18. Click OK.
The Start Copying Files dialog appears.
19. Click Next to start copying files.
Wait for the DeltaV Operate for PROVOX Viewers Toolbar Setup dialog to
appear.
20. Click OK.
21. Click the large icon button to continue.
Setup installs the software and displays a popup indicating success.
22. Click OK to acknowledge the popup.
A command window (CMD.EXE) that contains a question about continuing the
operation of stopping the IIS service may appear.
23. If the window appears, enter Y to continue.
The DeltaV Operate for PROVOX WebComponents Setup dialog appears.
A-3
24. Click OK.

25. Click the large icon button to install.
Setup installs the software and displays a popup indicating success.
A Windows Scripting Host popup appears saying that a Web Site has been
created.
A Question popup appears asking if you want to enter site-specific information.
28. Click Yes to enter or verify information or configure the HDL.
A popup appears with instructions for uninitializing the HDL. For complete
instructions refer to Chapter 5 of this manual. You can proceed without
configuring the HDL and configure it during software setup if you desire.
When you are ready to continue close this dialog and the DeltaV Operate for
PROVOX Properties dialog appears.
Note
If the POC Base service is set to start automatically, be sure to set the HDL information
correctly in the Console Properties dialog before you restart the Console Data Server.
Otherwise the HDL may not be initialized correctly which can cause communication
problems with other PROVOX devices on the data highway.
After you enter site specific information and close the dialog, the Setup Complete
dialog appears.
29. Select Yes, I want to restart my computer.
30. Remove the license media from the drive.
To verify the HDL settings from the Start menu navigate to DeltaV Operate for
PROVOX | Settings | Console Properties. Verify the HDL settings in the dialog
that appears.
31. Click Finish.
The computer restarts.
32. Once the system has restarted, log on as Administrator and examine the Event
Viewer and verify that the system came up correctly.
33. Before you use your system, refer to Chapter 5, Software Setup, for instructions
for verifying and changing several software settings.
A-4
Installation of the DeltaV Operate for PROVOX software is complete. Now install
the Network Time Protocol Service.
Note
Before you use your system, refer to Chapter 5, Software Setup, for instructions for
verifying and changing several software settings.
Installing the Network Time Protocol Service
You must install the Network Time Protocol (NTP) Service on the Console Data
Server. Use the utility InstallNtpService.exe and the NTP service ntpd.exe included in
the DeltaV bin directory on the ProfessionalPLUS workstation (C:\DeltaV\bin).
To install the NTP service:
1. Copy the files ntpd.exe, ntpq.exe, and InstallNtpService.exe from a DeltaV
system (in \DeltaV\bin) to c:\windows\system32 on the fixed disk of the
2. Open a command window and run InstallNtpService supplying the fully
qualified pathname of the ntpd.exe executable and the IP address of DeltaV
Network Time Server. For example:
c:\> InstallNtpService c:\windows\system32\ntpd.exe 192.168.0.1

Make sure you use the correct IP address of Network Time Server. The easiest way to
find the correct IP address is to open a command window and ping the Network
Time Server by name:
c:\> ping nodename
The command results include the IP address of the Network Time Server.
If the node whose IP address you specify is not the master time server, the node must
have Remote Access Server enabled.
This command line utility creates and removes the NTP service, updates the registry,
and creates an NTP configuration file.
The utility ntpq.exe, which is also in the DeltaV bin directory, is useful in verifying the
operation of the NTP service and for diagnosing problems.
After you install the NTP service you must start the Network Time Protocol service,
either from the Services dialog or by restarting the data server.
Refer to the section System Time in the DeltaV Maintenance manual for more
information on the Network Time Protocol Service.
A-5
Install DeltaV Operate for PROVOX Software on DeltaV

Operator Stations
Note
The DeltaV Operator Stations must already have the DeltaV software installed and
operating correctly.
To install DeltaV Operate for PROVOX software on DeltaV Operator Stations:
1. Restart the system and log on under the Administrator account.
2. Verify that the Windows Workstation system contains the following:
Windows 7.
Microsoft Internet Explorer 8 and Internet Tools
DeltaV software v11.3.
3. Exit all Windows applications.
4. Insert the DeltaV Operate for PROVOX software installation disk into the drive.
5. Open the Windows Explorer.
6. In the Explorer window, click on the root level directory of the installation disk.
7. Select and double click the Setup.exe program to start the installation process.
You may see a message that says:
Installation had to update one or more system files.
If you see this message, acknowledge it. If the computer does not automatically
restart after you acknowledge the message, restart it manually.
After the computer restarts, resume the installation at step 3.
The second time you start the installation, the Welcome dialog appears.
8. Click Next
The Refer to the Getting Started documentation popup appears.
The Software License Agreement appears.
10. Click Yes to accept the license.
The DeltaV Operate for PROVOX License dialog appears.
11. Insert the correct license media in the appropriate drive.
12. Click OK.
The Setup Type dialog appears.
A-6
13. Select DeltaV Operate for PROVOX Station Upgrade and click Next.
The Installation Folder dialog appears.
14. Select a folder and click Next.
The Installation Requirements popup appears. This popup lists the software
required for the console software.
15. Click OK to acknowledge.
The Service Startup Type dialog appears.
16. Select Automatic.
17. Click Next.
The PROVOX21Admin account password dialog appears.
18. Enter the PROVOX21Admin accounts current password in both the Password
and Confirm fields.
Note
Do not copy and paste the password from the Password field to the Confirm field.
The console software runs the POC Station service from the PROVOX21Admin
account so you must enter the current password or the service will not start
correctly when you restart the system.
The installation software does not validate the password you enter. If you enter an
incorrect password, you can correct it from the User Administration program and
the Services dialog and the User Administration program after you complete the
installation. Refer to Chapter 5 of this manual for more information.
19. Click OK.
The Start Copying Files dialog appears.
20. Click Next to start copying files.
The DeltaV Operate for PROVOX Viewers Toolbar Setup dialog appears.
21. Click OK.
The dialog contents change
22. Click the large icon button.
Setup installs the viewer software and displays a popup indicating success.
If you are upgrading the DeltaV Operate for PROVOX software from a previous
release, two Registry Editor popups appear.
A-7
Are you sure you want to add the information in

C:\POC\PreviousDOPRegSettingsSTATION.reg to the registry?
Are you sure you want to add the information in
C:\POC\PreviousDOPRegSettingsSERVER.reg to the registry?
24. Click OK to acknowledge these popups.
A Question popup appears asking if you want to enter site-specific information.
25. Click Yes to enter or verify information.
The DeltaV Operate for PROVOX Properties dialog appears.
After you enter site specific information, the Setup Complete dialog appears.
26. Select Yes, I want to restart my computer.
If a dialog appears saying that Loggedon.exe is still running click End Now to
continue.
27. Remove the license media from the drive.
28. Click Finish.
The computer restarts.
29. After the system restarts, log on as Administrator and examine the Event Viewer
and verify that the system came up correctly.
Note
Before you use your system, refer to Chapter 5, Software Setup, for instructions for
verifying and changing other software settings.
30. Install the Adobe Acrobat Reader software if it is not already installed.
The Acrobat software can be found on the DeltaV Operate for PROVOX software
installation disk in the \Support\Adobe directory.
The installation is complete.
Post-Installation Setup
Now that you have installed the DeltaV Operate for PROVOX software on your
Console Data Server and DeltaV Operator Stations, refer to Chapter 5 of this manual
for information on settings required for both servers and operator stations for the
system to function properly.
A-8
PROVOX Operator Console Systems

If your PROVOX system has PROVOX Operator Consoles, the tasks required to
install DeltaV Operate for PROVOX software can include:
On PROVOX Data Servers:
1. Save all settings.
2. Upgrade the operating system to Windows Server if possible.
3. Install the DeltaV Operate for PROVOX console software on the PROVOX
Operator Console Data Server hardware.
On PROVOX Operator Console Operator Workstations:
1. Save all settings.
2. Convert PROVOX Operator Console Operator Workstations to DeltaV
Operator Stations (if possible), then install the DeltaV Operate for PROVOX
software on them.
3. Create a migration workstation (a PROVOX Operator Console Workstation that
supports PROVOX systems but does not have DeltaV Operate software or
DeltaV Operate graphics and does not communicate with DeltaV systems). Do
not upgrade migration stations to Windows 7.
On DeltaV Operator Stations:
1. Install DeltaV Operate for PROVOX software on existing DeltaV Operator
Stations.
2. Convert existing PROVOX Operator Console displays or create new displays.
Create a Migration station (optional):
1. Install DeltaV Operate for PROVOX software on PROVOX Operator Console
Operator Workstations.
Converting Existing Console Data Servers

This subsection explains how to upgrade the console software on PROVOX
Operator Console Data Servers with the DeltaV Operate for PROVOX software. If
your Console Data Server hardware meets the minimum requirements for Windows
Server 2008 and DeltaV Operate for PROVOX software, you can upgrade Console
Data Servers by doing the following:
1. Plan your upgrade and take some initial steps to prepare for it.
2. Save information as required.
A-9
3. Install Windows Server software.

4. Install DeltaV Operate for PROVOX software.
5. Checkout, setup, and restore data.
Note
The instructions in the following sections assume the PROVOX Operator Console is
at the 3.x revision level. If it is not, to use these instructions you must first upgrade your
Console Data Server to the 3.x revision level.
Planning And Preparation
Before performing the upgrade, determine the answers to the following questions and
discuss with the appropriate site personnel. These questions involve changes that may
have been made to the system since the original installation.
Have there been any changes to the default directories for the message (*.csv)
files?
What are the current settings for the minimum and maximum number of records
saved in the Console Event Journal database?
Has the PROVOX21Admin account password been changed?
After you have the answers to these questions, continue with the following.
Saving Console Data Server Information

Use the following steps to preserve important information from the current
installation. This includes the following:
Current PROVOX Operator Console license files
Current set of Spooler files
To save console information perform the following steps:

1. Log on as Administrator.
2. Make sure the console software installation disk is in the drive.
3. If Windows Explorer is not already running, right click on the Start button and
select Explore
4. From Explorer, create a folder named POC_Upgrade on the C: drive.
5. In the POC_Upgrade folder, create a folder named cfg (resulting in the directory
C:\POC_Upgrade\cfg).
6. Make a text file record of the current FRSI key in the registry:
A-10
a.
Start REGEDT32 using the Start | Run command and entering regedt32 in
the Open field of the Run dialog.
b. In the HKEY_LOCAL_MACHINE window, navigate to the SOFTWARE

key set and then to the FRSI key set. Make sure FRSI is the highlighted key.
c.
Select Registry | Save Subtree As
d. Set the Save as type field to text files

e.
Set the File name to c:\POC_Upgrade\cfg\FrsiRegistrySettings.txt.
f.
Click on the Save button to save the registry key.
g.
Exit Regedt32.
7. Because the upgrade may make the System and Application logs unusable, save
them to text files:
Saving the Application log:
a.
Start the Event Viewer using the Start | Run command and entering eventvwr
in the Open field of the Run dialog.
b. On the Log menu make sure that Application is selected (a checkmark

appears next to it)
c.
Select Clear All Events.
d. When prompted by the Clear Event Log dialog, click on Yes to save the
current contents.
e.
In the Save As dialog set the File name to c:\POC_Upgrade\applog.txt
f.
Set the Save as type to Text Files (*.TXT).
g.
Click Save to save the file.
h. Click Yes to clear the log.

Saving the System log:
a.
On the Log menu make sure that System is selected (a checkmark appears
next to it)
b. Select Clear All Events.

c.
When prompted by the Clear Event Log dialog, click Yes to save the current
contents.
d. In the Save As dialog set the File name to c:\POC_Upgrade\syslog.txt

e.
Set the Save as type to Text Files (*.TXT).
f.
Click Save to save the file.
g.
Click Yes to clear the log.
A-11
h. Exit the Event Viewer.

Console Properties.
Record the current settings for this console under each tab. If there has been no
change to the defaults from the original installation, use the defaults for this
installation. If changes have been made, note them so that the custom values can
be re-entered after you install the new software.
Record your entries below:
Highway Interface Tab

HDL IP Address: _____._____._____._____
Port A Baud Rate: ______
Port B Baud Rate: ______
Network Index: ______
Highway: ______
Device: ______
Enable Primary: yes no
Enable Secondary: yes no
Enable Maintenance port: yes no
CDS IP Address [1]: _____._____._____._____
CDS IP Address [2]: _____._____._____._____
Subnet Mask _____._____._____._____
Initialize an uninitialized HDL at next restart: yes no
Workstations Tab
Primary Node Names: ___________ ___________
__________ _________ __________ __________
Secondary Node Names: ___________ ___________
__________ _________ __________ __________
Message Spooler Tab

Message Files Location: _______________________
Max Disk Space: __________
A-12
Keep messages for: __________
Event Journal Tab

Min Records Retained: __________
Max Records Retained: __________
Enable Event Journaling: yes no
Calculation Expressions Tab

Calculation Expressions Files Location: ___________________
Number of Calculation Expressions: __________
Reports Tab
Reports File Location: _______________________
Number of Reports Saved: __________
Keep reports for: __________
Trend Tab
Files Location: _______________________
9. Most installations have the D:\ drive available. It may be useful to copy the
current POC directory and all of its sub-directories to the D:\ drive or an
alternate folder on the C:\ drive.
If the Console Data Server contains save directories from previous upgrades, you
may want to examine them and delete them if they are no longer necessary.
If the D:\ drive partition is not present, use the Disk Administrator to set the
partition.
Install Windows Server Software

Refer to Appendix B for introductory information on installing Windows Server
software and pointers to complete installation instructions.
Install The Console Software

Refer to Installing Software on Console Data Servers on page A-1 for instructions on
installing the DeltaV Operate for PROVOX software on a Console Data Server.
A-13
Checkout, Setup, and Restore Data

The remaining steps explain how to:
Check the installation to make sure it is working
Perform a few additional setup tasks
Restore files you saved earlier.
Perform the following steps:

1. After the system has started, log on as the PROVOX21Admin account.
2. Examine the Event Viewer Application and System logs to verify that the
console software started without problems. Refer to Chapter 4 of this manual for
more information.
If the console software fails to start because of a service error, verify that the
POC Base service password is the same as the PROVOX21Admin account
password. Then restart the system again or stop and start the POC Base service.
For information on setting the POC Base service password, refer to Chapter 5 of
this manual.
If the console software fails to start because the HDL link was not established, do
the following:
3. At the Console Data Server open the Console Properties dialog (from the start
menu navigate to DeltaV Operate for PROVOX | Settings | Console
Properties).
4. Select the Highway Interface tab
5. Select the check box in the HDL Initialization area.
6. Click the Help button. A help window appears.
7. Click the How to button in the help window. Follow the instructions to
uninitialize the HDL.
8. At the HDL, follow the instructions to uninitialize the HDL.
9. Restart the system.
You can either shut down and restart the computer or stop and start the POC
Base service. Either of these actions should initialize the HDL.
10. Use the system for a few minutes to determine that the installation is working
properly.
A-14
11. Log off of any current account session.

12. Download a configuration to the Console Data Server, if desired.
The upgrade is complete for this computer.
Before using the Console Data Server, refer to the instructions in Chapter 5 of this
manual to ensure that all software settings are correct.
Converting PROVOX Operator Console Workstations to

If the hardware platforms for your PROVOX Operator Console Workstations meet
the minimum requirements for DeltaV Operator Stations, you can convert the
Operator Workstations to DeltaV Operator Stations:
1. Plan your upgrade and take some initial steps to prepare for it.
2. Save information as required
3. Install Windows 7 workstation software
4. Install DeltaV software
5. Install DeltaV Operate for PROVOX software
6. Checkout, setup, and restore data
Installing DeltaV Operate for PROVOX Software on DeltaV

Operator Stations
Refer to Install DeltaV Operate for PROVOX Software on DeltaV Operator Stations
on page A-6 for instructions on installing the DeltaV Operate for PROVOX software
on DeltaV Operator Stations.
Creating Migration Stations

If you have existing PROVOX Operator Console displays you are going to convert to
DeltaV Operate displays, you may want to convert one or more of your PROVOX
Operator Console operator workstations to migration stations. Use migration stations
to view your existing displays as you convert or redraw your graphics.
Create a migration station by installing DeltaV Operate for PROVOX software on a
PROVOX Operator Console operator workstation.
A-15
Note
Do not install Windows 7 on migration stations. Do not uninstall the PROVOX

Operator Console software before installing DeltaV Operate for PROVOX software.
The software allows the PROVOX Operator Console operator workstation to display
data from the DeltaV Operate for PROVOX Data Servers (also known as Console
Data Servers). These workstations cannot be connected to the DeltaV network,
cannot display DeltaV data, and do not support the DeltaV Operate graphics.
Note
Migration stations are supported for migration only. They are not supported for process
control.
To install the software:
Note
The following instructions apply only if you are installing DeltaV Operate for
PROVOX software for the first time. To install later releases of the DeltaV Operate
for PROVOX software on migration stations, you must first uninstall PROVOX
Operator Console software, reinstall PROVOX Operator Console P 3.0 software, and
then install the upgrade as described in the following steps.
1. Verify that the PROVOX Operator Console Workstation has P3.x revision
software installed.
2. Select Start | Settings | Control Panel.
3. Double click on Services
4. In the Services application, select the POC Station service and click Stop.
Confirm by clicking Yes.
5. In the Services application, select the Fix service and click Stop. Confirm by
clicking Yes
6. Exit the Services application and the Control Panel.
7. Insert the DeltaV Operate for PROVOX software installation disk in the
operator workstation's drive.
8. Insert the license media in the appropriate drive.
9. Close all applications except Windows Explorer.
10. From Windows Explorer, navigate to setup.exe on the installation disk and
double click it.
11. Acknowledge the dialogs until the Setup Type dialog opens.
12. Select PROVOX Operator Console P3.* Workstation Update (Fix32) and click Next.
13. Follow the remaining instructions until the installation is complete.
A-16
Note
When you set the password for the PROVOX21Admin account it must match the
password on the data server and operator stations.
Now that you have installed the DeltaV Operate for PROVOX software on your
Console Data Server and DeltaV Operator Stations, refer to Chapter 5 of this manual
for information on settings required for both servers and operator stations for the
system to function properly.
Install Adobe Acrobat Reader Software

Both Console Data Servers and Operator Workstations require Acrobat Reader
software to view the DeltaV Operate for PROVOX online manuals. To install Adobe
Acrobat Reader, follow these steps:
1. Log on as Administrator.
2. Make sure the console software installation disk is in the drive.
3. Open Windows Explorer if it is not already running.
4. Navigate to the directory \Support\Adobe
5. Double click on the file AdbeRdr90_en_US_Std.exe.
6. Follow the onscreen prompts to complete the installation.
7. Refer to Setting Acrobat Reader Options on page 5-25 to set up Acrobat Reader.
A-17
A-18
Appendix B Restoring Windows Software

Introduction
The DeltaV Operate for PROVOX software runs under the Microsoft Windows
operating system. The hardware for the system is shipped with the operating system
installed, but there may be circumstances in which you must restore the operating
system (and re-install the console software).
Installing any operating system is a major undertaking. To streamline this process, all
DeltaV workstations are shipped with an operating system recovery DVD. This DVD
restores the operating system according to the specifications for use with the DeltaV
software.The recovery DVD is the only supported method to install the Windows
operating system.
It is important to note that the operating system recovery DVD is specific for each
computer type in the DeltaV system. You must use the recovery DVD created for the
computer you are reinstalling. You should only need to reinstall the operating system
in the event of a computer problem. The image restore process is the only Emerson
supported method for restoring the operating system.
Please refer to Emerson Process Management KBA #AP-1000-0015 for operating
system recovery instructions.
If you need to restore the console software and the Windows operating system, you
must restore Windows before you install the console software.
There are two types of Windows software: Server and Workstation. DeltaV Operate
for PROVOX Data Servers (Console Data Servers) require Windows Server 2008
software. DeltaV Operate for PROVOX Operator Stations require Windows 7
workstation software.
After you recover Windows workstation software you can install the DeltaV software,
then the DeltaV Operate for PROVOX software.
After you install Windows Server software from the DeltaV instructions refer to
Additional Windows Server 2008 Setup on page B-3 for information on additional
server setup that applies to DeltaV Operate for PROVOX only, before you install the
DeltaV Operate for PROVOX software.
Before you install Windows Server software, refer to the following section for
information on preliminary planning.
Restoring Windows Software
B-1
Note
It is important that you install Windows and the supporting software in the order listed
in the instructions.
If you do not install in this order the software may not work as intended.
Note
The instructions for installing Windows are specific for the hardware and software being
shipped when the instructions were developed. You may need to modify these instructions
for your hardware.
cards and drivers have changed and will continue to change.
The instructions apply generally to NIC and sound hardware and drivers, but do not
apply directly to hardware and software of earlier releases.
Preliminary Planning
You should determine the following information prior to installing the Windows
Server software:
B-2
The name of the workgroup to which this computer belongs. The server must be
set up in a workgroup rather than a domain. The default workgroup is
PROVOX21 and it is recommended that you not change it.
The name that this computer will be called. This name must not conflict with
other devices on the network.
The TCP/IP address for this computer.
The TCP/IP addresses for the network interface controller (NIC) card
connecting the Highway Data Link to this Console Data Server. The default is
192.168.22.10.
The Gateway TCP/IP address for the network if available.
The TCP/IP address for the Highway Data Link (HDL). The default is
192.168.22.2.
The PROVOX Highway address for the HDL. This address is made up of the
highway number, the device number, and the area number.
Additional Windows Server 2008 Setup

After Windows Server 2008 software is installed there are additional tasks you must
perform to make the server ready for use with DeltaV Operate for PROVOX
software. The tasks are:
Adding an Application Server Role
Disable Internet Protocol Version 6 (TCP/IPv6)
Disable User Account Control
Disable Windows Time service
Adding an Application Server Role

To add an application server role:
1. Log on to the server as Administrator.
2. Click Start |Settings | Control Panel.
3. In the Control Panel window double-click Administrative Tools.
4. In the Administrative Tools window double-click Server Manager.
A dialog similar to the following appears
B-3
5. In the right pane, scroll down to the Roles Summary and click Add Roles.
The Add Roles Wizard Before You Begin dialog appears.
Note
Ignore the instructions to install Windows updates on this information dialog. All
approved updates are already installed. Do not enable automatic Windows updates.
6. After verifying the information on the dialog, click Next.
The Add Roles Wizard Select Server Roles dialog appears.
7. Select the check box for Web Server (IIS).

A popup dialog appears that lists other features that will be installed.
8. Click Add Required Features on the popup to continue.
9. Click Next on the Add Roles Wizard Select Server Roles dialog.
The Add Roles Wizard Web Server (IIS) informational dialog appears.
10. Click Next to continue.
The Add Roles Wizard Select Role Services dialog appears.
B-4
11. Select the check box for ASP (not ASP.NET).
12. Click Add Required Role Services on the popup to continue.
B-5
13. In the Add Roles Wizard Select Role Services dialog, scroll down and select the
check box for IIS 6 Scripting Tools. It is under Management Tools, IIS 6
Management Compatibility.
14. Click Add Required Role Services on the popup to continue.
15. On the Add Roles Wizard Select Role Services dialog, click Next.
16. On the Add Roles Wizard Confirm Installation Selections dialog, click Install.
An Installation Progress dialog appears, followed by an Installation Results dialog.
17. In the Server Manager dialog in the Role Services section review the services
installed, then exit the Server Manager.
B-6
Disabling Internet Protocol Version 6 (TCP/IPv6)

For the viewer applications to work correctly, TCP/IPv6 must be disabled on all NIC
cards on Windows Server 2008 machines. To do so:
1. Open the Network Connections dialog.
2. Double click one of the network connections.
3. On the connection Status dialog, click Properties.
4. On the connection Properties dialog, make sure the check box for Internet
Protocol Version 6 (TCP/IPv6) is not selected.
6. Click Close to close the connection Status dialog.
7. Repeat steps 2 through 6 for the other network connections.
Disabling User Account Control (UAC)

To disable UAC:
1. Log on to Windows as an Administrator.
2. Launch msconfig from the Run menu to open System Configuration.
3. Click on the Tools tab.
4. Scroll down till you find Disable UAC and click to highlight the line.
5. Click the Launch button.
A command window opens.
6. When the command completes, close the command window.
7. Close System Configuration.
You must restart the computer for the changes to apply.
Disabling Windows Time Service

To disable this service:
1. Log on to Windows as an Administrator.
2. Select Start | Settings | Control Panel | Administrative Tools | Services.
3. In the Services window, double click the Windows Time service.
B-7
4. On the Windows Time Properties dialog, if the Service status is Started, click
Stop.
5. Change the Startup type to Disabled.
6. Click OK
Additional setup is complete.
B-8
Appendix C Upgrading Consoles

Introduction
During the life of your system, you may need to upgrade or add or change one or
more components. This section addresses typical console upgrades:
Adding Connections (adding operator stations to a console)
Change the number of points
Add standard unsolicited data reporting (this may be necessary if your system
uses pre-1984 device programming)
Add Activities to the console
Adding Event Journal
Upgrading a previous release of DeltaV Operate for PROVOX software
The following table summarizes these upgrades and the actions required on both
servers and operator stations to implement the upgrades.
Table C-1 Actions Required for Various Console Upgrades

Upgrade
Action Required
Server
Install
License
Reinstall
Software
Total
Download
Operator Station
Partial
Download
Restart
Add Operator Station

Connections
Add PROVOX Points
Add Std. Unsol. Data

Reporting
Add Activities
Add Event Journal
Upgrade from previous

revision
Upgrading Consoles
Reinstall
Software
Restart
C-1
Upgrading Console Software Licenses

If you are upgrading your DeltaV Operate for PROVOX console software license and
are not making any other hardware or software changes, perform the following steps:
1. For every console you are upgrading, obtain new license media.
Note
Remember that the console software license is keyed to the License Module attached to
the console's Highway Data Link. You must use the license media that matches the
License Module when upgrading a console.
2. Stop the POC Base service on the primary Console Data Server to make sure the
license files can be copied. Note that stopping the POC Base service interrupts
console operations on operator stations.
3. Copy the POCLicense.txt and POCLicense.sig files from the License media to
%POCRoot%\cfg (typically C:\POC\cfg) on the Console Data Server.
4. Restart the POC Base service on the primary Console Data Server to establish
the license change.
5. Copy the POCLicense.txt and POCLicense.sig files from the License media to
%POCRoot%\cfg (typically C:\POC\cfg) on all operator stations defined as
Primary Nodes in the servers settings dialog. (From the Start menu navigate to
DeltaV Operate for PROVOX | Settings | Console Properties to verify which
operator stations are affected).
Repeat these steps on the secondary Console Data Server.
Adding Operator Stations to Existing Consoles

If you are adding a DeltaV Operator Station to an existing process control network of
PROVOX Console Data Servers and operator stations, perform the following steps:
1. Set up the operator station hardware as required. Refer to the section Installing the
DeltaV Workstation in the DeltaV Books Online.
2. Verify that the operator station you are adding has the same version of the
console software that is running on the primary and secondary Console Data
Servers this operator station will connect to.
If you are installing a new operator station, do the following:
C-2
Assign an IP address to the operator station per your plants policies

Assign a name to the operator station per your plants policies.
Restart the operator station so the IP address and name changes take effect.
If you are adding an operator station that has already been in service or that you
need to reinstall for some reason, do the following:
Install or re-install Windows and other Microsoft components as needed.

Refer to Getting Started with Your DeltaV Automation Software for more
information. During the installation set the IP address and name of the
operator station as required.
Install DeltaV software. Refer to the section Reinstalling DeltaV Software in
DeltaV Books Online for more information.
Install the DeltaV Operate for PROVOX software. Refer to Appendix A of
this manual for more information.
3. Use the Console Properties dialog (from the Start menu navigate to DeltaV
Operate for PROVOX | Settings | Console Properties) to set the primary and
secondary Console Data Servers for the operator station.
4. If you had to upgrade the existing console software license of the Console Data
Server to add the additional operator station, use the new license media and do
the following:
Note
Stop the POC Base service on the primary Console Data Server.
Copy the POCLicense.txt and POCLicense.sig files from the License media
to %POCRoot%\cfg (typically C:\POC\cfg) on the primary Console Data
Server. (If you are installing a new operator station, the license files should
already match those on the license media. If you are re-installing an existing
operator station, you installed the license when you installed the console
software.)
the server's Highway Data Link. You must use the license media that matches the
Restart the POC Base service on the Console Data Server to establish the
license change. Note that stopping and restarting the POC Base service
interrupts console operations briefly on operator stations.
5. Enter the operator station name in the Console Properties dialog of the primary
and secondary Console Data Servers. (From the Start menu navigate to DeltaV
Operate for PROVOX | Settings | Console Properties.)
If the operator station is connected to a secondary Console Data Server, repeat
steps 4 and 5 for the secondary server.
6. Set the password of the PROVOX21Admin account and the password for the
POC Station service to the same passwords used on other operator stations in
the console workgroup.
Upgrading Consoles
C-3
7. Start the POC Station service on the operator station.

8. Perform a total download to the console.
You should now be able to log on to the operator station and log on to the operator
interface.
Adding Unsolicited Data Reporting

If your PROVOX system uses pre-1984 device programming, you may need to add
Standard Unsolicited data reporting if it is not already installed. Do not install or
enable Standard Unsolicited data reporting unless you know you need it. If you are
unsure, consult with your Emerson Process Management service representative.
Note
Enabling Standard Unsolicited data reporting on systems can cause undesirable side
effects under some circumstances. Enable Standard Unsolicited data reporting only if
necessary.
1. For every console you are adding unsolicited data reporting to, obtain new license
media.
Note
3. Uninstall the Console Software from the primary Console Data Server. Refer to
Uninstalling Software from Console Data Servers on page C-5.
4. Reinstall the Console Software on the Console Data Server
Standard Unsolicited.
An informational popup appears.
6. Click OK.
The Unsolicited Reporting Control dialog appears.
7. Select Enable Standard Unsolicited Reporting and click OK.
8. Restart the POC Base service on the primary Console Data Server.
C-4
Adding Event Journal

If you want to add Event Journal capability to your system, do the following:
1. For every console you are adding Event Journal capability to, obtain new license
media.
Note
3. Save the following files from the installed \POC\Cfg directory to a location that
won't be overwritten during an install:
TrendTraces_Current.txt
TrendTraces_Master.txt
CalcAttrs_Current.csv
CalcAttrs_Master.csv
4. Uninstall the Console Software from the primary Console Data Server. Refer to
Uninstalling Software from Console Data Servers on page C-5.
5. Reinstall the Console Software on the primary Console Data Server.
6. Copy the files saved in step 3 back to the installed \POC\Cfg directory.
7. Restart the primary Console Data Server.
8. Perform a total download of the console.
Uninstalling Software from Console Data Servers

If an upgrade you are performing requires that you uninstall the Console Data Server
software, follow the instructions in this section.
1. Disconnect the Ethernet cables and restart the computer.
2. Log on as Administrator (not PROVOX21Admin).
3. Select Start | Settings | Control Panel.
4. Open Programs and Features.
Upgrading Consoles
C-5
5. Remove the following applications in the order listed:
Note
DeltaV Operate for PROVOX Viewer Toolbar

DeltaV Operate for PROVOX Web Components
DeltaV Operate for PROVOX
If prompted, select the Remove All option to remove all shared components.
A dialog appears showing the progress of the uninstall.
After the PROVOX Operator Console uninstall is complete and before you
close the dialog, click the Details button and make a note of the files listed.
You will have a chance to save these files in a later step.
6. Click the OK button on the Details window, then click the OK button on the
uninstall dialog.
7. Right click on the Internet Explorer icon on the desktop and select Properties.
(If the desktop does not contain an Internet Explorer icon, start Internet
Explorer and then select Tools | Options from its main menu.)
8. Click the Settings button in the Temporary Internet files area.
9. Click the View Objects button in the Settings dialog.
10. If FRSISystemInfo.MiscSysInfo is in the Program File list, right click on it and select
Remove. If the file is not in the list, continue with the next step.
11. If FRSIDisplayElements.DurationControl is in the Program File list, right click on it
and select Remove. If the file is not in the list, continue with the next step.
12. Close the Downloaded Program Files window, the Settings dialog, and the
Internet Properties dialog.
13. Make sure all drives are empty.
Cleanup
Before you continue, clean out the recycle bin and the Start menu document list:
1. Open the Recycle Bin by double clicking on the icon on the desktop. Select File |
Empty Recycle Bin to empty the recycle bin.
2. Close the Recycle Bin.
3. Place the cursor on the task bar and use the alternate mouse button to open the
popup selection menu. Select the Properties option. In Taskbar Start Menu
Properties on the Start Menu tab, click the Customize button for the selected
menu. On the Customize dialog, click Clear. This clears the Documents menu.
Exit the Taskbar properties dialog by clicking on the OK button.
C-6
Note
You must restart the computer so that files marked for deletion by the uninstall software
are actually deleted from the system.
4. Select Start | Shut Down, then select Restart the computer and click on the Yes
button to restart the system. You must restart so the system can remove files
marked for deletion.
5. After the system has started, log on under the PROVOX21Admin account.
6. Reconnect the Ethernet cables to the Console Data Server.
During uninstall the \POC directory was renamed to \POC-yyyy-mm-dd-hh-mm-ss-ms to
save any files that remain in the directory branch. You may need to refer to these files
during re-install.
Upgrading from a Previous Software Release

If you are performing an upgrade on a system that includes DeltaV Operate for
PROVOX consoles, there are some very specific sequential requirements to follow
during upgrades to minimize the amount of time control is interrupted. Before you
begin to upgrade such a system be sure to carefully read the following overview and
the detailed installation and upgrade instructions for servers and workstations.
DeltaV Operate for PROVOX Network Upgrade

The following overview explains how to upgrade a DeltaV Operate for PROVOX
system consisting of two redundant servers and four operator stations as shown in the
following figure.
Upgrading Consoles
C-7
Figure C-1
Upgrade Example System
One possible sequence to upgrade the system is:

1. Record all DeltaV and PROVOX setup information on the PROVOX Servers
and DeltaV Operate for PROVOX Operator Stations as described in Chapter 4
of this manual.
2. Stop Activities on the servers.
3. Manually switch hosted points to Server S1.
4. From the Console Properties dialog, assign all operator stations (temporarily) to
Server S1.
This server maintains control until Server S2 and the workstations are upgraded.
5. Upgrade Server S2.
The tasks required are:
C-8
Upgrading the operating system to the currently supported version of

Windows Server software, if necessary
Uninstalling the existing DeltaV Operate for PROVOX software (if

necessary) and installing the new DeltaV Operate for PROVOX software.
Restart the server.
6. Restore the setup data on Server S2.
7. Upgrade DeltaV Operate for PROVOX Operator Station W1.
The tasks required are:
Upgrading the operating system, if necessary.

Installing the new DeltaV software.
Uninstalling the existing DeltaV Operate for PROVOX software (if
necessary) and installing the new DeltaV Operate for PROVOX software.
Restart the workstation.
If you do not need to upgrade the operating system and are upgrading from a version
of DeltaV software that supports it, you can simplify the upgrade by using the DeltaV
Upgrade Wizard. The upgrade tasks are:
a.
The wizard saves PROVOX information.
b. The wizard uninstalls DeltaV software.

c.
You manually uninstall the DeltaV Operate for PROVOX software.
d. The wizard installs DeltaV software.

e.
Note
You manually install the DeltaV Operate for PROVOX software.
Do not start DeltaV Operate. If you start DeltaV Operate now errors result.
8. Ensure that all the setup data on the operator station is correct.
9. From the Console Properties dialog, assign this operator station to the Server S2.
10. Start DeltaV Operate on Operator Station W1 and establish control from the
operator station.
11. Repeat steps 7 through 10 on all other DeltaV Operate for PROVOX Operator
stations, assign each operator station to Server S2, and establish control from
each operator station.
12. Repeat steps 5 and 6 on Server S1.
13. Assign one operator station to Server S1 and establish control from the operator
station.
14. Reassign all workstations to servers as desired.
Upgrading Consoles
C-9
Component Upgrade Overview

After you decide the order to upgrade your DeltaV Operate for PROVOX network
based on the information in DeltaV Operate for PROVOX Network Upgrade on
page C-7, you can proceed with the component upgrade. The tasks required to
upgrade a DeltaV Operate for PROVOX network component depends on the type of
component. The following lists high-level instructions for upgrading components.
For detailed information on any step, refer to the appropriate section in this manual.
On DeltaV Operate for PROVOX Operator Console Data Servers:
1. Save settings.
2. Upgrade the operating system on the Console Data Server hardware to Windows
Server software, if necessary.
3. Install the new DeltaV Operate for PROVOX console software on the
PROVOX Operator Console Data Server hardware.
On DeltaV Operate for PROVOX Operator Stations:
1. Save settings.
2. Upgrade the operating system to Windows 7, if necessary.
3. Install the new DeltaV software.
4. Install the new DeltaV Operate for PROVOX software.
5. Convert existing PROVOX Operator Console displays or create new displays.
On migration workstations:
Note
Do not uninstall the PROVOX Operator Console software from the migration
workstation.
1. Uninstall any DeltaV Operate for PROVOX hotfixes that have been installed.
2. Install the DeltaV Operate for PROVOX software and select the PROVOX
Operator Console P3.* Workstation Update (Fix32) option. You do not need to
uninstall the previous version of DeltaV Operate for PROVOX software before
you install the current version.
C-10
Appendix D Other Network Solutions

Introduction
This section contains information on supported network configurations for installing
DeltaV Operate for PROVOX Consoles. The configurations shown in this section
include:
Note
Plant Network Connection with Router Only Connecting the process

network to a plant network using a router.
Remote Workstations Fiber Optic Link from a Console Data Server to

operator stations.
Redundant Remote Workstations Fiber optic links from Primary and

Secondary Console Data Servers to operator workstations.
In addition, the figures in this section show only the PROVOX control network and
operator stations. They do not show connections to the DeltaV control network.
Plant Network Connection with Router

This subsection shows how to connect two process networks to a plant network. In
this case one of the switches that serves operator stations connects through a router
to the plant network. Etherchannel links must be configured between switches if
redundant cables are used as shown.
Other Network Solutions
D-1
Figure D-1
D-2
Connecting Process Networks to A Plant Network without A Central Switch
Remote Workstations
If you need to install your operator stations remotely from the Console Data Servers,
you can use Fiber Optic cable and a switch that has additional built-in fiber optic ports
as shown in the following figure.
Note that the redundant Etherchannel links between the switches use fiber optic
cable and are limited to a length of 2 kilometers (full duplex).
Figure D-2
Using Fiber Optic Cables to Connect Remote Workstations
D-3
Redundant Remote Workstations

This subsection shows how to connect a primary/secondary pair of Console Data
Servers to operator stations at a distance of up to 2 kilometers using fiber optic cable.
Figure D-3
D-4
Primary/Secondary Console Data Servers with Remote Operator Stations
To set up the DeltaV Operate for PROVOX Console Ethernet Primary/Secondary

consoles, perform the following steps:
1. Perform the installation procedure to install the Primary Server (refer to Setting
Up Consoles on page 3-4). Include connecting it to a Ethernet switch.
2. Install the Console Data Server's operator stations remotely and connect them to
a second Ethernet switch.
3. Before connecting any fiber optic or twisted pair redundant Etherchannel links
between switches, be sure to configure the Etherchannels first.
4. Repeat steps 1 through 3 to install the Secondary Server and its remote operator
stations.
5. Connect the two switches connected to the operator stations with redundant
Etherchannel links.
D-5
D-6
Index
calculation attributes 7-13
examples 7-15
expressions 7-14
Symbols
#CURRENT
7-23
calculation expression
syntax 7-14
A
accounts
8-3
accumulations
character substitution
point and display tags
8-34
5-40
Acrobat Reader
installing A-8
CHIP
application software 8-34
Active Desktop
Internet Explorer 8-1
configuration
alarm priority 6-9
console device 6-3
converting
from
PROVUE
or
Workplace 6-1
database 6-1
display editor 6-11
equipment list definition 6-7
Highway Access Control List 6-11
operator display list 6-5
option definition 6-3
PMA definition 6-8
PMA list 6-6
PPA definition 6-9
procedures 6-8
report attributes 6-7
report header definition 6-7
report list definition 6-6
shift table definition 6-4
targeting points 6-12
trend 6-4
update 8-37
user access list 6-6
user definitions 6-9
activity point
8-34
Adobe Acrobat Reader

installing A-8
ANYNODE
6-10
attribute 7-9
selecting 7-7
attributes
calculation 7-13
display 7-10
FST 7-26
THISUSER 7-17
writable 7-25
writing from displays 7-23
writing from Instrument Area 7-23
writing to from displays 7-23
B
backups
4-1
books online
8-12
C
Cabling
server cabinet
3-8, 3-9
calculation attribute expression files
Index
7-16
Operator
console 8-34
defining HDL 5-16
interconnecting 3-13, 3-16
operator station parameters 3-31
password 5-8
primary 8-34
redundancy 8-25
Index-1
DDP area
redundant 8-34
redundant pairing 8-34
secondary 8-34
setting up 3-4
setup 3-4
simplex 8-36
system configuration 3-17
unintialize HDL 5-15
upgrading C-1
Windows administrator password
8-5
Defining HDL
console 5-16
DeltaV Operate
customizing 5-36, 5-38
starting and testing 5-44
3-18
Console Data Server

cabinet 3-7
preserving information A-10
redundancy 8-25, 8-28
server cabinet
installing 3-8
switchover 8-28, 8-35
DeltaV Operator Station

parameters 3-31
display
link limits 7-3
naming 7-2
display attributes
7-10
display configuration
7-1
display elements 7-3

dynamic 7-3
static 7-3
Console Data Server redundancy

integrity faceplate 8-29
display list

upgrading console software A-9
6-5
display names
7-1
console restart 8-24
display tag
substitution 5-40
valid characters in ENVOX software
console security 8-2

default 8-4
displays
converting
console service
download
partial 8-37
redundant pairs
total 8-37
console messages
8-8
5-18
console software
installing A-1
upgrading Console Data Servers
console startup
A-9
8-4
console-resident point
redundancy 8-26
5-44
8-37
customize DeltaV Operate 5-36, 5-38
entry fields
configuring 7-25
field types 7-23
ENVOX software
using 6-1
Data link
inserting
DCD point
DDP
Index-2
7-23
7-4
8-34
5-41
EPCI point
8-34
Ethernet switch
configuring 3-23
description 2-5
Installing Your DeltaV Automation System
Event Journal
size
8-9, 8-11
Expression Builder
integrity faceplate
Console Data Server redundancy
7-4, 7-5
Expression Builder dialog
8-6
7-7
8-29
integrity point 8-34
intended audience
faceplates
field
Internet Explorer
Active Desktop 8-1
8-8
7-9
frsPOCIntegrity
frsPocTasks
1-6
internet options
setting 5-24
7-18
7-18
FST attributes 7-26
license
upgrading
C-2
license popup
removing
5-27
Grounding
server cabinet
3-8
link limits
H
HDL
and POC Base service A-4
description 2-4
installing in server cabinet 3-7
uninitialize 5-15
Highway Data Link
description 2-4
horn
acknowledgment
Index
manual switchover
effects of console-resident point
8-36
8-8
6-4
Installing
console 3-4
HDL
server cabinet 3-7
Primary/Secondary consoles
server
server cabinet 3-8
server cabinet 3-7
UPS in server cabinet 3-7
5-43
messages
console
Network Time Protocol
Instrument Area 8-5

positioning 8-6
Logging in
7-3
NTP
8-5
8-5
O
occurrence numbers
3-34
7-8
Operator Display List form
6-5
operator station
adding to existing console C-2
setting POC service 5-18
Operator Workplace
6-1
Other network solutions

Index-3
application software 8-34

software
CHIP 8-34
plant network connection with router D-1

redundant remote workstations D-4
remote workstations D-3
PROVOX communication
enabling 5-29
P
password
changing default 5-8
console 5-8
PROVOX21Admin 5-20
pictures
converting
PROVOX toolbar
creating 5-32
PROVOX21Admin
password 5-20
5-44
POC Service
and setting the HDL
redundancy 8-25, 8-34

active console 8-35
changing console pairing 8-37
console
pairing 8-34
Console Data Server 8-25, 8-28
console-resident point 8-26
examples 8-37
standby console 8-35
synchronization 8-36
A-4
POC Station Service

stopping A-16
POC\programs folder
5-26
point
console_resident
accumulation 8-34
activity 8-34
discrete control device 8-34
extended pulse count input (EPCI)
integrity 8-34
manual switchover effects 8-36
sourced 8-34
targeted 8-34
point tag
substitution 5-40
valid characters in ENVOX software
Power-up test
server cabinet
3-12
8-34
redundancy application
Console Data Server 8-31
console-resident point 8-36
redundant console 8-35
pairing 8-34, 8-37
reports
5-41
restart
8-12
8-24
primary console
8-34, 8-37
scripts 7-18
accessing DDP values from 7-23
primary servers
5-39
secondary console
8-34, 8-37
secondary servers
5-39
primary workstations
5-39
Primary/Secondary Ethernet Consoles

setting up 3-34
privilege
example
PROVOX
Index-4
6-10
secondary workstations
security
5-39
8-2, 8-4
Server
equipment list
2-1, 2-4
switchover
Console Data Server
server cabinet
installing 3-8
server
connecting a viewer to
syntax
tagnames
8-10
system setup 3-2
server cabinet
cabling 3-8
grounding 3-8
installing HDL 3-7
installing server 3-8
power cabling 3-9
T
tag
selecting 7-7
substitution 5-40
tag substitution
log file 5-42
service 5-18
POC Base 5-18, A-4
POC Station 5-18
Setting up
console 3-4
Primary/Secondary Consoles
stale data
Standard Unsolicited Transmit
5-39, C-1, C-4
THISUSER
attributes
3-23
to
DeltaV
Operator
7-17
time
synchronizing
8-5
8-5
5-32
trace data set

definition files
8-22
trace data sets

adding 8-18
creating 8-19
removing 8-21
5-22
substitution
log file 5-42
point and display tags
Index
5-
network connections
Stations 3-33
toolbar
PROVOX
8-36
8-5
Switch
configuring
Test
time zone
8-24
startup 8-4
verifying
tagname 7-8
attribute 7-9
entering 7-9
field 7-9
syntax 7-9
tag 7-9
3-34
setup
customizing DeltaV Operate 5-36, 5-38
defining servers and workstations 5-39
other settings 5-27
positioning Instrument Area and Trend windows
27
task overview 5-2
Unsolicited Data Reporting C-4
Unsolicited Transmit method 5-39, C-1
simplex console
7-9
System configuration
console 3-17
Server cabinet
installing 3-7
power-up test 3-12
shutdown
8-28, 8-35
5-40
trend
adding trace data sets 8-18
trace data set 8-13
trace data sets 8-13
Index-5
trend views 8-13, 8-14

viewing 8-21
trend sets
importing configured sets
Trend Viewer
8-13
Trend viewer
8-16
Windows administrator password

console 3-18
8-16
Trend Window 8-16

positioning 8-14
size 8-14
troubleshooting
5-45, 8-23, 8-24
U
Uninitialize HDL
console 5-15
Unsolicited Transmit setup
5-39, C-1, C-4
upgrading consoles C-1

upgrading licenses
C-2
UPS
server cabinet
3-7
user definitions
ANYNODE
6-10
USER_SETTINGS.GRF
users
5-38
8-3
UserSettings.grf 5-36
creating 5-36
variables 5-38
V
VBA
7-18
viewer
connecting to a server
documents 8-12
Viewers
8-9
viewers
8-9
Index-6
8-10

002 Getting Started PDF

Uploaded by

Copyright:

Available Formats

002 Getting Started PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

002 Getting Started PDF

Uploaded by

Copyright:

Available Formats

D3P01861802

Getting Started With

Chapter 2 Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3 Initial Hardware Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

System Configuration: Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4 Saving Console Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Chapter 5 Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Getting Started with DeltaV Operate for PROVOX Consoles

Chapter 6 Database Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PMA Definition Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Chapter 7 Display Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Getting Started with DeltaV Operate for PROVOX Consoles

Chapter 8 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Importing Configured Trend Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A Installing the Operator Console Software . . . . . . . . . . . . . . . . . . . . . A-1

Getting Started with DeltaV Operate for PROVOX Consoles

Appendix B Restoring Windows Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C Upgrading Consoles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D Other Network Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Getting Started with DeltaV Operate for PROVOX Consoles

DeltaV Operate for PROVOX Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting Started with DeltaV Operate for PROVOX Consoles

Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Getting Started with DeltaV Operate for PROVOX Consoles

DeltaV Operate for PROVOX Console

PROVOX Control Network (HDLs, controllers, I/O, and so on)

DeltaV Operate for PROVOX Data Server

PROVOX Operator Console Migration Station (not shown)

DeltaV Operator Stations

DeltaV Control Network (controllers, I/O, and so on)

Getting Started with DeltaV Operate for PROVOX Consoles

Differences between Operator Workplace and DeltaV

ENVOX graphics configuration is not supported (DeltaV graphics are used

Complex conditionals must be reconfigured with the new Calculation Attribute

Real-time trending has different features.

PROVOX System Clock is not supported.

Alarms and Events are reported to the Event Journal.

Limited compatibility with Batch Data Manager.

DeltaV Operate for PROVOX Interface

Getting Started with DeltaV Operate for PROVOX Consoles

Typical User Interface

The user interface includes the following:

The main window which can consist of:

Two main pictures.

PROVOX-related applications that are available are:

Instrument Area (includes the DDP area)

Summaries (Point Status and Communications Failure)

Persons responsible for training operators how to use the software.

Getting Started with DeltaV Operate for PROVOX Consoles

Operate for PROVOX software, DeltaV terminology is used when required

Installation and Upgrade Scenarios

Upgrading to a new version of DeltaV Operate for PROVOX software.

References References to other documents give the document name and

Commands Command lines shown in this manual include the operating

Move the pointer (arrow or other shape) until the tip

Point to the item you want to select, then press and

Point to the item you want to select, then click the

Drag and Drop

Press and hold down the primary button while you