GEH-6126_Vol_I

(1)

g

GE Industrial Systems

GEH-6126A Volume I (1 of 2) (Supersedes GEH-6126)

(2)

(3)

Document: GEH-6126A Volume I (1 of 2)

(4)

Printed in the United States of America.

GE provides the following document and the information included therein as is and without warranty of any kind, express or implied, including but not limited to any implied statutory warranty of merchantability or fitness for particular purpose.

These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency to be met during installation, operation, and maintenance. The information is supplied for informational purposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications, and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflected herein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at any time. This document is intended for trained personnel familiar with the GE products referenced herein.

GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not provide any license whatsoever to any of these patents. All license inquiries should be directed to the address below. If further information is desired, or if particular problems arise that are not covered sufficiently for the purchaser’s purpose, the matter should be referred to:

GE Industrial Systems Post Sales Service 1501 Roanoke Blvd.

Salem, VA 24153-6492 USA

Phone: + 1 888 GE4 SERV (888 434 7378, United States) + 1 540 378 3280 (International)

Fax: + 1 540 387 8606 (All)

(“+” indicates the international access code required when calling from outside the USA) This document contains proprietary information of General Electric Company, USA and is furnished to its customer solely to assist that customer in the installation, testing, operation, and/or maintenance of the equipment described. This document shall not be reproduced in whole or in part nor shall its contents be disclosed to any third party without the written approval of GE Industrial Systems.

Document Identification: GEH-6126A Volume I (1 of 2) Technical Writer/Editor: Teresa Davidson

Technical Responsibility: Michael Good

ARCNET is a registered trademark of Datapoint Corporation.

CIMPLICITY and Genius are registered trademarks of GE Fanuc Automation North America, Inc. Ethernet is a trademark of Xerox Corporation.

Excel, Microsoft, NetMeeting, Windows, and Window NT are registered trademarks of Microsoft Corporation.

Modbus is a registered trademark of Schneider Automation. Pentium is a registered trademark of Intel Corporation.

(5)

Safety Symbol Legend

Indicates a procedure, condition, or statement that, if not strictly observed, could result in personal injury or death.

Indicates a procedure, condition, or statement that, if not strictly observed, could result in damage to or destruction of equipment.

Indicates a procedure, condition, or statement that should be strictly followed in order to optimize these applications.

(6)

To prevent personal injury or equipment damage caused by equipment malfunction, only adequately trained personnel should modify any

programmable machine.

The example and setup screens in this manual do not reflect the actual application configurations. Be sure to follow the correct setup procedures for your application.

(7)

We welcome comments and suggestions to make this publication more useful.

Your Name Today’s Date

Your Company’s Name and Address Job Site

GE Requisition No. Publication No. Your Job Function / How You Use This Publication

Publication Issue/Revision Date

If needed, how can we contact you? Fax No.

Phone No. E-mail Address

General Rating

Excellent Good Fair Poor Additional Comments

Contents ¡ ¡ ¡ ¡ _____________________________________________________________ Organization ¡ ¡ ¡ ¡ _____________________________________________________________ Technical Accuracy ¡ ¡ ¡ ¡ _____________________________________________________________ Clarity ¡ ¡ ¡ ¡ _____________________________________________________________ Completeness ¡ ¡ ¡ ¡ _____________________________________________________________ Drawings / Figures ¡ ¡ ¡ ¡ _____________________________________________________________ Tables ¡ ¡ ¡ ¡ _____________________________________________________________ Referencing ¡ ¡ ¡ ¡ _____________________________________________________________ Readability ¡ ¡ ¡ ¡ _____________________________________________________________

Specific Suggestions (Corrections, information that could be expanded on, and such.) Page No. Comments

______

__________________________________________________________________________________

______

__________________________________________________________________________________

______

__________________________________________________________________________________

______

__________________________________________________________________________________

______

__________________________________________________________________________________

______

__________________________________________________________________________________

Other Comments (What you like, what could be added, how to improve, and such.)________________________________________________

___________________________________________________________________________________________

g

Reader Comments

General Electric Company

g

Reader Comments

g

Reader Comments

To: GE Industrial Systems Documentation Design, Rm. 291 1501 Roanoke Blvd. Salem, VA 24153-6492 USA Fax: 1-540-387-8651 (GE Internal DC 8-278-8651)

g

Reader Comments

(8)

...

Fold here and close with staple or tape

...

____________________________

GE Industrial Systems

Documentation Design, Rm. 291

1501 Roanoke Blvd.

Salem, VA 24153-6492 USA

...

Fold here first

...

Place stamp here.

(9)

Safety Symbol Legend Reader Comments Chapter 1 Overview Introduction ...1-1 HMI Overview...1-2 Product Features...1-2 HMI Components...1-3 Graphic Displays ...1-4 Communications...1-6 Optional Features ...1-7 Application-Specific Features ...1-7 Technical Specifications...1-7 Related Documentation ...1-8 How to Use This Document ...1-9 Text Conventions ...1-9 How to Get Help...1-10

Chapter 2 Quick-Start Procedures

Introduction ...2-1 Starting Up HMI...2-2 Alarm Displays...2-3 Opening Projects ...2-4 Other Tools...2-5 Dynamic Rung Display ...2-5 Trip History...2-5 Trip Log Viewer...2-5 Demand Display...2-6 Alarm Logger Control ...2-6 Hold List Display (Steam Turbine Applications)...2-6

Chapter 3 Display-Only Programs

Introduction ...3-1 Dynamic Rung Display ...3-2 File Structure ...3-2 Dynamic Rung Display Windows ...3-3 Starting the Dynamic Rung Display...3-6 Selecting a Sequencing Display Screen...3-7 Using the Find All Function...3-7

(10)

Contents — Continued

Trip Log Viewer ...3-14 Trip Log File ...3-14 Trip Log Viewer Dialog Box...3-14 Viewing Results...3-15 Starting the Trip Log Viewer...3-15

Chapter 4 Control (Command) Programs

Introduction ...4-1 Demand Display ...4-2 Starting Demand Display...4-2 Working with Files ...4-3 Demand Display Windows...4-4 Data Area Description ... 4-6 Command Target Types ... 4-6 Using Demand Display...4-7 Displaying, Creating, and Modifying Screens... 4-7 Working with Command Targets ... 4-11 Other Options ... 4-13 Command Line Configuration...4-13 Commands and Arguments ... 4-13 Using Multiple Arguments... 4-14 Alarm Logger Control ...4-15 Starting the Alarm Logger Control... 4-15 Hold List (Steam Applications) ...4-16 Hold List Points...4-16 Hold List Programs...4-16 Hold List Rules...4-16

