Geh 6759 PDF

GE Energy GEH-6759B
WorkstationST* Application
Mark* V Feature
System Guide
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.
© 2009 – 2012 General Electric Company, USA. All rights reserved.

Revised: 2012-05-03
Issued: 090902
* Trademark of General Electric Company

ARCNET is a registered trademark of Datapoint Corporation.
CIMPLICITY is a registered trademark of GE Intelligent Platforms
Excel, Microsoft, and Windows are registered trademarks of Microsoft Corporation.
Modbus is a registered trademark of Schneider Automation.
Teflon is a trademark of E.I. DuPont de Nemours and Co., Inc.
To:
Readers Comments GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA
Fax: 1–540–387–8651
(GE Internal DC *278–8651)
We welcome comments and suggestions to make this publication more useful.
Your Name Today’s Date If needed, how can we contact

you?
Your Company’s Name and Address Job Site Fax No ........................................
Phone No ...................................
GE Requisition No. E-mail .........................................
Your Job Function / How You Use This Publication Publication No. Address
Publication Issue/Revision
Date
General Rating
Excellent Good Fair Poor Additional Comments
Contents ...............................................
Organization ...............................................
Technical Accuracy ...............................................
Clarity ...............................................
Completeness ...............................................
Drawings / Figures ...............................................
Tables ...............................................
Referencing ...............................................
Readability ...............................................
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No. Comments
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
............................................................................................. ..................................................................................................
.............................................................................................. ..................................................................................................
.............................................................................................. ..................................................................................................
Other Comments (What you like, what could be added, how to improve, and such) .....................................................................
.....................................................................................................................................................................................................
.....................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
......................................................................................................................................................................................................
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
Superior Comparable Inferior Do not know Comments .............................................

Detach and fax or mail.
....................................................................Fold here and close with staple or tape....................................................................
Place
stamp
_______________________
here
_______________________
_______________________
GE Energy
Documentation Design, Rm. 297
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.
Warning
Indicates a procedure, condition, or statement that, if not strictly

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

strictly followed to improve these applications.
Attention
To prevent personal injury or damage to equipment, follow all
GE safety procedures, LOTO, and site safety procedures as
indicated by EHS.
Warning
This equipment contains a potential hazard of electric shock,

burn, or death. Only personnel who are adequately trained and
thoroughly familiar with the equipment and the instructions
should install, operate, or maintain this equipment.
Warning
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
equipment’s case must be shielded to prevent contact by
personnel.
Warning 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.
Warning
Always ensure that applicable standards and regulations are

followed and only properly certified equipment is used as a
critical component of a safety system. Never assume that the
HMI or the operator will close a safety critical control loop.
Warning
Contents
Chapter 1 Mark* V................................................................................................................... 1-1
Mark V Controller .................................................................................................................................... 1-1
HMI Unit-specific Directory ................................................................................................................ 1-1
Compiling Unit-specific Configuration Files ........................................................................................... 1-6
Downloading Unit-specific Configuration Files ....................................................................................... 1-6
Control Constants .............................................................................................................................. 1-6
Unit Attribute Configuration File .......................................................................................................... 1-7
Auto-calibrate Display .............................................................................................................................. 1-9
Mark V Auto-calibration ..................................................................................................................... 1-9
Command Pushbutton ...................................................................................................................... 1-10
Command Line Arguments................................................................................................................ 1-12
Screen Description........................................................................................................................... 1-12
Auto-calibrate Display Dialog Boxes................................................................................................... 1-13
Control Constants Display ....................................................................................................................... 1-14
Changing a Control Constant ............................................................................................................. 1-15
Control Constants Adjust Display ...................................................................................................... 1-15
CONSTCHK - Constants Check ............................................................................................................... 1-18
Operation ....................................................................................................................................... 1-18
Diagnostic Counters Display ................................................................................................................... 1-19
File Type........................................................................................................................................ 1-19
Using the Diagnostic Counters Display Program.................................................................................... 1-19
Logic Forcing Display ............................................................................................................................ 1-24
File Structure .................................................................................................................................. 1-25
Using the Logic Forcing Display Program ............................................................................................ 1-26
PVOTE - Prevote Data Display ................................................................................................................ 1-34
Operation ....................................................................................................................................... 1-34
Command Line Description ............................................................................................................... 1-35
Header Time Tag ............................................................................................................................. 1-35
DABUILD - Diagnostic Alarm Build ........................................................................................................ 1-36
DDLOCATE - Data Dictionary Locate ...................................................................................................... 1-37
DDUTIL - Data Dictionary Utility............................................................................................................. 1-40
MK5MAKE - Mark V Make .................................................................................................................... 1-41
ALARM_L - Alarm List ......................................................................................................................... 1-43
Operation ....................................................................................................................................... 1-43
CONSTSET - Constants Set .................................................................................................................... 1-44
Operation ....................................................................................................................................... 1-44
Application Information.................................................................................................................... 1-45
EPA Log Configuration ........................................................................................................................... 1-47
SEQCOMPL - Sequencing Compiler ........................................................................................................ 1-48
File Structure .................................................................................................................................. 1-48
GEH-6759B Contents 1
Running the Sequence Compiler......................................................................................................... 1-49
Master Sequencing Configuration File ................................................................................................. 1-50
SEQDOCMT - Sequencing Documentor .................................................................................................... 1-53
File Structure .................................................................................................................................. 1-53
SEQEDIT - Sequencing Editor ................................................................................................................. 1-58
File Structure .................................................................................................................................. 1-58
Using the Control Sequence Editor...................................................................................................... 1-59
CSPPRINT - Control Sequence Program Printer .......................................................................................... 1-66
File Structure .................................................................................................................................. 1-66
Operation ....................................................................................................................................... 1-66
TABLE_C - Table Compile ...................................................................................................................... 1-69
Operation ....................................................................................................................................... 1-69
EEPROM Downloader ........................................................................................................................... 1-71
Operation ....................................................................................................................................... 1-71
Application Information.................................................................................................................... 1-73
CARD_ID ............................................................................................................................................ 1-75
Background .................................................................................................................................... 1-75
Operation ....................................................................................................................................... 1-75
I/O Configurator..................................................................................................................................... 1-76
Chapter 2 HMI ......................................................................................................................... 2-1
HMI ...................................................................................................................................................... 2-1
Dynamic Rung Display....................................................................................................................... 2-1
Trip Log Collection for the Mark V..................................................................................................... 2-11
Trip Log Viewer .............................................................................................................................. 2-17
DMD2SRC Demand to Source Conversion Program .............................................................................. 2-19
Starting the Demand Display to Source Conversion Program ................................................................... 2-25
Editing the Demand Display Source File .............................................................................................. 2-25
MODBUS_L Modbus List File Generator ............................................................................................ 2-26
MODBUS_L MODBUS List File Generator ......................................................................................... 2-26
CIMMOD_L MODBUS List File Generator ......................................................................................... 2-28
Configuration ........................................................................................................................................ 2-29
GeCssTci Configuration Files............................................................................................................. 2-29
TCI Modbus Configuration................................................................................................................ 2-30
Configuration File (AT_START.DAT And AT_STOP.DAT) ..................................................................... 2-32
Configuration File (CONFIG.DAT) ..................................................................................................... 2-34
Configuration File (IO_PORTS.DAT) .................................................................................................. 2-35
Configuration File (MODB_FWD.DAT) .............................................................................................. 2-38
Time Synchronization Configuration ................................................................................................... 2-39
Time Zone Make - TZ_MAKE........................................................................................................... 2-43
Turbine Control Maintenance Icons..................................................................................................... 2-46
The EPA Logger.............................................................................................................................. 2-47
Diagnostics ........................................................................................................................................... 2-50
2 Contents WorkstationST* Application Mark* V Feature

Alarm Dump 1 - ALMDUMP1 .......................................................................................................... 2-50
Alarm Dump 2 - ALMDUMP2........................................................................................................... 2-52
ARCWHO ..................................................................................................................................... 2-52
VIEW2 - View High-speed Mark V Data ............................................................................................. 2-54
VIEW2T - View High-speed Mark V Data, Triggered............................................................................. 2-57
VIEWPV - View High-speed Pre-vote Turbine Data .............................................................................. 2-60
VIEWQ - View Multi-processor High-Speed Turbine Data ...................................................................... 2-63
VIEWn Analysis Programs................................................................................................................ 2-66
VIEW_LIM - View Data Analysis, Limits ............................................................................................ 2-67
VIEW_SD - View Data Analysis, Standard Deviations ........................................................................... 2-68
VIEW2ASC - Convert View Data to ASCII .......................................................................................... 2-70
Chapter 3 Networks................................................................................................................ 3-1
Mark V System - StageLink ....................................................................................................................... 3-1
Terms of Reference ............................................................................................................................ 3-1
StageLink Characteristics.................................................................................................................... 3-2
Cable Recommendations..................................................................................................................... 3-3
Summary of StageLink Topology Rules ................................................................................................. 3-3
Total Effective Distance Rules ............................................................................................................. 3-6
Redundant System Rules .................................................................................................................... 3-7
GEH-6759B Contents 3
Notes
4 Contents WorkstationST* Application Mark* V Feature

Chapter 1 Mark* V
Mark V Controller
HMI Unit-specific Directory
Each Mark V controller communicating with a Human-machine Interface (HMI) has a
unit-specific directory and subdirectory on the HMI hard drive. These directories have
names referring to the unit. They are located under the Site Directory and are defined
in the Site Directory's CONFIG.DAT file. The unit configuration directories typically
follow a pattern of being named \UNIT1 and \UNIT2, or \UNIT_G1 and \UNIT_G2, or
simply \G1 and \G2. It is important that the name of the directory matches the entry
in the CONFIG.DAT file.
Many of the following procedures require work from a command prompt window in
either the Site Directory or a Unit Configuration Directory. These command prompt
windows are created as follows:
Ø To create a Command Prompt window in the Site Directory: from the

Start menu, select Turbine Control Maintenance (ST), HMI Configuration,
and Command Prompt menu. The GeCssTci Command Prompt window
displays in the Site Directory.
Ø To create a Command Prompt window in a Unit Configuration Directory:

from the Start menu, select Turbine Control Maintenance (ST), <Unit Name>
and Command Prompt . The GeCssTci Command Prompt window displays
in the Unit Configuration Directory for the selected unit.
It is important to create the command prompt windows using the above method because
these windows have the directory containing the GeCssTci toolset (including the Mark
V Maintenance Tools) added at the beginning of the PATH. That allows the programs
required for Mark V maintenance to be found without needing special directory specifiers.
Many batch files will fail if they are unable to find the needed programs.
Note It is especially important to launch the command prompt windows from the
Start menu if running on a Hybrid HMI. On a Hybrid HMI the eTCSS application
tools are included in the path by default. If the above procedure is not used, then tools
from the eTCSS application may inadvertently be used instead of the tools from the
ControlST software suite.
Configuration files contained in a unit-specific directory can be broken up into five

groups as follows:
• Assignment files
• Data Dictionary files
• I/O Configuration Constant files
• Table files
• ControlSequence Program (CSP) segment files.
GEH-6759B Chapter 1 Mark* V System Guide 1-1

Assignment Files
Assignment files, while not downloaded to a Mark V controller, contain unit-specific
control signal database pointnames and scale types for many of the control signals. The
information in assignment files is used when creating the primary unit Data Dictionary
file, UNITDATA.DAT. This file contains all of the unit-specific control signal database
pointname information.
For each unit, GE provides the following four assignment files in the HMI’s unit-specific
directory: IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, and SITE.ASG.
These are American Standard Code for Information Interchange (ASCII) text files,
sometimes called plain text files. They can be viewed or modified using any ASCII text
editor.
When I/O devices are connected to a Mark V controller, they must be assigned a control
signal database pointname and a scale type. I/O devices are specified in the I/O assignment
file, IO.ASG. In this file, a control signal database pointname and a scale type are assigned
to the location, which is being used for a particular device.
A Mark V controller has multiple spare control signal database memory locations (points)
which are available for use or assignment. To make use of these spare points for new
or additional control and protection functions it is necessary to define the type of point
required, the control signal database pointname, and the scale code. These definitions are
made in one of three assignment files. The file in which the assignment is made depends
on the type of signal required as well as on who is making the assignment, that is, factory
personnel or site personnel, customer or GEPS/Business Associate field personnel. The
files are as follows:
• FACTORY.ASG is used for control signal database pointnames and scale types.
GE or GEPS’s business associates assign these to spare memory locations in
FACTORY.ASG. This file can be altered to accommodate customization of the CSP
for a particular application.
• ALLOCSSP.ASG (ALLOCation of Structured Software Points) is used for additional
I/O, spare double-word variables, and spare alarm logic points. Spare double-word
variables and alarm logic points, which are required, are assigned pointnames
and scale types in ALLOCSSP.ASG. Both factory (GE and GEPS Business
Associates) and field/site personnel make assignments for these two types of points in
ALLOCSSP.ASG.
• SITE.ASG is used for points other than I/O, double-word variables, and alarm logic
points. Customer and/or GEPS/Business Associate field personnel make assignments
of signal pointnames and scale types to spare control signal database memory
locations in SITE.ASG.
1-2 WorkstationST* Application Mark* V Feature

Data Dictionary Files
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, such as type, units, and messages. The primary unit
Data Dictionary file, UNITDATA.DAT, can be created in the unit-specific directory.
Assignment files and template files are used in the creation of UNITDATA.DAT. Many
HMI configuration programs require information from UNITDATA.DAT when modifying
or compiling unit configuration files for downloading.
Some control signal database pointnames are common to applications (steam turbines or
gas turbines) and must reside in memory at specific locations and must not be changed.
These common, fixed pointnames are contained in template files. The fixed control-signal
database pointnames, the I/O assignments, and spare memory locations being specified in
the assignment files must be included in the UNITDATA.DAT file. If any new assignments
are made, they must be included in a new UNITDATA.DAT file.
The program DDLOCATE creates UNITDATA.DAT. This program uses the assignment
files which are specified at the time DDLOCATE is run, in addition to three template
files in the unit-specific PROM sub-directory: UNITDATA.TPL, UNITFREE.TPL,
and UNITMAP.TPL. Information from both the assignment files and the .TPL files
(TPL stands for template) in the PROM sub-directory are used to create the unit-specific
UNITDATA.DAT file. The command-line format for running DDLOCATE is as follows:
DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG
Refer to the section on Although their order is unimportant, all assignment files for a particular unit must be
MK5MAKE.BAT. for additional specified on the command line each time DDLOCATE is run. If a modification is made to
information. ALLOCSSP.ASG only, such as to use a spare alarm logic point, all the assignment files
must be specified on the command line when DDLOCATE is run. Each time DDLOCATE
is run, a new UNITDATA.DAT file is created; all the assignments must be included in this
new file. DDLOCATE is run as part of MK5MAKE.BAT.
Other Data Dictionary files that must be present in the unit-specific directory for proper
operation include:
• ALARM.DAT containing process and diagnostic alarm messages (maximum case).

• ENUMDATA.DAT containing display messages for Enumerated Data types.
• ENGLISH.DAT containing scale code information.
• METRIC.DAT containing scale code information.
The following unit-specific Data Dictionary files are optional and not required for proper
HMI operation:
• LONGNAME.DAT containing CSDB pointname descriptions.

• SYNONYM.DAT containing site-specific CSDB pointname synonyms.
Unit-specific Data Dictionary files are not downloaded to a Mark V controller, but are
loaded into the HMI’s RAM each time the HMI is turned on or reset. This information is
used to scale and display control signal database pointname information on the HMI as
well as for alarm and event logging. As discussed above, some HMI programs require
information from UNITDATA.DAT.

I/O Configuration Constants
I/O configuration constants are used to scale or condition signals to and from I/O
devices connected to the Mark V controller. IO configuration files are downloaded
to the controller. I/O devices include pressure transducers, temperature switches,
electro-hydraulic servo-valves, position transducers or reactors, thermocouples, and RTDs.
Many of the same type of I/O devices can have differing outputs or require dissimilar
inputs. For example, thermocouples produce a millivoltage proportional to temperature;
however, a Type K thermocouple produces a different millivoltage than a Type T for
the same temperature. An I/O configuration constant is used to appropriately scale the
input signals from the various types of thermocouples. As another example, milliamp
transducers come in several output ranges such as 4-20 mA, 0-1 mA, and 0-10 mA. More
than one type of milliamp transducer can be used on a unit or its auxiliaries, so I/O
configuration constants are used to scale the input for use in the controller.
I/O configuration constants are initially contained in the I/O configuration files in the
unit-specific directory. The three files are as follows:
• IOCFG_Q.DAT
• IOCFG_C.DAT
• IOCFG_D.DAT
All three files are present in the unit-specific directory for each Mark V controller that
communicates with the HMI, even if the controller does not include a <D> backup
communication processor. The information in these files is in hexadecimal format, and can
be viewed using the I/O configurator program, IO_CFG, usually available from the HMI
Main Menu. The screens presented in the I/O configurator depend on the configuration
data files found in the unit PROM directory. PROM\IO_CFG.DAT contains the list of files
required for the I/O configurator, such as TCCA_CFG.DAT. The I/O configuration files can
be downloaded to a Mark V controller without any intermediate steps such as compiling.
Table Files
The majority of unit-specific configuration files are Table Files. These files contain tabular
listings of CSDB pointnames and information about their type, use, and value. Table Files
contain information in an ASCII text format which, when compiled and downloaded to
the controller, is used by functions such as the Control Sequence Program and the loggers.
Several of the source Table Files are dummy files containing no information, created for
symmetry and possible future use.
Modifications can be made to any of the ASCII text Table Files (known as source
files) using any ASCII text editor. Prior to downloading the information in the source
Table Files, it must be converted into binary format using the Table Compiler program,
TABLE_C. The command line format for running the Table Compiler to compile all the
Table Files is as follows:
TABLE_C ALL
Using the Table Compiler, information in the source Table Files is converted into binary
format in files with the same filename but with an .AP1 filename extension. For example,
CONST_Q.SRC is compiled into CONST_Q.AP1.

The Table Compiler uses information contained in UNITDATA.DAT and one of the
scale code files (ENGLISH.SCA by default) when converting the source files into hex
files. Since no CSDB pointnames are downloaded to the Mark V controller, the Table
Compiler finds the software signal pointname in UNITDATA.DAT, and uses its memory
location/address, scale code, and point type when creating the downloadable Table Files.
Source Table Files
Table Files Description
CONST_B.SRC Default file; blank
CONST_Q.SRC All control constants and their (initial) values
EPA_B.SRC A list of pointnames for emissions logging purposes
EPA_Q.SRC Default file; blank
MAOUT_B.SRC Default file; blank
MAOUT_Q.SRC A list of pointnames and ranges for <C> mA outputs
CHNG_B.SRC A list of <C> analog pointnames and ranges monitored for excursions and logged as events
to the Historian
CHNG_Q.SRC A list of <Q> analog pointnames and ranges monitored for excursions and logged as events
to the Historian
EVENT_B.SRC A list of <C> logic signal pointnames logged as events
EVENT_Q.SRC A list of <Q> logic signal pointnames logged as events
TOTT_B.SRC A list of pointnames to configure the Hold List
TOTT_Q.SRC A list of pointnames for which data is totalized
HIST_B.SRC A list of pointnames included in the Trip History log, for Mark V
CBLR_B.SRC A list of digital inputs to <C> which are associated with command pushbuttons in the CSP
CBLR_Q.SRC A list of digital inputs to <Q> which are associated with command pushbuttons in the CSP
CSP Segment Files

A Control Sequence Program (CSP) segment is an ASCII text file containing information
such as control blocks, parameters, comments, and relay ladder diagram sequencing. The
turbine control program is contained in the CSP. The CSP for a unit is made up of at least
two segments, one for <Q>, and one for . CSP segments can be run at different
frequencies, such as 4, 8, 16, or 32 Hz depending on the application, and at different
skews, or offsets. Segments are subsets of the CSP containing sequencing functions,
which are related and must be run at a certain frequency. There can be as many as eight
CSP segments for and eight CSP segments for <Q>.
Refer to the section Using the CSP segments can be viewed and modified using the Control Sequence Editor program,
Control Sequence Editor for SEQEDIT.EXE, available in the HMI’s Turbine Control Maintenance section. In some
additional information. cases, all of the unit's control and protection (other than emergency overspeed trip and
servo regulator loops) can be accomplished in one CSP segment in <Q>. CSP segment
files can have any valid DOS filename of eight characters maximum but must have an
.SRC filename extension.

Prior to downloading to a Mark V controller, the CSP must be converted to binary (AP1)
format using the Control Sequence Compiler (CSP Compiler). The CSP Compiler uses
information from UNITDATA.DAT, Big Block definition files in the unit-specific PROM
subdirectory (PRIMITIV.DEF and BIGBLOCK.DEF), and the names of CSP segment
files, which have been specified in a unit-specific control sequencing configuration file,
MSTR_SEQ.CFG. The CSP Compiler creates binary format downloadable CSP files,
SEQ_B.AP1 and SEQ_Q.AP1. The CSP Compiler can be run from the HMI Turbine
Control Maintenance section or at the command line of the unit-specific directory with the
SEQCOMPL command.
Refer to the section Text file MSTR_SEQ.CFG contains two sections defining the names of CSP segment
MSTR_SEQ.CFG for files, which are compiled for <Q>’s CSP and ’s CSP. In addition, it defines the rates,
additional information. offsets, and skews as well as the order in which CSP segments are compiled and run. The
first segment file specified is run first, the second segment file specified is run next, the
third segment file specified is run next, and so on.
CSP segments are initially created using Big Block Library (BBL), relay ladder diagram
rungs, and comment rungs. They are customized by GE or its Business Associates to
match a particular application or customer’s requirements, and can be modified in the field
using the Control Sequence Editor. New CSP segments can be created using the Control
Sequence Editor. If a new segment is created, the name of a new segment must be added
to MSTR_SEQ.CFG to be included in the downloaded CSP files. The maximum number
of segments per <Q> and that can be compiled is eight.
Compiling Unit-specific Configuration Files

Refer to the sections on The unit-specific Table and CSP files must be converted to binary format prior to
the Table Compiler and downloading to the Mark V controllers. This is done using the Table Compiler program
MK5MAKE for additional directly or the MK5MAKE.BAT batch file, which calls the Table Compiler program.
information.
Downloading Unit-specific Configuration Files
When the unit-specific ASCII text Table and CSP files are compiled to binary format,
they, along with the I/O Configuration Constants, can be downloaded to the Mark V
controllers using the EEPROM Downloader program (EEPROM). EEPROM is available
from the HMI command line.
Refer to the section on the The EEPROM Downloader program transfers unit configuration file information,
EEPROM Downloader for sometimes known as EEPROM partitions or sections, from the HMI's hard drive to the
additional information. controller.
Control Constants
Special care is needed when modifying control constants in the CONST_Q.SRC file.
These constants are downloaded to non-volatile memory in the controller. They are copied
to RAM memory when the control is initialized and are used during the CSP operation.
Refer to the section on the The values of control constants in the processor’s RAM can be changed using the Control
Control Constant Adjust Constant Adjust Display program by selecting a constant on the HMI display. Control
Display for additional constants can be adjusted while the unit is running, although the rate of change of the
information. control constant’s value is quite slow when the unit is running to prevent a rapid change
from tripping the turbine.

A feature of the Control Constants Adjust Display is to copy the control constant, whose
value was changed in RAM, to the controller’s nonvolatile memory.
Ø To copy the control constant: from the display, click the target Storage
Update and in the Execute Dialog Box click OK. The current RAM value of
every control constant is copied to the processor's non-volatile memory.
However, there is no automatic method of updating the values of control constants in

the configuration file CONST_Q.SRC. If a control constant in a Mark V controller is
modified using the Control Constant Adjust Display, and the value of the control constant
in CONST_Q.SRC is not subsequently changed to match the unit’s value, a re-compiling
and downloading of control constants causes the controllers nonvolatile storage value of
the control constant to revert to the old value in CONST_Q.SRC.
Note Whenever a control constant is modified using the Control Constant Adjust
Display, the control constant source Table File, CONST_Q.SRC, should be edited
to reflect the new value and compiled. This assures the Control Constant Table
hexadecimal file, CONST_Q.DAT, contains the new value and any subsequent
downloads will be done with the correct value.
Refer to the section on It is possible to generate a list of the current values of control constants in the controller
CONSTCHK program for using the CONSTCHK program.
additional information.
Unit Attribute Configuration File
The ControlST software suite supports many additional features over what is supplied
by a Mark V and its programming tools. In many cases this results in extra attributes
about each point in the Mark V controller that are not configured by any of the tools
used to program the Mark V. The UNITATTR.DAT (Unit Attributes) file in the Unit
Configuration Directory can be used to add these additional attributes to the Mark V
signals as they are passed to the WorkstationST* application. This includes fields such as
the "Alarm Class" assigned to a point that generates an alarm, or a "Plant Area" attribute
that can be assigned to any point.
Note The Mark V Feature is an option in the WorkstationST Component Editor.

Enabling the Mark V Feature enables direct WorkstationST communication to the Mark
V controllers. The list of Mark V controllers that the WorkstationST component is to
contact is defined in the Consumed Devices list, and includes the Mark V components
configured into the system using the ToolboxST application.
The list of attributes supported by the UNITATTR.DAT file is found in the template file
supplied with the WorkstationST application. All of the Mark V Feature in WorkstationST
template files are found in a DATA directory under the program distribution, typically
as follows:
C:\Program Files\GE Energy\WorkstationST Features\TCI\DATA

A sample UNITATTR.DAT template is as follows:
;
;
; UNITATTR.DAT - Unit Attributes
;
; This is the attribute file for the signals in this unit.
; This file can be "max case", if a signal is not used the section for
; that signal is skipped.
;
; There is no required indentation in the file, but it is recommended
; that sections be left aligned and the attributes within that section
; be indented.
;
; Each section is started with the name of the desired point inside a
; set of square brackets. No spaces are allowed inside the brackets.
;
; Within each section is set of zero or more attributes that are to be
; set or overridden for that point. Attributes that override current
; settings imported from other files can be set to an empty string to
; remove the attribute completely.
;
;[VariableName]
; ActiveSeverity = "<integer>"
; Defines the Active Severity for an alarm generated from this variable.
; AlarmClass = "<string>"
; Defines the alarm class for an alarm generated from this variable.
; Alias = "<string>"
; Defines an alias for this variable.
; Deadband = "<real>"
; Defines the historical storage Deadband for this variable, indicating
; that this variable should be stored in the historian. The value is
; in the WorkstationST native engineering units. Normally this is NOT
; included here but in the HSTPOINT.SRC file where the conversion from
; Mark V native format to the WorkstationST native units can be computed.
; DescriptionAlt = "<string>"
; Defines the alternate language description for this variable.
; DisplayScreen = "<string>"
; Defines the Display Screen associated with this variable.
; NormalSeverity = "<integer>"
; Defines the Normal Severity for an alarm generated from this variable.
; PlantArea = "<string>"
; Defines the Plant Area associated with this variable.
; ShortTermDeadband = "<real>"
; Defines the Short Term Deadband for this variable, indicating that this
; variable should be included in a Recorder collection. The value is
; in the WorkstationST native engineering units. Normally this is NOT
; included here but in the ST_TREND.SRC file where the conversion from
; Mark V native format to the WorkstationST native units can be computed.
; SoeDescription = "<string>"
; Defines an optional SOE description for this variable. If not supplied
; the variable's normal description (LONGNAME) is used.

Auto-calibrate Display
The auto-calibrate function in the controller allows a user to calibrate the feedback
signals in the position control sections of the various Servo Valve Outputs (SVOs). This
consists of establishing the relationship between the required position and the actual
position. The servo board in the controller does the calibration process, with the required
inputs downloaded to it from the HMI. The results of the calibration are then collected
for display by the HMI.
Mark V Auto-calibration
In addition to the calibration function, two different verify functions are available. These
verify functions provide high-speed data (128 Hz) taken while ramping from one end stop
to the other. Verify under position control ramps the position at a constant rate and plots the
current, while verify under current control holds the current constant and plots the position.
A manual control mode is provided, which allows the user to specify a desired position.
This is useful for positioning a valve at a desired position when the normal regulator is
an integrator.
The HMI has a special display that accesses the auto-calibrate functions in the Mark V
control. The auto-calibrate display uses a data file to define the calibration parameters and
the format of the screen display for each SVO.
File Type
This section describes the format of the data file, ACALIB.DAT. The program
AUTOCAL.EXE runs the Autocal function. ACALIB.DAT defines the calibration
parameters and the format of the screen display for each SVO. ACALIB.DAT must be
located in the unit configuration directory. The three main sections to this data file are
Status Codes, Trace Information, and Display Definitions.
• Status Codes converts I/O board status codes to text. These are used to decipher the
hexadecimal I/O board state information to text for ease of understanding.
• Trace Information defines how many position traces are to be displayed for each
regulator type when displaying a Verify Under Current Control or Verify Under
Position Control plot.
• Display Definitions section defines all the different auto-calibrate displays for each
regulator. Each definition includes items such as the processor, I/O board, I/O
processor number, regulator number, positions at current saturation, logic permissive
for sending commands, and the data to be displayed. When auto-calibrate is run, it
displays a list of the regulators for user selection.

Menu Selections
Menu Command Use to
File SAVE AS Save the currently displayed text from the data window to a text file.
PRINT Display the standard Print dialog box. Use this menu selection to print the data window.
PRINTER SETUP Display the standard Printer Setup dialog box for selecting a printer and its
characteristics.
EXIT Close the auto-calibrate display.
Edit COPY Copy auto-calibrate Data Window to the clipboard as a bitmap.
SELECT UNIT Display the Unit Select dialog box which lists all the unit controls defined in the turbine
control interface. Double-clicking the left mouse button on a unit name, or highlighting a
unit name then selecting OK selects the unit.
View TOOLBAR Toggle the toolbar on and off.
STATUS BAR Toggle the status bar on and off.
Help HELP TOPICS Call the auto-calibrate program help.
ABOUT Present the auto-calibrate display About dialog box.
Command Pushbutton
The command pushbuttons in the button-view window have the following standard colors:
• Red - Immediate acting

• Green - Arm/Run; this requires confirmation before sending the command
• Gray - Setpoint: The user enters a desired setpoint
Command pushbuttons display based on the control state and permissive logic.
Personnel should keep clear of the area during an automatic

