Getting Started with Control Desktop

Transcription

1 Getting Started with Control Desktop This manual applies to software version P2.0. User Manual UM6.3:SW3311:G D2U Original May 1998 This manual supercedes the UM6.3:SW3311:CDT issue dated une 1997.

2 DOCVUE, ENVOX, Fisher-Rosemount, Fisher-Rosemount Systems, Managing The Process Better, PROVOX, and PROVUE are marks of one of the Fisher-Rosemount group of companies. All other marks are the property of their respective owners Fisher-Rosemount Systems, Inc. All rights reserved. PrintedinUSA 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.

3 Your Evaluation Please... iii Name: Title and Department: Company: Years of Experience: Instrumentation Distributed Control Telephone: ( ) -- Education: Years Years College Degree ob Responsibility: Please indicate your evaluation of this manual. Attach additional sheets with comments as needed. 1. How and when do you use this manual? 2. How well is the manual s content organized? Please explain on a separate sheet. Understandable 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 V Excellent parallels product s operation, 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 Applicable 3. Is the manual s content understandable and applicable to the product s operation? Please explain on a separate sheet. 4. How well do the manual s illustrations convey product information? Please explain on a separate sheet. V V V V V V Excellent very easy to understand, very applicable V Good easy to understand, applicable V Average applicable but some sections not easy to understand V Fair not very understandable/applicable, should be improved V Poor not understandable/applicable, must be improved V No Opinion V V Excellent very easy to understand, extremely usable 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

4 iv Your Evaluation Please Describe the amount of usable information in this manual including tables. Please explain on a separate sheet. Sections 6. How well is information cross-referenced in the manual s individual sections and index? Please explain on a separate sheet. V Too much information not all required to perform task V Proper amount provided not too much nor too little V Too little information needed additional information to perform task V No Opinion Index V V V V V V V V Excellent very easy to locate information, extremely usable V Good easy to locate information, very usable V Average fairly easy to locate information, usable V Fair not easy to locate information, should be improved, not very usable V Poor cannot locate information, must be improved, totally unusable V Did Not Use V No Opinion 7. How useful is the Glossary? V Useful V Useful but not complete/accurate V Not Useful V Did Not Use V No Opinion 8. What is your overall impression of this manual? Please explain on a separate sheet. V Excellent met all needs, extremely usable V Good met most of my needs, very usable V Average usable V Fair should be revised, not very usable V Poor must be revised, totally unusable V No Opinion Please FAX or MAIL this form to: FAX Number: (512) Fisher-Rosemount Systems, Inc. Technical Documentation Editor 8301 Cameron Road, MD#12 Attention: Technical Documentation Editor Austin, TX FISHER-ROSEMOUNT USE ONLY forwarded to: V Lead Writer V Engineering V Technical Support V Marketing V Project File

5 Getting Started with Control Desktop (Original May 1998) Contents v Contents 1 Introduction Who Should Read This Manual Control Desktop Revision This Manual Supports New this Release New for Control Desktop New for the Manual Set New Additions to the Help System Contents of this Manual Conventions Used in this Manual Cautions and Notes Control Desktop and ENVOX Documents Related Documents Electronic Documentation Where to Find Answers for Product and Document Questions Using the Online Help Systems Using the Built-in Help Systems Using the Online Help System Accessing General Help Accessing Context Help Using the Diagnostics Help System Control Desktop User--Defined Online Help Product Overview Similarities Between Control Desktop and ENVOX Software Differences Between Control Desktop and ENVOX Software Configuration with Control Desktop Legacy Device Support Exploring in Control Desktop Control Desktop User Administration... 23

6 vi Contents Getting Started with Control Desktop (Original May 1998) 4 Installing and Setting Up Control Desktop Software The Stages of Installation General Information What You Can Install What Gets Installed Directory Structures ODBC Data Sources Registry Modifications Stage 1: Before You Begin Upgrading ENVOX Databases for Use with Control Desktop P2.0 Summary Scenario A: ENVOX P3.4 Systems Scenario B: Pre-ENVOX P3.4 Systems Control Desktop User Administration Overview Application User Accounts ENVOX Database User Administration Control Desktop Client Administration Diagnostics User Administration Machine User Accounts Stage 2: Match Your Scenario Stage 3: Install Control Desktop P Scenario A: Install Control Desktop P2.0 When P1.0 Has Not Been Previously Installed Scenario B: Upgrade from Control Desktop P1.0 to P Scenario C: Add Control Desktop P2.0, Leaving P1.0 Available Running Setup Installing Control Desktop Diagnostics Stage 1: Before You Begin Setting Up a Web Server Microsoft Personal Web Server Files on CD-ROM Microsoft Personal Web Server Files on the Web Installing CDOS P Stage 2: Installing Diagnostics on the Web Server Install the Diagnostics Software Create a Database NT Service Add the CDOS Server to the SQL.INI File Configure the Web Server... 57