Chapter 5 CIMPLICITY Displays

Introduction ...5-1 CIMPLICITY ActiveX Objects...5-2 Manual Synchronizing Display ...5-2 Triggered Plot (Valve Travel) ...5-6 Alarm Filtering in HMI Servers...5-8 Configuring Users ...5-8 Configuring Resources ...5-12 Configuring Alarm Filters ...5-14 Examples of Screens for Filtered Alarms...5-23 Currently Implemented Filters...5-25 Extended Alarm Commands...5-26 Reactive Capability Display ...5-28

(11)

Contents — Continued

Chapter 6 CIMPLICITY Project Configuration

Introduction ...6-1 Using Workbench...6-2 Opening a Project ...6-3 Signal Manager...6-4 Setup...6-4 Signals ...6-5 Alarms ...6-6 Importing Signals ...6-8 External Alarm Manager ...6-10 SDB Exchange ...6-10 SDB Utilities ...6-10 Modbus® Data Interface ...6-11 OLE for Process Controls (OPC) ...6-12

Appendix A HMI Function Reference

HMI Functions for GE Turbine Controllers ...A-1 CIMPLICITY HMI Supported Functions ...A-4

Appendix B Alarm Overview

Introduction ... B-1 Hold List Alarms (Steam Turbine Only) ... B-2 Process Alarms ... B-2 Process (and Hold) Alarm Data Flow... B-2 Diagnostic Alarms ... B-3

Glossary Index

(12)

(13)

Chapter 1 Overview

Introduction

GE document GEH-6126A Volume 2 describes HMI maintenance features introduced in this chapter.

The Human-Machine Interface (HMI) for SPEEDTRONIC turbine control is a user-friendly operator interface for real-time control of power-plant processes and equipment. It runs on a pc-based workstation using a Microsoft® Windows NT® client-server architecture. The HMI provides operator display and control for the Mark IV, Mark V, Mark V LM, and Mark VI turbine controllers.

This document covers HMI operation. It is written as a guide to assist the operator in using applicable HMI and supported CIMPLICITY®_{HMI functions with the}

SPEEDTRONIC Mark IV, Mark V, Mark V LM, and Mark VI turbine controllers. Refer to How to Use This Document for more information.

This chapter provides a brief overview of the HMI, including both operator and maintenance features. Additionally, it defines the document content and structure to help the user better understand the information provided.

This chapter is organized as follows:

Section Page HMI Overview...1-2 Product Features...1-2 HMI Components...1-3 Graphic Displays ...1-4 Communications...1-6 Optional Features ...1-7 Application-Specific Features ...1-7 Technical Specifications...1-7 Related Documentation ...1-8 How to Use This Document ...1-9 Text Conventions ...1-9 How to Get Help...1-10

(14)

HMI Overview

The CIMPLICITY HMI is a product of GE Fanuc Automation.

HMI functions (listed in Appendix A) are provided by the Turbine Control Interface (TCI), CIMPLICITY Bridge (TCIMB), and GE Turbine Control Systems Solutions CD. Additionally, the HMI supports many functions of the CIMPLICITY HMI, for graphical interface and some support functions (see Appendix A).

The HMI can be configured to operate with a variety of system devices, integrating plant operation at a single level. Plant operators and engineers can view and control plant equipment through a common interface.

The toolbox is GE’s Windows-based software package used for controller configuration and diagnostics.

Note The GE Turbine Control Systems Solutions CD contains the Turbine Control

System Toolbox (toolbox), Data Historian, and Trend Recorder programs. Mark VI turbine controllers use the toolbox as a configuration and diagnostic interface. An operator can use the HMI for the following turbine control functions:

• Monitor one or more turbines through graphical displays (for example, alarms, wheelspace temperatures, and vibration feedback)

• Issue commands to the selected turbine or driven device (for example, Start, Stop, Cooldown On, Auto, and Raise Speed/Load)

Product Features

The HMI contains a number of product features important for power plant control:

• Dynamic graphics

• Alarm displays

• Process variable trending

• Point control panel display (for maintenance)

(15)

HMI Components

The turbine control HMI consists of the following functional components (refer to Figure 1-1):

GFK-1180 provides a detailed description of the CIMPLICITY product’s capabilities.

• CIMPLICITY HMI is used primarily to display turbine status screens, which enable an operator to monitor the unit(s). Refresh rate is typically 1 second. CIMPLICITY cannot configure the turbine control.

– HMI Server is the hub of the system, channeling data between the Unit Data Highway and the Plant Data Highway (Mark VI only), and providing data support and system management. The server also provides device

communication for both internal and external data interchanges.

– HMI Viewer provides the visual functions, and is the client of the server. It contains the operator interface software, which allows the operator or maintenance personnel to view screen graphics, data values, alarms, and trends, as well as to issue commands, edit control coefficient values, and obtain system logs and reports.

• Turbine Control Interface (TCI) is used to display higher speed data (faster than 1-second updates), and to configure and control a turbine unit. TCI allows remote access to turbine data and controls the following data functions: – Provides real-time device communications to the turbine control (Mark IV

and V)

– Provides turbine control configuration capabilities (Mark IV and V) – Collects data, alarms and forwards commands to the turbine control (Mark

VI)

– Maintains a data dictionary (Mark IV and V)

• TCIMB (TCI/CIMPLICITY Bridge, previously called CIMB or CIMBridge) is an interface between the CIMPICITY and TCI, as follows:

– Enables CIMPLICITY to collect data and alarms from a turbine unit – Forwards points (Mark IV, V, V LM) and alarms (all) to CIMPLICITY

• System database (Mark VI only) establishes signal management and definition for the control system. It provides a single repository for system alarm messages and definitions, and defines mapping between controller software and physical I/O. Additionally, it defines Ethernet Global Data (EGD) exchanges. The database is used for system configuration, but not required for running the system.

Depending on the size of the system, these elements can be combined into a single pc, or distributed in multiple units. The modular nature of the HMI allows units to be expanded incrementally as system needs change.

(16)

Point Database Alarm Queue Alarm Queue Data Dictionary Alarm Manager Point Manager Devcom (EGD...) External Alarm Manager Mark V RP Device Collector Devices P o int D a ta Point Alar ms Point Data Alarms Devices

CIMPLICITY TCIMB TCI