calibration sequence or when one of the automatic calibration
options is run. The hydraulic actuator is moving the device from
mechanical stop to mechanical stop as fast as four seconds using
Warning full hydraulic pressure.
If no pushbuttons are visible, one of the following conditions is occurring:
• The test permissive, usually L3ADJ is not TRUE.

• The test permissive, usually L3ADJ is not TRUE.
• The Autocal function is being used by another auto-calibrate window, HMI, or .
• Communications to the controller have failed.
The Enable Commands pushbutton must be activated to allow the user to issue further
commands to the unit. Read and heed the warnings accompanying this command.
Enable Commands The data file can define a logic Permissive signal that must be in a
required state before calibration commands can be sent to the Mark V. If the permissive
signal is found to be valid, the Enable Commands pushbutton is visible and a warning
message is displayed. Read and heed the warnings accompanying this command.

Start Calibrate Start Calibrate sends the command to the Mark V to start the Autocal
function. This runs the position calibrate function and reports the resulting information on
the display. When all required permissives are met and hydraulic operation of the valve
is possible, Autocal controls the servo-valve output current(s) to the servo-valve device
to position the actuator or device. The Mark V then measures the feedback voltages and
calculates I/O Configuration Constants. The currents determined during the auto-calibrate
procedure are stored in TCQA RAM.
Verify Position Verify Position starts the verify under position control function. This
function ramps the actuator from actuator mechanical minimum travel to mechanical
maximum travel then ramps back again at a constant rate (for example, constant inches per
minute). While verifying under position control, Autocal causes the servo-valve output
current to increase or decrease as necessary to maintain the fixed rate of travel as indicated
by the LVDT/R feedback signal(s). Servo current data is collected at a 128 Hz rate and
placed in the Mark V's buffer. If the servo-valve, the actuator, or device is not mechanically
binding or sticking, the amount of current required to maintain the fixed rate of travel
should be constant. Such things as valve packing, a scored hydraulic actuator cylinder, or
a damaged valve stem can cause such mechanical binding. The results of verifying under
position control can be plotted on the HMI and stored or printed for further analysis.
Verify Current Verify Current starts the verify under current control function. This
function causes Autocal to output a fixed servo-valve output current that causes the
device to move at a constant rate of approximately 30% travel-per-second from actuator
minimum mechanical to maximum mechanical travel and back. If the processor is
re-booted or another valve calibrated, the current values from the most recent Autocal
procedure are lost. If no values exist in TCQA RAM for moving the device, a message is
displayed indicating that the device must be calibrated before the operation can occur. The
current for each direction is different because of the null bias current required to overcome
the fail-safe spring bias in the servo-valve.
Enable Manual Enables Manual Setpoint control from the auto-calibrate display.
Manual Setpoint Manual Setpoint defines the position reference if manual control
is enabled. Manual control is used to check the accuracy of calibration or to hold the
device in some position for mechanical inspection or maintenance. The desired position is
entered, Enable Manual is selected, and then the valve is driven to the setpoint position.
Changing the Manual Setpoint when manual control is enabled ramps the device at a fixed
30% stroke-per-second rate to the new setpoint.
Idle Idle halts any calibration, verify, or manual control and clears any status or error
condition from a previous command.
View Verify View Verify is used to collect and plot data in the capture buffer.

Command Line Arguments
The auto-calibrate display can be started from a GeCssTci Command Prompt window
using the following command:
AUTOCALThe auto-calibrate display can be launched with the following optional

argument to quickly bring the display to a desired configuration:
/UNIT:
The following example specifies the unit name as T1:
AUTOCAL /UNIT:T1 Display actions are as follows:
• Valid Unit: The auto-calibrate display is opened with the unit already selected.
• Invalid Unit or None: A blank screen is displayed if an invalid unit is specified on
the command line.
• Single Unit Sites: The unit parameter is ignored on single unit sites.
Screen Description
The auto-calibrate screen consists of three windows as follows:
• Tree View window

• auto-calibrate Data window
• Button-view window
The Tree View is on the left side of the display, the auto-calibrate data is in the center, and
the Button view is on the right. The three portions are separated by movable splitter bars.
The program can display and update one set of auto-calibrate test data at a time.
Tree View The auto-calibrate Tree View window is a graphical window that depicts the
hierarchy of a unit and regulators available for calibration. The Tree View can hold and
display one unit at a time; it cannot be printed.
Auto-calibrate Data The auto-calibrate data window has three main regions:
• The Header contains the Unit Name, Site Name, Program Name, and Time tag - The
Header time tag displays the operator interface time and updates whenever a valid
new message is received. If no valid messages are received for five seconds, the
Header time tag is highlighted and the data being displayed may not be valid.
• The Data Area is below the Header. This displays the strings for the selected
auto-calibrate regulator calibration such as important data from each processor,
relevant test values, and test status messages. The Data Area is updated at 1 Hz.
• The Message Box is at the bottom of the data window and displays warnings and
information about the Autocal function status. Take note of all messages and
warnings.

The pushbuttons and their Button-view The button-view window contains the pushbuttons that interact with the
functions are discussed in the unit control to conduct and verify auto-calibration functions. These buttons are visible
section on auto-calibrate only when the board permissives have been met and no other window, HMI, or 
Command Pushbutton is conducting an auto-calibrate function. The Enable Commands pushbutton must be
Description. activated to allow the user to issue further commands to the unit. Read and heed the
warnings accompanying this command.
If the Mark V does not respond, or another auto-calibrate window, HMI, or is using
the Autocal function, the data fields remain blank.
Auto-calibrate Display Dialog Boxes

Unit Select Used to change which unit’s data is displayed. Only valid units are
displayed. Highlight the unit in the list box and select OK to display data from that unit
control. Select Cancel to close the dialog box and maintain the original unit data display.
About Displays the program name and current revision level. Select OK to close
this dialog box.
Confirm Displays any time the user initiates a control action from an arm/run
pushbutton within the auto-calibrate display. The box displays an appropriate message
regarding the unit, regulator, control action, and OK and Cancel buttons. The default
action of this dialog box is Cancel.
Manual Setpoint Command Used to enter and confirm the user’s auto-calibrate
actuator setpoint command. The setpoint signal information displays in text. Enter the
desired setpoint in the edit box. Select OK to send the new actuator setpoint to the desired
regulator. Select Cancel to cancel the command. The default action for the Manual
Setpoint dialog box is OK.
Warning Displays any time the user selects Enable Commands. It displays a warning
about the auto-calibrate procedure. The dialog box displays OK and Cancel buttons. The
default action of this dialog box is Cancel.
Processor Selection Displays any time the user selects View Verify and more than
one processor has data. Only those processors that have verification data are displayed as
choices. Highlight the processor in the list box and select OK to display data from that
controller. Select Cancel to close the dialog box and maintain the original data display.

Control Constants Display
The HMI Control Constants Display displays the value of each of the control constants in
the selected unit. All control constants in the selected unit’s data dictionary are displayed.
From this display the user can call up the Control Constants Adjust Display to change
any constants that are adjustable.
The Control Constants Display has a header that includes:
• Site name
• Unit name
• Current time being sent from the unit
The list of points has three columns:
• Point name
• Value
• Units
There is an icon to the left of the Point Name to determine if the point is adjustable. The
icon is a plus sign if the point is adjustable, and the icon is a question mark if the values
from the three processors (R, S, and T) do not match. The question mark is also displayed
if the value is outside the minimum and maximum value. Both the plus sign and the
question mark can be displayed at the same time.
Menu Structure
Menu Command Use to
File Print Send what is on the display to a printer
Print Setup Select the desired printer and its setup
Exit Exit the Control Constants display
Edit Select Unit Select the unit (controller) with which the Control Constants display
communicates
Find Point Bring up the Find Point dialog box. From this the user can locate a point in
the list
Set Point Set the font that both the header and the data list uses
Set Default Set the font and column widths back to the system default
View Tool Bar Toggle the tool bar on and off
Status Bar Toggle the status bar on and off
Help About Control Constants Display the revision level of the Control Constants Display
The Control Constants Display can be invoked from a GeCssTci Command Prompt
window using a command line with a unit name. If a valid unit name is specified, the
Control Constants Display starts with data from that unit. If no unit is specified on the
command line and there is more than one unit in the system, the user is prompted to
select a unit. For example, use the following:
CONSTDSP /UNIT:T1

The header time tag displays the time tag of the oldest piece of data being displayed in the
data list. Before data has been received, the time tag reads No Valid Data. If the oldest
piece of data on the screen is more than five seconds old, the time tag is highlighted.
Changing a Control Constant

Only Control Constants with a plus next to them can be adjusted.
Ø To change a Control Constant
Control Constants Display
Control Constants Adjust Display

The HMI Control Constants Adjust Display allows the user to adjust the value of any
control constant that is adjustable. The display is a dialog application. The dialog
application must not be closed until the ramping of the control constant is finished. If it is
closed, the ramping stops at the current value. More than one Control Constant Adjust
Display can be active at a time. The display can be minimized at any time (including
while a point is being ramped).
The Control Constants Adjust Display can be run from the Start menu or from a GeCssTci
Command Prompt window using a command line.

Ø To start the Control Constants Adjust Display: from the Start menu, select
Turbine Control Maintenance (ST), <Unit Name>, and and Constants
Display.
or
Open a GeCssTci Command Prompt window (typically in the target unit’s

Configuration directory) and enter the command:
CONSTDSP /UNIT:<unitname>
If no pointname is specified, then a dialog box displays to enter a point. The format of
the command line argument is:
/POINT:<UNIT>:<POINT NAME>
The unit is required for multi unit sites, for example:
/POINT:T1:CSKATS:
The unit is optional if there is only one unit, for example
CONSTADJ /POINT:CSKATS Header Time tag
The Control Constants Adjust Display dialog box has a header that includes: Site Name,
Unit Name, and Current Time being sent from the unit. The header time tag displays the
time tag of the oldest piece of data being displayed. Before data has been received, the
time tag reads No Valid Data. If the oldest piece of data on the screen is more than five
seconds old, the time tag is highlighted.
The following information is displayed in the dialog box: Point Name, Current Point
Value (if the unit is a TMR, three values are displayed), Target Point Value, Ramp Rate
Value, Minimum Value (if it exists), and Maximum Value (if it exists).

The Display Pushbuttons
Pushbutton Color Description
Enter Target Gray with black text Displays the Enter Target dialog box
Start Ramp Green with black text Displays a dialog box asking if you really want to start the ramp. The button
is green with yellow text when the ramp is in action
Stop Ramp Red with black text Immediately stops the ramp
Step Change Green with black text Displays a dialog box asking if you really want to make the step change. A
step change can only be made when the unit is off line
Storage Update Green with black text Displays a dialog box asking if you really want to save all constants in
non-volatile memory

CONSTCHK - Constants Check
When a turbine control is reset CONSTCHK is a command line configuration utility that displays control constants that
or powered up, it reads the have a different value in the controller's RAM and the controller's non-volatile storage. It
control constant values out of is useful in determining which control constants in RAM have changed value since the
non-volatile memory and loads controller was last reset or powered up.
them into RAM. The controller
then runs using these RAM The Control Constant Adjust Display can dynamically change the contents of the RAM
resident values. resident control constants. Use of the Control Constants Adjust Display results in the
contents of the RAM and the contents of the non-volatile memory values being different.
CONSTCHK outlines the differences, giving a list of the changes that were made.
Operation
CONSTCHK is a command line program that is run from a GeCssTci Command Prompt
window. It needs one command line parameter, the name of the unit to check. If run with
no parameters or the /? parameter, it displays a help screen.
Normally the program reports only the values of control constants that have different
values between the RAM and the non-volatile memory. If the /ALL qualifier is used on
the command line, all values are displayed.
The following example displays a check of a Mark V unit. Two control constants were
found where the value in RAM was different than in non-volatile storage. The Mark V
uses an EEPROM for its non-volatile storage.
E:\Site_ST\UNIT1> CONSTCHK T1
...Site: HMI Development
...Unit: T1
...Time: 03–DEC—1997 11:58:15
... Name Units RAM (CSDB) EEPROM

...--------- -------- ------------ ------------
LK90PSEL "MW" 24.0 22.6
LK90SPIN "MW" 3.0 4.0
...There were 2 Control Constants with different values.
E:\Site_ST\UNIT1>

Diagnostic Counters Display
The Diagnostic Counters Display (DIAGC) provides information on internal control and
I/O board functions used for troubleshooting or statistical data gathering. This display
permits I/O board data not defined in the unit CSDB to be viewed. Not all data is defined
in the CSDB because either the data must be processed or scaled before it can be used by
the Turbine Control programs, or it is data created by the operating or communication
systems of the I/O boards for troubleshooting purposes.
This information is intended for debugging by experienced field and factory personnel.
This program is not intended for use by plant operators. No unit control functions are
available on this display.
The display features a split window with a tree view of the unit on the left and the
Diagnostic Counter data on the right. The tree view can hold and display one unit at a
time. Selecting a valid sub-type from the list under a unit/core/card in the tree view,
displays that sub-type Diagnostic Counter. That data is displayed until the user selects
a different sub-type or changes the unit.
File Type
The program reads the Site Directory CONFIG.DAT file to obtain the site information.
The program also reads the DIAGC.DAT file for each unit. This file can be located
in the Unit Configuration directory or in its PROM subdirectory. For the Mark V, the
DIAGC.DAT file is completed by the requisition engineer.
Note For Mark V, the DIAGC.DAT file should not be edited except by qualified
field personnel as part of hardware or software modifications to the unit control.
DIAGC.DAT files should never be copied from one unit to another.
The program can save the current DIAGC output to a text file. This text file can be
opened and viewed with notepad or other text-viewing program. DIAGC cannot be used
to open the text file.
Using the Diagnostic Counters Display Program

This section provides information concerning the use of the following functions:
• Starting the Diagnostic Counters Display program

• The Diagnostic Counters Display window
• Selecting a DIAGC display screen
• Interpreting the data

Executing Diagnostic Counters Display (DIAGC)
The Diagnostic Counters Display, DIAGC, can be run from the Start menu or from a
GeCssTci Command Prompt window.
Ø To start the Diagnostic Counters Display: from the Start menu, select
Turbine Control Maintenance (ST), <Unit Name>, and Diagnostic Counters.
or

DIAGC /UNIT:<unitname>
The following example specifies the unit name as T1:
DIAGC /UNIT:T1 The DIAGC Display can also be launched from the Windows® Start
Menu Turbine Control Maintenance (ST) section.
DIAGC - Tree View and Splitter Bar

Diagnostic Counters Display Window
The Tree View is on the left side of the display and the Diagnostic Counter data is on the
right. A movable splitter bar separates the two portions. The program can display and
update one set of Diagnostic Counter data at a time.
The Diagnostic Counters Tree View is a graphical window that depicts the hierarchy of
panel/core/card/sub-type in a tree structure. The Tree View can hold and display one unit
at a time. The Tree View window cannot be printed.
Navigation in the Tree View is accomplished with the keyboard or mouse. The
panel/core/card levels can be expanded or collapsed to reveal the Diagnostic sub-types
available to the user. Selection of a sub-type causes that sub-type Diagnostic Counter data
to be displayed in the Diagnostic Counter window. That data is displayed in the data area
until the user selects a different sub-type or changes the unit selection.
Diagnostic Counter Data Window and Splitter Bar
The Diagnostic Counter data window on the right side has three main regions, the Header,
the Legend, and the Data Area
The Header is a non-scrolling region and therefore cannot be scrolled out of the window.
Although this region can be turned off using the View menu, it is recommended that users
leave the Header visible at all times because of the process information displayed.

The Header program name, card, core and socket names all appear on the same line and
serve to uniquely identify the board being examined. The legend contains the sub-type
currently being viewed.
The Header time tag displays the operator interface time and updates whenever a valid
new message is received. If no valid messages are received for five seconds, the Header
time tag is highlighted.
As new data is received from the unit, the replies received counter is updated and
displayed. If there is an error in the number of bytes returned in a message from the
unit, the replies received field in the Header is highlighted to indicate the mismatch and
possible corruption of Diagnostic Counter data on the display.
The Legend displays the title of the current Diagnostic Counter sub-type. The Legend is
in a non-scrolling region and cannot be scrolled out of the window. Although this region
can be turned off using the View menu, it is recommended that users leave the Legend
visible at all times.
The Data Area is below the Header and Legend. The Data Area displays the strings for
the selected Diagnostic Counters sub-type. The value field in the Data Area is updated at
either 1 Hz or 4 Hz.
The time tag displayed in the Header reflects operator interface time when the last update
message was received. Unlike the Header and Legend, the information in the Data
Area can be scrolled with the vertical scroll bar. If the Header replies received field is
highlighted, the Diagnostic Counter data being displayed may not be valid.
Selecting a Diagnostic Counters Display

Selecting a particular display establishes a communication link to the board in question
and asks for the PROM data associated with this display. The Tree View displays an
exploded diagram of all the cores within the panel. Each core can be expanded into its
component boards and each board expanded into its diagnostics displays. Use the cursor
and keyboard to expand the desired core and board, then select the appropriate diagnostic
display for the board. The selection is highlighted with a check mark on the tree view
portion of the screen.
Interpreting Data
DIAGC is a diagnostic tool for firmware designers and field personnel only. Its purpose
is to assist firmware designers in the performance evaluation of the EPROM based
programming and to assist field personnel in problem diagnosis. While the program is a
display only program that poses no threat to the operation of the turbine control, it does not
provide Turbine Operation information and should be run by authorized personnel only.

Information for Board Designers
The following data types are supported for the Diagnostic Counters Display. Board
designers should refrain from using data types other than those listed here because they are
not supported. Type Hn converts signed to unsigned; type Sn converts unsigned to signed.
Data Code Ctype Conversion-Algorithm

ASCII A0 %s char* =&raw_data
Binary B1 %8s char* =itoa((char)raw_data,str,2)
B2 %16s char* =itoa( (int)raw_data,str,2)
Integer C1 %f double= (char) (raw_data) *gain +offset
C2 %f double= (int) (raw_data) *gain +offset
C4 %lf double= (long) (raw_data) *gain +offset
Fixed F2 %f double= (int) (raw_data) /32768*gain+offset
Sign/un H1 %2X %u %c uchar = (char) (raw_data) *gain +offset
H2 %4X %u uint = (int) (raw_data) *gain +offset
H4 %1X 1u ulong = (long) (raw_data) *gain +offset
Logical L1 %d int = (char) (raw_data)? 1 : 0
Real R4 %f double= (float) (raw_data) *gain +offset
Un/sign S1 %f double= (uchar) (raw_data) *gain +offset
S2 %f double= (uint) (raw_data) *gain +offset
S4 %lf DOUBLE= (ULONG) (RAW_DATA) *GAIN+OFFSET

Logic Forcing Display
Forcing a point from the Logic Forcing Display program changes or maintains the logic
state of the point (0 or 1) regardless of the permissives driving the 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.
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.
Warning
The Logic Forcing Display program always displays the currently forced points in the
controller. The list of forced points appears on the display at the top of the Data Area
when the program is displaying a blank Logic Forcing Display file. For existing files, the
Logic Forcing Display program displays the forced points at the end of the pointname list
in the Data Area. Forced Logic signals already appearing on the Logic Forcing Display
screen are not duplicated. If the list of points is larger than the Logic Forcing Display
window, scroll bars are enabled. Forced points reappear if deleted. Unforced points do not
disappear; their updated values appear on the next scan of data. The Logic Forcing Display
program allows forcing of logic data points for the currently selected controller only.
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 prior to taking any action.
Caution

File Structure
The Logic Forcing Display program stores its data in a special text format file with a .TXT
extension. Never edit the Logic Forcing Display files directly, use the Logic Forcing
Display program to open, modify, and save these files. Each unit has its own point list in
the data file. It can be useful to set up several different logic forcing files. These files are
typically located in the Unit Configuration directory, but may reside in any directory.
Logic Forcing Display files use Data Dictionary files for the point list available for use
in the display. Logic Forcing Displays obtain their values for these points directly from
the Data Dictionary.
Logic Forcing Display

Using the Logic Forcing Display Program
Creating and editing Logic Forcing Displays requires unique operations including loading,
creating, editing, and saving a Logic Forcing Display file. Performing these operations
requires using the drop-down menu options from the menu bar selections. Some of the
operations are available on the toolbar.

and protection should use the Logic Forcing functions. Improper
the control system.
Warning
This section provides information concerning the use of the following functions:
• Forcing and Unforcing Logic Signals

• Starting the Logic Forcing Display program and loading a Logic Forcing Display file
• The Logic Forcing Display window
• Navigating within a Logic Forcing Display screen
• Modifying a pointname
• Adding/deleting a pointname line
• Using the Command targets
• Printing the Logic Forcing Display screen
• Other options available
• Saving a Logic Forcing Display file
• Exiting 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.
2. 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 Logic Forcing Command
dialog box displays.
3. Select 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.
Selecting Cancel from the Logic Forcing Command dialog box cancels the forcing
command. The default is Cancel. This procedure for confirming a forcing action helps
prevent a false command from running.

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
Caution signals prior to 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 double clicking
on it. The line highlights.
2. Select the Unforce Single command target. The Execute Command dialog
box displays.
3. Select OK to unforce the signal, or Cancel to leave the signal forced. The default
action is Cancel.
Ø To unforce all forced logic signals

1. Select the Unforce All command target. The Execute Command dialog box
displays.
2. Select OK to unforce all forced logic signals in the controller, or Cancel to cancel
the unforce 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.
Caution
Starting the Logic Forcing Display

Ø To start the Logic Forcing Display: from the Start, menu select Turbine
Control Maintenance (ST)- <Unit Name>, and Logic Forcing.
or
Open a GeCssTci Command Prompt Window (typically in the target unit's

configuration directory) then enter the command: LFORCE
The Logic Forcing Display program is configurable from the command prompt; however,
configuration arguments are not necessary. Typing LFORCE by itself at the prompt
accesses the display program. The configuration arguments are:
/UNIT:
/FILE:
The /UNIT: argument opens the Logic Forcing Display for the unit requested. For
example:
LFORCE /UNIT:T1

where the unit name must be a valid unit. Selecting an invalid unit or no unit displays
the Unit Selection dialog box. Single unit sites ignore this argument and default to the
single unit.
The Logic Forcing Display program allows files to be passed directly to it from the
command prompt using the argument /FILE:. The /FILE: argument opens the Logic
Forcing Display program and loads the requested Logic Forcing Display file. For example:
LFORCE /FILE:LFORCE2.TXT
or for files located in other directories:
LFORCE /FILE:E:\Site_ST\RUNTIME\LFORCE2.TXT
This argument requires permission to read the file or directory. Entering an invalid
filename, invalid path or no filename causes an error dialog box to display. Upon
acknowledgment, a blank Logic Forcing Display file displays.
The Logic Forcing Display program automatically opens an untitled blank Logic Forcing
Display text file unless a filename is passed to it from the command prompt. Selecting
the menu bar option File and the Open command from the drop-down menu causes the
Open dialog box to display. All the *.TXT files located in the directory from which the
program was run display, along with the directory and drive. Selecting the file and then
OK, displays the requested Logic Forcing Display file. Opening *.TXT files in other
directories is possible using the Open dialog box and selecting the drive, directory, and
filename of the desired file and the OK button. Selecting Cancel in the Open dialog box
cancels the opening of a Logic Forcing Display file.
Loading a Logic Forcing Display File

There are three ways to load an existing Logic Forcing Display file. If the Logic Forcing
Display program is started from the command prompt, add the name of the file after
the Logic Forcing Display program execution command, LFORCE, using the /FILE:
argument. The extension .TXT must be included with the filename. For example,
LFORCE /FILE:[filename].TXT
where {filename}.TXT would be a Logic Forcing Display filename such as

LFORCE2.TXT.
To load an existing Logic Forcing Display file after starting the Logic Forcing Display
program, select the menu bar option File and the Open command from the drop-down
menu. 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.

If no existing file is specified when running the Logic Forcing Display program, a
default blank file loads. To create a new Logic Forcing Display file, select the menu
bar option File and the New command from the drop-down menu, or select the toolbar
button with the blank sheet of paper to display a blank Logic Forcing Display screen.
The blank Logic Forcing Display screen displays with the Logic Forcing Display file
title UNTITLED.TXT. This file opens blank each time, but only allows saving once
per directory. Saving subsequent copies of UNTITLED.TXT overwrites the existing
UNTITLED.TXT in the same directory. A new Logic Forcing Display file name should
be given to this file when saving using the File menu bar option and the Save As command
from the drop-down menu. Any logic point forced in the specific unit is displayed even if
there is no specific file selected.
Note Saving a Logic Forcing Display file without renaming it overwrites the old Logic
Forcing Display file data with the new file data. Exiting the Logic Forcing Display
program without saving loses changes to the file.

Logic Forcing Display Window
The Logic Forcing Display operates in a Windows environment. The Logic Forcing
Display program performs functions selected from drop-down menu options from the
menu bar or buttons on the toolbar. The title bar displays the filename currently in the
Logic Forcing Display program. The horizontal scroll bar allows viewing of display
screens that exceed the window’s boundaries.
The menu bar at the top of the screen incorporates several items common to Windows
applications along with special items associated with the Logic Forcing Display. A
summary of these items and their corresponding functionality is displayed in the following
table:
Logic Forcing Display Menu Items and their Functions
Menu Items Drop Down List Function Description
File New, Open, Close, Save, Save As, Print, Selects new or existing files, recently edited files, saves
Print Preview, Print Setup, {Filenames}.TXT, edited files, prints files, exits the Logic Forcing Display
Exit program.
Edit Insert Blank Line, Modify Line, Delete Line, Inserts, deletes and modifies display lines. Set fonts and
Set Font, Select Unit, Find selects units.
View Toolbar, Status Bar Edits window display to show or remove toolbar and status
bar.
Help Index, Using Help, About Demand Display Accesses Help screens.
The toolbar immediately beneath the menu bar corresponds to particular drop-down menu
options. The toolbar buttons allow shortcuts to common menu commands. Placing the
cursor over any of these buttons causes a pop-up explanatory text window (Tooltip) to
appear. Selecting the Help Cursor (arrow with a question mark) changes the cursor to
an arrow with a question mark. Selecting a subsequent item calls up Help information
for that item.
Logic Forcing Display Screen Window

The Logic Forcing Display permits the viewing and forcing of Logic signals. Opening
a window displaying a Demand Display screen allows for viewing analog signals and
monitoring system reactions to forcing Logic signals. The Logic Forcing Display screen is
made up of three main regions, the Header, the List View, and the Command Target area
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 COMPUTER 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, then 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 (…) displays 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 unit’s data, which is the unit listed in the Header. Entering the unit
number with a colon prior to the pointname, as in T2:{pointname}, displays the data from
the requested controller. The Logic Forcing Display program allows entering other text
into this field for commenting and separating sections of points.
The Processor Value field displays the Logic signal pointname values taken from the
<R> 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 displays
exactly as entered in the scale code table file. This field is blank for invalid pointnames,
but indicates the units for valid points without data in the Data Dictionary.
The Command Target area is on the right side of the Logic Forcing Display window.
There are four Arm/Run 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/Run targets appear green with black text and require a
confirmation prior to sending the force or unforce signal to the controller.
Navigating within a Logic Forcing Display Screen

There are several ways to navigate within the Logic Forcing Display program. Viewing
pointnames that are off the bottom or top of the screen is done with either the up and
down arrow keys on the keyboard, the page up and page down keys on the keyboard,
or the scroll up/down bar on the window.
Modifying a Pointname or Line

Ø To modify a Pointname or Line
1. From the Logic Forcing Display, highlight the desired line.
2. Select the menu bar option Edit, and from the drop-down menu, select the Modify
Line command , or
3. Select the Modify Line toolbar button.
4. Type the new pointname or line in the highlighted pointname field.
The Logic Forcing Display program allows the entry of invalid pointnames to
accommodate adding textual information to the Logic Forcing Display screen. The
Processor Value and Unit fields remain blank if an invalid pointname is entered. Selecting
File:Save makes the changes permanent.

Adding and Deleting a Pointname Line
The Logic Forcing Display program allows adding lines at any point in the display screen.
Ø To add or delete a Pointname line

1. From the Logic Forcing Display, highlight the line above the desired insertion
point.
2. Select the menu bar option Edit and from the drop-down menu, select Insert Blank
Line, or
3. Select the Insert Blank Line toolbar button.
4. The Logic Forcing Display program inserts a blank line below the highlighted line.
To modify the line, refer to If the display is empty, Insert Blank Line can be applied without first highlighting a
the Modifying a Line section. location.
Saving the Logic Forcing
Display file makes the addition The Logic Forcing Display program allows deleting lines. Highlight the pointname field
permanent. in the line to be deleted. Select the menu bar option Edit and the Delete Line command
from the drop-down menu, or select the Delete Line toolbar button. The line is deleted.
Saving the Logic Forcing Display file makes the changes permanent.
Note Deleting lines removes lines permanently. Exiting without saving the file is
the only way to undo the line deletion.
Using the Command Targets

The Logic Forcing Display command targets are Arm/Run targets requiring confirmation
of their action prior to performing the command. This procedure for confirming a forcing
action helps prevent a false command from running.
Ø To use the Command Targets

1. Select the Command Target. The Execute Command dialog box displays.
2. Click OK. The command runs.
To cancel the command, select Cancel. The default action is Cancel.
Printing from the Logic Forcing Display File

The Print command prints the Logic Forcing Display screen. Only the data currently
displayed on the screen can be printed.
Ø To print the Logic Forcing Display screen

1. From the Logic Forcing Display screen, select the menu bar option File and either
the Print or the Print Setup commands from the drop-down menu, or select the
toolbar button with the picture of the printer.
2. The Print dialog box displays.
3. Click OK. The data prints
Selecting Cancel cancels the print command. The Print Preview command previews the
page and allows accessing the Print dialog box.

Other Options
There are other options available in the Logic Forcing Display program. Selecting the
menu bar option Edit and the 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 and the 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.
Saving a Logic Forcing Display File