7 Getting Started with Control Desktop (Original May 1998) Contents vii ISAPI Servers NSAPI Servers Stage 3: Configuring Web Browsers Stage 4: Adding Diagnostics Users Test the User s Login Troubleshooting Control Desktop Troubleshooting Significance of Common Control Desktop Error Messages Significance of Common Control Designer Error Messages Diagnostics Troubleshooting De-Installing Control Desktop P Starting Control Desktop Startup Procedure Login Procedure Login from Login Icon, ADMIN Option, or Right Mouse Menu Login by Double Clicking A Server Upgrading ENVOX Databases Licensing Control Desktop Software Licensing Procedure License File Operation Requesting Initial Licenses Requesting Additional Licenses Requesting New Hardware Licenses Activating License Keys License Activation Status Viewing A Targeting Points in Control Desktop

8 viii Contents Getting Started with Control Desktop (Original May 1998) B Control Desktop File Structure B.1 System Files Installed with Control Desktop P2.0 Software B.2 ODBC Data Sources Installed with Control Desktop P2.0 Software 116 C History Glossary Index

9 Getting Started with Control Desktop (Original May 1998) Contents ix Figures Figure 3-1. Control Desktop System Architecture Figure 4-1. Control Desktop P2.0 / ENVOX P4.0 Administration Overview 35 Figure 4-2. Sample OB.CONF Configuration File Figure 4-3. Control Desktop Server Setup Dialog Window Figure 5-1. Connect to Database Dialog Window Figure 5-2. Server Authorization Login Dialog Window Figure 6-1. License Registration Contact Details Dialog Window Figure 6-2. License Registration License Details Tab Dialog Window. 93 Figure 6-3. Additional Licenses Request Contact Details Dialog Window Figure 6-4. Additional Licenses Request License Details Dialog Window Figure 6-5. New Hardware License Request Contact Details Dialog Window Figure 6-6. New Hardware License Request License Details Dialog Window Figure 6-7. License Activation Dialog Window Figure 6-8. License Activation Status Display

10 x Contents Getting Started with Control Desktop (Original May 1998) Tables Table 1-1. Mouse or Trackball Terms Used in This Manual... 7 Table 1-2. Manual Conventions... 8 Table 3-1. Legacy Device Support Limitations Table A-1. Fields in the Target Data Dialog for CHIP Devices Table A-2. Fields in the Primary Tab of the Target Data Dialog for Console Devices Table A-3. Fields in the Console Target Tab of the Target Data Dialog for Console Devices Table A-4. Fields in the Target Data Dialog for Controller Devices

11 Introduction F Section 1 1 Figure 1-Table Introduction The Type SW3311 Control Desktop software is a PC-based application that accesses existing SW3150-series ENVOXr P4.0 Configuration software and databases. This manual describes Control Desktop, version P2.0, its relationship to the PC-based computer running under Windows NT 4.0, and details how the user navigates and uses the Control Desktop features. Control Desktop connects to and uses existing ENVOX databases on the DEC VAX, DEC AXP, and HP platforms that already have an ENVOX P4.0 installed client server. ENVOX P4.0, Control Desktop P2.0, and CDOS P2.0 are compatible. Earlier versions of these products are not compatible with later versions. For instance, when you upgrade ENVOX software to version P4.0, and you wish to use Control Desktop, you must also upgrade Control Desktop and CDOS to P Who Should Read This Manual This manual is intended for configuration engineers, users, and system administrators familiar with ENVOX configuration software on DEC Open VMS systems, and with Windows NT systems for installing Control Desktop on an NT platform. A knowledge of ENVOX interfaces to a PROVOXr system is required. For users not familiar with using ENVOX software to configure a PROVOX system, the appropriate FRSI school is recommended.

12 2 Section 1 F Introduction 1.2 Control Desktop Revision This Manual Supports This manual supports the version of Control Desktop software, P2.0, which runs on Microsoft NT version 4.0. Note... Only ENVOX version P4.0 software is compatible with Control Desktop version P New this Release The P2.0 release of Control Desktop contains: Product enhancements A complete restructure of the manual set Revisions, enhancements, and restructuring of the online help system Control Desktop is a client application that runs on a Windows NT--based PC to provide the user interface to the ENVOX server. It replaces the ENVOX forms data entry mechanism and integrates much of the user interface into a Windows NT--based engineering environment New for Control Desktop The P2.0 Control Desktop release provides: true Explorer viewing functionality user access functionality control tag set replacement

13 Introduction F Section 1 3 an interface to the audit trail configurable user options the ability to launch the Controller I/O View from the Plant I/O View user-specific security tag sets the ability to drag n drop console list items extended functions for the Matrix View a new Diagnostics module, enabling you to remotely diagnose system problems through HTML-based Web pages using a standard Web browser a new Administration module, providing easy-to-use client and database administration features new Item tab screens improved context sensitivity, especially in the right-mouse menu support in the Explorers for Global Point types many extensions to the Control Designer module, such as a user function feature that allows you to define your own function blocks New for the Manual Set The restructuring of the manual set reflects improvements in product usability that these enhancements generate. It also responds to customer requests to have certain pieces of information more accessible, either through expansion of the online help system, or elevating the information to a more prominent level within the manuals.

