5 - Geh-6126c - Vol - I Hmi Manual

GE Energy
HMI for Turbine Control

Operators Guide
GEH-6126& Vol I
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.
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 Energy.
GE provides the following document and the information included therein as is and
without warranty of any kind, expressed or implied, including but not limited to any
implied statutory warranty of merchantability or fitness for particular purpose.
If further assistance or technical information is desired, contact the nearest GE Sales or
Service Office, or an authorized GE Sales Representative.
2008 - 2011 General Electric Company, USA. All rights reserved.

Issued: 2008-06-11
Revised: 2011-09-19
* Trademark of General Electric Company
CIMPLICITY is a registered trademark of GE Fanuc Automation North America, Inc.

Modbus is a registered trademark of Schneider Automation.
SPEEDTRONIC is a trademark of General Electric Company, USA.

Windows and Windows NT are registered trademarks of Microsoft Corporation.
To:
Reader Comments
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Fax: 1-540-387-8651
(GE Internal DC 8-278-8651)
We welcome comments and suggestions to make this publication more useful.

Your Name
Todays Date
Your Companys Name and Address
Job Site
GE Requisition No.
If needed, how can we contact you?

Fax No.
Phone No.
E-mail
Your Job Function / How You Use This Publication
Publication No.
Address
Publication Issue/Revision Date
General Rating
Excellent
Contents
{
Organization
{
Technical Accuracy {
Clarity
{
Completeness
{
Drawings / Figures {
Tables
{
Referencing
{
Readability
{
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.) ________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
{ Superior
{ Comparable
{ Inferior
Detach and fax or mail to the address noted above.
{ Do not know
Comment ____________________________________________
........................................................................ Fold here and close with staple or tape ..........................................................................................

Place
stamp
here.
____________________________
____________________________
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
.......................................................................................... Fold here first ........................................................................................................
Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

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

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

strictly followed in order to optimize these applications.
Note Indicates an essential or important procedure, condition, or statement.
This equipment contains a potential hazard of electric shock

or burn. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
Isolation of test equipment from the equipment under test
presents potential electrical hazards. If the test equipment
cannot be grounded to the equipment under test, the test
equipments case must be shielded to prevent contact by
personnel.
To minimize hazard of electrical shock or burn, approved
grounding practices and procedures must be strictly followed.
To prevent personal injury or equipment damage caused by

equipment malfunction, only adequately trained personnel
should modify any programmable machine.
Contents
Chapter 1 Overview
1-1
Introduction ...............................................................................................................................................1-1
HMI Overview ..........................................................................................................................................1-1
Product Features.............................................................................................................................1-1
HMI Components...........................................................................................................................1-2
Graphic Displays............................................................................................................................1-3
Communications ............................................................................................................................1-5
Optional Features ...........................................................................................................................1-5
Application-Specific Features ........................................................................................................1-6
Technical Specifications............................................................................................................................1-6
Related Documentation .............................................................................................................................1-7
How to find the 3V number.......................................................................................................................1-8
Chapter 2 Quick-Start Procedures
2-1
Introduction ...............................................................................................................................................2-1
Starting Up the HMI..................................................................................................................................2-1
Other HMI Displays ..................................................................................................................................2-4
Lockout Function Master Reset - Mark IV, Mark V, Mark V LM and Mark VI...........................2-4
Trip Diagram Display - Mark IV, Mark V, Mark V LM and Mark VI ..........................................2-5
Lockout Function Diagnostic Reset - Mark V, Mark V LM and Mark VI....................................2-6
Start Checks Display - Mark V, Mark V LM and Mark VI ..........................................................2-7
Alarm Setup - Mark IV, Mark V, Mark V LM and Mark VI........................................................2-8
Turbine Startup Trend Display - Mark IV, Mark V, Mark V LM and Mark VI ............................2-9
Synchronization Display - Mark IV, Mark V, Mark V LM and Mark VI...................................2-10
Optional HMI Displays ...........................................................................................................................2-11
Reactive Capability Display - Mark IV, Mark V, Mark V LM and Mark VI .............................2-11
Manual Synchronizing Display....................................................................................................2-12
Triggered Plot Display .................................................................................................................2-15
Other Tools..............................................................................................................................................2-16
Viewing Sequencing Information ................................................................................................2-16
Viewing Trip Information ............................................................................................................2-24
Alarm Logger Control..................................................................................................................2-30
Hold List Display (Steam Turbine Applications).........................................................................2-31
Accessing the Web-Based Displays- Mark IV, Mark V, Mark V LM, Mark VI ........................2-32
Chapter 3 Display and Control (Command) Programs
3-1
Introduction ...............................................................................................................................................3-1
Viewing Sequencing Information..............................................................................................................3-1
Viewing Sequencing Information - Mark IV .................................................................................3-1
Viewing Sequencing Information - Mark V and Mark V LM ......................................................3-2
Viewing Sequencing Information - Mark VI ...............................................................................3-10
Viewing Trip Information .......................................................................................................................3-14
Viewing Trip Information - Mark IV...........................................................................................3-14
Viewing Trip Information Mark V and Mark V LM ................................................................3-14
Viewing Trip Information - Mark VI...........................................................................................3-20
Web-Based Displays - Mark IV, Mark V, Mark V LM, and Mark VI....................................................3-25
Accessing the Web-Based Displays.............................................................................................3-25
Historical Alarm and Event Report..............................................................................................3-26
GEH-6126C Vol I HMI Operators Guide
Contents i
Hold List (Steam Applications) - Mark V and Mark VI..........................................................................3-31

Hold List Rules ............................................................................................................................3-32
Demand Display - Mark IV, Mark V, and Mark V LM ..........................................................................3-33
Starting Demand Display .............................................................................................................3-33
Demand Display Menu Window..................................................................................................3-35
Using Demand Display ................................................................................................................3-39
Logic Forcing Display - Mark V and Mark V LM ..................................................................................3-46
Starting the Logic Forcing Display ..............................................................................................3-46
Opening, Creating, Modifying and Saving Logic Forcing Displays ............................................3-49
Using the Logic Forcing Display Program...................................................................................3-50
Forced Variables - Mark VI.....................................................................................................................3-53
Starting toolbox............................................................................................................................3-53
Using Finder to Locate a Variable to Force .................................................................................3-54
Locating Forced Variables ...........................................................................................................3-56
Forced Variables using Control System Toolbox.........................................................................3-57
Toolbox Privilege Level Functions - Mark VI ........................................................................................3-58
Appendix A HMI Function Reference
A-1
HMI Functions for GE Turbine Controllers .............................................................................................A-1

CIMPLICITY HMI Supported Functions ................................................................................................A-4
Appendix B Alarm Overview
B-1
Introduction .............................................................................................................................................. B-1

Hold List Alarms (Steam Turbine Only) .................................................................................................. B-1
Process Alarms ......................................................................................................................................... B-2
Process (and Hold) Alarm Data Flow ........................................................................................... B-2
Diagnostic Alarms .................................................................................................................................... B-3
Glossary of Terms
Index
ii Contents
G-1
I-1
CHAPTER 1
Chapter 1 Overview
Introduction
The Human-Machine Interface (HMI) for SPEEDTRONIC turbine control is an
operator interface for real-time control of power-plant processes and equipment. It
runs on a computer-based workstation using a Microsoft Windows Operating

System. The HMI provides operator display and control for the Mark* IV, Mark* V,
Mark* V LM and Mark* VI turbine controllers.
This document, Volume I, covers HMI operation. It is written as a guide to help 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. Volume II covers HMI maintenance features.
HMI Overview
The Human-Machine Interface (HMI) for SPEEDTRONIC turbine control is a
operator interface for real-time control of power-plant processes and equipment. It
runs on a pc-based workstation using client-server architecture. The HMI provides
operator display and control for the Mark IV, Mark V, Mark V LM, and Mark VI
turbine controllers.
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 HMI uses many different software packages to perform its functions. The
primary package used for the operator interface is CIMPLICITY HMI.
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 levels).
Issue commands to the selected turbine or driven device (for example: Start,
Stop, Cooldown On, Auto, and Raise/Lower Output).
Note CIMPLICITY HMI is a product of GE Fanuc Automation.
Product Features
The HMI contains a number of product features important for power plant control:
Dynamic graphics
Alarm displays
Process variable trending
HMI access security
Maintenance functions such as logic forcing and user-defined point displays
Chapter 1 Overview 1-1
HMI Components
The turbine control HMI consists of the following functional components (Refer to
figure Data Flow between HMI Components):
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 is not used to configure the turbine control.
An HMI Server connects to the controllers to retrieve and display realtime data. It optionally makes this information available on the Plant
Data Highway. HMI Servers typically also provide the
programming toolsets for turbine controllers.
An HMI Viewer 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. The HMI
Viewer gets its real-time data over the Plant Data Highway from an
HMI Server.
Note GFK-1180 provides a detailed description of the capabilities of the

CIMPLICITY product.
Turbine Control Interface (TCI) is a software package used to communicate

with Mark IV and Mark V controllers to retrieve real-time information and
alarms. It also provides the programming toolset for the Mark V controllers.
Specialized displays are included for specialty functions such as logic forcing
and displaying high-speed data. TCI performs the following functions for the
turbine controllers:
Mark IV: Provides real-time interface for data and alarms
Mark V: Provides real-time interface for data and alarms, specialized

displays, and the programming toolset to configure a Mark V.
Mark VI: Provides real-time interface for alarms.
TCIMB (TCI/CIMPLICITY Bridge, previously called CIMB or CIMBridge) is

an interface between the CIMPLICITY and TCI, as follows:
Enables CIMPLICITY to collect data and alarms from controllers

supported by TCI.
Forwards setpoint and alarm commands from CIMPLICITY to TCI for

controllers supported by TCI.
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, which provide the HMI with controller real-time data. Access to the
database is required when configuring the system, but is not required while
running.
Depending on the size of the system, these elements can be combined into a single
computer, or distributed in multiple units. The modular nature of the HMI allows
units to be expanded incrementally as system needs change.
1-2 Chapter 1 Overview
CIMPLICITY
TCI
Alarm
Queue
Point Data
Alarm
Manager
int
Po
ar
Al
Alarms
s
m
External
Alarm
Manager
Alarm
Queue
Device
Collector
Point Data
Mark V
RP
Devices
Point
Database
Point
Manager
TCIMB
Data
Dictionary
Devcom
(EGD...)
Devices
Data Flow between HMI Components
Graphic Displays
The HMI uses the graphics and alarm features of the CIMPLICITY software to
provide an operator interface integrating many different types of controllers. The
graphical displays offer representations of equipment in real-time.
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. Normal viewing allows the displayed data to be updated
once per second, and special tools allow collection and storage of data at faster rates.
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.
Note Screens are developed using preconfigured graphic building blocks that
provide commonality to different plant applications that use the HMI.
GEH-6126BVol
VolI IHMI
HMIOperators
OperatorsGuide
Guide
GEH-6126C
The following figure Sample HMI Display for Gas Turbine and Generator Data
displays a typical screen using graphics to display real-time turbine data.
Click buttons and other

animated objects to
open additional
displays or objects.
Click to open an
Alarm display which
will display all alarms.
Select an alarm listed on the

alarm display, then click the
button for the desired action.
Alarms
Sample HMI Display for Gas Turbine and Generator Data
The graphic system performs key HMI functions and provides the operator with realtime process visualization and control using the following:
CimEdit is an object-oriented program that creates and edits the user graphic
screen displays
CimView is the HMI program that displays the process information in graphical
formats. Screens have a 1-second refresh rate
Note GFK-1396 provides a detailed description of the CimEdit and CimView
applications.
CIMPLICITY 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.
The point control panel provides a listing of points in the system with realtime values.
The basic control engine allows users to run scripts in response to system
events. The program editor is used to create Visual Basic for Applications
scripts.
Communications
The following figure displays the networks used by the HMI to communicate within
a SPEEDTRONIC turbine control system.
Mark VI Plant Data Highway (Ethernet)
Data
Data
HMI Server # 1
HMI
Viewer
HMI Server # 2
Historian
TR
Mark VI Unit Data Highway (Ethernet)
Mark IV Control System Freeway (CSF)

Mark V Stagelink
Mark VI
Turbine
Control
I/O
Mark IV
Turbine
Control
I/O
Mark V
Turbine
Control
I/O
Example of a Turbine Control Communications Network
Note Refer to GEH-6126 Vol. II and individual controller documents for more detail
about the networks and protocol used for HMI communication.
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
The HMI supports a Windows-based Historian computer, which collects and stores
data from the control units for later analysis. OSI Software, Inc.s PI-ProcessBook
provides historical and real-time trending of all process data, and can run in the
Historian and/or HMI Viewer. The HMI communicates with the Historian through
the Ethernet-based Plant Data Highway (PDH) and through RS-232C lines.
Note Document GEH-6422 provides information about the Historian.
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 any computer on the
network that includes the HMI. 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 needs of the customer 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 can help in understanding HMI operation:
HMI-related documents:
GEH-6126 Volume II, HMI for SPEEDTRONIC Turbine Control, Application

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-100517, Modbus for HMI Applications
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

Note GEH-#### is the document identification number.
How to find the 3V number

The GE requisition or shop order number is referred to as the 3V number. These
numbers should be recorded and retained for future reference. The GE job sticker
with this number is located on the equipment such as the controller cabinet and the
HMI computers. Refer to figure Sample of GE Job Sticker.
This 3V number is required for support issues.
Sample 3V
job number
Sample of GE Job Sticker
CHAPTER 2
Chapter 2 Quick-Start Procedures

Introduction
A facility typically receives the HMI pre-loaded with all the programs and
customized software required for the customers application. It is configured during
installation to automatically log on and open to the main operator display 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.
Starting Up the HMI

To start up the HMI and open your application
1
Power up the computer if it is off. If Auto Log On is enabled the computer

should start the CIMPLICITY application CimView and its associated main
operation display automatically. If a Log On dialog box appears, type in Oper
in the User Name field (User names are not case sensitive) and its associated
password (default is no password) in the Password field.
If the computer is already running, press the three keys Ctrl+Alt+Delete all at
once to bring up the Log On dialog box to change the User to Oper.
If the main operation display does not start automatically, double-click the
desktop icon, typically Unit_Control.cim.
When the computer starts up, it starts all CIMPLICITY programs (Refer to figure
Typical Services Starting Display, below) and displays the main operation display
(Refer to figure Example of a Typical HMI Display).
Note GFK-1180 describes CimView in detail for the Mark V.
Note The HMI displays for the user's system are CimView displays (*.cim files),
which can open before CIMPLICITY finishes loading. If at first the display is not
animated or setpoints fail, wait a few minutes for the startup to complete before
beginning operation. During the startup process do not click any Cancel or Close
buttons.
Chapter 2 Quick-Start Procedures 2-1
Do not click
Close button
as it may
cancel the
complete
loading of
essential
services
before the
HMI starts.
Click to manually start HMI

if it does not start
automatically.
Typical Services Starting Display
Click buttons
and other
animated objects
to open
additional
displays or
objects.
Click to open
an Alarm
display which
will display all
alarms.
Select an alarm listed on the
alarm display, then click the
button for the desired action.
Alarms
Example of a Typical HMI Display
2-2 Chapter 2 Quick-Start Procedures
Example of a Typical Alarm Display
Other HMI Displays

Note The following HMI displays are not intended to be a guide to operating a
turbine. It is not a comprehensive list. Only typical displays are listed.
Lockout Function Master Reset - Mark IV, Mark V,

Mark V LM and Mark VI
The Master Reset does not reset diagnostic alarms. It typically is performed after a
turbine trip and all trip causes understood and corrected.
Master Reset Dialog

Box
Process alarm that has

returned to normal state.
Master Reset
button
Example of Master Reset
The Master Reset clears any latched process alarms that have returned to a normal
condition. The operator can also remove an alarm from the alarm queue by
Selecting the alarm by clicking on it.
Clicking the Ack button.
Trip Diagram Display - Mark IV, Mark V, Mark V LM

and Mark VI
The Trip Diagram display enables operators and maintenance personnel to determine
the causes of a turbine trip. The trip causes will remain displayed until a Master
Reset is performed. A Master Reset does not cancel any problem that is not
corrected.
Examples of
causes of a trip.
Click Gen
Capability
button to
open the
Reactive
Capability
window.
Not all causes for a trip will

appear on this display.
Typical Trip Diagram Display
Note Trips are displayed in RED. Some signals are not latched. The operator must
check the trip history for an accurate chain of events leading to any trips that appear
on the display. Refer to Viewing the Trip History in this chapter for more
information.
Lockout Function Diagnostic Reset - Mark V,

The Diagnostic Reset function does not reset process alarms.
Sycronization
display
Startup Trend
display
Diagnostic
Reset button
Diagnostic Reset dialog
box
Diagnostic alarm example
Example of Diagnostic Reset Function
The Diagnostic Reset clears any latched diagnostic alarms that have returned to a
normal condition. The operator can also remove an alarm from the alarm queue by
Start Checks Display - Mark V, Mark V LM and

Mark VI
The Start Checks display presents the turbine conditions that prevent the operator
from starting the turbine.
First select
Aux then
Start Check
Signals
which will
inhibit the
start of the
turbine.
Turbine start status
Example of a Typical Start Check Display
Note Signals in the proper state to permit a start are displayed in GREEN. Signals
which are RED inhibit start requests.
The Diagnostic Reset clears any latched diagnostic alarms that have returned to a
normal condition. The operator can also remove an alarm from the alarm queue by
Alarm Setup - Mark IV, Mark V, Mark V LM and

Mark VI
There can be many non-critical alarms displayed. The alarm list can be filtered so
that only a portion of the alarms is displayed. For example the operator may select
only process alarms to be displayed. This does not affect or change any alarms that
are not displayed. By selecting <<UNFILTERED>> the operator can display all
alarms. The alarm filters are configured using CIMPLICITY. Refer to Chapter 3 for
more information.
Previously
defined
CIMPLICITY
alarm filters.
Alarm Setups
dialog box.
Setup button
Example of a Typical Alarm Setups Dialog Box
The Alarm Setups dialog box is used to select alarms to be displayed based on
filtering criteria defined using CIMPLICITY.
Click Setup button.
Select filter.
Click Load.
Click Done to apply the filter to the alarm queue.
Turbine Startup Trend Display - Mark IV, Mark V,

Clicking on the Startup Trend button (Refer to figure Example of Diagnostic Reset
Function) opens a new window displaying the pre-defined Startup Trend display.
Slider to
select a time
for process
value to be
displayed.
Process
values
Options buttons
add/remove signals
from the display.
Time frame for

display
information
Typical Startup Trend Display
The Turbine Startup Trend display is available to the operators to monitor critical
turbine parameters during the startup phase of the turbine.
Click Startup Trend (Refer to figure Example of Diagnostic Reset Function

for the location of this control).
Select Options.
Synchronization Display - Mark IV, Mark V,

Clicking on the Synch button (Refer to figure Example of Diagnostic Reset
Function) opens the Synch display. Refer to figure Typical Mark V Auto
Synchronization Display.
Auto synch
permissives
Synch Mode
command
buttons.
Typical Mark V Auto Synchronization Display
Refer to Optional HMI Displays, Manual Synchronizing Display, in this chapter for
more information.
Optional HMI Displays

Note The following HMI displays are not intended to be a guide to operating a
turbine. The HMI displays are optional add-ons to CIMPLICITY. Only common
optional displays are included.
Reactive Capability Display - Mark IV, Mark V,

The Reactive Capability Display is a real-time graphic that displays the turbine
generator's current MW and MVAR operating point (Refer to figure Example of
Reactive Capability Display). The plot displays three lines of generator capability as
a function of generator coolant temperature or hydrogen pressure.
The operator can use this display to check how close the generator is operating to its
thermal limits. To prevent the generator from overheating, the current operating
point must be kept within the dynamic envelope displayed for the current conditions.
Note The ratings curves are different for each application. They are displayed as an
example only and should not be used unless they match the generator ratings.
Displaying the wrong curves can cause operation outside the machines rated limits.
To get generator capability curves

Click Gen Capability
Three static curves represent the thermal limits of the
generator at three discrete operating points. The
curves are plotted at constant generator hydrogen
pressure or constant ambient temperature, depending
on the application.
Red dot
represents the
current
generator
operating
point. It
moves as the
operating
point
changes.
Manual Synchronizing Display

To bring a generator online with a power grid, the speed (frequency) and phase angle
of the generators ac waveform must match that of the power grid. The preferred
method is to use the turbine controllers auto-synchronizing function.
Manual Synchronizing Display Mark V and Mark V LM

Mark V and Mark V LM For Mark V and V LM, all data in the object is updated
at 16 Hz. The Manual Synchronizing Display is run only from a HMI server. It must
run on a server due to its fast update rate.
If the Manual Synchronization option is enabled then both Automatic and
Manual Synchronization share the same window for synchronization control.
Mark IV Refer to GEK-833810, Mark IV Speedtronic Gas Turbine Control System
For Heavy Duty Gas Turbines, for more information.
Mark V Refer to GEH-6195, Mark V Turbine Control, for more information
Mark V LM Refer to GEH-6353, Mark V LM Speedtronic Turbine Control, for
more information.
Manual Breaker
Close button.
Synch mode
change
confirmation
box
Synch Mode
command button
Manual synch
mode button
Auto synch
mode button
Example of Manual Synchronizing Display for Mark V
Breaker Close Command Button
Auto Synch Mode Confirmation Dialog Window
Manual Synchronizing Display Mark VI

For Mark VI, some data in the Manual Synchronizing display object is updated at
the frame rate of the controller. It must run on a server due to its fast update rate.
If the Manual Synchronization option is enabled then both Automatic and
Manual Synchronization share the same window for synchronization control.
Refer to GEH-6421 Mark VI Control System Guide, for more information.
Auto synch
permissives
Manual
Auto Sync Sync mode
mode button button.
Close Breaker button

visible when Manual Synch
mode is enabled.
Manual Synchronizing Display for Mark VI
Manual Synchronizing Confirmation Window
Auto Synchronizing Confirmation Window
Triggered Plot Display

Triggered Plot Display Mark V and Mark V LM
The Triggered Plot function provides a graph of high-speed turbine data. The graph
can be triggered by the change in state of a logic signal in the unit. Turbine
commands can be sent from this display, making it useful for initiating turbine tests
(such as valve travel tests).
Note The Triggered Plot function is run only from a HMI server. It is not run
from a HMI viewer. It uses high-speed data (up to frame rate) that is only available
from a HMI server.
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.
Example of Triggered Plot Display
Other Tools
The following sections provide instructions for performing HMI functions, such as
viewing sequencing information and performing logic forcing.
Viewing Sequencing Information

Viewing Sequencing Information - Mark IV
Mark IV has no sequencing information and no Dynamic Rung Display
capability in an HMI. Sequencing information is available on the panel-mounted
Operator Interface.
Note Refer to GEK-83865 and GEK-83866.
Viewing Sequencing Information - Mark V and Mark V LM

Both Mark V and Mark V LM use the Dynamic Rung display function for viewing
sequencing information. The Dynamic Rung display is a tool for stepping through
the control programming of a Mark V and Mark V LM controller. The Dynamic
Rung display is used for monitoring purposes only. The units control sequence
program cannot be altered using this program.
Note Refer to Chapter 3 for more information. Refer to Appendix A for functions
and applicability.
To open the Dynamic Rung Display for Mark V and Mark V LM
1
From the Start

menu, select Programs, Turbine Control
Maintenance, Unit T#, then Dynamic Rung Display.
Or
From the Windows desktop, click the Dynamic Rung Display icon.
Turbine Control
Maintenance
Unit T#
Programs
Utilities
list
Start
From the HMI click Tools to display Turbine Control Maintenance

utilities.
Click to open
Turbine Control
Maintenance
utilities
Dynamic
Rung display
Title bar
displays unit
name and
segment name
Header, which displays
the following data
Unit, site, and segment
name.
Rung number, and
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.
Viewing Sequencing Information - Mark VI

The Mark VI controller uses the Control System Toolbox application to display
all sequencing information.
Note Refer to GEH-6403 Toolbox for a Mark VI Turbine Controller and Chapter 3
for more information.
This feature is similar to the Dynamic Rung Display for the, Mark V and Mark V
LM.
When a controller is configured and downloaded, the live signal values can be
viewed. This section defines how to go online to monitor these values and certain
Summary Views when the controller is being monitored. These views are displayed
when the Tracking button is on and an item is selected in the Outline View.
Typically toolbox opens the controller at a privilege
level of 0, which permits Read Only functions in
toolbox. Operators typically run using this lowest
privilege level to prevent inadvertent changes to the
controller.
To open the Monitor Display for Mark VI

1
From the Start

menu, select Programs, GE Control System
Solutions, then Control System Toolbox.
Or
From the Windows desktop, click the Control System Toolbox
icon.
The toolbox Work Area displays an empty window until a device is created or
opened.
From the toolbox File menu, open a previously saved configuration file.
Click the Tracking
button. Select the item of interest in the

Click the Go Online/Offline
Outline View. It appears in the Summary View with live signal values.
Tracking
Button
button to turn tracking on.
Finder
Go On/
Offline
Signal
connections
Titlebar
Toolbar
Outline
View
Live signal values
displayed in
Summary View
Control Block
Privilege
Level
To find all occurrences of a control signal

1
Click the Finder button displayed in above figure.
Enter control signal in dialog box and click Find.
Click on a location in the Context window to go to that location of the signal in

the Summary View. A signal marked with an * is the location where the signal
is written.
Always on
top button
Goto
button
Unit
Signal
Asterisk (*)
denotes location
where signal is
written.
Location of each
occurrence of the
signal.
User Defined Displays - Mark IV, Mark V, and Mark V LM

CIMPLICITY HMI uses the Demand Display function for the Mark IV. This
function is also available on the panel-mounted Operator Interface. The Demand
Display function is used for Mark V and Mark V LM. Demand Display is a
program that offers flexible monitoring and control of a variety of datapoints and of
multiple units. It provides the following turbine control features:
Ability to monitor several datapoints at a time.
Ability to issue process commands to the unit(s).
Alterable displays that conform to the user needs.
Easy to configure displays for testing and special procedures.
Control of unit functions while monitoring associated data.
Ability to accommodate different types of units in one Demand Display.
Note Refer to Chapter 3 for more information

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.
To load an existing Demand Display file

1
From the Start

Maintenance, Unit T#, then Dynamic Rung Display.
From the File menu, select Open.
Select the desired file. If no existing file is specified, the default file
DEMAND01.DM2 (located in the F:\RUNTIME directory) loads.
To load a desired display
Double click on the display name in the display menu.
List of Demand
Displays.
Double click to
open.
Header
Legend
Data Area
Command Target Field
User Defined Displays - Mark VI

Mark VI uses toolbox and its Watch Windows function to provide user-defined
displays. The Watch Windows function creates a quick reference list containing
names, values, units, and description of the online values of signals. Each controller
document can contain multiple, uniquely named watch windows.
Note Refer to GEH-6403 Toolbox for a Mark VI Turbine Controller and Chapter 3
for more information.
Typically toolbox opens the controller at a privilege level of
0, which permits Read Only functions in toolbox. Operators
typically run using this lowest privilege level to prevent
inadvertent changes to the controller.
To open a Watch Window
From the toolbox toolbar, click View and select Watch Windows. The Select
Watch Window dialog box displays.
On / Offline Must be online
to view values.
Select View
Select
Watch
Windows
Verify these fields are green or

incorrect data may be
presented.
To open a Watch Window

From Select Watch Window dialog box, click an existing Watch Window
and click View.
All Watch
Window
names are
listed here.
Click a name
to highlight or
double click
to open.
Click to
View
highlighted
Watch
Window
Note Refer to Chapter 3 for more information.
Click a column header

to change the order of
the headings
Signal
User-added
comment.
Note It is possible to minimize any watch window by clicking the minimize symbol
in the upper right hand part of the dialog.
Viewing Trip Information

Viewing Trip Information - Mark IV
Mark IV has no trip information display capability in an HMI. This information is
available from the panel-mounted Operator Interface.
Viewing Trip Information - Mark V and Mark V LM

Trip information is automatically gathered by the HMI from the controller. The last
ten trips are stored on the HMI and can be viewed by using the Trip Log Viewer.
The information about the last trip can be manually uploaded at any time, or the
current accumulated data can be uploaded even without a trip.
Mark V trip history information about the last trip is stored in the controller, and is
lost if the controller is reset or rebooted. The HMI runs the automatic collection scan
typically every five minutes, but the trip information can be uploaded manually
before the controller is reset or rebooted.
Mark V LM trip history information is stored in non-volatile memory and is not lost
if the controller is reset or rebooted.
Viewing Automatically Collected Trip Logs
The Trip Log Viewer is used to view the trip log data. The user selects a valid unit
and chooses a file from the list presented. The trips are identified by their date and
time stamps. The latest trips are listed at the top of the list. After selecting the trip to
be viewed, the results are displayed in a Notepad window. The data is organized
according to pre-trip, post-trip, and alarm categories.
To view a Mark V or a Mark V LM Trip log
1

From the Start
Maintenance, Unit T#, then Trip Log Viewer.
From the Trip Log Viewer dialog box, select a unit from the Select Unit list
box.
From the Select a Previous Trip Log list, select a log to display by
highlighting it.
Click the Go To button to display the selected log file.
The selected log file displays in a Notepad window.
Select a unit
from this list.
List of Trip
Logs
arranged by
date and
time. The
latest trip is at
the top of the
list.
Select one to
view.
Viewing Manually Collected Trip Logs - Mark V and Mark V LM

If the Mark V controller is rebooted or restarted before the Trip Log data is uploaded
to the HMI the information can be lost. The unit is scanned every five minutes and if
there is a new trip the trip information is collected and saved as a new Trip Log by
the HMI.
The Mark V LM controller has non-volatile memory for the Trip Log queue and can
save the contents of the trip information across restarts or reboots of the controller.
The Trip History program allows the user to manually retrieve data from the unit
control and view it on the operator interface. The data can be collected and saved
even if the unit is running (has not tripped).
To view a Trip History for Mark V or Mark V LM
1

From the Start
Maintenance, Unit T#, then Trip History.
From the Trip History dialog box, select a unit from the Select Unit list.
Select
Unit
Click a Select Log option button for the type of historical data to be collected
from the controller. Only one button can be selected.
Click the Collect button to retrieve the data or click the Stop button to
cancel.
Trip History Data This function enables the operator to view the contents of the
Trip Log buffer immediately after a trip. This is useful when the HMI has not yet
uploaded the trip data from the controller. Refer to figure Typical Trip History.
Saved History Data This function enables the operator to view previously
uploaded and saved trip files. It opens the dialog box displayed in figure Example of
Triggered Plot Display. The list appears in chronological order with the latest at the
top of the list. Refer to figure Typical Saved History Data.
New Data This function enables the operator to take a snapshot of the accumulating
data while the unit is running (not tripped). This data can be used in comparison of
data gathered by a trip condition. Refer to figure Typical New History Data.
The resulting data is displayed in a Notepad window. The displayed data can be
saved using File: Save As menu option in Notepad and specifying a file name and
location.
Typical Trip History
Typical Saved History Data
Typical New History Data
Viewing Trip Information - Mark VI

The Mark VI controller uses the toolbox Data Historian to collect trip history data.
The Data Historian trip log is a combination of historical analog and discrete data.
This trip history data is viewed using the toolbox Trend Recorder. The trip log
signals are trended on a full-page screen. Alarms, events, and SOEs can also be
viewed in a list format displaying the logic state and time of the event.
Note Refer to Data Historian document GEI-100278 and Trend Recorder document
GEH-6408 for more information.
To view Trip Logs for Mark VI
1
From the Start

Or
From the Windows desktop, click the Control System Toolbox icon. The Control
System Toolbox opens.
From the toolbox File menu click Open to open a Trip Log file.
List of trip
logs
Select one of the trip log files to view.
Trip Logs identified

by unit, TripLog,
date and time.
Select Files of type All

Files (*.*) to populate
list with trip logs.
The Trip Log file opens in the Trend display.
Alarm Logger Control

Alarm Logger Control - Mark IV, Mark V, Mark V LM, and Mark VI
Several classes of turbine control actions can be automatically logged to a printer as
they occur. The HMIs Alarm Logger allows the operator to select any of the
following to output to the printer using the Alarm Logger Control dialog box.
Process alarms
Diagnostic alarms
Events
SOEs
Note This program is used with Mark IV, Mark V, Mark V LM, and Mark VI.
Refer to Chapter 3 for more information. Also Refer to GEH-6126 Vol II for
additional information.
To enable printing of alarms or events
From the Start

Maintenance, Unit T#, then Alarm Logger Control.
From the blank Alarm Logger Control box select the Unit and the Logger
Function.
Click OK.
Exits dialog box without saving

changes.
Process identification data
Saves selections and exits.

Cancels changes and exits.
Click on drop -down box arrow to

select unit (displayed in alpha numeric order).
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).
There are four functions (catagories)

of information that can be printed.
Click on a box to select. (Blank is
unselected; a check is selected.)
You can select each function on a
unit basis by selecting t he Unit and
Function(s), then the OK button.
Hold List Display (Steam Turbine Applications)

Hold List Display - Mark V and Mark VI
The Hold List display is required for the HMI to support large and medium steam
turbine controls on systems that have Automatic Turbine Startup (ATS).
Turbine operating conditions can cause a hold, which prevents ATS from setting the
speed or load target to a higher value. The Hold List display is accessed from a
navigation button on the CIMPLICITY screen.
Override hold
Cancel Override
hold
Typical Hold List
The CIMPLICITY Alarm Viewer displays the Hold List on the HMI, used to view
and override the current hold points.
Accessing the Web-Based Displays- Mark IV,

Mark V, Mark V LM, Mark VI
Accessing the Web-Based Displays
The HMI provides Web displays to view certain types of information. These Web
displays can be viewed locally, or from other computers connected to the HMI
through a network.
To access the Web displays from the HMI
1
menu, select Programs then the Web browser (usually

From the Start
Internet Explorer).
The Web browser displays.
If the page is not already configured as the Home page, in the address area,
type: http://localhost
The TCI Information Web Home page displays.
If the user is not at the HMI, but at another computer connected to the HMI by a
network, the Web displays can be accessed from the user's Web browser by typing:
http://<name of HMI Computer>
Web Historical Alarm and Event Exception Report

The Historical Alarm and Event Exception Report is a tool for analyzing exception
data stored on the HMI. An Exception occurs when one of the Process Alarm, Event,
or SOE points scanned by the controller changes state. A change in state is a point
pickup or dropout, or a change in the lockout state of a Process Alarm. This data is
reported to the HMI whenever a change occurs.
Historical Alarm and Event Exception Report
The report contains a header, which displays the users form input selections:
The Site name and the Unit names selected.
The Data types selected.
The Time format.
The Reports Start time and End time.
The Report type.
The output page contains the following data on each line:
The Time tag of the exception; this time comes from the controller.
The Unit name
The Status of the alarm or discrete event, indicated as follows:
1 indicates Pickup, and 0 indicates Dropout.
L indicates Lock, and U indicates Unlock.
The Point name for SOEs and Events, or processor and drop number for alarms.
The Data type indicated as follows:
ALM for Alarms
EVT for Events
SOE for Sequence of Events
Descriptive text
The report begins with the oldest data and has the newest data at the end. It can be
printed or saved as a text file from the browser window. To return to the query form,
use the Back button on the web browser.
Historical Alarm and Event Summary Report

The Historical Alarm and Event Summary Report is useful for analyzing the
frequency of exception data, especially nuisance alarms and edge conditions
(chattering SOEs). It is important to eliminate frequently occurring nuisance alarms
and edge conditions since they crowd up the exception report without adding useful
information, making it difficult to interpret the relevant data.
The report contains a header that displays the users form input selections:
The Site name and the Unit names selected.
The Data types selected.
The Time format
The reports Start time and End time.
The Report type
The report data is listed separately for each unit, and each data type within that unit.
Data is listed in the order of drop number for alarms and events, and in point number
order for events and SOEs. The output page contains the following data on each line
for process alarms:
The number of pickups and the number of dropouts.
The number of locks and the number of unlocks.
The Unit name
The processor
The drop number
Descriptive text
The output page contains the following data on each line for Events and SOEs:
The number of pickups and the number of dropouts.
The Unit name
The point name for SOEs and Events.
Descriptive text
It can be printed or saved as a text file from the browser window. To return to the
query form, use the Back button on the web browser.
Notes
CHAPTER 3
Chapter 3 Display and Control

(Command) Programs
Introduction
The HMI provides an online database for collecting and storing data from multiple
controllers. Refer to the controller documentation for description of the online
database.
The HMIs display-only programs allow the user to view turbine control data as
needed to monitor the system. User cannot, however, send control commands from
these displays.
The HMIs control (command) programs allow the user to send commands to the
turbine control.
Viewing Sequencing Information

The program running in the controller that defines its control actions is called its
sequencing. Sequencing typically consists of individual AND/OR logic operations
(called relay-ladder logic rungs) and calls to library functions that do analog or
complex operations (called primitive blocks or big blocks).
Some controllers (such as the Mark V) use separate programs in the HMI to edit the
sequencing and view the running sequencing. Other controllers (such as the Mark
VI) use the same program for both, with a privilege level controlling whether
changes to the sequencing are allowed. Both schemes allow the user to view the
current running sequencing overlaid with the real-time data that is driving that
sequencing. This is often useful for determining what conditions are driving a
particular condition, such as what is preventing the unit from being ready to start, or
what conditions are driving a particular alarm.
Viewing Sequencing Information - Mark IV

The HMI has no knowledge of the sequencing running in the Mark IV controller, and
as such has no sequencing display capability. Sequencing displays are available from
the Mark IV controller's panel-mounted Operator Interface. The HMI does provide a
Demand Display for Mark IV data, but it does not display the sequencing that
creates the values.
Chapter 3 Display and Control (Command) Programs 3-1
Viewing Sequencing Information - Mark V and

Mark V LM
The sequencing running in a Mark V controller is referred to as the Control
Sequence Program (CSP). The HMI's Dynamic Rung display is used to view
the CSP overlaid with the current values from the controller.
The Dynamic Rung display program includes:
Animation to display the current state of the control.
Relay Ladder Diagram (RLD) rungs.
Primitive and Big Block rungs. Some blocks include pictures of the sequencing
inside the block.
Starting a Demand display with all of the signal names and values from the
current rung.
A Find utility to display the locations and usage of all occurrences of a signal.
The following rules apply to the Dynamic Rung display:
Can only display control segments from a single unit at any time.
Can display multiple control segments from the given unit.
Cannot be used to alter the units CSP.

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 can 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. Any text editor can open these text files, but it should use the
MSLineDraw font distributed with the TCI product.
Dynamic Rung Display Windows

The Dynamic Rung display is a multiple document interface that allows the user to
open windows with different segments or the same segment. The user can also have
picture file windows and sub rung windows open.
Starting the Dynamic Rung Display

To Start the Dynamic Rung Display
From the Start
menu, select Turbine Control Maintenance, Unit T#,
then Dynamic Rung Display.
Or
From the Windows desktop, click the Dynamic Rung Display icon.
3-2 Chapter 3 Display and Control (Command) Programs
Click to select
Dynamic Rung
display.
Click one to select

unit. More than one
unit may be available
The Dynamic Rung display is started with no segments opened. To open a

segment:
From the File menu select Open.
Click File Open to

open Sequence
Segment Selection
dialog box.
Main Display
Select a Segment to view from the list.
Selected unit
Click OK to
load segment
into the
Dynamic Rung
Display.
Click to select a
Segment to
View.
Click button to Find

next instance of a
point name in the
current Segment.
Click button to Find All

instances of a
Pointname in all
Segments.
Navigation
Buttons
There are three major types of windows: mainframe, rung, and picture described
below:
Main Frame This is the outer container display that contains the rung and picture
file displays.
Rung Rung displays enable the user to view the control programming with live data.
User can view control rungs and blocks in a control sequence segment for a given
unit. This function includes a Find utility.
Picture Picture file windows display a picture representation of non-sequencing
BBLs, which are used to perform analog type calculations.
Main Frame Window

This is the display that opens when Dynamic Rung Display is clicked. Upon opening
this display is empty and its display title is Dynamic Rung Display. It can contain
multiple rung displays and picture displays.
Rung Windows
Rung displays (Refer to figure Example of a Dynamic Rung Display) 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 in Big Blocks.
Title bar
displays unit
name and
segment name
Header , which displays
the following data
Unit, site, and segment
name.
Rung number, and
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.
Example of a Dynamic Rung Display
The Rung Window can contain the following types of rungs:
RLD rungs
Primitive rungs
Big blocks
Comment rungs
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 (Refer to Table
Animation Rules for Both RLD and Primitive Rungs).
In both the Big Block and Comment Rung displays (where there is no
dynamic data) the timetag indicates the operator interface time when the rung
was displayed. The time does not update.
Note Header data is located in the upper left of the window.
Animation Rules for Both RLD and Primitive Rungs
Rung Component
Animation Rule
Normally Open Contacts
A green rectangle between the contacts displays continuity.

No rectangle between the contacts displays an open circuit.
A > symbol between the contacts means forced signals.
A rectangle outline around the > symbol highlights contacts that are forced
to the open condition.
Normally Closed Contacts
A slash through the contact indicates normally closed.

A green rectangle between the contacts displays continuity.
No rectangle between the contacts means an open circuit.
A rectangle outline around the > symbol highlights contacts that are forced
to the open condition. The slash through the contacts is broken in the middle to
highlight the > symbol.
Normal Coils
A coil circle filled with green is energized.

A coil circle filled with the window background color is de-energized.
A > symbol in the coil circle indicates forced signals.
Inverted Coils
A slash through the coil indicates that it is inverted.

A coil circle filled with green is energized.
A coil circle filled with the window background color is de-energized.
A > symbol in the coil circle indicates forced signals. The slash through the
contacts is broken in the middle to highlight the > symbol.
To update the Primitive Block Rung or Big Block Rung display to

display passed parameters
From the View menu, select either Picture File or Demand Display.
To update Big Block Rung display to display automatic parameters
From the View menu, select Demand Display.
Picture File Windows

Picture file windows (Refer to figure Dynamic Rung Displays Picture File Window)
are used to display the picture file and animation of the passed parameters for
Primitive and Big Blocks.
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.
Dynamic Rung Displays Picture File Window
The type of information in the header timetag depends on the type of display:
For a values display, the timetag provides the oldest piece of data being
displayed as a passed parameter. This includes the coil output for primitive
blocks. If it has not received data from the unit, the timetag display is No Valid
Data. If the oldest piece of data in the rung has not been updated for at least five
seconds, the timetag is highlighted.
For a static display, the header timetag provides the operator interface time of
when the rung was displayed.
Note Picture files cannot be opened directly by selecting Open from the File
menu.
To open a picture file
Open a sequencing segment.
Navigate to the rung that contains the applicable Primitive or Big Block.
From the View menu, select Picture File. A static picture file window displays
with the passed parameter point names represented as inputs and outputs to the
block.
From the View menu, select Values 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 View - Demand Display from the
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 File Close
from the menu.
Selecting a Sequencing Display Screen

Sequencing files contain the Control Sequence for each control segment. The
following rules apply when opening these files:
Selecting File - Open from the menu can only open a regular sequencing
segment from the files listed in the MSTR_SEQ.CFG.
Select a unit before opening a sequencing file.
You can open more than one segment at a time, or have multiple views of the same
segment.
Use the Window menu to change between views.
To navigate within a segment, use the Rung menu and toolbar buttons.
Using the Find All Function

The Dynamic Rung display includes a Find All function, which allows you to find
the occurrence of a particular signal anywhere within the control sequencing. This
function will find the following:
Signal names in RLD rungs
Signal names as passed parameters
Signal names as automatic parameters
Primitive names
Big Block names
Find All does not do the following:
Locate signals and block names used in sub rungs
Search Comment Rungs. The Find All Function is available only after a valid
unit has been selected.
To display results using the Find All function
From the Edit menu, select Find All.
In the dialog box, enter the desired signal or block name.
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 displays the segment name.
The third column displays the rung type.
The fourth column displays how the signal is used in the rung.
To open a segment from the Find All results with the desired rung
displayed
Double-click on the rung number,
-OrHighlight the rung number and click the Goto button.
Note The Find All Results dialog box remains open until you select the
Close button or change units.
Viewing Tabular Data

Viewing tabular data can be useful when studying the behavior of a BBL with
automatic parameters.
The Dynamic Rung Display allows you to launch the Demand Display to view RLD
elements, Big Block and Primitive passed parameters, and Big Block automatic
parameters. The data is in tabular form ( Refer to figure Viewing Tabular Data).
Note The Demand Display is a separate program outside of the Dynamic Rung
display.
Current rung
Tabular Data for the

current rung
Viewing Tabular Data
Viewing Sequencing Information - Mark VI

The sequencing running in a Mark VI controller is viewed using the Control
System Toolbox program. This is the same program used to create and edit the
sequencing, but changes to the sequencing are only allowed if the user is running at a
suitable privilege level. At the lowest privilege level the user can view the
sequencing overlaid with the current values from the controller.
Note Refer to Control System Toolbox for a Mark VI Turbine Controller for more
information.
When a controller is configured and downloaded, the live signal values can be
viewed. This section defines how to go online to monitor these values and certain
Summary Views when the controller is being monitored. These views are displayed
when the Tracking button is on and an item is selected in the Outline View.
Note Refer to Toolbox Documentation for more information.
Typically toolbox opens the controller at a privilege level
of 0, which permits Read Only functions. Operators
typically run using this lowest privilege level to prevent
inadvertent changes to the controller.
To open the Toolbox window for the Mark VI
1
From the Start

Or
icon.
opened.
From the File menu, select Open to open a previously saved configuration file.
Click the Tracking
From the Outline View, select the item of interest. It appears in the Summary
View with live signal values.
button to turn tracking on.

button.
Tracking Button
Finder button
Go On/
Offline
Toolbar
Summary
View
Outline
View
Signal Connections
Summary View
Privilege Level
See Mark VI Logic

Forcing for changing
signal values
Verify these fields

are green or incorrect
data may be
presented.
Live signal values
To find all occurrences of a control signal

1
From the Toolbox toolbar, click the Finder button.
From the Finder dialog box, type or select the control signal from the Text dropdown list and click Find.
From the Context window click on a signal location to go to that signal

location in the Summary View. A signal marked with an * is the location
where the signal is written.
Finder button will

hide the tabs.
Always On Top
pin. Clicking
outside the Finder
Window will close
it.
Tabs
Select Unit for

location of
signal.
Goto button will

go to the
highlighted
location.
Signal name
Asterisk (*)
denotes
location where
signal is
written.
Output View with

all locations of
the signal.
Finder button will

show/hide the tabs.
Always On
Top pin.
Clicking outside
the Finder
Window will not
close it.
Output View
with a list of all
locations of the
signal.
Location
where
signal is
written to.
Location of
signal in outline
view.
Click
To
If this pushpin is displayed, the Finder Window closes whenever the area outside the Finder
Window is clicked. Search information cleared from the Finder Window will be lost. Click the
pushpin to keep the Finder Window on top of the Device Window in toolbox. The button
changes to the button displayed below.
This pushpin is displayed when the pushpin (described previously) is clicked. The Finder
Window remains open when this button is displayed even when working in another toolbox
window.
The Goto button is enabled only after a signal location is highlighted in the Outline View by
clicking on the signal. If the Goto button is clicked, Finder goes to the signal location in the
toolbox project.
This button is not to be confused with the similar button on the toolbox toolbar. If this button is
clicked it hides the Finder Window tabs. If it is clicked again the tabs are displayed.
Viewing Trip Information

Trips are defined as the unplanned (usually not requested) shutdown of the turbine
while the unit is running. A normal shutdown is not considered a trip.
Viewing Trip Information - Mark IV

An HMI has no Mark IV trip information display capability. A Trip Display is
available from the panel-mounted Operator Interface.
Viewing Trip Information Mark V and Mark V LM

Trip information is automatically gathered by the HMI from the controller. The last
ten trips are stored on the HMI and can be viewed by using the Trip Log Viewer.
The information about the last trip can be manually uploaded at any time, or the
current accumulated data can be uploaded even without a trip. The information is
viewed using Trip History.
Mark V trip history information about the last trip is stored in the controller, and is
lost if the controller is reset or rebooted. The HMI runs the automatic collection scan
typically every five minutes, but the trip information can be uploaded manually
before the controller is reset or rebooted.
Mark V LM trip history information is stored in non-volatile memory and is not lost
if the controller is reset or rebooted.
Trip History
Manual trip log
collection.
Trip Log Viewer
Automatic trip log
collection.
Select
unit
Starting Trip History or Trip Log Viewer
Viewing Trip Log - Mark V and Mark V LM

A Mark V controller loses the trip history data stored in its memory if the unit
control is reset or rebooted. A Mark V LM controller keeps the data for the last trip if
a reset or reboot occurs. However, the Turbine Control Interface (TCI) includes a
Trip Log Collection utility, TRPFIL that automatically collects and stores the data as
a Trip Log file on the HMI. (Both the utility and HMI must be running during the
trip.)
The Trip Log file can be opened and viewed by the Trip Log Viewer function of
the HMI. Refer to figure Mark V and Mark V LM Trip Log Viewer Dialog Box.
Note Refer to GEH-6126 Volume II for information on the Trip Log Collection
utility.
Opening a Trip Log File - Mark V and Mark V LM

The Trip Log Viewer reads the previously saved trip text files stored on the HMI.
It determines the trip times associated with each file from the name of the file, which
is encoded with the trip date and time information. Viewer opens a viewer window
and displays a list of the trips arranged in chronological order. Any Trip Log can be
selected and displayed.
To view the trip log data

1
From the Trip Log Viewer dialog box, select a valid unit from the Select
Unit list box.
From the Select a Previous Trip Log, select a log to display by highlighting
it.
Click the Go To button to display the selected log (file) with data from that trip.
Click the Close button to exit.
Identifies location
Select the Unit
from the list
Select to view log

Select to exit
dialog box
Listed by Trip
Date and
Time stamp.
Logs of past
trip events.
Select to
display
The number of trips is set by the
Trip Log Collection utility. Default
is 10.
The most recent is listed at the
top. Additional trips overwrite the
oldest log.
To save the Trip Log information to prevent its loss by the Trip Log
Collection utility of storing only the last ten trips:
1
From the File menu, select Save As.
Type in a different or unique file name and click Save.

Note The Trip Log Collection utility stores the last 1 10 trips. After that, it
overwrites the oldest trip file with any new trip data. TRPFIL can be configured
for storing a different number of trips.
The files are stored in the C:\HMIDATA directory. The automatic collection
program manages the file names in the format YYYYMMDD_UU_TRx.CSV, as
follows:
YYYYMMDD_HHMMSS_UU_TRx.CSV
File extension (to allow Microsoft Excel
viewing and analysis)
TRP indicates that the file contains trip
information; TRQ indicates a normal
shutdown or an aborted startup
Unit name
Data and time of trip (Y = year; M = minute,
D = day, H = hour, S = second
Viewing Trip History - Mark V and Mark V LM

The Trip History buffer information can be manually read from the controller at any
time from the HMI. The feature is the Trip History program.
To Start the Trip History program
From the Start
then Trip History.
Or
From the Windows desktop, click the Trip History icon.
Trip History Dialog Box - Mark V and Mark V LM

The Trip History dialog box controls the collection of Trip History information
from the unit controller. There are three options from the dialog box:
Trip History Data, which is the current content of the Trip History buffers.
This typically viewed immediately after a trip and before the automatic Saved
History Data, which is the current contents of the Trip History buffers and is
the result of opening the New Data option. This permits rereading the Trip
History buffers with information collected by using the New Data feature.
New Data, which moves the current contents of the trip log queue to the Trip
History buffer. This overwrites any previous buffer information. To reread this
information use Saved History Data.
To view the Trip History information from the controller

1
From the Trip History dialog box, select a valid unit from the Select Unit list.
Select the type of historical data to be collected from the Select Log options.
Click the Collect button to collect the data or the Cancel button to stop it.
Note User can retrieve only one type of data at a time.
When the data collection completes successfully, the results display in a separate
window. A message box displays if the data retrieval fails or is stopped by a user
command.
Select the Unit

from the list.
Select the type of data to
be collected.
Trip History is saved when the turbine
trips. For Mark V LM unit controls, the data
is saved in the control even after the
control is reset.
Click to start data

collection.
Click to close the
Trip History dialog
box.
Saved Data is saved into the control memory

when the user collects New Data. It remains in
memory until it is overwritten by New Data or
until the control is reset.
New Data is saved to the control memory when the user
collects New Data. The data reflects the most recent
control data. The data remains in the control memory as
Saved Data until it is overwritten or until the control is
reset.
Note Collecting New Data overwrites the Saved History Data in the control. On
Mark V units, New Data overwrites the Trip History Data in the control.
Note Trip History data is lost in Mark V controllers if the unit control is reset before
the HMI has saved the previous trip data. The trip history data is preserved in the
controller memory over a unit control reset or reboot in Mark V LM units.
Trip History Data Results Window - Mark V and Mark V LM

When the manual data retrieval completes successfully, the program opens and
displays the results in a separate viewer window. The data is displayed in a fixed
pitch font (all characters have the same width), with word wrapping disabled and
space padding to align the data columns. The results displayed are stored in a readonly temporary file.
The Trip History Data contains the following information:
Post Trip List: three 1-second post trip records. These three records are filled
with data only when there has been an actual trip. Otherwise, they are blank.
10 Second List: ten 1-second records.
1-Minute List: five 10-second records.
10-Minute List: nine 1-minute records.
1-Hour List: five 10-minute records.
4-Hour List: four 1-hour records.
Last 60 Process Alarms.
Each record consists of the following fields:
Timetag
Value of data from 1 to 64 points from the CSDB.

Note Enumerated state variable data is displayed as numbers, not as text strings.
Header , identifies the

unit and location.
Up to 64 points can be
viewed. HIS_AGE is
always reserved as the
first point.
Post trip list
Three 1-sec
records.
10-sec. list
Ten 1-sec
records
1-min. list
Five 10-sec
records.
Not displayed: 10-minute list,

1-hour list, 4-hour list , and
last 60 Process Alarms.
Data is padded with spaces

for easier viewing.
Trip History Information from the Controller
To save the Trip History data displayed

1
From the File menu select Save As.
Select the directory and name for the .txt file.
Click the Save button.
Viewing Trip Information - Mark VI

The Mark VI controller uses the Data Historian, a toolbox program to collect and
view trip history data. The Historian trip log is a combination of historical analog
and discrete data. High-speed data is uploaded from the unit and merged with low
speed data collected in the HMI for the 24 hours preceding the event.
Note Refer to Data Historian document GEI-100278 and Trend Recorder document
GEH-6408 for more information.
Trip Log File Data

The Trip Log is a file which resides on an HMI and which can be viewed using the
Trend Recorder function of the GE Control System Solutions Toolbox. The
Trip Log contains data for a pre-defined group of control signal database points for a
24-hour period before the trip, and for a brief period (approximately 5 seconds) after
the trip. The Trip Log also contains alarms, events and SOEs.
The Trip Log file contains data at the various sample rates as displayed in Table,
below.
Trip Log Data Sample Rates
The last three rates are dependent on the Frame Period (scan rate) of the Mark VI
and the number of pre- and post-trigger samples of the CAPTURE buffers.
The control signal database points for which data are gathered are defined by the
points passed to the CAPTURE buffers in the @Trip_History module of the .m6b
Toolbox file for the turbine.
The Trip Log file also contains alarms that occurred during the trip log period
indicated by blue triangles on the time axis. (For the exact times of the alarm
annunciations, Refer to the Alarm Historian Exception Report.)
Each Trip Log file is stored in a directory named for the day (expressed in UTC time
format) the trip event occurred. Multiple Trip Log files are stored in that day's
directory if more than one trip event occurs per day. The Data Historian Service
on the HMI maintains the 30 most recent Trip Log files; older Trip Log files are
automatically deleted to conserve disk space. Older files can be manually relocated
to another location to prevent their deletion and loss.
Viewing Trip Log Files

To view Trip Logs for Mark VI
1
From the Start

Or
icon.
opened.
From the toolbox File menu, open a Trip Log file.
List of trip logs in

selected directory.
Directory
containing trip
logs.
Select one of the trip log files to view.
Each
directory
contains at
least one trip
on that date.
Directory name
represents trip date.
Multiple trips for

one day.
Select All Files (*.*)
Select file, then

click Open or
double-click
selected file.
How to View Trip Log Files

Trip Log files can be opened either by double-clicking on the file name (on an HMI
with Toolbox installed on it) or with the File-Open function of Toolbox.
A Trip Log file for a heavy-duty gas turbine-generator is displayed in figure Typical
Mark VI Trip Log File In Trend Window, below.
Note When a .dca file is opened using Trend Recorder, the filename displayed in the
Menu/Title Bar of the Trend Recorder window has a .trn filename extension.
Older versions of the Trend Recorder can display Trip Log data collection
analysis files with gaps between the data lines. These spaces are not actual gaps in
data, but result from the way different versions of the Trip Log interpolate between
low-speed data points.
Typical Mark VI Trip Log File In Trend Window
How to Save Trend Files

The Trend Displays are saved as trend files (.trn) instead of original Trip Log file
(.dca) so that the settings, such as signal scaling and hidden signals, are saved with
the file. The file can be renamed but keep the file extension of .trn. Refer to figure
Using Save As from the File Menu to Save As a Trend File.
Default file name to save a

trend file with user formatting.
The file name can be changed.
Leave default .trn file extension.
Using Save As from the File Menu to Save As a Trend File
All features of the Trend Recorder can be used to manipulate the data in a Trip
Log file (such as axis scaling, hide/show signals, Zoom In/Out). Passing the cursor
over the blue triangles at the bottom of the graph displays the text message of the
associated Process Alarm, Event, or SOE. A full list of the Alarms and Events is
available using the View-Events option. Refer to figure Typical Mark VI Alarms
and Events List.
Typical Mark VI Alarms and Events List
The Alarms and Events List can be exported to a CSV file for use with spreadsheet
programs such as Microsofts Excel. Refer to figure Export to CSV Command.
Export as CSV
file for use with
a spreadsheet
program such
as Excel.
Export to CSV Command
Web-Based Displays - Mark IV, Mark V, Mark V LM, and

Mark VI
Accessing the Web-Based Displays
The HMI includes web browser displays of real-time data, historical data and
diagnostic information. The web pages are view-only and cannot be used for unit
control. The Web displays can be viewed locally or from other computers connected
to the HMI through a network.
Note The HMI web pages can be accessed from other computers on the network.
To access the Web display menu from the HMI
1
From the Start

menu, select Programs then the Web browser (usually
Internet Explorer).
If the page is not already configured as the Home page, in the address area, type:
http://localhost
The TCI Information Web Home page displays. A menu of additional Web
displays can be selected by clicking on the menu item name.
If the user is not at the HMI, but at another computer connected to the HMI by a
network, the Web displays can be accessed from user's Web browser by typing:
http://<name of HMI Computer>
Home
page
Click on
item
to open the
Web display.
Historical Alarm and Event Report

The Historical Alarm and Event Exception Report is a tool for analyzing exception
data stored on the HMI. An Exception occurs when one of the Process Alarm, Event,
or SOE points scanned by the controller changes state. A change in state is a point
pickup or dropout, or a change in the lockout state of a Process Alarm. This data is
reported to the HMI whenever a change occurs.
The report may be customized for any combination of point type, unit name, time
range, and report type by using a query form.
Historical Alarm and Event Query Form
Fill out and submit the Historical alarm and Event Query Form to generate a report.
To access the query form
From the Historian Information display, single click Alarm and Event
Report. The Historical Alarm and Event Report Query form displays.
This form is automatically filled in for the user, and is set up to display the last
eight hours of Alarms, Events, and SOEs for all units.
To view the report
1
On the Historical Alarm and Event Report Query form, modify the
default query form fields as needed.
When the form is complete, click the Submit button. The Historical Alarm
and Event Exception Report displays.
The most common way to customize the report is to change the time range of
interest. The form is automatically filled in for the user, and is set up to display data
from the last eight hours. Report time ranges are specified by a Starting Time and
Elapsed Time, and whether the Elapsed Time is before or after the Starting Time.
The report contains the data within the user specified time range.
To customize the Time Range

1
Type the time in the Starting Time box in the following format
YYYY.MM.DD HH:MM:SS.sss, where:
YYYY is the year
MM is the month (1-12)
DD is the day of the month
HH is the hour (0-23)
MM is the minute (0-59)
SS is the second (0-59)
sss are the subseconds

Note The default time is the current time. Fields after the hour field are not
required.
Type a positive or negative sign in the Elapsed Time operator box as follows:
+ specifies After the Starting Time
- specifies Before the Starting Time (Default)
Type the elapsed time in the Elapsed Time, using the following format:
dd HH:MM:SS.sss, where:
dd is the number of days (0-99)
HH is the hour (0-23)
MM is the minute (0-59)
SS is the second (0-59)
sss are the subseconds

Note Fields after the Minutes field are not required. The Days field is
optional.
To select the Query/Report Times
From the Historical Alarm and Event Query form, use the radio buttons to
select the Time standard. The time used in the report can be one of two
standards:
Site Local Time (Default) Displays information in site local time that can
have the most meaning to the user.
UTC (Coordinated Universal Time) Displays information in UTC time that

can make analysis easier especially across time zones and Daylight Savings
Time changes.
To select the Unit IDs
From the Historical Alarm and Event Query form, check the units of
interest in the boxes. All units are selected as the default. The Unit IDs
displayed on the form are the Turbine Control units defined in the HMI that
supports Alarms, Events, and SOEs.
Process Alarms
Events
SOEs Sequence of Events (Contact Inputs)

To select the Report Type
From the Historical Alarm and Event Query form, select the Report
Type using the radio buttons. The following Report Types are available:
Exception Report (Default selection) The Exception Report is the most

commonly used. It contains each occurrence in chronological order with the
oldest at the top and the newest at the bottom.
Summary Report This report is useful for identifying points that are
occurring frequently, such as nuisance alarms or toggling points. The report
displays the number of occurrences and is broken down by Unit ID and Point
Type.
To submit the Form
From the Historical Alarm and Event Query form, click the Submit
button. The Historical Alarm and Event Report displays the requested data.
Note Clicking the Reset button sets the form fields back to the default settings.
Exception Report Format
The report contains a header, which displays the users form input selections:
Site Name
Unit Names(s) selected
Data Type(s) selected
Time Format
Reports Start Time
Reports End Time
Report Type
The output page contains the following data on each line:
Timetag of the exception This time comes from the unit control.
Unit Name
Status
1 indicates Pickup.
0 indicates Dropout.
L indicates Lock.
U indicates Unlock.
Point name for SOEs and Events, or processor and drop number for alarms.
Data Type
ALM for Alarms.
EVT for Events.
SOE for Sequence of Events.
Descriptive text
The report begins with the oldest data and has the newest data at the end. It can be
printed and/or saved as a text file from the browser window. To return to the query
use the Back button on the web browser.
Summary Report Format
Number of
dropouts for
logic signal.
Number
of pickups
for logic
signal.
The report contains a header, which displays the users form input elections:
Site Name
Unit Names(s) selected
Data Type(s) selected
Time Format
Reports Start Time
Reports End Time
Report Type
The report data is listed separately for each unit, and each data type within that unit.
Data is listed in the order of drop number for alarms and events, and in point number
order for events and SOEs.
The report contains the following data on each line for process alarms:
Number of pickups
Number of dropouts
Number of locks
Number of unlocks
Unit Name
Processor
Drop Number
Descriptive text
The report contains the following data on each line for Events and SOEs:
Number of pickups
Number of dropouts
Unit Name
Point name for SOEs and Events
Descriptive text
It can be printed and/or saved as a text file from the browser window. To return to
the query form, select the Back button on the web browser.
Hold List (Steam Applications) - Mark V and Mark VI

The Hold List is required for the HMI to support Mark V controllers on systems
that have Automatic Turbine Startup (ATS).
ATS is used to set speed control targets and valve positions based on various inputs
(such as steam temperatures and pressures, calculated valve stresses, turbine rotor
stresses, and turbine shell stresses, metal temperatures, speed and operating mode).
Turbine operating conditions can cause a hold, which prevents ATS from setting the
speed or load target to a higher value. In the HMI, the Hold List display enables the
user to view the current points on the Hold List and to override any or all hold
points, if desired. Overriding a hold allows the ATS to advance its operating points
as operating conditions permit.
Note This program is used with Mark V and Mark VI controllers.
Example of a Typical Hold List
The CIMPLICITY Alarm Viewer displays the Hold List on the HMI. There is
usually a separate CIMPLICITY Alarm Viewer for the Hold List to allow only the
holds from a given unit on the display. Holds are not usually displayed on a regular
alarm list.
Note Refer to Chapter 2 and Appendix B for more information on alarm displays.
Hold List Rules

The Hold List is maintained according to the following rules:
A point that is picked up is entered in the Hold List as (0 - > 1).
Unacknowledged entries have an N character in the ACK field.
Acknowledged entries have a Y character in the ACK field.
A hold point whose state is a picked-up (logic 1) displays the ALARM state.
A hold point whose state is a dropped-out (logic 0) displays the NORMAL state.
A point that has been acknowledged is removed from the Hold List display.
A picked up hold point can 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.
Demand Display - Mark IV, Mark V, and Mark V LM

Demand Display is a program that offers flexible monitoring and control of a
variety of data points and of multiple units. It provides the following turbine control
features:
Ability to monitor several data points at a time.
Ability to issue process commands to the unit(s).
Alterable displays that conform to the user needs.
Easy to configure displays for testing and special procedures.
Control of unit functions while monitoring associated data.
Ability to accommodate different types of units in one Demand Display.
Note Mark IV also uses the Operator Interface; Refer to GEK-83865 and GEK83866 for this function.
Note This program is used on Mark IV, Mark V, and Mark V LM controllers.
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.
This chapter includes instructions using Demand Display with Mark V, and V LM
controllers. For Mark VI controllers, use the toolbox.
Starting Demand Display

To start the Demand Display:
1
From the Start

then Demand Display.
Or
From the Windows desktop, click the Demand Display icon.
From the HMI CIMPLICITY display, click the Demand button from the HMI
CIMPLICITY display.
Demand Display automatically opens a default file DEMAND01.DM2, which

contains sets of displays for multiple units. The user selects a display from that set.
The program provides two types of working windows:
A Menu window containing a list (menu) of all of the displays available in the
selected Demand Display file.
A Data window containing live data and commands.

Note DEMAND01.DM2 is located in the F:\RUNTIME directory.
Unit Selection after Demand

Data Display is opened.
Click to
open
Demand
Data
Display.
Click button to toggle

between Display Menu and
previously opened Demand
Display.
Double-click
a Demand
Display from
the list to
open it.
Value field
with live
values
Units field with
engineering
units
Point Name
field
Command
Target field
with
command
buttons
Demand Display Menu Window

This window provides a list of available displays. Selecting a display causes it to
replace the menu in the window.
Menu selections
include both standard
Windows and
program-specific
The title bar displays the filename currently
commands.
in the Demand Display.
The toolbar provides
quick access to menu
commands. Holding the
cursor over the button
displays the button
function.
Header containing
identification
data.
Display Menu
containing a list of
available
displays.
Example of Display Menu List
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. The user can select an item with this cursor to open the items Help
information.
Demand Display Data Window

This window provides real time data and commands.
There are two types of data windows:
Point List: These displays contain a user-defined list of points. The list of
points included can be edited and saved even as a new display.
Data Dictionary: These displays contain all points of a particular type. The
type of points can be edited, but not the list of points.
Header
Legend
Command
Target Field
Data Area
Example of Point List Display
Header
Legend
Data Area
Example of Data Dictionary Display (Displaying All Logic Points)
Both Demand Display windows are made up of three main regions:
The screen Header is non-scrolling process identification data. It contains the:
Unit name
Site name
Program name
Display screen name
Timetag (controller 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.
Note GE recommends the user keep the screen header visible at all times.
Although the header cannot scroll off the screen, you can toggle it on or off by
selecting Header from the View menu.
Note GE recommends the user keep the screen header visible at all times.
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, 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.
The Legend displays the non-scrolling column headers for the Data Area.
Although the legend cannot scroll off the screen, user can toggle it on or off by
selecting Legend from the View menu.
Note GE recommends the user keep the column headers visible at all times.
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 a list of point names, their values, and units.
This information is in a tabular format. (Refer to Data Area Description section
for more details.)
Any Command Targets defined are displayed on the right side of the window. (Refer
to Command Target Types section for more details.)
Data Area Description

Unlike the Header and Legend, the point names and command targets in the Data
Area scroll with the scroll bars. Demand Display updates only the visible points. The
following sections in the Data Area provide information or require input:
The Point Name field holds the control signal point name (or synonym) of
valid unit database points. Entering the point name causes Demand Display to
use the currently selected units data, which is the unit listed in the Header.
Entering the unit name with a colon before the point name, as in
T2:{Pointname}, displays data from the requested unit. The Point Name
field is 15 characters in length. Demand Display allows you to enter other text
into this field for commenting and separating sections of points. Invalid point
names are treated as text to allow for entering textual separations of the data.
The Value field contains point value information. This field updates once each
second, is right justified, and can contain up to 10 characters. If the value is
larger than 10 characters, 10 asterisks display. Enumerated state values display
across both the Value field and the Units field. The Demand Display program
centers the Enumerated state values across these fields and truncates them if
they are over 17 characters long. A blank Value field indicates either of 2
conditions:
The point information is invalid.
There is no data for the point in the Data Dictionary.
The Units field displays engineering units for valid point names exactly as
found in the Data Dictionary. This field is blank for invalid point names, and
indicates the engineering units for valid points. The Units field combines with
the Value field to display the text for enumerated points.
The Command Target field is to the right of the Units field. It contains Unit
Command Targets (buttons) for sending control commands to the unit.
Command Target Types

Command Targets (Refer to figure Example of Point List Display) are essentially
buttons that user select to perform the action identified on its label. There are three
Command Target types:
Immediate Action type sends a command to the control immediately without

requiring further action. They typically perform an incremental change to the
control, such as Raise or Lower.
Note Immediate Action targets use black text on a red background. The text
turns yellow if the feedback logic is supplied and met.
Note Feedback logic is optional.
Arm/Execute type typically performs changes to the control state, such as

Start and Stop. When selected, it opens the Execute Command dialog box
to confirm execution. Selecting OK sends the command to the unit. Selecting
Cancel cancels the command. Closing the dialog box cancels the command.
Refer to figure Example of Arm/Execute Dialog Box.
Note Arm/Execute targets use black text on a green background. The text turns
yellow if the feedback logic is supplied and met.
Note Requiring command confirmation before sending them to the unit helps
prevent execution of false commands.
Closing the dialog box

cancels the command.
Sends the command to

the unit.
Cancels the command and

closes box.
Example of Arm/Execute Dialog Box
Analog Setpoint type changes the setpoint value of the specified control. It
does not use feedback logic. When selected, a Change Setpoint dialog box
(Refer to figure Example of Change Setpoint Dialog Box) opens, requesting the
new value for the control signal. Closing the dialog box cancels the command.
Note Analog Setpoint targets use black text on a gray background.
Note Speed or Temperature references are examples of control signals.
Enter new value.
Uses the current

display engineering
units.
Sends new value
to unit.
Cancels command
and closes box.
Example of Change Setpoint Dialog Box
Using Demand Display

Each Demand Display file (*.DM2) contains a set of Demand Displays. These
binary files are loaded, edited, and saved by the Demand Display program - do not
edit these files directly. Demand Display files can be located anywhere but typically
are stored in F:\RUNTIME. When the Demand Display is opened it loads the
default file DEMAND01.DM2 (located in the F:\RUNTIME directory).
To load an existing .DM2 file from the Demand Display
1
Or click
Select the file from the directory that displays.

To create a new .DM2 file from the Demand Display
From the File menu select New.
Or click
A blank Demand Display Menu screen displays with the single menu item
Demand Display. This is an empty template that should be renamed after
modification.
Saving a 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 Any changes made to the file are lost if the displays are not saved before
exiting.
To save a Demand Display file
1
From the File menu select Save or Save As.
Save As displays the Save As dialog box, allowing user to select the directory
and a new file name.
Note Save Demand Display files anytime a Demand Display is saved or added.
If the user exits the Demand Display program before saving changes to the Menu or
Data screens, the program asks if the user wants to save the file. Select Yes to save
the file and No to exit the program without saving.
Note Saving a Demand Display to the set and saving the set to a file require
different steps. How to save a display to a set is described below.
Opening, Creating, Modifying, and Saving Displays

To open an existing display
1
From the list in Menu window select a data screen.
Either double-click on the selection or press Enter to open the screen.

To create a new display
From the Menu window, place the cursor at the point in the list where user want
to insert the new screen title.
From the Edit menu select Insert Line. A Display Definition dialog box
appears to configure the new display. Refer to the following section on To
modify the display. Be sure to update the title of the display.
To modify a display (title, type, options)
From the Menu window, place the cursor at line with the display name.
From the Edit menu select Modify Line. Or, from the Display menu select
Definition. The Display Definition dialog box displays.
Data screen
title
Selects the
display type.
Selects the point
types to display in a
Data Dictionary
display type.
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
display type is recommended to differentiate it from a Point List display
type.
In the Display Title text box, type a new name, if desired.
Use the Display Type options to change between a Point List type and a
Data Dictionary type.
Click OK to save the changes.
Save the display, as described below.

Note Figures Example Of Point List Display and Example Of Data Dictionary
Display (Displaying All Logic Points) provide samples of these types of Data
screens.
To save a display
1
From the Display menu select Save or Save As.
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.
If Save As is selected, the Display Definition dialog box opens; type a new
name in the Display Title text box.
From the Display menu select OK or Save As to save changes. Keep in mind
the following steps:
The option 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 the user does not enter a new Display Title, another Demand
Display screen with the same name is added to the bottom of the
Demand Display Menu. User should rename the edited Demand
Display screens if you keep the original.
This procedure saves the display to the set of displays, but not the
display set to a file. To save the display set to a file Refer to To Save a
Demand Display File.
If the user exits the Demand Display program before saving changes,
the program asks if the user wants to save changes before exiting.
Select Yes to save the changes in the *.DM2 file and No to exit
without saving.
To copy a display from one unit to another

1
From the Menu window, open the desired display.
From the Edit menu select Unit.
Select the new unit.
From the Display menu select Save.
From the File menu select Save or Save As to make this change permanent to
the Demand Display file (*.DM2).
Note At locations with duplicate or similar units, it can be useful to copy a
Demand Display from one unit to another and make any necessary
modifications.
Working with Point Names

To add a point name or line
1
On the Data display, click on the desired line to add the point name or line. The
cursor appears on the left edge of the line.
From the Edit menu select Insert Blank Line. This inserts a blank line at the
selected line.
Modify the new line using the following procedure.

Note Lines can be added, deleted, or modified in either Data display type, but
the changes are preserved only for a Point List type.
To modify a point name or line

1
On the Data display, click on the line.
From the Edit menu select Modify Line. The Modify Line dialog box
displays.
Enter the desired point name (or comment text) and click OK.
Remember to save both the display to the set and the set to the file to make the
changes permanent.
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.
To delete a point name or line

1
On the Data display, click on the line.
From the Edit menu select Delete Line. If the line corresponds to the first line
of a Command Target, the target deletes.
Remember to save both the display to the set and the set to the file to make the
changes permanent.
Working with Command Targets

Note Refer to the Command Target Types section in this chapter. Command targets
can be added in either Data display type, but the changes are preserved only for a
Point List type.
To add a Command Target
1
From the Target Window, select the line that corresponds to the Command
Target. There must be one blank line between targets in the Target Window.
From the Edit menu select Modify Line. The point name dialog box displays.
Enter the desired point name if adding to a blank line. Typically, the point name
on the line corresponding to the first line of the Command Target has direct
relevance to the button and its action.
Click the Define Command button. The Command Definition dialog box
displays. It contains fields to define a Command Target and its (optional)
feedback.
Enter values and selections into the Command Definition dialog box (Figure
Example of Command Definition Dialog Box provides descriptions):
Button text in Text Line 1 and Text Line 2, as needed.
Point name of the unit command in the Point Name field.
Button Type.
Unit command Value of the point.
Value Type.
Feedback Signal Pointname and Sense.
Confirm, check, or cancel as needed by selecting any of the following buttons on

the dialog box:
Check Form checks the command definition entries for consistency

and errors.
OK saves any changes and creates the target.
Help opens the help window for this dialog box.
Cancel stops all changes to the command definition.
Delete removes the Command Target.
To modify a Command Target

1
Click on the line containing the top line of the target.
Click the Define Command button. The Command Definition dialog box
displays.
Modify the definition as defined above using the procedure to add a Command
Target.
To delete a Command Target
Select the line containing the top line of the target.
Click Delete to remove the Command Target.

-Or-
Select the line containing the top line of the target.
From the Edit menu select Delete Line to delete both the point name and the
Command Target.
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 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.
Button 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 Pushbuttons value is the number of scans to hold the
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 button
types can use feedback signals. Analog Setpoint button
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.
Other Options
There are several other options available in the Demand Display program:
Selecting Edit - Set Font displays the Windows Font dialog box. Select the
font and color desired for the Demand Display screen. The selection applies to
all Demand Display screens, except for the Command Targets where the colors
are predefined.
Selecting Edit - Select Unit allows selection of 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. This option is not
available in single unit sites.
Selecting View - Menu toggles between the menu and the most recently viewed
Data screen. Toggling to the Menu display 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 display to the set. Selecting Yes saves the display, No toggles to
the Menu window without saving. Selecting View - Menu from menu returns
to the most recent display.
Logic Forcing Display - Mark V and Mark V LM

The Logic Forcing Display program can be used for monitoring and forcing a
logic point. For example, during maintenance or troubleshooting it may be necessary
to make the controller believe that a certain valve is in a particular position, as
indicated by a limit switch. A simple approach is to use the controller Logic Forcing
capability.
The Logic Forcing Display has the following features:
Ability to monitor multiple data points, both analog and logical.
Ability to change and maintain a logic state of the point (0 or 1) regardless of the
sequencing driving the point.
Ability to add comment text and blank lines.
Ability to alter displays to conform to user needs.
Ability to monitor points in other controllers.
Ability to create, save and reuse displays for testing and special uses.
Ability to continuously scan the controller and add forced logic points to the end
of the view list.
Note Mark IV uses the Operator Interface; Refer to GEK-83865 and GEK-83866 for
this function. Mark V and Mark V LM support this utility. Mark VI uses the toolbox.
Only qualified personnel knowledgeable about
turbine control and protection should use the Logic
Forcing functions. Improper use can adversely affect
the control and protective features of the control
system.
Note This feature may not be available to operator or maintenance personnel.
Starting the Logic Forcing Display

To Start the Logic Forcing Display
From the Start
then Logic Forcing Display.
Or
From the Windows desktop, click the Logic Forcing Display icon. The
Logic Forcing Display opens an empty display and starts scanning the
controller for forced logic points, adding the points to the display as they are
found.
Note Saving this display prompts the user for a new file name.
Select Logic
Forcing
Select Unit
File name
> represents forced

logic signals
Controller time
Header
Currently
selected
unit
Command target
areas
Pointname or
comment text
Current value
List view
Engineering units
A delay occurs before forced Logic signals appear on the

Logic Forcing Display screen. When opening a file, wait a
few moments for all of the forced signals to appear before
taking any action.
Logic Forcing Display Screen Window

The Logic Forcing Display screen is made up of three main regions, the Header, the
List View, and the Command Target area. Refer to figure Logic Forcing Display
Example.
The Header contains the unit name, site name, program title and time tag. The
Header is in a non-scrolling region and cannot scroll off the window. The menu
bar option View and the Header command toggles the Header on or off. The
Header contains valuable process information and it is recommended that it
remain visible at all times.
The Header time tag displays the controller time. 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 controller, the time tag displays No Valid Data. A highlighted
Header time tag indicates the oldest piece of data in the Data Area has not been
updated for five seconds.
The List View is composed of three columns, the Point Name, the Current
Value from each processor, and the Engineering Units.
The List View scrolls and each of the columns is adjustable in width. If the column
becomes too narrow to display all of the data, an ellipsis () appears on the right
side of the column. The Current Value field is updated once per second from each
controller processor. The time tag displayed in the Header reflects the time
tag of the oldest piece of data displayed. Only the points visible on the screen
are updated. There is no limit to the number of points that can be added to the point
list.
Unlike the Header, the information in the Data Area scrolls with the scroll bars. The
Logic Forcing Display updates only the visible points in the List View.
The Pointname field holds the Control Signal pointname (or synonym) of valid
unit database points. Entering the pointname causes the Logic Forcing Display
program to use the currently selected units data, which is the unit listed in the
Header.
Entering the pointname of a non-logic point results in the display of the voted value
instead of the value in the individual controllers. If a fully qualified point name is
entered (in the form unitname:pointname) voted values of points from a different
unit can be displayed (but not forced).
Text other than a pointname can be entered for commenting and separating sections
of points.
Each column in the Value field displays the value in a processor. If the pointname is
invalid or there is no data for the point in the Data Dictionary, this field remains
blank. Forced points appear with a > character preceding the value.
The Units field displays the Engineering units for valid pointnames. The text appears
exactly as entered in the scale code table file. This field is blank for invalid
pointnames, but indicates the units for valid points.
The Command Target area appears on the right side of the Logic Forcing
Display window. There are four Arm/Execute targets available for the Logic
Forcing function. These targets are for forcing Logic signals to a state of 1 or 0,
to unforce a single Logic signal, or to unforce all forced Logic signals.
Arm/Execute targets appear green with black text and require a confirmation
before sending the force or unforce signal to the controller.
Opening, Creating, Modifying and Saving Logic

Forcing Displays
Logic forcing display definitions can be saved and reloaded later.
To open an existing Logic Forcing Display
1
Select a file from the directory that displays.
The Open dialog box displays allowing for selection of the file to load. Selecting the
toolbar button with the picture of the open file also displays the Open dialog box.
Selecting a previously viewed file listed at the bottom of the File menu bar option
opens the file directly. If the specified file does not appear to be a Logic Forcing data
file, the user is prompted as to whether to continue loading the file or to exit the
operation without saving any changes made to the display.
whenever a Logic Forcing Display file is opened it adds all
Note Or click
forced logic points from the unit that has been selected.
To create a new display
From the File menu select New
A blank Logic Forcing display screen opens. This is an empty template that should
be renamed after modification. The Logic Forcing Display starts with no points listed
in the display. It scans the controller looking for forced signals and adds them to the
end of the display as they are found. Signals can be added to the display so that those
signals can also be monitored or forced.
Note Or click
to create a new Logic Forcing display.
To add a Pointname line

1
Select the line at the desired insertion point.
From the Edit menu select Insert Blank Line, or
Select the Insert Blank Line toolbar button.
To delete a Pointname line

1
Select the line to be deleted.
From the Edit menu select Delete Line, or
Select the Delete Line toolbar button.
To modify a Pointname line

1
Select the line to be modified.
From the Edit menu select Modify Line, or
Select the Modify Line toolbar button.
Type the new pointname or line in the highlighted pointname box.
The Logic Forcing Display program allows the entry of invalid pointnames to
accommodate adding textual information to the Logic Forcing Display screen. The
Value and Unit fields remain blank if an invalid pointname is entered.
Save the Logic forcing Display file to make the changes permanent.
To save the display to a file
1
From the File menu select Save to save back into the currently loaded file.
Select the toolbar button with the picture of a disk.
From the File menu select Save As to save as a different file. Be sure to
specify the desired directory and file name.
From the File menu select Save or Save As to save a new display (one not
loaded from a file). In both cases the File Save As dialog box appears with
the default file name of UNTITLED.TXT. The file name should be changed to
something meaningful before saving.
Using the Logic Forcing Display Program

Forcing and Unforcing Logic Signals
To force a logic signal
1
From the Logic Forcing Display program, position the cursor on the line
corresponding to the desired logic signal. Click on the pointname field to
select it and the pointname highlights.
Select one of the forcing Command targets on the right side of the screen to
arm the action, either Force To One or Force To Zero. The Execute
Command dialog box displays.
Click OK to force the signal. The force command is sent to the controller
forcing the logic signal. Signals remain forced until either an Unforce
command comes from the Logic Forcing Display program or until the controller
powers off.
When a command is selected, it opens the Execute Command dialog box to

confirm execution. Clicking OK sends the command to the unit. Clicking Cancel
cancels the command. Closing the dialog box cancels the command.
Note Requiring command confirmation before sending them to the unit helps
prevent execution of false commands.
Closing the dialog box

cancels the command.
Sends the command to

the unit.
Cancels the command and

closes box.
Clicking Cancel from the Execute Command dialog box cancels the forcing
command. The default is Cancel.
Signals remain forced until an unforce command comes

from the Logic Forcing Display program or until the
controller powers off. Forced signals can cause the
controller to function improperly if forgotten. Take care
to unforce all unnecessary signals before running the
turbine.
Return the logic signals to their normal state by either unforcing all of the forced
logic signals at once or by individually unforcing them.
To unforce a single logic signal
1
From the Logic Forcing Display, select the desired logic signal by clicking
on it. The line highlights.
Select the Unforce Single command target. The Execute Command dialog
box displays.
Click OK to unforce the signal, or click Cancel to leave the signal forced. The
default action is Cancel.
To unforce all of the forced logic signals
From the Logic Forcing Display, select the Unforce All command target.
The Execute Command dialog box displays.
Click OK to unforce all forced logic signals in the controller, or click Cancel to
cancel the unforcing command. The default action is Cancel.
Selecting UNFORCE ALL unforces all of the logic
signals forced in the controller, including any signals
forced from OTHER Logic Forcing Display screens.
Using the Command Targets

The Logic Forcing Display command targets are Arm/Execute targets requiring
confirmation of their action before performing the command.
To use the Command Targets
1
Select the Command Target. The Execute Command dialog box displays.
Click OK. The command executes. To cancel the command execution, select
Cancel.
Note This procedure for confirming a forcing action helps prevent executing false
commands.
Printing the Logic Forcing Display File

A printout can be made of the currently visible portion of the display. Data that is
scrolled off the display is not included in the printout.
To print the Logic Forcing Display screen
1
Click on the printer icon to immediately send the display to the default printer
using the default options, or
From the File menu select Print and chose the printer and options desired from
the Print dialog box.
Other Options
There are other options available in the Logic Forcing Display program. Selecting
the menu bar option Edit - Set Font command from the drop-down menu presents
the Windows Font dialog box. The Font dialog box allows for selecting the font
used for the Logic Forcing Display screen. The selection applies to the entire display
screen including the text defined in the Command Targets.
Selecting the menu bar option Edit - Select Unit command from the drop-down
menu allows for unit selections. In multiple unit sites, any unit can be monitored
from one Logic Forcing Display screen. Select Unit causes the Unit Selection
dialog box to appear. The currently selected unit is highlighted. The available units
are displayed in alphabetical order. Select the desired unit. This option is not
available in single unit sites.
Exiting the Logic Forcing Display Program

Selecting the menu bar option File - Exit from the menu exits the Logic Forcing
Display program. The Logic Forcing Display program requests whether to save
changes to any Logic Forcing Display file before exiting.
Forced Variables - Mark VI

Note This feature may not be available to operator or maintenance personnel. If the
user is not able to perform an operation described in this chapter, check the user's
privilege level (Refer to the section, Privilege Level Functions).
Starting toolbox
Mark VI uses the toolbox for forcing a signal. Refer to GEI-6403 Control System
Toolbox for Configuring a Mark VI Turbine Controller. The basic procedure is as
follows:
To start Toolbox
1

From the Start
Or
icon.
opened.
From the File menu, select Open to open the configuration file for the
controller of interest.
Click the Tracking button

unit (controller).
Verify that the Major and Minor Revisions match, otherwise the wrong signals
could be displayed or forced. Verify both status boxes are green.
to turn tracking on.

button to establish communications with the
Go On/ Offline
Live Signal Values displayed

in Summary View.
Click on Live
Signal Value
to be forced.
Click to
Change Live
Value.
Module
containing the
value to be
forced.
Current Privilege
Level.
Verify both status

boxes are green.
Using Finder to Locate a Variable to Force

Use the toolbox function, Finder, to locate the variable to force. This can be an
analog or logical variable.
Use View Finder from the menu to locate the variable to be forced. Refer to
Viewing Sequencing Information Mark VI for more information on using the
Finder function.
Double click on the variable to be changed in the Outline View. This can be
any location of the variable.
If the user does not have privilege level of 1 or higher the user is prompted to
change to the required privilege level.
Toolbox Privilege Dialog Box
Click Yes to bring up the Select Privilege Level dialog box. The user is
prompted to select a privilege level and enter its password.
Note Refer to GEH-6403 for more information on changing a privilege level.
The following changes can be made to live values.
Boolean Value
Use the dialog box below to modify a Boolean value.
Use this dialog box to

change or force the live value
of a Boolean signal. Forcing
the value keeps the
blockware from writing over
the forced value, whereas an
unforced value can be
overwritten in blockware.
Changing a Boolean Value
Numerical Value
The numerical value is modified with the dialog box below.
Use this dialog box to enter a
value to be sent to the controller.
These values cannot be forced,
so values that are written in
instruction blocks do not change
to the value being sent.
Current is the live

value of the signal.
Enter the Next
value and click
Send.
Click to decrement the

Current value by the
Delta amount and send
it to the controller.
Delta is the value to be

added or subtracted
from the current value.
Token is the logical address

of the signal.
Click to increment the Current

value by the Delta amount and
send it to the controller.
Changing a Numerical Value
Array Value
The dialog box below is used to modify the array value.
Click on the
element to
change.
Click
Modify
Changing a Value In an Array
Clicking Modify opens the Boolean or Numeric Send Value dialog display.
Refer to figure Changing a Value In an Array.
Locating Forced Variables

Using the Force Lists function displays a list of all forced signals and I/O points
that can be unforced if desired. A report can be generated and saved also.
To locate all forced signals in the controller
The Forced List can be generated with a Privilege Level of 0 and opens in readonly mode.
From the View menu select Force Lists. The Forced Lists report opens
displaying all variables that are forced.
Signals (tab)
that are forced.
I/O Points
(TAB) that
are forced.
Forced Lists
To remove forcing on one or more variables

Removing a force on a variable requires a privilege level of 1 or greater.
1
Select one or more variables from the forced list.
Click Remove to remove the forcing on the selected variables.
There is no confirmation dialog box. The command is sent immediately.

To go to where a forced variable is used
1
Select the desired forced variable.
Click Goto to display the results.
The Finder dialog box opens with a list of all occurrences of the signal. Refer to
Viewing Sequencing Information Mark VI for more information on using the
Finder function.
The list of signals does not update in real-time, to re-scan the unit for forced signals
click on Update. Click on Report to open a report window for saving or printing
the list of forced points.
Forced Variables using Control System Toolbox

The controller has a feature called Forced Variables. This allows the maintenance
technician using toolbox to set analog or logical variables to forced values. Variables
remain at the forced value until unforced. Both compute and input processing respect
forcing. Any applied forcing is preserved through power down or reboot of the
controller, because forced variables in the controller are saved in NOVRAM.
Logic Forcing is for offline software checkout and
troubleshooting and should only be used in conjunction
with proper lockout/tag out procedures. Forcing of
protective functions is never permissible for an
operating unit.
Toolbox Privilege Level Functions - Mark VI

The privilege/password system assigns different levels of access to the devices.
Passwords can be established for the different privilege levels, allowing the required
level of access for each job function. Each successive level allows all the functions
of the previous level.
Note Refer to the Control System Toolbox online help for more information.
To set a privilege level for the Mark VI toolbox
1
From the Options menu select Privilege.
The Select Privilege Level dialog box displays.
Select the requested privilege level and click OK. If a password has been
assigned for that level the user is asked to insert the password.
CHAPTER 4
Appendix A HMI Function Reference

HMI Functions for GE Turbine Controllers
GEs Turbine Control HMI functions are provided by the TCI, TCIMB, and GE
Turbine Control Systems Solutions CD. The following table lists these functions and
identifies their applicability in the SPEEDTRONIC turbine controllers. Functions are
provided through CIMPLICITY, unless otherwise noted.
HMI Function
Mark IV Mark V
Mark VLM
Mark VI Application Notes
Data and control

displays
Demand display
Toolbox graphics for Mark VI
Logic forcing
Toolbox function for Mark VI
Dynamic rung display
Pre-vote data display
TSM for Mark VI
Diagnostic counters
display
TSM for Mark VI
Control constants
display
Control constants
adjust display
Autocalibrate display
Trip history
Capture blocks for Mark VI
CIMPLICITY Addons
CIMPLICITY bridge
Signal manager
Toolbox HMI for Mark VI
External alarm
manager
Reactive capability
display
Manual synchronizing
display
Emissions analysis
Triggered plot
Unit
communications
Stagelink
Appendix A HMI Function Reference A-1
HMI Function
Mark IV Mark V
Mark VLM
CSF
Not available in some Mark IVs
MAMSP
TCI modbus master
EGD
Process alarms
Diagnostic alarms
Events
SOEs
Hold list
Controllers with steam ATS

only
Unit configuration
tools
Sequence editor
Sequence compiler
Sequence documenter
CSP Printer
Table compiler
Application code
downloads
Firmware downloader
Toolbox for Mark VI
Mark V make
Card identification
TSM for Mark VI
Alarm list
FMV ID
LDB configuration
tools
I/O configuration tool
Time
synchronizing
Timesync function
NTP for Mark VI
High resolution (IRIG)
Option
GPS
Option
NTP
Option
Other functions
Alarm printing
Alarm history
Trip history automatic
collection
Capture blocks + Data

historian for Mark VI
Normal data collection
A-2 Appendix A HMI Function Reference
HMI Function
Mark IV Mark V
High-speed data
collection
Mark VLM

Toolbox trend recorder for
Mark VI
Control constants
compare
Optional functions
TCI Modbus slave
TCI Modbus master
For external device interface
GSM
Power block control
Performance monitor
Simple cycle only
Web diagnostic
functions
Demand display
Logic forcing display
Alarm display
Control constants
display
HMI log files
ARCWHO utility
Diagnostic
programs
Product code file
verification
CIMPLICITY HMI Supported Functions

The turbine control HMI supports many functions of the CIMPLICITY HMI. The
following table lists and identifies these functions.
Do not load unsupported CIMPLICITY functions on
the HMI for SPEEDTRONIC Turbine controllers.
Although the CIMPLICITY HMI function listed below
runs on the HMI for SPEEDTRONIC Turbine
controllers, they are not necessarily supported by GE
Power Systems for use on the HMI. Please check with a
GE Power Systems representative for availability.
Options not listed as supported in the following table
have not been qualified.
Earliest supported version CIMPLICITY Function Supported Application notes
Action calendar
Calendar-based control
Alarm blocking
Alarm horn
3.2 SP7
Alarm viewer
Interactive ActiveX alarm

viewing object
3.2 SP7
Basic control engine
Visual Basic for applications

scripting language
Data logger
Data logging via ODBC
DDE server (CWSERV)

Dynamic measurement
systems
Dynamically switch between

English and metric units
Genius communication
from HMI
3.2 SP7
Historical data analyzer
Comprehensive data
summarization
Historical trends
Interactive ActiveX object for

viewing trend
HMI for CNC
Integration with GE Fanuc CNC

controllers
HMI Modbus master

Marquee
3.2 SP7
Display alarms and messages

to marquee devices
Modbus plus
communications
Modbus TCP/IP
communications
4.01 SP2
OPC client
Consult Salem, VA factory,

Turbine control application
engineering (540) 387-7388
4.01 SP2
OPC server
Consult Salem, VA factory,

Turbine control application
engineering (540) 387-7388
4.01 SP8
OpenProcess
Pending
Earliest supported version CIMPLICITY Function Supported Application notes

3.2 SP7
Pager
Send alarm information to

alpha-numeric pagers
PocketViewer
WinCE CimView
3.2 SP7
PointBridge
Allows CIMPLICITY server to

act as device to another server
4.01 SP2
Quick trends
Pop-up trends for any points on

a screen
3.2 SP7
Real-time trends
Interactive ActiveX object for

viewing trend
Recipes
Device-independent recipe
management
Report manager
Report generation and

management from process
Series 90 PLC fault

tables
View PLC faults
Server redundancy
Complete mission critical

redundancy support
SmartObjects
Reusable drag and drop graphic

and scripted objects
SPC
New features for SPC
System sentry
Constantly watches HMI and

system parameters
Tracker option
Track items through a

production facility
Web gateway
Send CIMPLICITY HMI data to

web pages
Web viewer
Send screens over web to

standard web browsers
XY plots
ActiveX object for plotting

multiple x-y data
3.2 SP7
4.01 SP2
3.2 SP7
3.2 SP7
Notes
CHAPTER 5
Appendix B Alarm Overview

Introduction
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.
The turbine controllers generate three types of alarms, which are viewed on the HMI
or toolbox: Process, Hold List, and Diagnostic (Refer to figure Three Types of
Alarms Generated by the Mark VI Controller).
HMI
Alarm
Display
HMI
Diagnostic
Display
Toolbox
UDH
Process &
<R>
Hold List
Controller
Alarms
I/O
<S>
Controller
<T>
Controller
Diagnostic
Alarms
I/O
I/O
Diagnostic
Alarm Bits
Three Types of Alarms Generated by the Mark VI Controller
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.
Hold List Alarms (Steam Turbine Only)

Hold List alarms are similar to process alarms with the additional feature that the
scanner drives a specified signal True whenever any Hold List signal is in the alarm
state (hold present). This signal is used to disable automatic turbine startup logic at
various stages in the sequencing. Operators can override a hold list signal so that the
sequencing can proceed even if the hold condition has not cleared.
Note Refer to the Hold List section in Chapter 3.
Appendix B Alarm Overview B-1
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 can be driven by
sequencing or they can 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
Process (and Hold) Alarm Data Flow

Process and Hold alarms are time stamped and stored in a local queue in the
controller. Changes representing alarms are time stamped and sent to the alarm
queue. Reports containing alarm information are assembled and sent over the UDH
to the CIMPLICITY HMIs. Here the alarms are again queued and prepared for
operator display by the Alarm Viewer.
Note The operator or the controller can take action based on process alarms.
Operator commands from the HMI, such as alarm Acknowledge, Reset, Lock, and
Unlock, are sent back over the UDH to the alarm queue. There they change the status
of the appropriate alarms. An alarm entry is removed from the controller queue when
its state has returned to normal and it has been acknowledged and reset (Refer to
figure Generating Process Alarms).
Hold alarms are managed in the same fashion but are stored on a separate queue.
Additionally, hold alarms cannot be locked but can be overridden.
B-2 Appendix B Alarm Overview
Mark VI Controller
Input
Signal 1
.
.
.
.
.
.
Input
Signal n
UDH
Alarm
Report
Alarm
Scanner
Alarm
Command
Alarm
Queue
Including
Time
Alarm Logic
Variable
Alarm ID
Mark VI HMI
Alarm
Receiver
Alarm
Viewer
Alarm Queue
Operator Commands
- Ack
- Reset
- Lock
- Unlock
- Override for Hold Lists
Generating Process Alarms
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
can be reset from the toolbox.
Appendix B Alarm Overview B-3
Notes
B-4 Appendix B Alarm Overview
Glossary of Terms
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 of Terms G-1
Atlanta Data Highway (ADH)

Ethernet communication network that connects an OSM to the GE remote services
network.
Balance of Plant (BOP)

Plant equipment other than the turbine that needs to be controlled.
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.
breaker (circuit breaker)

A switching device, capable of making, carrying, and breaking currents under normal
circuit conditions and also making, carrying for a specified time, and breaking
currents under specified abnormal conditions, such as those of short circuit
<C>
The Mark V 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
Computer-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.
G-2 Glossary of Terms
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 command prompt
windows, as opposed to a graphical user interface (GUI).
configure
Select specific options, either by editing disk files, or by setting the location of
hardware jumpers, or by loading software parameters into memory.
control system
Equipment that automatically adjusts the output voltage, frequency, MW, or reactive
power, as the case can 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.
Control System Solutions

Product software provided on a CD for a GE control system. This includes the
Control System Toolbox and TCI programs.
Control System Toolbox

Refer to toolbox.
CRC
Cyclic Redundancy Check 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 Mark V turbine controllers backup Communicator core (processor). (Also refer
to <C>.)
data dictionary
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
Data Dictionary also acts as the TCI real time database, holding the last timetag and
value received from the controller.
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 deadband algorithm to decide whether to
save or discard incoming data, as part of its data compression function.
Demand Display
An HMI function that allows user to monitor several turbine data points at a time and
issue simple commands.
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
Local Area Network used to link 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.
GSM
GE Energy Standard Messages. Refer to GEI-100658 GE Energy Standard
Messaging (GSM) 2.0 for HMI applications. 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.
Global Time Source (GTS)

Worldwide system supplying UTC (Coordinated Universal Time) using a network of
satellites.
graphical user interface (GUI)

An operating system interface between the user and the computer, based on graphics.
GUIs typically use a mouse or other tracking device and icons.
header
Textual information, such as a title, date, name, or other applicable identifying
information, positioned at the top of a screen, column, or page.
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 tool for
investigating cause-effect relationships.
HMI
Human-Machine Interface. The GE HMI is a Windows-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 an initial value before
processing.
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. The results of a logical expression can be stored in a
Boolean variable.
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 Windows-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 Windows-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 can select an operation to be performed.
Modbus
Serial communication protocol, initially developed by Gould Modicon for use
between PLCs and other computers to exchange real-time data and commands.
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
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.
On Site Monitor (OSM)

The on site monitor is a pc that can monitor equipment status and report the findings
back to GE Energy over the ADH network. It is used at sites with GE long term
service agreements or sites under GE warranties.
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.
OSM
Refer to On Site Monitor.
panel
The side or front of a piece of equipment on which terminations and termination
assemblies are mounted.
pc
Abbreviation for personal computer.
PDH
Refer to Plant Data Highway.
permissives
Conditions that allow advancement from one state to another.
ping
The ping utility command uses a series of Internet Control Message Protocol (ICMP)
Echo messages to troubleshoot network connectivity.
Plant Data Highway (PDH)

Ethernet communication network that connects the Historian, HMI Servers, HMI
Viewers, workstation, and printers.
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.
product code (runtime)

Software stored in the controllers Flash memory that converts application code
(pcode) to executable code.
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 computer after a controlled shutdown.
relay ladder diagram (RLD)

A ladder diagram represents a relay circuit. Power is considered to flow from the left
through contacts to the coil connected at the right.
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
Refer to product code.
Sequence of Events (SOE)

A high-speed record of contact closures taken during a plant upset to allow detailed
analysis of the event. Most turbine controllers support a data resolution of 1
millisecond.
server
A computer that gathers data over Ethernet from plant devices, and makes the data
available to computer-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
Refer to Sequence of Events.
SRTP
Service Request Transfer Protocol. An Ethernet communications protocol for
communications between the turbine controller and the HMI.
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.
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
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.
toolbox (Control System Toolbox)

Windows-based software package used to configure and troubleshoot the Mark VI
controllers, exciters, and drives.
trend
Time-based screen plot displaying 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.
Unit Data Highway (UDH)

Ethernet communication network that connects the Mark VI controllers, LCI,
EX2000, PLCs, and other GE provided equipment to the HMI servers.
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.
VLAN
Virtual Local Area Network. A scheme whereby a single network switch can support
multiple separate networks (such as UDH, PDH, and ADH). All networks configured
on the switch share a single switch-to-switch trunk port connection.
web browser
Computer software, such as Microsoft Internet Explorer or Netscape Navigator,
allowing screens and data to be viewed over a network from a server.
Windows (operating system)

Operating system from Microsoft Corporation.
Workbench
A CIMPLICITY HMI program used to view, configure, organize, and manage every
component of a CIMPLICITY project through a single window.
Index
animation rules 3-5
Dynamic Rung 3-2
main frame window 3-5
picture file windows 3-7
Rung windows 3-5
selecting a sequencing display screen 3-8
starting the 3-2
using the Find All function 3-8
viewing tabular data 3-9
A
alarm
diagnostic alarms B-3
hold list alarms (steam turbine only) B-1
introduction B-1
logger control 2-30
process (and hold) alarm data flow B-2
process alarms B-2
setup 2-8
CIMPLICITY
HMI supported functions A-4
communications 1-5
forced variables
locating forced variables 3-56
using control system toolbox 3-57
using Finder to locate a variable to force 3-54
demand displays
command target types 3-38
data area description 3-38
Demand Display 3-33
demand display data window 3-36
demand display menu window 3-35
opening, creating, modifying and saving demand
displays 3-40
other options 3-45, 3-52
saving 3-40
using demand display 3-39
working with command targets 3-43
working with point names 3-42
displays
Demand Display 3-33
Dynamic Rung 3-2
Logic Forcing 3-46
displays optional
Manual Synchronizing 2-12
Reactive Capability 2-11
Triggered Plot 2-15
displays other
Alarm Setup 2-8
Hold List 2-31
Lockout Function Diagnostic Reset 2-6
Lockout Function Master Reset 2-4
Start Checks 2-7
Synchronization 2-10
Trip Diagram 2-5
Turbine Startup Trend 2-9
displays user defined 2-20, 2-22
displays web-based 2-32, 3-25
Dynamic Rung Display
GE requisition number (3 V) 1-8
H
HMI
application-specific features 1-6
communications 1-5
components 1-2
functions for GE turbine controllers 4-1
graphic displays 1-3
optional features 1-5
overview 1-1
product features 1-1
starting up 2-1
Hold list
alarms (steam turbine only) 5-1
display (steam turbine applications) 2-31
rules 3-32
steam applications 3-31
L
lockout function
diagnostic reset 2-6
master reset 2-4
Logic Forcing Display
exiting 3-52
logic forcing display 3-46
Logic Forcing Display screen window 3-48
opening, creating, modifying and saving logic
forcing displays 3-49
Other options 3-45
printing the logic forcing display file 3-51
Starting 3-46
using the command targets 3-51
using the logic forcing display program 3-50
Index I-1
R
related documentation 1-7
reports
Historical Alarm and Event Exception Report 2-32
Historical Alarm and Event Report 3-26
Historical Alarm and Event Summary Report 2-34
S
sequencing information
Mark IV 3-1
Mark V and Mark V LM 3-2
Mark VI 3-10
viewing 2-16, 3-1
starting
demand display 3-33
dynamic rung display 3-2
logic forcing display 3-46
toolbox 3-53
up the HMI 2-1
T
technical specifications 1-6
Toolbox
forcing variables 3-57
privilege level functions 3-58
starting toolbox 3-53
trend
how to save trend files 3-24
Trend Recorder 2-24, 3-20
trip history
trip history data results window 3-18
trip history dialog box 3-17
Viewing 3-14, 3-20
trip information
for Mark IV 3-14
for Mark V and Mark V LM 3-14
for Mark VI 3-20
opening a trip log file 3-15
Viewing 3-14, 3-20
Index I-2
GE Energy
1501 Roanoke Blvd.
1 540 387 7000
www.geenergy.com

5 - Geh-6126c - Vol - I Hmi Manual

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

5 - Geh-6126c - Vol - I Hmi Manual

Загружено:

Авторское право:

Доступные форматы

GE Energy

HMI for Turbine Control

2008 - 2011 General Electric Company, USA. All rights reserved.

* Trademark of General Electric Company

CIMPLICITY is a registered trademark of GE Fanuc Automation North America, Inc.

SPEEDTRONIC is a trademark of General Electric Company, USA.

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

Your Companys Name and Address

If needed, how can we contact you?

Your Job Function / How You Use This Publication

Publication Issue/Revision Date

Detach and fax or mail to the address noted above.

........................................................................ Fold here and close with staple or tape ..........................................................................................

.......................................................................................... Fold here first ........................................................................................................

Safety Symbol Legend

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that, if not

Indicates a procedure, condition, or statement that should be

Note Indicates an essential or important procedure, condition, or statement.

This equipment contains a potential hazard of electric shock

To prevent personal injury or equipment damage caused by

Chapter 2 Quick-Start Procedures

Chapter 3 Display and Control (Command) Programs

GEH-6126C Vol I HMI Operators Guide

Hold List (Steam Applications) - Mark V and Mark VI..........................................................................3-31

Appendix A HMI Function Reference

HMI Functions for GE Turbine Controllers .............................................................................................A-1

Appendix B Alarm Overview

Introduction .............................................................................................................................................. B-1

GEH-6126C Vol I HMI Operators Guide

runs on a computer-based workstation using a Microsoft Windows Operating

Process variable trending

HMI access security

Maintenance functions such as logic forcing and user-defined point displays

GEH-6126C Vol I HMI Operators Guide

Chapter 1 Overview 1-1

CIMPLICITY HMI is used primarily to display turbine status screens, which

An HMI Viewer contains the operator interface software, which allows

Note GFK-1180 provides a detailed description of the capabilities of the

Turbine Control Interface (TCI) is a software package used to communicate

Mark IV: Provides real-time interface for data and alarms

Mark V: Provides real-time interface for data and alarms, specialized

Mark VI: Provides real-time interface for alarms.

TCIMB (TCI/CIMPLICITY Bridge, previously called CIMB or CIMBridge) is

Enables CIMPLICITY to collect data and alarms from controllers

Forwards setpoint and alarm commands from CIMPLICITY to TCI for

System database (Mark VI only) establishes signal management and

1-2 Chapter 1 Overview

GEH-6126C Vol I HMI Operators Guide

Data Flow between HMI Components

Chapter 1 Overview 1-3

Click buttons and other

Select an alarm listed on the

Sample HMI Display for Gas Turbine and Generator Data

1-4 Chapter 1 Overview

CIMPLICITY Alarm Viewer provides alarm management functions such as

GEH-6126C Vol I HMI Operators Guide

Mark VI Unit Data Highway (Ethernet)

Mark IV Control System Freeway (CSF)

Example of a Turbine Control Communications Network

GEH-6126C Vol I HMI Operators Guide

Chapter 1 Overview 1-5

1-6 Chapter 1 Overview