Ø To save a file
1. Select the menu bar option File and from the drop-down menu, select Save, or
2. Select the toolbar button with the picture of a disk
3. The Logic Forcing Display files are saved in the directory of the original file.
If the file is new, the Save As dialog box displays requesting a filename. If a new directory
is not selected, the Logic Forcing Display program saves the file in the directory from
which the program was run. Clicking the OK button after typing in a name saves the file
using the filename. Saving a file overwrites the previous file and all old information is lost.
To save new Logic Forcing Display files or to copy old files to new files with different
names, select the menu bar option File and the Save As command from the drop-down
menu. The Save As dialog box displays requesting a new filename for the file. The Save
As dialog box also allows entering different directories. If a new directory is not entered,
the Logic Forcing Display program saves the new filename in the directory from which
the program was run. Using an already existing filename overwrites the data in the old file
with the data from the new file.
Exiting the Logic Forcing Display Program

Selecting the menu bar option File and the Exit command from the drop-down menu exits
the Logic Forcing Display program. The Logic Forcing Display program requests whether
to save changes to any Logic Forcing Display file prior to exiting.

PVOTE - Prevote Data Display
The HMI Prevote Data Display allows a technician to view logic and analog I/O values
before the three independent processors have selected a value through voting. This display
is useful for troubleshooting voting mismatches or control I/O discrepancies. This display
only displays data. It has no control actions.
Operation
The Prevote Data Display has a header above a list of voted points. The header includes:
Site Name, Unit Name, and Current time being sent from the unit.
The list of points has six columns: Point Name, Voted value, R value, S value, T value, and
Units. This list of points can be scrolled to display the desired point. All points in the
data dictionary that are marked as voted are displayed in the list. The points are ordered
in the list according to their assigned offsets. A dash is displayed in the column heading
on each side of the processor name, for example -R-, if the data from that processor
is no longer valid.
Menu Structure
Button Menu Item Use to
File Print Send what is on the display to a printer.
Print Setup Select and setup the desired printer.
Exit Exit the Prevote display.
Edit Select Unit Select the unit (controller) with which the Prevote display communicates.
Find Point Bring up the Find Point dialog box. From this, the user can locate a point in the list.
Set Font Set the font for both the header and the data list.
Set Default Set the font and column widths back to the system default.
View Tool Bar Toggle the tool bar on and off.
Status Bar Toggle the status bar on and off.
Freeze Data Stop the update of the data on the screen. If the list is scrolled, the new entries are not
updated until the data is unfrozen.
Help About Prevote Display the revision level of the Prevote Data display.

Command Line Description
The Prevote Data Display can be run from the Start menu or from a GeCssTci Command
Prompt window using a command line with a unit name.
Ø To start the Prevote Data Display: from the Start menu, select Turbine
Control Maintenance (ST) , <Unit Name>, and Prevote Data .
or

PVOTE /UNIT:<unitname>
If a valid unit name is specified, the Prevote Display starts with data from that unit. If no
unit is specified on the command line and there is more than one unit in the system, the
user is prompted to select a unit. For example:
Header Time Tag

The Header Time tag displays the time tag of the oldest piece of data being displayed in
the data list. Before data has been received, the time tag displays No Valid Data. If the
oldest piece of data on the screen is more than five seconds old, the time tag is highlighted.
Prevote Data Display

DABUILD - Diagnostic Alarm Build
DABUILD is a Mark V specific program that configures the alarm text string for
diagnostic alarms. It is not part of the normal configuration process, it is used only after
special PROM updates. This program builds the template file, ALARMD.TPL, that is
used to create the master list of alarms, ALARM.DAT.
When the Mark V controller indicates a diagnostic alarm, it reports it with a diagnostic
alarm number. The HMI must be able to match that number to the diagnostic alarm
text to be displayed. This text information is read from the unit configuration directory
ALARM.DAT file, which contains the drop number and alarm text for each alarm. In
order to ensure that the drop numbers and alarm text match, the same file (DIAG.H) is
used to create the drops in the unit as is used by the HMI to create the template alarm text
file. DABUILD translates this file from the unit form to the HMI form.
DABUILD is a command line utility program. It reads the file that defines the diagnostic
alarms in the unit and creates the template diagnostic alarm text file for the HMI.
Ø To start the DABUILD command line utility program: open a GeCssTci

Command Prompt window (typically in the target unit’s Configuration directory)
and enter the command: DABUILD <filename>.
The file used is typically the DIAG.H file in the unit configuration directory, but you
can specify a different file as a command line parameter. If it is run with the parameter
/? it provides a help screen. The output from this program is a new version of the
ALARMD.TPL file.
Note DABUILD should only be run when directed as part of a PROM upgrade.
The following demonstrates the on-line help available:
E:\Site_ST\UNIT1> DABUILD /?
DABUILD - Diagnostic Alarm Text Builder for Mark V
This program is used to build the list of diagnostic alarm
text strings for a Mark V after a major upgrade. It uses
the Diagnostic Alarm header file (DIAG.H) as the source
of the text strings. This file is typically not required
on-site, but some major prom updates may require that
DABUILD be run on-site to redefine the Diagnostic Alarm
Text strings. This program will create the ALARMD.TPL
template file with the results.
COMMAND FORMAT: DABUILD [filename]
[filename] is the name of the file containing the
diagnostic alarm information, typically DIAG.H. If not
supplied on the command line, the user will be prompted
for the name of this file.
This program should only be used when directed as part of
a Mark V prom update procedure.
E:\Site_ST\UNIT1>

DDLOCATE - Data Dictionary Locate
DDLOCATE is a command line configuration program that decides the location of signals
in the Mark V CSDB (Control Signal DataBase). This program takes a list of the signals
that are needed and locates them in the proper section of the CSDB. It handles assignments
for both fixed locations, used for hardwired I/O points, and for floating locations, such as
software generated signals.
Each turbine controller has a CSDB which is the real-time database used in the controller.
All I/O signals are read and written from the CSDB, and all sequencing runs by reading
and writing CSDB signals.
When the controller is first created there are some fixed or permanent signals located in the
CSDB. These signals always exist, and cannot be renamed or moved. In addition, blocks
of signals are set aside for certain functions, such as Pushbuttons, Analog Setpoints, and
Control Constants. The set of signals that are voted is also determined, and regions are set
aside for spare logical and real numbers.
Note The size of each region is determined by the PROMS in the controller, and
cannot be changed in the field. If DDLOCATE indicates there are no more of a certain
type of signal (such as Pushbuttons or Control Constants) there is no way to add more
without a PROM change.
DDLOCATE uses this information, which is obtained from the PROM subdirectory, to
determine how to layout the rest of the signals in the CSDB. It does this by reading a set of
assignment files (*.ASG) that indicates the signals to be added to the CSDB. For each
signal to be added, the type of signal required determines which region of the CSDB is
used to store that signal. Hardwired I/O signals use the name of the input or output to land
the signal on an exact termination point on an I/O board. Software signals simply indicate
the type of signal and let DDLOCATE determine the exact location in memory. When
done, DDLOCATE writes out the final configuration of the CSDB, which is stored in
the UNITDATA.DAT file.
DDLOCATE is a command line utility, but is typically run using the MK5MAKE batch
file.
Ø To start the DDLOCATE command line utility: open a GeCssTci Command

Prompt window (typically in the target unit’s Configuration directory) and enter the
command: DDLOCATE <filename> <filename> …
It accepts as its command line parameters the list of assignment files (*.ASG) that contain
the signals for it to assign. Each time it runs it creates a new CSDB layout from scratch; it
is not used incrementally.
Note To incrementally add a signal, edit the *.ASG file to include the new signal
and rerun MK5MAKE.

When run it looks as follows:
E:\Site_ST\UNIT1>; DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG

------------ Opened PROM\UNITMAP.TPL file.
------------ Closed PROM\UNITMAP.TPL file.
------------ Opened file IO.ASG
------------ Closed file IO.ASG
------------ Opened file FACTORY.ASG
------------ Closed file FACTORY.ASG
------------ Opened file ALLOCSSP.ASG
------------ Closed file ALLOCSSP.ASG
------------ Opened file SITE.ASG
------------ Closed file SITE.ASG
------------ There were 1047 hardware and 478 software assign items found.
------------ Reading PROM\UNITDATA.TPL file.
------------ Reading PROM\UNITFREE.TPL file.
E:\Site_ST\UNIT1>
The typical system uses four assignment files for the list of signals used, as follows:
• IO.ASG contains the assignments for hardwired I/O points

• FACTORY.ASG contains assignments for factory supplied options
• ALLOCSSP.ASG contains structured software points, or points used for standard
options
• SITE.ASG contains site specific assignments, typically for customer use
The format of the assignment files is documented in the header of the SITE.ASG file, since
this is where field customization is done. Refer to this for specific information. The basic
format for the assignment files is as follows:
;HARDWARE ASSIGNMENTS
<hardware_name> <software_name> <scale_name>
;SOFTWARE ASSIGNMENTS
?<software_type> <software_name> <scale_name>
There is no required order in the *.ASG files, they are processed in the order that they are
read. Any line that starts with a semi-colon is treated as a comment line and ignored.
Hardware assignments land specific software signal names on specific I/O signals. To
do this a hardware_name is used to indicate the specific location to map the software
signal. The scale_name parameter defines how the signal should be scaled for display, and
must match one of the scale code names in the scale code files, either ENGLISH.DAT,
METRIC.DAT, HARDWARE.DAT, or CUSTOM.DAT.

Software assignments assign a spare signal in a specific region of the CSDB to the given
signal name. The software_type is used to indicate the region of the CSDB where
the signal should be stored. A list of the region types is included in the header of the
SITE.ASG file. The software types are of the format ?TCsss, where the letters are as
follows:
• The first letter is always a question mark (?) to indicate that this is a software
assignment.
• The second letter is either an L for a logic signal, or a V for a variable.
• The third character defines the controller in which to store the signal. The Mark V
uses a B for a signal that must be in the <C> (and optional <D>) controller, and a Q
for a signal in the <R> (and optional <S> and <T>) controller.
• The sss indicates a sub-class of signal. These subclasses include the following:
− <none> is a local, non-voted signal
− LS is a logic state command, only valid for logic signals
− PB is a Pushbutton command, only valid for logic signals
− PUB is a private (local) unsigned byte, only valid for logic signals
− AS is an analog setpoint, only valid for variable signals
− CC is a control constant, only valid for variable signals
In some cases an array of signals is needed. Each signal in the array has its own name,
but the entire array must be in continuous memory locations. This is done using an array
assignment in the form as follows:
;ARRAY ASSIGNMENT EXAMPLES
?<software_type> * Name1,Name2,Name3,Name4 <scale_name>
?<software_type> *4 Name1,Name2,Name3,Name4 <scale_name>
;Multi-line example
?<software_type> * Name1,Name2,Name3,Name4,Name5,Name6,
Name7,Name8,Name9 <scale_name>
An asterisk as the second word on the line indicates array assignments. This asterisk can
have an optional count of the number of signals to follow immediately after the asterisk.
The asterisk and the count should be one word. If the count is included, a warning is
issued if the required number of signals is not found. If no count is given, the number of
signals found is used as the number of signals in the array. The list of signal names must
be one word, with no white space between signal names. A comma is used to separate
each signal name. The list of signal names can be split over multiple lines by ending the
line with the comma, indicating that another signal name follows.

DDUTIL - Data Dictionary Utility
DDUTIL is a command line utility program that checks a unit's CSDB layout for obvious
errors. It does this by checking the UNITDATA.DAT file in the unit configuration directory
for cases where multiple signals share the same memory location, or two different signals
have the same name. It can also sort the UNITDATA.DAT file to put the signal names in
alphabetic order, making it easy to find signals when viewing or printing the file.
The UNITDATA.DAT file in the unit configuration directory defines the layout of the
signals in the unit's memory. However, The HMI does not consider the order of the signals
in the UNITDATA.DAT file. There are a few isolated conditions where a mistake in the
configuration can cause a signal to be defined multiple times. This can cause problems
since the name of a signal must uniquely define the signal's memory location in the unit.
DDUTIL scans the UNITDATA.DAT file looking for cases where multiple signals share
the same memory location, or separate memory locations share the same signal name.
If either of these cases is found, a warning message is displayed. Also if any invalid
characters are found in any of the file's numeric fields, a warning is issued.
If the SORT command line option is used, the original file is copied to the file
UNITDATA.BAK, and a new signal name sorted version of UNITDATA.DAT is written.
The sort is not performed if any invalid entries are found, but sorting can be done if
duplicates are found.
DDUTIL is a command line utility run from the unit configuration directory as part of the
standard MK5MAKE procedure.
Ø To start the DDUTIL command line utility: open a GeCssTci Command

Prompt window (typically in the target unit’s Configuration directory) and enter
the command: DDUTIL <optional>
If run with the /? command line parameter, a help screen is provided.
If no errors are found then no messages are generated during the scanning process. If the
SORT option was used, a message indicating that the file was sorted is printed. In the
following example, no errors were found:
E:\Site_ST\UNIT1> DDUTIL
E:\Site_ST\UNIT1>
In the next example, no errors were found, and the file was sorted in signal name order:
E:\Site_ST\UNIT1> DDUTIL SORT
SORTING COMPLETE: UNITDATA.DAT IS NEW FILE, UNITDATA.BAK IS

OLD.

MK5MAKE - Mark V Make
MK5MAKE is a batch file that contains the commands typically used when rebuilding the
CSDB layout for a Mark V unit. This batch file can be used to rebuild the CSDB layout,
recompile the unit's configuration tables, validate the unit's alarm list, and recompile
sequencing. These are the steps that are typically taken when adding or modifying signals
in the unit; MK5MAKE performs these steps in one command.
MK5MAKE is typically run when signals are added to the unit, or signal parameters
have been changed, such as the scale code. The MK5MAKE batch file simplifies
the configuration steps by running the various tools in the correct order. When run,
MK5MAKE performs the following steps:
• DDLOCATE is run to lay out the CSDB with the new signal definitions. It is run
using the following assignment files:
– IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, SITE.ASG
• DDUTIL is run to validate the new layout, and sorts the resulting UNITDATA.DAT
file
• The Table Compiler (TABLE_C) is run to recompile all tables downloaded to the unit
• The Alarm List program (ALARM_L) is run to validate the process alarm tables
The user is asked whether the sequencing should be recompiled. If the user replies Yes
or does not answer within 30 seconds, the sequencing is recompiled using the Sequence
Compiler (SEQCOMPL).
MK5MAKE is a command line utility that runs from the unit configuration directory.
Ø To start the MK5MAKE command line utility: open a GeCssTci Command

command: MK5MAKE
It can take one optional command line parameter. This parameter is passed directly to the
Table Compiler (TABLE_C) and is used to change the scale code set from the default of
ENGLISH to a user specified scale code set. For example, to build using the METRIC
scale code set, the following would be used:
MK5MAKE / scale=METRIC.SCA
MK5MAKE creates a log file that is basically a list of the outputs from running each
individual tool. This file is stored as the MK5MAKE.LOG file in the unit configuration
directory. The following example demonstrates this batch file in operation:
E:\Site_ST\UNIT1> MK5MAKE
Point assignments are now being made using IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, and SITE.ASG
------------ Opened PROM\UNITMAP.TPL file.
------------ Closed PROM\UNITMAP.TPL file.
------------ Opened file IO.ASG
------------ Closed file IO.ASG
------------ Opened file FACTORY.ASG
------------ Closed file FACTORY.ASG
------------ Opened file ALLOCSSP.ASG

------------ Closed file ALLOCSSP.ASG
------------ Opened file SITE.ASG
------------ Closed file SITE.ASG
------------ There were 1047 hardware and 478 software assign items found.
------------ Reading PROM\UNITDATA.TPL file.
------------ Reading PROM\UNITFREE.TPL file.
The new UNITDATA.DAT file is now being validity-checked and sorted. SORTING
COMPLETE: UNITDATA.DAT is new file, UNITDATA.BAK is old. The Table Files are
now being re-compiled.
: Table compiler for Mark V AP1 files. (Version 4.9)
Loading data dictionary.....5920 points loaded.
TABLE_C processing complete.
The Alarm Listing File (ALARM.LST) is now being created.
Loading data dictionary alarm.....467 alarm points loaded.
Would you like to re-compile the Control Sequence Program at this time?
(You have 30 seconds to answer Yes or No; a failure to respond will cause the
Control Sequence Program to be re-compiled by default.)
Please enter Y[es] or N[o]: Y
Mark V - Control Sequence Program Compiler
Revision Date: Mar 27 2009 at 15:23:51
Compiled on: Thu May 07 16:30:41 2009
---> Loading the signal data base
---> Loading the BBL and PRIM block definitions
... BBL revision Major := 7 Minor : 1
---> <Q>; segment: F:\UNIT1\SEQ_TRN1.src

... 177 rungs processed
---> segment: F:\UNIT1\SEQ_B.src
---> Creating the <Q> AP1 sequencing file: E:\Site_ST\UNIT1\SEQ_Q.AP1
---> Creating the AP1 sequencing file: E:\Site_ST\UNIT1\SEQ_B.AP1
-------- CSP Compiler Finished --------
The results of making point assignments, validity-checking and sorting the new
UNITDATA.DAT file, re-compiling the Table Files, rebuilding the alarm listing
file, and re-compiling the Control Sequence Program have been stored in
MK5MAKE.LOG.
E:\Site_ST\UNIT1>;

ALARM_L - Alarm List
ALARM_L is a command line utility program that generates a printable list of all of the
process alarms that a controller can generate, complete with all the signal names and alarm
text. The resulting alarm list file, ALARM.LST, includes a warning section if there are
any alarms that do not have any associated alarm text strings defined.
ALARM_L is used with the Backup Operator Interface (BOI) because the BOI only
indicates a process alarm's drop number. The ALARM.LST file listing created by
ALARM_L is printed and hung on the door of the Mark V control. This provides a
way to look at the process alarm number and see the alarm text, as well as the name of
the signal that created that alarm.
This alarm listing is also useful when connecting the HMI to a Distributed Control System
(DCS), since it provides a list of all of the process alarms generated by each turbine control.
The last section of the alarm list, if needed, defines all of the alarms that have been defined,
but do not have any alarm text strings defined. This is useful during unit configuration
to check for alarms without text strings.
Operation
ALARM_L is a command line utility that is run from a GeCssTci Command Prompt
window in the unit configuration directory.
Ø To start the Alarm_L command line utility: open a GeCssTci Command

command: Alarm _L
It takes no command line parameters, and generates the ALARM.LST file containing the
output from the program, as displayed in the following example:
E:\Site_ST\UNIT1> ALARM_L
Loading data dictionary alarm.....576 alarm points loaded.
E:\Site_ST\UNIT1>
SAMPLE OUTPUT (ALARM.LST)
DROP# SIGNAL NAME ALARM TEXT
--------------- -------------------–--- --------------------------------------------------
0 L30DIAG DIAGNOSTIC ALARM
1 L30FORCED FORCED LOGIC SIGNAL DETECTED
2 L4ETR_FLT PROTECTIVE MODULE ETR RELAY TROUBLE
3 L86MP MASTER PROTECTIVE STARTUP LOCKOUT
4 L48 TURBINE INCOMPLETE SEQUENCE
5 L83HOST OVERSPEED TEST MODE SELECTED - HP
6 L83LOST OVERSPEED TEST MODE SELECTED - LP
7 L12H_P_ALM PROTECTIVE MODULE HP OVERSPEED - SD
8 L12L_P_ALM PROTECTIVE MODULE LP OVERSPEED - SD
9 L86MAN_SYNC MANUAL SYNCHRONIZING LOCKOUT
10 L86S AUTO SYNCHRONIZING LOCKOUT

CONSTSET - Constants Set
CONSTSET is a Mark V configuration utility to make all control constants adjustable,
and to set the default ramp rate for each control constant.
In previous generations of Operator Interfaces, all control constants were adjustable

through the Control Constants Display. The HMI supports a user-controlled list of the
control constants considered adjustable, and the ones that are not. In addition, the ramp
rate can be defined for each control constant that is adjustable.
CONSTSET creates a default control constant configuration where all control constants
are defined as being adjustable, and the default ramp rate is the same rate as used in the
IDP Operator Interface. It is used in Mark V HMI applications to emulate the previous
generation of operator interface, without having to configure each control constant by
hand.
Note In the WorkstationST application the CONSTSET.DAT file is still required, but
an option to automatically generate the default values at Data Dictionary load time has
been added. Using this new option eliminates the need for running the CONSTSET
program. Refer to the application information at the end of this section for more details.
Operation
CONSTSET is a command line configuration utility. It requires one command line
qualifier, the name of the Mark V unit, supplied using the /UNIT=<unit_name> qualifier.
Ø To start the CONSTSET command line utility: open a GeCssTci Command

command: CONSTSET /UNIT: <unitname>.
If run with no parameters or the /? parameter, a help screen is displayed as shown in

the following example.
E:\Site_ST\UNIT>1CONSTSET /?
This program creates a CONSTSET.DAT file for a Mark V unit.
The CONSTSET.DAT file defines which control constants are
adjustable, and defines the ramp rate for each adjustable
constant. The file created defines all control constants as
adjustable. The ramp rate is set to approximately one display
unit per second, where the display unit is defined by the
control constant's scale code.
COMMAND FORMAT: CONSTSET /UNIT:<unitname>
E:\Site_ST\UNIT1>

A sample of the CONSTSET.DAT file, the output of the CONSTSET program, is
displayed in the following example:
; CONSTSET.DAT -- Control Constants Adjustment Settings File

;
;
; This file contains the adjustable constants for the unit.
;
;
; Point Engr Units Ramp Rate Min Value Max Value
Name
AFKQG "CNT09" 0.1
AFKQPC "CNT05" 0.001
AQK0_B "#/sec" 0.01
AQK0_E "#/sec" 0.01
<…and so on…>
Application Information
In the WorkstationST application the unit can generate the Mark V default ramp rates
without using the CONSTSET program. An option in the CONSTSET.DAT file causes the
Data Dictionary loader to recalculate the default ramp rates and set each control constant
to be adjustable while loading the points into the Data Dictionary. This program has
the advantage that any additions to the control constants, or new control constants, are
automatically picked up when TCI is restarted, with no additional configuration work.
To use this new option, create a CONSTSET.DAT file that contains as its first data line a
line with the option name *MARK V_DEFAULT. This special line triggers the Dictionary
Loader to set every control constant as adjustable, and set the ramp rate according to the
default scale code table. The results are the same as the results of running CONSTSET.
If desired, additional lines can be added to the CONSTSET.DAT file to override these
defaults. This allows a user to make some control constants non-adjustable or to change
the default ramp rate.
Note Make sure that any lines changing the defaults are after the *MARK V_DEFAULT
line, otherwise the lines are overridden when the defaults are computed.

The following example displays a CONSTSET.DAT file where the default values were
computed when TCI started:
;
;CONSTSET.DAT - CONTROL CONSTANT ADJUSTMENT SETTINGS
;
;This will set all control constants to be adjustable
;with a ramp rate of one display digit per second.
;
*MARKV_DEFAULT
;
;Add any overrides desired here
;

EPA Log Configuration
To define Mark V Control Data Points for the EPA screen, the user must modify the
EPA_Q.SRC source file in the Unit Configuration directory. With the use of the notepad
editor, control data points can be added or removed from the file. The following is a
sample EPA_Q.SRC source file:
; ----------------------------EPA_Q.SRC-------------------------
; Note that the TIME column header does not have to be defined
in this file.
: The header is automatically created when the program is run.
;
;SIGNAL NAME
; -----------------
DWATT
CTIM
TTXM
WXJ
WXC
FQG
FQL
CMHUM
;END OF FILE
Although any valid Mark V data point can be defined for the EPA Display, it is required
that both WXJ (ACTUAL FUEL/WATER-STEAM RATIO) and WXC (required
FUEL/WATER-STEAM RATIO) control data points be included in all EPA displays. In
addition, it is required that the points WXJ and WXC be defined for the fourth and fifth
positions (from the left) of the display respectively. Therefore, they must be in the fourth
and fifth positions from the top in EPA_Q.SRC.
Once the correct points have been added to the EPA_B.SRC file, the file must be compiled
and downloaded to the <C> processor.

SEQCOMPL - Sequencing Compiler
The Control Sequence Compiler is a separate command line program that compiles
Control Sequence Program (CSP) segments into one CSP for use in the controller. The
Sequence Compiler compiles only the sequencing source segments (*.SRC) listed in
MSTR_SEQ.CFG, the compiler configuration file. The Sequence Compiler is a command
line program, not a Windows program.

and protection should use the Sequence Compiler. Improper
the control system.
Caution
File Structure
The output of the Sequence Compiler is a set of *.AP1 files that can be downloaded to the
controller. The downloadable sequencing filenames are SEQ_B.AP1 and SEQ_Q.AP1
- one for sequencing run in the processors and one for sequencing run in the <Q>
processors. The program always writes a text log file, MSTR_SEQ.LOG in the unit
configuration directory.
Along with the segment source files, the Sequence Compiler uses several unit specific files
that contain signal name database definitions and definitions of the available application
building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF files are ASCII files that detail
the programming blocks available for the particular unit control. UNITDATA.DAT is a
data dictionary file the Sequence Compiler uses to check the validity of pointnames used
in the segment source files.
Sequence Compiler Block Diagram

Running the Sequence Compiler
The Sequence Compiler is a command line utility.
Ø To start the Sequence Compiler command line utility: open a GeCssTci

Command Prompt window (in the target unit’s Configuration directory) and enter
the command: SEQCOMPL.
The Sequence Compiler creates a listing, MSTR_SEQ.LOG, of the errors found in the
segments. These errors must be resolved by using the Sequence Editor program to make
appropriate changes to the sequencing source files (*.SRC). The *.AP1 output files are
not produced until the Sequence Compiler runs error free. A sample Sequence Compiler
is as follows:
E:\Site_ST\UNIT1> SEQCOMPL
Mark V – Control Sequence Program Compiler
Revision Date: Mar 27 2009 at 15:23:51
Compiled on: Thu May 07 16:30:41 2009
---> Loading the signal data base
---> Loading the BBL and PRIM block definitions
...BBL revision Major := 7 Minor : 1
---> <Q> segment: F:\UNIT\SEQ_TRN1.src
---> <Q> segment: F:\UNIT\SEQ_TRB1.src
---> <Q> segment: F:\UNIT\SEQ_TRB2.src Frequency := 2 Skew 0
---> <Q> segment: F:\UNIT\SEQ_TRB3.src Frequency := 2 Skew 1
---> segment: F:\UNIT\SEQ_TRN1.src
---> segment: F:\UNIT\SEQ_B.src

---> Creating the <Q> AP1 sequencing file:
E:\Site_ST\UNIT\SEQ_Q.AP1
---> Creating the AP1 sequencing file:
E:\Site_ST\UNIT\SEQ_B.AP1
--------CSP Compiler Finished ----------
Master Sequencing Configuration File

The Master Sequencing Configuration File, MSTR_SEQ.CFG, governs the sequencing
source files that are compiled for each controller in the unit, and at what rate the segments
are run within the controller. MSTR_SEQ.CFG is a text file that can be modified by
any word processor.
Only qualified personnel knowledgeable about turbine

control and protection should modify the Master Sequencing
Configuration File, MSTR_SEQ.CFG. Improper use can
adversely affect the control and protective features of the control
Caution system.
The file is located in the unit configuration directory, typically E:\Site_ST\UNITn. The
file features are as follows:
• A # character denotes a field to be processed.

• The #LIST directive causes the compiler to produce a listing file MSTR_SEQ.LST.
This is a text file, which can be viewed with any word processor. It is a text
representation of the AP1 file to be downloaded to the controller. Typically, this
directive is preceded by a ‘.’ to convert it to a comment.
• The #BBL_REVISION contains the revision of the \PROM\BIGBLOCK.DEF file.
This number must match the proms in the unit control. If not, the new AP1 file is not
able to run after it is downloaded. The BIGBLOCK.DEF file revision must match the
prom revision in the controller.

The following is a sample MSTR_SEQ.CFG Sequence Compiler Configuration File for
Mark V:
----------------------------------------------------------------
MSTR_SEQ.CFG: Configuration file for sequencing compiler
----------------------------------------------------------------
.#LIST
----------------------------------------------------------------
Major Minor UBL Major UBL Minor
rev rev rev rev
#BBL_REVISION 7 1
----------------------------------------------------------------
<R>, <S>, and <T> Segments
----------------------------------------------------------------
#<Q>_SEGMENTS
Segment Frequency Skew within Frequency
name power of 2 (units of 1/16 sec)
(>0)
#SEGMENT SEQ_TRN1 1 0
#SEGMENT SEQ_TRB1 1 0
----------------------------------------------------------------
<C> and <D> Segments
----------------------------------------------------------------
#_SEGMENTS
Frequency Skew within Frequency
power of 2 (units of 1/16 sec)
(>0)
#SEGMENT SEQ_B 1 0
----------------------------------------------------------------
#END

In the sample listing the sequencing information is grouped as follows:
• The #Q_SEGMENTS tag indicates sequencing for the <R>, <S>, and <T> processors.
• The #B_SEGMENTS tag indicates sequencing for the <C> and <D> processors,
(Mark V only)
• The #END tag indicates the end of the document information.
The following example demonstrates the Frequency and Skew features:
Segment name Frequency n power of Skew within scan rate

2 (>0) (units of 1/16 sec)
W 1 0
X 2 0
Y 2 1
Z 8 3
The Frame Rate of the Mark V is 16, and the frequency parameter denotes the period in
frames for the segment. To calculate the execution rate use the following formula:
Execution rate in Hz for a segment = Frame Rate / Frequency
16 / 2 = 8 Hz
Using the above configuration yields segment execution at the following Mark V
frequencies and skews, where each occurrence of a letter represents the execution time:
The frame rate is 16 Hz so a maximum of 16 segment executions per second are possible.
The execution rates are as follows:
• Segment W is run every frame, for a 16 Hz execution.

• Segment X is run every two frames, for an 8 Hz execution.
• Segment Y is run every two frames, for an 8 Hz execution, and is skewed by one
frame.
• Segment Z is run every eight frames, for a 2 Hz execution, and is skewed by three
frames.
• At Frame #0, the segments W and X run.
• At Frame #1, the segments W and Y run.
• At Frame #3, the segments W, Y, and Z run.

