Professional Documents
Culture Documents
Speedtronic HMI I
Speedtronic HMI I
Speedtronic HMI I
GEH-6126A Volume I (1 of 2)
(Supersedes GEH-6126)
GE Industrial Systems
Document: Issued:
2002 General Electric Company, USA. All rights reserved. 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 purchasers 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. PI-ProcessBook is a registered trademark of OSI Software Inc. SPEEDTRONIC is a trademark of General Electric Company, USA.
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.
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.
g
Your Name
To:
Reader Comments
General Electric Company
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)
General Rating Contents Organization Technical Accuracy Clarity Completeness Drawings / Figures Tables Referencing Readability Excellent Good Fair Poor Additional Comments _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________ _____________________________________________________________
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.) ________________________________________________
......................................................................... Fold here and close with staple or tape .......................................................................................... ____________________________ ____________________________ ____________________________
Place stamp here.
GE Industrial Systems
Documentation Design, Rm. 291 1501 Roanoke Blvd. Salem, VA 24153-6492 USA
Contents
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 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
Contents i
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
ii Contents
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
Contents iii
Notes
iv Contents
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 userfriendly 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
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 GEs Windowsbased 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) HMI access security
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 products 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.
CIMPLICITY
Point Database Alarm Queue
TCIMB
TCI
Point Data
Alarm Manager
s m ar l A
Alarms
int Po
Point Manager
Point Data
Mark V RP
Data Dictionary
Devcom
(EGD...)
Devices
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.
Figure 1-2. Sample HMI Display Showing Steam Turbine and Generator Data
The graphic system performs key HMI functions and provides the operator with realtime 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
CimView is the HMI run-time portion, displaying the process information in graphical formats (as shown in Figure 1-2). In CimView, the operator can view the system screens, and screens from other applications, using OLE automation, run scripts, and get descriptions of object actions. Screens have a 1-second refresh rate, and a typical graphical display takes one second to repaint. HMI opens in CimView.
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.
Data
Data
HMI Server # 1
HMI Server # 2
HMI Viewer
Historian
TR
Mark IV Control System Freeway (CSF) Mark V Stagelink Mark VI Turbine Control I/O
Mark IV Turbine Control I/O
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. OSIs 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 highresolution 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 customers needs and purchased options. The HMI workstation is typically sent to the customer with the HMI program already installed.
Related Documentation
The following documents apply to the HMI and SPEEDTRONIC turbine controllers and may assist in understanding HMI operation: GEH-#### is the document identification number. HMI-related documents: GEH-6126A Volume 2, HMI for SPEEDTRONIC Turbine Control, Maintenance Guide GEI-100165, GEDS Standard Message Format GEI-100279, SDB Exchange Users Guide for Control System Solutions GEI-100500, System Database Utilities for Control System Solutions GEI-100513, HMI Time Synchronization for SPEEDTRONIC Turbine Control GEI-100514, Power Block Control for SPEEDTRONIC Turbine Control, Product Description GEI-100515, Microsoft NetMeeting 3.0 for SPEEDTRONIC Turbine Control, Installation and Setup GEI-100516, GE Industrial System Standard Messages (GSM) GEI-100535, Modbus Communication Interface for SPEEDTRONIC Mark VI Turbine Controllers GEH-6422, Turbine Historian System Guide GFK-1180, CIMPLICITY Base System User's Manual GFK-1181, CIMPLICITY HMI Plant Edition, Base System Device Communications Manual GFK-1396, CIMPLICITY HMI CimEdit Operation Manual GFK-1675, CIMPLICITY HMI, OPC Server Operation Manual Mark VI controller and related documents: GEH-6403, Control System Toolbox for Configuring a Mark VI Turbine Controller GEH-6408, Control System Toolbox for Configuring the Trend Recorder GEH-6421, SPEEDTRONIC Mark VI System Guide, Volumes I and II GEJ-7485, SPEEDTRONIC Mark VI Turbine Control, Software Maintenance GEI-100278, Data Historian Mark V and V LM controller and related documents: GEH-5979, SPEEDTRONIC Mark V Turbine Control Users Manual GEH-5980, SPEEDTRONIC Mark V Turbine Control Maintenance Manual GEH-6195, SPEEDTRONIC Mark V Turbine Control Application Manual Overview GEH-6354, Mark V LM SPEEDTRONIC Turbine Control <I+> Users Manual
Text Conventions
The following symbols, formatting, and presentation conventions are used in this document to assist the user.
Convention Meaning
Numbered list Alphabetized list Bulleted () list w Boxed () list Arial Bold
A procedure follows. Procedural steps to be followed in order (for example, 1, 2, 3). Procedural substeps (of numbered steps) to be followed in order (for example, a, b, c). Related items or procedures, but order does not matter. A procedure with only one step. A checklist. 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. Represents examples of DOS screen text or display.
Monospace
Introduction
A facility receives the HMI pre-loaded with all the programs and customized software required for the customers 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
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 displays the 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.
Click buttons and other animated objects to open additional screens or objects.
Select an alarm listed, then click the button for the desired for action
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).
To apply a button to an alarm, highlight the alarm from the list, then click the button
Alarms are listed in the display. Figure 2-2. Example of Alarm Display Screen
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: - Configuration update - Status log - Project properties Right pane - Project wizard views
Help
Screens Points
Runtime Alarms
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.
Trip History
Refer to Chapter 3 for more information. The Trip History program provides a chronological record (log) of relevant data gathered 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.
Demand Display
Refer to Chapter 4 for more information. This display allows you to view values of a selected list of points. To load an existing Demand Display file 1. On the Windows desktop, select Start, Turbine Control Maintenance Group, 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.
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. Chapter 4 describes control (command) programs. The HMIs 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:
Section Page
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
File Structure
Table 3-1. Dynamic Rung Display File Description File Name MSTR_SEQ.CFG *.SRC \PROM\BIGBLOCK.DEF \PROM\PRIMITIVE.DEF \PROM\*.PIC \PROM\*.SPC Description Lists the sequencing source files (*.SRC) used in the control The source files for the individual control sequence segments The block definition file for the unit The primitive definition file for the unit The picture files for the big blocks and primitives 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.
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.
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.
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 Normally Open Contacts Animation Rule Normally Closed 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. 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. 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. 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 the middle to highlight the ">" symbol.
Normal Coils
Inverted Coils
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.
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.
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.
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 realtime 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.
rung number
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. The fourth column shows how the signal is used in the rung.
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. -Orw 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.
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).
;-----------------------------------------; 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
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.
Header, identifies the unit and location. Up to 64 points can be viewed. HIS_AGE is always reserved as the first point.
Select to view log Identifies location Select to exit dialog box Select the Unit from the list
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.
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.
Notes
Introduction
Chapter 3 describes displayonly programs. The HMIs 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:
Section Page
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
Demand Display
This program is used on Mark IV, V, and V LM controllers. For Mark VI, refer to the Control System Toolbox documentation, 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 control 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 Windows 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.
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 windows: A Menu window contains a list (menu) of all of the screens available in the selected Demand Display file. Data windows contain data associated with a particular unit. These screens are selected from the Menu window.
For description and operation of these program windows, see the Demand Display Windows section in this chapter.
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 Or click . w From the File menu, select New. A blank Demand Display Menu screen displays with the single menu item Demand Display. This is a template that must be renamed after modification.
Saving a new Demand Display file without renaming it overwrites 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.
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. Files that make up the Data Dictionary for a unit are stored in its unit-specific directory and should always be kept there.
Demand Display files, which are in binary format, contain definitions 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).
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 Displays).
The titlebar displays the filename currently in the Demand Display. 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.
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 items Help information.
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. You can define additional point names and command targets or remove existing ones from Point List data screens. Header Legend
Data Area
Command Target Field Figure 4-2. Example of Point List Type of Data Screen, User-Defined 4-4 Chapter 4 Control (Command) Programs HMI for SPEEDTRONIC Turbine Control GEH-6126A Volume I
The Data Dictionary data screen is built automatically from point information stored in the Data Dictionary. It configures the screens from options that select the points and commands to display. The Value field updates once each second. Header This data screen is used for examining specific point types Legend and command options.
Adding and deleting point names and command pushbuttons from a Data Dictionary data screen is temporary and cannot be saved.
Data Area
Figure 4-3. Example of Data Dictionary Type of Data Screen Using Logics
Both Demand Display windows are made up of three main regions (refer to Figures 4-1 through 4-3): GE recommends that you keep the screen header visible at all times. The screen Header is non-scrolling process identification data. It contains the: Unit name Site name Program name Display screen name Timetag (pc time) for the oldest piece of data in the Data Area. Although the header cannot scroll off the screen, you can toggle it on or off by selecting Header from the View menu. The Timetag displays the oldest of the displayed point name timetags in the controller. If the Data Area is empty (contains no valid points), or the Data Area contains valid points but no data has been received from the unit, then the timetag is No Valid Data. A highlighted timetag indicates that the oldest piece of data in the Data Area has not been updated for five seconds. GE recommends that you keep the column headers visible at all times. The Legend displays the non-scrolling column headers for the Data Area. Although the header cannot scroll off the screen, you can toggle it on or off by selecting Header from the View menu. The Data Area is below the Header and Legend. In the Menu screen, the Data Area consists of a list of the Data screens available for viewing. In a Data screen, the Data Area consists of an unlimited list of point names, their values, and units. This information is in a tabular format. (See Data Area Description below for more details.) Any Command Targets defined display on the right side of the window. (See Command Target Types below for more details.)
Analog Setpoint type changes the setpoint value of the specified control. It does not use feedback logic. When selected, a Setpoint Dialog box (see Figure 4-4) opens, requesting the new value for the control signal. No response cancels the command through default. These targets are gray and their text turns yellow if the feedback logic is supplied and met.
Enter new value Uses the current display engineering units Cancels command and closes box
To create (add) a new Data screen 1. From the Menu window, place the cursor at the point in the list where you want to insert the new screen title. 2. Select Insert Line from the Edit menu. This adds a new, blank data screen and its title as Untitled:#, where the # is the number of the new screen. 3. Give the screen a new name as described in the modify instructions below. To modify a Data screen (title, type, options) 1. From the Menu window, place the cursor at line with the screen name. 2. Select Modify Line from the Edit menu. Or, select Definition from the Displaymenu. The Display Definition dialog box opens (see Figure 4-5).
Data screen title (see guidelines below). Allows you to change the Data screen type.
Select the point types to display in a Data Dictionary type Data screen.
Display Title guidelines: Screen title can be up to 25 characters long. Names should not be duplicated, empty, or all blanks The use of ellipsis (.....) placed before the title of a Data Dictionary type Data screen is recommended to differentiate it from a Point List type Data screen.
3. In the Display Title text box, type a new name, if desired. Figures 4-2 and 4-3 provide samples of these types of Data screens. 4. Use the Display Type options to change between a Point List type or a Data Dictionary type, as desired. 5. Select OK to save the changes. 6. Save the Data screen, as described below. To save a Data screen 7. Select Save or Save As from the Display menu.
Save saves the screen changes to the same screen title on the Menu window. Save As saves the screen changes to a new screen title on the Menu window.
It also opens the Display Definition dialog box. 8. If the Display Definition dialog box opens, type a new name in the Display Title text box (see Figure 4-5). 9. Select OK or Save As from the Display menu to save changes. Keep in mind the following:
Save As does not change the old Display Title to a new one. It inserts the title
of the new Data screen at the bottom of the Menu list. If you do not enter a new Display Title, another Demand Display screen with the same name is added to the bottom of the Demand Display Menu. You should rename the edited Demand Display screens if you keep the original.
If you exit the Demand Display program before saving changes to the screens, the program asks if you want to save changes before exiting. Select Yes to save the changes in the *.DM2 file and No to exit without saving. To copy a Data screen from one unit to another At locations with duplicate or similar units, it may be useful to copy a Demand Display screen from one unit to another. 1. From the Menu window, open the desired screen. 2. Select Unit from the Edit menu. 3. Select the new unit. 4. Select Save from the Display menu. 5. To make this change permanent to the Demand Display file (*.DM2), select Save or Save As from the File menu.
Type new Point Name in text box. Click to save Point Name entries and exit box. Click to cancel Point Name entries and exit dialog box. Displays only when you can add or modify a Command Target associated with the line. Figure 4-6. Modify Line Dialog Box
To delete a point name or line 1. On the Data screen, place the cursor on the line to modify. 2. Select Delete Line from the Edit menu. If the line corresponds to the first line of a Command Target, the target deletes. 3. Save both the Demand Display screen and Demand Display file to make the changes permanent.
Target Text should indicate the Command Targets action. Text appears black, but turns yellow if the associated feedback logic is supplied and the sense met. Allows two lines of up to eight characters per line. Text is automatically centered on the target (button). Unit command Point Name is the control signal pointname that receives the targets value. Only command pointnames are allowed. They can be pushbutton, logics, or analog setpoints. Target Type defines which Command Target to use. For definitions, refer to Command Target Types. Value holds the value the Command target sends to the unit. Use the following guidelines (based on pointnames): A Targets value is the number of scans to hold the target (pushbutton) true. The minimum value is four scans. Logic States require a value of 1 or 0. Analog setpoints require a value in the engineering units specified for the command signal point.
Value type determines how the Command Target sends the value to the unit: Set (=) sends the value from the value type to the unit. It is required for Pushbuttons and Logic States and optional for Analog Setpoints. Increment (+) adds the value in the value field to the current value of an Analog Setpoint and sends it to the unit. Decrement (-) subtracts the value in the value field from the current value of an Analog Setpoint and sends it to the unit. Feedback Signal contains the feedback signals definition. Immediate Action and Arm/Execute types can use feedback signals. Analog Setpoint target types cannot. Pointname is for the control signal point name of the feedback signal, which can only be logic point types. Sense can invert the sense of the feedback signal.
To modify a Command Target 1. Place the cursor on the point name in the line that corresponds to the to the top text line of the desired Command Target. 2. Select Modify Line from the Edit menu. The point name dialog box displays (see Figure 4-6). 3. Select the Define Command button. The Command Definition dialog box displays. 4. Modify the definition as defined above using the procedure to add a Command Target.
Other Options
There are several other options available in the Demand Display program: Selecting Set Font from the Edit menu displays the Windows Font dialog box. You can then select the font and color of the Demand Display screen. The selection applies to all Demand Display screens, except for the Command Targets, whose colors are predefined. Selecting Select Unit from the Edit menu allows you to select a unit. In multiple unit sites, any unit can be monitored from one Demand Display screen. Select Unit displays the Unit Selection dialog box. The currently selected unit is highlighted. The available units display in alphabetical order. Select the desired unit. This option is not available in single unit sites. Selecting Menu from the View menu toggles between the menu and the most recently viewed Data screen. Toggling to the Menu screen from a Data screen loses any changes if the Data screen is not saved. The Demand Display program asks whether or not to save the Demand Display screen. Selecting Yes saves the screen, No toggles to the Menu window without saving. Selecting Menu from the Demand Display Menu screen displays the most recently viewed screen.
The unit name must be a valid unit. Selecting an invalid unit or no unit displays the Unit Selection dialog box. Single unit sites ignore this argument and default to the single unit. The /FILE: argument executes the Demand Display program and loads a requested Demand Display file. For example:
F:\RUNTIME>DEMAND /FILE:OPERATOR.DM2
or
F:\RUNTIME>DEMAND /FILE:F:\RUNTIME\OPERATOR.DM2
This argument requires permission to read the file and/or directory. Entering an invalid path or filename displays an error message and a blank, untitled Demand Display file. When entering no filename, the program attempts to open the default file F:\RUNTIME\DEMAND01.DM2. If it cannot open the file, the program displays an error message and a blank file.
The /DISPLAY: argument displays the screen in a particular file. For example:
F:\RUNTIME>DEMAND /FILE:OPERATOR.DM2 /DISPLAY:LUBE OIL
If the screen name is invalid, the program displays the menu for the file requested. If the file is invalid, a blank, untitled file displays. The /TYPE: argument displays the data screen with points specified at the command line. For example:
F:\RUNTIME>DEMAND /TYPE:(L1,F4)
The program displays a blank Demand Display file if the point types are invalid. If a filename is entered, it ignores the point types.
or
F:\RUNTIME> DEMAND/UNIT:T2 /TYPE:(F4)
Exits dialog box without saving changes. Saves selections and exits.
Click on drop-down box arrow to select unit (displayed in alphanumeric order). There are four functions (categories of information that can be printed. Click on box to select. (Blank is unselected; a check is selected.) You can select each function on a unit basis by selecting the Unit and Function, then OK button. Figure 4-8. Alarm Logger Control Dialog Box
Cancels changes and exits. Applies current units settings to all units. Immediately deletes all pending alarm print jobs for all units from the Alarm Printer (does not require OK to be selected).
To quickly display the desired configuration, start the Alarm Logger Control from the DOS command line with following argument:
G:\EXEC\LOGGER.EXE /UNIT:T1
A picked up hold point may be overridden by an operator using the Lock command button. An overridden point displays Locked as the first part of their long name text. An overridden point loses its override when it drops out (1 -> 0). The Hold List displays the time of the last pickup or override, unit, acknowledge state, current state, override status, and the short and long name of each hold point in the list. The text Hold displays in the drop number field and the CSDB offset displays in the reference field. The reference field is typically not displayed. The Hold List program in <C>, not <D>, outputs a logic signal indicating that there are one or more active holds that have not been overridden. This point is named L68DW_ATS_HL. ATS and the turbine control use this signal to set speed, load, and valve position targets.
Notes
Introduction
The CIMPLICITY HMI product must be installed before these applications can be used. GFK-1180 provides a detailed description of the CIMPLICITY display features. The CIMPLICITY HMI collects data from plant sensors and devices, then transforms the data into dynamic text, alarm, and graphic displays. Operators can access real-time information when monitoring and making control decisions. The turbine control HMI supports many CIMPLICITY applications for operation. CIMPLICITY 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. CIMPLICITY supports OLE and ActiveX applications for automation displays. CIMB (CIMPLICITY Bridge) enables CIMPLICITY to collect data and alarms from a turbine unit with Mark V. (Mark VI used EGD) TCIMB provides the following software functions: MARKV_RP collects data from a turbine using TCI and forwards the information to the CIMPLICITY Point Manager. EXTMGR collects alarms and forwards them to the CIMPLICITY Alarm Manager. (See Chapter 6.) LOCKOUT sends a lockout command to a unit using TCI. (See Extended Alarm Commands below.) SILENCE sends a silence command to a unit using TCI. (See Extended Alarm Commands below.) This chapter identifies these functions, as follows:
Section Page
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
Mark V, V LM.
OLE is Object Linking and Embedding (see the Glossary for a more detailed definition).
For Mark V and V LM, a Manual Sync Object (an OLE object) is provided in CIMPLICITY HMI to allow the user to see a display representing this synchronization process (see Figure 5-1). The object contains all the fields that need to be updated at a fast rate. For Mark V and V LM, all data in the object is updated at 16 Hz. For Mark VI, this operation is at 10 Hz. The Manual Synchronizing Display must be run from a CIMPLICITY server for the desired controller. This is because the object uses the messaging services of TCI. The object consists of five parts, which you can set using tabs on the CIMPLICITY HMI Properties dialog box for that object. These tabs are described below.
Synchroscope -Configure using Scope tab Resets green dots at end of pointer (see Figure 5-2)
Breaker close times -Configure using Breaker tab Breaker Trip and Breaker Close buttons -Configure using Buttons tab (see Note below) Values that need updating quickly -- Configure using Values tab
Note When you push the Breaker Close or Breaker Trip button, a dialog box displays with two buttons for command confirmation: Command sends the breaker close or trip command when selected and released Done exits the dialog box and cancels the breaker close or trip command
Select unit from drop-down list. Signal used to determine current slip frequency. If greater than maximum slip frequency, pointer is positioned at bottom of scope. Maximum slip frequency. Locations marks on scope. Entered in degrees separated by spaces. (Optional.) Signal used to change pointer color. If signal is not defined, pointer is white. If true, pointer is green. If false, pointer is red.
(Optional.) Signal indicating state of Sync relay. Each time signal is true and pointer is updated, a green dot is drawn at end of pointer. Scopes R button (located top right; see Figure 5-1) is used to reset dots.
Configuring Permissives
To configure the Permissives part of the object, add or edit the list entries in the Permissives tab.
Logic signal used. Determines color of box displayed by variable. If variable value equals Sense value, box is green. If not equal, box is red with a dash next to it. Add entries to list. Delete currently selected entry. Edit currently selected entry.
String displayed next to box. Permissives display in object in the same order as in list box.
Move currently selected entry up one row in the list. Move currently selected entry down one row in list.
(Optional.) Signal to send Breaker Close pushbutton command to. If not filled in, button is not displayed. Set length of pushbutton command in duration box. (Optional.) Signal to send the Breaker Trip pushbutton command to. If not filled in, button is not displayed. Set length of pushbutton command in duration box.
Configuring Values
To configure the objects Values, enter data into the Value tab.
Values in display in the object in the same order as in the list box Sets number of digits for displaying the value. Uses number of decimal places and units string specified in the scale code. Signal used for the value. String that displays to the left of the value.
Add entries to end of list. Apply to the currently selected entry. Up moves currently selected entry up one row; Down moves it down one row.
Click down arrow to select area to change Background or Foreground (text) color Click to change color of selection.
Mark V, V LM
Plotted data displays within graph box, up to two data points versus time. Data (status points) collected at a sample rate of 8 times per second for an elapsed time of 1 to 120 seconds, as selected by user. Updates once per second. Plot is triggered by user-specified logic signal and its desired state to trigger.
Select unit from drop-down list Name of variable that determines beginning of test State of trigger to begin the plot Plot points for left and right axis Range for low and high plot (in raw counts) Select color for each plot line Selected plot points are plotted from the time the trigger first reaches the specified state until the end of the entered elapsed time. Figure 5-3. Inactive Triggered Plot Screen Showing Version Window
Configuring Users
A user is an individual person working with a CIMPLICITY HMI project. Each CIMPLICITY HMI user has the following attributes, which must be configured: Security A user may be assigned a Password. If a Password is configured and enabled, then a user cannot access CIMPLICITY HMI project functions without entering both the User ID and Password. Roles and Privileges A user is assigned a role. Each role in the CIMPLICITY HMI project has certain privileges assigned to it. The privileges define the functions the user can access. If a user lacks the privilege to access a secure function, an error message is displayed and access is denied. View of Resources A users view determines the accessible resource data. Alarms for resources outside a users view do not display on the users Alarm Viewer window. All procedures in this section were completed successfully. To configure Users for the CIMPLICITY HMI project 1. Open the project in the CIMPLICITY Workbench (refer to Chapter 6 for an overview). 2. In the Workbench left pane under the Security folder, select below.
Users, as shown
Select
3. Open the New User dialog box and add a new user called OPERATOR.
Type in the new name (User ID) then click OK.
4. Open the User Properties dialog box for the user OPERATOR and enter Operator as the User name.
Select tab.
The Resources properties let you define the resources for which the user can view alarms.
5. Select the Resources tab and add all resources T1 through T8.
Select tab.
Note Resources can be added or removed based on the Users rights. For example if you want to have a User name as User1 who is supposed to operate only Gas Turbine T1 (GT1), then add only T1 as the Resource for the User1.
6. Define the Role Properties for the user OPERATOR, as shown below.
Select options
Configuring Resources
All procedures in this section were completed successfully. To configure Resources for the CIMPLICITY HMI project 1. In the Workbench left pane under the Security folder, select shown in the figure below.
Resources, as
Select
2. Add a New Resource T1 and click OK, as shown in the figure below.
Type in the new name (Resource ID) then click OK.
3. Add the Resource Definition for T1, as shown in the figure below.
Type in Description.
Displays Users currently assigned to Resource. To add Users for this Resource, select from Available Users box, then click Add.
4. Using the procedures in steps 2 and 3, add resources from T1 to T8 for GT1 to GT8, as shown in the figure below.
Select
Type in
Select The Order value is the priority for the Alarms that fall under that particular class. The lower the Order number, the higher the priority. Select options
3. Using the procedures in step 2, add the classes and descriptions shown in the figure below.
Enter values as shown here into Alarm Class dialog box (as shown in step 2).
Colors selected in Alarm Class dialog box are displayed as a numerical equivalent here.
4.
In the Workbench left pane as shown below, select Screens. Alarm.cim (standard template from Cimproj) then displays in the right panel. Select
Alarm.cim.
1. Select
2. Select
5. Right click in CimEdit, then select Edit to open the following Alarms screen. Open Frame Container from the menu, as shown below.
Select
Note CIMPLICITY HMI uses frame animation (frame containers) to navigate between individual screens. This enables you to access all control and monitoring features needed. The frame displayed can be changed by clicking buttons or other frames.
6. Right click in CimEdit, then select CIMPLICITY AMV Control Object and Properties from the menu, as shown below. This displays the CIMPLICITY AMV Control Properties dialog box.
1. Select 2. Select
For servers, select. (Connect to the remote project only when the alarm is not available locally
Select the project from the dropdown list. Click OK. The project displays in the Projects tab.
8. In Projects tab, double-click the newly added project ALARM_FILTER. This displays the Project Settings dialog box, as shown below. Add the Alarm setup as shown below.
Type in
Click to select Alarm setup and exit back to the previous Projects dialog box.
Project and Setup listed. Select to apply changes, thus adding new project.
9. Open the Alarm.cim file in CimVview and click Setup, as shown below. The Alarm Setup dialog box displays.
Click
Bet sure to include the $ symbol at the beginning of the Setup name. This makes it accessible to all users. Without the symbol, it can be accessed only by the user account that created it.
Type in Setup name Click The Modify Setup box then displays (see below).
11. Select the Classes tab, then select DIAG from the list box.
12. Select the Resources tab. Then select T1 from the list box and OK to return to the Alarm Setups dialog box, as shown below.
Click
Click
Click
14. Follow the same procedure (steps 10 to 13) to create other setup.
Figure 5-4. Screen for Gas Turbine T1, Displaying Alarm Only for T1
Note Typically the top alarm window is for process alarms and the bottom one for diagnostic alarms.
Figure 5-5. Screen for Gas Turbine T2, Displaying Alarm Only for T2
To edit custom alarm features for the Silence, Lock, and Unlock buttons 1. Right-click on the white background of the Alarm window. A menu displays, as shown below. 2. Select CIMPLICITY AMV Control Object, then Properties. The properties window displays. Make the Buttons tab selections, as shown in the figure below.
Select tab to display Button properties options. Select to move highlighted button up or down. Select to modify highlighted buttons properties.
Button list. Highlight button name to select for modifying. Select to display the Lock, Unlock, and Silence button list. (A different list displays for each selection.)
3. In the Button Caption window, modify the button properties as shown in the figure below.
Use the following command strings to configure the buttons: Required data and data format can be viewed from the DOS command line by typing SILENCE and LOCKOUT. LOCKOUT uses the syntax:
LOCKOUT: <action><unitname><Encoded_drop><RefID>[(nodename)] LOCK lockout 1 %res %id %refid [(nodename)] UNLOCK: lockout 0 %res %id %refid [(nodename)]
Red dot represents the current turbine operating point. It moves as the point changes.
Introduction
The CIMPLICITY HMI product must be installed before these applications can be used. This chapter provides information about configuring CIMPLICITY projects for use with the turbine control HMI product. To understand and implement the information in this chapter, you should have a working knowledge of CIMPLICITY projects. Document GFK-1180 provides this information. CIMPLICITY HMI should be configured with the following project properties: Project Name Appropriate name (for example, SVR1) Sub Directory Must be Cimproj Path F:\Cimproj General options Basic control, external alarm manager Protocols MarkV+ Communication (this is TCIMB) Others determined by the type of controller The project properties can be examined using the CIMPLICITY Workbench (see Figure 6-2). This chapter is organized as follows:
Section Page
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
Using Workbench
Document GFK-1180 provides detail about using Workbench. The CIMPLICITY HMI Workbench is an application used to view, configure, organize, and manage projects. It is similar to the Microsoft Windows Explorer in its display of the file structure and menu options across the top of the window. Refer to Alarm Filtering in HMI Servers (Chapter 5) for examples of the Workbench window. To open Workbench 1. Click Start on the Windows task bar. 2. Select Programs, then CIMPLICITY, HMI, and Workbench. -Orw Select the .gef file in the f:\Cimproj directory. Figure 6-1 shows the File menu for starting a New Project. Figure 6-2 shows the Project menu selection for examining project Properties.
Figure 6-1. Workbench Menu Showing Selections for Starting a New Project
Figure 6-2. Workbench Menu Showing Selections for Examining Project Properties
Opening a Project
Using the CIMPLICITY HMI, there are three ways to open a project, as described below. To open a CIMPLICITY project through the Windows Start menu 1. Click Start on the Windows task bar. 2. Select Programs, then CIMPLICITY, HMI, and Workbench. A blank CIMPLICITY Workbench now opens. 3. From the Workbench window, select Open from the File menu. 4. Select the project you want to open. To open a CIMPLICITY project from the Windows File Explorer 1. Open File Explorer. 2. Open the f:\cimproj directory. 3. Double-click the .gef file. To open a CIMPLICITY project from the Start Menu 1. Click Start on the Windows task bar. 2. Select Documents. 3. Click the .gef file.
Signal Manager
The program can be found on the HMI in G:\EXEC\CSDBUtil.EXE. In Mark IV, V, and V LM, the Signal Manager is a program for configuring CIMPLICITY points and alarms for the turbine controllers. The TCI service must be running before using this utility, since it accesses data from each units Data Dictionary, which is built and maintained by the TCI service. For Mark IV, Mark V, and Mark V LM controllers, the Signal Manager is used to configure both points and alarms. Point information is retrieved from the Control Signal Database (CSDB) and used to populate the CIMPLICITY Point Manager Database. Alarm information is configured for run-time retrieval of the alarm text from the TCI. For a Mark VI, signal management is through an HMI device.
Setup
To enable alarms for CIMPLICITY 1. Create a new project. 2. Select options in the New Project dialog box , shown below.
After creating a new CIMPLICITY project, you must configure a CIMPLICITY Port for the communications protocol. This enables signals to be imported into the project. Refer to the CIMPLICITY Base System Users Manual GFK-1180 for more information on creating projects and configuring ports.
When the Signal Manager imports controller signals into CIMPLICITY, it configures any needed CIMPLICITY devices and resources, if they are not already present. For example, when importing signals for unit T1, the utility configures a CIMPLICITY device and a CIMPLICITY resource, both called T1. MARKV_RP is TCIMB function that collects data from a turbine using TCI and forwards the information to the CIMPLICITY Point Manager. For each device that Signal Manager configures, it a also configures three virtual points needed by the MARKV_RP program. For example, for a device called T1, the utility produces the following virtual points: T1_TIME, which contains the units current time T1_DATE, which contains the units current date T1_VALID, a Boolean value that indicates if the HMI is currently communicating with the unit
Signals
CSDB is Control System Database. Signal Manager displays data from the Data Dictionary, which describes the units CSDB. Each row of the display shows information about a signal, divided into columns that display the following signal attributes:
Signal attribute Name Access Cim Type Description Eng. Units Flags High Limit Low Limit Offset Precision Scale Code Synonym Type Value Description Signals name Read /write CIMPLICITY point type that corresponds to this signal Description of the signal Engineering Units Signal attributes (for example, alarm, command, permanent) High limit for the signals value Low limit for the signals value Offset into the CSDB where this signal is located Numeric precision for display of the signals value Scale code for engineering unit conversion Optionally specified synonym for this signal Datatype for this signal Signals current value
You can configure the items listed. The display is a standard Windows List Control, which supports the expected user interface commands for selecting items, sorting rows, and sizing columns.
Alarms
The Signal Manager can also be used to configure alarms for EX2000 and EX2100 exciters. CIMPLICITY alarms are only placeholders that are given the appropriate parameters at run-time when they occur. The Signal Manager can be used to configure the alarms for Mark V, Mark V LM, and Mark VI turbine controllers, as well and other events. It uses the following configuration IDs:
Alarm use Process alarms for turbine Diagnostic alarms for turbine Hold list points** Sequence of events** Digital events** Alarm ID for configuration P<n>* D<n>* (Mark V only) HOLD (Steam only) SOE EVENT
* n is the drop number reported by the controller. ** These CIMPLICITY alarms are generated multiple times at run-time with different parameters for each instance.
When the Signal Manager configures alarms, it also configures alarm classes, as follows: If a needed alarm class is not configured, it is added to the CIMPLICITY configuration If the alarm class is already configured, the existing alarm class definition is used The following alarm classes apply:
Class PRC DIAG HOLD SOE EVENT EX2K Definition Process alarms Diagnostic alarms Hold list entries Sequence of events Digital events Exciter alarms (see below)
To configure alarms for EX2000 exciters 1. Select EX2000 Alarms from the Action menu. Signal Manager then configures exciter alarms as defined in F:\EX2000.DAT and displays the Exciter Fault Code dialog box. 2. Make the signal selections as shown in the figure below. Signal Manager then runs command line utilities and displays their output in a scrolling text box. In CIMPLICITY, these utilities configure events and actions that generate alarms when the value of the fault code CIMPLICITY point changes value.
Type in signal name (Point ID) Select exciter core that generates the fault
Click when selections for the signal are completed in this box. The box remains open Click when no more signal selections are to be made. This closes the dialog box.
3. After these events and actions are configured, specify additional exciter fault code points using the Exciter Fault Code box as in step 2. 4. When completed, select Done.
Importing Signals
When the Signal Manager is started, an empty list displays. To add signals to the Signal Manager list 1. Select New from the File menu. 2. A dialog box displays, allowing you to specify which signals to get from the Data Dictionary.
Type in name with wildcards to filter signals retrieved from the Data Dictionary. Supported are: Asterisk (*), which matches zero or more occurrences of any character Question mark (?), which matches zero or one occurrence of any character
Select box(es) to filter the signals by type. (A check mark in a box allow signals of the corresponding type to pass through the filter). Select Unit from list of available units. Click when completed, adding signals to Signal Manager.
To individually import signals individually into CIMPLICITY w In Signal Manager, select the desired signals from the displayed list.
To import all signals at once into CIMPLICITY 1. In Signal Manager, select Select All from the Edit menu. 2. Select Import from the Action menu. This displays a dialog box that allows you to select the .gef file for the desired CIMPLICITY project (see Figure 6-6).
You may sometimes want to populate the CIMPLICITY point database with points from a set of screens. To populate the Signal Managers displayed list of signals with the signals referenced in a set of screens 1. Select Match from the Action menu. Signal Manager then scans all the screens and displays any points not found in the Data Dictionary. 2. Select the signals as desired and import them into the CIMPLICITY point database using the procedures described previously.
SDB Exchange
The System Database (SDB) Exchange is available for Mark VI controllers. It provides a way to populate the CIMPLICITY point and alarm databases with the data extracted from the Mark VI SDB. Refer to GEI-100279 for more information about the SDB Exchange.
SDB Utilities
The SDB Utilities must run on the PC that is the CIMPLICITY Server. The SDB Utilities are available for Mark VI controllers. They provide a way to populate the CIMPLICITY point and alarm databases with the data extracted from the Mark VI SDB. The SDB Utilities support four sources for importing signal and alarm data into the CIMPLICITY HMI Project: Signals from the SDB, which contains data used by one or more system devices. Signals from a comma separated variable file (*.csv), which is a common text format for spreadsheet and database output. Signals from a shared name file (*.snf), associated with the Series 90-70 programmable logic controller (PLC). Alarms imported from the SDB into the CIMPLICITY HMI Project alarm definitions. Refer to GEI-100500 for more information about the SDB Utilities. .
Mark IV
TCI
CIMPLICITY
CIMMOD
DCS
CimMod_L is a command line utility (CIMMOD_L.EXE) that reads the necessary configuration files in the TCI to create a Modbus list for CIMPLICITY (CIMMOD.LST). The list defines the format and scaling of each mapped coil and register. It also indicates which signals are controller commands. Refer to document GEI-100517 for more information about using CimMod and CimMod_L.
Section
Page
HMI Functions for GE Turbine Controllers ............................................................A-1 CIMPLICITY HMI Supported Functions ...............................................................A-4
HMI Function Data and Control Displays Demand Display Logic Forcing Dynamic Rung Display Pre-vote Data Display Diagnostic Counters Display Control Constants Display Control Constants Adjust Display Autocalibrate Display Trip History CIMPLICITY Add-ons CIMPLICITY Bridge Signal Manager External Alarm Manager Reactive Capability Display Manual Synchronizing Display Emissions Analysis Triggered Plot
Application Notes
Toolbox graphics for Mark VI Toolbox function for Mark VI Toolbox function for Mark VI TSM for Mark VI TSM for Mark VI Toolbox function for Mark VI Toolbox function for Mark VI Toolbox function for Mark VI Capture blocks for Mark VI
HMI Function Unit Communications Stagelink CSF MAMSP TCI Modbus Master EGD Unit Communications (continued) Process Alarms Diagnostic Alarms Events SOEs Hold List SDB Utilities / Exchange Unit Configuration Tools Sequence Editor Sequence Compiler Sequence Documentor CSP Printer Table Compiler Application Code Downloads Firmware Downloader Mark V Make Card Identification Alarm List FMV ID LDB Configuration Tools I/O Configuration Tool Time Synchronizing Timesync Function High Resolution (IRIG) GPS NTP
Mark IV
Mark V
Mark V LM
Mark VI
Application Notes
Not available in some Mark IVs Not available in some Mark IVs Not available in some Mark IVs
Toolbox function for Mark VI Controllers with Steam ATS only Toolbox function for Mark VI
Toolbox function for Mark VI Toolbox function for Mark VI Toolbox function for Mark VI Toolbox function for Mark VI
HMI Function Other Functions Alarm Printing Alarm History Trip History Automatic Collection Normal Data Collection High-speed Data Collection Control Constants Compare Optional Functions TCI Modbus Slave TCI Modbus Master GSM Power Block Control Performance Monitor Web Diagnostic Functions Demand Display Logic Forcing Display Alarm Display Control Constants Display HMI Log Files ARCWHO Utility Diagnostic Programs Product Code File Verification
Mark IV
Mark V
Mark V LM
Mark VI
Application Notes
Simple cycle only For external device interface Capture Blocks + Data Historian for Mark VI Toolbox function for Mark VI Toolbox Trend Recorder for Mark VI
Supported
Alarm Viewer Basic Control Engine Data Logger DDE Server (CWSERV) Dynamic Measurement Systems Genius Communication from HMI Historical Data Analyzer Historical Trends HMI for CNC
Interactive ActiveX alarm viewing object Visual Basic for applications scripting language Data logging via ODBC
Comprehensive data summarization Interactive ActiveX object for viewing trend Integration with GE Fanuc CNC controllers
3.2 SP7
3.2 SP7
Consult Salem, VA factory, Turbine Control Application Engineering (540) 387-7388 Consult Salem, VA factory, Turbine Control Application Engineering (540) 387-7388 Pending
CIMPLICITY Function PointBridge Quick Trends Real-time Trends Recipes Report Manager
Supported
Application Notes Allows CIMPLICITY server to act as device to another server Pop-up trends for any points on a screen Interactive ActiveX object for viewing trend Device-independent recipe management Report generation and management from process
3.2 SP7
View PLC faults Complete mission critical redundancy support Reusable drag and drop graphic and scripted objects New features for SPC Constantly watches HMI and system parameters Track items through a production facility
4.01 SP2
3.2 SP7
Send CIMPLICITY HMI data to web pages Send screens over web to standard web browsers ActiveX object for plotting multiple x-y data
3.2 SP7
XY Plots
Notes
Introduction
The turbine controllers generate three types of alarms, which are viewed on the HMI or toolbox: Process, Hold List, and Diagnostic (see Figure B-1).
Alarm Display Diagnostic Display
HMI
HMI
Toolbox
UDH
<S> Controller
<T> Controller
Diagnostic Alarms
I/O
I/O
I/O
This appendix provides a general overview of turbine controller alarms viewed and addressed using the HMI. It is intended to assist the operator in understanding how to use the HMI for monitoring, using the features described in this document. Note The information in this appendix applies specifically to the Mark VI controller. However, it should also apply to Mark IV, Mark V, and Mark V LM controllers, except in discussion of Control System Toolbox features. This information is provided as follows:
Section Page
Hold List Alarms ..................................................................................................... B-2 Process Alarms ........................................................................................................ B-2 Process (and Hold) Alarm Data Flow............................................................... B-2 Diagnostic Alarms ................................................................................................... B-3
Process Alarms
Process Alarms are caused by machinery and process problems, and alert the operator by means of messages on the HMI screen. The alarms are created in the controller using alarm bits generated in the I/O boards or in sequencing. The user configures the desired analog alarm settings in sequencing using the toolbox. Process Alarms are generated by the transition of Boolean signals configured by the toolbox (for Mark VI) with the alarm attribute. The signals may be driven by sequencing or they may be tied to input points to map values directly from I/O boards. Process alarm signals are scanned each frame after the sequencing is run. In TMR systems, process signals are voted and the resulting composite diagnostic is present in each controller. A useful application for process alarms is the annunciation of system limit checking. Limit checking takes place in the I/O boards at the frame rate, and the resulting Boolean status information is transferred to the controller and mapped to Process Alarm signals. Two system limits are available for each process input, including thermocouple, RTD, current, voltage, and pulse rate inputs. System limit 1 can be the high or low alarm setting, and system limit 2 can be a second high or low alarm setting. These limits are configured from the toolbox in engineering units. There are several choices when configuring system limits. Limits can be configured as enabled or disabled, latched or unlatched, and greater than or less than the preset value. System out of limits can be reset with the RESET_SYS signal.
Mark VI Controller
UDH
Mark VI HMI
Input
Signal 1
. . .
Input
. . .
Signal n
Alarm Logic Variable Alarm ID
Alarm Scanner
Alarm Report
Alarm Receiver
Alarm Viewer
Alarm Command
Alarm Queue Operator Commands - Ack - Reset - Lock - Unlock - Override for Hold Lists
Diagnostic Alarms
Diagnostic Alarms are caused by equipment problems, and use settings factory programmed in the boards. Diagnostic Alarms identify the failed module to help the service engineer quickly repair the system. For details of the failure, the operator can request a display on the toolbox screen (Mark VI) or review the details in the HMI Alarm Display screen. The controller and I/O boards all generate diagnostic alarms, including the VCMI, which generates diagnostics for the power subsystem. The controller has extensive self-diagnostics, most that are available directly at the toolbox (for Mark VI). Diagnostic alarms can be viewed from the toolbox by selecting the desired board, clicking the right mouse button to display the drop down menu, and selecting display diagnostics. A list of the diagnostic alarms for any I/O board can be displayed, and may be reset from the toolbox.
Notes
Glossary
ActiveX
ActiveX, developed by Microsoft, is a set of rules for how applications should share information. With ActiveX, users can ask or answer questions, use pushbuttons, and interact in other ways with the web page or compatible program. It is not a programming language, but rather a model for writing programs so that other programs and the operating system can call them. ActiveX technology is used with Microsoft Internet Explorer to make interactive web pages that look and behave like computer programs, rather than static pages.
ActiveX control
A control (object) using ActiveX technologies to enable animation. An ActiveX control can be automatically downloaded and executed by a web browser. Programmers can develop ActiveX controls in a variety of languages, including C, C++, Visual Basic, and Java. ActiveX controls have full access to the Windows operating system.
alarm
A message notifying an operator or administrator of equipment, network, or process problems.
Alarm Viewer
A standalone window within CIMPLICITY (an OCX control) for monitoring and responding to alarms.
AMV
Alarm Viewer.
application
A complete, self-contained program that performs a specific function directly for the user. Application programs are different than system programs, which control the computer and run application programs and utilities.
ARCNET
Attached Resource Computer Network, a LAN communications protocol developed by Datapoint Corporation. ARCNET defines the physical (coax and chip) and datalink (token ring and board interface) layer of a 2.5 MHz communication network.
Glossary 1
board
Printed wiring board, or circuit board, used for electronic circuits.
Boolean
Digital statement that expresses a condition that is either True or False, also called a discrete, or logical signal.
<C>
The turbine controllers Communicator core (processor).
CimEdit
An object-oriented graphics editor tool of CIMPLICITY HMI that functions with its runtime viewer CimView. It can create graphical screens with animation, scripting, colors, and a variety of graphical elements that represent power plant operation.
CIMPLICITY HMI
Pc-based operator interface software from GE Fanuc Automation, configurable to work with a wide variety of control and data acquisition equipment.
cimproj
The required subdirectory name for a CIMPLICITY HMI project (F:\Cimproj). The project configuration Workbench (.gef) is located in this subdirectory.
CimView
An interactive graphical user interface of CIMPLICITY HMI used to monitor and control power plant equipment, displaying data as text or a variety of graphic objects. Its screens were created with CimEdit. They include a variety of interactive control functions for setting point values, displaying other graphic screens, and initiating custom software routines and other Windows applications.
client-server
Software architecture where one software product makes requests on another software product. For example, an arrangement of PCs with software making one a data acquisition device and the other a data using device.
command line
The line on a computer display where the user types commands to be carried out by a program. This is a feature of a text-based interface such as MS-DOS, as opposed to a graphical user interface (GUI) such as Windows.
configure
Select specific options, either by editing disk files, or by setting the location of hardware jumpers, or by loading software parameters into memory.
2 Glossary HMI for SPEEDTRONIC Turbine Control GEH-6126A Volume I
control system
Equipment that automatically adjusts the output voltage, frequency, MW, or reactive power, as the case may be, of an asset in response to certain aspects of common quality such as voltage, frequency, MW, or reactive power. Such equipment includes, but is not limited to, speed governors and exciters.
CRC
Cyclic Redundancy Check which is used to detect errors in data such as transmissions or files on a disk.
cross plot
Display of two variables, plotted one against the other over time, in an X-Y type plot to detect signal correlations and to analyze performance.
CSDB
Control Signal Database, used in the turbine controller to store real time process data used in the control calculations.
CSF
Control System Freeway, a token passing communication network, typically using TWINAX cabling, running at 2.3 MHz.
<D>
The turbine controllers backup Communicator core (processor). (Also see <C>.)
data dictionary
A system file that contains the information needed to operate a database in a database management system. This file includes basic operating information about the records and fields of a certain database, the limits on acceptable data values, and access-authorization information. For the HMI, the data dictionary files contain information about unit-specific control signal database pointnames, alarm text messages (for both process and diagnostic alarms), and display information for signal pointnames (type/units, messages, and such). The primary unit Data Dictionary file, UNITDATA.DAT, can be created on an HMI in the unit-specific directory.
DCS
Distributed Control System, used for process control applications including control of boilers and other power plant equipment.
deadband
Range of values inside of which the incoming signal can be altered without changing the output response. The Historian uses a sophisticated deadband algorithm to decide whether to save or discard incoming data, as part of its data compression function.
Glossary 3
Demand Display
An HMI function that allows you to monitor several turbine data points at a time and issue simple commands. It supports multiple units.
device
A configurable component of a process control system.
Devcom
Application program that serves as a communications bridge between the CIMPLICITY HMI Point Manager and a device being monitored.
dynamic
An attribute emphasizing motion, change, and process as opposed to static.
EGD
Ethernet Global Data, a network protocol used by some controllers. Devices share data through periodic EGD exchanges (pages of data).
Ethernet
LAN with a 10 or 100 megabaud data rate, used to link one or more computers and/or controllers together. It features a collision avoidance/collision detection system. It uses TCP/IP and I/O services layers that conform to the IEEE 802.3 standard, developed by Xerox, Digital Equipment Corporation (DEC), and Intel.
event
Discrete signal generated by a change in a status of a logic signal in a controller.
EX2000
GE generator exciter control. It regulates the generator field current to control the generator output voltage.
fault code
A message from the controller to the HMI indicating a controller warning or failure.
firmware
Set of executable software, stored in memory chips that hold their content without electrical power, such as EPROM or Flash memory.
filter
A program that separates data or signals in accordance with specified criteria.
forcing
Setting a signal to a particular value, regardless of the value the blockware or I/O is writing to that signal.
frame rate
Basic scheduling rate of the controller. It encompasses one complete input-computeoutput cycle for the controller.
4 Glossary
GSM
GE Industrial Systems Standard Messages. Application-level messages processed in gateway to the DCS. The gateway serves as a protocol translator and can communicate directly with several process controllers. No data is emitted from the gateway unless previously requested by the DCS equipment.
header
Textual information, such as a title, date, name, or other applicable identifying information, positioned at the top of a screen, column, or page, and usually repeated at every occurrence.
Historian
A client/server-based data archival system for data collection, storage, and display of power island and auxiliary process data.. It combines high-resolution digital event data from the turbine controller with process analog data to create a sophisticated tool for investigating cause-effect relationships.
HMI
Human-Machine Interface. The GE HMI is a Windows NT-based operator interface to the turbine controllers and auxiliary power plant equipment. The HMI uses CIMPLICITY as the operator interface, and supports the Historian Client Toolset for viewing Historian data.
HRSG
Heat Recovery Steam Generator. This uses exhaust heat from a gas turbine to generate steam.
icon
A small picture intended to represent something (a file, directory, or action) in a graphical user interface. When an icon is clicked on, some action is performed, such as opening a directory or aborting a file transfer
ICS
Integrated Control System. The GE ICS combines various power plant controls into a single distributed control system.
initialize
Set values (addresses, counters, registers, and such) to a beginning value prior to the rest of processing.
Glossary 5
IONet
The Mark VI I/O Ethernet communication network.
LAN
Local area network (communications). A typical LAN consists of peripheral devices and controllers contained in the same building, and often on the same floor.
logical
Statement of a true/false sense, such as a Boolean.
Mark IV
SPEEDTRONIC gas turbine controller, introduced in 1983. The first GE triple modular redundant (TMR) control for fault-tolerant operation.
Mark V
All-digital SPEEDTRONIC gas and steam turbine controller, introduced in 1991, available in Simplex and TMR control versions. At first equipped with a DOS-based pc operator interface, later upgraded to use the NT-based CIMPLICITY HMI.
Mark V LM
SPEEDTRONIC gas turbine controller, introduced in 1995, designed specifically to support the aeroderivative Dry Low Emissions (DLE) technology developed by GE Aircraft Engines. Equipped to use the NT-based CIMPLICITY HMI.
Mark VI
VME-based SPEEDTRONIC gas and steam turbine controller, available in Simplex and TMR control versions. Equipped to use the NT-based CIMPLICITY HMI and Control System Toolbox.
menu
(Software.) A list from which the user may select an operation to be performed.
Modbus
Serial communication protocol, initially developed by Gould Modicon for use between PLCs and other computers.
network
A data communication system that links two or more computers and peripheral devices.
object
(Software.) Generally, any item that can be individually selected and manipulated. This can include shapes and pictures that appear on a display screen, as well as less tangible software entities. In object-oriented programming, for example, an object is a self-contained entity that consists of both data and procedures to manipulate the data.
OCX
OLE custom control. An independent program module that can be accessed by other programs in a Windows environment. ActiveX (Microsofts next generation of controls) is backward compatible OCX.
6 Glossary HMI for SPEEDTRONIC Turbine Control GEH-6126A Volume I
OLE
(Pronounced as separate letters.) Object linking and embedding. A compound document standard developed by Microsoft Corporation. It enables you to create objects with one application and then link or embed them in a second application. Embedded objects retain their original format and links to the application that created them. Support for OLE is built into the Windows.
OPC
OLE for Process Controls. The OPC Specification is a non-proprietary technical specification that defines a set of standard interfaces based upon Microsofts OLE/COM technology. The application of the OPC standard interface makes possible interoperability between automation/control applications, field systems/devices, and business/office applications.
panel
The side or front of a piece of equipment on which terminations and termination assemblies are mounted.
pc
Abbreviation for personal computer.
PDH
See Plant Data Highway.
permissives
Conditions that allow advancement from one state to another.
PLC
Programmable logic controller. These are designed for discrete (logic) control of machinery, and they also compute math (analog) functions and perform regulatory control.
plot
To draw an image by connecting a series of precisely placed points on a screen or paper, using a series of lines.
point
Basic unit for variable information in the controller, also referred to as signal.
Glossary 7
reactive capability
The reactive power injection or absorption capability of generating sets and other reactive power resources such as Static Var Compensators, capacitors, and synchronous condensers. This includes reactive power capability of a generating set during the normal course of the generating set operations.
reboot
Restart the controller or pc after a controlled shutdown.
resources
Also known as groups. Resources are systems (devices, machines, or work stations where work is performed) or areas where several tasks are carried out. Resource configuration plays an important role in the CIMPLICITY system by routing alarms to specific users and filtering the data users receive.
runtime
See product code.
server
A pc that gathers data over Ethernet from plant devices, and makes the data available to pc-based operator interfaces known as Viewers.
setpoint
Value of a controlled variable, departure from which causes a controller to operate to reduce the error and restore the intended steady state.
signal
Basic unit for variable information in the controller, also referred to as point.
Simplex
Operation that requires only one set of control and I/O, and generally uses only one channel.
SOE
See Sequence of Events.
SRTP
Service Request Transfer Protocol. An Ethernet communications protocol for communications between the turbine controller and the HMI.
8 Glossary
Stagelink
ARCNET-based communication link used by many controllers.
synchroscope
Instrument for detecting whether two moving parts are synchronized
tag
Identifying name given to a process measurement point.
TCEA
DS200TCEA Emergency Overspeed Board (TCEA), located in the controllers Protective Core <P1>, is used for the high-speed protection circuitry. It is often referred to as the Protective Processor. The three TCEA boards used in the <P1> core are referred to as the <X>, <Y>, and <Z> processors. These boards scale and condition input for high and low shaft speed, flame detection, and automatic synchronization. They then output the signals via the TCEA (location 1) board over the IONET to the <R1> cores DS200STCA board. The TCEAs send emergency trip signals to the Turbine Trip Board (DS200TCTG). Each TCEA has its own power supply and power supply diagnostics.
TCI
Turbine Control Interface. The GE-supplied software package on the HMI that interfaces to the turbine control.
TCP/IP
Communications protocols developed to inter-network dissimilar systems. It is a de facto UNIX standard, but is supported on almost all systems. TCP controls data transfer and IP provides the routing for functions, such as file transfer and e-mail.
timetag
Information added to data to indicate the time at which it was collected. Also called a time stamp.
TMR
Triple Modular Redundancy. This is an architecture that uses three identical sets of control and I/O, and votes the results to obtain highly reliable output signals.
trend
Time-based screen plot showing the history of process values, available in the Historian, HMI, and the Control System Toolbox.
trigger
Transition in a discrete signal from 0 to 1, or from 1 to 0, initiating an action or sequence.
Glossary 9
UTC
Coordinated Universal Time, an international time-reference standard.
utility
A small helper program that performs a specific task, usually related to managing system resources. Utilities differ from applications mostly in terms of size, complexity, and function.
web browser
Pc software, such as Microsoft Internet Explorer or Netscape Navigator, allowing screens and data to be viewed over a network from a server.
Windows NT
Advanced 32-bit operating system from Microsoft Corporation for 386-based PCs and above.
Workbench
A CIMPLICITY HMI program used to view, configure, organize, and manage every component of a CIMPLICITY project through a single window.
10 Glossary
Index
A
ActiveX objects, 1-9, 5-1, 5-2, 5-6, A-4, A-5 Manual Synchronizing Display, 5-2, 5-6, A-1 trends, 1-6, A-4, A-5 Triggered Plot, 5-2, 5-6, 5-7, A-1 alarm display, 2-3, 2-6, 4-16 Alarm Viewer, 1-6, 2-3, 2-6, 4-16, 5-8, 5-26, A-4, B-2 CimView, 1-5, 1-6, 2-2 Extended Alarm Commands, 2-3, 5-1, 5-26 Lock, 2-3, 4-17, 5-26, 5-27, B-2 Lockout, 5-1, 5-26, 5-27 Silence, 2-3, 5-1, 5-26, 5-27 Unlock, 2-3, 5-26, 5-27, B-2 alarm filters, 5-8 configuring, 5-14 Alarm Viewer, 1-6, 2-3, 2-6, 4-16, 5-8, 5-26, A-4, B-2, AMV, 5-18, 5-26 CimView, 1-5, 1-6, 2-2 Extended Alarm Commands, 2-3, 5-1, 5-26 Lock, 2-3, 4-17, 5-26, 5-27, B-2 Lockout, 5-1, 5-26, 5-27 Silence, 2-3, 5-1, 5-26, 5-27 Unlock, 2-3, 5-26, 5-27, B-2 alarms, 1-3, 1-4, 1-6, 2-3, 2-5, 3-9, 4-15, 4-16, 5-1, 5-8, 5-26, 6-4, 6-5, 6-6, 6-10, A-4, B-2 alarm display, 2-3, 2-6, A-3, B-3 Alarm Logger Control, 2-6, 4-15 Alarm Viewer, 1-6, 2-3, 2-6, 4-16, 5-8, 5-26, A-4, B-2 alarm.cim file, 5-16, 5-20 AMV, 5-18, 5-26 diagnostic, 6-6, 6-10, A-2, B-1, B-3 Extended Alarm Commands, 2-3, 5-1, 5-26 Lock, 2-3, 4-17, 5-26, 5-27, B-2 Lockout, 5-1, 5-26, 5-27 Silence, 2-3, 5-1, 5-26, 5-27 Unlock, 2-3, 5-26, 5-27, B-2 External Alarm Manager, 6-10, A-1 filtered, 1-9, 5-23 filtering, 5-8, 6-2 Hold List, 2-6, 4-16, 4-17, 6-6, A-2, B-1, B-2 process, 3-12, 6-10, A-2, B-1 B-3 AMV, 5-18, 5-26 animation, 1-5, 3-3, 3-4, 5-17 graphic displays, 1-2, 1-3, 1-4, A-1
B
Balance of Plant, 1-7, 5-8, 5-25 board (see printed wiring boards) Boolean, 6-5, B-2 BOP (see Balance of Plant) breaker (see circuit breaker)
C
CimEdit, 1-5, 1-8, 5-17 animation, 1-5, 3-3, 3-4, 5-17 CIMPLICITY ActiveX objects, 1-9, 5-1, 5-2, 5-6, A-4, A-5 HMI, 1-3, 1-8, 2-3, 5-1, 5-2, 5-6, 5-8, 5-12, 5-14, 5-17, 6-1 6-3, 6-10, 6-12, A-1, A-4, A-5, B-2 Cimproj, 5-16, 6-1, 6-2 CimView, 1-5, 1-6, 2-2, A-4 circuit breaker, 5-2, 5-3 client-server, 1-1 command line, 3-6, 3-11, 3-15, 4-13 4-15, 5-27, 6-7, 6-11 communications, 1-3, 1-6, 1-8, 6-4, 6-12, A-2, A-4 Ethernet, 1-7, 3-13, 6-1, 6-11 Modbus, 1-7, 6-11, A-2 A-4 configuration, 1-3, 1-9, 2-4, 4-7, 4-13, 4-14, 4-16, 5-1, 5-3 5-6, 5-8, 5-12, 5-14, 6-2, 6-4 6-7 alarm filters, 5-14 Demand Display, 4-13 resources, 5-12 users, 5-8 Control Signal Database (CSDB), 4-17, 6-4, 6-5 control system, 1-3, 1-6, 1-9, 4-1 Control System Freeway (CSF), A-2 Control System Solutions, 1-8 Control System Toolbox (toolbox), 1-2, 1-7, 1-8, 2-5, 3-2, 3-9, 3-13, 4-2, 6-10, B-1 B-3 Trend Recorder, 1-2, 1-8, 3-13, A-3 controllers Mark IV, 1-1, 1-3, 4-2, 4-13, 4-15, 5-28, 6-4, 6-10, 6-11, A-1, A-2, B-1 Mark V, 1-1 1-3, 1-7, 1-8, 2-5, 2-6, 3-2, 3-9, 3-12 3-15, 4-2, 5-2, 5-6, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 Mark V LM, 1-1, 1-8, 3-12, 3-14, 3-15, 6-4, 6-6, A-1, B-1 Mark VI, 1-1 1-3, 1-7, 1-8, 2-5, 3-2, 3-9, 3-13, 4-2, 4-16, 5-2, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 controls ActiveX, 1-9, 5-1, 5-2, 5-6, A-4, A-5 CSDB (see Control Signal Database), 4-17, 6-4, 6-5 CSF (see Control System Freeway)
Index 1
D
Data Dictionary, 1-3, 4-3 4-6, 4-9, 6-4, 6-5, 6-9 data history, 3-9, 3-11, 3-12, 3-15 database Control Signal Database (CSDB), 4-17, 6-4, 6-5 SDB Exchange, 1-8, 6-10 SDB Utilities, 6-10, A-2 DCS (see Distributed Control System) Demand Display, 2-6, 3-2, 3-3, 3-5, 3-8, 4-2 4-11, 4-13, 4-14, A-1, A-3 configuring, 4-13 Find All Function, 3-7 starting, 4-2 timetag, 4-5 diagnostic alarms, 6-6, 6-10, A-2, B-1, B-3 displays CimView, 1-5, 1-6, 2-2 Demand Display, 2-6, 3-2, 3-3, 3-5, 3-8, 4-2 4-11, 4-13, 4-14, A-1, A-3 Manual Synchronizing, 5-2, 5-6, A-1 Reactive Capability, 5-28, A-1 Sequencing, 3-7 Distributed Control System (DCS), 1-7 documentation, 1-8, 1-10, 4-2 DOS commands (command line), 3-6, 3-11, 3-15, 4-13 4-15, 5-27, 6-7, 6-11 Dynamic Rung Display, 1-4, 3-2 3-8 starting, 3-6 timetag, 3-4, 3-5, 3-9
G
GE Standard Messages (GSM), 1-7, A-3 graphic displays, 1-2 1-6, 5-1, 5-28, A-1, A-5 CimEdit, 1-5, 1-8, 5-17 CimView, 1-5, 1-6, 2-2 GSM (see GE Standard Messages)
H
Help, 4-11 How to Get, 1-10 Historian, 1-2, 1-7, 1-8, 3-13, A-3 HMI (see Human-Machine Interface) hold alarms data flow, B-1, B-2 Hold List, 2-6, 4-16, 4-17, 6-6, A-2, B-1, B-2 Human-Machine Interface (HMI) features, 1-2 optional features, 1-7 other tools, 2-5 program files, 4-3 setup, 1-8, 5-19 5-21, 6-4 specifications, 1-7 startup, 2-2
I
ICS, 1-7
K E
EGD (see Ethernet Global Data), 3-13, A-2 Ethernet, 1-7, 3-13, 6-11 Ethernet Global Data (EGD), 3-13, A-2 EX2000, 6-6, 6-7 fault code, 6-6, 6-7 exciter, 5-8, 6-6, 6-7 Extended Alarm Commands, 2-3, 5-1, 5-26 Lock, 2-3, 4-17, 5-26, 5-27, B-2, 4-17 Lockout, 5-1, 5-26, 5-27 Silence, 2-3, 5-1, 5-26, 5-27 Unlock, 2-3, 5-26, 5-27, B-2 External Alarm Manager, 6-10, A-1 keypad menus, 1-9
M
Manual Synchronizing Display, 5-2, 5-6, A-1 Mark IV, 1-1, 1-3, 4-2, 4-13, 4-15, 5-28, 6-4, 6-10, 6-11, A-1, A-2, B-1 Mark V, 1-1 1-3, 1-7, 1-8, 2-5, 2-6, 3-2, 3-9, 3-12 3-15, 4-2, 4-16, 5-2, 5-6, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 Mark V LM, 1-1, 1-8, 3-12, 3-14, 3-15, 6-4, 6-6, A-1, B-1 Mark VI, 1-1 1-3, 1-7, 1-8, 2-5, 3-2, 3-9, 3-13, 4-2, 4-16, 5-2, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 Modbus, 1-7, 6-11, A-2, A-3, A-4
F
fault code, 6-6, 6-7 file structure, 3-2, 6-2 filter, 5-8 filtered alarms, 1-9, 5-23 Resource Definition, 5-13 Role Properties, 5-11 User Properties, 5-10
N
network, 1-4 Ethernet, 1-7, 3-13, 6-1, 6-11 Modbus, 1-7, 6-11, A-2, A-3, A-4
2 Index
O
objects ActiveX, 1-9, 5-1, 5-2, 5-6, A-4, A-5 OCX, 2-3, 5-8 OLE, 1-5, 2-3, 5-1, 5-2, 6-12 OPC, 1-8, 6-12, A-4 OCX, 2-3, 5-8 OLE, 1-5, 2-3, 5-1, 5-2, 6-12 OLE for Process Controls (OPC), 1-8, 6-12, A-4 OPC (see OLE for Process Controls)
Mark V, 1-1 1-3, 1-7, 1-8, 2-5, 2-6, 3-2, 3-9, 3-12 3-15, 4-2, 4-16, 5-2, 5-6, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 Mark V LM, 1-1, 1-8, 3-12, 3-14, 3-15, 6-4, 6-6, A-1, B-1 Mark VI, 1-1 1-3, 1-7, 1-8, 2-5, 3-2, 3-9, 3-13, 4-2, 4-16, 5-2, 6-4, 6-6, 6-10, A-1 A-3, B-1 B-3 startup, 1-5, 1-6, 2-2
T
TCI (see Turbine Control Interface) TCP/IP, 1-7, A-4 timetag, 3-4, 3-5, 3-9, 3-12, 4-5 TMR (see Triple Modular Redundancy) toolbox (see Control System Toolbox) trend, 1-6, A-4, A-5 Trend Recorder, 1-2, 1-8, 3-13, A-3 Trip History, 2-5, 3-9 3-15, A-1, A-3 trends ActiveX objects, 1-6, A-4, A-5 Triggered Plot, 5-2, 5-6, 5-7, A-1 valve travel, 5-6 Trip History, 2-5, 3-9 3-15, A-1, A-3 Data History Results Window, 3-9, 3-11, 3-12, 3-15 Dialog Box, 3-9, 3-11 Display, 2-5 Log, 2-5, 3-14, 3-15 Mark VI, 3-13 starting, 3-11 timetag, 3-9 Triple Modular Redundancy (TMR), B-2 Turbine Control Interface (TCI), 1-2, 1-3, 2-3, 2-5, 3-14, 4-16, 5-1, 5-2, 5-26, 6-4, 6-5, 6-11, A-1 A-3
P
panel, 1-6, 5-16 PDH (see Plant Data Highway) permissives, 1-4, 5-4 Plant Data Highway (PDH), 1-3 PLC (see Programmable Logic Controller) points, 1-3, 1-6, 2-6, 3-3, 3-8, 3-9, 3-12, 4-3, 4-5, 4-6, 4-14 4-17, 6-4 6-7, 6-9, A-5, B-2 printed wiring boards, B-3 process alarms, 3-12, 6-10, A-2, B-1 B-3 data flow, B-1, B-2 TMR systems, B-2 program files, 4-3 Programmable Logic Controller (PLC), 6-10, A-5 projects, 1-9, 2-4, 5-8, 5-12, 5-14, 5-19, 6-1 6-4, 6-9, 6-10, 6-12 configuration Cimproj, 5-16, 6-1, 6-2 Workbench, 2-4, 5-8, 5-12, 5-14, 5-16, 6-1 6-3 opening, 2-4, 6-3
R
Reactive Capability Display, 5-28, A-1 requisition, 1-10 Resource Definition, 5-13 resources, configuring, 5-12 Role Properties, 5-11 rungs, 2-5, 3-2, 3-3, 3-6 3-8, A-1
U
UDH (see Unit Data Highway) Unit Data Highway (UDH), 1-3, B-2 User Properties, 5-10 users, configuring, 5-8
S
SDB Exchange, 1-8, 6-10 SDB Utilities, 6-10, A-2 security, 1-2, 5-8, 5-12 Sequence of Events (SOE), 6-6 Sequencing Display, 3-7 setpoint, 4-7, 6-12, 4-7 Signal Manager, 6-4 6-9, A-1 signals, importing, 6-8 SOE (see Sequence of Events) specifications, 1-7 SPEEDTRONIC controllers Mark IV, 1-1, 1-3, 4-2, 4-13, 4-15, 5-28, 6-4, 6-10, 6-11, A-1, A-2, B-1
V
valve travel, 5-6
W
web, A-5 Diagnostic Functions, A-3 Gateway, 1-7, A-5 Workbench, 2-4, 5-8, 5-12, 5-14, 5-16, 6-1 6-3
Index 3
Notes
4 Index
*( ,QGXVWULDO 6\VWHPV
Brrhy@yrpvp8h $#"'&& B@vqvhyp $ Shxr7yq ThyrW6!# $"%#(!VT6