Figure 1-1. Data Flow Between HMI Components

Graphic Displays

The HMI uses the graphics and alarm features of the CIMPLICITY software to integrate controls from a variety of applications. The graphical displays offer realistic viewing in a real-time environment.

Screens are developed using preconfigured graphic building blocks that provide

commonality to different plant applications that use the HMI.

The HMI displays data and processes operator commands using screens that represent a variety of signals, their values, and units. Display items change color based on logic signals, while certain objects are dynamic and refresh with every data update, like bar graphs. High-speed viewing allows the displayed data to be updated once per second, and special tools allow collection and storage of data at rates as fast as 10 ms.

HMI graphic displays include main unit, vibration, sensor readings, control setpoints, alarms, permissives, logic forcing, demand display, sequence editor, dynamic rung display, trip history display, trending, and many others depending on the application. An operator can view alarms from any HMI on the network as they occur and to freeze the scrolling as needed to address an alarm condition. The alarm management feature provides options for response.

Figure 1-2 illustrates a typical Viewer screen using graphics to display real-time turbine data.

The associated printer(s) enables the operator to manually select and copy any display, to automatically log selected parameters, and to log alarms.

(17)

Figure 1-2. Sample HMI Display Showing Steam Turbine and Generator Data

The graphic system performs key HMI functions and provides the operator with real-time process visualization and control using the following:

GFK-139 provides a detailed description of the CimEdit and CimView applications.

• CimEdit is an object-oriented program that creates and maintains the user graphic screen displays. Editing and animation tools, with the familiar Windows environment, provide an intuitive, easy to use interface. Features include: – Standard shape library

– Object Linking and Embedding (OLE) – Movement and rotation animation

– Filled object capabilities, and interior and border animation

Alarm Detail display selection Shaft Vibration display selection Setpoint Entry selection Alarm Viewer window

(18)

• Alarm Viewer provides alarm management functions such as sorting and filtering by priority, by unit, by time, or by source device. Also supported are configurable alarm field displays, and embedding dynamically updated objects into CimView screens.

• Trending, based on Active X technology, gives users data analysis capabilities. Trending uses data collected by the HMI or data from other third-party software packages or interfaces. Data comparisons between current and past variable data can be made for identification of process problems. Trending includes multiple trending charts per graphic screen with unlimited pens per chart, and the operator can resize or move trend windows to convenient locations on the display.

• The point control panel provides a listing of points in the system with real-time values and alarm status. Operators can view and change local and remote set points by direct numeric entry.

• The basic control engine allows users to define control actions in response to system events. A single event can invoke multiple actions, or one action can be invoked by many events. The program editor uses a Visual Basic for

Applications compliant programming language.

Communications

Refer to GEH-6126 Vol. II and individual controller documents for more detail about the networks and protocol used for HMI communication.

Figure 1-3 shows the networks used by the HMI to communicate within a SPEEDTRONIC turbine control system.

TR

Historian HMI Server # 1 HMI Server # 2 ViewerHMI

Mark VI Plant Data Highway (Ethernet)

Mark VI Unit Data Highway (Ethernet)

Data Data

Mark IV Control System Freeway (CSF)

Mark VI Turbine Control I/O Mark IV Turbine Control I/O Mark V Turbine Control I/O Mark V Stagelink

(19)

For Ethernet TCP/IP communication to third party equipment, such as a distributed control system (DCS ), the HMI provides GE Industrial Systems standard messages (GSM) and Modbus®_{protocol. GSM application layer protocols support four classes}

of application-level messages: administration, event-driven, periodic data, and common request messages.

Alternatively, communication to remote DCS equipment is available through a Modbus interface, where the HMI acts as a slave to the DCS master. Such a system allows an operator at a remote location to initiate any operator command and to monitor turbine data.

Optional Features

Document GEH-6422 provides information about the

Historian.

The HMI supports a Windows NT®-based Historian computer, which collects and stores data from the control units for later analysis. OSI’s PI-ProcessBook®_provides

historical and real-time trending of all process data, and can run in the Historian and/or HMI Viewer. The HMI communicates with the Historian through the Ethernet-based Plant Data Highway (PDH) and through RS-232C lines. The HMI includes a time synchronization capability in both low- and high-resolution forms. When redundant time masters are available, all turbine controllers and operator interface units on a system automatically select the same, highest quality time master.

A Web Gateway allows operators to access HMI data from anywhere in the world over the Internet. Third party interfaces allow the HMI to exchange data with the DCS, programmable logic controllers, I/O devices, and other computers.

Application-Specific Features

When the HMI is paired with either the Mark V or the Mark VI turbine

controllers, the turbine control software tools can be added to as an integral part of

the HMI. The Mark VI features are based on the GE Control System Toolbox (toolbox).

When the HMI is used in our Integrated Control Systems (ICS) product line or as a

Balance-of-Plant (BOP) control interface, the ICS/BOP toolset becomes part of the

HMI.

Technical Specifications

Exact hardware and software specifications for the HMI are determined according to the customer’s needs and purchased options. The HMI workstation is typically sent to the customer with the HMI program already installed.

(20)

How to Use This Document

The user of this document should be familiar with the Microsoft Windows pc interface and experienced with SPEEDTRONIC controllers and operating turbine control systems.

For an exact outline of the document’s content and organization, refer to the Table of Contents.

This document is organized into the following chapters and appendices to assist an operator in understanding and using the HMI.

Chapter 1, Overview, provides an introductory product summary with related

reference information to assist the user.

Chapter 2, Quick Startup, serves as a reference to assist the operator in starting up

the HMI.

Chapter 3, Display-Only Applications, describes HMI programs for data display,

including sample screens.

Chapter 4, Control (Command) Applications, describes HMI programs for

displaying and controlling data, including sample screens.

Chapter 5, CIMPLICITY Displays, covers HMI functions that use CIMPLICITY

screens, including ActiveX objects and filtered alarms.

Chapter 6, CIMPLICITY Project Configuration, defines applications used to

configure a CIMPLICITY project.

Appendix A, HMI Function Reference, lists all current HMI functions and

identifies which SPEEDTRONIC controller includes each function.

Appendix B, Alarm Overview, a general overview of turbine controller alarms

viewed and addressed using the HMI.

Text Conventions

The following symbols, formatting, and presentation conventions are used in this document to assist the user.

Convention Meaning

Ø A procedure follows.

Numbered list Procedural steps to be followed in order (for example, 1, 2, 3). Alphabetized list Procedural substeps (of numbered steps) to be followed in

