Installing and Using the Recipe
Manager NT for the PROVOX System
This manual applies to software version P2.1. For earlier
versions, retain the applicable manuals for those versions.
User Manual
UM41.0:APS311
D4U01541202
Revision B -- March 2000
This manual supercedes the issue dated December 1997.
DeltaV, DOCVUE, ENVOX, Fisher-Rosemount, PROVOX and PROVUE are marks of one of the
Fisher-Rosemount group of companies.
All other marks are the property of their respective owners.
ã 1997, 1999 and 2000 Fisher-Rosemount Systems, Inc. All rights reserved.
Printed in USA
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,
express or implied, regarding the products or services described herein or their use or applicability.
We reserve the right to modify or improve the designs or specifications of such products at any time
without notice.
Your Evaluation Please ...
Name:
iii
Title and Department:
Company:
Years of Experience: ___ Instrumentation ___ Distributed Control
Telephone:
(
)
--
Education: ____Years ____Years College ____Degree
e-mail:
Job Responsibility:
Please indicate your evaluation of this manual. Attach additional sheets with comments as needed.
1. How and when do you use
this manual?
V
V
V
V
V
Read entire manual before attempting task
Read selected sections before attempting task
Read while attempting task
Attempt task first
Read as last resort
2. How well is the manual’s
content organized? Please
explain on a separate
sheet.
V
V
V
V
V
V
Excellent — parallels product’s operation, very usable
Good — representative of the product’s operation, usable
Average — usable but can be improved
Fair — not very usable, should be improved
Poor — not usable, must be improved
No Opinion
Understandable
3. Is the manual’s content
understandable and
applicable to the product’s
operation? Please explain
on a separate sheet.
4. How well do the manual’s
illustrations convey product
information? Please explain
on a separate sheet.
Applicable
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
V
Excellent — very easy to understand,
very applicable
Good — easy to understand, applicable
Average — applicable but some sections not easy to
understand
Fair — not very understandable/applicable, should
be improved
Poor — not understandable/applicable, must be
improved
No Opinion
Excellent — very easy to understand, extremely usable
Good — easy to understand, very usable
Average — fairly easy to understand, usable
Fair — not easy to understand, should be improved, not
very usable
Poor — cannot understand, must be improved, totally
unusable
No Opinion
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
iv
Your Evaluation Please ...
5. Describe the amount of
usable information in this
manual including tables.
Please explain on a
separate sheet.
V
V
V
V
Too much information — not all required to perform task
Proper amount provided — not too much nor too little
Too little information — needed additional information to
perform task
No Opinion
Sections
6. How well is information
cross-referenced in the
manual’s individual sections
and index? Please explain
on a separate sheet.
Index
V
V
V
V
V
V
V
V
V
V
V
V
V
V
Excellent — very easy to locate information,
extremely usable
Good — easy to locate information, very usable
Average — fairly easy to locate information, usable
Fair — not easy to locate information, should be
improved, not very usable
Poor — cannot locate information, must be
improved, totally unusable
Did Not Use
No Opinion
7. How useful is the Glossary?
V
V
V
V
V
Useful
Useful but not complete/accurate
Not Useful
Did Not Use
No Opinion
8. What is your overall
impression of this manual?
Please explain on a
separate sheet.
V
V
V
V
V
V
Excellent — met all needs, extremely usable
Good — met most of my needs, very usable
Average — usable
Fair — should be revised, not very usable
Poor — must be revised, totally unusable
No Opinion
Please FAX or MAIL this form to:
FAX Number: (512) 834-7200
Attention: Technical Documentation Editor
Fisher-Rosemount Systems, Inc.
Technical Documentation Editor
8301 Cameron Road, MD#13
Austin, TX 78754
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
Contents
v
Contents
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
2
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.3
3
3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.1.7
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
Who Should Read This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Revision This Manual Supports . . . . . . . . . . . . . . . . . . . . . . .
What’s New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Is This the Right Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What This Manual Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings, Cautions, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Electronic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Where to Find Answers for Product and Document Questions . . .
2
2
2
3
3
5
8
10
11
11
Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Introducing the Recipe Manager NT System . . . . . . . . . . . . . . . . . . .
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introducing the Recipe Manager NT User Interfaces . . . . . . . . . . . .
DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROVOX Phase Logic Interface (PPLI) Configuration . . . . . . . . . .
The Batch Operator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How Recipe Manager NT Relates to the PROVOX System . . . . . .
14
14
15
17
17
19
21
22
25
Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
Planning the Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .
Environmental Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Electrical installation Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of an Uninterruptible Power Supply . . . . . . . . . . . . . . . . . . . . . .
Grounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ProfessionalPLUS Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Application Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Highway Data Link (HDL) Preparation . . . . . . . . . . . . . . . . . . . . . . . .
28
28
28
29
30
31
31
31
vi
Contents
3.1.8
3.1.9
3.2
3.2.1
3.2.2
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
HDL Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Area Control Network (ACN) . . . . . . . . . . . . . . . . . . . . . . . . .
Post-Installation Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checklists for the DeltaV Application Station . . . . . . . . . . . . . . . . . .
Checklists for the Highway Data Link (HDL) . . . . . . . . . . . . . . . . . . .
33
35
35
35
36
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
4.1
Planning the Software Installation and System Configuration . . . .
4.1.1
Understanding the Recipe Manager NT System . . . . . . . . . . . . . . .
4.1.1.1
Batch Executive Machine and Batch Operator Interface
Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.2
Recipe Manager NT Simulator . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1.1.3
PROVOX Phase Logic Interface Programs Overview . . . . . . . .
4.1.1.4
Batch History Options for the DeltaV Batch Historian or
the Batch Archiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2
Installing the Recipe Manager NT and CHIP NT Software . . . . . . .
4.3
Uninstalling the Recipe Manager NT Software . . . . . . . . . . . . . . . . .
38
39
4
5
5.1
5.2
5.3
5.4
5.5
5.5.1
5.5.2
5.5.3
5.5.4
5.6
5.6.1
5.6.1.1
5.6.1.2
5.6.1.3
5.6.1.4
5.6.2
5.7
39
41
41
41
42
53
Recipe Manager NT Configuration . . . . . . . . . . . . . . . .
57
Configuring PROVOX Phases for Use With DeltaV Batch . . . . . .
Engineering Personnel Requirements . . . . . . . . . . . . . . . . . . . . . . . . .
System Requirements and Limitations . . . . . . . . . . . . . . . . . . . . . . . .
The PPLICFG Program Requirements . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PPLICFG Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Opening Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Invoking PPLICFG Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Navigating the Tree Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PPLI Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Understanding the PROVOX Phase Connection to
the Equipment Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding and Editing PROVOX Points . . . . . . . . . . . . . . . . . . . . . . .
Linking a Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing a Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Copy Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a PROVOX Watchdog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flexible Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
60
61
61
63
63
64
65
66
67
67
68
69
69
70
72
72
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
5.8
5.9
5.9.1
5.9.2
5.10
6
6.1
6.1.1
6.1.2
6.1.3
6.1.4
6.2
6.3
6.3.1
6.3.2
6.3.3
6.4
6.4.1
6.4.2
6.5
6.5.1
6.5.2
6.5.2.1
6.5.2.2
6.5.2.3
6.5.2.4
6.5.2.5
6.5.3
6.5.4
6.5.4.1
6.5.4.2
6.5.4.3
6.5.5
6.6
6.6.1
6.6.1.1
Contents
vii
Modifying or Changing Recipes on Existing Systems . . . . . . . . . . .
Change Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Batch Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Changed Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameter Reference Configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
75
76
76
77
78
Phase Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Understanding Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Logic Components and Communications . . . . . . . . . . . . . . .
Phases at the Batch Executive Machine . . . . . . . . . . . . . . . . . . . . . .
Equipment Phase Connections at PPLI . . . . . . . . . . . . . . . . . . . . . .
Equipment Phases at the UOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a New Phase in the PROVOX System . . . . . . . . . . . . . . . .
Recipe Manager NT/PPLI Requirements for Phase Logic . . . . . . . .
State Transition Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Register Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT Data Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROVOX Capabilities and Characteristics . . . . . . . . . . . . . . . . . . . . .
Unit Points with Operation Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LCPs with FST Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT for PROVOX Phase Logic Interface Solution
DCD Control Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit Operation Shell for PROVOX Phase Logic . . . . . . . . . . . . . . .
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Parameter Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHIP ASCII Point Considerations . . . . . . . . . . . . . . . . . . . . . . . . .
Failure Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Connections for Recipe Manager NT Software . . . . . . . .
Importing the Shell Configuration into the ENVOX Database . . . .
FST Shell for PROVOX Phase Logic . . . . . . . . . . . . . . . . . . . . . . . . .
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Execution Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Register Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROVOX Unit Operation and Phase Name File for PPLI . . . . . . .
Phase logic Design and Programming . . . . . . . . . . . . . . . . . . . . . . . .
Register Interactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COMMAND Register and STATUS Register . . . . . . . . . . . . . . . .
82
82
84
84
84
84
86
86
90
92
95
95
97
97
98
101
102
103
104
105
107
107
110
110
113
114
114
117
119
119
viii
Contents
6.6.1.2
6.6.1.3
6.6.1.4
6.6.1.4.1
6.6.1.4.2
6.6.1.4.3
FAIL_INDEX Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OWNER Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAUSE, PAUSED and SINGLE_STEP Registers . . . . . . . . . . . .
PROVOX LCP PAUSE Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROVOX Unit Operation PAUSE Logic . . . . . . . . . . . . . . . . . . .
Handling the PAUSE, RESUME and SINGLE_STEP
Commands from the PROVOX Console . . . . . . . . . . . . . . . . . .
REQUEST Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PHASE ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STEP_INDEX Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNIT Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch ID Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DeltaV Watchdog Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
# of Request Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integer Prompt Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Floating Point Prompt Register . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Boolean Prompt Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
String Prompt Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Use of the DOWNLOAD Command . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Request Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the REQUEST Register and Request Arguments . . . . . .
Phase Request Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Phase Request Information and Examples . . . . . . . . . .
Request Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Direct vs. Indirect Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PROVOX Operation Code Example — Downloading
Phase Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FST Example for Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upload Report Values — Journal Entries . . . . . . . . . . . . . . . . . . .
Send Messages to Other Phases . . . . . . . . . . . . . . . . . . . . . . . . . .
141
142
143
144
Recipe Manager NT Operation Overview . . . . . . . . . .
149
The Recipe Manager NT for PROVOX Operating Environment . . .
Overview of the Batch Operator Interface Operations . . . . . . . . . .
Overview of the PROVOX Console Operations . . . . . . . . . . . . . . . .
Interoperability Within the Recipe Manager NT Environment . . . . .
The Recipe Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
151
151
152
152
6.6.1.5
6.6.1.6
6.6.1.7
6.6.1.8
6.6.1.9
6.6.1.10
6.6.1.11
6.6.1.12
6.6.1.13
6.6.1.14
6.6.1.15
6.6.2
6.6.3
6.6.3.1
6.6.3.2
6.6.4
6.6.4.1
6.6.4.2
6.6.4.3
6.6.4.4
6.6.4.5
6.6.4.6
7
7.1
7.1.1
7.1.2
7.2
7.2.1
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
120
121
121
122
124
125
127
128
129
130
130
131
131
131
131
132
132
132
135
135
136
140
141
141
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
7.2.2
7.3
7.3.1
7.3.2
7.3.3
7.3.4
7.3.5
7.3.6
8
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.2
8.2.1
8.2.2
8.3
8.4
A
A.1
A.1.1
A.1.2
A.2
B
B.1
B.2
Contents
ix
The DeltaV Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interaction Between the Recipe Manager NT and
PROVOX Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
An ISA S88 Operation Approach for PROVOX Systems . . . . . . . .
The Control DCD Operating Method . . . . . . . . . . . . . . . . . . . . . . . . .
The Manual Equipment Phase Operation . . . . . . . . . . . . . . . . . . . . .
Failure Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operator Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
153
153
154
154
155
155
155
Using the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
157
PROVOX Point Interaction with Recipe Manager NT Batch Control
PROVOX Point Values Used for Recipe Manager NT
Equipment Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT Phase Status Not Related to
PROVOX Point Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Failure Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PPLI Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Control from the PROVOX Console . . . . . . . . . . . . . . . . . . .
Equipment Phases Based on Unit Operations . . . . . . . . . . . . . . . . .
Equipment Phases Based on LCP FSTs . . . . . . . . . . . . . . . . . . . . . .
Using the PPLI Diagnostics Screen . . . . . . . . . . . . . . . . . . . . . . . . . . .
Warm Start Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
157
159
159
160
163
164
164
165
165
Installation Considerations . . . . . . . . . . . . . . . . . . . . . .
167
Installing the POC/BOI Applications on one Application Station with
the Batch Executive on a Separate Application Station . . . . . . . . .
Installing BOI/POC on the Application Station . . . . . . . . . . . . . . . . .
Installing the Batch Executive/RMNT Application on
a Separate Application Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing POC/BOI and the Batch Executive/RMNT on
the Same Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
153
157
168
168
168
169
Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . .
171
Upgrading from RMNT 1.0 TO RMNT 2.1 . . . . . . . . . . . . . . . . . . . . . .
Upgrading from Activity Points to RMNT 2.1 . . . . . . . . . . . . . . . . . . .
171
173
x
Contents
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
175
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
Contents
xi
Figures
Figure 2-1.
Figure 2-2.
Figure 2-3.
Figure 2-4.
Figure 2-5.
Figure 3-1.
Figure 3-2.
Figure 4-1.
Figure 5-1.
Figure 6-1.
Figure 6-2.
Figure 6-3.
Figure 6-4.
Figure 7-1.
The PROVOX System with the Recipe Manager NT System .
The DeltaV Explorer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Recipe Studio Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The PPLI Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . .
The Batch Operator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Batch Executive Machine Location . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT Wiring for Twisted-Pair Hubs . . . . . . . . . .
A Simplified Recipe Manager NT System Arrangement . . . . .
PPLI Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT Phase Components and Communication
Recipe Manager NT State Transition Diagram . . . . . . . . . . . . .
PPLIOPER Shell Flow Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example PFC for the DOWNLOAD Command . . . . . . . . . . . . .
Components of Recipe Manager NT for PROVOX Operation
14
18
20
22
24
32
34
40
64
83
87
101
133
150
xii
Contents
Installing and Using the Recipe Manager NT for the
PROVOX System
(Revision B -- March 2000)
Tables
Table 1-1.
Table 2-1.
Table 2-2.
Table 2-3.
Table 4-1.
Table 4-2.
Table 5-1.
Table 5-2.
Table 6-1.
Table 6-2.
Table 6-3.
Table 6-4.
Table 6-5.
Table 6-6.
Table 6-7.
Table 8-1.
Type Styles Used in this Manual . . . . . . . . . . . . . . . . . . . . . . . .
Key Recipe Manager NT Hardware Components . . . . . . . . . .
Overview of Recipe Manager NT Software Components and
Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Key Recipe Manager NT Software Components . . . . . . . . . .
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses . . . . . . . . . . . . .
Recipe Manager NT and CHIP NT Uninstallation Steps,
Screens, and Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing an Existing System . . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT Module Name Changes . . . . . . . . . . . . . .
Recipe Manager NT States . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PPLICFG Phase Register Definitions . . . . . . . . . . . . . . . . . . . .
Recipe Manager Data Items . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ENVOX Configuration Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Logic Register Allocations . . . . . . . . . . . . . . . . . . . . . . .
Phase Request Programming . . . . . . . . . . . . . . . . . . . . . . . . . .
Phase Communication Purposes . . . . . . . . . . . . . . . . . . . . . . . . .
Recipe Manager NT for the PROVOX System
Equipment Phase Point Values . . . . . . . . . . . . . . . . . . . . . . . .
9
15
16
16
42
55
75
76
88
91
93
108
117
136
144
158
Introduction F Section 1
1
Figure 1-Table 1
1
1 Introduction
Recipe Manager NT for the PROVOXr System is a member
of Fisher-Rosemount System’s Performance Software for
Batch Execution. Recipe Manager NT enables users to
effectively manage recipes and execute batches from a
graphical Windows NT platform. Recipe Manager NT for the
PROVOX system addresses the challenges facing batch
manufacturers today and in the future, including:
J
J
J
J
Saving time by working in a familiar environment —
The Recipe Manager NT user interfaces save engineering
and operating time by providing a familiar look and feel for
Windows NT application users.
Improving time to market by eliminating software
coding — The Recipe Manager NT system has full IEC
1131-3 compliant procedure function chart (PFC)
capability.
Simplifying the total engineering effort — Included with
the Recipe Manager NT software is a set of templates to
guide the configuration of the PROVOX-resident
sequences.
Reducing engineering and set-up costs with simple
integration — The PROVOX Phase Logic Interface
(PPLI) software guides you through the tasks to join the
Recipe Manager NT system with the PROVOX control
system.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
2
Section 1 F Introduction
J
Simplifying regulatory compliance by exporting batch
data — The Recipe Manager NT event journal can be
exported to a relational database for integration with other
production data.
The goal of this planning and installation manual is two-fold:
J
J
1.1
To provide an overview of the Recipe Manager NT
functionality by describing its basic architecture.
To describe the preparation and procedures for installing
the major hardware and software components and for
configuring the Recipe Manager NT system.
Who Should Read This Manual?
This manual assumes the reader is familiar with the Microsoft
Windows NT environment, has a working knowledge of the
equipment, resources, and processes of the batch plant in
which the Recipe Manager NT system will be running, and is
trained in the functions and use of both the PROVOX process
control system and the DeltaVt process control system.
1.2
Product Revision This Manual Supports
This manual supports the version of Recipe Manager NT for
PROVOX configuration software, P2.1. For earlier versions,
retain the applicable manuals for those versions, which runs
on Windows NT, version 4.0.
1.3
What’s New in this Release
The following functions are new in this release of the Recipe
Manager NT software.
J
Flexible points
J
OPC Communication Transport
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Introduction F Section 1
J
1.4
3
Recipe Management functionality from DeltaV Batch
software
Is This the Right Manual?
This manual makes up the documentation for the Recipe
Manager NT system.
The Contents and Index pages are useful for locating
information, and the Glossary for defining terms. For further
information, see the subsection, Related Documents, on
page 5.
After Recipe Manager NT is installed and running, you can
use the online help features linked to the software. Both
procedural and context-sensitive online help are available in
all Recipe Manager NT windows during every part of using
this application. To get context-sensitive help for data fields or
dialog boxes, select the field and press the F1 key.
This manual describes installation and maintenance
procedures for products that have been tested to be in
compliance with appropriate CE directives. To maintain
compliance, these products must be installed and
maintained according to the procedures described in
this document. Failure to follow the procedures may
compromise compliance.
1.5
What This Manual Contains
The sections and appendixes in this manual are described
below.
Section 1 — Introduction: Describes the purpose and
contents of this manual, provides references to related
documents, and explains typographical conventions used
throughout.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
4
Section 1 F Introduction
Section 2 — Product Overview: Introduces the Recipe
Manager NT system, describes its major concepts and
functions, presents its hardware and software components,
and explains how it relates to the PROVOX system.
Section 3 — Hardware Installation: Presents planning and
installation considerations, describes the preparation and
installation steps, and provides a post-installation checklist.
Section 4 — Software Installation: Describes how to install
the Recipe Manager NT and CHIP NT software.
Section 5 — The PROVOX Phase Logic Interface (PPLI):
Describes the configuration requirements for PPLI, explains
how to navigate using the tree control, and introduces the
linking and editing of phases.
Section 6 — Recipe Manager NT Phase Programming:
Introduces PROVOX capabilities and characteristics, presents
the PPLI solution, and describes phase logic design and
programming.
Section 7 — Operations Overview: Introduces the Recipe
Manager NT and PROVOX components that enable
operation of a batch process, previews the operator tasks
done from the Batch Operator Interface and the PROVOX
console, and briefly describes batch states, commands, and
modes.
Section 8 — Using Recipe Manager NT and PPLI with the
PROVOX System: Describes the interaction of the Recipe
Manager NT and PROVOX systems for batch control, with
descriptions of PROVOX points, manual control of phases,
use of PPLI diagnostics, and warm start considerations.
Appendix A — Installation Considerations: Describes the
installation procedures necessary for the user who desires to
install the FRSI PROVOX Operator Console (POC), the
DeltaV Batch Operator Interface (BOI), and RMNT
applications on the same Application Station computer.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Introduction F Section 1
5
Installation of BOI/POC software on Server platforms is not
supported.
Appendix B — Migration Considerations: Describes the
issues involved for customers who currently create
batches/recipes using Activity Points (PROVOX), or who are
upgrading from RMNT (1.0).
Glossary — Lists acronyms, abbreviations, and terms and
definitions related to the Recipe Manager NT system, batch
manufacturing, and process control.
Index — Lists topics and references to pertinent information
presented in this manual.
1.6
Related Documents
Refer to the following documents for detailed information
about other PROVOX products used with the Recipe
Manager NT system:
J
DeltaV Batch book online
J
DeltaV Release Notes
J
Installing Your DeltaV System
J
Planning the Installation (PN4.002)
J
AC and DC Power & Ground Wiring (PN1:003)
J
Signal Wiring and Data Highway Guidelines (PN1:004)
J
J
J
Environmental Conditions for Instrumentation Systems
(PN4:006)
Lightning Protection Guidelines for Instrumentation
Systems (PN4:007)
Installing the 20-Series (SR90) Controller Family
(PN2.2:CL6633)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
6
Section 1 F Introduction
J
J
J
J
J
J
J
J
J
J
J
J
J
Configuring the 20-Series (SR90) Controller Family
(CE10.0:CL6633:VOL1&2)
Maintaining the 20-Series (SR90) Controller Family
(MM3.0:CL6633)
Installation and Maintenance of the SRx Controller Family
(PN8.0:CL6640)
Configuring the SRx Controller Family
(CE12.0:CL6640:VOL1&2)
Installing DC9400-Series Operator Workplace with
DC9500 WS-Series Console Electronics
(PN7.1:DC9400:OWP)
Installing and Managing DC9440-Series Operator
Workplace Console Software (PN7.2:DC9440)
Configuring DC9440-Series Operator Workplace Console
Software (CE11.0:DC9440)
Using DC9440-Series Operator Workplace Console
Software (UM13.0:DC9440)
Installing and Maintaining the Types DH6032 Highway
Data Link (HDL) and DH7742 Highway II Bridge
(PN5.1:DH6032)
DH6040-Series Process Network Communications
Products (BU4.10:DH6040)
Configuring DH6200-Series Computer/Highway Interface
Package (CHIP) Software (CE8.0:DH6200)
Technical Reference Information for DH6200-Series
Computer/Highway Interface Package (CHIP) Software
(TR2.0:DH6200)
Using DH6200-Series Computer/Highway Interface
Package (CHIP) Software (UM3.0:DH6200)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Introduction F Section 1
J
J
J
J
J
J
7
Type DH6212 Computer/Highway Interface Package
(CHIP NT) (BU4.10:DH6212)
Installing Type DH6212 Computer/Highway Interface
Package (CHIP NT) Software (PN3.1:DH6212)
Installing the PROVOX Highway II Communications
System (PN4.2:DH7700)
Using ENVOXr Configuration Software (UM6.1:SW3151)
Getting Started With The PROVOX Operator Console
Software (PN9.2:NT2100)
Installing PROVOX Operator Console Hardware
(PN9.1:NT2100)
Note ... Fisher-Rosemount Systems’ documents are
periodically revised. Before using any manual,
confirm that it corresponds to the revision level of
the software you are using. The title page lists the
manual’s printing date and the versions of the
product or application package covered.
Contact your Fisher-Rosemount Systems sales
office or representative for copies of individual
manuals.
For detailed information on batch operations and control
requirements, refer to the following documents:
J
J
J
ISA-S88.01 Batch Control Part 1: Models and Terminology
IEC-1131-3 Programmable Controllers, Programming
Languages
NAMUR Guidelines: Normen Arbeitsgemeinschaft für
Mess-ûnd Regeltechnik in der Chemischen Industrie
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
8
1.7
Section 1 F Introduction
Manual Conventions
This manual uses the following conventions to convey
information:
J
J
J
J
J
J
Acronyms and Abbreviations — Terms are spelled out
in their entirety the first time they appear in the text.
Thereafter, only the acronym or abbreviation is used. The
glossary defines all of the acronyms and abbreviations
used in this manual. The same definitions can be obtained
online by choosing the Help --> Glossary menu
command, then selecting an acronym, abbreviation, or
term in the Glossary window.
Cross References — References to other
Fisher-Rosemount Systems’ documents give the
document name and number.
Key References — This manual refers to keys found on a
typical IBM/MS Windows 95-compatible keyboard. See
Table 1-1 on page 9 for how keys are named and
explained, if necessary.
Menu References — The Recipe Manager NT software
displays a menu name’s bar across the top of most
application windows. Each menu name and its drop-down
command list are explained.
Toolbar and Tool References — The Recipe Manager
NT software displays a toolbar below the menu bar on
most application windows. The tools on the toolbar give
you quick access to many commands and actions.
Individual tools are also available for particular tasks.
Type Style Conventions — Table 1-1 lists the type styles
used in this manual to distinguish different kinds of
information.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Introduction F Section 1
Table 1-1.
9
Type Styles Used in this Manual
When Text Appears This Way...
It Means...
Installing and Using Recipe
Manager NT for the PROVOXr
System
The title of a manual.
BACKUP
An operating mode, alarm state, status, instruction,
operand, or keyword.
Choose Help --> About Recipe
Manager NT from the menu bar
Menu options you choose (in the order given)
Press the Enter key...
Press the F12 key...
A key name is shown as it appears on the keyboard. An
explanation of the key’s acronym or function, if needed,
immediately follows the first reference to the key. (Note
that some keyboards label the Enter key as Return or
use this symbol: ¿.)
Press the Ctrl L key
combination...
Press and hold down the first key while pressing the
second key, then release both keys.
Click the OK button...
Either move the cursor to point to the button, then click
the primary button on the mouse, or press the Tab key
and up or down arrow keys to select (or highlight) the
button, then press the Enter key.
Username:BAD BATTERY$
WRITE SYS$OUTPUT “”
A system prompt, text that appears on the screen, or
text in a source file
example3.trn
A command or text you should enter. You can enter
commands or text either in uppercase or lowercase
letters, since the Recipe Manager NT software is not
case sensitive.
my_data
Text that you replace with your own values when issuing
commands. For example, you would replace my_data
with an appropriate value.
An object is¼
A new term or a word being emphasized.
Do not set¼
A word or term given special emphasis so you will not
miss the idea being presented.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
10
1.8
Section 1 F Introduction
Warnings, Cautions, and Notes
Warnings, cautions, and notes attract attention to essential or
critical information. The following examples explain the types
of information included in each.
Warning ... Warnings appear like this. They describe critical
procedures, conditions, statements, and so forth,
that must be followed to prevent a safety risk to your
health or an injury risk to your body.
Caution ... Cautions appear like this. They describe
procedures, conditions, statements, and so forth,
that must be followed to prevent equipment
malfunction or data loss.
Note ... Notes appear like this. They contain additional
information that make the Recipe Manager NT
tasks easier or increase your understanding.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Introduction F Section 1
1.9
11
Electronic Documentation
This manual is also available in DOCVUEt Electronic
Documentation, which is a CD-ROM set. The CDs contain
current and past Fisher-Rosemount Systems’ sales literature,
manuals, and technical service bulletins.
The DOCVUE CDs run on UNIX and Microsoft Windows
systems. They offer advantages such as full-text searching,
menus, bookmarks, browsing, and point-and-click navigation.
To find out more about DOCVUE documentation, contact your
Fisher- Rosemount Systems representative or sales office.
1.10
Where to Find Answers for Product and
Document Questions
Fisher-Rosemount Systems’ goal is to provide products and
documentation that excel in meeting your needs. If you have
questions or comments about this product, please contact
your Fisher-Rosemount Systems representative or sales
office.
To help us evaluate how well this manual fills your needs,
please complete and send in the Reader Evaluation Form
located in the front of this manual. We also appreciate your
suggestions on ways to improve any page of the manual.
Please copy the page and mark it up with your suggestions,
then return it to us with the evaluation form.
Thank you for providing this information.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
12
Section 1 F Introduction
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
13
Figure 2-Table 2
2
2 Product Overview
The Recipe Manager NT for the PROVOXÒ System is a
complete batch production solution. The Recipe Manager NT
system combines the power of the PROVOX distributed
control system with the ease of graphical configuration in a
familiar MS Windows NT environment. Recipe management is
provided by DeltaVt Batch software.
The Recipe Manager NT system enables users to configure
physical and procedural models, create and execute recipes,
and seamlessly integrate batch actions with the control
system. It also allows you to generate and store production
information in a relational database.
This section introduces the key hardware and software
components that make these Recipe Manager NT features
possible. It also provides an overview of the Recipe Manager
NT system by introducing the major concepts and functions.
This section contains these subsections:
J
J
J
Introducing the Recipe Manager NT System
Introducing the Recipe Manager NT User Interfaces and
the DeltaV User Interfaces
How Recipe Manager NT Relates to the PROVOX System
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
14
Section 2 F Product Overview
2.1
Introducing the Recipe Manager NT System
This subsection introduces the key hardware and software
components and their functions in the Recipe Manager NT
system.
2.1.1
Hardware
Figure 2-1 on page 14 shows the major hardware
components of a typical Recipe Manager NT system.
Table 2-1, on page 15, lists the major hardware components
and their purposes in the Recipe Manager NT for the
PROVOX system.
For detailed hardware descriptions and installation
instructions, see Section 3.
Plant Network
Batch Operator
Interface
Hub
DeltaVt ACN
Router
HDL
PROVOXr Highway
HDL
PROVOX
Operator
Console
Client
Figure 2-1.
PROVOX
Controller
POC
Server
Batch
Executive
RMNT
Software
ProPlus
Example shows only POC.
The PROVOX System with the Recipe Manager NT System
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
Table 2-1.
15
Key Recipe Manager NT Hardware Components
This Hardware
Component ¼
Serves This Purpose ¼
DeltaVt Application
Station
The computer supplied by Fisher-Rosemount Systems for the purpose of
running the Batch Executive. This computer also has the Windows NT
Server version 4.0 software installed when it ships from the factory.
Batch Operator
Interface
One or more computers running the Batch Operator Interface Client
software. These computers must have the DeltaV Application station or
remote station software installed and licensed.
Highway Data Link
(HDL)
A device that connects the Batch Executive machine to the PROVOX
Highway. The HDL allows the Batch Executive machine and CHIP NT
software to communicate with the PROVOX control system over an
Ethernet link using the TCP/IP protocol. Another HDL links each PROVOX
operator console (OWP or POC) to the Highway.
PROVOXr Console
(OWP, PROVUEr
Console, or POC)
A graphical user interface (GUI) terminal or device that an operator uses
for the lower-level PROVOX process control. Higher-level recipe control is
performed at the BOI node.
PROVOX Controller
A PROVOX control device that executes the lowest levels of batch
processes (known as phases), while the Recipe Manager NT system
supervises these phases and sequences them to run batch recipes.
Hub
A device that connects one or more Batch Operator Interface Stations to
the Batch Executive machine on DeltaV Area Control Network, and to a
router if a plant network connection is required.
Router
A device that isolates the process network formed by the hub from general
plant network traffic.
ProfessionalPLUS
The computer supplied by Fisher--Rosemount Systems for the purpose of
running the DeltaV software. This computer also has the Windows NT
Server version 4.0 software installed when it ships from the factory
2.1.2
Software
Table 2-2 shows the major software components of the
Recipe Manager NT system. Arrows depict the relationships
between the components and external software. Table 2-3
lists the major software components and their functions.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
16
Section 2 F Product Overview
Table 2-2.
Overview of Recipe Manager NT Software Components and
Operations
ProfessionalPLUS
Batch Executive
Other Stations
Workstation
Machine
DeltaVt Database
Equipment & Recipe Download
from ProfessionalPLUS
Workstation
Batch Operator Interface
DeltaV Explorer
PPLI Configuration & Mapping
to PROVOX Phases
Recipe Studio
Recipe Studio
Batch Operator Interface
Other Applications
Batch Operator Interface
Batch Executive
PPLI Runtime
PAS OPC Server
CHIP NT
Table 2-3.
Key Recipe Manager NT Software Components
This Software
Component ¼
Performs This Function ¼
Batch Executive
The batch engine running on the DeltaVt Application Station that
coordinates the execution of recipes, the equipment database, and each
Batch Operator Interface during production. The DeltaV Batch Executive
also generates batch event data and communicates with the PPLI.
DeltaV Explorer
Integrates configuration activities into one interface for developing recipes
and the equipment database. Runs on the ProfessionalPLUS Workstation.
Recipe Studio
Configures recipes using procedural function charts.
Batch Operator
Interface
Displays that communicate with the Batch Executive and enable operators
to monitor and interact with executing recipes. Runs on the Batch
Executive machine or the Batch Operator Interface machine.
Simulator
Simulates control system phases for testing and demos.
PROVOXr Phase Logic
Interface (PPLI)
Run-time interface between the DeltaV Batch Executive and the PROVOX
system. Runs on the Batch Executive machine.
PPLI Configurator
Configures links between Recipe Manager NT phases and PROVOX
operations and function sequence tables. Runs on the Batch Executive
machine.
PPLI Shell
Templates of operations and function sequence tables used to assist in
writing phases for the PROVOX controller.
Computer/Highway
Interface Package
(CHIP NT)
Data interface between the Recipe Manager NT personal computer PPLI
software and the PROVOX system, using a Highway Data Link (HDL).
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
17
For information on licensing your DeltaV software, refer to the
Getting Started with DeltaV manual in either its printed form
or from the DeltaV Books online.
2.2
Introducing the Recipe Manager NT User
Interfaces
Modularity and graphical configuration are characteristics of
all of the Recipe Manager NT user interfaces, which include
the DeltaV Explorer, Recipe Studio, PROVOX Phase Logic
Interface (PPLI), and Batch Operator Interface. All of these
interfaces are described in the following subsections.
2.2.1
DeltaV Explorer
The DeltaV Explorer is an engineering interface that allows
you to configure and maintain your Recipe Manager NT
configuration. The DeltaV Explorer provides a Microsoft
Explorer-style browser with point-and-click access to all the
components of your area model. For access to the DeltaV
Explorer, on your ProfessionalPLUS Workstation, select Start
--> DeltaV --> Engineering --> DeltaV Explorer.
The DeltaV Explorer is the main application for entering,
viewing, and maintaining the components of the DeltaV
database. The major components you will use are the
equipment configuration and the recipe configuration. After
entering the appropriate configuration, you use the DeltaV
Explorer to download the configuration to your Batch
Executive machine. See Section 5.1 for an overview of the
entire configuration procedure.
Figure 2-2 on page 18 illustrates the DeltaV Explorer window.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
18
Section 2 F Product Overview
Figure 2-2.
The DeltaV Explorer Window
For more information about the DeltaV Explorer, refer to the
DeltaV Batch book online.
2.2.2
Recipe Studio
The DeltaV Recipe Studio application is used to create and
modify recipes. Recipes are any series of steps used in a
batch process. This includes phases, operations, unit
procedures and procedures. A recipe can be as simple in
design as a single phase, or as complex as a series of
procedures that have embedded unit procedures, operations,
and phases.
Figure 2-3 on page 19 illustrates the Recipe Studio window.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
Figure 2-3.
19
The Recipe Studio Window
Recipes consist of descriptions, formulas, equipment
requirements, and procedures used to make a batch. The
Recipe Studio lets you graphically configure and organize all
of this information.
You can construct recipes graphically using procedural
function charts (PFCs), as specified in the IEC1131-3
standard. You can also change formulation parameters
without programming. Simply select parameters from a list,
change the recipe flow by moving graphic objects on the
screen, or delete operations by changing the PFC.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
20
Section 2 F Product Overview
For more information about Recipe Studio, including
Procedural Function Charts (PFCs) and the development of
control strategies, refer to the DeltaV Batch book online.
2.2.3
PROVOX Phase Logic Interface (PPLI) Configuration
The PROVOX Phase Logic Interface contained within the
Batch Executive machine enables communication between
the recipe phases and the actual sequences implemented in
the PROVOX controller.
The PPLI configuration window provides a familiar look and
feel for Windows NT application users. To save engineering
time, you can use the Copy Template tool to copy an existing
phase linked to a PROVOX point, with all its characteristics.
To avoid configuration errors, the PPLI displays a validation
icon to indicate if an item is correctly connected to a PROVOX
point.
As the recipe executes, the PPLI collects batch report data
and downloads formulation data and commands, and returns
state or status information.
Figure 2-4 on page 21 illustrates the PPLI Configuration
window.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
Figure 2-4.
2.2.4
21
The PPLI Configuration Window
The Batch Operator Interface
The DeltaV Batch Operator Interface application is the
graphical interface used by the operator to perform most
batch operations.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
22
Section 2 F Product Overview
The DeltaV Batch Operator Interface provides operators with
screens that allow them to do the following (if appropriate
permissions have been granted):
J
J
J
J
J
J
Create batches from the list of recipes released to
production
Control and monitor recipe-based batches through the
use of Start, Hold, Restart, Stop, and Abort commands
Provide advanced batch control (change the mode of a
batch, bind equipment to a recipe, scale a recipe, or run a
segment of a recipe)
Acquire and release batch resources and monitor
resource arbitration
Control and monitor individual phases
Respond to prompts for parameter input (depending upon
how the phases are defined)
J
View event logs of current or past batches
J
Monitor, acknowledge, and clear batch-related alarms
Figure 2-5 on page 23 illustrates the Batch Operator
Interface.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
Figure 2-5.
23
The Batch Operator Interface
For more information on the Batch Operator Interface, refer to
the DeltaV Batch book online.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
24
2.3
Section 2 F Product Overview
How Recipe Manager NT Relates to the
PROVOX System
The Recipe Manager NT system works in conjunction with
PROVOX controllers to execute batch recipes. The controllers
are responsible for executing the lowest levels of control
(called phases) and the Recipe Manager NT system is
responsible for supervising these phases and sequencing
them to execute the recipes.
The Recipe Manager NT system performs a similar function to
an Activity point that a PROVOX console can execute. Since
they work in different ways, the Recipe Manager NT system
and Activities each provide some unique capabilities.
Normally, a single PROVOX system would use either the
Recipe Manager NT system or Activities, not both, as they
represent different philosophies. A significant amount of work
would be required to modify an Activity-based system to use
the Recipe Manager NT system.
The Recipe Manager NT system uses CHIP NT software and
an HDL to communicate with the PROVOX system. CHIP NT
software must be configured to receive certain points that
reside in the PROVOX controller — primarily units, logic
control points (LCPs) and discrete control device (DCD)
points — so the Recipe Manager NT system can access
them.
The PROVOX controllers must be configured in accordance
with the phase logic interface that the Recipe Manager NT
system expects. A set of shell operations and function
sequence tables (FSTs) are provided to facilitate this. The
shell operations and FSTs are loaded into the ENVOXR
configuration and the user makes copies of them before
starting to configure a new phase.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Product Overview F Section 2
25
The Recipe Manager NT system does not directly
communicate with the PROVOX console devices (OWP, POC
or PROVUE console). An operator will often use both the
Batch Operator Interface and a console to access all the
information required. The console is the user interface for the
lower-level process control, while the Batch Operator
Interface is the user interface for higher-level recipe control.
A POC client may be installed on a Batch Operator Interface
machine on which the Batch Operator Interface is also used.
However, it is not recommended that you use the POC client
on the same station as the Batch Executive.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Hardware Installation F Section 3
27
Figure 3-Table 3
3
3 Hardware Installation
This section provides hardware installation information for the
Recipe Manager NT system. This section is intended for
those who plan, install, or maintain the Recipe Manager NT
system hardware.
While the Recipe manager NT system uses hardware from
both the PROVOX and DeltaVt environments, it is not the
intent of this section to provide a complete description of the
installation requirements for these systems. It is assumed that
the reader has some experience with installing these
systems. Please refer to the appropriate hardware installation
sections in the respective manuals if further understanding is
required for these systems.
This section contains the following subsections:
J
Planning the Hardware Installation
J
Post-Installation Checklists
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
28
3.1
Section 3 F Hardware Installation
Planning the Hardware Installation
This subsection provides information for planning the physical
and electrical installation of the DeltaV Application Station, its
components, and related Recipe Manager NT assemblies.
3.1.1
Environmental Considerations
Refer to the manual, Environmental Considerations for
Instrumentation Systems (PN1:006), to verify that the plant
environment satisfies the requirements for reliable
instrumentation system operation.
For additional information on physical and electrical planning,
consult the following manuals:
J
Planning the Installation (PN1:002)
J
AC and DC Power & Ground Wiring (PN1:003)
J
Signal Wiring and Data Highway Guidelines (PN1:004)
J
J
J
J
3.1.2
Installing the PROVOXR Highway II Communications
System (PN4.2:DH7700)
Installing and Maintaining the Types DH6032 Highway
Data Link (HDL) and DH7742 Highway II Bridge
(PN5.1:DH6032)
Installing Your DeltaV Scalable Process System (Part No.
D800001X062 July 1999)
Fieldbus Supplement to Installing Your DeltaV Scalable
Process System (Part No. D800003X062 July 1999)
Electrical installation Planning
Proper electrical installation of the Recipe Manager NT
system includes the following:
J
Grounding
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Hardware Installation F Section 3
J
Power connections
J
Highway Data Link (HDL) connections
J
Monitor connections
J
DeltaV Application Station connections
29
Note ... All power and ground wiring practices must conform
to applicable federal, state, and local codes and
regulations.
Use the guidelines in the manual, AC and DC Power &
Ground Wiring (PN1:003), to verify the plant power source is
acceptable for use with a process control instrumentation
system. Many of the problems encountered with
instrumentation systems are due to noisy power sources,
improper voltage levels, and instrumentation grounding.
Unfavorable environmental conditions can also contribute to
electrical problems.
3.1.3
Use of an Uninterruptible Power Supply
It is recommended that an uninterruptible power supply (UPS)
be installed to provide power to the DeltaV Application Station
in the event of a power failure. With a UPS unit, the DeltaV
Application Station retains its operating system and
configuration data for a limited amount of time.
Fisher-Rosemount Systems offers a UPS as an option. If a
plant-wide UPS already exists, it is recommended that the
DeltaV Application Station be connected in the appropriate
manner to that UPS system.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
30
Section 3 F Hardware Installation
Caution ... A ferro-resonant UPS may produce a magnetic field
that can cause interference with VDUs. To avoid this
interference, plan the control room grouping so
there is a space of at least 3 ft (0.9 m) between the
UPS and any VDU.
3.1.4
Grounding
Poor or faulty grounding are among the most common causes
of instrumentation problems. Instrumentation grounding
should:
J
J
J
J
Conform to all applicable federal, state, and local electrical
code requirements for proper system grounding.
Connect to a single-point ground as defined in the
manual, AC and DC Power & Ground Wiring (PN1:003).
This applies to all grounding systems.
Ensure the recommended resistance from any ground
connection in the instrumentation system to true
earth-ground, not exceeding 1 ohm, with a maximum
allowable resistance of three ohms. A grounding path
resistance of 1 ohm or less minimizes phantom errors that
result from instrumentation-ground-circuit-induced
voltages and ground current flow.
Be at least as good as any other ground system in the
plant.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Hardware Installation F Section 3
3.1.5
31
ProfessionalPLUS Workstation
The ProfessionalPLUS Workstation must be installed
according to DeltaV Installation practices. The
ProfessionalPLUS workstation must be installed in a user
accessible location as it is used to configure the Batch
Executive machine. It can also be used to run Batch Operator
Interface.
For additional information on this topic and information on
DeltaV ProfessionalPLUS workstation connections, refer to
the Installing Your DeltaV Scalable Process System manual.
3.1.6
DeltaV Application Station
The DeltaV Application Station that runs the Batch Executive
software is called the Batch Executive Machine. Other
Application Stations may be added to run the Batch Operator
Interface client software and Recipe Studio for creation of
recipe items.
Locate the DeltaV Application Stations as shown in Figure 3-1
only in tightly controlled environmental conditions such as any
other PROVOX console product. Room or internal cabinet
temperature cannot exceed 95_ F (35_ C).
For additional information on this topic and information on
DeltaV Application Station connections, refer to the Installing
Your DeltaV Scalable System manual.
3.1.7
Highway Data Link (HDL) Preparation
Refer to the manual, Installing and Maintaining the Types
DH6032 Highway Data Link (HDL) and DH7742 Highway II
Bridge (PN5.1:DH6032), for information on preparing the HDL
before installing it on the network.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
32
Section 3 F Hardware Installation
DeltaV Application Station
DeltaV Batch Operator Interface
POC Operator Interface
DeltaV Application Station
DeltaV Batch Executive
RMNT PPLI
PROVOXr
r CHIP kernel
DeltaV
ProPlus
N
I
C
N N N
I I I
C C C
N N
I I
C C
N N
I I
C C
POC Console Workstations
POC Operator Interface
Configure
Batch
DeltaV
Network Hub
DeltaV
Network Hub
POC
Network
Switch
N
I
C
10Mb
100Mb
N
I
C
POC Server
10Mb
Process
Network
POC HDL
Data Highway I or II
Process Control Network
Figure 3-1.
PROVOX CHIP
Network Hub
PROVOX CHIP
HDL
Controllers
Unit Operations
Batch Executive Machine Location
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Hardware Installation F Section 3
3.1.8
33
HDL Connections
Before making the Ethernet and PROVOX Highway
connections, read the manual, Installing and Maintaining the
Type DH6032 Highway Data LInk (HDL) (PN5.1:DH6032), for
information about Data Highway and Highway II connections
and troubleshooting information. That manual contains
information for both single- and dual-port operation of the
HDL, and for coaxial and twisted-pair networks. The Batch
Executive machine operates in HDL single-port mode.
The following steps describe how to make connections to the
HDL:
1. See Figure 3-2 for twisted-pair hubs to connect the HDL to
the Batch Executive machine and hub.
Note ... The connector locations may vary from these
examples.
2. For twisted-pair network, attach the cable and be sure the
blue connector is placed on the HDL LAN port. The metal
connector on the opposite end of the cable must be
connected to the hub (for proper ground isolation).
3. Connect primary and secondary PROVOX Highway
connections to the highway ports.
4. Verify (or connect) the power cord between the HDL and a
power strip. Route and secure the power cord so it cannot
easily be disconnected from the HDL or power strip.
For more information on this topic, refer to the DeltaV Batch
Installation manual.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
34
Section 3 F Hardware Installation
Rear of
Batch
Executive
(Sample only,
locations of
your
connections
may vary.)
DeltaVt ACN
Shielded Twisted Pair Cable
Blue Connectors
to Batch Operator
Interfaces
To
Power
Strip
Modem
To Power Strip
Metal Connectors to Hub
Twisted Pair Hub
Blue
Connector
to Batch
Executive
Blue Connectors
to Batch Operator
Interfaces
Shielded Twisted Pair Cable
Shielded Twisted
Pair Cable
To Power Strip
Metal Connectors to Hub
Twisted Pair Hub
To Power Strip
Twisted Pair Hub
To Power Strip
Metal Connector to HDL
Highway Connectors
Blue Connector to HUB
HDL
LAN
Figure 3-2.
Primary
Comm
Secondary
Comm
Recipe Manager NT Wiring for Twisted-Pair Hubs
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Hardware Installation F Section 3
3.1.9
35
DeltaV Area Control Network (ACN)
The following step describes how to make connections to the
process network:
1. See Figure 3-2 for twisted-pair hubs to make the Batch
Executive machine and ACN connections.
Note ... Fisher-Rosemount Systems form-factor hubs are
shown in Figure 3-2 on page 34. For Additional
specific information regarding DeltaV network
connections, refer to DeltaV Installing your DeltaV
System.
3.2
Post-Installation Checklists
After you complete all of the installation tasks, you can
power-up the Recipe Manager NT equipment. To verify the
connections, use the post-installation checklists in this
subsection.
3.2.1
Checklists for the DeltaV Application Station
For a twisted-pair network — Verify that the blue connector
of the STP cable assembly is on the DeltaV Application
Station’s twisted-pair port and the metal connector on this
cable is on the hub port.
Use the following DeltaV Application Station checklist to verify
that:
1. The AC power cord is installed and connected to the
power strip.
2. The monitor cable is attached to both the DeltaV
Application Station and monitor and that the thumb
screws on each end are tight.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
36
Section 3 F Hardware Installation
3. The mouse cable is connected to the mouse port and the
keyboard cable is connected to the keyboard port.
4. The Software License Key is securely connected to the
parallel port of the DeltaV Application Station.
3.2.2
Checklists for the Highway Data Link (HDL)
For a twisted-pair network — Verify that the blue connector
is attached to the HDLs LAN port and the metal connector to
the hub port. Verify both are secure (snap in place).
Use the following HDL checklist to verify that:
1. The Data Highway or Highway II is connected according
to instructions in the manual, Installing and Maintaining
the Types DH6032 Highway Data Link (HDL) and DH7742
Highway II Bridge (PN5.1:DH6032).
2. The alarm contact connector (if used) is installed and the
screws securing the wires in the connector are tight. Also
verify that the alarm is connected.
3. During normal operations there are no connections to
Ports A and B.
4. The AC power cord is installed and connected to the
power strip.
For information on Fisher-Rosemount System’s Ethernet
network hardware, including the process network hub for both
the twisted pair network and the coaxial network, please refer
to either the appropriate PROVOX manual or the appropriate
DeltaV manual.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
37
Figure 4-Table 4
4
4 Software Installation
This section explains how to install the Recipe Manager NT
Software onto the Batch Executive machine. Also included
are guidelines for customizing the user interface.
This section is intended for someone with appropriate
experience in Windows NT administration and the necessary
passwords to access the system, who will be present to
handle the software installation. This section contains the
following subsections:
J
J
J
Planning the Software Installation and System
Configuration
Installing the Recipe Manager NT, CHIP NT, PROVOX
Application Server, and the OPC Mirror Lite Software
Uninstalling the Recipe Manager NT Software
For information on installing the DeltaVt software, refer to
the DeltaV Release Notes.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
38
4.1
Section 4 F Software Installation
Planning the Software Installation and System
Configuration
The Recipe Manager NT system accommodates four types of
station configurations:
J
J
J
Batch Executive — runs on a DeltaV Application Station
and contains the PPLI, PPLICFG, CHIP, PROVOX
Application Server (PAS), and the OPC Mirror Lite
software.
Batch Operator Interface — runs on a DeltaV Application
Station on which Batch is enabled. Provides operator
control and interaction with recipes during the production
of a batch. You may also choose to install a PROVOX
Operator Console (POC) client on this station.
DeltaV ProfessionalPLUS Workstations — contains the
configuration database for the DeltaV system, including
the equipment and recipe data for batch systems. From
here, you can create and modify your equipment
database and may also create and modify recipes. When
you generate and download, files are sent from this
station to the other stations in the system. This station
would also run Recipe Studio to create a recipe.
Recipe Manager NT can be licensed to run on any DeltaV
node.
You also need to initialize the Highway Data Link (HDL) and
possibly set up applications for other process network
hardware using the programs and instructions provided with
these products. For information on the PROVOXR HDL, refer
to the manual, Installing and Maintaining Highway
Communications Common Hardware and Application
Modules: Type DH6032 Highway Data Link and Type DH7742
Highway II Bridge (PN6.1:DH6032.)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
4.1.1
39
Understanding the Recipe Manager NT System
Before you begin installing the Windows NT or Recipe
Manager NT software, you need to understand:
J
The installed process network hardware
J
Each type of node you can configure
J
The different tasks each node performs
The following subsections provide detailed information on the
nodes.
4.1.1.1
Batch Executive Machine and Batch Operator
Interface Configuration Overview
In general, the Recipe Manager NT system supports one
Batch Executive and one or more development workstations
and Batch Operator Interfaces, although multiple Batch
Executive machines with development workstations and
Batch Operator Interfaces are possible.
The Batch Executive is a computer that coordinates the
function of your recipes, the equipment database, and each
Batch Operator Interface during production. The Batch
Executive uses the OPC protocol to communicate externally
with each development workstation and Batch Operator
Interface and internally with the Recipe Manager NT
Simulator and PROVOX Phase Logic Interface (PPLI)
programs. OPC allows development workstations and Batch
Operator Interface computers to be located across the
network.
A Batch Operator Interface is a computer used by operators
to manage batches.
If you need only one Batch Operator Interface, you can use
both the Batch Executive and Batch Operator Interface
software on the same Batch Executive machine. However,
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
40
Section 4 F Software Installation
this is not recommended. Typically, you would set up multiple
Batch Operator Interface computers distributed throughout
your plant. Figure 4-1 on page 40 shows a simplified view of
this arrangement.
Note ... For an explanation of the Batch Executive machine
requirements and the Batch Operator Interface
requirements, please refer to the DeltaV Batch
book online.
Batch
Operator
Interface
Batch
Operator
Interface
Batch
Executive
Professional
PLUS
Workstation
PROVOXR
Process
Control
System
Batch
Databases
Figure 4-1.
A Simplified Recipe Manager NT System Arrangement
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
4.1.1.2
41
Recipe Manager NT Simulator
The Recipe Manager NT Simulator program allows you to
model and test your equipment configuration and recipes
during the development phase. The Simulator allows you to
build an equipment database and to tie equipment entities to
simulated phases rather than actual PROVOX phases. Then
when these recipes and the equipment database are built,
you can then simulate production by executing test batches.
4.1.1.3
PROVOX Phase Logic Interface Programs Overview
The PPLI program communicates with the PROVOX control
system using the Computer/Highway Interface Package
(CHIP NT) program, which in turn uses the Transmission
Control Protocol/Internet Protocol (TCP/IP) to communicate
with its HDL. The Batch Executive server uses the OPC
protocol to communicate with PPLI.
4.1.1.4
Batch History Options for the DeltaV Batch Historian
or the Batch Archiver
The DeltaV Batch Historian is a software option that you may
purchase. This software allows the integrated storage and
reporting of batch data. (Alternatively, you may use the Batch
Archiver to copy batch journal files to a relational database.)
For more information on Batch History options, refer to the
DeltaV Batch book online.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
42
Section 4 F Software Installation
4.2
Installing the Recipe Manager NT and CHIP NT
Software
This subsection explains how to install the Recipe Manager
NT, Computer/Highway Interface Package (CHIP) NT
software, PROVOX Application Server (PAS) software, and
the OPC Mirror Lite software on the Batch Executive
machine.
Before you start the installation process, make sure that:
J
J
J
DeltaV software has been successfully installed on this
machine.
Software on the Batch Executive machine is
communicating with the ProfessionalPLUS.
You have a Windows NT logon account with administrator
rights.
To install the Recipe Manager NT, CHIP NT, PAS, and OPC
Mirror Lite software on the Batch Executive machine, follow
the steps listed in Table 4-1. If any issues develop with
installing CHIP, refer to the CHIP NT Installation manual.
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses
Shown on the Screen
Your Responses
1. Begin the
Recipe Manager
NT and CHIP NT
software
installation.
Power up the
computer and logon
with administrator
privileges.
2. The Control
Panel window
appears.
Double-click on the
Add/Remove
Programs icon.
In the Windows NT
desktop taskbar,
choose Start -->
Settings --> Control
Panel.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
43
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
3. The
Add/Remove
Programs
Properties window
appears.
To install a new program from a floppy
disk or CD-ROM drive, click Install.
Choose the
Install/-Uninstall
page (tab) and then
click the Install
button.
4. The Install
Program From
Floppy Disk or
CD-ROM window
appears.
Insert the product’s first installation
CD-ROM and then click Next.
Insert the Recipe
Manager NT P2.0 and
CHIP NT P5.0
compact disc in the
CD-ROM drive.
Click the Next button.
5. Access the
Microsoft Explorer.
6. A Question
pop-up message
appears.
Use the browse
button. Look in the
CDROM. Select the
CHIPNT folder and
select setup.exe.
Click the Finish
button.
Would you like to view the README_NT
file now?
Click the No button.
(Note: After installing CHIP NT, you can access the
README_NT file from the desktop taskbar by choosing
Start - > Programs - > CHIP_UTILS - >
README_NT.)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
44
Section 4 F Software Installation
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
7. The Welcome to
FRSI CHIP
(Computer/Highway
Interface Package)
screen appears.
Welcome to the CHIP NT Setup program.
This program will install CHIP NT on
your computer.
Click the Next button
to continue.
It is strongly recommended that you exit
all Windows programs before running this
Setup program.
Click Cancel to quit Setup and then
close any process you have running.
Click Next to continue with the Setup
program.
WARNING: This program is protected by
copyright law and international
treaties.
Unauthorized reproduction or
distribution of this program, or any
portion of it, may result in severe
civil and criminal penalties, and will
be prosecuted to the maximum extent
possible under law.
8. The CHIP NT
Product Destination
window appears.
Enter the path where you want CHIP NT to
reside:
Destination Directory
C:\CHIP
9. The CHIP NT
Read Me window
appears.
c:\chip doesn’t exist - do you wish to
create it?
Do not change the
default destination
directory unless you
are required to do so.
Click the Next button
to accept the default
directory, or click the
Browse button to
choose another, or
click in the text box
and type a new path.
Click the Yes button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
45
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
10. The NT Service
window appears.
Operation as an NT service allows
automatic startup of CHIP at boot time
and execution in the background without
needing a user to be logged in.
Click the Yes button.
For CHIP to operate as an NT service,
you must supply an existing Domain
Account and Password.
The Domain must be spelled out (for
local domain, use your PC name, not a
period).
The account must already exist: if it
doesn’t, cancel out of here, define it
and then install. (to cancel out, click
NO, NO, CANCEL, EXIT SETUP). The
password cannot be blank (or <return>).
11. The CHIP
Account Security
window appears.
Enter the account that CHIP Service
should run in:
In the text box, type in
your Domain and
User Name, and then
click the Next button.
12. The CHIP
Password Security
Window appears.
Enter the CHIP Service account password:
In the text box enter
the password.
A confirmation
window will appear
after you enter the
password and click
the OK button.
When the
confirmation window
appears, enter the
password a second
time.
Click the Next button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
46
Section 4 F Software Installation
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
13. The CHIP
System
Environment
Variables window
appears.
Variable 1 => CHIP
Read the text on the
screen and make note
of the syntax for the
two variables.
CHIP = DirName, where DirName is the
desired product directory path.
Click the Yes button
to continue.
Two System Environment Variables must be
defined via the SYSTEM applet in the
CONTROL PANEL Group.
Variable 2 => CHIP_INTERFACE_HOSTNAME
CHIP_INTERFACE_HOSTNAME = hostname,
where hostname is the name you have
associated with your HDL interface IP
address.
PLEASE NOTE:
Both SYSTEM environment variables are
required to run CHIP!
14. The CHIP
System
Environment
Variables Defined?
window appears.
If “CHIP” or “CHIP_INTERFACE_HOSTNAME”
system environment variables are not
properly defined for some reason, they
may be defined at any time during this
installation, or they may be re-defined
after the installation completes.
Type the directory
path, then click the
Next button to
continue.
NOTE:
====
There is no need to restart your
computer until these system environment
variables have been successfully
defined!
15. The Get
Environment
Variable window
appears.
CHIP_INTERFACE_HOSTNAME
Name associated with your HDL or the
HDLs TCP-IP address.
Enter the hostname in
the text box and then
click the Next button.
If you intend to operate standalone
(i.e., no HDL), use the name of your PC.
16. The next Get
Environment
Variable window
appears.
CHIP_SCOPE
Security level choices = SameAccount,
Group or Global.
Enter the security
level choice in the text
box and then click the
Next button.
If not defined, the default is
SameAccount.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
47
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
17. The next Get
Environment
Variable window
appears.
CHIP_GROUP
Group whose members may access the CHIP
database.
Enter the Group in the
text box and then click
the Next button.
The variable is used only when
CHIP_SCOPE = Group
If not defined, the default is CHIP.
18. The next Get
Environment
Variable window
appears.
CHIP_EVENT_LOGGING
Choices = EventViewerOnly, LogFilesOnly,
Both.
Enter the choice in the
text box and then click
the Next button.
If not defined, the default is
EventViewerOnly.
19. The CHIP NT
window appears.
Press NEXT> to begin installation of
CHIP NT files.
Click the Next button.
This screen also lists the settings that were chosen in
the steps above.
20. The Installing
FRSI CHIP NT
screen re-appears
with pop-up
messages telling
you what
installation steps
the computer is
taking.
21. The CHIP
Installation/Setup
Complete window
appears.
Copying files¼
No response needed.
(Note: This is an example message; others appear
with different wording.)
(Note: See the
progress bars in the
pop-up windows.)
It is recommended that you reboot the
machine now to allow setting of any
environment variables and for any system
modifications to take effect.
Select the No option
button (which clears
the other option
button).
f Yes, I want to restart my computer
now.
F No, I will restart my computer later.
Click the Finish
button.
Remove any disks from their drives, and
then click Finish to complete Setup.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
48
Section 4 F Software Installation
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
22. Access the
Microsoft Explorer
to start the OPC
Mirror Lite
installation.
23. The OPC Mirror
Lite window
appears.
Select the OPC
Mirror Lite folder on
the CDROM. Double
click OPC Mirror
Lite.exe.
Setup will install OPC MirrorLite,
continue?
24. The Unpacking
OPC Mirror Lite
Setup window
appears.
25. The Setup
window appears,
then a Welcome
window.
Click the Yes button.
No action is
necessary.
OPC Mirror Lite
Click the Next button.
Welcome to the OPC Mirror Lite Setup
program. This program will install OPC
Mirror Lite on your computer.
It is strongly recommended that you exit
all Windows programs before running this
Setup program.
Click Cancel to quit Setup and then
close any programs you have running.
Click Next to continue with the Setup
program.
WARNING: This program is protected by
copyright law and international
treaties.
Unauthorized reproduction or
distribution of this program, or any
portion of it, may result in severe
civil and criminal penalties, and will
be prosecuted to the maximum extent
possible under law.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
49
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
26. The Software
License Agreement
window appears.
Software License Agreement
(Note: Only selected portions of the text on the
screen for the selectable options are shown here.)
If the site at which this program is
used is a Licensed Facility under a
Master License Agreement (MLA), you can
view and print a copy of the MLA
Certificate by clicking on the “View
Certificate” button.
If the site at which this program is
used is NOT a Licensed Facility under a
Master License Agreement with FRSI and
the user of the program is NOT governed
by a Beta Test Agreement, the use of
this program shall be governed by the
Software License Agreement that is
printed in the sales literature and on
the package in which the program was
delivered. You can read this agreement
by clicking on “View License” button.
Read all of the legal
text on the screen.
You must click the
Yes button to validate
the existence of a
license agreement
between you or your
organization and
FRSI prior to using
this product.
If you click the No
button, the installation
program will not
proceed and the
product will not
operate.
If you CAN confirm the existence of a
License Agreement by and between your
company and Fisher-Rosemount Systems,
Inc., please click on the “Yes” button.
If you CANNOT confirm the existence of a
License Agreement by and between You and
Fisher-Rosemount Systems, Inc., please
click the “No” button.
27. The Choose
Destination
Location window
appears.
Select the base path to install OPC
Mirror Lite.
OPC Mirror Lite program files will be
loaded into directory “bin” below this
directory.
The bitmaps will be loaded into
directory “bmp” below this directory.
The demo files will be loaded into
directory “projects/demo” below this
directory.
Do not change the
default destination
directory unless you
are required to do so.
Click the Next button
to accept the default
directory, or click the
Browse button to
choose another, or
click in the text box
and type a new path.
Destination Directory
C:\Programfiles\FRS\OPCMirrorLite
28. The Setup
Type window
appears.
Click the Type of Setup you prefer, then
click Next.
Select Typical and
then click the Next
button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
50
Section 4 F Software Installation
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
29. The Select
Program Folder
window appears.
30. The Setup
Complete window
appears
Select the default
folder, FRS OPC
Mirror Lite and then
click the Next button.
Do you wish to restart your computer?
31. Access the
Microsoft Explorer
to start the PAS
installation.
Select the Yes option
and then click the
Next button. After the
computer reboots,
proceed to the next
step.
Select the PAS Server
folder and then
doubleclick
setup.exe.
32. The OPC
Server window
appears.
Do you want to read the readme file?
Click the No button.
33. The Setup
window appears,
then a Welcome
window.
PROVOX Application Server
Click the Next button.
Welcome to the PAS Setup program. This
program will install PAS on your
computer.
It is strongly recommended that you exit
all Windows programs before running this
Setup program.
Click Cancel to quit Setup and then
close any programs you have running.
Click Next to continue with the Setup
program.
WARNING: This program is protected by
copyright law and international
treaties.
Unauthorized reproduction or
distribution of this program, or any
portion of it, may result in severe
civil and criminal penalties, and will
be prosecuted to the maximum extent
possible under law.
34. The OPC
Server Product
Destination window
appears.
Enter the path where you want the OPC
Server to reside:
Click the Next button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
51
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
35. The Target
Directory window
appears.
OPC Server doesn’t exist, do you wish to
create it?
Click the Yes button.
36. The OPC
Server window
appears.
Press Next to begin installation of the
OPC Server.
Click the Next button.
37. ActiveX setup.
ActiveX may be required to develop C++
OPC clients and to register some DLLs.
Do you want ActiveX installed on your
computer?
Click the Yes button.
38. The OPC
Server Registration
window appears.
How do you wish to register the OPC
Server?
Select the default,
Local, and then click
the Next button.
39. The Setup
Complete window
appears.
The OPC Server Installation is complete.
Click the Finish
button.
This screen also allows the user to view the current
settings.
40. Access the
Microsoft Explorer
to start the RMNT
installation.
41. The Setup
window appears,
then a Welcome
window.
Select the RMNT
folder, and then the
Setup folder.
Recipe Manager NT P2.0
Click the Next button.
Welcome to the Installation of Recipe
Manager NT 2.1.
It is strongly recommended that you exit
all Windows programs before running this
Setup program.
Click Cancel to quit Setup and then
close any programs you have running.
Click Next to continue with the Setup
program.
WARNING: This program is protected by
copyright law and international
treaties.
Unauthorized reproduction or
distribution of this program, or any
portion of it, may result in severe
civil and criminal penalties, and will
be prosecuted to the maximum extent
possible under law.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
52
Section 4 F Software Installation
Table 4-1.
Steps
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
42. The Software
License Agreement
window appears.
Software License Agreement
(Note: Only selected portions of the text on the
screen for the selectable options are shown here.)
If the site at which this program is
used is a Licensed Facility under a
Master License Agreement (MLA), you can
view and print a copy of the MLA
Certificate by clicking on the “View
Certificate” button.
If the site at which this program is
used is NOT a Licensed Facility under a
Master License Agreement with FRSI and
the user of the program is NOT governed
by a Beta Test Agreement, the use of
this program shall be governed by the
Software License Agreement that is
printed in the sales literature and on
the package in which the program was
delivered. You can read this agreement
by clicking on “View License” button.
Read all of the legal
text on the screen.
You must click the
Yes button to validate
the existence of a
license agreement
between you or your
organization and
FRSI prior to using
this product.
If you click the No
button, the installation
program will not
proceed and the
product will not
operate.
If you CAN confirm the existence of a
License Agreement by and between your
company and Fisher-Rosemount Systems,
Inc., please click on the “Yes” button.
If you CANNOT confirm the existence of a
License Agreement by and between You and
Fisher-Rosemount Systems, Inc., please
click the “No” button.
43. The RMNT 2.0
Product Destination
window appears.
Enter the path where you want RMNT 2.0
(PPLI Shell) support files to reside.
Click the Next button
to accept the default
directory, or click the
Browse button to
choose another, or
click in the text box
and type a new path.
44. The Target
Directory window
appears.
RMNT 2.0 doesn’t exist, do you wish to
create it?
Click the Yes button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-1.
Steps
53
CHIP NT, PAS, OPC Mirror Lite, and Recipe Manager NT
Installation Steps, Screens, and Responses (Continued)
Shown on the Screen
Your Responses
45. The RMNT 2.0
Product Destination
window appears.
Enter the path where you want RMNT 2.0
(PPLI Shell) executable files to reside.
Click the Next button
to accept the default
directory, or click the
Browse button to
choose another, or
click in the text box
and type a new path.
46. The Recipe
Manager NT 2.0
window appears.
Press Next to begin installation of the
RMNT files.
Click the Next button.
47. The RMNT2.0
Installation window
appears.
RMNT 2.0 Installation is complete.
Click the Finish
button.
48. Open a DOS
command window.
An open DOS command window.
49. Go to the folder
where you have
RMNT2.0 installed.
Run registerppli.exe to register the
PPLI application.
Please reboot your system to ensure that
all RMNT components are installed
properly.
>registerppli.exe
After you have run the command, the PPLI application
is registered.
Note ... After successfully installing CHIP NT, verify that the
application is running and the HDL is properly
configured.
4.3
Uninstalling the Recipe Manager NT Software
When you install the Recipe Manager NT or CHIP NT
software, the Setup program also installs an uninstall routine
in the Windows NT registry (a database that stores vital
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
54
Section 4 F Software Installation
information concerning the computer’s hardware and
software).
Caution ... Make sure you have good backups of your files
before you try to uninstall the Recipe Manager NT
or CHIP NT software.
If you should ever need to remove the Recipe Manager NT or
CHIP NT software from your computer system, do not try to
do so by simply going into a folder and deleting its files.
Instead, follow the steps listed in Table 4-2 on page 55.
The uninstall routine will warn you before any files are deleted
or changed — giving you an opportunity to back out without
proceeding. Then, if you choose to continue, the uninstall
routine removes all of the files except the following:
J
J
J
Files from previous Recipe Manager NT installations
Files created after the installation (such as recipes and
logs)
Certain dynamic-link library (.DLL) files that can be
shared by other applications
Many files might remain in the directory, C:\RMNT2.0.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Software Installation F Section 4
Table 4-2.
Steps
55
Recipe Manager NT and CHIP NT Uninstallation Steps, Screens,
and Responses
Shown on the Screen
Your Responses
1. Begin
uninstalling the
Recipe Manager
NT and CHIP NT
software.
In the Windows NT
desktop taskbar,
choose Start -->
Settings --> Control
Panel.
2. The Control
Panel window
appears.
Double-click on the
Add/Remove
Programs icon.
3. The
Add/Remove
Programs
Properties window
appears.
The following software can be
automatically removed by Windows. To
remove a program or to modify its
installed components, select it from the
list and click Add/Remove.
Choose the
Install/-Uninstall
page (tab), select
Recipe Manager NT
in the list box, then
click the
Add/Remove button.
4. The Confirm File
Deletion window
appears.
Are you sure you want to completely
remove the selected application and all
of its components?
If you are sure you
wish to remove the
Recipe Manager NT
software from the
computer, click the
Yes button.
5. The
unInstallShield logo
appears, followed
by the Remove
Programs From
Your Computer
window.
unInstallShield will remove the software
‘Recipe Manager NT’ from your computer.
Please wait while each of the following
components is removed¼
No response needed.
n
n
n
n
n
n
Shared program files¼
Standard program files¼
Folder items¼
Program folders¼
Program directories¼
Program registry entries¼
(Note: A check mark
appears by each
listed component
when it has been
removed from the
hard disk.)
Uninstall successfully completed.
6. The
Add/Remove
Programs
Properties window
reappears.
The following software can be
automatically removed by Windows. To
remove a program or to modify its
installed components, select it from the
list and click Add/Remove.
Choose the
Install/Uninstall page
(tab), select CHIP NT
in the list box, then
click the
Add/Remove button.
7. The Confirm File
Deletion window
reappears.
Are you sure you want to completely
remove the selected application and all
of its components?
If you are sure you
wish to remove the
CHIP NT software
from the computer,
click the Yes button.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
56
Section 4 F Software Installation
Table 4-2.
Steps
Recipe Manager NT and CHIP NT Uninstallation Steps, Screens,
and Responses (Continued)
Shown on the Screen
Your Responses
8. The
unInstallShield logo
reappears, followed
by the Remove
Programs From
Your Computer
window.
unInstallShield will remove the software
‘CHIP NT’ from your computer. Please
wait while each of the following
components is removed¼
n
n
n
n
n
n
Shared program files¼
Standard program files¼
Folder items¼
Program folders¼
Program directories¼
Program registry entries¼
No response needed.
(Note: A check mark
appears by each
listed component
when it has been
removed from the
hard disk.)
Uninstall successfully completed.
9. After uninstalling
the Recipe
Manager NT and
CHIP NT
application files,
you can install new
versions of these
products, or you
can remove icons
from the Recipe
Manager NT folder
on the desktop and
the CHIP UTILS
folder in the start
menu.
To remove icons, click
and drag the Recipe
Manager NT folder on
the desktop to the
Recycle Bin.
From the desktop
taskbar, choose Start
--> Settings -->
Control Panel -->
WINNT --> Profiles
--> All Users --> Start
Menu and then locate
and delete the CHIP
UTILS folder.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
57
Figure 5-Table 5
5
5 Recipe Manager NT Configuration
This section introduces the major concepts involved in
configuring the Recipe Manager NT system, and contains the
following topics:
J
PROVOX Phase Configuration for use with the DeltaVt
System
J
Engineering Personnel Requirements
J
System Requirements and Limitations
J
Recipe Manager NT Configuration Requirements for PPLI
J
The PPLICFG Program Requirements
J
Getting Started
J
PPLI Configuration
J
Flexible Configuration
Four types of requirements must be met before Recipe
Manager NT configuration can start: engineering personnel
requirements, system requirements, DeltaV Batch
requirements, and PPLICFG program requirements.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
58
5.1
Section 5 F Recipe Manager NT Configuration
Configuring PROVOX Phases for Use With DeltaV
Batch
The following list provides an overview of the steps needed to
configure PROVOX phases to be used with DeltaV Batch.
1. In ENVOX, configure phase logic needed in PROVOX
operations and/or FSTs, according to the directions in
Section 6 of this manual.
2. In DeltaV Explorer, under Library --> Batch, create Phase
Classes to correspond to each distinct type of PROVOX
phase. At this point, you also configure batch input
parameters, report parameters and messages needed for
operator prompts. (You do not need to configure Phase
Logic inside the DeltaV system.)
3. In DeltaV Explorer, under Library --> Batch, create Unit
Classes to correspond to each logical batch unit for your
recipes. Note that you will be able to connect one or more
PROVOX unit points and/or LCPs to each unit.
4. In DeltaV Explorer, under Library --> Batch, create one or
more Process Cell Classes to correspond to the needs of
your plant. Then create one or more process cells under
Control Strategies --> Equipment by dragging the
Process Cell class to Equipment.
5. In DeltaV Explorer, under System Configuration -->
Control Strategies --> Equipment --> External Phases,
create one external phase for each equipment phase in
PROVOX (one for each phase class at each unit). Modify
the Equipment Phase Properties and select PROVOX as
the external phase type.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
59
6. If using unit modules (the recommended method), in the
DeltaV Explorer, assign appropriate phase classes to unit
classes by dragging and dropping the phase class onto the
unit class under Library --> Batch. Create unit modules by
dragging the unit class to an Area under System
Configuration --> Control Strategies. For each phase in
each unit module, select Properties, and then the
Arbitration tab. Check the Phase Is External box, and
type in the appropriate external phase name. Drag the unit
to the Assigned Modules of the Batch Executive machine
under Physical Network --> Control Network.
7. If using PLM units, drag the unit class to the process cell
for each unit you wish to create. Then, drag each external
phase to the appropriate unit.
8. Drag the Unit to the Process Cell under Equipment.
9. Download the Batch Executive.
10. Create the pplioper.txt file by running pplioper.sql against
the ENVOX database, and copy it to the
DeltaV/DvData/batch directory on the Batch Executive
machine.
11. Configure the PROVOX connections using pplicfg at the
Batch Executive machine. All check marks must be green
before the run-time software (dvppli) will work.
12. To run, start CHIP, PPLI, and the DVBexecutive. You can
then run the DeltaV Batch Operator Interface and run
phases in the phase control screen. You should be able to
check the phase status using PPLI Show Phase Status.
The file DVBExecutive.log under DeltaV/DVDData/Logs
may be helpful for certain problems.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
60
Section 5 F Recipe Manager NT Configuration
13. You can now use Recipe Studio by following the DeltaV
Batch book online instructions, and you can also download
and run recipes using the Batch Operator Interface. If you
wish to use PROVOX point references in your recipe
transitions, refer to the instructions in Section 5.10 of this
manual.
For more information on the Recipe Studio and the Batch
Operator Interface, please refer to the DeltaV Batch book
online.
Note ... When configuring PROVOX phases, the
recommended method is to use unit modules rather
than PLM units. Unit modules ensure that equivalent
phases are created for each unit, enabling class
based recipes.
5.2
Engineering Personnel Requirements
The engineer designing a batch application using the Recipe
Manager NT system, which includes the PROVOX Phase
Logic Interface, must have expertise in the following main
areas:
1. Experience with the PROVOX system and PROVOX
engineering.
2. Understanding of the PROVOX operation and FST shells
provided with the PPLI software.
3. Understanding of the Recipe Manager NT software.
J
J
DeltaV Explorer — including requirements due to
PROVOX interface
Recipe Studio
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
J
J
61
Batch Operator Interface operation
Phase programming requirements of the Recipe
Manager NT system
4. Understanding of the PPLI configuration software.
5.3
System Requirements and Limitations
The following are limits of the batch software (each per
phase): 99 parameters (phase logic inputs), 99 reports (phase
logic output parameters), and 5 request parameters (used by
phase logic, such as phase to phase messages). Message
strings are ascii parameters and up to 58 characters in length.
5.4
The PPLICFG Program Requirements
To run the PPLICFG program, you must install the PROVOX
CHIP interface, and the CHIP Manager must be active. It is not
necessary, however, for CHIP to communicate with the
PROVOX system. You must target and download to the
Recipe Manager NT CHIP all Unit points, LCPs, DCDs, and
points used in creating Recipe Manager NT unit parameters.
When you open a configuration file through PPLICFG, the
program must find an ASCII file named PPLIOPER.TXT in the
DeltaV/DVData/Batch directory. This file is used to configure
PROVOX Unit Operations and phase name connections.
(Directions for creating this file are in the subsection, PROVOX
Unit Operation and Phase Name File For PPLI, on page 114,
in the section, Recipe Manager NT Phase Programming.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
62
Section 5 F Recipe Manager NT Configuration
Warning ... It is extremely important that you set up engineering
and operating procedures to ensure that the
PPLIOPER.TXT file is updated whenever you
change the number of operations, the number or
order of phases within an operation, or the valid
operations for one or more unit point.
These changes must not be downloaded to the
PROVOX controller while any Recipe Manager NT
batch is operating, since they will affect currently
operating batches.
If the PPLIOPER.TXT file does not exactly reflect the
configuration of the running system, serious and
unpredictable results may occur, which are hard to
trace.
For optimal error detection and listing assistance, the CHIP
database on the NT system should contain the PROVOX
points you will use. All points used must be in the CHIP
database before running recipes.
You can use PPLICFG concurrently with the other Recipe
Manager NT programs including the Batch Executive, Batch
Operator Interface, etc. However, the changes made in a
configuration file by PPLICFG are not visible to PPLI until you
save the file and restart DeltaV PPLI. Likewise, any DeltaV
Explorer changes are not visible to PPLICFG until you
download.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
5.5
63
Getting Started
This subsection gets you started using the PPLICFG to
connect your configured recipes and equipment phases to the
PROVOX system.
5.5.1
PPLICFG Main Screen
The major elements on the main PPLICFG screen are as
follows:
J
Standard menu bar
J
Tool bar
J
J
J
J
Display area for the Active Phase Template — described in
the subsection, Invoking PPLICFG Functions on page 65.
A Tree control containing all configurable items
A List control where the contents of an element in the Tree
can expand and contract (similar to Microsoft Explorer)
A box at the bottom of the screen containing any validation
error messages encountered when an item is selected
These elements are shown in Figure 5-1.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
64
Section 5 F Recipe Manager NT Configuration
Figure 5-1.
5.5.2
PPLI Configuration Window
Opening Configuration Files
PPLICFG automatically opens the AREAMODEL file when you
start it. At any given time, only one configuration file can be
open in PPLICFG.
Use the DeltaV Explorer to create the configuration files that
describe the configuration of equipment and phases. The file
that PPLICFG uses is downloaded from the DeltaV database
in the ProfessionalPLUS Workstation to the Batch Executive
machine. This file is AREAMODEL.SCR and is located in the
DeltaV/DVData/download directory.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
65
When existing Recipe Manager NT configuration files are
being modified, it is advisable to make a backup copy of the
AREAMODEL.PPC file found in DeltaV/DVData/Batch
directory.
5.5.3
Invoking PPLICFG Functions
The following general functions, available from either the
pull-down menus or toolbar, apply to the entire configuration:
J
J
J
File --> Open — reopens a configuration file for editing
(used to erase unwanted changes)
File --> Save — saves changes in the open file
Configure --> Validate Using CHIP Database —
determines whether the PROVOX point information is valid
using the CHIP database (validation shows only
unconfigured items)
The following additional set of functions can apply to objects
selected in either the Tree or List control:
J
J
J
J
J
Configure --> Add PROVOX Point — adds a point where
phases are to be run
Configure --> Delete PROVOX Point — removes a point
which has been previously added
Link Phase to PROVOX Point — (accessed by clicking
the right mouse button on a phase in the List control)
specifies on which point a phase is to run
Configure --> Set Template — specifies an equipment
phase which has already been configured as the source
for the definition of other phases (Once specified, this is
the Active Phase Template)
Configure --> Copy Template — copies the Active Phase
Template to a target phase (unit references are replaced
with target unit)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
66
Section 5 F Recipe Manager NT Configuration
J
Configure --> Open Edit Dialog — edits the information in
a PROVOX point definition, a phase, or a unit parameter
Note ... You can invoke these functions through the
pull-down menus, toolbar, or by using a floating
menu displayed when you click the right mouse
button over an object in the Tree or List control. You
can also initiate the Open Edit Dialog on phases
and unit parameters by clicking the right mouse
button on the objects and then selecting from the
floating menu, Edit PROVOX Point.
5.5.4
Navigating the Tree Control
The Tree control is the mechanism used to display all
configurable items. There are two main branches in the tree:
J
Phase configuration
J
PROVOX Watchdog configuration
Under the phase configuration branch is an object for each
equipment phase that the DeltaV Explorer defines in the
selected configuration file. PROVOX points, defined as being
related to each equipment phase, are below these objects,
and there are phases below these points with links to each
PROVOX point.
Any phase not yet linked to a PROVOX point has an unlinked
position under its associated Recipe Manager NT unit.
An icon indicates if an object has an improper configuration.
These icons propagate up the branches of the tree so that you
can easily navigate from the top of the tree down to any error’s
location. The icons are:
J
A green check (indicates a valid configuration)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
J
67
A red X (indicates an improper configuration)
Before a phase configuration is complete, all phases must be
linked to a corresponding PROVOX point. Therefore, all of the
icons in the Tree control must be green checks.
5.6
PPLI Configuration
A configuration file contains only Recipe Manager NT unit
names and unlinked phases when you first open it. To link the
phases, you need to define one or more PROVOX points
attached to each Recipe Manager NT unit; you accomplish this
by using the Add PROVOX Point function. Once you add a
point, you can link phases to it by using the Link to PROVOX
Point function. You can set the details of the phase by using
either the Open Edit Dialog or Copy Template functions.
Performing the Open Edit Dialog function for each unit
parameter ensures their proper configuration.
5.6.1
Understanding the PROVOX Phase Connection to the
Equipment Database
Each DeltaV Batch external phase results in one PPLI
equipment phase definition, in which you connect all of the
external phase data items to PROVOX point attributes. The
term connecting implies the setting of a one-to-one
correspondence between each Recipe Manager NT data item
and a PROVOX point attribute. ASCII items should be
connected to CHIP ASCII points.
Messages are used only within the Recipe Manager NT
system (though they are referenced by the phase logic). It is
not necessary for the messages to have a connection to the
PROVOX system.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
68
Section 5 F Recipe Manager NT Configuration
5.6.1.1
Adding and Editing PROVOX Points
Accessed by selecting an object in the Tree or List control and
clicking the right mouse button, the Add PROVOX Point and
Edit PROVOX Point functions involve a two menu sequence.
The first menu allows you to select which point to use. You can
key in the point name or select a point name accessed from
the CHIP database. The contents of the drop-down list consist
only of those points of type selected by the radio buttons
(either LCP Point or Unit Point). In this menu you may choose
the Flexible Configuration option. A second menu will appear if
you click the OK button.
If you do not choose the Flexible Configuration option, the
second menu allows you to select DCDs used for phase
commands and states. You can key in the names or select
them from the associated lists. The lists support your keying a
character to position the list to the first entry starting with that
character. If you select an item in the list, it copies
automatically to the corresponding entry field.
If you do choose the Flexible Configuration option, the second
menu allows you to select which features of Recipe Manager
NT you wish to use.
Note ... If you use the Flexible Configuration option, read the
information about each option carefully (Section
5.7). It is important that you select all of the items
that are important to your operations.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
5.6.1.2
69
Linking a Phase
In the tree control, you may select an unlinked phase to link to
a PROVOX point. After selecting the phase, clicking the right
mouse button and selecting Link to a PROVOX Point, a
submenu appears containing the valid points to which you can
link the phase. Since each phase attaches to a particular
Recipe Manager NT unit, you can only link it to PROVOX
points attached to the same Recipe Manager NT unit.
After you select the PROVOX point, the phase moves under
the point in the Tree structure. If there are no additional
unlinked phases, the unlinked branch disappears.
5.6.1.3
Editing a Phase
To edit a phase you must first access the Edit Recipe Manager
Phase Definition window by performing an Open Edit Dialog
function. Once inside this window, if you attach the phase to a
PROVOX Unit point, you must specify the unit operation, along
with the phase on which it will run. You must specify a tag,
attribute, and occurrence for every item associated with the
phase. For more information, see the subsection,
Understanding the PROVOX Phase Connection to the
Equipment Database, on page 67.
For phases based on Unit points, you must also select the unit
operation and unit phase that connects the Recipe Manager
NT phase to its associated logic in the PROVOX system. For
more information, see the subsection, PROVOX Unit
Operation and Phase Name File for PPLI, on page 114.
You can use the Copy Template function in place of this
editing operation, if you have already defined an appropriate
phase as a template for this phase definition.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
70
Section 5 F Recipe Manager NT Configuration
5.6.1.4
Using Copy Template
To quickly configure equipment phases for different units built
from the same phase (multiple instances of the same phase),
use the Copy Template function.
Perform an Open Edit Dialog function to completely configure
the equipment phase for the first unit. Then return to the main
PPLI configuration screen.
Use the Set Template function to copy the configuration to the
Active Phase Template section of the PPLI Configuration
window. Note that the Active Phase Template section of the
screen changes to describe the contents of the template.
Use the Copy Template ( ) to Phase function to copy the
phase appropriately. The tag name contained within the
parenthesis indicates from which phase the active phase
template has been copied.
The results of using the Copy Template function depend on
the data item point. For each element in a phase template that
references the point the phase runs on, the Copy Template
function sets the corresponding target information using the
target’s point as the tag name.
Therefore, if the original data item references the name of the
source point, then the item is copied using the target point
name as the tag name. Also, if there is an item in the template
that references a different point, the item is copied directly to
the target phase. These are marked internally so that they do
not verify, and a warning message results on exiting the phase
they are in. It is necessary to accept each of these by either
answering OK to the warning message or by using Next or
Previous to verify the entries in the phase.
Special handling has been added for associated points that
meet certain requirements (e.g., an associated point could be
an ASCII point for messages associated with a unit). The
requirements are (1) the source point name is wholly
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
71
contained in the source item point name, (e.g., TK100 is
contained in TK100MSG) and (2) the target point name is of
the same length as the source point name (e.g., TK100 is the
same length as MT200). If these requirements are met, Copy
Template will alter the target item point name to similarly
wholly contain the target point name (e.g., TK100MSG would
become MT200MSG for the previously named source and
target). As with items copied directly, these are marked
internally so that they are not automatically accepted. It is
necessary to accept each of these by either answering OK to
the warning message or by using Next or Previous to verify
the entries in the phase.
Any target items not in the template have the question marks
setting (???) for attribute with the source point as the tag.
The Copy Template function relies on the template and the
target both linking to the same type of PROVOX point.
Therefore, this function is usable only when the point types of
the template and the target phase are the same.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
72
5.6.2
Section 5 F Recipe Manager NT Configuration
Adding a PROVOX Watchdog
The PROVOX Watchdog allows for alarm notification or other
actions at the PROVOX console if communication with the
Recipe Manager NT system is lost. You need to enter a name
for the Watchdog, tag, attribute, and occurrence. The tag
name refers to the PROVOX point that is to be the source of
the desired value. The attribute and occurrence names show
the location of the desired value with the PROVOX point.
While PPLI is running, the value at this location will be set to
zero every five seconds. You can configure a Watchdog FST
in each PROVOX controller to detect any malfunctioning of the
Watchdog. This allows you to take appropriate action in the
event of a failure in the Recipe Manager NT system, or in any
communication. Examples of an appropriate action might be
an alarm or a hold on all phases.
The PPLI shell configuration includes an FST called
RMWATCHDOG (for description inside PPLICFG only) that
implements a simple watchdog. You can use this as the
starting point for your watchdog implementation. However, by
itself, this action does nothing but set an alarm if the watchdog
fails.
5.7
Flexible Configuration
The Flexible Configuration option allows the user to choose
which of the registers of the PROVOX Phase Logic interface
(PPLI) to use. These registers are used in the interaction with
the Batch Executive. Those that are selected require that a
corresponding PROVOX register is allocated. If left
unselected, default action is done by PPLI, and, depending on
the register, there is also a loss of functionality available to the
user code in the register.
Command Register — At this time, the Command Register is
pre-selected and may not be de-selected. The Command
register is used to transmit the commands from the Batch
Executive to the user code. You may connect this to a
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
73
command DCD. If you do not, you are responsible for
corresponding changes to the PPLI shell code in your
controller configuration.
Status Register — At this time, the Status register is
pre-selected and may not be de-selected. The Status register
is used to transmit the batch state back to the Batch
Executive.
Failure Register — If selected, the Failure register can be
populated by the user code to include error codes specific to
the user phase logic. If set, the phase is recognized by the
Executive as Failed, and a Hold command is issued. User fail
values are from 501 to 756, corresponding to the
phase_failures set in the DeltaV Explorer. These fail values
are configured by the user and displayed by the Batch
Executive. The PPLI shell code also copies to the Fail Index
from the control point (Unit or LCP) to the fail register. This
should be maintained if the shell is altered for Flexible
Configuration use.
If not selected, the PPLI software uses the value of the Fail
Index as the Fail register, and the user logic cannot enter error
codes. However, failure at the Unit point or LCP is interpreted
as a failure, and the batch is held. It is recommended that a
Failure register be allocated since operational difficulties can
result if not. If the user does not allocate a Failure register, the
user should thoroughly test failure scenarios.
Request Register — If selected, the user logic may make
requests through the Batch Executive, including requests for
parameter download or upload, messages or prompts to the
operator, equipment acquirements and releases, and
messages to other phases. If not selected, the user logic may
not use the Request functionality.
Step Index Register — If selected, user code may write a
number to indicate the progress of the phase. This number is
available on the Hierarchical Step List, Active Phase
Summary, and the Phase Control displays of the Batch
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
74
Section 5 F Recipe Manager NT Configuration
Operator Interface. If not selected, the Step Index is populated
with the step number if a PROVOX Unit point is used, and with
0 if an LCP is used.
Owner Register — If selected, the user can set the owner
register bit to show external control of a phase. If not selected,
the user has no capability for external control.
Unit Register — If selected, the Equipment ID of the active
recipe manager unit is available in the phase logic. This is
useful for shared phases, or for phases where multiple units
use common logic. If not selected, the Equipment ID of the unit
is not available to the phase logic.
Pause Register Set — If selected, the pause functionality
may be used. If not selected, attempts to use the Pause
functionality will have no effect, except that the PAUSING
indicator will remain until the phase is reset to IDLE.
Phase ID Register — If selected, the PPLI software can
check to see if the desired phase is the active one during
warm start. If not selected, a warm start after a down time
during which phases were run manually could result in the
recipe step attempting to control a phase that it should not.
Caution ... If the Phase ID Register is not selected, ensure that
operating procedures for warm start include a
verification that any active phases are the same as
those of the recipe.
Download Register — If selected, user code may be
programmed to request a download in cases where the same
phase is called before and after a transition. In this case, the
phase remains in the RUNNING state, but may be
programmed to respond to this flag, which is set when the
phase goes through the transition. If not selected, user code
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
75
that occurs on both sides of a transition does not indicate
when the transition occurs.
5.8
Modifying or Changing Recipes on Existing
Systems
Under certain conditions, users may desire to change or
modify a recipe (or configuration) on an existing system that is
running. The actions required by a user to recipes on an
existing and running system are summarized in Table 5-1.
If more that one type of change is done concurrently, make
sure to do all required actions. Note that you can stop and
restart PPLI without affecting batch operation greatly; however,
it is best to do this when any running recipes are in a
quiescent state. A quiescent state implies that there is not
much activity, such as phase transitions, operator prompts,
etc.
Table 5-1.
Changing an Existing System
Type of Change
Actions Required
Add PROVOX Unit Points or
LCPs for new phases
Target Points to CHIP. Generate and Download UOC and CHIP; if
Unit Points, re--create (and transfer to PC if changed)
PPLIOPER.TXT file. Make any needed changes in PPLICFG.
Assure any running recipes are in a quiescent state (with no
phases starting, completing, or doing requests). Stop and restart
PPLI.
Add (or delete or rename)
PROVOX Operations, Phases
and/or Steps
Complete any affected recipes. Generate UOC; re--create and
transfer the PPLIOPER.TXT file to the PC. Make any needed
changes in PPLICFG. Download UOC. Assure any running
recipes are in a quiescent state. Stop and restart PPLI.
Modify or add logic in existing
PROVOX operation or FST
Complete any affected recipes. Make sure corresponding phases
are in Idle state at RMNT. Partial download UOC.
Add (or delete or rename)
phases (units and/or phase
classes) and external phases in
DeltaVt Explorer
Complete any affected recipes. Download Batch Executive station.
Make any changes needed in PPLICFG. Hold any running recipes.
Stop Batch executive and PPLI. Restart Batch Executive and
PPLI.
Add, rename, or delete phase
parameters, reports, messages,
or properties
Complete any affected recipes. Download Batch Executive station.
Make any changes needed in PPLICFG. Stop Batch executive and
PPLI. Restart Batch Executive and PPLI.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
76
Section 5 F Recipe Manager NT Configuration
Table 5-1.
Changing an Existing System (Continued)
Type of Change
Actions Required
Add, modify, or delete recipes
Download the recipes from the Recipe Studio or the DeltaV
explorer. Make sure all recipe levels are included, and that
“Release to production” is checked in Properties of top level
recipes.
Modify options or connections
in PPLI configuration
Make changes in PPLICFG and Save configuration. Assure any
running recipes are in a quiescent state. Stop and restart PPLI (no
need to stop Batch Executive).
5.9
Change Summary
The following subsections describe the changes that apply in
this release. These changes include name and functionality
changes.
5.9.1
DeltaV Batch Differences
The following table provides the current names for various
Recipe Manager NT modules.
Table 5-2.
Recipe Manager NT Module Name Changes
Current Name
Previous Name
Batch Executive
Batch Server
Batch Operator Interface
Batch Client
External Phase (PROVOX)
PROVOX Equipment Phase
PLM Based Unit
Unit
Unit Module
Unit
Unit Parameter - Parameter Reference
Unit Tag
Named Set
Enumeration
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
77
Registers that are added with a conversion to an interaction
with DeltaV Batch are also flexible, and the user is allowed to
choose which of the two to use. These registers determine
how certain features of the software are used. Those that are
selected require that a corresponding PROVOX register is
allocated. If left unselected, the corresponding functionality is
not available to the user code in the controller.
An enumeration in Recipe Manager, Version P1.0, could
handle over 30,000 values. A Named Set in DeltaV is limited
to 255 values (1--255). In the Phase_failures Named Set, the
user--defined failure range is now 501 -- 755. These values are
converted to correspond to the phase_failures values of 1--255
in DeltaV by the PPLI software.
5.9.2
Additional Changed Functionality
The Batch Executive runs as a background task and is
managed by the Batch Executive Manager. Since PPLI is an
OPC information server to the Batch Executive, the Batch
Executive automatically starts PPLI if the Executive is shut
down. Therefore, it is necessary to shut down both programs
to shut down operations.
After a download which affects the area model (phases and
phase parameters), the Batch Executive and PPLI must be
shut down to load the changes on Restart. PPLICFG changes
can be made before shutting down and restarting. Recipe
downloads do not require any shutdown.
The DeltaV Recipe Studio has an improved interface and more
capabilities than the Recipe Manager NT, Version P1.0,
Recipe Editor. Most notable are the addition of formulas and
methods of deferring parameters.
Formulas are now available in the Recipe Studio so that
parameter sets or grades of a recipe can be configured.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
78
Section 5 F Recipe Manager NT Configuration
There are now up to 99 input parameters and 99 report
parameters per phase available.
Phases are now limited to 5 request registers. This number
had been 50, but these were only useful in phase to phase
message requests.
Assignments between objects are no longer implicit, but must
be made explicitly in the DeltaV explorer. The applies to phase
classes assigned to unit classes, and units to process cells.
Failure to make the assignments causes the object not to be
visible in the Batch Operator Interface.
Copy template now causes internal marks for copied items,
rather than requiring the user to edit remove a question mark
(? –).
5.10
Parameter Reference Configuration
You are not limited to the use of phase states in making recipe
transitions decisions. You may also choose to monitor the
process values (such as pH) to determine when to proceed to
the next recipe step. If the transition expression which uses
the value goes TRUE, preceding phases are sent the STOP
command. After the phases have stopped and have been
reset, the next step in the recipe proceeds.
In order to make process values available to the DeltaV Batch
Executive, configure the OPC Mirror to communicate the
desired PROVOX value to a DeltaV module parameter. Then,
configure the DeltaV parameter as the attribute reference for
the parameter reference of the unit module as described in the
following paragraphs.
Parameter references are process values that can be used in
recipe transitions. These references were formerly called unit
tags. They are configured within the unit class by selecting the
desired unit class, right-clicking, and then selecting New -->
Unit Parameter Definition. A dialog box appears in which you
then select Parameter Reference in the Parameter selection.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Configuration F Section 5
79
In order to supply a PROVOX process value for the parameter
reference, you must use PROVOX Application Server (PAS)
and OPC Mirror Lite. Create one or more DeltaV modules that
will be used on your DeltaV Batch Executive machine as
storage locations for your parameter references (these cannot
be unit modules). Start the PAS and the OPC Mirror
configuration, and then configure a pipe to move the correct
PROVOX values to the DeltaV module parameters.
Select the unit (unit module or PLM unit) created for the unit
class under the area for Control Strategies. The parameter
reference is shown as a tag shaped icon in the parameter list
for the unit. Select this icon, right click, and then select
Properties. Under Attribute References, you may browse to
the DeltaV module parameter that you wish to use. This
completes the steps needed to configure a parameter
reference.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
80
Section 5 F Recipe Manager NT Configuration
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
81
Figure 6-Table 6
6
6 Phase Programming
This section introduces you to the requirements for
programming both the PROVOXr unit operations and the LCP
FSTs needed to implement Recipe Manager NT phases.
The following topics are included in this section:
J
Understanding Phases
J
Creating a New Phase in the PROVOX System
J
Recipe Manager NT/PPLI Requirements for Phase Logic
J
PROVOX Capabilities and Characteristics
J
J
Recipe Manager NT for PROVOX Phase Logic Interface
Solution
Phase Logic Design and Programming
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
82
6.1
Section 6 F Phase Programming
Understanding Phases
A phase is a series of steps that causes one or more
equipment or process-oriented actions.
In the Recipe Manager NT system, equipment phases, defined
in the equipment database, control the execution of the phase
logic that resides in the PROVOX unit controller. The phase
logic in the controller contains instructions on how to control a
set of physical devices, such as pumps, valves, and motors.
6.1.1
Phase Logic Components and Communications
Equipment phase implementation consists of several
components at several levels, as illustrated in Figure 6-1.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
83
DeltaVt Batch Executive
NT Resident
Components
Equipment Phase Commands and Requests (OPC)
PROVOXR Phase Logic Interface (PPLI) - (with CHIP NT)
PROVOX Data Highway Communication
PPLI Shell Phase Interface Logic
Equipment Phase Control Logic
UOC Resident
Components
Controller Point Level Communications (Driven by Phase Logic)
PROVOX Points (Lower Level)
Controller Point Level Communications (Driven by Points)
Physical Devices
Figure 6-1.
Recipe Manager NT Phase Components and Communication
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
84
6.1.2
Section 6 F Phase Programming
Phases at the Batch Executive Machine
Configured in the DeltaVt Explorer, phases contain
parameters, reports, requests, and registers. The operator can
start these phases from the Batch Operator Interface by:
J
J
6.1.3
Running a recipe that will sequence through the phases
automatically
Running the phases manually at the Phase Control screen
Equipment Phase Connections at PPLI
Equipment phases at PPLI contain information on how Recipe
Manager NT external phases correspond to the PROVOX unit
or LCP point equipment phases. You must define this
connection as well as the connection between Recipe
Manager NT parameters, reports, requests and registers and
the corresponding PROVOX locations. At execution time, PPLI
transfers these data items between the two systems: Recipe
Manager NT and the PROVOX data highway (through CHIP).
6.1.4
Equipment Phases at the UOC
Equipment phases at the UOC consist of:
J
J
6.2
PPLI Shell logic made up of either unit operation or FST
code that controls the state transitions as required by the
Recipe Manager NT system.
Process specific logic that performs a control sequence.
As a control systems engineer, your work is primarily at
this level.
Creating a New Phase in the PROVOX System
To create a new LCP-based phase in the PROVOX system,
follow these steps:
1. Select the ENVOXr Item Copy utility.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
85
2. Set the copy mode to overwrite.
3. Enter TS-LCP-Phase in the Copy From field. Press
Enter and this will expand to a list of 10 tags (an LCP, two
DCDs, and seven FSTs). You must make copies of these
items to implement the new phase.
4. You must assign a new tag to each of the copies. Enter
these under the Copy To column. Use tags that indicate
the items are all part of the same phase.
5. Select the Copy! menu option and the ENVOX
configuration will make copies of each of the items you
need.
6. Edit each of the items in turn to customize them for your
new phase. It is particularly important that you set the
initial values of registers I29 and I30 in the LCP point to
indicate the ABS DBI of the COMMAND and STATE
DCDs, respectively. The phase will not operate as
expected if these values are not correct. For information on
calculating the ABS DBI of a point, refer to the manuals,
Configuring the 20-Series (SR90) Controller Family
(CE10.0:CL6633:VOL1&2), or Configuring the SRx
Controller Family (CE12.0:CL6640:VOL1&2).
To create a new unit-based phase in the PROVOX system,
follow these steps:
1. Select the ENVOX Item Copy utility.
2. Set the copy mode to Overwrite.
3. Enter TS-UNITPHASE in the Copy From field. Press
Enter and this will expand to a list of four tags (a Unit, two
DCDs, and an operation). These are the items that you
must make copies of to implement the new phase.
4. You must assign a new tag to each of the copies. Enter
these under the Copy To column. Use tags that indicate
the items are all part of the same phase.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
86
Section 6 F Phase Programming
5. Select the Copy! menu option and the ENVOX database
will make copies of each of the items you need.
6. Edit each of the items in turn to customize them for your
new phase. It is particularly important that you enter the
tags of the COMMAND and STATE DCDs into the first two
entries of the unit definition of the new Unit point.
6.3
Recipe Manager NT/PPLI Requirements for
Phase Logic
When developing equipment phases at the controller, you
must address these conditions set by the Recipe Manager NT
system:
1. Equipment phase state transitions
Each phase must contain logic that conforms to the
predefined state transition protocol. See the State
Transition Diagram below.
2. Equipment phase register definitions
You should adhere to the well-defined method of phase
interaction protocol between the Recipe Manager NT
system and the controller.
3. Equipment phase data storage and transfer
You should connect batch parameters so that the image of
the equipment phase seen by the Recipe Manager NT
system is the same as that seen at the controller.
The following subsections detail the Recipe Manager NT
requirements for each of these areas.
6.3.1
State Transition Diagram
Phase programming must adhere to the rules of the state
transition logic represented below in the State Transition
Diagram. The diagram depicts the active states (those
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
87
supported by equipment phase logic), and quiescent states
(those that do not require phase specific logic) and the paths
between the states.
The best way to ensure adherence to this requirement is to
use the supplied shell configurations as the starting point for
all of the operations and FSTs you write.
Seq Done
ABORTED *
ABORTING
Abort
Reset
Abort
Abort
Seq
Done
HOLDING
HELD *
Stop
RUNNING
Stop
COMPLETE *
Figure 6-2.
Seq
Done
Abort
STOPPING
Seq
Done
Seq
Done
Reset
Stop
Fail/Hold
Fail/
Hold
Start &
Not Fail
RESTARTING
Stop
Abort
IDLE *
Restart &
Not Fail
STOPPED *
Reset
NOTE: * Indicates Quiescent State
Recipe Manager NT State Transition Diagram
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
88
Section 6 F Phase Programming
The meaning of the ten states is given in Table 6-1.
Table 6-1.
State
Recipe Manager NT States
Meaning
IDLE
The phase is waiting for a START command. No
processing is being carried out.
RUNNING
The phase is executing its normal control
actions. This could be a complex sequence of
actions, as in a PROVOXr operation, or a
simple continuous control strategy implemented
in a PROVOX FST. When the phase’s control
task is done, it will move to the COMPLETE
state.
STOPPING
The phase is executing an orderly shutdown. It
will transition next to STOPPED, and eventually
to IDLE. There is no way to return to RUNNING
from STOPPING. In STOPPING, the phase
programmer should include code to set all plant
devices to a safe condition and bring the plant to
a safe state. The phase will enter STOPPING
when an operator presses the STOP button, or
in a recipe if the transition expression that
follows goes to TRUE.
STOPPED
The phase has completed the STOPPING logic
and is waiting for a RESET command to go
IDLE. There is no way to return to RUNNING
from STOPPED. Normally no control actions are
being carried out in STOPPED.
ABORTING
The phase is executing an emergency
shutdown. It will transition next to ABORTED,
and eventually to IDLE. There is no way to
return to RUNNING from ABORTING. In
ABORTING, the phase programmer should
include code to set all plant devices rapidly to a
safe condition and bring the plant to a safe
state. The phase will enter ABORTING when the
operator presses the ABORT button.
ABORTED
The phase has completed the ABORTING logic
and is waiting for a RESET command to go
IDLE. There is no way to return to RUNNING
from ABORTED. Normally no control actions are
being carried out in ABORTED, although it
would be possible to have some continuous
monitoring programmed into the phase logic.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
Table 6-1.
State
89
Recipe Manager NT States (Continued)
Meaning
HOLDING
The phase has detected a failure condition and
is executing logic to bring the plant to a safe
condition before going to HELD. This state will
also be entered if the operator pressed the
HOLD button. It would be used where there is
some temporary problem on the plant or the
batch, but where the batch is expected to
eventually restart.
HELD
The phase has completed the HOLDING logic
and is waiting for a RESTART command.
Normally no control actions are being carried out
in HELD, although it would be possible to have
some continuous monitoring programmed into
the phase logic. It is also possible to go to
STOPPING or ABORTING from the HELD state.
RESTARTING
The phase is restarting after being in HELD. It
will transition to RUNNING next. The
RESTARTING phase should contain the phase
logic to restart plant devices and restore
conditions to normal before going back to
RUNNING. The RESTARTING state will be
entered when the operator presses the
RESTART button following a HELD.
COMPLETE
The phase has reached the natural end of its
RUNNING sequence and is waiting for a RESET
command to go to IDLE.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
90
Section 6 F Phase Programming
Note ... The distinction between STOPPING/STOPPED and
ABORTING/ABORTED is determined by the phase
programmer. Both are provided to allow for planned
and emergency shutdowns to be handled differently
if necessary. In some cases different actions might
be programmed for STOPPING versus ABORTING.
In other cases, the shutdown logic might be the
same (possibly using a common subroutine in the
operation/FST to eliminate duplicated code).
6.3.2
Phase Register Definitions
Table 6-2 below shows the registers used for communication
between equipment phases in the Recipe Manager NT system
and the controller. The primary registers are BCOMMAND,
BSTATUS, FAIL_INDEX, and REQUEST. Specific requests
may require additional data such as parameters and
arguments defined in the subsection, Recipe Manager NT
Data Items on page 92. Usage of these additional items
depends on specific equipment logic and operating
requirements.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
PPLICFG Phase Register
Definitions
Recipe
Phase Logic Type
Manager NT Usage
Name
91
Table 6-2.
Purpose
BCOMMAND
Read
Integer
Commands the
equipment
phase to go to a
particular state,
as defined by
the State
Transition
Diagram
BSTATUS
Write
Integer
Shows the state
of the
equipment
phase
FAIL_INDEX
Write
Integer
Shows and
defines the
failure of an
equipment
phase or phase
interface
REQUEST
Write
Integer
A request to the
Batch Executive
machine from
the phase logic
STEP_INDEX
Write
Integer
An identifier of
the location for
the phase
OWNER
Write
Boolean
Identifies if the
control mode is
External (1 or
true) or the
Recipe Manager
NT system (0 or
false)
UNIT
Read
Integer
Shows the
phase logic of
the ID of the unit
PAUSE_REQ
Read
Boolean
Shows the
operator
requested
pause
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
92
Section 6 F Phase Programming
Table 6-2.
PPLICFG Phase Register
Definitions (Continued)
Recipe
Phase Logic Type
Manager NT Usage
Name
Purpose
PAUSED
Write
Boolean
Shows the
operator
requested
pause
SINGLE_STEP
Read
Boolean
Shows the
continuous
pause request
For more phase register information, see Table 6-5, Phase
Logic Register Allocations.
6.3.3
Recipe Manager NT Data Items
For each batch interaction, it is necessary to set particular
data locations in the controller for each piece of data
associated with an equipment phase. Table 6-3 contains this
list of items.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
Table 6-3.
93
Recipe Manager Data Items
Name
Usage (by
phase
logic)
Type
Description
Comment
External
Reference
Parameter
none (recipe
only)
Real, Int,
String, ENUM
Refers to
(arbitrary)
named system
data value.
Used in recipe
transition logic,
not used by
phase logic.
Parameters
Read
Real, Int,
String, ENUM
Recipe
Manager NT
values
downloaded to
the PROVOXr
system for use
by phase logic.
Connected to
unit, LCP, or
ASCII point
attributes.
Reports
Write
Real, Int,
String, ENUM
Values which
result from
phase logic
reported back
to the Recipe
Manager NT
system.
Connected to
unit, LCP, or
ASCII point
attributes.
Messages
ID
Message
String
Parameters
that are either
used as
messages to
coordinate
phases, sent to
the operator, or
are operator
prompts.
Optional, for
use with
request
functionality.
BATCH_ID
None (for
display)
String
If selected,
BATCH_ID is
automatically
transferred
Optional, must
use CHIP
ASCII point
PROMPT
BOOL
Read (and/or
display)
Boolean
Value to hold
operator
response to
Prompt
requested by
phase logic
Optional, use if
phase code
requests
Boolean
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Section 6 F Phase Programming
94
Table 6-3.
Recipe Manager Data Items (Continued)
Name
Usage (by
phase
logic)
Type
Description
Comment
PROMPT
FLOAT
Read (and/or
display)
Real
Value to hold
operator
response to
Prompt
requested by
phase logic
Optional, use if
phase code
requests Real
PROMPT INT
Read (and/or
display)
Int
Value to hold
operator
response to
Prompt
requested by
phase logic
Optional, use if
phase code
requests
Integer
PROMPT
STRING
None (for
display)
String
Value to hold
operator
response to
Prompt
requested by
phase logic
Optional, use
with CHIP
ASCII point
and phase
code requests
DeltaVt
WATCHDOG
Read/Write
Int
Used by Phase
Code to detect
communication
failure
Optional, FST
code is
required to use
as intended
REQDATA1
Read/Write
Int
Values used by
certain
requests
Optional, for
use with
request
functionality
::
::
REQDATA5
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.4
95
PROVOX Capabilities and Characteristics
This subsection points out the characteristics of the logic
capabilities in PROVOX controllers that allow for the
construction of equipment phases as required by the Recipe
Manager NT system. For complete information, please consult
your PROVOX console and controller documentation.
6.4.1
Unit Points with Operation Logic
This subsection describes the use of Unit points without any
implementation of the Recipe Manager NT system. Some of
the commands listed are not used within the Recipe Manager
NT system.
Operation logic is the fundamental type of batch control logic
used in the PROVOX system. Operations consist of named
phases and steps that in turn consist of instructions. The logic
proceeds from instruction to instruction within a step or phase,
and may proceed from phase to phase within an operation.
Alternatively, the logic may complete (go to idle) after each
phase or set of phases. The operator uses the following
commands to run operations at a PROVOX console.
Load/Start and Change Phase — This command is used to
start a unit operation. If the operator has tune privilege, he can
select the phase to run, or change to a different phase.
PPLI performs a Load/Start command for phases run from the
Recipe Manager NT system. For Recipe Manager NT phases
run manually from the PROVOX system, the operator must
perform the Load/Start command at the Unit point. After this,
any other interaction is made from the COMMAND DCD point.
Cancel Operation — This command is used to cancel a failed
operation, and allows the point state to go to IDLE. The
operator should not use this command for Recipe Manager NT
phases.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
96
Section 6 F Phase Programming
Hold, Hold Next, Clear Hold, Continue from Hold — These
commands allow the operator to schedule a hold if the current
PROVOX phase can implement this command. This is quite
different from a Recipe Manager NT HOLD. The PROVOX
HOLD does not change the course of the logic, but allows the
current logic to continue until the end of the phase. In contrast,
the Recipe Manager NT HOLD requires that the equipment
phase invoke the HOLDING logic. The operator should not use
this command for Recipe Manager NT phases.
Retry — This command allows the operator to retry a failed
operation by invoking the step configured as the retry step.
Stop/Fail — This command allows the operator to stop the
operation by invoking the step configured as the fail step. The
fail step is automatically called upon if a failure occurs with
associated equipment. The operator should not use this
command for Recipe Manager NT phases.
With the Recipe Manager NT system, the PPLI shell invokes
the Fail step as part of processing Recipe Manager HOLD,
STOP, and ABORT commands, as well as process failures.
The operator should not use this command for Recipe
Manager NT phases.
Operator Attention Requests (OARs) — OARs are not Unit
point commands as the above operator commands. An OAR
requests operator input through a special console request
facility, and may be invoked by operation logic.
OARs may be used with Recipe Manager NT phases if
desired. If phase parameters are supplied to fulfill INPUT
requests, the parameters replace OARs for recipe operation
with the Recipe Manager NT system, similar to the technique
of PROVOX activity procedures. If the phase is run manually
from the PROVOX system, these INPUT statements cause
OARs to be invoked.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
97
The State Transition Diagram for Unit points is much different
from that of the Recipe Manager NT system. In addition to the
Active, Holding, Failing, Failed, and Idle states as mentioned
above, there is a Waiting state used while waiting for the
operator to respond to an OAR request, or other process
waits.
6.4.2
LCPs with FST Logic
LCPs with FST logic are useful for many purposes, but
primarily for advanced regulatory or discrete control in the
PROVOX system. FSTs consist of instructions that may
branch to labels within an FST, or request that another FST be
invoked. An entire set of FST instructions is evaluated during
each scan. This scan rate can be configured. Each LCP has a
configured FST. LCP points contain operator commands to
Start, Advance, and Stop the FST.
6.5
Recipe Manager NT for PROVOX Phase Logic
Interface Solution
The preceding subsections have covered both Recipe
Manager NT requirements and PROVOX capabilities. This
subsection describes how the PROVOX Phase Logic Interface
uses these capabilities.
The interface and the protocol for the Recipe Manager NT
system, created from two PROVOX conventions, differ
substantially from those of the PROVOX system.
The DCD Control Interface — This interface allows the
generation of Recipe Manager NT-style manual phase control
from a PROVOX console. This interface uses two PROVOX
DCD points (per unit or LCP point); one to transfer the Recipe
Manager NT command to the PROVOX system, and one to
transfer the phase status back to the Recipe Manager NT
system.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
98
Section 6 F Phase Programming
The PPLI Shell — This shell enables engineers to limit their
efforts primarily to design and implementation of plant-specific
equipment phase control. It contains predefined phase
transition logic for both unit operations and LCP FSTs, and
also includes other standard configuration items.
The Flexible Option — The Flexible Option may be chosen to
allow for fewer register resources being required by Recipe
Manager NT. However, this option also disables certain Recipe
Manager NT features. The user must thoroughly understand
all the features affected before choosing this option.
You can still use the DCD Control Interface with the Flexible
Configuration option by selecting DCDs for the COMMAND
and STATUS registers.
6.5.1
DCD Control Interface
The DCD Control Interface allows operators to manipulate one
DCD point as the Recipe Manager NT command, and to view
another DCD point as the Recipe Manager NT status. This
method supersedes the standard PROVOX point control
methods.
The DCD Control Interface uses two DCD points together with
each main control point that is either a Unit point or an LCP
point. Each unit or LCP point interacts with user written
(operation or FST) phase logic to support an arbitrary number
of phases, with the connections configured in the PPLI. For the
DCD control interface’s phase logic, the DCD point types are
available for the CONTROL register and STATUS register.
These no input, no output DCDs allow the control request and
status to be clearly visible at the PROVOX console.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
99
This interface also allows basic operation of the control logic
without the use of the Recipe Manager NT system. The
following are the DCD templates used to support the Recipe
Manager NT COMMAND and STATUS registers. The order of
setpoints in this template is the same as in that of the
command for the Batch Operator Interface.
Flexible Option users can choose whether or not to use the
DCD interface. If the DCD interface is not chosen, it is the
user’s responsibility to adjust the PPLI shell accordingly.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
100
Section 6 F Phase Programming
PPLI_COMMAND DCD template:
Entry
SP Name
1
START
2
HOLD
3
RESTART
4
ABORT
5
STOP
6
RESET
7
PAUSE
8
RESUME
9
SINGLESTEP
10
Outputs
Inputs
Outputs
Inputs
DOWNLOAD
PPLI_STATE DCD template
Entry
SP Name
1
RUNNING
2
HOLDING
3
RESTARTING
4
ABORTING
5
STOPPING
6
COMPLETE
7
HELD
8
IDLE
9
ABORTED
10
STOPPED
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.5.2
101
Unit Operation Shell for PROVOX Phase Logic
The operation X-PPLIOPER is a template that assists the
configuration engineer in creating Recipe Manager NT phases
that conform to the Recipe Manager NT requirements. For
ease of configuration, you should make a copy of
X-PPLIOPER, giving it an appropriate new tag. You should
modify the copy according to the application requirements. If a
new copy of X-PPLIOPER is not feasible for each phase, you
can combine multiple Recipe Manager NT phases into one
PROVOX operation, specifying each Recipe Manager NT
phase as a PROVOX phase. Figure 6-3 charts the PPLIOPER
shell.
Recipe Manager NT
Starts Operation
RUNNING
FAIL
PROVOXR Failure
COMPLETE
Operation Ends
Failure from
COMPLETE
Recipe Manager NT
Hold Selected
Recipe
Manager NT
Stop
Selected
Recipe
Manager NT
Abort
Selected
STOP
ABORT
Figure 6-3.
HOLD
HOLD-SD
RESTART
PPLIOPER Shell Flow Chart
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
102
Section 6 F Phase Programming
See the Recipe Manager NT State Transition Diagram for
details of the various states for a phase, and the legal
commands that can cause a phase to move from one state to
another.
6.5.2.1
Organization
Upon receiving a START command, the operation will
commence at the RUNNING step (or if more than one Recipe
Manager NT phase exists per operation, the first step of the
PROVOX phase corresponding to the Recipe Manager NT
phase). When an operation starts, the first few instructions call
two subroutines. The SETUP subroutine sets up the
COMMAND and STATE DCDs to reflect current actions, and
performs any other initializations you have configured. The
CLEAR-FAIL subroutine disables second failures in the
operation, and clears the first failure index. Note that the first
failure index is not the same as the failure index of the Unit
point. The first failure index traps the very first failure that
occurs, while the failure index holds the value of the last
failure.
After the two subroutine calls, you can insert
application-specific logic to handle the normal RUNNING state
of the phase (for example, filling a reactor). You should edit
code only between the labels USER-EDIT and
USER-NO-EDIT. Instructions on how to modify the code follow
these characters.
Note that according to the State Transition Diagram, the phase
can leave the RUNNING state if the COMMAND DCD is in
ABORT, STOP or HOLD. If this happens, the FAILEXP causes
the operation to jump to a FAIL step where you can determine
the appropriate new state. For more information, see the
subsection, Failure Processing, on page 105.
In addition to RUNNING, there are also steps for the other
active states (HOLD, HOLD-SD, STOP, ABORT, RESTART).
You should insert any application-specific logic.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
103
Each step in the template X-PPLIOPER contains several
instructions for managing the COMMAND and STATE DCDs.
You should be careful not to change these, as they are
essential in allowing the Recipe Manager NT system to track
the state of the phase.
6.5.2.2
Parameter Handling
PPLI includes up to 16 auto-download parameter UVs in the
OPERATE command to the PROVOX system that starts the
unit operation at a phase. These UVs fulfill INPUT statements
in the PROVOX phase code which request values for the UVs,
so that OARs are not sent to request this data from the
operator. (This is equivalent to Grade data sent from
procedures in PROVOX activities.) If run from the PROVOX
system in manual mode, the operator supplies these UV
values through OARs.
Other auto-download parameters are sent prior to the operate
call. These may be sent to the source Unit point, other Unit
points, LCP points, or CHIP ASCII points. If you use the
PROVOX system in manual mode, an operating procedure or
special code must be used to populate these parameters.
Auto-upload reports do not use the Complete mechanism
used by Batch-end data in PROVOX activities. Use 0 as the
UV mask argument for all Complete statements in PROVOX
phases that implement the Recipe Manager NT system’s
equipment phase logic. Auto-upload reports values are
transferred by PPLI using request-response communications
after the PROVOX STATE DCD goes to the COMPLETE state,
but before the PPLI sets the phase status to COMPLETE for
the Recipe Manager NT system.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
104
Section 6 F Phase Programming
6.5.2.3
CHIP ASCII Point Considerations
Either local CHIP ASCII points or points from a remote CHIP
that have been targeted to the local CHIP may be used for
Recipe Manager NT report parameters. All Recipe Manager
NT report parameters (including ASCII reports) are read from
the source point at the time of upload.
For parameters connected to a CHIP ASCII point, you may
use an occurrence number of up to 79 characters to build an
ASCII message from various parameter sources. Use an
occurrence number of 0 or 1 to clear the current message and
to supply a base message. Then, use appropriate (1 origin)
occurrence numbers to merge other values into this message.
For example, the following message could be used as the
base message in a MANUAL_INGREDIENT phase:
The amount of ___________ added is _____ lbs.; Operator
id = __________
This message can be set as both the default in the equipment
configuration, and as a value parameter in the recipe. The text
that completes the blanks can then be set by other parameters
connected to the same PROVOX ASCII point. The occurrence
numbers (determined by the counting characters) would be 15
for the ingredient name, 35 for the amount, and 60 for the
operator ID. These must all be configured in the DeltaV
Explorer as type String.
The recipe author can fill in the ingredient name and amount in
the recipe, which would either be value or formula (defer)
parameters. The following message is an example of a
partially built up message:
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
105
The amount of Salt added is 45.5 lbs.; Operator id =
__________
The amount (actual) and Operator ID can be requested as
Operator parameters. The following message is an example of
a fully built up message.
The amount of Salt added is 45.5 lbs.; Operator id =
JD-301
These built up messages are best created with local ASCII
points, so that the autodownload option can be used. If
creating these messages with remote points, use one
parameter merge per phase, or supply phase logic that
provide timers between the parameter requests. These
methods ensure that the local database can be updated
between each parameter download. (The strings are merged
into the local copy of the string at the ASCII point.)
6.5.2.4
Failure Processing
There are four different ways in which an operation run by the
Recipe Manager NT system can cause a PROVOX operation
FAIL. These are as follows:
J
ABORT command from the Recipe Manager NT system
J
STOP command from the Recipe Manager NT system
J
J
HOLD command from the Recipe Manager NT system
(this can be caused either by an operator selection or a
Recipe Manager NT failure)
PROVOX failure detection
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
106
Section 6 F Phase Programming
The PROVOX operation FAIL step handles all of the above
cases. The FAIL step deciphers the cause of the failure and
branches to the appropriate step. For example, if an operator
sets the COMMAND DCD to ABORT, STOP or HOLD from the
Recipe Manager NT system, the operation then branches to
the ABORT, STOP or HOLD step, respectively. You should
insert required application-specific logic in all three steps.
A different set of procedures handles PROVOX failures. If the
operation fails from the PROVOX controller or console level,
the operation branches to the FAIL step. In the FAIL step, you
can specify phase specific failure conditions monitored in the
operation’s fail expression (FAILEXP). The FAIL step
translates the phase specific failure into a value that is stored
into the Recipe Manager NT FAILURE register (UV1). The
FAIL step also monitors for PROVOX failures as well. For
example, if the operation fails because the driven point was
not in the proper mode, the FAIL step would copy the failure
index into the Recipe Manager NT FAILURE register.
An operation failure caused by PROVOX drives the FAIL step
to branch to the HOLD-SD (SD = Shut Down) step. You should
insert any required application-specific logic in the HOLD-SD
step.
If the operation branches to the HOLD-SD or HOLD step, the
operator has the option of restarting the operation. This
selection activates the operation to the RESTART step that
then branches back to the step from which the operation first
failed.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.5.2.5
107
Phase Connections for Recipe Manager NT Software
If you use unit operations, you must also connect the
operation and phase name. To do this, these names must be
accessible at the NT level for the PPLI software. SQL can
generate a file from information in the ENVOX database from
which you can select an appropriate name. For more
information, see the subsection, PROVOX Unit Operation and
Phase Name File for PPLI, on page 114.
6.5.3
Importing the Shell Configuration into the ENVOX
Database
The shell configuration consists of a set of CDV files
containing various ENVOX items that can be used in creating
a Recipe Manager NT system.
These files are located by default in the C:\RMNT2.0 directory.
Copy these files to your ENVOX database and import all of
them using the ENVOX Import utility. Check the log file to
ensure that everything has been imported correctly.
Do not modify any of these items through the ENVOX forms.
These are meant to be copied to create new phases; the
originals should not be changed. If you are using the ENVOX
Audit Trail, it is useful to check occasionally that none of these
items has been inadvertently changed. If any of these items
have been modified accidentally, re-import them from the CDV
files to restore them.
The tags in this configuration, with their intended purpose, are
summarized in the Table 6-4.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
108
Section 6 F Phase Programming
Table 6-4.
Tag
ENVOX Configuration Tags
ENVOXr
r Item
Type
Purpose
X-ABORTING
LCP FST
Template FST for
ABORTING state.
Copy for each phase.
X-HOLDING
LCP FST
Template FST for
HOLDING state. Copy
for each phase.
X-RESTARTING
LCP FST
Template FST for
HOLDING state. Copy
for each phase.
X-RUNNING
LCP FST
Template FST for
RUNNING state. Copy
for each phase.
X-STOPPING
LCP FST
Template FST for
STOPPING state.
Copy for each phase.
X-PPLIMAIN
LCP FST
Template main FST for
a phase. Copy for
each phase.
X-PHASE1
LCP FST
Template FST for
subroutine called from
X-PPLIMAIN.
X-PHASE2
LCP FST
Template FST for
subroutine.
ABORTED
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
COMPLETE
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
HELD
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
IDLE
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
STOPPED
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
Table 6-4.
Tag
109
ENVOX Configuration Tags (Continued)
ENVOXr
r Item
Type
Purpose
PHASELOGIC
LCP FST
Standard Recipe
Manager NT FST - Do
not modify.
CHECK-PAUSE
LCP FST
Standard FST for
pause processing call where needed, do
not modify.
X-PPLIOPER
OPERATION
Template Operation for
a phase. Copy for
each phase.
X-PPLI-LCP
LCP
Template LCP point.
Copy for each phase.
X-PPLI-UNIT
UNIT
Template Unit point.
Copy for each phase.
X-PPLICMD
DCD
COMMAND DCD.
Copy for each phase.
X-PPLISTAT
DCD
STATE DCD. Copy for
each phase.
T-PPLICMD
DCD TEMPLATE
Template for
COMMAND DCDs.
T-PPLISTAT
DCD TEMPLATE
Template for STATE
DCDs.
A-PPLI
ALIAS TEMPLATE
Alias Template for
units running Recipe
Manager NT phases.
TS-LCP-PHASE
TAG SET
Tag set to help in
creating a new
LCP-based phase.
TS-UNITPHASE
TAG SET
Tag set to help in
creating a new
unit-based phase.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
110
Section 6 F Phase Programming
6.5.4
FST Shell for PROVOX Phase Logic
There is a set of 14 FSTs provided to help you implement
phase logic if you have an LCP with COMMAND and STATE
DCDs for an equipment module. Some of these FSTs are
templates for you to copy and then modify according to
application control requirements. The others are standard
code that you should not copy or change.
The job of these FSTs is to carry out the control tasks required
by the phase while it is conforming to the State Transition
Diagram defined for all phases.
See the State Transition Diagram for details of the various
phase states, and the legal commands that can cause a phase
to move between these states. For information on how to copy
the shell to new items, see the section, Creating a New Phase
in the PROVOX System, on page 84.
6.5.4.1
Organization
PPLI’s set of FSTs includes one main FST and the eleven
subroutines it calls. The PHASELOGIC subroutine determines
what the new state should be, based on the current state and
any new commands received. Then, one of the other
subroutines executes to perform the appropriate actions for
the state.
X-PPLIMAIN
call PHASELOGIC
switch (state)
RUNNING: call X-RUNNING
call X-PHASE1, X-PHASE2, etc.
(X-RUNNING occurs only once per execution)
HOLDING: call X-HOLDING
RESTARTING: call X-RESTARTING
ABORTING: call X-ABORTING
STOPPING: call X-STOPPING
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
111
COMPLETE: call COMPLETE*
HELD: call HELD*
IDLE: call IDLE*
ABORTED: call ABORTED*
STOPPED: call STOPPED*
end switch
Each of the subroutines apart from PHASELOGIC represents
one of the ten possible states of an equipment module. The
FST determines what happens in that state. The asterisks
indicate standard, quiescent states that should not be
modified.
The FSTs COMPLETE, HELD, IDLE, ABORTED, and
STOPPED are standard, and you should not modify them.
These FSTs are indicated by an asterisk in the example that
follows. Upon the configuration of a new equipment module,
you should copy the others to new tag names. These can then
be modified according to need.
Those FSTs without an asterisk indicate an active state where
you need to configure some application specific actions. Note
that the names of the FSTs for the active states all end in the
characters ...ING indicating that they are active states. The
FSTs with an asterisk represent the quiescent states where the
equipment module waits for a new command.
The subroutines, written generically, are usable on any LCP.
There are no references to specific point tags or global
registers.
To create a new phase for controlling an agitator, you may
copy X-PHASE1 to a new FST called 1-AGIT. (Note that it is
advisable that the prefix, X-, be substituted with a character
that groups all of the non standard FSTs associated with the
same LCP. Doing so combines the set into one coherent
group.)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
112
Section 6 F Phase Programming
1-AGIT will then be edited to provide the control logic required
for normal operation. You will need to copy the X-RUNNING
subroutine as 1-RUNNING, and modify it to call 1-AGIT. You
may also copy X-ABORTING and X-STOPPING to new FSTs
called 1-ABORTING and 1-STOPPING and edit these to
provide specific behavior in the event of an ABORT or STOP
command.
Finally, you will copy X-PPLIMAIN to a new tag (for example,
1-PPLIMAIN), and edit the call statements so that 1-AGIT,
1-RUNNING, 1-ABORTING and 1-STOPPING are usable.
The structure of FSTs for this example are as shown in the
following example. The asterisks indicate standard, quiescent
states that should not be modified.
1-PPLIMAIN
call PHASELOGIC
switch (state)
RUNNING: call 1-RUNNING
call 1-AGIT, 1-DRAIN, 1-FILL, etc.
(X-RUNNING occurs only once per execution)
HOLDING: call 1-HOLDING
RESTARTING: call 1-RESTARTING
ABORTING: call 1-ABORTING
STOPPING: call 1-STOPPING
COMPLETE: call COMPLETE *
HELD: call HELD *
IDLE: call IDLE *
ABORTED: call ABORTED *
STOPPED: call STOPPED *
end switch
You can also write as required specific versions of HOLDING
and RESTARTING.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.5.4.2
113
Execution Scheme
You should configure the main FST (and user-modified copies
of it) with an LCP that runs continuously. Set the scan rate to
match the response time requirements of the process.
Every scan calls PHASELOGIC to determine if it has received
any change (for example, a STOP command from the Recipe
Manager NT system). Based on this it will set register I31
(Reserved Scratch) to indicate in what state the phase should
now be. Then, one of the other FSTs will run corresponding to
the (new) state. On the next scan the process repeats.
For properly handled state changes, it is important that the
main FST runs on a periodic basis. Therefore, you must write
your logic to conform with this execution scheme. Avoid
instructions like WAIT that pause the FST execution.
When using the template FSTs, write application-specific logic
to ensure that the placement of instructions occurs only
between the labels USER-EDIT and USER-NO-EDIT. Further
instructions normally follow this mark. The code in the
template FSTs ensures that the Recipe Manager NT system
receives the state of the phase report.
When a user-written subroutine determines that the phase
needs to change state, the subroutine must appropriately set
the STATE DCD setpoint. For example, 1-ABORTING would
perform some application specific actions (for example, to stop
the agitator), and then it would change the phase to the
ABORTED state. Note that the template code in X-ABORTING
shows how to do this (set the STATE DCD setpoint to 9).
Normally the 1-ABORTING code would verify that the agitator
had actually stopped before proceeding to the ABORTED
state.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
114
Section 6 F Phase Programming
6.5.4.3
Register Usage
Certain registers are held in reserve for the use of the shell
code. For a complete list of these registers, see Table 6-4, and
for their allocation, see Table 6-5.
Caution ... You are responsible for initializing I29 and I30 with
the appropriate DCD database index (DBI) numbers.
You must do this carefully for every LCP using this
shell. Unpredictable results could occur if you write
the DBI to the wrong DCD.
The absolute DBI is calculated by multiplying the point type
number (8) by 256, getting the answer 2048, and then adding
the relative DBI number of the DCD. For example, relative DBI
7 would result in the absolute DBI 2055.
6.5.5
PROVOX Unit Operation and Phase Name File for
PPLI
PPLI uses an input file to provide both operation and phase
names, and entry numbers. It is your responsibility to ensure
that the current ENVOX data is in use at the time of
configuration. You may accomplish the Initial entry manually
with an editor, if you have not yet completed the ENVOX
configuration. Before running the configuration, however, you
must use a file derived from the ENVOX database to ensure
that the entry numbers are correct. (Entry numbers replace tag
names in the PROVOX commands.)
How to access the file from OpenVMS:
1. Copy the supplied input file, PPLIOPER.SQL from the
PPLI shell directory, placing the actual data base name
where indicated.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
115
2. From the machine where the ENVOX configuration is
displayed, run the file under OpenVMS or Unix using the
following command:
$ISQL /u=“sa”/p=<sapassword>
/inp=pplioper.sql/out=pplioper.txt
for UNIX or MS-DOS (Control Desktop or Open Database),
use:
> isql -U sa -P sapassword -i pplioper.sql >
pplioper.txt
3. On the NT computer on which the Recipe Manager NT
system resides, copy the PPLIOPER.TXT file into the
same directory as the other configuration files.
The following is an example of the resulting file format in
PPLIOPER.TXT
unit_tag
opn_tag
index_no
------------ ------------ -------DUMP TK 1
DUMP OP
1
DUMP TK 1
RINSE OP
2
DUMP TK 2
DUMP OP
1
DUMP TK 2
RINSE OP
2
REACT0R-1
REACT
3
REACT0R-1
TRANSFER
4
(6 rows affected)
opn_tag
step_name
entry
---------- ---------------DUMP OP
DUMP_RUNNING
1
DUMP OP
COMPLETE
2
DUMP OP
FAIL
3
RINSE OP
RINSE_RUNNING 1
RINSE OP
COMPLETE
2
RINSE OP
FAIL
3
::
::
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
116
Section 6 F Phase Programming
Warning ... It is extremely important that you set up engineering
and operating procedures to ensure that the
PPLIOPER.TXT file is updated whenever you
change the number of operations, the number or
order of phases within an operation, or the valid
operations for one or more unit point.
These changes must not be downloaded to the
PROVOX controller while any Recipe Manager NT
batch is operating, since they will effect currently
operating batches.
If the PPLIOPER.TXT file does not exactly reflect the
configuration of the running system, serious and
unpredictable results may occur, which are hard to
trace.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6
117
Phase logic Design and Programming
You can organize your phase logic programming around
connections with the used registers. Table 6-5 lists these
connections. If you use the Flexible Option, you may alter
these connections. If that is the case, it is your responsibility to
communicate your connection.
Table 6-5.
Register
Phase Logic Register Allocations
Read/Write
(from phase
logic)
PROVOXr
r
Unit Point
with
Operation
logic
PROVOX
Logic
Control
Point (LCP)
with FST
logic
Command
Read
SP of
PPLI_CMD
DCD
SP of
PPLI_CMD
DCD
Status
Write (shell
only)
SP of
PPLI_STAT
DCD
SP of
PPLI_STAT
DCD
FAIL_INDEX
Write
(shell/logic)
UV[1]
FPREG[1]
(MVPCV[1])
Request
Write (logic)
UV[2]
IREG[2]
(MVPCV[6])
Phase_ID
Read/Clear
(shell)
UV[3]
IREG[3]
(MVPCV[7])
Step_Index
(Last Step#)
Write (logic)
UV[5]
IREG[1]
(MVPCV[5])
Owner
Write (logic)
BV[1]
BREG[1]
(MVPCV[9])
Unit
Read (logic)
UV[4]
IREG[28]
PAUSE_REQ
Read (logic)
BV[2]
BREG[30]
PAUSED
Write (logic)
BV[3]
BREG[2]
(MVPCV[10])
SINGLE_STEP
Read (logic)
BV[4]
BREG[31]
DOWNLOAD_
REQ
Read (logic)
BV[5]
BREG[29]
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
118
Section 6 F Phase Programming
Table 6-5.
Register
Phase Logic Register Allocations (Continued)
Read/Write
(from phase
logic)
PROVOXr
r
Unit Point
with
Operation
logic
PROVOX
Logic
Control
Point (LCP)
with FST
logic
Write
PPLI SHELL
(Scratch/
Next Status)
UV[32]
IREG[31]
COMMAND
DCD
Configuration
Unit Definition
Alias Name
PPLI-CMD
REG[29]
(Absolute DBI #)
STATE DCD
Configuration
Unit Definition
Alias Name
PPLI-STAT
IREG[30]
(Absolute DBI #)
Batch ID
N/A
Flexible
Flexible
Boolean Prompt
Write
Flexible
Flexible
DeltaVt
Watchdog
Read/Write
Flexible
Flexible
Floating Point
Prompt
Write
Flexible
Flexible
Integer Prompt
Write
Flexible
Flexible
String Prompt
Write
Flexible
Flexible
# of Request
Write
Flexible
Flexible
REQDATA1
.
.
.
REQDATA5
Read/Write
Flexible
Flexible
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.1
119
Register Interactions
Registers are used for any communication between equipment
phases in the Recipe Manager NT system and the controller.
The primary registers are BCOMMAND, BSTATUS,
FAIL_INDEX, and REQUEST. The following subsections
describe these and other registers used in the Recipe
Manager NT system.
6.6.1.1
COMMAND Register and STATUS Register
The PPLI translates the BCOMMAND register to become the
COMMAND DCD setpoint. It is the responsibility of the phase
logic to monitor and respond to this setpoint. The operation
and FST shell code, provided with the Recipe Manager NT
system, respond so that the phase programmer supplies
custom logic for running, holding, restarting, aborting, and
stopping in the reserved locations. If the shell code is
changed, it is your responsibility to test for proper monitoring
of the state change commands.
The PPLI translates the STATE DCD setpoint to become the
BSTATUS register for the Recipe Manager NT system. It is the
responsibility of the phase logic to set the setpoint of the
STATE DCD. The STATE DCD thereby indicates phase state
changes to the Recipe Manager NT system. The operation
and FST shell code, provided with the Recipe Manager NT
system have already been programmed to do this. If the shell
code is changed, it is your responsibility to test for proper
operation of all valid state transitions.
For the Flexible Configuration option, both the COMMAND
register and the STATUS register are pre-selected, and may
not be de-selected. These may be assigned to DCDs if
desired. If they are not, it is up to the user to modify the shell.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
120
Section 6 F Phase Programming
6.6.1.2
FAIL_INDEX Register
The controller phase logic may detect error conditions
requiring batch HOLD and operator action. To cause this, the
phase logic writes an error condition code to the FAIL_INDEX
register. You can modify the Recipe Manager NT configuration
so that the displayed text message interprets the error code
for the operator.
A failure number occurs whenever any device detects a fail
condition or whenever a process condition occurs that requires
a HELD state. An increase in the failure priority when the
phase is in the RUNNING, HOLDING, HELD or RESTARTING
state causes the phase to transition to the start of the
HOLDING logic. A failure number greater than zero can also
inhibit the state transitions of IDLE to RUNNING and HELD to
RESTARTING.
If selected from the Flexible Configuration option, the Failure
register can be populated by the user code which includes
error codes specific to the user phase logic. If set, the phase is
recognized by the Executive as Failed, and a Hold command
is issued. User fail values are from 501 to 756, corresponding
to the phase_failures set in the DeltaV Explorer. These
phase_failures are configured by the user and displayed by
the Batch Executive.
The PPLI shell code also copies to the Fail Index from the
control point (Unit or LCP) to the fail register. This should be
maintained if the shell is altered for Flexible Configuration use.
If not selected, the PPLI software uses the value of the Fail
Index as the Fail register, and the user cannot enter error
codes. However, failure at the Unit point or LCP is interpreted
as a failure, and the batch is held. It is recommended that a
Failure register be allocated since operational difficulties can
result if not. If the user does not allocate a Failure register, the
user should thoroughly test failure scenarios.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.1.3
121
OWNER Register
The phase programmer may use the OWNER Register only if
there is a need to take ownership of a different phase from the
phase logic, while leaving the point in Computer mode. In this
case, the controlling phase would set the OWNER register of
the unit or LCP point of the phase to control to 1 (TRUE).
In normal operation, setting the mode of the Control DCD or
the phase logic point (unit or LCP) to Manual mode causes the
setting of the OWNER bit. This setting in turn causes the batch
to be HELD according to the HOLD propagation setting of the
Batch Executive machine.
The OWNER register may be set to TRUE to indicate that a
phase is under Manual control by the PROVOX system. Note
that the Recipe Manager NT system will only recognize this
setting when the phase is IDLE; therefore, it would normally be
set by tuning the BREG or BV as a DDP rather than from FST
code. When this is TRUE, and the phase is IDLE, the Recipe
Manager NT system will not allow any commands to be sent to
the phase.
If selected from the Flexible Configuration option, the user can
set the owner register bit to show external control of a phase.
If not selected, the user has no capability for external control.
6.6.1.4
PAUSE, PAUSED and SINGLE_STEP Registers
The operator can request a single pause by issuing a PAUSE
command to the phase. This sets the PAUSE bit, indicating
that the phase will pause at the next programmed transition.
The PPLI resets the PAUSE bit when the next RESUME
command occurs, causing only a single pause to occur.
The SINGLE_STEP attribute indicates when the phase is in
the SINGLE_STEP mode. The SINGLE_STEP mode allows
the phase to continue to the next programmed pause and then
to wait for the operator to issue a RESUME command.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
122
Section 6 F Phase Programming
Correct operation of PAUSE, PAUSED and SINGLE_STEP
depends on the phase logic to handle them appropriately. The
phase logic must contain the instructions to take action on
these pause commands. If no action is taken, these
commands will have no effect. This may be a desired
behavior, if, for example, pauses are not permitted.)
This approach is necessary since neither the Recipe Manager
NT system, PPLI, nor the shell can know what behavior is
appropriate for all applications.
The phase programmer should determine the points in the
phase execution where a pause is allowed, and then insert the
appropriate code to deal with it. The code required will be
different depending on whether the phase is LCP-based or
unit-based.
Pause Register Set — If selected, the pause functionality
may be used. If not selected, attempts to use the Pause
functionality will have no effect, except that the PAUSING
indicator will remain until the phase is reset to IDLE.
6.6.1.4.1
PROVOX LCP PAUSE Logic
In an LCP-based phase, the subroutine CHECK-PAUSE
should be called at any point where the phase is able to
accept a pause. CHECK-PAUSE will return with the SVD set
to TRUE if a pause is in effect. In this case the phase
programmer should write the code so that the phase responds
appropriately. If the phase is running a fixed-sequence control
task, for example, the appropriate behavior might be to defer
proceeding to the next step in the sequence while the pause is
in effect.
After the operator presses the RESUME button, the next time
CHECK-PAUSE is called, it will return FALSE. The phase
programmer should interpret this as a signal that the phase
should proceed with normal operation.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
123
If SINGLE_STEP is in effect, CHECK-PAUSE will return TRUE
until the operator presses Resume, and then it will return
FALSE for one execution only. The phase programmer must
detect this condition and advance the phase to the next pause.
The LCP phase programmer should not need to monitor the
PAUSE, PAUSED and SINGLE_STEP registers directly.
CHECK-PAUSE will handle them. Also, the phase programmer
should be careful to avoid changing those registers.
Example usage:
To open a valve and start a pump, and we should allow the
operator to pause the phase in between these tasks. (In a real
application you would probably want to check that the valve
actually opened.)
LDSV
(1)
DAWT (I, SP:VALVE-1)
{open valve}
{We accept a pause at this point, so check for
one}
CALL
(CHECK-PAUSE)
BRA
(=, TRUE, THE-END)
{jump to the end of the FST and do not do any more
processing while being paused}
RESUME
(LABEL10)
{SVD = FALSE, means there is a RESUME from the
Recipe Manager system, so proceed from here on the
next scan}
LABEL10:
LDSV
(1)
DAWT (I, SP:PUMP-1)
{start pump}
....continue with next step in processing
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
124
Section 6 F Phase Programming
Note that the RESUME instruction above tells the FST where
to start processing on its next scan. (Despite the similar name
it has no direct relationship to the RESUME in Recipe
Manager NT terminology.) In this case the next scan will start
from LABEL 10, and CHECK-PAUSE will not be called again
once the RESUME command has been processed.
6.6.1.4.2
PROVOX Unit Operation PAUSE Logic
In a unit-based phase, monitoring of the PAUSE and
SINGLE_STEP registers is entirely the responsibility of the
phase programmer. There is no special support in the shell as
there is for LCPs. User code must also take care of updating
the PAUSED register to indicate to the Recipe Manager NT
system that the pause has been accepted.
At any place in the operation where a pause may be accepted,
code such as this might be inserted to handle a single pause:
CONST (SP:VALVE-1, 1)
{open valve}
{We accept a pause at this point, so check for
one}
IF (BV[2] = FALSE,LABEL10)
{test Pause flag}
CONST (BV[3], TRUE)
{indicate that you are paused}
WAITUNTIL (BV[2] = FALSE)
{wait for the RESUME}
CONST (BV[3], FALSE)
{indicate you are resuming}
LABEL10: ....
{start pump}
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
125
This can be extended to handle SINGLE_STEP by additionally
checking on BV[4] in the first instruction:
IF (BV[2] = FALSE AND BV[4] = FALSE, LABEL10)
CONST (BV[2], TRUE)
CONST (BV[3], TRUE)
{indicate you are paused}
WAITUNTIL (BV[2] = FALSE)
{wait for the RESUME}
CONST (BV[3], FALSE)
{indicate you are resuming}
LABEL10: ....
{proceed}
To have the preceding code perform correctly, you must set
the PAUSE register BV[2].
6.6.1.4.3
Handling the PAUSE, RESUME and SINGLE_STEP
Commands from the PROVOX Console
If a phase is being controlled from the PROVOX system
(COMMAND DCD is in MAN, Owner flag is TRUE) then the
PROVOX operator can still use the PAUSE, RESUME and
SINGLE_STEP commands from the console by manipulating
the COMMAND DCD setpoint.
For an LCP-based phase, this needs no special handling on
the part of the phase programmer. The three registers used in
PAUSE/RESUME/SINGLE_STEP processing will be kept
updated by the FST shell.
For a unit-based phase, there is no special shell support for
keeping the registers updated. Therefore, if a unit-based
phase is to be manually operated, and if
PAUSE/RESUME/SINGLE_STEP functionality is desired, the
code above should be written to use the DCD setpoint rather
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
126
Section 6 F Phase Programming
than relying on the registers. The second example would
become:
IF (SP:CMD-DCD<>’PAUSE’ AND
SP:CMD-DCD<>’SINGLESTEP’, LABEL10)
DBI (UV[6], SP:CMD-DCD)
{save whether it was RESUME or SINGLESTEP}
CONST (BV[2], TRUE)
CONST (BV[3], TRUE)
{indicate you are paused}
WAITUNTIL (SP;CMD-DCD = ’RESUME’)
{wait for the RESUME}
CONST (BV[3], FALSE)
{indicate you are resuming}
IF (UV[6] <> 9, LABEL10)
{not SINGLESTEP}
CONST (MODE:CMD-DCD, 6)
CONST (SP:CMD-DCD,SINGLESTEP)
{SINGLESTEP,stay there}
LABEL10: ....
{proceed}
Note ... It is important to remember whether you are in
PAUSE or SINGLE_STEP, and to restore to
SINGLE_STEP if necessary. The CMD-DCD
setpoint changes as the operator goes from
SINGLE_STEP to RESUME However, it is
necessary to stay in SINGLE_STEP until specifically
cancelling it by selecting START.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.1.5
127
REQUEST Register
Phase logic uses the REQUEST register to:
J
J
J
Cause a transfer of recipe parameters from the Recipe
Manager NT system.
Cause a transfer of report parameters to the Recipe
Manager NT system.
Acquire or release the Recipe Manager NT system
resources.
J
Send a predefined message to the operator.
J
Send, wait for, and receive messages from other phases.
J
Cause a prompt for data from the operator. See sections
6.6.1.7 through 6.6.1.15.
If the Request register is selected from the Flexible
Configuration option, the user logic may make requests
through the Batch Executive, including requests for parameter
download or upload, messages or prompts to the operator,
equipment acquirements and releases, and messages to other
phases. If not selected, the user logic may not use the
Request functionality.
PPLI provides automatic download of phase parameters and
upload of report parameters. If this is sufficient for phase
needs, the phase logic may not need to use the REQUEST
register at all.
Find information on using the REQUEST register for phase
logic code in the subsection, Phase Logic Design and
Programming, on page 117.
If the REQUEST register is in use, it may be necessary to
program separate paths for PROVOX manual mode operation
versus Computer mode. These separate paths are necessary
since OARs (input statements) must perform some of these
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
128
Section 6 F Phase Programming
functions in PROVOX manual mode, and then wait until
commands are required to do the REQUEST register actions.
6.6.1.6
PHASE ID Register
PPLI writes and uses the PHASE ID Register to determine
which phase is running at the PROVOX point. This is the
equipment ID configured in the DeltaV Explorer for the
equipment phase. Use operation or LCP logic to read this
register to determine which phase is active.
The Phase ID register indicates which Recipe Manager NT
Equipment phase is in control of this PROVOX point. The
Phase ID can be set in the DeltaV Explorer (select the phase,
then click the secondary [right] mouse button and choose
Phase Properties from the drop-down menu, and look for the
Equipment ID field). This can be read by user code to allow
decisions to be made. This technique allows a single FST to
be used for multiple similar or identical phases. User code
may not modify the contents of the Phase ID register.
If the Phase ID register is selected from the Flexible
Configuration option, the PPLI software can check to see if the
desired phase is the active one during warm start. If not
selected, a warm start after a down time during which phases
were run manually could result in the recipe step attempting to
control a phase that it should not.
Caution ... If the Phase ID Register is not selected, ensure that
warm start procedures include steps to verify that
any active phases are the same as those of the
recipe.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.1.7
129
STEP_INDEX Register
Maintaining the STEP_INDEX is the (optional) responsibility of
the phase logic. PPLI monitors and transfers this register
directly to the Recipe Manager NT system, and then it is
usable for the recipe logic, for example in transition conditions.
The STEP_INDEX register may be modified by user code. It
is available as an attribute in transition expressions in recipes.
The conventional use would be to indicate which of a series of
steps a phase had completed, and allow a recipe to make
decisions based thereon. The user must define the values
written to this register, and how it is used and to keep the
recipe and the FST code in alignment.
If the Step Index register is selected from the Flexible
Configuration option, user code may write a number to
indicate the progress of the phase. This number is available
on the Hierarchical Step List, Active Phase Summary, and the
Phase Control displays of the Batch Operator Interface. If not
selected, the Step Index is populated with the PROVOX
operation step number if a PROVOX Unit point is used, and
with 0 if an LCP is used.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
130
Section 6 F Phase Programming
6.6.1.8
UNIT Register
The Equipment ID number (set in the Recipe Manager NT
DeltaV Explorer) indicates the Recipe Manager NT unit in
which the phase is running. This register is for the use of the
phase logic, if needed. (The Unit point running an
operation-based phase indicates this information for many
applications.)
The UNIT register indicates which Recipe Manager NT unit is
in control of this PROVOX point. The unit ID can be set in the
DeltaV Explorer (select the unit, then click the secondary
[right] mouse button and choose Unit Properties from the
drop-down menu, and look for the Equipment ID field). This
can be read by user code to allow decisions to be made. This
technique allows a single FST to be used for multiple similar or
identical units. User code may not modify the contents of the
UNIT register.
If the Unit register is selected from the Flexible Configuration
option, the Equipment ID of the active recipe manager unit is
available in the phase logic. This is useful for shared phases,
or for phases where multiple units use common logic. If not
selected, the Equipment ID of the unit is not available to the
phase logic.
6.6.1.9
Batch ID Register
If the Batch ID register is selected, the Batch Executive and
PPLI automatically transfer the Batch ID to the connected
CHIP ASCII point. If not selected, the Batch ID is not
automatically transferred. (In either case, the Batch ID is
available through the 71xx request, as it was in Recipe
Manager NT V.1.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.1.10
131
DeltaV Watchdog Register
If the DeltaV Watchdog register is selected, the user code
must clear the lower bit of the Watchdog register whenever it
is set. If not selected, the DeltaV Watchdog is maintained
entirely within the PPLI code.
6.6.1.11
# of Request Registers
Set this number to indicate the maximum number of request
registers needed for any request you may do from the code. If
an insufficient number is used, requests for which they are
required will return invalid results.
6.6.1.12
Integer Prompt Register
If the Integer Prompt register is selected, the user may use
request code 32nn (3200 indirect) to request integer data from
the operator, where nn is the number of the Phase Message
configured with the Phase Class. The connected PROVOX
register is populated with the result. If not selected, the 32nn
request does not return the operator’s value.
6.6.1.13
Floating Point Prompt Register
If the Floating Point Prompt register is selected, the user may
use request code 33nn (3300 indirect) to request floating point
data form the operator, where nn is the number of the Phase
Message configured with the Phase Class. The connected
PROVOX register is populated with the result. If not selected,
the 33nn request does not return the operator’s value.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
132
Section 6 F Phase Programming
6.6.1.14
Boolean Prompt Register
If the Boolean Prompt register is selected, the user may use
request code 34nn (3400 indirect) to request boolean data
from the operator, where nn is the number of the Phase
Message configured with the Phase Class. The connected
PROVOX register is populated with the result. If not selected,
the 34nn request does not return the operator’s value.
6.6.1.15
String Prompt Register
If the String Prompt register is selected, the user may use
request code 35nn (3500 indirect) to request String data from
the operator, where nn is the number of the Phase Message
configured with the Phase Class. The connected CHIP ASCII
point is populated with the result. If not selected, the 35nn
request does not return the operator’s value.
6.6.2
Use of the DOWNLOAD Command
In certain special cases, the Recipe Manager NT system might
issue a DOWNLOAD command to a phase. This will happen
where the same phase is active before and after a recipe
transition. For an example procedural function chart (PFC),
see Figure 6-4.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
133
TRUE
FERM_CHRG:1
AGITATE:1
FERM_CHRG:1.STATE=COMPLETE
FERM_CHRG:2
AGITATE:2
FERM_CHRG:2.STATE=COMPLETE
Figure 6-4.
Example PFC for the DOWNLOAD Command
Here, two charge phases are being executed in sequence, for
different ingredients, but the AGITATE phase is required to
keep executing without stopping. Notice that the transition
expression does not wait for the AGITATE step to be complete
before proceeding. Also note that it is the same AGITATE
phase before and after the transition.
In such a recipe, the Recipe Manager NT system assumes
that AGITATE is not to be STOPPED and then STARTED.
Rather, the AGITATE phase continues to run, but is sent by
the Batch Executive a DOWNLOAD command. Typically, the
phase would take some action on receiving this command,
such as asking for a parameter to be downloaded (perhaps a
parameter is used to set the agitator speed differently for the
two charges). The Recipe Manager NT system sets the
COMMAND DCD to DOWNLOAD when this happens. It also
sets the DOWNLOAD register to TRUE.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
134
Section 6 F Phase Programming
It is the user’s responsibility to create phase logic to detect
and handle the DOWNLOAD command. This would mean
writing unit operation or FST code to:
J
J
J
Monitor the DOWNLOAD flag (a BV or BREG) and branch
to some special code when it becomes TRUE
Take whatever action is necessary for the application (for
example, performing a 1000 request to download all phase
parameters)
Clear the DOWNLOAD register after it has been
processed
Note ... The Recipe Manager NT will reset the COMMAND
DCD setpoint the next time a new command is
received, but it will not clear the DOWNLOAD
register. This is the user code’s responsibility.
There is no specific shell support for this other than to set the
DOWNLOAD flag.
If the Download register is selected from the Flexible
Configuration option, user code may be programmed to
request a download in cases where the same phase is called
before and after a transition. In this case, the phase remains in
the RUNNING state, but may be programmed to respond to
this flag, which is set when the phase goes through the
transition. If not selected, user code that occurs on both sides
of a transition does not indicate when the transition occurs.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.3
135
Phase Request Programming
The REQUEST register is the mechanism that interacts with
the Batch Executive machine from the phase logic. By setting
this register to specific values, the phase can cause the DeltaV
Application to acknowledge that the phase needs attention,
and then to service the request.
6.6.3.1
Using the REQUEST Register and Request
Arguments
The sequence that the phase logic needs to follow is listed
below.
1. Prepare for request (set reports, for example).
2. Set any request arguments, if needed.
3. Set the request value.
4. Wait for the request to be zero.
When using the # of Request register from the Flexible
Configuration option, set the number to indicate the maximum
number of request registers needed for any request you may
do from the code. If an insufficient number is used, requests
for which they are required will return invalid results.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
136
Section 6 F Phase Programming
6.6.3.2
Phase Request Codes
Table 6-6 is a reference for programming requests from
phases:
Table 6-6.
Phase Request Programming
Purpose
Request
Download
Parameters:
All phase
parameters
Range of
parameters
Requests the DeltaV Batch Executive to
download phase parameter values.
1000
11nn
nn=size of range,REQDATA1 = ID of 1st
1100
REQDATA=ID of 1st, REQDATA2= size of
range
Single parameter
12xx
xx=ID of parameter
Single parameter,
indirect
1200
REQDATA1=ID of parameter
Range, indirect
Upload Report
Values:
Requests the DeltaV Batch Executive to
upload report values.
All phase report
values
2000
Range of report
values
21nn
nn=size of range, REQDATA1=ID of 1st,
Range, indirect
2100
Single report value
22xx
REQDATA1=ID of 1st, REQDATA2=size of
range
xx=ID of report value
SIngle report value,
indirect
2200
REQDATA1=ID of report value
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
Table 6-6.
137
Phase Request Programming (Continued)
Purpose
Request
Send Message to the
Operator:
Requests controlling display of
preconfigured phase messages at the
phase summary view.
Send message
30nn
nn=ID of message
Send message,
indirect
3000
REQDATA1=ID of message
Clear message
3100
Send Operator
Prompt, Integer
32nn
nn=ID of message
Send Operator
Prompt, Integer
indirect
3200
REQDATA1=ID of message
Send Operator
Prompt, Floating
Point
33nn
nn=ID of message
Send Operator
Prompt, Floating
Point indirect
3300
REQDATA1=ID of message
Send Operator
Prompt, Boolean
34nn
nn=ID of message
Send Operator
Prompt, Boolean
indirect
3400
REQDATA1=ID of message
Send Operator
Prompt, String
35nn
nn=ID of message
Send Operator
Prompt, String
indirect
3500
REQDATA1=ID of message
Acquire Resources:
Requests the DeltaV Batch Executive to
allow the phase to acquire a Recipe
Manager NT resource.
Single resource
40xx
xx=ID of resource
Single, indirect
4000
REQDATA1= ID of resource
Multiple resources
41nn
nn=number of resources,
REQDATA1--argnn=ID of resources
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
138
Section 6 F Phase Programming
Table 6-6.
Phase Request Programming (Continued)
Purpose
Request
Release Resources:
Requests the DeltaV Batch Executive to
release a Recipe Manager NT resource for
a phase.
Single resource
42xx
xx=ID of resource
Single, indirect
4200
REQDATA1= ID of resource
Multiple resources
43nn
nn=number of resources,
REQDATA1--argnn=ID of resources
All resources
4400
Acquire and Hold
Resources:
Requests the DeltaV Batch Executive to
allow the phase to acquire and hold a
resource.
Single resource
45xx
xx=ID of resource
Single, indirect
4500
REQDATA1= ID of resource
Release Held
Resources:
Requests the DeltaV Batch Executive to
release a held resource for a phase.
Single resource
46xx
xx=ID of resource
Single, indirect
4600
REQDATA1= ID of resource
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
Table 6-6.
139
Phase Request Programming (Continued)
Purpose
Request
Messages to other
phases:
Requests the DeltaV Batch Executive to
send a message id and values to linked
phases.
Send message
50nn
nn=ID of message, REQDATA1=# of
receivers, REQDATA2--argnn=message
value
Send message,
indirect
5000
REQDATA1=message ID, REQDATA2=# of
receivers, REQDATA2--argnn=message
value
Send and Wait
51nn
nn=ID of message, REQDATA1=# of
receivers, REQDATA2--argnn=message
value
Send & Wait,
indirect
5100
REQDATA1=message ID, REQDATA2=# of
receivers, REQDATA3--argnn=message
value
Send & Wait for 1
receiver
52nn
nn=message ID,
REQDATA1--argnn=message value
Send & Wait for 1,
indirect
5200
REQDATA1=message ID,
REQDATA2--argnn=message value
Cancel Message:
Requests the DeltaV Batch Executive to
cancel send of a message ID to linked
phases. When canceling all messages, it
cancels pending requests in the phase from
where the requests originated.
Cancel message
53nn
nn=ID of message
Cancel, indirect
5300
REQDATA1=ID of message
Cancel all
messages
5400
Waiting for a
Message:
Requests the DeltaV Batch Executive to
wait for a message ID between linked
phases.
Wait for a message
55nn
nn=message ID,
REQDATA1--argnn=message value
Wait, indirect
5500
REQDATA1=message ID,
REQDATA2--argnn=message value
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
140
Section 6 F Phase Programming
Table 6-6.
Phase Request Programming (Continued)
Purpose
Request
Abort Request:
Abort Request
6000
Requests abort of any outstanding phase
request
request.
Download DeltaV Parameters:
Download
Customer Batch ID
71xx
xx = ID of (string) parameter
Download Unique
Batch ID
72xx
xx = ID of (string) parameter
Download Phase
ID
73xx
xx = ID of (integer) parameter
Abort Batch:
Requests the Batch Executive to ABORT
the batch that this phase is running in.
Caution All other phases that are part of the
same batch will also be aborted.
Abort Batch
8100
Stop Batch:
Note
To cause an ABORT of a batch
that is under External control, write to the
XCOMMAND parameter from another
module.
Requests the Batch Executive to STOP the
batch that this phase is running in.
Caution All other phases that are part of the
same batch will also be stopped.
Stop Batch
Note:
6.6.4
8200
Note
To cause a STOP of a batch that is
under External control, write to the
XCOMMAND parameter from another
module.
REQDATA1, REQDATA2..--argnn above refer to the request argument
locations as configured in the phase screen of PPLICFG
Additional Phase Request Information and Examples
Specific requests may require additional data such as
parameters and arguments. Some examples of these data
items are outlined below.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
6.6.4.1
141
Request Arguments
By default, the DeltaV software allows for five REQDATA
registers, which are the request arguments. The PPLI
configuration software allows the user to connect 0--5 of these.
6.6.4.2
Direct vs. Indirect Requests
Direct requests embed the first request argument (number or
ID) together with the request call, as the last two digits.
Therefore, the number or ID cannot exceed 99.
Indirect requests use an allocated location to contain the
request argument. You can use code to set the value of this
location. You should determine the number based on your
needs in programming phase requests.
Note ... PPLI connects the location of the request
arguments. This connecting occurs in the phase
definition screen when the number of PPLI request
registers is 1 or more.
6.6.4.3
PROVOX Operation Code Example — Downloading
Phase Parameters
Suppose that you need a single parameter download of the
parameter H2O_LEVEL that has ID 2, and has been
connected with PPLICFG to UV[21].
As a direct request, you would set the value of UV[2], the
location for requests, to 1202, as indicated by Table 6-6.
CONST ( UV[2], 1202 )
{ Request download of ID 2 }
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
142
Section 6 F Phase Programming
Alternatively, as an indirect request, you would first set the
value in the first request argument to 2 (assume its
configuration is for UV[6]). Then you would set the value of
UV[2] to 1200.
CONST( UV[6], 2 )
{ Set request arg. to for download of ID 2 }
CONST( UV[2], 1200 )
{ Request download, indirect }
In either case, you would wait for PPLI to set the value in
UV[2] to 0, and then you could find the downloaded
H2O_LEVEL in UV[21].
WAITUNTIL (UV[2]=0, 0 S, NOCWEN)
{ Wait for request to complete }
DBI (UV[21], SP:LIC-100)
{ SP of Level Control set to result }
6.6.4.4
FST Example for Requests
The section of FST code below is an example of a request.
Assume for this example that the vessel temperature is to be
compared with a recipe value that may have been updated by
the operator since the equipment phase started. Here, the
recipe value is a phase parameter (ID 2) connected to
FPREG[19] of the same LCP (COOK-LCP) in PPLICFG.
You should use a DAWT instruction and not the STSV
instruction to write the request code to the request register.
This instruction causes an exception to occur at the LCP point,
so that it is immediately transmitted to CHIP (exception
reporting is recommended).
0014:LDSV (1202)
{Read Recipe Manager NT parameter ID 2}
0015:DAWT (I, IREG[2]:COOK-LCP)
{Send the request; Use DAWT rather than STSV so
that exception reporting is triggered}
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
143
0016:RESUME (LABEL50)
{Resume the next scan at wait}
LABEL 50:
0017:EXPR (B, IREG[2]<>0)
{Check if the Recipe Manager NT system cleared the
request register}
0018:BRA (=, TRUE, END_OF_FST)
{If the request register is not clear, branch to
Label at the end of the FST}
0019:DARD (F, PV:TIC101)
{Load actual temperature}
0020:EXPR (B,SVA > FPREG[19])
{Use the result of the parameter read from the
Recipe Manager NT system to check against the
temperature}
6.6.4.5
Upload Report Values — Journal Entries
The report values combine with the following information, and
then are written as journal entries in the batch journal. (This is
in an nn.evt file in the Journals directory.)
Batch ID
Recipe Name
Process Cell
Time/Data
Unit ID
Area
Phase Name
Engineering Units
Report Description
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
144
Section 6 F Phase Programming
6.6.4.6
Send Messages to Other Phases
Phases that are members of a synchronization group
communicate with each other, defining the role of the
synchronization group. You can use this communication for the
purposes listed in Table 6-7.
Table 6-7.
Phase Communication Purposes
Purpose
Description
Synchronization
Performed to ensure that multiple phases are in
exactly the proper state before they proceed.
Since the phases can execute synchronization
through this messaging function, there is no
additional phase synchronization implementation
in the phase, unit or batch executives.
Permissive
Performed to ensure that one phase of the
synchronization group has passed a certain
point before other phases can proceed.
Data Transfer
Performed to move data from one phase to
another.
Phase Message ID — This message ID uniquely defines the
passed message.
Completion of Messages — A Send Message Wait and a
Receive Message Wait request pair completes only if the
message IDs for each of the calls are identical. This
completion prevents messages from being routed to the
improper request.
Additionally, the Send Message Wait call must specify the
number of messages confirmed as a parameter. This number
of messages allows synchronization groups with more than
two members.
Processing Send and Receive Messages — Upon receiving
the Send Message call, the Batch Executive machine stores
the message into the message queue. Then it actively
responds to outstanding or incoming Receive Message Wait
calls from other phases within the synchronization group.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
145
When the Batch Executive machine receives a Receive
Message Wait call from a phase of the synchronization group,
it checks the message ID and completes the message if
appropriate. Upon completion of the message transfer, the
Batch Executive machine removes the message from the
message queue.
Configuring a Message ID — When the configuration of a
Recipe Manager NT phase class occurs, the configuration of
phase messages for that class also occurs. Each phase
message’s configuration allows for a message ID, an integral
positive value or an operator prompt. Requests to send a
message to another phase refer to the message using the
message ID and the number of phases that will receive the
message.
Phase to Phase Message Example
An example of this type of message would be for a DRAIN
phase from one of two units in a REACTOR unit class to send
a message to a FILL phase from one of two hold tanks. The
message will accomplish two purposes:
J
J
To synchronize the DRAIN and FILL phases
To tell the FILL phase which reactor (indicated by the
equipment ID) is the source.
For more information on phase request programming, see
Table 6-6.
For this example, we will program the DRAIN phase with the
Send Message request (50nn), which has one argument for
the number of message receivers, and one for each message
value. We have one message value (the equipment ID of the
reactor unit), so we will need two request arguments for the
DRAIN phase. Here, allocate UV[8] and UV[9] of the PROVOX
reactor Unit points.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
146
Section 6 F Phase Programming
To receive the message from the DRAIN phase of the reactor,
the FILL phase of the hold tank performs a Wait for a Message
request (55nn), which has one argument for each message
value. Therefore, we need only one argument for the FILL
phase. Here, allocate UV[8] of the hold tank Unit points.
For this example, at the DeltaV Explorer, in select Number of
Tags --> Request from the Edit Equipment Phase Class
screen and enter 2 for the DRAIN phase and 1 for the FILL
phase. Select Transfer Type --> Partners and enter 1 in
phases. In addition, create messages with the same ID in the
DRAIN phase and in the FILL phase. In our example, we use
message ID 4 since 1--3 are already in use as operator
messages in the DRAIN phase.
In PPLICFG, all four equipment phases need to be configured
with the request (though the Copy Template function can be
used to speed the process). For DRAIN_RX1, connect
requests (arguments) REQUEST1 and REQUEST2 to the
PROVOX locations REACTOR1, UV [8] and UV [9]
respectively. (REACTOR1 is the default PROVOX point tag, so
it is only necessary to select or enter UV and the numbers.)
Similarly, connect FILL_HD1, REQUEST1 to HOLDTK1, UV
[8]. Then copy or enter these configuration changes to
DRAIN_RX2 and FILL_HD2.
In the ENVOX configuration, add the following code at the
appropriate location in the reactor DRAIN phase. (UV[2] is the
request register.)
0004:CONST (UV[8], 1)
{Indicate 1 msg receiver}
0005:DBI (UV[9], UV[4])
{Copy Unit ID into parameter}
00006:CONST (UV[2], 5004)
{Send xfer unit message to FILL phase}
00007:WAITUNTIL ((UV[2] = 0), 1 S, CWEN)
{Wait for the Recipe Manager for NT system to
process message}
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Phase Programming F Section 6
147
We add the following code at the appropriate location in the
hold tank FILL phase.
0005:CONST (UV[02], 5504)
{Wait for msg id 4 from partner (DRAIN phase)}
0006:WAITUNTIL ((UV[02] = 0), 1 S, CWEN)
{Wait for request complete}
0007:IF (UV[08] = 101, LABEL12)
{Process according to equipment ID received}
From the Recipe Studio, in each (top level) recipe that invokes
these phases, select Link to bring up the Phase Link Group
screen. To find an empty phase link group, select Next Group.
Then, click on the DRAIN phase in the recipe tree on the left
side of the Recipe Studio screen, select Add on the Phase
Link Group screen, and then select and add the FILL phase.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
148
Section 6 F Phase Programming
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Operation Overview F Section 7
149
Figure 7-Table 7
7
7 Recipe Manager NT Operation
Overview
This section provides an overview of the Recipe Manager NT
and PROVOXr components that enable operation of a batch
process. It also previews the operator tasks done from the
Batch Operator Interface and the PROVOX console, and
gives important descriptions of batch states, commands,
modes, and active step changes.
For more information on all batch operations such as batch
states, batch modes and batch commands, please refer to the
DeltaVt Batch book online.
7.1
The Recipe Manager NT for PROVOX
Operating Environment
The Recipe Manager NT operating environment includes two
main interfaces:
J
J
The Batch Operator Interface— used primarily to manage
recipes
The PROVOX console — used primarily to monitor the
process equipment
Depending on how your plant is set up, you might use these
interfaces on separate screens, or on the same screen.
This environment also contains two main sources of control:
J
The Batch Executive — for recipe control
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
150
Section 7 F Recipe Manager NT Operation Overview
J
The PROVOX Unit Controllers — for the control of
equipment phases
Several other components are included that enable
communications between the Recipe Manager NT Software
and the PROVOX software. These include the PROVOX
Phase Logic Interface (PPLI), Communications Highway
Interface Package NT (CHIP-NT), and Highway Data Link
(HDL). The PPLI and CHIP-NT software each include
run-time interfaces that can be used for diagnostic purposes.
Figure 7-1 illustrates the Recipe Manager for PROVOX
operating environment.
PROVOXR System
Recipe Manager NT
Monitor
and
Operate
Equipment
Monitor
and
Operate
Recipes
PROVOX
Console
Batch
Operator
Interface
Batch
Executive
Control
Recipes
Figure 7-1.
PROVOX
Data
Highway
PPLI
CHIP NT
HDL
Translate
Equipment
Phase
Commands
Maintain
PROVOX
Point Data
on NT
Convert
TCP/IP to
PROVOX
Data
Highway
HDL
Controller
Control
Equipment
Phases
Components of Recipe Manager NT for PROVOX Operation
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Operation Overview F Section 7
7.1.1
151
Overview of the Batch Operator Interface Operations
The Batch Operator Interface provides operators with screens
that allow them to do the following (if appropriate permissions
have been granted):
J
J
J
J
J
J
7.1.2
Create batches from the list of recipes released to
production
Control and monitor recipe-based batches through the
use of START, HOLD, RESTART, STOP, and ABORT
commands
Provide advanced batch control (change the mode of a
batch, bind equipment to a recipe, scale a recipe, or run a
segment of a recipe)
Acquire and release Recipe Manager NT-based batch
resources and monitor resource arbitration
Control and monitor individual equipment phases
Respond to prompts for Recipe Manager NT parameter
input (this depends upon how the equipment phases are
programmed)
J
View event logs of current or past batches
J
Monitor, acknowledge, and clear batch-related alarms
Overview of the PROVOX Console Operations
Batch related tasks that are done from the PROVOX console
(POC, PROVUEr or OWP console) include:
J
J
Viewing equipment graphics and status
Responding to operator attention requests (OARs) from
the phase logic (this depends upon how the equipment
phases are programmed)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
152
Section 7 F Recipe Manager NT Operation Overview
J
J
Running individual equipment phases from MANUAL
mode, when needed, using the discrete control device
(DCD) interface
Acknowledging and responding to PROVOX point alarms
Refer to the appropriate PROVOX console operations manual
for instructions about using your PROVOX console. PROVOX
operation considerations that apply specifically to the Recipe
Manager NT system are summarized in the next subsection
and documented more completely in Section 8, which begins
on page 157.
7.2
Interoperability Within the Recipe Manager NT
Environment
This subsection offers an overview of the interoperability
between the Batch Operator Interface and some other
components of the Recipe Manager NT system.
7.2.1
The Recipe Studio
The Batch Operator Interface uses procedural function charts
(PFCs) built in the Recipe Studio. The PFCs developed in the
Recipe Studio interact with the Batch Operator Interface in
the following manner:
J
J
J
A batch executes based on how the PFC was designed in
the Recipe Studio
The Batch Operator Interface displays the PFC, allowing
the operator to view each step of the batch process
Only recipes marked as released to production in the
recipe’s properties can be executed in the Recipe
Manager NT system
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Operation Overview F Section 7
7.2.2
153
The DeltaV Explorer
Many tasks performed on batches are a direct result of
equipment configuration decisions made earlier in the DeltaV
Explorer. For example:
J
J
7.3
The arbitration and allocation processes in the Batch
Operator Interface are based on how equipment was
defined in the DeltaV Explorer.
The equipment must be bound prior to running a batch
when using class based recipes. The binding occurs in the
Batch Operator Interface.
Interaction Between the Recipe Manager NT
and PROVOX Environments
This subsection offers an overview of the areas of operating
interaction between the Recipe Manager NT and PROVOX
systems. This topic is more completely described in Section 8,
which begins on page 157.
7.3.1
An ISA S88 Operation Approach for PROVOX
Systems
The Recipe Manager NT system uses an ISA S88.01
standard (S88)-based, Windows-oriented approach to recipe
management that is substantially different than that provided
by PROVOX activity points, unit points, or logic control points
(LCPs). You do not use activity points with this approach. The
software does use unit points and LCPs, however, since
Recipe Manager NT equipment phases are written in
PROVOX function sequence table (FST) or unit operation
logic, which require these point types.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
154
7.3.2
Section 7 F Recipe Manager NT Operation Overview
The Control DCD Operating Method
Fisher-Rosemount Systems has implemented a method that
allows operation at the PROVOX console to reflect operation
on the Recipe Manager NT system. This operating method
associates the following two DCD points with each LCP or
unit point used for phase logic:
J
J
The first DCD is the COMMAND DCD; its setpoint reflects
the command that the Recipe Manager NT system sends
to the active equipment phase on that point.
The second DCD is the STATUS DCD (or STATE DCD);
its setpoint reflects the state that the PROVOX phase
logic sends to the Recipe Manager NT system.
The use of DCDs is not required in Recipe Manager NT 2.0 or
later if the Flexible Configuration option is chosen. However, if
this option is chosen, the control engineer must communicate
the conventions that are used.
7.3.3
The Manual Equipment Phase Operation
It is important that all equipment phase logic is completely
tested at the PROVOX console using the COMMAND DCD in
MANUAL mode before it is used to run recipes. Thereafter, it
is best to use the Batch Operator Interface’s Phase Control
screen to run phases manually; this keeps the PROVOX point
in COM mode and allows the Recipe Manager NT resource
arbitration facilities to remain in effect.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Recipe Manager NT Operation Overview F Section 7
7.3.4
155
Failure Notification
Equipment failures detected by the PROVOX system might
cause Recipe Manager NT recipe failures if they interfere with
the operation of active equipment phases. In this case, the
operator is notified of the failure at the Batch Operator
Interface screen by a flashing alarm icon. Clicking on this icon
brings up the Batch Operator Interface’s Alarm Summary
screen, which gives a text message about the cause of the
alarm. Complete diagnosis of the problem, however, typically
requires use of the PROVOX console.
7.3.5
Operator Prompts
Operators can request data by using the Batch Operator
Interface’s operator prompts or through the PROVOX
console’s operator action requests (OARs), depending on the
design of the phase logic.
7.3.6
Resource Allocation
Facilities for equipment allocation and arbitration exist in both
the Recipe Manager NT and PROVOX systems. These
facilities do not interact with each other, though they may
(independently) act in parallel. Normally, the Recipe Manager
NT system takes care of arbitration issues at the unit level.
The Recipe Manager NT software can be configured to
address issues of shared equipment below this level.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
156
Section 7 F Recipe Manager NT Operation Overview
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Using the Software F Section 8
157
Figure 8-Table 8
8
8 Using the Software
This section describes the interaction of the Recipe Manager
NT and PROVOXr systems for batch control, with
descriptions of PROVOX points, manual control of phases,
use of PPLI diagnostics, and warm start considerations.
8.1
PROVOX Point Interaction with Recipe
Manager NT Batch Control
This subsection describes certain characteristics of PROVOX
points used with Recipe Manager NT for phase control. The
topics covered include:
J
J
J
8.1.1
PROVOX point values used for Recipe Manager NT
equipment phases
Recipe Manager NT equipment phase status not related
to PROVOX point status
Failure considerations
PROVOX Point Values Used for Recipe Manager NT
Equipment Phases
Table 8-1 on page 158 lists the PROVOX point values
pre-defined by the Recipe Manager NT system for those
points it uses. The setpoints (SPs) and current values (CVs)
can be viewed from the operator faceplate display. Others are
viewed from the detail display parameter (DDP) display for the
point.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Section 8 F Using the Software
158
Table 8-1.
Name
Recipe Manager NT for the PROVOX System
Equipment Phase Point Values
Unit Point
LCP Point
Purpose
Command
SP of PPLI-CMD DCD
Control operation of Recipe Manager
NT equipment phase
Status
SP of PPLI-STAT DCD
Show state of Recipe Manager NT
equipment phase
Failure
UNITVAR 1
CV 1 (FP REG 1)
Failure code transferred to Recipe
Manager NT from the phase logic
Request
UNITVAR 2
CV 6 (INT REG 2)
Phase request to Recipe Manager
NT to perform function
Phase ID
UNITVAR 3
CV 7 (INT REG 3)
From Recipe Manager NT,
equipment ID of active phase.
Unit
UNITVAR 4
INT REG 28
From Recipe Manager NT,
equipment ID of active unit
Step Index
UNITVAR 5
CV 5 (INT REG 1)
Number set by equipment phase
logic to show the currently running
step
Owner
BOOLEAN 1
CV 9 (BOOL REG 1)
TRUE indicates that Recipe Manager
NT is not owner; external ownership
shown at Recipe Manager NT
(COMMAND DCD or control point not
in COM also have this effect)
Pause
BOOLEAN 2
BOOL REG 30
If implemented, shows a PAUSE
command
Paused
BOOLEAN 3
CV10(BOOL REG 2)
Indicates phase is paused
Single Step
BOOLEAN 4
BOOL REG 31
If implemented, shows that a phase
is to be in SEMI-AUTO mode
(repeated pauses)
Downloaded
BOOLEAN5
BOOL REG 19
Indicates a DOWNLOAD command
is in progress
Note:
May not apply if Flexible Configuration is used.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Using the Software F Section 8
8.1.2
159
Recipe Manager NT Phase Status Not Related to
PROVOX Point Status
The setpoint of the STATUS DCD is the only indicator of
status of the equipment phase at the PROVOX console.
Do not confuse the status of the unit point or logic control
point (LCP) with status of the phase. For example, an LCP
might have an ACTIVE status even though the associated
equipment phase is IDLE. Or, a unit point might have a FAIL
status when the operator requested a HOLD and the phase
status is HELD. This is normal operation.
8.1.3
Failure Considerations
Failures may be detected by the phase logic shell or the
phase logic in the PROVOX controller, or by the PPLI or
Recipe Manager NT software in the PC. In either case, the
Batch Executive machine issues a HOLD command to all
active phases in the batch, if configured to do so in the Hold
Propagation setup.
If errors are detected at the PROVOX controller, the failure
code is written to the failure value (see Table 8-1 on page
158) by the phase logic. If this value is 500 or less, it is a
failure detected by the phase interface shell. If it is less than
256, the value matches the fail code of the function sequence
table (FST) or unit operation.
If this is the case, you should reference the unit definition for
the PROVOX unit point to determine the source of the error. If
it is greater than 500, the value is a failure that has been
encoded into the phase logic.
After clearing the cause of the error, select the batch level in
Recipe Manager NT, and click on the Clear All Failures
button from the Batch Operator Interface screen. Then, you
can restart the batch by selecting the RESTART command.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
160
8.1.4
Section 8 F Using the Software
PPLI Failures
Failures that are detected in the PPLI may have a significant
impact on the ability of the software to correctly control a
phase. The more common failures are listed below, together
with the appropriate action for each. Please review the latest
Technical Support Bulletins for more information concerning
failures.
To display the phase status of any phase in your process,
select the Action --> Show Phase Status command when
these errors are encountered. You may also wish to view the
PPLI.LOG file found in the C:\RMNT2.0 directory (if the
default location has been used). This file is best viewed by
using EXCEL with a tab delimiter selected. When PPLI is
started and when the PPLI.LOG file exceeds 10,000 lines, it
is written to a PPLI_LOG.BAK file. It is recommended that you
try to discover the source of a failure before you execute the
Clear All Failures command.
After recovering from these failures, monitor any active
batches for proper operation. The best procedure may be to
shut down the PPLI operation and the Batch Executive
machine, and then to bring them back up with a warm start.
The error messages below occur due to a point accessed by
PPLI being set to PROVOX MANUAL mode.
PPLI encountered a phase in Manual mode. See PPLI
error list for specific tag.
Phase Command (DCD) Point in Manual mode - must
return to COM before Clearing Failures
Phase Control (Unit or LCP) Point in Manual mode must return to COM before executing command
PPLI error - PROVOX Tag not in COM mode. See PPLI
error list for specific tag
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Using the Software F Section 8
161
While running recipes, you should avoid the PROVOX
MANUAL mode. If this error occurs, change the mode of the
point or points back to COM on the PROVOX console, and
execute the Clear All Failures command on the Batch
Operator Interface. If the points were in the PROVOX
MANUAL mode at the Start call to the phase, you will get a
second error message. Execute the Clear All Failures
command again, and then use the RESTART command to
start the batch or phase.
The error message below is typically the result of attempting
to run a second phase on a PROVOX Unit point or a LCP that
is already active with a first phase. This may be due to a point
in use in the Recipe Manager NT Phase Control screen. Use
the PPLI Show Phase Status command to clarify the cause
of this error.
PPLI error trying to lock a resource. Check
interaction with other recipes.
If it is possible, correct the error in the Phase Control screen,
or if necessary, correct the cause using PROVOX Manual
control. You can then restart the phase.
The following error can be caused in two ways:
J
J
A call made by a phase to the controller has failed.|
The control point from which the data is being read for the
phase has a COM FAIL (9) status, and a timer has
expired. (A normal re--sync of the CHIP and controller
causes a temporary COM FAIL status, but does not
normally cause this failure.)
PPLI error doing a remote CHIP call. Check PROVOX
highway integrity.
For this failure, correct the communications problems. (The
CHIP_UTIL --> 2 - SMRY --> C utility can be used to ensure
that the CHIP database is being updated.)
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
162
Section 8 F Using the Software
The following error may indicate a very serious CHIP problem.
If there is a CHIP problem, shut down the PPLI and the Batch
Executive machine, and then restart both using the normal
warm start procedures after the problem has been corrected.
PPLI error accessing Chip database. Please check
CHIP status.
Use CHIP_UTIL --> 5 - CHIPTASKS to check the status of
CHIP. MSRTR, FUNNEL, RECVR, XMITR, and TIMER must
all be present. (LOADER and DWNRCV are normally present
as well.)
The following error may be caused at anytime by a phase not
returning to the Idle state so that the phases are not reset to
Idle.
PPLI detected phase not idle at start. See PPLI
error list for specific tag.
For this error there are two possible workarounds:
J
J
Use the Recipe Manager NT Active Step Change to
change the active steps of the recipe. Then, from the
Phase Control screen move the phase to an Idle state and
change back to the original phase using the Active Step
Change utility.
Use the PROVOX MANUAL mode to move the phase to
Idle.
The following messages are secondary messages whose
purpose is to provide information about the status of the
phase logic to be run.
Phase was not started; will proceed with RUNNING
logic on a restart.
Phase was not started, therefore Abort/Stop logic
will not be run.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Using the Software F Section 8
163
The following messages are not likely to occur except during
a warm start after the PPLI and the Batch Executive machine
have been shut down.
PROVOX Point PhaseID = 0, indicating PROVOX manual
Start. Verify Phase before restart.
Phase ID at PROVOX point has been altered. Verify
Process before restart.
If you have advanced manually to a different phase in the
intervening time, the Recipe Manager NT software and your
process may be at different points. You may need to wait for
the phases to reach a terminal state, and then perform an
Active Step Change in order to ensure the proper running of
the batch.
8.2
Manual Control from the PROVOX Console
Manual control of phases may be done from the Batch
Operator Interface’s Phase Control screen or from the
PROVOX console’s point interface.
Under normal operating conditions, it is best to use the Batch
Operator interface’s Phase Control screen to manually control
equipment phases. From the Batch Operator Interface, all
phase operations are done from a single interface.
Engineers developing phase logic should use manual control
from the PROVOX console to do their initial testing of phase
logic to avoid the possibility of multiple sources of error.
An operator may also need to use manual control from the
PROVOX console if control from the Recipe Manager NT
computer is lost; so it is important to understand this interface.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
164
8.2.1
Section 8 F Using the Software
Equipment Phases Based on Unit Operations
To run equipment phases based on unit operations, you
should have tune privilege (unless your phases have been
specifically designed for the operator to change modes). You
may need to set certain DDP registers that the phase
requires; this should be included in the operating procedure, if
needed.
Next, start the PROVOX unit operation/phase using the
PROVOX unit point interface. This is the only command you
should use at the unit point. All others should be run using the
Control DCD. The phase might request data by way of
operator attention requests (OARs) at the PROVOX console.
After the phase is started, use the HOLD, RESTART, ABORT,
STOP, and RESET setpoints of the Control DCD to control the
phase. If you are testing the phase logic, verify that the
STATUS DCD responds according to the state transition
diagram. Check each path of the state transition diagram.
Anytime an equipment phase is in a terminal state (Stopped,
Aborted, or Complete), you must issue a RESET command to
return it to Idle.
Thus, for a normal, uninterrupted equipment phase, you start
the phase with the PROVOX unit point and reset it with the
PROVOX DCD point.
8.2.2
Equipment Phases Based on LCP FSTs
To run equipment phases based on LCP FSTs, you should
have tune privilege. First, you might need to set certain DDP
registers that the phase requires; this should be included in
the operating procedure, if needed. Also, if you have more
than one phase for the LCP FST, you must set IREG[3] to be
the appropriate Phase ID (which is available at the Recipe
Manager NT equipment phase configuration).
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Using the Software F Section 8
165
It is possible to leave the FST in ACTIVE mode continuously,
using only the COMMAND DCD and STATUS DCD for
control. If the FST is not running, start the FST from the LCP
faceplate. When the COMMAND DCD setpoint is set to
START, the phase will start.
Again, anytime an equipment phase is in a terminal state
(Stopped, Aborted, or Complete), you must issue a RESET
command to return it to Idle.
8.3
Using the PPLI Diagnostics Screen
The PROVOX Phase Logic Interface (PPLI) run time
executable includes facilities that display performance
statistics, an error log, and phase status.
The error log is also available from the file PPLI.LOG in the
FRSI\RMNT\PPLI\bin directory.
The Phase Summary screen shows PPLI status, PROVOX
status, the PROVOX tag, the PPLI processing status, and the
phase name. The PROVOX status is reported by the STATUS
DCD, while the PPLI status is reported to the Recipe Manager
NT system. In certain cases, these statuses might be
different, such as during an automatic parameter download.
The Phase Summary screen is helpful for identifying the
PROVOX point to which each phase is connected.
8.4
Warm Start Considerations
A warm start might be performed after a brief shutdown of the
Recipe Manager NT computer because of a power failure or
some other cause. If this happens, you can expect a
reasonably seamless re-start — provided you have not
performed manual phase intervention at the PROVOX
console and there are no additional failures.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
166
Section 8 F Using the Software
Assuming the controller was not affected, all equipment
phases in the PROVOX system should either have
completed, or should be HELD after the PPLI and Batch
Executive machine are restarted. Issuing a RESTART
command at the batch level from the Batch Operator Interface
will then restart the batch.
If you found it necessary to perform manual phase control at
the PROVOX console, use caution when you attempt to
re-establish the Recipe Manager NT connection for automatic
batch control. In this case, the actual active phases might
differ from those active at the time when Recipe Manager NT
control was lost.
The active step change function of the Recipe Manager NT
software can be used to align the proper phases for
re-establishment of automatic control. If this is of concern,
make sure you are thoroughly familiar with the active step
change function (by working with simulations, for example)
before attempting to use it in a plant situation.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Installation Considerations F Appendix A
167
Figure A-Table A
Appendix A
A
Installation Considerations
This section is included for the user who desires to install the
FRSI PROVOXr Operator Console (POC), the DeltaVt
Batch Operator Interface (BOI), and RMNT applications on
the same Application Station computer. FRSI Technology has
successfully tested specific versions of these applications
under various conditions on workstations. Installation of
BOI/POC software on Server platforms is not supported.
The following sections describe the procedures required to
implement a separate and an integrated configuration.
Separate configurations have the POC and BOI software
applications installed on a different Application Station than
the machine which has the Batch Executive, while an
Integrated configuration has the POC Client, the BOI, and the
Batch Executive applications on the same DeltaV Application
Station computer. The configurations are illustrated in
Figure 3--1.
While the documentation provides an overview of installing
the Batch Executive, RMNT, BOI, and POC applications on
the same Application Station, it is strongly recommended that
the POC/BOI applications be installed on a single application
station with the Batch Executive being installed on another.
Loading issues may cause unforeseen problems that were
not present during the initial testing of the applications.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
168
A.1
Appendix A F Installation Considerations
Installing the POC/BOI Applications on
one Application Station with the Batch
Executive on a Separate Application
Station
In this configuration, the applications can simply be installed
according to the installation directions provided with the
applications.
A.1.1
Installing BOI/POC on the Application Station
1. Install DeltaV (4.2) according to the DeltaV installation
guidelines.
(This installs the BOI application)
2. Install POC (3.0) according to the POC installation
guidelines
A.1.2
Installing the Batch Executive/RMNT Application on
a Separate Application Station
1. Install DeltaV (4.2) according to the DeltaV installation
guidelines.
2. Install RMNT (2.1) according to the RMNT installation
guidelines.
3. Install CHIP (5.0) according to the CHIP installation
guidelines.
4. Install PAS (1.1) according to the PAS installation
guidelines.
5. Install OPC Mirror Lite (3.2) according to the installation
guidelines
6. Install BOI client application
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Installation Considerations F Appendix A
169
7. Make sure the appropriate DeltaV/FRSI software licenses
are loaded.
A.2
Installing POC/BOI and the Batch
Executive/RMNT on the Same
Computer
In this configuration, the POC and BOI client applications as
well as the Batch Executive are loaded/installed on the same
DeltaV Application Station (refer to Figure 3.1). The user
should be careful to install the applications following the listed
order.
Installing Batch Executive/BOI/POC on the Application
Station:
1. Install DeltaV (4.2) according to the DeltaV installation
guidelines.
2. Install RMNT (2.1) according to the RMNT installation
guidelines.
3. Install CHIP (5.0) according to the CHIP installation
guidelines.
4. Install PAS (1.1) according to the PAS installation
guidelines.
5. Install OPC Mirror Lite (3.2) according to the installation
guidelines
6. Install BOI client application
7. Install POC client application according to the POC
installation guidelines.
8. Make sure the appropriate DeltaV/FRSI software licenses
are loaded.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
170
Appendix A F Installation Considerations
The POC/BOI applications were successfully tested on
machines which were representative of the current DeltaV
hardware configurations provided with DeltaV. The specific
hardware tested follows:
PC platform: Dell Precision 410
CPU:
Pentium III - 500 MHz
Memory:
256 MB SDRAM
Video card:
Appian Jeronimo Pro2, dual monitor;
8 MB memory size
NICs:
Three 3Com 3C905b-TX Fast Etherlink
XL cards (one on motherboard)
Mouse:
Logitech wheel mouse (MS compatible)
Monitors:
Two ViewSonic P810 21” monitors used for
dual-head configuration
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Migration Considerations F Appendix B
171
Figure A-Table A
Appendix B
B
Migration Considerations
This section provides an overview of issues involved for
customers who currently create batches/recipes using
PROVOXr Activity Points, or who are upgrading from RMNT
(1.0).
B.1
Upgrading from RMNT 1.0 TO RMNT
2.1
The close coupling of RMNT (2.1) with DeltaVt requires that
RMNT be looked at as a new product as opposed to being
viewed as a traditional upgrade to RMNT (1.0). As such, users
upgrading from a 1.0 environment cannot simply copy a few
files and continue to run their recipes. The requisite process to
go from 1.0 to 2.1 is not difficult, but it does have to be
approached with care. The following steps should assist in
making this process easier and reduce problems associated
with converting to 2.1.
Warning ... Prior to proceeding with the following steps, the user
should be familiar with the DeltaV Batch environment
and should have thoroughly read the RMNT
documentation pertaining to “Phase Programming”.
1. PROVOX configuration
You do not need to change your RMNT 1.0 PROVOX
configuration in any major way to work with RMNT 2.1.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
172
Appendix B F Migration Considerations
The following are issues that you require you to make
changes.
Check for Failure Codes larger than 755
Failure Codes are handled differently in 2.1 than 1.0.
Within 1.0 user--defined failure code indexes could be any
number between 501 and 32,767, and the RMNT Failure
enumeration was configured accordingly. RMNT (2.1 and
greater) permits you to use the indexes between 501 and
755 in your PROVOX code. The RMNT 2.1 software maps
these indexes to the DeltaV “phase_failures” named set
values between 1 and 255. Refer to Section 8.1.3 and the
DeltaV Online Books for a more thorough description of
this topic.
2. Entering the DeltaV Configuration Information (Area Model
and Recipes)
The design of the Area Model and Recipes created in 1.0
are valid for 2.1. However, as the software tools are
different and there is no automatic import utility for the
migration process, the configuration information must be
manually re--entered into the DeltaV Explorer and Recipe
Studio.
From the DeltaV Explorer, the Area Model (Process Cells,
Units, and phases) must be recreated. Where possible, the
same names from the 1.0 configuration should be
maintained. To assure that the names displayed/used in
the PPLICFG (2.1) are the same as (1.0), the external
phases in the Explorer should have the same name as the
phases used in 1.0.
Recipe Studio entry of recipes is very similar to the entry of
recipes in the RMNT P1.0 recipe editor. The process for
deferring parameters to higher Recipe levels is different,
but more straightforward. Recipe formulas (grades) are
available so that you no longer need multiple recipes
where different sets of values are used in the same recipe.
3. Entering the PPLI Configuration Information
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Migration Considerations F Appendix B
173
PPLI configuration is very much the same as it was in
RMNT 1.0. If your DeltaV area model configuration
successfully matches your previous RMNT 1.0 area model,
you should be able to re--enter the configuration from a
print of your RMNT 1.0 PPLICFG configuration.
One exception you will note is the configuration of Unit
Tags. These are no longer configured in PPLICFG, but are
sent to the Batch Executive by way of OPC and DeltaV
module attributes. Refer to section titled Parameter
Reference Configuration for information about
configuration of Unit Tags.
You will notice a check box for Flexible Configuration on
the PROVOX Point Type dialog. You should not check this
box to copy an RMNT P1 configuration. You will also notice
several check boxes on the Edit PROVOX Point dialog.
These checkboxes should be left unchecked unless you
wish to use the features (note that the BATCH ID feature
does not require any phase code changes; just a CHIP
ASCII point). The # of Request registers box should match
the number of tags for requests configured in the RMNT
1.0 equipment editor Edit Equipment Phase Class dialog.
DeltaV sets the number at 5; if not used, you do not have
to provide connections.
B.2
Upgrading from Activity Points to
RMNT 2.1
The following are the range of options available to those
customers who wish to migrate from use of Activity points to
use of RMNT.
Standard RMNT Configuration Option: If you currently have a
control strategy that is not modular and cannot take advantage
of the modular design benefits offered by the S88 approach,
you may wish to thoroughly re--design your code, including
re--allocation of registers, and fully use the capabilities
provided by RMNT. In this case, you would use the RMNT
shell as--is and not choose flexible configuration.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
174
Appendix B F Migration Considerations
Flexible RMNT Configuration Option: If most of your control
code is appropriate for S88--style control, you may wish to add
a shell or wrapper for your code to work with phase control
command logic, while leaving large portions unchanged. In this
case, you would use the Flexible Configuration Option so that
you would not have to alter current usage of UVs or BVs. You
should thoroughly understand the operation of the operation
x--pplioper provided with RMNT and alter it or re--design it to
meet your needs. You will need to provide logic so that
RUNNING, HOLDING, STOPPING, ABORTING, and
RESTARTING logic transitions match the State Transition
Diagram which is in the User Manual for RMNT, or is available
online by opening the DeltaV control studio for a New Phase
Class Object type. The diagram shows each State that must
result from each Command when received from the Batch
Executive. You must accommodate some Unit Point, LCP, or
DCD locations for the Command and Status codes. At a
minimum, you should also accommodate a failure register.
Review documentation for all other registers and plan to
thoroughly test your phase design before fully implementing
your solution. You should be able to run phases manually from
the PROVOX software, from the phase control screen of the
Batch Operator interface and also from recipes.
FST Executive Option: If you wish to maintain your current
PROVOX operations as is and use RMNT recipes to execute
them, it is possible to use LCP FSTs as RMNT phases to drive
the PROVOX operations. Keep in mind that the behavior in
this case will not match that of PROVOX Activities: in some
ways, there is more flexibility; however, the Batch Operator
Interface is set up to run according to the State Transition
Diagram, which must be followed by the executive FST. Since
you have control of the FST logic, you have much latitude in
determining behavior. Be sure to allow adequate time for
preliminary development and testing. (Note: if the logic desired
is straightforward and you have limited controller space
available for FSTs, you may wish to consider obtaining an ISR
quote for addition of the executive logic to the PPLI – if
accepted, it would be added to standard product.)
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Glossary
175
Glossary
Abort
This Recipe Manager NT command invokes the aborting logic for applicable
phases of a batch, to reach the aborted state. The operator cannot restart a
batch after an abort command. Abort is an emergency stop.
Aborted
This Recipe Manager NT state indicates that an emergency shutdown has
completed.
Aborting
This Recipe Manager NT state indicates that an emergency shutdown is in
progress.
Active Step Change
This Recipe Manager NT command allows change between steps of a recipe.
This command does not forward to PPLI.
Allocation
A form of coordination control that assigns a resource to a batch or unit. An
allocation can be for the entire resource or for portions of a resource.
And Structure
The logic for parallel processing. Use this sequence selection when you need
two or more steps to run in parallel.
Application Feature
Application functions protected by security; for example, releasing a recipe to
production.
Arbitration
The negotiation of equipment allocation when the equipment is requested by
more than one batch or by the operator.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
176
Glossary
Archiver
A Recipe Manager NT application that manages batch journal files. The archiver
moves the journal files to a storage location and deletes them after a specified
time.
Area
A physical, geographical, or logical grouping of equipment. In a Recipe Manager
NT application, an area contains process cells, units, and equipment phases.
Area Model
A database that contains the definitions of the process cells, units, and
equipment phases that represent a physical, geographical, or logical grouping of
equipment used to build and execute recipes. Typically, an area model contains
all of the equipment in the plant.
Array
A list of variables. You define parameter arrays for phases in the process
controller. Phase parameter arrays store phase parameter values. A phase
parameter array contains a number of elements, which are referenced using an
array index. Each element in a phase parameter array can store one phase
parameter value.
Auto
This Recipe Manager NT command enables automatic execution of a batch at
the Recipe Manager NT procedure, Recipe Manager NT unit procedure, or
Recipe Manager NT operation level. This command does not forward to PPLI.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
177
Batch
A specific quantity of a given product, produced in a single complete processing
procedure.
The material that is being produced or that has been produced by a single
execution of a batch process.
An entity that represents the production of a material at any point in the process.
Note ... Batch means both the material made by and during
the process and also an entity that represents the
production of that material. Batch is used as an
abstract contraction of the words “production of a
batch.”
Batch Operator Interface
A graphical Recipe Manager NT application used by the operator to monitor and
control batches.
Batch ID
A name given by the operator to each batch that is typically unique.
Batch Journal
A file produced by the Batch Executive for each batch and accessed by the
Batch Operator Interface and DeltaVt Batch History View applications. These
reports detail information such as status information about each batch; recipe
header information; changes in the state of recipe steps, values, ownership, and
mode; requests for changes of state; operator information; and informational
messages about phase logic requests and responses.
Batch Process
A process that leads to the production of finite quantities of material by
subjecting quantities of input materials to an ordered set of processing activities
over a finite period of time using one or more pieces of equipment.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
178
Glossary
Batch Report
The report printed at the completion of a batch that includes the recipe name,
batch ID, the activity point and procedure that ran the batch, expected and actual
values of grade parameters, and alarm and change-of-state messages.
Browser
A navigational tool for locating objects. The objects appear in a hierarchical
display of folders.
Class-based Recipe
A recipe that defines equipment in terms of a unit class and not specific unit
instances. This feature allows the recipe to run on any unit in the class.
Clear All Failures
This Recipe Manager NT command sets the FAILURE register of the Unit or
LCP to zero.
Common Resource
A resource that provides services to more than one requester. In a Recipe
Manager NT application, common resources are control modules such as
pumps, motors, or valves, that are shared between phases or units.
Complete
This Recipe Manager NT state indicates that a normal operation sequence is
complete. A variable that represents a process value such as mixing time,
temperature, or ingredient.
Constant Value Parameter
A phase or step parameter that defines a single numeric or string value.
Control Module
The lowest level grouping of equipment in the physical model that can carry out
basic control. Control modules consist of sensors and other control modules that
together perform a specific task. Control modules perform regulatory or state
control over their constituent parts.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
179
Control Recipe
Defines the manufacturing environment for a single batch and includes the
specific equipment and raw materials to be used. Control recipes are devised
from master recipes.
Create ID
The unique identification number assigned to each batch by the Recipe Manager
NT application.
Deferred Parameter
Defines a value that is passed to another recipe. By deferring a parameter, you
instruct a recipe to retrieve the phase parameter’s value from a formula and not
from the equipment database.
DeltaV Batch Executive
An application on the DeltaV system that coordinates the function of your
recipes, the defined equipment, and each Batch Operator Interface station during
production.
DeltaV Batch Operator Interface
A DeltaV application that the batch operator uses to monitor and control batches.
Device
A single, physical piece of plant equipment that has an active function in the
process. Examples: valves and pumps.
DOCVUEt
t Electronic Documentation
A mark of Fisher-Rosemount Systems for the electronic documentation library,
which is available on CD-ROM.
Dwell Time
The length of time a phase maintains a specific state.
Enterprise
An organization that coordinates the operation of one or more sites.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
180
Glossary
Enumeration (named set)
A list of strings that can be referenced by their ordinal offset in a list. Example:
Sunday=0, Monday=, Tuesday=2.
ENVOXr Software
A Fisher-Rosemount Systems’ line of configuration products for PROVOXr
systems. The use of a third-party relational database is the principle
distinguishing feature of configuration with ENVOX software.
Equipment Database
The database that contains definitions of the process cells, units, and equipment
phases that represent a physical, geographical, or logical grouping of equipment
used to build and execute recipes.
Equipment Entity
A collection of physical processing and control equipment and equipment control
grouped together to perform a certain control function or set of control functions.
Equipment ID
A unique ID that is assigned to all equipment configured in DeltaV Explorer. This
ID is used by the phase logic to acquire and release resources.
Equipment Module
Consists of equipment and control modules that together perform a minor
processing task (a phase). In a Recipe Manager NT application, phases are
directly tied to the equipment modules on which they execute.
Equipment Phase
A phase that is part of the equipment control. The logic for an equipment phase
resides in the process controller. In the DeltaV system, a unit phase is equivalent
to a PROVOX equipment phase.
Error Log
A list of errors that occurred during the production of a batch. In addition to being
written to the log file, severe errors and warnings are sent as alarms to the
Recipe Manager NT Client screen.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
181
Executive/log File
During operation, the Batch Executive maintains a historical record of the
commands it received and the operations performed. The Recipe Manager
stores this record in a log file called DVBEXECUTIVE.LOG. This file resides in
the DvData\Batch\Logs directory.
Exclusive-use Resource
Resources that only one user can use at a time.
External Phase
In DeltaV Batch, an external phase is used for equipment logic external to
DeltaV. The parameters and messages are configured in the DeltaV library
phase class. Each external phase tied to PROVOX is a PROVOX equipment
phase.
Failure ID
The ordinal associated with a string in the PHASE_FAILURES enumeration set.
Formula
A variable that represents a process value such as mixing time, temperature, or
ingredient.
A category of recipe information that includes process input, process parameter,
and process output data. A formula defines variables to produce a variation of
the product. One recipe can have multiple formulas and produce multiple
variations of the product.
Formula Parameter
A formula associated with a step in a recipe. The step represents another recipe
that defines the formula.
Group Account
Defines common application features shared by two or more people.
HDL
Highway Data Link; a PROVOX device that allows CHIP and OWP to
communicate to the data highway through a TCP/IP protocol ethernet
connection.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
182
Glossary
Header
Information about the purpose, source, and version of the recipe, such as recipe
and product identification, creator, and issue date.
Held
This Recipe Manager NT state indicates that a temporary stop operation
sequence has completed, and that the system is ready for a restart.
Hold
This Recipe Manager NT command is usable for a batch in a running or
restarting state. It invokes the holding logic for applicable phases of a batch to
temporarily stop operation of a batch, and reach the held state. This written logic
should put the batch in a safe state, from which the restart command is usable.
Holding
This Recipe Manager NT state indicates that a temporary stop operation
sequence is in progress.
Hold Propagation
This propagation controls how the Batch Executive responds when a phase logic
module goes to HELD or when a failure occurs. The Batch Executive can either
ignore the hold command (no hold propagation) or hold the batch at the batch
procedure level, the unit procedure level, the operation level, or the phase level.
ID
A unique identifier for batches, lots, operators, technicians, and raw materials.
Idle
This Recipe Manager NT state indicates that there are no operation sequences
in progress, and that the system is ready for a start command.
Input Parameter
An input category associated with a phase class. Input parameters are used to
transfer recipe data from the Batch Executive to the phase logic module.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
183
Line
A collection of one or more units and associated lower level equipment groupings
that has the ability to be used to make a batch of material.
Logical Data Model
The table structures and rules that represent the storage of Recipe Manager NT
recipes in a relational database.
Loop
1. Defines the logic to repeat a series of steps multiple times.
2. A control loop.
Manual
This Recipe Manager NT command disables automatic execution of a batch at
the Recipe Manager NT procedure, Recipe Manager NT unit procedure, or
Recipe Manager NT operation level. This command does not forward to PPLI.
MANUAL Mode
1. A loop control mode: the operator directly sets the output of a control loop.
2. A state associated with a step in a batch. When a step is in MANUAL mode,
its transition does not execute until an operator sends a message instructing it to
do so.
Master Recipe
A recipe that defines the equipment requirements to manufacture a product. This
equipment is grouped into process cells. Control engineers design master
recipes to run on many different lines within a process cell.
Maximum Owner
Identifies the maximum number of owners that can simultaneously own an
equipment module. It is used to arbitrate resources and is typically set to one to
allow only one owner at a time.
Mode
The manner in which the transition of sequential functions are carried out within
equipment entities manually or by other types of control.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
184
Glossary
Named Set
See Enumeration.
O-AUTO Mode
A state associated with a step in a batch. When a step is in O-AUTO mode, its
transition executes and an operator can send commands to its procedure.
OLE for Process Control (OPC)
Defines standard objects, methods, and properties for meeting interoperability
requirements of real-time process automation applications. In Recipe Manager
NT 2.0 and later, the Batch Executive communicates with the Batch Server
through OPC.
OLE Object
A document, graphic, or other component from an application that supports
object linking and embedding (OLE); for example, a Word document or Excel
spreadsheet. These OLE objects are created in one application and can be
embedded into another application. In a Recipe Manager NT application, OLE
objects can be embedded into a project where they can be opened and edited.
OPC
Acronym for OLE for Process Control. OPC defines standard objects, methods,
and properties for meeting interoperability requirements of real-time process
automation applications.
OPC Item
A named data structure accessed through OLE for process control (OPC).
OPC Server
An application that makes its data available to other applications using OLE for
process control (OPC).
Operation
An independent production activity within a procedure, consisting of phase
names and the algorithm necessary for the initiation, organization, and control of
those phase names. An operation can consist of one or more phases that might
execute sequentially or concurrently.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
185
Operator Message
Identifies a string that is sent to the operator when the phase executes. The
message ID must correspond with the ID used by the phase logic.
Operator Parameter
A phase parameter that prompts the operator for a value.
Ordinal
A number used by the phase logic to represent an enumeration.
Or Structure
A Boolean operation that determines if one of two or more conditions are true.
Parallel Production
When two or more steps must be complete before the next step can execute.
Parameter Class
Defines common properties for a class of parameters. Used to create
class-based recipes.
Path
1. The lowest level of procedural element in the procedural control model. It
provides an interface to basic control.
2. A series of steps that cause one or more equipment or process oriented
actions. These actions issue commands to set or change controller constants,
modes, or algorithm, for example, heat or drain.
Pause
This Recipe Manager NT command accessed from the Phase Control screen
indicates that the pause bit has been set, enabling logic with a stepwise pause
functionality to stop at programmed pause locations and wait for the resume
command.
P-AUTO Mode
A state associated with a step in a batch. When a step is in P-AUTO mode, its
transition executes, but an operator cannot send commands to its procedure.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
186
Glossary
Phase
1. The lowest level of procedural element in the procedural control model. It
provides an interface to basic control.
2. A series of steps that cause one or more equipment or process oriented
actions. These actions issue commands to set or change controller constants,
modes, or algorithm, for example, heat or drain.
Phase Class
Defines common properties for a class of phases and phase logic modules.
Phase Link Group
A list of phases within a recipe that communicate with each other.
Phase Logic
Automates the equipment in a plant. Contains the instructions to sequence the
individual equipment connected to the physical devices. It is the code that
contains the control steps; for example, open a valve, start a pump, or
stop a totalizer.
Phase Memory Variable
A named storage space that exists in the process controller’s memory to store
the values for 5 unique data items that the Recipe Manager NT Server and the
phase use to communicate.
Phase Message
Identifies a string that is sent to the operator by the phase. The phase message
is configured at the phase class. All phases derived from that class will inherit the
phase message. The message ID must correspond with the ID used by the
phase logic.
Phase Parameter
An input or report category associated with a phase class. Input parameters are
used to transfer recipe data from the Batch Executive to the phase logic module.
Report parameters are used to transfer data from the phase logic module the
Batch Executive for inclusion in the batch journal.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
187
Phase Parameter Array
Resides in the process controller and contains a number of elements that are
referenced using an array index. Each element of a phase parameter array can
contain one phase parameter value.
Phase Partner
Phases that communicate with other phases from the same phase class are
considered phase partners. The phase class must have a number of phase
partners greater than 1 to enable this feature. The PROVOX phase logic
interface (PPLI) allows phases to send messages to other phases.
Phase Report
Reports that detail actual process values or batch values used by the equipment
phase. This information is uploaded from the phase logic in the process
controller to the Recipe Manager NT Server after the phase completes.
POC (PROVOX Operator Console)
This PROVOX console runs on an NT system and may be used with the Recipe
Manager NT Batch Operator Interface.
PPLI (PROVOX Phase Logic Interface)
The interface between the Recipe Manager NT Server and phases in the
PROVOX controller. The interface consists of the PPLI program on the PC, plus
the PPLI shell configuration.
PPLI Equipment Phase Connecting
PPLI information and operation that connects a Recipe Manager NT equipment
phase to PROVOX phase logic for a PROVOX control point.
PPLI Unit Parameter Connecting
PPLI information and operation that connects a Recipe Manager NT unit
parameter to a PROVOX point attribute.
Primary Journal
A list of the events that took place during the production of a batch. The primary
journal is located at the path where the Server first tries to write the file. If the
primary path is unavailable, the Server writes the journal to the secondary path.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
188
Glossary
Procedure
Defines a process strategy for making a batch. Procedures consist of unit
procedures defined for a recipe.
Procedural Control
Control that directs equipment-oriented actions to take place in an ordered
sequence that can carry out some process oriented task.
Procedural Element
A building block for procedural control, and defined by the procedure modal.
Procedural Function Chart (PFC)
A diagram that defines the algorithm for an operation, unit procedure or
procedure. The PFC uses steps, transitions and termination.
Process
A sequence of chemical, physical, or biological activities for the conversion,
transport, or storage of material or energy.
Process Cell
A logical grouping of equipment that includes the equipment required for
production of one or more batches. It defines the span of logical control of one
set of process equipment within an area.
Process Cell with Fixed Path
A process cell in a network environment for which the path cannot be altered by
an operator.
Process Cell with Variable Path
A process cell in a network environment for which the path is chosen by an
operator at batch runtime.
Process Control
The control activity that includes the control functions needed to provide
sequential, regulatory, and discrete control and to gather and display data.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
189
Process Stage
A part of a process that usually operates independently from other process
stages and that usually results in a planned sequence of chemical or physical
changes in the material being processed.
Production Report
A report generated at the conclusion of a batch that details events that happened
while the batch was running.
Project
The entire set of elements needed to deliver a batch solution. These elements
include the recipes, pictures, configuration files, and equipment database.
PROVOX FST (Function Sequence Table)
A PROVOX scanned logic sequence used with an LCP point (for general control
functions).
PROVOX LCP (Logic Control Point)
A PROVOX point type that maintains parameter registers for a PROVOX FST,
and defines operator interface for PROVOX FST control.
PROVOX Operation
PROVOX stepwise logic sequence used with a Unit point (typically for unit
control).
PROVOX Phase
The named step (set of command statements) of a PROVOX operation; may be
run from a PROVOX console or from external supervisory control through a
PROVOX operate command.
PROVOX Phase Logic Interface (PPLI)
The interface between the Recipe Manager NT Server and the phase logic. The
PPLI is the Recipe Manager NT-specific portion of the phase and contains the
state transition PPLI logic. It resides in the controller.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
190
Glossary
PROVOX Point
A logical entity in the PROVOX system that defines a grouping of configuration,
operational, and tuning information for an equipment entity of a plant.
PROVOX Point Attribute
A single, accessible data item or information value of a PROVOX point.
PROVOXr
r Process Control Products
The Fisher-Rosemount Systems’ line of process control products used in
PROVOX process measurement systems. It is a distributed control and data
acquisition system that communicates over a data highway.
PROVOX Unit Point
PROVOX point type that defines the collection of PROVOX points controlled by
a PROVOX operation, and the operator interface for PROVOX operation control.
PROVUEr
r Console
One of Fisher-Rosemount Systems’ lines of console products for PROVOX
systems that uses global database configuration and has high-resolution
graphics, ergonomically designed keyboards, and color printers.
Quiescent State
A state in which the phase is not executing process control instructions, but is
waiting for a new command from the Recipe Manager NT system.
Recipe
A set of grade parameters and process statements that communicate to a batch
control system how to process raw materials to make a particular product. A
recipe has four main components: the header, the formula (or grade
parameters), the procedure (or sequence), and the equipment list.
Recipe Author
The individual responsible for creating a recipe.
Recipe Directory
A list of the recipes in the current project.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
191
Recipe Formula
Variables used to control process values such as time, temperature, and
quantities. Recipe formulas are beneficial because they let you create flexible
and reusable recipes.
Recipe Header
Administrative information about the recipe. This information includes the
procedure identifier, version number, version date, and author.
Recipe Hierarchy
The S88.0 procedural model that defines procedures, unit procedures and
operations in a hierarchy of recipes. The recipe editor conforms to this model.
Recipe Management
The process of creating, maintaining and, if necessary, deleting recipes.
The control activity that includes the control functions needed to create, store,
and maintain general, site, and master recipes.
Recipe Manager NT Batch Record
The record of or current set of values and events that result from starting a
Recipe Manager NT recipe for a Recipe Manager NT unit.
Recipe Manager NT Commands
Commands that the operator may enter at the Recipe Manager NT client
interface.
Recipe Manager NT Equipment Phase
Recipe Manager NT phase logic for an equipment module.
Recipe Manager NT for the PROVOX System
A software product that combines the Recipe Manager NT system and the
PROVOX Phase Logic Interface (PPLI) which interacts with the PROVOX
system through the PROVOX CHIP NT product.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
192
Glossary
Recipe Manager NT Phase
The lowest level of a Recipe Manager NT recipe that is accessible to the Recipe
Manager NT system; used in Recipe Manager NT operations, and connected to
phase logic from a source external to the Recipe Manager NT system.
Recipe Manager NT Procedure
Implemented as an SFC of Recipe Manager NT unit procedures, the highest
level of a Recipe Manager NT recipe.
Recipe Manager NT Recipe
A multilevel SFC, which determines the sequence of execution of Recipe
Manager NT phases or equipment phases, together with associated parameter
values.
Recipe Manager NT Unit
A collection defined in the Recipe Manager NT system establishing the set of
valid Recipe Manager NT equipment phases for an equipment entity.
Recipe Manager NT Unit Class
An abstraction of a unit in the Recipe Manager NT system that may be a type of
unit, such as a reactor derived from specific units.
Recipe Manager NT Unit Parameter
A value maintained in the Recipe Manager NT system that reflects a value in a
plant, and may be used to determine Recipe Manager NT recipe execution
decisions.
Recipe Manager NT Unit Procedure
Implemented as an SFC of Recipe Manager NT operations, the second level of a
Recipe Manager NT recipe; used in Recipe Manager NT procedures.
Recipe Phase
A phase that is part of a recipe procedure in a master or control recipe.
Recipe Procedure
The part of a recipe that defines the strategy for producing a batch.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
193
Register
Registers are used for any communication between equipment phases in the
Recipe Manager NT system. The primary registers are BCOMMAND, BSTATUS,
FAIL_INDEX and REQUEST. In the DeltaV system, parameters are equivalent to
PROVOX registers.
Report Parameter
Variables, defined in the equipment database, that represent process values
such as name, ID, data type, and engineering units for an equipment phase
class.
Reset (or Remove Batch)
This Recipe Manager NT command accessed from the Batch List screen
transitions the Recipe Manager NT system from aborted, complete, or stopped
state to the idle state, releasing any equipment not properly released otherwise.
Resource
All equipment defined in Recipe Manager NT is considered a resource that is
acquired by and released from batches.
Resource class
A logical grouping of common resources.
Restart
This Recipe Manager NT command is usable for a batch in the held state. It
invokes the restarting logic for applicable phases, and then transitions to the
running state.
Restarting
This Recipe Manager NT state indicates that a sequence for a recovery from a
temporary stop is in progress.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
194
Glossary
Restart Mode
Controls how the Recipe Manager NT Server starts. The restart mode can be:
Cold restart: Provides an empty batch list to operators, forcing them to select the
batches they want to create and run.
Warm restart: Restores the batch list and the state of the Recipe Manager NT
Server to their last known state.
Prompt: Prompts the user to select the restart mode: warm or cold.
Resume
This Recipe Manager NT command accessed from the Phase Control screen
invokes the resume logic for a paused phase.
Running
This Recipe Manager NT state indicates that a normal operating sequence is in
progress.
Scale Factor
A quantity that defines the percentage of a batch to be produced.
Shell (Recipe Manager NT for PROVOX Phase Logic Shell)
PROVOX operation and FST starter code provided to address phase logic state
management issues. This code contains locations to which you may add specific
phase logic.
Site
A component of a batch manufacturing enterprise that is identified by physical,
geographical, or logical segmentation within an enterprise. A site may contain
areas, process cells, units, equipment modules, and control modules.
Server
A computer which acts like a hub. Other PCs extract from or upload data to this
computer. Commonly, a DBMS runs on the server, which stores/retrieves data
into a database on the server. Data is sent from other PCs to the server to be
stored or retrieved. Data is also sent from the server to requesting PCs. PCs
interacting with the server are called clients.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
195
Shared-use Resource
A resource that can be used by more than one user at a time.
Single Product Process Cell
Produces the same product in each batch.
SINGLE_STEP (or SEMI-AUTO Mode)
When a phase is set to SINGLE_STEP mode, the phase transitions to the next
programmed pause location and waits for the operator to issue a RESUME
command. The pause locations are preprogrammed into the phase logic.
Typically, the phase logic is in SINGLE_STEP mode when testing a phase.
Start
This Recipe Manager NT command invokes the running logic for the phases of a
batch, as determined by the recipe SFC.
State
The condition of a piece of equipment or a procedural element at any given time.
Possible states are: ABORTED, ABORTING, COMPLETE, HELD, HOLDING,
IDLE, READY, RESTARTING, RUNNING, STOPPING, and STOPPED. The
number of possible states and their names vary for equipment and for procedural
elements.
State Transition Logic
The logic within the PPLI that provides a standard interface to the project-specific
phase logic. The state transition logic receives commands from the Recipe
Manager NT Server or the operator, then initiates the different components of the
project-specific phase logic. It resides in the controller.
Step
A logical piece of a sequential function chart (SFC). In the recipe editor, steps
define the logic of a recipe.
Step Buffer
Used to store the previous value of the step index.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
196
Glossary
Step Index
The current step of the active phase.
Step Parameter
A formula defined in the recipe.
Stop
This Recipe Manager NT command invokes the stopping logic for applicable
phases of a batch to permanently halt the operation of the batch and to place all
equipment in a safe state (the stopped state). The operator cannot restart a
batch after a stop command. Abort is an emergency stop.
Stopped
This Recipe Manager NT state indicates that a permanent, (but not emergency)
shutdown has completed.
Stopping
This Recipe Manager NT state indicates that a permanent, (but not emergency)
shutdown has completed.
Stream
See the definition for path.
Tag
An individual unit of instructions, stored in the database, capable of receiving,
verifying, manipulating, and outputting process values.
Transition
Defines when a recipe moves from one step to another in the sequential function
chart.
Unit
1. A defined group of specific process equipment that processes a particular
batch. For control purposes, such a unit is one entity.
2. A PROVOXr point type. A unit point has many attributes, enabling it to
control the execution of a unit operation.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Glossary
197
Unit Class
Defines common properties for a class of units. Used to create class-based
recipes.
Unit Instance
A specific unit in a unit class, defined by the information that ties the equipment
to the physical equipment.
Unit Operation
A procedural element defining an independent processing activity that controls
phases on a single piece of equipment.
Unit Parameter
Parameters that are associated with a unit, such as temperature and level
parameters. Unit parameters are accessible to all phases that execute on that
unit.
Unit Procedure
Operations that control the function of a single piece of equipment.
Unit Parameter Class
A variable name assigned to a class of unit parameters. Used in recipe
transitions to implement class-based recipes.
VBEXEC.LOG
The file containing the historical record of the commands received and the
operations performed by each Recipe Manager NT Server. This file resides in the
Recipe Manager NT log directory.
Work Area
The section of the equipment editor that you use to build your equipment
database.
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
198
Glossary
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
Index
199
Index
Symbols
B
# of Requests register, 131
batch
command, 149
control, 151, 157
control logic in PROVOX, 95
creation, 151
event journals, writing entries to,
143
mode, 149
process, 152
resource
acquirement, 151
release, 151
state, 149
A
ABORT command, 151
Abort logic, 102
description of states, 88
in FST shell, 111
in unit operation shell, 106
vs. Stop logic, 90
acquiring resources, request codes
for, 137
ACTIVE mode, 165
active phase template, 63, 70
active step change, 149, 166
active vs. quiescent states, 87
adding
a PROVOX watchdog in PPLI,
72
PROVOX point (PPLICFG), 65,
68
Batch Executive
and phase requests, 135
DeltaV software, 16
machine, 26
overview, 39
multiple machines, 39
software, 38
Batch ID register, 130
alarm, icon, 155
Batch Operator Interface, 15, 22,
24, 26, 38, 149, 151, 152, 153
DeltaV software, 16
starting phases, 84
tasks, 23
Alarm Summary screen, 155
batch--related, alarm, 151
alias template, 109
BCOMMAND register, 91
Archiver, 41
Boolean Prompt register, 132
ASCII point, 104
BSTATUS register, 91
automatic, control re--establishment,
166
building, ASCII messages, 104
Advance command in LCP, 97
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
200
Index
C
Cancel Operation command
(PROVOX), 95
CHECK--PAUSE subroutine, 109,
122
checklists
Highway Data Link, 36
post--installation, 35
checkmark on PPLI screen, 66
CHIP--NT. See Computer/Highway
Interface Package (CHIP)
Clear Hold command (PROVOX),
96
CLEAR--FAIL subroutine, 102
coaxial, network, 36
codes, table of phase request, 136
COM FAIL status, 161
command
ABORT, 151
HOLD, 151, 159
operator, 95
RESTART, 151, 166
START, 151
STOP, 151
COMMAND DCD, 154
and FST shell, 110
control, 165
setpoint, 119, 154
setting registers to ABS DBI of,
85
setting to abort, stop or hold,
106
setting up, 102
template, 99, 109
COMMAND register, 73
COMMAND register, 119
DCD template for, 99
communication
among synchronized phases,
144
between Recipe Manager
equipment phases and the
controller, 90, 135
Complete state, 89
computer mode, 121
Computer/Highway Interface
Package (CHIP), 17, 25, 150, 161,
162
and PPLI configuration, 61
ASCII point, 104
database, 62
installation procedure
selecting directory, 44
system environment
variables, 46
installing, 42
uninstalling, 54
configuration tags, ENVOX, 108
configuring
flexible, 72, 98
OPC Mirror, 78
parameter references, 78
PPLI, overview of tasks, 67
PROVOX phases, 58
recommended method, 60
connecting
Highway Data Link, 33
Recipe Manager NT to
PROVOX, 67
to PROVOX highway, 33
to the process network, 35
consoles, operator, 15, 26
Continue from Hold command
(PROVOX), 96
Control DCD, 154, 164
setpoint, 164
controller, 161
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
controlling, phases, manually, 163,
166
conventions
keyboard, 9
manual, 8
type style, 8
warnings, cautions, and notes,
10
Copy Template (PPLICFG function),
21, 65, 69, 70
creating, phases
in PROVOX, 84
using shell template, 101
D
data items for equipment phases,
92
data request, 155
database, CHIP, 62
database index (DBI)
calculating, 114
initializing LCPs with, 114
DCD, 152
COMMAND, 154
Control, 154
control interface, 97, 98
point, 154
points, 25, 61
adding and deleting, 68
STATUS, 154
DDP
display, 157
register, 164
deleting
CHIP NT, 54
PROVOX point (PPLICFG
function), 65
Recipe Manager software, 54
201
DeltaV Application Station, 15
checklist, 35
location, 31
DeltaV Batch, PROVOX phase
configuration for use with, 58
DeltaV Batch Historian, 41
DeltaV Explorer, 17, 153
DeltaV software, 16
DeltaV Watchdog register, 131
detail display parameter. See DDP
discrete control device. See DCD
displays, 22
documents
industry standards, 7
Recipe Manager, 3
related FRSI, 5
DOCVUE, 11
DOWNLOAD
command, 132
register, 75
clearing the, 134
downloading
DeltaV parameters, 140
phase parameters, 136
example of, 141
points to CHIP, 61
Dynamic Data Exchange (DDE), 16,
39
dynamic states, 111
E
edit PROVOX point (PPLICFG
function), 68
editing
equipment phases in PPLI, 69
in FST shell, 113
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
202
Index
in unit operation shell, 102
PPLI configuration, 65
determining the active
phase, 128
LCP--based, creating, 84
requirements for
developing, 86
state transition diagram, 86
unit--based, creating, 85
Recipe Manager, 84
communication among
synchronized phases, 144
creating using template, 101
requests, 135
sending messages among,
144
status, 159
terminal state, 164, 165
understanding, 82
electrical installation planning, 28
environmental considerations for
hardware installation, 28
ENVOX, 25
configuration tags, 108
creating phases in PROVOX, 84
data for PPLI input, 114
importing shell configuration,
107
equipment
arbitration, 155
binding, 151, 153
configuring, 104
failure, 155
graphics, 151
IDs, 130
and Phase ID register, 128
phase class, configuring phase
messages, 145
shared, 155
status, 151
equipment phases, 150, 151, 153,
154, 164
logic testing, 154
operation, 154
PPLI, 84
data items, 92
editing, 69
linking to PROVOX points,
69
Phase ID register, 128
register allocations, 117
register definitions, 90
requirements for phase
logic, 86
PROVOX, 84
and unit operation logic, 95
description of states, 88
error conditions, 120
error log, 165
Ethernet network, 15
event, log, 151
event journals, writing entries to,
143
execution, of main FST, 113
External Reference Parameter, 93
F
FAIL
command (PROVOX), 96
step, 102, 106
FAIL--INDEX register, 91
failure
and CLEAR--FAIL subroutine,
102
and transition to holding state,
89, 120
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
considerations, 157, 159
in unit operations, 105
notification, 155
numbers and priorities, 120
PPLI, 160
PROVOX, 106
recovery, 160
value, 159
FAILURE register, 73, 120
file, input, for unit operation and
phase names, 114
files
deleting during uninstall, 54
PPLIOPER.SQL, 114
PPLIOPER.TXT, 61, 115
.SQL, 114
.TXT, 115
flexible configuration, 72, 98
Floating Point Prompt register, 131
flow chart for PPLI unit operation
shell, 101
FST, 25, 153, 165
continuous execution of main,
113
ENVOX configuration tags for
template FSTs, 108
logic and logic control points, 97
shell, 110
FST shell, 84, 98, 110
changes affecting command
and status registers, 119
editing, 113
handling pause, resume, and
single--step processing, 125
importing, 107
initializing LCPs with DBIs, 114
reserved integer registers, 114
203
G
green checkmark, on PPLI screen,
66
grounding, 30
H
hardware
components, Recipe Manager,
14
installation planning, 28
HDL. See Highway Data Link (HDL)
help, online, 3
Highway Data Link (HDL), 15, 38,
150
checklists, 36
connecting, 33
preparing, 31
Hold, Propagation setup, 159
HOLD command, 151, 159
Hold logic, 102, 106
and failure numbers, 120
description of states, 89
in FST shell, 111
in unit operation shell, 106
PROVOX operator commands,
96
hubs, 15
I
Idle state, 88, 162
function sequence table. See FST
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
204
Index
IEC 1131--3 standard, 20
documents, 7
support of, 1
importing, shell configuration, 107
industry standards, 1
documents, 7
installing
CHIP NT, 42
DeltaV Application Station,
location, 31
hardware, 28
hardware key, 31
Highway Data Link, 31, 36
connections, 33
process network, connections,
35
Recipe Manager, 42
software, 37
Integer Prompt register, 131
integer registers used in the shell
code, 85, 114
ISA S88.01 (S88) standard, 153
documents, 7
J
journals, batch event, writing entries
to, 143
K
keyboard conventions, 9
L
LCP, 153
faceplate, 165
FSTs, running equipment
phases, 164
LCP--based phases, 84
and pause logic, 122
creating, 84
licensing agreements, Recipe
Manager, 49, 52
limits, system, PPLI, 61
link phase to PROVOX point
(PPLICFG function), 65, 69
list control, PPLICFG, 63
Load/Start and Change Phase
command (PROVOX), 95
logic control points (LCPs), 25, 153
adding and editing, 68
downloading to CHIP, 61
initializing with DBI, 114
with COMMAND and STATE
DCDs, 110
with FST logic, 97
M
MANUAL, mode, 152, 154, 160,
161, 162
manual
conventions, 8
for physical and electrical
planning, 28
mode, 121
handling pause, resume,
and single--step processing,
125
programming separate
paths for, 128
setting in OWNER register,
121
with DCD control interface,
97
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
phase control, 157, 163, 166
related FRSI, 5
messages, 93
canceling, 139
error, 160, 161, 163
in PPLI configuration, 67
sending to operator, 137
sending to other phases, 139,
144
mode
ACTIVE, 165
computer vs. manual, 121
MANUAL, 152, 154, 160, 161,
162
single--step, 121
205
open edit dialog (PPLICFG
function), 66
editing phases, 69
operation logic, PROVOX, 95
operator
action request, 155
attention request, 164
commands (PROVOX), 95
displays, 22
ID, 104
parameter, 105
prompt, 155
Operator Attention Requests
(PROVOX), 96, 128
modifying, PPLI configuration, 65
operator workplace (OWP), console,
15, 26
mouse, using the right button
to access editing functions, 66
to add/edit PROVOX points, 68
Or sequence selections, in PFCs,
transition of phase to stopped state,
88
OWNER register, 74, 91, 121
N
name changes, 76
P
NAMUR guidelines, 7
parameter references, configuration,
78
navigating, PPLICFG tree control,
66
network, typical arrangement
Batch Executive machine, 40
Batch Operator Interface, 40
O
OAR, 155, 164
occurrence number, 104
online help, 3
OPC Mirror, configuration, 78
parameters
download, 105
external reference, 93
handling, 103
Pause logic
and LCP--based phases, 122
and unit--based phases, 124
handling from PROVOX
console, 125
operator command, 121
registers, 121
PAUSE register, 74, 121, 122
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
206
Index
PAUSE_REQ register, 91
PAUSED register, 92, 121
PFC, 20, 152
phase
configuration in PPLI tree
structure, 66
logic, 151, 154, 162
testing, 163, 164
logic shell, 159
manual control, 157
name, 165
Phase Control screen, 84, 154
Phase ID, 164
PHASE ID register, 74, 128
phase logic, 105
components, 82
data items, 92
description of states, 88
failure value, 159
in the PROVOX unit controller,
82
programming, 117
register allocations, 117
register definitions, 90
requirements for developing, 86
state transition diagram, 86
Phase Logic Module (PLM), unit, 59
phase parameters, 93
automatic download of, 127
example of downloading, 141
phase programming, adherence to
state transition logic, 87
phase registers
allocation table, 117
definition table, 90
Phase Summary screen, 165
phase--to--phase communications
messages, 139, 144
requests, 136
PHASELOGIC subroutine, 109, 110,
113
phases
creating using template, 101
description of states, 88
LCP--based, 84
and pause logic, 122
creating, 84
programming, 81
PROVOX
creating, 84
determining the active
phase, 128
sending messages among, 144
understanding, 82
unit--based, 84
and pause logic, 124
creating, 85
unlinked, 66, 69
planning, hardware installation, 28
POC, 38
points, PROVOX, 25
adding and editing functions, 65,
68
in CHIP database, 62
linking phases to, 65
unit control of, 130
powering up Recipe Manager
hardware, 35
PPLI, 16, 21, 41, 57, 150, 162, 163
configuration program, 61
configuration window, 22
Configurator, 16
DCD control interface, 97, 98
description of interface, 97
diagnostics, 157
diagnostics screen, 165
editing the configuration, 65
equipment phase connections,
84
error clarification, 161
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
error log, 165
failure, 160
FSTs and subroutines, 110
input file for operation and
phase names, 114
main FST, 110
continuous running of, 113
main screen, 63
manual phase control, 97
phase register allocations, 117
phase register definitions, 90
processing status, 165
requirements for phase logic, 86
restarting programs after
changes, 62
run time executable, 165
shell, 17, 84, 98
changes affecting command
and status registers, 119
flow chart, 101
FST shell, 110
importing, 107
input file, 114
unit operation shell, 101
status, 165
system limits, 61
PPLICFG program, 61
list of functions, 65
main screen elements, 63
PPLIOPER.SQL file, 114
PPLIOPER.TXT file, 61
copying into Recipe Manager
directory, 115
prerequisites, engineering
knowledge, 60
procedural function chart. See PFC
process network, connecting to the,
35
ProfessionalPLUS Workstation, 38
hardware key, 31
207
PROVOX
ASCII point, 104
console, 15, 26, 149, 151, 154
equipment phase status,
159
manual phase control, 163
point interface, 163
controller, 15, 25
detected failure, 159
creating phases, 84
failure detection, 106
handling pause, resume, and
single--step from the console,
125
highway, connecting to, 33
logic capabilities, 95
operation considerations, 152
operator commands, 95
phase configuration, for use
with DeltaV Batch, 58
phase logic, 154
Phase Logic Interface. See
PPLI
point, 154
alarm, 152
characteristics, 157
current value, 157
description, 157
values, 157
relationship to Recipe Manager,
25
requirements for phase logic, 86
software, 150
status, 165
System, 153
tag, 165
unit controllers, 150
unit operations controller (UOC)
phases, 84
unit point
interface, 164
unit definition, 159
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
208
Index
watchdog
adding, 72
in PPLI tree structure, 66
PROVOX Operator Console. See
POC
PROVOX Phase Logic Interface.
See PPLI
PROVUE console, 15, 26
Q
question mark, meaning in PPLI
screen, 70
quiescent states, 87, 111
R
re--establishing automatic control,
166
recipe
author, 104
control, 149
management, 153
scaling, 151
transitions, 78
value parameter, 104
Recipe Manager NT
active step change function, 166
Batch Executive, 149, 160, 162,
163
Batch Operator Interface, 149,
151, 152, 153
command, 154
components, 149, 150, 152
document, 3
environment, interoperability,
152
equipment phase, 157
configuration, 164
status, 157
hardware components, 14
installation procedure, 42
adding/removing programs,
43
choosing destination
location, 49, 52, 53
software license agreement,
49, 52
installing, 42
interaction with the PROVOX
system, 157
name changes, 76
parameter input, 151
Phase Control screen, 161
phase status, 159
power failure, 165
product overview, 13
recipe failure, 155
relationship to PROVOX, 25
report parameters, 104
resource arbitration, 154
Simulator, 39
Software, 150, 163
software components, 15
System, 153
uninstalling software, 54
user interface overview, 17
Recipe Studio, 19, 152
DeltaV software, 16
window, 20
recipes, definition of, 20
red X, on PPLI screen, 67
registers, 119
# of Requests, 131
allocations for phase logic, 117
Batch ID, 130
Boolean Prompt, 132
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
COMMAND, 73, 119
DeltaV Watchdog, 131
DOWNLOAD, 75, 134
FAILURE, 73, 120
Floating Point prompt, 131
integer, setting to COMMAND
and STATE DCDs, 85
Integer Prompt, 131
OWNER, 74, 121
PAUSE, 74, 121, 122
PAUSED, 121
PHASE ID, 74, 128
REQUEST, 73, 127, 135
SINGLE_STEP, 121
STATUS, 73, 119
STEP_INDEX, 74, 129
String Prompt, 132
UNIT, 74, 130
used in FST shell, 114
related documents, 5
remote point, 105
report parameters, 104
reports, phase, 93
automatic upload of, 127
uploading, 143
REQUEST register, 73, 91, 127,
135
using, 135
requests
aborting, 140
arguments, 141
direct vs. indirect, 141
example of download, 141
table of codes for, 136
RESET to idle state after phase
completion, 88, 89
resource
acquiring and releasing, 127,
137
allocation, 155
209
arbitration, monitoring, 151
RESTART command, 151, 166
Restart logic, 102
after PROVOX failure, 106
description of state, 89
restarting after transition to held
state, 89
restarting, Recipe Manager NT after
changes, 62
RESUME command, 121, 122
Resume logic, 121
handling from PROVOX
console, 125
in FST code, 124
Retry command (PROVOX), 96
routers, 15
run--time interface, 150
running equipment phases, 164
Running state, 88, 102
S
saving, configuration files, 65
scan rate, of main FST, 113
screen
Alarm Summary, 155
Phase Control, 154
Phase Summary, 165
send messages, 144
sending messages, 137
set template (PPLICFG function),
65, 70
setpoint, 157
COMMAND DCD, 119
STATE DCD, 119
setting, DDP registers, 164
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
210
Index
Setup program
CHIP, 44
Recipe Manager, 43
SETUP subroutine, 102
shared equipment, 155
shell, PPLI, 84, 98
changes affecting command
and status registers, 119
directory, copying input files,
114
FST shell, 110
handling pause, resume, and
single--step processing, 125
importing into ENVOX, 107
phase register allocations, 117
phase register definitions, 90
unit operation shell, 101
shell operations, 25
shutdown, using Stop or Abort logic,
88, 90
Simulator, 16, 41
Single--step logic, 121
handling from PROVOX
console, 125
in unit operation shell, 125
SINGLE_STEP register, 92, 121
software
components, 15
deleting, 54
installing, 37
uninstalling, 54
Software License Agreement,
Recipe Manager, 49, 52
.SQL file, 114
standards
documents, 7
IEC 1131--3, 1, 7, 20
ISA S88.01, 7
NAMUR Guidelines, 7
START command, 88, 97, 102, 151
state
and FST subroutines, 111
description of, 88
dynamic vs. quiescent, 111
ENVOX configuration tags for,
108
Idle, 162
STATE DCD
and FST shell, 110
changing the setpoint, 113
setpoint, 119
setting registers to ABS DBI of,
85
setting up, 102
template, 100, 109
state transition diagram, 86, 164
and FST shell, 110
for unit points, 97
STATUS DCD, 154
control, 165
setpoint, 154, 159
STATUS register, 73, 119
DCD template for, 99
STEP_INDEX register, 74, 91, 129
steps, in unit operations, 102
STOP command, 151
Stop logic, 102
description of states, 88
in FST shell, 111
in unit operation shell, 106
LCP command, 97
stopping a phase, 88
vs. Abort logic, 90
Stop/Fail command (PROVOX), 96
String Prompt register, 132
subroutines
CHECK--PAUSE, 122
in PPLI shell, 110
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Index
synchronizing phases, and sending
messages, 144
Uninterruptible Power Supply
(UPS), 29
system environment variables,
defining for CHIP, 46
unit
T
tags
ENVOX configuration, 108
replaced by entry numbers in
PROVOX, 114
targeting points for PPLI
configuration, 61
template, set, 70
templates
copy, 21, 65, 69, 70
ENVOX configuration tags, 108
set, 65
X--PPLIOPER, 101
terminal state, 165
toolbar, PPLICFG, 63
transitions, recipe, 78
tree control, PPLICFG, 63
navigating, 66
tune privilege, 164
twisted--pair
cables and HDL connections, 33
network, 35, 36
.TXT file, 115
type style conventions, 8
U
211
definition, 159
in UNIT register, 130
modules, 60
operation, logic, 153
operations, running equipment
phases, 164
unit operation shell, 84, 98, 101
and pause logic, 124
changes affecting command
and status registers, 119
connecting operations and
phase names, 107
creating unit--based phases, 85
editing, 102
handling pause, resume, and
single--step processing, 126
importing, 107
unit parameters
changing the PPLI connection,
66
downloading to CHIP, 61
unit points, 25, 153
adding and editing, 68
state transition diagram for, 97
with operation logic, 95
UNIT register, 74, 91, 130
unlinked phases, 66, 69
upload report values, 136, 143
USER--EDIT locations
in FST shell, 113
in unit operation shell, 102
UV failure register, 106
uninstalling
CHIP NT, 54
Recipe Manager software, 54
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
212
Index
in PPLI tree structure, 66
V
validate using CHIP database
(PPLICFG function), 65
Windows NT operating system, 15
workstations, ProfessionalPLUS, 38
X
W
X on PPLI screen, 67
WAIT instructions, avoiding in FSTs,
113
X--PPLIMAIN template, 108, 110
warm start, 157, 160, 162, 163, 165
X--PPLIOPER template, 101, 103,
109
watchdog configuration (PROVOX)
adding, 72
Installing and Using the Recipe Manager NT for the PROVOX System
(Revision B -- March 2000)
Notes
213
Notes ...
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
214
Notes
Notes ...
Installing and Using the Recipe Manager NT for the PROVOX System (Revision B -- March 2000)
UM41.0:APS311