SEQDOCMT - Sequencing Documentor
The Control Sequence Documentor is a separate command line program that produces a
CSP control document. The CSP document is a text file that contains a representation of
the CSP control program, and is used by field service and maintenance personnel to check
out and debug the controller. It is also used as a hard copy to document the CSP.
The Control Sequence Documentor uses only the sequencing source segments (*.SRC)
listed in MSTR_SEQ.CFG, the compiler configuration file.
File Structure
The CSP Documentor program produces two files. The first, CSP.PRN, is a complete
representation of the control. The second, CSP_XREF.PRN, is a signal name
cross-referencing document. Both files are located in the unit configuration directory.
CSP.PRN
The CSP.PRN document is a text file pre-formatted with page breaks to form a complete
document. The CSP.PRN is a complete representation of the unit CSP. It can be viewed
with any word processor with a fixed pitch font with line drawing characters. It is best to
print this document with the CSP Printer program as it adapts the format of the document
to the selected printer. Each page of the document begins with a header displaying the
segment name, date, and page number. Each rung starts with a rung number followed
by a graphic representation of the rung and finishing with signal and cross-referencing
information. More than one rung can display on any page. The page number represents
the page number within the segment.
The following is a sample CSP print output:
Control Sequence Document for Segment

E:\Site_ST\UNIT_EA\SEQ20_1.SRC
Tue Nov 18 13:55:02 1997 Page - 34
<< Rung Number 50 >>>

GP2SEL -- SELECTED GP2* VALUE USED IN SEQUENCING psi
SEQ20_1 39 SEQ20_1 40 SEQ20_1 42 SEQ20_1 49 SEQ20_1 50
SEQ20_1 52 SEQ20_1 59 SEQ20_1 60 SEQ20_1 62 SEQ_10GG 52
SEQ_10GG -60 SEQ_10GG 64
GP3PFF -- PILOT TRIM VALVE P3 FEED FORWARD psi
SEQ20_1 -49 SEQ20_1 50 N/D
GP3T2_PFFX -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD AUX
SEQ20_1 -50 SEQ20_1 51
<<< Rung Number 51 >>>
GP3T2_PFF -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD

N/D
SEQ20_1 -51 SEQ20_1 52
GP3T2_PFFX -- PILOT TRIM VALVE P3/P2 RATIO FEED FORWARD AUX
N/D
SEQ20_1 -50 SEQ20_1 51
RZERO -- FLOATING POINT CONSTANT N/D <0.0 N/D>
SEQ20_1 18 SEQ20_1 31 SEQ20_1 38 SEQ20_1 41 SEQ20_1 48
SEQ20_1 51 SEQ20_1 58 SEQ20_1 61 SEQ_80 18 SEQ_80 43
SEQ_40 32 SEQ_10GG 66

CSP_XREF.PRN
The CSP_XREF.PRN document is a text file pre-formatted with page breaks to form a
complete document. It is a cross-reference document containing a list of signal names
with the segment and rung number where the signal is used. It can be viewed with any
word processor having a fixed pitch font. To print this document it is best to use the CSP
Printer program as it adapts the format of the document to the selected printer.
Along with the segment source files, the Control Sequence Documentor uses several
unit specific files that contain signal name database definitions and definitions of the
available application building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF files are
ASCII files that detail the programming blocks available for the particular controller.
UNITDATA.DAT is a data dictionary file that contains the pointnames and types used in
the segment source files. *.PIC files are used for the primitive and BBL block graphics.
*.SCA files contain the engineering units. The LONGNAME.DAT file contains the
corresponding signal long names. A CSP_XREF.PRN Sequence Documentor output
example is as follows:
Unit Master Cross Reference - Page 4 Fri Jan 31 10:53:51 1997
CDPSUMAVGA -- CDP VALVE LVDT A SECONDARY SUM AVERAGE V RMS

SEQ_CAL -3
CDPSUMAVGB -- CDP VALVE LVDT B SECONDARY SUM AVERAGE V RMS
SEQ_CAL -3
CDP_CUR -- CDP BLEED VALVE SERVO DRIVER FEEDBACK <R2> QTBA-033 %
SEQ_640 63
CDP_CUR_REF -- CDP BLEED VALVE SERVO DRIVER OUTPUT %
SEQ_640 63 SEQ_10GG -57
CDP_ERR -- CDP BLEED VALVE DEMAND POSITION ERROR %
SEQ_640 63 SEQ_10GG -57
CDP_ERRABS -- ABSOLUTE VALUE OF CDP_ERR %
SEQ_640 -63
CDP_NBIAS -- CDP BLEED VALVE NULL BIAS BASED ON CDPSEL %
SEQ_10GG -57
CDP_NSC -- CDP BLEED VALVE SERVO CURRENT NULL COMPENSATION %
SEQ_10GG 57
CDP_POS_DMD -- CDP BLEED VAVLE POSITION DEMAND %
SEQ20_1 -23 SEQ_10GG 57
CHIP_AGB -- ohms
SEQ_640 76
CHIP_BSUMP -- ohms
SEQ_640 76
CHIP_CSUMP -- ohms
SEQ_640 76
CHIP_DSUMP -- ohms

SEQ_640 76
CHIP_TGB -- ohms
SEQ_640 76
CPCVAVG -- BACKUP RATIO OF SPECIFIC HEATS (CP/CV) N/D
SEQ_0 -14 SEQ_640 8
CPCVMAN_PV -- PREVIOUS VALUE OF MANUAL SELECT CP/CV RATIO LOGIC
SEQ_640 -8
CPCVRATEVAL -- N/D
SEQ_0 -14 SEQ_640 -8
CPCV_MAN -- RATIO OF SPECIFIC HEATS (CP/CV) FOR MANUAL SELECTION N/D
SEQ_640 8
CPCV_PVGOOD -- RATIO OF SPECIFIC HEATS (CP/CV) FAULT TIME DELAY N/D
SEQ_640 -8
CPCV_PVINP -- PREVIOUS VALUE OF CP/CV RATIO INPUT N/D
SEQ_640 -8
CP_CV -- GAS FUEL RATIO OF SPECIFIC HEATS N/D
SEQ_0 -14 SEQ_0 -15 SEQ_640 8
CP_CV_SEL -- SELECTED VALUE OF CP_CV USED IN SEQUENCIN N/D
SEQ_0 -14 SEQ20_1 42 SEQ20_1 52
SEQ20_1 62 SEQ_640 -8 SEQ_10GG 68
CS3 -- INTERMEDIATE HEAT SOAK GAIN N/D
SEQ_20 -4
D30T2A -- ALMTXT:'COMPRSR INLET TEMP(T2A) SENSOR FAILED' AL 37 LOGIC
SEQ_40 -2
D30T2B -- ALMTXT:'COMPRSR INLET TEMP(T2B) SENSOR FAILED' AL 38 LOGIC
SEQ_40 -2
D30T2DIFF -- ALMTXT:'T2A & T2B SENSOR DIFFERENTIAL' AL 42 LOGIC
SEQ_40 -2
To initiate the compiling program, select the Control Sequence Documentor from the
Turbine Control Maintenance (ST) menu or type SEQDOCMT in a GeCssTci Command
Prompt window in the Unit Configuration directory.
Ø To start the compiling program: from the Start menu, select Turbine Control
Maintenance (ST), <Unit Name>, and Control Sequence Documentor
or

Configuration directory) and enter the command: SEQDOCMT.

The Sequence Documentor has four possible parameters. Run SEQDOCMT /? for a
definition of the parameters.
For example, a valid command line with all possible parameters is as follows:
E:\ E:\Site_ST\UNIT1> SEQDOCMT.EXE METRIC.SCA N -LOG

E:\Site_ST\UNIT1
• The first parameter is the scale code file name; the default is ENGLISH.SCA.
• The second parameter is Y or N where:
− N causes the documentor to skip cross-referencing
− Y is the default to do cross-referencing
• The third parameter is -LOG or -N. -LOG tells the documentor to produce a log file
SEQDOCMT.LOG. The default is -N for no log file.
• The fourth parameter is the path to the unitn directory. The default is to use the
current default or working directory.
The Sequence Documentor can display error messages during operation. These errors
must be resolved using the Sequence Editor program to make appropriate changes to the
sequencing source files, *.SRC, or other unit configuration files as needed.
Note Run the Sequence Compiler any time changes are made to the files in the unit
configuration directory.

SEQEDIT - Sequencing Editor
CSP, the Turbine Control's application software, uses a programming language known
as Big Block Language (BBL). BBL is a relay ladder logic-based software structure that
defines data flow and function execution. A series of rungs containing combinations of
comments, relay ladder diagrams, Primitives, and Big Blocks makes up the software
structure. The Sequence Editor is the application tool for making control changes by
modifying the CSP. The Sequence Editor does not directly modify the control code
running in the controller. It is an off-line tool, so its changes are made to a source file only.
After saving the changes made with the Sequence Editor, the CSP must be compiled by
the Sequence Compiler and downloaded to the controller. The Sequence Compiler and
download functions are described later in this document.
A segment consists of a set of sequential rungs. The Control Sequence Editor allows
four different types of rungs as follows:
• RLD rungs, which are relay ladder diagram rungs.

• PRIMITIVE rungs, which combine RLD operations with a primitive function block
call.
• BBL rungs, which are rungs without RLD operations, but with a Big Block call. Big
Blocks are application modules that perform standardized control functions.
• COMMENT rungs, which are rungs containing only text, usually identifying
important information about the sequencing or segment.
The Sequence Editor creates new CSP segments or edits existing ones. Once the Sequence
Editor creates the segment source files, the Control Sequence Compiler compiles
them into the CSP for downloading to the controller. The compiler configuration file,
MSTR_SEQ.CFG, selects the segments to compile and defines a unique scan rate and
execution offset for each segment. The downloaded CSP segments provide the controller
with the parameters and instructions on how to control the process.
File Structure
The Sequence Editor operates on segment source files within the Unit Configuration
directory. These files have a *.SRC extension. The CSP segment source files have a text
format. Never edit the segment source files directly, use the Sequence Editor program
to open, modify, and save them.
Note Other source files in the unit configuration directory have a *.SRC extension that
are not CSP segment source files. While it is possible to open these files, they are not
sequencing files and their contents could be overwritten if the user attempts to modify
and save them from the Sequence Editor.
Along with the segment source files, the Sequence Editor uses several unit specific files
that contain signal name database definitions, and definitions of the available software
building blocks. PRIMITIVE.DEF and BIGBLOCK.DEF are ASCII files that detail the
programming blocks available for the particular unit control. UNITDATA.DAT is a data
dictionary file used by the Sequence Editor to check the validity of pointnames used in
the segment source files. It is usually a good idea to restrict the editing of sequencing
source files to a single unit at a time. This is because different units may have different
functions defined in their associated BIGBLOCK.DEF and PRIMITIV.DEF files and
different signals defined in their UNITDATA.DAT files.

Modification of these files is not necessary, and not
recommended, as their contents correlate directly to the contents
of the unit control’s block library. If a block is added, modified,
or removed from the unit control, the factory provides new
definition files along with new files for the controller’s block
Caution library.
Control Sequence Editor File Structure
Using the Control Sequence Editor

Editing a segment requires several standard operations. These operations include loading
a segment from the disk, creating a new segment, finding an existing rung, creating a
new rung, and saving a modified segment to a disk. Using either the drop-down menu
options from the menu bar selections or the buttons on the toolbar performs the following
operations:
• Starting the Control Sequence Editor and Loading segments

• Opening the Control Sequence Editor window
• Navigating within segments
• Editing rungs
• Selecting rungs
• Copying rungs
• Moving rungs
• Adding or deleting rungs
• Creating rungs
• Viewing multiple segments
• Saving a segment
• Exiting the Control Sequence Editor
Starting the Control Sequence Editor

Ø To start the Control Sequence Editor: select the Control Sequence Editor
icon.

or

Configuration directory) and enter the command: SEQEDIT.
Loading an Existing Segment

The Sequence Editor loads existing segments in three ways. If the Sequence Editor starts
from the command prompt, type the name of the segment after the Sequence Editor
execution command, SEQEDIT. Include the source extension, .SRC with the segment
name. For example, enter:
E:\Site_ST\UNIT1> SEQEDIT [Segment name].SRC
where {Segment name}.SRC is a sequencing segment filename such as SEQ_160.SRC.
To load an existing segment after starting the Sequence Editor, select the menu option
File:Open command from the drop-down menu. The Sequence Editor provides a list of
files with .SRC extensions. Select the desired file and press enter to load the segment.
Selecting the toolbar button with the picture of an open file also provides a list of existing
files. To load a recently edited segment, select the menu bar option File, and then the
segment name from the drop-down menu.
Note Not all the .SRC files are sequencing segment source files.
Loading a New Segment

If no existing file is specified when the Sequence Editor starts, a blank screen displays. To
start a new segment window, select the menu bar option File:New command from the
drop-down menu.
Note Exiting a new segment file without saving it loses the file.
The Control Sequence Editor Window

The Sequence Editor operates in a Windows environment. The Editor performs functions
selected from drop-down menu options from the menu bar or buttons on the toolbar:
• The titlebar displays the filename currently in the Sequence Editor.

• The Sequence Editor opens each segment in a separate segment window that displays
the segment one rung at a time.
• RLD rungs display on an 8x8 matrix.
• Primitive rungs display using a 4x8 permissive matrix and a tile representation of
the primitive.
• Big Blocks display as a tile representation of the Big Block.
• The horizontal and vertical scroll bars allow viewing portions of rungs and blocks
that exceed the segment window boundaries.

The Sequence Editor Window Displaying an RLD Rung
The menus and toolbar at the top of the screen incorporate items common to Windows
applications along with special items associated with the Editor. The toolbar immediately
beneath the menu bar corresponds to particular drop-down menu options. The toolbar
buttons allow short cuts to common menu commands.
Navigating Within a Segment Window

Individual rungs make up the sequencing segments. The top right-hand corner of the
segment window displays the rung number. Navigate between the rungs using the
drop-down menu options from the menu bar, the toolbar buttons, or the page up and
down keys on the keyboard. The Edit:Find menu selection locates a signal name or block
name within a given segment. No tools are provided to search all sequencing segment
source files.
Editing an Existing Rung

The Editor allows for editing existing rungs as follows:
• Double-clicking on an RLD component or name within a BBL or Primitive block

accesses the signal name point list dialog box for changing the associated control
signal name.
• Selecting a component from the Component menu bar option or from the toolbar and
double-clicking on the addition location adds a component or changes an existing
component.
• Selecting a new control signal name from the signal name point list dialog box.
• Selecting Edit:Comment from the menu displays the text window with the existing
comment text. The text window allows modifying text or adding text to the comment
rung.
• Changing BBL blocks and Primitive blocks deletes the components on the rung.
Changing the rung type also deletes the rung components.

• Selecting the Delete Element from the Component menu, and double-clicking on the
component deletes the component. Adding components to the resulting gap in the
rung is necessary for proper function of the rung.
Selecting Rungs
Selecting rungs allows access for copying, editing, or deleting. Navigating to the rung and
selecting the menu bar option Edit and the Select command from the drop-down menu
highlights the rung to indicate its selection. Repeating the selection process for other rungs
selects multiple rungs. Selecting the menu option Edit:Deselect deselects the rungs.
Copying Rungs
The Sequence Editor allows for copying rungs within a segment window or to another
segment window.
Ø To copy rungs
1. Navigate to the rung and select it using the menu option Edit:Select. The rung
highlights.
2. Select the Edit:Copy menu item. Navigate to the insertion point and select the
menu bar option Edit:Paste. The Editor inserts the copied rung and re-numbers
the following rungs.
3. Selecting Paste in other locations inserts the copied rung again. Copying multiple
selected rungs and pasting them copies the selected rungs and inserts them to the new
location. Toolbar buttons also perform copy and paste functions.
Once a rung is selected and copied, the Editor permits copying to another segment
window. Exiting the existing segment window and opening the new segment window, or
opening a new segment window both allow for copying the rung from one segment to
another. Copying the rung to another segment follows the above procedure.
Moving Rungs
The Sequence Editor allows for moving one rung or multiple rungs. The procedure is
similar to copying rungs except the menu option Edit:Cut is used to remove the rung
and re-number the following rungs. Navigating to the new rung location and selecting
Edit:Paste inserts the rung to the new location and renumbers the following rungs. Cutting
and pasting multiple selected rungs removes all selected rungs and inserts them in the
new location. .
Note Toolbar buttons also perform the cut and paste functions
Adding a Rung
The Editor allows adding new rungs at any point in the segment. Navigate to the insertion
point for the new rung. At the location, select the menu option Rung:Add. The Editor
displays a dialog box to select adding the rung before or after the current rung. The
selection adds a blank RLD rung and re-numbers the following rungs.

Deleting a Rung
The Editor allows deleting rungs. Navigate to the desired rung and select the menu
option Rung:Delete. A dialog box requesting confirmation of the deletion displays.
Deleting a rung is permanent. Only exiting the Editor without saving restores a deleted
rung since there is no undelete selection. To cancel a delete, select the Cancel button in
the confirmation window.
Selecting the Rung Type

New rungs are one of four different types. Selecting the Rung:Type menu item displays
the Modify Rung Type dialog box that allows the choice of one of the four rung types
as follows:
• RLD (relay ladder logic alone) displays a blank grid for adding components.
• Primitive (a basic block made up of relay ladder logic) displays another dialog box
to choose the Primitive to add. Primitives display both a tile and an RLD grid and
require signal names.
• BBL (one large block alone) displays another dialog box to choose the BBL or
Primitive to add. BBLs display as tiles, and often require signal names.
• COMMENT (text only) rung type displays a blank screen without the RLD grid.
Adding RLD Rungs

Selecting the RLD rung type displays a blank RLD grid on the screen. Selecting
the Components menu option displays a drop-down menu of the different possible
components. Selecting a component from this menu allows it to be added to the grid.
The new rung must begin at the top left grid line and end at the top right grid line.
Double-clicking on the grid line adds the component to that location. A Signal Name
dialog box displays if the component is a normally open contact, normally closed contact,
or coil or inverted coil. This dialog box allows for typing the control signal name or for
browsing the control signal name database to select the control signal. If the control signal
name or the type of signal is invalid for the component, the Editor displays a warning.
Selecting cancel at the warning removes the use of that control signal name. Selecting
OK allows for the use of the control signal name. RLD rungs must follow standard
relay ladder logic format. Selecting Component:Delete Component from the menu and
double-clicking on the component deletes a component.
Note The toolbar component buttons allow for quick component addition and deletion.
The menu bar option Component has six commands available for editing RLD rungs and
the RLD section of Primitive rungs as follows:
• The drop-down menu command NOC represents a Normally Open Contact

component selection.
• The NCC command represents a Normally Closed Contact selection.
• The HOR drop-down menu command represents a Horizontal connector. This
selection creates both horizontal and vertical connections. Selecting HOR and
double-clicking on a horizontal or vertical grid line adds the connector.
• The Coil and ICoil commands from the drop-down menu select normal coils and
inverted coils respectively.

• The Delete Element command deletes any components as described above.
Adding Primitive Rungs

Selecting the PRIMITIVE rung type displays a Select Primitive Function dialog box
displaying a list of the available Primitives blocks. After selecting one of the Primitive
blocks from the list, the Primitive block tile appears on the right side of the segment
window. The left side of the segment window displays the RLD grid for adding
components. Primitive blocks automatically include their associated coil.
Double-clicking on locations requiring control signal names displays the Signal Name
dialog box. Primitive blocks typically require signal names on the coils and any locations
indicated inside the primitive tile. Double-clicking on a name inside the primitive tile
displays the Signal Name dialog box for selecting the associated control signal name.
Typically, a primitive block requires a contact or contacts to enable it. Follow the Adding
RLD rungs rules to add the enabling contacts. Normally open contacts, normally closed
contacts, connectors, or combinations are allowed.
Adding BBL Rungs

Selecting the BBL rung type displays a Select Block Function dialog box. This dialog
box displays the list of the available Big Blocks. After selecting one of the Big Blocks
from the list, the BBL tile for that Big Block displays across the entire segment window
because BBL blocks do not include any RLD rung components. Double-clicking on a
name within the block displays the Signal Name dialog box for selecting the associated
control signal name.
Adding Comment Rungs

Selecting the COMMENT rung type displays a blank segment window. Adding text
involves either selecting the menu option and Edit:Comment, or double-clicking anywhere
in the comment rung. The Edit Comment dialog box displays for typing the text comment.
Selecting the OK button on the bottom of the text window adds the text to the comment
rung. Selecting the Cancel button cancels the text addition and reverts to the blank
comment rung.
Note Comments of 40 characters wide and 20 lines long are allowed.
Viewing Multiple Segment Windows

The Editor allows displaying any number of segments at one time. Multiple selection of
the menu option File:Open from the drop-down menu opens multiple segment windows.
The Window menu option provides a choice for displaying the multiple segment windows.
Cascade displays the windows one after the other, down the screen in an overlapping
fashion. Tile displays the windows in a non-overlapping tile fashion across the screen,
dependent on the number of windows open.
The Window menu option offers other commands for multiple segment windows. To open
another window of a segment, select the menu bar option Window and the New command
from the drop-down menu. The Editor allows multiple windows of the same segment, and
all windows of the same segment reflect changes to one of the segment windows. The List
1,2, ... command displays a list of currently open segment windows at the bottom of the
Window drop-down menu. A check mark appears in front of the segment name of the
active window. A segment window chosen from this list becomes the active window.

Note The latest segment window displays on top of the others unless Tile or Cascade
are selected.
Minimizing a window by clicking on its top left bar button and selecting Minimize removes
the segment window from the presentation window and iconizes it. Double-clicking on
the icon loads the segment window back onto the Editor window. Selecting Maximize
enlarges the segment window to fit the size of the Editor window. Using the cursor to select
and drag the side bar of a segment window adjusts the size of the window. A highlighted
title bar on a segment window indicates the segment window currently selected.
Saving a Segment
Selecting the menu option File:Save or clicking on the toolbar Save button saves segments.
Saving a file overwrites the previous file and all old information is lost.
To save new segments, select the menu option File:Save As command from the drop-down
menu. A Save As dialog box prompts for a new file name and directory location. The
Save As dialog box appears if the Save command or Save toolbar button are selected and
the segment was not given a name previously.
Saving a segment overwrites the segment losing the data in the

initial (unedited) file. It is recommended that, prior to editing
a segment, the segment is copied to a separate location. After
verifying the saved segment’s functionality, delete the old copy
Caution of the segment.
Selecting the menu option File:Close closes a segment. A Save As dialog box displays
when closing with new or not-yet saved segments, and asks whether to save the segment if
the segment was changed and not saved prior to closing. Selecting Yes saves an existing
segment or prompts for a file name for a new segment.
Exiting the Control Sequence Editor

Selecting the menu option File:Exit exits the Editor program. The Save As dialog box asks
whether to save the segment if the current file has not been saved. Selecting No exits the
Editor without saving the segment, losing all changes. Selecting Yes saves the segment.

CSPPRINT - Control Sequence Program Printer
CSPPRINT is a command line utility for printing Control Sequence Program (CSP)
documents using the standard Windows printing support. CSP documents represent the
control sequencing used by the Mark V.
Note CSPPRINT is not designed for printing document types other than CSP.
There are two options for printing a CSP document:
• Print a complete document at once to a default printer, or

• Open the CSP Printer window for more control
CSPPRINT functions with other programs, as follows:
• CSP file, which is a pre-formatted file containing all the necessary information for
pagination. CSPPRINT uses this information to display and print the CSP document.
• Sequence Editor, used to modify the CSP source code (CSPPRINT is not an editor).
• Sequence Documentor, which produces the CSP document (refer to Sequence
Documentor in this chapter).
Note During the printing process, CSPPRINT runs at a lower priority to make CPU
resources available to other processes.
File Structure
CSPPRINT operates on two CSP documents produced by the Sequence Documentor
utility: CSP.PRN and CSP_XREF.PRN. These files are located in the unit configuration
directory. The CSP output document is pre-formatted containing all the necessary
information for pagination. These files can also be viewed with any word processor that
has access to a fixed pitch font with the line drawing characters. However, because the
CSP documents are pre-formatted, they may not print correctly from the word processor.
Note CSP.PRN, is a complete representation of the control. CSP_XREF.PRN, is

a signal name cross-reference.
Operation
Ø To start the CSSPRINT command line utility: from the Start menu, select
Turbine Control Maintenance (ST) , <Unit Name>, and Sequence Printer.
or

Configuration directory) and enter the command: CSSPRINT CSP.PRN.
CSPPRINT E:\Site_ST\UNIT1\CSP.PRN
The file name is E:\Site_ST\UNIT\CSP.PRN/p; and only one file name is

permitted on the command line. Without /p, the command launches the CSP Printer
window.

The optional parameter /p (case sensitive) when entered on the command line along with a
file name causes the entire CSP document to be printed to the default windows printer.
No program window displays when using the /p parameter, however a dialog box displays
the status of the print job formatting and gives the user the option to cancel the print job.
Using the CSP Printer

The CSP Printer is a single document interface launched by the CSPPRINT utility. Use
the menu selections at the top of the CSP Printer program screen to adjust the page
appearance, select a printer, and print a CSP document.
It allows only one CSP document to be displayed by the program at any time. More
than one copy of the CSP Printer program can be run to view and print multiple CSP
documents at the same time.
CSP Printer Window
Only one page of the CSP document is displayed at time. Use the Page menu or toolbar
buttons to navigate through the pages of the document. The window title bar displays the
CSP document name including the full path, current page number, and total number of
pages in the CSP document. In print preview mode, the main window is replaced with a
print preview window in which one or two pages are displayed in their printed format.

Ø To print the CSP document
1. From the File menu, select Open. The *.PRN document in the unit configuration
directory opens.
2. Select File then Page Setup to adjust the appearance of the page:
• If desired, select a header to be printed on each page.

• Set the page margins in either metric or English units.
• Select OK to accept the setup changes (or Cancel to cancel them) and return to the
CSP display.
3. Select File then Print. The Print dialog box displays.
4. Select the printer and paper options, then select OK. A dialog box displays the print
progress.
Ø To cancel CSP printing in progress

1. Select Cancel from the dialog box.
While printing, the CSP Printer program runs at a lower priority to make the CPU resources
available to other processes. Therefore, if a CPU-intensive application is running, the CSP
Printer Program stops until there is enough free CPU time to resume processing.
Note Refer to your Microsoft® Windows documentation for instructions on selecting

printer and paper options

TABLE_C - Table Compile
TABLE_C is a configuration tool that compiles the configuration tables for Mark V units.
It takes the configuration information out of the ASCII configuration source files (*.SRC)
and converts it to the binary images that the controller needs. The results are placed in a
set of *.AP1 files.
Editing a set of tables containing configuration information creates some of the

configuration information. These tables contain the signals to be totalized, the signals to
be treated as events, and the values of the control constants. The tables are edited in ASCII
source files and stored as *.SRC files in the unit configuration directory. These *.SRC
files refer to signals using the signal name.
TABLE_C reads the *.SRC files and converts the contents from ASCII to binary format. It
stores the binary files as *.AP1 files in the unit configuration directory. These binary *.AP1
files are downloaded to the controller to provide the table driven configuration information.
Operation
TABLE_C is a command line configuration program run from the unit configuration
directory.
Ø To start the TABLE_C command line utility: open a GeCssTci Command

command: TABLE_C
If run with no parameters or with the /? parameter, a help screen displays. This help screen
includes the list of tables supported by the unit.
A few of the table files contain values, such as the control constant values. These values
must be translated from ASCII to binary values, using a scale code table. By default the
ENGLISH.SCA file is used. This can be overridden by using the /SCALE=<filename>
qualifier in the TABLE_C command line.
TABLE_C requires a list of the tables to compile, supplied as parameters to TABLE_C.

There is a special parameter ALL that compiles all the table files, as displayed in the
following example:
E:\Site_ST\UNIT1> TABLE_C ALL

TABLE_C: Table compiler for Mark V AP1 files.
E:\Site_ST\UNIT1>
In the preceding example, all the table files were compiled. In this case TABLE_C
determined that the unit was a Mark V.
F:\UNIT1> TABLE_C CONST

TABLE_C: Table compiler for Mark V AP1 files.
CONST WARNING: constant "COMMHTHY" not found, set to zero.

E:\Site_ST\UNIT1>
In the preceding example, only the Control Constant table was compiled. TABLE_C
found that the Control Constant named COMMHTHY was defined in the unit, but no
value was given for it in the configuration table. It warns that this constant is being
given the value of zero.
Note The ALL parameter is also used by MK5MAKE to compile all tables.

EEPROM Downloader
EEPROM is a Mark V configuration utility that downloads binary configuration
information from the HMI into the non-volatile memory in the Mark V controller.
Various configuration tools create the *.AP1 files that define the Mark V controller
configuration. These include the Sequence Compiler, the Table Compiler, and the I/O
Configurator. These files are stored in the unit configuration directory for each unit,
and must be downloaded from the HMI to the non-volatile memory in the controller for
them to take effect. The non-volatile memory in the Mark V is EEPROM (Electronically
Erasable PROM). The EEPROM program does the download, provides a directory
command to view the contents of the Mark V EEPROM, and does a simple check to verify
the unit's EEPROM has not been corrupted.
Note The EEPROM program transfers the configuration from the HMI to the
controller.
Operation
EEPROM is a command line utility program run from a GeCssTci Command Prompt
windows in the Unit Configuration directory.
Ø To start the EEPROM command line utility: open a GeCssTci Command

command: EEPROM
If run with no parameters or the /? parameter, help is provided, as displayed in the

following example:
E:\Site_ST\UNIT1>
Mark V EEPROM downloader.
EEPROM <option> <unit_name> <proc> <sections>
Where:
<option> is one of { UP | DOWN | DIR | CHECK | NOCHECK | HELP | EXIT }
<unit_name> is the name of the desired unit.
<proc> is the processor to talk to, one of { R | S | T | C | D }
<sections> is ALL, USER, or a list of EEPROM partition names, including:
FORMAT - Formats (reinitializes) the EEPROM. [Not in USER category]
SEQ - Contains the Control Sequence Program.
CONST - Contains control constants.
IOCFG - Contains IO configuration.
UBBL - Contains User BBL library.
HIST - Contains point list for history log.
EPA - Contains point list for EPA log.
MAOUT - Contains point list for 4-20 mA outputs.
EVENT - Contains point list for events.
CHNG - Contains point list for change detection.