14 4 Section 1 F Introduction As a result, the manual set now consists of: Getting Started with Control Desktop (UM6.3:SW3311:G) this manual tells you what you need to know to install, set up, start, navigate within, and use the Control Desktop application. Using Control Desktop Modules (UM6.3:3311:M) this manual tells you how to use such Control Desktop features and utilities as Control Designer, Report Writer, Task Monitor, Client Administration, and Diagnostics, as well as how to translate control strategies into an ENVOX format. Both manuals also tell you what is in the online help system, as well as how to access it and navigate within it New Additions to the Help System Finally, the online help systems for Control Desktop and its associated functions and utilities have been restructured and expanded to improve usability. New features include the addition of: a Web-based intranet segment of the help system to support the new Diagnostics utility a help file for the new Administration module 1.4 Contents of this Manual This manual contains the following Sections and Appendixes: Section 1 Introduction: includes an overview of this manual, the intended audience, the stylistic typographical conventions used, and defines documentation available for Control Desktop configuration software.

15 Introduction F Section 1 5 Section 2 Using the Online Help System with Control Desktop: describes the online help system architecture, as well as providing instructions for accessing and navigating within the help system. Section 3 Control Desktop System Overview: describes the Control Desktop software requirements and features, and the system architecture that includes the system s structure and interfaces. Section 4 Installing and Setting Up the Control Desktop Software: outlines the system requirements and installation considerations, and provides instructions for installing and de installing the Control Desktop software on the client PC, moving Control Desktop to another disk, and setting up the Control Desktop parameters. Section 5 Control Desktop Licensing: describes licensing requirements. Section 6 Starting Control Desktop: defines startup and login procedures, and describes how to move from one server to another, as well as how to change databases, and ENVOX database upgrade requirements. Appendix A Targeting Points in Control Desktop: describes the procedures for targeting PROVOX points with Control Desktop. Appendix B Control Desktop File Structure: identifies the system files and the ODBC data sources installed with the software. Appendix C History: lists all Control Desktop documentation by version number and release date.

16 6 Section 1 F Introduction 1.5 Conventions Used in this Manual This manual uses the following conventions: Abbreviations The glossary of this manual contains abbreviations, their phrases, and explanations for the abbreviations. Revision Controls The title page lists the revision level and the printing date of this manual. When the manual is revised, the revision level and the printing date are changed. Cross Referencing References to other documents give the document name and document number. Commands Commands do not include the Return Key at the end. If the manual describes a command, assume that depressing Return is required to enter the command. Most operating system commands require that you press the Return or Enter key after entering the command. This manual does not show these keys in command lines and assumes you use them when necessary. Long Command Lines This manual may present some command lines on more than one line due to margin restrictions. However, you normally should enter these commands into your workstation on a single line when possible. Mouse or Trackball Conventions You can use either a two-button mouse or multi-button mouse or trackball. Since you can swap use of the left and right buttons, this manual refers to the primary button (the left button) as the one used for most actions such as selections, and the right mouse button for specific actions. Table 1-1 lists terms describing actions you take with the mouse.

17 Introduction F Section 1 7 Table 1-1. Mouse or Trackball Terms Used in This Manual When Text Appears This Way... It Means... Point Click or Select Double-click Drag n Drop Move the pointer (arrow or other shape) until the tip rests on the object or area to which you want to point. Point to the item you want to select, then press and release the primary button without moving the mouse. If you want to select several items for deletion, hold down the Shift key and click the items to be deleted. Point to the item you want to select, then click the primary button twice rapidly without moving the mouse. Press and hold down the primary button while you move the mouse. When you have moved the mouse pointer to the position you want, release the primary button. Special Drag n Drop Tasks: Target: Hold the Shift key down and press and hold the primary button to drag an item onto its destination component. Move: Hold the Ctrl key down and press and hold the primary button to drag an item onto its destination component.

18 8 Section 1 F Introduction Typographic Conventions Table 1-2 describes the type styles this manual uses to distinguish different types of information. Table 1-2. Manual Conventions When Text Appears This Way... It Means... Installing and Using the Type SW2011 Data Historian Software BACKUP Turn off the power...an attribute is... Press the Return key... press the F12 key... press the Ctrl L key combination... Choose the OK button... select a file name from the list... Database CREATE filename The title of another manual or the introduction of a key term. (Helvetica font, italic) An operating mode or status, or a key function (used instead of a specific keyboard key). (Helvetica font, upper case) An emphasized or new term. A named keyboard key. Some keyboards indicate Enter instead of Return. An explanation of the key s acronym or function, if required, immediately follows thefirstreferencetothekey Press and hold the first key, press the second key, then release both keys. You can either click on the button by moving the cursor to point to it and pressing the primary button on the pointing device (mouse or track-ball), or press the Tab key and up or down arrow keys to select (or highlight) the button, then press the Enter key. A message or prompt that appears on a screen. (Courier font) An entry which you should make (in the same format as it appears on the printed page). Examples are commands you enter at an operating system prompt and keywords in a configuration source file. (Courier font, bold) Theguidelineforthekindofitemtotype in. You use the name applicable for your system. (Courier font, bold italic)

