PID de Controlador Americano

D800002X152
May 2010
Getting Started With Your

DeltaV™ Digital Automation System
Printed in the Republic of Singapore
© Emerson Process Management 1996 - 2010. All rights reserved. For Emerson Process Management trademarks
and service marks, go to http://www.emersonprocess.com/home/news/resources/marks.pdf. All other marks are
property of their respective owners. The contents of this publication are presented for informational purposes
only, and while every effort has been made to ensure their accuracy, they are not to be construed as warranties or
guarantees, expressed or implied, regarding the products or services described herein or their use or applicability.
All sales are governed by our terms and conditions, which are available on request. We reserve the right to modify
or improve the design or specification of such products at any time without notice.
Contents
Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Using the Mouse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Selecting from Menus or Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
What You Need to Get Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Chapter 1 DeltaV System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
DeltaV System Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
DeltaV Software Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Engineering Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Auto-Update Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Configuration Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Continuous Historian Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Control Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Database Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
DeltaV Operate Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
FlexLock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Recipe Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
System Alarm Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
System Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
User Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Advanced Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
DeltaV Neural . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
DeltaV Predict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
DeltaV PredictPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
DeltaV Simulate Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Inspect with InSight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Tune with InSight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Operator Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Batch History View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Batch Operator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
DeltaV Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Contents iii
DeltaV Operate Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
MPC Operate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Process History View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Installation Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Other Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
OPC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
DeltaV Excel Add-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
DeltaV Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
OPC Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Introducing DeltaV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
DeltaV Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
DeltaV Books Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
DeltaV Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Paper Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Technical Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Windows Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Chapter 2 Overview of the Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

A Look Ahead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Scenario for the Tank Process Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Sequential Function Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Operator Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Let’s Get Started! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Chapter 3 Learning About the DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Opening the DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Navigating the DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Opening and Closing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Documentation Convention for DeltaV Explorer Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Exploring the Library Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Function Block Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Module Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
On Your Own. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
iv Getting Started with Your DeltaV Digital Automation System

Chapter 4 Creating and Downloading the Control Strategy . . . . . . . . . . . . . . . . . 4-1
Exercise 1: Creating and Naming Plant Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Exercise 2: Using the DeltaV Explorer to Copy a Module (MTR-101) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Introducing Control Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Parameter Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Exercise 3: Creating a Control Module (XV-101) in Control Studio Using a Library Template. . . . . . . . . . . . 4-7
Opening Control Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Modifying the XV-101 Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Exercise 4: Finishing Steps for All Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Identifying the Operator Pictures Associated with a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Assigning the Module to a Controller Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Saving the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Verifying the Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Exercise 5: Creating a New Module (LI-101) from Scratch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Finishing the LI-101 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Exercise 6: Creating a PID Control Loop (FIC-101) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Looking at the Module in Control Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Modifying Alarms for the PID Loop Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
Finishing the FIC-101 Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Exercise 7: Modifying the Motor Module (MTR-101) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
Removing the Excess Condition Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Specifying Conditions with the Expression Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
Parameter Tagnames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
Interlock Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Finishing the MTR-101 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Exercise 8: Creating a Sequential Function Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
The Sequence for the Tank Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Creating the SFC Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Finishing the SFC Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Exercise 9: Downloading the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
A Look Ahead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Chapter 5 Creating Operator Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