BOI - Contains point list for backup operator interface.
TOTT — Contains point list for totalized data.
TOTD - Contains totalized data. [Not in USER category]
CBLR - Contains point list for cable remote.
E:\Site_ST\UNIT1>
EEPROM options
Options Description
UP Uploads the binary from the Mark V to the HMI. It is used when the contents in the unit are to be
preserved as disk files on the HMI. This option requires one or more section names.
DOWN Downloads a binary file from the HMI to the Mark V when configuring the controller. This option requires
one or more section names.
DIR Provides a directory of the current contents of the Mark V. This option does not require a section name;
all sections are displayed.
CHECK Checks the nonvolatile memory for possible corruption. This is done by looking at the checksum field in
the EEPROM header and comparing the expected checksum with the actual checksum. Some sections
(such as the totalizer data) do not use a checksum so these sections are skipped in this check. This
option does not require a section name.
NOCHECK Marks a particular section as NOT using a checksum. Currently the totalizer data (TOTD) section is the
only section that is marked to not use a checksum due to constantly changing values. This option
requires a section name, which is typically only the TOTD section.
HELP Provides a help screen.
EXIT Exits the EEPROM program. This is typically used as the command in the last line in a batch file driven
download.
In addition to the individual sections (or partitions) in the EEPROM, two special pseudo
section names are provided which act as a collection of the other sections.
EEPROM Pseudo Sections
Sections Description
ALL This pseudo section means all of the sections, including the Format section. This is a dangerous section
when used with the Down option since it reformats the entire EEPROM and downloads all the sections. It
erases all information (including totalizer data) already in the EEPROM. This option is seldom used with a
download, and the program requests a confirmation if this pseudo section name is included. This pseudo
section is most commonly used with the Up option to upload all sections prior to a unit upgrade.
USER This pseudo section means all of the sections except the FORMAT and TOTD sections. It is commonly
used to download all of the user-configured sections after rebuilding the controller configuration.

A directory example is as follows:
E:\Site_ST\UNIT1> EEPROM DIR T1 R

DIRECTORY OF UNIT T1 PROCESSOR R: 03-DEC-1997 10:28:53
Partition offset size --------date-------- cksum -id-
SEQ 5000 243A 03-MAY-1997 12:36:48 4E28 SEQ
CONST 2000 1000 03-MAY-1997 12:36:26 0936 CNST
IOCFG 4000 00CB 24-MAY-1995 13:10:56 2C8F IO
UBBL 4800 0117 24-NOV-1993 13:54:34 6B5A UBL
HIST 0000 0000 03-MAY-1997 12:36:26 0000 HIST
EPA 0000 0000 03-MAY-1997 12:36:26 0000 EPA
MAOUT 0DD0 003C 03-MAY-1997 12:36:26 0FCD 4-20
EVENT 0E60 007A 03-MAY-1997 12:36:26 2570 EVNT
CHNG 0F60 0100 03-MAY-1997 12:36:28 38BD CHNG
BOI 12E0 02B6 03-MAY-1997 12:36:28 847A BOI
TOTT 0C00 00A9 03-MAY-1997 12:36:28 1EAF TOTT
TOTD 0200 0910 11-MAR-1992 16:40:48 0000 TOTD
CBLR 1160 0006 03-MAY-1997 12:36:28 CAFE CBLR
E:\Site_ST\UNIT1>
Application Information
The date and time in the EEPROM header is a copy of the date and time from the file in
the HMI used to download the controller. This means that the date in the controller is the
date the file was prepared in the HMI, not the date that the information was downloaded to
the controller. Doing this helps to correlate the information in the unit to the HMI disk
files that were used to configure the panel. If a file is uploaded from the unit, the date and
time on the HMI is set to the date and time from the EEPROM header.
There is a default layout for the EEPROM built into the EEPROM program. The default
layout defines what EEPROM partitions exist, where each one starts in the EEPROM, and
how large each partition is. Most sites use this default layout with no problems. Some
sites and some product lines redefine the layout to resize the partitions or to allow for a
larger EEPROM supplied on some jobs. This is done using the EEPROM.DAT file in the
unit configuration directory. If no EEPROM.DAT file exists, the program assumes the
default layout. If EEPROM.DAT exists, it uses the partition layout defined in that file.
If the partition layout is changed, the EEPROM needs to be completely reformatted and
downloaded for the change to take effect. If a different EEPROM layout is required in the
 controllers and <Q> controllers, separate EEPROM_B.DAT and EEPROM_Q.DAT
files can be used.

The header of the EEPROM contains some unit specific information including this unit's
ARCNET address, whether the unit is a Simplex or a TMR, and the base frame rate. This
information, along with the EEPROM directory and partition layout, is stored in a special
partition known as FORMAT. Downloading the FORMAT partition to the controller
re-formats the EEPROM, losing all the contents. Because of the unit specific information
in the FORMAT section, extra care needs to be taken if the FORMAT section is copied
from one unit configuration to another.
Note The FORMAT partition is not included in the USER pseudo section.

CARD_ID
CARD_ID is a Command Line utility program that scans a Mark V controller and reports
on the versions of the PROMS that are found. It is useful when the version of the
controller's PROMs is required, such as during upgrades, field replacements, or advanced
troubleshooting.
Note The term firmware means software in an integrated circuit form. In this case,
changing the PROM on the controller board varies the firmware.
Background
The Mark V controllers consist of individual processor boards. Each processor board has a
PROM containing the firmware that drives the board. Revising the firmware by changing
the PROM is often required. The PROM revision level determines the available board
options. This information is often needed during board replacement and during controller
upgrades, and can be read from the sticker on the PROM, but it is sometimes easier to
use the CARD_ID utility.
There are some differences in the information that is available for the Mark V controllers.
The Mark V controller is polled for each possible PROM, and it responds with the version
of the PROM. The version consists of two fields, the board name (such as TCDA) and
the version number (such as 1.2).
Note Because the Mark V poll is for any possible board, a controller that does not
have every possible board generates a diagnostic alarm when a non-existent board is
polled. These diagnostic alarms can be safely ignored.
The alarms generated are as follows:
• DCC DPM indicates an invalid destination address.

• DCC indicates there is no queue server for the destination.
The Mark V front panel messages that correspond to these alarms are:
• QST DPM NO DEST

• NO QST AVAILABLE
Operation
CARD_ID is normally run from the command prompt.
Ø To start the CARD_ID command line utility: open a GeCssTci Command

the command: CARD_ID <unitname>

If it is run with no parameters or with a /? parameter, it presents a summary of the
command line options. CARD_ID requires the name of the unit (controller) to check as a
command line parameter.
Mark V Example
In the following example, a Mark V Simplex controller is queried and the PROM revisions
of the boards that are present are reported.
E:\Site_ST\UNIT1> CARD_ID T1
Card identification for SALEM PLANT unit T1: System is type 'B'
C-TCCA:(TCCA 4.2 ) C-TCCB:(TCCB 4.1 ) C-320B:(TCCB 4.1 )
C-SLCC:(LCCB 4.4 ) C-SDCC:(DCCB 6.6 ) C-TCDA:( )
C-IOMA:(IOMA 4.5 )
R-TCXX:(TCQA 2.5 ) R-TCXX:(TCQB 1.4 ) R-320B:(TCQB 1.1 )
R-SLCC:(LCCQ 4.4 ) R-SDCC:(DCCQ 6.6 )
R-IOMA:(IOMA 4.5 ) R-TCPA:( ) R-320P:( )
R-TCD1:(TCD1 3.5 ) R-TCD2:( )
R-TCE1:(TCE1 5.2 ) R-TCE2:(TCE2 5.2 ) R-TCE3:(TCE3 5.2 )
No response from <S>
No response from <T>
Enter any key to exit program:
E:\Site_ST\UNIT1>
I/O Configurator
For information regarding the I/O Configurator, refer to GEH-6195, Mark V Turbine
Control Application Guide.

Chapter 2 HMI
HMI
Dynamic Rung Display
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 unit’s 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.
Caution
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.
GEH-6759B Chapter 2 HMI System Guide 2-1

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.
The Dynamic Rung Display is started with no segments opened.

Ø To open a segment
• Select a Segment to view from the list.

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.
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 A slash through the contact indicates normally closed.
Contacts 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 Display’s Picture File Window)
are used to display the picture file and animation of the passed parameters for Primitive
and Big Blocks.
Dynamic Rung Display’s Picture File Window
The type of information in the header timetag depends on the type of display:
• For a values display, the timetag provides the oldest piece of data being displayed
as a passed parameter. This includes the coil output for primitive blocks. If it has
not received data from the unit, the timetag display is No Valid Data. If the oldest
piece of data in the rung has not been updated for at least five seconds, the timetag
is highlighted.
• For a static display, the header timetag provides the operator interface time of when
the rung was displayed.
Note Picture files cannot be opened directly by selecting Open from the File menu.

Ø To open a picture file
1. Open a sequencing segment.
2. Navigate to the rung that contains the applicable Primitive or Big Block.
3. 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.
4. 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 segment at a time, or have multiple views of the same
segment.
• Use the Window menu to change between views.
• To navigate within a segment, use the Rung menu and toolbar buttons.

Using the Find All Function
The Dynamic Rung display includes a Find All function, which allows you to find the
occurrence of a particular signal anywhere within the control sequencing. This function
will find the following:
• Signal names in RLD rungs

• Signal names as passed parameters
• Signal names as automatic parameters
• Primitive names
• Big Block names
Find All does not do the following:
• Locate signals and block names used in sub rungs.

• Search Comment Rungs. The Find All function is available only after a valid unit
has been selected.
Ø To display results using the Find All function

1. From the Edit menu, select Find All.
2. In the dialog box, enter the desired signal or block name.
3. Select Find to display the results.
The Find All Results dialog box contains four columns, as follows:
• The first column displays the rung number where the rung was found.
• The second column 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
or
Highlight the rung number and click the Goto button.
Note The Find All Results dialog box remains open until you select the Close button
or change units.

Viewing Tabular Data
Viewing tabular data can be useful when studying the behavior of a BBL with automatic
parameters.
The Dynamic 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.
Viewing Tabular Data

Trip Log Collection for the Mark V
TRPFIL is a software product that runs in the WorkstationST application to collect,
format, and store the contents of the Mark V Trip Log buffer. The program is launched as
a background task when the Mark V feature in the WorkstationST component is started,
and runs continuously in the background collecting the trip information. The program
scans all Mark V units when the program starts, then rescans the site every five minutes.
The Trip Log collection program scans all Mark units configured on the HMI for trip
information in the unit's trip log buffer. On finding a trip condition, it collects the trip
information from the unit, formats the data as a CSV (Comma Separated Values) file, and
stores the file in the E:\HMIDATA directory for later analysis or forwarding. Both the data
and alarm portions of the trip log are provided in the one CSV file.
Two different formats of CSV output files are supported. The default is to provide the
information in an expanded format that adds spaces to visually align the data in the
columns, making the data easier to analyze without external programs. The second format
writes the information in as compact a form as possible. This saves disk space on the HMI
and transmission time when forwarding the file for analysis. This is ideal when programs
such as Microsoft Excel® are available for presentation. A configuration file is used to
determine which output format is to be created.
A simple emergency trip filter is included in the program to assist in identifying the
conditions of the trip. By default, trip filtering is enabled, but it can be disabled using a
program option. The trip filtering controls the file ID and in no case is the information
discarded.
To assist in disk maintenance, the program purges each type of data file back to the last ten
reports. The purge depth is controllable using a program option.
Operation
This section defines some of the technical details of the TRPFIL program, including
configuration and format of the data files that this program generates.
The Mark V feature in the WorkstationST component launches the TRPFIL program when
it is started, and runs in the background until the Service is stopped. During each site scan
unhealthy units are skipped, but are checked again on the next site scan. Healthy units are
polled for the contents of the trip log buffer. This buffer is analyzed to see if there is valid
trip information in the buffer. If there is, the contents of the Trip Log Buffer are uploaded
and the date and time of the trip is obtained. For the purposes of this program, the date and
time of the trip is taken to be the date and time of the first record in the post trip queue.
Note Scanning of all units is retriggered in five-minute intervals. This interval is

configurable in TRPFIL.DAT that resides in the TCI Historical data directory.
The date and time of the trip, along with the unit number and a flag identifying this as
a trip, are used to create a filename to store the data. If this file already exists, then it is
not overwritten. If this file does not already exist, then the information uploaded from
the unit's trip log buffer is reformatted into a CSV file format and the file is created. All
trip log data files are stored in the GeCssTci Historical data directory using the TRP or
TRQ file identification strings.

Prior to each site scan the program reads the TRPFIL.DAT file for any program options
specified. If this file does not exist, all program options assume their default value.
Options in this file override the default behavior.
There is nothing to preclude or prevent running the Trip Log Collection program on
multiple HMI processors. The program only creates message traffic to the controller
during its unit poll, which occurs every five minutes. There are no buffer interlock
problems created by trip buffer scanning, and message traffic rates are low enough that no
problems are expected even if multiple HMI processors scan a controller at the same time.
Trip Log Filtering

The contents of the trip log buffer are retrieved, and then examined. If the buffer was filled
by a user request, the information is not saved. If the buffer contains a trip, the contents of
the first post-trip record are examined. The time of the first post trip record becomes the
time used to record the trip. This is the time used to determine the file name.
If trip log filtering is enabled (the default) then the first post-trip record is examined to
determine if it was an emergency trip. If the data passes this filter, it is stored with the
file ID associated with a trip, or TRP. If the data does not pass this filter, then it is stored
with the file ID associated with a trip queue, or TRQ. In no case is the data discarded, it is
saved as either a TRP or TRQ file.
If any of the points required in the trip filter equation are not present in the post trip
data then the file is saved with the file ID associated with a trip, or TRP. The trip log
filter equation is:
TRIP = ((Not L94X) OR (TNH > 95%)) AND (TNH > 20%)
Trip log filtering can be disabled by including the option FILTER_TRIPS = No in the
option file.
Trip Log File Names

The Trip Log Collection program reformats the trip log information into CSV format and
store the results in the E:\HMIDATA directory. The file names are created in a format
that allows for easy identification of the file information.
The file names are generated as a function of the date and time of the trip, the unit name,
and the file type (trip report or trip queue report). All of this is encoded in the filename
such that a directory sorted by name gives the trips sorted by time.
The File Name Format is YYYYMMDD_HHMMSS_UU_TR?.CSV, where the

configuration is as follows:
• YYYYMMDD - The year, month, and day, zero padded if required.

• HHMMSS - The hour, minute, and second, zero padded if required, using a 24-hour
format.
• UU - The unit name as defined on the HMI.
• TRP -or-TRQ - The trip file type.
• .CSV - The file extension, always .CSV for Comma Separated Value files.

Trip Log File Format
The CSV files are formatted into three basic sections for easy import into a spreadsheet or
database application program. Each section is separated from the previous section by a
blank line and a Section,Title line, where the Title defines the section contents.
Automatic analysis routines can trigger from the blank line as the end of one section and
the beginning of the next. The name of the section indicates the type and format of data
that follows. This section information can be used by automated analysis routines to parse
the different types of data that exist within one file. For example, The Trip Log Collection
files contain both data and alarm sections that must be formatted differently. The section
headers allow an automated routine (or macro) to format each section correctly.
The three sections of the Trip Log Collection CSV files are as follows:
IDENTIFICATION The first section is an unnamed section starting at the beginning of

the file (line 1) that provides the report type, site name, and unit name information. Each
piece of information is presented as an information type field and a value field. Three
information type fields are currently provided:
• Report For the Trip Log Collection files the value is always TRIP LOG.
• Site The value is the site name as defined on the HMI.
• Unit The value is the unit name as defined on the HMI.
DATA The second section is titled Data and includes the time stamped data samples from
the unit's trip log buffer. The first line in this section is the name of each column. The
name of the column containing the time tags is DATETIME, and the name of all the other
columns is the name of the point in the column.
The second line in this section is the engineering units for the value in the column. For the
DATETIME column this is given as YYYY-MM-DD HH:MM:SS.000. All other columns
use the engineering units string assigned to the point in that column.
The remaining lines in this section are the values from the unit's Trip Log buffer. The data
is presented in the order that it was collected from the controller. This should appear in
chronological order, but if the controller underwent a jump in time the values displayed
can appear uneven or possibly even out of order. The order of the data collection has been
preserved in the file for analysis, and the actual time references can be reconstructed
from the HIS_AGE variable, which should always be in column two, right after the time
in column one.
By default the data is written to the file one field right after another. This provides for
the most compact file at the expense of being able to scan the file unaided (the Trip Log
Display program provides a user readable version of the trip log data). If desired, the
program options file can be used to inject extra spaces into the file to align the fields so
that the values can be easily read by inspection. This option increases the size of the file
(often dramatically) so it is not enabled by default. Refer to the Options File section for
information on how to request the expanded format.

ALARMS The third section includes the alarm information collected from the controller's
trip log buffer. The first line in this section is the name of each column as follows:
• DATETIME- The time tag for the alarm, with the format YYYY-MM-DD
HH:MM:SS.000, where .000 indicates the subseconds. (milliseconds)
• S The state of the alarm.
• P The processor generating the alarm. For process alarms this is always Q.
• DROP/NAME For process alarms, this is the drop number in decimal.
• DESCRIPTION This is the alarm text associated with the alarm. The alarm text is
obtained from the HMI configuration, not the unit.
The remaining lines in the section are the alarms as recorded by the unit. The data is
presented in the order that it was collected from the controller. This should appear in
chronological order, but if the controller underwent a jump in time, the values displayed
can appear uneven or possibly even out of order.
Program Options
Prior to each site scan, the Trip Log Collection program reads an options file
(E:\HMIDATA\TRPFIL.DAT) for any options that override the default actions. This
is an ASCII file that contains a list of options and option values separated by an equals
sign. Lines that start with a semi-colon are taken to be comment lines. The currently
supported options are listed here.
• CSV_EXPAND_DATA = {Yes | No} [Default = Yes]
This option directs the program to add additional spaces to the data section to expand the
columns to their full width. This aligns data in an easily readable column format so that
no tools are required to format the file for simple viewing. This increases the size of the
file (often dramatically) from the compressed format, which increases the disk space
consumption and transmission size of the file. Possible values are Yes and No, with Yes
being the default value if this option is not specified or the option file does not exist.
The file size can differ dramatically due to field widths used on the HMI. In the worst-case
expansion, an unexpanded digital signal recorded as 0 or 1 is expanded up to the width of
the signal name used as the header, which can be 12 characters. Thus, each one character
digital may be expanded up to a 12-character field. The effects of this depend upon the
number of digital signals and the lengths of their point names. Analog signals also have
some expansion, but not as dramatic. Due to the formatting rules on the HMI, no column
is reduced to less than seven characters when running in the expanded mode.
• PURGE = <integer> [Default = 10]
After a trip log data file is written, the number of trip log data files from that controller
is purged back to prevent the files from taking up too much hard disk space. By default
the last ten files are saved, but this can be controlled by the PURGE option. The PURGE
option is an integer that specifies how many files to keep for each unit with the TRP
identification. If not supplied, this defaults to ten. If this value is set to zero the Trip Log
Collection program will not purge its data files.
• SHOW_FORCING = {Yes | No} [Default = No]

The SHOW_FORCING option defines whether forced logic values should indicate the
forcing. If set to No all logic points are displayed as 0 or 1, with no indication that they
are forced. If set to Yes the values 2 and 3 generate for forced to zero and forced to one
respectively. If not defined, logic points are displayed as 0 or 1.
• FILTER_TRIPS = {Yes | No} [Default = Yes]
The FILTER_TRIPS option defines whether the trip should be examined and a
determination made of whether this is an emergency trip or not. If the filtering is not done,
then all trips are assumed to be emergency trips and stored with a file ID of TRP. If the
filtering is enabled, trips that do not pass the filter are stored as Trip Queue files using a
file ID of TRQ. In no case is the information discarded.
• SCAN_RATE = <integer> [Default = 5]
The SCAN_RATE option specifies the frequency at which the controllers are scanned for
new trip data. The scan rate is specified as the number of minutes between scans, with a
default scan rate of one scan every five minutes. The maximum scan rate allowed is one
scan per minute. An entry of 0 for the scan rate is interpreted as a request to scan at the
maximum allowed rate of one scan per minute.
Importing Results into Microsoft Excel

One of the reasons the CSV file format is used is for ease of import into Microsoft Excel.
Microsoft Excel can open the CSV file directly and provide a reasonable display with the
exception of the time fields. To fix the formatting of the time fields, select the first column
and change the format to the following custom format:
yyyy-mm-dd hh:mm:ss.000
This can be accomplished by the following EXCEL macro:
Columns(1).NumberFormat = "yyyy-mm-dd hh:mm:ss.000"
The section separations and section names can be used by macros to split each section of
the file off to its own worksheet and do any column formatting desired. It is recommended
that the name of the section be used as the name of the worksheet in the workbook for
compatibility with future tools. This allows the following macro commands to handle
the custom time formats:
Worksheet("Data").Columns(1).NumberFormat = "yyyy-mm-dd
hh:mm:ss"
Worksheet("Alarms").Columns(1).NumberFormat = "yyyy-mm-dd
hh:mm:ss.000"
When graphing the data it is highly recommended an X-Y or scatter plot be used with
the DATETIME column for the X-axis and the data point(s) of interest on the Y-axis.
This optically corrects for the non-linear collection times in the Mark V trip log. With
this, the format of the time axis can usually be shortened to the HH:MM or HH:MM:SS
format to save space on the graph axis labels.
If the SHOW_FORCING option was enabled, then the state of the logic signal can be
extracted from the least significant bit of the value. This can be done by taking the value
mod 2, which in Excel is accomplished using MOD (value,2).

Diagnostic Display
There is a special diagnostic mode in this version of the TRPFIL program that allows it
to be run interactively to report on the state of the background data collection. If the
program is run from a command line prompt with no parameters it reports one of the
following conditions:
• If the TRPFIL program is not running in the background, it gives a message that
indicates that the program cannot be run in interactive mode, but must be launched
from the system service.
• If the TRPFIL program is already running in the background, it provides a simple
report of the collection state for each unit. Included in the state is a report on the
contents of the unit's Trip Log Buffer, and if it contained a valid trip, and the name of
the file on the HMI that contains the information about that trip. Those familiar with
the version of the Trip Log Collection program recognize this status report as
its user interface display.)
The report includes a state for the unit collection. Because this report is generated at the
completion of a site scan, not all interim collection states are visible in this report. The
In Progress, Decoding, or Saving states are not present since the diagnostic report is not
generated until after the collection scan is complete. The states that the unit goes through
in the Trip Log Collection process include:
• Disabled Scanning of this controller has been disabled. (This state is currently
not used).
• Unsupported The unit is not a Mark V and will not be scanned.
• No License The program license (for the TRPFIL software product on the HMI) is
missing or invalid, the controller will not be scanned.
• Pending The controller will be scanned as soon as the controllers before it have
been scanned.
• In Progress Messages are being exchanged with the controller to collect the trip
log data.
• Timeout The controller did not respond to multiple requests for the data. The
controller will be scanned again in the next scan.
• Decoding All data has been received from the controller and is being decoded to
determine if the data needs to be saved.
• Saving The data is being converted to CSV format and is being written to disk.
• Done All data has been collected and saved for this scan. The controller will be
rescanned in the next scan.
The diagnostic information is also available as a trace global section under the name
trpfil_trace. This global section can be viewed using the same mechanisms as all other
trace global sections. The following is a sample display for a single unit site:
Trip Log Collection Status Report

03-SEP-1999 11:03:56 TCI Development

UNIT Collection Unit Trip Buffer Filename
---- ---------- ------------------ ------------
T1 Done 01–SEP–1999 19990901_171028_T1_TRP
17:10:28
Trip Log Viewer

A Mark V controller loses the trip history data stored in its memory if the unit control
is reset or rebooted. 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 Trip Log Viewer Dialog Box.
Opening a Trip Log File - Mark V

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

Ø 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.
2. Enter 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:
DMD2SRC Demand to Source Conversion Program

The Demand to Source Conversion Program, DMD2SRC.EXE, converts the Demand
Display binary storage file to a text format for easy editing by hand. The program has
a reverse option, which converts the text source file back to a binary storage file. It is a
command line program, not a Windows program, and run from the HMI.
The conversion program converts the binary file to a text file. The text file has the same
name as the binary file, but with a *.SRC extension. An explanation of the file contents is
included in this sample file and all *.SRC files produced by this program. The following is
a sample DMD2SRC..EXE source file output.
;
;
; The name of Demand Display file being read is DEMO.DM2.
;
;
; The Demand Display file is being read on Thu Nov 20 11:31:00 1997
;
;
;
; +-----------------------------------------------------------------+
; |UNIT_NUMBER <num> TITLE "<title>" TYPE "<display type>" |
; +-----------------------------------------------------------------+

