Professional Documents
Culture Documents
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.
To:
Reader Comments
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Fax: 1-540-387-8651
(GE Internal DC 8-278-8651)
Todays Date
Job Site
GE Requisition No.
Publication No.
Address
General Rating
Excellent
Contents
{
Organization
{
Technical Accuracy {
Clarity
{
Completeness
{
Drawings / Figures {
Tables
{
Referencing
{
Readability
{
Good
{
{
{
{
{
{
{
{
{
Fair
{
{
{
{
{
{
{
{
{
Poor
{
{
{
{
{
{
{
{
{
Additional Comments
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
Specific Suggestions (Corrections, information that could be expanded on, and such.)
Page No.
Comments
_____
_________________________________________________________________________________
_____
_________________________________________________________________________________
_____
_________________________________________________________________________________
_____
_________________________________________________________________________________
_____
_________________________________________________________________________________
_____
_________________________________________________________________________________
Other Comments (What you like, what could be added, how to improve, and such.) ________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
__________________________________________________________________________________________
Overall grade (Compared to publications from other manufacturers of similar products, how do you rate this publication?)
{ Superior
{ Comparable
{ Inferior
{ Do not know
Comment ____________________________________________
____________________________
____________________________
____________________________
GE Energy
Documentation Design, Rm. 293
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
Contents
Chapter 1 Overview
1-1
Introduction ...............................................................................................................................................1-1
HMI Summary...........................................................................................................................................1-1
System Configuration.....................................................................................................................1-1
Text Conventions ...........................................................................................................................1-3
Related Documentation .............................................................................................................................1-4
Chapter 2 Installation
2-1
Introduction ...............................................................................................................................................2-1
Login and Startup ......................................................................................................................................2-1
Initial Power Up .............................................................................................................................2-1
CIMPLICITY Project.....................................................................................................................2-3
Check Usernames and Passwords ..................................................................................................2-3
Chapter 3 Mark IV
3-1
Overview ...................................................................................................................................................3-1
Features, Utilities, and Tools.....................................................................................................................3-1
DDVAL - Data Dictionary Validation ...........................................................................................3-1
Chapter 4 Mark V
4-1
Contents i
Chapter 5 Mark VI
5-1
Mark VI Controller....................................................................................................................................5-1
Flash Downloader......................................................................................................................................5-1
EPA Log ....................................................................................................................................................5-1
Trend Recorder..........................................................................................................................................5-2
Auto Calibration ........................................................................................................................................5-2
Control Constants ......................................................................................................................................5-2
Forcing and Unforcing Logic Signals........................................................................................................5-2
Terminal Session Monitor .........................................................................................................................5-2
Chapter 6 HMI
6-1
Overview ...................................................................................................................................................6-1
Directory Structure and Files .........................................................................................................6-1
CIMPLICITY Directories ..............................................................................................................6-1
TCI Directories...............................................................................................................................6-2
Drive F: Files..................................................................................................................................6-2
Drive F: Sub-directories .................................................................................................................6-3
Drive G: Sub-directories ................................................................................................................6-3
Features, Utilities, and Tools.....................................................................................................................6-3
Device Communications Links ......................................................................................................6-3
Mark IV..........................................................................................................................................6-4
Mark IV Modbus............................................................................................................................6-5
Mark IV MA/MSP (Manufacturing Associates / Message Service Protocol)................................6-6
Mark IV Predefined Data Dump ....................................................................................................6-7
Mark V and Mark V LM ................................................................................................................6-7
Mark VI..........................................................................................................................................6-7
DCS Communications Links..........................................................................................................6-7
TCI Modbus Slave/Master .............................................................................................................6-8
CIMPLICITY Modbus Master.......................................................................................................6-8
GSM ...............................................................................................................................................6-9
Predefined Data Dump Transmitter................................................................................................6-9
EPA Log.........................................................................................................................................6-9
Real Time Logger Control - LOGGER ........................................................................................6-10
Using the Alarm Logger Dialog Box ...........................................................................................6-11
ii Contents
Trip History..................................................................................................................................6-12
Trip History on the Mark V and Mark V LM (First Version).....................................................6-12
Trip History on the Mark V (New Version).................................................................................6-17
Trip History on the Mark VI ........................................................................................................6-23
DMD2SRC Demand to Source Conversion Program ..................................................................6-24
Starting the Demand Display to Source Conversion Program .....................................................6-29
Editing the Demand Display Source File .....................................................................................6-29
MODBUS List File Generators....................................................................................................6-30
MODBUS_L MODBUS List File Generator...............................................................................6-30
Cimmod_L Modbus List File Generator ......................................................................................6-31
Configuration ..........................................................................................................................................6-32
Introduction..................................................................................................................................6-32
TCI Control Panel Applet ............................................................................................................6-32
TCI Configuration........................................................................................................................6-36
TCI Configuration Files ...............................................................................................................6-37
TCI - Starting and Stopping .........................................................................................................6-39
TCI Modbus Configuration..........................................................................................................6-42
HMI Configuration Using HMI Device - Mark VI ......................................................................6-45
Configuration File (F:\AT_START.DAT And AT_STOP.DAT) ................................................6-54
Configuration File (F:\CONFIG.DAT) ........................................................................................6-56
Configuration File (F:\EGD_PUSH.DAT)...................................................................................6-59
Configuration File (F:\IO_PORTS.DAT) ....................................................................................6-60
Configuration File (F:\MODB_FWD.DAT) ................................................................................6-65
Configuration File (F:\PICONFIG.DIF) ......................................................................................6-67
Configuration File (F:\PI_PUSH.DAT) .......................................................................................6-69
Creating a Data Dictionary...........................................................................................................6-70
Configuration File (F:\TIMESYNC.DAT)...................................................................................6-77
Ethernet Alarm Protocol File (F:\ENATALM.DAT)...................................................................6-81
Exciter Configuration File (EX2000.DAT)..................................................................................6-82
EX2100 Data and Alarms - Mark VI ...........................................................................................6-82
Predefined Data Dump Configuration..........................................................................................6-83
Predefined Data Dump Transmitter (PDXMIT) Configuration ...................................................6-84
Time Synchronization Configuration...........................................................................................6-90
Time Zone Make - TZ_MAKE ....................................................................................................6-93
Time Zone Transition File (TIMEZONE.DAT) ..........................................................................6-96
Turbine Control Maintenance Icons.............................................................................................6-97
EM_ANA - Emissions Analysis ..................................................................................................6-99
Performance Monitor .................................................................................................................6-101
Using EMapView.......................................................................................................................6-102
Setup Procedure (Heavy Duty Gas Turbines, EMAP 7) ...........................................................6-103
Alarm Printing and Logging ......................................................................................................6-106
Alarm History ............................................................................................................................6-108
Disk Manager.............................................................................................................................6-109
Control Hierarchy (F:\CTRL_LOC.DAT) .................................................................................6-110
Setting the HMI Web Server Homepage....................................................................................6-116
Web Server Installation..............................................................................................................6-119
The EPA Logger ........................................................................................................................6-120
Diagnostics ............................................................................................................................................6-122
Diagnostic Tools ....................................................................................................................... 6-122
Basic Generic Questions ............................................................................................................6-122
Overview of Approach...............................................................................................................6-122
Alarm Dump 1 - ALMDUMP1 - Mark IV, Mark V, Mark V LM, and Mark VI ......................6-134
Alarm Dump 2 - ALMDUMP2..................................................................................................6-135
ARCWHO..................................................................................................................................6-135
CHECKCRC ..............................................................................................................................6-137
GBL2FILE - Global Section To File..........................................................................................6-138
MM_STAT - Modbus Master Statistics.....................................................................................6-139
M_STAT - Modbus Slave Statistics...........................................................................................6-140
PDD_STAT - Predefined Data Dump Status .............................................................................6-140
VIEWn Series ............................................................................................................................6-141
VIEWn Collection Programs .....................................................................................................6-141
Contents iii
Chapter 7 Networks
7-1
iv Contents
Chapter 8 CIMPLICITY
8-1
Overview ...................................................................................................................................................8-1
Introduction....................................................................................................................................8-1
Features, Utilities, and Tools.....................................................................................................................8-2
CIMPLICITY Optional Displays ...................................................................................................8-2
Manual Synchronizing Display - Mark V, Mark V LM.................................................................8-2
Manual Synchronizing Display - Mark VI.....................................................................................8-6
Triggered Plot - Mark V and Mark V LM......................................................................................8-6
Reactive Capability Display - Mark IV, V, V LM, VI...................................................................8-8
Configuration ............................................................................................................................................8-9
Introduction....................................................................................................................................8-9
Frame Containers and Single Screens ............................................................................................8-9
Using Workbench ..........................................................................................................................8-9
Opening a Project.........................................................................................................................8-10
CIMPLICITY - Starting and Stopping a Project..........................................................................8-11
Configuring Users ........................................................................................................................8-12
Configuring Ports.........................................................................................................................8-15
Adding Devices............................................................................................................................8-17
Configuring Resources.................................................................................................................8-18
Allowing Local System Account Access .....................................................................................8-20
Alarm Filtering in HMI Servers ...................................................................................................8-20
Configuring Alarm Filters............................................................................................................8-21
Alarm Screen in a Frame Container - Mark IV, V, and V LM ....................................................8-23
Examples of Screens for Filtered Alarms.....................................................................................8-30
Currently Implemented Filters .....................................................................................................8-32
Single Screen Features - Mark VI ................................................................................................8-32
Extended Alarm Commands ........................................................................................................8-39
External Alarm Manager..............................................................................................................8-40
Signal Manager - Mark V and Mark V LM .................................................................................8-40
Alarms..........................................................................................................................................8-42
Importing Signals.........................................................................................................................8-43
Toolbox HMI Device - Mark VI ..................................................................................................8-45
System Database ..........................................................................................................................8-45
TCI - CIMPLICITY Modbus Data Interface ...............................................................................8-46
OLE for Process Controls (OPC) .................................................................................................8-46
Diagnostics ..............................................................................................................................................8-47
System Status Logs ......................................................................................................................8-47
Viewing the Status Log................................................................................................................8-47
Viewing the System Log..............................................................................................................8-48
Viewing the Project and System Status Logs...............................................................................8-48
System Log Files..........................................................................................................................8-49
Project Log Files ..........................................................................................................................8-49
Gather File Utility ........................................................................................................................8-49
How to use the Gather File Utility ...............................................................................................8-49
Glossary of Terms
Index
G-1
I-1
Contents v
Notes
vi Contents
CHAPTER 1
Chapter 1 Overview
Introduction
The Human-Machine Interface (HMI) for SPEEDTRONIC Turbine Control
Application Guide Vol. II describes the maintenance features for the HMI used with
HMI Summary
The HMI is an operator interface system based on client-server technology,
providing data collection, logging, and display of power island and auxiliary process
data. The HMI also has the ability to issue operator commands to the control
equipment. Depending on the requirements, the product can be configured for just
turbine-related data, or for broader applications that include balance of plant process
data.
System Configuration
The HMI provides operator display and control for the Mark IV, Mark V, Mark V
LM, and Mark VI controller types. The controllers and supported networks are as
follows:
Controller Type Supported Controller Communication Network
Mark IV
Data
Data
HMI Server # 1
HMI
Viewer
HMI Server # 2
Historian
TR
Mark IV
Turbine
Control
I/O
Mark V
Turbine
Control
I/O
Data Paths to the HMI Servers and Viewers from Various Controllers
In the Mark VI system, the controllers and other devices communicate with the HMI
Server through the Ethernet-based Unit Data Highway and through RS-232C lines.
The HMI Server uses the Plant Data Highway to communicate with the HMI
Viewers.
System Capability
The HMI provides an online database for collecting and storing data from multiple
controllers. For TCI version 1.6, points can be collected from as many as eight
turbine controls. For later versions of TCI, the number of turbine controls has been
increased; consult GE for advice on your system.
Data Collection
Data is collected by various methods, depending on the product. For the Mark IV,
Mark V, Mark V LM, and Mark VI, the process is centered about the Control Signal
Database (CSDB), which is the real-time database in the controller. The control
scans the CSDB for alarm and event state changes. When a state change occurs, or a
sequence of events occurs, these are sent to the HMI. These points are time tagged
by the controller.
HMI Terminology
Definitions of three important terms used in this manual are as follows:
The term unit is used in the HMI configuration and refers to the turbine control
being configured. Unit has also been used to refer to the physical combination of
the turbine, generator, and exciter.
The term controller refers to the Mark IV, Mark V, Mark VI, or PLC control
equipment in the control panel.
The term panel refers to the cabinet containing the controllers and I/O boards. In
prior manuals the term panel has been used to refer to the controller.
Text Conventions
Convention
Meaning
A procedure follows.
Numbered list
Alphabetized list
Bulleted () list
Bold
Provides emphasis.
Arial Bold
Italic
Monospace
Related Documentation
The following documents apply to the HMI and SPEEDTRONIC turbine controllers
and can help in understanding HMI operation:
CHAPTER 2
Chapter 2 Installation
Introduction
A facility receives the HMI pre-loaded with all the programs and customized
software required for the customers application. It is then configured during
installation to automatically log on and open to the main operator screen when
powered-up. This chapter covers the installation, setup, and checkout of the HMI.
If the computer is already running, press the three keys Ctrl+Alt+Delete all at
once to bring up the Log On dialog box to change the User to Oper.
If the main operation display does not start automatically, double-click the
desktop icon, typically Unit_Control.cim.
When the computer starts up, it starts all CIMPLICITY programs (refer to the
following screen Typical Services Starting Display) and displays the main operation
display (refer to Example of a Typical HMI Display).
Note GFK-1180 describes CimView in detail for the Mark V.
Note The HMI displays for the user's system are CimView displays (*.cim files),
which can open before CIMPLICITY finishes loading. If at first the display is not
animated or setpoints fail, wait a few minutes for the startup to complete before
beginning operation. During the startup process do not click any Cancel or Close
buttons.
Note To login to a different account such as Administrator or maint (abbreviation
for maintenance), it is necessary to hold down the Shift key while the computer is
booting. This will open a login box where the user name and password can be
entered.
Do not click
Close button
as it may
cancel the
complete
loading of
essential
services
before the
HMI starts.
CIMPLICITY Project
Check that the CIMPLICITY software is loaded, its shortcuts appear on the Start
menu and the CIMPLICITY projectis located in directory C:\Site\Cimproj.
Both Windows 2000 and Windows XP are covered in this section because there
are differences in the procedures for checking for the existence of proper user
accounts. Password text cannot be read directly because passwords are obscured by
the operating system by displaying representative asterisks in place of the actual
password. Passwords can only be verified by attempting to log on to an account with
the associated password. If the logon procedure fails then the password may be
incorrect and can be reset from the Administrator account.
Typical GE systems have three (possibly more) accounts on the pc:
Note There should be a backup of the HMI hard drive or a Restore Disk (Refer to
Microsoft Windows documentation). If this is not the case, a backup of the HMI hard
drive or a Password Restore Disk should be made before making any changes. Refer
to the Microsoft Windows documentation on how to create a Password Restore Disk.
You may need to obtain a floppy drive for your system if one is not present.
Note The client can add or remove additional user accounts as needed. Refer to
Microsoft Windows documentation for further information. User accounts, other than
those setup by GE, may not operate the HMI properly.
Windows 2000
You must be logged in as
administrator to perform
procedure
Select User. A list of users on the computer displays in the left pane. Right
click on a User name to open a drop-down box.
Click Set Password. The Set Password dialog box opens. Enter the new
password in the New password and the Confirm password fields. Click OK.
Close all open windows. The new password takes effect immediately. Confirm,
by logging on as that user.
Windows XP
You must be logged in as
administrator to perform
procedure
Select User. A list of users on the computer will display in the right pane. Right
click on a User, which will open a drop-down menu window. Click Set
Password.
Click Proceed to change the password. The Set Password dialog box opens.
10 Enter the desired Password in the New Passsword and Confirm password fields,
then click OK to reset password.
CHAPTER 3
Chapter 3 Mark IV
Overview
The Mark IV configuration is PROM-based, not downloaded from the HMI. There
are no tools on the HMI to configure and download a Mark IV.
All control changes are made directly either by using the Mark IV front panel display
or a terminal connected to the Mark IV.
This message is produced if the HMI finds that the name of the point in the HMI is
different than the name of the point reported by the Mark IV. In some cases this will
be because the Mark IV considers it a spare (unused) point but the HMI believes that
the point is used (or vice versa).
Success- Data Dictionary point number 0x2A7A with name
"TTXSPL" validated.
This message is produced only if the /VERBOSE option is used and there are no
errors validating this point.
"ERROR -
This message is produced if there is an error outside of the normal errors shown
above. It typically means that something has gone wrong in the process (such as the
Mark IV was shut down in the middle of the scan). It is worth retrying the validation
again to see if it clears the error.
CHAPTER 4
Chapter 4 Mark V
Mark V Controller
HMI Unit-Specific Directory
Each Mark V controller communicating with an HMI has a unit-specific directory
and subdirectory on the HMI hard drive. These directories have names referring to
the unit. They are located on the F: drive and are defined in F:\CONFIG.DAT. The
unit-specific directory for the first unit is usually named F:\UNIT1, and its
subdirectory is F:\UNIT1\PROM. Subsequent unit-specific directories and their
subdirectories are F:\UNIT2 and F:\UNIT2\PROM, F:\UNIT3 and
F:\UNIT3\PROM, and so on.
Configuration files contained in a unit-specific directory can be broken up into five
groups as follows:
Assignment files
Table files
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 HMIs unitspecific directory: IO.ASG, FACTORY.ASG, ALLOCSSP.ASG, and SITE.ASG.
These are ASCII (American Standard Code for Information Interchange) 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 GEPSs 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.
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.
Other Data Dictionary files that must be present in the unit-specific directory for
proper operation include:
The following unit-specific Data Dictionary files are optional and not required for
proper HMI operation:
Unit-specific Data Dictionary files are not downloaded to a Mark V controller, but
are loaded into the HMIs 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.
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 executing 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
CONST_Q.SRC
EPA_B.SRC
EPA_Q.SRC
MAOUT_B.SRC
MAOUT_Q.SRC
CHNG_B.SRC
CHNG_Q.SRC
EVENT_B.SRC
EVENT_Q.SRC
TOTT_B.SRC
TOTT_Q.SRC
HIST_B.SRC
HIST_Q.SRC
CBLR_B.SRC
CBLR_Q.SRC
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
execution.
The values of control constants in the processors RAM can be changed using the
Control Constant Adjust Display program by selecting a constant on the HMI
display. Control constants can be adjusted while the unit is running, although the rate
of change of the control constants value is quite slow when the unit is running to
prevent a rapid change from tripping the turbine. Refer to the section on the Control
Constant Adjust Display.
A feature of the Control Constants Adjust Display is to copy the control constant,
whose value was changed in RAM, to the controllers nonvolatile memory. Clicking
on the target Storage Update and then clicking on the OK button in the Execute
Dialog Box copy the current RAM value of every control constant to the processors
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 units 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.
It is possible to generate a list of the current values of control constants in the
controller using the CONSTCHK program. Refer to the section on CONSTCHK
program.
Auto-Calibrate Display
The Autocalibrate 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.
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, F:\UNITn. 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 Autocal 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 Autocal
is run, it displays a list of the regulators for user selection.
Menu Selections
Options
Commands
Description
FILE:PRINT
FILE:PRINTER SETUP
FILE:EXIT
Command Pushbutton
The command pushbuttons in the button-view window have the following standard
colors:
Not all command pushbuttons are available at all times. Their visibility depends 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 full
hydraulic pressure.
If no pushbuttons are visible, then either one of the following conditions is
occurring:
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 datafile 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 Autocal.
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 Autocal 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 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 could 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 Autocalibrate 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.
Valid Unit: The Autocalibrate display is opened with the unit already selected.
Single Unit Sites: The unit parameter is ignored on single unit sites.
Screen Description
The Autocalibrate screen consists of three windows as follows:
Tree-view window
Button-view window
The tree-view is on the left side of the display, the Autocalibrate 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 Autocalibrate test data at
a time.
Tree-view. The Autocalibrate tree-view window is a graphical window that depicts
the hierarchy of Unit and regulators available for calibration. The tree-view can hold
and display one unit at a time; it cannot be printed.
Autocalibrate Data. The Autocalibrate data window has three main regions,
Header, Data Area, and Message Box.
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.
The Data Area is below the Header. This displays the strings for the selected
Autocalibrate 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 time tag displayed in the Header reflects operator interface time when the
last update message was received. If the Header time tag field is highlighted, the
data being displayed may not be valid.
If the Mark V does not respond or another Autocalibrate window, HMI, or <I> is
using the Autocal function, the data fields remain blank.
Message Box. This area at the bottom of the data window displays warnings and
information about the Autocalibrate function status. Please take note of all messages
and warnings.
Button-view
The Button-view window contains the pushbuttons that interact with the unit control
to conduct and verify Autocalibration functions. These buttons are visible only when
the board permissives have been met and no other window, HMI, or <I> is
conducting an autocalibrate function. 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. The pushbuttons and their functions are
discussed in the section on Autocalibrate Command Pushbutton Description.
The Value
The 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
File
Print Setup
Exit
Select Unit
Find Point
Brings up the Find Point dialog box. From this the user can
locate a point in the list
Set Point
This dialog box sets the font that both the header and the data
list uses
Set Default
This sets the font and column widths back to the system default
Tool Bar
Status Bar
Edit
View
Help
About Control This Dialog box displays the revision level of the Control
Constants
Constants Display
The Control Constants Display can be invoked from the 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:
G:\EXEC\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.
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
Start Ramp
Stop Ramp
Step Change
Storage
Update
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
Start Ramp
Stop Ramp
Step Change
Storage
Update
Operation
CONSTCHK is a command line program that is usually run from a DOS prompt. 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.
F:\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.
F:\UNIT1>
AP1
-----------0.000
0.00
0.00
0.00
0.00
0.00
0.00
different values.
File Type
The program reads the F:\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
F:\UNITN directory or in the F:\UNITN\PROM directory.
For the Mark V LM, the DIAGC.DAT file is a text file that is produced by the tool
program G:\EXEC\DCBUILD1.EXE.
Note For Mark V LM, DIAGC.DAT should always be built from the card library
by the tool program. While DIAGC.DAT is a text file, it should never be edited by
hand. DIAGC.DAT files should never be copied from one unit to another.
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.
DIAGC.EXE is located within the product code in the G:\EXEC subdirectory. The
Diagnostic Counters Display can be launched from the command line with the
following argument to quickly bring the display to a desired configuration:
/UNIT:T1
The following example specifies the unit name as T1:
G:\EXEC\DIAGC.EXE /UNIT:T1
The DIAGC Display can be launched from the Windows Start Menu Run dialog box
by entering the command as displayed on the command line above, or by selecting
the DIAGC icon from the appropriate program group.
Tree view
Diagnostic
subtypes
Selected
sub-type
Diagnostic
data area
Unit name
Site name
Program name
Board, core and
socket name
Timetag
Number of replies
received from the
Unit.
Legend with title of
diagnostic sub-type
The Diagnostic Counter data window on the right hand 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.
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.
Data
Code
Ctypes
Conversion-Algorithm
ASCII
A0
%s
char* =&raw_data
Binary
B1
%8s
char* =itoa((char)raw_data,str,2)
B2
%16s
C1
%f
C2
%f
C4
%lf
Fixed
F2
%f
Sign/un
H1
%2X %u %c
H2
%4X %u
H4
%1X 1u
Logical
L1
%d
Real
R4
%f
Un/sign
S1
%f
S2
%f
S4
%lf
Integer
File Structure
The Logic Forcing Display program is located in the executable directory,
G:\EXEC\LFORCE.EXE. Never tamper with this file.
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 specific directory on the F:\ drive,
but may reside in any directory such as F:\RUNTIME.
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.
Header
PC time
Current
value
Command
target area
Engineering
units
List
view
Starting the Logic Forcing Display program and loading a Logic Forcing
Display file
Modifying a pointname
From the Logic Forcing Display program, position the cursor on the line
corresponding to the desired logic signal. Click on the pointname field to select
it and the pointname highlights.
Select one of the Forcing Command targets on the right side of the screen to arm
the action, either Force To One or Force To Zero. The Logic Forcing
Command dialog box displays.
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 executing.
Signals remain forced until an unforce command comes
from the Logic Forcing Display program or until the
controller powers off. Forced signals can cause the
controller to function improperly if forgotten. Take care
to unforce all unnecessary signals 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.
Select the Unforce Single command target. The Execute Command dialog
box displays.
Select OK to unforce the signal, or Cancel to leave the signal forced. The
default action is Cancel.
To unforce all of the forced logic signals
From the Logic Forcing Display, select the Unforce All command target.
The Execute Command dialog box displays.
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:
F:\RUNTIME>LFORCE /UNIT:T1
where the unit number 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:
F:\RUNTIME>LFORCE /FILE:LFORCE2.TXT
Menu Items
Description
File
New, Open, Close, Save, Save As, Selects new or existing files, recently
Print, Print Preview, Print Setup,
edited files, saves edited files, prints files,
{Filenames}.TXT, Exit
exits the Logic Forcing Display program.
Edit
View
Help
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.
The List View is composed of three columns, the Point Name, the Current Value
from each processor, and the Engineering Units.
The List View scrolls and each of the columns is adjustable in width. If the column
becomes too narrow to display all of the data, an ellipsis () appears on the right
side of the column. The Current Value field is updated once per second from each
controller processor. The time tag displayed in the Header reflects the time tag of the
oldest piece of data displayed. Only the points visible on the screen are updated.
There is no limit to the number of points that can be added to the point list. Unlike
the Header, the information in the Data Area scrolls with the scroll bars. The Logic
Forcing Display updates only the visible points in the List View.
The Pointname field holds the Control Signal pointname (or synonym) of valid unit
database points. Entering the pointname causes the Logic Forcing Display program
to use the currently selected units data, which is the unit listed in the Header.
Entering the 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 appears
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 appears 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.
Select the menu bar option Edit, and from the drop-down menu, select the
Modify Line command , or
Select the Modify Line toolbar button.
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.
From the Logic Forcing Display, highlight the line above the desired
insertion point.
Select the menu bar option Edit and from the drop-down menu, select the
Insert Blank Line, or
Select the Insert Blank Line toolbar button.
The Logic Forcing Display program inserts a blank line below the highlighted
line.
If the display is empty, Insert Blank Line can be applied without first highlighting
a location. To modify the line, refer to the Modifying a Line section. Saving the
Logic Forcing Display file makes the addition permanent.
The Logic Forcing Display program allows deleting lines. Highlight the pointname
field 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.
Select the Command Target. The Execute Command dialog box displays.
To cancel the command execution, select Cancel. The default action is Cancel.
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.
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 dropdown 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.
Select the menu bar option File and from the drop-down menu, select Save, or
Select the toolbar button with the picture of a disk
The Logic Forcing Display files are saved in the directory of the original file.
If the file is new, the Save As dialog box appears 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. Selecting 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.
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 the 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
Description
File
Print Setup
Exit
Select Unit
Find Point
Brings up the Find Point dialog box. From this, the user can
locate a point in the list.
Set Font
This dialog box sets the font for both the header and the
data list.
Set Default
This sets the font and column widths back to the system
default.
Tool Bar
Status Bar
Freeze Data
About Prevote
Edit
View
Help
The ALARMD.DAT file maps the diagnostic alarm numbers to the diagnostic
alarm text. The TCI System Service reads this file to find the text message to use
for each diagnostic alarm.
The HELP_QD.DAT file supports the HMI Alarm Help feature. When a user
requests additional information about the diagnostic alarm, the Alarm Help
program uses this file as the additional help text.
Update a Unit Configuration Directory (and its \PROM subdirectory) with files
from the Card Library that match the software revisions found in the Panel
Configuration (PANEL.CFG) file.
COMMAND LINE: DPBUILD1 [/?] [/GO] [/LIB=<card library path>]
/? - prints this help message
/GO performs all operations needed without prompting user. Useful for batch
or spawned operations.
/LIB=<card library path> Causes DPBUILD to go to a specific directory to retrieve card library
information, instead of the default card library directory.
This program reads the PANEL.CFG file in the current directory to determine the type and revision
level of the product being updated.
It then updates the Unit Configuration directory (including \PROM) with the files contained in the
compressed library file included in the card library distribution. The library file contains
current versions of the *.pic, *.def, *.tpl, and *.txt files needed to support the product.
F:\>
The typical system uses four assignment files for the list of signals used, as follows:
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 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
Mark V LM only uses Q.
The sss indicates a sub-class of signal. These subclasses include the following:
PUB is a private (local) unsigned byte, only valid for logic 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.
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:
F:\UNIT1>DDUTIL
F:\UNIT1>
In the next example, no errors were found, and the file was sorted in signal name
order:
F:\UNIT1>DDUTIL SORT
SORTING COMPLETE: UNITDATA.DAT IS NEW FILE, UNITDATA.BAK
IS OLD.
F:\UNIT1>
DDLOCATE is run to lay out the CSDB with the new signal definitions. It is
run using the following assignment files:
DDUTIL is run to validate the new layout, and sorts the resulting
UNITDATA.DAT file
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,
and 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:
F:\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_C: 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: Aug 20 1997 at 11:12:38
Compiled on: Tue Dec 02 11:35:57 1997
---> 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
---> <B> segment: F:\UNIT1\SEQ_B.src
... 5 rungs processed
---> Creating the <Q> AP1 sequencing file: F:\UNIT1\SEQ_Q.AP1
---> Creating the <B> AP1 sequencing file: F:\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.
F:\UNIT1>
Operation
FMVID is a command line configuration program. It requires the name of the unit as
a command line parameter. If no additional parameters are given, it displays the
FMV IDs stored in the unit.
If run with the /SET option, it changes the FMV ID in the unit to match the serial
number information in the /SET command. The format of the /SET option is:
FMVID
/SET=<num>:<part_num>:<serial_num>
<num> is the FMV number, starting with 1 for the first valve
The <serial_num> field is the serial number as defined in the linearization table
for that particular valve.
Multiple /SET commands can be given in the FMVID command line. These
commands are processed from left to right. If a valve number is repeated, the last
entry is the one used. After all /SET commands have been processed, the nonvolatile memory in the unit is read and displays the results of the changes.
If FMVID is run with no parameters, or the parameter of /?, it displays a help screen,
as displayed in the following example:
F:\UNIT1>fmvid /?
FMVID - FMV IDENTIFICATION UTILITY
This program will show the user which FMVs are listed in the unit's
NonVolatile RAM (NVRAM) as being installed on the unit.
The FMV identification can be changed by using the /SET option.
COMMAND LINE: FMVID <UnitName> [/SET=<num>:<part>:<serial>]
The unit name must be supplied. If no /SET commands are supplied then no
changes will be made, and the current settings will be shown. If one or more
/SET commands are supplied, the values will be changed in the unit's NVRAM,
and the resulting configuration will be shown.
/SET=<num>:<part_num>:<serial_num>
This option will set the given FMV number to expect the given part number and
serial number. The FMV number is an integer (1..n), the part number and
serial number are treated as strings. More than one /SET can be given on the
command line.
Example: FMVID T1 /SET=1:C329465-B2:11
This registers unit T1's FMV number one (1) as expecting part number C32465B2, serial number 11. After the change is made the new configuration is
shown.
F:\UNIT1>
In order to download an LDB table to RAM, the following conditions must be met:
The table must be marked as Adjustable in the HMI LDB table file
The table ID must be the same the HMI file and the unit's RAM
The [X] table dimension in the HMI file and the unit's RAM must be the same
The [Y] table dimension in the HMI file and the unit's RAM must be the same
The [X] data values in the HMI file and the unit's RAM must be the same
The [Y] data values in the HMI file and the unit's RAM must be the same
Operation
To change an LDB table in the unit RAM, first make the changes to the appropriate
LDB table in the HMI unit configuration directory, and then download it using the
LDB2RAM utility.
Note Save a backup copy of the HMI file to undo changes if required later.
LDB2RAM needs to know which unit to download, and which table to download.
The unit is specified using the /UNIT=<unit_name> qualifier. The table can be
specified using either the file name or the table number, by using either the
/FILE=<file_name> qualifier or the /TABLE=<table_number> qualifier. The
associated file is compiled and downloaded directly to the controller.
If LDB2RAM is run with no command line values or with a command line
parameter of /? , a help screen is displayed, as in the following example:
F:\UNIT1>ldb2ram /?
LDB2RAM - Download an LDB TABLE to a Mark V LM's RAM
This program will read an LDB table and transmit it to the RAM
in the specified unit. It does not alter the value in the
LDB.AP1 file, that is done using the TABLE COMPILER (TABLE_C).
COMMAND LINE:
LDB2RAM /UNIT=<unitname> [/TABLE=<number>] [/FILE=<filename>]
<unitname> is the name of the unit
<number>
is the number (decimal) of the table to download
<filename> is the name of the file to be downloaded
F:\UNIT1>
Operation
LDBCHK is a command line utility program that is typically run from a command
prompt. 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, as displayed in the
following example:
F:\UNIT1>LDBCHK /?
LDBCHK - LDB Table Check Utility
This program will check the LDB Table definitions in
the given unit and report on Tables that have
different values in the RAM than in the LDB.AP1 file.
This indicates which values have been changed in RAM
since the unit was restarted.
COMMAND LINE:
LDBCHK <UnitName>
- The name of the unit to be checked.
<UnitName>
F:\UNIT1>
Operation
ALARM_L is a command line utility that is run from the unit configuration
directory. It takes no command line parameters, and generates the ALARM.LST file
containing the output from the program, as displayed in the following example:
F:\UNIT1>alarm_l
Loading data dictionary alarm.....576 alarm points loaded.
F:\UNIT1>
SAMPLE OUTPUT (ALARM.LST)
DROP#
SIGNAL NAME
ALARM TEXT
------ -------------- -------------------------------------0
1
2
3
4
5
6
7
8
9
10
L30DIAG
L30FORCED
L4ETR_FLT
L86MP
L48
L83HOST
L83LOST
L12H_P_ALM
L12L_P_ALM
L86MAN_SYNC
L86S
DIAGNOSTIC ALARM
FORCED LOGIC SIGNAL DETECTED
PROTECTIVE MODULE ETR RELAY TROUBLE
MASTER PROTECTIVE STARTUP LOCKOUT
TURBINE INCOMPLETE SEQUENCE
OVERSPEED TEST MODE SELECTED - HP
OVERSPEED TEST MODE SELECTED - LP
PROTECTIVE MODULE HP OVERSPEED - SD
PROTECTIVE MODULE LP OVERSPEED - SD
MANUAL SYNCHRONIZING LOCKOUT
AUTO SYNCHRONIZING LOCKOUT
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. If run with no parameters or the /? parameter, a help screen is displayed as
shown in the following example.
F:\UNIT1>constset
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>
F:\UNIT1>
Application Information
With TCI Version 1.2 and above, the unit can generate the Mark V default ramp
rates without using the CONSTSET program. A new 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.
;
*MARK V_DEFAULT
;
;Add any overrides desired here
;
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.
File Structure
The output of the Sequence Compiler is an *.AP1 file (or files) that can be
downloaded to the controller. The downloadable sequencing filename is SEQ.AP1
for Mark V LM, and for Mark V there are two, SEQ_B.AP1 and SEQ_Q.AP1. 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.
MSTR_SEQ.CFG
SEQ.AP1
(Mark VLM)
UNITDATA.DAT
PROM\PRIMITIVE.DEF
PROM\BIGBLOCK.DEF
SEQCOMPL.EXE
Control
Sequence
Compiler
{Segment1
{Segment2
SEQ_B.AP1
(Mark V)
SEQ_Q.AP1
(Mark V)
{Segment name}.SRC
Sequence Compiler Block Diagram
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)
Frequency n
name
power of 2
(>0)
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:
WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y
Z
Z
Z
Z
Z
Z
Z
Z
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|.|
0123456789ABCDEF
0.0sec 0.5sec 1.0sec 1.5sec 2.0sec 2.5sec 3.0sec 3.5sec 4.0s
Segment Y is run every two frames, for an 8 Hz execution, and is skewed by one
frame.
Frame
Rate
(base)10
20
40
80
160
320
640
1280
Frame Time(period)
Hz
; Scan Rate n = 1
=
= msec iteration interval 100
; Scan Rate n = 2
=
= msec iteration interval 50
; Scan Rate n = 4
=
= msec iteration interval 25
; Scan Rate n = 8
=
= msec iteration interval 12.5
; Scan Rate n = 16 =
= msec iteration interval 6.25
; Scan Rate n = 32 =
= msec iteration interval 3.125
; Scan Rate n = 64 =
= msec iteration interval 1.5625
; Scan Rate n = 128 =
= msec iteration interval 0.78125
;
; For Mark VLM the reference rate is 100 Hz, 10 msec
#<Q>_SEGMENTS
;
Scan rate, n Offset within scan
rate
#SEGMENT SEQ_10GE 1
0
;GENIUS COMM ;CHECK
#SEGMENT
#SEGMENT
#SEGMENT
#SEGMENT
#SEGMENT
SQ_BLK
SQ40_2
SQ40_1
SQ640
SQ160_5T
1
4
4
64
16
0
2
1
11
5
#SEGMENT
#END
SQ160_3T
16
;
;PD
;PD
;13
; DRAIN / PURGE
;VALVE DEMAND AND
FEEDBACK
; DRAIN / PURGE
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 of these 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 appear 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 F:\UNIT_EA\SEQ20_1.SRC
Tue Nov 18 13:55:02 1997
Page - 34
<< Rung Number 50 >>>
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
CDPSUMAVGA
CDPSUMAVGB
CDP_CUR
CDP_CUR_REF
CDP_ERR
CDP_ERRABS
CDP_NBIAS
CDP_NSC
CDP_POS_DMD
CHIP_AGB
CHIP_BSUMP
CHIP_CSUMP
CHIP_DSUMP
CHIP_TGB
CPCVAVG
CPCVMAN_PV
CPCVRATEVAL
CPCV_MAN
CPCV_PVGOOD
CPCV_PVINP
CP_CV
CP_CV_SEL
CS3
D30T2A
D30T2B
D30T2DIFF
Page 4
N/D
LOGIC
N/D
N/D
N/D
N/D
N/D
N/D
N/D
LOGIC
LOGIC
LOGIC
To initiate the compiling program, either select the Control Sequence Documentor
icon, or type SEQDOCMT, or press enter while at a command prompt in the unit
specific directory. The Sequence Documentor has four possible parameters. They
must be listed in order after the SEQDOCMT.EXE command. For example, a valid
command line with all possible parameters is as follows:
F:\UNIT1>SEQDOCMT.EXE METRIC.SCA N -LOG F:\UNIT1
The first parameter is the scale code file name; the default is ENGLISH.SCA.
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.
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, typically F:\UNITn. 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.
UNITDATA.DAT
PROM\
BIGBLOCK.DEF
SEQEDIT.EXE
Control
{Segment name}.SRC
Sequencing
Editor
file
Editing rungs
Selecting rungs
Copying rungs
Moving rungs
Creating rungs
Saving a segment
Select the Control Sequence Editor icon, or from the Command Prompt,
enter: SEQEDIT
The Sequence Editor opens each segment in a separate segment window that
displays the segment one rung at a time.
Primitive rungs display using a 4x8 permissive matrix and a tile representation
of the primitive.
The horizontal and vertical scroll bars allow viewing portions of rungs and
blocks that exceed the segment window boundaries.
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.
Selecting a component from the Component menu bar option or from the
toolbar and doubling 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.
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.
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.
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.
The Coil and ICoil commands from the drop-down menu select normal coils
and inverted coils respectively.
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 segments
functionality, delete the old copy 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.
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).
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
CSPPRINT is run from a DOS window at a command prompt, as follows:
G:\EXEC\CSPPRINT.EXE
F:\UNIT1\CSP.PRN/p
The file name is F:\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.
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
Select File then Open. The *.PRN document in the unit configuration directory
opens.
Select File then Page Setup to adjust the appearance of the page:
Select OK to accept the setup changes (or Cancel to cancel them) and
return to the CSP display.
Select the printer and paper options, then select OK. A dialog box displays the
print progress.
To cancel CSP printing in progressw
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.
Operation
TABLE_C is a command line configuration program run from the unit configuration
directory. It looks to see if it is configuring a Mark V or a Mark V LM and processes
the tables accordingly. 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
type.
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:
F:\UNIT1>TABLE_C ALL
TABLE_C: Table compiler for Mark V AP1 files.
Loading data dictionary.....5920 points loaded.
TABLE_C processing complete.
F:\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.
Loading data dictionary.....5920 points loaded.
CONST WARNING: constant "COMMHTHY" not found, set to zero.
TABLE_C processing complete.
F:\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.
Operation
EEPROM is a command line utility program that is typically run from a DOS
prompt. If run with no parameters or the /? parameter, help is provided, as displayed
in the following example:
F:\UNIT1>EEPROM /?
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.
F:\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
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.
0000
0DD0
0E60
0F60
12E0
0C00
0200
1160
0000
003C
007A
0100
02B6
00A9
0910
0006
03-MAY-1997
03-MAY-1997
03-MAY-1997
03-MAY-1997
03-MAY-1997
03-MAY-1997
11-MAR-1992
03-MAY-1997
12:36:26
12:36:26
12:36:26
12:36:28
12:36:28
12:36:28
16:40:48
12:36:28
cksum
4E28
0936
2C8F
6B5A
0000
-idSEQ
CNST
IO
UBL
HIST
0000
0FCD
2570
38BD
847A
1EAF
0000
CAFE
EPA
4-20
EVNT
CHNG
BOI
TOTT
TOTD
CBLR
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 <B> 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.
Operation
UDF is a command line utility program that is typically run from a DOS prompt.
When the program is run it prompts the user for the desired unit. This must be a
Mark V LM unit. Entering a question mark when prompted for the unit name
provides a list of valid Mark V LM unit names. The user is then prompted for the
controller to talk to, with the default being the <R> controller. UDF then prompts the
user with its UDF> prompt. The Help command providing the list of commands is
displayed in the following example:
UDF> HELP
COMMAND FORMAT: UDF [/NODE=\\nodename]
AVAILABLE COMMANDS:
AP1 [filespec...]
- Remote AP1 file check
CD [dir]
- Remote change directory
CRC [filespec...]
- Remote CRC command
DELETE [filespec*...]
- Remote delete command
DIR [filespec*...]
- Remote directory command
EXEC [filespec*...]
- Mark file(s) as executable
FLASH [filespec*...]
- Send files to remote FLASH
FREE [dir]
- Get free space in directory
GET [filespec...]
- Get files from remote
LCD [dir]
- Local change directory
LCRC [filespec*...]
- Local CRC command
LDIR [filespec*...]
- Local directory command
MD [dir]
- Remote make directory
RD [dir]
- Remote remove directory
SEND [filespec*...]
- Send files to remote
STAT*US
- Show status of settings
AVAILABLE OPTIONS:
AUTOEXEC { ON | OFF }
- Marks no-extension files as Execs
CASE { NONE | UPPER | LOWER - Forces case of remote names
}
SEP*ARATOR { "/" | "\" }
- Defines remote directory specifier
TRACE { ON | OFF }
- Enable/Disable trace buffer
RESTART
- Restart with new connection
EXIT, BYE, QUIT
- Leave the program
[parameter] parameters are optional
"filespec*" parameters can include the wildcards "*" and "?"
"filespec..." parameters can be a list, separated by spaces Attached to
<88:R> via <R>.
UDF>
A special condition exists when a brand new turbine controller is downloaded for the
first time. The controller comes with enough software to be able to talk on the
ARCNET, but not enough software to perform as a controller. In this condition, the
controller cannot understand if its address is specified as a unit name. For UDF to
contact the controller, the ARCNET address of the controller must be used instead of
the unit name. To do this, when asked for the unit name, enter instead 0x followed by
the ARCNET address. This allows the UDF program to talk to a particular address,
even before the unit software has been downloaded to it. When the ARCNET
address is used, the core the address maps to must be known. This is typically the
<R> core, which is the default.
The UDF program has the ability to run from a remote node by using the
/NODE=<nodename> option on the command line. This is intended for cases where
the unit must be contacted from a remote location through the HMI. The nodename
is the name of the HMI that is going to act as a pass-through node for the UDF
messages. When run from a remote location, the unit name cannot be used to specify
the unit, so the ARCNET address must be used instead. Refer to the following
example:
F:\UNIT1>UDF
Enter the Unit Name: T1
Enter the target core (R, S, T) [R]:
Attached to <88:R> via <R>.
UDF>
F:\UNIT1>UDF
Enter the Unit Name: 0x88
Enter the Control Engine the LUN is for (R,S,T) [R]:
Enter the target core (R, S, T) [R]:
Attached to <88:R> via <R>.
UDF>
The date and time in the controller's non-volatile memory is a copy of the date and
time from the file used to download the panel. This means that the date in the
controller is the date the file was configured in the HMI, not the date that the
information was downloaded to the controller. This helps correlate the information in
the controller to the HMI disk files that were used to configure the unit. If a file is
uploaded from the controller, the date and time on the HMI is set to the date and time
from the controller's non-volatile memory.
Diagnostics
CARD_ID - Mark V and Mark V LM
CARD_ID is a Command Line utility program that scans a Mark V or Mark V LM
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. Mark VI uses the
toolbox.
Background
The Mark V and Mark V LM 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 and
the Mark V LM 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:
The Mark V front panel messages that correspond to these alarms are:
NO QST AVAILABLE
The Mark V LM controller uses a slightly different approach due to the flexibility in
the board sets that can be configured. The Mark V LM uses the PANEL.CFG file in
the unit configuration directory as a list of boards to poll in the panel. For each board
it finds in the PANEL.CFG file, it polls the controller for that board. The board
responds with the hardware version, firmware version, and current board state.
Comparing the board return with what is configured in the PANEL.CFG file flags
any differences. The flag field uses letters to indicate what differences were found
using the following letters:
After the Mark V LM revision report, it prints out a list of physical locations for
boards of interest. A board is included in this list if there are any flags indicated. A
command line parameter /ALL can be used to include all boards in this list instead of
only the flagged boards.
Operation
CARD_ID is normally run from the command prompt. 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.
If CARD_ID is being run on a Mark V LM, the following command line options can
be used:
/ALL - This option includes every board in the summary instead of only the
flagged boards.
/FULLID - Normally the information returned by the board is a string that ends
with a null character. Some early boards included information after the null
terminator that is useful during advanced debugging. If this option is used the
full field, including the information after the null terminator, is displayed.
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.
F:\UNIT1> CARD_ID T1
Card identification for SALEM PLANT unit T1:
C-TCCA:(TCCA
4.2 ) C-TCCB:(TCCB
4.1 )
C-SLCC:(LCCB
4.4 ) C-SDCC:(DCCB
6.6 )
C-IOMA:(IOMA
4.5 )
R-TCXX:(TCQA
2.5 ) R-TCXX:(TCQB
1.4 )
R-SLCC:(LCCQ
4.4 ) R-SDCC:(DCCQ
6.6 )
R-IOMA:(IOMA
4.5 ) R-TCPA:(
)
R-TCD1:(TCD1
3.5 ) R-TCD2:(
)
R-TCE1:(TCE1
5.2 ) R-TCE2:(TCE2
5.2 )
No response from <S>
No response from <T>
Enter any key to exit program:
F:\UNIT1>
1.1 )
)
5.2 )
Mark V LM Example
In this example, a Mark V LM is queried and the PROM revisions of the boards that
are present are reported. Notice that a board that does not support the CARD_ID
message type (R:25 processor 1) is not displayed in the list of Items of Interest.
Boards that respond but are unable to determine their own revisions (R:25 processor
0) do appear in the Items of Interest.
F:\UNIT2> CARD_ID T2
SYSTEM IS MARK V LM
|----------EXPECTED-----------|------------ACTUAL------------BMS |PR HARDWARE
FIRMWARE
|PR HARDWARE
FIRMWARE
ST
----- |-- ------------ ------------ |-- ------------ ------------ -R:13 | 0 UCIAG2AC*
UCIAP1AAC
|
R:25 | 0 UCPBG7AF*
DS206TMCAED | 0
DS206TMCAED A7
R:25 | 1 UCPBG7AF*
DS206TMQAEF |
R1:01 | 0 TCQAG1BF*
TCQAP1BBB
| 0 TCQAG****
TCQAP1BBB
A7
R1:02 | 0 TCQEG1AE*
TCQEP1ABB
| 0 TCQEG****
TCQEP1ABB
A7
R1:02 | 1 TCQEG1AE*
TCQEP2AAB
| 1 TCQEG****
TCQEP2AAB
A7
R1:04 | 0 TCDAG1BF*
TCDAP1BCG
| 0 TCDAG1BG*
TCDAP1BCG-1 A7
R1:12 | 0 UCPBG6AF*
UCPBP1ACE
| 0 UCPBG****
UCPBP1ACE
A7
R1:13 | 0 STCAG1AA*
STCAP1AAB
| 0 STCAG1AA*
STCAP1AAB
A7
R1:13 | 1 STCAG1AA*
STCAP2AAB
| 1 STCAG1AA*
STCAP2AAB
A7
R1:15 | 0 TCEAG1BA*
TCEAP1BBC
| 0 TCEAG****
TCEAP1BBC
A7
R1:16 | 0 TCEAG1BA*
TCEAP1BBC
| 0 TCEAG****
TCEAP1BBC
A7
R1:17 | 0 TCEAG1BA*
TCEAP1BBC
| 0 TCEAG****
TCEAP1BBB-1 A7
R2:01 | 0 TCQAG1BF*
TCQAP1BBB
| 0 TCQAG****
TCQAP1BBC
A7
R2:12 | 0 UCPBG6AF*
UCPBP1ACE
| 0 UCPBG****
UCPBP1ACE
A7
R2:13 | 0 STCAG1AA*
STCAP1AAB
| 0 STCAG1AA*
STCAP1AAB
A7
R2:13 | 1 STCAG1AA*
STCAP2AAB
| 1 STCAG1AA*
STCAP2AAB
A7
R3:01 | 0 TCQAG1BF*
TCQAP1BBB
| 0 TCQAG****
TCQAP1BBB
A7
R3:12 | 0 UCPBG6AF*
UCPBP1ACE
| 0 UCPBG****
UCPBP1ACE
A7
R3:13 | 0 STCAG1AA*
STCAP1AAB
| 0 STCAG1AA*
STCAP1AAB
A7
R3:13 | 1 STCAG1AA*
STCAP2AAB
| 1 STCAG1AA*
STCAP2AAB
A7
R5:01 | 0 TCCAG1BA*
TCCAP1BAD
| 0 TCCAG****
TCCAP1BAD
A7
R5:02 | 0 TCCBG1BE*
TCCBP1BAC
| 0 TCCBG****
TCCBP1BAC
A7
R5:02 | 1 TCCBG1BE*
TCCBP2BAB
| 1 TCCBG****
TCCBP2BAB
A7
R5:04 | 0 TCDAG1BF*
TCDAP1BCG
| 0 TCDAG1BG*
TCDAP1BCG
A7
R5:12 | 0 UCPBG6AF*
UCPBP1ACE
| 0 UCPBG****
UCPBP1ACE
A7
R5:13 | 0 STCAG1AA*
STCAP1AAB
| 0 STCAG1AA*
STCAP1AAB
A7
R5:13 | 1 STCAG1AA*
STCAP2AAB
| 1 STCAG1AA*
STCAP2AAB
A7
----- |-- ------------ ------------| --- -------- ---- ---------- LIST OF ITEMS OF INTEREST ----BMS |PR HARDWARE
FIRMWARE
| HFS PHYSICAL SLOT (DHTR)
----- |-- ------------ ------------| --- -------- ---- -----R:25 | 0 UCPBG7AF*
DS206TMCAED | H
R
1 ( 1H1)
R1:04 | 0 TCDAG1BA*
TCDAP1BCG
| HF Q11
1 (
)
R1:17 | 0 TCEAG1BA*
TCEAP1BAD
| F P1
3 (
)
R2:01 | 0 TCQAG1BF*
TCQAP1BBB
| F R2
2 (
)
R5:04 | 0 TCDAG1BF*
TCDAP1BCG
| H
R51
1 (
)
--HFS
--H
HF
F
F
Notes
CHAPTER 5
Chapter 5 Mark VI
Mark VI Controller
The Mark VI controller is configured using the control system toolbox. The toolbox
is a Windows-based software package used for hardware module selection,
configuring, downloading, and monitoring the Mark VI controller. Refer to GEH6403 Control System Toolbox for Configuring a Mark VI Turbine Controller for
more information. The toolbox provides the following main functions:
Report generation
The toolbox can run in the HMI PC or in a separate workstation on the data highway.
Note The HMI is not used to configure the Mark VI.
Flash Downloader
The Mark VI controller is configured from the toolbox. The toolbox software can be
run in the HMI PC or in a separate workstation on the data highway. If the controller
is being setup for the first time, the first step in the configuration procedure is to load
the flash memory, called CompactFlash, using the Flash Downloader software. For
details, refer to GEH-6403 Control System Toolbox for Configuring a Mark VI
Controller.
EPA Log
When the emissions are not in compliance, data is stored in capture blocks in the
Mark VI controller. The controller determines compliance with the EPA regulations
based on hourly averages, and when not in compliance, the controller sets an alarm
and starts injection of water. It then uses capture blocks to store the data in the form
of four-minute averages and hourly averages. This data is uploaded to the HMI
where the EPA log is printed out. If the optional Data Historian is present, it can
upload the data and store it in a collection file.
Trend Recorder
In the Mark VI, real time process data can be collected and trended by the toolbox.
Process data is sampled in the controller as fast as every 32 ms. The sample set is
then transmitted over the Unit Data Highway to the toolbox where it is trended.
Multiple process points can be color trended on a white background to give a highresolution display. Refer to GEH-6126 HMI for Turbine Control Operators Guide
and 6408 Control System Toolbox for Configuring a Trend Recorder.
Auto Calibration
Mark VI uses the toolbox for valve auto calibration. A series of commands are made
from the LVDT/R Calibration dialog box, which is found in the Outline View under
the appropriate VSVO board. These force the actuator to the end positions and store
the data. The plots of stroke (position) against current (amps) and can be used to
check linearity. For more information, refer to GEH-6421 SPEEDTRONIC Mark VI
Turbine Control System Guide, and the toolbox manual, GEH-6403 Control System
Toolbox for a Mark VI Turbine Controller.
Control Constants
Mark VI uses the toolbox to view and work with control constants. The toolbox
control constants display is called the Control Constant View. This display provides
the Signal name, live Value, Initial Value, Type, Scale, and Note information for all
control constants. Control constants can be edited and live values modified from this
display. For more information, refer to GEH-6403 Control System Toolbox for
Configuring a Mark VI Controller.
CHAPTER 6
Chapter 6 HMI
Overview
Directory Structure and Files
The HMI software is stored in multiple directories on the hard drive; the first is
CIMPLICITY
HMI
api
arc
Bsm_data
cimpole
classes
data
docs
ETC (Version 5.5)
exe
extras
help
log
pager
projects
report
scripts
Setup
symbols
TCI Directories
The two TCI directory groups are product-specific software and site-specific
software, and are divided on pseudo or substitute drives.
The G: drive and its subdirectories contain the software common to all turbine
control panels.
The hard drive for a typical factory-configured HMI is partitioned to be two drives,
C: and E:. The following diagram displays the TCI directory trees for C: and E: of a
typical HMI.
As displayed in the directory trees, drives F: and G: point to directories on the C: and
E: drives. The pseudo drives are established by TCI when it starts up. Programs
running under TCI require the above pseudo drive and directory structure for proper
operation.
Drive F: Files
The top level of the pseudo drive F: contains files that configure the HMI.
Drive F: Sub-directories
\CIMPROJ contains the CIMPLICITY project files including the device and
screen definitions.
\UNITn is created for each unit being controlled by a TCI, where n is equal to
the unit designator. This directory holds the files that define and configure a
specific unit.
Drive G: Sub-directories
Sub-directories on drive G: contain the following information files:
\EXEC contains all the executable files and programs that form TCI, and any
batch files used during start-up or execution.
\DATA contains any data files required by programs that are not site-specific. It
also contains template data files that can be used as a reference to configure the
site-specific files located on the F: drive.
\LOG contains the output from various programs, which is important for
debugging or troubleshooting purposes. Error log files and normal start-up files
are stored here.
Mark IV
Mark IV Modbus
Mark VI
Mark IV
This displays how to set up the addresses for the Mark IV, Historian, and HMI when
communicating using the CSF or serial media. The following Mark IV address
conventions must be followed to communicate successfully between HMI and Mark
IV. Note the differences between serial and CSF interfaces.
The following table displays the CSF address and LUN assignments that are
assigned to the Mark IV controllers. Routing tables in the communications layers
expect these Address/LUN bindings, they cannot be chosen at random.
Mark IV CSF addressing
Unit
FE
0401
FC
0402
FA
0403
F8
0404
F6
0405
F4
0406
F2
0407
F0
0408
The following table displays the CSF addresses and LUN assignments for an HMI or
Historian. Routing tables in the communications layers expect these Address/LUN
bindings, they cannot be chosen at random.
HMI/Historian CSF Addressing
HMI
CSF Address
LUN
1F
0A01
1E
0A02
1D
0A03
When using a serial MSP link from an HMI (or Historian) to the Mark IV a special
address must be used on the HMI end depending upon which port (top or bottom) is
used in the Mark IV.
If connecting to the top port on the Mark IV, the LUN of the HMI must be
0B01. (This is specified in the My LUN field of the F:\CONFIG.DAT file.)
If connecting to the bottom port on the Mark IV, the LUN of the HMI must be
0B02.
HMI
0F
0D01
0E
0D02
Unit
Serial
Address
PC
LUN
Mark IV
Port
FE
0B01
Top
FC
0B02
Bottom
Mark IV
Mark IV
Card (HCMx) Port
HMI
LUN
Top
0B01
Bottom
0B02
Top
0B03
Bottom
0B04
Mark IV Modbus
The HMI can act as a Modbus Master to the Modbus Slave option in the Mark IV
controller.
To configure HMI as a Modbus Master:
1
Create a Data Dictionary in F:\UNITn to hold the point values in the HMI. Refer
to the Creating a Data Dictionary section for more information.
The Modbus list defined in F:\UNITn\MMbus<n>.DAT must match the list in the
Mark IV controller as defined on the Data List 17 screen.
Use the MM_STAT program to verify communications, refer to the MM_STAT Modbus Master Statistics section for more information.
If using ARCNET/CSF then the TCI Control Panel Applet is used to configure
the CSF card in the computer. Refer to the TCI Control Panel Applet, ARCNET
(ISA) section for more information.
Create a Data Dictionary in F:\UNITn to hold the point values in the HMI. Refer
to the Creating a Data Dictionary section for more information.
Create PDDump.dat to define the points received from the Mark IV. Refer to
Predefined Data Dump Configuration for more information.
Create a Data Dictionary in F:\UNITn to hold the point values in the HMI. Refer
to the Creating a Data Dictionary section for more information.
The Mark IV PROM list and the HMI PDDump.dat list should match so the correct
data is displayed on the HMI.
Use the PDD_STAT program to verify communications. Refer to the PDD_STAT
Predefined Data Dump Status section for more information.
Mark VI
The UDH network is used to communication between the HMI and the Mark VI
controller. The network interface is configured using the toolbox. From the
Network Interface window, in the Outline View, click on the interface name, and
then select Modify from the Edit menu. Refer to GEH-6403 Control System
Toolbox for a Mark VI Turbine Controller.
GSM
HMI SERVER
Modbus
Slave
Device
CIMPLICITY
Modbus
Master
Communications
CIMPLICITY
CIMMOD
TCI
Modbus
Slave
Historian or
DCS
(Modbus
Master)
(Modbus
Slave device
includes Meters
and Relays)
Data Flow from a Modbus Device
GSM
The GSM (GE Energy Standard Messages) protocol provides real time information
as well as alarm and event information to a DCS over an Ethernet link. GSM is a
client/server protocol where the GSM Client issues requests to the GSM Server
running on the HMI.
The GSM protocol uses signal names to define each signal, and as such there is no
configuration required on the HMI to support a GSM Client. The GSM Server will
return whatever information is requested by the GSM Client, resolving signal names
inside the HMI as needed.
The GSM messages allow the GSM client to:
EPA Log
The EPA log is used on dual fuel-gas turbines with water injection for reducing the
emission of oxides of nitrogen. The EPA data is used to determine compliance with
government environmental regulations.
Process Alarms
Diagnostic Alarms
Events
The definition and configuration of these point categories and the setup of the Alarm
Printer is covered later in this manual.
Select Unit
Each of the categories of information may be selected on a unit basis. The unit may
be changed by selecting a unit name from the Select Unit box. Unit names are
listed in alphabetical order. The categories are as follows:
All Units. The All Units button applies the settings for the current unit to all
units.
Flush Button. The Flush button deletes all pending alarm print jobs from the
Alarm Printer for all units. The Flush button takes immediate action and does
not require the OK button to be activated.
Save Settings. Any changes made to the Alarm Logger settings are saved
only if the user selects OK when leaving the Alarm Logger Control dialog box.
File Type. The Alarm Logger Control does not access any files when making
its changes. Instead, it writes its output to a special section of global memory
that is then read by the Alarm Log program, which writes the alarms and events
to the alarm printer.
FTP Interface
The FTP Interface allows the transfer of files to and from the HMI. The only
directories accessible are the ones below the ftp-root directory. Virtual directories
can be used to make any directory appear in the ftp-root directory.
Trip History
In a Mark V system, the logged trip history data can be viewed on the HMI. In a
Mark VI it can be viewed on the HMI or on the toolbox using the Data Historian
software. The Mark V and Mark V LM Trip History file collection and report format
were changed under TCI 1.6 to be more compatible with the OSM. The new file
format is much easier for loading into Microsoft Excel for processing. (Excel is not
included with the HMI. It can be purchased as an option.) Refer to Volume I for
description of Trip History features.
File Type
Viewing. The Trip History Program stores the results of the data retrieval in a readonly temporary text file. This file is displays using Notepad and then may be saved
to another permanent file by using the File:Save As menu option in Notepad.
The Trip History dialog box controls the collection of Trip History data and
Historical log from the unit control. The user must select a valid unit in the Select
Unit list box and select the type of historical data to be collected from the radio
buttons in the Select Log section. Only one type of data may be collected at a time.
There are three categories of information that may be collected:
Trip History
Saved Data
New Data
Trip History Data. Trip History Data is saved when the turbine trips. For Mark V
LM unit controls, the data is saved in the control even after the control is reset.
Saved Data. Saved Data is saved into the control memory when the user collects
New Data. It remains in memory until it is overwritten by New Data or until the
control is reset.
New Data. New Data is saved to the control memory when the user collects New
Data. The data reflects the most recent control data. The data remains in the control
memory as Saved Data until it is overwritten or until the control is reset.
Note Collecting New Data overwrites the Saved Data in the controller. On Mark
V units, New Data overwrites the Trip History Data in the controller.
Data Retrieval. Begin data retrieval by selecting the Collect button in the Trip
History dialog box. Selecting the Stop button may halt data retrieval. A message
box displays if the data retrieval fails or is stopped by a user command. When the
data retrieval completes successfully, the results are displayed in a separate viewer
window.
Select the Close button to exit the Trip History dialog box. Any results currently
being viewed remain in their respective windows.
Viewing Results. When the data retrieval completes successfully, the results are
displayed using Notepad in a separate viewer window. The data is designed to be
viewed using a fixed pitch font (all characters have the same width). Any word
wrapping features should be disabled. The results displayed are stored in a read-only
temporary file. To save the information being displayed, the file must be copied to a
permanent file location using the File:Save As menu option.
The results saved are in the following format:
Post Trip List: three 1-second post trip records. These three records are filled
with data only when there has been an actual trip. Otherwise, these records are
blank.
Timetag
Executing the Trip History Program. The Trip History Program may be
launched from the command line with the following optional argument to quickly
bring the display to a desired configuration. The user can use this command line
parameter to customize the startup of the program, or enter TRIPDLOG.EXE in the
Run dialog box in the Start menu, or simply double click on the program icon.
Run the Mark V Trip Log Viewer and select a valid unit.
The trips are displayed by their date and time stamps. The latest trips are listed at the
top of the list. After selecting the trip to be viewed, the results are displayed in a
separate viewer window.
File Type. The Mark V Trip Log List Viewer Program determines the trip times
associated with each file from the name of the file, which is encoded with the time of
the trip. The selected file is displayed using Notepad and then may be saved to
another permanent file by using the File: Save As menu option in Notepad.
The files are stored in the C:\HMIDATA directory. The files are managed by the
automatic collection program where the file name format is
YYYYMMDD_HHMMSS_UU-TR?.CSV, where:
TRP or TRQ is used to indicate that the file contains trip information (TRP) or
user requested data (TRQ).
The file is given a *.CSV extension to facilitate viewing and data analysis from
Excel.
After the maximum number of trip log files is created, the oldest trip log is
overwritten by any new data.
The Trip Log List Viewer dialog box controls the selection of Trip History data
stored on the disk. Select a valid Mark V or Mark V LM unit in the Select Unit list
dialog box. The list of past trips for that unit is listed below for selection. The files
are displayed in the Trip Log List Viewer dialog box by the trip date and time.
Highlighting a selection and use the Go To button to display that file. Select the
Close button to exit the Trip Log List Viewer dialog box.
Data Retrieval. Trip History data for Mark V and Mark V LM controllers is
automatically retrieved and stored on the HMI disk by the Trip Log Collection
utility, if the HMI is running and communicating with the controller. The last n trips
are stored where n can be user-specified with a default of 10. After that, the oldest
trip log is overwritten by any new trip data.
Viewing Results. Please refer to the Viewing Results section on the Trip Log
Collection utility for a detailed description of the data format and viewer program.
Executing the Trip Log Viewer. The Trip Log Viewer may be launched from the
command line with the following optional argument to quickly bring the display to a
desired configuration.
Use this command line parameter to customize the startup of the program, or enter
tripvwr.exe in the Run dialog box in the Start Menu, or simply double click on the
program icon. The following example specifies the unit name (/UNIT:) as T1:
G:\EXEC\TRIPVWR.EXE /UNIT:T1
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 TCI System Service launches the TRPFIL program when the HMI is started, and
runs in the background until the TCI 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 TCI 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.
HHMMSS - The hour, minute, and second, zero padded if required, using a 24hour format.
.CSV - The file extension, always .CSV for Comma Separated Value files.
Report - For the Trip Log Collection files the value is always TRIP LOG.
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)
P - The processor generating the alarm. For process alarms this is always Q.
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
(C:\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.
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.
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.
Note The Disk Manager deletes the files as part of its normal disk purging
operation. Refer to the Disk Manager section for more details.
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.
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.
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.
Diagnostic Display
There is a special diagnostic mode in this version of the TRIFIL 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 TRIFIL 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.
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).
No License. The program license (for the TRPFIL software product on the
HMI) is missing or invalid, the controller will not be 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
----
T1
Done
01-SEP-1999
17:10:28
Filename
19990901_171028_T1_TRP
+-----------------------------------------------------------------+
|UNIT_NUMBER <num>
TITLE "<title>" TYPE "<display type>"
|
+-----------------------------------------------------------------+
DISPLAY RECORD: One of the displays defined.
start in the first column.
These must
<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"
+------------------------------------------------------------------+
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 "LOAD"
"SETPOINT" # ""
"L90PSEL_CMD" ""
""
0
;
;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 "START"
""
? ""
"L1START_CPB" ""
"L1X"
1
;
;P unit-pointname
;- ---- -------------P ""
"L2TV"
P ""
"L14HM"
P ""
"L14HS"
P ""
"L3"
;
T value
- -----= 0x00
T value
- -----= 0x04
The following four examples show the Demand Display screens from DEMO.DM2
corresponding to the DEMO.SRC source file.
Demand Display Screen Logics, a dictionary based display. This can display
logics given the types of points and classes of points.
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 userdefined commands. The command spacing is no closer than every fourth line to
prevent overlap.
If the data comes through the TCI Data Dictionary then the Modbus register
layout is defined in the MODBUS.DAT file in the unit configuration directory,
and MODBUS_L is used to provide a formatted list of the signals available.
The Mark V can use either of the above two versions to obtain Modbus data, the
Mark IV and the Mark VI always get data through CIMPLICITY. When the TCI
MODBUS Master retrieves data from a device it forwards the data to CIMPLICITY,
therefore CIMMOD is used to retrieve the data.
MODBUS_ L is run from the unit configuration directory for the desired unit,
typically F:\UNITn.
A sample F:\UNITn\MODBUS.LST file is displayed below:
+HR0001
|
+HR0002
|
+HR0003
|
HR0004
|
HR0005
|
+HR0006
|
+HR0009
|
HR00010 |
HR0200.00|
HR0200.01|
HR0200.02|
HR0200.03|
+HC0001
|
+HC0002
|
+HC0003
|
+HC0004
|
SWREF_CMD
DRVAR_CMD
SC43LOAD
@SPARE
@SPARE
L90PSEL_CMD
SC43
SS43
L52GX
L94X
L30D_SD
L30D_SU
L1FAST_CPB
L1START_CPB
L70R4R_CPB
L70R4L_CPB
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SIGN16
SIGN16
UNS16
spare
spare
SIGN16
UNS16
UNS16
PACKED
PACKED
PACKED
PACKED
LOGIC
LOGIC
LOGIC
LOGIC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
512 | 0 | MW
|
512 | 0 | MVAR |
65536 | 0 | STATE |
512 | 0 | MW
| PRESELECTED LOAD ANALOG SETPOINT
65536 | 0 | STATE | TURBINE CONTROL SELECTION
65536 | 0 | STATE | TURBINE COMMAND STATE SELECTION
GENERATOR BREAKER CLOSURE
NORMAL SHUTDOWN
NORMAL DISPLAY MESSAGE SHUTDOWN STATUS
NORMAL DISPLAY MESSAGE STARTUP STATUS
FAST LOAD START SIGNAL
START SIGNAL
SPEED SETPOINT RAISE COMMAND PUSHBUTTON
SPEED SETPOINT LOWER COMMAND PUSHBUTTON
To run CimMod_L.
1
Configuration
Introduction
This chapter discusses the HMI architecture, TCI configuration, device
communications configuration, diagnostic tools, alarm logging, and remote access.
Special functions such as emissions analysis, the EPA log, and the performance
monitor are covered.
Auto Login
This tab configures the login procedure. Auto Login causes the computer to login as
the defined user when it is rebooted or when the current user logs off. To override
the auto login when it is enabled, reboot and hold the shift key down after the desktop
background displays.
Disabled/Enabled - If Disabled is selected, the computer will not try to auto
login the user. If Enabled is selected, the computer will try to automatically login
the user defined in the Username, Domain and Password sections below.
Username - This is the user name used to login if auto login is enabled.
Domain - This is the domain used if auto login is enabled. It is usually the assigned
computer name.
Password - This is the password used by the login if auto login is enabled.
Password Verify - This entry must match the entry in Password. If they do not
match, a warning is displayed with a request to enter it again.
TCI Site
This tab sets the default site parameters for the TCI, and the scale.
Site Directory - This is the directory in which all the site information is located.
The F: drive is mapped to this location.
Default Scale - This is the default scale used to display information. It can be set to
any scale defined in the data dictionary (for example, English or Metric).
Disable Text Translation - This option is available only if the F:\phrase.dat file is
present. Signal text descriptors will appear in the language defined in the phrase.dat
file. Select this option to disable text translation and return to the original language.
Select to return to
original alarm text.
Time Hardware
This tab sets the type of time synchronization hardware used with this TCI.
Time Card - This selects the type of time synchronization hardware to use.
IO Address This is the IO address of the Time Card. Not all cards require this
field, it will be grayed out if not required.
Time Code This sets the type of time code used (for example IRIG-B).
Time Base This sets the time base used (for example UTC).
This tab sets the time synchronization modes for this TCI.
ARCNET (ISA)
This tab sets the parameters the ARCNET driver uses to talk to the ARCNET card.
The jumpers on the card must be set to match these parameters for the ARCNET
driver to work.
The ARCNET Peripheral Component Interconnect (PCI) card does not require setup
in the TCI Control Panel Applet it is a plug-and-play card and no additional
configuration is required.
The TCI control Panel Applet will have all fields grayed out.
This tab configures the parameters the ARCNET driver uses to talk to the ARCNET
card. The jumpers on the card must be set to match these parameters for the
ARCNET driver to work. An ARCNET tab is displayed on the Turbine Control
Interface Control Panel applet for each ARCNET card on the HMI.
Base Memory Address is the memory address set on the ARCNET card.
ARCNET Link Address is the address of the ARCNET card on the ARCNET
network. All card on the network must have a unique address.
Note Press the Apply button to save changes already made to fields on any of the
tabs before using the Add New or Remove This buttons.
Add New adds an ARCNET card to the registry. Zero, one, or two ARCNET
cards are permitted. Pressing this button causes the immediate addition of a new
card. This is an instant action button and does not require the Apply button.
Remove This removes the currently selected ARCNET card from the registry,
reducing the total number of ARCNET links by one. The current ARCNET page
will disappear unless this is the last ARCNET page; existing ARCNET cards
with higher card numbers will shift down to fill the gap.
TCI Configuration
TCI runs the processes that allow communication with unit controllers. TCI contains
the following:
The TCI Service that uses the unit configuration on the HMI to communicate
with unit controllers.
File Name
Internal
Mark IV
Mark V
Mark V LM
Mark VI
DCS
AT_START.DAT
Optional
Optional
Optional
Optional
Optional
Optional
AT_STOP.DAT
Optional
Optional
Optional
Optional
Optional
Optional
CONFIG.DAT
Required
Required
Required
Required
Required
Required
ENETALM.DAT
NA
NA
NA
NA
Required
NA
EGD_PUSH.DAT
NA
NA
NA
NA
TCI to PI option
NA
IO_PORTS.DAT
MODBUS,
Em_Ana
MODBUS, PDD,
Serial MSP
NA
NA
NA
MODBUS
MDB_FWD.DAT
Optional
Optional
Optional
Optional
Optional
Optional
PICONFIG.DIF
TCI to PI option
TCI to PI option
TCI to PI option
TCI to PI
option
PI_PUSH.DAT
TCI to PI option
TCI to PI option
NA
TCI to PI
option
TIMESYNC.DAT
Recommended Recommended
Recommended
Recommended
Mark V
NA
TIMEZONE.DAT
Required
Required
Required
Required
Required
Required
Internal Unit For storage of computed values and data from a DCS, for example.
A number of optional configuration files are only required if the option they control
is in use at this site.
F:\AT_START.DAT is used to define a set of commands that are run after TCI is
started. It is used to start any site-specific programs that need to be started after TCI
is started.
F:\AT_STOP.DAT is used to define a set of commands that are run before TCI is
shut down. It is normally used to stop any site-specific programs that need to be
stopped before TCI is stopped.
F:\CONFIG.DAT is the primary configuration file for the TCI System Service. This
file informs the TCI System Service of the following:
The list of turbines with the internal unit number (1..n), unit name,
configuration directory, and controller type (Mark IV, Mark V, Mark V LM,
Mark VI).
F:\EGD_PUSH.DAT is used at sites with controllers that use the EGD protocol
over Ethernet, such as the Mark VI controller. This file defines the list of signals that
are to be read from EGD and pushed into PI for the TCI to PI option.
LINEDRAW.TTF. This TrueType font includes the special symbols used for
drawing line and box graphics in a non-proportional spaced font. This is used for
printing out CSP documents, and is used by the Dynamic Rung Display for
presenting information.
From the Menu click Action Stop or Action Start. A Service Control
confirmation window will open with a status progress bar. Upon completion the
confirmation window closes and the Status field in the Services window will
display the new status (Started or blank).
Double click the TCI (Turbine Control Interface) in the Name field. This
will open a dialog window with the necessary Stop and Start buttons. Click the
button and a Service Control confirmation window will open with a status
progress bar. Upon completion the confirmation window closes and the Status
field in the Services window will display the new status (Started or blank).
Click the Stop or Start icon from the toolbar to immediately change the
running state of TCI. A Service Control confirmation window will open with
a status progress bar and will close upon completion.
Services
window
Stop icon
TCI Status has
been Started
Click to Start
TCI if it has
been Stopped.
Click to Stop TCI if it
has been Started.
Right click to
open context
menu.
Click to select
Manage from the
context menu.
Stop
Refer to Controlling the TCI Service in the TCI Service Stop and Start From The
Services Window section for information on how to control the service from here.
For each Modbus slave, the data communicated is specified by the contents of a data
file found in the unit directory. This file specifies what data is read from the slave
and stored in the Data Dictionary, and also what data is sent (written) to the slave.
The Modbus slave can be located anywhere within the restrictions of the RS-232C
serial communication link, or anywhere on the Ethernet link.
The RS-232C link transmission rate makes it satisfactory for one or two units on a
single communication link, depending on the amount of data that is requested for
transmission. It has a maximum 19,200-baud (bit/s) transmission rate, but lacks
individual time tags for alarms and events. An evaluation of the link load for a
specific application requires a review of the amount and frequency of the data
transmissions, the specified baud rate, and verification that all is within the desired
sampling rate.
Refer to the Configuration File (F:\IO_PORTS.DAT) section in this chapter for
details on how to configure a TCI Modbus Master.
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 diagram below displays the data flow paths through CIMPLICITY to the TCI
Modbus Slave to the DCS. Mark V data flows directly to the TCI Modbus Slave,
whereas Mark IV and VI data passes through CIMMOD first.
HMI SERVER
Mark VI
Mark IV
TCI
CIMPLICITY
CIMMOD
TCI
Modbus
Slave
DCS
Mark V and
Mark V LM
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 for a single TCI. 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 TCI Modbus slave, configured with the appropriate address, replies with the
requested data. A single TCI can respond to multiple slave addresses. Up to a
maximum of 16 slave addresses can be configured for a single TCI. Normally each
separate slave address would be assigned to gather data from a separate unit control.
PLC data can also be supplied to the DCS or Historian through the TCI Modbus
Slave. For a Mark VI based system with the GE Fanuc 90-70Programmable Logic
Controller (PLC), the Series 90 Ethernet driver is used, and for other
manufacturer's PLCs, the TCI Modbus Master is used.
Modbus Forward
The Modbus Forward is 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. Refer to the section on Configuration File
(F:\MODB_FWD.DAT) for more information.
If the existing Toolbox version is older than version eTCSS V01.02.03 build
an HMI Device by following the directions below.
Prerequisite
The HMI Device build adds Mark VI devices to the CIMPLICITY project. Mark VI
devices must be added to an already existing Port in the CIMPLICITY project. Refer
to CIMPLICITY Configuring Ports Mark VI in Chapter 8 for details on how to
create the port used for Mark VI devices.
Build an HMI Device
Note Execute the build for each HMI Device only on the target HMI. For example:
Only build the CRM1 HMI device on the CRM1 HMI.
Normally changes are made by opening an existing Toolbox HMI Device (*.HMB
file) and applying changes. Double click on the *.HMB file to open Toolbox with the
HMI Device opened in the initial window.
If you need to add new exchanges (such as new exchanges in an existing device
or a new device) proceed to step 6.
If you are not adding any exchanges, you simply need to update existing
exchanges, proceed to step 7.
Select New by selecting the New icon or by selecting File -- New which will
open the New dialog box. Select the System Configuration tab, then select
Turbine HMI Configuration, and click OK.
The hmdv1 Window opens. Hmdv1 is the default HMI Device Name.
Additional HMI devices default to hmdv<n>, where n is one higher than the last
existing device.
Select Options - Privilege, which will open the Select Privilege Level
dialog box. Select Level 2 and click OK. Enter Password (if required) and click
OK.
Double click on hmdv1 in the left pane. This will open the HMI Configuration
Properties dialog box with default values.
Enter the required information using the 4108 drawing to obtain the correct computer
names and IP addresses.
Configuration Name is usually the first part of the HMI Name, such as CRM1,
CRM2, GT1, GT2, and so on.
PDH IP Address is the assigned IP Address. This is obtained from the 4108
documentation.
UDH Name is the PDH Name prefixed with a U such as UCRM_SVR, and so
on.
UDH IP Address is the assigned IP Address. This is obtained from the 4108
drawing.
HMI Project File is the Project Name preceded by the path. This is typically
E:\SITE\Cimproj\xxxx.gef
Right click on Hardware and I/O Definitions and select Insert First from
the context menu. This opens the Enter or Select a Network dialog box. The
Network Name is typically EGD1.
Click OK. The network should now appear under the Hardware and I/O
Definitions section.
Right click on EGD1 :EGD Network and select Insert First from the context
menu. This opens the Select EGD Exchange(s) for network EGD1 dialog box.
Select EGD Exchange(s) for network EGD1 dialog box with list of available Exchanges
Select the desired Exchanges from the list to add to the HMI Device and click OK.
Usually all the Exchanges are selected except those for EX2000.
Selected
Exchanges will be
added to device.
List of Available Exchanges to Add to the HMI Device
Observe the selected Exchanges were added to the Network. The Exchange Name
field will be populated with the desired exchange, but the rest of the fields will have
illegal or default values. This is not a problem the remaining fields will be updated
during the Get From Database.
Exchanges added
to the HMI device.
Each Exchange will need to be configured. Right click on an Exchange and select
Modify from the context menu. This opens the Edit EGD Exchange dialog
window.
Update Mode: This field defines when the point value is sent to CIMPLICITY.
The recommended setting (Unsolicited on Change) will send values when it
detects a change in the value. The other setting (Unsolicited on Scan) will send
value each time it is scanned whether or not the value changed.
Point Scan Multiplier: This determines whether each time an EGD page is
received the value is scanned for sending to CIMPLICITY. EGD pages that are
transmitted at a high rate sometimes use a multiplier other than one (1) to slow
down the data flow into CIMPLICITY.
Select Unsolicited on Change for the Update Mode. Leave the default value of
one (1) for the Point Scan Multiplier. Click OK. Configure the remaining
Exchanges.
Select the Put In Database icon or select Device then Put to Database.
Select Yes from the confirmation dialog box to begin populating the database
(SDB).
Put In
Database
icon
Resolve
errors before
continuing.
Select the Get From Database icon or select Device then Get From
Database. Select Yes from the confirmation dialog box to begin reading the
database (SDB).
The Get From Database can take several minutes. During the procedure
dialog boxes are presented to display the progress, and error messages are
logged to the main error window.
When the Get Scales from Database dialog box opens, select Yes.
Select Yes
Resolve errors
before continuing.
Select the HMI Device name at the top level of the tree in the left hand panel,
then select the Validate icon or select Device then Validate. If the top level is
not selected before selecting Validate the validation will fail with errors.
Validation icon
Results of Validate
10 Select the Build icon or select Device then Build. Select Yes to begin the
Build. During the procedure dialog boxes are presented to display the progress,
and error messages are logged to the main error window.
Build icon
Resolve any
logged errors.
Results of Build
11 Save the HMI Device by using the toolbox Save icon or File - Save.
12 Stop TCI. Refer to TCI Starting and Stopping in this chapter.
13 Stop the CIMPLICITY project if it is not already stopped. Refer to Chapter 8
CIMPLICITY Starting and Stopping a Project. Perform a CIMPLICITY
Configuration Update. Refer to Chapter 8 CIMPLICITY Configuration
Update.
14 Check for error messages in the
C:\WINDOWS\System32\drivers\etc\hosts file (open with Notepad)
and the C:\CIMPLICITY\HMI\ETC\Cimhosts.txt file before
continuing.
15 Start TCI. Refer to TCI Starting and Stopping in this chapter.
16 When TCI has completed starting it should start the CIMPLICITY Project verify that data is being received.
The F:\AT_STOP.DAT file is used to define a set of commands that are run before
TCI is shut down. It is normally used to stop any site-specific programs that need to
be stopped before TCI is stopped. The following is a sample F:\AT_STOP.DAT
file:
;
; F:\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 stopped before the core systems are stopped.
;
; A companion file (AT_START.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>\SHUTDOWN.DAT
;
; [End of File]
;----------------------------------------------------------------------------;
; 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
;
MSP LUN............. The node's assigned HEX MSP LUN (CSF, SERIAL only)
;
;
UNIT
NETWORK
NET
MSP
NETWORK_DATA
;
NUMBER
PROC NUMBER
ADDR
LUN
;
--------- ------------- -----------1
C
1
FE
0401
2
C
2
FC
***
4
R
2
F8
***
;
;----------------------------------------------------------------------------OPTIONS
;
;
Specialized settings
The F:\CONFIG.DAT file displayed above is configured with unit T1 as a Mark IV
with communication over CSF. The NETWORK_DATA section for CSF and
SERIAL communication must contain the LUN number used with the corresponding
unit control. Refer to the NETWORK_TYPE settings, which define the CSF, Serial,
and Stagelink Networks that are used. The LUN for the HMI must appear in the
NETWORK_TYPE section for CSF and SERIAL Mark IV communication.
Stagelink needs to be defined only once if there are Mark V units, as it can
communicate with multiple Mark V and Mark V LM units. CSF needs to be defined
only once if there are Mark IV units, as it can communicate with multiple units over
CSF.
Each Serial network defined must have a corresponding section in the
IO_PORTS.DAT file.
NETWORK
TYPE
------STAGELINK
DEVICE
DRIVER
------CCSI20020Dev1
MY
LUN
----****
NETWORK_TYPE
------------
Note The LUN file entry is used only for Mark IV CSF communications.
A typical NETWORK_TYPE section for two PCI ARCNET cards on a single
computer follows:
;
;
;
;
;
;
;
;
;
;
;
NETWORK
TYPE
------STAGELINK
STAGELINK
DEVICE
DRIVER
-------CCSI20020Dev1
CCSI20020Dev2
MY
LUN
---****
****
NETWORK_TYPE
--------------
Note The first PCI ARCNET card must use device driver CCSI20020Dev1,
otherwise the computer can lock up.
Note The following section is used to configure a Modbus Slave application. Refer
to the TCI 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]
;
;format1:
SLAVE nnn
UNIT uu
MODE keyword
;format2:
SLAVE nnn
CIMPLICITY project 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)
;
project is the name of a CIMPLICITY project on this computer.
;
keyword is either RS16, RU16, UN12, HW12, or NATIVE for Signed 16,
;
Unsigned 16, Unsigned 12, Honeywell 12, and Native data
;
respectively.
;
;
SLAVE and MODE are required entries. UNIT or CIMPLICITY must also be
;
on a valid line.
;
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 RS16
;SLAVE 2 CIMPLICITY <project_name> MODE RU16
;------------------------------------------------------------------------;
; 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.
;-------------------------------------------------------------------------
Note This section configures a Modbus Master application. Refer to the TCI
Modbus Master section for further information.
;------------------------------------------------------------------------;
; This section defines MODBUS MASTER port and hardware characteristics.
; This section can be duplicated up to 8 times.
; Communication can be established with up to 48 modbus slaves.
;
[MODBUS_MASTER_PORT]
;1
port none
;port ethernet
;port com1
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
4
;Timeout interval between characters, msec. Default=40
;Normally, port_it should specify 3.5 character times as
;defined by the Modbus Gould specification. At 9600
baud,
;and 8 data bits, 1 start, and 1 stop bit, this yields
;a character time of 1.04 msec. 3.5 character times
would
;therefore be 3.125 msec.
port_tt
200
;Timeout for total message, msec. Default=200
;This is time to receive message only, not process it.
modbus_timeout
2000
;Time (milliseconds) before we give up
;waiting for a response from a slave.
;Default timeout is 2000 milliseconds.
;Minimum timeout is
100 milliseconds.
;Maximum timeout is 60000 milliseconds.
modbus_loop
5000
;Time (milliseconds) before we restart
;the request loop. This is the period of
;between asking the slave(s) for all the
;data specified and the time we start
;over and reask.
;Default loop is 5000 milliseconds.
;Minimum loop is 100 milliseconds.
;Maximum loop is 86400000 milliseconds.
tcp_port
502
;Specify tcp port to use.
;range 1-65000, default 502
tcp_addr
127.0.0.1 ;Specify the tcp port address using
;dotted number format (example: 127.0.0.1)
;or name format (example: division.company.com)
;default is 127.0.0.1
tcp_timeout
20
;tcp timeout in seconds when using ethernet
;If no reply in this period, close connection
;range 10-120, default 20 seconds
;format:
MASTER mmm UNIT uu
MODE keyword
; where:
mmm is the SLAVE address (in decimal) to use when
; communicating with unit uu.
; uu is the two character unit name (defined in F:\CONFIG.DAT)
; keyword is either RS16 or RU16 for Signed & Unsigned data
; respectively.
;
; UNIT, MODE, and MASTER are required entries.
; A new line should appear for each unit. Normally this is one
; or two lines for typical data patterns. A maximum of 48
; MASTER-UNIT-MODE lines may appear.
; MASTER 5 UNIT MM MODE RS16
;------------------------------------------------------------------------[MODBUS_MASTER_PORT]
;2
port none
;port com1
baud 9600
parity
0
;0-4 (none,odd,even,mark,space)
databits
8
;5-8
stopbits
Note The following section configures reception of the Mark IV Predefined Data
Dump messages. Refer to the Predefined Data Dump Configuration section for
further information.
;------------------------------------------------------------------------;
;
Mark IV Predefined Data Dump Interface
;
;The Mark IV Predefined Data Dump Program, PDDump, is a program that receives
;ASCII data over an RS232-C input port on a GE HMI processor, checks the
;received data, and then stores the data into the data dictionary.
;
[PDDump_SETUP]
;port com2
port none
unit T1
;unit name as specified in f:\config.dat
baud
9600
parity
2
;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
ic_timeout 500 ;intercharacter timeout, character times. Default=500
;-------------------------------------------------------------------------
;------------------------------------------------------------------------;
;
Mark IV Predefined Data Dump Transmit - PDXMIT
;
; This defines the interface that looks like a Mark IV. PDXMIT is a program
; that sends ASCII data over an RS232-C output port on a GE HMI processor.
;
; One of these sections exists per defined port. For each port in use, only
; one Unit can be used. However, the same unit can be used as the source of
; Mark IV style data dump messages from different physical ports. In this
; case, the optional line "Filename <pdxmit datafilename>" can be used to
; override the default filename, which is PDXMIT.DAT in the F:\UNITx directory.
;
;
Defaults values are:
;BAUD
9600
;PARITY
2
;DATABITS 8
;STOPBITS 0
;
FILENAME PDXMIT.DAT
;
unit
<No default - NULL>
;
; Section that have header lines of the form:
; [PSXMIT_SETUP none]
; are ignored. Change "none" to physical port name (ie. COM2, COM3 etc) to
; activate.
;
[PDXMIT_SETUP none] ; Change none to COM2 - Repeat for COM3, COM4 etc. as needed.
unit T1
;unit name as specified in f:\config.dat
filename pdxmit.dat ; Used if unit is used as data source on more than 1 port.
baud
9600
parity
2
;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)
[PDXMIT_SETUP none] ; Change none to COM3 etc. as appropriate
unit T1
;unit name as specified in f:\config.dat
filename
; Used if unit is used as data source on more than 1 port.
pdxmit_1.dat
baud
9600
parity
2
;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)
;-------------------------------------------------------------------------
Note The following section configures reception of the Emissions Analysis data.
Refer to the EM_ANA - Emissions Analysis section for further information.
;----------------------------------------------------------------------;
;
Mark V LM Emissions Analysis Interface
;
; This is the setup definition file for the RS232-c link
; between the HMI and the Emissions Analysis System.
; Remove ";" from beginning of each line to enable
;
;[em_ana_setup]
;unit
T1
;Unit name
;port
com2
;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
;trailer
1
;1=Linefeed termination. 2=Carriage return,linefeed term.
;port_it
40
;Timeout interval between characters, msec. Default=40
;port_tt
200
;Timeout for total message, msec. Default=200
;-----------------------------------------------------------------------
Note The following section configures a Mark IV serial MSP link. Refer to the
section MSP Over RS-232C for further information.
;-----------------------------------------------------------------------;
;
Setup for serial MSP (MA/MSP)
;
; This section of IO_PORTS.DAT is tendered as an example setup for serial
; MSP based on a NETWORK_TYPE section in the file F:\CONFIG.DAT that
; contains the line:
;
;NETWORK
NETWORK
DEVICE
MY
;NUMBER
TYPE
DRIVER
LUN
;------------------------;3
SERIAL
MSP_3
0B01
;
; The entry above, MSP_3, must match the section header below, [MSP_3].
; The "3" that appears as the first entry on the line above to represent
; the network number does not have to match, but it may be less confusing
; if they do match. The "0B01" is a hexadecimal representation of the
; LUN desired for MSP to use when communicating over the serial link.
; This will usually be 0B01 or 0B02 when communicating with a Mark IV.
; Set as appropriate.
;
[MSP_3]
;port com2
port none
baud
9600
parity
2
;0-4 (none,odd,even,mark,space)
stopbits
0
;0-2 (1, 1.5, 2 stop bits) (1.5 stop bits currently
unsupported)
port_it 1000
;intercharacter timeout, 10-60000ms. Default=1000ms.
*
float32,1,T1:BB_MAX ,IN/S ,2, 0.00, 8.00, 1,0, 0.0320, 0.0800,Max
Vibration
float32,1,T1:BB1 ,IN/S ,2, 0.00, 8.00, 1,0, 0.0320, 0.0800,Vibration
sensor
float32,1,T1:BB2 ,IN/S ,2, 0.00, 8.00, 1,0, 0.0320, 0.0800,Vibration
sensor
*
@endsection
*
*
@istr pointtype,pointsource,tag,exdesc
*
float32,1,T1:BB_MAX ,Max Vibration
float32,1,T1:BB1 ,Q -TBQB-051 Vibration sensor
float32,1,T1:BB2 ,Q -TBQB-053 Vibration sensor
*
@endsection
*
*
@istr pointtype,digitalset,pointsource,tag,descriptor
*
Digital,LogicF,1,T1:L14HA ,HP Speed - Accelerating speed
Digital,LogicF,1,T1:L14HM ,HP Speed - Minimum Firing Spd
Digital,LogicF,1,T1:L14HR ,HP Speed - Zero Speed
*
@endsection
*
*
@istr pointtype,digitalset,pointsource,tag,exdesc
*
Digital,LogicF,1,T1:L14HA ,HP Speed - Accelerating speed
Digital,LogicF,1,T1:L14HM ,HP Speed - Minimum Firing Spd
Digital,LogicF,1,T1:L14HR ,HP Speed - Zero Speed
*
@endsection
UNITDATA.DAT
LONGNAME.DAT
Scale Code File (ENGLISH.SCA or METRIC.SCA)
UNITDATA.DAT
Data dictionary files contain information about unit-specific control signal database
pointnames, alarm text messages (for both process and diagnostic alarms), and
display information for signal pointnames (type/units, messages, so on).
The primary unit Data Dictionary file, UNITDATA.DAT, can be created in the unitspecific directory, F:\Unitn. Assignment files and template files are used in the
creation of UNITDATA.DAT. Many of the 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. The common, fixed pointnames are contained in template files. The
fixed control signal database points, 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.
UNITDATA.DAT is created by the program DDLOCATE. This program uses the
assignments files which are specified at the time DDLOCATE is executed in
addition to three template files in the unit-specific HMI 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 subdirectory are used to create the unit-specific UNITDATA.DAT file. The commandline format for executing DDLOCATE is:
ALARM.DAT Process and Diagnostic Alarm messages (This file can be defined
as generic Max-cased)
The following unit-specific Data Dictionary files are optional and not required for
proper operation of a HMI:
If you need point names that are compatible with all Mark V tools, limit the
point name to 12 characters. If you don't have that restriction they can be up to
31 characters. All subsystems can handle point names that begin with a letter
and contain only numbers, letters, and underscores. Some subsystems have
problems if you get fancier than that - verify your requirments before proceeding
too far.
The offset for each point must not overlap the previous point. Logic points take
up one byte, so their offsets can be one higher than the previous entry. Other
point types must have offsets that increase by the byte size of the data. For
example: If you add a REAL point at offset 0x0004 the next point's offset must
be 0x0008 or higher. No two points can have the same offset, and offsets can
not overlap.
By convention, logic points are given offsets of from 0x0000 to 0x0FFF, and all
other points start at offset 0x1000 and go up from there. This is a convention,
not a requirement. Gaps in memory offsets do not cause problems, but do not
allow any overlaps.
Unit name: The Unit name shown in the UNITDATA.DAT file is ignored, but
should be present to pass the syntax and validity checks. All unit names are now
obtained from the F:\CONFIG.DAT file, allowing the cloning of
UNITDATA.DAT files across identical units with no modifications required.
Name: This is the point name, and must be unique for each point. Point names
are not case sensitive, but typically are entered in upper case for readability.
Point Number: This is a unique number for each point, typically assigned
starting at one (1) and going up by one for each point. It should be unique for
each point, but it is not used in the HMI. (The point number field should be
unique for each point, but is currently not used by any subsystem. (The original
purpose of this field was to allow a point to change any of its attributes,
including the point name and memory location, but preserve this point number
so that it can be identified in long term collections, such as historical databases.
This feature is not used with the OSI PI or GE FANUC iHistorian products.)
Point Type: This must define the binary representation of the point value in the
Data Dictionary. It should be a value as defined in the Point Type table.
Scale Code Type: This is the index into the Scale Code file to define the
conversion of the raw value to one or more sets of engineering units.
Note Be aware that the scale code used for a value (such as temperature) must be
separate from the scale code used for a difference in values (such as a delta
temperature). This is required to support the ability to switch scale code sets. Using
temperature as an example, when switching from English to Metric, the absolute
temperatures will need a gain and an offset, but the difference in temperatures will
only require the gain, not an offset.
Plotting Limits Type: The default Plotting Limits and High/low limits values
should be zero. These are indexes into files similar to the Scale Code file that
define the default plotting limits and alarm (control of presentation color) limits
for points. Since moving to CIMPLICITY and PI for displays these fields have
been unused.
High/low Limits Type: This field is no longer used and should be set to zero
(0).
Flags (Hex): The flags field is used to indicate items such as whether this came
from a <Q> or <B> processor, whether this is an alarm, whether this is a
command signal, and whether this is a voted signal. For non-turbine control
units (such as external sources of data) this field is set to zero (0).
Memory Offset (Hex): This is the memory offset for this particular point. This
must be unique and non-overlapping any other signal. By convention logic
points are assigned individual addresses from 0x0000 to 0x0FFF, and other
signals are started at 0x1000 and go up from there.
LONGNAME.DAT
The LONGNAME.DAT file defines optional descriptions for each signal. There is
no problem if the file is set up as max-case to include long names for signals that
are not used or defined. When TCI is loading the Data Dictionary it will lookup the
long names for points found in UNITDATA.DAT file, ignoring entries that are not
used. This file uses a simple format with two columns:
Point Name: This is the name of the point, as defined in the UNITDATA.DAT
file.
Description: This it the text description for the point. Most applications can
handle up to 50 characters for this description, the field can actually handle up to
80.
#scale_data: This is a constant string that indicates that this line contains a scale
code definition.
Scale Code Number: This is an integer that defines the scale code number.
This number must match the Scale Code nubmer defined in the
UNITDATA.DAT file for a point. By convention scale code number zero (0) is
used for logic points, with the rest of the scale codes starting at one (1) and
incrementing by one.
Parameter 1 - Gain: This is typically the gain used in the raw value to
engineering units conversion.
Parameter 2 - Offset: This is typically the offset used in the raw value to
engineering units conversion.
Precision: This defines the number of places after the decimal point to show for
points using this scale code.
Engineering Units String: This is a string of up to six (6) characters that define
the resulting engineering units. This can include imbedded spaces, but their use
is discouraged as it can cause issues with application programs that use these
strings.
Scale Code Name: This is a single word of up to five (5) characters that is used
by some tools as a method to specify the scale code using something other than
its scale code number. This has the advantage that from site-to-site these names
can be made standard even if the scale code numbers change.
The following table defines the point type, the point type value used in the
UNITDATA.DAT file, the binary format, and the algorithm to convert the binary
into an engineering units value. The Gain and Offset used are the Gain and Offset
from the scale code file for the scale code number assigned to the point.
Name
L1
Type
1
F2
R4
C1
C2
C3
C4
S1
S2
T1
T2
T3
T4
H1
10
11
12
13
14
H2
15
H3
16
H4
17
X2
18
F4
19
Description
Logic Point
Format: 1 byte value, bit 0 is the current state, bit 1 is true if forced
Conversion: Value is the value of bit 0, some applications show forcing
Fixed Point
Format: 2 byte signed integer
Conversion: Engineering = (Raw / 32768) * Gain + Offset
IEEE Floating Point Real
Format: 4 byte IEEE Floating Point (23 bit fraction, 8 bit exponent)
Conversion: Engineering = Raw * Gain + Offset
Counter
Format: 1 byte unsigned integer
Conversion: Engineering = Raw * Gain
Counter
Format: 2 byte unsigned integer
Conversion: Engineering = Raw * Gain
Counter
Format: 3 byte unsigned integer
Conversion: Engineering = Raw * Gain
Counter
Format: 4 byte unsigned integer
Conversion: Engineering = Raw * Gain
Enumerated State
Format: 1 byte unsigned integer
Conversion: Used as index into array of enumerated strings
Enumerated State
Format: 2 byte unsigned integer
Conversion: Used as index into array of enumerated strings
Timer
Format: 1,2,3,4 byte timer
Conversion: <No generic conversion, special Mark IV applications only>
HEX
Format: 1 byte unsigned value
Conversion: None, always displayed in HEX
HEX
Format: 2 byte unsigned value
Conversion: None, always displayed in HEX
HEX
Format: 3 byte unsigned value
Conversion: None, always displayed in HEX
HEX
Format: 4 byte unsigned value
Conversion: None, always displayed in HEX
Extended Value
Format: 2 byte unsigned integer, the LSW of a 32 bit counter
Always paired with an F2 used as the MSW of a 32 bit counter
Fixed Point
Format: 4 byte signed integer
Conversion: Engineering = (Raw / 2147483648) * Gain + Offset
Note In the IDP and OSM 2.x software, Counters (C1-C4) were presented with no
conversion. The conversion according to the GAIN was added in TCI and OSM 3.x
for Mark V LM which stored 1/10 of an hour counters as native C4 points requiring
a gain of 0.1 for display.
;
; NOTE: MARK V LM control panels always have UTC as their timebase.
; This is not changeable. <I> 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 data file.
;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;
; MSP_TSET <NetworkNumber> <mode> <delay n> <period n>
;
; defines time synchronization on MSP enabled networks
; including CSF and Serial MA/MSP networks)
; where <NetworkNumber> ranges from 1 to the number
; of networks supported
; where <mode> is"MASTER" to indicate that MSP_TSET will
; become the timeset
; master of network number <NetworkNumber> and will send messages
; every four seconds (or as specified) via broadcast. MSP_TSET
; will delay initial operation by dd seconds if dd is specified
; with a "DELAY dd" entry. No check will be made to see if other
; timeset masters are active. No more than one HMI or Historian
; should use "MASTER" mode!
;
; "BACKUP" to indicate that MSP_TSET will become the timeset master
; of network number <NetworkNumber> whenever it detects no other
; timeset messages on network <NetworkNumber> for a period of
; dd seconds where dd is specified in the "DELAY dd" entry later
; on the same line. In this case, it will begin
; timeset operations as
; in the "MASTER" case until such time as messages from another
; time source are detected. "BACKUP" mode is not used for serial
; links.
;
; "NONE" to indicate that MSP_TSET will never become timeset
; master of network number <NetworkNumber>. This option applies
; to any unspecified network. Using mode none is equivalent to
; no MSP_TSET entry at all.
;
; "" to default to the mode. If the mode entry is blank or left
; out, MSP_TSET will assume:
; i. "MASTER" in the case of a serial network, or
; ii. "BACKUP", in the case of a CSF network.
; Defaulting the mode IS recommended and allows several GE HMIs or
; Historians to have identical configuration files (F:\TIMESYNC.DAT)
;
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.
;
; 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
;
TPRO-PC
IRIG-B (Modulated only)
;
NASA-36 (Modulated only)
;
1PPS
(Requires -m option on board)
;
1PPM and 1PPH
;
FLYWHEEL
;
PC-SG2
IRIG-A (Modulated and DC Level Shifted)
;
IRIG-B (Modulated and DC Level Shifted)
;
1PPM and 1PPH
;
FLYWHEEL
;
ISA-SYNCCLOCK16 IRIG-A (Modulated only)
;
IRIG-B (Modulated only)
;
NASA-36 (Modulated only)
;
1PPS, 1PPM, and 1PPH
;
FLYWHEEL
;
TIMESYNC BC620AT
MODE IRIG-B
;
; -------------------------------------------------------------------
Create a data dictionary in F:\UNITn to hold the point values in the HMI. Refer
to the Creating a Data Dictionary section for more information.
The Mark IV PROM list and the HMI PDDump.dat list should match so the correct
data is displayed on the HMI. Sample F:\UNITn\PDDump.dat file:
;
GE Software
;
Mark IV Predefined Data Dump Interface
;
; The Mark IV Predefined Data Dump Program, PDDump, is a program that receives
; ASCII data over an RS232-C input port on a GE HMI processor, checks the
; received data, and then stores the data into the data dictionary.
; channel number_of_bytes DDname
;MDATA
1
6
TIME
;time
; 4
1
4
TIMR_01
;Total fired hours
; 10
1
4
TIMR_02
;Peak fired hours
; 14
1
4
TIMR_03
;Gas fuel fired hours
; 18
1
4
TIMR_04
;Liquid fuel fired hours ; 22
1
4
CNTR_01
;Manual initiated starts ; 26
1
4
CNTR_02
;Total starts
; 30
1
4
CNTR_03
;Fast load starts
; 34
1
4
CNTR_04
;Fired starts
; 38
1
4
CNTR_05
;Trips
; 42
; IDATA
1
2
TTXD1_1
; 46
1
2
TTXD1_2
; 48
:
:
:
:
:
:
1
2
DDUMP9
; 210
1
2
DDUMP10
; 212
; LDATA points
1
BIT
L30D_SD
; 214/0
1
BIT
L30D_SU
; 214/1
:
:
:
:
:
:
1
BIT
LDDUMP25
; 224/6
1
BIT
LDDUMP26
; 224/7
; Alarms
1
BIT
L30A0
; 225/0
1
BIT
L30A1
; 225/1
:
:
:
:
:
:
1
BIT
L30A254
; 256/6
1
BIT
L30A255
; 256/7
A 4-byte header. *
A 2-byte checksum***
All data within the packet is byte-stuffed, if necessary, to maintain data transparency.
The purpose of byte-stuffing data bytes is to ensure that the message header is
always a recognizable entity. Byte stuffing is used whenever a byte within the packet
is equal to the FLAG character (0xAA). Any occurrence of 0xAA within the packet
is transmitted as a double occurrence (that is byte stuffed): This is 0xAA followed by
0xAA.
The header is nominally 3 bytes:
** - The data bytes are transmitted as-is (binary) except that any occurrence of 0xAA
within the data stream is transmitted as 0xAA followed by 0xAA. This increases the
actual number of transmitted bytes, but the logical number of data bytes is still equal
to the BYTECOUNT specified in the header.
*** - The 2-byte checksum is the 16-bit sum of all non-stuffed bytes from
CHANNEL, SEQUENCE, BYTECOUNT values and all data bytes. It excludes the
initial FLAG character. The packet trailer (checksum) is the least significant byte of
the checksum followed by the most significant byte. If the least significant byte of
the checksum is 0xAA, then it will be transmitted as 0xAA followed by 0xAA. Note
that it is neither necessary nor done to byte-stuff the most significant byte of the
checksum. After the most significant byte of the checksum is transmitted, the
receiver will search for a new header. Any number of 0xAA (FLAG) characters
could be transmitted between data packets with no confusion on the part of the data
receiver, although this is not done in practice.
Each channel is normally transmitted once per second. PDXMIT will allow slower
rates to be optionally specified.
Program Operation
The PDXMIT program is part of TCI and automatically starts and stops with TCI.
PDXMIT logs configuration errors into an output file (G:\LOG\PDXMIT.LOG). If
any configuration or hardware errors are encountered, one or more entries are made
into the log file, and then PDXMIT terminates.
To configure the HMI to transmit a predefined data dump:
1
The Mark IV PROM list and the HMI PDxmit.dat list must match if you require the
exact same message from the HMI as was transmitted by the Mark IV. PDXMIT will
also flag with errors any lines with the following problems:
L1
;
;
;
;
;
;
F2
;
;
;
;
;
;
;
;
;
;
C4
;
;
T4
;
;
;
;
;
;----------------------------------------------------------------------------;
; Conflicts in message definitions (overlapping of data)
; or definitions beyond
; the @END definition will be flagged as errors.
;
;----------------------------------------------------------------------------;
;
================================================
;
CHANNEL #1 DEFINTIONS
;
================================================
[Channel 1]
; Channel 1 of 2
@LENGTH = 252
@PERIOD = 1
;
-----------------------------------------------;
MISCELLANEOUS POINTS
;
-----------------------------------------------0
@TIME
6
T4
TFT_T
; "Total fired time"
- TIMR-01
10
T4
TFT_L
; "Total fired time on Liquid"
- TIMR-02
14
C4
TCMIS
; "Manually initiated starts
- CNTR-01
count"
18
C4
TCTS
; "Total starts count"
- CNTR-02
22
C4
TCFLS
; "Fast load starts count"
- CNTR-03
26
C4
TCFS
; "Fired starts count"
- CNTR-04
30
C4
TCES
; "Emergency trips count"
- CNTR-05
;
-----------------------------------------------;
INTEGER POINTS
;
-----------------------------------------------34
F2
TTXD1_1
-2048
+2048
; "Exhaust Thermocouple 1-Compensated"
36
F2
TTXD1_2
-2048
+2048
; "Exhaust Thermocouple 2- Compensated"
:
:
:
:
:
:
78
F2
TTXD1_23
-2048
+2048
; "Exhaust Thermocouple 23 - Compensated"
80
F2
TTXD1_24
-2048
+2048
; "Exhaust Thermocouple 24 - Compensated"
82
F2
TTXM
-2048
+2048
; "Exhaust Temp Median Corrected By
Average"
84
F2
CTIF1A
-2048
+2048
; "Compressor Inlet Thermocouple 1A"
:
:
:
:
:
:
122
F2
TTXSPL
-2048
+2048
; "Combustion Monitor Allowable Spread"
124
F2
TTXSP1
-2048
+2048
; "Combustion Monitor Actual Spread 1"
:
:
206
208
;
;
;
;
; 210.0
; 210.1
:
:
212.6
212.7
:
:
; 219.7
;
;
;
;
;220
;220.1
:
:
:
:
F2
SFL1
-62.50 +62.50
; "Bus PT Frequency"
F2
DVAR
-204.8 +204.8
; "Generator VARS"
-----------------------------------------------LOGIC POINTS
-----------------------------------------------L1
L1
:
:
L1
L1
:
:
L1
L30D_SD
L30D_SU
:
:
L30D_CD
L30D_CDC
:
:
L20WN1X
-----------------------------------------------ANNUNCIATOR ALARMS
-----------------------------------------------L1
L30A0
; TURBINE BEARING DRAIN TEMPERATURE HIGH
L1
L52QA1_ALM
; AUX LUBE OIL PUMP MOTOR RUNNING
;251.5
L1
LCPD_SENSR
; COMPRESSOR DISCH XDUCER DIFF FAULT HIGH
L1
; SPARE
;*SPARE* 251.6
;*SPARE* 251.7
L1
; SPARE
;
;
================================================
;
CHANNEL #2 DEFINTIONS
;
================================================
[Channel 2]
; Channel 2 of 2
@LENGTH = 146
@PERIOD = 1
;
-----------------------------------------------;
MISCELLANEOUS POINTS
;
-----------------------------------------------0
;
;
;
; 6
; 8
:
:
; 74
; 76
@TIME
-----------------------------------------------INTEGER POINTS
-----------------------------------------------F2
WXJ
-4
+4
; "Ratio of Actual Fuel to NOx Water
Flow"
F2
WXC
-4
+4
; "Ratio of Required Fuel to NOx Water
Flow"
:
:
:
:
F2
FPRG
-2048
+2048 ;*"Gas Ratio Valve Control Pressure Ref"
[oldname: FPRG1, newname: FPRG]
F2
SVLX
-18
+18
;*"System Bus Voltage - Scaled to KV"
[oldname: VOLTS, newname: SVLX]
-----------------------------------------------INTEGER POINTS - DDUMP1 through DDUMP30
------------------------------------------------
;
;
;
;
; Space left for spare points.
; Offsets 84 [DDUMP4] through 136 [DDUMP30].
; [Offsets 84 - 137 inclusive]
;
78
F2
H2GP
-2048
+2048 ; "Hydrogen Gas Pressure"
; 80
F2
TBCT
-2048
+2048 ; "Turbine Compartment Temperature"
; 82
F2
LDCT
-2048
+2048 ; "Load Compartment Temperature"
;
-----------------------------------------------;
LOGIC POINTS
;
-----------------------------------------------138.0
L1
L52QS
; "Generator Auxiliary Seal Oil Pump Motor Running"
;138.1
L1
L4FDLD
; "Master Relay for 88FD1&2"
:
:
:
:
:
:
;142.6
L1
L41AUX
; "Generator Field Breaker ON"
;142.7
L1
L43SR
; "Local Select Manual Voltage Regulator"
;
-----------------------------------------------;
LOGIC POINTS - LDUMP4 through LDUMP11
;
-----------------------------------------------;
;
;
Space Left for spare logics. Offsets 143.0 - 143.7
;
;
-----------------------------------------------;
LOGIC POINTS - LDUMP12 through LDUMP19
;
-----------------------------------------------;
;
Space Left for spare logics. Offsets 144.0 - 144.7
;
;
-----------------------------------------------;
LOGIC POINTS - LDUMP20 through LDUMP27
;
-----------------------------------------------;
;
Space Left for spare logics. Offsets 145.0 - 145.7
;
NTP Client
HMI Server No. 2
NTP Client
HMI/Historian
Viewer(Client)
Time
Server
Satellite Receiver
UTC (IRIG-B)
or GPS
Mark VI
Turbine
Control
Mark IV
Turbine
Control
Mark V
Turbine
Control
I/O
I/O
I/O
I/O
NTP Client
NTP Client
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 highresolution time card, the Time Server, or they use one HMIs low-resolution system
time to feed the other HMIs.
LOCAL_TIMESET
[ENABLED | DISABLED]
I_TIME
[LOCAL
| UTC]
MARKV_TIME
[LOCAL
| UTC]
TIME_SOURCE
[LOCAL
| UTC]
TIME_LOAD
[MANUAL
| LOCAL |NETWORK]
TZ= is used to define the rules on daylight savings to standard time transitions.
<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:
;
;
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
TIME_OFFSET
-----------UTC---------07-APR-1991 08:00:00.000
27-OCT-1991 07:00:00.000
05-APR-1992 08:00:00.000
25-OCT-1992 07:00:00.000
04-APR-1993 08:00:00.000
31-OCT-1993 07:00:00.000
03-APR-1994 08:00:00.000
30-OCT-1994 07:00:00.000
02-APR-1995 08:00:00.000
29-OCT-1995 07:00:00.000
07-APR-1996 08:00:00.000
27-OCT-1996 07:00:00.000
06-APR-1997 08:00:00.000
26-OCT-1997 07:00:00.000
05-APR-1998 08:00:00.000
25-OCT-1998 07:00:00.000
04-APR-1999 08:00:00.000
31-OCT-1999 07:00:00.000
02-APR-2000 08:00:00.000
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
Note The resulting TIMEZONE.DAT file can require editing if local laws change
the actual transition times normally used by a given locale.
Mark V
Mark VI
The Mark VI Start menu is rebuilt by clicking on the menu icon.
Rebuild Start
Menu
port specifies the name of the RS-232C port where data is received. Do not
follow the port name with a colon. This entry is required.
unit specifies the unit name where data is to be written using analog setpoints.
The unit name is a maximum length of two characters. Specify the unit desired
for the possible units supported. File F:\CONFIG.DAT specifies the unit
names; Refer to the UNIT_DATA section. This entry is required.
baud specifies the baud rate desired. Specify this as a whole number, using any
of the standard computer baud rates supported. Do not use the letter K to denote
a thousand. This entry is required.
parity specifies the parity used. Specify 0 when no parity bit is used, specify 1
when odd parity is used, specify 2 when even parity is used, specify 3 when
mark (always 1) parity is used, and specify 4 when space (always 0) parity is
used. This entry is required.
databits specifies the number of bits per character. Specify a number between
5 and 8 inclusive. This entry is required.
stopbits specifies the number of stop bits used. Specify 0 to use 1 stop bit,
specify 1 to use 1.5 stop bits, and specify 2 to use 2 stop bits. This entry is
required.
trailer specifies the number of characters to follow the ASCII data stream.
Specify 1 if just a linefeed terminates. Specify 2 if a carriage return linefeed pair
terminate.
port_tt specifies a total record timeout. This number represents the maximum
time in ms between the first character and the final end of record character
(linefeed). If this time is exceeded, a message in progress times out and is
ignored. Port_tt defaults to 200. This does not affect timing before the first
character.
EFF_2
0 ;
PCT
HCPPM
CO2DRY
O2DRY
NOXRAW
UHCRAW
NOPPM
NOXPPM
1
1
1
1
1
1
1
0
0
0
0
0
0
0
PPM
PCT
PCT
PPM
PPM
PPM
PPM
;
;
;
;
;
;
;
CO @ 15%O2
COMBUSTOR
COMBUSTOR
UHC @15%O2
CO2
O2
NOX
UHC
NO @15%O2
NOX @15%O2
In the EM_ANA.DAT file, a list of points follows, one per line, with each pointname
optionally followed by a gain and offset. The gain and offset, if omitted, default to
1.0 and 0.0 respectively. Up to 15 points may be listed. Each point is set to the
proper value using an analog setpoint command; therefore each point specified must
be enabled for analog setpoint control.
If the 91-character burst (see note 5) is received without error, data is copied to
the 10 data points.
If no good data is received within seven seconds, data with value -9999.9 is
copied to the 10 data points.
If other than 10 points are configured, then the burst of ASCII characters
received from the EM_ANA program is other than 92 characters. The exact
count is calculated as n*9 + trailer where n is the number of points configured
and trailer is specified in the data file.
Program considerations
The program normally resides at G:\EXEC\EM_ANA.EXE. The program is
automatically run when the HMI software is started. As a debugging tool, a global
section trace buffer can be viewed with the command:
gbl2file em_ana_trace <some_file_name>
This creates a file with a snapshot of the operating condition of the program and
error conditions. Error message and time stamped data streams are placed in this
global section trace.
If the program encounters an error or terminates early due to a serious error in the
data file, an error message is placed in the global section. In addition, a log file
describing the problem is placed in the G:\LOG\Em_Ana.log file.
Performance Monitor
The EfficiencyMap v. 7.0 Performance Monitoring Software is an HMI option
to calculate and display turbine power and efficiency. Efficiency is defined as fuel
consumption per unit power production.
Power plant performance monitoring is defined here as a process to continuously
evaluate the power generation capacity and efficiency of plant equipment.
EfficiencyMap continuously calculates a gas turbines performance defined by its
current capacity and efficiency. It then calculates the performance change relative to
a defined reference point or benchmark that defines good performance.
The performance monitor can take its input from Mark V or Mark VI controllers.
Using EMapView
EMapView provides an interface to the EfficiencyMap inputs and calculated
results. The plants current performance can be evaluated using the report screens.
The main EmapView display shows three reports configured for this application
(Performance Report, Status Report and Equipment Status Indicators). On the left is
an explorer window similar to the Microsoft Windows Explorer, used to open
various reports. This is the same design as used within. Reports are loaded by double
clicking on the name on the explorer window. Reports can be dragged-and-dropped
into new locations in the tree structure and can be renamed by highlighting the report
name first, then single clicking on the name.
; Example:
; OILFUEL_GT1_TEMP = "59", 2048, 0, "deg F", "Oil fuel temperature"
; Extra white space can be included between parameters to aid in the
; reading of this file. The programs that read this file ignore any
; whitespace within a line that is not inside quotation marks.
;
; Example:
;
; GT1_CPD=CPD,2048,0,"psi (gage),"Compressor discharge pressure"
; GT1_CDT=CTDA1,2048,0,"deg F","Compressor discharge temperature"
;
; or
;
; GT1_CPD = CPD, 2048, 0, "psi", "Compressor discharge pressure"
; GT1_CDT = CTDA1, 2048, 0, "deg F", "Compressor discharge temperature"
;
;
; ***** NOTE: This section starts the data definition area *****
; ***** Required 'Critical' Inputs *****
;
[Inputs]
PLANT_PAMB =AFPAP, 512,0, "In Hga", "Ambient pressure"
GT1_CDP =CPD, 2048,0, "psig", "Compressor discharge pressure"
GT1_IGV =CSGV, 128,0, "DGA", "Inlet Guide vane angle"
GT1_CDT1 =CTDA1, 2048,0, "deg F", "Compressor discharge temperature"
INLET1_GT1_TEMP1 =CTIF1A, 2048,0, "deg F", "Compressor inlet temperature"
GT1_PWRGRS =DWATT1, 512,0, "MW", "Gas Turbine gross power"
GT1_OUTLET1_TEMP =TTXM, 2048,0, "deg F", "Gas turbine exhaust temperature"
GT1_OUTLET1_TEMP_REF =TTRXP, 2048,0, "deg F", "Primary exhaust temperature control
reference"
;
; Select fuel to be used
;
NGFUEL_GT1_FLOW =FQG1, 64,0, "#/sec", "Natural gas fuel flow"
;OILFUEL_GT1_FLOW =FQLM1, 64,0, "#/sec", "Oil fuel flow"
;
; ***** Select 'Optional' Inputs *****
;
PLANT_SHAMB =CMHUM, 128,0, "%", "Inlet specific humidity"
GT1_INDP =AFPCS, 512,0, "In H2Og", "Inlet pressure drop"
GT1_OUTDP =AFPEP, 512,0, "In H2Og", "Outlet pressure drop"
GT1_CDT2 =CTDA2, 2048,0, "deg F", "Compressor discharge temperature"
GT1_CDT3 =CTD, 2048,0, "deg F", "Max compressor discharge temperature"
INLET1_GT1_TEMP2 =CTIF1B, 2048,0, "deg F", "Compressor inlet temperature"
INLET1_GT1_TEMP3 =CTIM, 2048,0, "deg F", "Max compressor inlet temperature"
NGFUEL_GT1_TEMP =FTG, 2048,0, "deg F", "Natural gas fuel temperature"
NGFUEL_GT1_LHV =KFG_LHV, 2048,0, "MBtu/klb","Natural gas Lower Heating Value"
;OILFUEL_GT1_TEMP =????, 2048,0, "deg F", "Oil fuel temperature"
;OILFUEL_GT1_LHV =????, 2048,0, "MBtu/klb","Oil fuel Lower Heating Value"
;H2ONOX_GT1_FLOW =WQJ, 2048,0, "#/sec", "Water/steam injection
;flow for Nox control"
;H2ONOX_GT1_TEMP =STSJ, 2048,0, "deg F", "Water/steam injection
;temperature for Nox control"
;H2ONOX_GT1_PRES =SPSJ, 2048,0, "psig", "Water/steam injection
;pressure for Nox control"
;H2OAUG_GT1_FLOW =WQJA, 2048,0, "#/sec", "Water/steam injection
;flow for power augmentation"
;H2OAUG_GT1_TEMP =STAJ, 2048,0, "deg F", "Water/steam injection
;temperature for power augmentation"
;H2OAUG_GT1_PRES =SPAJ, 2048,0, "psig", "Water/steam injection
;pressure for power augmentation"
;
in the EMap data files and monitor the program functions. NetMeeting is provided
on the HMI for this purpose. It is not necessary (or desirable) to have this program
running continuously, nor to have a phone line connected to the HMI continuously.
Special arrangements can be made with GE to coordinate their phone access to the
HMI.
A Windows printer must be named Alarm Printer using the Print Manager. This
printer receives all the alarm and event log messages. The printer should
generally be associated with a line-printing device such as a dot matrix printer
rather than a page printing device such as a laser printer. This allows the alarm
and event records to be examined as they are received and printed out.
The alarm and event logging printer must be configured with a small font to
allow printing alarm and event messages on a single line. Alarm messages can
be up to 90 characters wide, event messages up to 140 characters wide. A font
pitch of 15 characters per inch on 8.5 inch wide paper allows all alarm messages
to be printed on a single line, and all but the widest event messages to be printed
on a single line. This should be configured as the default font size on the printer.
Once these two items are done, the Alarm and Event Logger logs alarm and event
messages to the Alarm Printer as they are received, as filtered by the Logger
Control dialog box.
CIMPLICITY
System
dot-martix printer
Share Name:
alarmpri
BOP, PLC
Right click on the printer named Alarm Printer and select Properties.
Alarm History
Mark IV, Mark V, Mark V LM, and Mark VI
The TCI Historical Alarm subsystem has the ability to save alarms to the TCI
Historical data directory as they are received. A Web-based query can be used to
retrieve the information. The alarms display in the Web browser, which should have
a Print option. The Print option is the standard Windows Print; it can print to any
print queue on any computer connected to the network. Often a site has one laser
printer connected to a single HMI, and all other printouts are directed to this printer.
The Web-based reports all ask the user for the units desired, then print the alarms in
order of occurrence for the list of units selected. If all plant alarms are wanted, select
all units, and if only one unit's alarms are wanted, select and print one unit at a time.
Use the Back button in the browser to select a different unit or set of units.
Alarm Collection. Alarm collection is a new function under TCI 1.5. To enable
alarm history, add the following entry to the F:\CONFIG.DAT file under the
Options section:
ALARM_HISTORY=YES
To specify the location of the TCI Historical data directory location for the history
files, add the following entry to the F:\CONFIG.DAT file under the Options
section:
HST_DIR=C:\HMIDATA
If this entry is not present, the default of C:\HMIDATA is used. Make sure that the
specified directory exists otherwise data will not be saved.
Alarms, Events, and SOEs are collected by default. The following displays how to
modify the options section of F:\CONFIG.DAT to change the default
configuration:
Disk Manager
This disk space used for historical storage is limited to prevent filling up the hard
drive. There are two criteria used to remove files, age and space. The age is always
limited to the last 30 days; files older than this will automatically be removed.
Prior to TCI V03.04.02 the space used was limited to no more than 10 MB. TCI
V03.04.02 added the ability to change the amount of space used to allow for storing
either more or less information as desired.
This will only trim files in the TCI Historical Data directory. Other subsystems, such
as the Mark VI Trip Logs from Data Historian, have their own methods for purging
their historical files.
The settings are made in the F:\CONFIG.DAT files OPTIONS section. The
settings are:
Trim files to provide this much free disk space (MB). Default value displayed:
DSKMGR_FreeSpaceMB = 250
Do not use more than this amount of disk space (MB). Default value displayed:
DSKMGR_MaxUsedMB
= 150
Do not trim files to below this amount of disk space (MB). Default value
displayed:
DSKMGR_MinUsedMB
10
If only MinUsed is supplied but it is larger than the default MaxUsed then
increase MaxUsed to match the user supplied MinUsed.
If only MaxUsed is supplied but it is smaller than the default MinUsed then
decrease MinUsed to match the user supplied MaxUsed.
If both MinUsed and MaxUsed are supplied but MinUsed is larger than
MaxUsed then increase MaxUsed to match MinUsed. (In case of conflicting
information opt to save the data instead of throw it away.)
Decide which control ports can send commands to the unit while it is in each
control location.
Decide which ports are allowed to change the control location, based on the
current control location.
Step 3 - Decide which ports are allowed to change the control location,
based on the current control location.
The next major decision is what control ports are allowed to change the control
location from one value to another. This is done dependent upon the current control
location. A useful philosophy is that any control port that is closer to the turbine can
take control if desired. This means that an HMI can take control away from a
Modbus link, or an Ethernet link, and the BOI can take control away from any
location.
When changing control, control is taken, not given away. This prevents the control
being turned over to another location that is unaware that it is expected to take
control.
Step 4 - Create the HMI file F:\CTRL_LOC.DAT according to the
decisions made in steps 1, 2, and 3.
Once the decisions are made on how the Control Hierarchy is to be implemented, the
actual implementation is done by creating a file on each HMI. The file is the
F:\CTRL_LOC.DAT file that is an ASCII text file that can be edited using the
standard text editor.
This data file defines a COMMAND table that indicates what control ports are
allowed to forward commands and alarm commands to the unit based upon the unit's
current control location. This table will be different for HMI processors at different
levels. For example, the local HMI has the table filled in differently than the remote
HMI.
The data file also defines a TRANSFER table that indicates what control ports are
allowed to change the current control location based upon the unit's current control
location. This table is also different for HMI processors at different levels. If desired,
the LOCKOUT signal and the one command that can be passed when the lockout
signal is TRUE can be defined.
Step 5 - (Optional) Modify the HMI configuration to define an
enumerated state table, which defines the control locations.
The HMI processor uses a special signal in the Mark V control panel to hold the
control location. The point used has the pointname of I_C_CTRL_1. This signal
defaults to an analog signal scaled with a scale type of CNT15. When displayed, it is
shown as an integer.
Many sites prefer to change this point from an integer to an enumerated state point.
This allows the displays to show the control locations as:
"UNASSIGNED" - "BOI" - "LOCAL" - "DCS" - REMOTE"
instead of simply 0 - 1 - 2 - 3 - 4.
This can be done by editing the ENUMDATA.DAT file for the unit to define a new
enumerated type that contains the strings for the control locations. Once this table
has been defined the I_C_CTRL_1 signal can have its scale type changed from
CNT15 to ENMnn, where nn is the number of the newly created control locations
enumerated table. Once this is done, the displays show the control location using the
enumerated string, not the integer value.
If your site is using synonyms, you can also edit the SYNONYM.DAT file to include
a synonym for the I_C_CTRL_1 point.
Step 6 - Create the HMI displays for changing the control locations.
Any display that can send a command to the controller can have a command added to
change the control locations. Add control targets to send the I_C_CTRL_1 point the
value of the desired control location. The HMI checks the command against the
TRANSFER table before sending the command to the controller. The following is a
sample CTRL_LOC.DAT file:
;
; CTRL_LOC.DAT
;
; This file defines the parameters required to
; implement Control Hierarchy
; for the Mark V.
;
; ***********************************************************************
; The default CTRL_LOC.DAT file is defined by GE Energy Standards, it
; may be necessary to modify this file for a
; specific site or customer
; application. Please feel free to do so. However, if the file is
; altered from this standard it may be necessary
; to investigate changing
; the sequencing to correspond.
; ***********************************************************************
;
;--------UNIT Definition Section--------------------------------------;
; The UNIT section defines which units the tables
; are being defined for.
; At some sites all units will share the same tables,
; and at other sites
; there may be different tables for each unit.
;
; The unit section is the keyword UNIT followed
; by the unit NAMES of the
; units that the following tables are valid for.
; All units that the <I>
; will control must be listed in this file.
; For multi-unit <I>'s where
; all units are to have the same COMMAND and
; TRANSFER tables list the units
; as follows:
;
;UNIT T1 T2 S1 ... etc
;
; If the units are to have different COMMAND and TRANSFER tables they
; must be listed separately:
;
;UNIT T1
;COMMAND ...
;TRANSFER ...
;
;UNIT T2
;COMMAND ...
;TRANSFER ...
;... etc
;
;
UNIT T1
; List of units that use the following tables.
;
;--------LOCKOUT Section---------------------------------------------;
; The (optional) LOCKOUT section is used to
; block commands if the given
; logic signal is TRUE, passing only the given command.
; Needless to say,
; the one command that is passed needs to be able
;
;----------------------------------------------------------------------;
; The above tables show the settings used for a typical local HMI.
; For the Remote HMI the following COMMAND and TRANSFER
; tables are suggested.
; This implies that the Remote HMI must take control (when a unit is
; unassigned) or be given control prior to sending commands.
; The Remote can
; set the unit to Unassigned, but can not hand control to
; the local HMI (the local HMI must take control from the remote HMI). ; ; The Remote can
turn
; control over to the DCS, or take control back from the DCS.
;
; COMMAND
; This defines the command table
;
; CONTROL
CONTROL
ALARM
;Control Location Description
; LOCATION
COMMANDS
COMMANDS
; --------------------------------------------------0
...
...
; Unassigned
1
...
...
; Backup Operator Interface Only
2
...
...
; Local HMI Control
3
...
...
;General Remote (MODBUS/Ethernet/Cable)
4
I..
I..
; Remote HMI Control
;
;TRANSFER ; This table shows what transfers of control
;location are allowed
;
; CURRENT
<---- DESIRED LOCATION ----->
; Location
0
1
2
3
4
; -----------------0
...
...
...
I..
I..
1
...
...
...
...
...
2
...
...
...
...
...
3
...
...
...
...
I..
4
I..
...
...
I..
...
;
;-----------------------------------------------------------------------
If the TCI web page is made the computers home page then requesting the home
page of the computer (or localhost if running on the HMI) will result in the TCI web
page being presented.
If the TCI web page is not used as the computers home page, a link to the TCI web
page should be added to the computers home page. Use the sample below as a
model.
<a href=/GEDS/TCI.htm>TCI Home Page</a>
Expand <computer name>(local computer) and Web Sites to get to the Default
Web Site entry. Right click on Default Web Site and chose Properties.
Default.htm appears in the list of documents, usually at the top of the list
TCI uses three virtual directories for its displays and log files. These virtual
directories should already exist, but if they do not they need to be created.
If the virtual directory already exists, check its settings by right clicking on
the virtual directory name and choosing Properties. Verify that the properties
are as displayed in Property Setting column of the table Virtual Directory
Settings.
If the virtual directory does not already exist it must be created by right
clicking on the Default Web Site and choosing New Virtual Directory. Use
the items in the Wizard Settings column to answer the wizards questions.
After the virtual directory has been created you can check the settings by
using the procedure above for when it already exists.
Virtual Directory Settings
Wizard Settings
Property Settings
Scripts
C:\InetPub\scripts
Execute
Scripts and
Executables
~tcilogs
G:\log
Read, Browse
Read, Directory
Browsing
~pclogs
C:\pclogs
Read, Browse
Read, Directory
Browsing
From the Start menu select Control Panel, Add or Remove Programs,
Add/Remove Windows Components. The Windows Components Wizard
window opens.
Select Internet Information Services (IIS), and then click the Details button.
Select World Wide Web Service, and then click the Details button.
Check both the Scripts virtual directory and World Wide Web Service
checkboxes.
Click OK to close window and return to the Internet Information Services (IIS)
window.
clear
<C> DCC
SS
List of inputs
from
EPA_B.SRC
L83WQL3N
Calculate
average of each
input every
minute based on
once per second
sampling
enable
time
clear
time
clear
Minute
Averages:
Stored in 60
point circular file
clear data
Hourly Average:
Calculated after
each 60 points
have been stored.
clear data
LWLX4MIN
enable
Hourly Alarm:
If WXC>WXJ for
hourly average
then set
LWLXHR=1
LWLXHR
enable
Processor
Output to
display:
CONFIG.DAT
If
hourly and
minute averages
EPA_LOG=YES
collect data from
<C> and enable
outputs
Output to printer:
minute average
All minute
averages from
hourly average
calculation
hourly average
enable
enable
LWLXHR
AND
IO_PORTS.DAT
Enable output to
printer assigned to
EPA$PRINT
variable
Output to printer
once an hour:
hourly average
enable
enable
Diagnostics
The HMI provides diagnostic tools for basic troubleshooting. The following basic
questions can often help in determining where to start the troubleshooting process.
Sometimes the most productive approach in debugging tells you where not to spend
your time.
Did the configuration stop functioning?
Yes: If this configuration has worked in the past, then concentrate on
communications links or device specific problems first. Do not alter the
configuration unless you know that something in the plant has changed, forcing a
change to the configuration.
No: If this configuration has never functioned, check the communications paths first,
and then start looking at the configuration settings to see if there is a mismatch
causing the problem.
Has anything been changed?
Yes: If possible, undo the change and see if the problem disappears.
No: If it is certain that nothing has changed, look outside the computer for the source
of the problem, typically communications or device errors.
Are other computers functioning correctly?
Yes: If the problem is loss of data from this computer, and all other computers are
still getting the data OK, then the problem is probably related to this computer
configuration or communication.
No: If the loss of data is across all computers, then the problem is probably in the
device itself, or in a communication link to the computer.
Overview of Approach
The Architecture overview section of this chapter provides a roadmap for following
the data flow through the system. By watching the data flow through the system, the
point at which the problem appears can be located. From this, the subsystem that
needs to be addressed to solve the problem is known.
There are essentially three major data flow operations taking place in the HMI:
The data is collected from the device by the TCI and placed in the Data
Dictionary. (Note that Mark VI data does not go through the Data Dictionary).
Data and alarms are passed from TCI to the CIMPLICITY software by CIMB.
CIMPLICITY presents the data and alarms through its own screens and sends
the data to the viewer's screens.
It is possible to debug using either a start-to-end or end-to-start data path Once the
subsystem experiencing the problem has been identified, the root cause can usually
be tracked down to the subsystem not receiving its input data, or to a configuration
error causing it to mishandle or ignore the data that it does receive.
Troubleshooting
This section defines troubleshooting details and how to use various diagnostic tools
to observe the data flow through the HMI. Most of the debugging tools are run from
a command prompt window, and are distributed in the G:\EXEC directory. That
directory should be included in the PATH statement, so simply typing the name of
the program should start the debugging program.
Error Logs
One of the first steps is to check for error log files generated by the HMI. Often these
error logs indicate the source of the problem without any further investigation. This
is typically true for configuration errors, but can also apply to communication errors.
The HMI creates its internal error logs as a set of files in the G:\LOG directory. This
should always be the first stop in troubleshooting any problem. Most programs do
not create an error log file unless they have something to report. The primary
exception to this is the TCI System Service itself, which always generates a
TCI.LOG file. To allow for getting the system running again quickly and
troubleshooting the problem afterwards, the TCI System Service generates a new
TCI.LOG when it starts, but preserves the previous version as TCI1.LOG. This
means that if the TCI System Service is restarted after a problem, the TCI.LOG file
is from the restart, and the TCI1.LOG is the one to use when troubleshooting the
problem that required the restart.
If your site uses an ARCNET (for a Stagelink interface to a Mark V or Mark V LM,
or for a CSF interface to a Mark IV) then the ARCNET device driver is used. Device
drivers log errors into the Windows error log. If an ARCNET communication
problem is suspected of causing the loss of all data from an ARCNET, make sure to
check the Windows error log for any messages from the ARCNET driver. To access
the error log, click on Start, Programs, Administrative Tools, then Event
Viewer. These messages are under the System error log. This is also the case with
the Ethernet Global Data EGD System Service used when there are Mark VI or PLC
devices that support the EGD protocol.
<global_section_name>
<filename>
Where:
<filename> is the name of the file selected to store the results. By convention,
usually a *.DMP extension is used to indicate that this is the dump of a global
section, but this is not a requirement. Some people use a *.TXT extension so
that double clicking on the file brings up Notepad.
A Web interface has been added to the global sections. This is a smart Web interface
that scans for global sections and presents a menu of the global sections found.
Clicking on the desired global section displays its contents. The results can then be
saved to a file using the normal Web browser interface, typically by clicking File,
then Save As.
To access the Web Global Section Form
1
From the preferred Web browser, access the Web HMI main menu.
The Web Global Section Form starts, providing the list of global sections found,
for example:
HMI Menu: http://192.168.1.40
Global Section Form: http://192.168.1.40/scripts/GEDS/wgblf.exe
Communication Layer
The communication layer is responsible for communicating with the device in its
native format, retrieving the required data, and entering it into either the Data
Dictionary or the EGD Global Section. To verify that this layer is working, check the
Data Dictionary or EGD Global Section for periodic updates of the point values.
(Check the EGD Global Section if the information is from an EGD based controller,
and the Data Dictionary for all others).
The diagnostic tool VIEW0 is used to watch the Data Dictionary for point updates
and report them to the screen. It is run from a command prompt window, and
watches and reports on a single point. It shows the point's timetag, value, and
engineering units. Under normal conditions, it displays the history of point reports
scrolling up through the window.
The diagnostic tool VIEWEGD is used to watch the EGD Global Section for point
updates and report them to the screen. It is run from a command prompt window, and
watches and reports on a single point. It displays the point's timetag, value, and
engineering units. Under normal conditions, it displays the history of point reports
scrolling up through the window.
VIEW0 and VIEWEGD are usually the first diagnostic tools run when tracking
down a problem because of the amount of information that they present. If the point
is not being updated, it indicates that the front-end communication system is the
source of the problem. If the point is being updated, they provide information on the
point's timetag and scaling, either of which could be causing problems in the other
subsystems.
If the data is being updated in the Data Dictionary or EGD Global Section correctly,
proper communication with the device and proper configuration of the point is
verified. Do not spend any more time looking at the communications layer.
VIEW0 and VIEWEGD display information as it enters the Data Dictionary or EGD
Global Section. Two other tools exist for watching information in the Digital
Exception Message side of the front-end programs. These programs can verify
whether alarm, event, and SOE messages are being received from the device.
Verifying that the messages are being received limits debugging to the configuration
if the messages are not making it all the way to the operator interface screens.
If the messages are being received but the data in the Data Dictionary does not match
the data in the device, then it is either a configuration error in the layout of the
message, or a problem with the scaling of the signal. The layout of the message must
be obtained from the people who did the device configuration, and this must match
the F:\UNITn\PDDUMP.DAT file.
The scaling used for each signal is determined by matching the scale code from the
unit's UNITDATA.DAT file to the unit's ENGLISH.SCA file.
Sometimes you can verify message layout problems by varying one point and
making sure that the correct point (and only that one point) changed in the Data
Dictionary. Make sure to check the signal before and after the signal of interest to
make sure that there is not a single byte offset while looking at two byte values. If
the correct signal is changing then there can be a scaling issue instead of a data
message layout issue.
The Predefined Data Dump keeps a log of the messages it receives and errors it
encounters in a global section of memory. This global section can be viewed to see
the message flow by looking at the pddump_trace<n> global section.
For new installations, if ARCWHO does not show any information about the
network, or does not show any nodes at all, then it is possible that the
configuration information that tells the computer how to talk to the ARCNET
card is incorrect. The ARCNET card used for the CSF needs to be an 18.432
MHz card (not a 20 MHz card). If in doubt, look at the markings on the crystal
on the ARCNET card to verify the crystal frequency.
The computer interfaces to the ARCNET card using a section of dual ported
memory, a set of I/O registers, and an interrupt request line (IRQ). The TCI
Control Panel Applet is used to inform the ARCNET driver how to
communicate with the card, and which type of card it is. If the card settings and
the Control Panel Applet settings disagree, the card will not function correctly.
Usually the ARCNET driver detects the problem (when it can't contact the
ARCNET card using the settings given) and logs that fact to the System section
of the Windows operating system Event Log. Look there for any ARCNET
driver error messages.
If network or node stability is in question, there is another resource that can help find
the extent of the problem, or at least when the problem occurred. The Beacon
Monitor program exchanges heartbeats with each node that is assigned to a unit, and
keeps a log of the birth and death of each node. This log of the birth and death of
each node is kept in a global section of memory, and can be viewed as the
beacon_trace global section. Each entry indicates the time, network, node, and
transition (birth, death, restart) of the node. High transition rates indicate either a
node that is restarting often, or a communication link problem.
For new installations, if ARCWHO does not show any information about the
network, or does not display any nodes at all, then it is possible that the
configuration information that tells the computer how to talk to the ARCNET
card is incorrect. The ARCNET card used for the Stagelink needs to be a 20
MHz ARCNET card (not an 18.432 MHz card). If in doubt, you can look at the
markings on the crystal on the ARCNET card to verify the crystal frequency.
The computer interfaces to the ARCNET card using a section of dual ported
memory, a set of I/O registers, and an interrupt request line (IRQ). A PCI based
ARCNET card obtains these settings directly from the Operating System, an
ISA based ARCNET card requires use of the TCI Control Panel Applet to
specify how to communicate with the card. If the card settings and the Control
Panel Applet settings disagree, the card does not function correctly. Usually the
ARCNET driver detects the problem (when it can't contact the ARCNET card
using the settings given) and logs that fact to the Windows System Event Log.
Look there for any ARCNET driver error messages.
If network or node stability is in question, there is another resource that can find the
extent of the problem, or at least when the problem occurred. The Beacon Monitor
program exchanges heartbeats with each node that is assigned to a unit, and keeps a
log of the birth and death of each node. This log of the birth and death of each node
is kept in a global section of memory, and can be viewed as the beacon_trace global
section. Each entry indicates the time, network, node, and transition (birth, death,
restart) of the node. High transition rates indicate that a node that is restarting often
or there is a communication link stability problem.
PCI ARCNET
HMIs with PCI ARCNET cards using ARCNET Driver Version 4.0 or earlier
should be updated with a later version.
To identify the HMIs ARCNET Driver Version
1
The Digital Exception Message subsystem can sometimes be used to track down
configuration problems. The Alarm Receiver program (ALMRCV.EXE) keeps track
of all Digital Exception Messages that it receives over the Ethernet. This message
history can be obtained from the global section named almrcv_enet. If this displays
reception of messages from the correct IP address, but the alarms do not display up
in the ALMDUMP1 program, then the mapping of the Ethernet IP address to the unit
number is probably incorrect. This mapping is done in the F:\ENETALM.DAT file.
Make sure that the unit number is the correct unit number, and that the
F:\CONFIG.DAT file indicates that the unit with that unit number is a Mark VI
turbine control. (If it was configured with the wrong unit type, it does not expect
messages from the Ethernet and does not forward them if they are received).
ARCWHO
Mark IV CSF, Mark V and Mark V LM
ARCWHO is a Command Line utility program that provides a list of the ARCNET
nodes present on any of the ARCNET networks. Both Stagelink and CSF networks
are ARCNET based and are included in the networks listed. 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 F:\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
ARCWHO is run from a Command Prompt window. If run with the /? parameter a
help page is displayed. If the TCI System Service is running then ARCWHO can
determine the network number and network type for each network and include that in
its report. If TCI 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 F:\CONFIG.DAT file.
MY ADDRESS:
1F
NODES FOUND: FE FC FA 1E
F:\>
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).
CHECKCRC
The HMI Product Code distribution contains many files spread out over a number of
different directories. While it is unlikely, the HMI Product Code can become
corrupted by a hard drive error, or possibly even infected by a computer virus. If this
happens, all kinds of symptoms can occur and troubleshooting these symptoms
would be very difficult.
The HMI Product Code includes a utility program for checking the validity of the
Product Code files on the disk. This check only takes a few seconds to run, and
verifies that the programs on the disk are as distributed. When the Product Code
distribution was made, a CRC (Cyclic Redundancy Check) file was created and
included in the distribution. The CHECKCRC utility reads this CRC file and reports
on any files that are missing or have been corrupted.
To run CHECKCRC
From a Command Prompt window, type:
CHECKCRC
Press Enter. The resulting report displays and a copy of the report is deposited
in the G:\LOG directory.
If a file is reported as missing or is a mismatch from the original distributed file, then
consider reinstalling the HMI Product Code distribution to repair the problem.
Note Sites that are running beta copies of the HMI Product Code should not expect
any missing or mismatched files reported, as all distributions (including beta
distributions) have valid CRC files when they ship. If code has been updated in the
field as a result of the beta test program, the updated files displays up as a mismatch.
This indicates that the system cannot be recreated by reinstalling the last beta
Product Code release. Under the beta tester software agreements, all beta code users
must update to the next official Product Code release when available.
If all files are reported to be in place and intact, then the particular version of the
HMI Product Code that is running can be found in the file
G:\DATA\VERSION.DAT. This file is included in the CRC check, so if the CRC
checks pass, this defines the version of the product code being used.
<global_section_name>
<filename>
<filename> is the name of the file selected to store the results. Usually a *.DMP
extension is used to indicate that this is a global section dump, but this is not a
requirement. Sometimes a *.TXT extension is used so that double-clicking on
the file brings up an ASCII file viewer.
Decoding the information contained in these trace global sections usually requires
knowledge of the internal workings of the program that created it. This information
is for advanced debugging, and typically the reports obtained are either obtained
directly by the factory, or are forwarded to the factory for analysis.
This example displays two statistical sections. Up to eight sections can be displayed,
one for each of the possible eight communication ports. Each section corresponds in
number to the [PDDUMP_SETUP] section number as configured in the
F:\IO_PORTS.DAT file.
VIEWn Series
VIEW* utility programs are used in troubleshooting and debugging. They display
data flowing through the system, and collects specialized data, often at very high
speeds. A few analysis tools are provided to do simple analysis of the data retrieved
or to convert the data into a format compatible with most spreadsheet programs.
There are two basic classes of VIEW* program, collection programs and analysis
programs.
VIEW0 - View One Second Data, Single Data Dictionary Point. This program
displays a single point value and time tag out of the Data Dictionary, and
updates it whenever it changes. This is often used to verify unit
communications, unit time settings, or to study a single point.
VIEW1 - View One Second Data, Set of Dictionary Points. This program
displays a set of points out of the Data Dictionary, updated once per second. One
common time tag is applied to all signals. The output is sometimes directed to a
disk file to create a simple one-second logging of a set of points for further
analysis.
VIEW2 - View High-Speed Mark V Data. This program collects a set of points
directly from a Mark V or Mark V LM controller. It can collect high-speed data
at, or even above, the controller's frame rate, time-tagged by the controller. The
results are stored in a disk file. It is often used for high-speed data analysis.
VIEWEGD - View EGD Point. This program displays a single point value and
time tag out of the EGD global section. This is often used to verify unit
communications, unit time settings, or to study a single point.
VIEWPV - View High Speed Mark V PreVote Data. This program collects
high-speed Mark V prevote data at a rate up to or above the controller's frame
rate. The results are written to a disk file for analysis.
VIEWQ - View High Speed Mark V <Q> Data. This program collects highspeed Mark V data directly from the <R>, <S>, and <T> processors. It can
collect high-speed data from the unit, at or even above the controller's frame
rate, time tagged by the unit.
Operation
VIEW0 is run from a Command Prompt window. If run with the /? parameter, a help
screen is provided. If run with no parameters, it asks for the name of the point to
monitor.
The following example displays a sample VIEW0 help screen:
F:\UNIT1>VIEW0 /?
VIEW0 is a simple console utility program to watch a point in
the Data Dictionary. If you enter a unit name and point name
on the command line it will look for that point, otherwise it
will prompt for the unit and point name.
COMMAND FORMAT:
VIEW0 [/SHOW] [un:pointname]
The /SHOW option causes the program to use the 7 character
XdShow() value instead of the default display value.
F:\UNIT1>
In the following example, the point BB1, a vibration measurement, was collected
from unit T1. It was stopped by pressing a key on the keyboard.
F:\UNIT1>VIEW0 T1:BB1
06-FEB-1998
13:55:12.187
0.28 in/s
06-FEB-1998
13:55:13.187
0.28 in/s
06-FEB-1998
13:55:14.187
0.29 in/s
06-FEB-1998
13:55:15.187
0.31 in/s
06-FEB-1998
13:55:16.187
0.32 in/s
06-FEB-1998
13:55:17.187
0.34 in/s
06-FEB-1998
13:55:18.187
0.28 in/s
06-FEB-1998
13:55:19.187
0.29 in/s
06-FEB-1998
13:55:20.187
0.31 in/s
06-FEB-1998
13:55:21.187
0.32 in/s
06-FEB-1998
13:55:22.187
0.34 in/s
06-FEB-1998
13:55:23.187
0.28 in/s
06-FEB-1998
13:55:24.187
0.29 in/s
06-FEB-1998
13:55:25.187
0.31 in/s
06-FEB-1998
13:55:26.187
0.32 in/s
06-FEB-1998
13:55:27.187
0.34 in/s
06-FEB-1998
13:55:28.187
0.29 in/s
06-FEB-1998
13:55:29.187
0.31 in/s
06-FEB-1998
13:55:30.187
0.32 in/s
06-FEB-1998
13:55:31.187
0.34 in/s
06-FEB-1998
13:55:32.187
0.28 in/s
06-FEB-1998
13:55:33.187
0.29 in/s
06-FEB-1998
13:55:34.187
0.31 in/s
F:\UNIT1>
Operation
VIEW1 is run from a Command Prompt window. If run with the /? parameter, a help
screen is provided. If run with no parameters, it asks for the name of the point to
monitor.
The following example displays a sample VIEW1 help screen:
F:\UNIT1>VIEW1 /?
VIEW1 - View a set of points from the Data Dictionary.
Command: VIEW1 [/UNIT=unitname] [@pointlist] [output]
where
/UNIT=unitname allows you to supply a default unit name,
so that only the point name must be given from the file or from
the user prompts. If UnitName:PointName is given, it will
override the default unit.
@pointlist is the name of a file that defines the list of points
to be displayed, one pointname per line. output is the name of a
file to write the results to. Hitting any key will exit the
program.
F:\UNIT1>
In the following example, the vibration measurement point BB1 was collected from
unit T1. It was stopped by pressing a key on the keyboard.
F:\UNIT1> VIEW1 /UNIT:T1
To also send output to a file, enter filename as a program
parameter.Eight points can print on the screen, up to 50 points
go into the file.
Note: Do not send more than 29 points to the file if your
analysis program
: can not handle lines longer than 256 characters.
To read point list from a file, enter @filename as a program
parameter.
Default unit is T1.
Enter pointname[1]: BB1
Enter pointname[2]: BB2
Enter pointname[3]: BB3
Enter pointname[4]: BB4
Enter pointname[5]: BB5
Enter pointname[6]: BB_MAX
Enter pointname[7]:
##
Unit
Pointname Scale
-------------- ----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
The TIME shown is the local PC time, not the unit time.
26-OCT 09:29:43
0.28
0.31
0.29
0.29
0.31
26-OCT 09:29:44
0.28
0.29
0.28
0.29
0.28
26-OCT 09:29:45
0.29
0.30
0.30
0.30
0.27
26-OCT 09:29:46
0.31
0.31
0.29
0.30
0.29
26-OCT 09:29:47
0.32
0.30
0.31
0.29
0.28
26-OCT 09:29:48
0.29
0.28
0.32
0.29
0.30
26-OCT 09:29:49
0.31
0.31
0.32
0.31
0.29
26-OCT 09:29:50
0.32
0.31
0.30
0.31
0.31
F:\UNIT1>
0.31
0.29
0.30
0.31
0.32
0.32
0.32
0.32
Operation
VIEW2 is a command line utility program that is run from a DOS window. If run
with no parameters or the /? parameter, a help screen is provided.
Note At the current time, the Mark V LM accepts its scan parameter in units of 5ms
intervals, although its internal task schedule rate is at 10ms. For that reason, non-zero
even values for the /SCAN are recommended for Mark V LM units.
The following is a sample help screen:
F:\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, AND "R" FOR A MARK V LM
/SCAN (1=EVERY SCAN, 2 = EVERY OTHER SCAN...)
- MARK V: BASIC SCAN RATE = 1/32 SECOND, DEFAULT IS 1 FOR 32 HZ
- MARK V LM: BASIC SCAN RATE = 5 MSEC, DEFAULT IS 8 FOR 25 HZ
- .........: SCAN SHOULD BE A NON-ZERO EVEN NUMBER FOR THE MARK V LM
/SAMPLES DEFAULTS TO AS MANY AS WILL FIT IN A 1 MB MEMORY BUFFER
F:\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.
F:\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.
F:\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
## UNIT POINTNAME
SCALE
-- ---- ------------ ----1
T1
FSR
%
2
T1
CPD
PSI
08-DEC 11:23:10.937
16.02
08-DEC 11:23:10.968
16.02
08-DEC 11:23:11.000
16.02
08-DEC 11:23:11.031
16.02
08-DEC 11:23:11.062
16.02
08-DEC 11:23:11.093
16.02
08-DEC 11:23:11.125
16.02
08-DEC 11:23:11.156
16.02
08-DEC 11:23:11.187
16.02
08-DEC 11:23:11.218
16.02
08-DEC 11:23:11.250
16.02
08-DEC 11:23:11.281
16.02
<<< AND SO ON >>>
101.6
101.6
101.6
101.6
101.6
101.6
101.6
101.6
101.6
101.6
101.6
101.6
Operation
VIEW2T is a command line utility that collects high-speed turbine data from a Mark
V or Mark V LM 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 program that is run from the command prompt. If
run with no parameters or the /? parameter, a help screen is provided.
Note At the current time, the Mark V LM accepts its scan parameter in units of 5
ms intervals, although its internal task schedule rate is at 10 ms. For this reason, nonzero even values for the /SCAN are recommended for Mark V LM units.
The following displays a sample help screen:
F:\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, AND "R" FOR A MARK V LM
/SCAN (1=EVERY SCAN, 2 = EVERY OTHER SCAN...)
- MARK V: BASIC SCAN RATE = 1/32 SECOND, DEFAULT IS 1 FOR 32 HZ
- MARK V LM: BASIC SCAN RATE = 5 MSEC, DEFAULT IS 8 FOR 25 HZ
- .........: SCAN SHOULD BE A NON-ZERO EVEN NUMBER FOR THE MARK V LM
/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
F:\UNIT1>
The results can be found in the TRIP_VIB.TXT file. The following is a sample of the
output file:
F:\UNIT1> TYPE TRIP_VIB.TXT
## UNIT POINTNAME
SCALE
-- ---- ------------ ----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
26-OCT 10:30:05.718
0
0.28
26-OCT 10:30:05.750
0
0.28
26-OCT 10:30:05.781
0
0.29
26-OCT 10:30:05.812
0
0.29
<< and so on >>
0.30
0.30
0.31
0.32
0.31
0.29
0.29
0.30
0.30
0.30
0.28
0.28
0.29
0.29
0.29
0.30
0.31
0.31
0.30
0.31
0.30
0.31
0.31
0.32
0.31
Operation
VIEWEGD is run from a Command Prompt window. If run with the /? parameter, a
help screen is provided. If run with no parameters, it asks for the name of the point to
monitor. The point to watch can be specified by name if the name-to-address
information can be found in either the F:\EGD_PUSH.DAT file or the
UNIT_EGD.DAT file in the unit configuration directory. (The EGD_PUSH.DAT
file is created by running the UNIT_EGD utility.) If no name-to-address translation
file is present, the point can be viewed by specifying the EGD address and point type
instead of the point name.
The VIEWEGD program scans the EGD Global Section about 10 times per second,
printing a new line on the screen when it detects a change in the point's value or time
tag in the EGD Global Section. This can be faster or slower than the rate that the
controller is configured to send the updates.
The following example displays a sample VIEWEGD help screen:
F:\UNIT1>VIEWEGD /?
VIEWEGD - View EGD Point Data
VIEWEGD is a console mode utility program to watch a single point in the EGD Global
section and report whenever it is updated. It scans for the data ten times per
second. The time tag reported is the time sent with the EGD data, not the time of
the local PC.
There are two methods available to specify what point to watch, DIRECT and
INDIRECT.
INDIRECT: The INDIRECT method allows specifying the unit name and point name
desired. The program looks for F:\EGD_PUSH.DAT and then for the UNIT_EGD.DAT file
in the unit configuration directory to resolve the point name to the location of
the data in the EGD Global Section. The command format is:
VIEWEGD Unit:Pointname
DIRECT: The DIRECT method specifies the actual EGD Producer ID,Exchange ID, Offset,
and Point Type. An optional Display Gain and Display Offset are supported if you
wish to rescale the point for display. The command format is:
VIEWEGD PID:ExchID:Offset:Type:Dgain:Doffset
where:
PID:
The Producer ID, this can be the node name or an IP address.
ExchID: This is the integer Exchange ID. (This can not be zero.)
Offset: This is the byte offset within the exchange, starting at zero. If a bit
packed logic signal is specified, this is specified as "int.int", where
the number after the decimal point is the bit location in the byte. Zero
(0) is the least significant bit, seven (7) is the most significant bit.
Type:
This is the keyword BOOL, WORD, DWORD, or REAL. Direct mode also supports
HEX1, HEX2, and HEX4 types, which ignore the Dgain and Doffset fields.
Dgain:
This is an optional Display Gain applied to the signal.
Doffset: This is an optional Display Offset applied to the signal.
COMMAND FORMAT SUMMARY:
VIEWEGD Unit:Pointname
VIEWEGD PID:ExchID:Offset:Type:Dgain:Doffset
VIEWEGD /?
F:\UNIT1>
In the following example, the vibration measurement point BB1 was collected from
unit G1. Collection was stopped by pressing a key on the keyboard.
F:\UNIT1>VIEWEGD G1:BB1
24-APR-2000 12:14:03.485
24-APR-2000 12:14:03.588
24-APR-2000 12:14:03.697
24-APR-2000 12:14:03.748
24-APR-2000 12:14:03.857
24-APR-2000 12:14:03.965
24-APR-2000 12:14:04.069
24-APR-2000 12:14:04.176
24-APR-2000 12:14:04.285
24-APR-2000 12:14:04.388
24-APR-2000 12:14:04.496
24-APR-2000 12:14:04.548
24-APR-2000 12:14:04.657
24-APR-2000 12:14:04.765
24-APR-2000 12:14:04.868
24-APR-2000 12:14:04.976
24-APR-2000 12:14:05.085
24-APR-2000 12:14:05.188
24-APR-2000 12:14:05.296
24-APR-2000 12:14:05.405
24-APR-2000 12:14:05.456
24-APR-2000 12:14:05.565
24-APR-2000 12:14:05.668
24-APR-2000 12:14:05.776
24-APR-2000 12:14:05.885
24-APR-2000 12:14:05.988
F:\UNIT1>
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
Raw:
0.231447
0.239975
0.239975
0.239975
0.236861
0.236861
0.236861
0.236352
0.236352
0.236352
0.234684
0.234684
0.234684
0.234684
0.234300
0.234300
0.234300
0.231716
0.231716
0.231716
0.240573
0.240573
0.240573
0.239612
0.239612
0.239612
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
Converted:
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0.231447
0.239975
0.239975
0.239975
0.236861
0.236861
0.236861
0.236352
0.236352
0.236352
0.234684
0.234684
0.234684
0.234684
0.234300
0.234300
0.234300
0.231716
0.231716
0.231716
0.240573
0.240573
0.240573
0.239612
0.239612
0.239612
In the following example, two points were collected from a Mark V at the default
rate. The test concluded when the memory buffer was full, and 100 samples were
taken. The results can be found in the VIEWPV.OUT file.
F:\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
Enter pointname[2]: bb2
Enter pointname[3]:
## 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
100 Samples
samples:
Number of samples per
32 Samples/sec
second:
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.
F:\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.
F:\UNIT1>type viewpv.out
## Unit Pointname
Scale
-- ---- ------------ ----1
T1
BB1
in/s
2
T1
BB2
in/s
05-FEB 10:10:52.156
0.32 0.32
05-FEB 10:10:52.187
0.32 0.32
05-FEB 10:10:52.218
0.34 0.34
05-FEB 10:10:52.250
0.34 0.34
05-FEB 10:10:52.281
0.28 0.28
05-FEB 10:10:52.312
0.28 0.28
05-FEB 10:10:52.343
0.29 0.29
05-FEB 10:10:52.375
0.29 0.29
05-FEB 10:10:52.406
0.31 0.31
05-FEB 10:10:52.468
0.32 0.32
05-FEB 10:10:52.500
0.32 0.32
05-FEB 10:10:52.531
0.34 0.34
05-FEB 10:10:52.562
0.34 0.34
<<< and so on >>>
0.32
0.32
0.34
0.34
0.28
0.28
0.29
0.29
0.31
0.32
0.32
0.34
0.34
|
|
|
|
|
|
|
|
|
|
|
|
|
0.32
0.32
0.33
0.33
0.27
0.27
0.29
0.29
0.30
0.32
0.32
0.33
0.33
0.32
0.32
0.33
0.33
0.27
0.27
0.29
0.29
0.30
0.32
0.32
0.33
0.33
0.32
0.32
0.33
0.33
0.27
0.27
0.29
0.29
0.30
0.32
0.32
0.33
0.33
Operation
VIEWQ is a command line utility program that is run from a Command Prompt
window. If run with no parameters or the /? parameter, a help screen is provided.
The following example displays a help screen:
F:\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 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
F:\UNIT1>
In the following example, two points were collected from a Mark V at the default
rate. The test concluded when the memory buffer was full, and 200 samples were
taken. The results can be found in the VIEWQ.OUT file.
F:\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
Enter pointname[2]: bb2
Enter pointname[3]:
## Unit Pointname
Scale
-- ---- ------------ ----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.
F:\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.
## Unit Pointname
-- ---- -----------1
T1
BB1
2
T1
BB2
05-FEB 16:01:46.968
05-FEB 16:01:46.968
05-FEB 16:01:46.968
05-FEB 16:01:47.000
05-FEB 16:01:47.000
05-FEB 16:01:47.000
05-FEB 16:01:47.031
05-FEB 16:01:47.031
05-FEB 16:01:47.031
05-FEB 16:01:47.062
05-FEB 16:01:47.062
05-FEB 16:01:47.062
05-FEB 16:01:47.093
05-FEB 16:01:47.093
05-FEB 16:01:47.093
05-FEB 16:01:47.125
05-FEB 16:01:47.125
05-FEB 16:01:47.125
05-FEB 16:01:47.156
05-FEB 16:01:47.156
05-FEB 16:01:47.156
<<< and so on >>>
Scale
----in/s
in/s
0.29
0.29
0.29
0.29
0.29
0.29
0.31
0.31
0.31
0.31
0.31
0.31
0.32
0.32
0.32
0.32
0.32
0.32
0.34
0.34
0.34
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0.29
0.29
0.29
0.29
0.29
0.29
0.30
0.30
0.30
0.30
0.30
0.30
0.32
0.32
0.32
0.32
0.32
0.32
0.33
0.33
0.33
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.
Operation
VIEW_LIM is a command line utility program that is run from a Command Prompt
window. 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.
F:\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
F:\UNIT1>
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.
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 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.
Operation
VIEW_SD is a command line utility program that is run from a Command Prompt
window. If run with no parameters or the /? parameter, a help screen is provided. The
mean value displayed is the sum of the values divided by the number of points. The
standard deviation is the sample standard deviation.
The following is a sample help screen:
F:\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
F:\UNIT1>
0.34
0.33
0.33
0.33
0.34
0.34
0.308000
0.302000
0.298000
0.298000
0.308000
0.308400
0.021794
0.021794
0.021794
0.021794
0.021794
0.021541
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.
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 convert 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 is a command line utility program that is run from
a DOS window. If run with no parameters or the /? parameter, a help screen is
provided. The following example is a help screen:
F:\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.
F:\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.
F:\UNIT1>type view1.out
## Unit Pointname
Scale
-- ---- ------------ ----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
F:\UNIT1>VIEW2ASC 1,2,3,4,5,6 view1.out view1a.out
12 data points have been written to the file "view1a.out"
F:\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.28
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
F:\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.
F:\UNIT1>TYPE view2.out
## Unit Pointname
Scale
-- ---- ------------ ----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.30 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.27 0.28 0.28 0.28 0.34
05-FEB 17:15:55.000
0.34 0.33 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.30 0.31 0.31 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.27 0.28 0.28 0.28 0.34
05-FEB 17:15:56.250
0.34 0.33 0.27 0.27 0.34 0.34
F:\UNIT1>VIEW2ASC 1,2,3,4,5,6 view2.out view2a.out
12 data points have been written to the file "view2a.out"
F:\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
F:\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.
Web-based Displays
WEB programs are available from the HMI as a Web-based display. These Web
displays can be viewed locally, or from other computers connected to the HMI
through a network. These displays are listed below and discussed in the following
sections.
WARCWHO - WEB ARCNET Status Display. This program displays the list
of ARCNET nodes that are visible to the HMI. It is useful in debugging
ARCNET communication problems.
WGBL - WEB Global Section Display. This program provides a list of the
advanced debugging trace global sections that are available, and the ability to
retrieve the contents of any trace global section.
WHAERPT - WEB Historical Alarm and Event Report. This program provides
either a detailed list of alarms or a summary report of alarm for a given set of
units over a given time range. This is the primary interface to the HMI Historical
Alarms and Events.
WHISTORY - WEB Historical Alarm and Event Report by Day. This utility
program provides either a detailed list of alarms or a summary report of alarms
for any particular digital exception message day file.
WLFORCE - WEB Logic Forcing Display. This program provides a list of the
logic signals that are currently forced in a Mark V or Mark V LM controller.
WPBRO6 - WEB Point Browser for Mark VI. This program provides a list of
signals that are available from a Mark VI. A list of only the published signals or
a list of all signals in the unit can be returned.
WPBROXD - WEB Point Browser for Data Dictionary. This program provides
a list of signals that are available from any Data Dictionary based unit, which
includes the Mark V and Mark V LM.
Demand Display - This displays the values of a selected list of points from the
TCI Data Dictionary. Any point in the data dictionary can be displayed by
typing in the point name. New Point Lists can be added, or the points in a Point
List can be modified, by editing the F:\WDEMAND.DAT file.
Logic Forcing This Mark V display displays a list of all the forced points in
the unit. It does not allow the forcing or unforcing of points.
HMI Startup log This displays the last startup log file for this HMI.
(Browse) This allows the desired log file to be picked and displayed.
Point Browser This displays all the points in the data dictionary for the
selected unit.
ARCWHO This displays all the nodes that are active on the ARCNET.
To access the Web displays from the HMI
From the Desktop, select Start, Programs, then the Web browser (usually
Internet Explorer)
If the page is not already configured as the Home page, in the address area, type:
http://localhost
Click
displays.
or press the Enter key. The TCI Information Web Home page
If you are not at the HMI, but some other computer connected to the HMI by a
network, the Web displays can be accessed from your Web browser by typing:
http://<HMI computer name>.
Home
page
Click on item to
open the Web
display.
For example, the address for a display with Process Alarms sorted by the unit and
alarm drop number would be as follows:
http://<computer>/scripts/GEDS/WALMDUMP.EXE?PALARM+DROP
Users can add the ability to get HOLD alarms for Steam Turbine sites with Mark V
and Mark VI systems by adding the following entry to the Web menu:
<A HREF="/scripts/GEDS/walmdump.exe/HOLDS.TXT?HOLD">
Current Hold List</A>
The list of supported parameters is as follows:
PALARM
DALARM
DIAG
HOLD
TIME
DROP
To add a parameter to the web-based request, add a question mark to the end of the
URL followed by the command line parameter. If multiple command line parameters
are desired, separate them with the plus sign +. For example, to display the
ARCNET protocols that have been allocated, use the following:
<A HREF="/scripts/geds/wanetc.exe?/p">ARCNET Driver
Protocols</A>
After selecting the unit number and the sorting method, click on Submit and the
control constants are displayed.
The predefined point lists are defined in the F:\WDEMAND.DAT file. Each point list
is defined by enclosing the name of the point list in square brackets starting in the
first column. Under each list definition are the names of the points in the list, one
point name per line. If a unit name is not included with the point name then the unit
that the user selected is used. If the unit name is included with the point name then
the selected unit is ignored. If every point in the list has a unit name and point name,
then no unit needs to be selected. This is often used for plant summary displays
where status points from all units are used to make a plant overview display. Any
line that starts with a semi-colon in the first column is taken to be a comment line
and is ignored. Blank lines are also ignored.
The following is a sample F:\WDEMAND.DAT file:
[Plant Overview]
T1:STATUS_FLD
T1:DWATT
T1:DVAR
T2:STATUS_FLD
T2:DWATT
T2:DVAR
[Turbine Vibration]
BB_MAX
BB1
BB2
BB3
BB4
BB5
The report contains a header, which displays the users form input selections:
The Report type output page contains the following data on each line:
The Time tag of the exception; this time comes from the controller
The Point name for SOEs and Events, or processor and drop number for alarms.
Descriptive text
The report begins with the oldest data and has the newest data at the end. It may be
printed or saved as a text file from the browser window. To return to the query form,
use the Back button on the web browser toolbar.
The report contains a header that displays the users form input selections:
The report data is listed separately for each unit, and each data type within that unit.
Data is listed in the order of drop number for alarms and events, and in point number
order for events and SOEs. The output page contains the following data on each line
for process alarms:
The processor
Descriptive text
The output page contains the following data on each line for Events and SOEs:
Descriptive text
It can be printed or saved as a text file from the browser window. To return to the
query form, use the Back button on the web browser toolbar.
The day is based upon UTC time, not site local time. If no records for a particular
type are received during a day, no file is created. The files are stored in a historical
data directory and are named YYYYMMDD_***.D03 as follows:
EVT = Events
Along with the name of each file found, the display includes links to View the
detailed records in the file, Summarize the contents of the file, or Download the
file. If you are trying to download the file to your local COMPUTER, the easiest
way is to right click on the Download link and choose Save target as or Save
link as.
The View report is similar to the Historical Alarm and Event report, and the
Summarize report is similar to the Historical Alarm and Event Report's summary.
The main difference in content is that all data in the file is included, instead of being
able to select the time range and units. The main difference in format is that the
native UTC time tag is displayed, not site local time. (This is one reason why this
utility is typically not exposed to end users on the Web menu).
If you wish to add the WHISTORY program to the TCI WEB menu, the following
entries can be used. To add the program and give the user the choice of list or table
modes, add two entries such as the following to either the Alarm Displays section of
the menu or the Debugging Information section of the menu:
<LI>
<A HREF="/scripts/GEDS/whistory.exe">Alarm, Event, and SOE files (List mode)</A>
</LI>
<LI>
<A HREF="/scripts/GEDS/whistory.exe?Table">Alarm, Event, and SOE files (Table
mode)</A>
</LI>
The Unit and Sorting methods are selected, and the resulting forced points display
is as follows:
From the Desktop, double click the TCI Menu icon. The TCI Information
web browser screen displays presenting choices.
From HMI Information, click the Point Browser (Mark VI Toolbox) text.
The Mark VI Toolbox Browser - Select Options form displays. The
default form is set up to display the list of all points defined on EGD pages. The
file location is partially filled with F:\UNIT. The user must fill out the remaining
information to identify the desired Mark VI Toolbox file, for example,
F:\UNIT1\G1.M6B.
From the Mark VI Toolbox Select Options display, modify the default form
fields as needed. This is described in the sections below.
When the form is complete, click the Submit button. The requested Mark VI
Toolbox Report displays.
The following sections describe the entries in the Mark VI Toolbox Browser Select
Options display.
Selecting the Points. All points or specific points based on the pointname can be
chosen. A wildcard string such as G1:TN* is allowed.
Selecting the List Type. The default list is EGD, which produces a report starting
with the first point on the first EGD exchange and ending with the last point on the
last EGD exchange produced by the Mark VI. Selecting Signal list produces a report
in alphabetic order of the signal name for all signals defined for this Mark VI.
Selecting the EGD Exchange list produces a report with information about each
EGD exchange.
Selecting the Display Type. The default report type is Text. By checking the
CSV radio button, the output format will be a Comma Separated Variable format
used for loading in Spreadsheet and Database applications.
Selecting the File Location. The specific Mark VI Toolbox file name, with full
path, is entered here.
EGD Report
The EGD report displays data in column format with the point name in the first
column, the Producer ID for the EGD Exchange, the exchange number, the points
offset within the exchange, the exchanges revision number (Configuration
Signature), and the EGD type for the point. If the GE Control System Toolbox 6.2 is
installed on the HMI, the defined engineering units are displayed next. For GE
Control System Toolbox 6.1, N/A is displayed. The points description appears last.
EGD Report
The CSV format display is used for loading the data into Spreadsheets and Database
applications.
To load the EGD Report CSV file into a spreadsheet
From the CSV format EGD Report, select the menu item File.
From the File drop-down menu, select Save As. Save the file with a *.csv
extension.
Signal Report.
The Signal report displays data in column format with the signal name in the first
column, followed by the Mark VI data type for the point. If the GE Control System
Toolbox 6.2 is installed on the HMI, the defined engineering units are displayed
next. For GE Control System Toolbox 6.1, N/A is displayed. The points description
appears last.
Signal Report
The CSV format display is used for loading the data into Spreadsheets and Database
applications.
To load the Signal Report CSV file into a spreadsheet
From the CSV format Signal Report, select the menu item File.
From the File drop-down menu, select Save As. Save the file with a *.csv
extension.
The CSV format display is used for loading the data into Spreadsheets and Database
applications.
To load the EGD Exchange Report CSV file into a spreadsheet
1
From the CSV format EGD Exchange Report, select the menu item File.
From the File drop-down menu, select Save As. Save the file with a *.csv
extension.
From the Desktop, double click the TCI Menu icon. The TCI Information
web browser screen displays presenting choices.
From TCI Information, click the Point Browser (Data Dictionary) text.
The XD Point Data Base Browser Select Options form displays. The
form is automatically filled in and is set up to display the list of all points for the
first defined unit, sorted by name, with their associated engineering units and
long name.
From the XD Point Data Base Select Options display, modify the default
form fields as needed. This is described in the sections below.
When the form is complete, click the Submit button. The requested Data
Dictionary Report displays.
The following sections describe the entries in the XD Point Data Base Browser
Select Options display.
Selecting the Points. All points or specific points based on the pointname can be
chosen. A wildcard string such as G1:TN* is allowed.
Selecting the Unit. Any defined unit can be selected.
Selecting the Sort. The default sort is by Name, which produces a report in
alphabetic order of the pointname. By checking the Offset radio button, the report is
sorted in increasing order of the points address.
Selecting the Data Types. Users can wish to reduce the amount of information
on the output report. The Engineering Units and Long Names are selected by default.
The user can uncheck these boxes to delete them from the output.
Selecting the Display Type. The default report type is Text. By checking the
CSV radio button, the output format is a Comma Separated Variable format used for
loading in Spreadsheet and Database applications.
The CSV format display is used for loading the data into Spreadsheets and Database
applications.
To load the Data Dictionary Report CSV file into a spreadsheet
1
From the CSV format Data Dictionary Report, select the menu item File.
From the File drop-down menu, select Save As. Save the file with a *.csv
extension.
From the Spreadsheet application, open the saved file. The file displays correctly
in the spreadsheet.
EVT = Events
D03 is the internal format of the exception messages (digital, format 03)
The files are stored in the historical data directory, which is typically C:\HMIDATA.
Historical files are only saved if the Options section includes the Alarm_History =
Yes option.To extract information from the desired file, the WSUM_D03 program is
run. It needs to be told using command line parameters the type of report desired and
the file that it should process. The program can be run with HELP as its only
command line parameter to provide a simple help screen. The available command
line parameters are as follows:
For example, to create a detailed report displaying each alarm transition from a file
that contains all the process alarms for March 15, 2001 located in the current default
directory, and write the results to a file called alarms.txt, the following command
would be used:
WSUM_D03 DIRECTORY=. RPT 20010315_ALM.D03
>alarms.txt
CHAPTER 7
Chapter 7 Networks
Network Overview
This chapter discusses the communication networks connecting the HMI to the Mark
IV, Mark V, Mark VI controllers, and to the distributed control system. The Control
System Freeway, Stagelink, Unit Data Highway, Plant Data Highway, and Serial link
are covered.
CSF Characteristics
CSF consists of a 2.3-MHz system that uses either fiber-optic or twinax copper
cabling. Fiber-optic cabling prevents electromagnetic interference and is often a
better alternative for long outdoor segments (refer to the section on Fiber-optics in
this chapter).
Mark IV Control System Freeway
CSF Feature
Description
Communication type
Baseband
Frequency or speed
2.3 MHz
Cable type
Topology
100
CSF uses Global memory, which is a section of memory in each station transmitted
to every other station on a regular basis. The message from each station is 256 bytes
in length. For communication integrity, 16-bit CRC is used on every message.
Note Many early Mark IV systems have been upgraded by replacing the twinax
cables with coax, and by adding Mark V communication equipment, Ethernet
communications, HMIs, and the Historian.
Terms of Reference
Terminology used in this Mark V section is as follows.
Node Any device connected to the Stage Link system that has a valid address:
An HMI
The Stage Link 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
31 micro seconds
Repeater Nodes
Other Repeaters
Fiber-optic hubs
HMI
Within the Mark V panels, the ARCNET cable is connected to the CTBA board, and
with the Mark V LM it is connected to the AAHA board. These are located in the
TCP communication processor. The CTBA or AAHA 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 Stage Link through a T type connector. The ARCNET board within
the HMI receives data by tapping off a portion of signal transmitted on the Stage
Link. 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.
Stage Link Cable Recommendations
Cable Type
Recommendation
Copper Cable
Indoor Cable
Outdoor Cable
Connector Type
Fiber-optic Cable
Cable
Connector Type
ST bayonet
Hub Power
Hub Configuration
Both ends of the Stage Link must have a 93-ohm terminating impedance.
Cable Segments
Cable Lengths
The network diagrams in figure Stagelink Cable Segment Rules illustrate the segment
rules. The following apply to these diagrams:
TCP
coax
coax
Active
hub
Active
hub
coax
coax
TCP
R 93 ohms
HMI
TCP
HMI
HMI
HMI
HMI
HMI
HMI
TCP
HMI
HMI
HMI
HMI
R
HMI
HMI
TCP
HMI
TCP
HMI
HMI
HMI
TCP
HMI
TCP
TCP
HMI
HMI
HMI
HMI
HMI
HMI
Each TCP repeater has a relay that drops out when the power is off,
connecting the two ports in order to maintain communication.
HMI 2
267m
HMI 1
HMI 4
S3
S2
30m
TCP1
30m
HMI 3
Segments
TCP3
Segment
S1
S2
S3
S4
270
30
55
270
270m
25m
TCP2
S4
3 TCPs @ 25 = 75
625
75+625 = 700, well below the 6000 meter limit
Calculation of Maximum
segment with one node
failure.
Failure of node:
Results in a combined
segment of:
TCP1
TCP2
TCP3
HMI1 to
TCP2
TCP1 to
TCP3
TCP2 to
HMI4
300
85
325*
FOH
HMI
HMI
FOH
HMI
HMI
FOH
FOH
HMI
R
<C>
<C>
<C>
<C>
<C>
<C>
<C>
<C>
<D>
<D>
<D>
<D>
<D>
<D>
<D>
<D>
R
HMI
<C> - Communications Processor
<D> - Backup Communications Processor
FOH - Fiber Optic Hub
HMI - Operator Interface
R - Terminating Resistor (93 ohms)
Redundant Stage Link
S1
FOH1
HMI
S11
HMI
HMI
FOH3
HMI
S10 760m
Fiber-optic
S2 600m
Fiber-optic
FOH2
FOH4
S3 3m
S9 3m
S4
S5
TCP1
TCP2
S6
TCP3
S7
HMI
TCP4
S8
TCP5
TCP6
Segments
Segment
Coax Cable length
Fiber-optic Cable
Maximum Effective
Cable length
S1
S2
Totals
S3
S4
S5
S6
S7
S8
30
30
180
30
150
S9 S10 S11
3
6
760
600
438
1360
2388, well below the
6000 meter limit
Calculation of Maximum
segment with one node
failure.
Failure of node:
Results in a combined
segment of:
TCP1
TCP2
TCP3
TCP4
TCP5
TCP6
FOH2 to
TCP2
TCP1 to
TCP3
TCP2 to
TCP4
TCP3 to
TCP5
TCP4 to
TCP6
TCP5 to
FOH4
210
210
180
153
33
30
Fiber-optics
Fiber optics can be an effective substitute for copper-coax cabling, especially in
cases where longer distances are required, or electrical disturbances are a serious
problem.
Advantages
The main advantages of fiber-optic cabling are as follows:
If the plant is in a high lightning area, fiber-optic segments can reduce control
outages caused by lightning.
Grounding problems are avoided with optical cable. The ground potential can
rise when there is a ground fault on transmission lines, caused by currents
coming back to the generator neutral grounding point.
Optical cable can be routed through switchyards and other electrically noisy
areas and not pickup interference. This can shorten the required runs and
simplify the installation.
With proper cable jacket materials, fiber-optic cable can be run direct buried, in
trays, or in conduit, with care not to install below the specified bend radius.
Larger diameter fiber extends this to 9000 feet (2,740 m) because the light
transmitter can insert more light into the fiber.
Disadvantages
The main disadvantages of fiber-optic cabling are as follows:
Fiber-optic links require powered hubs at each end, with a reliable source of ac
power. Failure of power to either hub causes a link failure.
The effective distance of a fiber segment is 1.25 times the actual cable routing
distance. The rule for Stage Link is that the total effective distance between
devices the farthest apart must not exceed 20,000 feet.
The extra equipment required for fiber links can increase maintenance.
The cost a fiber-optic Stage Link segment, particularly for short runs, may be
more than for coax.
Inexpensive fiber-optic cable is easily broken during installation and more prone
to mechanical and performance degradation over time. The highest quality cable
is recommended.
Review of Components
This section reviews the basic components of a fiber-optic system, including cable,
hubs, and connectors.
Basics
The recommended fiber-optic hub accepts two copper coax connections and two
fiber-optic links. A message coming in on any one of the four ports is repeated from
the other three ports. Each fiber port consists of an outgoing fiber and an incoming
fiber. The incoming signal is picked up with a phototransistor and converted to an
electrical signal. The outgoing signal is converted from a train of electrical pulses to
infrared light using a light emitting diode. On the fiber segment the optical output of
one hub is connected through the fiber cable to the optical input of the other hub.
Two fibers are needed for each segment.
Multimode fiber, with a graded index of refraction core and an outer cladding, is
recommended for the Stage Link. The amount of light that enters the fiber depends
on the brightness of the light source and the area of the light-carrying portion of the
fiber. The amount of light that comes out of the other end depends on the clarity of
the glass, the distribution of the index of refraction, the condition of the fiber, and the
attenuation of the connectors. The strength of electrical signal generated depends on
the light coming out of the fiber and the area and sensitivity of the phototransistor.
Tracking all this is done using a power budget.
Note The Power Budget predicts the optical signal strength at the receiver.
The fiber is protected with buffering, which is the equivalent of insulation on
metallic wires and protects the cable from excessive bends. Mechanical stress can
damage fibers. One way to protect the fiber is to spiral it on the inside of a tube filled
with gel, but there are problems with this. A more reliable system uses tight
buffering with precision tensioned Kevlar fibers, which carry the stress of pulling
and the stress of vertical runs.
Never look directly into a fiber. Although most fiber
links use light emitting diodes that cannot damage the
eyes, some longer fiber links use lasers that can cause
permanent damage to the eyes.
Fiber-optic Cable
High quality, 62.5/125-micron optical cable is recommended, especially for long
distance links. The cable attenuation should be between 3.0 and 3.3 dB/km at 850 nm
and around 1 to 1.2 dB/km at 1300 nm.
The acrylate protective layer of the fiber should be specified with a 100-kpsi proof
test and a 500-micrometer coating, rather than the 50-kpsi and 250-micrometer
coating. Gel filled, or loose tube cables should not be used because of the special
care required during installation, the difficulty of making terminations, and problems
of maintaining the gel seal, particularly in vertical runs where hydrostatic pressure
can cause gel leakage.
Use a high quality break out cable, in which each fiber is a sturdy cable that helps
prevent sharp bends. Combine the sub-cables with more strength and filler members
to build up the cable for resisting mechanical stress and the outside environment.
Multimode
Core diameter:
62.5 microns
Cladding Diameter:
125 microns
100 kpsi
Coating Diameter:
500 microns
Bandwidth
Attenuation
850 nm
160 MhzKm
3.5 dB/km
1300 nm
500 MhzKm
1.3 dB/km
Stripping ability: All layers can be easily removed with commercially available
tools.
Sub Cables: Four sub cables each with one fiber.
Fiber strength member: Aramid yarn
Sub-cable diameter:
2.5 + - 0.125 mm
Sub-cable jacket:
Elastomeric
Color-coded:
Color:
Black
Cable weight:
65 kg/km
Cable diameter:
8.0 mm
16 cm (when pulling)
2200 N
Location:
Pulling:
Operating:
Min bend radius:
8 cm
550 N
Temperature:
-40C to +85C
Immersion:
No damage
Storage:
-55C to +85C
2200 N/cm
Cyclic flexing:
2000 cycles
Multimode
Core diameter:
62.5 microns
Cladding Diameter:
125 microns
100 kpsi
Coating Diameter:
500 microns
900 microns
Bandwidth
850 nm
3.5 dB/km
160 MhzKm
1300 nm
1.3 dB/km
500 MhzKm
Stripping ability: All layers easily removed with commercially available tools.
Sub Cables: Four sub cables each with one fiber.
Fiber strength member:
Aramid yarn
Sub-cable diameter:
2.5 0.125 mm
Sub-cable jacket:
Elastomeric
Color-coded:
Color:
Black
Armor:
Armor overlap:
Over jacket:
Cable weight:
174 kg/km
Cable diameter:
13.0 mm
Strength members:
Installation:
Min bend radius:
26 cm (when pulling)
2660 N
Location:
Pulling:
Operating:
Min bend radius:
13 cm
532 N
Temperature:
-40C to +65C
Immersion:
No damage
50 impacts
Crush resistance:
440 N/cm
Rodent damage is one of the major causes of failure of optical cable. If there is a
possibility of wire insulation damage from rodents, the armored cable should be
chosen. Otherwise, the armor is not recommended because it is heavier, has a larger
bend radius, is more expensive, attracts lightning currents, and has lower impact and
crush resistance. Particularly for underground runs, a direct lightning strike through
the earth to the cable shield can cause explosive formation of steam in damp earth.
The explosion can mechanically damage the cable.
Test the optical characteristics of the cable with either an optical time domain
reflectometer (OTDR), which can be provided by the manufacturer, or with a simpler
device that compares light levels at both ends of the cable.
Four-fiber cables can be used to bring redundant communications to a central control
room, or the extra fibers can be retained as spares. A less expensive option is to get
the same cable with only two fibers.
Hubs
The type of hub described here is built particularly for ARCNET communications
and has the correct impedance to match the ARCNET line (93 ohms). For this
reason, a fiber hub intended for Ethernet, for example, will not function properly on
the Stage Link. The hub contains a power supply that runs from 120 or 220 V ac, 50
or 60 Hz. One model can be converted to the other by moving an internal jumper to
accept the other voltage in case an error was made in ordering.
The rack contains a power supply with sufficient power for four expansion boards.
Each board has two copper coax ports and two fiber-optic ports. A signal coming in
on any port is amplified and transmitted on the other three ports. Ordinarily only one
board is used. If the system uses two fiber segments, a second hub is recommended
to improve the communications availability. On the board, normally only one copper
port and one fiber port are used for the same reason. The fiber-optic ports in the hub's
board have bayonet-type ST connectors. The light gray one is the transmit port, the
dark gray one is the receive port. In service a light gray connector always attaches to
a dark gray one in the other device.
Connectors
Two types of connectors are used, SMA and ST. The ST connectors give fewer
problems in the field because they are bayonet type and not subject to over
tightening. Over tightening the SMA connector can chip the glass fiber surface
causing problems with reflections and loss of transmission. The bayonet type uses a
spring to push the two connecting fibers together with the proper force.
Note ST type fiber-optic connectors are preferred.
Ceramic, glass-filled plastic, or stainless steel is used to make the connectors. They
come in three standard sizes to fit the different diameter fibers. Connectors for the
62.5/125-micron fiber are relatively easy to procure. The ceramic connectors can be
precisely made, and the ceramic matches the coefficient of expansion of glass.
System Considerations
Having two HMIs in the central control room allows one to be down for maintenance
while control of the turbines continues using the remaining HMI. Similarly, having
two fiber segments also allows for failure of one of the hubs, or the power to it. A
failure of any one of the copper segments still allows control of all machines.
Often only HMIs and possibly an Historian are in or near the central control room.
The control room must have reliable ac power, since if that ac fails, control from that
location stops. Therefore, the reliable ac power in the control room is satisfactory for
the hubs as well.
Another system consideration is the optical power budget for the Stage Link. The
total power budget refers to the brightness of the light source divided by the
sensitivity of the light receiver. These power ratios are measured in dB to simplify
calculations. The difference between the dB power of the source and the dB power of
the receiver represents the total power budget. This must be compared to the link loss
budget, which is made up of the loss in the connectors and optical cable.
Installation of the fiber can decrease its performance over the new cable condition.
The LED light source can get dimmer over time, the connections can get dirty, the
cable loss increases with aging, and the receiver can become less sensitive. For all
these reasons there must be a minimum margin of 3 dB between the available power
budget and the link loss budget. A good installation results from using correct parts
and cabling, preparing connectors properly, and laying the cable so as to avoid sharp
bends and hot locations. This will maintain availability.
The hub manufacturer specifies one fiber segment to operate as far as 6,000 feet with
62.5/125-microns fiber, and 9,000 feet with the 100/140-microns fiber. These
distance limitations have been incorporated into the Stage Link layout rules. It is
recommended that the Stage Link fiber-optic sections be shorter than the specified
6,000 and 9,000 feet for the two fiber diameter types. If the application significantly
exceeds these distances another hub must be added to amplify the optical signals.
HMI
Viewer
HMI
Viewer
HMI
Viewer
Field
Support
Enterprise Layer
Router
Supervisory Layer
PLANT DATA B
P LANT DATA A
Router
HMI Servers
OSM
Historian
Control Layer
U NIT DATA HIGHWAY B
U NIT D ATA HIGHWAY A
Simplex
Unit
Controls
Mark VI
TMR Unit
Controls
Mark VI
Mark VI
Generator
Protection
Gen.
Protect
(Future)
Misc
.
Controls
Exciter
GEF PLC
Static
Starter
EXCITER
LCI
EXCITER
GEF PLC
Mark VI
IONet
IONet
I/O Boards
I/O Boards
Genius
Bus
I/O Boards
Genius
Bus
I/O Boards
Mark VI Control and HMI Servers and Viewers with Redundant Networks
UDH Feature
Description
Type of Network
Speed
Number of Nodes
With 10 nodes, system provides a 25-Hz data rate. For other configurations
contact the factory.
Protocol
PDH Feature
Description
Type of Network
Speed
Number of Nodes
Protocols
External Interfaces
Various third-party interfaces are available; GSM and Modbus are the most
common.
Network Rule
Description
The local HMI would normally be a server to its local turbine control. As a multi-unit
option, the HMI server may be a server to other units also. Data collection is
accomplished over the UDH. For multi-unit configurations, create a single project that
contains all units and copy the project to the other multi-unit HMIs
The control room HMI may be a server for multiple Mark VI controllers. This can be
accomplished by creating a single project covering all desired units
Remote CIMPLICITY viewer is available for remote monitoring and control. Consult the
Turbine Control System factory for its availability
Historian
Only GE devices, Mark VI, HMI Servers, Engineering workstations, Historians, and GE
PLCs are allowed on the UDH
HMI viewers, HMI servers, Engineering workstations, Historians, printers, DCSs, third
party PLCs, and interfaces to customers corporate LANs are allowed
Interface links
The HMI server can provide Modbus Serial, Modbus TCP/IP, GSM, or OPC links to
devices such as a DCS system
Mark VI also has capability of Modbus from the controller
References
Network Redundancy
Both the PDH and the UDH typically use redundant Ethernet networks for increased
reliability. Refer to figure Mark VI Non-Redundant Network Overview for an
example of a non-redundant system and figure Mark VI Redundant Network
Overview for an example of a redundant network.
The redundant network systems HMIs can include software that monitors the health
of the networks and will report on loss of communication links, which may not be
visible due to the redundant network. A failure will appear in the alarm screens on
the HMI. The HMI can contain diagnostic screens to assist in locating the point of
failure for repair. Refer to the section Network Diagnostics for more information.
Note Refer to GEH-6421 Mark VI Control System Guide for more information.
The abbreviations used in figure Mark VI Non-Redundant Network Overview and
figure Mark VI Redundant Network Overview are as follows:
OSM stands for On Site Monitor, used for monitoring mechanical turbine
variables
EWS stands for Engineering Work Station, used for system configuration.
R, S, and T are the three redundant Mark VI controllers in the triple modular
redundant control system.
PDH Hardware
Description
Twisted-pair cable
Unshielded Twisted Pair (UTP) cable, 22-26 AWG, 4 pair, Category 5 EIA/TIA 568 A/B or better,
including RJ-45 connectors
Maximum distance for UTP cable is 100 m (328 ft)
A one-to-one UTP cable is used to connect a device, HMI, or printer to a switch
A one-to-one UTP cable is used to connect a switch to a router.
A cross-over UTP cable is used to connect a switch to a switch
Fiber-optic cable
Optical fiber cable, Ethernet 100Base-FX type, 62.5/125 micron, dual window, graded index profile,
multimode glass-on-glass construction, thermoplastic jacket, including SC type connectors
Maximum distance for fiber-optic cable is 2000 m (6562 ft)
When connecting fiber-optic cable using SC type connectors, the connections have to be crossed,
that is the transmit at one end is connected to the receive at the other end, and vice-versa
Redundant Network
If only one RS-232 link is required the port on the main computer is used, a serial
extender is used if more RS-232 ports are required.
If the required cable distance is more than 50 ft (15.2 m), a serial line driver is
needed. Serial line drivers can support distances up to a mile and baud rates up to
19,200. The following table describes the features.
Serial Link Features
Feature
Description
Media
RS-232C cable; without line drivers the distance is 50 ft (15.2 m); with line drivers the distance is over a mile
Speed
From the Start menu access the teaming software by selecting Control panel
Broadcom Advanced Control Suite 2.
The Broadcom configuration utilities window opens with a list of network cards.
Refer to figure Typical List of Network Cards for an HMI Server.
Network Diagnostics
There are two levels of diagnostic support.
Alarms only
A link failure creates an alarm message that indicates the link that failed. If a switch
fails then all used ports on that switch are reported as link failures.
Failures should be investigated and corrected because if a second failure occurs
before the first failure is corrected then there can be communications loss.
If the optional network diagnostic screens are present they will graphically assist in
locating the point of failure. Refer to figures Typical System Switches Diagnostics
Screen, Port Status Diagnostic Screen and Typical Network Devices Diagnostic
Screen for examples of these diagnostic screens.
Note PDH and UDH are typically redundant so a single failure will not prevent
communication.
An alarm message will typically announce the failure of a network system or device.
To identify the failed device:
Failed switch
Alarm message
Clicking on a switch icon from the System Switches diagnostic screen opens a
window with a graphical representation of the ports associated with that switch. This
assists in determining the cause for the failure of that communications link. The ports
are color coded as follows:
Failed device
and network
Alarm messages
Note A computer cannot respond to a ping request from another computer if its
firewall blocks the ICMP Echo request. Refer to the section on Firewall Settings
later in this section to check this feature.
Ping Options
Refer to figure Successful Ping Command for a typical ping request. The round trip
time should be typically less than 10 milliseconds and no lost packets for a local
network.
Refer to figure Unsuccessful Ping Command for a typical ping request. By default
the ping command will try four times before it exits. In this example the four
requests timed out and all four packets were lost.
Firewall Settings
Different firewalls on a computer will have different procedures for allowing ICMP
Echo requests. Windows XP firewall configuration is accessed from Start
Control Panel Windows Firewall Advanced ICMP Settings. Refer to
figure ICMP Settings.
ICMP Settings
CHAPTER 8
Chapter 8 CIMPLICITY
Overview
Introduction
The CIMPLICITY HMI collects data from plant sensors and devices, and then
transforms the data into dynamic text, alarm, and graphic displays. Operators can
access real-time information when monitoring and making control decisions. The
turbine control HMI supports many CIMPLICITY applications for operation.
CIMPLICITY is used primarily to display turbine status screens, which enable an
operator to monitor the unit(s). Refresh rate is typically 1 second. CIMPLICITY
cannot configure the turbine control.
CIMPLICITY supports OLE and ActiveX applications for automation displays.
CIMB (CIMPLICITY Bridge) enables CIMPLICITY to collect data and alarms from
a turbine unit with Mark V. (Mark VI uses EGD) TCIMB provides the following
software functions:
MARKV_RP collects data from a turbine using TCI and forwards the
information to the CIMPLICITY Point Manager.
Note The CIMPLICITY HMI product must be installed before these applications
can be used. Refer to the Online Documentation for CIMPLICITY display and
CimEdit features.
Breaker close
times Configure
using
Breaker tab.
Note When you push the Breaker Close or Breaker Trip button, a dialog box
displays with two buttons for command confirmation:
Command sends the breaker close or trip command when selected and released.
Done exits the dialog box and cancels the breaker close or trip command.
Name of ActiveX
control
Configuring Permissives
To configure the Permissives part of the object, add or edit the list entries in the
Permissives tab.
Logic signal
used.
Determines color of box
displayed by variable. If
variable value equals
Sense value, box is
green. If not equal, box is
red with a dash next to it.
Add entries to
list.
Delete currently
selected entry.
Edit currently
selected entry.
Configuring Values
To configure the objects Values, enter data into the Value tab.
Values in display in the object in the
same order
as in the list box. Sets number of
digits for displaying the value.
Uses number of decimal places and
units string specified in the scale
code.
Signal used for the value.
String that displays to the left of
the value.
Add entries to end of list.
Select object
colors.
Red dot
represents the
current
generator
operating point.
It moves as the
operating point
changes.
Configuration
Introduction
This chapter provides information about configuring CIMPLICITY projects for use
with the turbine control HMI product. To understand and implement the information
in this chapter, you should have a working knowledge of CIMPLICITY projects as
covered in the CIMPLICITY online documentation. CIMPLICITY HMI should be
configured with the following project properties:
Project Name Appropriate name (for example, SVR1)
Sub Directory Must be Cimproj
Path F:\Cimproj
General options Basic control, external alarm manager
Protocols Refer to CIMPLICITY Project Properties in Chapter 2.
Note The CIMPLICITY HMI product must be installed before these applications
can be used.
Previously a typical turbine control CIMPLICITY HMI used set of screens that were
contained in a Frame Container within the Unit_Control.cim screen.
CIMPLICITY projects may now use single screens for each of the previous frames
contained in a Frame Container. The objects of Single Screens are programmed and
configured much the same way as their counterparts in Frame Containers. See
CIMPLICITY online documentation for more information.
If your project uses Single Screens refer to New_Single_Screeen_Features.PDF
located in the F:\Cimproj\Screens directory for more information.
A new tool easily configures the menu buttons that control screen navigation. This
allows for easier screen additions and corrections.
Using Workbench
The CIMPLICITY HMI Workbench is an application used to view, configure,
organize, and manage projects. It is similar to the Microsoft Windows Explorer in its
display of the file structure and menu options across the top of the window.
Document GFK-1180 provides detail about using Workbench. Refer to Alarm
Filtering in HMI Servers (Chapter 5) for examples of the Workbench window.
To open Workbench
1
Opening a Project
Using the CIMPLICITY HMI, there are two ways to open a project, as described
below.
To open a CIMPLICITY project through the Windows Start menu
1
From the Workbench window, select Open from the File menu.
Stop TCI. Refer to TCI Starting and Stopping in this chapter. Open the
Project in CIMPLICITY and verify the project is stopped.
Stop Project
icon
Start Project
icon
Configuration Update
icon
Click OK
Start the CIMPLICITY Project has completed startup verify that data is being
received.
Save the HMI Device by using the Save icon or File - Save.
Configuring Users
A user is an individual person working with a CIMPLICITY HMI project. Each
CIMPLICITY HMI user has the following attributes, which must be configured:
Security A user can be assigned a Password. If a Password is configured and
enabled, then a user cannot access CIMPLICITY HMI project functions without
entering both the User ID and Password.
Roles and Privileges A user is assigned a role. Each role in the CIMPLICITY
HMI project has certain privileges assigned to it. The privileges define the functions
the user can access. If a user lacks the privilege to access a secure function, an error
message is displayed and access is denied.
View of Resources A users view determines the accessible resource data.
Alarms for resources outside a users view do not display on the users Alarm
Viewer window.
To configure Users for the CIMPLICITY HMI project
Users, as
Left pane
displays
CIMPLICITY
application
folders.
Select Users
Right pane
displays files or
records of
selected object.
Open the New User dialog box and add a new user called OPERATOR.
Open the User Properties dialog box for the user OPERATOR and enter
Operator as the User name.
Select tab.
Select the Resources tab and add all resources T1 through T8.
Select tab.
Displays resources
currently assigned
to user.
To add resources,
select from Available
box then click Add.
Note The Resources properties let you define the resources for which the user can
view alarms. Resources can be added or removed based on the Users rights. For
example if you want to have a User name as User1 who is supposed to operate only
Gas Turbine T1 (GT1), then add only T1 as the Resource for the User1.
6
Select
options
Define the Role Properties for the user OPERATOR, as displayed below.
Click boxes to
select
Configuring Ports
Note All of the necessary ports should be setup before the unit leaves the factory.
In CIMPLICITY a Port defines the program and protocol used to communicate with
a device. The programs required for each port are usually included as CIMPLICITY
Project Options, such as the Mark V+ Communications option to include the Mark V
port driver (Markv_RP), and the GEDS EGD option to include the Mark VI EGD
port driver (ICN_Devcom).
Before any devices can be defined that use a port, the port must be created. Follow
the procedure displayed below to create the port before running any automation
routines that attempt to create or define devices that use the port:
Mark IV, Mark V, Mark V LM: Add a port using the MARKV protocol using the
default port name of MARKV. The description should indicate that it is for TCI
Data Dictionary devices. This will create the port Master_MarkV in the
CIMPLICITY Project.
Mark VI: Add a port using the GEDS_EGD protocol using the default port
name of ENET0. The description should indicate that it is for EGD based
devices. This will create the port Master_Enet0 in the CIMPLICITY Project.
Once the port(s) have been created the Mark V and Mark VI automation tools can be
used to add devices that use the port along with the signals from those devices. Refer
to the Add Devices section.
Note Do not create multiple instances of a port.
Right Click to
add port.
Select MARKV from the Protocol drop down list and select OK. The Port
Properties dialog box will display.
Accept Default
parameters.
Provide
Description
Accept Default
parameters
Click to Apply.
Note Create any additional ports if needed. You do not have to create MARKV
resources or devices but you will have to create resources and devices for any other
communication such as BOP.
4
Select Protocol
Accept default
Port.
Adding Devices
Configuring Resources
For most turbine applications, a CIMPLICITY resource is synonymous with a unit
name. The Mark V and Mark VI automation tools add one resource for each turbine
controller, and then add the points from the unit under the resource with that unit's
name. You should not need to create resources for turbine controls; the automation
tools should do that for you.
To configure Resources for the CIMPLICITY HMI project
1
Resources.
Select
Resources
Type in Description.
Displays Users
available for this
Resource.
Using the procedures in steps 2 and 3, add resources from T1 to T8 for GT1 to
GT8.
Alarm type or function (for example, Diagnostic, Process, Low, Medium, High).
To configure alarms for filtering in HMI servers, you need to do the
following:
Configure users
Configure resources
Note The procedures in this section require that you have a working knowledge of
CIMPLICITY, including its Workbench application, User Configuration, Resource
Configuration, and various aspects of Alarms.
Alarm
Select
Alarm
Classes.
Type in
Select
The Order value is the priority for the
Alarms that fall under that particular
class. The lower the Order number,
the higher the priority.
Select
options
You can place and configure anything in a frame that you place on a screen. The
key is to create a logical rationale for causing one frame to replace another.
A small section of the screen can be used for animation in a Frame Container.
Right click Alarms.cim in CimEdit, and then select Edit to open the following
Alarms screen. Open Frame Container from the menu, as displayed below.
2. Select
1. Select
Right click in CimEdit, and then select Edit to open the following Alarms
screen. Open Frame Container from the menu, as displayed below.
Right click in CimEdit, and then select CIMPLICITY AMV Control Object
and Properties from the menu, as displayed below. This displays the
CIMPLICITY AMV Control Properties dialog box.
1. Select
2. Select
Type in
Project and
Setup listed.
Select to apply
changes, thus
adding new
project.
Open the Alarm.cim file in CimVview and click Setup, as displayed below.
The Alarm Setup dialog box displays.
Click
Setup
Click
The Modify Setup box
then displays (see below).
Note Be sure to include the $ symbol at the beginning of the Setup name. This
makes it accessible to all users. Without the symbol, it can be accessed only by the
user account that created it.
11 Select the Classes tab, and then select DIAG from the list box.
Click Classes
tab.
Click
(Do not click
OK)
12 Select the Resources tab. Then select T1 from the list box and OK to return to
the Alarm Setups dialog box, as displayed below.
Click Resources
tab.
Select T1
Click OK
Note Typically the top alarm window is for process alarms and the bottom one for
diagnostic alarms.
$ALL
$SYSTEM
$BOP
Only two (2) screen level variables are defined an all screens.
a) UNIT Same as Unit_Control.cim, used as prefix on all point names in screen.
b) TITLE Used to display screen Title in the banner at the top of each screen.
There are no longer any procedures defined at the screen level. All procedures
have been moved to the associated button / object.
On most screens, the OnScreenOpen event and script have been eliminated. This
function is now part of the navigation template object, tp_screen.
Most screens contain only two scripts, SetUnit and SetUnit1. In most cases, the
scripts are not used, unless there is a specific need to transfer to another screen
from within the existing screen, without having a button defined on the
navigation menu (for example trend screens).
Screen Names
A screen naming convention has been developed for the screens. The screen name
will contain a prefix indicating a particular class of screen, followed by the
remainder of the name indicating the primary screen function (for example
gt7f_startup.cim). The following prefixes have been used for this release:
gt7f_ xxxxxx.cim These screens are the new 7F turbine single screens, each
representing the corresponding frame container in the old Unit_Control screen.
trend_xxxxx.cim These are basically the same captive pop-up trend screens
used with Unit_Control.cim.
alarms.cim This is the same captive pop-up alarm screen used with
Unit_Control.cim.
Smart Objects
Smart Objects have been used for many of the pushbuttons and indicators (motor,
lead/lag, start checks, trips) on the screens. Smart Objects are similar to the grouped
objects, with one important difference you dont have to navigate down into the
grouped object to modify the text and points used for descriptions, commands and
feedbacks. A Smart Object presents the user with a pop-up dialog box when the user
double clicks on the object, or pastes the object into the screen. The user then
specifies the descriptive text and point names to be used in the object. This makes
editing the object significantly faster and easier, with less chance for errors.
Note For standard grouped objects, one of the features is the ability to edit grouped
objects without having to ungroup them (and thereby losing all the top level
configuration settings).
Refer to tp_screen.cim for the Navigation Buttons and other documentation.
Banner Information
Navigation
Buttons
Alarm Window
Linked Objects
Any single object, multiple objects, or even an entire screen can be used as linked
objects. The only restriction for using an object as a linked object is that the object
must have a name defined in its Properties (General, Object name). The object is
then copied to the Clipboard, and pasted into the screen using Edit, Paste Special,
and Paste Link.
Link Source
information
This will keep Navigation pushbuttons from moving around when changing
screens.
tp_timers Contains different timer / totalizer objects. On the screen with the
linked object, set the link container object name based on turbine options.
Note When a different linked object needs to be selected in place of an existing one,
DO NOT delete the existing linked object. Just access the Link Container property
of the object, and select the new name.
Nav_Layout Worksheet
This is the main worksheet in Excel where the menu hierarchy is configured. All
configuration is done on this sheet (the others should be protected, preventing
changes). There are sample template worksheets which can be copied / renamed to
use as a guide. Note that the Excel VBA code will always use data from the
worksheet named Nav_Layout to produce the new tp_screen.cim file (new
navigation template).
navigation_template.xls
There are notes / comments in the worksheet, but the main items are the following:
Columns A-D represent the navigation levels 1-4 respectively, with Level 1
being the topmost level.
Outline view can be used to graphically display the menu levels collapsing /
opening.
Column E is used to specify the screen name to Overlay when the button is
pressed.
Column F is used to specify the screen title that is displayed at the top of the
screen.
Column H is used to specify the UNIT variable value to be used with that
screen.
Column I can be used to designate a keyboard shortcut (Hot Key) to take you to
that screen.
Make_Nav Worksheet
This worksheet is used to select a few options before the build.
To rebuild / change navigation buttons on tp_screen:
1
When complete, CimEdit will open with tp_screen loaded for review.
EM_INIT.BCL script
A CIMPLICITY script file named new_em_init.bcl is included with the screen files.
This file should be copied to the script directory of the CIMPLICITY project to be
used with the new screens. The existing em_init.bcl file should be renamed to
em_init_orig.bcl. This file should then be renamed to em_init.bcl. The em_init.bcl
file is run whenever CIMPLICITY starts up. This new script will run at project start,
and create a few CIMPLICITY points automatically if they do not exist in the
project. The script will then read the existing f:\config.dat file, and populate these
points with the configured Site name, Unit names, Unit numbers, Exciter names, and
Unit file locations. These items will then be available for use with certain items on
various screens.
EM_INIT.BCL Script
Select to move
highlighted button up or
down.
Select to Modify
highlighted buttons
properties.
Note Required data and data format can be viewed from the DOS command line by
typing SILENCE and LOCKOUT.
Setup
To enable alarms for CIMPLICITY
1
Select
applicable
After creating a new CIMPLICITY project, you must configure a CIMPLICITY Port
for the communications protocol. This enables signals to be imported into the
project. Refer to the CIMPLICITY Base System Users Manual for more information
on creating projects and configuring ports.
When the Signal Manager imports controller signals into CIMPLICITY, it
configures any needed CIMPLICITY devices and resources, if they are not already
present. For example, when importing signals for unit T1, the utility configures a
CIMPLICITY device and a CIMPLICITY resource, both called T1.
For each device that Signal Manager configures, it also configures three virtual
points needed by the MARKV_RP program. For example, for a device called T1, the
utility produces the following virtual points:
Note MARKV_RP is TCIMB function that collects data from a turbine using TCI
and forwards the information to the CIMPLICITY Point Manager.
Signals
Signal Manager displays data from the Data Dictionary, which describes the units
Control System Database (CSDB). Each row of the display displays information
about a signal, divided into columns that display the following signal attributes:
List of Signal Attributes
Signal attribute
Description
Name
Access
Read / Write
Cim Type
Description
Eng. Units
Engineering Units
Flags
High Limit
Low Limit
Offset
Precision
Scale Code
Synonym
Type
Value
You can configure the items that are listed in the above table. The display is a
standard Windows List Control, which supports the expected user-interface
commands for selecting items, sorting rows, and sizing columns.
Alarms
CIMPLICITY alarms are only placeholders that are given the appropriate parameters
at run-time when they occur. The Signal Manager can be used to configure the
alarms for Mark V, Mark V LM, and Mark VI turbine controllers, as well and other
events. The Signal Manager can also be used to configure alarms for EX2000 and
EX2100 exciters. It uses the following configuration IDs:
List of Alarm Types
Alarm use
P<n>*
Sequence of events**
SOE
Digital events**
EVENT
If the alarm class is already configured, the existing alarm class definition is
used.
Class
Definition
PRC
Process alarms
DIAG
Diagnostic alarms
HOLD
SOE
Sequence of events
EVENT
Digital events
EX2K
After these events and actions are configured, specify additional exciter fault
code points using the Exciter Fault Code box as in step 2.
Importing Signals
When the Signal Manager is started, an empty list displays.
To add signals to the Signal Manager list
1
A dialog box displays, allowing you to specify which signals to get from the
Data Dictionary.
Signal Selection
This displays a dialog box that allows you to select the .gef file for the desired
CIMPLICITY project.
You can sometimes want to populate the CIMPLICITY point database with points
from a set of screens.
Select the signals as desired and import them into the CIMPLICITY point
database using the procedures described previously.
System Database
The System Database (SDB) is a client/server Windows-based database that uses
.dbf files for storing data. Only the device that owns the topology and signal data can
put that information into the SDB. There is no separate import program.
Select the database from the Options menu, Settings option, and Database tab.
The SDB:
Can be created from the toolbox as long as the SDB server is running.
I/O points and internal signals that can be put into the database are stored in the
signal table.
Mark IV
TCI
CIMPLICITY
CIMMOD
TCI
Modbus
Slave
DCS
Mark V
& Mark
V LM
Triggered reads
Diagnostics
System Status Logs
CIMPLICITY HMI software consists of a large number of interrelated programs;
many of them run in the background as part of the CIMPLICITY project.
Background programs do not have any user interface, so they report errors and
messages to a log file. CIMPLICITY keeps two log files, the System Log File for
programs and errors that are not associated with any specific project, and a Project
Log File for programs launched by starting a CIMPLICITY project. Refer to
document GFK-1180 for more information.
.OUT and .ERR files for all CIMPLICITY HMI processes other than user
processes.
.OUT_<n> and .ERR_<n> backup files for all CIMPLICITY HMI processes
other than user.
Notes
Glossary of Terms
ActiveX
ActiveX, developed by Microsoft, is a set of rules for how applications should share
information. With ActiveX, users can ask or answer questions, use pushbuttons, and
interact in other ways with the web page or compatible program. It is not a
programming language, but rather a model for writing programs so that other
programs and the operating system can call them. ActiveX technology is used with
Microsoft Internet Explorer to make interactive web pages that look and behave
like computer programs, rather than static pages.
ActiveX control
A control (object) using ActiveX technologies to enable animation. An ActiveX
control can be automatically downloaded and executed by a web browser.
Programmers can develop ActiveX controls in a variety of languages, including C,
C++, Visual Basic, and Java. ActiveX controls have full access to the Windows
operating system.
alarm
A message notifying an operator or administrator of equipment, network, or process
problems.
Alarm Viewer
A standalone window within CIMPLICITY (an OCX control) for monitoring and
responding to alarms.
AMV
Alarm Viewer.
application
A complete, self-contained program that performs a specific function directly for the
user. Application programs are different than system programs, which control the
computer and run application programs and utilities.
ARCNET
Attached Resource Computer Network, a LAN communications protocol developed
by Datapoint Corporation. ARCNET defines the physical (coax and chip) and
datalink (token ring and board interface) layer of a 2.5 MHz communication
network.
board
Printed wiring board, or circuit board, used for electronic circuits.
Boolean
Digital statement that expresses a condition that is either True or False, also called a
discrete, or logical signal.
<C>
The turbine controllers Communicator core (processor).
CimEdit
An object-oriented graphics editor tool of CIMPLICITY HMI that functions with its
runtime viewer CimView. It can create graphical screens with animation, scripting,
colors, and a variety of graphical elements that represent power plant operation.
CIMPLICITY HMI
Computer-based operator interface software from GE Fanuc Automation,
configurable to work with a wide variety of control and data acquisition equipment.
Cimproj
The required subdirectory name for a CIMPLICITY HMI project (F:\Cimproj). The
project configuration Workbench (.gef) is located in this subdirectory.
CimView
An interactive graphical user interface of CIMPLICITY HMI used to monitor and
control power plant equipment, displaying data as text or a variety of graphic objects.
Its screens were created with CimEdit. They include a variety of interactive control
functions for setting point values, displaying other graphic screens, and initiating
custom software routines and other Windows applications.
client-server
Software architecture where one software product makes requests on another
software product. For example, an arrangement of computers with software making
one a data acquisition device and the other a data using device.
command line
The line on a computer display where the user types commands to be carried out by a
program. This is a feature of a text-based interface such as MS-DOS, as opposed to a
graphical user interface (GUI) such as Windows.
configure
Select specific options, either by editing disk files, or by setting the location of
hardware jumpers, or by loading software parameters into memory.
control system
Equipment that automatically adjusts the output voltage, frequency, MW, or reactive
power, as the case can be, of an asset in response to certain aspects of common
quality such as voltage, frequency, MW, or reactive power. Such equipment
includes, but is not limited to, speed governors and exciters.
CRC
Cyclic Redundancy Check, which is used to detect errors in data such as
transmissions or files on a disk.
CSDB
Control Signal Database, used in the turbine controller to store real time process data
used in the control calculations.
CSF
Control System Freeway, a token passing communication network, typically using
TWINAX cabling, running at 2.3 MHz.
<D>
The turbine controllers backup Communicator core (processor). (Also refer to
<C>.)
data dictionary
A system file that contains the information needed to operate a database in a database
management system. This file includes basic operating information about the records
and fields of a certain database, the limits on acceptable data values, and accessauthorization information. For the HMI, the data dictionary files contain information
about unit-specific control signal database pointnames, alarm text messages (for both
process and diagnostic alarms), and display information for signal pointnames
(type/units, messages, and such). The primary unit Data Dictionary file,
UNITDATA.DAT, can be created on an HMI in the unit-specific directory.
DCS
Distributed Control System, used for process control applications including control
of boilers and other power plant equipment.
deadband
Range of values inside of which the incoming signal can be altered without changing
the output response. The Historian uses a sophisticated deadband algorithm to decide
whether to save or discard incoming data, as part of its data compression function.
Demand Display
An HMI function that allows you to monitor several turbine data points at a time and
issue simple commands. It supports multiple units.
Devcom
Application program that serves as a communications bridge between the
CIMPLICITY HMI Point Manager and a device being monitored.
device
A configurable component of a process control system.
dynamic
An attribute emphasizing motion, change, and process as opposed to static.
EGD
Ethernet Global Data, a network protocol used by some controllers. Devices share
data through periodic EGD exchanges (pages of data).
Ethernet
LAN with a 10 or 100 megabaud data rate, used to link one or more computers
and/or controllers together. It features a collision avoidance/collision detection
system. It uses TCP/IP and I/O services layers that conform to the IEEE 802.3
standard, developed by Xerox, Digital Equipment Corporation (DEC), and Intel.
event
Discrete signal generated by a change in a status of a logic signal in a controller.
EX2000
GE generator exciter control. It regulates the generator field current to control the
generator output voltage.
fault code
A message from the controller to the HMI indicating a controller warning or failure.
firmware
Set of executable software, stored in memory chips that hold their content without
electrical power, such as EPROM or Flash memory.
filter
A program that separates data or signals in accordance with specified criteria.
forcing
Setting a signal to a particular value, regardless of the value the blockware or I/O is
writing to that signal.
frame rate
Basic scheduling rate of the controller. It encompasses one complete input-computeoutput cycle for the controller.
GSM
GE Industrial Systems Standard Messages. Application-level messages processed in
gateway to the DCS. The gateway serves as a protocol translator and can
communicate directly with several process controllers. No data is emitted from the
gateway unless previously requested by the DCS equipment.
header
Textual information, such as a title, date, name, or other applicable identifying
information, positioned at the top of a screen, column, or page, and usually repeated
at every occurrence.
Historian
A client/server-based data archival system for data collection, storage, and display of
power island and auxiliary process data.. It combines high-resolution digital event
data from the turbine controller with process analog data to create a sophisticated
tool for investigating cause-effect relationships.
HMI
Human-Machine Interface. The GE HMI is a Windows NT-based operator interface
to the turbine controllers and auxiliary power plant equipment. The HMI uses
CIMPLICITY as the operator interface, and supports the Historian Client Toolset for
viewing Historian data.
icon
A small picture intended to represent something (a file, directory, or action) in a
graphical user interface. When an icon is clicked on, some action is performed, such
as opening a directory or aborting a file transfer.
ICS
Integrated Control System. The GE ICS combines various power plant controls into
a single distributed control system.
initialize
Set values (addresses, counters, registers, and such) to a beginning value prior to the
rest of processing.
IONet
The Mark VI I/O Ethernet communication network.
LAN
Local area network (communications). A typical LAN consists of peripheral devices
and controllers contained in the same building, and often on the same floor.
logical
Statement of a true/false sense, such as a Boolean.
Mark IV
SPEEDTRONIC gas turbine controller, introduced in 1983. The first GE triple
modular redundant (TMR) control for fault-tolerant operation.
Mark V
All-digital SPEEDTRONIC gas and steam turbine controller, introduced in 1991,
available in Simplex and TMR control versions. At first equipped with a DOS-based
computer operator interface, later upgraded to use the NT-based CIMPLICITY HMI.
Mark V LM
SPEEDTRONIC gas turbine controller, introduced in 1995, designed specifically to
support the aeroderivative Dry Low Emissions (DLE) technology developed by GE
Aircraft Engines. Equipped to use the NT-based CIMPLICITY HMI.
Mark VI
VME-based SPEEDTRONIC gas and steam turbine controller, available in Simplex
and TMR control versions. Equipped to use the NT-based CIMPLICITY HMI and
Control System Toolbox.
menu
(Software.) A list from which the user can select an operation to be performed.
Modbus
Serial communication protocol, initially developed by Gould Modicon for use
between PLCs and other computers.
network
A data communication system that links two or more computers and peripheral
devices.
object
(Software.) Generally, any item that can be individually selected and manipulated.
This can include shapes and pictures that appear on a display screen, as well as less
tangible software entities. In object-oriented programming, for example, an object is
a self-contained entity that consists of both data and procedures to manipulate the
data.
OCX
OLE custom control. An independent program module that can be accessed by other
programs in a Windows environment. ActiveX (Microsofts next generation of
controls) is backward compatible OCX.
OLE
(Pronounced as separate letters.) Object linking and embedding. A compound
document standard developed by Microsoft Corporation. It enables you to create
objects with one application and then link or embed them in a second application.
Embedded objects retain their original format and links to the application that
created them. Support for OLE is built into the Windows.
OPC
OLE for Process Controls. The OPC Specification is a non-proprietary technical
specification that defines a set of standard interfaces based upon Microsofts
OLE/COM technology. The application of the OPC standard interface makes
possible interoperability between automation/control applications, field
systems/devices, and business/office applications.
OSM
Refer to On Site Monitor.
panel
The side or front of a piece of equipment on which terminations and termination
assemblies are mounted.
pc
Abbreviation for personal computer.
PDH
Refer to Plant Data Highway.
permissives
Conditions that allow advancement from one state to another.
ping
The ping utility command uses a series of Internet Control Message Protocol (ICMP)
Echo messages to troubleshoot network connectivity.
PLC
Programmable logic controller. These are designed for discrete (logic) control of
machinery, and they also compute math (analog) functions and perform regulatory
control.
plot
To draw an image by connecting a series of precisely placed points on a screen or
paper, using a series of lines.
point
Basic unit for variable information in the controller, also referred to as signal.
reactive capability
The reactive power injection or absorption capability of generating sets and other
reactive power resources such as Static Var Compensators, capacitors, and
synchronous condensers. This includes reactive power capability of a generating set
during the normal course of the generating set operations.
reboot
Restart the controller or computer after a controlled shutdown.
resources
Also known as groups. Resources are systems (devices, machines, or work stations
where work is performed) or areas where several tasks are carried out. Resource
configuration plays an important role in the CIMPLICITY system by routing alarms
to specific users and filtering the data users receive.
runtime
Refer to product code.
server
A computer that gathers data over Ethernet from plant devices, and makes the data
available to computer-based operator interfaces known as Viewers.
setpoint
Value of a controlled variable, departure from which causes a controller to operate to
reduce the error and restore the intended steady state.
signal
Basic unit for variable information in the controller, also referred to as point.
Simplex
Operation that requires only one set of control and I/O, and generally uses only one
channel.
SOE
Refer to Sequence of Events.
SRTP
Service Request Transfer Protocol. An Ethernet communications protocol for
communications between the turbine controller and the HMI.
Stagelink
ARCNET-based communication link used by many controllers.
synchroscope
Instrument for detecting whether two moving parts are synchronized.
tag
Identifying name given to a process measurement point.
TCEA
DS200TCEA Emergency Overspeed Board (TCEA), located in the controllers
Protective Core <P1>, is used for the high-speed protection circuitry. It is often
referred to as the Protective Processor. The three TCEA boards used in the <P1>
core are referred to as the <X>, <Y>, and <Z> processors. These boards scale and
condition input for high and low shaft speed, flame detection, and automatic
synchronization. They then output the signals via the TCEA (location 1) board over
the IONET to the <R1> cores DS200STCA board. The TCEAs send emergency trip
signals to the Turbine Trip Board (DS200TCTG). Each TCEA has its own power
supply and power supply diagnostics.
TCI
Turbine Control Interface. The GE-supplied software package on the HMI that
interfaces to the turbine control.
TCP/IP
Communications protocols developed to inter-network dissimilar systems. It is a de
facto UNIX standard, but is supported on almost all systems. TCP controls data
transfer and IP provides the routing for functions, such as file transfer and e-mail.
timetag
Information added to data to indicate the time at which it was collected. Also called a
time stamp.
TMR
Triple Modular Redundancy. This is an architecture that uses three identical sets of
control and I/O, and votes the results to obtain highly reliable output signals.
trend
Time-based screen plot showing the history of process values, available in the
Historian, HMI, and the Control System Toolbox.
trigger
Transition in a discrete signal from 0 to 1, or from 1 to 0, initiating an action or
sequence.
UTC
Coordinated Universal Time, an international time-reference standard.
utility
A small helper program that performs a specific task, usually related to managing
system resources. Utilities differ from applications mostly in terms of size,
complexity, and function.
VLAN
Virtual Local Area Network. A scheme whereby a single network switch can support
multiple separate networks (such as UDH, PDH, and ADH). All networks configured
on the switch share a single switch-to-switch trunk port connection.
web browser
Computer software, such as Microsoft Internet Explorer or Netscape Navigator,
allowing screens and data to be viewed over a network from a server.
Windows NT
Advanced 32-bit operating system from Microsoft Corporation for 386-based PCs
and above.
Workbench
A CIMPLICITY HMI program used to view, configure, organize, and manage every
component of a CIMPLICITY project through a single window.
Index
A
ActiveX, G-1
applications, 8-1
control, 8-1, 8-3, G-1
objects, 8-1, 8-6
alarms, 4-2, 4-31, 6-81, 8-30, 8-42
Alarm Logger Control, 6-10
Alarm Viewer, 8-12, 8-20, 8-36, 8-39, G-1
AMV, 8-25, 8-39, G-1
diagnostic,6-158, 6-170,
display, 6-158, 6-170
Extended Alarm Commands, 8-1, 8-39,
Lock, 6-167, 8-39
Lockout, 4-45, 6-107, 6-108, 6-109, 6-110, 6-166,
8-1, 8-39,
Silence, 6-130, 8-1, 8-39
Unlock, 6-167, 8-39
External Alarm Manager, 8-9, 8-40
filtered alarms, 8-30
filtering, 8-9, 8-20, 8-21
Hold List,4-4, 6-130, 6-156, 8-42,
process, 4-39, 4-44, 6-9,
animation, 8-23, 8-40, G-1
B
Balance of Plant (BOP), 1-1, 6-8, G-1
Boolean, 6-84, 8-41, G-2
breaker (see circuit breaker)
C
CimEdit, 8-1, 8-23, G-2
CIMPLICITY,
configuration, 8-9
diagnostics, 8-47
directories, 6-1
Modbus Master, 6-8
overview, 8-1
project, 2-3
Cimproj, 2-3, 6-2, 6-3, 6-31, 6-46, 8-9, 8-49, G-2
CimView, 2-1, G-2
.cim files, 2-1, 8-23, 8-27, 8-32,
circuit breaker, G-2
client-server, 1-1, G-2
command line
arguments, 4-10
Control Constant, 4-12
CONSTCHK, 4-15
DABUILD, 4-31
description, 4-30
DIAGC, 4-17
Invalid Unit, 4-10
EEPROM, 4-6
format, 4-2, 4-4
parameters, 3-1
SEQCOMPL command, 4-5
communications
Mark IV, 6-4
Ethernet, 7-16, 7-20
Modbus, 6-6, 6-8
TCI, 6-35
Control Signal Database (CSDB), 1-2,4-1
Control System Freeway (CSF), 7-1
control system toolbox, 4-77, 5-1, 5-3, 6-7, 6-22,
6-44, 6-81, 6-173, 8-40, 8-45
Trend Recorder, 5-2
controllers
Mark IV, 3-1,6-4, 6-81
Mark V, 4-1, 4-31, 4-67, 6-11, 6-89, 6-106, 6-115
Mark V LM, 4-32, 4-42, 4-70, 4-73, 6-15, 6-89, 6-96
Mark VI, 1-1, 5-1, 6-37, 6-79, 6-89, 6-98, 7-1, 7-18
D
Data Dictionary
creating, 6-69
DDVAL, 3-1
DDLOCATE, 4-35
DDUTIL, 4-38
WPBROXD, 6-176
Demand Display
editing, 4-5
starting, 6-27
WDEMAND, 6-163
Display
Manual Synchronizing, 4-45, 8-2, 8-6
Reactive Capability, 8-8
Distributed Control System (DCS), 4-44, 6-8, 6-42, 7-1
DOS commands (see command line)
Dynamic Rung Display,6-37,
E
Ethernet, 7-16, 7-20
Ethernet Global Data (EGD), 6-119
VIEWEGD, 6-144
EX2000, 6-48
alarms, 8-42
Exciter Configuration File, 6-80
Index 1
G
GE Standard Messages (GSM), 6-9
H
Historian, 1-2, 4-4, 5-2, 6-4, 6-8
Human-Machine Interface (HMI), 1-1, G-5
I
Integrated Control System (ICS), G-5
M
Modbus, 6-6, 6-8, 6-28, 6-29, 6-30, 6-41, 6-134, 8-46
N
network
configuration, 7-21
diagnostics, 7-23
equipment, 7-20
overview, 7-1,
redundancy, 7-18
rules, 7-18
serial link, 7-20
O
OCX, 8-20, G-1, G-6
OLE, 8-1, 8-46, G-7
OPC, 8-46, G-7
P
permissives, 4-9, 4-11, 4-21, 8-2, 8-4
Plant Data Highway (PDH), 1-1, 6-88, 7-17
points, 1-2, 3-2, 4-2
Programmable Logic Controller (PLC), 6-43, G-7
projects, 8-9, 8-26
R
Reactive Capability Display, 8-8
requisition, 4-17, 6-7, 6-81, 6-99
Resource Definition, 8-18
resources
configuring, 8-17
Role Properties, 8-14
rungs, 4-5, 4-40, 4-49, 4-56
2 Index
T
TCP/IP, 7-17, 7-18, G-4
timetag, 4-19, 6-13, 6-121, G-9
toolbox (see Control System Toolbox)
trend, 5-1, 8-32, 8-33, G-9
Recorder, 5-2
Trip History, 6-22
Triggered Plot, 8-1, 8-6, 8-7
Triple Modular Redundancy (TMR), 4-14, 4-15, 4-70
Turbine Control Interface (TCI), 1-1, 4-8, 6-35, 6-38
U
Unit Data Highway (UDH), 1-1, 1-2, 5-2, 5-3, 7-17
User
configuring, 8-12
usernames and passwords, 2-3
UDF, 4-70
WAUTHEN, 6-161
V
valve travel, 8-6
W
web, 6-156 to 6-166
displays, 6-156
server homepage, 6-111
server installation, 6-114
WALMDUMP, 6-158
WANETC, 6-159
WARCWHO, 6-160
WAUTHEN, 6-161
WCONST, 6-161
WDEMAND, 6-163
WGBL, 6-165
WHAERPT, 6-166
Workbench, 6-30, 8-9
GE Energy
1501 Roanoke Blvd.
Salem, VA 24153-6492 USA
1 540 387 7000
www.geenergy.com