19 Introduction F Section Cautions and Notes Cautions and Notes attract attention to essential or critical information in this manual. The types of information included in each are explained in the following: 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 equipment, interruption of normal software operation, or cause a long term health hazard. Note... Notes have this form and symbol. Notes contain installation, operation, or maintenance procedures, practices, conditions, statements, and so forth, that alert you to important information which may make your task easier or increase your understanding. 1.7 Control Desktop and ENVOX Documents Although Control Desktop and ENVOX software are your primary configuration tool, the documentation is also a tool for getting the most value out of developing an effective configuration. Different users require different documentation support, depending on their background and the tasks they are doing.

20 10 Section 1 F Introduction The documentation available for Control Desktop P2.0 and ENVOX P4.0 Configuration Software includes: Getting Started with Control Desktop, PN6.3:SW3311:G (Revision A May 1998) Using Control Desktop Modules, UM6.3:SW3311:M (Revision A May 1998) Note... Only ENVOX version P4.0 software is compatible with Control Desktop version P2.0. Use only the indicated manuals with Control Desktop version P2.0 and ENVOX version P4.0 software. Documents available for ENVOX configuration software version P4.0 includes the following items: Installing and Upgrading ENVOX Configuration Software on DEC VAX and AXP Systems, PN6.1:SW3151:VMS (Revision B une 1998) Installing and Upgrading ENVOX Configuration Software on HP-UX Systems, PN6.2:SW3153:HPX (Revision C une 1998) Using ENVOX Configuration Software, UM6.1:SW3151 (Revision une 1998) The Technical Reference to ENVOX Configuration Software, TR1.0:SW3151 (Revision H une 1998) The System manager s Guide to ENVOX Configuration Software, SM1.0:SW3151 (Revision E une 1998) Installing and Using the ENVOX Open Database, UM6.2:SW3152 (Revision F une 1998)

21 Introduction F Section 1 11 Online and Web help screens: describe the menu options, forms, and each field on the forms, and provide navigation help. The screens are embedded in the ENVOX software. Configuration engineering manuals: describe the functions of the PROVOX products so that you can apply the right functions to your process. The manuals provide guidelines for using ENVOX forms specific to the associated product. Relational database documents: You can purchase ENVOX software with or without the Sybase relational database. When you purchase ENVOX software with the relational database, you also receive a complete set of relational database documents. 1.8 Related Documents Operating system manufacturers make many manuals available for their software products. Manuals that may be especially helpful when you install Control Desktop are: HP-UX System Administrator Tasks Manual OpenVMS, Version 6.1, Installation and Upgrade Manual OpenVMS User s Manual OpenVMS DCL Dictionary: A M OpenVMS DCL Dictionary: N Z OpenVMS System Manager s Manual: Essentials OpenVMS System Manager s Manual: Tuning, Monitoring, and Complex Systems OpenVMS System Management Utilities Reference Manual: A L OpenVMS System Management Utilities Reference Manual: M Z

22 12 Section 1 F Introduction Microsoft Windows NT Resource Kit V V V V Volume 1 -- Microsoft Windows NT Resource Guide Volume 2 -- Microsoft Windows NT Networking Guide Volume 3 -- Microsoft Windows NT Messages Volume 4 -- Optimizing Microsoft Windows NT Microsoft Windows NT Server Resource Kit V V V V Volume 1 -- Microsoft Windows NT Server Resource Kit Volume 2 -- Microsoft Windows NT Server Resource Guide Volume 3 -- Microsoft Windows NT Server Networking Guide Volume 4 -- Microsoft Windows NT Server Internet Guide 1.9 Electronic Documentation This manual is also available in DOCVUEt Electronic Documentation which is a CD-ROM set. The CD-ROMs contain current and past Fisher-Rosemount Systems sales literature, manuals, and technical service bulletins. DOCVUE documentation runs on OpenVMS, UNIX, and Microsoft Windows systems with the advantages of full-text searches, menus, bookmarks, browsing, and point-and-click navigation. We recommend that you call your Fisher-Rosemount Systems representative or sales office and find out more about DOCVUE documentation.

23 Introduction F Section Where to Find Answers for Product and Document Questions If you believe that this product is not performing as expected, or if you have comments about this manual, please contact your Fisher-Rosemount Systems representative or sales office. You may also complete and send in the Reader Evaluation Form located in the front of this manual. We also appreciate your suggestions on ways to improve any page of the manual. Please mark your suggestions on a copy of the page and include it with the evaluation form. Thank you for providing this information.

24 14 Section 1 F Introduction

25 Using the Online Help Systems F Section 2 15 Figure 2-Table UsingtheOnlineHelpSystems The Control Desktop online help is your main source of information as you develop a configuration database for your process control system. The built-in help system contains extensive procedural and quantitative information about all aspects of using Control Desktop to configure your system. In addition, you can add your own help system to meet your site-specific requirements. 2.1 Using the Built-in Help Systems Release P2.0 of Control Desktop contains two types of help systems. The standard Windows-based online help system provides in-depth information on using and exploring Control Desktop and its associated modules (except for the Diagnostics module). The Diagnostics help system consists of HTML files that are accessible through the Diagnostics module and provides information on using the module Using the Online Help System You can search the help system in several ways to find the topic in which you are interested. The way you initially access the help system depends on whether you want general help or context help.