; DISPLAY RECORD: One of the displays defined. These must
; start in the first column.
;
;
; <num> is the decimal unit number. This must match the description
; in the F:\CONFIG.DAT file.
;
; <title> is the title of the display. (Limited to 25 characters.)
;
; <display type > is the type of the display. Only two types are
; allowed: Dictionary and Point
;
;
; +------------------------------------------------------------------+
; | P "unit" "pointname" |
; +------------------------------------------------------------------+
;
; POINT RECORD: One of the points shown on the display.
; These lines must be indented under the DISPLAY RECORD.
; Point records are valid only for Point type displays. (see DISPLAY RECORD)
; <unit> is the NAME of the unit. If an empty string is supplied, the
; currently selected unit is used. The name must match the list in
; the F:\CONFIG.DAT file.
;
; <pointname> is the control signal name, as described in the
; F:\UNITDATA.DAT file. The synonym can NOT be used, but will be
; displayed if synonyms are enabled.
;
;
; +-------------------------------------------------------------------+
; |T "Text line1" "Text line2" btype "bunit" "command" "funit" "fname"|
; | fsense vtype value |
; +-------------------------------------------------------------------+
;
; TARGET RECORD: One of the targets shown on the display.
; These lines must be indented under the DISPLAY RECORD. (It must
; also be one line, it was broken into two lines here for explanation
; only. A target record is associated with the point record immediately
; preceding it. The top line of the button text will line up with the
; point name text on the display. A target record is permitted every
; three point records so they will not overlap when displayed. Target
; records are valid only for Point type displays. (see DISPLAY RECORD)
;
; If both are blank, the rest of the line is ignored.
;
; <btype> is a single character button type:
; - - <not used>
; ? - ARM/EXECUTE
; ! - IMMEDIATE ACTION
; # - ANALOG SETPOINT
;

; <bunit> is the name of the unit to send the command to. If an empty
; string is supplied, the command will be sent to the currently
; selected unit.
;
; <command> is the name of the command signal.
;
; <funit> is the name of the unit to get the feedback signal from. If
; an empty string is supplied, the currently selected unit is used.
;
; <fname> is the name of the feedback signal. If an empty string is
; supplied, no feedback signal is used.
;
; <fsense> is a feedback signal state that highlights the target:
; 0 - Highlight when the feedback signal is FALSE (0).
; 1 - Highlight when the feedback signal is TRUE (1).
;
; <vtype> is a single character value type:
; + - The value is added to the current value and sent.
; - - The value is subtracted from the current value and sent.
; = - The value is sent to the unit.
;
; <value> is the HEX value for the command.
;
;
; +------------------------------------------------------------------+
; | S "search class" |
; +------------------------------------------------------------------+
;
; SEARCH RECORD: One of the point classes to be shown on the display.
; These lines must be indented under the DISPLAY RECORD. The entries;
; in the search record are used to search the data dictionary and
; points matching at least one of the criteria are displayed.
; Search records are valid only for Dictionary type displays. (see
; DISPLAY RECORD)
;
; <search class> is the data dictionary search criteria. All
; valid XDTYPEs are allowed (for logics, XDTYPEL1, use L1 and so on.
; Also allowed are special classes - Command Pushbuttons, Logic State,
; Analog Setpoints, Control Constants, and All.
;
;
; +-----------------------------------------------------------------+
;-------------------------------------------------------------------
UNIT_NUMBER 1 TITLE "Demand Display" TYPE "Point"
;
; This is a point list based display.
;
;
; There are 0 lines in this display.
;
;
;P unit-pointname
;- ---- --------------

;--------------------------------------------------------------------
UNIT_NUMBER 1 TITLE "Logics" TYPE "Dictionary"
;
; This is a dictionary-based display.
;
;
;S Point Type
;- ----------
S "L1"
;---------------------------------------------------------------------
UNIT_NUMBER 1 TITLE "Demonstration" TYPE "Point"
; This is a point list based display.
;
;
; There are 11 lines in this display.
;
;
;P unit-pointname
;- ---- --------------
P "" "L4"
;
;T Text line1 Text line2 BT unit-command-name unit-feedback-name F T value
;- ---------- ---------- -- ---- -------------- ---- -------------- - - ------
T "LOAD" "SETPOINT" # "" "L90PSEL_CMD" "" "" 0 = 0x00
;
;P unit-pointname
;- ---- --------------
P "" "L52GX"
P "" "L90PSEL_CMD"
P "" "DWATT"
P "" "TTXM"
P "" ""
P "" "L1X"
;
;T Text line1 Text line2 BT unit-command-name unit-feedback-name F T value
;- ---------- ---------- -- ---- -------------- ---- -------------- - - ------
T "START" "" ? "" "L1START_CPB" "" "L1X" 1 = 0x04
;
;P unit-pointname
;- ---- --------------
P "" "L2TV"
P "" "L14HM"
P "" "L14HS"
P "" "L3"
;

The following four examples show the Demand Display screens from DEMO.DM2
corresponding to the DEMO.SRC source file.
• Demand Display Menu File

• Demand Display screen, empty of data
• Demand Display Screen Logics, a dictionary based display. This can display logics
given the types of points and classes of points.
• Demand Display Screen Demonstration, a point based display. This is populated by
user-selected points and user defined commands.
Demand Display Menu Screen Example
Demand Display Screen (empty) Example

Demand Display Points Base Display, User Defined, Example
Demand Display Points Base Display, User Defined

Starting the Demand Display to Source Conversion
Program
The Demand-to-Source Conversion Program, DMD2SRC.EXE, is a command line
program run from a GeCssTci Command Prompt window. The program has a reverse
option, which converts the text source file back to a binary storage file.
Ø To convert a Demand Display binary file (*.DM2) to text source file

(*.SRC): open a GeCssTci Command Prompt window (typically in the target
unit’s Configuration directory) and change directories to the location of the *.DM2
file, typically E:\Site_ST\RUNTIME, then enter: DMD2SRC.EXE filename
It is not necessary to enter the file extension as the program appends the appropriate
extension. The output file will have the same name with a *.SRC extension. This
procedure overwrites any existing source text file with the same name without displaying
a warning dialog box..
Ø To convert a text source file (*.SRC) to Demand Display binary

file (*.DM2):Change directories to the location of the *.SRC file, then enter:
DMD2SRC.EXE filename /R
It is not necessary to enter the file extension as the program appends the appropriate
extension. The output file will have the same name with a *.DM2 extension. The program
displays an error message and stops if it encounters an error in the *.SRC file. This
procedure overwrites any existing source text file with the same name without displaying
a warning dialog box.It is not necessary to enter the file extension as the program appends
the appropriate extension. The output file will have the same name with a *.SRC
extension. This procedure overwrites any existing source text file with the same name
without displaying a warning dialog box.
Editing the Demand Display Source File

The Demand Display source file may be edited by any word processor that can use a fixed
pitch font and save to a text format. The rules for formatting the text file are described in
the source file example displayed earlier.
Each demand display must have a title, which:
• Defines the unit number to which the screen is applied

• Defines the screen title
• Defines the display type
There are two types of displays as follows:
• Dictionary based displays, which can contain only specific point types, or point
classes, and which do not contain commands.
• Point based displays, which contain user-defined points, and may have user-defined
commands. The command spacing is no closer than every fourth line to prevent
overlap.

MODBUS_L Modbus List File Generator
Refer to GEI-100517 MODBUS The Modbus List File Generator is a utility program that produces a list of the points
for SPEEDTRONIC Turbine that are available over the Modbus link along with the scaling for each point. The DCS
Control for additional vendor uses this list to determine what points to ask for and how to interpret the data. The
information. list indicates which signals are read only (normal data) and which signals are writeable
(commands).
The program is also used to create a configuration file that defines the Modbus register
layout and scaling so that it can be imported into the ToolboxST* application. By
importing the definitions it allows the WorkstationST Modbus Slave to produce the same
register layout and scaling for any WorkstationST-based unit - including Mark VI, Mark
VIe, and Mark Ve controllers. This is often used when upgrading a Mark V controller to a
Mark Ve controller to have the Modbus interface remain the same.
MODBUS_L MODBUS List File Generator

MODBUS_L is a command line utility program.
Ø To start the MODBUS_L command line utility: open a GeCssTci Command

command: MODBUS_L /<parameter>
One command line parameter is required to support the ToolboxST import file. Run
MODBUS_L /? for the required parameter and a list of options. Additional command
line parameters are available to change the default format or scale codes generated. If run
with the /? parameter, it produces a help screen.
Sample MODBUS_L Help File

MODBUS_L is used to generate a formatted list of the Modbus register numbers, turbine
signal names, and scaling information for each signal defined. This information is stored
in the MODBUS.LST file. The MODBUS.LST file is then used to configure the Master
side of the Modbus link.
MODBUS_L also generates the ToolboxST import file. This information is stored
in the MODBUS.CSV file. The MODBUS.CSV file is then imported into the
ToolboxST application to configure the WorkstationST Modbus Slave. You can use the
/UNIT:<name> parameter to change the name of the unit used in the ToolboxST import
file. This is useful when making Mark VI, Mark VIe, or Mark Ve controllers use the same
Modbus layout and scaling as a Mark V.
MODBUS_ L is run from the unit configuration directory for the desired unit. It is a
file-to-file translation that does not require the background system be running.
A sample MODBUS.LST file is displayed below:
+HR0001 | SWREF_CMD | SIGN16 | 512 | 0 | MW |

+HR0002 | DRVAR_CMD | SIGN16 | 512 | 0 | MVAR |
+HR0003 | SC43LOAD | UNS16 | 65536 | 0 | STATE |
HR0004 | @SPARE | spare |
HR0005 | @SPARE | spare |
+HR0006 | L90PSEL_CMD | SIGN16 | 512 | 0 | MW | RESELECTED LOAD ANALOG SETPOINT
+HR0009 | SC43 | UNS16 | 65536 | 0 | STATE | TURBINE CONTROL SELECTION
HR00010 | SS43 | UNS16 | 65536 | 0 | STATE | TURBINE COMMAND STATE SELECTION
HR0200.00| L52GX | PACKED | GENERATOR BREAKER CLOSURE
HR0200.01| L94X | PACKED | NORMAL SHUTDOWN
HR0200.02| L30D_SD | PACKED | NORMAL DISPLAY MESSAGE “SHUTDOWN STATUS”
HR0200.03| L30D_SU | PACKED | NORMAL DISPLAY MESSAGE “STARTUP STATUS”
+HC0001 | L1FAST_CPB | LOGIC | FAST LOAD START SIGNAL
+HC0002 | L1START_CPB | LOGIC | START SIGNAL
+HC0003 | L70R4R_CPB | LOGIC | SPEED SETPOINT RAISE COMMAND PUSHBUTTON
+HC0004 | L70R4L_CPB | LOGIC | SPEED SETPOINT LOWER COMMAND PUSHBUTTON
Refer to GEI-100517, Modbus for HMI Applications for further information.

CIMMOD_L MODBUS List File Generator
The eTCSS based HMI supported retrieving Modbus information from CIMPLICITY®
and rescaling it before returning it to the Modbus Master. This was often used to make
Mark VI data (floating point) look like Mark V data (integer). It was controlled by creating
a CIMMOD.DAT file that defined the Modbus register layout and scaling.
CIMMOD_L is a command line utility program.
Ø To start the CIMMOD_L command line utility: open a GeCssTci Command

the command: CIMMOD_L
It reads the CIMMOD.DAT file and produces a CIMMOD.CSV file that can be imported
by the ToolboxST application to configure the WorkstationST Modbus Slave with the
same register layout and scaling. Run CIMMOD_L /? for a list of options. It requires
no command line parameters, but additional command line parameters are available to
change the default format or scale codes generated. If run with the /? parameter, it
produces a help screen.
Refer to GEI-100696, The eTCSS based HMI also supported a CIMMOD_N.DAT file to run in CIMPLICITY
WorkstationST* Modbus® Native mode. This returned the information from CIMPLICITY with no rescaling, leaving
for additional information. it in the CIMPLICITY native form of a double precision floating point number taking up
four (4) 16 bit registers. The WorkstationST Modbus Slave subsystem supports a default
data type that can be used to define the default format of all data. Use this default data
type when emulating data returned in CIMPLICITY native mode.

Configuration
GeCssTci Configuration Files
The configuration files for GeCssTci (the main runtime component of the Mark V feature
in the WorkstationST application) are stored in the Site Directory as defined using
the Mark V Feature Settings program found under the START menu Turbine Control
Maintenance ST item. The easiest way to work with the Site Directory is to open a
GeCssTci Command Prompt window in the Site Directory from the Start Menu "Turbine
Control Maintenance (ST)" - "HMI Configuration" - "_Command Prompt" option. The
Site Directory contains the files that configure the Mark V feature in the WorkstationST
component's GeCssTci Service for a particular site.
The following files are used:

Files by Controller Type
File Name Usage
AT_START.DAT Optional
AT_STOP.DAT Optional
CONFIG.DAT Required
IO_PORTS.DAT Optional - MODBUS
MODB_FWD.DAT Optional
TIMESYNC.DAT Recommended
TIMEZONE.DAT Required
A number of optional configuration files are only required if the option they control is in
use at this site.
AT_START.DAT is used to define a set of commands that are run after the Mark V
feature in the WorkstationST component is started. It is used to start any site-specific
programs that need to be started.
AT_STOP.DAT is used to define a set of commands that are run before the Mark V
feature in the WorkstationST component is shut down. It is normally used to stop any
site-specific programs that need to be stopped.
CONFIG.DAT is the primary configuration file for the Mark V feature in the
WorkstationST component (GeCssTci Service). This file defines the following:
• The site name included on displays and reports.

• The list of turbines with the internal unit number (1..n), unit name, configuration
directory, and controller type (Mark V).
• The number and type of ARCNET interfaces
• The addresses of each node on the Stagelink
• The GeCssTci options that are in use at this site
\IO_PORTS.DAT is used if the Mark V feature in the WorkstationST component uses

any of the RS-232 ports on the computer. This file indicates which communication ports
should be used, what the port settings are (baud rate, parity…), and what the port function
is - such as a Modbus Slave.

MODB_FWD.DAT is only used if the Modbus Slave over Ethernet function is being
used and the Modbus master does not support sending a slave address as part of the
Ethernet message. The file remaps the individual slave register sets into one large register
set, allowing information from multiple slaves to be treated as information from one
large slave. (This function is only supported for the Modbus over Ethernet link, not for
RS-232C links.)
TIMESYNC.DAT is used if the HMI is to be a time master or time slave on the Stagelink.
TIMEZONE.DAT is used to convert times from UTC to the local time format on the
computer.
TCI Modbus Configuration

Note Most sites can use the WorkstationST Modbus Slave subsystem to provide
the Modbus link to a DCS Modbus Master. In those cases the GeCssTci Modbus
Slave subsystem is not use. In cases where the customer has large data requirements
that would cause issues with the WorkstationST application’s 970 point count limit
the GeCssTci Modbus Slave can be used instead. This subsystem goes around the
WorkstationST application limitations by contacting the Mark V controller directly
for Modbus data.
The Modbus interface for GeCssTci can be configured to act as a slave to the DCS master.
Modbus slave mode supports RS-232C serial communications and Ethernet.
Refer to GEI-100517, Modbus In Modbus slave mode the DCS can request information from each controller by sending a
for SPEEDTRONIC Turbine Modbus data request message over the Modbus link to a specific slave address. The
Control for more information. DCS master can also issue Modbus command messages to initiate operator commands
to each controller. These command messages support both pushbutton commands (such
as START, STOP) and analog setpoint commands (such as preselected load setpoint). A
Modbus data file specifies the correspondence between Modbus coil and register numbers
and the Unit’s data.
GeCssTci Modbus Slave

Modbus slave mode is often used for a link with the plant distributed control system (DCS).
Data can be supplied from controllers to the DCS when running Modbus Slave mode.
Refer to the Configuration File The Modbus Slave program uses three sections as follows:
(IO_PORTS.DAT section in this
chapter for more information) • The [MODBUS_SLAVE_PORT] sections are repeated once for each I/O port to be
used as a Modbus slave link. Both serial and Ethernet ports are defined here. Serial
links can use the COM1 or COM2 port, or a port from a serial expansion board.
The Ethernet link, if used, can also be specified here, but is only needed once (not
once per Modbus master using this link).
• The [MODBUS_ASSIGNMENT] section is used to bind Modbus slave addresses to
internal unit numbers, and indicates what Modbus addresses the GeCssTci Modbus
slave should answer as. It also controls the data format (mode) used over the Modbus
link.
• The [MODBUS_SLAVE_TIMEOUT] section controls the message level timeouts,
and the NAKs that are returned when a timeout occurs.

The rate at which the data can be collected from a serial Modbus slave is limited by the
transmission rate on the RS-232C link, and by the turn-around times of the computers on
each end of the link. The rate at which the data can be collected from an Ethernet Modbus
slave is limited by the Ethernet traffic and by the turn-around times of the computers on
each end of the connection. The DCS can issue no more than ten command messages
per second.
A maximum of eight serial links can be configured. The number of Ethernet connections
an Ethernet Modbus slave will accept is configurable. Ethernet and serial links can both
be used at the same time. All data to and from a controller is serialized and operated on
one at a time.
The GeCssTci Modbus slave configured with the appropriate address replies with the
requested data. The Modbus Slave subsystem can respond to up to 16 slave addresses
where normally each slave address responds with data from a different Mark V controller.
Modbus Forward
Refer to the section The Modbus Forward is used if the Modbus Slave over Ethernet function is being used
on Configuration File and the Modbus master does not support sending a slave address as part of the Ethernet
(MODB_FWD.DAT) for message. The file remaps the individual slave register sets into one large register set,
more information. allowing information from multiple slaves to be treated as information from one large
slave.

Configuration File (AT_START.DAT And AT_STOP.DAT)
The Site Directory AT_START.DAT file is used to define a set of commands that are run
after the Mark V feature in the WorkstationST component is started. It is used to start any
site-specific programs that need to be started. The following is a sample AT_START.DAT
file:
;
; AT_START.DAT
;
; This file is run by the Turbine Interface after it has started up the
; basic core routines. This allows a site dependant set of application
; programs to be started up after the core systems are running.
;
; A companion file (AT_STOP.DAT) is used to start any additional
; application programs after starting the Turbine Interface.
;
; Available commands include:
;
; INCLUDE <<filename>
;
; This includes the given filename as if the file were contained in
; this file. There is no limit to the level of includes, but please
; don't make them circular.
;
; CDP <priority> <program> [<parameters>]
;
CreateDetachedProcess creates a detached process at the given
; priority running the given program with the given (optional)
; parameters. The program and parameters will be environment string
; expanded prior to being run. The priority is an ASCII string that
; must be one of (REALTIME, HIGH, NORMAL, or IDLE).
;
;-------------------------------------------------------------------------
;
;INCLUDE %SystemDrive%\<your_product>\STARTUP.DAT
;
; [End of File]

The AT_STOP.DAT file is used to define a set of commands that are run before the
Mark V feature in the WorkstationST component is shut down. It is normally used
to stop any site-specific programs that need to be stopped. The following is a sample
AT_STOP.DAT file:
;
; AT_STOP.DAT
;
; This file is run by the Turbine Interface before it shuts down the
; basic core routines. This allows a site dependant set of application
; programs to be started up after the core systems are running.
;
; A companion file (AT_START.DAT) is used to shut down any additional
; application programs prior to shutting down the Turbine Interface.
;
; Available commands include:
;
; INCLUDE <filename>
;
; This includes the given filename as if the file were contained in
; this file. There is no limit to the level of includes, but please
; don't make them circular.
;
; CDP <priority> <program> [<parameters>]
;
; CreateDetachedProcess creates a detached process at the given
; priority running the given program with the given (optional)
; parameters. The program and parameters will be environment string
; expanded prior to being run. The priority is an ASCII string that
; must be one of (REALTIME, HIGH, NORMAL, or IDLE).
;
;
;-------------------------------------------------------------------------
;
;INCLUDE %SystemDrive%\<your_product>\SHUTDOWN.DAT
;
; [End of File]
;-------------------------------------------------------------------------
;INCLUDE %SystemDrive%\<your_product>\SHUTDOWN.DAT
;
; [End of File]

Configuration File (CONFIG.DAT)
The Site Directory CONFIG.DAT file is the main Mark V feature in the WorkstationST
component (GeCssTci Service) configuration file that defines the site name,
communications links, turbine controllers, and options in use at this site. The following
is a sample CONFIG.DAT file:
;
; CONFIG.DAT - HMI CONFIGURATION FILE
;
; CONFIG.DAT - This file defines the overall configuration of the system.
; After making any changes, you will have to restart the Mark V Feature
; in WorkstationST in order for the change to take effect.
;
;-----------------------------------------------------------------------------
;
; This section defines the site name (16 char max)
;
SITENAME
Power Station
;
;-----------------------------------------------------------------------------
;
; UNIT DATA - A definition of the units
; Unit Number......... Decimal number from 1-n
; Unit Name........... 1 or 2 character unit name
; Path to Config...... Directory path of unit configuration directory
; Note: "F:\" will translate to the Site Directory
; Unit Type........... (MARKV)
;
; UNIT UNIT PATH TO UNIT
; NUMBER NAME CONFIG DATA TYPE
; ------ ---- ----------------- ------
;
UNIT_DATA
; 1 T1 E:\Site_ST\UNIT01 MARKV
; 4 T4 F:\UNIT04 MARKV
;
;-----------------------------------------------------------------------------
;
; NETWORK TYPE - A definition of the networks this PC is on.
; Network Number...... Decimal number 1-n
; Network Type........ (STAGELINK)
; Device Driver....... Name of the network driver used
;
;
; NETWORK NETWORK DEVICE
; NUMBER TYPE DRIVER
; ------- ------- --------
NETWORK_TYPE
1 STAGELINK CCSI20020DEV1
2 STAGELINK CCSI20020DEV2

;-----------------------------------------------------------------------------
;
; NETWORK DATA - A list of the network nodes we need to talk to.
;
; Unit Number......... The unit number associated with this node
; Processor........... The identity of the processor at this node address
; Network Number...... The network this node is on
; Network Address..... The HEX address of the node on this network
; UNIT NETWORK NET
; NUMBER PROC NUMBER ADDR
; ------ ---- ------- ----
NETWORK_DATA
1 C 1 FE
2 C 1 FC
3 C 1 FA
4 C 2 34
;
;-----------------------------------------------------------------------------
OPTIONS
;
;
Note The first PCI ARCNET card must use device driver CCSI20020Dev1, otherwise
the computer can lock up.
Configuration File (IO_PORTS.DAT)

This file is used to configure all of the I/O channels owned by the GeCssTci System
Service. The Modbus Slave program uses this file to specify important site variable data
such as the port, baud rate, and Modbus slave ID.
Refer to GEI-100517 Modbus The configuration file is an ASCII-based text file that may be modified with any standard
for SPEEDTRONIC Turbine text editor. Lines are not case sensitive. The configuration file is divided into sections and
Control for more information. each section begins with a title enclosed in brackets [ ].
Note Breaks are inserted with references to other portions of this document.
The following sample IO_PORTS.DAT file illustrates how ports are set up:
;--------------------------------------------------------------
;--------------------------------------------------------------
;
; <HMI> PORT DEFINITION FILE -
;
;
; This file defines the serial ports that exist on this PC
; and that are to be controlled by the GeCssTci service.
;
;--------------------------------------------------------------
Note The following section is used to configure a Modbus Slave application. Refer
to the GeCssTci Modbus Slave section for more details.

;-------------------------------------------------------------------------
;
; This section defines MODBUS SLAVE port and hardware characteristics.
; This section can be duplicated up to 8 times (Ethernet plus serial ports).
;
[MODBUS_SLAVE_PORT]
;port com2
port none
baud 9600
parity 0 ;0-4 (none,odd,even,mark,space)
databits 8 ;5-8
stopbits 0 ;0-2 (1, 1.5, 2 stop bits)
(1.5 stop bits currently unsupported)
xonxoff 0 ;0-1
port_it 40 ;Timeout interval between characters, msec. Default=40
port_tt 200 ;Timeout for total message, msec. Default=200
;-------------------------------------------------------------------------
;
; This section defines that the MODBUS can receive requests over the
; ethernet. There can only be one of these sections.
;
[MODBUS_SLAVE_PORT]
;port ethernet
port none
timeout 60 ; no activity disconnect time in minutes (0 =
disable)
socket 502 ; default ethernet port for modbus slave
Max_Connections 10 ; Maximum number of socket connections allowed
;-------------------------------------------------------------------------
;
; This section defines MODBUS slave address and software characteristics
;
[MODBUS_ASSIGNMENT]
;
;format: SLAVE nnn UNIT uu MODE keyword
; where: nnn is the SLAVE address (in decimal) to recognize when sent
; a message from a modbus master.
; uu is the two character unit name (defined in F:\CONFIG.DAT)
; keyword is either RS16, RU16, UN12, HW12, or NATIVE for Signed 16,
; Unsigned 16, Unsigned 12, Honeywell 12, and Native data
; respectively.
;
; A new line should appear for each definition. Normally this is one
; or two lines for typical data patterns. A maximum of 16
; definition lines may appear.
;
;SLAVE 1 UNIT <unit_name> MODE RS1
;

;-------------------------------------------------------------------------
;
; This section defines MODBUS slave timeout and Nak characteristics
;
[MODBUS_SLAVE_TIMEOUT]
modbus_timeout 4000 ;Time (milliseconds) before we give up and send nak
modbus_timeout_nak 6 ;Nak code used if unit timeout occurs.
;To use timeout, specify 4 or 6 only.
;To disable timeout, specify 0.
;-------------------------------------------------------------------------

Configuration File (MODB_FWD.DAT)
This function is only supported The file is only used if the Modbus Slave over Ethernet function is being used and the
for the Modbus over Ethernet Modbus master does not support sending a slave address as part of the Ethernet message.
link, not for RS-232C links. The file remaps the individual slave register sets into one large register set, allowing
information from multiple slaves to be treated as information from one large slave.
The following is a sample file:
; Modb_fwd.dat
;
; This file contains the configuration for the Modb_fwd program.
; The Modb_fwd program will translate the Master Register number
; into a Slave address and Slave register. On the way back to
; the Master it will do the conversion in reverse.
;
; The Master Reg Numbers must be in ascending order. The Slave
; addresses must not be duplicated.
;
; This program will support MODBUS functions 1,2,3,4,5,6,8,15,16.
; Function 7 is not supported because it can not specify a
; register number and thus can not be translated.
;
; For Modb_fwd to work, the line "SOCKET xxx" must be added to the
; Ethernet MODBUS definition in the io_ports.dat file. xxx must
; be something other than 502 which is the standard port and will
; be used by Modb_fwd. Port 503 is usually available.
;
;Master Slave Slave
;Reg. Number Address Reg. Number
;----------- ----------- -----------
1 1 1
1001 2 1
2001 3 1
3001 4 1
4001 5 1
5001 6 1
6001 7 1
7001 8 1

Time Synchronization Configuration
Refer to GEI-100513 HMI, To synchronize time among the controllers and devices connected to a network, a single
Time Synchronization manual source such as a HMI is selected as the primary time reference. The source can receive
for more information. its time from either an internal system clock or a Coordinated Universal Time (UTC)
satellite transmission.
Turbine Control System Time Synchronization Network
A turbine control system generally consists of a collection of devices. The types of devices
determine the communications systems used, as follows:
• Mark IV controllers communicate over CSF or RS-232C serial networks.

• Mark V controllers communicate over Stagelink.
• Mark VI controllers communicate over Ethernet.
Ethernet based controllers (such as the Mark VI) are typically configured to get their time
directly from the Time Server (if present) and from an HMI if there is no Time Server.
The Mark IV and Mark V controllers get their time from an HMI, which typically has
its time set from the Time Server as well. An option for connecting an IRIG-B or GPS
time source directly to the HMI is available when high precision is required for Mark V
systems. HMIs get their time either from the installed high-resolution time card, the Time
Server, or they use one HMI’s low-resolution system time to feed the other HMIs.

Timesync Configuration (TIMESYNC.DAT)
Refer to GEI-100513 HMI, Time synchronization between devices on Stagelink networks is achieved using the
Time Synchronization manual Timesync program. Timesync is installed on the HMI as part of the Turbine Control
for more information. Interface (TCI) product. One or more HMIs act as Stagelink Time Masters, to which the
other HMIs and controllers on the Stagelink network synchronize.
The TIMESYNC.DAT file configures the options for the Mark V timesync program to
exchange time over the Stagelink. This file is normally maintained by the GeCssTci
Control Panel applet, you should not need to make changes to this file.
The key lines in are displayed below:
TIMESYNC [HIGHRES | LOWRES | SLAVE]

LOCAL_TIMESET [ENABLED | DISABLED]
I_TIME [LOCAL | UTC]

MARKV_TIME [LOCAL | UTC]
TIME_SOURCE [LOCAL | UTC]
TIME_LOAD [MANUAL | LOCAL | NETWORK]

An example of the template file TIMESYNC.DAT is as follows:
;-------------------------------------------------------------------
;
; GeCssTci TIMESYNC Parameters
;
; Any line beginning with a semicolon (;) is treated as a comment. All
; keywords are case-insensitive.
;
; The line beginning with "TIMESYNC" indicates the type of time
; synchronization in use. Acceptable syntax is one of the following:
; 1.) TIMESYNC <controller> MODE <mode> [LEVEL_SHIFT]
; 2.) TIMESYNC LOWRES
; 3.) TIMESYNC SLAVE
;
; Example (1) indicates high accuracy time acquisition hardware is in use.
; Hardware parameters such as I/O addresses are stored in the Windows NT
; Registry. Node-to-node time errors of +/- 1 millisecond are possible
; using this type of time synchronization.
;
; Example (2) indicates low resolution time synchronization will be used.
; In this case, the Windows NT system clock is used as the time reference.
; Node-to-node time errors of +/- 10 milliseconds are typical using this
; type of time synchronization.
;
; Example (3) indicates that this computer will not act as a time master,
; but may set its' local time to that of other time masters on the stagelink.
;
; <controller> in Example (1) is one of the following keywords:
;
; "BC620AT" (from Bancomm, Division of Datum Inc.)
; "BC627AT" (from Bancomm, Division of Datum Inc.)
; "TPRO-PC" (from KSI, Division of Odetics Inc.)
;
;
; <mode> in Example (1) is one of the following keywords:
;
; "IRIG-A" IRIG-A Timecode.
; "IRIG-B" IRIG-B Timecode.
; "NASA-36" Nasa 36 bit timecode.
; "2137" 2137 Timecode.
; "1PPS" 1 pulse per second.
; "1PPM" 1 pulse per minute.
; "1PPH" 1 pulse per hour.
; "FLYWHEEL" Free Running Clock.
;
; "LEVEL_SHIFT" is specified if the timecode is DC Level Shifted
; rather than modulated. DCLS is not supported for 2137 timecode
; signals.
;
; Different timeboards do not support all <mode> selections. The
; following table defines available combinations of timeboards and
; mode combinations:
;

; TimeBoard External Time References Supported
; --------- ----------------------------------
; BC620AT IRIG-A (Modulated and DC Level Shifted)
; IRIG-B (Modulated and DC Level Shifted)
; NASA-36 (Modulated and DC Level Shifted)
; 2137 (Modulated only)
; 1PPS, 1PPM, and 1PPH
; FLYWHEEL
;
; BC627AT GPS (Normal Mode for this card)
; IRIG-A (Modulated and DC Level Shifted)
; IRIG-B (Modulated and DC Level Shifted)
; NASA-36 (Modulated and DC Level Shifted)
; 2137 (Modulated only)
; 1PPS, 1PPM, and 1PPH
; FLYWHEEL
;
; TPRO-PC IRIG-B (Modulated only)
; NASA-36 (Modulated only)
; 1PPS (Requires -m option on board)
; 1PPM and 1PPH
; FLYWHEEL
;
; TIMESYNC SLAVE
;
; "LOCAL_TIMESET [ENABLED | DISABLED]" is used to allow this computer's
; time to be set to the same time as the Stagelink Time Master. Note that
; this computer does not require a time/frequency board in order to be a
; time slave.
;
LOCAL_TIMESET ENABLED
;
; "I_TIME", "MARKV_TIME" and "TIME_SOURCE" identify what timebase is used
; in /<G> computers, Mark V control panels, and the externally supplied
; Global Time Source. Choices are UTC and LOCAL.
;
; NOTE: computers typically use LOCAL time as their time base.
; <I+>, HMI, Historian, and OSM computers use UTC as their internal timebase.
;
I_TIME LOCAL
MARKV_TIME LOCAL
TIME_SOURCE UTC
; "TIME_LOAD [MANUAL | LOCAL | NETWORK]" defines whether major time elements

; (year, day-of-year etc.) are derived from the PC automatically (i.e. LOCAL);
; or obtained from other Stagelink Time Masters (i.e. NETWORK),
; or whether TIMESYNC functions are disabled until major time is entered
; manually via TIMEUTIL (i.e. MANUAL).

;
; This parameter is only needed for Example (1) above.
;
TIME_LOAD LOCAL
; "TIMESET <node-address>" is used when Mark V panels with older versions

; of firmware exist on the stagelink that do not support the timesync
; protocol. In this case, this computer can act as a "repeating timeset"
; computer, transmitting time every hour. <node-address> is the Arcnet
; address in HEX and must be in the range 01-FF. There may be up to
; 32 "TIMESET <node-address>" lines specified in this datafile.
;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; -------------------------------------------------------------------
Time Zone Make - TZ_MAKE

Many applications need to convert times between local time and Universal Time
Coordinated (UTC). Information on the relationship between local time and UTC is stored
in the Site Directory TIMEZONE.DAT file. TZ_MAKE is a utility program that builds
TIMEZONE.DAT. It is a rule-based program that calculates past and future dates and times
for transitions between Standard Time from/to Daylight Time. It generates entries starting
five years before the year in which it is run, and generates 100 entries. For example, if
TZ_MAKE is run in 1996, it generates entries spanning from 1991 through 2040 inclusive.
By default, TZ_MAKE uses the computer site local timezone information. This is the
preferred method.
Ø To create a TIMEZONE.DAT file using the computer site local timezone

information: open a GeCssTci Command Prompt window (typically in
the target unit’s Configuration directory) and enter the command: TZ_MAKE
timezone.dat. The timezone.dat file is created. (Refer to the sample file)
Optionally, the user can define a TZ parameter to define the rules used to calculate
Standard/Daylight transition date, as described below.
Ø To create a TIMEZONE.DAT using the TZ parameter to define the time

zone: open a GeCssTci Command Prompt window (typically in the target
unit’s Configuration directory) and enter the command: TZ_MAKE timezone.dat
“TZ=timezone definition>”. The timezone.dat file is created. (Refer to the sample
file). Run TZ_MAKE /? for a list of options.
The TZ parameter is defined as follows:
• TZ= is used to define the rules on daylight savings to standard time transitions.
• If TZ=<timezone definition> is specified, it must be enclosed in double quotes.
• If TZ= argument is omitted, local Windows NT timezone rules are used.
<timezone definition> takes the following form (spaces are for clarity only):
std offset dst offset, rule std, dst are strings containing three or more characters and
spaces as follows:
std is the name to use for Standard Time.

