Using ENVOX Server
Using ENVOX Server
Control Desktop
User Manual
UM:SW3159:EN
Original — May 2000
This manual supercedes the issue dated May 1998.
D2U01701002
DOCVUE, ENVOX, Fisher-Rosemount, Instrument Information System, PROVOX, and PROVUE are
marks of one of the Fisher-Rosemount group of companies.
All other marks are the property of their respective owners.
The contents of this publication are presented for informational purposes only, and while every effort
has been made to ensure their accuracy, they are not to be construed as warranties or guarantees,
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.
Using ENVOXr Server and Control Desktop Your Evaluation Please ... iii
(Original — May 2000)
Job Responsibility:
Please indicate your evaluation of this manual. Attach extra sheets if needed.
1. How and when do you use this manual? V Read entire manual before attempting task
V Read selected sections before attempting task
V Read while attempting task
V Attempt task first
V Read as last resort
2. How well is the manual’s content V Excellent — parallels product’s operation,
organized? Please explain. very usable
V Good — representative of the product’s
operation, usable
V Average — usable but can be improved
V Fair — not very usable, should be improved
V Poor — not usable, must be improved
V No Opinion
Understandable Applicable
3. Is the manual’s content understandable V V Excellent — very easy to understand,
and applicable to the product’s operation? very applicable
Please explain. V V Good — easy to understand, applicable
V V Average — applicable but some sections
not easy to understand
V V Fair — not very understandable/applicable,
should be improved
V V Poor — not understandable/applicable,
must be improved
V V No Opinion
4. How well do the manual’s illustrations V Excellent — very easy to understand, extremely
convey product information? usable
Please explain. V Good — easy to understand, very usable
V Average — fairly easy to understand, usable
V Fair — not easy to understand, should be
improved, not very usable
V Poor — cannot understand, must be improved,
totally unusable
V No Opinion
iv Your Evaluation Please ... Using ENVOXr Server and Control Desktop
(Original — May 2000)
5. Describe the amount of usable information V Too much information — not all required to
in this manual including tables. perform task
Please explain. V Proper amount provided — not too much nor
too little
V Too little information — needed additional
information to perform task
V No Opinion
Sections Index
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.2 Product Version this Manual Supports . . . . . . . . . . . . . . . . . . . . . . 15
1.3 How to use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4 First Release for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.5 Enhancements in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.6 Structure of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.7 Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.8 Cautions and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.9 ENVOX Server and Control Desktop Documents . . . . . . . . . . . . 21
1.10 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
1.11 Electronic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.12 Where to Find Answers About This Product or Manual . . . . . . . 22
2 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 Product Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.4 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5 Configuration Planning and Design . . . . . . . . . . . . . . . . . . . . . . . . 25
2.6 Configuration Engineering and Maintenance Tasks . . . . . . . . . . 26
2.6.1 Server and Client Administration . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.6.2 Import/Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.6.3 Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6.4 Tag Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6.5 Control Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6.6 Display Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.6.7 Logic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.6.8 Generate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.6.9 Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.6.10 Portable Database Transfer (PDX) . . . . . . . . . . . . . . . . . . . . . . . 29
2.6.11 LCP Trace/Tune . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.6.12 Report Writer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.13 Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.14 Task Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.15 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.6.16 Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3 User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2 Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.1 Help Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
vi Contents Using ENVOXr Server and Control Desktop
(Original — May 2000)
5 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1 ENVOX Server and Control Desktop Navigation . . . . . . . . . . . . . 47
5.1.1 Explorers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.1.1.1 Explorers’ Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1.1.2 Explorer Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.1.1.3 System Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.1.1.4 Resource Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.1.1.5 Plant I/O Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
5.1.1.6 The Controller Device I/O Explorer . . . . . . . . . . . . . . . . . . . . . 52
5.1.2 Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
5.1.2.1 Top-Level Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.1.2.2 Pull-Down Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5.1.2.3 Context Menu (Right Mouse Button) . . . . . . . . . . . . . . . . . . . 53
5.1.3 Toolbar Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.2 Accessing Modules and Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.2.1 From the Windows NT Start as Standalone Modules . . . . . . . 55
5.2.2 From within Control Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3 ENVOX Server Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
5.4 Client Administration Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7 Tag Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.1 Configuration Tasks with Tag Sets . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.2 Create a Tag Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.3 Tag Set Creation from ISQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.3.1 Appending Tag Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.3.2 Using Pattern Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
viii Contents Using ENVOXr Server and Control Desktop
(Original — May 2000)
8 Logic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.1 Accessing the Logic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.1.1 Procedures and Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.1.2 LCP FSTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.1.3 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.1.4 Conditional Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.2 Add an Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.2.1 Entering Instruction Mnemonics . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.2.2 Filling in the Operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.2.3 Closing an Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.3 Setting Logic Editor Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.4 Including Blocks of Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
8.5 Modifying Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.6 Adding a Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.7 Cutting or Copying and Pasting Text . . . . . . . . . . . . . . . . . . . . . . . 106
8.7.1 Cutting or Copying and Pasting a Closed Instruction . . . . . . . 106
8.7.2 Cutting or Copying and Pasting Text Within Comments . . . . . 106
8.8 Finding and Replacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
8.8.1 Using Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.8.2 Using Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.9 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.10 Determining FST or Step Instruction Size . . . . . . . . . . . . . . . . . . . 109
8.11 Saving Your Instruction Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.11.1 Save with Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.11.2 Save without Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.12 Viewing Generation Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
8.13 Creating a Console Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.13.1 LAYOUT Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.13.2 HISTORY Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.13.3 REPEAT, NEXT, UNTIL, and UNTIL END Instructions . . . . . . 113
8.13.4 Additional Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.13.5 Previewing a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
8.13.6 Example Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
8.14 Printing Logic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.14.1 Printing from the Logic Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.14.1.1 Printing All Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
8.14.1.2 Printing Selected Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.14.1.3 Printing to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.14.2 Printing from the Item Detail Window . . . . . . . . . . . . . . . . . . . . . 117
14 Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
14.1 Highway Reference List/Highway Access Control List . . . . . . . . 205
14.1.1 Search the Highway Reference List . . . . . . . . . . . . . . . . . . . . . . 208
14.1.2 Populating the Highway Reference List . . . . . . . . . . . . . . . . . . . 209
14.2 Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
14.2.1 Viewing Events for a Particular Item . . . . . . . . . . . . . . . . . . . . . . 212
14.2.2 Searching Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
14.3 Importing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
14.3.1 Importing from Control Desktop . . . . . . . . . . . . . . . . . . . . . . . . . 217
14.3.2 Importing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . 218
14.4 Exporting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
14.4.1 Running the Export Utility from Control Desktop . . . . . . . . . . . 219
14.4.1.1 Exporting the Entire Database . . . . . . . . . . . . . . . . . . . . . . . . . 220
14.4.1.2 Exporting Selected Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
14.4.2 Exporting from a Command Line . . . . . . . . . . . . . . . . . . . . . . . . 222
14.5 Upgrading Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
xii Contents Using ENVOXr Server and Control Desktop
(Original — May 2000)
Figures
Figure 3-1. Map of Help System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 6-1. Matrix View for AI Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Figure 6-2. New Item Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 6-3. Item Detail Window for New AI Point . . . . . . . . . . . . . . . . . . 64
Figure 6-4. New I/O Data Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 6-5. Creating a New Item From an Item Type . . . . . . . . . . . . . . 67
Figure 6-6. Creating a New Item from a Specific Item in the
Resource Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 6-7. Saving Data From Matrix View To External Format . . . . . . 74
Figure 6-8. Finding the File for Loading from External Format . . . . . . 75
Figure 6-9. Copy Item Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 6-10. Target Data Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Figure 6-11. CONSOLE Target Matrix View . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 6-12. Example Validation Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 8-1. Instruction in Open Format . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 8-2. Example Instruction In Closed Format . . . . . . . . . . . . . . . . 103
Figure 8-3. Example Layout Instruction Field . . . . . . . . . . . . . . . . . . . . . 111
Figure 8-4. Example Edit Layout Print Attributes Dialog . . . . . . . . . . . . 111
Figure 8-5. Example Report in Edit Window . . . . . . . . . . . . . . . . . . . . . . 115
Figure 8-6. Edit Layout Print Attributes Dialog . . . . . . . . . . . . . . . . . . . . 115
Figure 8-7. Example Report in Preview Window . . . . . . . . . . . . . . . . . . 116
Figure 9-1. Excel Matrix Connection to ENVOX Server . . . . . . . . . . . . 121
Figure 9-2. Excel and Open Database . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Figure 9-3. Workbook Type Selection Dialog . . . . . . . . . . . . . . . . . . . . . 123
Figure 9-4. Excel Matrix Enhanced DCD Workbook . . . . . . . . . . . . . . . 126
Figure 10-1. Devices to Generate Window . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 10-2. Devices to Download Window . . . . . . . . . . . . . . . . . . . . . . . . 139
Figure 10-3. Initial Devices to Download Window . . . . . . . . . . . . . . . . . . 145
Figure 10-4. Devices to Download Window after Entering a Device . . 146
Figure 10-5. Upload Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Figure 10-6. Task Monitor Showing Upload Status . . . . . . . . . . . . . . . . . 154
Figure 10-7. Example Upload Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 10-8. Example Upload Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 11-1. The LCP Trace/Tune Window . . . . . . . . . . . . . . . . . . . . . . . . 166
Figure 11-2. The Trace Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Figure 12-1. Select Report Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Figure 13-1. Task Monitor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Figure 13-2. Generate Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 14-1. Highway Reference List Dialog . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 14-2. Search Dialog for Highway Reference List Data . . . . . . . . 209
Figure 14-3. Populate Highway Access Control List Dialog . . . . . . . . . . 210
Figure 14-4. Audit Trail Tab of Item Detail Window . . . . . . . . . . . . . . . . . 212
Figure 14-5. Event Detail for a Selected Event . . . . . . . . . . . . . . . . . . . . . 213
Using ENVOXr Server and Control Desktop Contents xiii
(Original — May 2000)
Figure 14-6. The Audit Trail Search Window—Date Range Tab . . . . . . 214
Figure 14-7. Audit Trail Search Window—Item Criteria Tab . . . . . . . . . . 215
Figure 14-8. Audit Trail Search Window—Event No. Tab . . . . . . . . . . . . 216
Figure 14-9. Import Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Figure 14-10. Import and Export Utility Flow Diagram . . . . . . . . . . . . . . . . 219
Figure 14-11. Export Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 14-12. Upgrade Devices Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
xiv Contents Using ENVOXr Server and Control Desktop
(Original — May 2000)
Tables
Table 1-1. Type Style Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 2-1. Computer Requirements for ENVOX Server and
Control Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 7-1. Rules for Appending Tags to a Tag Set . . . . . . . . . . . . . . . . 95
Table 7-2. ENVOX Database Default Pattern Tags . . . . . . . . . . . . . . . 96
Table 10-1. Types of Downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 10-2. Uploadable Point Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Table 10-3. Uploadable Detail Display Parameters . . . . . . . . . . . . . . . . 157
Table 11-1. Instructions That Can Be Added As Tune Items . . . . . . . . 185
Introduction F Section 1 15
Figure 1-Table 1
1
1
1 Introduction
Type SW3159 ENVOXr Server and Type SW3311 Control Desktop
Software are applications used for configuring a PROVOXr process
management system. Control Desktop software, the interface, is the
client to the ENVOX server that contains your ENVOX databases.
ENVOX Server P5.0 uses Control Desktop P5.0 for the user interface.
The SYBASE APT forms system used in earlier ENVOX releases is not
included.
J A combination of new item detail screens and the new Logic Editor
module provides configuration support for LCP FSTs, Procedures,
Operations, Conditional Colors, Conditional Text, and Console
Reports.
J Import lets you import configuration data into the current database.
J Export lets you copy configuration data to a file, which can later be
used when importing data into a database.
1
J Download Backup lets you download data for all devices to be
backed up.
J Populate HACL lets you assign Highway Access Control List (HACL)
numbers to points targeted to all, or selected, consoles.
Revision Control — The title page and the footer of each page contain
the revision level and the print date of the manual. The title page and
Prompt Style — This manual may present displays and prompt lines
differently than they appear on your screen. Enter the commands shown
in this manual at the equivalent prompt as shown on your screen.
Caution ... All cautions have this form and symbol. Do not disregard
cautions. They are installation, operation, or maintenance
procedures, practices, conditions, statements, and so forth,
which if not strictly observed, may result in damage to, or
destruction of, equipment or may cause a long term health
hazard.
Note ... Notes have this form and symbol. Notes contain installation,
operation, or maintenance procedures, practices, conditions,
statements, and so forth, that alert you to important information 1
which may make your task easier or increase your
understanding.
To help us evaluate how well this manual fills your needs, please
complete and send in the evaluation form located in the front of this
manual. We also appreciate your suggestions on ways to improve any
page of the manual. Please mark your suggestions on a copy of the
page and include it with the evaluation form. Thank you for providing this
information.
Figure 2-Table 2
2 2 Product Overview
The ENVOXr Server P5.0 and Control Desktop P5.0 applications and
2
the modules and utilities they include provide engineering support for
control systems implemented with the following PROVOXr devices:
20-Series controllers and newer with Control I/O or MUX I/O, PROVUEr
P5.5 and newer consoles, Operator Workplace consoles, PROVOX
Operator Consoles, and CHIP.
2.1 Introduction
ENVOX Server and Control Desktop client run on Windows NT
computers using the Intel processor family. The P5.0 release provides
full engineering capability for supported devices, including point, device,
and I/O configuration, language editing, and FST tracing, display editing
for supported revisions of PROVUE and Operator Workplace consoles,
and all PROVOX engineering utilities.
Working with the ENVOX Server, Control Desktop provides powerful and
easy-to-use configuration capabilities for a PROVOX Process
Management system, including:
Easy Navigation
After you’ve entered data for one I/O card, you can drag and drop the
configuration onto another I/O card, reducing subsequent configuration
time to a few seconds.
Table 2-1. Computer Requirements for ENVOX Server and Control Desktop
Option (Usage) Processor Memory System Disk Database Disk
CHIP Daemons 200 MHz 64 Mbytes 20 Mbytes ------
Client 200 MHz 64 Mbytes 130 Mbytes ------
Server
Client Server
400 MHz
450 MHz
192 Mbytes
256 Mbytes
100 Mbytes
190 Mbytes
300Mbytes
300Mbytes
2
CDOS 400 MHz 64 Mbytes 20 Mbytes ------
Display Designer 200 MHz 64 Mbytes 60 Mbytes ------
Excel Matrix 200 MHz 48 Mbytes 5 Mbytes ------
Emergency Download 200 MHz 48 Mbytes 5 Mbytes ------
Diagnostics(1) 400 MHz 128 Mbytes 30 Mbytes ------
User Manuals(2) 100 MHz 24 Mbytes 40 Mbytes ------
1. To install the Web-based Diagnostics to an existing Web Server requires a maximum of 12 Mbytes. This amount is less if
some of the required software has already been installed, for example, via a Control Desktop install.
If you need to install a Web Server first, then the combined Windows NT Service Pack 4 or Service Pack 6, Internet
Explorer 5.0 and MS Personal Web Server together require a maximum of 110 Mbytes with the options recommended in
the installation instructions. Other Web Servers require different amounts.
To use the Excel Matrix module, you must have Service Pack 2 and
Microsoft Excel installed.
In addition, this manual assumes that you have documented your I/O
needs in an instrument index or instrument specification sheet, or
perhaps by using ENVOX Instrument Signal Tags (ISTs). Finally, this
manual assumes that you have identified your basic control needs by
documenting the loops, batch descriptions, and logic required to support
your process.
You want to proceed in a way that takes full advantage of ENVOX Server
and Control Desktop software and the PROVOX system while making
effective use of your time. The following steps describe an effective way
to approach configuration planning:
Step 2: Identify your control strategies and the I/O that supports them.
J Create points — You copy and modify existing points and add new
points. You provide the point with a tag (name) and define its
operating, tuning, and configured parameters. You specify which
device each point is located in, and you also specify the devices to
which the point reports data (targeting).
J Create console reports — Using the Logic Editor, you design reports
that record process changes. You also determine which console
manages each report.
2.6.2 Import/Export
You can use the Import utility to load previously exported comma
delimited value (CDV)-formatted data into an ENVOX database, and use
the Export utility to move the data from one database to another. The
files holding the CDV data are simply an ASCII version of ENVOX
configuration data.
The primary interface for configuring any database item is the Item
Detail window. This window contains several tabs, each containing fields
in which you can enter the configuration information for any item.
2 Additionally, Control Desktop includes the Matrix View utility and the
Excel Matrix module that provide interfaces you can use to efficiently
configure multiple items of some types.
Displays you create with Display Designer are stored directly to the
ENVOX database.
You can open, edit, and save displays from the ENVOX database
(supported by Control Desktop) directly without any need for migration.
Similarly display files saved from the Graphics Toolkit P4.0 Application
can be opened and edited in the Display Designer application without 2
any need for migration.
2.6.8 Generate
The ENVOX Server and Control Desktop generate option checks the
consistency of the data that the software did not already verify as you
entered it. The generate option then creates download files which are
ready to be downloaded to the PROVOX devices.
2.6.9 Download
The download utility sends the generated data to the devices. The
download can be total; that is, the utility sends all the generated data to
all the devices you specify. Or the download can be partial: you limit the
download to include only new or modified data for the devices. The
download can include one or more than one device, depending on the
your login privileges.
The Control Desktop LCP Trace/Tune module replaces the ENVOX LCP
Trace/Tune Utility, and runs on the Windows NT Control Desktop Client
application using the conventions of normal Windows applications.
2 You can debug a maximum of 16 LCPs in any controller at any one time.
Each LCP can have a maximum of 10 Trace Points. (These limits are a
function of the controller implementation.)
2.6.13 Upload
Once the devices have their configuration download files and are online,
console operators can change the device tuning parameter values.
Uploading is the process of updating the ENVOX configuration database
with these changes.
The Task Monitor is a standalone utility you can use to examine the
status of jobs currently in the job queue. You can also resubmit Generate
and Download jobs from the Task Monitor.
2.6.15 Diagnostics
Desktop P5.0 Diagnostics you can examine both live and historical
diagnostics data. The design of the Diagnostics architecture enables:
Blank page.
Figure 3-Table 3
3 3 User Documentation
ENVOXr Server and Control Desktop software is accompanied by
3
3.1 Introduction
The documentation for ENVOX Server and Control Desktop software
provides the information necessary for successful implementation and
use of the application and its modules and utilities. The information is
structured in four formats:
J Printed manuals
J Field help — Appears in the status bar when certain fields are
selected. This is not available everywhere within Control Desktop.
Field help (also known as microhelp) provides information specific to
a field or area of the interface. For example, as you move from field
to field in an Item Detail window, help for the currently selected field
3 appears in the status line.
The following is a list of the help files available from the Help Map:
J Display Designer — Defines the ways you can use the Display
Designer to create and maintain console displays.
J Control Designer — Defines the ways you can use Control Designer 3
to configure and manage continuous process control strategies.
J Task Monitor — Describes the ways you use the Task Monitor utility
to monitor the state of various Control Desktop jobs.
J Report Writer — Describes the ways you use the Report Writer
module to generate reports from data in Control Desktop.
J Server Setup — Defines the ways users with appropriate access can
use this utility.
J ViewPDF — Help for the application you use to view displays saved
in Display Designer as PROVOXr Display Format files.
The only ENVOX Server and Control Desktop printed manual included
and distributed with the software is:
If you select the Install User Manuals option during installation, the
Books OnLine are installed on your configuration workstation.
Additionally, you can install the Books OnLine on other computers so you
can use the online manuals on any convenient computer.
Note that the Adobe PDF format is not related to the PROVOX Display
Format, also known as PDF. The two formats are completely different. To
view PROVOX Display Format files (graphic display files) use the
ViewPDF utility.
3
There are security features available that let you set up access to Books
OnLine according to your particular requirements. The default security
state for Books OnLine is open access to anyone using the computer on
which you have installed the software and the Books OnLine set.
C:\Program Files\Frsi\ControlDesktopP50\UserManuals
Blank page.
Figure 4-Table 4
Note ... The steps below describe the general procedure for starting
Control Desktop and logging in to the ENVOX Server. Your
system manager can alter the procedure. For example, your
system manager can modify your account to start the software
automatically when you log into your computer.
How you choose to start Control Desktop does not change how you
operate the application. Either way, Control Desktop starts and initially
displays the top-level menu, the toolbar, and the System Explorer
window.
The selections of the top level menu and the toolbar change to fit the
selections available for the individual operations.
When you start the application, notice that the Application menu is only
partially available, indicating that you must log into the servers and
database before you can continue. Once you have logged in, the
remaining menus become available. Login procedures are detailed in the
following pages and in the Control Desktop online help.
4.2.1 Login
4 After you have started Control Desktop, you may log in to servers and
databases from:
4.2.1.1 Login from Login Toolbar Icon, Top-level Menu Admin Option,
or Context (Right Mouse) Menu
When you login to the system from the Login toolbar icon, from the
Admin option in the top-level menu, or from the Login option in the
context (right mouse) menu, the Login dialog appears.
The title of the Control Desktop main window changes to include the
selected server and database in the window title. You may save the
server and database settings shown as the next entry point when you
start Control Desktop again.
A Server Authorization window appears when you log into the system
by double clicking on the server listed in the System Explorer. For
security reasons, the system requires you to enter a valid username and
password in this dialog before you can navigate past a server.
Entering this information does not immediately log you onto a particular
database; it connects you to the server allowing you to explore that
server and choose an appropriate database.
Selecting the Login... option from the right mouse button menu connects
you to the selected database directly and inserts the database name in
the Control Desktop title bar.
If you later wish to select a server other than the default server listed in
the List field under Database information, follow the process described in
the Control Desktop online help. Refer to Section 3 of this manual for
instructions on accessing and using the online help system.
Once you are logged in and connected to a database, you have the
options to:
J Startup Settings
J Edit Preferences
You may also elect to change your toolbars, an option located under the
top-level menu as Window --> Toolbars. Settings that have been made
by your system administrator may also affect what you can and cannot
do and how you use Control Desktop.
Once the license file contents have been validated and accepted, you
can view the current information about available licenses in your system
and which users currently have them checked out. License management
windows can be selected from the top-level Admin menu option.
Since there may be a delay between the time you receive the software
and the time you receive the license keys from FRSI, there is a 29-day
grace period following installation of the CDOS software during which
period you are granted the use of one Control Desktop, one Control
Designer, and one Display Designer license.
Following the expiration of the 29-day grace period, the Control Desktop
grace period licenses are no longer valid and Control Desktop ceases to
function, except that you can run Control Desktop to request licenses.
The license management selections are located under the top-level
Admin option in Control Desktop.
When the keys are faxed or e-mailed to you, you can enter the details to
activate the license keys and use the software beyond the 29-day grace
period.
The same general procedure is used when you need to add new
licenses due to increases in nodes, changes of Ethernet cards, adding
new hardware, and so on. The licensing process provides the following
types of license requests:
J Initial Licenses
J Additional Licenses
4
4.3.2.1 Requesting Initial Licenses
If you are requesting licenses for the first time for your new installation,
you should provide the following information:
J System Name — Enter the name you wish to call your system.
With these numbers, you inform the FRSI license generation group
the number of concurrent Control Desktop licenses you wish to run.
With these numbers, you inform the FRSI license generation group
the number of concurrent Control Designer licenses you wish to run.
4 J Display Designer Total Licenses, Change From — The current
number of Display Designer licenses in your system.
With these numbers, you inform the FRSI license generation group
the number of concurrent Display Designer licenses you wish to run.
Note ... Make absolutely sure that you fill in the Return Info Fax field
with the fax number to which you would like the license
activation keys sent. Also, make sure that you select the correct
world area in the To field. The world area is selected from a
drop down list containing FRSI Response Center (North
America or Europe). This action makes sure that you get the
correct Response Center fax number printed on the new 4
hardware license request form.
You may activate license keys when you receive the keys by fax or email
from the FRSI Response Center to you.
You will have to supply the requested information that appears on the
licensing window:
To view license status, select Admin --> License Acquisition from the
Control Desktop main menu.
Figure 5-Table 5
5 5 Navigation
There are several ways to navigate in ENVOXr Server and Control
Desktop software. Navigation in ENVOX Server and Control Desktop
software is based on a Windows-like explorer system. The information
that appears in each window depends on your location in the Explorer 5
structure and on which information you have selected for viewing.
ENVOX Server and Control Desktop navigation tools and window types
include:
J Explorers
J Toolbar Buttons
5.1.1 Explorers
The Explorers that are found in Control Desktop include the following:
J System Explorer
J Resource Explorer
J Controller Device I/O (an internal explorer imbedded within the Plant
I/O Explorer or a Controller Item Detail window)
In the left-hand pane, you can select only single items. In the right-hand
pane; however, you can select multiple items using the Ctrl and Shift
keys in conjunction with a single mouse button click.
J Manage Items
J Copy Items
J Move Items
J Delete Items
J Select multiple items by using the mouse and Shift or Ctrl Arrow Key
combinations for deleting, moving, targeting, and copying.
J Print
5
J Refresh Branch
When you launch Control Desktop, the system automatically opens the
System Explorer. The System Explorer provides functions and contains
restrictions such as the following:
J The root expands to show the available Sybase servers for the PC
client.
J You can use the System Explorer to expand and explore servers and
databases down to the device level.
J With the System Explorer you can browse the system, but you
cannot modify any item data. You can also use the System Explorer
to launch the Resource and Plant I/O Explorers for all devices or with
a selected device in context.
You may use any of the following configuration functions when you have
the Resource Explorer open and active on the desktop:
J Items
J Move Items
J Copy Items
J Delete Items
5 J Associate a User Definition, PMA, or Display Console Global Item
with a Console
J Target Points
J Create an IST
The device types at the top of the tree are the following:
J CHIP devices
Expanding this level displays the devices of the selected type in the right
pane of the Explorer — these are categorized into Global and Devices
items for Consoles and Controllers.
All devices are displayed along with their highway address where
configured. The list is ordered such that device tags are displayed
You may use any of the following functions when you have the Plant I/O
View open and active on the desktop:
J Create an IST
J Print
You cannot delete configuration information from the Plant I/O Explorer.
To delete an item, use the Controller I/O Explorer that you access from
within this Explorer.
The Explorer relationships that are provided in the Plant I/O Explorer are
as follows:
J All Controllers
You can launch the Controller Device I/O Explorer either by selecting the
I/O icon when the Item Detail window for a specific controller is open or
from the Plant I/O Explorer for a particular file, card or channel.
You use this Explorer and its Item Detail View to navigate and configure
a single Controller’s I/O using an Explorer.
J Move I/O data within the controller, file to file, card to card, or channel
to channel
J View the different I/O data for each type of I/O card you select in the
left-hand pane
5.1.2 Menus
Menus allow you to select a specific option with your mouse. In a menu
name, the highlighted letter indicates the character you may use to
select that menu if you wish to use your keyboard and not the mouse.
Menu keys are displayed in the menus on the menu bar and on the
pull-down menus.
Many modules and utilities have menus as well. In some cases the
menus that appear and the options available on menus depend on the
current sate of the application, module, or utility you are using.
J Drop down menus for each of the top level options arranged across
the top of the ENVOX Server and Control Desktop System Explorer
window
The choices on the drop down menus are either operable or not,
depending on the task you are doing. Inoperable choices appear dim
and cannot be selected. 5
ENVOX Server and Control Desktop menus, described below, appear in
the following format:
J Top-level Menu
J Pull-down Menus
J Toolbar Icons
You may use the right mouse button (reverse these buttons if you
configure your mouse for left-hand operation) when the selection of a
menu option or function is better done from a mouse button. Clicking the
right mouse button displays a context menu for the current level or
function in which you use the button.
J You want to create a device, point, card, channel, block, or card list
5 when you are working within an explorer view
J You want to delete a point, card, channel, block, or card list when you
are working within an explorer view
J You want to edit an item type when you are working within an
explorer view
This list of examples is not all inclusive. There are menu options that are
operational from the context menu alone. In some cases, ENVOX Server
and Control Desktop software offers more than one choice for choosing
menu options. Context menu use depends on the user’s preferences.
Depending on system settings, you can position the cursor over each
toolbar icon to display text that explains the ENVOX Server and Control
Desktop and function provided by the toolbar.
these modules and utilities also have help files available to them from
within Control Desktop or as standalone files.
J Modules
J Display Designer
J Utilities 5
J Client Administration
J Server Administration
J Server Setup
J Task Monitor
J Books Online
J View PDF
J Modules
J Control Designer
J Display Designer
J Report Writer
J Utilities
J Client Administration
J Server Administration
J Upgrade Devices
J Generate
J Download
J Download Backup
J Upload
Task Monitor
5 J
J Populate HACL
J Give users access to a database and define what the user can do
with the database information.
J Windows with tabs and entry fields, and message boxes that ask for
an action or convey information or warnings about an action you
have initiated.
5
All of these are available to you when navigate in ENVOX Server
Administration to perform administration tasks.
J Give users access to a database and define what the user can do
with the database information.
J Windows with tabs and entry fields, and message boxes that ask for
an action or convey information or warnings about an action you
have initiated.
All of these are available to you when you need to navigate Client
Administration to perform administration tasks.
Figure 6-Table 6
management task. There are several different tools you use to navigate
to or select and manage items:
The remainder of this section explains each tool and how to use it.
6
6.1.1 Introduction to the Item Detail Window
The Item Detail window is actually a set of tabbed windows, one window
for each item type. Depending on how you are navigating and the task
you are working on, you can open the Item Detail window in any of
several ways. Three examples are:
J By selecting File --> New or File --> Open from the Control Desktop
main menu
J By selecting Tag Data from the context menu when a tag is selected
in an Item Detail window.
See subsection 6.2 for more information on using the Item Detail
window.
J Copy Items
J Move Items
J Delete Items
J Target Points
J Selection of multiple items with the mouse and Shift or Ctrl Arrow Key
combinations for deleting, moving, targeting, and copying
J Switch databases
J Micro Help line (status bar), which gives you one line help information
for the configurable fields within item configuration
J Controller point types: AI, AO, DCD, DI, DM, DO, EPCI, Group, LCP,
PCI, PDO, Unit
J Instrument signals
J CHIP points
J Loop points
See Section 9 of this manual for more information on using Excel Matrix.
J Create an item
To create a new item, select File --> New from the Control Desktop main
menu, the New Item dialog opens as shown in Figure 6-2.
Select a type from the pull down menu. For example, Figure 6-3 shows
the Item Detail window that opens if you select AI. The Item Detail
windows for other item types have different tabs and different fields.
After the window opens you can enter information in the fields on the
tabs of the window to complete the configuration of the item.
If you created a controller, you must also edit the I/O data:
Step 1: With the Item Detail window for the controller selected, select
Data --> I/O Data.
Step 2: Navigate to and select a card whose I/O you wish to change.
Step 4: Enter I/O data and click OK to save the data and close the
dialog. 6
6.2.2 Create an Item from an Existing Item
Step 1: Select File --> New from the Control Desktop main menu.
The Create From dialog appears, listing all the items currently
in the database.
The Item Detail window opens. The window title bar indicates
this is a new item created from an existing item. The window’s
fields are filled with the existing item’s data.
Step 6: Enter the tag you want to save the item as and click OK.
The Item Detail window uses a tabbed format; clicking a tab reveals the
data fields related to the tab. You may move between tabs in any order.
When you select a field on a tab, the Help line at the bottom of the
screen provides a brief description of the field. Clicking the Help icon in
the sheet Toolbar displays further information about the current Item
Detail window.
If you have made changes but not saved them, you can revert to the last
saved version of the window by selecting Data --> Retrieve Data.
The only information about targeting for the item that is displayed on an
Item Detail window is a list of the currently targeted devices and the
index number of the point in that device. This information is read-only.
You can view the targeting information using the Matrix view.
Signal data for points that have instrument signals associated with them
are not displayed on the Item Detail windows. You can access signal
data using the context menu Tag Data from the Signal Tag field within
6 the point and from the Instrument Signal Matrix display.
Step 1: Select an item type folder in the left pane of the Resource
Explorer, as shown in Figure 6-5.
Control Desktop opens the Item Detail window for a new item
of that type.
To create an item with the fields filled with information from an existing
item:
Step 1: Select an item tag in the right pane of the Resource Explorer,
as shown in Figure 6-6.
If you create a point using the New option in the context menu in the
explorers, the source device is filled in automatically.
Use Move in the context menu when you have displayed the tag level in
the right-hand pane of the Resource Explorer and wish to move one or
more items. Selecting Move from the context menu opens the Move
dialog.
To drag ’n’ drop an item from one device tag to another while in the
Resource Explorer, simply drag the selected item onto the destination
component.
To move an item from one device tag to another using drag ’n’ drop:
Step 1: Display the Resource Explorer and display the tag level in the
right-hand pane.
Step 2: Click and drag the item to be moved onto the new location.
The following shows the function that you are initiating and the action or
results that occur when you use the listed Drag ‘n Drop functions.
J Move Item — Select item in the right pane and drag it onto another
device component in the left pane while holding the Ctrl key down.
J Target Item to Device — Select item in the right pane and drag it onto
a CONSOLE, CHIP or UOC device component in the left pane while
holding the Shift key down.
Note ... If you delete an item that has references to it elsewhere in the
system (for example, an AI point which is referenced by an
Operation and a Display), the rest of the database will still refer
to the deleted tag. If you then try to rename another point to the
deleted tag, it is not allowed because those references still
exist.
J Move — Hold the Ctrl key down and drag the item onto destination
component
J Target — Hold the Shift key down and drag the selected item onto
destination component.
Moving file-card-channel data removes the data from the source location
and transfers it into the destination location. You can move
file-card-channel data in the Plant I/O Explorer using one of several
methods:
J Delete an Item
The File --> New top-level menu option is not applicable to the Matrix
view. Create a new item in the Matrix view by adding a new row in the
matrix and assigning it a tag.
When within a Matrix View, you can create a new item only of the same
type as the current Matrix view. (The AO Matrix view can be used to
create AO and FIELDVUEr AO points and the CHIP Points Matrix view
can be used to create any CHIP point type.) New items can be added
using the Duplicate Row(s), Insert Row and Default Row Values, and
Default Tag features.
If you want to create several new rows in a matrix view that have most of
the same basic details as another existing row, or you want to override
the current settings of several rows with the settings of an existing row,
then use the default tag facility.
Step 1: Click Matrix in the Toolbar. The Matrix — Data View dialog
appears.
Step 2: Select the type of Matrix view in the drop down on the Matrix
— Data View dialog. 6
Step 3: To display an empty Matrix view of the selected type, leave
the Retrieve All Rows for the View check box blank.
The default tag row has a tag icon in the third column of the row. If you
change any of the settings for the default tag, then the icon’s
background changes color to indicate that the tag’s settings have
changed but have not been saved. If you copy its settings to another
row, then the row’s current settings are copied, not the saved settings.
To copy a default tag’s settings to another row, select the row, then
select Default Row Values from the context menu. The selected row’s
cells are filled with the values from the default tag’s row.
If you have not saved the Matrix view, you can revert a row to its saved
values by selecting the row, then selecting Reject Update from the
context menu.
You can create a new item of the same type as the current Matrix view.
New items can be added using the Duplicate Row(s), Insert Row and
Default Row Values, and Default Tag features.
Step 1: Highlight a row at which you wish the insertion to take place in
an active Matrix view with a left mouse click on the row index
column.
Step 2: Select Edit --> Insert Row in the top level menu or Insert
Row in the right mouse menu.
Step 3: The system inserts a new empty row in the Matrix identified
by the NEW icon.
6
Step 4: Enter new information at this point or use data from an
existing row.
Step 1: Highlight the desired row(s) that you wish to duplicate with a
left mouse click on the row index column.
Step 2: Select Edit --> Duplicate Row(s) in the top level menu or
Duplicate Row(s) from the right mouse menu.
Step 3: A new row appears below each highlighted row and contains
the parameters of the highlighted row. The New icon appears
in each new row.
Step 4: Enter a point name for each new row. Modify any fields in the
row as necessary.
Step 1: Highlight the row that you wish to use as the default row with
a left mouse click on the row index column.
Step 2: Select Data --> Set Default Tag in the top level menu or Set
Default Tag in the right mouse menu to identify the tag of the
item that will be the basis for the default row information. The
tag will not be carried to the newly created row because that
would be a duplicate.
Step 3: Select Edit --> Default Row Values in the top level menu or
Default Row Values in the right mouse menu to specify the
data that carries over to the newly created row.
Step 4: Select Edit --> Insert Row in the top level menu or Insert
Row in the right mouse menu to create a new row.
Step 5: Highlight the new row and select Edit --> Default Row Values
in the top level menu or Default Row Values in the right
mouse menu. The new row is populated with the values from
the default row.
Step 6: Enter a point name for each new row. Modify any fields in the
row as necessary.
To edit items in a Matrix view, click the field you want to change.
Step 1: If the field contains a drop down list of values, the list
appears.
Step 2: If there are tag values associated with the field, click Tag
Values in the right mouse menu.
Step 3: Refer to the Help line at the bottom of the window for a brief
description of the field, including value ranges where
appropriate. Click Context Help in the Toolbar to open further
information about the current Matrix view.
Step 4: Use the right mouse menu to copy, paste, and delete field
values.
Step 5: When you are finished making edits, select Data --> Validate
(or click Validate in the Toolbar) to make sure that all field
values are within range and no required fields are empty.
If you have not saved the Matrix view, you can revert a row to its saved
values by selecting the row, then selecting Reject Update from the
context menu.
Step 1: Highlight the row(s) containing the item(s) you want to delete.
Step 2: Select Delete Row from the right mouse menu. To restore a
deleted row, select Edit --> Restore Deleted Row.
To save changes you have made to a Matrix view, click Save in the
Toolbar.
You must specify the location and file type to which the data will be
saved as shown in Figure 6-7.
Note that though you can save to several different formats, the only
formats that Matrix view can load are tab-delimited *.TXT files and dBase
format *.DBF files.
You should provide a name for the file and specify the file type. The file
is written in the specified format to the specified location.
You can load data from an external format into a Control Desktop Matrix
view. For example, if you have exported the Matrix view data and edited
it in an external application and you wish to return the changed data to
the database. The data file must be in the tab-delimited text (.TXT) or
database (.DBF) format. If you are using another application, for
example Excel, then save (or export) the file in tab-delimited text format.
Figure 6-8. Finding the File for Loading from External Format
You cannot delete items by loading (importing), though you can overwrite
item settings. If there are any items in the database that are not included
in the import, they are left in the database intact. If you have removed
data from a particular field before reloading the data into Control
Desktop, the value for the field is returned to the value in the database.
In addition, no target data information is changed during an import of
source points — an import activity does not delete any target data.
If there are problems with the file being loaded, you are prompted. For
example, if the following message is displayed, there is a basic error (for
example alphabetical characters in a numeric-only field):
You can select Yes to continue the import, or No to stop importing and
locate the error in the other application.
You may save each customized Matrix view. You may also restore the
revised Matrix to a standard Matrix view. Customized Matrix views load
automatically when you specify that you wish to see the customized
Matrix.
J To set the data selection criteria for your custom grid, select the Data
6 --> Set Criteria option in the top level menu, or click the Set Criteria
icon in the left Toolbar.
When you save your custom grid, the query is saved with it. Then,
when you open your custom grid, the query runs to select the range
of data to be automatically included in the Matrix.
J To sort the entire matrix view, click the column header that contains
the sort criteria.
J To change the order of the columns, click and drag the column
heading to a new location.
Step 1: Click and hold on the dividing line to the left of the column
heading whose width you want to change. The cursor
changes to a two-sided arrow.
Step 2: Drag the cursor to the left or right to the desired column width.
Step 3: Save the customized view by selecting Format --> Save Grid
Definition.
Enter the applicable data for the fields. If the Destination Tag already
exists, it must be of the same type as that specified by the Source Tag.
You may select an existing tag as the source, destination, instrument
signal, and/or a point’s target data for the copy operation from a list of
items displayed by the Tag Values option of the right mouse button or
the Data option of the top-level menu. When copying points, you can
specify an Instrument Signal Tag to be copied to the destination tag. You
may also specify whether the Point’s Target data is included in the copy.
The Copy Items option let you reuse existing data in several ways. The
options can:
remains in the source location. You can copy file, card and/or channel
data in the Plant I/O Explorer using one of several methods:
This subsection refers to the item you are copying to as the destination
and the item from which you are getting data as the source.
J Target Data — the system copies the target data when you check a
checkbox on the Copy Item window window.
J PPA Number — The PPA number on the PPA Definition form must
be unique throughout the system. The software sets this field to null
in the destination item.
J Pen Recorder Data — Any pen driver specified in the Console Pen
Recorder List form can only be specified as a pen driver once
throughout the system. The software does not copy any pen recorder
information to the destination item.
J Console Device Redundancy fields — The system does not copy the
Secondary Console and Parent Console field values to the
destination device. The software sets the Clone field in the
destination device to NO.
J For a PPA definition, the software copies priority tag data with each
state name.
J For group templates, the software copies DCD setpoint data with
each group setpoint.
The Copy Item option copies group field data to the destination as they
appear in the source.
items in the tag set into the fields. If you then use UOC1-A01 in the Copy
from field, the software copies the data configured for UOC1-A01 to
UOC2-AO1, UOC2-AO2, UOC2-AO3, and UOC2-AO4.
J Copy Item does not copy the highway address. You must modify the
new console device definition to specify the highway address.
6 J The Copy Item option does not copy hosted points such as activities
and accumulations, but will target these points to the new console.
The following items are copied from the parent console to the clone
console and cannot be re-defined separately:
J Shift Table
J PMA List
J Reports List
The following items are not copied from the parent console to the clone
console. You must define them for the clone as required (not all items
apply to both PROVUE and Operator Workplace consoles):
J System Clock
J Horn Tones (valid for WPCON, and PROVUE P5.3 or later consoles)
The console you make into a clone must be similar to the parent
console. That is, if the parent is a P5.x console then the clone must be a
P5.x console. If the parent is a WPCON console, the clone must be a
WPCON console. The database size of the clone console must be equal
or greater in size to that of the parent console.
It is not possible to clone one redundant console pair from another. That
is, a primary console cannot be a clone of another console. Also note
that a simplex console cannot be a clone of a primary or secondary
console in a redundant console pair. When cloning simplex consoles, it is
not possible to have a parent console be a clone of another console. It is
possible however to have multiple simplex clones of a single parent
simplex console.
When removing a clone from its parent, all items that were cloned from
6 the parent console no longer exist in the clone, so the clone console is
no longer functional. The duplicated items must be re-entered for the
previously cloned console. To remove the cloning relationship between
two consoles but keep the same configuration on the clone, delete the
clone console from the ENVOX database. Then use Copy Item to
recreate the console just deleted.
Deleting a tag set from the Delete Items window lets you delete all the
items in a tag set or the tag set only, depending on your choice of option.
If you enter the tag of a tag set, you are asked if you want to expand the
tag set. You have two choices and the result depends on these choices:
J If you choose Yes, the tag set is expanded and all items in the tag
set are deleted, but the tag set itself is not deleted.
J If you select No, the tag set tag is deleted, but the items in the tag
set are not.
Note ... Renaming an item locks the database to prevent other functions
from writing to the item. Functions like generate and download
cannot start until the rename is complete. Renaming more than
a few tags can take a long time. Therefore, renaming multiple
items should be done when no other users are using the
ENVOX database.
The Rename Item dialog window appears when you select Application
--> Rename Item. The Rename Item dialog contains the following fields:
J Destination Tag — Enter the destination tag, i.e. the tag’s new
name.
You must enter the Source Tag. You can click Tag Values from the
context menu to select a tag. Next, enter a unique name for the
Destination Tag for the tag you want to rename. When you click the
Rename button, .the software displays a confirmation dialog box
informing you that the job you requested has been submitted, and
showing the job number.
When the item is renamed, the previous tag no longer exists in the
database and so can be reused.
Note ... If you delete a point that has references to it elsewhere in the
system, such as in operations, FSTs, procedures, reports, and
UDKs, you cannot rename another item to that tag while those
references still exist.
You can rename an item from the command line in a DOS window with
the following command:
where
Old Tag and New Tag must not be supplied if running in recovery mode.
Caution ... Renaming via the command line interface includes a check for
valid tag names. If an invalid tag is entered, an appropriate error
message is displayed. You must not create a command file in
an attempt to perform multiple item renames. If such an attempt
is made, and the rename fails, the database may be left in an
inconsistent state. To rectify this situation, the cause of the
rename failure must be first ascertained, and then the
rename_tag.exe utility must be run from the command line in
recovery mode before any further attempt is made to rename
another tag. 6
Note ... If you delete an item that has references to it elsewhere in the
system (for example, an AI point which is referenced by an
Operation and a Display), the rest of the database will still refer
to the deleted tag. If you then try to rename another point to the
deleted tag, it is not allowed because those references still
exist.
You can select one or more points and drag and drop them onto the
device you want to target them to. You can also select one or more
points, then select the Data --> Target To menu option. A dialog
appears on which you select the target device.
Regardless of the method you use the Target Data form appears as
shown in Figure 6-10.
On the Target Data form enter the various target parameters such as
reporting mode, deadband, and so on.
You can target points using Target Matrix views. There are three
Target Matrix views available, one for each type of target device
(Console, CHIP, and UOC). Figure 6-11 shows a Console Target
Matrix view.
If you are targeting a point to multiple devices, you enter one line in
the Matrix views for each device the point is targeted to.
ISTs provide you with the flexibility to log instrument signal data
independently from point and logic configuration. ISTs link PROVOX
points to their I/O signals and define the characteristics for each signal.
The characteristics are:
J Strategy
J Signal type
J Card number
J Channel number
J Alarm values
J SMART variable
More than one IST can reference the same signal source; that is, the
same file-card-channel (F-C-C). Thus, you can specify different alarms
and ranges for the same I/O signal—a useful feature when defining
points that reference the same signal data but require unique alarm
values. Modifications to one IST have no effect on other ISTs referencing
the same signal source. However, modifying IST data does affect
multiple points referencing that IST.
You must use ISTs to configure PROVOX points. Even points with
pseudo I/O have F-C-C, engineering units and ranges associated with
them and, consequently, require ISTs. Points cannot be generated
successfully without configured ISTs.
When the validation process is complete, the Validation Log for the point
appears only if there are any validation messages or errors. The Validate
window also appears when you Save, if the item being saved has errors.
Figure 6-12 shows the appearance of the Validation Log for a point.
Figure 7-Table 7
7 7 Tag Sets
Tag sets are user-defined groups of tags on which the ENVOXr Server
and Control Desktop software can perform functions, such as Report
Writer, generate, and download. These can be easily defined and
maintained in various ways from various places in Control Desktop.
A special type of tag set is available and is called a Tag Base. The tag
base is essentially a scratch pad of tags that you can use instead of
having to make notes on paper to list tags that you later want to add,
investigate, update, delete, etc. 7
Control Desktop groups items in Explorers, matrix views, and so on, in
logical collections normally based on the type of item or device.
However, you may want to investigate or work on tags that are not
grouped by Control Desktop; for example, by an area of your plant. You
can use Control Desktop to group these items together into tag sets.
There are many methods and many places in which you can use tag
sets within Control Desktop. This makes the way you create, maintain
and use tag sets very flexible, in order to suit your needs.
The ways you can use tag sets include the following situations:
Tag sets can be created and updated in many different ways within
Control Desktop, such as:
Control Desktop does not support the ENVOX Fixed Attribute Criteria tag
sets, as these are superseded by the use of SQL. Neither are ENVOX
Adhoc tag sets supported — those that start with an ’&’ and were
created in ENVOX software when you saved generation errors to a tag
set (tag set name is ’&username’).
Tag sets help optimize productivity because they allow you to execute
configuration functions on a group of items. For example, you can use
tag sets to:
J Report Writer — When you use the Report Writer module, you may
use a tag set to specify which items you want a report to include.
J Delete items — When you wish to delete items, you may enter the
name of a tag set. The software displays the items in the tag set so
that you can review the items and decide whether to delete them.
J Generate — You can build the list of devices that you want to
generate by specifying a tag set. The software includes the devices
represented by the tag set in the Generate option.
J Copy all the data from one point to another — When you select the
Copy Item menu option, you can copy all the data (except IST data)
in an existing point to the points in a tag set, thereby creating a new
set of points.
J Create a tag base from the tag set — There is an option on the
Startup tab on the Control Desktop Options dialog which makes
Control Desktop create a tag base based on a specific tag set when
you log in.
J The standard Item Detail window — You can use this window to
define the tag set’s details, including the type of tag set (No SQL,
Static SQL or Dynamic SQL).
J From the Task Monitor — You can create a report that contains all
the devices that have generation errors, then use the Save To Tag
Set... button on the report to create a Tag Set containing the items
that prevented a successful generation.
J From within Report Writer — After you have created a report and
have a list of tags in a report on the screen, you can create a tag set
for these tags.
J After an audit trail search — When you are viewing the history
summary of an audit trail, you can create a tag set of the listed tags.
J From a tag base — Which can have tags added to it from many
places in Control Desktop — almost everywhere tags are displayed.
For example, you can add items to a tag base from Explorers and
from item detail windows.
You can modify a tag set or the tags in a tag set as well as delete tags
and tag sets. Use the tag set’s Item Detail window, the menu option for
Tag Set to open the tag set that contains those tags you wish to modify
or delete. If you delete tags, you do not delete the tag set.
You must be careful when using ISQL to insert the row; if not done
correctly, the integrity of the configuration data can be lost. Contact your
system administrator for instructions before attempting to use ISQL.
J A tag set’s row cannot be updated from one tag set to another.
J A row cannot be inserted for a new tag set such that the tag of the
new tag set already exists in the database.
When you decide you want to add tags to an existing tag set, bear in
mind the rules shown in Table 7-1 on what is the result of trying to
append tags in one tag set type to tags in another.
Although some tag set types cannot be appended to, all tag set types
can be overwritten.
However, while Control Desktop does not generate pattern tags, they are
included in the error and limit checking functions that are also performed
by Control Desktop. Therefore, to avoid errors when generating and
downloading devices, do not include the name of the pattern tag that is
being modified.
If you want to fill in a tag window with pattern-tag data, use the Copy
Item menu option. See the online help files for additional details on the
Copy Item menu option.
Figure 8-Table 8
8 8 Logic Editor
The Logic Editor is an integrated language editor that you use to create
and edit the following types of logic items:
J Procedures
J Operation Steps
J Console reports
Launch the Logic Editor from one of these items by selecting the
appropriate selection from the Data menu. For example, after opening
an LCP FST, select Data –> Edit FST. To create a new item, select File
–> New, then enter or select the item type to create.
Control Desktop allows you to have several Logic Editor sessions open
on your desktop at the same time. This includes Logic Items of different
types. You can copy and paste information between windows of the
same type.
The basic way you use the Logic Editor to create a list of instructions is
the same for all items, but the instruction set depends on the item.
Creating and maintaining the instruction list comprises:
J Adding Instructions
J Editing Instructions
The instructions that you use to create these sequences are different for
each item type and are not described in this section (except for the
console reports editor). For information about specific instructions, refer
to the configuration engineering manuals for the controllers and operator
consoles or the online help for the Logic Editor.
This section describes how to access the Logic Editor, use the editor to
enter and save instructions, and use the various editor features such as
cut and paste and find and replace.
The editor works the same for all logic item types. Keep in mind,
however, that you can only use the instructions for the sequence type
you are currently editing. For example, if you are editing an FST, you
cannot use console report instructions.
Step 2: Select the Processes or Steps tab and click on the Process
or Step you wish to edit.
8 Step 3: Select Data --> Edit Process (or Step).
Step 2: After the LCP FST Item Data Window is open, select Data -->
Edit FST.
8.1.3 Reports
Open the Console Report (File --> Open). The Logic Editor opens the
report instruction data.
Open the Conditional Text/Expression (File --> Open). The Logic Editor
opens the conditional text/expression instruction data.
Begin typing instructions on the first line in the editor. If you do not know
the complete mnemonic, enter the first few letters and press Return. The
system either:
J Completes the instruction and opens the instruction for editing, if only
one instruction matches the letters you typed. For example, if you
enter CAC in the operations language editor, the software completes
the instruction by adding QUIRE so that CACQUIRE is displayed.
J Displays a list of all valid instructions that start with the characters
you typed. For example, if you enter AD, the software displays ADD
and ADVREQ. Select the desired instruction and click OK to accept it
and close the dialog, or click Cancel to exit the dialog.
If you do not know which instructions are valid, you can find a list of valid
instructions in the online help for Control Desktop. To see a list of valid
instructions, move the cursor to the [End of File] marker, enter ?
(question mark), and press Return.
displays a prompt for each operand that the instruction requires. For
example, if you enter the mnemonic ADD when editing an operation, the
software displays the expanded instruction in Figure 8-1.
J Operand prompts — The prompts for all of the operands required for
this instruction.
J Status Line — The Logic Editor uses the Control Desktop Status Line
to present brief information about the current state of the editor and
to prompt for the information the editor expects at the current cursor
location.
Enter data at the operand prompts. If you enter an invalid operand, the
software displays an error message in the error box that describes why
the operand is invalid.
When you are done entering instructions, save your instruction set.
After entering instructions in the Logic Editor window, you may need to
edit them in some way. There are facilities available to let you:
J Edit an Instruction
J Delete an Instruction
J Disable an Instruction
J Enable an Instruction
J Indent an Instruction
J Suppress Warnings
Step 5: Move to the point in the first instruction set where you want to
insert the instructions you copied.
Because you can copy and paste between Logic Editor windows, you
can create one or more instruction sets that contain commonly used
instructions or combinations of instructions. You can use these
instruction sets as libraries, copying blocks of instructions from them to
instruction sets you are creating.
Note ... Use register names with caution in instruction sets you use this
way because register names may result in invalid register
references or indices when pasted into the second instruction
set. The editor will not give any warning message to this effect
following an include.
To write a comment when all instructions are closed, position the cursor
at the desired point and select Insert Comment from the context menu.
The Comment Edit window opens. Enter your comment and click OK.
The Logic Editor inserts the comment with opening and closing brackets.
You can perform some simple formatting (inserting blank lines and
limiting line lengths using returns) in the Comment Edit window. Note
that the Logic Editor window ignores leading spaces entered in the
Comment Edit window. To retain indenting in comments, start each
comment line with a non-space character. For example:
J instructions
Step 3: Move the cursor to the desired position and select Paste from
the context menu.
Step 2: Use the cursor to select the desired text and select Cut or
Copy from the context menu.
Step 3: Select Paste from the context menu to paste this text
elsewhere within this comment or in another comment within
this instruction set or another instruction set. The paste buffer
retains its contents until you cut or copy something else into it.
You can therefore copy or cut once and then paste the same
text multiple times.
The Find tab of the Find and Replace window has two functions:
Step 1: Position the cursor where you want to begin the search.
Step 4: In the Search String field, enter the string you want the
software to find. If desired, select the Match Case checkbox.
Step 5: To start the search, click Find Next. The software finds the
first occurrence of the string, if any. You can skip to the next
8
occurrence by clicking Find Next. To abort the search, click
Cancel.
Step 1: Position the cursor where you want to begin the search.
Step 5: To start the search, click Find Next. The software finds the
first incomplete instruction, if any. You can skip to the next
occurrence by clicking Find Next. To abort the search, click
Cancel.
Step 1: Position the cursor where you want to begin the search.
Step 4: In the Search String field, enter the string you want the
software to find. If desired, select the Match Case checkbox.
Step 5: In the Replace String field, enter the text you want to
substitute for the string you find.
Step 6: To start the search, click Find Next. The software finds the
first occurrence of the string, if any. To replace, click Replace.
To replace all occurrences, click Replace All. You can skip to
the next occurrence by clicking Find Next. To abort the
search, click Cancel.
8
The software checks instructions after you replace operands. If it finds
errors it asks if you want to continue. It does not replace operands that
will result in an error.
To view the list of valid language editor instructions that are specific to
the type of logic sequence you are editing (FSTs, operations, and so on)
make sure the cursor is not on an instruction, then press the Shift F1
key combination. A list of all valid instructions appears. To see detailed
help, click on an instruction of interest.
Validation Complete
0 Errors - FST size = 326 bytes.
If an error is found, that is, if the referenced data is not there, the system
displays an error and returns to the instruction editor. Incomplete fields
are not considered to be errors, so you can save incomplete instruction
sets and return to finish your work later.
If you did not select the Check References Before Save option, the
software checks only the syntax (overlooking reference errors).
Selecting File --> Close prompts you to save your data if you have made
changes.
As you scroll through the generation errors with the arrow keys, the
cursor in the Logic Editor moves to the instruction that caused the error.
Note that the generation errors are a snapshot of the Logic instructions
that caused errors at the time of the generate. Therefore if the logic
instructions have been modified since the last generate, the generation
errors instruction numbers may no longer be correct.
The basic instruction that you use to build a report is LAYOUT. When you
enter the LAYOUT instruction or select Insert Layout from the context
menu, the editor opens a text editing field in the editor window.
The layout field provides a working area for positioning the text and other
data you want in the report. A report line can include as many as 132
characters. The normal editor window displays only the first 101
characters of the line. To view the full 132 characters go into Edit Full
Screen mode and resize the editor window. The editor does not wrap
lines since it attempts to show what the report would look like when
printed.
The next step is to identify the text you want printed (if any) and to create
a placeholder for your data. Figure 8-3 shows an example layout field.
To exit the layout window, press the Return key. If you enter the
information shown above, the editor reads your text string and data
placeholder and automatically opens the Edit Layout Print Attributes
dialog. Figure 8-4 shows the dialog that results from the example in
Figure 8-3.
You can reopen the dialog by placing the cursor at the beginning of the
layout field (not in the field) and then selecting Layout Print Attributes...
from the context menu.
Note that the software creates one row in the Layout Print Attributes
dialog to support each data place holder you put in the layout field.
The following paragraphs describe the values that can be put in the
three fields of the dialog:
J Print Item — Identifies the type of report item that you want printed.
Selections are:
J The keyword TIME DATE. This calls the actual time and date into
the report from the system clock.
J The keyword PHRASE followed by: phrase list name. This prints
the next phrase in the list.
For example:
To print the alarm history of point ACT 121, the instruction would read:
To print the change history of point ACT 121, the instruction would read:
NEXT — Selects the next element of a point list or phrase list for use by
PRINT instructions.
UNTIL END — Marks the end of a series of instructions that begin with a
REPEAT instruction. The instructions between the REPEAT instruction
and the UNTIL END instruction repeat until the system reaches the end
of the point list or phrase list. Include a NEXT instruction in the loop to
step through the list.
J FORM FEED — Advances the paper to the top of the next page.
At any point as you create your report, you may want to see how it will
look when printed. To preview a report, select Report Preview from the
context menu. The software displays the report in a window that
approximates the layout of the report.
J LAYOUT field
J REPEAT instruction
J UNTIL instruction
8 J blank lines
You can edit the LAYOUT fields in the preview view. To return to the
editor, select Report Preview from the context menu.
8
Figure 8-5. Example Report in Edit Window
Figure 8-6 shows the Edit Layout Print Attributes dialog associated with
the LAYOUT fields:
Figure 8-7 shows how the example report appears in the preview
window.
J You can print any Logic item’s instruction data from within the Logic
Editor. You have the option of printing a selection of instructions
J You can print from a logic item’s Item Detail Window. You have the
option of printing all tabs and the logic instructions, or printing the
currently selected tab.
Step 1: Select (highlight) the title bar of the Logic Editor window
containing the instructions you want to print.
For Procedures, Operations and FSTs, you have the option of printing
from the Item Detail window. When you print from the window, a popup
appears and provides the choices for printing:
J Tabs and Logic Instruction data — This option prints the complete
logic data—all the tabs and the instructions.
J Current Tab only — This option prints just the current tab.
Note ... When printing from an Item Detail window, the Logic Editor
always produces a text file of the printed data in the Control
Desktop Temp directory.
\Program Files\FRSI\ControlDesktop50\Temp
Depending on the type of logic item you are printing, the text file created
is one of:
J lcp_fst_data.txt
J operation_data.txt
J procedure_data.txt
The file of a particular type is overwritten each time an item of that type
is printed. If you want to use these files for your own purposes, move or
rename them after printing an item.
Figure 9-Table 9
9 9 Excel Matrix
Excel Matrix is an Excel add-in that you use to configure Loop or
Enhanced DCD (EDCD) points in a Microsoft Excel workbook. Using
Excel Matrix you can efficiently configure large numbers of these points.
9.1 Overview
In early releases of Control Desktop, configuration of multiple points was
provided through the Matrix views in Control Desktop. Unfortunately, due
to their relative complexity, Loop and Enhanced DCD points were
excluded. With release P5.0, that shortcoming is addressed by Excel
Matrix.
J As with Open Database, you can save the workbook to disk for
offline work if it is necessary to stop at a given point and restart the
configuration work at a later time.
The chief advantage of Excel Matrix over the Open Database is that the
interface to the ENVOX database is achieved entirely through Microsoft
Excel, the NT and Windows spreadsheet application. The widespread
use of Windows NT and its associated applications places Excel Matrix
in the familiar Microsoft Excel environment and is a seamless extension
to Excel that becomes part of Excel but contains the essential
connection to the ENVOX server.
You can save the workbook to disk for offline work. Additionally, though,
can write the contents of the workbook directly to the ENVOX Server
database or can perform a select operation to read from the ENVOX
Server database.
Open/Save
File
Load
Excel Workbook
Unload Synchronize
INSTRMNT
Open Database
With Open Database, an Excel workbook was saved to disk and the
resultant file loaded into the Open Database’s tables. These files were
then later merged into the ENVOX database through a populate
operation.
9 9.1.3 Workbooks
There are two workbooks that provide multiple point configurations for
loops and EDCDs. The workbooks provide the capability to:
Control Desktop displays a dialog for you to choose the type of workbook
you want to start, or you can open a previously saved workbook using
the From File field. You can also create a new Excel Matrix workbook
from within Excel. Figure 9-3 shows the dialog that opens from Control
Desktop.
For both Loops and EDCDs, the Excel Matrix workbooks are made up of
worksheets containing configuration data. There are five worksheets
within the Loop workbook and six within the EDCD workbook. However,
there is a fundamental difference between the two workbooks. The
workbook used to configure loops represents a single loop point by a
single row in one of the five worksheets. The workbook used to configure
EDCDs represents a single point in several rows in all of the worksheets.
Excel Matrix does not check if points are defined more than once in any 9
Loop worksheet or the Main worksheet of an Enhanced DCD workbook.
If a point is defined more than once, during a Database update every
definition is written to the database. Only the last definition written
remains in the database. Usually this is the last definition in the
worksheet, but this is not true in all cases. For best results ensure that
you have not defined any point more than once.
Note that it is clearly valid for a point tag to appear in more than one row
of any of the sub-worksheets of an Enhanced DCD workbook (Inputs,
Outputs, Disabled SPs, Conditions, and Actions). Only if more than one
row contains identical values in the POINT TAG and POSITION columns
(of the Inputs worksheet, for example) is this considered duplication. If
duplicates exist, all rows are written to the database during an Update
DB operation, but only the last row written remains in the database.
Both workbooks provide a status column for each item. The status
column is not directly user editable, but is automatically updated as the
points are modified or written to the database. The values in the Status
column affect the operation of Update and Select commands:
J Blank — indicates that Excel Matrix will not ordinarily process this
item during an Update operation
J Modified — indicates that the user has modified the item on at least
one of the worksheets in a workbook. Excel Matrix processes this
J Delete — indicates that the item will be deleted from the ENVOX
database during the next Update operation at which time it will also
be removed from the worksheet.
These are the only values that are valid for the Item Status field. These
values are not stored in the database, but are informational for the user
and are essential to control update operations. The processing for points
varies for each of these Item Status values according to the user’s
specification in the dialog for the Update DB menu option:
J Selected Points — all selected points except those with Item Status
9 of Sample are sent for processing.
J All Points — all points except those with Item Status of Sample are
sent for processing.
Figure 9-4 shows part of the Main sheet of an example Excel Matrix
workbook for EDCD points.
J Create from — creates a new point from the currently selected point
J Delete Item From Spreadsheet — Deletes the selected point from the
workbook, but does not affect the database.
J Delete From DB (on Update) — Marks the selected point for deletion
from the database the next time database is updated
J Set Item Status — enter either Sample or Modified in the Item Status
field for the point
When Excel has been updated with the add-in, there are various
additional menu options (including a new menu Control Desktop) that
provide facilities you can use when you configure Loop and Enhanced
DCD points.
If, during installation, you selected either the full Control Desktop option
or the Excel Matrix option, the Excel Matrix add-in is installed and added
to Microsoft Excel, ready for use. Under unusual circumstances the
add-in file is added to the machine’s hard disk but is not added into
Excel. In this case manual addition of the add-in from within Excel is
required.
The Control Desktop menu is available, though many of the options may
be grayed out. When you start a new workbook or open an existing 9
workbook, the add-in is fully loaded.
There are some situations where the Excel Matrix add-in is not installed
and loaded into Excel. You can tell that this is the case if you cannot see
the Control Desktop menu in Excel. In this case, you need to manually
install the add-in to Excel.
J Where the add-in has been unloaded (switched off) from within Excel
Launch Excel Matrix from within Control Desktop under the View
top-level menu option and select Excel Matrix. Be sure that you have
logged in and are connected to the server and database.
Create a Workbook
9 J
In addition, Excel Matrix provides you with the ability to adjust your
worksheets for the type and quantity of data that you are configuring.
When you start a new configuration project from scratch, part of what
you may need to configure may be Enhanced DCD or Loop items.
To enter new data for Loop or Enhanced DCD points, use the Excel
Matrix add-in to enter a workbook of data, which you will later load into
the ENVOX database. Each time you save your data, the data items
displayed in the worksheet are flagged with Modified in the Item Status
column to indicate that you are entering new data. See the Excel Matrix
Add-in online help file for illustrations of this procedure and detailed
instructions for this task.
When you have finished entering the data and have manually checked
that it seems accurate, you can update the ENVOX database with the
data with Update DB menu option. The data is written to the database.
All rows that are successfully written to the database have the Modified
removed from the Item Status column. Items with problems have an
Item Status of Error. Commands are available through which a
description of the error can be displayed. You can edit the data in order
to correct the problem and then send the corrected data to the database
with the Update DB menu option.
Once the workbook is complete, the user changes the Item Status to
Sample by using the Set as Sample menu option so that configuration 9
engineers can readily identify the workbook as a sample. Any
configuration engineer who wants to create and to configure EDCD
points can use the workbook sample. You can also create Sample items
in your normal Excel Matrix workbooks. The sample items created are
useful in two ways:
The tasks that you can perform with Excel Matrix to transfer data to and
from the database enable you to bring database information into a
workbook so that you can make changes to item information regardless
of the source of your database. You can also examine, track, and correct
errors in the information that you are changing. In Excel Matrix, you can
do the following:
The module displays an icon in the data column headings that displays
comments when you pass your cursor over the icon. These comments
provide the table name and column name of the database column. You
can use this to make sure that your SQL query is accurate.
9 You can then edit the worksheet and save the workbook to disk. The
Item Status changes from no entry to Modified to indicate that the data
has been changed. You should save your changes at regular intervals.
Once you have finished editing, you instruct the module to update the
database. The term Modified is removed from the Item Status of items
that are successfully written. Items with problems have an Item Status
displaying the term Error. For those items that display an error, you can
re-edit the data to correct the problem and then instruct the module to
write the corrected data to the database. As usual, you can save the
workbook to disk for future reference.
You can now check each of the worksheets to make sure the data
seems correct and can update the database with these details.
J Some of the changed points — select only these items. All items are
updates except those with an Item Status of Sample.
J All Points — updates the database with every item in the workbook
except those with an Item Status of Sample
This option may take some time. If it does, then a message may be
displayed “Microsoft Excel is waiting for another application to complete
an OLE application.” Because this process uses the DIAL Service, which
is built on OLE technology, you may need to wait some minutes before
the process finishes.
As in the other situations, you can examine the error messages, edit the
9
items to correct them, write them to the database, and save the
workbook to disk for future reference.
There are a number of tasks that you can do to set up your workbook for
the type and quantity of data that you are configuring. The module lets
you edit a workbook in the following ways:
J Insert a Row
that you can create a new point in the position of your choice in the
worksheet.
If you need to create many points with similar details, you can create
a sample item to act as a template, enter the details into a new item,
and mark the item with an Item Status of Sample.
J Insert a Column
J Delete a Row
Deleting a row from an Excel Matrix worksheet does not remove the
item from the ENVOX database.
J Delete Items
You must select each row that contains data for the items that you
want to remove from the workbook. This operation does not delete
the item from the database — it simply removes it from the workbook
you are editing.
Once you have opened a workbook in Excel Matrix that contains the
items you want to delete, you can select those items and instruct the
module to delete them. It is also possible for you to edit items that
need correction at the same time. When you select the update option
For an EDCD workbook, you can only delete data from the Main
worksheet.
Typically, you can hold data in the User Data columns in order to sort
points.
You cannot change the width of the Loop and Enhanced DCD
worksheet columns in the same way you change standard Excel
worksheets because the cells are locked and cannot be deleted or
altered. Header cells are locked to avoid inadvertent changes that
may prevent the add-in functioning properly.
9
The module provides two ways in which you can change column
widths. You can make the column width fit its contents or change the
column width to a value of your choice. See the Excel Matrix Add-in
online help file for detailed procedures to accomplish this task.
j Delete — this item will be deleted from the database during the
next update. Upon completion, the item is also removed from the
workbook. You can manually set an item to have this status.
J Sort Rows
You can sort the rows on the worksheet into alphanumerical order.
You can choose to sort the items by any column, in either ascending
or descending order. You can carry out a multi-level sort, specifying
up to three sort keys.
J Messages
There are four message menu options that control how you navigate
9 through the messages and errors generated as a result of a
database update:
j Next — takes you to the next message for an item with an error
These menu options are disabled if the active worksheet is not the
Messages worksheet.
Figure 10-Table 10
10.1 Generating
When you have entered all of the configuration data into the database,
you need to send the data to the PROVOXr devices. The Generate
application extracts data for each device from the database and creates
a file that is ready to download to a selected device. The Generate
application also checks for inconsistencies or errors in the data before it
creates the download file.
10
Note ... You need to generate the device each time you modify or add
new data to the device’s configuration. If you do not generate
the device after changing the configuration, the next download
does not include the new data.
J Select the Application –> Generate, option in the top level menu
J Select the Generate option in the right mouse menu when in the
Resource or Plant I/O navigators at the device level
J Select the Task Monitor view from the View option in the top level
menu
If you select Generate from the top level menu, Control Desktop displays
the Devices to Generate window that lets you enter the devices you
wish to generate. In the window:
Step 2: Select the Action –> Submit Job, option in the top level
menu or click the Submit Job icon in the Toolbar.
10
Figure 10-1. Devices to Generate Window
When you select the Task Monitor for a selected device, the system
launches the Task Monitor application and displays generate information
for the selected device.
Once you have generated the download data using the Generate
application, you send (download) the data to the PROVOX devices. You
can choose whether to download information to one or several devices,
download the entire configuration for a device, or download only the
changes to the configuration since the last download (a partial
download).
J Select the Application –> Download, option in the top level menu
J Select the Download option in the right mouse menu when in the
Plant I/O or the Resource navigator at the device level
J Select View --> Task Monitor view from the top level menu
In the first two cases, Control Desktop opens the Devices to Download
window shown in Figure 10-2. 10
Use the window to enter the devices you wish to download. In the
window:
Step 4: Select the Action –> Submit Job, option in the top level
menu or click the Submit Job icon in the left Toolbar.
Step 2: From the list of jobs or tags, highlight the device, or devices.
Task Monitor displays the progress of the job. When the job is
complete, the Task Monitor icon in your Windows task bar and
the Task Monitor title bar flash.
Where:
Note ... The dlexec command also has a /J switch. Do not use this
switch. The Client Task Daemon uses this switch when it runs
this command for Control Desktop.
After you have completed your configuration and have a working set of
download files, you may want to make a backup copy of the associated
configuration download data. Having a backup ensures that you have a
dependable copy of your current configuration.
During the backup, which may take some time, no devices can be
generated. (Devices, can be downloaded, however, both from backed up
or normal download data, providing this is done from another Control
Desktop session.) 10
You can now download from the backup you created, if it becomes
necessary. Refer to subsection 10.2.3 for more information.
Step 3: Enter the device tag names, or click Tag Values and select
the appropriate device tags of the devices you want to
download. (If the device has not been backed up, then a
message is displayed informing you of this. The device tag is
grayed out in the list.)
If you have selected a tag set, the Devices in Tag Set dialog
is displayed, showing the tags referenced by the tag set.
Select the ones you want to include in the download.
Step 5: When you have finished selecting devices, click the Submit
Job icon on the toolbar, or select Action --> Submit job.
You can review the status of the download from within Task Monitor.
Click on the Help Map button at the top of this window, and select Task
Monitor for more information. After a download from backup, the next
download of that device from the current database must be a total
download.
You can select the Data --> Report menu option on the Task Monitor for
a particular job, or click the Report toolbar icon to produce a report of
the process — the Report dialog is displayed. When you run the report,
the Download Report dialog is displayed for you to view the details.
You can create an emergency download (ED) file in either of two ways:
You are prompted for a location to store the emergency download files
on the server.
10
Step 3: Enter device tag names or click Tag Values from the context
menu and select tags from the list that appears.
Step 4: If you select a tag set, the Devices in Tag Set dialog
appears, showing the tags referenced by the tag set. Select
the tags you want to include.
Note that the software allows you to enter or select only tags
10 of devices which have been successfully generated.
Step 5: After you have entered or selected all the tags you want to
create emergency download files for, select Action -->
Submit job from the main menu.
Step 6: Enter or browse to the path where you want to save the
emergency download files. You can save download files to
the server or any networked PC.
You can review the status of the job from the Task Monitor.
If you are logged in to the ENVOX server, you can create emergency
download files from a command prompt using the dlexec command. To
see the command line options for the dlexec command refer to
subsection 10.2.1.3.
C:\>dlexec_ed /?
Parameters required :
Note that when downloading data from an emergency download file, the
system does not make sure that the device can accept a download or
that a user has download privilege. The system administrator must,
therefore, set any necessary protection on files so that only certain users
can download from them.
DeviceTag_mask_yyyymmddhhmm.dwn
The DeviceTag part of the name is the device tag. If the tag is fewer than
12 characters, it is filled with underscores. The mask part of the file name
depends on the length and the characters used in the tag. Each letter in
the tag becomes an l (letter l) in the mask. Each number in the tag
becomes a d. Each hyphen becomes an h.
device-1_____llllllhd_200005081326.dwn
Breaking the name into its components and explaining the pieces results
in:
device-1____ -- tag
_ -- separator
llllllhd -- tag mask
_ -- separator
2000 -- year
05 -- month
08 -- day
13 -- hour
26 -- minutes
.dwn
10.3 Uploading
You can use Control Desktop to upload the values of detail display
parameters (DDPs) from a downloaded and tuned PROVOX device to a
Control Desktop database. You can also determine the status of upload
requests. Upload also makes it easier to update the source configuration
data and encourages the regular backup of the tuned parameters.
Uploading an item updates the database, but not the download data.
After uploading, you must generate all devices affected by the uploaded
changes.
J Displays
J Device definitions
J Points from devices from which the user has no privilege to upload
J DDPs the ENVOX software has not configured (for example, UTIMR)
J DDPs used for some temporary purpose during plant operation that
should not be permanently included in the database. (REM OFS
exemplifies this type of DDP. Normally a point is tuned off scan to get 10
around some temporary problem, such as a faulty transmitter, and it
is not desirable to upload this data.)
Also, you can upload IAC and computing controller AUX EUs if an FST
references them. As a result, they appear in the DDP list of a point. AUX
EUs are really part of the device definition, so you must upload a point
that references them to get the new values.
DDP values for pre-SR90, SR90 and SRx family controllers have certain
limitations on uploading. If a DDP value in the controller differs from the
database value by more than 0.001 percent, the software uploads that
DDP value only if it has been tuned. This limitation prevents upload of
spurious values. If the controller DDP value differs by less than 0.001
percent, the software does not upload the DDP value. Changing a DDP
value in the controller has no effect on whether that value gets uploaded
if the point is uploaded.
Step 2: Enter the name of a tag or tag set. You can select Tag Values
from the context menu to select from a list.
10 The status of the tag is shown.
Step 3: Repeat this for all the tags you want to upload.
Step 4: When you have selected all the tags, select Application -->
Submit job to submit the upload. You can use Task Monitor
to monitor the status of the upload.
Upload ignores NULL DDP fields that were not previously configured in
the database. Therefore, if you tune controller DDPs that are NULL in
the configuration database, they are not uploaded.
The uploadable point types are: LOOP, GROUP, DCD, AO,DO, PDO, AI,
DI, DM, PCI, LCP, EPCI, MUX EXT DO, MUX STD AO, MUX EXT AO,
MUX STD AI, MUX EXT AI, MUX DI, CONFIGURABLE DCP, IAC DCP,
IAC ANALOG ICP, and IAC DISCRETE ICP.
Note ... Upload ignores NULL DDP fields that were not previously
configured in the database. Therefore, if you tune controller
DDPs that are NULL in the configuration database, the ENVOX
software does not upload them.
If communications are lost during the upload of a tag set, the following
occurs:
J If all the points in the tag set reside in the same controller, only those
points uploaded before the failure are updated.
Only logic control point (LCP) registers with initial values are uploadable.
This gives you a flexible and simple way of using registers:
J Local registers, excluding the SVA, SVD, and SVP, are configurable,
tunable parameters to the FST. These registers are uploadable, if
they had initial values configured in the database.
J Depending on how you write your FST, you may not want all of your
local registers to be uploaded. For example, a boolean register might
have an initial value of TRUE, which directs the FST to perform a
special action on the first execution after download. (An example of
this special action would be initialization of an accumulation
calculation). After the FST has performed the special action, it may
reset the register to FALSE to avoid doing the special action again. In
this case, you would not want the value FALSE to be uploaded;
otherwise, your special action would not be performed after the next
download.
If you are using registers in this way, you may not wish to use Upload
on the LCPs. Alternatively, you could modify your FST so that you
avoid this effect, possibly by using the DLR or DLS instruction to
detect the first execution after download.
J Task Monitor
J Upload reports
And
10
10
10
Upload jobs can access the log while an upload takes place. Logs
remain in the database until the next upload, at which time they are
replaced.
You can view a report of the most recent (or currently processing) upload
through the Task Monitor. Figure 10-8 shows an example Upload Report.
10
J Tag — The tag of the item you selected for this upload.
J DDP — The DDP numbers. All DDP types have a unique number,
consistent for all device types.
J Mnemonic — The mnemonic for the DDP. Each DDP type has a
unique mnemonic, consistent for all device types.
Table 10-2 lists the uploadable point types for the IACs; computing and
configurable controllers; UOC family of controllers; multiplexers; and
SR90 and SRx controllers.
Table 10-3 lists the uploadable DDPs for each point type in numerical
order. Each cell of the mnemonic-and-name column shows a DDP
mnemonic in boldface type and the name in regular type. Your program
may tune most DDPs; the boldface words Not tunable denote the DDPs
your program may not tune. The last column in the table shows the
devices to which the DDPs pertain.
10
Blank page.
10
Figure 11-Table 11
Menu options are enabled when the session is in a valid state. For
example, a device must be selected before options on the Debug and
Tune menus are enabled.
11.1.1.3 Toolbar
Depending on system settings, you can position the cursor over each
toolbar icon to display a tool tip that explains the to which function the
toolbar icon applies. You may hide the toolbar.
Trace points and the current breakpoint are indicated with disk and arrow
symbols to the left of the step number.
From this window you can add tune data items from an FST instruction
and can set and clear trace points when you are tracing and testing.
You can view I/O signals, registers and attributes in the controller’s
11
process database using dialogs called from the Tune menu. If you need
to monitor or change data periodically, the change can be added to this
window.
This window is hidden by default. Use the View menu to enable it. A
summary of all the trace points you have set is displayed in this window.
Each trace point is identified by its FST tag and step number. An
abbreviated instruction mnemonic and the accumulator values SVA,
SVD, SVI and SVP are displayed in a standard list control.
This window can be used to view and debug downloaded FSTs at times
when the configuration in the ENVOX database is not synchronized with
the downloaded FSTs.
The Toolbar, Tune Data window and Trace Point Summary windows
are all dockable, which means that they can be floated into the center of
the document window area and repositioned. The Tune Data window
and Trace Point Summary window can be resized while they are
floating. All of these windows can be made visible or hidden using the
View menu.
The LCP Trace/Tune module provides a window into the data inside the
controller Device that you select in the Header Control Bar and allows
11 you to do two things:
Debugging usually combines the use of both these features. When you
have downloaded a valid configuration to a controller device, you can
start an LCP Trace/Tune session to debug the configuration.
LCP debug can be implemented with the LCP mode set to either
WINDOW or to BREAKPOINT in the Header Control. You can set trace
points and examine the results of the instruction execution in WINDOW
mode without affecting the FST executions. Alternatively, you can set the
LCP mode to BREAKPOINT: controller execution is suspended at the
next breakpoint when you select this mode. The Step command is used
to move execution from one step to the next. The Continue command is
used to move execution from one trace point to the next.
When the controller device is offline, process inputs and outputs can be
overridden as shown in Figure 11-2.
Process Inputs
Normal Input
Interrupt
Override Input
Trace Utility
FST
Calculated Output
Override Output
Interrupt
Normal Calculated
Output
Process Outputs
X00016:SW3151--0
J NORMAL — In this mode, the system clears all selected LCP trace
points and resumes normal LCP execution. The LCP trace mode
status affects neither the I/O channel override status nor other LCPs.
Breakpoint is not available for loop LCPs. (You can tune the LCP
type to be continuous at the console in order to debug it, but this
disables the coordination between the LCP and its associated loop.)
When the selected LCP reaches a trace point (or the next step if
single stepping) the following occurs:
The first time the module traces an LCP after download, the LCP mode
is NORMAL. Otherwise, when the trace mode is exited and reentered, it
is the last mode set. Normally, before you exit a controller trace session,
the mode is set back to NORMAL to clear the FST breakpoints and
virtual I/O assignments.
The way you choose to use the LCP Trace/Tune software depends on
your specific circumstances and requirements. However, as a general
procedure, you are able to:
Step 1: Select the device and LCP tag in which you are interested.
Step 7: Override some tune data item values, such as I/O channels,
to force the program down a different path. This technique
lets you test all the possible paths the LCP FST program may
take.
With the Trace portion of the LCP Trace/Tune module, you can:
Trace points can be set or cleared while the LCP is in the WINDOWS or
BREAKPOINT modes. The online Trace/Tune help contains an
illustration of the interface windows and dialogs and detailed instructions
for carrying out these operations.
You can run an LCP in any Trace mode and force the LCP to execute if it
is currently idle. Idle LCPs are those that are executed in a one-shot
fashion and depend on other LCPs for initiation and are newly
configured LCPs that are not scheduled. As well as idle LCPs, this option
can be used with caution for scheduled LCPs or those associated with
direct control inputs.
You can stop an LCP in any Trace mode and force the LCP execution to
cease. It is available for LCPs that are currently continuously executing,
though it can be used with caution for scheduled LCPs associated with
direct control inputs.
The system confirms whether the LCP was successfully run. You remain
in the Run LCP dialog, so that you can run another LCP, until you exit
the dialog.
Continue from Breakpoint is only available when the LCP Trace Status is
at breakpoint. If the LCP is on a slow scan it may take some time to
reach this state.
While using LCP Trace/Tune you may decide to debug another controller
device’s LCPs. The module lets you select a different device from within
the Trace function through the following features:
J If you are actively tracing or tuning, option to return the device’s I/O
channels and LCPs to normal.
J With the default system settings and if you are currently in Window or
Breakpoint trace point mode, the option to restore the current LCP
and its I/O channel overrides to normal.
J With default system settings, the option to restore the current LCP
and its channel overrides to normal, if you are currently in Window or
Breakpoint trace mode.
The LCP Trace/Tune module lets you choose the appropriate trace
mode that suits what you want to view and how you want to debug
devices. The module lets you select another trace mode through the
following features:
J Drop down list selection of the new mode from among the three trace
modes, which are the following:
j Normal
j Window
j Breakpoint
J You can carry out tracing only in Window or Breakpoint trace modes.
J Any trace points are removed from the Trace Point Summary
window and document windows.
J The FST goes to continuous execution (provided that the LCP Mode
is shown as RUNNING).
download the item, and close and re-open the document window in LCP
Trace/Tune. Some values may be re-initialized after a download.
J You can quickly add tune data items to the Tune Data window from
FST instructions in a document window and remove data items.
j I/O channels
j Accumulators
j Point DDPs
j Operating parameters
When tuning data items, you can add items (I/O channels, registers,
accumulators, point DDPs, and operating parameters) using the
standard procedures. However, you can add tune data items to the Tune
Data window from FST instructions in a document window if there is at
least one parameter containing an appropriate address/location context.
You can also remove tune data items as needed.
Using the Add Tune Item(s) option to add tune data items is not
available if the option Show Register Numbers was unchecked on the
LCP Trace/Tune Options dialog when the FST was opened:
The following information also pertains to the use of the Add Tune
Items(s) option to add tune data items:
J Local register tune Items are created from local register references in
any of the supported instruction. Save registers are ignored.
J DDP tune items are created from DDPRD and DDPWT instructions
only
J Duplicate tune items are ignored. There can be only one occurrence
of each unique item. The data format is included in the uniqueness
test so it is possible to display a single integer register in any or all of
the supported formats.
J The item type and location information is checked before items are
11 added. If an error message is output, that tune item will not be
added. For example, 1-1-1:2 is a valid SMART address, but it is not
valid in the context of this feature.
If you remove overridden I/O channels, the I/O overrides remain in effect
until you clear them manually.
this way, you can specify I/O values and monitor their effects on LCP
operation. The Trace/Tune module lets you:
Since I/O channels are tune data, you can add an I/O channel to the
tune data for periodic update. If it has already been added, you can
remove the channel from the display.
11.4.3 Registers
The procedure you follow to view and edit registers is the same for local
and global registers. See the online Trace/Tune help file for an
illustration of this window and specific instructions for its use.
Local and global registers that can be viewed are the following:
Through the Tune Data window, you can view and tune local and global
registers. If the register you wish to see is not displayed, you can add the
register; if it appears in the display, you can remove it. If you remove
overridden I/O channels, the I/O overrides remain in effect until you clear
them manually.
If the register you wish to examine is shown in the Tune Data window,
you can change the current register value. The Tune Data window is
updated to show the changed value.
Note ... Any change to a tune data item modifies information in the
target controller and the process that it controls. Make sure you
have complied with all relevant site procedures and fully
understand the effect of any proposed change before
implementing it.
11
11.4.4 View and Tune the Accumulators
You can view and set the value of accumulators — SVA, SVD, SVI, SVP
(Analog, Digital, Integer, Percent Signal Values). Because an
accumulator is a type of local register, the procedure you follow is the
same as for standard local registers. You can update the accumulator
only when the controller is being held at a breakpoint or is being
single-stepped. You can then examine and change the accumulator’s
analog, integer, and discrete values.
J SVP/SVI — the SVI is the integer accumulator signal value. The SVP
is the SVI in highway percent format (SVP = SVI divided by 256).
If the point DDP has not been added to the Tune Data window, you can
add this point DDP for periodic update. If, however, it has already been
added, you can remove it from the Tune Data window.
The displayed value is the current point DDP value, which may be
changed. Any change to a tune data item modifies information in the
target controller and the process that it controls. Make sure you have
complied with all relevant site procedures and fully understand the effect
of any proposed change before implementing it.
11
You cannot change the setpoint of a DDP when in computer mode.
Any message responses from the controller are displayed on the dialog.
Channel values appear in percent for analog I/O, in raw count for pulse
count inputs, and as 0 or 1 for discrete values. An asterisk indicates the
value of an overridden channel.
You can view and set the state of Point Operating Parameters.
If the operating parameter has not been added to the Tune Data
window, you can add this operating parameter for periodic update. If,
however, it has already been added, you can remove it from the Tune
Data window.
The Value field contains the current operating parameter value, which
may be changed.
Any message responses from the controller are displayed on the dialog.
For the debugging work you are carrying out, you want to suspend all
updates so that the data remains as it stands until you specifically elect
to update it. In other words, you want to change from continuous mode
to snapshot mode.
You may want to make sure that the display reflects the latest live data.
For example, you want to determine if automatic continuous updates
The value fields of the items in the Tune Data window (and other
windows) are updated. If an error occurs during the update, the field
shows the value #Error.
Specific instructions and a detailed view of the Tune Data window can
be found in the online Trace/Tune help file.
Significant Figures
The Real Values and Percentage Values fields define the number of
figures shown in LCP Trace/Tune. The default settings are the following:
J Real values: 6
J Percentage values: 6
This field defines the fastest frequency of the automatic update. The
actual update frequency depends on the number of tune items. The
default setting is 3 seconds. The valid range is 3 to 60 seconds.
Options
The list of options area on the dialog contains check boxes which you
click to turn on or to turn off. A blank check box means the option is
disabled.
Caution ... Change registry settings with great care. Accidental or incorrect
changes can cause system problems.
16 disables checking
11
Figure 12-Table 12
12 12 Report Writer
Report Writer is an integrated application that lets you create,
manipulate, view, and print reports for certain Control Desktop
information.
J Standard Reports, which are built in and have a fixed format report
J Custom Reports, which are generated from an SQL query you create
Though you use the Report Writer to create both types of reports the
menus, menu options, and dialogs you use to create and manipulate the
reports are different. When you switch between the two types of reports,
the interface changes. If you have reports of both types open, the menus
change when you move from report to report
The default list shows every standard report available. You can use the
radio buttons at the bottom of the dialog to limit the type of reports
shown. If you have previously saved a report as a *.PSR (previously
saved report) file, you can open it by clicking Saved PSR Files, then
navigating to the saved report you want to open.
After you create a standard report, you can work with it to change its
appearance, save it, and print it.
12
The online help system contains complete instructions for using the
menu options and dialog boxes to create standard reports. Refer to
Section 3 for instructions on accessing the online help for the Report
Writer module.
the tables you want to work with and put them in the Query Builder
window..
Use Query Builder SQL functions, such as joins, to collect and arrange
information in non-standard ways.
Caution ... Remember that you are using an open SQL interface on the
ENVOXr database. Fisher-Rosemount Systems recommends
that you only create a custom report if you are familiar with
Transact SQL and database structures.
At this point, you may select the following options from the top-level
menu or the icons in the Toolbar to further refine your query for the
custom report:
J File --> New — displays the Select Tables dialog window from which
you select the table data to be used in the query. When you select a
table or tables, Query Builder displays the information available in an
information window.
J File --> Open Query — opens the Open Query dialog window that
lets you locate Query files previously saved as *.QRY file type.
J File --> Run — executes the query to create the desired report
J Edit --> Edit Joins — lets you change join conditions before you
execute the query
J Objects --> Display Columns — highlights the table entries that will
be used as the columns for your report output.
J Objects --> Joins — specifies conditions upon which the report data
is selected
J Options --> View/Edit SQL — directly edit the SQL query in the
Query Builder (changes you make are not applied to the graphical
version of the query in the Query Builder window)
The online help system contains instructions for using the menu options
and dialogs to create custom reports.
Turn gridlines on and off using the Grid field in the Report header.
The gridlines appear on screen and when you print the report.
With the gridlines on, you can use the grid to size and move
columns. To size a column, move the cursor to a vertical grid line.
When the cursor changes, press the left mouse button and drag.
To change the size of the font used in the report and the text printed
in the report heading, select Edit --> Report Options. Use the
Change Report Detail Font spin button to change the font size.
Enter the heading you want to appear in the Title field. Select the
Date-Time check box to have the current time and date appear in the
report heading.
Use the Zoom spin button in the Report window to shrink or expand
the report. Zooming affects the appearance of the report both on
screen and when printed.
You can save the tags into a tag set, for example, to retrieve the list of
tags as part of your selection criteria when producing a report within
Report Writer.
In particular, you may want to use this option so that you don’t have to
create a complex SQL query, with many joins, in order to produce a
custom report containing all the tags in the list. Instead, you can build up
a tag set from the result of several custom reports and then use that tag
set as part of your selection criteria for a new report.
You can choose to create a new tag set, containing the tags in the report
or the SQL used to create it. Alternatively, you can update an existing 12
tag set with this information.
If the tag set name exists already, then you are prompted to choose to
either overwrite or append the tags to the existing tags set, if the two tag
set types are compatible.
Blank page.
12
Figure 13-Table 13
13 13 Task Monitor
The Task Monitor is a standalone application you can use to examine the
status of jobs currently in the job queue. Task Monitor can be accessed
from within Control Desktop, from within Control Designer, or from the
Windows Start menu.
J Display job status by tag item or by job for all job types.
J Filter the job list to either show all jobs or only completed jobs.
The initial state of the Task Monitor is to show all Generate jobs in a job
list view as shown in the figure. Using menu and pull-down selections
you can show other types of jobs, show jobs by item tag, or show only
completed jobs.
Task Monitor also contains options in its top-level menu that provide you
with the following selection capabilities:
J File — provides print options as well as the Exit from Task Monitor
J Job — selects the actions that specify the function you want
displayed:
j Select a Report
j Generate any of the jobs displayed in Task Monitor (if Job Type is
set to GENERATE or DOWNLOAD)
j Download any of the jobs displayed in Task Monitor (if Job Type
is set to GENERATE or DOWNLOAD)
j Abort a job
Note ... The Client Task Daemon is responsible for running tasks such
as Verify/Generate, Rename, ASCII FST Import, PDX, Import 13
and Export. The Client Task Daemon is installed on the client
workstation when you install Control Desktop.
The online help system contains instructions for using the Task Monitor
functions. Refer to Section 3 for instructions on accessing the online help
for the Task Monitor utility.
J Log File
J Reports
The online help system contains instructions for generating reports within
13 Task Monitor.
In the Job List view, Task Monitor displays information in two panes. The
left-hand pane shows the job number, the name of the user than ran the
job and the status of the job. If the job is currently in progress, the status
changes according to the stage the job has reached, for example,
Creating, Executing or Completed.
The right-hand pane shows more detailed information about that job,
relating to the tags in the job.
When you are using Task Monitor in the Job List view, you can do the
following:
When you are using Task Monitor in the Tag List view, you can do the
following:
Note ... In the Tag List view the status value of devices that are
currently being generated are displayed as Fatal Error. Similarly,
devices being downloaded display Download Failing in the
status column. These are transitional state set at the start of the
generate and that is updated to the correct value when the
generate completes. To see the true current status of generate
or download jobs, open the Job List view.
If you are using the Job List view, Task Monitor displays the following
information about Download jobs:
In the left-hand pane: In the right-hand pane:
the job number. list of device tags within the job selected in
the left-hand pane.
the name of the user who ran the job. the type of download .
status of the job. the time the tags were last downloaded.
the download status of the tag.
the number of packets used in the
download
You can restrict the number of jobs that appear by filtering the jobs. To
filter the jobs, from the Job Filter drop-down list, select All Jobs or
Completed Jobs. Note that jobs that were completed in the current
session are shown in blue text in the left-hand pane.
If you are using the Tag List view, Task Monitor displays the following
information:
13
J the name of the device tag.
In the Tag List view, the Job Filter option is not available.
If you are using the Job List view, Task Monitor displays the following
information for Generate jobs:
You can restrict the number of jobs that appear by filtering the jobs. To
filter the jobs, from the Job Filter drop-down list, select All Jobs or
Completed Jobs.
If you are using the Tag List view, Task Monitor displays the following
information:
J the number of any warnings or errors that resulted when the tag was
generated
In the Tag List view, the Job Filter option is not available.
If you are using the Job List view, Task Monitor displays the following
information about Translate jobs:
You can restrict the number of jobs that appear by filtering the jobs. To
filter the jobs, from the Job Filter drop-down list, select All Jobs or
Completed Jobs.
When you display Translate jobs in the Job List view, the Generate and
Download options on the Job menu are no longer available.
If you are using the Tag List view, Task Monitor displays the following
information:
J the number of any warnings or errors that resulted when the tag was
translated.
In the Tag List view, the Job Filter option is not available and the only
options available on the Job menu are Report, Find Item, and Abort.
J Generate Report.
J Download Report.
J Translate Report.
J Upload Report
For these jobs the details pane does not contain job details but contains
a statement saying to view the log file for more information.
13
Figure 14-Table 14
14 14 Utilities
ENVOXr Server and Control Desktop provide utilities that enable you to
perform several important tasks to maintain your data after you have
configured, generated, and downloaded your system. Included in these
utilities are the following:
J Upgrade Devices
Highway Reference List numbers are also used to access console point
information from Computer Highway Interface Package (CHIP) programs
using the Highway Reference List number as the point number in the
CHIP request.
14
Note ... The Highway Reference List (HRL) has also been called the
Highway Access Control List (HACL), the highway access list,
and the highway control list in other PROVOXr documents,
particularly those relating to the PROVUEr console. Both terms
Highway Reference List and Highway Access Control List
appear in Control Desktop.
J From the Highway Ref No field in the point’s Item Detail window
If you do not assign Highway Reference List numbers to points that are
not console-resident, when the console is generated and downloaded a
reference number local to the console is assigned to the point. This local
reference number is not a Highway Reference List number and the
number is not added to the Highway Reference List. This local reference
number may change on subsequent downloads.
number to remain fixed, especially if you are using CHIP programs with
hard-coded HRL/HACL numbers.
If you use activities in a redundant pair you must put unit points in the
Highway Reference List (HRL/HACL).
If you delete a point, then add it, the Highway Reference List number
control desktop assigns to it may change. If you then do a partial
download to every device that uses the old reference number, (including
pairs of redundant consoles), different devices may end up with similar
points that have different Highway Reference List numbers. Assigning
your own Highway Reference List (HRL/HACL) number prevents
unwanted duplication and associated problems.
The Highway Reference List contains all of the points for which a
Highway Reference List number (HRL/HACL) has been assigned. To
view the Highway Reference List, select View --> Highway Reference
List. Figure 14-1 shows an example list.
14
You can perform the following tasks from the Highway Reference List
dialog:
J Increase the maximum list size — that is, increase the number of
permitted highway reference numbers. You do not have to view the
entire list to be able to do this.
J View the entire list of point tags and their highway reference
numbers.
If the Highway Reference List does not contain any data when you open
it, select Data --> Retrieve Data from Control Desktop when the
Highway Reference List dialog has focus. Retrieving the list may take
some time for a large database.
The entire list of highway reference numbers and the point tags to which
they are assigned is displayed. This list is read-only, except that you can
increase the number of permitted highway reference numbers.
Figure 14-1 shows a filled Highway Reference List dialog.
Use this dialog to scroll through the point tags to reach the desired point.
You can also sort the list of points through the Point Tag heading or the
Reference No. heading. You can also change the maximum number
through the Maximum List Size field.
When you make a change and close the list, you should save the
change when you are prompted.
14
14.1.1 Search the Highway Reference List
You can search the Highway Reference List to locate a point tag or a
reference number. For a detailed description of this procedure, see the
Control Desktop online help file. Figure 14-2 shows the dialog that lets
you specify the criteria for your search. The criteria are the following:
J Find what — search with some or all of the characters of either the
point tag or highway reference number
J Match Case — find text that exactly matches the case of the entry in
the Find what field
J Find Next — highlight in the Highway Reference List dialog the first
item found that matches the search criteria
You can also copy the information with a standard highlight and copy
procedure. You may want to paste it into another application such as a
word processor.
14
Figure 14-2. Search Dialog for Highway Reference List Data
You can use the Populate Highway Access Control List dialog to have
Control Desktop software assign HRL/HACL numbers. Open the dialog
by selecting View --> Populate HACL. The dialog appears as shown in
Figure 14-3.
There are two options on the Populate Highway Access Control List
dialog in the Add Points Targeted To area:
J All consoles with Global Ack Alarms and PPA Tracking Enabled
J All Consoles
There are three read-only fields on the dialog in the HACL Properties
area:
J Configured Max List Size — The number set in the Maximum List
Size field of the Highway Reference List dialog.
If the Number of Points to Add field on the dialog is zero, the Populate
HACL button is disabled.
If the Configured Max List Size value is less than the sum of the values
in the Number of Points In HACL and Number of Points to Add fields,
clicking the Populate HACL button Control Desktop displays a message,
increases the configured list size, and adds the points to the list.
Control Desktop increases the list size to 500 greater than the sum of the
number of points currently in the Highway Reference List (HRL/HACL)
and the number of points to add. Note that increasing the maximum list
size requires a total download to the consoles.
If the sum of the number of points to add and the current number of
points in the list is greater than the largest valid size for the Highway
Reference list (22767), Control Desktop displays a message and
disables the Populate HACL button.
The first time you run this utility several points are likely to be 14
regenerated with the new Highway Reference List number allocated
when the consoles are generated. Subsequent runs and regenerates
should only mean that the changed points get regenerated.
For detailed procedures for using the Populate HACL option, see the
Control Desktop online help file.
To view the audit trail for a particular item, select the Audit Trail tab from
the Item Detail window. Figure 14-4 shows the Audit Trail tab of an
Item Detail window.
The tab shows a list of the events that have occurred to the item. You
can sort the list by clicking one of the column headings.
14 To view the details of an event double-click on a row or select Detail
from the context menu for an event in the history summary area of the
Item Detail Audit Trail tab or of the Audit Trail Search dialog. In either
case, the Audit Trail (Event Detail) window appears and contains
information similar to that illustrated in Figure 14-5.
The top area of the window shows the background information about the
event — event number, date and time, user name, and so on. The
bottom area shows the actions that occurred during the event. You can
view previous events in the history summary or the next events with the
click of the Previous or Next buttons, respectively.
You can search all events for items of interest by selecting View -->
Audit Trail Search. The Audit Trail Search dialog opens. The dialog
contains three tabs you use to specify your search: 14
J Date Range
J Item Criteria
J Event No
Use the Date Range tab to specify whether to search all events or only
those events that occurred in a specified time period.
14
Use the Item Criteria tab to narrow your search based on the following:
Use the Event No. tab to narrow your search to the last event recorded,
a single specified event number, or a range of event numbers.
After you have set the criteria for your search, click the Find Now button.
The events matching the criteria you specified appear in the list at the
bottom of the window.
You can use the Import utility to load previously exported comma
delimited value (CDV)-formatted data into an ENVOX database, and use
the Export utility to move the data from one database to another. The
files holding the CDV data are simply an ASCII version of ENVOX
configuration data.
The Import utility, which can be run either from Control Desktop or from
command lines, lets you:
Step 2: Enter or browse to the directory that contains the CDV data
you want to import.
Step 3: If you are importing into an empty database, select the Verify
Database is empty before Importing checkbox. If you are
merging the imported data into an existing database, do not
select this checkbox.
You can view the Import job status using the Task Monitor.
You can also import CDV data from the command line. The syntax is:
/L Load the data into the database after verifying that the
database is empty. If you are merging data into the
database, omit this option.
Note ... The import command also has a /J switch. Do not use this
14 switch. The Client Task Daemon uses this switch when it runs
this command for Control Desktop.
Importing a device causes that device and all its source and target points
to be deleted if the device already exists in the database. However, if
you are importing a redundant pair of PROVUE or WPCON consoles you
must ensure they are deleted prior to the import.
HOST COMPUTER
ENVOXr SOFTWARE
Database
Database
Database
Utility
:
Import
Utility
:
Export
Format:
CDV
Basically, the export utility copies data to a comma delimited value (CDV)
format. The import utility can import this data into a different ENVOX
database, converting it back to the standard ENVOX format.
The export utility can be initiated from either Control Desktop or from a
command line. The following subsections describe how to run the utility
via either method.
Note ... Running the export utility from a command line is only 14
recommended for experienced users. Users not familiar with the
command line system should use the Control Desktop interface.
contains the data you wish to export. See Figure 14-11 for the Export
dialog.
To export all of the sourced, targeted, and referenced items from the
database you are currently logged on to:
You can view the Export job status from the Task Monitor.
You can export single items or items from a tag set. Obviously, if you
have a large number of items you want to export, it is faster to build tag
sets for these items than to export them individually. For each device
name, the software exports all source points, targeted data, and
referenced items for the device.
Step 2: Enter a tag or tag set name in the Tag of item or Tag Set to
Export field on the Export dialog.
where...
Note ... The export command also has a /J switch. Do not use this
switch. The Client Task Daemon uses this switch when it runs
this command for Control Desktop.
You must enter the tag name (or tag set name) of the device to be
upgraded. You can select Tag Values from the context menu to select
from a list.
When the type of device is shown, select from the drop-down list the
type of upgrade you want to carry out. The software shows the device’s
current status.
You can create new rows for entering all of the devices you want to
upgrade.
When you have selected all the tags of the devices you wish to upgrade,
select Action --> Upgrade from the menu or click the toolbar icon to
submit the upgrade. The status of the upgrade appears in the Status
column on the Upgrade Devices window.
14
History
The list below shows the printed manuals available for each version of
ENVOXr software and Control Desktop.
ENVOX P1.0
ENVOX P1.1
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P1.2
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P2.0
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P3.0
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P3.2
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P3.3
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P3.4
J ENVOX Tutor
TU4.14:SW3151 (Original — June 1991) D2T00481002
ENVOX P4.0
ENVOX P5.0
History
Blank page.
History
Glossary
Address Attribute
One or more integers arranged to identify An individual parameter of a process
the location of a device or logical unit of control point. Also the name of a
an instrumentation system. In PROVOXr PROVOX data type. In some systems,
systems, address values identify such points have just one or two attributes;
things as data highway, device, file, card, however, points in PROVOX systems
and channel. have many. Accordingly, each point of a
PROVOX system commonly provides the
AI control of four or five non-PROVOX
Acronym: Analog Input system points.
AO CDV
Acronym: Analog Output Acronym: Comma Delimited Values
ASCII CHIP
A PROVOX point type. An ASCII point Acronym: Computer/Highway Interface
contains a single real value, referenced Package
by the setpoint attribute, and an
80-character ASCII string.
Glossary
Glossary Faceplate
An established display figure, used in
Display Designer, that shows the most
important information about a process
control point. Faceplates are vertical
rectangles, several of which fit on a
console screen at once.
Import
The process of placing configuration data Glossary
Information stream
The first stream in a CDV file.
Kernel Log
The lowest layer into which a large A record of events that have occurred
operating system is divided -- each layer within the database. A log may consist of
handles some aspect of the system successful and unsuccessful events and
hardware. ENVOX Server and Control any error or warning messages related to
Desktop uses a CHIP kernel. those events.
Loop Name
A PROVOX point type. A loop point A unique identifier for any device or
provides control for a continuous logical unit of an operations console
process. Loop points have many system except a point or a controller
attributes, so can provide very (points and controllers have tags instead
sophisticated control. Bias or ratio factors of names).
often can be added to loop points.
Null
Master Database Having no assigned value. In a CDV file,
The central database which holds details null is represented as two commas with
of all of the other databases. It is created zero or more spaces in between.
by SYBASE when SYBASE is installed.
Operand
Matrix 1. In the language editor, a value that
A means of displaying data in column modifies or qualifies a function.
format in Control Desktop, so that you 2. In ASCII configuration source files, an
can quickly and efficiently configure large expression, a simple operand, a phrase
amounts of items. (Item types Loops and list, or an operand list.
EDCDs can be configured in Excel
Matrix.) Operation Parameters
The 32 unit variables that contain default
Migrate grade values. Operation parameters are
The process of converting PROFLEX common to all phases of an operation.
configuration data into CDV file format,
from which the data can be imported into Option Button
an ENVOX database A button that excludes other options
when you select it. Option buttons are
Model Database sometimes known as radio buttons.
The database which is used as the basis
for a new database. It is created by PDF
SYBASE when SYBASE is installed. Acronym: PROVOX Display Format. An
ASCII tab-delimited file format in which
Multiple Document Interface (MDI) Display Designer can store displays.
In a Multiple Document Interface (MDI) These can then be viewed using the
application such as Control Desktop, you ViewPDF utility.
can open several windows at the same Acronym: Adobe Portable Document
time and work on the contents of those Format
windows. In Control Designer, when you
have several program diagrams open at Glossary
Process
A user-initiated action that affects or
accesses a database. Each process
represents one connection to the server.
An ENVOX user typically has three to five
Glossary
processes active at once. Adding a point,
generating files, and downloading files
are examples of processes. The ENVOX
administrator can determine which users
have initiated which processes and can
also kill processes.
Upload ViewPDF
The movement of configuration This utility displays PDF files on a PC,
instructions from system devices to a simulating the appearance of the display
configuration device or interface. An on the console or operator interface. You
upload lets the current values of can use this utility to check the
parameters be incorporated into new appearance of a display before saving
configuration source files, eliminating the display to the database from within
specific user entry. Uploads also may be Display Designer.
used to verify that configuration
instructions are correct. Where Clause
Sets the search conditions to apply to an
User Functions SQL query.
A user function diagram, created with the
same drawing methods as program Window
diagrams, can be used on one or more A particular type of console display that
program diagrams in a current project. has a specific purpose. A DDP window,
These user-created diagrams can contain for example, shows point DDP
standard functions but not other user information. A trend window shows trend
functions. set information. An application window
emulates a computer terminal.
Variable A trace utility mode within LCP
A variable is an IEC concept for a data Trace/Tune, in which accumulator values
type; for example, real, integer, percent, appear on the console screen as trace
or Boolean. point FST steps execute, but FST
execution does not stop at trace points.
Variables Editor
A module of Control Designer that you
use to define and to edit user variables in
addition to the (standard) system
constants. Variables can be local to a
specific program diagram or global and
you can set access to them as read-only,
write-only, or read-write.
Glossary
Index
cloning
console configurations, 80
A restrictions, 81
command lines, entering, 19
abbreviations used in manual, 18
command prompt styles, 19
aborting, from Task Monitor, 203
commands, use of return key, 19
accumulator, 179
comments, language editor, 105
Add menu option, 85
conditional color expressions, creating
adding an item to the database, 85 from the language editor, 100
alarm conditional text expressions, creating from
conventions, 25 the language editor, 100
management, 25
configuration
audit, particular item, 212 conventions
Audit Trail, 211 alarm, 25
searching events, 213 display, 25
copying items, 77
Audit Trail, 31
managing, 59
planning and design, 25
configuration data, validating, 89
C starting, 39
Control Desktop stops, 43
change column heading, matrix view, 77
conventions, typographical, 18
change column width, matrix view, 76
copy, configuration item, 77
client administration navigation, 57
Index
from command prompt, 141 Excel Matrix, 119
from Control Desktop, 139 concurrent users, 128
from emergency download file, 147 connection to ENVOX Server, 120
from Task Monitor, 140 editing a workbook, 133
download data, 139 errors and warnings, 133
external data, 132
downloading configuration data installing the Add-in, 128
download utility, 29
L
M
language editor, 99
accessing, 100 M--partial download, 141
comments, 105 M--total download, 141
cutting and pasting text, 106
finding and replacing text, 106 making suggestions, 22
help, 108 manuals
LAYOUT, print attributes, 111 in PDF format, 37
online, 37
Index LAYOUT instruction, 110 printed, 35
LCP Matrix View, 61
running, 172 creating items, 72
stopping, 172 customizing, 76
tuning, 175
navigation, 47
help, 33
new blank row, matrix view, 72 R
NEXT instruction, 113
registers, 177
NORMAL, trace mode, 169
renaming, from command line, 84
renaming an item, 82
Index
REPEAT instruction, 113
O report
previewing, 114
on-line help. See help print attributes, 111
online books, 37 Task Monitor, 198
S target devices, 85
Target! menu option, 85
saving instruction sets, 109 targeting point data
search criteria, Audit Trail, 213 source data, 85
security areas, tag sets, 93 target devices, 85
utilities, 55
U
UNTIL END instruction, 113
V
UNTIL instruction, 113
upgrading devices, 223 validating data, 89
upload, 30 validation
data precision, 152 errors, 89
logs, 154 log, 89
privileges, 151 versions, 23
reports, 155
to LCP registers, 151 view license users, 42
uploading, 148
and Task Monitor, 153
uploading on-line configuration data
detail display parameters (DDPs),
W
149–164
BREAKPOINT, trace mode, 170
limitations, 149
uploadable point types, 149–151 WINDOW, trace mode, 170
using return key for commands, 19
Index
Blank page.
Index
Notes
Notes
UM:SW3159:EN