Getting Started with DeltaV Operate for RS3

Transcription

Getting Started with
DeltaV Operate for RS3
Part No. 12P30870401
March 2007
© 1996-2007 Fisher-Rosemount Systems, Inc. All rights reserved.
Printed in UK
DeltaV, the DeltaV design, PlantWeb, and RS3 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 warrantees 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
DeltaV Operate for RS3 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Station Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
DeltaV Operate for RS3 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
DeltaV Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Conventions Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Warnings, Cautions, and Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Chapter 2: PC Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
PC Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
PC Naming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Chapter 3: Installing DeltaV Operate for RS3 Software . . . . . . . . . . . . . . . . 3-1
Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Install Microsoft Access 2002 Runtime Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Install Other Application Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install DeltaV Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Install DeltaV Operate for RS3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Operator Station Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
RNI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Running the RNI Configuration Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
RS3 Environment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
General Setup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Connection Setup Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
RS3 Tag Data Rate Control Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Security Setup Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Setup Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Chapter 4: Re-Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Uninstalling the DeltaV Operate for RS3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Saving Existing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Saving the Security Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Contents-1
Saving the Console Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving Registry Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-installing the DeltaV Operate for RS3 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore the Security Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore the Registry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore the Configuration Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4-2
4-3
4-3
4-4
4-4
4-5
Chapter 5: Software Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
System and Security Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Setting Up Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Security Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Excel Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Testing the RNI Device Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Enable RS3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Creating RS3 Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Create Settings and Layout Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Settings and Layout Files Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Creating Settings Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Creating Layout Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Chapter 6: Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Console Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS3 Environment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Process Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Historical Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Journal Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-1
6-2
6-2
6-3
6-4
6-4
6-4
6-5
Chapter 7: DeltaV Operate for RS3 Desktop . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toolbar Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS3 Alarm Banner Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RS3 Alarm Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Highest Priority Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm List Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch Input Button (INP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents-2
7-2
7-2
7-2
7-3
7-5
7-5
7-6
7-6
7-7
Acknowledge Button (ACK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Alarm Lists Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Alarm States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Alarm List Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Alarm Types in List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
List Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Select Plant Unit/Plant Unit Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Selecting, Acknowledging, and Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
User Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Faceplates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Faceplate Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Controller Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Continuous Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Discrete Faceplate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Device State Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
RS3DIAG Picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Tag Status Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Alarm Conditions Displayed on Tag Status Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Tuning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Display of Lost or Questionable Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Chapter 8: Using the Online Help and Documentation . . . . . . . . . . . . . . . . 8-1
DeltaV Operate for RS3 Operator Station Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Help Menu: Entering Help from Help Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Find Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting to the Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Jumps in Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Context-Sensitive Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tool Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What’s This? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Annotating Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Searching Online Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-1
8-2
8-2
8-3
8-3
8-4
8-6
8-6
8-6
8-6
8-6
8-7
8-8
8-9
Chapter 9: RS3 Configuration Applications . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Configure DeltaV Operate for RS3 Operator Station Application . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
General Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Configure Alarm Acknowledge Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Contents-3
Configure Alarm Broadcast Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Pairs Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node Ownership Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Plant Unit Ownership Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Plant Unit Configuration Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure RS3 Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-6
9-6
9-7
9-7
9-7
9-9
Chapter 10: Creating and Configuring Graphics . . . . . . . . . . . . . . . . . . . . 10-1
DVSYS and FIX32.THISNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Names in DeltaV Operate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Display Elements and Link Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Expression Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Expression Builder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selecting a Tag and Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Dynamos. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-1
10-1
10-2
10-2
10-3
10-4
10-5
10-5
10-7
10-8
Chapter 11: Trending and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Historical Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Real-time Trending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Chapter 12: DeltaV Operate for RS3 Operator Station Journal Viewer. . . 12-1
Starting the Journal Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Operator Station Journal (*.mdb) Schema Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Alarms for RS3 Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Chapter 13: RS3 ABC Batch Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Starting RS3 Batch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Displaying Batch Information on Process Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13-2
13-2
13-3
13-4
Chapter 14: RS3 ABC Batch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Filtering ABC Batch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Detail View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting ABM Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABC Batch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents-4
14-1
14-2
14-3
14-3
14-5
Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Appendix A: ControlBlock and I/O Block Attributes . . . . . . . . . . . . . . . . . . A-1
Supported ControlBlocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ControlBlock Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Supported I/O Blocks and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
System and User Flag Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Testing I/O Block Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Testing ControlBlock Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
Accessing System and User Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Using Aspects in Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
Appendix B: System Planning and Hardware Installation . . . . . . . . . . . . . . B-1
Planning an RS3 Process Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Appendix C: RS3 System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Upgrading Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Installation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Backing up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Complete RS3 System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Configuration Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Saving Registry Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Journal Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Trend Data Files Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Report Configuration and Data Files Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Backup Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Backup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Installing Other Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Changing the Computer Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Contents-5
Contents-6
Chapter 1
Introduction
The DeltaV Operate for RS3™ Operator Station is the combination of DeltaV and
RS3 hardware and software that allows an operator to control both DeltaV and RS3
systems from a single DeltaV Operator Station.
The RS3 components of the software have evolved from RS3 Operator Station
software.
The following schematic figure shows one way the DeltaV Operate for RS3
system can be implemented in a plant.
DeltaV
Operate
for RS3
Configuration/
Operator
Station
DeltaV
Operate
for RS3
Operator
Station
PC with third
party
application
software
DeltaV
Operator
Station
DeltaV
ProfessionalPLUS
Station
Ethernet
RS3 Process LAN
DeltaV Control Network
Hub
Hub
Hub
DeltaV
Controller
RS3
Network
Interface
RS3
Network
Interface
Switch
PeerWay
Router
Multi-tube
Command
Console
Control
File
Plant Network
I/O
Figure 1-1 Schematic of DeltaV Operate for RS3 System
Introduction
1-1
DeltaV Operate for RS3 Overview
As the schematic figure shows, DeltaV Operate for RS3 Operator Stations
integrate the operation of RS3 and DeltaV systems at the operator station. The two
control networks remain separate. Data does not move between the systems. For
example, you cannot add an RS3 value to the DeltaV Data Historian or view
DeltaV parameters in the RS3 trend viewer.
Conceptually, a DeltaV Operate for RS3 Operator Station combines the functions
of both a standard DeltaV Operator Station controlling a DeltaV network and an
RS3 Operator Station controlling an RS3 system in one PC workstation.
The DeltaV Operate for RS3 update adds RS3 Operator Station functionality to
your DeltaV Operator Stations so that you can include links to data from RS3
controllers and links to data from DeltaV controllers on the same display.
DeltaV Operate for RS3 software also installs several RS3 Operator Station
applications on the DeltaV Operator Stations that let you view and manipulate
information in your RS3 system as if you were working from an RS3 Operator
Station.
Experienced DeltaV users will see no difference when operating a DeltaV control
system. Experienced RS3 Operator Station users operating an RS3 control system
will see the advanced graphics capabilities provided by DeltaV Operate. DeltaV
Operate for RS3 software does not support the graphics used in the RS3 Operator
Station, but the DeltaV Operate software includes utilities to help you convert the
pictures. Operators should notice no difference when using the other RS3 Operator
Station applications.
The DeltaV Operate for RS3 Operator Station desktop, with the DeltaV alarm
banner on the left screen and the DeltaV Operate for RS3 alarm banner on the right
screen is shown below.
1-2
Introduction
Figure 1-2 Typical DeltaV Operate for RS3 Operator Station
The DeltaV Operate for RS3 software includes many of the same applications for
plant operation as an RS3 console (MTCC or System Manager Station). However,
the configuration and operation of these applications have been redesigned to take
advantage of the Windows operating system environment.
The DeltaV Operate for RS3 Operator Station has three user modes:

Note
Introduction
Configuration — In this mode, the configuror designs and specifies graphics,
trending, reporting, and alarms. After the configuration is completed, the
configuror selects specific configurations for use by each station on the
process network.
An MTCC or SMS is required for control file and PeerWay
configuration.

Operation — In this mode, an operator executes plant operations from a
DeltaV Operate screen, using configurations, tools, and graphics designed by
the configuror.

Administration — In this mode, an administrator uses database maintenance
utilities such as compression, copy, move, and database size. Refer to the
online help for database maintenance specifics. Administration
responsibilities also include backing up critical data, such as the event journal
and historical trend data. See Appendix C.
1-3
Each of these modes is available at any time on the operator station, dependent on
appropriate login privileges.
Refer to subsequent sections and appendixes of this manual for a more detailed
overview of these applications. Refer to the online documentation for specific
procedures and detailed information.
Station Types
The DeltaV Operate for RS3 Operator Station is available in the following station
types. Note that these types apply to RS3 tags and blocks only and not to DeltaV
tags and modules.
Configuration/
Operator
Full DeltaV Operate for RS3 Operator Station functionality,
including Operator Station and RNI configuration, trend collection, database management, and Batch capabilities.
Operator
Operation functionality, including DeltaV Operate, Batch,
and Alarm applications—but without Operator Station and
RNI configuration, and database management. Requires a
Configuration/Operator station. Up to 2 Operator Stations
per Configuration/Operator station.
The software consists of the DeltaV Operate for RS3 software operating on the
Microsoft Windows XP Professional platform. The hardware consists of a
computer (with 512 Mbyte of memory, additional network connection for the RNI,
and required dual-monitor capability), keyboard, mouse, monitors, speakers, and
RNI; and optionally, a printer.
Licensing
DeltaV Operate for RS3 Operator Stations are licensed by RS3 tag count and
whether it is a Configuration workstation or Operate workstation.
There are five tag count levels:

250-tag limit

500-tag limit

1000-tag limit

2500-tag limit

Unlimited tags
License level is set by a license media during installation.
1-4
Introduction
The Batch option is included in all licenses.
In addition the following DeltaV licensing requirements must be met:

The ProfessionalPLUS station requires a 25 DST license - minimum.
Additional DST licenses may be required depending upon the number of
DeltaV controller DSTs.
Each DeltaV Operate for RS3 station requires a 100 DST Operator license minimum. Additional DST licenses may be required depending upon the
number of DeltaV controller DSTs.
Architecture
The DeltaV Operate for RS3 Operator Station connects to the RS3 PeerWay
system through the RS3 Network Interface (RNI™) gateway. Data from the RS3
PeerWay is stored in a data cache that is accessed by application programs running
on the operator station.
Each DeltaV Operate for RS3 Operator Station Configuration and Operator station
has its own local data cache that is available for use by its user applications.
Installation Overview
DeltaV Operate for RS3 Operator Station software installation instructions are
included on the CD ROM, and are provided in printed form in this manual.
Workstations are delivered with the Windows XP operating system installed. Some
items must be modified to make the workstation function properly in your
environment.
Caution
You must install the console software and supporting software in a
particular order to ensure that the software works properly.
You must install software in the following order:
1. Access Runtime Libraries 2002 located on DeltaV Operate for RS3 CD.
2. Other application software.
3. DeltaV Operate software.
Introduction
1-5
4. DeltaV Operate for RS3 software.
After you install the Access Runtime Libraries, other application software, and
DeltaV software, installation and management of DeltaV Operate for RS3
software consists of these phases:

Planning and hardware installation, covered in Appendix B and the DeltaV
documentation.

System administration, covered in Appendix C.

DeltaV Operate for RS3 Operator Station software configuration, covered
throughout this manual.
The DeltaV Operate for RS3 Operator Station system administrator will:

Install Access Runtime Libraries 2000

Install Microsoft Excel (optional for reporting).

Install DeltaV software

Install DeltaV Operate for RS3 software.

Change the passwords on DeltaV Operate for RS3 Operator Station user
accounts.

Establish a user account for each user.

Assign Plant Units to Group Accounts.

Establish new Group Accounts if needed.
The Windows system administrator will:

Change the passwords on Windows user accounts.

Enter network data for the workstation (if connected to plant network).

Enter network data for the associated RNI device (if connected to plant
network).

Install printer software (optional).

Install Uninterruptible Power Supply (UPS) software on workstations so
equipped.
About This Manual
This Getting Started manual provides information on the DeltaV Operate for RS3
Operator Station. The primary source of information on any specific application is
available online.
1-6
Introduction
This manual is intended for many different readers. RS3 operators, RS3
configurors, system administrators, installation/maintenance technicians, and
system designers require different information. The manual is organized to address
these different needs.
Section 1 is an overview of DeltaV Operate for RS3 systems. It includes a
discussion of what the system includes and how the DeltaV and RS3 portions
interact. The section mentions licensing, RS3 system architecture, and includes an
installation overview. This section also explains the contents of this manual and
other related documentation.
Section 2 explains the PC configuration required for a successful installation or
upgrade.
Section 3 contains instructions for installing the DeltaV Operate for RS3 software.
Information on configuring the RNI is included.
Section 4 contains information on uninstalling and re-installing the DeltaV
Operate for RS3 software.
Section 5 contains information on setting up software components for use.
Section 6 is an overview of configuration tasks for DeltaV Operate for RS3
software. Control configuration, alarm messaging, historical trending, reporting,
security, and journal viewing are introduced.
Section 7 is an overview of the DeltaV Operate for RS3 environment, as well as
operational basics such as logging in and out and navigating the desktop. All users
should read these sections.
Section 8 provides information on the online documentation. Because the primary
source of information on any DeltaV Operate for RS3 application is available
online, all users should read this section.
Section 9 provides information on configuration applications.
Section 10 provides RS3-specific information required to create graphics displays.
(Refer to DeltaV documentation for general information.) The information in this
section includes how to reference RS3 data from displays and operator toolbar
buttons used in the RS3 environment.
Section 11 provides information on configuration and use of the reporting and
historical trending capabilities of DeltaV Operate for RS3 consoles for RS3 data.
Section 12 provides an overview of the Journal Viewer.
Section 13 provides an overview of the RS3 Batch application.
Introduction
1-7
Section 14 provides an overview of the ABC Batch Messages and the additional
functionality of the RS3 Journal Viewer.
Appendix A is a reference for RS3 attributes information.
Appendix B provides information on network planning and hardware installation.
Appendix C provides information on RS3-specific system administration.
The following table lists the sections and appendixes, and a matrix showing the
intended readers.
Table 1-1 Intended Readers by Section
Section/
Appx
Operators
Configurors
System
Admin
Technicians
System
Design
Section 1
X
X
X
X
X
Section 2
X
X
Section 3
X
X
Section 4
X
X
Section 5
X
X
Section 6
X
X
X
X
X
Section 7
X
X
X
X
X
Section 8
X
X
X
X
X
Section 9
X
X
X
Section 10
X
X
X
Section 11
X
X
X
Section 12
X
X
X
Section 13
X
X
X
Section 14
X
X
X
Appendix A
X
X
X
Appendix B
X
X
Appendix C
X
X
1-8
X
X
X
Introduction
Related Information
The following resources provide additional information on the DeltaV Operate for
RS3 Operator Station.
DeltaV Operate for RS3 Documentation

DeltaV Operate for RS3 Getting Started manual

DeltaV Operate for RS3 online help

DeltaV Operate for RS3 Operator Station online manuals:
•
•
•
•
Note
Getting Started with DeltaV Operate for RS3
Implementing Security on DeltaV Operate for RS3
Trending in DeltaV Operate for RS3
Using DDE in DeltaV Operate for RS3
The online manuals are accessible from the Online Manuals Help menu
selection in several RS3 applications and from the Start menu.
DeltaV Documentation
For general information on the following topics refer to the DeltaV books online:
•
•
•
•
Workstation and network hardware
Operator Graphics (creating and using)
Visual Basic
Tag Groups
Conventions Used in this Manual
Throughout this manual, the following conventions are used:

The characters < and > and italic typeface in statements such as:
type: <drive letter>\i386\WIN32.EXE /u
define a variable, such as drive letter or computer name.
When you see this variable designation method in this document, type the actual
letter of the drive (for example: D:), or type the actual name of the computer (for
example: OPSTAT1).
Introduction
1-9

The pipe character (|) in statements such as:
select File | Run
separates the menu and the command strings.
In this example, under the File menu, execute the Run option.
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:
1-10
Warning
All warnings have this form. 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. 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. 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.
Introduction
Chapter 2
PC Configuration Requirements
PC Hardware
The hardware requirements for DeltaV Operate for RS3 PCs are the same as for
DeltaV Operate PCs, except that DeltaV Operate for RS3 PCs require three
network interface connections (NIC) and dual monitors. Refer to the DeltaV
Release Notes KBA for more information.
PC Naming
In DeltaV Operate for RS3 PC names must be eight or fewer characters, start with
a letter, and can contain only letters, numbers, and underscores (_). The DeltaV
Operate for RS3 installation process checks this and will not install the software on
a PC if its name does not meet these requirements.
Caution
You cannot rename a PC after you install DeltaV Operate for RS3 software.
Attempting to do so may corrupt Windows software requiring that you reinstall the operating system.
If you must rename a PC refer to Appendix C for an overview of the tasks required.
2-1
2-2
Chapter 3
Installing DeltaV Operate for RS3 Software
Use this section as a guide when installing the DeltaV Operate for RS3 software.
The computer you are installing the DeltaV Operate for RS3 software on must
already have DeltaV software with the Operator license installed and working
properly. You cannot install DeltaV Operate for RS3 software on a
ProfessionalPLUS workstation.
Caution
You must install the software in the order specified in the Installation
Overview to ensure that the software works properly.
Installation Overview
For DeltaV Operate for RS3 software to function properly it is important that you
install software in a certain order. Starting with a PC that has only the Windows XP
Professional operating system installed, install software in the following order:
1. Install Microsoft Access 2002 Runtime Libraries.
2. Install other application software. Refer to the DeltaV Compatibility Chart in
DeltaV Books Online for supported software.
3. Install DeltaV software.
4. Install DeltaV Operate for RS3 software.
The following subsections explain these steps in detail or refers to other
information as appropriate.
Install Microsoft Access 2002 Runtime Libraries
Note
The Microsoft Access 2002 Runtime Libraries must be installed on the
C: drive.
1. Navigate to the \AccessRT2002 directory on the DeltaV Operate for RS3
installation CD and double click Accessrt.msi.
2. Click Install on the dialog that appears.
3-1
3. Click OK in the dialog that appears saying that Microsoft Access 2002
Runtime setup installed successfully.
Install Other Application Software
If you need to install other application software, refer to the documentation of the
application software for installation instructions. For example, if you are going to
use DeltaV Operate for RS3 Reporting, you will need to install Microsoft Excel.
Note
If you install Microsoft Office components (Word, Excel, and Access),
they must be installed on the C: drive.
Install DeltaV Software
Refer to the DeltaV documentation for instructions on installing DeltaV software.
Install DeltaV Operate for RS3 Software
Before You Install
There are a few conditions that you must verify before you begin installing DeltaV
Operate for RS3 software:
1. The PC’s name must be eight or fewer characters, start with a letter, and can
contain only letters, numbers, and underscores (_). The DeltaV Operate for
RS3 installation process checks this and will not install the software on a PC if
its name does not meet these requirements.
2. Select Start | Settings | Control Panel.
3. Double click Network Connections.
4. In the Network Connections application select Advanced | Advanced Settings
from the main menu.
5. In the Connections field of the Advanced Settings dialog, if necessary use the
up and down arrow buttons to set the binding order for the network adapters
to the following:
• DeltaV Secondary
• Ethernet to RNI (Plant LAN)
• DeltaV Primary
3-2
6. Click OK in the Advanced Settings dialog to accept any changes and close the
dialog.
7. Close the Network Connections dialog.
8. If the PC is in a Domain, make sure the C drive has the security of the
Everyone group set to (Modify, Read & Execute, List Folder Contents, Read,
Write).
9. If the PC is in a Workgroup, make sure the Local Security Policy Network
access: Sharing and security model for local accounts is set to Classic - local
users authenticate as themselves and then make sure the C drive has the
security of the Everyone group set to (Modify, Read & Execute, List Folder
Contents, Read, Write).
10. Verify that DeltaV software is operating correctly.
This section includes information on the following:

Running the DeltaV Operate for RS3 installation Setup program

Creating an initial operator station configuration

Configuring the RNI™ device

Configuring the RS3 environment
The DeltaV Operate for RS3 Installation shield automatically tailors the
installation process according to your particular install scenario, and in response to
the selections you make in the dialog boxes that guide you through the installation.
Caution
You cannot install DeltaV Operate for RS3 software and Asset Management
Systems (AMS) software on the same machine.
Note
During installation popups may appear saying that a read-only file was
found while attempting to copy files. Answer Yes at these prompts to
overwrite the read only files. Optionally, you can select the checkbox on
the popup to avoid seeing further messages.
3-3
To install DeltaV Operate for RS3 software:
1. Place the DeltaV Operate for RS3 Installation CD in the CD drive.
2. Log in to Windows XP as Administrator.
3. Run Windows Explorer.
4. Select the CD ROM drive.
5. Navigate to the \DISK1 directory on the installation CD and double-click
Setup.exe.
The welcome dialog appears.
6. Click the Next button.
An information popup appears.
3-4
7. Read the popup text and click OK to continue.
The DeltaV Operate for RS3: DeltaV Operate Picture Datalink Conversion
information popup appears.
8. Read the popup text and click OK to continue.
The Software License Confirmation window appears.
9. In the window, read the License Agreement, and click Yes to accept.
The license dialog appears.
10. Insert the license media in the appropriate drive and click OK.
The Setup Type dialog appears.
3-5
11. In the dialog select the type of workstation you are installing the software on,
Configuration/Operator Station or Operator Station, then click Next.
The Select Installation Options dialog appears.
The options that appear depend on whether you are installing a Configuration/
Operator Station or Operator Station.
Emerson Process Management recommends that you accept the default
settings.
12. Click the Next button to continue.
The Start Copying Files dialog appears to show the current setting in a
scrollable window.
3-6
13. Click the Next button to begin copying files to the PC’s hard drive.
At this point the Adobe Acrobat Reader setup dialog appears if it is not already
installed. If it is already installed, skip to step 17.
14. Click Next to begin installing Acrobat Reader.
15. Click Next to accept the default installation directory.
After the reader installs, an acknowledgement dialog appears.
16. Click OK to close the acknowledgment dialog.
17. The copy files dialog appears and installation continues. As files are copied, a
% progress popup appears.
If you are installing on an Operator Station, skip to the section RS3
Environment Configuration.
Operator Station Configuration
If you are installing on a Configuration/Operator Station the Console
Configuration application starts at this time.
3-7
Note
Console configuration is not required and the Console Configuration
application does not start if you are installing the software on DeltaV
Operate for RS3 Operator Stations.
Perform the following steps:
1. Select File | Open Current Configuration from the main menu.
2. In the RNI Host field, fill in the name of the RNI device that this DeltaV
Operate for RS3 Configuration/Operator Workstation will use to
communicate to the PeerWay.
3. Click the Save Current button. You may need to expand the dialog to see the
Save Current button.
3-8
4. Select File | Exit from the main menu.
The RNI Configuration Utility appears.
For more information on the Console Configuration application, refer to Section 9.
RNI Configuration
Running the RNI Configuration Utility
If the Bootup the RNI check box was selected in the Select Installation Options
dialog, the RNI Configuration Utility appears as shown in the figure.
The RNI Configuration Utility allows you to configure the Hosts file, the bootptab
file, and some of the necessary RNI configuration files. If you did not install RNI
Services during installation, you can access the RNI Configuration utility at any
time by selecting Start | DeltaV Operate for RS3 | Engineering | RNI Boot
Configuration.
3-9
Note
Fields in this window that are white need to have values entered. Fields
that are grey have values assigned and cannot be changed.
In the RNI Configuration Utility window:
1. In the Enter RNI Name to be configured field, enter the name of the RNI
device you want to configure.
• If you are updating an existing RNI device, enter the name or use the dropdown list to select a name. The Configuration Utility will fill in many of
the additional information fields in this window.
• If this is a new RNI device not previously on the network, enter the name.
The Configuration Utility will look for this name on the system and fill in
as much information as it can.
2. Press the Tab key to enable fields for writing and to move to the next field.
Note
Press the Tab key to move from field to field.
3. In the IP Address of RNI field, enter the IP address of the RNI device, if the
correct number is not already filled in. You should obtain this address from
your system administrator. The IP address must be on the same subnet as the
host PC.
4. In the PeerWay Node Number field, enter a value between 1 and 992, which
you have obtained from your RS3 system administrator.
5. Check the Enable Error Logging to RNI serial port box if you want the RNI
device to write all of its error messages to the RNI device’s serial port in
addition to the Error Log server. (The default is unchecked.)
Note
The next five fields (steps 6 through 10) are in the Bootptab Information
group, and apply only to bootptab.
6. In the Gateway IP Address field, accept the default obtained from the PC you
are working from), or enter all zeros if you do not want a gateway.
7. Tab past the Subnet Mask field, which is provided for information only; you
cannot change the values in this field.
8. In the RNI Boot File Name field accept the default shown if you have not
changed the default location. If you have changed the default location, enter
the full path name including drive letter, path, and file name where you
installed RNI device.
You will get an error message if you provide a file name that does not exist.
3-10
9. In the MAC Address of RNI (Hex) field, enter the MAC address shown on the
back of the RNI device.
This field is required, and you will get an error message if you do not enter 12
hexadecimal digits.
10. In the Name of Primary Configuration Workstation field, you can accept the
default (normally the same as the PC the Configuration Utility is being run
on) or select a different workstation from the drop-down box.
11. Click the Advanced button, if you want to change the name of the secondary
Configuration Server or the port number of the primary Configuration Server.
(Normally, you will not need to use this button.)
12. Click OK when you have reviewed and approved the settings, to apply the
information and close the window. Or, click Apply if you want to keep this
window open to configure additional RNI devices (when booting multiple
RNI devices, for example).
Note
The two fields in the Host PC Information group are provided for
informational purposes only. FRS Support Services may request this
information for troubleshooting a problem situation.
RS3 Environment Configuration
At this point the RS3 Environment Configuration utility dialog appears.
3-11
1. In the dialog box, you enable or disable various installation options on the four
tabs as required.
General Setup Tab
Enable RS3 tags Log Default: enabled. Sets whether or not the DeltaV Operate for RS3 Operator
Station keeps a list of the RS3 tags that are accessed while the operator station
is running. This list is a text file (BlockTags.txt) held on disk. Normally an
operator station does not access the data for an RS3 tag until that tag is
referenced on a picture and that picture is loaded onto the view screen. The list
is used on system startup to quickly provide the data for those previously
defined tags. Picture load time can be significantly reduced.
Update RS3 tags LogDefault: enabled: Write any changes to RS3 tags on shutdown. This box is
dimmed if the Enable box is not checked.
Enable Translation This selection is not applicable and is dimmed.
3-12
Peerway is on Daylight Saving Time Default: disabled. Enable only if PeerWay has been set to local daylight
savings time.
Connection Setup Tab
If this is a Configuration/Operator workstation, these fields are dimmed and
you cannot change them. If this is an Operator workstation, fill in the name and
IP address of the Configuration Server and the RNI it boots.
RS3 Tag Data Rate Control Tab
You can select the defaults, or enter other values if required for your situation.
Security Setup Tab
Enter the primary and secondary password server node number. This tells the
operator station which RS3 nodes have the $$PASSWD file.
Note
The RS3 Environment Configuration utility cannot be run when you are
logged into any other account except Administrator. An error may occur
if you try to run the RS3 Environment Configuration utility while logged
in as something other than Administrator.
2. Click OK to verify the settings and close the dialog.
Setup Complete
The installation process configures the program groups for the DeltaV Operate for
RS3 applications. When the installation is complete, the following dialog box
appears.
3-13
1. Remove any disks from their respective drives.
2. Make sure the Restart the machine option is selected.
3. Click the Finish button. The PC restarts.
4. If you are installing the software on the Configuration/Operator station, make
sure that the RNI device is connected to the PeerWay and Ethernet and
powered up, then press the reset button to restart the RNI device.
Note
3-14
After installation is complete and your system restarts, you must
complete the tasks in Section 5 to ensure that the software is set up
properly before you can use your DeltaV Operate for RS3 software.
Chapter 4
Re-Installing the Software
Use this section as a guide if you need to uninstall and re-install the same version
of the DeltaV Operate for RS3 software.
Uninstalling the DeltaV Operate for RS3 Software
Use the following steps to uninstall the DeltaV Operate for RS3 software.
1. Save existing data (if you are going to re-install).
2. Save Registry information (if you are going to re-install).
3. Uninstall the DeltaV Operate for RS3 software.
Saving Existing Data
There are two broad types of data to consider preserving. The first type includes
pictures, trend data and configuration, environment settings, RNI configuration,
and so on. The best way to preserve this data is to copy the entire FRSI directory to
a location out of the \FRSI path and rename the copied directory FRSIOLD.
Saving the Security Configuration
In addition, you must save the security settings by exporting your security.rpt file.
Follow these steps:
1. Run the System Configuration Utility (SCU) by selecting Start | DeltaV |
Installation | DeltaV Operator System Configuration Utility.
2. Click the Security Configuration padlock icon on the toolbar in SCU.
3. Select File | Export...
4. Rename the security.rpt file, and specify a location to save the file. The file
name must be eight characters or less. Use a location that will not be affected
when uninstalling or re-installing the software.
4-1
Note
After you reinstall DeltaV Operate for RS3 software, run the Security
Configuration application and import the renamed security.rpt file.
Exported security configuration files do not include user account
passwords in order to protect them. When you import an exported
configuration file, the Security Configuration program creates user
accounts without passwords.
Saving the Console Configuration
The second type of data to consider preserving is the online database: the settings
that you make in the Console Configuration utility. To preserve these settings (this
can only be done on a DeltaV Operate for RS3 Configuration/Operator
Workstation, it is not available on DeltaV Operate for RS3 Operator Workstation)
do the following to backup the Database:
1. Run the Operator Station Configuration application by selecting Start | DeltaV
Operate for RS3 | Engineering | Operator Station Configuration.
2. Select File | Backup Database in the Console Configuration window.
The Choose File to Backup To dialog appears.
3. Specify a location that will not be affected by uninstalling or re-installing the
software.
After you re-install DeltaV Operate for RS3 software use the Restore Database
function.
Saving Registry Information
When saving console data you must also save the registry information about the
console configuration:
1. Log in to Windows as Administrator.
2. Run Regedit.
3. Select HKEY_LOCAL_MACHINE\SOFTWARE\Fisher-Rosemount
Systems.
5. Specify a location and file name to save the registry information, for example:
Fisher-Rosemount Systems.reg.
4-2
Systems\NetConnect\n.nn.nnn\ROS\RS3Glue\DB\PlantUnits.
PlantUnits.reg.
Uninstalling the Software
Over the life of your consoles you may need to uninstall the software. To
successfully uninstall the DeltaV Operate for RS3 software you must perform
tasks in a specific order. The tasks are:
1. Back up any pictures you have created or modified.
2. Restore the UserSettings.grf file (comment out the changes made).
3. Delete the file \DVData\Graphics-iFix\Pic\SecondSystemFilesCopied.RS3.
4. On the DeltaV User Settings dialog uncheck RS3 and Click OK to save the
changes to frsVariables.fxg.
5. Restore DeltaV Operator System Configuration Utility settings:
• Select No Network Support in Network Configuration
• Remove FixReady.exe from the Task list
• Disable User Based Security in the Security Configuration dialog.
6. Uninstall the following programs from Add/Remove Programs:
• DeltaV Operate for RS3, then restart the computer.
7. Clean up the computer’s hard disks:
• Delete the C:\FRSI folder.
8. Empty the Recycle bin.
Re-installing the DeltaV Operate for RS3 Software
Before you can re-install the software you must first uninstall it. Refer to the
previous section for information on uninstalling the software.
Refer to Section 3 for instructions on installing the DeltaV Operate for RS3
software. After you install the software you can restore the previous database and
security configuration.
4-3
Restore the Security Configuration
You must import the DeltaV Operate for RS3 security settings for the system to
function properly. To import the security settings:
2. Select Start | DeltaV | Installation | DeltaV Operator System Configuration
Utility.
The System Configuration Utility (SCU) opens.
3. Click the Security Configuration padlock icon on the toolbar in SCU.
4. Select File | Import...
5. Navigate to the location where you exported the security settings.
6. Select the security settings file (you renamed it when you exported it).
7. Click Open.
8. Click YES when prompted that imported user accounts may not have
passwords.
9. Click REPLACE to replace the existing default security configuration with
the settings you exported previously.
Restore the Registry
Now you need to restore the console configuration registry information you saved
previously. You must be logged in as Administrator:
1. Run Regedit.
2. Select File | Import...
3. Navigate to and select the file you saved previously. For example,
PlantUnits.reg.
4. Click Open to import the information.
5. Click OK to acknowledge the information was successfully imported.
4-4
Restore the Configuration Database
1. Run the Operator Station Configuration application by selecting Start | DeltaV
Operate for RS3 | Engineering | Operator Station Configuration.
2. Select File | Restore Database in the Console Configuration window.
3. Navigate to and select the file you saved previously.
4. Click the Open button.
The following message appears:
This will restore the selected database over your current database select OK to
continue.
5. Click the OK button.
Wait until the following message appears:
Database has been restored. Please open a general configuration and save it as
current.
6. Click the OK button.
The Offline Configurations window appears.
7. Select Default from the list box and click the Open button.
8. Click the Save Current button.
9. Select File | Exit to close the window.
Note
After re-installation is complete, work through the tasks in Section 5 to
ensure that the software is set up properly before you use your DeltaV
Operate for RS3 software.
4-5
4-6
Chapter 5
Software Setup
After you have completed the software installation described in Section 3, you
must complete the tasks in this section to insure that the DeltaV Operate for RS3
software functions properly. The tasks included are:

Set up the console system and security

Set up Excel reporting

Test the RNI device connection

Enable RS3 software components

Create an RS3 toolbar

Create Settings and Layout files
System and Security Setup
The first time you start DeltaV Operate for RS3, you must perform the following
procedures to set up the security system. The instructions in this section are the
minimum required to allow users to start and navigate in the software and do not
create a secure system. For complete information on defining and implementing
security, refer to the manual Implementing Security on DeltaV Operate for RS3.
Note
Because you have not configured security yet, logins are disabled. You
must configure security before you continue.
Utility.
3. Select Configure | Network...
The Network Configuration dialog appears.
Software Setup
5-1
4. Select the following items in the dialog:
• TCP/IP
• Dynamic Connections
• Show All Names
5. Click OK to close the Network Configuration dialog.
6. Select Configure | Alarms... from the SCU dialog.
The Alarm Configuration dialog appears
7. In the dialog, enable Alarm Summary Service and Alarm History Service.
Disable all other choices.
8. Click OK to accept your changes and close the dialog.
5-2
Software Setup
9. Select Configure | Tasks....
The Task Configuration dialog appears.
10. Click the ? button and browse to \FRSI\NetConnect\Bin\ and double click on
FixReady.exe.
11. Select Background.
12. Click the Add button.
13. Click OK to close the dialog.
14. Select Configure | Security....
The Security Configuration application opens on top of the System
Configuration Utility.
15. Select File | Import....
Note
You cannot import the security file from an RS3 Operator Station (ROS).
ROS security files are not compatible with DeltaV Operate for RS3
security files.
16. Click on security.rpt and click Open to import the default security file.
A popup asks: Warning: imported user accounts may not have passwords!
Continue?
17. Click YES to continue.
A popup asks: Replace or add to existing configuration?
18. Click REPLACE to continue.
19. Select Edit | AutoLogin....
The Automatic Login at Startup dialog appears.
The Automatic Login Node dialog appears.
21. Enter this computer’s node name in the Node field.
Software Setup
5-3
22. In the Application User field, enter the user name GUEST to have that
account logged in when the computer restarts.
An RS3 user must be logged in for users to have access to DeltaV Operate
functionality.
Note
When a privileged RS3 user logs out he must login in as another user
with restricted privileges, such as the default user GUEST. An RS3 user
must be logged in for users to have access to DeltaV Operate
functionality.
23. Click OK to close the Automatic Login Node dialog.
24. In the Automatic Login at Startup dialog, delete RS3OPS. Leave the node
name of this computer in the list of Autostarted Nodes.
25. Click OK to close the Automatic Login at Startup dialog.
26. From the Security Configuration dialog, select File | Save.
27. Select File | Exit to close the Security Configuration dialog.
28. From the SCU dialog, select Configure | Local Startup...
The Local Startup Definition dialog appears.
29. Enter this computer’s node name in the Local Node Name field.
30. Leave THISNODE in the Local Logical Name field.
5-4
Software Setup
31. Select Local Node Alias, Continue running after Logoff, and Start FIX at
system boot.
32. Click OK to close the Local Startup Definition dialog.
Note
If the SCU message Invalid node name entered appears, click OK to
acknowledge the message, then click OK on the Local Startup Definition
dialog. If the SCU message Invalid node name entered appears again,
cancel the Local Startup Definition dialog, exit SCU, restart SCU, and
reopen the Local Startup Definition dialog.
33. From the SCU dialog, select File | Save, then select File | Exit to close the
dialog.
Setting Up Users
How you set up users depends on whether you are in a Workgroup or a Domain. If
you are in a workgroup environment, follow the instructions in the section Setting
Up Users in a Workgroup Environment. If you are in a domain environment, skip
to the section Setting Up Users in a Domain Environment.
Setting Up Users in a Workgroup Environment
To set up users, on every DeltaV Operate for RS3 station 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 NetConnect21 group.
5. On the NetConnect21 Properties dialog, click the Add button.
6. On the Select Users dialog click the Advanced button.
A second Select Users 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 NetConnect21 group.
Software Setup
5-5
9. Click OK to accept your selections and close Select Users dialog on top.
10. Click OK to confirm your changes and close the Select Users dialog.
11. Click OK to close the NetConnect21 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 2003 domain controller and each individual DeltaV Operate for
RS3 station.
On the Windows Server 2003 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.
3. For each user you want to have access to the DeltaV Operate for RS3
functionality:
a. Open the user Properties dialog.
b. On the Member Of tab add the groups Domain DeltaV and Domain Users
if they are not already there.
c. Close the user Properties dialog.
4. Close the Active Directory Users and Computers application.
On each DeltaV Operate for RS3 Station:
To set up users:
1. Open the Computer Management application (select Start | Settings | Control
Panel | Administrative Tools | Computer Management).
5-6
Software Setup
2. Open the Local Users and Groups folder.
3. Open the Groups folder.
4. Double click on the NetConnect21 group.
If you want all domain users to have access to DeltaV Operate for RS3
software, proceed to the next step. If you want only specific users to have
access to DeltaV Operate for RS3 software, skip to step 8.
To Allow All Domain Users Access to DeltaV Operate for RS3 Software perform
the following steps:
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 RS3 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.
10. Click, Shift Click, and Ctrl Click to highlight all the users you want to add to
the NetConnect21 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 NetConnect21 Properties dialog.
14. Close the Computer Management window (select File | Exit).
15. Restart the computer.
Note
Software Setup
You must restart the computer to ensure that the DCOM servers are
restarted with the correct security settings.
5-7
Security Configuration
Now set up the security configuration.
1. After the computer has restarted, log in to Windows as Administrator.
Utility.
3. Select Configure | Security....
The Security Configuration application opens on top of the System
Configuration Utility.
4. Select Edit | Configuration...
The Configuration Dialog appears.
5. Make sure Enabled is selected for User Based Security.
6. Click OK to close the Configuration dialog.
7. From the Security Configuration dialog, select File | Save.
8. Select File | Exit to close the Security Configuration dialog.
9. From the SCU dialog, select File | Exit to close the dialog.
Excel Reporting
In order for RS3 Reporting to function correctly with Excel, you must copy the
startup.xla file (installed in \FRSI\RPTDATA) to the XLStart directory (typically,
\Program Files\Microsoft Office\Officenn\XLStart).
You must also ensure that the default directory where Excel looks for files for each
user account is set correctly. Do this by logging in to Windows under each account.
While logged in under each account start Excel. In Excel, select Options from the
Tools menu. On the General tab, change the Default file location: field to
C:\FRSI\RPTDATA and enter the user name of the currently logged in user in the
User name: field.
Excel Reporting also depends on some software services. For more information,
refer to the manual Using DDE in DeltaV Operate for RS3.
5-8
Software Setup
Testing the RNI Device Connection
This procedure will verify that the workstation and the associated RNI devices are
properly setup.
To verify the RNI device connection:
1. Check the RNI Configuration screen and the RNI Status screen from an SMS
or MTCC:
a. Type CRN [ENTER] to bring up the RNI Configuration screen.
b. Press [EXCHANGE] to bring up the RNI Status screen.
Enable RS3 Components
The console must be communicating with the RNI before you can enable the RS3
components in the DeltaV Operate interface.
To enable RS3 components do the following:
1. Start DeltaV Operate and go to Configure mode.
2. Open the DeltaV User Settings dialog by clicking the
Configure toolbar.
button on the
The DeltaV User Settings dialog opens.
Software Setup
5-9
3. Select the RS3 checkbox as shown to enable communication with the RS3
system, if it is not already selected.
For information on the other checkboxes, refer to the section Using the DeltaV
User Settings Dialog in the DeltaV Operator Graphics manual.
4. Click the Add files button.
5. Acknowledge the popup dialogs that appear.
6. Click OK to close the DeltaV User Settings dialog.
7. Close DeltaV Operate.
8. If the Workspace popup asking if you want to save changes to frsVariables
opens, click Yes.
9. Wait 30 seconds, then open DeltaV Operate to refresh the file list.
Note
The Add files button copies files to the DeltaV directory structure to
support RS3 pictures.
The Add files button copies a number of RS3-specific files to the DeltaV directory
structure. These files include dynamo sets, alarm banners, alarm summaries, and
toolbars that support RS3 systems. These files are visible in DeltaV Operate
(configure mode) so you can use them when you create pictures.
5-10
Software Setup
Creating RS3 Toolbars
The software includes two RS3 toolbars: RS3Toolbar and RS3Toolbar2. If these
do not meet your needs, you must create one or more RS3 toolbars for operators to
have access to RS3 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 RS3 system only or a combination of DeltaV and RS3
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 RS3 systems.
To create an RS3 toolbar:
1. Start DeltaV Operate and go to Configure mode.
2. Select 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 by clicking the
button on the toolbar.
The Toolbar Picture Builder dialog opens.
Software Setup
5-11
5. Select a toolbar template and 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 TBRS3Template1 toolbar template (the template for RS3 toolbars) 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.
There are several sets of buttons:
•
•
•
•
TBEDeltaVAllUI (Common Tools for any Toolbar)
TBEDeltaVTools (DeltaV Specific Tools)
TBETerminalSession (DeltaV Terminal Session)
TBEsys2RS3 (RS3 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.
5-12
Software Setup
7. Select the Common Tools for any Toolbar set.
You should probably include the following buttons on any toolbar you create
to ensure operators can open and manipulate pictures, open faceplates and
detail pictures, print displays, and reset the display, if necessary.
From the TBEDeltaVAllUI Toolbar set:
•
•
•
•
•
Print Main Window
Last Picture
Open Picture
Swap Main Displays
Reset DeltaV Operate
From the TBEDeltaVTools Toolbar set (if your system includes DeltaV
modules):
•
•
Open Module Faceplate
Open Module Detail
Include any other buttons your operators need from any of the tool sets.
After you have the common and DeltaV buttons on the toolbar, add the buttons
required from the RS3 Specific Tools button set (TBEsys2RS3, which is
selected in the figure).
Refer to Chapter 7 for information on the RS3 toolbar buttons available. Refer
to the DeltaV documentation for information on the other toolbar buttons.
8. Move buttons between your toolbar and the button set using the left and right
arrow buttons.
9. Set the order of the buttons on your toolbar by selecting a button and using the
up and down arrow buttons.
10. 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.
The picture \Pic\RS3\TBEsys2RS3.grf contains additional fields you may want to
use on your toolbar.
Refer to the following section for information on creating and editing settings and
layout files so the toolbar you created appears in DeltaV Operate.
Software Setup
5-13
Create Settings and Layout Files
DeltaV Operate for RS3 software includes settings and layout files you can use to
tailor the appearance of the software to your needs. You can define size and the
location of 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 RS3-specific tasks to create settings files and layout files.
For general information on setting up DeltaV Operate, refer to DeltaV Books
Online, in particular the topics Customizing the DeltaV Operate Environment and
Running DeltaV Operate on Multiple Monitors.
Note
DeltaV Operate for RS3 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:

User_Ref_RS3.grf (in \DeltaV\DVData\Graphics-iFix\Pic\Standard)

DeltaVPicture.Template (in \DeltaV\DVData\Graphics-iFix\Local)
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.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_RS3.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:
5-14

DeltaVPicture.Layout to create a layout file that applies to all operator stations

computername_Picture.Layout to create a layout file that applies to a the
specific operator station computername.
Software Setup
Note
The user settings 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.
The order in which the files are applied 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
To create a settings file:
1. If your DeltaV Operator Station already has a UserSettings.grf file, save it to
another name.
2. Open \Pictures\Standard\User_ref_RS3.grf.
3. Save the file in the Standard subdirectory as UserSettings.grf or
computername_Settings.grf.
4. Press 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.
Software Setup
5-15
Settings files are copied to an operator station's 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_RS3.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 more
complex sections of the file are explained in more detail below.
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 RS3 and
DeltaV software.
In the DeltaV-only workstation settings part define the toolbar and toolbar help
pictures that appear on operator stations that do not have DeltaV Operate for RS3
software installed. The RS3/DeltaV workstation settings section applies to
operator stations that have DeltaV Operate for RS3 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 RS3 software
installed.
Also in this section, the RS3 horn default is set to sound at DeltaV priority level 5.
If you want the RS3 horn to sound at a different DeltaV priority level, uncomment
the line containing gn_sys2RS3HornTone.CurrentValue and change 5 to the
desired value.
5-16
Software Setup
Note
For this setting to take effect, you must define an Alarm Priority in the
DeltaV Explorer Setup Data that matches this setting, then download
the Setup Data to the DeltaV ProfessionalPlus workstation.
Restoring Changes from a Previous Settings File
If you have a previous UserSettings.grf file it may contain some custom settings
you want to preserve. Do not copy the previous UserSettings.grf file over the new
file.
Open or print the previous version of the UserSettings.grf file. Compare the
contents of that file with the settings 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.
Other Settings File Variables
The settings files contain comments that explain how to modify the variables to
accomplish changes. Follow the instructions in the file. For example, using the
variables in the settings file you can do the following:
Software Setup

Set whether DeltaV Operate uses the standard alarm 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 the initial display.

Set the overview display.

Initialize the display history list.

Prevent changes to the display history list.

Initialize the module history list.

Prevent changes to the module history list.

Set the picture that is opened by the display directory toolbar button.
5-17
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.
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.
5-18
Software Setup
Chapter 6
Configuration Overview
The DeltaV Operate for RS3 Operator Station configuration can be subdivided into
functional areas: control configuration, process graphics, alarms, trending,
reporting, security, and Journal Viewer. All areas can be accessed through DeltaV
Operate, the interface from which operators control the process, view graphics,
and acknowledge alarms. The following pages list the applications you can use to
configure control operations, and provide an overview of process graphics, alarm
messaging, historical trending, reporting, security, and Journal Viewer.
Refer to subsequent sections of this manual for a more detailed overview of these
applications. Refer to the online documentation for specific procedures and
detailed information
Control Configuration
Process Graphics
Alarm Messaging
Configuration
Historical Trending
Reporting
Security
Journal Viewer
Console Configuration
The DeltaV Operate for RS3™ Configuration/Operator Station provides tools for
the control engineer or supervisor to set up basic operating parameters, alarm list
sizes, and node and plant unit information. Most of these tools are implemented in
a utility called the Console Configuration utility. Access this utility from a
Configuration/Operator station by selecting Start | DeltaV Operate for RS3 |
Operator Station Configuration.
6-1
The Configuration utility includes the following tabs:

General Configuration — Lets you select existing configuration files for node
ownership, plant unit ownership, alarm broadcast and alarm acknowledge
areas, message pairs, RNI™ name, and some alarm configuration. See Chapter
9 for more information.

Plant Unit Configuration — Assigns names and graphics to plant units.
Although you can maintain and save several configuration files, you can have
only one selected at any time in the DeltaV Operate for RS3 Operator Station
configuration.

Node Ownership — Allows the DeltaV Operate for RS3 Operator Station to
receive alarms from ControlBlocks on a node ownership basis when the blocks
have a plant unit of zero.

Plant Unit Ownership — Defines plant units from which the DeltaV Operate
for RS3 Operator Station can receive alarms.

Message Pairs — Define messages that you can use to represent discrete block
states on a faceplate or other graphic displays. For example: ON / OFF,
START / STOP, HIGH / LOW, etc.

Configure Alarm Acknowledge (CAA) — Controls which RS3 nodes can
receive alarm acknowledgments from the DeltaV Operate for RS3 Operator
Station. CAA is configured by selecting the RS3 nodes associated with the
consoles from which you want to generate acknowledgments of alarms.

Configure Alarm Broadcast (CAB) — Controls which RS3 nodes receive
alarms from the DeltaV Operate for RS3 Operator Station. CAB can help limit
the amount of message traffic to specific nodes on the PeerWay.
RS3 Environment Configuration
The RS3 Environment Configuration utility has its own Start menu selection. Use
the utility to set up variables for the DeltaV Operate for RS3 Operator Station.
Process Graphics
Refer to the DeltaV Operate documentation for general information on creating
process graphics. For RS3-specific information refer to Chapter 10 of this manual.
6-2
Alarm Messaging
Alarm Messaging consists of tools that manage alarms generated by the RS3,
including alarm types, alarm display, alarm acknowledgment, alarm storage, and
alarm animation:

Alarm List Setup
Determines alarm list size, determines user lists, and sets the update rate of the
list. To access, click the Alarm List button on the toolbar, and then click the
SETUP button.

Configure Alarm Acknowledge (CAA)
Controls which RS3 nodes can receive alarm acknowledgments from the
DeltaV Operate for RS3 Operator Station. CAA is configured by selecting the
RS3 nodes associated with the consoles from which you want to generate
acknowledgments of alarms. To access, click the Configure Alarm
Acknowledge tab on the Console Configuration application.

Configure Alarm Broadcast (CAB)
Controls which RS3 nodes receive alarms from the DeltaV Operate for RS3
Operator Station. CAB can help limit the amount of message traffic to specific
nodes on the PeerWay. To access, click the Configure Alarm Broadcast tab on
the Console Configuration application.

Journal Configuration
Lets you set the journal file name, directory, and file size. You can also set the
journal file size warning alarm limit and enable and disable journal data
collection. To access, select Journal Configure from the Start menu.

Journal Viewer
Lets you view operator changes, alarms and events generated by devices on
the PeerWay, and DeltaV Operate for RS3 Operator Station and RNI events.
To access, click the Journal Viewer button on the toolbar.
Note
See Chapter 7 for pictures and descriptions of the buttons that are
displayed on the desktop.
6-3
Historical Trending
Historical trending is used to store process data so that it can be accessed and
analyzed. The DeltaV Operate for RS3 Operator Station provides some special
tools for configuring trending:

Historical Assign
Use Historical Assign to create trending groups and define nodes, collection
rates, tagnames, and other parameters for each trending group. To access, click
the Historical Assign button on the toolbar or select Historical Assign from the
Start menu.

Historical Collect
Use Historical Collect to turn on data collection. When you start Historical
Collect, the program retrieves data from the blocks assigned to the trend
groups defined in Historical Assign. To access, select Mission Control from
the Start menu, or the toolbar, then select the HTC tab.

Historical Display
DeltaV Operate for RS3 includes the RS3 Trend Display (accessed from a
toolbar button or by opening the RS3Chart picture). Use the RS3 Trend
Display to create and manage a collection of trend displays. You can also
create your own pictures that include charts.
Note
See Chapter 7 for pictures and descriptions of the buttons that are
displayed on the desktop.
Historical trending is covered in Chapter 11 and in the online documentation.
Reporting
Reporting is used to link process information to the screen or to a printout. The
DeltaV Operate for RS3 Operator Station uses Dynamic Data Exchange (DDE) to
transfer data to Excel. Excel is the DDE-compliant application most commonly
used as the display application for reports.
Reporting is covered in Chapter 11 and in the online documentation.
Security
A user account is configured for each DeltaV Operate for RS3 Operator Station
user. The user account determines what group privileges, plant units, and
6-4
application features are available to a user. The system administrator defines user
accounts.
Each user account is a member of a user group. The user can access all the
application features and plant units defined for the user group.
Security is covered in Appendix C.
Journal Viewer
The Journal Viewer is a Microsoft Access-based user interface that allows you to
view, sort, filter, and print alarms and events in your process. Journal files, whose
sizes and locations are configurable, are set up in the Journal Configuration. To
access Journal Configuration, select Journal Configure from the Start menu. To
access the Journal Viewer, click the Journal button on the toolbar or select Journal
Viewer from the Start menu.
Complete documentation for the Journal Viewer is contained in online help in the
application itself. A short overview of the Journal Viewer is presented in Chapter
12.
6-5
6-6
Chapter 7
DeltaV Operate for RS3 Desktop
The desktop opens when you start the DeltaV Operate for RS3™ Operator Station.
With Configuration/Operator and Operator configurations, you control your
process from the DeltaV Operate for RS3 Operator Station desktop. The
appearance of the desktop is configurable and the controls and other items that
appear can vary. The following figure shows a typical user interface for a control
system that has both DeltaV and RS3 controllers.
Dual-monitor workstations are required for DeltaV Operate for RS3 Operator
Stations. The dual monitors ensure that operators have access to all pertinent
information.
The user interface includes the following:

The main window which can consist of:

• Two main pictures.
• Two toolbars, DeltaV on one screen and RS3 on the other.
• Two alarm banners, DeltaV on one screen and RS3 on the other.
• DeltaV integrity indicators.
• Alarm Acknowledge buttons on each alarm banner.
RS3-specific pictures and dialogs:
•
•
•
Faceplates
Alarm lists
RS3Diag picture
7-1
The following information is specific to the DeltaV Operate for RS3 parts of the
user interface. For DeltaV-specific information, refer to the DeltaV
documentation.
In addition, the RS3 interface includes continuous and discrete faceplates, tag
status screens, and alarm lists.
The DeltaV Operate for RS3 user interface is built on the DeltaV Operate user
interface. Because the interface is configurable, you can modify it to fit your needs.
Logging In
The DeltaV Operate for RS3 Operator Station automatically logs in the user set up
in the AutoLogin section of the Security Configuration application.
To log in from the desktop:
1. Click the RS3 Login/Logout button to open the RS3 User Login dialog box.
2. Enter your username and password in the RS3 User Login dialog box. Click
the Login button.
Note
When a privileged RS3 user logs out he must login in as another user
with restricted privileges, such as the default user GUEST. An RS3 user
must be logged in for users to have access to DeltaV Operate
functionality.
RS3 Toolbar
The DeltaV Operate for RS3 toolbar contains buttons that provide shortcuts to
menu commands and other fields and controls. If the Start menu is disabled in your
installation you use the toolbar buttons and controls to interact with the console.
The toolbar is configurable and may look different than the examples shown in this
manual.
Toolbar Fields
There are several RS3-specific fields that can appear in a toolbar:
7-2

Login — The Login Name of the user currently logged in.

Type — RS3 console type (Configuration/Operator or Operator).

Group — The group the current user belongs to.

Name — The full name of the user currently logged in.
Toolbar Buttons
Table 7-1shows the RS3-specific toolbar buttons. The location and set of buttons
that are displayed are configurable. The default toolbar included in the software
contains all of these buttons. Refer to Chapter 5 for information on using the
Toolbar Picture Builder to create operator toolbars.
Note
The RS3 faceplate and detail buttons search only the RS3 database.
When you use these buttons enter only the RS3 block name at the
prompt. For example, if the block name is PID1, enter PID1 at the
prompt.
Table 7-1 RS3 Operator Toolbar Buttons
Button
Function
Description
Open RS3
Block
Faceplate
When clicked, prompts for a block name, then opens the RS3
faceplate for the specified block.
This button searches only the RS3 database.
Open RS3
Block Detail
When clicked, prompts for a block name, then opens the RS3 Tag
Status picture for the specified block.
This button searches only the RS3 database.
RS3 Login/
Logout
When you log in, the desktop provides you with the toolbar and
system permissions assigned to your user account.
RS3 Plant Unit
Ownership
Display the current plant unit ownership table. This can be changed
online, but will not be saved permanently. Only users in the RS3
SYSTEM ADMIN, CONFIGURE, TUNE, and MAINTENANCE
groups can use this button.
RS3
Diagnostics
Open the RS3 Diagnostics picture.
RS3 Alarm List
Configure alarm lists and the properties of alarms that are entered
into the alarm lists. Properties include the alarm type and plant
units. Only alarms of the alarm types and from the plant units that
you select are entered into the alarm list.
7-3
Table 7-1 RS3 Operator Toolbar Buttons (Continued)
Button
Function
Description
RS3 Batch
Start the RS3 Batch application. See Chapter 13 for more
information.
RS3 Journal
Viewer
Start the Journal Viewer. The Journal Viewer captures systemgenerated alarms and events and displays them in a datasheet
format. The DeltaV Operate for RS3 Operator Station Journal must
be configured before you can complete station startup.
RS3 Historical
Assign
Assign tagnames from which you want to collect data. You can
organize these tagnames into groups and define parameters of
those groups. Only users in the RS3 SYSTEM ADMIN and
CONFIGURE groups can use this button.
RS3 Mission
Control
Use Mission Control to start and stop historical collection. If you
make changes to collection groups or other variables in the
Historical Assign program you must stop and restart historical
collection for the changes to take effect. Only users in the RS3
SYSTEM ADMIN and CONFIGURE groups can use this button.
RS3 Trend
Display
Open the RS3Chart picture. Use the picture to create, display, and
print trend charts.
RS3 Books
Online
Opens the DeltaV Operate for RS3 Books Online menu.
In addition, there are some DeltaV toolbar buttons that work with RS3 as shown in
the following table.
7-4
Note
Because the DeltaV faceplate and detail buttons search the DeltaV
database first when looking up the module or block it may several
seconds to open an RS3 block. Speed the search for RS3 block names by
prepending RS3 to the block name. For example, if the RS3 block name
is PID1, enter RS3.PID1 at the prompt.
Table 7-2 DeltaV Operator Toolbar Buttons
Button
Function
Description
Open the
faceplate for
any DeltaV
Module or RS3
Block
Opens the module or block in the appropriate faceplate picture.
Because this button searches the DeltaV Database, then the RS3
database, its performance may lag that of the RS3-specific
faceplate button.
Open detailed
information for
any DeltaV
Module or RS3
Block
DeltaV modules open in DeltaV detail faceplates. RS3 blocks open
in RS3 Tag Status screens.
Because this button searches the DeltaV Database, then the RS3
database, its performance may lag that of the RS3-specific detail
button.
RS3 Alarm Banner Overview
RS3 alarms are announced with an RS3 alarm banner at the bottom of the screen.
The alarm banner contains alarm buttons for the five highest priority alarms,
detailed information on the highest priority alarm, batch input button,
acknowledge button for the highest priority alarm, and five buttons that open predefined alarm lists.
RS3 Alarm Buttons
The alarm buttons in the alarm banner indicate the five highest priority alarms
currently active. Each button contains a left and right portion.
The text in the left part is the configured name of the plant unit (or number if no
name is configured) in which the alarm occurred. The numbers in the right part of
7-5
the button show the number of active alarms and the number of unacknowledged
alarms separated by a slash (/).
Click on the left part of the button to open the graphic associated with the block in
alarm. Click on the right portion of the button to open the alarm list for the plant
unit that contains the block in alarm.
Highest Priority Alarm
Information about the highest priority unacknowledged alarm in the system is
displayed in the second line of Alarm Banner.
The information can include:
Note

A box that indicates the current state of the alarm

Time Alarm occurred

Tag and Descriptor of alarm block

Alarm Text

Occur Value and Engineering Unit for continuous values

Message Pair and Logged Value for discrete values

The alarm type

The block priority

The plant unit number
The Journal Viewer application may show additional alarm information
that does not occur in the alarm banner, for purposes of logging and
recording.
Alarm List Buttons
The five buttons at the right of the alarm banner open predefined alarm lists.
Each button contains a letter followed by a number or pair of numbers. The buttons
open the following lists:

7-6
P — Process alarms

H — Hardware alarms

B — Batch alarms

S — System alarms

U — A list of all unacknowledged alarms for all plant units, including those
alarms not associated with a plant unit.
The color of a button indicates the highest priority unacknowledged alarm in the
corresponding list. The numbers in the P, H, B, and S buttons are the number of
active alarms and the number of the unacknowledged alarms in each list. The
number in the U button is the total number of unacknowledged alarms.
Batch Input Button (INP)
This button starts up the RS3 Batch application. It flashes orange when input is
pending.
Acknowledge Button (ACK)
The ACK button on the alarm banner acknowledges the current highest priority
RS3 alarm. Acknowledging an alarm indicates that you have recognized that the
alarm exists.
The ACK button on the alarm banner acknowledges only the alarm listed in the
banner. Alarms acknowledged with the acknowledge button in the banner will
always be immediately acknowledged, but may not be updated in an alarm list if
any alarm is in a selected state. Deselecting the alarm in an alarm list causes the list
to update.
Alarm Lists Overview
Alarm lists contain the most critical and most recent alarms in the RS3 system.
Click on the bell in the toolbar to display the unacknowledged alarm list. It will
replace any graphic currently on the screen. You can filter the types of alarms
which appear here. You can also create custom alarm lists, called user lists.
Clicking on the colored boxes on the left side of the alarm list take you to the plant
unit graphic associated with that alarm.
If you are viewing alarms for a single plant unit, the plant unit’s name (which you
specify in the Plant Units and Areas application) appears in a field at the top left of
the window. The alarm list you are viewing appears in a field at the top of the
window.
7-7
You can use the up and down arrows on the right of the screen to scroll through the
Alarm List. Clicking on HOME takes you to the top of the list.
The numbers to the right of the first and last lines in the Alarm List show your
position in the alarm list.
To get to the main alarm list, either:

click on the right side of an alarm button in the alarm banner

click on the RS3 alarm bell icon in the toolbar.
Alarm States
At the beginning of each alarm line in the Alarm List and in the Alarm Banner is a
colored box. This box is a representation of the state of the alarm:
7-8

large flashing box — the alarm is active and unacknowledged.

small flashing box — the alarm is inactive and unacknowledged.

large box — the alarm is active and acknowledged.
Note
When an alarm has been acknowledged and becomes inactive, it
disappears from the list.
Alarm List Setup
Click the SETUP button to open the Alarm List Setup dialog. You can modify the
alarm list characteristics from any alarm list screen. The dialog contains the
following areas:

Note
Depending on how close you set your alarm update rate (Alarm Setup)
and picture refresh rate, you may continue to see alarms from a previous
list for a few seconds after changing to a new alarm list.

Note
Alarm Lists Section: Set up the update rate of alarms and number of alarms
that appear on each user list. These alterations affect all alarm lists. They do
not affect the Journal Viewer list.
Alarm Horn Section: Enable or disable the alarm horn and set the silence
time.
Your modifications to the Alarm List Setup dialog remain in effect only
until the station is shut down. You can make permanent changes to the
alarm horn by using the RS3 Operator Station Configuration
application.
Alarm Types in List
Use this area to filter alarms that appear in an Alarm List. These filtering criteria
apply only to the alarm list you are currently viewing, and can only be saved if they
are applied to the user-defined lists. Once you leave a non-user alarm list, your
filtering criteria are lost.
You can only see the Alarm Types in List box from a valid alarm list, such as a
plant unit alarm list, user-defined alarm list, or unacknowledged alarm list.
Obviously, a single type alarm list cannot be sorted by alarm type.
List Sorting
Use this area to sort alarms that appear in an Alarm List.These sorting criteria
apply only to the alarm list you are currently viewing, and can only be saved if they
are applied to the user-defined lists. Once you leave a user-define alarm list, your
sorting criteria are lost.
7-9
To sort an alarm list:
1. Open the alarm list you would like to sort.
2. Click a sort method in the List Sorting Area below the lists.
The primary sort order of alarm lists is controlled by the following matrix:
button
primary sort
secondary sorts
Time
most recent
time
alarm type, active,
unacknowledged, block
priority
Priority
active alarms
alarm type, block priority,
most recent time
Unack
unacked
alarms
alarm type, active,
unacknowledged, block
priority, oldest time
The unacknowledged alarm list uses the unacknowledged sort order.
3. Return to the unacknowledged alarm list by clicking the alarm button in the
toolbar.
Select Plant Unit/Plant Unit Filter
This button allows you to filter the alarms that appear on the alarm list by plant
unit.
If you have a pre-defined alarm list open and click the Select Plant Unit button an
entry box appears. Enter the number of a single plant unit. An alarm list containing
alarms from the selected plant unit appears.
If you are in a user-defined list, click the Plant Unit Filter button to open a picture
from which you can select any or all of the plant units.
Plant Unit 0 represents all alarms that are not associated with a plant unit.
Selecting, Acknowledging, and Clearing Alarms
Use the List Selection area to select ALL or NONE of the alarms in the current list.
You can select individual alarms by clicking on the alarms in the alarm list.
After you have selected alarms you can acknowledge them by clicking the ACK
button. Any alarms that are selected will be acknowledged.
7-10
Note
The acknowledgement depends on the settings in the Configure Alarm
Acknowledgment (CAA) tab of the Console Configuration application.
If there are active alarms, the toolbar alarm list icon bell is red. A green
bell indicates no active alarms.
Clear the selected alarms by clicking the CLEAR button. The clear button forces
selected alarms to become inactive. Some user groups, such as operators, will not
have permissions to Clear alarms. In the operator station, alarm clear notification is
only recorded in the Journal of the clearing node. It is not broadcast according to
the settings in the Configure Alarm Broadcast (CAB) tab of the Console
Configuration application.
User Lists
Use the User Lists area to configure up to three alarm lists with the alarm types and
plant units that you choose. Click on a User List button to call up an alarm list and
configure that list.
Faceplates
Each ControlBlock in the RS3 system can be manipulated by the Continuous and
Discrete faceplates. The following figure shows the faceplates.
7-11
Figure 7-1 Continuous and Discrete Faceplates
Note that there are two versions of the Continuous faceplate available: Figure 7-1
shows the default version with the Output bar horizontal. The other version has the
Output bar vertical. To change to the vertical output bar faceplate:
1. Navigate to \DeltaV\DVData\Graphics-iFIX\Pic\RS3\Faceplate.
2. Rename RS3_FP.grf to RS3_HOUT_FP.grf
3. Rename RS3_VOUT_FP.grf to RS3_FP.grf
Note that only the vertical Output bar allows scrolling of the Output value.
7-12
Faceplate Bars
The faceplate bars graphically display values. They display configured colors, as
well as critical (red) and advisory (yellow) colors when a value enters an alarm
condition.
Controller Modes
If you click on the MODE... button the following dialog appears from which you
can select a mode.
Continuous Faceplate
Use this faceplate to view operating conditions for a control loop. Values
configured in the MTCC (multi-tube command console) are used as labels for the
five fields on the faceplate, but the default labels and colors for the fields are
shown in the following table.
Discrete
Label
Continuous
Label
Meaning
Default Color
A
PV
Process Variable
green
B
LS
Local Setpoint
cyan
C
RS
Remote Setpoint
purple
D
FF
Feedforward
tan
Q
Q
Output
orange
7-13
Click the button to the left of a field to open a data entry dialog for the field. If you
attempt to change a value for a field that cannot be changed, an error dialog
appears.
Click on the Exchange button to display the discrete faceplate for the control loop.
Click the Detail button to call up a tag status screen for the faceplate you are
viewing. You can change faceplate values from the faceplate or the tag status
screen.
Discrete Faceplate
Use this faceplate to view up to 17 lines of information, such as equipment status,
continuous variable value, control output confirmation, and various symbols.
You can toggle the values in discrete fields by clicking the button to the left of the
field, if displayed. Discrete fields include on/off and start/stop. A discrete field
behaves in one of the following ways while under operator control:
Momentary
Turns on or off for one second.
Sustained
Turns on or off until changed.
Select
Only one switch of a group can be on at a time.
Click the Detail button to call up a tag status screen for the faceplate you are
viewing. You can change faceplate values from the faceplate or the tag status
screen.
Note
7-14
Sometimes momentary operations occur too quickly to provide a visual
indication on the discrete faceplate. The button will depress when it is
clicked, however.
Device State Indicators
Motor and valve controllers use several indicators to display device states on the
controller faceplate.
Indicator
Definition
Letter Case
All upper case letters indicate that the device state is
active. Lower case letters indicate that the device state is
not active.
Backlighting
Some device states are backlit when active.
Green
This color indicates that the device state is not critical.
Blue
This color indicates that the device state is neutral.
Yellow
The device is performing a noncritical action. For
example, if the travel state is yellow, the valve stem is in
the process of opening or closing.
Red
The device state is critical. For example, if the interlock
state is red, the interlock condition is false and the device
cannot function.
7-15
RS3DIAG Picture
The RS3DIAG picture contains diagnostic information about various components
of the console. The numbers in the title line you see may be different than shown in
the figure.
The following explains the meaning of the fields in the areas of the picture.
Server Area
7-16

Execution State — The current state of the RS3Serve process. This should
typically be 2, Running

Total RS3 Blocks — The number of RS3 blocks created within memory or
cache. This is the number that the license manager reads for licensing.

Total DB Blocks — The number of RS3 blocks configured on the PeerWay.

Resolve Queue — The number of points in the resolve queue to be resolved.
This value should be zero (0) unless a display has recently opened or points
being trended do not exist.

Tag Request Queue — The number of tags to be resolved by the RNI. This
value should be zero (0) unless a display has recently opened or points being
trended do not exist.

R/W Link Data Queue — The number of links to be resolved by the RNI. This
value should be zero (0) unless a display has recently opened or points that
have links are being trended.

Subscribe Queue — The number of subscriptions to be subscribed to by the
RNI. This value should be zero (0) unless a display has recently opened or
points being trended do not exist.

Heap Peak — The peak amount of heap memory used since startup.

Heap Current — The current amount of heap memory being used.
STK Area

Node Name — The name of this Station

Peak Slots — The peak number of slots used in the STK point table.

Current Slots — The current number of slots being used in the STK point
table.

Num links of last display — The total number of display links used in the last
request made to the RS3Serve process. This could be a picture or a trend
group.

Database Errors — The number of tag not found errors (attempts to access
points by tags that do not exist).

Serial Number — The current serial number used by the STK interface. The
number changes whenever a block is deleted.
RNI Area

Node Number — PeerWay node number of the RNI.

Connection State — Current state of the RNI connection. This should
normally be 3, Connected.
DDS Area

Blocks — Maximum limit and the number of blocks currently being
subscribed.

Data Pnts — Maximum limit and the number of points currently being
subscribed.

Subscrib — Maximum limit and the number of subscriptions currently being
used. For a single operator station this equals the number of data points being
subscribed.

Sessions — Maximum limit and the number of sessions currently being used.
The number is one for every operator station connected.
7-17

TimeIntvl — The time interval of all four rates in milliseconds.The default
intervals for rate 1 through 4 are 1, 10, 30, and 60 seconds.

UnitMsgs — The number of unit messages received by the RNI for a specific
rate. A number of data points can be combined into a unit message.

Saturation — The percent of the time interval that the RNI spent sending
requests for information on the points for that rate. Anything over 100%
indicates that the RNI was not able to send out all necessary information for
that rate.

Pts/Msg — The average number of points per unit message that is currently
being requested. Multiplying this number by the number of unit messages
indicates how many total points are being requested for this rate.
License Area

RS3 Console Type — The type of workstation: Configuration/Operator or
Operator.

Batch — Yes (The Batch option is included in all licenses).

License File Count — The licensed block count for this computer.

Configuration License Count — The licensed block count for the
Configuration/Operator station.

Set ID — The identifier for the license set. A license media set can contain as
many as three pieces (one for the Configuration/Operator Station and two for
the Operator Stations). Each license media in a license set has the same Set ID.

Serial Number — The number that identifies a license within the license set.
Each license media in a license set has a unique serial number.
Tag Status Screens
The Tag Status screens display RS3 Block information in the desktop. You can
access Function, Continuous and Discrete Links, Continuous Alarms, Discrete
Outputs, and Continuous and Discrete Faceplate screens.
Call up a Tag Status screen by clicking the Detail button in a faceplate or in the
toolbar.
Some fields are changeable on Tag Status screens, depending on your permissions
and login ID. These fields are marked with carats (>) Click on the value or text to
change it.
7-18
The Tag Status screen includes a line of buttons below the header information. The
following table lists the buttons and their functions.
Table 7-3 Tag Status Screen Buttons
Tag Status Screen Button
Function
Function
Displays the Block Detail Faceplate
(data only)
Links C
Displays Continuous Block Links
Links D
Displays Discrete Block Links
Continuous Alarms
Displays alarms for the block
Discrete Outputs
Displays the block’s Discrete
outputs
7-19
Table 7-3 Tag Status Screen Buttons
Tag Status Screen Button
Function
Opens the Continuous faceplate for
the block
Discrete Faceplate
Opens the Discrete faceplate for the
block.
Alarm Conditions Displayed on Tag Status Screens
The Tag Status screens change based on alarm information. When a value goes into
an alarm condition:

The tag field changes color (Yellow = advisory, Red = critical) and blinks
when there is an unacknowledged alarm.

The line of the register in alarm state turns the alarm color (Yellow = advisory,
Red = critical) on the following Tag Status Screens:
•
•
•
•
Function
Continuous Alarms
Continuous Links
When you adjust these values to remove the alarm condition, the values remain in
critical or advisory color until the alarm condition is acknowledged.
Tuning Parameters
You can change some PID tuning parameters associated with ControlBlocks
directly from the operator station:

Eng Zero and Eng Max fields (Continuous Links screen)

High critical and advisory, low critical and advisory fields, Deadband and Rate
fields (Continuous Alarms screen)

Prop Band, Integ Time, Deriv Time, and FFGain fields (Function Screen)
The Tag Status screens provide a single entry cursor, the carat (>). This symbol
indicates a field is enterable based on your RS3 login. If you see an entry cursor,
you can write the value. If a cursor is not present, the value cannot be written.
Note
7-20
You cannot change a value linked to a register.
Display of Lost or Questionable Data
If you lose a connection with an RS3 controller whose blocks you are viewing
from a DeltaV Operate for RS3 Operator Station, or you lose connection with an
RNI™ device, your data quality for points in that block will be unreliable.
When connection with the controller is lost, the DeltaV Operate for RS3 Operator
Station displays graphic objects and text in magenta. When connection with the
RNI device is lost, DeltaV Operate for RS3 Operator Station data changes to
question marks.
If configuration changes are made to a register value or units field on an MTCC or
System Manager Station, the DeltaV Operate for RS3 Operator Station will
momentarily display values in magenta while it updates its data. This can take up
to 30-40 seconds; then the display will return to its normal color.
If connection with a remote node is lost or not established, strings of @ characters
are displayed in place of data.
Note
If network connections are interrupted, reset the RNI to minimize the
time required to re-establish normal communications in the RS3
network.
7-21
7-22
Chapter 8
Using the Online Help and Documentation
This section explains the online help and documentation for DeltaV Operate for
RS3 only. For information on the help and documentation for DeltaV, refer to the
DeltaV documentation.
For DeltaV Operate for RS3, online help and documentation is available at both
the Windows and the Operator Station levels. Standard Windows help will assist
you in performing Windows system administration tasks. The DeltaV Operate for
RS3 Operator Station offers three forms of online documentation: contextsensitive help, help topics, and online manuals.
Note
Do not move online help files or help directories from their installed
locations. Doing so can create broken links and lead to the appearance
of incomplete help information.
DeltaV Operate for RS3 Operator Station Online Help
To see help for an RS3 application, open help from the application. For example, if
you open Help Topics for the Console Configuration application the following
window appears.
8-1
From this Help Topics screen, there are three ways to find information: The
Contents tab, the Index tab, and the Find tab.
Help Menu: Entering Help from Help Topics
You can browse through the table of contents, use the index to find specific topics,
or search the Help.
Contents Tab
The Contents tab shows a list of books that are either open or closed, and under
those books, pages. The pages represent particular topics. A book will not show
pages unless it is open. To open a book, double click on it. To go to a topic
represented by a particular page, double click on the page.
8-2
Index Tab
The following example shows the Index tab on top. Use the index to look up a
particular term and go to the topic or topics associated with that term.
To look for a particular term, either scroll through until the term appears in the list,
or type the first few characters of the term in the box at the top of the tab until the
term is highlighted in the list. Double click on the term in the list to show the topic
or topics associated with that term.
Find Tab
Finally, the Find tab allows you to search the entire word list in the help file for
topics that include that word. The following is an example of the Find tab.
8-3
The Find tab will either show the word list, or will ask you if you want to compile
the word list (if this is the first time you have ever performed a search on this help
area). If you are asked to compile a word list, follow the prompts on the screen.
Once the word list is compiled, perform the search in the same way you would look
up an index term on the Index tab.
Getting to the Information
Accessing general help may place you directly in a topic related to the application
you were viewing.
For example, selecting RS3 Batch Overview from the RS3 Batch help contents
opens the following help window:
8-4
The example shows a window with a title bar and several buttons below the title.
The buttons perform the following functions:

Help Topics: This button opens the Help Topics window for the particular area
of help you are viewing.

Back: This button takes you to the previous topic you were viewing in this
particular area of help.

<< and >>: Use these buttons to move through predefined sequences of the
topics in this area of help. The << button takes you back one topic in the
browse sequence, while the >> button takes you forward one topic. Note that
the browse sequence cannot be altered and that not all topics are in a browse
sequence.

RS3 Attributes: This button takes you to the help file associated with RS3
attributes. You can use the Back button to return to the topics you were
viewing originally.
8-5
Jumps in Online Help
Online help often includes jumps to other associated topics or other areas of help.
An example of a jump that you are already familiar with is the RS3 Attributes
button. Clicking this button jumps to the RS3 Attributes help.
Another type of jump occurs within a topic itself, and is indicated by green text, a
small button, or both. Clicking on the green text or the button will show a different
topic in the help window.
Context-Sensitive Help
Context-sensitive help is information about a particular item on the screen that you
are working with (an object or a toolbar button, for example). The following
explains the types of context-sensitive Help available through DeltaV Operate for
RS3 Operator Station, and the methods for accessing it. Most DeltaV Operate for
RS3 Operator Station applications have context-sensitive help.
Tool Tips
Tool tips are titles that appear underneath a button when the cursor has been on that
button for a few seconds.
F1
Pressing F1 when an object or window is selected will display the online help for
that particular object or window. This is not implemented for all objects in DeltaV
Operate for RS3 Operator Station. If nothing happens when you press F1, the
selected object does not have online help.
What’s This?
In some applications you can quickly display a pop-up window that tells you what
the currently selected object (fields and buttons, for example) is and a little about
what it does.
What’s This? help is opened in several ways depending on the application:
8-6

Press SHIFT + F1 and click the object.

Press ALT + F1 and click the object.

Select an object, right click, and select What’s This.
If the object has online help, a small popup window appears with information.
Note that this is not implemented for all objects in DeltaV Operate for RS3
Operator Station. If nothing happens when you attempt to open help, the selected
object does not have online help. The figure below shows a typical What’s This
popup.
Annotating Online Help
You can add an annotation (comment) to any online help topic. The presence of an
annotation is indicated by a green paper clip in the upper left-hand corner of the
help topic.
To annotate (add comments to) a help topic:
1. Select Annotate from the Help Edit menu.
2. Type your comments and select Save.
Note
Annotations are saved by default in the directory
\Documents and Settings\username\Application Data\Help in the
following format: <helpfilename>.ann.
8-7
You can read the comments indicated by the green paper clip and you can cut and
paste the comments into another application.
To read an annotation:
1. Click on the paper clip.
2. To close the note, select Close.
To cut and paste annotation text:
1. Click on the paper clip.
2. Select the text you want to copy.
3. Click the Copy button.
4. Paste the text in the desired location.
Note
The DeltaV Operate for RS3 Operator Station system administrator can
make all annotations read-only. When this is done, you can read
annotations but cannot add new ones or edit existing ones. The system
administrator can also place annotation files in network locations.
Online Manuals
In addition to the RS3 online help, a set of RS3 online manuals (similar to a paper
manual set) is also provided. DeltaV Operate for RS3 Operator Station online
manuals are viewed with Adobe Acrobat Reader. You also have access to the
DeltaV books online. Refer to the DeltaV documentation for more information.
The DeltaV Operate for RS3 Operator Station online manuals often contain more
detailed information about the DeltaV Operate for RS3 Operator Station than can
be found in the general or context-sensitive online help. If you cannot find the
information you need in the online help, go to the online manuals.
DeltaV Operate for RS3 Operator Station and RS3 online manuals can be accessed
from the Start menu and from Help menus in RS3 applications.
8-8
Searching Online Manuals
You can search online manuals as follows:
1. In Acrobat Reader, select Edit | Find...
2. Enter the text to find.
3. Click Find.
The first instance of the text in the manual is highlighted.
4. To continue looking for the text, click Find Again.
8-9
8-10
Chapter 9
RS3 Configuration Applications
You can select the RS3™ Operator Station configuration and RS3 Journal
configuration applications from the Start menu.
Note
To make changes take effect, you must shut down and restart the
workstation:
1. Log out, and log back in as a DeltaV Operate for RS3 Operator Station system
administrator.
2. Press Ctrl-Alt-Del, and select Shutdown and Restart in the dialog.
3. Services and DeltaV Operate for RS3 Operator Station restart automatically.
Configure DeltaV Operate for RS3 Operator Station
Application
From the Start menu select Operator Station Configuration to open the Console
Configuration application. Open a configuration by selecting File | Open Current
Configuration or File | Open Offline Configuration. If this is the first time you have
used the Console Configuration application, the only configuration will be the
default configuration.
9-1
An open configuration contains the following tabs:

General Configuration

Alarm Configuration

Configure Alarm Acknowledge

Configure Alarm Broadcast

Message Pairs

Node Ownership

Plant Unit Ownership

Plant Unit Configuration
You can have multiple configurations, but only one of them is the current (or
online) configuration being used by the console. Configurations are organized as
9-2
several subsets of configuration information. All of the configurations and subsets
are stored in the registry.
The configuration subsets combine the tabs in the following way:

General Configuration and Alarm Configuration

Configure Alarm Acknowledge

Configure Alarm Broadcast

Node Ownership

Plant Unit Configuration and Plant Unit Ownership

Message Pairs.
Note that the General Configuration subset specifies all other subsets of a
configuration.
Use the Console Configuration application to edit and save configuration subsets,
as well as back up configurations to database files (and restore configurations from
database files) and write configurations to the registry.
The remainder of this subsection explains the information contained on each tab of
a configuration.
Refer to the online documentation for detailed information on all configuration
applications.
General Configuration Tab
The General Configuration tab includes areas for Workstation, Configure Alarm
Broadcast, and Plant Configuration.
9-3
Workstation Area
Item
Description
Site
The name of the site. You cannot change the value in this
field (display only).
LAN
The process network to which the DeltaV Operate for RS3
Operator Station and RNI device are connected. You
cannot change the value in this field (display only).
PeerWay
The number of the PeerWay connected to the process
network through the RNI™ device. You cannot change the
value in this field (display only).
RNI Host
The name of the RNI device used by the DeltaV Operate
for RS3 Operator Station. You must enter an RNI device in
order for the DeltaV Operate for RS3 Operator Station to
communicate with the RS3 PeerWay system.
Note: This name must be the same as the name entered in
the RNI Configuration Utility.
Message Pairs
Selects the message pair subset to be used by the DeltaV
Operate for RS3 Operator Station. Message pair sets are
defined from the Message Pairs tab.
Configure Alarm Broadcast Area
9-4
Item
Description
Generate Alarms
Selects the set of RS3 nodes to which the DeltaV
Operate for RS3 Operator Station can send alarms. The
set is defined from the Configure Alarm Broadcast tab.
Acknowledge
Alarms
Selects the set of RS3 nodes to which the DeltaV
Operate for RS3 Operator Station can send alarm
acknowledgments. The set is defined from the Configure
Alarm Acknowledge tab.
Plant Configuration Area
Item
Description
Node Ownership
Selects the set of nodes containing blocks in plant unit 0
(zero) from which the operator station can receive alarms
and operate blocks. A node containing blocks in plant unit
0 must be assigned to the operator station if you want to
receive alarms and operate the blocks.
Plant Unit
Ownership
Selects the set of plant units from which the operator
station can receive alarms and operate blocks.
If a block is in plant unit 0 (zero), you must assign the
node containing the block to the operator station from the
Node Ownership tab to receive alarms and operate the
block.
Alarm Configuration Tab
Use the Alarm Configuration tab to set the silence time and enable and disable the
horn.
Item
Description
Silence Time
Specifies the length of time (in seconds) that the console
horn is silent after the Silence Horn button on the alarm
banner has been clicked. New RS3 alarms do not
reactivate the horn until the silence time has expired.
Note that Silence Time has no effect on DeltaV alarms.
Alarm Horn
Enable and disable the RS3 horn.
Configure Alarm Acknowledge Tab
Use the Configure Alarm Acknowledge tab to define which nodes are sent alarm
acknowledgement messages from this node. By configuring the CAA, you can
limit the amount of message traffic to specific nodes on the PeerWay.
9-5
Item
Description
Destination Nodes
Enabled
A list of the nodes that will receive alarm
acknowledgement messages from this node.
Destination Nodes
Disabled
A list of the nodes that will not receive alarm
acknowledgement messages from this node.
Buttons
The Add, Add All, Remove, and Remove All buttons
move nodes between the two lists.
Configure Alarm Broadcast Tab
Use the Configure Alarm Broadcast tab to define which nodes are sent alarm
messages from this node. By configuring Alarm Broadcast, you can limit the
amount of message traffic to specific nodes on the PeerWay.
Item
Description
Destination Nodes
Enabled
A list of the nodes that will receive alarm messages
from this node.
Destination Nodes
Disabled
A list of the nodes that will not receive alarm messages
from this node.
Buttons
Message Pairs Tab
Use the Message Pairs tab to define message pairs for the console. The message
pair consists of one message for the on (1) state and one message for the off (0)
state. When you configure discrete states on a ControlBlock, you can specify
which message pairs you want to use to represent the states on a faceplate or
graphic display: For example, ON / OFF, START / STOP, HIGH / LOW, etc. The
Message Pairs application can contain up to 255 message pairs:

1 to 100 are preconfigured.

101 to 250 are user-configured.

251 to 255 are preconfigured.
The tab contains a list of the true and false messages for the console. To edit a pair,
double click on it. The message pair editor dialog opens. From the dialog you can
9-6
edit the message text and change the foreground and background colors of the
message.
Node Ownership Tab
Use the Node Ownership tab to assign nodes containing blocks in plant unit 0
(zero) to the operator station. A node containing blocks in plant unit 0 must be
assigned to the operator station if you want it to receive alarms and operate the
blocks. If the node contains blocks in a plant unit other than 0, to receive alarms
and operate the blocks, assign the plant unit to the operator station from the Plant
Unit Ownership tab.
Item
Description
Enabled Nodes
A list of the nodes that will receive alarms.
Disabled Nodes
A list of the nodes that will not receive alarms.
Buttons
Plant Unit Ownership Tab
Use the Plant Unit Ownership tab to assign plant units to the operator station to
receive alarms and operate blocks. If a block is in a plant unit other than 0 (zero),
the operator station must own that plant unit to receive alarms and operate the
block.
Item
Description
Enabled Units
A list of the units from which the console can receive
alarms.
Disabled Nodes
A list of the units from which the console will not receive
alarms.
Buttons
move units between the two lists.
Plant Unit Configuration Tab
Use the Plant Unit Configuration tab to name plant units and assign graphics to
plant units. The plant unit names you configure on this tab appear in alarm banner
9-7
buttons when a block in a plant unit is in alarm. If you do not name plant units,
plant unit numbers appear in alarm buttons.
The graphics you assign to plant units appear when an alarm button is clicked. By
associating graphics with plant units you make it easier for operators to monitor
and respond to plant units that are generating alarms.
Item
Description
Unit, Name, and
Graphic list
A scrollable list of plant units (by number) and their
associated names and graphics.
Number
Read-only field that shows the plant unit number you
are assigning a name and graphic to.
Name
Enter a name for the currently selected plant unit.
Names can be as many as 16 characters.
Graphic
Enter a graphic (*.grf file) to associate with the currently
selected plant unit. The graphic name can be no more
than 16 characters.
The following figure shows the Plant Unit Configuration tab.
To name a plant unit and associate a graphic with it, follow these steps:
1. In the list on the left side of the tab, click anywhere in the row corresponding to
the plant unit that you want to configure.
9-8
The plant number appears in the Edit Unit Name area of the tab and default
entries appear in the Name and Graphic Fields.
2. In the Name field enter up to 16 characters to name the selected plant unit.
This name appears in the alarm banner button when a block in this plant unit
is in alarm.
3. In the Graphic field enter the name of the graphic that you want to associate
with this plant unit. The graphic file must be located in the
\DeltaV\DVData\iFix-Graphics\PIC subdirectory and its name cannot be
longer than 16 characters.
4. Click Apply.
5. After you have configured all the plant units necessary, select File | Save
Subset to save your changes.
Note
The information on the Plant Unit Configuration tab is global across
console configurations. Selecting File | Save Subset from the Plant Unit
Configuration tab makes the information available to all console
configurations.
Configure RS3 Journal
Use the DeltaV Operate for RS3 Operator Station Journal Configuration
application to enable, name, and define the properties of the DeltaV Operate for
RS3 Operator Station Journal.
Item
Description
Enable Journal
Enable and disable the DeltaV Operate for RS3
Operator Station Journal.
Name
Enter a file name for the journal.
Directory
Enter a directory to store the journal files.
Maximum File Size
Enter the maximum size you want a journal file to
be.
Maximum File Count
Enter the maximum number of journal files you want
to keep on disk.
Maximum Journal Size
This read-only field shows the calculated maximum
disk space allocated for the journal.
9-9
Item
Description
Warning Alarm Limit
Enter the percentage of maximum journal size that
can fill with events before notification that the
warning % full limit has been reached. (Check your
hard drive to make sure you have enough free disk
space.)
Note: Setting the limit to 0% turns off the notification
function
9-10
Chapter 10 Creating and Configuring Graphics
One of the most useful features of the DeltaV Operate for RS3 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 and creating a picture navigation
scheme for the DeltaV Operate environment, refer to Creating Pictures in the
DeltaV Books Online.
This section explains only RS3-specific information you need to create displays
that reference data from the RS3 control system.
DVSYS and FIX32.THISNODE
DeltaV Operate for RS3 systems have two data servers available for specifying
datalinks: DVSYS and FIX32.THISNODE. On workstations that have only
DeltaV Operate software installed, both of these data servers refer to DeltaV data.
After you install DeltaV Operate for RS3 on a workstation FIX32.THISNODE
refers only to RS3 data from that workstation. This means that complete
development and testing of displays that access RS3 data cannot be performed
from the ProfessionalPLUS workstation, but must be performed from a DeltaV
Operate for RS3 Configuration or Operator station.
Note
If you are integrating DeltaV Operate for RS3 software into an existing
DeltaV system, all links to DeltaV data in pictures and scripts
downloaded to workstations on which DeltaV Operate for RS3 is
installed must be in the form:
DVSYS.MODULE/BLOCK/PARAMETER.FIELD
On workstations with DeltaV Operate for RS3 software installed
FIX32.THISNODE refers only to RS3 data.
Display Names in DeltaV Operate
In DeltaV Operate each display is a file with a .GRF extension. Display files are
stored in the directory DeltaV\DVData\Graphics-iFIX\PIC. The display name and
Creating and Configuring Graphics
10-1
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:
Note

Start with a letter

Contain only letters, numbers, and underscores (_)

Be no more than 31 characters long.
Displays that you are going to assign to plant units as alarm displays (in
the Console Configuration application) can be no longer than 16
characters.
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 block mode, as well as
attributes such as alarm priority and alarm status.
Console resources are required to process each link to the database and therefore
the number of dynamic elements you can have on a display is limited. The limit
depends on your system's dynamics and the speed at which you require displays to
be updated.
Tagnames
In RS3 the term tagname usually refers to the specifier for an RS3 block attribute.
A tagname consists of the node name, block tag, process variable, field, attribute
name, aspect, and occurrence, if any.
Note
Block tags you configure in the MTCC for use in the DeltaV Operate for
RS3 software should:

10-2
Contain at least one letter.
Contain only uppercase letters, numbers and dashes (-). These are the
only characters valid in MTCC configuration that are also valid in
DeltaV Operate.
Be no more than 16 characters long (8 characters for Batch tags).
In particular:

Change all lowercase letters in the MTCC block tag configuration to
uppercase.
Block tags that contain lowercase letters but are otherwise valid are not visible
in the Expression Builder. However, the block’s hardware address is visible.

Change all periods (.) in the MTCC block tag configuration to a valid
character.
Block tags that contain periods but are otherwise valid appear in the
Expression Builder and can be selected, but DeltaV Operate does not accept
tagnames built with these tags. In addition, the hardware addresses for tags
with periods do not appear in the Expression Builder.
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:

Your configuration database tags must be valid DeltaV Operate tagnames
(contain only uppercase letters, numbers, and dashes (–)).

If you enter tags rather than use the Expression Builder, there are
recommended syntaxes to use in most cases.

Entering tagnames in dynamos may require that you edit the tagname after you
insert it.
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 RS3 systems the tab of interest is
the FIX Database tab. This tab is an interface you use to browse to the combination
of RS3 node, Tag Name or Tag Address, and Field Name to place as a link on a
display.You can access the Expression Builder from most dialogs that use
tagnames.
Note
Not all tags or attributes are visible in the browser. You must manually
enter tagnames that include batch tags and batch attributes.
10-3
When you insert a data link in a display, the Datalink dialog appears.Clicking the
… button on the Datalink dialog opens the Expression Builder.
Note
The example uses the Datalink dialog, but most dialogs that require or
use tagnames work the same way.
Expression Builder
Select the FIX Database tab as shown in the figure.
Figure 10-1 Expression Builder
For information on using the dialog, use the What’s This help by clicking on the ?
button, then clicking on an area of interest. For help on RS3 attributes, click the
Help button, then click on the link for RS3 attributes help.
10-4
Selecting a Tag and Attribute
Start by clicking THISNODE in the Node Names area of the dialog. A list of RS3
blocks appears in the Tag Names area. Note that some tags (the batch tags, for
example) do not appear in the list. Select a block and a list of attributes valid for
that block type appear in the Field Names area. Note that some valid attributes do
not appear in the list. For a complete list of attributes, click the Help button in the
expression builder, then click the link to the help for RS3 attributes.
After you have navigated to and selected the desired combination of block name
and attribute, the selected tag and attribute and a valid default field appear in the
expression box. For example, in the figure the expression is:
Fix32.THISNODE.267B-1.A_BLKTYPE
To specify an aspect, you must edit the tagname either in the Expression Builder or
the Datalink dialog.
Click the OK button to transfer the attribute reference to the Datalink dialog
Source field.
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. In
some cases, using batch tags and aspects for example, you must manually enter or
edit the tagname.
Common Syntax
There are five common syntax variations, two for named blocks, one for highway
addresses, and two for tagnames that refer to database addresses.
For named blocks:
FIX32.THISNODE.RS3Tag.A_ATTRIBUTE[N]/ASPECT
or
FIX32.THISNODE.RS3Tag/ATTRIBUTE[N].A_ASPECT
For highway addresses:
FIX32.THISNODE.\’HW:=nnZ-mm\’.A_ATTRIBUTE[N]/ASPECT
where
FIX32 is required
10-5
THISNODE is a non-machine-specific reference to the local machine. Using
THISNODE instead of the computer name allows you to transfer tags easily across
operator stations.
RS3Tag is the RS3 block tag
nn is the node number
Z is the controller (A through G)
mm is the point number
A_ (or F_) is the data type specifier. Use A_ to display attribute data in ASCII
format. This displays text and numeric data as ASCII strings. To display data as
floating point numbers, use F_. Note that not all attributes can display as floating
point numbers.
ATTRIBUTE is an attribute valid for that block type.
N 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.
ASPECT is an optional qualifier that defines elements of data in an RS3 block
attribute. For example, /PCTCV returns the unscaled percentage value (0-100) for
register A. For a list of aspects valid for particular block types, refer to the RS3
Attributes online help.
For batch tags:
Fix32.THISNODE.\’BS:=node:slot\’.A_ATTRIBUTE[N]/ASPECT
or
Fix32.THISNODE.\’BS:=node:slot/ATTRIBUTE[N]\’.A_ASPECT
where
Fix32 is required
THISNODE is a non-machine-specific reference to the local machine. Using
THISNODE instead of the computer name allows you to transfer tags easily across
operator stations.
Note
The backslash and quote pairs (\’) are required to set off the tag or tag
and attribute when the tag contains characters that are not valid in
tagnames. The quoted string is passed to the MTCC for parsing.
BS means Batch Session
10-6
node is the batch node number
slot is the batch slot number and must be the parent slot of the recipe (slots 1-32)
A_ (or F_) is the data type specifier. Use A_ to display attribute data in ASCII
format. This displays text and numeric data as ASCII strings. To display data as
floating point numbers, use F_. Note that not all attributes can display as floating
point numbers.
ATTRIBUTE is a batch attribute
N is an optional index number.
ASPECT is a valid batch aspect.
If you enter a tagname (attribute reference) that does not exist in the database, a
Connection Error appears saying the Source does not exist. 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.
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 RS3 and DeltaV systems (opening
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 RS3 software includes the Visual Basic function
frsRS3Tasks you can use to access RS3 functionality from scripts. The command’s
definition is:
Public Sub frsRS3Tasks(strCmd As String)
The following examples show the RS3 functions you can access using
frsRS3Tasks.
frsRS3Tasks "Login"
frsRS3Tasks "HistoryAssign"
frsRS3Tasks "MissionControl"
frsRS3Tasks "BooksOnline"
10-7
frsRS3Tasks "Batch"
frsRS3Tasks "ViewJournal"
Using Dynamos
For general information on using dynamos, and information on the dynamos
included with DeltaV software, refer to the DeltaV documentation.
DeltaV Operate for RS3 software includes the following dynamos:
10-8

FrsRS3FP.fds — Add analog and discrete faceplates to a picture

FrsRS3Dyn1.fds — Add fields for RS3 continuous block links. The fields
include the block address, tag, description, register, value, and engineering
units. Each field prompts you for the tagname of the RS3 block.

FrsRS3Dyn2.fds — Add discrete faceplate block links to a picture.
Chapter 11 Trending and Reporting
DeltaV Operate for RS3 software supports trending of historical and real-time in
charts you add to operator pictures and in the pre-configured RS3 Trend Display
picture. The software also supports reporting of real-time (but not historical) data
using Dynamic Data Exchange (DDE) and Microsoft Excel.
Historical Trending
Historical trending is the display of process data that has been saved (or is being
saved) to disk. Historical trend traces are persistent. That is, if you close and reopen a trend picture, the historical data reappears. Historical trending has three
components:
1. Historical Assign
2. Historical Collect
3. Display (either in pictures you create or from the RS3 Trend Display picture)
Refer to the manual Trending in DeltaV Operate for RS3 for information on
historical trending
Real-time Trending
Real-time trending is the display of process data that is current. Real-time trend
data is kept for only a short period. Each time you open a trend picture, real time
trends restart.
Refer to the manual Trending in DeltaV Operate for RS3 for information on Realtime Trending
Reporting
Reporting is the creation of real-time data in a form suitable for printing. Reports
can be formatted with titles, explanatory text, dynamic values, and static values
(values that are updated only when the report opens).
DeltaV Operate for RS3 does not support reporting of historical data.
Refer to the Using DDE manual for more information.
Trending and Reporting
11-1
11-2
Trending and Reporting
Chapter 12 DeltaV Operate for RS3 Operator Station
Journal Viewer
The Journal Viewer enables you to view, sort, filter, and print alarms, events, and
ABC Batch™ messages (ABMs) in your process. Journal files, whose sizes and
locations are configurable, are set up in the Journal Configuration. To access
Journal Configuration, select Journal Configure from the Start menu.
The Journal Viewer adds a front-end user interface based on Microsoft Access. In
addition, you can now perform complex operations on your journaled data,
including:

Filtering data with Primary or Interactive filters

Viewing data in color

Viewing detailed message information

Sorting data in alphabetical or numeric order

Printing

Formatting the appearance of data and cells in the datasheet

Exporting data to a text editor or in Microsoft Excel (.xls) format

Importing and exporting primary filters
Complete documentation on the Journal Viewer is available by selecting Help
Topics from the Help menu in Journal Viewer.
Note
The Journal Viewer is intended to display and manipulate historical
data. Use the Alarm List to monitor and respond to process alarms.
Note
Under some circumstances all Journal fields may become filled with
#Name?. This can occur if the data the Journal is reading becomes
unavailable. To restore the Journal, refresh the screen, reduce the filter
time span, or restart the Journal viewer.
Starting the Journal Viewer
To start the Journal Viewer, click the Journal button on the toolbar:
DeltaV Operate for RS3 Operator Station Journal Viewer
12-1
Note
When using the Journal Viewer you may occasionally see a message
that says:
Can’t open database
C:\FRSI\NetConnect\JournalViewer\Viewer.mde.
It may not be a database that your application recognizes or
the file may be corrupt.
This message appears when you attempt to view a database file that the DeltaV
Operate for RS3 Operator Station system is currently writing data to. If you see this
message, acknowledge it and try again.
Operator Station Journal (*.mdb) Schema Definition
The structure of the data as sent to the DeltaV Operate for RS3 Operator Station
Journal is known as its schema. What follows is a complete list of the columns
available in the Journal Viewer, their associated datatype, and a short description.
If you want to make your own user interface to the journal (you cannot modify the
Journal Viewer UI) you can do so using the parameters in the following table.
The following table lists columns of the journal. Some columns are hidden by
default. Columns that appear in Color mode are marked with an asterisk (*).
Table 12-1 Column Definitions
12-2
Column Name
Field Description
*Source
Displays the tag, address, node, or plant unit that generated the event.
*Occur Time
Date/Time the event occurred, which is associated with
the timestamp in Occurrence.
*Address
RS3 block address associated with the message.
*Description
The RS3 Descriptor field, the value captured as the
block alarmed (or for discrete blocks, the message pair
associated with the alarm state), and units.
Table 12-1 Column Definitions (Continued)
Column Name
Field Description
*ST
Alarm Status. For Critical, Advisory, Hardware, and
Batch type alarms.
Critical High (CH)
Critical Low (CL)
Critical Deviation (CD)
Critical Rate (CR)
Critical Step (CS)
User Step (US)
Advisory High (AH)
Advisory Low (AL)
Advisory Rate (AR)
Advisory Step (AS)
Advisory Deviation (AD)
Batch Step (BS)
Hardware High (HH)
Hardware Step (HS)
Hardware Low (HL)
Hardware Miscellaneous (HW)
*BP
Block priority of the block issuing the alarm or event.
*PU
Plant unit number of the block issuing the alarm or
event.
*Acknowledge Time
Timestamp of when an operator acknowledged the
alarm or event. This filter function does not affect ABM
messages.
*Inactive Time
Timestamp of when the alarm condition became no
longer active (alarm was cleared). This filter function
does not affect ABM messages.
*Transaction
Transaction type:
Ack=acknowledge
Clr=inactive (clear)
Occ=occur
Msg=message (alarms that can only be acknowledged, not cleared)
12-3
12-4
Column Name
Field Description
*Type
Alarm type:
Adv=Advisory
Bat=Batch
Crit=Critical
Disk=Disk
HW=Hardware
OCL=Operator Change
Sys=System
ABM = ABC Batch Message
*Id
Alarm ID. A numeric value that uniquely identifies the
event or alarm type. Alarm IDs are listed in the RS3
Alarm Messages Manual and in the online help index
for the Journal Viewer.
Node
Node number of the node that generated or sourced
this alarm.
Block
The block number. (Hidden by default)
PU Name
The plant unit name (as configured in the Plant Units
application) associated with the message.
Seconds Since 1980
Along with milliseconds, this is the default sort order of
the journal. (Hidden by default)
Milliseconds
In the case where two alarms arrive on the same second, the milliseconds field determines precedence.
(Hidden by default)
Late Flag
If the controller received a late message from the PeerWay, the message is stamped with a late flag.
KeyInfo
Field reserved for troubleshooting alarm and event
based problems. (Hidden by default)
S
Reserved for future use. (Hidden by default)
Batch Start ID
The time at which a batch (i.e. working recipe) is
started in seconds since 1980.
Batch Start Time
The time at which a batch (i.e. working recipe) is
started in time and date format.
Column Name
Field Description
Recipe Sequence
Number
The number maintained on a per batch, per node, per
recipe (main/unit) basis and increments for each batch
message associated to a given main or unit recipe.
This number is reset to zero after a DYN (parent)
memory allocation, associated with a new main or unit
recipe, occurs.
Main Tag
The tag assigned to a Main recipe guaranteed to be
unique through the life cycle of a batch (i.e., working
recipe).
Domain ID
Defines the ID of the executing entity that generates an
event.
Domain Type
Determines which executing entity is the origin of an
event.
Slot Number
The task number in which a Unit Process icon executes for a Main Recipe or the task number in which a
Unit Recipe icon executes for a Unit Recipe.
Message Type
Sub-message body type which includes the message
CLASS, SUBCLASS, and TYPE
Version
The version level of the sub-message structure.
Record Source
File the record is stored in. (Hidden by default)
Color mode column definitions appear in the following table. Note that the
columns are not exactly a subset of the previous table.
Table 12-2 Color Mode Column Definitions
Column Name
Field Description
Source
Displays the tag, address, node, or plant unit that generated the event.
Occur Time
Time the event occurred, which is associated with the
timestamp in Occurrence.
Occur Date
Date the event occurred, which is associated with the
timestamp in Occurrence.
TR Date
Transaction date
Address
RS3 block address associated with the message.
12-5
Table 12-2 Color Mode Column Definitions (Continued)
12-6
Column Name
Field Description
Description
The RS3 Descriptor field, the value captured as the block
alarmed (or for discrete blocks, the message pair associated with the alarm state), and units.
ST
Alarm Status. For Critical, Advisory, Hardware, and Batch
type alarms.
Critical High (CH)
Critical Low (CL)
Critical Deviation (CD)
Critical Rate (CR)
Critical Step (CS)
User Step (US)
Advisory High (AH)
Advisory Low (AL)
Advisory Rate (AR)
Advisory Step (AS)
Advisory Deviation (AD)
Batch Step (BS)
Hardware High (HH)
Hardware Step (HS)
Hardware Low (HL)
Hardware Miscellaneous (HW)
BP
Block priority of the block issuing the alarm or event.
PU
Plant unit number of the block issuing the alarm or event.
Ack
Timestamp of when an operator acknowledged the alarm
or event. This filter function does not affect ABM messages.
Inactive
Timestamp of when the alarm condition became no
longer active (alarm was cleared). This filter function
does not affect ABM messages.
TR
Transaction type:
Ack=acknowledge
Clr=inactive (clear)
Occ=occur
Msg=message (alarms that can only be acknowledged,
not cleared)
Table 12-2 Color Mode Column Definitions (Continued)
Column Name
Field Description
Type
Alarm type:
Adv=Advisory
Bat=Batch
Crit=Critical
Disk=Disk
HW=Hardware
OCL=Operator Change
Sys=System
ABM = ABC Batch Message
Id
Alarm ID. A numeric value that uniquely identifies the
event or alarm type. Alarm IDs are listed in the RS3
Alarm Messages Manual and in the online help index for
the Journal Viewer.
Alarms for RS3 Batch
The RS3 Batch application contains a number of RS3 Batch-related alarms. The
list below indicates the RS3 Batch alarm IDs. More information about these alarms
is available from the Index tab of the Journal Viewer Online Help.
447
448
470
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
496
497
499
12-7
12-8
Chapter 13 RS3 ABC Batch Operations
RS3 ABC Batch™ Operations (RS3 Batch) lets you view and control RS3™ Batch
tasks from the DeltaV Operate for RS3 Operator Station. Batch information is
presented on four tabs:

The Batch Faceplate tab provides status information on the batch task, and
buttons to control the task.

The Recipe Faceplate tab provides status information on the recipe and recipe
icons.

The Recipe View tab lets you monitor the execution of the Working Recipe.

The Batch Input tab displays messages and input prompts. This is where you
enter data requested by the task.
You can view and answer input prompts for up to four Batch tasks simultaneously.
The RS3 Batch application, with the Batch Faceplate tab in front, is shown below
RS3 ABC Batch Operations
13-1
Starting RS3 Batch
RS3 Batch is started from the desktop, using one of these methods:

Clicking the ABC button on the toolbar
RS3 Batch starts up without opening a particular task. You can then open a task
by selecting File | Open and entering a node and slot, or by selecting a task
from the list of the four most recently opened tasks under File.

Clicking the INP button on the alarm banner
If RS3 Batch is not running, the INP button starts the application and opens the
task associated with the first Batch active input alarm on the alarm list. If RS3
Batch is running, the button opens the task associated with the first active
batch input alarm on the alarm list. (The button flashes orange when a Batch
input alarm is received.)
Displaying Batch Information on Process Graphics
You can display the Batch Faceplate and Recipe Faceplate information on a
DeltaV Operate for RS3 Operator Station process graphic using the following
syntax:
THISNODE.‘BS:=node:slot’.A_attribute[n]
where BS means Batch Session, node is the batch node number, slot is the batch
slot number, and n is an optional index number. The slot number must be the parent
slot of the recipe (slots 1-32).
The batch attributes are as follows:
13-2
Batch Attribute
Description
BATTAG
Batch tag
BATID
Batch ID
*BATNODE
Batch node number
*BATSLOT
Batch slot number
*BATPU
Batch plant unit number
BATPHASE
Batch phase
BATSTATE
Batch state
Batch Attribute
Description
†BATDPVR[n]
Batch display variable, where n is the variable
number (between 0 and 15)
RECDATE
Recipe start date
RECTIME
Recipe start time
RECNAME
Control Recipe name
RECOPST[n]
Recipe operation icon state, where n is the operation number (between 0 and 15)
RECOPNA[n]
Recipe operation icon name, where n is the operation number (between 0 and 15)
RECSTATE
Recipe state
RECUNIT
Recipe unit name
† The BATDPVR[n] attribute requires you to add the Batch Script
Command Display to the RBL script to display a string variable in the
RS3 batch display.
Refer to the RS3 manuals for the Display script command syntax.
* Represents the attributes that can be used in floating point format.
Example:
THISNODE.‘BS:=953:24’.A_BATTAG
This displays the batch tag for the batch in node 953, slot 24.
Batch Operations
With RS3 Batch, you can do the following:

Monitor batch task information

View a Working Recipe

Monitor the status of the units and operations related to a Working Recipe

Enter Batch input data

Start a standard batch task

Put a recipe in Static mode

Trip an on abort trap

Trip an on hold trap and terminate an on hold trap
13-3

Trip an on stop trap

Print out batch task information
Online Help
The RS3 Batch online help provides detailed information on using the application.
You can access RS3 Batch procedural and general batch reference information by
selecting Help Topics from the Help menu. For descriptions of fields, screen areas,
and buttons, use context-sensitive help (see Context-Sensitive Help in Chapter 8).
The RS3 manual set provides more detailed information on ABC Batch operation.
13-4
Chapter 14 RS3 ABC Batch Messages
You can monitor ABC Batch™ Messages (ABMs) and view them in the Journal
Viewer. In addition, the Journal Viewer contains ABM filtering functions that
enable you to view, sort, filter, export, and print ABC Batch Messages.
As you implement a batch process and initiate the recipes that comprise the batch
process, the DeltaV Operate for RS3 Operator Station system will begin to receive
ABC Batch messages. This raw data is stored in the journal as .mdb files. The
figure below shows the logical path of an ABC Batch message.
Note
The default filter for the RS3 Journal Viewer excludes the ability to
monitor ABMs. You must enable ABC Batch messaging, and configure
a filter to view ABMs in the Journal Viewer. Refer to the Start ABM
Messaging subsection for the procedure to configure ABM monitoring.
Filtering ABC Batch Messages
The Journal Viewer includes ABM features that enable you to filter classic batch or
ABC Batch information in the Journal Viewer. The following paragraphs identify
these features in the Journal Viewer.
RS3 ABC Batch Messages
14-1
The Journal Viewer displays message header information for each ABC Batch
message in columns within the viewer. The following table identifies the new
Journal Viewer columns and a brief description of each addition. None of these
columns appear when you view them in color mode.
ABM Journal Column
Description
Batch Start ID
The time at which a batch (i.e. working recipe) is started in seconds
since 1980.
Batch Start Time
The time at which a batch (i.e. working recipe) is started in time and
date format.
Recipe Sequence Number
The number maintained on a per batch, per node, per recipe (main/
unit) basis and increments for each batch message associated to a
given main or unit recipe.
Main Tag
The tag assigned to a Main Recipe, and is guaranteed to be unique
through the life cycle of a batch (e.g. working recipe).
Domain ID
The tag of the unit recipe.
Domain Type
Determines the origin of an event by listing the executing entity.
Slot Number
The task number in which a Unit Process icon executes for a Main
Recipe or the task number in which a Unit Recipe icon executes for a
Unit Recipe.
Message Type
The type of ABC Batch Message.
Version
The version level of the ABM structures.
Primary Filter
The Filter Being Edited dialog is used to enable ABC Batch messaging. This
dialog contains tabbed pages that apply directly to ABC Batch messaging. You can
open this dialog box by selecting either of the following menu items: Records |
Primary Filters | New..., or Records | Primary Filters | Edit.... All ABM filtering
will be done using the following tabbed pages.
14-2

ABM Type Tab — This tab enables you to filter ABC Batch messages based
on a specific ABC Batch message type or a specific domain type (e.g. main,
unit, or classic recipe). (These fields, and the remaining ABM fields, do not
apply to alarms, events, or OCLs.)

Recipe Tab — This tab contains two fields, the ABM Main Tag field and the
ABM Domain ID field. From this tabbed page you can filter messages based
on a tag from either a main or unit recipe.

Batch Start Time Tab — This tab enables you to define a range of time when
you can query for batch recipes that have been started within a set time frame.

Sequence/Slot Tab — This tab enables you to filter ABC Batch messages
according to the ABM Slot Number, or the ABM Recipe Sequence Number.
ABC Batch messages provide you with an accurate record of a process as it
executes. For more specific information about the ABC Batch messages, refer to
the online help.
Message Detail View
Each ABM in the Journal Viewer contains more specific information than what is
shown in the main viewer table. A corresponding Message Detail dialog box that
contains message-specific information exists for each ABC Batch message. Every
Message Detail dialog box contains two basic types of information:

Header information. This is the same header information that appears in the
Journal Viewer.

Message-specific information. This information defines the message-specific
fields associated with each ABM.
You can view the Message Detail information of an ABM by performing one of the
following steps.
1. Select a message in the Journal Viewer and then select View | Message Detail
View
2. Select a message in the Journal Viewer and click on the Message Detail View
icon in the toolbar.
3. Select the message and press the Enter key
Starting ABM Messaging
How you enable ABC Batch messaging depends on whether you are running ABC
Batch or Classic Batch on your system. The following procedure defines how you
enable ABC Batch messaging on an RS3™ system running Classic Batch. (The
order in which you perform these steps is not relevant as long as you ensure that
you set both of these fields.) At the MTCC:
1. Enable the host flag on the Console Configuration screen.
14-3
2. Enter the RNI node number in the Host Report Data field on the Batch
Configuration screen. (The RNI node number must be the node number of the
RNI device that connects to the DeltaV Operate for RS3 Operator Station.)
Note
You can enter a backup RNI node number on the Batch Configuration
screen.
3. Start the batch recipe on the Batch Run screen
The first time you execute a Classic Batch recipe you must start and execute
the recipe from the Batch Run screen on the MTCC console. This will ensure
that you can receive ABC Batch messages from the batch faceplate (BFACE).
4. Verify that the DeltaV Operate for RS3 Operator Station node ownership is
configured for the Control File nodes and MTCC nodes associated with the
Batch.
The following procedure defines how you enable ABC Batch messaging on a
system running ABC Batch software. Again, at the MTCC:
1. Enable the host flag on the Console Configuration screen
2. Enter an RNI node number in the Host Report Data field on the Batch
Configuration screen. (The RNI node number must be the node number of the
RNI device that connects to the DeltaV Operate for RS3 Operator Station.)
Note
You can enter a backup RNI node number on the Batch Configuration
screen.
3. Start the batch recipe on the Batch Run screen
The first time you execute an ABC Batch recipe you must start and execute the
recipe from the Batch Run screen on the MTCC console. This ensures that you
will receive ABC Batch messages when you start a recipe from the batch
faceplate (BFACE).
4. Verify that the DeltaV Operate for RS3 Operator Station node ownership is
configured for the Control File nodes and MTCC nodes associated with the
Batch.
5. Ensure that the Batch Configuration stored within the ABC Batch recipe is
current. (The host reporting data field must contain the proper RNI node
number.)
After you create an ABC Batch recipe, the entire content of the Batch
Configuration screen is stored in an ABC Batch recipe. Once you configure and
14-4
store the parameters of the Batch Configuration screen, the recipe will run based
on the Batch Configuration information that appears on the Batch Configuration
screen.
Note
You are required to update the Batch Configuration of any previously
existing ABC Batch master/control recipe that you want to use to
monitor ABC Batch messages. More specifically, you must update the
Host Report Data fields for each exiting recipe.
ABC Batch Messages
There are a number of ABMs (ABC Batch Messages) that DeltaV Operate for RS3
Operator Station can filter and display in the Journal Viewer. The table below
identifies each ABM and briefly describes when each of these messages are sent.
For more information about each message, refer to the Journal Viewer online help.
ABC Batch Message
Main Recipe Start
Description
The Main Recipe Start message is sent when:
A working recipe, which originates from a console node via an operator
action, begins to execute.
Or

A working recipe begins from an executing script via the RBL functions
begin_recipe and run_recipe
For an operator initiated start, a working recipe begins when the Start button
is selected. An RBL function start begins when the RBL function is
executed.

Main Rec Start
Environment
The Main Recipe Start Environment message is sent following a Main
Recipe Start message. It is not included as part of the Main Recipe Start
message because of size limitations for PeerWay messages.
Main Recipe End
The Main Recipe End message is sent when a working recipe stops
executing because of one of the following:

Normal processing of all icons

Killing the Main Recipe (i.e. parent task) via the kill_task RBL instruction

Finishing the Main Recipe via the RBL instruction finish

Wiping the batch
Unit Recipe Start
The Unit Recipe Start message is sent when a unit recipe begins to
execute.
14-5
ABC Batch Message
Description
Unit Recipe End
The Unit Recipe End message is sent when a unit recipe concludes
because of:

Normal processing of all icons

Killing the Unit recipe (i.e. parent task) via the kill_task RBL instruction

Finishing the unit recipe via the finish RBL command
Recipe Locals
The Recipe Locals message is sent at the beginning of an ABC Batch
recipe. There are ten sets of LocalValue and LocalDescription aspects.
Recipe State Change
Occur
The Recipe State Change Occur message is sent when a Working, Main, or
Unit Recipe changes state (i.e. kill, stop, abort, hold, or resume) because of
operator intervention or an RBL script.
Recipe Mode Change
Occur
The Recipe Mode Change Occur message is sent when a Working, Main, or
Unit Recipe changes mode (i.e. static, restart, or qrestart) because of
operator intervention. The message indicates potential working recipe
configuration changes (i.e. icon/link add, modify, delete and parameter
value changes).
Unit Process Icon Start
The Unit Process Icon Start message is sent when a unit-process (main)
icon begins to execute.
Unit Recipe Icon Start
The Unit Recipe Icon Start message is sent when a unit-recipe icon begins
to execute.
Operation Icon Start
The Operation Icon Start message is sent when an operation icon begins to
execute.
Material Icon Start
The Material Icon Start message is sent when a material icon begins to
execute.
Communication Operation
Icon Start
The Communication Operation Icon Start message is sent when a receive
operation or a send operation icon begins to execute.
Execute Icon End Occur
The Execute Icon End Occur message is sent when one of the following
icons complete execution.

Unit Process Icon Start

Unit Recipe Icon Start

Communication Operation Icon Start

Operation Icon Start

Material Icon Start
Label Icon Occur
The Label Icon Occur message is sent when a label icon is executed.
Decision Icon Occur
The Decision Icon Occur message is sent when a decision icon is executed
Goto Icon Occur
The Goto Icon Occur message is sent when a Goto icon is executed.
14-6
ABC Batch Message
Description
Start Unit Recipe Icon
Occur
The Start Unit Recipe Icon Occur message is sent when a start unit recipe
icon is executed.
End Icon Occur
The End Icon Occur message is sent when an end icon (for either a main or
unit recipe) is executed.
Null Icon Occur
The Null Icon Occur message is sent when a null icon is executed.
Icon State Change Occur
The Icon State Change Occur message is sent when an icon changes state
(i.e. next, retry, stop, abort, hold, resume, block, or unblock) due to operator
intervention or an RBL script.
Script Occur
The Script Occur message is sent when a script begins execution.
Parameter Occur
The Parameter Occur message is sent when private script variables are
initialized from the operation parameters.
Property Occur
The Property Occur message is sent when a putmaterial or a getmaterial
RBL function is executed.
Ownunit Start
The Ownunit Start message is sent when an ownunit RBL function is
executed.
Ownunit End
The Ownunit End message is sent when disownunit RBL function is
executed.
Logunit Start
The Logunit Start message is sent when a logunit RBL function is executed.
Logunit End
The Logunit End message is sent when an unlogunit RBL function is
executed.
Input Notification Occur
The Input Notification Occur message is sent when a prompt, reprompt,
notify, or renotify RBL statement is executed.
Input Occur
The Input Occur message is sent when the operator presses the Enter key
in response to an input, input$, or inputp RBL statement.
Align On Occur
The Align-on Occur message is sent when the align_on RBL function is
executed.
Classic Batch Start
The Classic Batch Start message is sent when a classic batch begins
execution.
Classic Batch End
The Classic Batch End message is sent when a classic batch ends
execution because of the completion of:

A kill_task RBL instruction

A Kill command via the Batch Run Screen

A finish RBL command
14-7
ABC Batch Message
Description
Classic Batch State
Change
The Classic Batch State Change message is sent when a classic batch
changes state (kill, wipe, hold, stop, abort, continue, or resume) because of
operator intervention or RBL script.
Chain Start
The Chain Start message is sent when a chain RBL function is executed.
NOTE: This applies to a classic batch only.
Chain End
The Chain End message is sent when an endchain RBL function is
executed.
NOTE: This applies to a classic batch only.
Generate Numeric
Variable Occur
The Generate Numeric Variable Occur message is sent when a gennumlog
Generate String Comment
Occur
The Generate String Comment Occur message is sent when a genstrlog
Operator Comment Occur
The Operator Comment Occur message is sent when an operator
interactively enters a comment into the Operator Comment field on a
Working Recipe Screen.
Move Material Occur
The Move Material Occur message is sent when the movemtl RBL function
is executed
Flush Material Occur
The Flush Material Occur message is sent when the flushmtl RBL function
is executed
Record Actual Occur
The Record Actual Occur message is sent when the rec_actual RBL
function is executed
Online Help
The Journal Viewer online help provides detailed information about the ABM
functionality and message types. You can access general ABM reference
information by selecting Help Topics from the Help menu. For descriptions of
fields, screen areas, and buttons, use context-sensitive help (see Context-sensitive
Help in Chapter 8).
14-8
Appendix A ControlBlock and I/O Block Attributes
This appendix lists the ControlBlock and I/O Block attributes used in DeltaV
Operate for RS3 Station tagnames. A tagname consists of values that enable the
process graphic to link to the RS3 PeerWay system and read and write data. Refer
to the RS3 Attributes online help for a description of the tagname format.
Note
The Batch attributes are listed in Chapter 13.
Supported ControlBlocks
DeltaV Operate for RS3 software supports the RS3 ControlBlocks shown in
Table A-1.
Table A-1 Supported ControlBlocks
Control
Block
Description
ATPID
PID controller with autotuning capability
D
Derivative control only
DASMC
Auto Sequence Motor Controller: use with single-speed electric motor
that is one of several that must be started in a defined sequence.
DASVC
Auto Sequence Valve Controller: use with a valve that is one of
several valves that must be opened in a defined sequence.
DDDMC
Dual Direction Motor Controller: use with reversible electric motors.
DDSMC
Dual Speed Motor Controller: use with two-speed electric motors.
DISC
Discrete: block output Q is determined by the operator or by
configured equation.
DMC
Motor Controller: use with single-speed electric motors.
DMVC
Motorized Valve Controller: use with motorized valve controller that
requires a contact closure to change but not maintain position.
DT
Dead Time: provides a configurable delay time.
DVC
Valve Controller: use with valves that require contact closure to
maintain an open or closed position.
I
Integral control only
ControlBlock and I/O Block Attributes
A-1
Table A-1 Supported ControlBlocks
Control
Block
Description
LL
Lead Lag: provides one lead term and two lag terms for modeling
process dynamics.
MAN
Manual: output Q set by operator.
MATH
User-defined calculations determine block output or any continuous
input.
P
Proportional control only.
PD
Proportional and Derivative control.
PI
Proportional and Integral control.
PID
Proportional, Integral, and Derivative control.
PLI
Piecewise Linear Interpolator: approximates a curve with a series of
straight line segments.
POLY
Polynomial: approximates a curve with a polynomial equation.
RB
Ratio/Bias: provides adjustable ratio and bias.
SS
Signal Selector: a one-of-N switch that can function in the input or
output side of a loop.
TOT
Stack Totalizer: integrates an input until reset. On reset, the value is
pushed onto a stack.
TOTSP
Setpoint Totalizer: Integrator whose output resets to zero when the
output reaches a high limit.
VLIM
Velocity Limiter: The output is a rate-limited function of the input.
ControlBlock Attributes
The tables on the following page lists ControlBlock attributes you can use in
tagnames to read specific items of block data. Each attribute represents a field in a
block. Some attributes reference data only in specific types of blocks, while other
attributes can reference data in many different types of blocks. The table describes
each attribute and indicates which types of blocks it can read.
A-2
The system uses the following mnemonics to indicate the ControlBlock functions:
CB Mnemonic
Includes These Blocks
Description of the Function
All
All blocks (includes MAN
and DISC)
All ControlBlock types
ATPID
ATPID
Autotune PID Block
DMC
DMC, DASMC, DDDMC,
DDSMC
Discrete Motor Control
DVC
DVC, DMVC, DASVC
Discrete Valve Control
DT
DT
Dead Time
LL
LL
Lead Lag
MATH
MATH
User-defined
PID
P, I, D, PI, PD, PID
Proportional and/or Integral and/or
Derivative
PLI
PLI
Piecewise Linear Interpolator
POLY
POLY
7th Order Polynomial
R/B
R/B
Ratio/Bias
SS
SS
Signal Selector
TOT
TOT, TOTSP
Stack and/or Setpoint Totalizer
VLIM
VLIM
Velocity Limiter
For a list of attributes sorted by ControlBlock type, open the RS3 Attributes help
from the Expression Builder help.
Attribute
Description
Used With
*ACTION
Action of controller output (Q):
0 reverse, 1 direct (default).
PID
*ALMPRIOR
Alarm priority for critical and process alarms.
All
*AUTOLOCK
Indicates if block is locked in Auto mode: 0 no, 1 yes.
All
*BIBARFUL
A bias value represented as a 0 on the continuous faceplate bias
bar: from -999999 to 999999.
RB
A-3
Attribute
Description
Used With
*BIBARZER
The maximum rate at which the ratio can be changed: from.0000
to 999999.
RB
*BIHILIM
Bias high limit.
PID
*BILOWLIM
Bias low limit.
PID
*BIRTLIM
Bias rate limit.
PID
BLKADDR
The hardware address of the block.
All
BLKDESC
A text description of the block.
All
BLKMODE
Block mode states.
All
BLKTAG
Block tag for 16 character tags.
All
*BLKTYPE
Type of controller processor blocks.
All
*CFMCLS
Confirm Close.
DVC
*CFMCLSIG
Ignore Confirm Close.
DVC
*CFMOFF
Confirm Off.
DMC
*CFMOFFIG
Ignore Confirm Off.
DMC
*CFMONIG
Ignore Confirm On.
DMC
*CFMOPN
Confirm Open.
DVC
*CFMOPNIG
Ignore Confirm Open.
DVC
*CONTGAIN
Controller Gain
PID
*CQ_HILIM
Q (output) high limit.
All
*CQ_LOLIM
Q (output) low limit.
All
You can use the following attributes to reference block data associated with continuous registers A
through Q. For continuous registers A through Q, substitute one of these registers for the x in the
attributes below. For example, in place of Cx, use CA, CB, CC, CD ... CQ.
*Cx
A continuous block value (registers A though Q).
All
*Cx_ADVHI
High output value at which advisory alarms are generated.
All
*Cx_ADVLO
Low output value at which advisory alarms are generated.
All
*Cx_CRTHI
High output value at which critical alarms are generated.
All
*Cx_CRTLO
Low output value at which critical alarms are generated.
All
A-4
Attribute
Description
Used With
*Cx_DBAND
Input alarm range.
All
*Cx_ENGMX
Maximum range value in engineering units for display scaling.
All
Cx_ENGUN
Engineering units of measure.
All
*Cx_ENGZE
Minimum range value for display scaling.
All
*Cx_HOLD
The hold output action if a bad input signal is received:
no, yes.
All
Cx_LINK
The tag number, address, value, or function of the input link.
All
*Cx_RATE
Maximum rate at which input can change before an alarm.
All
*CUTOFFTP
Cutoff type values that are totalized: 0=Signed, 1=Band.
TOT
*CV
The ControlBlock output (Q) variable.
All
You can use the following attributes to reference block data associated with discrete registers A through
P. For discrete registers A through P, substitute one of these registers for the x in the attributes below.
For example, in place of Dx_IMSGP, use DA_IMSGP, DB_IMSGP, DC_IMSGP, DD_IMSGP...
DP_IMSGP.
*Dx_IMSGP
Message pair associated with the discrete input.
All
*Dx_IN
Discrete input value or message pair text.
All
Dx_LINK
Discrete input link.
All
*Dx_OMSGP
Message pair associated with the discrete output.
All
*Dx_OUT
Discrete output value or message pair.
All
*Dx_STPMD
Output step mode.
All
*DBANDERR
Deadband error. Output does not change unless the output is
greater than the deadband error.
PID
DERIVACT
Derivative action type.
PID
*DERIVTM
Derivative filter time in seconds.
PID
DFACE[n]
The number of a line on the discrete faceplate. The attribute
requires an index from 1 to 17. For example, DFACE[7].
All
*DRVFLTTM
Filter time used by the derivative term to filter the following
variable types: PV, LS, RS, FF, E to O, 0 S to 999999 H.
PID
*DTDEADTM
Actual current dead time.
DT
A-5
Attribute
Description
Used With
FALLDVTR
The deviation trigger. When (Q-PV)> deviation trigger, the Fall
High Limit is used.
VLIM
FALLHILM
The rate limit used to decrease direction when the deviation limit
is exceeded: None, PV, B to O, or -999999 to 999999.
VLIM
FALLLM
The normal rate limit in the decreasing direction: None, PV, B to
O, or -999999 to 999999.
VLIM
*FFGAIN
Feed forward term gain.
PID
*GAPVALUE
Gap value of PID block.
PID
*HRNENBLE
Alarm horn enable toggle.
--
*HRNSIL
Silence alarm horn.
--
*HRNSILTM
Alarm horn silence time.
--
*INTEGTM
Integral action time constant (reset time).
TOT
*INTRLK
Interlock enabled status: no, yes.
DMC, DVC
*INTRLKIG
Interlock ignore status: no, yes.
DMC, DVC
*INTRMSTP
DMC Motor Immediate stop enabled status: no, yes.
DMC
*KAGAIN
Gain on input A.
DT, LL
*KBGAIN
Gain on input B.
LL
*KCGAIN
Gain on input C.
DT, LL
*KGAIN
Gain on input A.
TOT
*LAGTM1
First-order lag time constant.
LL
*LAGTM2
Second-order lag time constant.
LL
*LEADTM
Lead time constant.
LL
*LOCUTOFF
Totalizer low cutoff value
TOT
LSPVTRK
Track input source of tracking signal: 0=none, 1=A, 2=B, 3=C,
4=D, 5=E, 6=F, 7=G, 8=H, 9=I, 10=J, 11=K, 12=L, 13=M, 14=N,
15=O
PID
*MAXGAIN
Tracking type, max gain back calculate (0)
MATH
*MTOPTION
Options for the PID algorithm.
PID
*NUMINPUT
Number of inputs used by the selector.
SS
A-6
Attribute
Description
Used With
NODEOWN[n]
Indicates whether the node number is owned. 1 = owned.
Specify node number within brackets.
For example: NODEOWN [5]
--
*OPRENADV
Operator permission to enter advisory alarm points: no, yes.
All
*OPRENCRT
Operator permission to enter critical alarm points: no, yes.
All
*PLNTUNIT
Plant unit to which the block is assigned.
All
PLYCOEFF[n]
Coefficient (K) for a polynomial from K0 to K7. The attribute
requires an index from 0 to 7. For example: PLYCOEFF[7].
POLY
*PREBIAS
Pre-bias term or ratio/bias equation.
RB
*PROPACT
Variable used by the PID algorithm to calculate the P term: SP,
PV, ER.
PID
*PROPBAND
Proportional band: SP, PV, Err.
PID
PUOWN[n]
Indicates whether the plant unit is owned. 1 = owned.
Specify PU within brackets. For example: PUOWN [5]
--
*RATGAIN
Ratio gain term of the ratio/bias equation.
RB
*RATHILIM
Ratio high limit value.
PID
*RATLOLIM
Ratio low limit value.
PID
*RATRTLIM
Maximum rate at which ratio value can be changed.
PID
*RETRY
Number discrete motor/valve retries.
DMC
RISEDVTR
Rise deviation trigger value.
VLIM
RISEHILM
Rise rate limit when deviation trigger is exceeded.
VLIM
RISELM
Normal rise rate limit.
VLIM
*SAMPLETM
Sample time interval between ControlBlock output updates.
All
*SECLCKUP
Motor/valve lockup on security.
DMC, DVC
*SELNUM
The nth highest signal value to be selected
SS
*SIZEDYN
Amount of dynamic space used by the block and the total amount
of space that the block uses.
All
*SIZESTAT
Amount of static space used by the block and the total amount of
space that the block uses.
All
A-7
Attribute
Description
Used With
*SIZETOT
Amount of static and dynamic space used by the block and the
total amount of space that the block uses.
All
*SPHILIM
Local setpoint high limit: None, PV, LS RS, FF, E to O, or -999999
to 999999.
PID
*SPLOLIM
Local setpoint low limit. Units are same as local setpoint.
PID
*SPRTLIM
Local setpoint rate limit in units/seconds.
PID
TRACKINP
Input source of tracking signals: 0=A, 2=B, 3=C, 4=D, 5=E, 6=F,
7=G, 8=H, 9=I, 10=J, 11=K, 12=L, 13=M, 14=N, 15=O
ATPID, LL,
MATH, PID,
POLY, RB, SS
*TRKBAND
Value, in percent, that limits the amount of windup in deselected
controllers.
SS
TRKPV
Back tracking selection for the PV (A) input.
VLIM
Supported I/O Blocks and Attributes
The tables on the following page lists I/O block attributes you can use in tagnames.
The table describes the attribute and indicates which types of blocks it can read.
The system uses the following mnemonics to indicate the I/O block functions:
A-8
I/O Mnemonic
Description of the Function
All
All I/O block types
AIB
Analog Input Block
AOB
Analog Output Block
CIB
Contact Input Block
COB
Contact Output Block
DIB
Discrete Input Block
DOB
Discrete Output Block
MIB
Multiplex Input Block
PLCB
PLC Block
SIB
Smart Transmitter Input Block
TIB
Temperature Input Block
VIB
Value Input Block
For a list of attributes sorted by I/O Block type, open the RS3 Attributes help from
the Expression Builder help.
Attribute
Description
Used With
*ALMPRIOR
Alarm priority for critical and process alarms
All
*AUTOLOCK
Indicates if block is locked in Auto mode: 0 no,
1 yes
All
BLKADDR
Hardware address of the block
All
BLKDESC
Text description of the block
All
BLKMODE
Current block mode.
NOTE: In Simulate mode, for PLCBs only, a
control block simulates the PLCB address
register and the block functions drive the block
output. There is also a FAIL indication that
appears in the Mode field when there is no
communication.
All
BLKTAG
Block tag for 16 character tags
All
*BLKTYPE
Type of controller processor blocks
All
*CV
Block output in engineering units
All
F_PLC_UF
Contains all of the flag values of the PLCB
PLCB
F_PLC_UFx
Contains the flag value for a user-specified flag
from A through P;
where x designates a flag from A - P
PLCB
*IO_xCPLC
When attribute: State in which an alarm is
generated. (Unique to each flag)
PLCB
IO_xDPLC
Alarm Descriptor: Text to be displayed when
the alarm is generated. (Unique to each flag)
PLCB
*IO_xEPLC
Event number: (Only shown when event
selected as alarm type) (Unique to each flag)
PLCB
A-9
A-10
Attribute
Description
Used With
*IO_xFPLC
Color selection for the flag name. (Unique to
each flag)
PLCB
IO_xNPLC
FlagName: This attribute is a 16-bit, bit
descriptor for a through p. (Unique to each flag)
PLCB
*IO_xSPLC
BacklightState: State in which the bit descriptor
appears in reverse video. (Unique to each flag)
PLCB
*IO_xTPLC
AlarmType: Type of alarm to generate. (Unique
to each flag)
PLCB
IO_BLKIN
Block input in engineering units
All
IO_BLKMD
Input/output block mode
PLCB
*IO_BLKOU
Block output in engineering units
All
IO_ENGMX
Output maximum scaling value: Available for
scaled PLCBs exclusively
All
IO_ENGUN
Output units text: Available for scaled PLCBs
exclusively
All
IO_ENGZE
Output zero scaling value: Available for scaled
PLCBs exclusively
All
IO_MSGP
Message pair ID
CIB, COB,
DIB, DOB
*IO_PLCAD
PLC word address
PLCB
IO_PLCAF
Alarm flags: 0000-FFFF
PLCB
*IO_PLCCP
Port: Identifies the communication port that the
PLCB uses
PLCB
*IO_PLCDT
DataType: Type of word that is being read from
or written to the PLC
PLCB
*IO_PLCFV
PLCValue: Value from PLC (For data types
other than flags)
PLCB
*IO_PLCN
PLCNumber: Address of the PLC with which
this block communicates
PLCB
*IO_PLCRO
Read: Indicates if data is to be read from the
PLCB
PLCB
Attribute
Description
Used With
*IO_PLCSI
SimTag/Address: Tag or address of the
ControlBlock from which data is obtained when
in simulation mode
PLCB
IO_PLCSS
SimSubTag/Address: Tag or address suffix of
the ControlBlock from which data is obtained
when in simulation mode
PLCB
IO_PLCST
SampleTime: Interval (in seconds) between the
PLC read/write cycles
PLCB
*IO_PLCSV
SourceValue: value from Source (For data
types other than flags)
PLCB
*IO_PLCWF
WriteFilter: Invokes a logic step that enables
the write of a PLCB to occur at a configured
time, rather than at the default sample time of
the controller. (normal, filter, no)
PLCB
IO_PLCWM
PLCWriteMask: Configurable value that
provides a means to write to selected bits of the
PLC register. Default if FFFF, indicating I/O can
modify all 16 bits of the PLC register.
PLCB
IO_PLCWV
ValueToPLC: Hexadecimal representation of
the 16 bits of data currently being sent to the
PLC
PLCB
*PLNTUNIT
Plant unit to which the block is assigned
All
*PLC_ADHI
Advisory High Alarm: (scaled PLCB tag status
function screen attributes)
PLCB
*PLC_ADLO
Advisory Low Alarm: (scaled PLCB tag status
PLCB
*PLC_CRHI
Critical High Alarm: (scaled PLCB tag status
PLCB
*PLC_CRLO
Critical Low Alarm: (scaled PLCB tag status
PLCB
*PLC_DBND
Deadband: (scaled PLCB tag status function
screen attributes)
PLCB
*PLC_UFx
PLCUserFlags: Dynamic bit states of the PLC
flags
PLCB
SIZEDYN
Dynamic size: Indicates the amount of dynamic
space (bytes) used
All
A-11
Attribute
Description
Used With
SIZESTAT
Static size: Indicates the amount of static space
(bytes) used
All
SIZETOT
Total size: Indicates the amount of total space
(bytes) used
All
x Represents the bit A through P.
System and User Flag Attributes
This section provides a brief explanation of flags and flag notations.
Introduction
When you link a block to a ControlBlock, the system will continuously pass
information packets to the ControlBlock. These packets contain 64-bit
representations of block and status information that consists of system flags, user
flags, and an analog value or variable.
System flags generally contain information such as block alarm status, hold
forward status, valid data status, or the current mode. User flags generally contain
alarm information. The analog value consists of continuous inputs A through O or
the continuous output Q. The figure below shows the components of a link packet.
System Flags: xxxx xxxx xxxx xxxx; Where x is 0 or 1
User Flags: xxxx xxxx xxxx xxxx; Where x is 0 or 1
Value or variable: A through O, Q
ponm lkji hgfe dcba
|||| |||| |||| ||||
xxxx xxxx xxxx xxxx
System and user flags exist for I/O blocks and ControlBlocks. All of the linked
information, including system and user flags, is stored in the destination
ControlBlock input registers. You can test one or all system and user flags in the
destination ControlBlock logic and obtain information about the source block or
the destination ControlBlock input registers.
Each supported block type provides a comprehensive list of system and user flags.
You can access these flags as attributes from DeltaV Operate (configure mode).
This enables you to animate graphic picture objects based on the values of the
flags. There are attributes that represent each individual system or user flag, and
A-12
attributes that represent the decimal equivalent for all of the flags (system or user)
for a specific ControlBlock register.
Testing I/O Block Flags
You test I/O block flags by linking the I/O block to a continuous input register of a
ControlBlock. The I/O block sends its system and user flags to the ControlBlock
where you can test the flags as follows:

The ControlBlock continuous input contains the linked system flags of the I/O
block; d (Valid Data) and g (Hold Forward), and the ControlBlock link system
flags, a-c, e-f, and h-p.

The continuous input user flags of the ControlBlock contain the alarm status
information for the linked flags of the I/O block.
Testing ControlBlock Flags
You can test ControlBlock flags by either linking the continuous input register or
continuous output register of a source ControlBlock to the continuous input
register of a destination ControlBlock, or by testing flags within a block. For
example:

If you link a continuous input link (A - O) of a source ControlBlock to a
continuous input link (A - O) of a destination ControlBlock, the source
ControlBlock sends its continuous input user and system flags to the
destination ControlBlock’s continuous input register.

If you link the continuous output link (Q) of a source ControlBlock to a
continuous input link (A - O) of a destination ControlBlock, the source
ControlBlock sends its discrete outputs to the destination ControlBlock’s
continuous input user flags.
You can access the ControlBlock continuous output system flags from within a
ControlBlock. The individual system flags of the ControlBlock continuous output
contain rate limit, output limit, tracking, and ControlBlock mode information. All
continuous output system flags of the ControlBlock contain alarm, and
ControlBlock mode information.
A-13
Accessing System and User Flags
You can access and read system and user flags from the DeltaV Operate
application. You can use the following attributes to link and animate any type of
object in your process.
Cx_SYSF
The overall value of ControlBlock continuous input system
flags (x = A through O)
Cx_SYSFy
You use the y value to look at the individual bits of the
ControlBlock continuous input system flags
(y = a through p; x = A through O)
Cx_USRF
The overall value of ControlBlock user flags
(x = A through O and Q)
Cx_USRFy
ControlBlock user flags
(y = a through p; x = A through O and Q)
CQ_TSYSy
ControlBlock continuous output system flags
(y = a through p)
CQ_SYSFL
The overall value of ControlBlock continuous output system
flags
NOTE: For more information about testing individual system flags, refer to
Chapter 7, Section 3, of the RS3 ControlBlock Configuration Manual.
Using Aspects in Tagnames
Aspects define elements of data in an RS3 block attribute. For example,
/PCTCV in the following tagname returns the unscaled percentage value (0-100)
for register A:
Tagname: FIX32.THISNODE.DEVICEA.F_CA/PCTCV
For a list of valid aspects for each I/O Block and ControlBlock type, open the RS3
Attributes help from the Expression Builder help. Click an I/O Block or
ControlBlock to see the valid attributes. Click a block attribute to see its valid
aspects.
A-14
Available aspects include:
Aspect
Description
/ALIAS
Alias. Use ALIAS to return the alias of a label. For example,
in a PID block, the ‘A’ register’s alias is ‘PV’.
/BGCLR
Background color. Corresponds to the 16 original RS3
system colors. Used to indicate background color of a
message pair.
/BLINK
Blink State. Use BLINK to return a Boolean value: 0=no
blink, 1=blink. BLINK is useful in scripts to determine an
alarm condition.
/COLOR
Foreground color. Use COLOR to return a value (1 to 16),
which corresponds to the 16 original RS3 system colors.
/CV
Current Value. If no aspect is specified, CV is the default
aspect. In registers that have scaled values, CV is the
scaled value. For unscaled values, use PCTCV.
NOTE: This aspect is not the same as the CV attribute,
which returns the output value of the block.
/DATAQ
Data quality. Use DATAQ to return a quality value for an item
of data. For example, if the RNI™ device stops
communicating with the PeerWay, the graphic may not
refresh values. Quality values include:
0 - Valid data
1 - Data not valid
2 - Cannot access block
3 - Cannot access PeerWay
/LABEL
Label. Use LABEL to return the character label associated
with an attribute. For example, the a register’s label is ‘a’;
the hold value’s label is ‘hold’.
/LINKNAM
Shows the link name of a link on the RS3 Continuous Links
Screen. This aspect can only be used with the ENGMX and
ENGZE attributes as follows: .A_ENGMX/LINKNAM or
.A_ENGZE/LINKNAM.
/PCTCV
Percent Current Value. In registers that have unscaled
values (0-1), use PCTCV to return the current value as a
percent (0-100). For scaled values, use CV.
/RAWCV
Raw Unscaled Value. In registers that have unscaled
values, use RAWCV to return the current unscaled value
(0-1).
A-15
A-16
Aspect
Description
/STLEN
String Length. Use STLEN to return the maximum string
length of ASCII attributes (A_).
/WRITE
Write permission. Use WRITE to return write permissions for
RS3 fields and your login permissions. Write is expressed
as a Boolean value:
0 - No write permission
1 - Write permission
Appendix B System Planning and Hardware
Installation
This appendix is divided into two major subsections:

Planning a Process Network

Hardware Installation
This appendix covers only the hardware and procedures specific to DeltaV Operate
for RS3 systems. For information on installing hardware that is common to DeltaV
systems and DeltaV Operate for RS3 systems (workstations, hubs, switches, and
so on) refer to the DeltaV documentation.
Hardware installation of the RNI™ device is also covered in the RS3™ Site
Preparation and Installation Manual (SP). RNI service issues are covered in the
RS3 Service Manual (SV), Volume 2.
Other third-party components, such as printers, monitors, routers, and hubs are
typically shipped with user and installation manuals.
Planning an RS3 Process Network
The DeltaV Operate for RS3™ network is the combination of DeltaV and RS3
hardware and software that allows an operator to control both DeltaV and RS3
systems from a single DeltaV Operator Station.
DeltaV Operate for RS3 Operator Station Network
The figure below shows one way to implement a DeltaV Operate for RS3 network
with a DeltaV network. Note that to simplify the figure not all DeltaV network
components and redundant components are shown. Note also that the maximum
workstation load on a single RNI device is:

1 Configuration/Operator workstation

2 Operator workstations
System Planning and Hardware Installation
B-1
DeltaV
Operate
for RS3
Configuration/
Operator
Station
DeltaV
Operate
for RS3
Operator
Station
PC with third
party
application
software
DeltaV
Operator
Station
DeltaV
ProfessionalPLUS
Station
Ethernet
RS3 Process LAN
DeltaV Control Network
Hub
Hub
Hub
DeltaV
Controller
RS3
Network
Interface (RNI)
RS3
Network
Interface
Switch
PeerWay
Router
Multi-tube
Command
Console
Control
File
Plant Network
I/O
An RS3 process network is an Ethernet network dedicated to RS3 process control
traffic. A router must be used between the plant network and the process network
to protect the integrity of the mission critical process network from plant network
traffic. When designing your network for applications such as remote
maintenance, DDE connections, and remote printing, you will be required to
install a router between the plant network and the process network.
The router is necessary to keep broadcast traffic on the plant network from
flooding the process network hub, and can also be configured to block specific
network protocols and source and destination addresses, as a means of security.
Emerson Process Management cannot guarantee acceptable performance if this
necessary isolation is not provided.
B-2
The only equipment installed in the RS3 process network should be
workstation(s), RNI devices, and a hub. The RNI (RS3 Network Interface) device
connects the RS3 PeerWay and the process network. The hub connects all
equipment in the process network and supports connection to the plant network
through a router. The workstations and hub should be connected to a reliable power
supply, preferably an uninterruptible power supply (UPS).
The RS3 process network uses Category 5 10BaseT cables (shielded for EMC
compliance) that can be up to 100 meters (328 feet) long. You should consider
having the network installed by an organization skilled in the installation of
Ethernet networks. Cabling problems are the most common forms of trouble with
Ethernet installations. Experienced installers minimize these problems.
At least one workstation on the process network should have:
Note

A CD Read/Write drive for backup of all workstations on the process network.

A printer. The printer should be configured as a shared printer so it can be used
by any workstation on the process network.
Alarm logging should be done on a printer attached to an RS3 PeerWay
command console.
There is a one-to-one relationship between a DeltaV Operate for RS3
Configuration/Operator Station and an RNI device. Each Configuration/Operator
Station is set up to work with a particular RNI device. The RNI device should have
no other responsibilities.
The simplest and most basic process network consists of an RNI device, a
workstation, and a 10BaseT crossover cable. The crossover cable has the transmit
and receive connections reversed, similar to a null modem cable. This places the
workstation on a dedicated Ethernet network, providing a stand-alone workstation
with no communication to any other workstation except through the RS3 PeerWay.
There is no communication path to a plant network.
To be able to back up the hard disk, the workstation must have a CD RW drive. A
printer is optional.
To expand the network add a hub or switch between the RNI and the workstation.
The hub has multiple ports and several workstations can be connected to the hub
with 10BaseT Ethernet cable. The hub is at the center of a star configuration with a
cable running from it to each piece of equipment on the process network. There is
no communication path to a plant network.
You can connect a printer to one of the workstations and configure it as a shared
printer. Any workstation can then use the printer. To be able to back up the hard
B-3
disks of all workstations, at least one workstation must have a CD RW drive. The
workstation with the CD RW drive becomes the backup workstation. It must also
have the appropriate backup software loaded.
Note
Using one hub with multiple Configuration/Operator stations and RNI
devices is not supported. Using one hub per RNI device reduces the
effect of single-point failures. That is, a failure of a single network
component, such as a cable, hub, RNI device, or PC node, will affect at
most one Configuration/Operator station when a relationship of one
hub per RNI device is maintained.
If you require your consoles to communicate with each other, you can
connect the hubs with properly configured switches.
Connecting the process network to a plant network requires special consideration.
A router is required. The equipment required depends on the size, design, and
usage of the plant network, so only general guidelines can be given here. Isolation
is essential, so that a malfunctioning device somewhere in the plant does not affect
the process network.
The system administrator of the plant network will specify the required equipment
and might also specify the addresses to be used for the process network. A large
plant network might be using network management software. If so, the system
administrator may require a network management module in the process network
hub.
Hardware Installation
This section covers installation of the RNI device. Refer to the DeltaV
documentation for information on installing all other network equipment.
The RNI (RS3 Network Interface) device is a node on the PeerWay and a host on
the process network. It serves as a bridge between the networks. The RNI device
gets its boot code and PeerWay identity from its dedicated workstation.
The RNI device can be physically installed whenever convenient, although it
cannot boot up until the workstation BOOTP server is operating. The RNI device
sends a boot request on the Ethernet once per minute until a BOOTP server
responds. The RNI device will not affect the PeerWay until it is booted, because it
gets the PeerWay software and PeerWay address in the boot code.
Install the RNI device as directed in Chapter 8 of the RS3 Site Preparation and
Installation Manual (SP).
B-4
Service issues are covered in the RS3 Service Manual (SV), Volume 2.
The RNI device requires:

DC power source (18-36 V)

Ethernet 10BaseT cable to the hub or workstation

PeerWay drop cables to the PeerWay Tap Box set

Configured BOOTP server on the process network
The RNI device can be installed in a system cabinet, if desired. It can be powered
from the RS3 DC bus.
Caution
Do not connect the RNI device to the PeerWay until it is assigned the correct
node number, and is verified to boot correctly. If the RNI device is not
assigned the correct node number, it will use the last known node number,
which may cause a duplicate-node problem on the PeerWay.
All connections are made to the front of the RNI device as shown below.
Key:
1. Ethernet 10BaseT connector
2. PeerWay B drop cable
3. PeerWay A drop cable
4. Ethernet 10Base2 connector (not used)
5. Console/Serial connector (for monitoring RNI boot process)
6. DC power connector to RS3 DC power bus
The write-on label provides space to record the PeerWay Node address of the RNI
device, the Ethernet host name of the RNI device, and which Ethernet port is in
B-5
use. The MAC Address (machine address) is filled out at the factory. This
is the unique Ethernet address of the RNI device.
B-6
Appendix C RS3 System Administration
This section covers only system administration information specific to DeltaV
Operate for RS3 software. For Windows system administration information, refer
to the Windows documentation. For DeltaV system administration information,
refer to the DeltaV documentation.
The DeltaV Operate for RS3™ Operator Station system administrator is
responsible for:

Managing RS3 user accounts and assigning passwords

Managing RS3 user and group accounts

Managing RS3 networking

Enabling and disabling the RS3 security system

Backing up the system

Adjusting system features with the RNI™ Configuration Utility

Customizing a station with the RS3 Environment Configuration utility (refer
to the utility’s online help)
For detailed information on RS3 Security and managing user and group accounts,
refer to the online manual Implementing Security on DeltaV Operate for RS3.
Caution
All DeltaV Operate for RS3 Operator Station system administration tasks
affect only the workstation used. You must repeat the action on each
workstation or copy files from workstation to workstation to keep the
system consistent. For example, if you register a user on one workstation,
the user can only log onto that workstation, and cannot log onto other
workstations until registered on them.
To keep the system consistent, you can create the security configuration on one
DeltaV Operate for RS3 Operator Station and then copy it to the other DeltaV
Operate for RS3 Operator Stations. You copy the security configuration by using
the Security Configuration application to export the SECURITY.RPT file to each
DeltaV Operate for RS3 Operator Station.
RS3 System Administration
C-1
Upgrading Software Licenses
If you are upgrading your DeltaV Operate for RS3 console software license and are
not making any other hardware or software changes, perform the following steps:
1. For each Configuration/Operator Station and Operator Station you are
upgrading, obtain new license media.
2. Using the correct license media for the Configuration/Operator Station, copy
DORLicense.sig and DORLicense.txt files from the license media to the
C:\FRSI\Netconnect\bin directory.
3. Restart the Configuration/Operator Station computer.
4. Using the correct license media for one of the Operator Stations connected to
the Configuration/Operator Station, copy DORLicense.sig and
DORLicense.txt files from the license media to the C:\FRSI\Netconnect\bin
directory.
5. Restart the Operator Station computer.
6. Repeat steps 4 and 5 on the other Operator Station connected to the
Configuration/Operator Station.
7. Open the RS3DIAG picture on each upgraded computer to verify the new
license information.
Installation Data
Collect the following information for every Configuration/Operator and Operator
Station in your system.:
Department name
_______________
Company name
_______________
Local time zone
_______________
Workstation process network data:
C-2
Name (8 characters or less, letters,
numbers, underscores)
_______________
IP address
___.____.____.___
IP address in hex format
_______________
Subnetwork mask
___.____.____.___
Gateway address
___.____.____.___
RNI process network data:
Name (8 characters or less)
_______________
IP address
___.____.____.___
Subnetwork mask
___.____.____.___
Gateway address
___.____.____.___
MAC address (from RNI device front label)
_______________
RNI PeerWay node number
_______________
RNI password (for Operator Station access to
RNI device)
_______________
Filename pwxxxxxx.cfg
(substitute the RNI name for xxxxxx)
pw_________.cfg
Printer name (for workstations with a printer)
_______________
Passwords for the predefined RS3 user accounts:
ADMIN
_______________
CONFIG
_______________
GUEST
_______________
OPERATOR
_______________
MAINTENANCE
_______________
TUNE LOOPS
_______________
Backing up the System
Backups can be done across the network, from a workstation that does not have a
CD RW drive to one that does.
With any computer system, frequent backups should be performed to preserve data
and work that has been done. Users should consider what they would have to do if
the operator station had a catastrophic failure such as a hard disk drive crash or an
inadvertent deletion of files or directories.
C-3
The likelihood of this occurring may be small but the recovery time will be related
to when the last backups were done on the system.
The DeltaV Operate for RS3 Operator Station system administrator should back up
the contents of each workstation hard disk to writeable CD on a regular basis.
With the operator station, there are several levels of backup:

A complete backup of the system, including the entire operating system with
all files and all directories. This would be done very infrequently because of
the time required to back up the entire hard disk drive. The Operator Station
must be halted in order to do this.

A backup of configuration and picture files, which should be done each time
any changes to the Operator Station configuration have been made.

A backup of the event journal, which is the historical record of alarms and
events and operator changes received by the Operator Station.

A backup of the trend data files, which are used to record process data.
Complete RS3 System Backup
A complete system backup should be performed when a system is first configured
and is in a state where the Operator Station is ready for its normal job function.
Refer to the DeltaV documentation for information on backing up DeltaV
information, which includes operator pictures.
This backup will make a complete copy of the entire hard disk drive, including the
Windows registry. The backup will involve hundreds of megabytes of disk space,
and could take several hours to perform.
In the event of a major system failure, such as a hard disk drive crash, you would
install a new hard disk drive. The next step would be a minimal install of the
system from diskette and CD, to the point where Windows was running. You
would then use the catastrophic backup CD to restore the entire system. This
would get the system back to exactly where it was at the time the backup was done.
Configuration Backup
Before any significant configuration changes are made to a running system, a
backup of the existing configuration files should be made. This would include the
database. Following the configuration changes, a further backup should be done so
that a complete before and after record is preserved.
C-4
The files that should be part of this backup are in:

\FRSI\NetConnect\Database
Note
As part of the normal functions of the Operator Station, the database
can also be backed up using a utility available through the Console
Configuration application. See the online documentation for details.
Note
The Operator Station need not be stopped in order to perform this
backup. The Windows registry needs to be saved as part of the database
backup.
Saving Registry Information
When saving console data you must also save the registry information about the
console configuration:
2. Run Regedit.
Systems\Netconnect\n.nn.nnn\ROS\RS3Glue\DB\PlantUnits.
This backs up the plant unit names displayed in the alarm banner and the
picture associated with the plant units. You can use this file to move plant unit
names between Configuration stations. The Workstation Configuration backup
does not store this information so you must do it separately.
PlantUnits.reg.
Systems.
This backs up the entire registry structure for DeltaV Operate for RS3 for this
computer.
Fisher-Rosemount Systems.reg.
C-5
Journal Backup
During the normal operation of the Operator Station, events, alarms, and operator
changes are recorded in the RS3 Journal. This journal is configured for a specified
maximum size. When it reaches that size, an alarm is generated, indicating that
data may be overwritten. Old Journal files are eventually deleted as new files are
added.
If you want to keep backups of the old data files, periodic backups are required.
Note
The Operator Station need not be stopped in order to perform this
backup. The Windows Registry need not be backed up as part of this
backup procedure.
The files that should be part of this backup are:

C:\FRSI\NetConnect\Journal
and all files and directories in and below this directory tree.
Trend Data Files Backup
During the normal operation of the Operator Station, trending may be configured
and turned on. In order to preserve old trend data files and free up disk space on the
hard disk drive, it is recommended that these files be saved to writeable CD-ROM.
Files are purged after a certain number of days, as selected during the trend assign.
The files that should be part of this backup are:

C:\DeltaV\iFIX\HTR

C:\DeltaV\iFIX\HTRDATA
Report Configuration and Data Files Backup
The files that should be backed up are in the following locations:
C-6

C:\FRSI\RPTDATA

Folders that contain the Report Data files. Check the Destination File Path
field of the SCHEDULE.LST file using MicroSoft Excel
Backup Summary
It cannot be overemphasized how important regular backups are to protecting
engineering investment and important data. Backups should be a way of life and
taken very seriously.
To summarize the various backups that are needed:
Include
Registry?
Stop
Operator
Station?
On major system changes or after new system
installation
YES
YES
Configuration /
Database
After significant configuration changes
YES
NO
Event Journal
Periodically, less than configured journal period
NO
NO
Historical Trend
Data
Periodically, less than the purge date specified in the
Trend assign application
NO
NO
Report Data
Periodically, before deleting files
NO
NO
Backup Type
Frequency
Complete/
Catastrophic
Backup Software
There are two software packages that can be used to perform backups:
Note

Windows Backup - Supplied as part of Windows.

Easy CD Creator 5 Basic - An optional software package.
Installing the Seagate Backup Exec disables the Windows Backup
utility.
Windows Backup
This software package, which comes with Windows, provides all the necessary
backup capabilities for an Operator Station PC.
The disadvantage of Windows Backup is that it does not back up the registry over a
network. Therefore, it cannot be used to back up another PC for complete/
catastrophic or database backups.
For more information on Windows Backup, consult the Windows manuals or
online documentation.
C-7
Installing Other Applications
Install other applications in accordance with their specific installation instructions.
Caution
Emerson Process Management strongly recommends that you install only
those packages actually needed for system operation. We cannot guarantee
correct functioning if unauthorized software is installed.
Excel can be used to format and print reports. Install Excel on any workstation
where reports will be generated.
Changing the Computer Name
Caution
You cannot rename a PC that has the DeltaV Operate for RS3 software
installed. Attempting to do so may corrupt Windows software requiring that
you re-install the operating system.
This subsection outlines the tasks you must perform to rename a computer after
you have installed the DeltaV Operate for RS3 software. To rename a computer:
1. Uninstall the DeltaV Operate for RS3 software.
2. Refer to the DeltaV documentation for information on Renaming
Workstations.
The PC’s name must be eight or fewer characters, start with a letter, and can
contain only letters, numbers, and underscores (_).
3. Re-install the DeltaV Operate for RS3 software.
4. Make sure the new name is entered in the following places:
• In the Local Startup Definition of the System Configuration Utility.
• In the Automatic Login at Startup dialog of the Security Configuration
application.
• In the Connection Setup tab of the RS3 Environment Configuration (on
Operator Stations only).
C-8
Index
A
B
backup
overview C-3
ABC Batch Messages
description 14-5
Batch
attributes 13-2
new alarms 12-7
Accessing System and User Flags A-14
batch input button 7-7
ACK button 7-7
acknowledge button 7-7
batch messages
filtering 14-1
Adobe Acrobat
using 8-1
batch messaging
starting 14-3
alarm
configuration 9-5
messaging 6-3
C
alarm acknowledge
configuration 9-5
alarm broadcast
configuration 9-6
alarm buttons
RS3 7-5
alarm list buttons
RS3 7-6
alarm lists
configuring 7-9
RS3 7-7
alarm states
RS3 7-8
alarms
acknowledging 7-10
clearing 7-10
selecting 7-9, 7-10
attribute 10-6
selecting 10-5
attributes
Batch 13-2
ControlBlock A-3
entering 10-5
I/O Block A-8
configuration 1-4
alarm 9-5
alarm acknowledge 9-5
alarm broadcast 9-6
applications 6-1
console 3-7
message pairs 9-6
node ownership 9-7
plant unit 9-7
plant unit ownership 9-7
RNI 3-9
RS3 environment 3-11
RS3 Journal 9-9
configuration overview 6-1
configure alarm broadcast 9-4
configuring graphics 10-1
console configuration 3-7
continuous faceplate 7-13
ControlBlock
attributes A-3
D
data
lost 7-21
questionable 7-21
Index-1
Data link
inserting 10-4
I
desktop
DeltaV Operate for RS3 7-1
I/O Block attributes A-8
descriptions A-8
testing A-13
device state indicators 7-15
installing software 3-3
discrete faceplate 7-14
display
link limits 10-2
display elements 10-2
dynamic 10-2
static 10-2
display names 10-1
displays
link limits 10-2
J
Journal
schema 12-2
Journal Viewer
configuration 6-5
description 12-1
Message Detail View 14-3
Primary Filter Enhancements 14-2
starting 12-1
documentation, online 8-1
dynamos 10-8
L
link limits 10-2
E
lost data 7-21
Expression Builder 10-3
M
F
message pairs
configuration 9-6
faceplate
batch 13-1
continuous 7-13
discrete 7-14
mnemonics for ControlBlock functions A-3
faceplates
RS3 7-11
N
field 10-6
node ownership
configuration 9-7
modes 7-13
filtering batch messages 14-1
FIX32 10-5
O
G
online
help 8-1
manuals 8-1
graphics
configuring 10-1
Index-2
operator station configuration 9-1
P
S
plant unit
configuration 9-7
security configuration 6-4
plant unit ownership
configuration 9-7
software
installing 3-3
re-installing 4-1
uninstalling 4-1
Q
software setup 5-1
questionable data 7-21
station types 1-4
R
re-installing software 4-1
syntax
named blocks 10-5
tagnames 10-5
reporting 6-4, 11-1
system administration C-1
RNI configuration 3-9
System and User Flag Attributes A-12
RS3
logging in 7-2
RS3 alarm acknowledgement 7-7
T
tag
RS3 alarm banner 7-5
entering 10-5
selecting 10-5
RS3 alarm buttons 7-5
Tag Status screens 7-18
RS3 alarm list buttons 7-6
tagname 10-2
attribute 10-6
entering 10-5
field 10-6
syntax 10-5
tag 10-6
RS3 alarm lists 7-7
RS3 alarm states 7-8
RS3 Batch
alarms 12-7
RS3 communication
enabling 5-9
RS3 environment configuration 3-11
RS3 faceplates 7-11
RS3 Journal
configuration 9-9
RS3 toolbar 7-2
RS3 toolbar buttons 7-3
RS3 user settings 5-14
RS3DIAG Screen 7-16
tagnames
batch tags 10-6
entering 10-5
THISNODE 10-5
trending 6-4, 11-1
tuning parameters 7-20
U
uninstalling software 4-1
User Flags A-12
user settings
restoring from previous 5-17
Index-3
User_ref_RS3.grf 5-14
UserSettings.grf
variables 5-17
Index-4