26 16 Section 2 F Using the Online Help Systems Accessing General Help The Help Topics window appears when you press the F1 key, or select the Help -> Contents option. The Help Topics window contains three tabs: Contents displays a list of the contents of the Control Desktop help file. To display a topic or subtopic, either: V V double--click on the topic name to open it select a topic name and click the Display button to open the topic Repeat this process as often as necessary to find the information you need. Index displays a list of topics based on the keyword you enter in the search field. When you press Enter after you enter the keyword, the help system displays a list of topics containing that word. To display one of the topics in the list: V V double--click on the topic name to open it select a topic name and click the Display button to open the topic Find displays every instance of the keyword you enter in the search field. When you press Enter after you enter the keyword, the help system displays a more comprehensive list of topics containing that word. The Find tab works much like the Index tab. The Control Desktop Help window appears when you select a topic from the Contents window. The Control Desktop Help window has a top--level menu and a toolbar.

27 Using the Online Help Systems F Section Accessing Context Help In addition to the Help Topics window, you can access context help that is directly related to the window or dialog box you are viewing within Control Desktop, such as valid entries, numerical ranges, and so on. To access context help, do one of the following (some options are available only when certain dialog windows are open): Press Shift+F1 From the Help menu, select the Context Help option Click on the Help button The help topic that appears relates directly to the current window or dialog box. You can view the information in the help topic and can access information it contains. You can also use the toolbar to display the Help Topics window to view a different help topic Using the Diagnostics Help System The Control Desktop P2.0 Diagnostics module has its own Web--based help system, separate from the traditional MS Windows online help system. Once you have logged into the Diagnostics module using your Web browser, access the help system by selecting the Help link at the top of any Diagnostics Web page. This creates a separate Web browser window to display the Diagnostics help. The help window is divided into two frames. The left frame contains a table of contents, and the right frame displays the text for a selected help topic.

28 18 Section 2 F Using the Online Help Systems 2.2 Control Desktop User -Defined Online Help You can add your own site-specific help file which is accessible from the Help -> User Defined Help in the top level menu. You add your help file by defining a path in Control Desktop so that it recognizes your help system and then writing your help system. Once the path is defined and the help screens are written, you can open your help screens with the normal Control Desktop help menu as noted above. To define the help file and path, use the Control Desktop Options dialog box. Follow this procedure: 1. Select Admin -> Options to display the Control Desktop Options dialog box. 2. In the dialog box, select the Edit tab. 3. Enter the full path and filename of the User -defined Help File. Alternatively, click the Browse button, find the help file, and select the appropriate file. The user--defined help file does not necessarily have to be in a standard MS Windows help format. It may be an ASCII text file, for example.

29 Product Overview F Section 3 19 Figure 3-Table Product Overview Type SW3311 Control Desktop P2.0 software provides an MS Windows environment for configuration engineering functions. Control Desktop uses an MS Windows NT Graphical User Interface (GUI) and works with ENVOXr P4.0 configuration software and databases. The Windows PC client(s) communicate with ENVOX P4.0 database servers which themselves run on the DEC OpenVMS VAX, DEC OpenVMS AXP, and HP platforms. With this GUI environment, you can use a mouse device to explore and use the Control Desktop software for your configuration activities. 3.1 Similarities Between Control Desktop and ENVOX Software Control Desktop P2.0 provides configuration support for current PROVOXr devices. Control Desktop streamlines and simplifies the configuration process for the configuration engineer. Version P2.0 is the second phase in several planned iterations of Control Desktop. Each release of Control Desktop adds a number of features, many of which are also provided by ENVOX software. Note... Only ENVOX version P4.0 software is compatible with Control Desktop version P2.0.

30 20 Section 3 F Product Overview Control Desktop architecture retains the fundamental client/server configuration found in ENVOX P4.0. Therefore, Sybase provides all of the client/server functions, and the system operates in conjunction with ENVOX P4.0. Both Control Desktop clients and ENVOX software clients access the same server and databases. 3.2 Differences Between Control Desktop and ENVOX Software Major differences in Control Desktop are the MS Windows graphical user interface and the capability of manipulating multiple items simultaneously. In addition, the client software contains the configuration application and Generate, Download, and FST Translate functions, as well as a Web-based Diagnostics utility. The client manages these applications through a software layer called CDOS, which is installed with the ENVOX software. The architecture of Control Desktop has two major components: The client user interface runs on a PC with the MS Windows NT operating system. The Sybase server contains the ENVOX databases and the CDOS software. Some of the important features under this architecture are: Multiple clients may connect through the CDOS layer to multiple Sybase servers. The client can make connections to one server at a time with access to multiple servers possible. The client can browse more than one database. However, data can be modified only in the current database.