order (for example, a, b, c).

Bulleted (•) list Related items or procedures, but order does not matter. w A procedure with only one step.

Boxed (¨) list A checklist.

Arial Bold When describing software, indicates the actual command or option that is chosen from a menu or dialog box, or typed in a text box or at the command prompt.

(22)

How to Get Help

If help is needed beyond the instructions provided in the system documentation, contact GE as follows:

“+” indicates the international access code required when calling from outside the USA.

GE Industrial Systems Post Sales Service 1501 Roanoke Blvd.

Salem, VA 24153-6492 USA

Phone:+ 1 888 GE4 SERV (888 434 7378, United States) + 1 540 378 3280 (International)

Fax: + 1 540 387 8606 (All)

Note Please have the GE requisition or shop order number and the equipment serial

(23)

Chapter 2 Quick-Start Procedures

Introduction

A facility receives the HMI pre-loaded with all the programs and customized software required for the customer’s application. It is then configured during installation to automatically log on and open to the main operator screen when powered-up.

This chapter provides basic startup procedures to help the operator use the HMI. Detail of these HMI features is covered in the other sections of this document. This chapter is organized as follows:

Section Page

Starting Up HMI...2-2 Alarm Displays...2-3 Opening Projects ...2-4 Other Tools...2-5 Dynamic Rung Display ...2-5 Trip History...2-5 Trip Log Viewer...2-5 Demand Display...2-6 Alarm Logger Control ...2-6 Hold List Display (Steam Turbine Applications)...2-6

(24)

Starting Up HMI

Ø Ø Ø

Ø To start up the HMI and open your application

w Power up the pc if it is off, or press the three keys Ctrl+Alt+Delete all at once if the system needs to be restarted.

GFK-1180 describes CimView

in detail. When the pc starts up, it opens the CIMPLICITY Viewer (CimView) and displaysthe main operation screen for its custom application (see Figure 2-1). All needed programs are loaded and CIMPLICITY is started.

Note The HMI displays for your system are CimView screens (*.cim files), which may open before CIMPLICITY finishes loading. If at first the screen is not animated or setpoints fail, wait a few minutes for the startup to complete before beginning operation.

Figure 2-1. Example of HMI Starting Screen

Click buttons and other animated objects to open additional screens or objects.

Click to open screen displaying all alarms.

Select an alarm listed, then click the button for the desired for action

(25)

Alarm Displays

OCX is an object linking and embedding (OLE) custom control.

Alarm Viewer is an OCX object embedded into a CIMPLICITY HMI screen, as

shown in Figure 2-1. It provides alarm management functions such as sorting and filtering by priority, unit, time, or source device. Also supported are configurable alarm field displays.

Custom TCI programs are used to enhance the CIMPLICITY alarm viewer for Turbine applications. TCI provides the Silence, Lock, and Unlock Alarm Viewer features (see Extended Alarm Commands in Chapter 5).

Figure 2-2. Example of Alarm Display Screen Alarms are listed

in the display.

(26)

Opening Projects

Document GFK-1180 provides

detail about using Workbench. The CIMPLICITY Workbench is an application used to view, configure, organize,and manage projects. Refer to Chapter 5 for examples using Workbench. Ø

Ø Ø

Ø To open a project

1. Open the Windows File Explorer. 2. Open the f:\cimproj directory. 3. Double-click on the .gef file.

The Workbench display opens (see Figure 2-3).

Left to right: - Dynamic update - Stop project - Start project Left to right: - Configuration update - Status log - Project properties

- Project wizard Right pane views Help

Search Field chooser Properties Screens Points Application folder Runtime Alarms Objects in application Files or records associated with object

Fields chosen for display Figure 2-3. Sample Workbench Display

(27)

Other Tools

The following sections provide simple Windows-based start-up instructions for HMI display-only and control applications. However, they can also be started up and configured using typed in commands, as described in Chapters 3 and 4 of this document.

Dynamic Rung Display

Refer to Chapter 3 for more

information. The Dynamic Rung Display program is used to step through the controlprogramming of a Mark V controller. It displays the control rungs and blocks in a control sequence segment for a given unit. (Mark VI uses the toolbox for this function.)

Ø Ø Ø

Ø To open the Dynamic Rung Display

w On the Windows desktop, select Start, Turbine Control Maintenance Group,

Unit T#, then Dynamic Rung Display.

Trip History

information. The Trip History program provides a chronological record (log) of relevant datagathered by the unit control. The data is organized according to post-trip, pre-trip, and alarm categories.

Ø Ø Ø

Ø To view the Trip History

1. On the Windows desktop, select Start, Turbine Control Maintenance Group,

Unit T#, then Trip History.

2. From the Trip History dialog box (see Figure 3-3), select a valid unit from the

Select Unit list.

3. Click a Select Log option button for the type of historical data to be collected. 4. Click the Collect button to retrieve the data or the Cancel button to stop. You can retrieve only one type of data at a time. When the data retrieval completes successfully, the program displays the results in a separate window.

Trip Log Viewer

information. If TCI and HMI are running during Mark V controller trips, the programautomatically collects and stores data of the last ten trips in the HMI. (The HMI must also be communicating with the control.)

Ø Ø Ø

Ø To view the Mark V Trip log

Unit T#, then Trip Log Viewer.

2. From the Trip Log Viewer dialog box, select a valid unit from the Select Unit list box.

(28)

Demand Display

information. This display allows you to view values of a selected list of points.

Ø To load an existing Demand Display file

Unit T#, then Demand Display. 2. From the File menu, select Open.

3. Select the file from the directory that displays.

If no existing file is specified when using Demand Display, the default file

DEMAND01.DM2 (located in the F:\RUNTIME directory) loads.

Alarm Logger Control

information. The HMI’s Alarm Logger Control program allows you to select alarms and events tooutput to the printer. Ø

Ø Ø

Ø To print alarms or events using this program

Unit T#, then Alarm Logger Control.

2. Select the Unit and the Logger Function from the dialog box. 3. Click OK.

Hold List Display (Steam Turbine Applications)

Refer to Chapter 4 and Appendix B for more

information on the Hold List.

The Hold List is required for the HMI to support Mark V large and medium steam turbine controls on systems that have Automatic Turbine Startup (ATS). Turbine operating conditions may cause a hold, which prevents ATS from setting the speed or load target to a higher value.

The CIMPLICITY Alarm Viewer displays the Hold List on the HMI, to view and override the current hold points. Refer to Alarm Displays in this chapter.