dst is the name to use for Daylight Savings Time.
offset takes the form HH[:MM[:SS]], optionally preceded by "+" or "-". These indicate
the values to add to LOCAL time to arrive at UTC.
"-" indicates the local area is East of the Prime Meridian.
"+" indicates the local area is West of the Prime Meridian.
rule std, dst takes the form of date/time, date/time, where the first date/time defines the
transition from Standard Time to Daylight Savings Time, and the second date/time defines
the transition from Daylight Savings Time to Standard Time.
date is specified in the form Mm.n.d, where:
m = month (1= January, 2 = February, .....12 = December)
n = week of the month (1 = 1st week, 2 = 2nd week, 3 = 3rd week, 4 = 4th week, 5 =
last d day of the month)
d = day of the week (0 = Sunday, 1 = Monday, .....6 = Saturday)
time takes the form HH[:MM[:SS]] as above, but may not have "+" or "-" specified in
front of HH.
The following is a sample definition for Central Timezone of the U.S.A:
TZ_MAKE timezone.dat "TZ=Central Standard Time6Central

Daylight Time5,M4.1.0/2,M10.5.0/2"
This example used the "TZ=" construct to define the transitions for Central Time USA. It
displays that Central Standard Time is 6 hours earlier than UTC, and that Central Daylight
Time is 5 hours earlier than UTC.

Daylight Savings Time begins on the first Sunday in April at 02:00:00.
Standard Time begins on the last Sunday in October at 02:00:00. An abbreviated sample
output is as follows:
;
; TZ_MAKE Generated File.
;
; This file was created on: 20-NOV-1996 20:06:32 (UTC)
;
; NOTE: This file was created using a day-of-week and week-of-month algorithm.
; This file may require editing if local laws caused changes in actual
; standard/daylight transition dates
;
; The TZ argument used to create this text file was:
;
; "TZ=Central Standard Time6Central
; Daylight Time5,M4.1.0/2,M10.5.0/2"
;
; Standard Time Name: Central Standard Time
; Standard Time is entered on the last
; Sunday in October
; at 02:00:00 (Local Time)
;
;
; Daylight Time Name: Central Daylight Time
; Daylight Time is entered on the first Sunday in April
; at 02:00:00 (Local Time)
;
;---------------------------------------------------------------
;
; Time Offset Definition Table. Each entry
; defines number of minutes
; correction to use when Universal Time
; Coordinated (UTC) crosses:
;
; -----------UTC---------- Minutes Correction to LOCAL Time
TIME_OFFSET 07-APR-1991 08:00:00.000 -300
TIME_OFFSET 27-OCT-1991 07:00:00.000 -360
TIME_OFFSET 05-APR-1992 08:00:00.000 -300
TIME_OFFSET 25-OCT-1992 07:00:00.000 -360
TIME_OFFSET 04-APR-1993 08:00:00.000 -300
TIME_OFFSET 31-OCT-1993 07:00:00.000 -360
TIME_OFFSET 03-APR-1994 08:00:00.000 -300
TIME_OFFSET 30-OCT-1994 07:00:00.000 -360
TIME_OFFSET 02-APR-1995 08:00:00.000 -300
TIME_OFFSET 29-OCT-1995 07:00:00.000 -360
TIME_OFFSET 07-APR-1996 08:00:00.000 -300
TIME_OFFSET 27-OCT-1996 07:00:00.000 -360

TIME_OFFSET 06-APR-1997 08:00:00.000 -300
TIME_OFFSET 26-OCT-1997 07:00:00.000 -360
TIME_OFFSET 05-APR-1998 08:00:00.000 -300
TIME_OFFSET 25-OCT-1998 07:00:00.000 -360
TIME_OFFSET 04-APR-1999 08:00:00.000 -300
TIME_OFFSET 31-OCT-1999 07:00:00.000 -360
TIME_OFFSET 02-APR-2000 08:00:00.000 -300
TIME_OFFSET 29-OCT-2000 07:00:00.000 -360
TIME_OFFSET 01-APR-2001 08:00:00.000 -300
TIME_OFFSET 28-OCT-2001 07:00:00.000 -360
[Full file not shown]
Note The resulting TIMEZONE.DAT file can require editing if local laws change the
actual transition times normally used by a given locale.
Turbine Control Maintenance Icons

The User Icon Program, UICON.EXE, automatically creates the Desktop and Start
menu icons for programs supplied as part of the Mark V feature in the WorkstationST
component for both HMI and unit configuration and control. Users can customize the
menu selections by adding or deleting items through use of the user interface.
For a Mark V the menu is filled out with many maintenance options.
The Mark V Turbine Control Maintenance (ST) Start Menu Selections

This program can be run from a GeCssTci Command Prompt window in the Site Directory
using the command line:
UICON
or from the Start Menu-Turbine Control Maintenance (ST) section as the "Rebuild
Start Menu" item displayed above. The program can rebuild the entire Turbine Control
Maintenance section, and build desktop Icons.
The EPA Logger

The EPA Logger provides access to the EPA data that has been configured in the
controller. To enable the EPA Logger on the HMI, configure a printer in Windows, name
it EPA Printer, and add the following entry to the Site Directory CONFIG.DAT file in
the Options section:
Options
EPA_LOG=Yes
The EPA logger periodically polls any controllers that have EPA logging enabled; reports
determined by the controller are printed on the EPA Printer.
The printer configured as EPA Printer should be different from the printer configured
for alarm logging.
A properly configured demand display should provide enough information to verify the
operation of the EPA logger. A description of the inputs, outputs and operation of the EPA
function in the controller can be found in the EPALOG.PIC file in the unit configuration
directory. This feature for the Mark V is displayed in the following two figures.

EPALOG, Mark V Controller Portion

EPALOG, the HMI Processor Portion

Diagnostics
Alarm Dump 1 - ALMDUMP1
The Alarm Dump 1 program (ALMDUMP1) displays each alarm message received from
the turbine controllers as it is received. It also has the ability to send alarm commands
(acknowledge, reset…) to the controllers. This is useful in debugging alarm information
flow between the HMI and the controller. The Alarm Dump 1 program can be used to
watch alarms, events, or SOEs.
The Alarm Dump 1 program (ALMDUMP1.EXE) watches for messages received by

the HMI from the turbine controllers. As each message is received, it is formatted and
displayed in the command prompt window.
Ø To start the ALMDUMP1 program: open a GeCssTci Command Prompt

window (typically in the target unit’s Configuration directory) and enter the command:
ALMDUMP1
This program can also be used to generate commands back to the controller to test the
ability to send commands. RunALMDUMP1 /? for a list of options. Press the question
mark (?) key for a list of available commands while it is running. ALMDUMP1 is run
with the /? qualifier to display a list of commands, and entering the ? command while it is
running produces a screen with the list of runtime commands that it accepts. (Runtime
commands are always a single keystroke, but some commands will prompt for a parameter
such as a unit number or drop number.)
While the program is running you can press the question mark (?) to see what runtime
commands are available. Runtime commands include switching the default unit and
sending alarm commands. (Sending commands is not supported for events and SOEs
since they do not accept commands.)

The following is a sample display:
E:\Site_ST>almdump1 /?
ALMDUMP1 - Alarm Dump of exception messages.
This program will display the exception messages received
from each unit as they arrive. By default it will show the
Process Alarm exceptions, but this can be changed by
supplying a command line parameter indicating
the exception list to display.
Commands can be sent back to the unit to silence, acknowledge,
or reset alarms. Enter "?" while running for a list of valid
commands.
COMMAND FORMAT: ALMDUMP1 [list] [/EX] [/NODE=\Nodename]
[list] indicates the exception list to display, which can be:
PALARM or Displays the Process Alarm exceptions
PROCESS..... Displays the Diagnostic Alarm exceptions
DALARM or Displays the Hold List exceptions (if used)
DIAG.......... .Displays the Event List exceptions
Displays the Sequence of Events exceptions
HOLD...................
EVENT..................
SOE....................
/EX indicates to use the Extended interface to provide a
formatted dump
of the data records.
/NODE=<nodename> can be used to obtain records from another computer.

Alarm Dump 2 - ALMDUMP2
The Alarm Dump 2 program, ALMDUMP2.EXE, displays a formatted copy of the current
alarm queue entries in the computer. The output can be sorted by time, or by unit and drop
number. When run, this command prompt window program displays the current contents
of the queue and then exits – it is not a real time display that displays updates as they occur.
ALMDUMP2 is run with the /? qualifier to display a list of command line options. This
program can be used to verify the set of alarms that the HMI has received from the unit,
and also displays the set of alarms that are being passed into the WorkstationST application
for operator display. Alarm Dump 2 displays the entries in alarm queues, which include
process alarms and Mark VI diagnostic alarms – it does not display events or SOEs.
ARCWHO
ARCWHO is a command line utility program that provides a list of the ARCNET® nodes
present on any of the ARCNET networks. This program is used to verify that the network
drivers are installed, the configuration is correct, and network connectivity exists to all
network nodes.
Each device on an ARCNET network is given a unique address. This address is used
in the Site Directory CONFIG.DAT file to match units with ARCNET addresses. The
ARCWHO program uses the ARCNET driver to poll for nodes. All nodes found are listed
regardless of what type of node it is, for example, turbine control, HMI, or Historian.
ARCWHO is a command line utility program.
Ø To start the ARCWHO command line utility: open a GeCssTci Command

command: ARCWHO
If run with the /? parameter a help page is displayed. If the Mark V feature in
WorkstationST component is running then ARCWHO can determine the network number
and network type for each network and include that in its report. If it is not running it is
not able to report on the network numbers and network types, but it can still produce a
list of the nodes found. All node addresses are displayed in HEX, which is how they are
specified in the CONFIG.DAT file.

The following example displays the ARCWHO help page:
ARCWHO - Map of ARCNET (and CSF) networks.

ARCWHO is a utility program that will generate a list
of nodes that are found on an ARCNET or CSF.
It does this by attempting to send a message
to each node and then looks at the status of the
message send. If the send was successful it adds
the address to the list of valid addresses.
If ARCWHO is run while a Turbine Control Interface

is running, such as TCI or HST, then the list of networks
to scan is already defined. If no such list is available,
ARCWHO will scan for the networks to process.
While scanning, the network number and network type
is not known.
If no networks are reported, it probably means that the

ARCNET device driver has not been started.
The network reconfiguration count indicates th

enumber of times that the network has undergone
reconfiguration. Networks will reconfigure when a
node is added or removed from the network, or when
power is cycled on a node. Extra reconfigurations are a
sign of communications problems.
The following example displays the results of running ARCWHO on an HMI connected to
a system with a single Stagelink:
E:\Site_ST\>arcwho
Network #1: A Stagelink using device CCSI20020Dev1
MY ADDRESS: 1F
NODES FOUND: FE FC FA 1E
E:\Site_ST\>
In this example, the HMI was assigned the ARCNET address 1F, which is typical for
the first HMI. There are four ARCNET nodes visible, at addresses FE, FC, FA, and 1E.
This is typical of a site with three Mark V controllers (addresses FE, FC, and FA) and
one other HMI (1E).

VIEW2 - View High-speed Mark V Data
VIEW2 is a command line utility that collects high-speed turbine data from a Mark V
controller into a memory buffer. When the buffer fills or the collection is stopped by
the user, the data is formatted into ASCII and saved in a disk file. The data contains a
unit-defined time tag, and the values for each of the points requested. It is commonly used
for conducting high-speed data collection during a specific test, where the duration of the
test (or its conclusion) is known.
All points collected must be from the same turbine control. Up to 50 points can be
collected. A Mark V controller can support data at up to 32 Hz.
When performing advanced diagnostics, it is often handy to be able to collect data at or

even above the frame rate of the controller. It allows for the collection of data as fast as
the controller supports it, and saves that data into a disk file for later analysis. All data is
time tagged by the unit when the data was sent.
Because many of these tests are repetitive in nature, the list of points to be collected can
be stored in a Point List file. The name of the Point List file is then passed to the program,
preventing having to type in each point name every time the test is run. The point list file
is an ASCII file containing a list of point names, one point name per line.
Operation
VIEW2 is a command line utility program.
Ø To start the VIEW2 command line utility: open a GeCssTci Command

the command: VIEW2
If run with no parameters or the /? parameter, a help screen is provided.

The following is a sample help screen:
E:\Site_ST\UNIT1>VIEW2 /?
VIEW2 - VIEW HIGH SPEED TURBINE DATA
THIS PROGRAM WILL COLLECT HIGH SPEED DATA FROM THE TURBINE AND SAVE
IT IN A MEMORY DATA BUFFER. WHEN THE BUFFER FILLS (OR A USER
SPECIFIED NUMBER OF SAMPLES IS REACHED) THE DATA IS WRITTEN INTO A
FILE FOR ANALYSIS. IT CAN COLLECT DATA AS FAST AS THE PROCESSOR CAN
SUPPLY IT. UP TO 50 POINTS CAN BE COLLECTED, BUT DO NOT ASK FOR MORE
THAN 29 IF YOUR ANALYSIS ROUTINES CAN NOT HANDLE LINES LONGER THAN
256 CHARACTERS.
COMMAND FORMAT: VIEW2 [OPTIONS] [@POINTLIST_FILE] OUTPUT_FILE

OPTIONS ARE:
/UNIT=<UNIT> WHERE <UNIT> IS THE UNIT NAME
/PROC=<PROC> WHERE <PROC> IS THE NAME OF THE PROCESSOR (OR CORE)
/SCAN=<INT> WHERE N IS MULTIPLIER OF PROCESSOR SCAN RATE (1=EVERY)
/SAMPLES=<INT> WHERE N IS MAXIMUM NUMBER OF SAMPLES
DEFAULTS:
/UNIT IS REQUIRED AND DOES NOT HAVE A DEFAULT VALUE
/PROC DEFAULTS TO "C" FOR A MARK V
/SCAN (1=EVERY SCAN, 2 = EVERY OTHER SCAN...)
- MARK V: BASIC SCAN RATE = 1/32 SECOND, DEFAULT IS 1 FOR 32 HZ
/SAMPLES DEFAULTS TO AS MANY AS WILL FIT IN A 1 MB MEMORY BUFFER
E:\Site_ST\UNIT1>
In the following example, two points were collected from a Mark V at the default rate.
The user hit a key after 2210 samples had been collected when the test was done.
E:\Site_ST\UNIT1>VIEW2 /UNIT=T1 /PROC=R VIEW2.OUT

OUTPUT WILL BE WRITTEN TO THE FILE VIEW2.OUT
TO READ A POINT LIST FROM A FILE, ENTER @FILENAME AS A PROGRAM
PARAMETER.
CURRENT UNIT IS: T1
ENTER POINTNAME[1]: FSR
ENTER POINTNAME[2]: CPD
ENTER POINTNAME[3]:
## UNIT POINTNAME SCALE
-- ---- ------------ -----
1 T1 FSR %
2 T1 CPD PSI
MEMORY FOR DATA SAMPLES: 1048570 BYTES
SIZE OF EACH DATA SAMPLE: 10 BYTES
MAXIMUM NUMBER OF SAMPLES: 104857 SAMPLES
NUMBER OF SAMPLES PER SECOND: 32 SAMPLES/SEC
DURATION OF SAMPLES: 3276 SECONDS
2 % - PERCENT OF SAMPLE BUFFER FILLED. << HIT ANY KEY TO STOP.>>
2210 SAMPLES TO BE WRITTEN TO THE OUTPUT FILE.
0 SAMPLES LEFT TO WRITE.
THE MAXIMUM PENDING MESSAGE QUEUE DEPTH WAS 2.
OUTPUT HAS BEEN WRITTEN TO FILE VIEW2.OUT.
E:\Site_ST\UNIT1>

The results can be found in the VIEW2.OUT file. The following is a sample of the
output file.
F:\UNIT1>TYPE VIEW2.OUT
-- ---- ------------ -----
1 T1 FSR %
2 T1 CPD PSI
08-DEC 11:23:10.937 16.02 101.6
08-DEC 11:23:10.968 16.02 101.6
08-DEC 11:23:11.000 16.02 101.6
08-DEC 11:23:11.031 16.02 101.6
08-DEC 11:23:11.062 16.02 101.6
08-DEC 11:23:11.093 16.02 101.6
08-DEC 11:23:11.125 16.02 101.6
08-DEC 11:23:11.156 16.02 101.6
08-DEC 11:23:11.187 16.02 101.6
08-DEC 11:23:11.218 16.02 101.6
08-DEC 11:23:11.250 16.02 101.6
08-DEC 11:23:11.281 16.02 101.6
<<< AND SO ON >>>

VIEW2T - View High-speed Mark V Data, Triggered
VIEW2T is a command line utility that collects high-speed turbine data from a Mark V
controller into a circular memory buffer. The first point collected is a logical point used
to trigger the saving of the data to a disk file. When the trigger-point transitions in the
user-defined direction, the contents of the memory buffer are written to a disk file for
analysis. The program can be configured to collect samples before and after the trigger
signal transitions, so the trigger signal can be used to indicate the start, end, or any
point within the test. The data contains a unit-defined time tag and the values for each
of the points requested.
VIEW2T is commonly used for conducting high-speed data collection during a specific
test, where a logic signal can be used to trigger the saving of the data. It is also useful
when a particular condition does not occur very often, since it can be left running
continuously watching for the trigger signal. When the trigger signal transitions it saves
the data then exits.
collected. A Mark V controller can support data at up to 32 Hz.
When performing advanced diagnostics, it is often useful to collect data at, or even above,
the frame rate of the controller, but only trigger the saving of data when a specified logic
signal makes a specified transition. This allows the program to collect data for long
periods of time, but only save it for analysis when a certain condition occurs. All data
collected is time tagged by the controller when the data was sent.
avoiding having to type in each point name every time the test is run. The point list file is
an ASCII file containing a list of point names, one point name per line.
Operation
VIEW2T is a command line utility that collects high-speed turbine data from a Mark V
controller into a circular memory buffer. The first point collected is a logical point used
to trigger the saving of the data to a disk file. When the trigger-point transitions in the
user-defined direction, the contents of the memory buffer are written to a disk file for
analysis. The program can be configured to collect samples before and after the trigger
signal transitions, so the trigger signal can be used to indicate the start, end, or any
point within the test. The data contains a unit-defined time tag and the values for each
of the points requested.
VIEW2T is commonly used for conducting high-speed data collection during a specific
test, where a logic signal can be used to trigger the saving of the data. It is also useful
when a particular condition does not occur very often, since it can be left running
continuously watching for the trigger signal. When the trigger signal transitions it saves
the data then exits.
VIEW2T is a command line utility.
Ø To start the VIEW2T command line utility: open a GeCssTci Command

the command: VIEW2T

The following displays a sample help screen:
E:\Site_ST\UNIT1>VIEW2T /?
VIEW2T - VIEW TRIGGERED HIGH SPEED TURBINE DATA
THIS PROGRAM WILL COLLECT HIGH SPEED DATA FROM THE TURBINE AND SAVE
IT IN A CIRCULAR MEMORY BUFFER. WHEN THE FIRST POINT SPECIFIED (A
LOGIC POINT) TRANSITIONS IT WILL COLLECT A USER DEFINED NUMBER OF
POST-TRIGGER RECORDS AND THEN WRITE THE DATA INTO A FILE FOR
ANALYSIS. IT CAN COLLECT DATA AS FAST AS THE PROCESSOR CAN SUPPLY
IT.
UP TO 50 POINTS CAN BE COLLECTED, BUT DO NOT ASK FOR MORE THAN 29 IF
YOUR ANALYSIS ROUTINES CAN NOT HANDLE LINES LONGER THAN 256
CHARACTERS.
COMMAND FORMAT: VIEW2T [OPTIONS] [@POINTLIST_FILE] OUTPUT_FILE
OPTIONS ARE:
/UNIT=<UNIT> WHERE <UNIT> IS THE UNIT NAME
/PROC=<PROC> WHERE <PROC> IS THE NAME OF THE PROCESSOR (OR CORE)
/SCAN=<INT> WHERE N IS MULTIPLIER OF PROCESSOR SCAN RATE (1=EVERY)
/SAMPLES=<INT> WHERE N IS MAXIMUM NUMBER OF SAMPLES
/POST=N WHERE N IS NUMBER OF SAMPLES AFTER TRIGGER
/TRIG=0 TRIGGER UPON DROPOUT OF THE FIRST SIGNAL.
/TRIG=1 TRIGGER UPON PICKUP OF THE FIRST SIGNAL.
DEFAULTS:
/UNIT IS REQUIRED AND DOES NOT HAVE A DEFAULT VALUE
/PROC DEFAULTS TO "C" FOR A MARK V
/SCAN (1=EVERY SCAN, 2 = EVERY OTHER SCAN...)
- MARK V: BASIC SCAN RATE = 1/32 SECOND, DEFAULT IS 1 FOR 32 HZ
/SAMPLES DEFAULTS TO AS MANY AS WILL FIT IN A 1 MB MEMORY BUFFER
/POST DEFAULTS TO ONE, IT SHOWS THE TRIGGER RECORD BUT NO MORE
/TRIG DEFAULTS TO 1, TRIGGER ON THE PICKUP OF THE SIGNAL
E:\Site_ST\UNIT1>

In the following example, six vibration-related signals were captured, triggered by a
high vibration alarm. There were 3200 samples defined in the collection with 100 of
them coming after the trigger. The points were collected from a Mark V at its default
rate of 32 Hz. The results were written to a file in the current default directory called
TRIP_VIB.TXT.
E:\Site_ST\UNIT1> VIEW2T /UNIT=T1 /PROC=R /SAMPLES=3200 /POST=100

TRIP_VIB.TXT
OUTPUT WILL BE WRITTEN TO THE FILE TRIP_VIB.TXT
TO READ A POINT LIST FROM A FILE, ENTER @FILENAME AS A PROGRAM
PARAMETER
CURRENT UNIT IS: T1
ENTER POINTNAME[1]: L63STX_ALM
ENTER POINTNAME[2]: BB1
ENTER POINTNAME[7]: BB_MAX
ENTER POINTNAME[8]:
-- ---- ------------ -----
1 T1 L63STX_ALM LOGIC
2 T1 BB1 IN/S
3 T1 BB2 IN/S
4 T1 BB3 IN/S
5 T1 BB4 IN/S
6 T1 BB5 IN/S
7 T1 BB_MAX IN/S
MEMORY FOR DATA SAMPLES: 64000 BYTES
SIZE OF EACH DATA SAMPLE: 20 BYTES
MAXIMUM NUMBER OF SAMPLES: 3200 SAMPLES
NUMBER OF SAMPLES PER SECOND: 32 SAMPLES/SEC
DURATION OF SAMPLES: 100 SECONDS
SAMPLES AFTER TRIGGER: 100 SAMPLES
12 % - LOCATION IN CIRCULAR SAMPLE BUFFER. <<HIT ANY KEY TO
STOP.>>
3200 SAMPLES TO BE WRITTEN TO THE OUTPUT FILE.
THE MAXIMUM PENDING MESSAGE QUEUE DEPTH WAS 3.
OUTPUT HAS BEEN WRITTEN TO FILE TRIP_VIB.TXT.
E:\Site_ST\UNIT1>

The results can be found in the TRIP_VIB.TXT file. The following is a sample of the
output file:
E:\Site_ST\UNIT1> TYPE TRIP_VIB.TXT

-- ---- ------------ -----
1 T1 L63STX_ALM LOGIC
2 T1 BB1 IN/S
3 T1 BB2 IN/S
4 T1 BB3 IN/S
5 T1 BB4 IN/S
6 T1 BB5 IN/S
7 T1 BB_MAX IN/S
26-OCT 10:30:05.687 0 0.28 0.30 0.29 0.28 0.30 0.30
26-OCT 10:30:05.718 0 0.28 0.30 0.29 0.28 0.31 0.31
26-OCT 10:30:05.750 0 0.28 0.31 0.30 0.29 0.31 0.31
26-OCT 10:30:05.781 0 0.29 0.32 0.30 0.29 0.30 0.32
26-OCT 10:30:05.812 0 0.29 0.31 0.30 0.29 0.31 0.31
<< and so on >>
VIEWPV - View High-speed Pre-vote Turbine Data

VIEWPV is a command line utility that collects high-speed pre-vote turbine data from a
Mark V controller into a memory buffer. When the buffer fills or the collection is stopped
by the user, the data is formatted into ASCII and saved in a disk file. The data contains a
unit defined time tag, and the <R>, <S>, and <T> values for each of the points requested.
VIEWPV is sometimes used to diagnose intermittent problems with sensors associated
with voted points. It is more common to use the pre-vote Data Display to investigate
most issues relating to voted data. This program is only used when a log of the results is
required, or data is required at high-speeds.
All points collected must be from the same turbine control. Only points that are fast-voted
can be collected using this program. Up to 16 points with three values per point can
be collected, which results in 48 values.
For advanced diagnostics, it is sometimes useful to be able to collect pre-vote data at or

even above the frame rate of the controller. VIEWPV allows collection of pre-vote data as
fast as the controller supports it, and saves that data into a disk file for later analysis. All
data is time tagged by the unit when the data was scanned.
The pre-vote data all comes from the <C> or <D> controller, which keeps copies of
the pre-vote data packets from each controller. This utility obtains the contents of these
pre-vote data packets to provide its information. This program does not query the
individual processors.
Because many of these tests are repetitive, the list of points to be collected can be stored in
a Point List file. The name of the Point List file is then passed to the program, preventing
having to type in each point name every time the test is run. The point list file is an ASCII
file containing a list of point names, one point name per line.
Note When the data must be obtained from each processor, VIEWQ is used

Operation
VIEWPV is a command line utility program.
Ø To start the VIEWPV command line utility: open a GeCssTci Command

the command: VIEWPV
The following is a sample help screen:
E:\Site_ST\UNIT1>VIEWPV /?
VIEWPV - VIEW HIGH SPEED TURBINE PREVOTE DATA
This program will collect high speed PreVote data from the
Turbine and save it in a memory data buffer. When the buffer
fills (or a user specified number of samples is reached) the
data is written into a file for analysis. It can collect data
as fast as the processor can supply it.
Up to 16 points can be collected, but do not ask for more than 9
if your analysis routines can not handle lines longer than 256
characters.
COMMAND FORMAT: VIEWPV [options] [@pointlist_file] output_file
Options are:
/UNIT=<unit> where <unit> is the unit name
/PROC=<proc> where <proc> is the name of the processor (or
core)
/SCAN=<int> where n is multiplier of processor scan rate
(1=every)
/SAMPLES=<int> where n is maximum number of samples
/[NO]SEP show separators in output file
DEFAULTS:
/UNIT is required, and must be a Mark V unit
/PROC defaults to "C"
/SCAN (1=every scan, 2 = every other scan...)
- Mark V: Basic scan rate = 1/32 second, default is 1 for 32 Hz
/SAMPLES defaults to as many as will fit in a 1 MB memory buffer
/SEP defaults to show data separators in output file
E:\Site_ST\UNIT1>

The test concluded when the memory buffer was full, and 100 samples were taken. The
results can be found in the VIEWPV.OUT file.
E:\Site_ST\UNIT1>VIEWPV /unit=T1 /samples=100 viewpv.out

Output will be written to the file VIEWPV.OUT
To read a point list from a file, enter @filename as a program
parameter.
Current unit is: T1
Enter pointname[1]: BB1
## Unit Pointname Scale
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
Memory for data samples: 1800 Bytes
Size of each data sample: 18 Bytes
Maximum number of samples: 100 Samples
Number of samples per second: 32 Samples/sec
Duration of samples: 3 Seconds
100% - Percent of sample buffer filled. <<Hit any key to stop.>>
100 Samples to be written to the output file.
0 Samples left to write.
The maximum pending message queue depth was 1.
Output has been written to file VIEWPV.OUT.
E:\Site_ST\UNIT1>

The following output file displays the <R>, <S>, and <T> values for each of the points
requested. All three values for the first point are displayed, then the three values for the
next point, and so on. Unless the /NOSEP option is used, a visual separator is displayed
between each point. Within each separated section, the <R> value is displayed first,
followed by the <S> value, and the <T> value.
E:\Site_ST\UNIT1>type viewpv.out
## Unit Pointname Sacle
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
05-FEB 10:10:52.156 0.32 0.32 0.32 | 0.32 0.32 0.32
05-FEB 10:10:52.187 0.32 0.32 0.32 | 0.32 0.32 0.32
05-FEB 10:10:52.218 0.34 0.34 0.34 | 0.33 0.33 0.33
05-FEB 10:10:52.250 0.34 0.34 0.34 | 0.33 0.33 0.33
05-FEB 10:10:52.281 0.28 0.28 0.28 | 0.27 0.27 0.27
05-FEB 10:10:52.312 0.28 0.28 0.28 | 0.27 0.27 0.27
05-FEB 10:10:52.343 0.29 0.29 0.29 | 0.29 0.29 0.29
05-FEB 10:10:52.375 0.29 0.29 0.29 | 0.29 0.29 0.29
05-FEB 10:10:52.406 0.31 0.31 0.31 | 0.30 0.30 0.30
05-FEB 10:10:52.468 0.32 0.32 0.32 | 0.32 0.32 0.32
05-FEB 10:10:52.500 0.32 0.32 0.32 | 0.32 0.32 0.32
05-FEB 10:10:52.531 0.34 0.34 0.34 | 0.33 0.33 0.33
05-FEB 10:10:52.562 0.34 0.34 0.34 | 0.33 0.33 0.33
<< and so on >>
VIEWQ - View Multi-processor High-Speed Turbine

Data
VIEWQ is a command line utility that collects high-speed turbine data from each of the
<R>, <S>, and <T> processors in a Mark V controller into a memory buffer. When the
buffer fills, or the user stops the collection, the data is formatted into ASCII and saved in a
disk file. The data contains a record from each processor containing a unit-defined time
tag and the data values for each of the points requested. This program is sometimes used
to track down problems with CSDB values that differ from processor to processor. Unlike
the pre-vote data collected using VIEWPV, any point in the database can be collected
with this program, not just voted signals.
collected with three values per point, which results in 48 values.
When performing advanced diagnostics, it is sometimes useful to collect CSDB data from
each controller at or even above the frame rate of the controller. VIEWQ allows data
collection as fast as the controller supports it, and saves the data into a disk file for later
analysis. All data is time tagged by the unit when the data was scanned.
The data comes from each controller processor, meaning that it takes three individual
messages to collect the data from the <R>, <S>, and <T> processors. The time tags from
the three processors are not guaranteed to match, but all of the data is time tagged by the
scanning processor so that it can be analyzed correctly. At high speeds, the data may arrive
out of time sequence order, but the program sorts the data by time and processor before
placing it into the data file. This can be overridden if desired.

preventing having to type in each point name every time the test is run. The point list file
is an ASCII file containing a list of point names, one point name per line.
Operation
VIEWQ is a command line utility program.
Ø To start the VIEWQ command line utility: open a GeCssTci Command