31 Product Overview F Section 3 21 The architecture of the Control Desktop software and its interfaces with the ENVOX P4.0 software are illustrated in Figure 3-1. Platform: Windows NT Control Desktop PC Client Interface Client Based Applications X--Window Interface Existing ENVOX Servers on Platforms VAX/AXP/HP SQL Commands Data Rows Control Desktop CDOS Application ENVOX Server Processing ENVOX Item Buffering ENVOX R Client Figure 3-1. Control Desktop System Architecture 3.3 Configuration with Control Desktop With Control Desktop, you configure and maintain your PROVOX control system with the same target device functions as in ENVOX P4.0, but the use of an MS Windows NT-based client eases the tasks needed to configure your system. In Control Desktop, explorers provide a structure that enables you to graphically and rapidly search through your database to find items for configuration or change. In addition, you may set the explorer entry point to a specific device or I/O based on an item s current tag.

32 22 Section 3 F Product Overview Configuration in Control Desktop can be done in two ways. First, you may use a set of tabbed forms for each item that enables you to determine which configuration items need data. When you select an item type for configuration, you are presented with a clear view of the configuration windows that need information. Second, you may use the Matrix (spreadsheet-like) windows, which enable you to manipulate multiple items at the same time. Refer to the online help system for information and instructions on using either of these Control Desktop configuration options. 3.4 Legacy Device Support Even though Control Desktop software is designed to fully support current PROVOX devices, the product provides limited support for a number of older devices. Control Desktop software does not support the creation, modification of source data, or download for the devices shown in Table 3-1. Table 3-1. Device Configurable IAC/Computing MUX PCIU Trend UOC Series 10 UOC ABE UOC UOC Plus IFC Pre-P5.0 PROVUEr Consoles Legacy Device Support Limitations Point Type Configurable DCP IAC Computing Point MUX Points PCIU Points N/A Controller points cannot be sourced on these devices. Points can not be sourced on the device The device definition or I/O can not be edited The device itself can not be downloaded Controller points cannot be sourced on these devices. Console points cannot be sourced on these devices.

33 Product Overview F Section 3 23 Control Desktop software supports the Unit Operations Controller (UOC) Series 10 device in the following ways: The device can be viewed in the Control Desktop explorers Points already sourced on the device can be re-targeted to consoles 3.5 Exploring in Control Desktop There are two main methods of exploring in Control Desktop: Top Level Application Menu Explorers The top level menu contains options that perform the Control Desktop functions. With this menu, you can select menu options with your mouse to move around Control Desktop, as well as open Control Desktop modules such as Control Designer, and to carry out configuration activities. The menu always appears when you open Control Desktop and is always available for your use regardless of where you are located in Control Desktop. With the Explorers, you have true MS Windows Explorer capabilities. You can move quickly to any portion of your configuration information, examine the configuration information that is related to your place in the system, and carry out configuration activities. You choose where you want to examine your configuration.

34 24 Section 3 F Product Overview 3.6 Control Desktop User Administration Control Desktop user accounts fall into two categories: Application User accounts provide user access to specific major Control Desktop modules and control database access and capabilities. Machine User accounts provide access to the Control Desktop clients themselves Subsection contains complete information on user administration and accounts.

35 Installing and Setting Up Control Desktop Software F Section 4 25 Figure 4-Table Installing and Setting Up Control Desktop Software These instructions enable you to carry out the installation of Control Desktop P2.0 on a Windows NT workstation. Note... Fisher-Rosemount Systems recommends that you read this information fully before you start any installation. The most current version of this information is duplicated online, and is accessible from the first installation screen. This Section contains: Full installation instructions, split up into three stages, as described in subsection 4.1. More general information about installation, including what gets installed, and how to de-install P2.0, should you need to.

36 26 Section 4 F Installing and Setting Up Control Desktop Software 4.1 The Stages of Installation You can split the installation of Control Desktop P2.0 into the following stages: Stage 1: Before You Begin this includes upgrading the ENVOX databases and finding out what Sybase and CDOS server names and addresses you are going to use for ENVOX P4.0 and CDOS P2.0 servers. Stage 2: Match Your Scenario this depends on whether you have Control Desktop P1.0 installed on your PC and, if so, whether you want to keep a version on the PC or remove it when upgrading to P2.0. Stage 3: Install Control Desktop P2.0 the procedure you use depends on your scenario. It may include altering INI files, and SYBASE and PATH variables. When the installation is completed, you can run Control Desktop to make sure the installation is successful. If it does not, there is some troubleshooting information available to help you diagnose and fix your problem. Note... There are some special considerations for PCs that have Control Desktop P1.0 currently installed. These are explained within stages 2 and 3 of the installation instructions.

37 Installing and Setting Up Control Desktop Software F Section General Information Note... This section provides general information about what you may install. Fisher-Rosemount Systems recommends that you read it before you start any installation. The Control Desktop P1.0 release required the PC client installation to be carried out using a specific user account. Once the software had been installed under this account on a given PC, only that user account could access Control Desktop. The Control Desktop P2.0 release requires the PC clients to be installed using an account with Windows NT administrator privileges. The administration privileges are required to install Sybase Open Client and to set up ODBC drivers and data sources. This makes the Control Desktop Start menu icons available to all valid Windows NT user accounts on the specific PC. The main advantages of this approach are: Multiple user accounts can access a single copy of Control Desktop on a given workstation. Each user account has its own specific Control Desktop working area, and its own custom user environment. User preferences are not shared. A user can run Control Desktop on another workstation and keep preferences intact, because they are saved with user s profile. Information on application user accounts is provided in the section Control Desktop User Administration Overview. The installation process uses long filename formats.