(29)

Chapter 3 Display-Only Programs

Introduction

The HMI provides an online database for collecting and storing data from multiple controllers. Refer to the controller documentation for a description of this.

The HMI’s display-only programs allow you to view turbine control data as needed to monitor the system. You cannot, however, send control commands from these. This chapter describes display-only programs. It is presented as follows:

Dynamic Rung Display ...3-2 File Structure ...3-2 Dynamic Rung Display Windows ...3-3 Starting the Dynamic Rung Display...3-6 Selecting a Sequencing Display Screen...3-7 Using the Find All Function...3-7 Viewing Tabular Data ...3-8 Trip History ...3-9 Trip History File...3-9 Starting Trip History ...3-11 Trip History Dialog Box...3-11 Data History Results Window...3-12 Trip History on the Mark VI ...3-13 Trip Log Viewer ...3-14 Trip Log File ...3-14 Trip Log Viewer Dialog Box ...3-14 Viewing Results ...3-15 Starting the Trip Log Viewer ...3-15

Chapter 4 describes control (command) programs.

(30)

Dynamic Rung Display

Mark VI uses the toolbox for

this function. The Dynamic Rung Display program is used for viewing the control programming ofa Mark V controller. It displays the control rungs and blocks in a control sequence segment for a given unit. The program features the following:

• Animation to show the current state of the control

• Rung Ladder Display (RLD) rungs displayed with green representing continuity in contacts and the energized state in a coil

• Primitive and Big Block rungs sometimes displayed with their associated picture files showing either signal names or actual point values

• A Demand Display (see Chapter 4) with all of the signal names and values from a rung

• A Find utility to display the locations and usage of all occurrences of a signal in the unit’s Control Sequence Program (CSP).

The following rules apply to the Dynamic Rung Display:

• TCI must be running

• More than one control segment from a given unit can be open at a time

• Can display only segments from a single unit at any time

• Cannot be used to alter the unit’s CSP

File Structure

Table 3-1. Dynamic Rung Display File Description

File Name Description

MSTR_SEQ.CFG Lists the sequencing source files (*.SRC) used in the

control

*.SRC The source files for the individual control sequence

segments

\PROM\BIGBLOCK.DEF The block definition file for the unit

\PROM\PRIMITIVE.DEF The primitive definition file for the unit

\PROM\*.PIC The picture files for the big blocks and primitives

\PROM\*.SPC Sequencing BBL source files

The files are used by the Dynamic Rung Display to coordinate and accurately display the unit control data. These files are also used for unit control configuration and cannot be altered by the Dynamic Rung Display. It is imperative that the

configuration and sequencing files in the unit control and in the operator interface match. The Dynamic Rung Display does not independently verify that the operator interface files match the unit control files. If these files do not match, the Dynamic Rung Display may display data that does not reflect the state of the unit control.

(31)

The Dynamic Rung Display can save picture file displays in a text format for future reference. These text files may be opened by any text editor or word processor. It also creates temporary Demand Display files (*.DM2) in the system temporary directory when the Demand Display is used to show the points and values from a given rung. These files are automatically deleted when the Demand Display closes.

Dynamic Rung Display Windows

The Dynamic Rung Display is a multiple document interface that allows you to open windows with different segments or the same segment. The user may also have picture file windows and sub rung windows open. The windows are sized to display a full view of a rung. However, the window may be resized and repositioned. There are three major types of windows: rung, picture, and main frame, described below.

Rung Windows

Rung windows (see Figure 3-1) are used to display the animation of the control sequencing and navigate through the control sequencing segments. They can display data from main sequencing rungs or sub rungs that are predefined into Big Blocks.

Title bar displays unit name and segment name

Header, which displays the following data:

• Unit, site, program, and

segment name

• Rung number

• Timetag

The Header can scroll off the screen or be hidden by other windows. However, it is good practice to keep it visible because it contains valuable process information.

(32)

Dynamic Rung Display windows can contain the following types of data:

• RLD rung

• Primitive rungs

• Big blocks

• Comment rungs

Header data is located in the upper left of the window.

The type of information in the header timetag depends on the type of display:

• In both the RLD and primitive rung displays, the timetag provides the oldest piece of data being displayed in the RLD portions of the rung. If it has not received data from the unit, the timetag display is No Valid Data. If the oldest piece of data in the rung has not been updated for at least five seconds, the timetag is highlighted. Rung animation occurs once per second (see Table 3-2).

• In both the big block and comment rung displays, the timetag indicates the operator interface time when the rung was displayed. It does not update.

Note RLD Rung displays update automatically, and thus are animated in the rung

window. Parameter information passed in Primitive Block and Big Block rungs is not animated in the rung window, although you can update the display manually. Comment Rungs do not update.

Table 3-2. Animation Rules for Both RLD and Primitive Rungs Rung

Component Animation Rule Normally

Open Contacts

• A green rectangle between the contacts shows continuity.

• No rectangle between the contacts shows an open circuit.

• A ">" symbol between the contacts means forced signals.

• A rectangle outline around the ">" symbol highlights contacts that are forced to the open condition.

Normally Closed Contacts

• A slash through the contact indicates normally closed.

• A green rectangle between the contacts shows continuity.

• No rectangle between the contacts means an open circuit.

• A rectangle outline around the ">" symbol highlights contacts that are forced to the open condition.

The slash through the contacts is broken in the middle to highlight the ">" symbol.

Normal Coils • A coil circle filled with green is energized.

• A coil circle filled with the window background color is de-energized.

• A ">" symbol in the coil circle indicates forced signals.

Inverted Coils • A slash through the coil indicates that it is inverted.

• A coil circle filled with green is energized.

• A coil circle filled with the window background color is de-energized.

• A ">" symbol in the coil circle indicates forced signals. The slash through the contacts is broken in

(33)

Ø Ø Ø

Ø To update the Primitive Block Rung or Big Block Rung display to

show passed parameters

w Select either Picture File or Demand Display from the View menu. Ø

Ø Ø

Ø To update Big Block Rung display to show automatic parameters w Select Demand Display from the View menu.

Picture File Windows

Picture file windows (see Figure 3-2) are used to display the picture file and animation of the passed parameters for Primitive and Big Blocks.

Figure 3-2. Dynamic Rung Display’s Picture File Window

The type of information in the header timetag depends on the type of display:

• For a values display, the timetag provides the oldest piece of data being displayed as a passed parameter. This includes the coil output for primitive blocks. If it has not received data from the unit, the timetag display is No Valid