The DeltaV Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Developing a Picture Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
The Overview Picture and the UserSettings File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Navigating to Other Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Switching Between Configure and Run Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Getting Started with DeltaV Operate (Configure Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Toolbars and the Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Color. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Contents v
Line Styles and Fill Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Links, Dynamic Properties, and Parameter References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Creating Datalinks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Switching to DeltaV Operate in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Dynamos . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Creating a Pump Using a Dynamo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Creating a Tank Using a Dynamo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
Finishing the Process Picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Trend Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Setting Previous and Next Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Creating a Pushbutton to Start the SFC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Chapter 6 Using DeltaV Operate in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Main History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
The Standard Buttons in the Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Faceplate and Detail Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Entering Data in User-Changeable Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Acknowledging Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
On Your Own. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Chapter 7 Collecting and Displaying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Continuous Process Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
History Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Continuous Historian and Alarms and Events Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Assign TANK-101 to the Continuous Historian Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Enable History Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Download the Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
View the Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Chapter 8 Configuring the Network, Loading and Assigning Licenses,

and Setting Up User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Configuring DeltaV Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Accessing DeltaV Workstation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
DeltaV Software Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Controller Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Workstation Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Loading and Assigning Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Loading Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Assigning Licenses to Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
vi Getting Started with Your DeltaV Digital Automation System

Downloading the ProfessionalPLUS Workstation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Configuring Other Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Configuring the Controller Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Configuring I/O Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Downloading the Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Setting Up Your First User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Adding a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
The Groups and Keys Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Downloading the Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Contents vii
viii Getting Started with Your DeltaV Digital Automation System
Welcome
Welcome to the Emerson Process Management DeltaV digital automation system.
The DeltaV system offers powerful, easy-to-use software for designing and operating
a process control application. The system uses many standard Windows features to
provide a familiar user interface.
This revision of Getting Started with Your DeltaV Digital Automation System supports
DeltaV Version 10.3 software. For earlier versions of the DeltaV software, retain the
manual applicable to that version.
Important Information
This book is intended for users of a new system, not one that is already controlling a
process. We recommend that you do not perform any tutorial procedures that involve
installation of configuration information into an operational system without fully
considering the impact of these changes.
The first user must log into Windows using the Administrator account. The
procedure for the first user’s logon differs between workgroups and domains. Refer to
the important information in “Setting Up Your First User Account” on page 2-27 for
instructions.
It is assumed that Windows software and the DeltaV software are installed on your
computer and that you are using a new DeltaV system. The Emerson recommended
Windows installation and the DeltaV installation procedure set up your computer to
operate properly with DeltaV software. Do not make any registry changes to your
operating system as these may result in unpredictable behavior.
About this Book

This introduction to the DeltaV software applications will help you get a control
system up and running quickly. It is divided into eight chapters and a Glossary.
 Chapter 1, DeltaV System Overview, introduces basic concepts and terminology
and gives an overview of the system’s applications.
 Chapter 2, Overview of the Tutorials, describes the tutorial exercises in Chapters
3 through 8. The tutorials guide you through the development of a control
Welcome ix
strategy and operator pictures for a simple process example. The scenario for the
process example is described in detail.
 Chapter 3, Learning About the DeltaV Explorer, shows you how to open the
DeltaV Explorer and use the navigation features.
 Chapter 4, Creating and Downloading the Control Strategy, steps you through the
creation of four modules for controlling a tank discharge and a sequential
function chart that defines the process startup sequence.
 Chapter 5, Creating Operator Pictures, introduces the basic tools for using
DeltaV Operate in configure mode and shows you how to create a set of operator
pictures complete with colorful graphics, faceplate and detail pictures,
pushbuttons, and a trend chart.
 Chapter 6, Using DeltaV Operate in Run Mode, shows the operator pictures from
the operator viewpoint and explains how to navigate the pictures, change
operating parameters, acknowledge alarms, and perform other operator tasks.
 Chapter 7, Collecting and Displaying Data, shows how you can gather and display
system and process data using DeltaV tools, such as DeltaV Reporter and the
DeltaV Excel Add-In.
 Chapter 8, Configuring the Network, Loading and Assigning Licenses, and
Setting Up User Accounts, steps you through the procedures for configuring
workstations, controllers, and I/O, and assigning licenses to workstations and
controllers.
 The Glossary is limited to the terms introduced in this book. A more complete
glossary can be found in the DeltaV Books Online.
Assumptions
It is assumed that you are a control engineer getting ready to configure a DeltaV
application. You are familiar with control theory and are somewhat familiar with the
implementation of control systems.
x Getting Started with Your DeltaV Digital Automation System

Documentation Conventions
The following sections contain information on conventions used in this document for
using the mouse and selecting from menus.
Using the Mouse

Instructions for using the mouse follow the conventions below.
 Click means click the left mouse button (unless you are specifically told to click
the right mouse button).
 Double-click means rapidly click the left button twice.
 Drag-and-drop means point to the object, hold down the left mouse button,
point to a new position, and release the mouse button.
In most DeltaV applications, special context menus (also called shortcut menus) are
available when you point to a particular area or object and click the right mouse button.
The menu displayed will vary, depending on the application and where you are
pointing when you click the right mouse button.
Selecting from Menus or Hierarchies

A vertical bar is used to indicate that you should select items in sequence. For
example, to open the DeltaV Explorer application, the instruction would be to click
Start | DeltaV | Engineering | DeltaV Explorer. This means click the Start button,
select DeltaV, select Engineering, and click on DeltaV Explorer.
What You Need to Get Started

If you are the first user of a new DeltaV system, the minimum you need to get started
using the DeltaV system is a ProfessionalPLUS workstation with pre-installed DeltaV
software.
When you turn on your workstation for the first time, you will see a screen telling you
that you need to configure your workstation.
Welcome xi
To be able to use the DeltaV system, the startup steps you need to perform are:
1. Configure the workstation.

2. Load and assign licenses.
3. Download the workstation setup data.

These basic steps are described in Chapter 8. After the three steps listed above are
done, you can go through the other tutorials in this book to get acquainted with the
system.
xii Getting Started with Your DeltaV Digital Automation System

Chapter 1 DeltaV System Overview
This chapter gives an overview of the DeltaV digital automation system. It takes a
brief look at the hardware, describes the basic concepts and terminology, introduces
the major software components, and ends with a summary of the ways you can find
out more about the DeltaV system from the Help and Books Online.
Hardware
The manual, Installing Your DeltaV Digital Automation System, also available as an online
book, describes the DeltaV system hardware and provides instructions for installing
and powering up the system.
The system hardware consists of the following:

 One or more DeltaV workstations
 A control network (optionally redundant) for communication between system
nodes
 Power supplies
 One or more DeltaV controllers (optionally redundant) that perform local
control and manage data and communications between the I/O subsystem and
the control network
DeltaV System Overview 1-1

 At least one I/O subsystem per controller that processes information from field
devices
 System Identifier
The System Identifier, shipped in the License Pack, is a connector that plugs into the
parallel printer port or Universal Serial Bus (USB) on the ProfessionalPLUS
workstation. It gives each DeltaV system a unique identification that allows you to
download changes to the system. Install the System Identifier on the
ProfessionalPLUS workstation before you power up your system. DeltaV systems may
be engineered and configured using a Development System Identifier prior to going
online. DeltaV systems used for training or simulation may use a Multi-Node Simulate
System Identifier. Development and Multi-Node Simulate System Identifiers cannot
be used for online, running systems. Only a User System Identifier can be used with
an online system. Refer to the Knowledge Base for information on converting a
system based on a Development or Multi-Node System Identifier to one based on a
User System Identifier.
DeltaV System Concepts

The DeltaV system helps users create process control systems that are easy to set up,
easy to operate, consistent, and secure. To accomplish these goals, the DeltaV system
uses the following:
 Plug-and-play technology for hardware configuration
 A library of reusable control modules to simplify the initial configuration effort
 Integrated, context-sensitive help and online documentation
 Hardware and software approaches to ensure system security and integrity
Terminology
Control strategies in the DeltaV system are configured in modules. A module, which
is the smallest logical control entity in the system, contains algorithms, conditions,
alarms, displays, historical information, and other characteristics that define the
process equipment. Algorithms are the logical steps that define how the module
behaves. The DeltaV system provides control, equipment, and unit modules.
Generally, a control module contains one uniquely tagged control entity, such as a
control loop or motor, with its associated logic. Defining a module around a single
field device and its related control logic makes it easy to create, download, operate,
debug, and take a single module out of service without affecting other modules.
1-2 Getting Started with Your DeltaV Digital Automation System

Equipment modules coordinate the operation of control modules and other
equipment modules that work together to control related equipment. The algorithm
for the containing equipment module manages the operation of the contained
modules.
Unit modules can be used in non-batch applications to group control modules and
equipment modules for alarm management purposes. For example, alarms for a
specific unit, such as a boiler, can be combined. All control and equipment modules
associated with the unit will be contained within the unit module.
Function blocks are building blocks for creating the continuous and discrete
algorithms that perform the control or monitoring for the process. The DeltaV
Library contains function block templates for analog control (bias/gain, lead/lag,
PID, etc.), Logical, I/O (analog and discrete input/output), and other basic functions.
Each function block contains parameters that can be modified to customize the
algorithm. Algorithms range from simple input conversions to complex control
strategies. Function blocks can be combined into composite function blocks to build
complex algorithms.
In addition to Function Block algorithms, the DeltaV system supports Sequential
Function Charts (SFCs) as well as Command-driven and State-driven algorithms
for control tasks requiring sequencing strategies.
Parameters are the user-defined data used within a module’s algorithm to perform its
calculations and logic. Parameters can be described by the type of information they
provide, such as input or output. Tables listing the parameters and their properties are
included in the Books Online information.
The DeltaV system includes a library of pre-engineered module templates with basic
characteristics. You can customize these library modules or create your own modules
from scratch. Your customized modules can be added to the library, making them
available for reuse in the development of your control strategy.
Modules that work closely together to perform a specific process control function are
typically grouped in an area. An area is a logical division of a plant. Areas typically
represent plant locations or main processing functions. The configuration engineer
determines how to logically divide the plant into areas.
Nodes are physical pieces of equipment on the control network, such as a controller
or a workstation. You control your process by downloading modules in the controller
nodes. The configuration tells the node how to act and what information to receive or
save from the process.
Device Tags represent the instruments, valves, and other field devices. A Device
Signal Tag consists of a specific signal from a device.

Alarms alert the operator that an event has occurred. (Alarms are assigned to
modules.) Typically, you want the operator to perform some action and respond to the
alarm. Alarms can be both visible and audible.
The database contains configuration information and lets you make off-line changes
without affecting the process. Online control algorithm monitoring and modification
are also available.
Following is a diagram showing the DeltaV system’s hierarchical structure.
DeltaV Software Applications

DeltaV system software includes a variety of applications to help you configure,
operate, document, and optimize your process. The primary applications are
categorized as Engineering Tools and Operator Tools. Additional tools are available
for Advanced Control, Installation, and Online Help.
There are several ways to start an application. One is to click Start (in the lower left
corner of your screen), point to DeltaV, point to the category, and click the name of

the application. For instance, to start the DeltaV Explorer, the Start menu selection
would look like the following:
In this book, the instruction for starting the DeltaV Explorer is expressed as “Click
Start | DeltaV | Engineering | DeltaV Explorer.”
Many applications allow quick access to other DeltaV applications through buttons
on their toolbars and through an Applications menu. The following example shows
the Applications menu and some of the toolbar buttons in the DeltaV Explorer.

In the paragraphs that follow, the application’s toolbar button or Start menu icon is
shown next to the description.
Engineering Tools
The main engineering tools are Configuration Assistant, DeltaV Explorer, Control
Studio, and, if you have a license for the batch applications, Recipe Studio. Others
include User Manager, Database Administrator, FlexLock, and System Preferences.
Auto-Update Service
Use the Auto-Update Service to set which files are automatically transferred
from the ProfessionalPLUS workstation to all other workstations after any node is
downloaded.
Configuration Assistant
If you are a first time user, Configuration Assistant is a great tool to learn the
basics of the DeltaV system. Once you become familiar with the configuration
methodology, you will most likely use the DeltaV Explorer.

Continuous Historian Administration
The Continuous Historian Administration application provides tools to

manage Continuous Historian historical data. This application must be run on the
same workstation as the Continuous Historian.
Control Studio
Control Studio is used to design and modify the individual modules and
templates that make up your control strategy. With this application you can
graphically build a control module by dragging items from a palette to the module
diagram. You then “wire the items together” to create an algorithm for the module.

Control Studio supports a range of industry concepts including Function Blocks (for
continuous control) and Sequential Function Charts (for sequential control). You can
mix elements of these control languages within a single control module.
The graphical languages are based on the IEC 61131-3 standard, and function blocks
were developed using the FOUNDATION™ fieldbus standard.
Database Administrator
The Database Administrator tools let users with the necessary administrator
privileges perform database maintenance tasks such as creating, deleting, copying, and
backing up databases.
DeltaV Explorer
DeltaV Explorer, similar in appearance to the Windows Explorer, is an

application that lets you define system components (such as areas, nodes, modules,
and alarms) and view the overall structure and layout of your system.
You can do many things with this application, including:

 Create, copy, or move modules

 Configure system hardware
 Define types and priorities of alarms
 Launch Control Studio and other applications
DeltaV Operate Configure
The DeltaV Operate application functions in two modes. In configure mode,

you use it to build real-time process graphics. In run mode, control system operators
use these graphics in the daily monitoring and maintenance of the process.
In configure mode, you can incorporate scanned plant images, text, graphics,
animation, and sound into the process graphics. A predefined desktop template
simplifies the typical effort of designing operator displays. This application uses pull-
down menus, toolbox buttons, drag-and-drop features, and easy-to-use drawing tools.
It also provides sets of dynamos (reusable graphics, many of which have animation
capabilities) for use in designing operator graphics.

FlexLock
The DeltaV FlexLock application creates dual desktops (Windows desktop and
the DeltaV desktop) on a single workstation to provide both a secure operating
environment and a wide open engineering environment. Access to a desktop is
determined by the current user's privileges.

Recipe Studio
Recipe Studio is used to create and modify recipes. A recipe is a set of

information that uniquely identifies the ingredients, the quantities of ingredients, and
the production equipment required to manufacture a product. A recipe can be as
simple or as complex as you would like to make it. DeltaV Recipe Studio is modeled
after Control Studio.
System Alarm Management
The System Alarm Management application lets you view and work with
alarms within selected areas, units, modules, and Logic Solvers. It provides a way to
efficiently view multiple alarms, enable and disable multiple alarms, and set limits and
priorities on multiple alarms.
System Preferences
System Preferences allows you to tailor the Engineering Tools to hide any
functions that you do not require. Enabling or disabling a function causes the DeltaV
applications to reveal or conceal the applicable menus and choices without adding or
removing any application software.
User Manager
User Manager lets you specify access levels for groups and individuals. You
define the roles users can have (administrator, operator, engineer, and so on) and the
typical privileges and span of control required for each role. Then, when you create
individual user accounts, you specify the role or roles a user will have.
To be able to create or edit control modules, a user needs to have configure privileges.
Similarly, to download configuration changes, a user needs download privileges.

Advanced Control
The advanced control applications are DeltaV Neural, DeltaV Predict, DeltaV
PredictPro, DeltaV SimulatePro (in DeltaV Simulate Suite), Inspect with InSight, and
Tune with InSight.
DeltaV Neural
DeltaV Neural is a collection of tools used to implement neural networks in

DeltaV environments. With DeltaV Neural you can create virtual sensors to monitor
and predict process parameters that are otherwise expensive, difficult, or impossible
to measure directly. Neural networks are sometimes referred to as intelligent or
software sensors. DeltaV Neural consists of:
 Neural Network (NN) function block

 Lab Entry (LE) function block
 Neural application
 NN and Lab Entry dynamos
 NN and Lab Entry faceplates
 NN and Lab Entry detail displays
DeltaV Predict
DeltaV Predict implements model predictive control for small and medium-
sized multivariable processes in DeltaV environments. DeltaV Predict allows you to
control interactive processes within measurable operating constraints while
automatically accounting for process interaction and measurable disturbances. DeltaV
Predict consists of:
 Model Predictive Control (MPC) function block
 MPC Simulation function block
 Dynamos
 MPC Operate application
DeltaV PredictPro
DeltaV PredictPro implements model predictive control of large multivariable

processes in DeltaV environments. It allows you to define as many as five control
objectives for interactive processes within measurable operating constraints while
automatically accounting for process interaction and measurable disturbances. With
PredictPro you can easily address a wide variety of multivariable processes as large as
40x80 that can benefit from Model Predictive Control (MPC) technology. DeltaV
PredictPro consists of:
 Model Predictive Control Professional (MPCPro) function block
 MPC SimulatePro application
 Dynamos
 MPCPro Operate application

DeltaV Simulate Suite
The DeltaV Simulate Suite consists of the following products:

 DeltaV Simulate Standalone
 DeltaV Simulate Multi-Node
 DeltaV SimulatePro
DeltaV Simulate Standalone and Multi-Node enable you to install all DeltaV software
on standalone or networked PCs for off-line development and operator training.
Using DeltaV Simulate, you can configure all of the features that the DeltaV system
supports (for example, continuous control, batch control, advanced control and its
associated workstation displays, alarms, and historical data collection) without DeltaV
hardware. DeltaV SimulatePro enables more memory and a user interface for
coordinating module execution, permitting interaction with any process simulation
package that uses an OPC interface running on the PC.
Inspect with InSight
Inspect with InSight provides advanced process monitoring that allows you to
instantly identify under-performing loops and malfunctioning field devices. InSight
performance monitoring takes full advantage of the fieldbus block architecture
supported in the DeltaV system. The InSight user interface provides indices that
quantify loop utilization, measurements with a Bad, Uncertain or Limited status,
limitations in control action, process variability, and availability of recommended
tuning.
Tune with InSight
Tune with InSight provides two basic approaches to loop tuning.

On-demand Tuning—Uses an on-demand test of the process to automatically
provide tuning recommendations for PID and Fuzzy Logic Control blocks. InSight
tuning identifies process dynamics and applies tuning rules to calculate the PID
tuning (gain, reset, and rate) or FLC scaling factors. Users can accept the new values,
calculate different tuning values, or continue operating with the present tuning values.
Adaptive Tuning—Uses normal operator changes in setpoint or output to identify
the process and provide tuning recommendations. Adaptive tuning is based on

automatically learning the process by continuously evaluating your plant performance,
evaluating controller tuning, and calculating process models based on normal day-to-
day operations. A high quality model and the expected operation with the
recommended tuning is used as criteria for setting adaptive control.
Operator Tools
The operator tools are used for the day-to-day operation of the process control
system. The primary operator tools are DeltaV Operate Run, Process History View,
Diagnostics, and Batch Operator Interface. The DeltaV Login application is used to
log in and out of the DeltaV system and to change the DeltaV system password.
Batch History View
Batch History View retrieves batch-specific data from the Batch Historian
database and allows you to view the data in several different formats. It is also possible
to add comments and have them saved as part of a batch's history in the Batch
Historian database.
Batch Operator Interface
The Batch Operator Interface is the graphical interface used by the operator to
monitor and control all automated batch operations. The Batch Operator Interface
provides the operator many different views into the batch production process.
Operators can easily switch between views by clicking on toolbar buttons.
DeltaV Login
The DeltaV Login application shows the current user and lets operators log on
and off the DeltaV system and change their DeltaV system password.
DeltaV Operate Run
The DeltaV Operate application functions in two modes. In configure mode, it

is used to build high resolution, real-time process graphics. In run mode, control

system operators use these graphics in the daily monitoring and maintenance of the
process.
In run mode, operators interact with the process control system through the DeltaV
Operate application. High-resolution graphics allow extensive detail and flexibility in
the way information is displayed. A standard operating desktop designed specifically
for DeltaV process control systems provides an easy-to-use, highly reliable operator
environment.
Alarm presentation and management focus the operator’s attention on the most
important alarms. Toolbar buttons enable single-click access to common operator
functions.
Diagnostics
The Diagnostics application provides you with information on the status and
integrity of the system devices. You can view the diagnostics information any time
after you have placed the system devices on the control network and downloaded
your workstations.
MPC Operate
The MPC Operate application provides an overview to the MPC (Model

Predictive Control) block operation. It contains faceplates to view and manipulate
parameter values associated with the block’s inputs and outputs and a trend chart to
view historical, current, and predicted values for Controlled and Constrained inputs.
Process History View
DeltaV Process History View displays real-time and historical data from the
Continuous Historian as well as from the Event Chronicle. Module and node
parameters are plotted on a graph and events are displayed in a tabular (grid) format.

You use the application to examine how your process functioned at any point in time.
You must download the setup data for the workstation that has an enabled Event
Chronicle and Continuous Historian in order for the Process History View to view
the Continuous Historian and Event Chronicle data.

Installation Tools
The main tools in this category are listed below.
 DeltaV Controller and I/O Upgrade Utility is used to update the firmware in the
controller when new software is released by Emerson Process Management. It is
also used to upgrade I/O modules, remote I/O nodes, DeltaV SIS components,
H1 fieldbus devices, and RS3 and PROVOX I/O interfaces.
 DeltaV Operator System Configuration Utility is used to configure aspects of the
Operator System, such as file paths for picture files and trend data.
 DeltaV Workstation Configuration is used to set up the ProfessionalPLUS
workstation and other workstations. Workstation Configuration is described in
detail in Chapter 8, under Configuring DeltaV Workstations.
 DeltaV Guardian Application is used by Emerson SureService support to enable
and disable monitoring of the DeltaV system when the system is enrolled in the
Guardian Support Plan.
 The SureService Registration utility is used to complete and submit your DeltaV
system registration form.
Other Applications
The following subsections contain information on other applications related to the
DeltaV system.
OPC Server
The DeltaV OPC Server works in the background and does not show up on the Start
menu. It makes data such as process data, alarms, diagnostics, and engineering
information easy to access and available for import into desktop applications such as
Microsoft Excel. The Real-Time Data Server also supports comprehensive analysis
tools such as historian packages, manufacturing systems, and laboratory management
systems.
DeltaV Excel Add-In

The DeltaV system provides an interface to Microsoft Excel to allow access to real-
time data from your DeltaV process system. You can then use Excel to generate
reports, create charts, and perform further analysis on the data.

DeltaV Reporter
DeltaV Reporter provides functions and dialogs to aid in the creation of detailed
Excel worksheets containing historical data read from or interpolated from the
Continuous Historian or Event Chronicle database.
OPC Mirror
The OPC (OLE for Process Control) Mirror connects OPC servers on multiple
control systems and enables bidirectional data traffic from one system to another.
This linkage can be between DeltaV OPC servers, DeltaV and PROVOX servers, or
several other OPC server combinations.
Introducing DeltaV
Introducing DeltaV lets you choose between the Configuration Assistant for a guided
tour of the DeltaV system or the DeltaV Explorer so you can easily get started using
the DeltaV software.
Where to Find More Information

The DeltaV system provides online help to assist you when you need a description of
a field or step-by-step instructions for how to do something. It also has a set of online
reference books that discuss basic concepts and provide background information
about the major applications. Other sources of information include the DeltaV web
site, paper manuals, and a number of technical service support options.
DeltaV Online Help
The DeltaV system provides online assistance in several forms. The Help system
can be accessed in DeltaV applications by pressing the F1 key, by clicking the Help
Topics button on the toolbar, or by selecting Help | Help Topics on the menu bar.
The Help Topics dialog has three tabs: Contents (for an expandable list of topics),
Index (for keyword search), and Find (for full-text search). If you need assistance on
using Help, one of the topics in every Help application is “Using Help.” Below are
examples of the Contents and Index tabs from the DeltaV Explorer Help.

Context-sensitive help is available in most applications by clicking the Help
(question mark) button. Context-sensitive help gives you more information about
what you see on your screen. Simply click the button and then click the field or area
for which you want a description.
The “What’s This?” help button is also available in several applications to

describe commands and objects. In some applications, you can point to an object,
click the right mouse button, and select “What’s This?” from the context menu to get
the same information.
DeltaV Books Online
The DeltaV Books Online is a set of online reference books on installing,

configuring, operating, and troubleshooting your DeltaV system. This Getting Started
book is also available online.
There are three main ways to access Books Online:
 Click the Books Online button on a DeltaV application toolbar.
 From the Help menu in a DeltaV application, select Books Online.

 From your Windows desktop, click Start | DeltaV | Help | Books Online.
To open a book, simply click the plus sign (+) next to the title in the Table of
Contents.
Books Online provides an easy-to-use Table of Contents that lets you select a topic
from the contents on the left and view the topic in a window on the right. For
example, the figure below shows the contents under Function Blocks - General
Information (in the Configuration book). To move through a book, continue to click
the plus signs to expand the Table of Contents.

DeltaV Web Site
Current information is available on the DeltaV web site.
Paper Manuals
Most DeltaV product information is in Books Online. You can print single pages,
chapters, or whole books. You can also order a paper copy of most manuals from
Emerson Process Management.
Technical Service
There are several options available for technical service, including help desk support,
remote diagnosis, 24-hour emergency support, and software update service. The
technical support options are described in the Maintenance manual in the Books
Online.
The Technical Support telephone numbers are listed in the Help System under
Frequently Asked Questions, as well as in the Maintenance manual in the Books
Online.

Windows Online Help
If you are unfamiliar with Microsoft Windows, you can access the Windows online
Help by clicking Start | Help and Support.

Chapter 2 Overview of the Tutorials
The tutorials in this book will show you how to get a process system up and running
quickly. You will learn the basic concepts needed to configure workstation and
controller nodes, define I/O, develop a control strategy, and create operator pictures.
You will also see the process system from the operator’s point of view.
Hardware configuration is typically a one-time operation—and may already have been
done for your system. Therefore, we have put this information near the end (in
Chapter 8). If your workstation has not been configured, you may want to begin with
that section after reading this chapter.
Once your workstation has been configured, you can do almost all the tutorial
exercises in Chapters 3 through 7 without having actual controllers and I/O set up.
However, to make the examples more realistic and to be able to do some things (such
as assigning control modules to a controller), you need to have a controller
configured.
A Look Ahead
The tutorials focus on developing the control strategy and operator pictures for a
process that involves monitoring the level in a tank and controlling the flow while
discharging the contents. The book contains six tutorials:
 Chapter 3, Learning About the DeltaV Explorer, shows you how to open the
DeltaV Explorer and use the navigation features.
 Chapter 4, Creating and Downloading the Control Strategy, steps you through the
creation of four modules for controlling the tank process and a sequential
function chart that defines the process startup sequence.
 Chapter 5, Creating Operator Pictures, introduces the basic tools of the DeltaV
Operate application in configure mode and shows you how to create a set of
operator pictures complete with colorful graphics, faceplate and detail pictures,
pushbuttons, and a trend chart.
 Chapter 6, Using DeltaV Operate in Run Mode, shows the operator pictures from
the operator viewpoint and explains how to navigate the pictures, change
operating parameters, acknowledge alarms, and perform other operator tasks.
 Chapter 7, Collecting and Displaying Data, shows how you can gather and display
system and process data using DeltaV tools, such as DeltaV Reporter and the
DeltaV Excel Add-in.
Overview of the Tutorials 2-1

 Chapter 8, Configuring the Network, Loading and Assigning Licenses, and
Setting Up User Accounts, steps you through the procedures for configuring
workstations, controllers, and I/O.
Scenario for the Tank Process Example

The diagram below shows the main parts of a hypothetical process system that
controls the flow while discharging liquid from a tank. In the tutorial lessons that
follow, you will configure the control strategy for this process and automate a
sequence for it.
Control Modules
The first thing you will do is create four control modules for the process equipment
and flow loop. In the figure above, the labels in the ovals (LI-101, MTR-101, and so
on) are the names you will give to the DeltaV control modules. The labels LT-1, FT-1,
XI-1, and so on, are the Device Tags that you will use for the transmitters, valves, and
other I/O instruments.

Table 2-1 contains information about the control modules and I/O Device Tags that
will be used in the tutorial.
Table 2-1 Control Modules and Associated I/O Device Tags
Control Module Description Purpose Input Device Output Device

Tags Tags
LI-101 Level Indicator Monitor level of product in tank LT-1
MTR-101 2-State Motor with Start and stop pump XI-1 ZX-1
interlocks
XV-101 Block Valve Open/close valve for tank LSC-1 XV-1

discharge
FIC-101 Flow Control Loop Regulate flow rate FT-1 FY-1
The Device Tags are assigned to I/O card channels as part of the I/O configuration
process, which is described in Chapter 8.
Sequential Function Chart

After you create the control modules, you will create a module (SFC-START) that
uses a Sequential Function Chart algorithm to automate emptying of the tank. The
steps in the sequence are listed below.
1. Set to automatic the flow loop controlling the outlet flow valve (FIC-101).
2. Specify a desired setpoint for the flow loop.
3. Wait for the regulatory valve to open, then open the block valve (XV-101).
4. Start the outpump motor (MTR-101).
5. Confirm the motor start.
Operator Pictures
You will also create a graphical representation of the tank system, similar to the one
shown below, for operators to use in monitoring and controlling the process.
Overview of the Tutorials 2-3

Let’s Get Started!
Now that you have an overall picture of what you can expect to accomplish in the
tutorials, you can decide if you want to try the exercises online or simply read through
the material.

Chapter 3 Learning About the DeltaV Explorer
The DeltaV Explorer allows you to define system characteristics and view the overall
structure and layout of the system hardware and configuration. In addition to viewing
your database, you can copy and move objects, modify the properties of objects, and
add new objects.
Some of the things you can do with the DeltaV Explorer are:
 Add workstations and controllers to the database
 Add plant areas and control modules to the database
 Add and edit alarm types and edit alarm priorities
 Create named sets that can be used by control modules
 Edit network, controller, and workstation properties
 Download control modules in controllers
 Load and assign licenses
 Export data for use in an external editing tool such as a spreadsheet or database
 Import data from an external editing tool such as a spreadsheet or database
The DeltaV Explorer also provides a fast way to add control modules to your
database. When creating your control strategy, you can simply drag-and-drop control
modules from the template library into a plant area. While you are still in the DeltaV
Explorer, you can edit the module parameters to tailor them to your application. (For
more extensive editing, you can use Control Studio).
You will learn more about the DeltaV Explorer as you go through the tutorials in this
book. For now, let’s take a quick look at how to open and navigate this application.
Opening the DeltaV Explorer
 To open the DeltaV Explorer
Click Start | DeltaV | Engineering | DeltaV Explorer.
Learning About the DeltaV Explorer 3-1

Tip If the Start button is not visible on your Windows desktop, the Windows taskbar/Start
button may be hidden. Point to the lower left corner. If the taskbar/Start button do not
pop up, try the other corners of the screen.
The DeltaV Explorer opens.

Views
Under the View menu, there are several options you may want to try. You can change
from small icons (the default) to large. You can also choose to have additional details
displayed in the right pane. As you work with the DeltaV Explorer, you will determine
which view option is best for the work you are doing.
Navigating the DeltaV Explorer

The left pane of the DeltaV Explorer shows the information in your configuration
database. The right pane lists the contents of the object selected in the left pane.
Opening and Closing Levels

Here are a few tips about opening and closing levels in the DeltaV Explorer hierarchy.
To open or expand an object, do one of the following:
 Click the beside an object.
 Double-click the object’s name.
 Select the object and press the right arrow key on the keyboard.
To close or collapse the objects under an object:
 Click the beside an object.
 Double-click the object’s name.

 Select the object and press the left arrow key on the keyboard.
Documentation Convention for DeltaV Explorer Navigation

In future references to navigating the DeltaV Explorer, we will use a vertical bar
between items to indicate that you should open successive levels. For example,
Library | Module Templates | Analog Control | PID_LOOP
means open the Library, open the Module Templates, open Analog Control, and
select (click) the module named PID_LOOP.
Exploring the Library Templates

In the following exercises, you will use the DeltaV Explorer to look at some of the
function block and module templates available in the library.
Function Block Templates

Function block templates each contain a single function block.
 To see a list of the basic function blocks in the DeltaV library
1. Open the DeltaV Explorer if it is not already open.
2. Expand Library | Function Block Templates.

The items listed are the categories of function block templates available.
3. Click the Details button or select View | Details.

This lets you see at a glance the object name, the type of object, a description, and
other details.
4. Select Analog Control.

The items listed in the right pane are the basic function blocks used in analog
control, including bias/gain, deadtime, filter, lead/lag, and so on.
Tip You can change the width of the columns in the right pane by pointing to the line between
columns in the column title bar, holding down the left mouse button, and dragging the line
right or left to the column size desired.
5. Click the other Function Block Template categories to see their contents.
6. Close the Function Block Templates.
Module Templates
Module templates provide basic control strategies for common control tasks such as
analog control, monitoring, motor control, and valve control.
 To see some of the module templates in the library
1. Expand Module Templates and Analog Control.

2. Click Analog Control to see the details on the module templates in this category.
3. Select PID_LOOP.
The contents are listed in the right pane.
4. Expand Motors-2State, then select MTR-11_ILOCK.

You will use this module template later to configure a pump for the tank process
example.
5. Click beside Motors-2State to close the category.
Context Menus
Pointing to an object and clicking the right mouse button displays a context menu that
allows you to perform different tasks, depending on the type of object.
 To see the context menu for a workstation
1. Select System Configuration | Physical Network | Control Network and point to

a workstation.
2. Click the right mouse button.

System Time
The Set/Synchronize Network Time application determines the date and time for the
DeltaV system. A single workstation called the master time node keeps time for the
entire system and broadcasts the time to the other nodes. The ProfessionalPLUS
workstation is the master time node by default. You use the DeltaV Explorer to:
 Set and synchronize the system time
 Define another workstation as the master time node
 To set/synchronize the system time
1. Click Tools | Set/Synchronize Network Time.
2. Specify the new time and date.
3. Click Apply to send the time and date changes to the master time node, which
broadcasts the time to all nodes on the Control Network.
4. Click Close to close the dialog box without changing the time.

 To define another workstation as the master time node
1. Navigate to Physical Network (under System Configuration).
2. Click Physical Network.
3. Click the right mouse button, and then click Properties.
4. In the Physical Network Properties dialog box, click Browse and select the
workstation that you want to be the source for the master time.
Caution Do not change the time using the Windows date and time properties. Windows date and time
properties do not synchronize the time in all the workstations and controllers. Instead, use the
Set/Synchronize Network Time tool (accessed from the Tools command in the DeltaV
Explorer) to change the system time. This ensures that all workstations and controllers are
synchronized.
Be aware that setting and synchronizing the system time affects event journals and historical
data.
On Your Own
Take a few minutes to open and close different levels in the hierarchy to get familiar
with the database contents and with the navigation tools.
You can also take a look at some of the context menus. This will give you an idea of
how much you can do in the DeltaV Explorer application. At this point, however, do
not make any selections from the context menus.

Chapter 4 Creating and Downloading the Control
Strategy
In the following exercises, you will perform these steps to create the control strategy:
 Create and name a plant area to hold the control modules.
 Create the modules that specify the input, processing, output, alarms, and
conditions for the process equipment, control loops, and other parts of the
process.
 Create a Sequential Function Chart (SFC) to automate the process.
Strictly speaking, you do not need to create an SFC. You can set up your process
system in such a way that an operator would activate specific equipment, change
setpoints, and perform other operations. However, in many cases, it is useful to define
a Sequential Function Chart to automate the process (or parts of the process, such as
startup or shutdown procedures) with minimal operator intervention.
When creating the control modules that make up your control strategy, sometimes
you will create a module from scratch (using the basic function blocks), but more
often you will start with one of the predefined module templates.
There are a number of ways to create the control modules.
 In the DeltaV Explorer, you can copy a module template from the library by
dragging and dropping it onto your plant area and then renaming it.
 In Control Studio, you can start from a module template, modify the module, and
save it in your plant area under a new module name.
 In Control Studio, you can start from scratch by dragging and dropping function
blocks and other items from palettes of predefined items, connecting the blocks,
and modifying block parameters.
 In Configuration Assistant, you can copy a module template from the library.
In the exercises in this chapter, you will learn how to use the first three methods.
Note This manual assumes that you are working on a new system or one that is in the
beginning stages of configuration—not one that is controlling a process.
Creating and Downloading the Control Strategy 4-1

Exercise 1: Creating and Naming Plant Areas
Plant areas are logical, software-based divisions of your control system, which may or
may not correspond to physical areas in your plant. Plant areas contain the modules
that make up the control strategy. You can have as many as 100 plant areas. How you
define your plant areas affects your overall system security scheme because you can
authorize access to the system based, in part, on plant areas.
The DeltaV system provides a default system area called AREA_A. You cannot delete
AREA_A because it is essential for system operations and for performing certain
DeltaV functions. If you decide to create additional plant areas, you may want to put
your control modules in other areas and reserve AREA_A for only these system
operations and functions. (You can rename AREA_A to a more meaningful name for
your process.)
In the next procedure we will create a plant area named TANK-101 to hold the
tutorial modules. The name must be 16 characters or less, and may contain only
alphanumeric characters, hyphens (-), and underscores (_). Hyphens or underscores
are typically used to represent spaces between words.
 To add a plant area
1. In the DeltaV Explorer, point to Control Strategies and click the right mouse
button.
2. Select New Area from the context menu.

A new area, named AREA1, is added and appears in an edit box in the right pane.
3. Enter a new name (for our example, TANK-101) and press Enter.
Now you are ready to start creating the control modules.

Exercise 2: Using the DeltaV Explorer to Copy a Module
(MTR-101)
The tank process has a pump with a two-state (on or off) motor. The motor interlocks
under certain conditions. In this exercise, you will use DeltaV Explorer to copy a
module template from the Library to the TANK-101 area and rename it. Later, you
will use Control Studio to modify the module. (Modifying includes specifying the
conditions for the interlocks.)
When you copy a module template from the Library, the module includes history
collection. History collection is added to a module or node parameter field and
defines the history collection strategy (the value recorded, how it is displayed, the
sampling period, and so on) for that field value. Library modules include history
collection so that you do not have to set up history collection when you copy a library
module to an area. You can add additional history collection to the module if you
wish. We will add history collection to the module that we create from scratch in
Exercise 5: Creating a New Module (LI-101) from Scratch. Later, we will use the
Process History View application to view the field value.
Note In naming the motor (MTR) templates, the following convention was used: the first digit
after MTR is the number of outputs; the second is the number of inputs. Thus, MTR-
11_ILOCK is for a motor with one output, one input, and interlocks.
 To copy the module and rename it
1. In the DeltaV Explorer, open Library | Module Templates | Motors-2State, and

select MTR-11_ILOCK.
2. Drag-and-drop the MTR-11_ILOCK module onto the TANK-101 plant area.

To drag-and-drop, point to MTR-11_ILOCK, hold down the left mouse button,
move the pointer to TANK-101, and release the mouse button. TANK-101 now
contains a copy of the module, named MTR-11_ILOC_1.
3. Open TANK-101 and select MTR-11_ILOC_1. The name is highlighted.
4. Click the module name a second time (or click the right mouse button and select
Rename from the context menu).
Note If you are copying a module from an area, you must hold down the Ctrl key or the module
will be moved rather than copied to the new location. If you are copying a module from
the library, it is not necessary to hold down the Ctrl key while dragging the module.

5. Enter the new name for the module: MTR-101.
Note If you are creating a module in a DeltaV Batch application, module names are limited
to 16 characters (letters, numbers, and underscores) and the first character must be a
letter. Dashes should not be used in any control module that will be used in the DeltaV
Batch system.
6. Click the minimize button in the upper right corner to minimize DeltaV
Explorer. It appears on the Windows taskbar at the bottom of your screen. To
reopen it later, simply click on its name in the taskbar.
It’s that easy. You now have a control module in your TANK-101 plant area.
Introducing Control Studio

Take a few minutes and read the next few pages to learn about the Control Studio
application before you open Control Studio and create a module. The Control Studio
window has different sections called views, that are used to define the characteristics of
a module. Each view can be closed or resized individually so that you can optimize the
size of the view you are working in.
You can set the size of the overall window by dragging the sides or corners. Then, on
the View tab, in the Windows group, click Arrange to automatically reshape the views
to a predefined arrangement.

The figure above shows the default arrangement of the Control Studio views. The
views are:
 Diagram View - used to create a module’s control algorithm graphically on a
diagram (includes a palette of items that can be placed on the diagram)
 Parameter View - used to define the module’s characteristics, alarm limits,
default values, mode, and other parameters
 Hierarchy View - used to see a hierarchy of the elements that make up the
module
 Alarm View - used to see the alarms that are defined, their limits, priorities, and
other information
The palette shows the items that can be added to the diagram using the drag-and-drop
technique. Several palettes are available. You can change to a different palette by
clicking on the palette name.
Note If the palette is not showing, point to the edge of the Diagram window, hold down the
mouse button and drag the side of the window to resize it to show the palette column.

The palette can be moved from one side of the Diagram View to the other. To do this,
point anywhere on the palette, click the right mouse button, and select Switch Sides
from the menu.
The items in the palette may be displayed with either large or small icons. To change
the selection, point anywhere on the palette, click the right mouse button, and select
the desired icon size.
Note If another user has changed the Diagram Preferences (on the Diagram tab in the Layout
group), your pictures may look different than the ones in this book. The default settings
are shown below:
Parameter Filtering
Parameters are data used in module function blocks to perform calculations and logic.
Some parameters are defined and unchangeable for certain function blocks. Some
default to a most common value, but may be modified. Others must be set by the user.
Some function blocks have a large number of parameters. To help you quickly access
the ones you need, a number of parameter filtering options are available. In the
Parameter view, the Common configuration filter setting lists the parameters that are
most often used for the configuration of the control module. These parameters
generally have default values set, but should be modified to fit the application.
Parameters and parameter filtering are described in detail in the Books Online
Configuration manual.

Exercise 3: Creating a Control Module (XV-101) in Control
Studio Using a Library Template
In this exercise you will use a module template to create a control module for the
block valve. This time you will use Control Studio, rather than the DeltaV Explorer, to
create the module from a library template.
Opening Control Studio
 To open Control Studio and create a module from a template
1. Click Start | DeltaV | Engineering |Control Studio.
(Another way to launch Control Studio is to click its button in the DeltaV
Explorer toolbar. We have minimized the Explorer to keep the desktop

uncluttered; if you are comfortable using Windows, you can have several DeltaV
application windows open at once.)
2. To choose a template from the library, click the Main button, then click
New. On the New dialog, select Start from Existing and click the Browse button.
The Browse dialog box appears.
3. Click in the Object Type field at the bottom of the dialog box, and select Module
Templates.

4. In the large center box that lists the contents of Module Templates, double-click
Valves-Normally Closed.
5. From the contents of Valves-Normally Closed, select VLVNC-11. (This name is

automatically placed in the Object name field.)
6. Click OK in the Browse dialog box.

7. Click OK in the New dialog box.
Control Studio now displays an untitled copy of the VLVNC-11 module.
Modifying the XV-101 Control Module

The module template is fairly simple, consisting of only one function block. To
customize the module for the tank application, all you need to do is identify the
Device Signal Tags for the input and output. (Device Tags are assigned to the I/O

channels as part of the I/O card configuration process, described in Chapter 8.) Refer
to the Glossary for definitions of Device Tag and Device Signal Tag.
 To modify the control module
1. In Diagram View, click the Device Control function block, DC1.

Four small black squares (called “handles”) appear at the corners to indicate that
this block is the currently selected item on the diagram.
Filtering may be applied to limit the list of parameters displayed.
2. Select a parameter, click the right mouse button, and select Filter Parameter List.
The Parameter Filtering dialog box opens.
3. Select Common configuration to display the group of parameters that are

identified as the most commonly used in process control configuration and
select On-line to display the parameters most commonly used for operating a
process.

4. Deselect any other boxes that may be checked by clicking on each, and click OK
to close the dialog.
5. In the Parameter View, scroll down the list if necessary, and select IO_IN_1.
6. Double-click the IO_IN_1 parameter to open the Properties dialog box.
7. In the Device Tag field, enter LSC-1. (LSC-1 is the Device Tag used in our tank
example for Limit Switch-Closed.)
The Device Tags for the tank application are listed in the table in Chapter 2.

The IO_IN_1 parameter is given a value of FIELD_VAL_D. (You can click in
the Parameter field to see this value. It also appears in the Parameter view.) LSC-
1, together with the FIELD_VAL_D parameter define the Device Signal Tag
(DST).
(If you have configured placeholders for the I/O cards, as described in Chapter 8,
you can browse for the Device Tags. Clicking the Browse button opens a dialog
box that lists all the configured I/O card channels and their assigned Device Tags.
You can scroll down the list, select the appropriate Device Tag, and click OK.
Click the Alphabetic tab to alphabetize the list and scroll past the entries
beginning with COxx to get to the Device Tag names such as LSC-1.)
8. Click OK.
9. In the Parameter View, double-click IO_OUT_1.

The Properties dialog box appears.
10. In the Device Tag field, enter XV-1 and click OK.
XV-1 is the Device Tag used in our example for the Block Valve. The DST is
given a default parameter value of OUT_D.
The Parameter list should now look like this:

Exercise 4: Finishing Steps for All Control Modules
There are four things that you should do every time you create a control module.
 Identify the operator pictures that will be associated with the module.
 Assign the module to a controller.
 Save the module to the database.
 Verify the module’s configuration.
The procedures for accomplishing these tasks follow. (An additional step is
downloading. Modules can be downloaded to a controller individually. However, we
will download our whole control strategy at one time, as you will see at the end of this
chapter.)
Identifying the Operator Pictures Associated with a Module

Three types of operator pictures are associated with control modules: the Primary
Control picture, the Faceplate picture, and the Detail picture.
You will see what these pictures look like and how they are used in Chapter 5,
Creating Operator Pictures and Chapter 6, Using DeltaV Operate in Run Mode. For
now, you simply need to know how to associate the module with the pictures.
 To identify the Primary Control picture associated with this control module
1. In Control Studio, click the Main button, point to Module, then click Properties.

2. Click the Displays tab and, under Primary Control, enter TANK101.
This will be the name for the Primary Control picture that will be associated with
this control module. You will create the Primary Control picture TANK101 later
(in Chapter 5).
Note Picture file names must be alphanumeric and cannot contain the hyphen character, begin
with a number, or use a Visual Basic reserved word.
Note that the fields for Detail picture and Faceplate picture are already filled in.
All the control module templates in the library have pre-defined Detail and
Faceplate pictures associated with them.
3. Click OK.
Assigning the Module to a Controller Node

If you configured a controller or created a placeholder controller, you will be able to
assign the module to the controller. If you have not configured a controller, go to the

section “Configuring the Controller Node” on page 8-17 for information on how to
do this. For information on connecting your controller hardware, refer to the
hardware manual, Installing Your DeltaV Digital Automation System.
 To assign the control module to a controller node
1. Click the Main button, point to Download, then click Assign to Node.
The Browse dialog box opens.
2. In the Browse dialog box, select the controller.
3. Click OK.
Note After clicking OK in the Browse dialog box, an information message appears, notifying
you that assigning a module to a node will modify the database. Click Yes to confirm
that you want to assign the module.
Saving the Module
 To save the control module
1. Click the Save button on the Quick Access Toolbar.

2. In the Objects Type box, select Modules.

3. In the Look In field select Control Strategies, and double-click TANK-101.
MTR-101, the module we created earlier in the DeltaV Explorer, is in the list of
modules.
4. In the Object Name box, type XV-101 as the name for this module and click
Save.
Verifying the Module Configuration
 To verify the module’s configuration
1. Click the Main button, point to Module, then click Properties.

The Properties dialog box opens.
2. Click the Tools tab.

3. Click the Verify Now button.
A message is displayed it may contain minor warnings due to I/O references.
4. Click OK to close the message box and click OK on the Properties dialog.
You now have two control modules, one for the motor and one for the block
valve. You have learned quite a bit, which you will be able to put to use in the
following exercises.
If you want to take a break you can quit Control Studio by clicking the Close button in
the upper right corner. Before starting the next exercise, simply start Control Studio
from the Start button.

Exercise 5: Creating a New Module (LI-101) from Scratch
In this exercise, you will use Control Studio to create from scratch a module to
monitor the tank level. The module will have one analog input function block (to
allow reading of the analog input signal) and one output, a promoted parameter.
Promoted parameters are available under the Special Items palette. The promoted
output parameter allows this value to be more easily accessed systemwide.
Four other changes will be made.
 The IO parameter of the analog input block will be edited to identify the Device
Signal Tag for the level transmitter, LT-1.
 The OUT_SCALE parameter on the analog input block will be changed from the
default value of 100 to 10,000 to reflect the 10,000-gallon capacity of the tank.
 The HI_HI_LIM value will be changed to 1000.
 History collection will be added to the PV of the AI block so that the tank level
can be trended in the Process History View application.
 To create a new module
1. In Control Studio, click the Main button, then click New. The New dialog box
appears.
2. Click OK to accept the default settings in the New dialog.

Control Studio opens with a blank, untitled Function Block diagram.

 To add and modify a function block for analog input
1. Select IO palette category. A list of function blocks related to I/O appears.
2. Select the Analog Input (AI) function block from the palette; drag-and-drop it
onto the Function Block diagram.
3. To find out more about this function block, point to the AI block, click the right
mouse button and select What’s this? from the menu.

Tip To access detailed information, you can click the Books Online (Reference) icon at the end
of the pop-up text. After reading about the function block, click the Close button in the
Books Online window to quit that application and return to Control Studio.
4. Make sure the block is selected.
5. In the list of parameters, double-click HI_HI_LIM (or click the right mouse
button and select Properties).
6. In the Properties dialog box, change the value to 1000 and click OK.
7. Double-click the IO_IN parameter.

8. In the Properties dialog box, enter the Device Signal Tag, LT-1 (for the level
transmitter), and click OK. The system selects the default parameter.
In the Parameter list, note that the parameter named L_TYPE (linearization type)
has a default value of Indirect. This must remain Indirect for you to be able to
define the Engineering Units of the input.
9. To set the Engineering Units (EU) and the scale, double-click the OUT_SCALE
parameter.
10. Modify OUT_SCALE as follows:

• Change the 100% scale from 100 to 10000 (for 10,000 gallons).
• For Engineering unit descriptor, select gal (for gallons).
11. Click OK.
For our example, we would like to make the output value easy to reference system
wide. Promoting the parameter to the module level allows the value to be referenced
throughout the system as LI-101/PV rather than LI-101/AI1/OUT.

 To add a module-level parameter for output of the process value
1. Select the Special Items palette.
2. Select the Output parameter, click the right mouse button, and select What’s
This? from the menu to get a description.
3. Drag-and-drop the Output parameter onto the diagram to the right of the AI
function block.
A Properties dialog box appears.
4. Change the parameter name to PV (for process value).

5. Select Floating point with status in the Parameter field, select I/O in the
Parameter category field, accept the default status (it will be overwritten), and
click OK.
The block named PV now appears on the Function Block Diagram.
 To add history collection to the PV
1. Select the AI block in the Diagram View.

2. In the Parameter View list, click the right mouse button on PV and select Add
History Recorder.
The Add History Collection dialog opens.

3. The path to the current value for the PV (AI1/PV.CV) appears in the Parameter
field path box. (If this path does not appear here, click the Browse button and
browse for it.)
4. Click Enabled.
5. Click Line as the Display Representation.
Note The line style can be changed in the Process History View application.
6. Use the default value of 60 seconds as the sampling period.
7. Click OK.
Later, we will assign the area (TANK-101) to the Continuous Historian subsystem,
enable history collection on the workstation, and download the workstation in order
to collect and view the historical data for the field values.
 To connect the two blocks
1. Click the Out connector on the AI block and hold down the left mouse button.
(The focus must be in Diagram View for this button to be active.)

2. While holding down the left mouse button, draw a line from the Out parameter
on the AI block to the PV parameter.
The pencil changes to a * when you are over the right spot for making the
connection.
Tip If you want to rearrange the diagram, click one of the function blocks and move it. The
connector line moves and resizes automatically.
Your finished diagram should look like this:
Finishing the LI-101 Module
 To finish the module
We have abbreviated the instructions for finishing the module. If you have forgotten
any of the steps, refer to the details in Exercise 4.
1. Right-click the Diagram View, then click Properties and set the Primary Control
picture to TANK101.
2. Assign the control module to the controller.
3. Save the control module in area TANK-101 under the object name LI-101.
When you have finished, quit Control Studio. Do not simply minimize Control
Studio. In the next exercise, we will show you a new way to open Control Studio
directly from the Explorer. If you minimize Control Studio, you will have two copies
of Control Studio open.
If you have the DeltaV Explorer minimized, restore it to full size by clicking on its
name in the Windows taskbar at the bottom of your screen. Otherwise, open it from
the Start button.
Exercise 6: Creating a PID Control Loop (FIC-101)

In this exercise, you will use the PID_LOOP module template from the Analog
Control group as the basis for a module to control the outlet flow valve. This time,

you will use the DeltaV Explorer to create the module, assign it to a controller, and
modify most of the parameters.
 To create the control module and assign it to the controller
1. In the DeltaV Explorer, select Library | Module Templates | Analog Control |

PID_LOOP and drag it to the TANK-101 area.
2. In the TANK-101 area, select PID_LOOP_1 and rename it to FIC-101.
3. Select FIC-101, click the right mouse button, and select Assign.
Alternatively, drag-and-drop FIC-101 from the TANK-101 area to the controller
object under the Physical Network | Control Network.
4. In the Browse dialog box, select the controller and click OK.
Note After clicking OK in the Browse dialog box, an information message appears, notifying
you that assigning a module to a node will modify the database. Click Yes to confirm
that you want to assign the module.
 To modify the control module
1. Double-click FIC-101 in the left pane to open the module.
2. If necessary, click the List button to display the contents of the right pane as
shown in the next figure.
3. Select PID1 (the PID loop function block) and make the following changes to
the parameters in the right pane.

a. Double-click IO_IN. In the Properties box, enter the Device Tag of FT-1.
b. Double-click IO_OUT and enter the Device Tag of FY-1.
c. Double-click GAIN and change the value from .5 to 1.
d. Double-click RESET and change the value from 10 to 3 (that is, 3 seconds per
repeat).
e. Double-click PV_SCALE and change the Engineering unit descriptor to GPM

(gallons per minute).
4. In addition, note these default settings for other parameters:
• On the CONTROL_OPTS (control options) parameter, Direct acting is not
selected, meaning that it is set as reverse acting.
• On the IO_OPTS (I/O options) parameter, Increase to close is not selected,
meaning that it is set as increase to open.

Looking at the Module in Control Studio
Now let’s take a look at the module in Control Studio.
 To open the FIC-101 module for further editing in Control Studio
1. Select FIC-101 in the DeltaV Explorer.

2. Click the right mouse button and select Open | Open with Control Studio from
the context menu.
Control Studio opens with module FIC-101 preloaded.
3. Resize the individual views as necessary so that your screen looks similar to this:

Modifying Alarms for the PID Loop Module
Alarms are used in the DeltaV Operate application (in run mode) to notify operators
about changes in the process that might require their attention. Alarms are visible on
the Alarm Banner at the bottom of the operator picture, as well as on any Faceplate
pictures or other pictures that are set to show alarms.
Alarms have been set up in the PID_LOOP template which we used as the basis for
the FIC-101 module. Take a closer look at the alarms that appear in the Alarm view,
the bottom pane in Control Studio.
Only three of the alarms, HI_ALM, LO_ALM, and PVBAD_ALM are enabled. For
the example, you will modify the HI_ALM slightly to change the value from 95 to 90.
This means that an alarm will be activated if the flow goes above 90 gallons per
minute.
 To modify the alarm
1. Double-click HI_ALM (or select HI_ALM in the Alarm View, click the right
mouse button, and select Properties).

2. Change the Limit value from 95 to 90 and click OK.
Finishing the FIC-101 Module
You have already named the module and assigned it to the controller.
1. Set the Primary Control picture to TANK101.

2. Save the module.
Exercise 7: Modifying the Motor Module (MTR-101)

Earlier in this chapter, in Exercise 2, you created the MTR-101 module in the
Explorer by copying the MTR_11_ILOCK template to the TANK-101 area. In this
lesson, you will open the module for editing in Control Studio. This module looks
complex at first, but becomes more understandable as you look at the individual parts.
Tip If you have access to a printer, you can print out the diagram, which includes
Configuration Tips. Click the Main button, then click Print. Click the diagram check

box.
The motor module, shown later in this exercise, includes these function blocks, all of
which are from the palette group named Logical:
 Eight Condition blocks (CND)
 Boolean Fan Input (BFI) block
 Logical And (AND), logical Not (NOT), and logical Or (OR) blocks
 Device Control (DC) block
The CND, BFI, AND, NOT, and OR blocks are used to specify the interlock logic.
The DC block is for motor control.
Some of the things you will do in this exercise are:
 Delete the excess condition blocks.
 Specify the interlock conditions using the remaining three condition blocks.
 Specify the Device Signal Tags for the input and output parameters.
 Change the Detail picture associated with this module to one that has three
conditions rather than eight.
 To open the module for editing
1. In Control Studio, click the Main button, then click Open.

The Browse dialog box appears.
2. Select Modules in the Object Type field.
3. If TANK-101 is not in the Look in field, open the pull down list and select
Control Strategies. In the large center box that lists the contents of Modules,
double-click TANK-101.

4. Select MTR-101 and click Open.
The MTR-101 module is displayed in the Diagram view.
5. Enlarge the Control Studio application window to its full size by clicking the
Maximize button in the upper right corner.
6. Change the palette to Logical so you can easily access the descriptions for the
individual blocks.
(Remember, you can point to a palette item or a function block on the diagram, click
the right mouse button, and select What’s This? for a description.)

Removing the Excess Condition Blocks
Although it does not matter if there are unused condition blocks on the Function
Block Diagram, it will improve the appearance to delete the ones that will not be
needed. You can remove the excess condition blocks and their connecting lines by
selecting one or more than one and pressing the Delete key. To select more than one,
click them while holding the Shift key, or drag a selection box around the whole
group.
 To remove the excess condition blocks
1. Place the mouse pointer outside the upper left corner of CND4.

2. Click and hold the mouse button, then drag to include the lower right corner of
the CND8 box.
The boxes named CND4 Through CND8 should be selected. If not, click a blank
spot and try again.
3. Press the Delete key to delete the selected items. (Or click the right mouse
button and select Delete from the context menu.)
4. Click Yes when asked to confirm the deletion.

The blocks and connection lines are deleted.
Specifying Conditions with the Expression Assistant

The motor should shut off if any of the following three conditions occurs:
 The block valve is closed.
 The tank level is less than 100 gallons.
 The regulatory valve is less than 5 percent open.

Now we need a way to specify these requirements. The condition blocks serve this
purpose. Each condition will have associated with it an expression that identifies the
condition precisely in mathematical or logical terms. Expressions are made up of
operands, operators, functions, constants, and keywords.
Two guidelines for writing an expression for a condition are:
 The expression must end with a semi-colon (;).
 Parameter values are enclosed by single quotes (').
The DeltaV system provides an Expression Assistant to help you define these
expressions. After you have entered an expression, the Expression Assistant checks
the syntax, indicates problems, and identifies any unresolved parameters. The
Expression Assistant is accessed through the Object menu or context menu (right
mouse click) for Action, Calculation/Logic, and Condition function blocks. The
dialog box for the Expression Assistant looks like this:
The Expression Assistant inserts the characters shown in the following table when
constructing expressions. If you type the expressions without using the Expression
Assistant, you need to use these characters in the same way.

Table 4-1 Characters for Constructing Expressions
Characters Use Example
/ Precedes a reference to an internal

parameter (one within the current module).
Use the Insert Internal Parameter button to
browse for these parameters.
^/ Precedes a reference to an internal

parameter up one block level. Use the Insert
Internal Parameter button to browse for
these parameters.
// Precedes a reference to an external '//XV-101/DC1/PV_D.CV'

parameter (one within another module). Use
the Insert External Parameter button to
browse for these parameters.
## In Batch processing, used to enclose an

alias.
: Used to separate a named set from the 'vlvnc-sp:OPEN’

named set value.
:= Used to assign values. Step actions use this 'SP':='SFCCTRL:IDLE'

operator. The value of the right operand is
assigned to the left operand.
= Used to compare values. Similar operators 'SP'='SFCCTRL:START'

include >, <, >=, <=,!= (not equal to), <> (not
equal to). Transitions use these operators.
+ Used for addition of numeric values or for

concatenation of strings.
'' Single quotes are used to enclose

parameters.
"" Double quotes are used to enclose strings.
; Used to continue action statements on

subsequent lines of the Expression
Assistant.
Parameter Tagnames
Parameter values are defined by their tagnames (tags, for short) in the form:
module/function block/parameter
When identifying parameter tags, you can build the tags from scratch by typing them
in or you can use the parameter browser, which is a tool for searching the database.

Interlock Conditions
In this procedure, we will use the Expression Assistant to specify the interlock
conditions on the three condition blocks.
 To specify the first interlock condition (the block valve is closed)
1. On the View tab, in the Windows group, click Arrange so that you can see all the
views again.
2. Select the block named CND1.
3. Click the right mouse button and select Expression from the menu to open the
Expression Assistant.
4. Highlight and delete the default first line of FALSE.
5. Click the External Parameter button. This button browses for parameters that
are external to the current parameter.
6. Open the TANK-101 area.
7. Double-click these items in each succeeding level: XV-101, DC1, PV_D and CV.
The Expression Assistant assembles the tagname and puts it in the Expression
box.
8. Click or type “=”.

9. Click Named State, double-click the named set vlvnc-pv, select the state
CLOSED, and click OK.
10. Type a semicolon at the end of the expression.

The completed expression now reads as follows:
'//XV-101/DC1/PV_D.CV' = 'vlvnc-pv:CLOSED';
XV-101 is the module for the block valve; DC1 is the function block; PV_D.CV is the
current value for the process value; and CLOSED is one of the states in the named
set, vlvnc-pv. The expression indicates that an interlock should occur (the motor
should shut off) if the block valve is closed. (A named set is simply a way to define
names and equate them to integer values. Named sets are defined in the DeltaV
Explorer, under System Configuration | Setup.)
11. Click Parse.

The Expression Assistant checks the syntax. If there are any errors, correct them.
12. Click OK.
 To specify the second condition
1. Select the CND2 block and use the Expression Assistant to specify the interlock
condition as:
'//LI-101/AI1/PV.CV'< 100;
LI-101 is the control module for the level indicator. AI1 is the analog input
function block. PV.CV is the parameter for the analog input current value. The
expression indicates that an interlock should occur (the motor should shut off) if
the tank level goes below 100 gallons.
2. Click Parse, correct if necessary, and click OK.
 To specify the third condition (the regulatory valve is less than 5 percent open)
1. Select the CND3 block and use the Expression Assistant to specify the interlock
condition as:
'//FIC-101/PID1/PV.CV' < 5;
FIC-101 is the module for controlling the outlet flow (regulatory) valve. PID1 is
the loop function block, and PV.CV is the parameter indicating the current state
of the valve (percent open). The expression indicates that an interlock should
occur if the valve is less than 5 percent open.

2. Parse the expression and click OK.
 To specify the DSTs for MTR-101
1. In the Function Block diagram, click the Device Control function block, DC1.
2. In the Parameter window, double-click the IO_IN_1 parameter. (This is the

parameter for the run status signal.)
3. In the Properties dialog box, type XI-1 in the Device Tag field and click OK.
(If you have configured the controller and I/O channels, as described in Chapter
8, you can browse for the Device Tag under the controller.)
The parameter field is automatically set to the correct parameter,
FIELD_VAL_D.
4. Double-click the IO_OUT_1 parameter. (This is the output signal from the
Discrete Loop block to the field device.)
5. In the Properties dialog box, type ZX-1 in the Device Tag field and click OK.
The parameter field is automatically set to OUT_D.
Finishing the MTR-101 Module
1. Open the Properties dialog and set the Primary Control picture on the Displays
tab to TANK101.
Note that this module has two predefined pictures: DL_DT8 for the Detail
picture and DL_FP for the Faceplate picture.
2. Change the Detail picture to DL_DT3 to match the number of conditions.
3. Assign the control module to the controller.

4. Save the control module by clicking the Save button. (The module has already
been named.)
5. Minimize Control Studio by clicking the Minimize button in the upper right
corner.

Exercise 8: Creating a Sequential Function Chart
Sequential Function Charts (SFCs) are types of module algorithms that are useful for
controlling time-event sequences, such as startup or shutdown of a process. SFCs are
made up of steps and transitions. Steps contain a set of actions. A transition allows a
sequence to proceed from one step to the next when the transition condition is true.
Each time the SFC scans, the system evaluates the active steps and transitions. When a
transition evaluates as True, the step prior to the transition is made inactive and the
step following the transition becomes active.
There are no predefined module templates for SFCs since process sequences are
highly individual. In defining an SFC, you may find it helpful to first define the steps
in the process, and then identify the conditions that must be met before proceeding
from step to step.
The Sequence for the Tank Process

For the tank process, you will create an SFC to control the tank discharge. As a way to
start and stop the SFC, you will create an SFC parameter called SP that the operator
will be able to change. The SP will be manipulated with a named set called SFCCTRL.
A named set defines names and equates them to integer values. For the tank example,
you will create the named set with two values: 0=IDLE and 1=START.
Following is a suggested sequence for the tank discharge application.
Step 1: Stop (that is, set the SP to IDLE).
Transition: Wait for the user to change the SP to START.
Step 2: Put the flow loop in auto mode and set the setpoint to 50 gpm.
Transition: Wait for the regulatory valve to be 30% open.
Step 3: Open the block valve.
Transition: Confirm that the block valve is open.
Step 4: Start the pump.
Transition: Confirm that the pump has started.
First, you will create the named set, SFCCTRL, in the DeltaV Explorer. Then you
will go to Control Studio to create the module containing the Sequential Function
Chart.

 To create the named set
1. Open (or restore) the DeltaV Explorer.
2. Select System Configuration | Setup | Named Sets.
3. Point to Named Sets in the left pane, click the right mouse button and select
New | Named Set.
A new entry, NamedSetn (where n is the next number available), is added to the
end of the list of existing named sets. The entry is in an edit box, ready to be
renamed.
4. Type the new name, SFCCTRL, and press Enter.
5. Double-click SFCCTRL (or select SFCCTRL, click the right mouse button, and
select Properties from the menu).
6. Type Sequence Control in the description box.
7. Click Add.
The State Properties dialog box appears.
8. Type IDLE in the Name box and click OK.

Note Named sets are case-sensitive. They may be defined using uppercase or lowercase
characters, but all future references to the state must be as originally defined.
9. To add another state, click Add.

10. Type START in the Name box and click OK.
The Properties dialog box now has 2 named states, IDLE and START.
11. Click OK to save the set and close the dialog box.
12. Minimize the DeltaV Explorer.

Creating the SFC Module
Now you are ready to create the Sequential Function Chart. Here are the things you
will do in the following exercises:
 Create an SFC module.
 Add a parameter, SP, to the module to let the operator change the state from
IDLE to START.
 Add the steps and transitions to the SFC.
 To create a Sequential Function Chart
1. Restore Control Studio by clicking its button on the Windows task bar.
2. Click the Main button, then click New.
3. In the New dialog box, select Control Module or Template as the Object Type.
4. Select Sequential Function Chart as the Algorithm Type and click OK.
A new SFC diagram opens, with a single step, S1.

 To add the SP parameter
1. Click in the Parameter View, click the right mouse button, and select Add from
the menu.
2. Type SP as the Parameter Name.
3. Select Named Set as the Parameter type.
4. For the Named set and Named state, browse and select SFCCTRL |IDLE.
5. Click OK. The parameter is added to the module.
 To create a step action in the SFC
1. In the Diagram View, select the step box named S1.
2. Click the name, S1, and change it to STOP_AND_WAIT.

3. In the step Action View (in the lower right corner), click the right mouse button
and select Add.
4. Enter the Step Description: Stop and Wait.
5. For the Action type, select Assignment. (This type assigns the result of an
expression to a destination.)
6. For the Action qualifier, select P Pulse.

A pulse action of any type means the action is only active on the first scan when
the step goes active. Thus, the assignment statement is evaluated and the
assignment made on the first scan through the step actions when the step goes
active. After the first scan, the assignment destination retains the assigned value; it
is not rewritten for each scan.
7. To set the setpoint to the IDLE state, type the Action expression:
'SP':='SFCCTRL:IDLE'; (remember: named sets are case-sensitive.)
An alternative is to click the Expression Assistant button to open the Expression

Assistant to define the Action expression. (The Expression Assistant was used
earlier to define the interlock conditions for the motor control module.) Click the

Insert Named State button in the Expression Assistant to define the Action
expression.
8. Click OK on the Properties dialog box. If necessary, make any corrections, and
click OK.
9. Select the step action (A1) in the Step Action View, right-click and select
Rename, and change the name to SET_TO_IDLE.
Giving the step actions meaningful names instead of A1, A2, etc., helps you
identify a particular action you may want to modify.
 To create a transition in the SFC
1. From the palette of All SFC Items, click Transition, drag to a point below
the box named STOP_AND_WAIT, and release the mouse button.
A plus sign named T1 appears.
2. Click the right mouse button and select Properties (or double-click the
transition).
3. Enter the transition description (Wait until Start), open the Expression Assistant
and build the condition statement:
'SP'= 'SFCCTRL:START'

4. Click Parse on the Expression Assistant. Correct, if necessary, and click OK on
both dialogs.
5. Rename the transition to WAIT_UNTIL_START.
 To complete the Sequential Function Chart diagram
1. Repeat the procedures for adding steps and transitions using the information in
Table 4-2, which follows. (Drag-and-drop Step and Transition icons from the
palette or use the Sequence item on the palette to automatically add multiple steps
and transitions in one operation. Use a Termination icon for the last transition.)
Tip On the View tab, in the Diagram group, click Diagram Preferences and check Display
Grid and Snap to Grid to help you line up the SFC objects on the diagram.
Note In the example, all Action Types are Assignment; all Action Qualifiers are Pulse,
except for Action 2 in Step 2, which has an Action Qualifier of Non-stored. (The reason
is that if Action 2 Step 2 were Pulse, it might not get set because it waits until the actual
mode is Auto. It would fail on the first try and never be set.)
2. Use the Connect Mode tool to connect the steps and transitions in order.
3. Change the step and transition names by clicking the right mouse button,
selecting Rename, and typing the Name listed in the table.

Note Read the table footnote for important information about statement syntax.
Table 4-2 Actions and Transitions in the SFC
Step/Transition Name Action Text or Condition Text* Description
S1 STOP_AND_WAIT 'SP':='SFCCTRL:IDLE'; Inhibits startup sequence

(until the user changes the
SP to START).
T1 WAIT_ UNTIL_START 'SP'='SFCCTRL :START' Waits until operator selects

START. If SP is START,
proceeds to the next step.
S2 SET_FLOW_RATE A1: '//FIC-101/PID1/MODE. Sets the flow loop to AUTO.

TARGET':= AUTO;
Sets the setpoint at 50 GPM.
A2: '//FIC-101/PID1/SP':=50;
(Action Qualifier is Non-Stored.)
T2 WAIT_FOR_OUT_30 '//FIC-101/PID1/OUT' > 30 Waits for the regulatory valve

to be 30% open.
S3 OPEN_BLK_VLV '//XV-101/DC1/SP_D':=1; Opens the block valve.
T3 WAIT_VLV_OPEN '//XV-101/DC1/PV_D'=1 Confirms that the block valve

is open.
S4 START_PUMP '//MTR-101/DC1/SP_D':=1; Starts the pump.
T4 WAIT_PUMP_START '//MTR-101/DC1/PV_D'=1 Confirms the pump started.
* IMPORTANT: Step actions use a special assignment operator (:=) and end with a semicolon (;). Transitions use an
equals sign (=) to indicate that when the condition is true, the next step should be made active. Parameter values are
enclosed in single quotes.

The finished SFC looks like the following.
Finishing the SFC Module
 To finish the SFC
1. Select File Properties and set the Primary Control picture to TANK101.
2. Click the Assign to Node button on the toolbar and assign the SFC module to
the controller.
3. Click the Save button and save the SFC module as SFC-START.
4. Quit Control Studio by clicking the Close button in the upper right corner.

Exercise 9: Downloading the Modules
Now that the control modules are all defined, you need to download the control
strategy to the controller, assuming you have a controller configured. If you are
working with a controller placeholder, you can assign the modules to the
placeholder, but you cannot do a download.
There are several different levels of downloads. In the DeltaV Explorer, you can
download:
 individual modules
 the controller node
 the control network, including the workstations and controllers
Important If you are working on a system that is controlling a process, it is recommended that you
do not perform any downloads for this tutorial unless you understand the impact of doing
so.
Note You must load and assign the controller licenses before downloading the modules to the
controller. Loading and assigning licenses is described in Chapter 8.
 To download the modules
1. Open (or restore) the DeltaV Explorer and open System Configuration |
Physical Network | Control Network | CTLR1 (or your controller name) |
Assigned Modules. (This shows you all the modules you have assigned to the
controller.)
2. Point to Control Network, click the right mouse button, and select Download
| Control Network.

PID de Controlador Americano

Uploaded by

Copyright:

Available Formats

PID de Controlador Americano

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PID de Controlador Americano

Uploaded by

Copyright:

Available Formats

D800002X152

Getting Started With Your

Chapter 1 DeltaV System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2 Overview of the Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Chapter 3 Learning About the DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

iv Getting Started with Your DeltaV Digital Automation System

Chapter 5 Creating Operator Pictures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Chapter 6 Using DeltaV Operate in Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Chapter 7 Collecting and Displaying Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Chapter 8 Configuring the Network, Loading and Assigning Licenses,

vi Getting Started with Your DeltaV Digital Automation System

About this Book

x Getting Started with Your DeltaV Digital Automation System

Using the Mouse

Selecting from Menus or Hierarchies

What You Need to Get Started

1. Configure the workstation.

3. Download the workstation setup data.

xii Getting Started with Your DeltaV Digital Automation System

The system hardware consists of the following:

DeltaV System Overview 1-1

DeltaV System Concepts

1-2 Getting Started with Your DeltaV Digital Automation System

DeltaV System Overview 1-3

DeltaV Software Applications

1-4 Getting Started with Your DeltaV Digital Automation System

DeltaV System Overview 1-5

1-6 Getting Started with Your DeltaV Digital Automation System

The Continuous Historian Administration application provides tools to

DeltaV System Overview 1-7

DeltaV Explorer, similar in appearance to the Windows Explorer, is an

You can do many things with this application, including:

1-8 Getting Started with Your DeltaV Digital Automation System

DeltaV Operate Configure

The DeltaV Operate application functions in two modes. In configure mode,

DeltaV System Overview 1-9

1-10 Getting Started with Your DeltaV Digital Automation System

Recipe Studio is used to create and modify recipes. A recipe is a set of

System Alarm Management

DeltaV System Overview 1-11

DeltaV Neural is a collection of tools used to implement neural networks in

1-12 Getting Started with Your DeltaV Digital Automation System

DeltaV PredictPro implements model predictive control of large multivariable

DeltaV System Overview 1-13

The DeltaV Simulate Suite consists of the following products:

Inspect with InSight

Tune with InSight

Tune with InSight provides two basic approaches to loop tuning.

1-14 Getting Started with Your DeltaV Digital Automation System

Batch History View

Batch Operator Interface

DeltaV Operate Run

The DeltaV Operate application functions in two modes. In configure mode, it

DeltaV System Overview 1-15

The MPC Operate application provides an overview to the MPC (Model

Process History View

1-16 Getting Started with Your DeltaV Digital Automation System

DeltaV System Overview 1-17

DeltaV Excel Add-In