38 28 Section 4 F Installing and Setting Up Control Desktop Software What You Can Install There are two separate installation processes you can carry out, for: Control Desktop P2.0 Install this on ALL workstations that are to use the Control Desktop user interface. These instructions describe how to install Control Desktop. Diagnostics module The Control Desktop Diagnostics Web Server extensions software only needs to be installed on one PC in your network -- a PC running a Web Server. Normally your Windows NT system administrator installs this. Once the Control Desktop Diagnostics extensions have been installed on the Web Server PC, users on any other workstation that has a Web browser can run Control Desktop Diagnostics. A Web browser (such as Internet Explorer or Netscape Navigator) is the only software required to display Control Desktop Diagnostics. Instructions for installing Diagnostics are provided in the Installing Control Desktop Diagnostics section What Gets Installed During the Control Desktop P2.0 installation, the following components are added: Sybase Open Client and Net Libraries Sybase System 10 ODBC Driver Microsoft Access ODBC Driver Control Desktop DLLs and executables Control Designer database and executables

39 Installing and Setting Up Control Desktop Software F Section Directory Structures The default folder/directory structures depend on whether Control Desktop P1.0 has been previously installed on the PC. If Control Desktop P1.0 is not installed on the workstation, the default locations are: Control Desktop Software: C:\Program Files\FRSI\ControlDesktop Sybase Open Client: C:\SQL10 If Control Desktop P1.0 is installed on the workstation, the default locations are: Control Desktop Software: C:\Program Files\FRSI\ControlDesktopP20 Sybase Open Client: C:\SQL ODBC Data Sources The following ODBC data sources are set up during the installation. These are required for Control Designer to communicate with the Open Server and the Control Designer system database: Control Desktop: Sybase System 10 Control Designer P2 System DB: Microsoft Access Driver

40 30 Section 4 F Installing and Setting Up Control Desktop Software Registry Modifications Control Desktop uses the Registry to store information it needs to run, i.e. the name of the CDOS server to use. This information is added under the key: HKEY_LOCAL_MACHINE\SOFTWARE\FRSI\Control Desktop\2.0 Users who modify preferences within Control Desktop have the changes saved to a similar section under HKEY_CURRENT_USER. This allows them to move between PCs and retain their Control Desktop preferences. It also means that, for a first time user, the preferences are taken from the workstation s setting Stage 1: Before You Begin Before starting the installation process for Control Desktop P2.0, do the following: Make sure that the ENVOX databases have been installed. Find out and make a note of what Sybase and CDOS server names and addresses you are going to use for ENVOX P4.0 and CDOS P2.0 servers. You need these when completing the installation, so that Control Desktop can be set up to access the correct servers. If you are a Control Desktop P1.0 user, decide whether you want to be able to run version P1.0 after you have installed P2.0. In most situations, Fisher-Rosemount Systems recommends that you do not. In addition to the above, you may find it useful to read and understand the user administration facilities available in Control Desktop P2.0 before you start the installation. Control Desktop Administration has been enhanced.

41 Installing and Setting Up Control Desktop Software F Section Upgrading ENVOX Databases for Use with Control Desktop P2.0 Summary Before you can install and use Control Desktop P2.0, you must have at least one server with ENVOX P4.0 on it. The installation of ENVOX P4.0 should already have been carried out by a system administrator. Note... The information in this section is simply a summary of what should have been done already. If it hasn t been done, an administrator must carry out these instructions. For full instructions, refer to either Installing and Upgrading ENVOX Configuration SoftwareonHP-UXSystems (PN6.2:SW3151:HPX), or Installing and Upgrading ENVOX Configuration Software on DEC VAX and DEC AXP Systems (PN6.2:SW3151:VMS), as appropriate. There are two upgrade scenarios for the ENVOX P4.0 / Control Desktop P2.0 database upgrade process, depending on what version of ENVOX you currently have. For users with ENVOX P3.4 systems, refer to subsection For users with pre-envox P3.4 systems, refer to subsection (For new users of ENVOX and Control Desktop, simply install ENVOX P4.0, install Control Desktop P2.0, and use the interactive database upgrade facility from within Control Desktop to make the databases compatible with Control Desktop P2.0.)