Data. If the oldest piece of data in the rung has not been updated for at least five

seconds, the timetag is highlighted.

• For a static display, the header timetag provides the operator interface time of when the rung was displayed.

Title bar displays:

• Unit name

• Segment name

• Rung number

• Picture file name

Header, which displays the following data:

• Unit, site, segment, and

picture file name

• Rung number

• Timetag (differs for Static

and Values displays)

The Header can scroll off the screen or be hidden by other windows. However, it is good practice to keep it visible because it contains valuable process information.

(34)

Note Picture files cannot be opened directly by selecting Open from the File menu. Ø

Ø Ø

Ø To open a picture file

1. Open a sequencing segment (see Selecting a Sequencing Display Screen). 2. Navigate to the rung that contains the applicable Primitive or Big Block. 3. Select Picture File from the View menu.

A static picture file window displays with the passed parameter point names represented as inputs and outputs to the block.

4. Select Values from the View menu to change to a values type display.

The parameter point names are replaced with their current values from the real-time database. The data is updated once per second.

The following rules also apply to the picture file displays:

• To toggle between the values display and the static display, select Values from the View menu.

• Big Block automatic parameters are not animated in the picture file window. You can only view their values by selecting Demand Display from the View menu.

• You cannot navigate to other rungs or picture file windows from a picture file window.

• A picture file window remains open until you close it by selecting Close from the File menu.

Main Frame Window

This is the outer window that contains the rung and picture file windows. If no control sequencing files or picture files are open, this window is empty.

Starting the Dynamic Rung Display

There are four ways to start the Dynamic Run Display:

• Double-click the program icon (if it is available on the desktop).

• On the Windows desktop, select Start, Turbine Control Maintenance Group,

Unit T#, then Dynamic Rung Display.

• Enter dynrung.exe in the Run dialog box in the Start menu.

• Enter dynrung.exe at the DOS command line, then press Enter.

To quickly bring the display to a desired configuration, you can launch the Dynamic Rung Display from the DOS command line with the following arguments:

You can use the command line arguments to customize the Dynamic Rung Display startup.

/UNIT: /FILE: /RUNG:

For example:

G:\EXEC\DYNRUNG.EXE /UNIT:T1: specifies the unit as T1

G:\EXEC\DYNRUNG.EXE /UNIT:T1 /FILE:SEQ_40.SRC: specifies the file name

G:\EXEC\DYNRUNG.EXE /UNIT:T1 /FILE:SEQ_40.SRC/RUNG:23 specifies the rung number

(35)

Selecting a Sequencing Display Screen

Sequencing files contain the Control Sequence for each control segment. The following rules apply when opening these files:

• Selecting File then Open can only open a regular sequencing segment from the files listed in the MSTR_SEQ.CFG.

• You must select a unit before you can open a sequencing file.

• You can open more than segment at a time, or have multiple views of the same segment.

• Use the Window menu to change between views.

• To navigate within a segment, use the Rung menu and toolbar buttons.

Using the Find All Function

The Dynamic Rung Display includes a Find All function, which allows you to find the occurrence of a particular signal anywhere within the control sequencing. This function will find the following:

• Signal names in RLD rungs

• Signal names as passed parameters

• Signal names as automatic parameters

• Primitive names

• Big Block names

Find All does not do the following:

• Locate signals and block names used in sub rungs

• Search Comment Rungs. The Find All Function is available only after a valid unit has been selected.

Ø Ø Ø

Ø To display results using the Find All function 1. Select Find All from the Edit menu.

2. In the dialog box, enter the desired signal or block name. 3. Select Find to display the results.

The Find All Results dialog box contains four columns, as follows:

• The first column displays the rung number where the rung was found.

• The second column shows the segment name.

• The third column shows the rung type.

(36)

Ø Ø Ø

Ø To open a segment from the Find All results with the desired rung

displayed

w On the rung number, double-click the left mouse button.

-Or-w Highlight the rung number and click the Goto button.

Note The Find All Results dialog box remains open until you select the Close

button or change units.

Viewing Tabular Data

Viewing tabular data can be useful when studying the behavior of a BBL with automatic parameters.

The Dynamic Run Display allows you to launch the Demand Display to view RLD elements, Big Block and Primitive passed parameters, and Big Block automatic parameters. The data is in tabular form.

The Demand Display is a separate program outside of the Dynamic Rung Display. Refer to Chapter 4 for more information.

Ø Ø Ø

Ø To view tabular data in a Demand Display w Select Demand Display from the View menu. This displays all of the points from the current rung.

(37)

Trip History

Mark VI uses the Control System Toolbox for this function.

The Trip History program provides a chronological record (log) of relevant data gathered by the Mark V or V LM unit control. The data is organized according to post-trip, pre-trip, and alarm categories. The program is used to help evaluate turbine trip events.

You can use this program to retrieve data from the unit control and view it on the operator interface (see Trip History Dialog Box below).

Control Signal Database Points (CSDBs) can be defined for collection. These definitions (64 max.) are made in a single file (HIST_B.SRC). All data in the display is chronologically indexed according to Mark V controller time and a separate controller counter (HIS_AGE).

Trip History File

Trip History stores the results of the data retrieval in a read-only temporary text file. This file is displayed using Microsoft Notepad (see Data History Results Window). The Trip History file contains the points for collection and retrieval by the Trip History program. This file for the unit is HIST_B.SRC, located in the unit

configuration directory. Information logged in the alarm section of the display is not user-definable. You can use any text editor to modify the file.

SOEs are sequence of events. For pre-trip and post-trip screens, timetag (TIME) definitions are listed for the displayed Control Data Point information. These designations provide a

chronological index that ties the exhibited signal information to the unit control time. This register can provide valuable information for determining the SOEs that lead to a turbine trip.

If the controller time is reset during an event, this index is lost. To prevent this, the Trip Log Display includes a second counter (HIS_AGE) that is internal to the unit control, but runs independently of the controller clock. This counter updates once-per-second. It advances until a maximum value is reached, at which point the counter returns to zero and restarts.

Figure 3-3 provides a sample HIST_B.SRC file in which the counter increments only when the turbine is in a run condition. HIS_AGE must always be the first point in the

HIST_B.SRC file.

(38)

;---; HIST_B.SRC