the command: VIEWQ
The following example displays a help screen:
E:\Site_ST\UNIT1>VIEWQ /?
VIEWQ - VIEW HIGH SPEED TURBINE CONTROLLER DATA
This program will collect high speed data from each controller
and save it in a memory data buffer. When the buffer fills (or a
user specified number of samples is reached) the data is written
into a file for analysis. It can collect data as fast as the
processor can supply it.
Up to 16 points can be collected, but do not ask for more than 9
Up to 16 points can be collected, but do not ask for more than
9 if your analysis routines can not handle lines longer than
256 characters. Because the data can arrive out of order, the
program will sort the output according to time and processor
instead of displaying it in the order received. If you do not
want the data sorted, use the /NOSORT option.
COMMAND FORMAT: VIEWQ [options] [@pointlist_file] output_file
Options are:
/UNIT=<unit> where <unit> is the unit name
/SCAN=<int> where n is multiplier of processor scan rate
(1=every)
/SAMPLES=<int> where n is maximum number of samples
/[NO]SEP show separators in output file
/[NO]SORT defines if output is time sorted
DEFAULTS:
/UNIT is required, and must be a Mark V unit
/SCAN (1=every scan, 2 = every other scan...)
- Mark V: Basic scan rate = 1/32 second, default is 1 for 32 Hz
/SAMPLES defaults to as many as will fit in a 1 MB memory buffer
/SEP defaults to show data separators in output file
/SORT defaults to time sorting the data
E:\Site_ST\UNIT1>

The test concluded when the memory buffer was full, and 200 samples were taken. The
results can be found in the VIEWQ.OUT file.
E:\Site_ST\UNIT1>VIEWQ /unit=T1 /samples=200 viewq.out

Output will be written to the file VIEWQ.OUT
To read a point list from a file, enter @filename as a program
parameter.
Current unit is: T1
Enter pointname[1]: bb1
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
Memory for data samples: 2200 Bytes
Size of each data sample: 11 Bytes
Maximum number of samples: 200 Samples
Number of samples per second: 96 Samples/sec
Duration of samples: 2 Seconds
100% - Percent of sample buffer filled.
<< Hit any key to stop. >> Sorting
200 Samples to be written to the output file.
0 Samples left to write.
The maximum pending message queue depth was 1.
Output has been written to file VIEWQ.OUT.
E:\Site_ST\UNIT1>

The output file displays the records received from the <R>, <S>, and <T> processors.
Each record has one value for each point. The points are displayed similar to VIEWPV
with the points collected into sections. Unless the /NOSEP option is used, a visual
separator is displayed between each point. Within each separated section, the <R> value
is the first column, followed by the <S> value, and the <T> value. During times of high
communication traffic loading, it is possible to miss a record. In this case there will simply
be a line missing in the data file.

-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
05-FEB 16:01:46.968 0.29 | 0.29
05-FEB 16:01:46.968 0.29 | 0.29
05-FEB 16:01:46.968 0.29 | 0.29
05-FEB 16:01:47.000 0.29 | 0.29
05-FEB 16:01:47.000 0.29 | 0.29
05-FEB 16:01:47.000 0.29 | 0.29
05-FEB 16:01:47.031 0.31 | 0.30
05-FEB 16:01:47.031 0.31 | 0.30
05-FEB 16:01:47.031 0.31 | 0.30
05-FEB 16:01:47.062 0.31 | 0.30
05-FEB 16:01:47.062 0.31 | 0.30
05-FEB 16:01:47.062 0.31 | 0.30
05-FEB 16:01:47.093 0.32 | 0.32
05-FEB 16:01:47.093 0.32 | 0.32
05-FEB 16:01:47.093 0.32 | 0.32
05-FEB 16:01:47.125 0.32 | 0.32
05-FEB 16:01:47.125 0.32 | 0.32
05-FEB 16:01:47.125 0.32 | 0.32
05-FEB 16:01:47.156 0.34 | 0.33
05-FEB 16:01:47.156 0.34 | 0.33
05-FEB 16:01:47.156 0.34 | 0.33
<<< and so on >>>
VIEWn Analysis Programs

Some of the VIEWn routines do not collect data, but instead analyze or prepare data
collected by the other programs for analysis. This includes statistical analysis (Max, Min,
Standard Deviations…) and putting the information into a format that can be imported
into spreadsheet programs (such as Microsoft Excel).
• VIEW_LIM View Limits. This program scans the output from VIEW1, VIEW2
or VIEW2T and reports each signal's minimum and maximum value along with
the time of that value.
• VIEW_SD View Standard Deviation. This program scans the output from VIEW1,
VIEW2, or VIEW2T and reports each signal's mean value and standard deviation.
• VIEW2ASC View File to ASCII File Conversion. This program reads the output
from VIEW1, VIEW2, or VIEW2T and generates a comma-separated value (CSV)
file suitable for import by most spreadsheet and database application programs.

VIEW_LIM - View Data Analysis, Limits
VIEW_LIM is a command line utility that reads the output of VIEW1, VIEW2, or
VIEW2T and provides a summary analysis of the range limits of each individual point.
For each point collected, it indicates the maximum value found, the minimum value
found, and the times each was recorded. This is often useful when looking at large
(multi-megabyte) data files containing lots of data.
Data collection programs such as VIEW1 or VIEW2 can collect large amounts of data.
This is often done during steady state plant operation, and the data is later analyzed for
variability or disturbances found during this steady state operation. VIEW_LIM scans
through this data and notes the minimum value, maximum value, and the times associated
with each for every point in the file. This can be used to target further investigation, or
eliminate further investigation if the values all lie within an acceptable range.
Operation
VIEW_LIM is a command line utility program.
Ø To start the VIEW_LIM command line utility: open a GeCssTci Command

command: VIEW_LIM
If run with no parameters or the /? parameter, a help screen is provided. If the same
maximum or minimum value is found multiple times in the data file, the time tag displayed
indicates the first occurrence of the value.
The following example displays a help screen.
E:\Site_ST\UNIT1>VIEW_LIM /?
VIEW_LIM - VIEW FILE LIMITS ANALYSIS
This program will sift through the output of VIEW1 or
VIEW2 and report on the minimum and maximum values found
for each point.
COMMAND FORMAT: VIEW_LIM filename
where "filename" is the name of the file to be read. The
resulting report is written to standard output, so you can vector
the report to a file using the normal DOS redirection commands,
ie: VIEW_LIM filename >report_filename
E:\Site_ST\UNIT1>

The following example is a data analysis by VIEW_LIM:
E:\Site_ST\UNIT1>VIEW_LIM view1.out
VIEW_LIMITS ANALYSIS OF FILE view1.out
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
3 T1 BB3 in/s
4 T1 BB4 in/s
5 T1 BB5 in/s
6 T1 BB_MAX in/s
Point Min Max Time of Min Time of Max
----- ------- ------- ----------------- -----------------
1 0.28 0.34 05-FEB 17:07:39 05-FEB 17:07:43
2 0.27 0.33 05-FEB 17:07:39 05-FEB 17:07:43
3 0.27 0.33 05-FEB 17:07:43 05-FEB 17:07:42
4 0.27 0.33 05-FEB 17:07:43 05-FEB 17:07:42
5 0.28 0.34 05-FEB 17:07:39 05-FEB 17:07:43
6 0.28 0.34 05-FEB 17:07:39 05-FEB 17:07:45
In the preceding example, six vibration points were captured using VIEW1 into the file
VIEW1.OUT. This file was then analyzed by VIEW_LIM, to display the range of values
found for each point in the file. The same type of information is available from VIEW2
output, but that also displays subseconds on the time tags.
VIEW_SD - View Data Analysis, Standard Deviations

VIEW_SD is a command line utility that reads the output of VIEW1, VIEW2, or VIEW2T
and provides a summary analysis of the standard deviations of each individual point. For
each point collected, it calculates the point's minimum value, maximum value, mean
value, and standard deviation. This is often useful when looking at large (multi-megabyte)
data files containing lots of data.
If further analysis is indicated, Data collection programs such as VIEW1 or VIEW2 can collect large amounts of data.
VIEW_LIM is useful for finding This is often done during steady-state plant operation, and the data is later analyzed for
the times of the disturbances. the variability or disturbances found during this steady-state operation. VIEW_SD scans
through this data and notes the minimum value and maximum value. It then calculates each
point's mean value and sample (n-1) standard deviation. This can be used to target further
investigation, or eliminate further investigation if the results lie within an acceptable range.
Ø To start the VIEW_SD command line utility: open a GeCssTci Command

command: VIEW_SD

The following is a sample help screen
E:\Site_ST\UNIT1>VIEW_SD /?
VIEW_SD - VIEW FILE STANDARD DEVIATION
This program will sift through the output of VIEW1 or VIEW2 and
report on the mean and standard deviation found for each point.
COMMAND FORMAT: VIEW_SD filename
where "filename" is the name of the file to be read. The
resulting report is written to standard output, so you can vector
the report to a file using the normal DOS redirection commands,
ie: VIEW_SD filename >report_filename
E:\Site_ST\UNIT1>
The following example shows a statistical analysis by VIEW_SD:
E:\Site_ST\UNIT1>VIEW_SD view1.out
VIEW_SD ANALYSIS OF FILE view1.out
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
3 T1 BB3 in/s
4 T1 BB4 in/s
5 T1 BB5 in/s
6 T1 BB_MAX in/s
Point Min Max Mean Std Deviation
----- ------- ------- ----------------- -----------------
1 0.28 0.34 0.308000 0.021794
2 0.27 0.33 0.302000 0.021794
3 0.27 0.33 0.298000 0.021794
4 0.27 0.33 0.298000 0.021794
5 0.28 0.34 0.308000 0.021794
6 0.28 0.34 0.308400 0.021541
E:\Site_ST\UNIT1>
In this example, six vibration points were captured using VIEW1 into the file
VIEW1.OUT. This file was then analyzed by VIEW_SD, to display the range of values
found for each point in the file, and the calculated mean and standard deviation.

VIEW2ASC - Convert View Data to ASCII
VIEW2ASC is a command line utility that reads the output files from VIEW1, VIEW2,
or VIEW2T and converts them to an ASCII format that can be imported into most
spreadsheet programs. It can be used to export only some of the points in the file, thereby
reducing the size of the data imported into the spreadsheet program. It also converts
the time tags from absolute calendar time tags to a file relative time tag that is suitable
for use in a spreadsheet X-Y plot.
Data collection programs such as VIEW1 and VIEW2 collect lots of data and can write
that data into a disk file. Once this data has been collected, it is often useful to transfer that
data into a spreadsheet program for further analysis or charting. Two problems are often
encountered during this process:
• The time tags used by the VIEW programs use an absolute calendar format that is not
understood by many spreadsheet programs. This is especially true of VIEW2 data,
which contains subsecond data. Many spreadsheet programs refuse to understand
time tags with fractional seconds.
• Some spreadsheet programs do not handle the large amounts of data supplied by the
VIEW programs very well. VIEW files can contain data for up to 50 points, which
may be more than the program can accept. This can be due to the large memory
requirements, or the fact that the program cannot import from lines containing more
than 256 characters.
VIEW2ASC creates its output file with the time converted from a calendar format to a real
number format. This real number is the number of seconds into the test, where the first
time tag in the file (with the subsecond field zeroed) indicates the time of the start of the
test. This new time into test value can be used with the spreadsheet X-Y plot to provide
an accurate plot of the value versus time.
VIEW2ASC also removes the header indicating the point sources, leaving only the actual
data lines.
VIEW2ASC allows the user to indicate which points in the data file should be included
in the ASCII file that will be passed into the spread sheet program. By selecting only
the points desired, the total memory requirements or line length requirements of the
spreadsheet program can be met.

Operation
VIEW2ASC is a command line utility that reads the output files from VIEW1, VIEW2,
or VIEW2T and converts them to an ASCII format that can be imported into most
spreadsheet programs. It can be used to export only some of the points in the file, thereby
reducing VIEW2ASC.
Ø To start the VIEW2ASC command line utility: open a GeCssTci Command

command: VIEW2ASC
If run with no parameters or the /? parameter, a help screen is provided. The following
example is a help screen:
E:\Site_ST\UNIT1>VIEW2ASC /?
VIEW2ASC - VIEW TO ASCII FILE CONVERSION
This program will take the output from VIEW1 or VIEW2 and
reformat it so that it can be input into most spreadsheet and
database programs. The time is converted to a raw number of
seconds and the data is left as is. Because many spreadsheets
can not accept as many numbers as are in the VIEWx file (memory
limitations) the user must specify which points are to be
included in the output file. This is done as a list of the point
numbers in the VIEWx file.
COMMAND FORMAT: VIEW2ASC pt#,pt#,pt#...pt# infile outfile
The list of point numbers must be one WORD. No spaces are
allowed, only numbers separated by commas.
E:\Site_ST\UNIT1>

In the following example, six vibration points were captured using VIEW1 into the file
VIEW1.OUT. This file was then converted keeping all points.
E:\Site_ST\UNIT1>type view1.out
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
3 T1 BB3 in/s
4 T1 BB4 in/s
5 T1 BB5 in/s
6 T1 BB_MAX in/s
05-FEB 17:07:39 0.28 0.27 0.28 0.28 0.28 0.28
05-FEB 17:07:40 0.29 0.29 0.30 0.30 0.29 0.33
05-FEB 17:07:41 0.31 0.30 0.31 0.31 0.31 0.33
05-FEB 17:07:42 0.32 0.32 0.33 0.33 0.32 0.30
05-FEB 17:07:43 0.34 0.33 0.27 0.27 0.34 0.30
05-FEB 17:07:44 0.28 0.27 0.28 0.28 0.28 0.30
05-FEB 17:07:45 0.29 0.29 0.30 0.30 0.29 0.34
05-FEB 17:07:46 0.31 0.30 0.31 0.31 0.31 0.34
05-FEB 17:07:47 0.32 0.32 0.33 0.33 0.32 0.31
05-FEB 17:07:48 0.34 0.33 0.27 0.27 0.34 0.31
05-FEB 17:07:49 0.28 0.27 0.28 0.28 0.28 0.31
05-FEB 17:07:50 0.29 0.29 0.30 0.30 0.29 0.28
E:\Site_ST\UNIT1>VIEW2ASC 1,2,3,4,5,6 view1.out view1a.out
12 data points have been written to the file "view1a.out"
E:\Site_ST\UNIT1>TYPE view1a.out
0 0.28 0.27 0.28 0.28 0.28 0.28
1 0.29 0.29 0.30 0.30 0.29 0.33
2 0.31 0.30 0.31 0.31 0.31 0.33
3 0.32 0.32 0.33 0.33 0.32 0.30
4 0.34 0.33 0.27 0.27 0.34 0.30
5 0.28 0.27 0.29 0.28 0.28 0.30
6 0.29 0.29 0.30 0.30 0.29 0.34
7 0.31 0.30 0.31 0.31 0.31 0.34
8 0.32 0.32 0.33 0.33 0.32 0.31
9 0.34 0.33 0.27 0.27 0.34 0.31
10 0.28 0.27 0.28 0.28 0.28 0.31
11 0.29 0.29 0.30 0.30 0.29 0.28
E:\Site_ST\UNIT1>

In the following example, six vibration points were captured using VIEW2 into the file
VIEW2.OUT. This file was then converted keeping all points. With VIEW2 data, the
times include subseconds.
E:\Site_ST\UNIT1>TYPE view2.out
-- ---- ------------ -----
1 T1 BB1 in/s
2 T1 BB2 in/s
3 T1 BB3 in/s
4 T1 BB4 in/s
5 T1 BB5 in/s
7 T1 BB_MAX in/s
05-FEB 17:15:53.500 0.29 0.29 0.30 0.30 0.29 0.30
05-FEB 17:15:53.750 0.34 0.33 0.27 0.27 0.34 0.30
05-FEB 17:15:54.000 0.32 0.32 0.33 0.33 0.32 0.30
05-FEB 17:15:54.250 0.31 0.31 0.31 0.31 0.31 0.34
05-FEB 17:15:54.500 0.29 0.29 0.30 0.30 0.29 0.34
05-FEB 17:15:54.750 0.28 0.28 0.29 0.29 0.28 0.34
05-FEB 17:15:55.000 0.34 0.34 0.27 0.27 0.34 0.34
05-FEB 17:15:55.250 0.32 0.32 0.33 0.33 0.32 0.34
05-FEB 17:15:55.500 0.31 0.31 0.32 0.32 0.31 0.34
05-FEB 17:15:55.750 0.29 0.29 0.30 0.30 0.29 0.34
05-FEB 17:15:56.000 0.28 0.28 0.28 0.28 0.28 0.34
05-FEB 17:15:56.250 0.34 0.34 0.27 0.27 0.34 0.34
E:\Site_ST\UNIT1>VIEW2ASC 1,2,3,4,5,6 view2.out view2a.out
12 data points have been written to the file "view2a.out"
E:\Site_ST\UNIT1>TYPE view2a.out
0.500 0.29 0.29 0.30 0.30 0.29 0.30
0.750 0.34 0.33 0.27 0.27 0.34 0.30
1.000 0.32 0.32 0.33 0.33 0.32 0.30
1.250 0.31 0.30 0.31 0.31 0.31 0.34
1.500 0.29 0.29 0.30 0.30 0.29 0.34
1.750 0.28 0.27 0.28 0.28 0.28 0.34
2.000 0.34 0.33 0.27 0.27 0.34 0.34
2.250 0.32 0.32 0.33 0.33 0.32 0.34
2.500 0.31 0.30 0.31 0.31 0.31 0.34
2.750 0.29 0.29 0.30 0.30 0.29 0.34
3.000 0.28 0.27 0.28 0.28 0.28 0.34
3.250 0.34 0.33 0.27 0.27 0.34 0.34
E:\Site_ST\UNIT1>
In the preceding example, six vibration points were captured using VIEW2 into the file
VIEW2.OUT. This file was then converted keeping all points. With VIEW2 data, the
times include subseconds.

Notes

Chapter 3 Networks
Mark V System - StageLink

Communication between the HMI and the Mark V panels is by means of StageLink. In
its simplest configuration, StageLink connects one Mark V turbine control panel to a
single HMI (or node) across a single segment (refer to segment definition below). This
communication topology may be expanded to accommodate multiple HMIs and multiple
panels. For example, a single operator interface can be configured to issue commands to,
and receive turbine data from, multiple Mark V turbine controls. In addition, multiple
HMIs may be attached to the StageLink with each HMI communicating with multiple
control panels. In this way, StageLink provides communications flexibility for different
site needs.
The StageLink was designed specifically to address turbine control needs such as
downloading or uploading software between the Mark V and the HMI, issuing commands,
alarm management, and monitoring. Distributed control systems (DCS) interface to the
Mark V over a separate serial communication link routed to the HMI, typically using a
Modbus protocol.
This section provides guidance and rules for successfully designing StageLinks to
maximize communication link availability and network distances.
Terms of Reference
Terminology used in this Mark V section is as follows:
Node Any device connected to the StageLink system that has a valid address:
• A TCP core, which for a Mark V is a <C> core communications processor

• A <D> core backup communications processor
• An HMI
Where a specific core (communications processor) is meant, like <C>, t is explicitly

written <C> instead of TCP.
Repeater An electronic device that receives, amplifies, and re-transmits StageLink

signals. The TCP cores and a hub are considered repeaters, HMIs are not.
Hub For the StageLink, the hub is a 4-port repeater, with two coax ports and two
fiber-optic ports. The fiber-optic port converts the electrical signals to or from light pulses
for fiber-optic transmission or reception. The hub can also be used as a repeater to amplify
coax signals. It is not considered a node because it does not have an address.
Segment Any StageLink section that joins two repeaters or connects one repeater to one
or more high impedance devices, and ends with a terminating resistor. A segment may
have multiple taps for high impedance connections to HMIs.
GEH-6759B Chapter 3 Networks System Guide 3-1

StageLink Characteristics
The StageLink consists of a 2.5-MHz (2.5-Mps) ARCNET system that uses either
fiber-optic or standard RG-62 A/U copper cabling. Either type can be purchased with a
variety of insulation systems such as flame retardant Teflon™ or high-density polyethylene.
In applications that must meet IEC codes, GE recommends using armored co-axial cable.
These cable types have a metal sheath outer layer that functions as both a mechanical
shield and as an electrical conductor that can alleviate lightning induced disturbances on
short outdoor runs. This outer layer must be grounded at each building's entrance and exit.
Fiber-optic cabling prevents electromagnetic interference and is often a better alternative
for long outdoor segments.
Mark V ARCNET Local Area Network
ARCNET Feature Specification
Communication Type Baseband
Frequency or Speed 2.5 MHz or 2.5 Mbps
Propagation Delay (Maximum) 31 micro seconds
Maximum Network Length, based on 6,000 meters (19,690 ft)
Propagation Delay
Repeater Nodes TCP or <C> core
Other Repeaters Fiber-optic hubs
High Impedance Nodes HMI
Within the Mark V panels, the ARCNET cable is connected to the CTBA board. These
are located in the TCP communication processor. The CTBA board communicates
directly with the TCP communication processor. This data exchange is carried out through
the one internal port of a three-port repeater; the remaining two ports are for external
customer use. Signals entering any one of these three legs are amplified and sent out
through the other two. Therefore, a signal entering the first external port is sent to TCP
and re-transmitted on the second external port. Signals entering the internal port are
sent out on both external ports.
Should the CTBA or AAHA board lose control power, a relay de-energizes and connects
the two external ports. In this manner, all the other nodes on the Stage Link can continue
to function as long as the topology is designed in accordance with the distance rules
provided later in this Chapter.
Note Repeaters have a fail-safe design to maintain communication.
The HMI utilizes a single high-impedance port that distributes signals in both directions
on the StageLink through a T type connector. The ARCNET board within the HMI
receives data by tapping off a portion of signal transmitted on the StageLink. It does
not repeat the signal.

Cable Recommendations
If the turbine control application requires a segment too long for a co-axial cable, a
fiber-optic cable should be used. For more on fiber-optic installation, refer to the section
on Fiber-optics.
StageLink Cable Recommendations
Cable Type Recommendation
Copper Cable
Indoor Cable RG-62 A/U Co-axial Cable
Outdoor Cable Armored Co-axial or Tri-axial Cable
Connector Type BNC Male (both ends)
Fiber-optic Cable
Cable Multi-mode with 62.5-micron core and 120-micron
cladding
Connector Type ST bayonet
Hub Power 120 Vac/60 Hz or 240 Vac/50 Hz (Customer
supplied)
Hub Configuration 2 Co-axial ports and 2 Fiber-optic ports (4 ST type
connectors)
Summary of StageLink Topology Rules

A segment refers to the cable and nodes between two repeaters. The topology rules are
as follows:
• No loops are allowed.

• The maximum number of nodes allowed is 100.
• The maximum number of HMIs in one network is 16.
• The maximum time delay between any two nodes is 31 microseconds.
• Both ends of the StageLink must have a 93-ohm terminating impedance.
• Every node must have a unique network address.

Maximum Cable Segment Length Rules
Cable Segments Cable Lengths
Coax repeater to repeater 609.6 m (2000 ft)
Coax repeater to single HMI 609.6 m (2000 ft)
Coax repeater to more than one HMI 304.8 m (1000 ft)
HMI between two repeaters 304.8 m (1000 ft)
Maximum HMIs per segment 8
Fiber-optic cable hub-to-hub (62.5/120 micron fiber) 1825 m (5988 ft)
Minimum cable length between HMIs 1.5 m (4.9 ft)
Refer to the following figure StageLink Cable Segment Rules. The network diagrams in
this figure illustrate the segment rules. The following apply to these diagrams:
• TCP is a Mark V <C> or <D> core

• The TCP cores and active hubs are considered repeaters
• HMIs are not considered repeaters

StageLink Cable Segment Rules

Total Effective Distance Rules
Always calculate the total effective cable distance between the two network nodes that
have the longest effective distance. These are not always the nodes that are farthest apart
physically. Each repeater has a delay equal to the delay in 25 meters of cable. The
effective distance is calculated as follows:
Copper (coax) cable length in meters + (Fiber-optic cable length in meters* 1.25) +
(number of repeaters* 25 meters)
The total effective cable distance may not exceed 6000 meters.
The maximum 31-microsecond propagation delay is approximately equal to the delay in

6000 meters of cable. Because it is easier to calculate effective cable distance than it is to
measure propagation delay, this approximation is used. The deciding factor is propagation
delay, not total length. If questions arise about a particular application, it may be necessary
to measure the propagation delay.
Note Propagation delay decides the maximum cable length.
Complex Plant Application

Segments Totals and Comments

Segment S1 S2 S3 S4
Cable length, meters 270 30 55 270 625
Effective Cable length 75+625 = 700, well below the 6000 meter
3 TCPs @ 25 = 75
limit
Calculation of Maximum segment
with one node failure
Failure of node: TCP 1 TCP 2 TCP 3 * All combined segments have HMIs, so the
maximum length is 304.8 meters.
Results in a combined segment of: HMI1 to TCP1 to TCP2 to
TCP2 to HMI4 exceeds the limit.
TCP2 TCP3 HMI4
TCP1 to TCP3 is OK.
HMI1 to TCP2 is close to the limit but
300 85 325* should work if TCP1 fails, depending on the
conditions.
Total number of nodes 7 nodes, much less than the 100 maximum
Redundant System Rules

The Mark V system displayed in figure Redundant Stage Link has redundant
communication processors. The two StageLink systems, <C> and <D>, are not
interconnected. Interconnections are not allowed as they lower the communication
interface reliability, since both networks could be brought down by a common failure such
as a shorted coax or one node continuously transmitting.
The <C> and <D> cables can be routed independently to minimize opportunities for
a common failure.
Typically unit control nodes are connected in a daisy-chain configuration. A cable from
the <C> Stage Link is routed from one physical end of the daisy chain to the central
control room. The <D> cable to the central control room is attached to the opposite side of
the unit control string. In this way, a break in the cable or loss of power to a <C> and/or
<D> leaves all other nodes accessible from some HMI in the central control room.
On a system with a fiber-optic link, the fiber-optic repeater pair does not have bridging
relays. Some customers may therefore prefer to use two links to the central control
room, one from each end of the chain of unit controls as displayed in figure Redundant
StageLink. In this example, one set of HMIs in the central control room is operational if
any one of the four fiber-optic active hubs fails.

Redundant StageLink

Segments Totals
Segment S1 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11
Coax Cable length 6 3 30 30 180 30 150 3 6 438
Fiber-optic Cable 300 760 1360
Maximum Effective 2388, well below the 6000
(16TCPs @ 25) + (4 FOH @ 25) + 1.25* (600 + 760) + 438
Cable length meter limit
Calculation of Maximum
segment with one node
failure
Failure of node: TCP 1 TCP 2 TCP 3 TCP 4 TCP 5 TCP 6
Results in a combined FOH2 to TCP1 to TCP2 to TCP3 to TCP4 to TCP5 to
All are less than
segment of: TCP2 TCP3 TCP4 TCP5 TCP6 FOH4
609 or 304 meter
33 30 210 210 180 153 maximum
Total number of nodes 7 nodes, much less than the 100 maximum

Notes

GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com

Geh 6759 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Geh 6759 PDF

Transféré par

Droits d'auteur :

Formats disponibles

GE Energy GEH-6759B

© 2009 – 2012 General Electric Company, USA. All rights reserved.

* Trademark of General Electric Company

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

Your Name Today’s Date If needed, how can we contact

Superior Comparable Inferior Do not know Comments .............................................

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

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

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

Indicates a procedure, condition, or statement that should be

This equipment contains a potential hazard of electric shock,

Isolation of test equipment from the equipment under test

Warning To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused by

Always ensure that applicable standards and regulations are

2 Contents WorkstationST* Application Mark* V Feature

4 Contents WorkstationST* Application Mark* V Feature

Ø To create a Command Prompt window in the Site Directory: from the

Ø To create a Command Prompt window in a Unit Configuration Directory:

Configuration files contained in a unit-specific directory can be broken up into five

GEH-6759B Chapter 1 Mark* V System Guide 1-1

1-2 WorkstationST* Application Mark* V Feature

DDLOCATE IO.ASG FACTORY.ASG ALLOCSSP.ASG SITE.ASG

• ALARM.DAT containing process and diagnostic alarm messages (maximum case).

• LONGNAME.DAT containing CSDB pointname descriptions.

GEH-6759B Chapter 1 Mark* V System Guide 1-3

1-4 WorkstationST* Application Mark* V Feature

CSP Segment Files

GEH-6759B Chapter 1 Mark* V System Guide 1-5

Compiling Unit-specific Configuration Files

1-6 WorkstationST* Application Mark* V Feature

However, there is no automatic method of updating the values of control constants in

Note The Mark V Feature is an option in the WorkstationST Component Editor.

C:\Program Files\GE Energy\WorkstationST Features\TCI\DATA

GEH-6759B Chapter 1 Mark* V System Guide 1-7

1-8 WorkstationST* Application Mark* V Feature

GEH-6759B Chapter 1 Mark* V System Guide 1-9

• Red - Immediate acting

Personnel should keep clear of the area during an automatic

If no pushbuttons are visible, one of the following conditions is occurring:

• The test permissive, usually L3ADJ is not TRUE.

1-10 WorkstationST* Application Mark* V Feature

GEH-6759B Chapter 1 Mark* V System Guide 1-11

AUTOCALThe auto-calibrate display can be launched with the following optional

The following example specifies the unit name as T1:

AUTOCAL /UNIT:T1 Display actions are as follows:

• Tree View window

1-12 WorkstationST* Application Mark* V Feature

Auto-calibrate Display Dialog Boxes

GEH-6759B Chapter 1 Mark* V System Guide 1-13

The Control Constants Display has a header that includes:

The list of points has three columns:

1-14 WorkstationST* Application Mark* V Feature

Changing a Control Constant

Ø To change a Control Constant

Control Constants Display

Control Constants Adjust Display

GEH-6759B Chapter 1 Mark* V System Guide 1-15

Open a GeCssTci Command Prompt window (typically in the target unit’s

The unit is required for multi unit sites, for example:

The unit is optional if there is only one unit, for example

CONSTADJ /POINT:CSKATS Header Time tag

1-16 WorkstationST* Application Mark* V Feature