42 32 Section 4 F Installing and Setting Up Control Desktop Software Scenario A: ENVOX P3.4 Systems Note... If you currently have an ENVOX P3.4 system (not earlier) and want to upgrade to ENVOX P4.0, then read this section. To upgrade ENVOX from P3.4 to P4.0, follow these steps: 1. Run the ENVOX P4.0 installation. This displays a list of ENVOX P3.4 databases. 2. Select the databases you want to transfer out with the PDX utility. 3. Continue with the installation, including the upgrade of Sybase and the installation of the new ENVOX executables. 4. Open the ENVOX P4.0 administration application, create databases for PDX load, and load the saved databases from the saved PDX dumps. They are automatically upgraded to ENVOX P4.0. The databases you have selected are automatically upgraded to the Control Desktop P2.0 version. This automatic upgrade is triggered on a per-database basis by the existence of the P1.0 database design date stamp in a given database. That is, if the database has been upgraded for use with Control Desktop P1.0 previously, it is automatically upgraded for use with Control Desktop P Upgrade or Install to Control Desktop Open Server (CDOS) on the workstation. Control Desktop P1.0 licenses are preserved, and will function with Control Desktop P2.0.

43 Installing and Setting Up Control Desktop Software F Section Either upgrade or install Control Desktop P2.0 clients, depending on whether or not you have Control Desktop P1.0 on the PC. The first part of the procedure involves removing Control Desktop P1.0, if you have it. Note... It is possible to install and run Control Desktop P2.0 without removing an existing P1.0 installation, although Fisher-Rosemount Systems recommends that you do this only if essential. The procedure you follow for the Control Desktop P2.0 upgrade or installation is fully described in subsection 4.1 and in the online help system. 7. (Optional) If there is an ENVOX P4.0 database that you want to use with Control Desktop that has not previously been upgraded for use with Control Desktop P1.0, then use Control Desktop to upgrade the ENVOX database for use with Control Desktop Scenario B: Pre-ENVOX P3.4 Systems Note... If you currently have a pre-envox P3.4 system, such as P2.0, P3.0, P3.2, or P3.3, and want to upgrade to ENVOX P4.0, then read this section. To upgrade ENVOX from pre-p3.4 to P4.0, follow these steps: 1. Before installing ENVOX P4.0, run your existing administration application, and use PDX to transfer out the databases.

44 34 Section 4 F Installing and Setting Up Control Desktop Software 2. Uninstall (remove) that version of ENVOX / Sybase. (The ENVOX P4.0 installation process will install Sybase System 10 and the ENVOX P4.0 executables from scratch.) 3. Install ENVOX P Install Control Desktop Open Server (CDOS) P2.0 on the workstation platforms. 5. Open the ENVOX P4.0 administration application, create logical devices, create databases for PDX load, and load the saved databases from the saved PDX dumps. They are automatically upgraded to ENVOX P Install Control Desktop P2.0, using the procedure described in subsection 4.1 and in the online help system. 7. Use Control Desktop to upgrade each ENVOX database you want to use with Control Desktop Control Desktop User Administration Overview Control Desktop user accounts fall into two categories: Application User accounts provide user access to specific major Control Desktop modules and control database access and capabilities. Machine User accounts provide access to the Control Desktop clients themselves Application User Accounts Figure 4-1 shows an overview of the Control Desktop P2.0/ENVOX P4.0 administration facilities. The diagram shows a Sybase server in which two ENVOX user databases exist. A single Control Desktop Open Server (CDOS) is shown. It can run on the same computer as the Sybase server, or on a separate computer.

45 Installing and Setting Up Control Desktop Software F Section 4 35 Control Desktop Administration Diagnostics Administration ENVOXr Administration CDOS ENVOX Database ENVOX Database SYBASE Server Figure 4-1. Control Desktop P2.0 / ENVOX P4.0 Administration Overview The diagram also shows three clients, each having an administration capability. The following subsections describe each client s administration capabilities ENVOX Database User Administration The ENVOX P4.0 installation contains the ENVOX administration application, which runs on the ENVOX workstation client. Its functionality is mostly unchanged from ENVOX version P3.4. In terms of Control Desktop, the ENVOX administration utility is important in that it is required to do system administration tasks, such as creating and backing up databases. It is also used to create database users within the Sybase server. The Control Desktop Project Administrator for that database can then grant and revoke access for the database.

46 36 Section 4 F Installing and Setting Up Control Desktop Software The system administrator can create either standard ENVOX database users for a single database, or database administration users with privileges across all databases. For Control Desktop purposes, the ENVOX database user profile does not require database administration privileges. Instead, the Control Desktop Project Administrator for each database can create additional Project Administrators with database privileges for that particular Control Desktop database Control Desktop Client Administration The Control Desktop Client Administration module is new to the P2.0 release. This module allows project leaders to manage their team s access to project data without having to know the Sybase system administrator (SA) passwords. This approach allows more definition and distinction between Sybase System Administrator functions (like creating new databases and backing up existing databases) and Control Desktop Project Administrator functions (like performing project--specific tasks within a single database, such as enabling Audit Trail options, switching Verify mode on and off, and so on). The Control Desktop Client Administration module is structured for two user roles: Project Administrator can define user roles and assign access privileges that determine which Control Desktop features that user has, such as read--only or read/write privileges. The Project Administrator can also grant and revoke user access to that database depending on the project requirements of that user. Project Engineer the standard user role that is assigned to all typical Control Desktop configuration users. A Project Engineer s role can be customized by the Project Administrator to grant or restrict access to specific areas of the Control Desktop software.