; HIS_AGE MUST BE THE FIRST POINT! ; ; Signal Name ; ---HIS_AGE DWATT TNH FSR L52GX L14HR L14HM L14HA L14HS L94X L4 L3 L2TV L28FDX TTXD_1 TTXD_2 TTXD_3 TTXD_4 TTXD_5 TTXD_6 TTXD_7 TTXD_8 TTXD_9 TTXD_10 TTXD_11 TTXD_12 TTXD_13 TTXD_14 TTXD_15 TTXD_17 TTXD_18 FQG FQL1 FSG CTIM CSGV CPD TTXSPL TTXSP1 TTXSP2 TTXSP3 L4CT

(39)

Starting Trip History

You can start the Trip History program any of four ways:

Unit T#, then Trip History.

• Enter tripdlog.exe in the Start menu’s Run dialog box.

You can use the command line arguments to customize the Trip History startup.

• Enter tripdlog.exe at the DOS command line, then press Enter.

When the program starts, the Trip History dialog box displays (described below). From there, you select the unit and type of data to display.

To quickly bring the display to a desired configuration, you can launch the Trip History Program from the DOS command line with the /UNIT argument, as follows:

G:\EXEC\TRIPDLOG.EXE /UNIT:T1 specifies the unit as T1

Trip History Dialog Box

The Trip History dialog box controls the collection of Trip History data and Historical log data from the unit control.

Ø Ø Ø

Ø To view the Trip History log

You can retrieve only one type

of data at a time. 1. From the Trip History dialog box (see Figure 3-4), select a valid unit from theSelect Unit list. 2. Choose the type of historical data to be collected from the Select Log options. 3. Click the Collect button to collect the data or the Cancel button to stop it.

When the data collection completes successfully, the results display in a separate window (see Data History Results Window). A message box displays if the data retrieval fails or is stopped by a user command.

Click to start data collection. Click to close the Trip History dialog box. Select the Unit from the list. Select the type of data to be collected. Trip History is saved when the turbine trips. For Mark V LM unit controls, the data is saved in the control even after the control is reset. Saved Data is saved into the control memory when you collect New Data. It remains in memory until it is overwritten by New Data or until the control is reset.

New Data is saved to the control memory when the user collects New Data. The data reflects the most recent control data. The data remains

(40)

Note Trip History data is lost in Mark V controllers if the unit control is reset. The

trip history data is preserved in the controller memory over a unit control reset or reboot in Mark V LM units.

Data History Results Window

When the data retrieval completes successfully, the program opens Microsoft Notepad and displays the results in a separate viewer window (see Figure 3-5). The data is designed to be displayed in a fixed pitch font (all characters have the same width) and word wrapping disabled. The results shown are stored in a read-only temporary file.

Ø Ø Ø

Ø To save the Trip History data displayed by Notepad 1. From the Notepad File menu, select Save As.

2. Select the directory and name for the .txt file. 3. Click the Save button.

The results saved are in the following format:

• Post Trip List: three 1 second post trip records. These three records are filled with data only when there has been an actual trip. Otherwise, they are blank.

• 10 Second List: ten 1-second records

• 1-Minute List: five 10-second records

• 10-Minute List: nine 1-minute records

• 1-Hour List: five 10-minute records

• 4-Hour List: four 1-hour records

• Last 60 Process Alarms Enumerated state variable data

is displayed as numbers, not as text strings.

Each record consists of the following fields:

• Timetag

(41)

Figure 3-5. Trip History Results Displayed in Notepad

Trip History on the Mark VI

Refer to Data Historian document GEI-100278 and Trend Recorder document GEH-6408 for more information.

The Mark VI controller uses the Data Historian, a toolbox program to collect and view trip history data. The Historian trip log is a combination of historical analog and discrete data collected at a rate of one second, and multiple capture buffers collected at high speed. Ethernet Global Data (EGD) is available for 24 hours. The controller capture buffers hold 60 seconds of data.

This trip history data is viewed using the Trend Recorder, another toolbox program. With this, multiple analog signals are trended on a full-page screen, which also contains information on the configured discrete variables. High-speed discrete data including all events, alarms, and SOEs can also be viewed in a list format showing the logic state and time of the event.

Header, identifies the unit and location. Up to 64 points can be viewed. HIS_AGE is always reserved as the first point.

Post trip list Three 1-sec records

10-sec. list Ten 1-sec records

1-min. list Five 10-sec records

(42)

Trip Log Viewer

Refer to GEH-6126 Volume 2 for information on the Trip Log Collection utility.

A Mark V controller loses the trip history data stored in its memory if the unit control is reset or rebooted. A Mark V LM controller keeps the data for the last trip if a reset or reboot occurs. However, the Turbine Control Interface (TCI) includes a Trip Log Collection utility that automatically collects and stores the data. (Both the utility and HMI must be running during the trip.)

You can access this data, which is displayed in a separate viewer window, using the HMI’s Trip Log Viewer.

Trip Log File

The Viewer reads the previously saved trip text files stored on the disk. It determines the trip times associated with each file from the name of the file, which is encoded with the trip date and time information. Viewer opens Microsoft Notepad and displays the valid trip times for the selection.

Ø Ø Ø

Ø To save the trip times

1. From Notepad, select Save As from the File menu.

The Trip Log Collection utility stores the last 1 – 10 trips . After that, it overwrites the oldest trip file with any new trip data.

2. Type in a file name and click Save.

The files are stored in the C:\HMIDATA directory. The automatic collection program manages the file names in the format YYYYMMDD_UU_TRx.CSV, as follows:

YYYYMMDD_HHMMSS_UU_TRx.CSV

TRP indicates that the file contains trip information; TRQ indicates a normal shutdown or an aborted startup Unit name

Data and time of trip (Y = year; M = minute, D = day, H = hour, S = second

File extension (to allow Microsoft Excel viewing and analysis)

Figure 3-6. Trip History File Name Convention

Trip Log Viewer Dialog Box

The Trip Log Viewer dialog box controls the selection of Trip History data stored on the disk.

Ø Ø Ø

Ø To view the trip log data (refer to Figure 3-7)

1. From the Trip Log Viewer dialog box, select a valid unit from the Select Unit

list box.

2. From the Select a Previous Trip Log, select a log to display by highlighting it. 3. Click the Go To button to display the selected log (file) with data from that trip. 4. Select the Close button to exit.

(43)

Figure 3-7. Mark V and Mark V LM Trip Log Viewer Dialog Box

Viewing Results

Refer to the previous Data History Results Window for a detailed description of the data format and viewer program.

Starting the Trip Log Viewer

There are four ways to start the Trip Log Viewer:

Unit T#, then Trip Log Viewer.

• Enter tripvwr.exe in the Start menu’s Run dialog box.

You can use the command line arguments to customize the Trip Log Viewer startup.

• Enter tripvwr.exe at the DOS command line, then press Enter.

When the program starts, the Trip History dialog box displays (described previousy in this chapter). From there, you select the unit and type of data to display.

Select to view log Identifies location Select to exit dialog box Select the Unit from the list

Listed by Trip Date and Time stamp.

Logs of past trip events. Select to display The number of trips is set by the Trip Log Collection utility. Default is 10. The most recent is listed at the top. Additional trips overwrite the oldest log.

(44)

(45)

Chapter 4 Control (Command)

Programs

Introduction

The HMI’s control (command) programs allow you to control system operation by sending commands to the controller.

This chapter describes the HMI control programs. It is presented as follows:

Demand Display ...4-2 Starting Demand Display ...4-2 Working with Files...4-3 Demand Display Windows...4-4 Figure 4-1. Example of Menu Window...4-4 Data Area Description... 4-6 Command Target Types ... 4-6 Using Demand Display ...4-7 Displaying, Creating, and Modifying Screens ... 4-7 Working with Command Targets... 4-11 Other Options... 4-13 Command Line Configuration...4-13 Commands and Arguments ... 4-13 Using Multiple Arguments... 4-14 Alarm Logger Control ...4-15 Starting the Alarm Logger Control ... 4-15 Hold List (Steam Applications)...4-16 Hold List Points...4-16 Hold List Programs ...4-16 Hold List Rules...4-16

Chapter 3 describes display-only programs.

(46)

Demand Display

This program is used on Mark IV, V, and V LM controllers. For Mark VI, refer to the Con-trol System Toolbox documen-tation,

Demand Display is a Microsoft® Windows®-based program that offers flexible monitoring and control of a variety of datapoints and multiple units. It provides the following turbine control features:

• Ability to monitor several datapoints at a time

• Ability to issue simple commands to the unit(s)

• Alterable displays that conform to the user needs

• Easy conformance to the displays required for testing and special procedures

• Control of special unit functions while monitoring associated data

• Ability to accommodate different types of units in one Demand Display file (see

Working with Files in this chapter).

Only qualified personnel knowledgeable about turbine con-trol and protection should create and execute commands. The commands can affect the control state and action of the unit control

.

The Demand Display program can be started and customized through either Win-dows or a DOS-based line command (see Starting Demand Display). This chapter includes instructions using Demand Display with Mark IV, V, and V LM controllers. For Mark VI controllers, use the toolbox.

Starting Demand Display

There are four ways to start Demand Display:

Unit T#, then Demand Display.

• At the DOS command prompt, type DEMAND then press Enter.

• On the Windows desktop, select Start and Run, then enter DEMAND.EXE in the dialog box.

DEMAND01.DM2 is located in the F:\RUNTIME directory

Demand Display automatically opens a generic default file DEMAND01.DM2, which can use data from multiple units. The program provides two types of working win-dows:

For description and operation of these program windows, see the Demand Display Windows section in this chapter.

• A Menu window contains a list (menu) of all of the screens available in the se-lected Demand Display file.

• Data windows contain data associated with a particular unit. These screens are selected from the Menu window.

(47)

Ø Ø Ø

Ø To load an existing .DM2 file from the Demand Display

Or click .

1. From the File menu, select Open.

2. Select the file from the directory that displays.

If no existing file is specified when executing Demand Display the default file

DEMAND01.DM2 (located in the F:\RUNTIME directory) loads.

Ø Ø Ø

Ø To create a new .DM2 file from the Demand Display w From the File menu, select New.

A blank Demand Display Menu screen displays with the single menu item De-mand Display. This is a template that must be renamed after modification.

Saving a new Demand Display file without renaming it over-writes the existing file data with the new file data.

Saving the Demand Display template screen without a new screen name causes the template to no longer be a blank.

Note Exiting either the screen or file without saving loses changes to the file.

Working with Files

Demand Display uses the following files:

File name Location (Directory) Description

DEMAND.EXE G:\EXEC (executable directory) Opens the Demand Display program. The program opens files with

.DM2 extensions (for example, DEMAND01.DM2).

To ensure that the Demand Display program functions correctly, do not modify the DEMAND.EXE file

.

xxxxx.DM2 RUNTIME directory in the F:\ drive (typically). The Demand Display program saves new files in the directory in which the program was executed, unless a different directory is selected.

Demand Display files, which are in binary format, contain defini-tions for all of the Data screens listed on the Demand Display Menu for that file. One file generally saves several Demand Display screens. One unit may use several of these files. Open, modify, and save these files using the Demand Display program (do not edit the files directly).

unitname.DD (unitname varies as needed.)

Files that make up the Data Dictionary for a unit are stored in its unit-specific directory and should always be kept there.

Data Dictionary files contain the point list available for use in the Data screens. Demand Display obtains points values directly from the Data Dictionary. (SYSTEM.DD is the master data dictionary file, which contains pointers to all *.DD files used by the Demand Dis-plays).

(48)

Demand Display Windows

As defined previously, there are two types of Demand Display windows:

To display a screen listed on the menu, select that item using the mouse or Enter key.

• The Menu window lists all screens available in the selected *.DM2 file (see Fig-ure 4-1). It is the starting point for working with Data screens. .

• Data windows are screens selected from the Menu window. The name and defi-nition of Data screen is associated with a particular unit. (For example, Unit 1 would differ from Unit 2 in the names and definitions of the Data displays.) There are two types of Data screens: Point List and Data Dictionary (see Fig-ures 4-2 and 4-3).

Figure 4-1. Example of Menu Window

Figure 4-2. Example of Point List Type of Data Screen, User-Defined The titlebar displays the filename currently in the Demand Display.

Note Selecting the Help button opens the Help window. Selecting the Context Sensitive Help button changes the cursor to an arrow with a question mark. You can then select an item with this cursor to open the item’s Help information.

Menu selections include both standard Windows and program-specific commands.

The toolbar provides quick access to menu commands. Holding the cursor over the button displays the button function (see Note). Header, which contains process identification d t )

Data Area, which contains menu of available data screens. New screens can be added.

The Point List data screen is created and edited from points and commands entered by the user from the Demand Display program. It is the most common type of display.

Header Legend

Data Area

Command Target Field You can define additional

point names and command targets or remove existing ones from Point List data screens.