GEH-6808 ControlST Software Suite

GEH-6808N
ControlST* Software Suite

How-to Guides
June 2019
Non-Public Information
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.
Non-Public Information – This document contains proprietary information that belongs to the General Electric Company
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 or the information it contains shall not be copied or reproduced in whole or in part or
disclosed to any third party without the express written consent of GE.
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.
For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE Sales
Representative.
Revised: June 2019

Issued: June 2013
© 2013 - 2019 General Electric Company.

___________________________________
* Indicates a trademark of General Electric Company and/or its subsidiaries.
All other trademarks are the property of their respective owners.
We would appreciate your feedback about our documentation.

Please send comments or suggestions to controls.doc@ge.com
Document Updates
Rev Location Description
N Install Adobe Reader 11.0 or Later Updated the Adobe Reader installation .exe file name to be more general
How to Disable Network Services and Modify
Passwords in Mark* VI and Mark VIe Generation
M Added UCSC controller serial connection details and baud rate settings
Controllers,
Re-enable Network Services
How to Order ControlST Software and License Added some example prices in the section ControlST Versions, Part Numbers,
Keys and Cost
L
Replaced various screenshots throughout the chapter to show the correct
How to Configure Time Synchronization
settings for NTP Primary/Secondary Time Source Preferred Network
Updated reference to most current ControlST release version to V07.00.00 and
ControlST version license key part number to ST70GE (+ KEY M5 AC hardware
key)
In the section Ordering Procedure, updated the table Hardware and Software
Keys to include the M5 key and provide a note that the White key and Solution
Provide key (Siebel part numbers) are no longer available as of April 7, 2017
In the section ControlST Versions, Part Numbers, and Cost:
How to Order ControlST Software and License
• Updated the tables with a note that the Siebel part numbers are no longer
K Keys available as of April 7, 2017 and greyed out this column in each relevant
table
• Replaced the table Latest Version V05.xx or Higher) with the table
ControlST V07.00.xx
• Added Remote Desktop Connections (Terminal Services) for ControlST
Options to the table ControlST V07.00.xx
• Updated the ControlST V06.1 to V06.2; V06.1 is no longer being sold. Also
updated associated PNs
How Set Up IEC 60870 Protocol Data Links Removed this section; GE no longer maintains the Triangle Microworks tools
How to Order ControlST Software and License
J Updated the license key ordering procedure overview
Keys
How to Configure the Alarm Scanner Feature of
Added a Note stating that the Alarm condition name for an Analog Alarm variable
the WorkstationST Alarm Server, the section
values displays in the Alarm State column in Alarm Viewer.
Configure EGD Produced Data
How to Set Up and Download to Mark VIe and
Moved these procedures to GEH-6721_Vol_II System Guide
H Mark VIeS UCSB Controllers and I/O Modules
How to Set Up and Download to Legacy Mark VIe
Moved the procedure for setting up the UCSA to GEH-6721_Vol_II System Guide
and Mark VIeS Controllers
How to Qualify FOUNDATION Fieldbus Field Devices Updated references
Configuration Management System This chapter has been moved to GEH-6700 ToolboxST User Guide
Updated information, added reference to ControlST Computer Compatibility, and
How to Link a ToolboxST Block to an HMI Block
fixed text error
Added this section with a history of GE’s software file integrity verification tool
How to Verify Software File Integrity Verification
G improvements and the procedures to verify files using each tool
How to Order ControlST Software and License Added this section containing procedures to order software media and license
Keys keys
Configuration Management System Updated this entire chapter to describe the improvements in CMS functionality
Instruction Guide GEH-6808N 3

Acronyms and Abbreviations
ASCII America Standard Code for Information Interchange RLD Relay Ladder Diagram
ASK Automatic Station Keeping RTD Resistance Temperature Device
AWG American Wire Gauge RTU Remote Terminal Unit
BoP Balance of Plant SEM Subsea Electronics Module
BOP Blowout Protector SIFT Software Implemented Fault Tolerance
CDH Control Data Highway SOE Sequence of Events
CMOS Complementary Metal-Oxide Semiconductor SRS Signal Reference Structure
COI Computer Operator Interface TMR Triple Modular Redundancy
CPCI CompactPCI 6U high enclosure TTL Transistor-transistor Logic
CRC Cyclic Redundancy Code/Check UDH Unit Data Highway
DAC Digital-to-Analog Converter UDP User Datagram Protocol
DCE Data Communication Equipment uOSM Universal Onsite Monitor
DCS Distributed Control System UPS Uninterruptible Power Supply
DHCP Dynamic Host Configuration Protocol UTC Coordinated Universal Time
DRAM Dynamic Random Access Memory VLAN Virtual Local Area Network
DTE Data Terminal Equipment device WAN Wide Area Network
EGD Ethernet Global Data
EMC Electromagnetic Capability
EMI Electromagnetic Interference
ERA Electrical Riser Angle
FE Functional Earth
FTD Flow Totalizer Display (OTEK)
FTI Flow Totalizer Input (XMT868i Panametrics Ultrasonic Flow Transmitter)
GPS Global Position System
GSM GE Standard Messaging
GTS Global Time Source
HMI Human-machine Interface
HRSG Heat Recovery Steam Generator
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers
KP Keyphasor*
LAN Local Area Network
MPU Magnetic Pickup
MTBF Mean Time Between Failures
MTBFO Mean Time Between Forced Outage
MTTR Mean Time To Repair
NEMA® National Electrical Manufacturer’s Association
NFPA National Fire Protection Association
NTP Network Time Protocol
NVRAM Non-volatile Random Access Memory
OPC Standard for data exchange in the industrial environment
PDH Plant Data Highway
PDM Power Distribution Module
PE Protective Earth
PLC Programmable Logic Controller
PMC PCI Mezzanine Card
4 GEH-6808N ControlST Software Suite How-To Guides

Related Documents
Doc # Title
GEH-6700 ToolboxST* User Guide for Mark VIe Control
GEI-100620 WorkstationST* Alarm Viewer Instruction Guide
GEI-100621 WorkstationST OPC® DA Server
GEI-100623 WorkstationST Service Instruction Guide
GEI-100624 WorkstationST OPC AE Server
GEI-100626 WorkstationST Alarm Server Instruction Guide
GEI-100627 WorkstationST Recorder User Guide
GEI-100628 WorkstationST Historian
GEI-100629 WorkstationST HMI Configuration
GEI-100661 WorkstationST Web View Instruction Guide
GEI-100693 WorkstationST Network Monitor Instruction Guide
GEI-100696 WorkstationST Modbus®
GEI-100697 WorkstationST/CIMPLICITY* Advanced Viewer Integration Instruction Guide
GEI-100757 WorkstationST Device Manager Gateway Instruction Guide
GEI-100795 Trender Instruction Guide
GEI-100828 WorkstationST OPC UA Server Instruction Guide
GEI-100829 WorkstationST Application Mark V Feature GSM Server
Instruction Guide GEH-6808N 5

Safety Symbol Legend
Indicates a procedure or condition that, if not strictly observed, could result in

personal injury or death.
Warning
Indicates a procedure or condition that, if not strictly observed, could result in damage
to or destruction of equipment.
Caution
Indicates a procedure or condition that should be strictly followed to improve these

applications.
Attention
Control System Warnings
To prevent personal injury or damage to equipment, follow all equipment safety

procedures, Lockout Tagout (LOTO), and site safety procedures as indicated by
Employee Health and Safety (EHS) guidelines.
Warning
This equipment contains a potential hazard of electric shock, burn, or death. Only
personnel who are adequately trained and thoroughly familiar with the equipment
and the instructions should install, operate, or maintain this equipment.
Warning
Isolation of test equipment from the equipment under test presents potential electrical
hazards. If the test equipment cannot be grounded to the equipment under test, the
test equipment’s case must be shielded to prevent contact by personnel.
To minimize hazard of electrical shock or burn, approved grounding practices and

Warning procedures must be strictly followed.
To prevent personal injury or equipment damage caused by equipment malfunction,

only adequately trained personnel should modify any programmable machine.
Warning
Always ensure that applicable standards and regulations are followed and only
properly certified equipment is used as a critical component of a safety system. Never
assume that the Human-machine Interface (HMI) or the operator will close a safety
critical control loop.
Warning
Contents
1 Introduction ..................................................................................................................................... 11
2 ToolboxST Application.................................................................................................................. 13
2.1 How to Configure Alarm Capability in the ToolboxST* Application................................................................ 13
2.2 How to Configure Time Synchronization in the ToolboxST* Application ......................................................... 38
2.3 How to Use the Mark* VIe Tools in the Simulink™ Environment................................................................... 51
2.4 How to Qualify a Foundation Fieldbus Field Device..................................................................................... 76
2.5 How to Test the TMR Capability of the Mark* VIe Control Using the ToolboxST Application ............................. 96
2.6 How to Shelve and Place Alarms Out of Service ........................................................................................109
2.7 How to Configure Alarm Parent Child ......................................................................................................119
2.8 How to Configure Mark* VIe Controller Frame State Timeouts.....................................................................123
2.9 How to Upgrade a BPPB-based I/O Module to a BPPC-based I/O Module.......................................................126
2.10 How to Configure Mark* VIe Control I/O Modules for Expansion in an EX2100e Excitation Control ..................127
3 WorkstationST Application ........................................................................................................141
3.1 How to Interface to Third-party Clients Using the WorkstationST* OPC® DA Server ........................................141
3.2 How to Configure and Troubleshoot a Trip Log in the WorkstationST* Application ..........................................151
3.3 How to Configure the Alarm Server in the WorkstationST* Application..........................................................159
3.4 How to Configure the Alarm Scanner Feature of the WorkstationST* Alarm Server ..........................................168
3.5 How to Analyze Historical Alarm Data Using the WorkstationST* Alarm Viewer - Online Mode ........................182
3.6 How to Analyze Historical Alarm Data Using the WorkstationST* Alarm Viewer - Offline Mode ........................194
3.7 How to Filter Live and Historical Alarms Using the WorkstationST Alarm Viewer ............................................201
3.8 How to Set Up Alarm and Diagnostics Help for use in the WorkstationST* Alarm Viewer..................................215
3.9 How to Configure OPC® AE Capability ....................................................................................................224
3.10 How To Export Alarm Data for Rationalization ..........................................................................................238
4 Human-machine Interface ..........................................................................................................241
4.1 How to Enable Adobe® PDF Full Text Search for ControlST* Documentation .................................................241
4.2 How to Display a Variable on an Human-machine Interface Screen ................................................................248
4.3 How to Configure a Second Language for ControlST* HMI Applications........................................................254
4.4 How to Troubleshoot a CIMPLICITY* Project...........................................................................................268
4.5 How to Define a Measurement System for Use by ControlST* HMI Applications .............................................272
4.6 How to Link a ToolboxST* Block to an HMI Block ....................................................................................278
4.7 How to Set Up the HMI Master Screens Copy Functions ..............................................................................280
4.8 How to Create CIMPLICITY* Screens .....................................................................................................282
4.9 How to Integrate CIMPLICITY* 6.1 HMI with the WorkstationST* Application ..............................................290
4.10 How to Change the IP Address for an Allied Telesis™ 8516/8624 Network Switch ...........................................298
4.11 How to Configure an Alias for ControlST* HMI Applications.......................................................................312
4.12 How to Install and Replace the Linksys™ SFE2000 Network Switch..............................................................319
5 Renewable Energy .......................................................................................................................335
5.1 How to Set Up the Dynamic Data Recorder (DDR) and Trender for Wind Farms ..............................................335
5.2 How to Configure a Wind Turbine ESS Doubly Fed Induction Generator Control .............................................357
5.3 How to Configure a Solar Power Inverter ..................................................................................................360
6 Legacy Support.............................................................................................................................365
6.1 How to Set Up and Download to Legacy Mark VIe and Mark VIeS Controllers ................................................365
6.2 How to Download the IP Address for a Mark* VI Controller Using the Control System Solutions (toolbox)
Application................................................................................................................................375

6.3 How to Import Control System Solutions (toolbox) Turbine Historian Configurations to the WorkstationST*
Historian Feature ........................................................................................................................377
6.4 How to Import Control System Solutions (toolbox) Data Historian Configurations to the WorkstationST*
Recorder Feature ........................................................................................................................384
6.5 How to Configure the ToolboxST* Application to Receive Mark* VI Data from a Control System Solutions
(toolbox) Application ..................................................................................................................390
6.6 How to Convert a Mark* V Component for Use in ControlST* Applications....................................................397
6.7 How to Import Control System Solutions (toolbox) Network Interface Configurations to a ToolboxST* External
Device ......................................................................................................................................420
6.8 How To Test the TMR Capability of the Mark* VI Control using the Control System Toolbox ...........................428
7 Miscellaneous Procedures ........................................................................................................447
7.1 How to Verify Software File Integrity .......................................................................................................447
7.2 How to Order ControlST* Software Media and License Keys .......................................................................455
7.3 How to Set Up the Remote Services Gateway ............................................................................................469
7.4 How to Set Up the ExperTune® PlantTriage Control Loop Monitoring System .................................................497
7.5 How to Set Up and Tune a Control Loop With ExperTune® OPC® PID Tuner ..................................................507
7.6 How to Disable Network Services and Modify Passwords in Mark* VI and Mark VIe Generation
Controllers ................................................................................................................................540
7.7 How to Set Up a Remote ExperTune® PlantTriage Tuning Server ..................................................................553
7.8 How To Use the ExperTune® PlantTriage Control Loop Monitoring System ....................................................587
7.9 How To Use Norton Ghost™ 9 to Backup and Restore Hard Disk Drives .........................................................604
7.10 How to Use Norton Ghost™ 10 to Backup and Restore Hard Disk Drives ........................................................608
7.11 How to Use Norton Ghost™ 2003 to Backup and Restore Hard Disk Drives .....................................................629
7.12 How to Use Acronis® True Image Home to Backup and Restore RAID1 and Non-RAID1 Hard Disk
Drives ......................................................................................................................................633
GEH-6808N Instruction Guide 9

Notes

1 Introduction
The ControlST* Software Suite includes several high-performance tools, including the ToolboxST* configuration and
diagnostic application, the WorkstationST* application for managing the Human-machine Interface (HMI), Historian, Alarm
Viewer, and Trender, and other tools used for efficient plant-wide communications, monitoring, and asset management. This
document includes a collection of How-to Guides that provides helpful instructions for Mark* control system operation,
configuration, maintenance, and more.
Introduction GEH-6808N Instruction Guide 11

Notes

2 ToolboxST Application
2.1 How to Configure Alarm Capability in the ToolboxST*
Application
assume that the HMI or the operator will close a safety critical control loop.
Warning
This document provides information necessary to create an alarm from either an analog or a Boolean variable. The
ToolboxST application is used to configure alarm functions. The WorkstationST* Alarm Server collects alarm and event data
from configured components and makes the data available to alarm clients (such as Alarm Viewers). The WorkstationST
Alarm Viewer is used to manage and display alarms in an active control system.
The following procedures are included:
• Open the System Information Editor

• Add an alarm block template
• Configure automatic alias names for a template
• Edit alarm classes
• Add an alarm definition
• Edit alarm definitions
• Display analog alarm default alarm definitions
• Configure alarm inhibit groups
• Edit sounds
• Edit alarm state definitions
• Edit alarm symbols
• Configure sort method for alarm symbols
• Configure an alarm for a Boolean variable
• Assign an alarm to an EGD page
• Configure an alarm for an analog variable
• Assign the L and H limits to a variable
• Enable Alarm Shelving and Alarm Out-of-service features
• Enable Alarm Parent Child
ToolboxST Application GEH-6808N Instruction Guide 13

Refer to the following documents for further information:
• ToolboxST User Guide for Mark* Controls Platform (GEH-6700)

• WorkstationST Alarm Viewer (GEI-100620)
• WorkstationST Alarm Server (GEI-100626)
• WorkstationST CIMPLICITY* Advanced Viewer Integration (GEI-100697)
• The section, How to Configure a Second Language for ControlST HMI Applications in this manual
• The section, How to Shelve and Place Alarms Out-of-service in this manual
The System Information Editor edits alarm classes, format specifications, and other items available to all components in the
system. If access to a System Database (SDB) is enabled, the contents of the System Information Editor can be stored to the
SDB.
➢ To open the System Information Editor: from the System Editor Edit menu, select System Information.
2.1.1 Alarm Block Templates

Alarm Block Templates are used in conjunction with the ANALOG_ALARM block in certain controller configurations. The
ANALOG_ALARM block provides analog alarm documentation defined in application code; it also allows automatic
configuration of the Alias properties of each alarm associated with the analog alarm. Refer to the Mark VIe Control Standard
Block Library Instruction Guide (GEI-100682) for additional information.

➢ To add an Alarm Block Template
1. From the System Information Editor Tree View, right-click Alarm Block Templates.
2. From the shortcut menu, select Add Alarm Block Template.
➢ To configure automatic alias names for a template

1. From the Tree View, select the alarm block template.
2. From the Tree View, expand the template and select Attributes.
3. Define any attributes needed for the Alias properties. Typically, these attributes will have Prompt For Input set to
True.

2.1.2 Alarm Classes
Alarm classes are groups or collections of related alarms that share a common priority and color scheme.
➢ To edit Alarm Classes: from the System Information Editor Tree View, select Alarm Classes. A data grid with
the existing Alarm Classes displays in the Summary View.
Tip � The columns displayed in the Summary View can be selected and rearranged by right-clicking in the header row and
selecting Organize Columns.

Alarm class properties include:
Ack Background Color shows background color for an alarm in the Acknowledged state.
Ack Foreground Color shows foreground color for an alarm in the Acknowledged state.
Alarm Background Color displays the background color for an alarm in the Alarm state.
Alarm Foreground Color displays the foreground color for an alarm in the Alarm state.
Blink Background Color displays the background color for the blink state of the active unacknowledged alarm.
Blink Enabled, if set to True, enables blinking ability.
Blink Foreground Color displays the foreground color for the blink state of the active unacknowledged alarm.
Normal Background Color displays the background color for an alarm in the Normal state.
Normal Foreground Color displays the foreground color for an alarm in the Normal state.
Description displays the description in the primary language (English).
Name displays the name of the Alarm Class. Limited to five characters if using an SDB.
Priority is the alarm class priority (1 to 99, where 1 is the highest priority).
Sound Reference is the sound definition to select when an active alarm displays in the Alarm Viewer.
Symbol is the symbol displayed for a particular alarm class (read-only).

2.1.3 Alarm Definitions
The alarm definitions item contains one or more sets of user defined analog alarm definitions. The Analog Alarm Default
definition (described in next section) is used as a template when creating a new alarm definition. Alarm definitions provide a
template of the analog alarm parameters and their properties. When an analog alarm is created in a component, these values
are used to configure analog alarm parameters.
➢ To add an alarm definition
Note The Second Language Alarm Descriptions must be entered and saved at this point for them to display in all other
locations when code is instanced. Refer to the section, How to Configure a Second Language for ControlST HMI Applications
in this manual for additional information.
Note The Alarm Description must contain the substitution string $Desc and the Second Language Alarm Description must
contain the substitution string $2ndDesc.

➢ To edit alarm definitions: from the Tree View, expand Definitions and select an alarm definition (such as
alarmNew).
Note The Second Alarm State (second language names) must be entered and saved at this point for them to display in all
other locations when code is instanced. Refer to the section, How to Configure a Second Language for ControlST HMI
Applications in this manual for additional information.
Columns include:
Alarm Parameter is the name of the alarm (read-only).
Alarm State is the parameter state. This is the property configured in the Alarm State Definition (read-only).
Second Alarm State is the alarm state for the second language, configured in the Alarm State Definitions (read-only).
Alarm Description is the parameter description for this alarm.
Second Language Alarm Description is the second language parameter description for this alarm.
Alarm Class is the class associated with the alarm parameter.

2.1.4 Analog Alarm Default
The Analog Alarm Default item displays the set of analog alarm definitions (states) that are available for each analog alarm
defined in the system. The names of the analog alarm definitions are used when the actual alarm variable is defined for use
when configuring a device.
➢ To display the analog alarm default alarm definitions
locations when code is instanced. Refer to the section, How to Configure a Second Language for ControlST HMI Applications
in this manual for additional information.
Note Additional analog alarm definition sets can be created to override the default assignments. The Analog Alarm Default
is used as the source when new analog alarm definitions are created. Refer to the procedure To add an alarm definition.

2.1.5 Alarm Inhibit Groups
The Alarm Inhibit Groups feature uses standard blockware to suppress the generation of alarms in the controller. It also
removes the suppressed alarm from the alarm queue (if present), and from all alarm displays in the control system.
➢ To configure alarm inhibit groups

2.1.6 Sounds
Use the System Information Editor to define sound options that can annunciate certain sounds within the Alarm Viewer. A
specific sound definition is assigned to an alarm class.
➢ To edit sounds
When a sound is selected in the Data Grid, properties include:

Delay displays the time lapse between sounds (from 100 to 10,000 ms). The Repeat Quantity property must be 1 or more.
Duration displays the sound’s duration (from 100 to 10,000 ms).
Frequency displays the sound’s frequency (range is 100 to 500 Hz).
Name is the sound’s name.
Repeat Quantity displays the number of times the sound is repeated.
Sound Type displays the type of sound annunciated. The options are Tone, Wave File, and Text to Speech.
Wave File, if selected as the Sound Type, displays the name of the Wave File. When the system information is saved, the
wave files are published to the Master WorkstationST computer.

2.1.7 Alarm State Definitions
Alarm state definitions are user-defined descriptions for analog alarm parameters.
➢ To edit alarm state definitions: from the Tree View, select State Definitions. Available parameters display in the
Data Grid.
Columns include:
Alarm Parameter is the parameter for the alarm state values being entered.
Alarm State is the description that displays in the Alarm Viewer.
Second Alarm State is the second language description that displays in the Alarm Viewer.
Note The Second Alarm State must be entered and saved at this point for it to display in all other locations when code is
instanced. Refer to the section, How to Configure a Second Language for ControlST HMI Applications in this manual.
2.1.8 Alarm Symbols

Alarm symbols can be associated with an alarm class and feature. The symbol, using the same alarm color and priority
configuration, displays in the Alarm Viewer and on CIMPLICITY* screens. Only one symbol can be associated with an alarm
class; however, the same symbol can be used by multiple alarm classes.
➢ To edit alarm symbols: from the Tree View, select Symbols.

2.1.8.1 Sort Alarm Symbols
➢ To configure sort method for alarm symbols
1. From the Tree View, select Symbols.
2. From the Property Editor, select either Option 1 or Option 2.
Option 1 (Alarm State, Priority, Acknowledgement State) includes:
• Priority 1 Active Unacknowledged

• Priority 1 Active Acknowledged
• Priority 1 Normal Unacknowledged
• Priority 1 Normal Acknowledged
Option 2 (Acknowledgement State, Alarm State, Priority) includes:

2.1.9 Alarm Configuration

Alarms can be configured from Boolean or Analog variables. For displaying alarm values on CIMPLICITY, the boolean
alarms and the analog alarm variable are assigned to Ethernet Global Data (EGD). For analog alarms, only the analog variable
is put on EGD, not the individual alarms.

2.1.9.1 Configure a Boolean Alarm in a Controller
➢ To configure an alarm for a Boolean variable
1. From the System Editor, double-click a controller to display the Component Editor.

Note A description of each property is displayed when selected.
Tip � All alarm properties (such as Alarm, Alarm Class, and Alarm On Zero) can be configured from the Property Editor or
the Summary View.
2. When the configuration is complete, Build, Download, and Save the controller.
The alarm displays on the WorkstationST Alarm Viewer as an active alarm when the variable is true, and as an inactive alarm
when the variable is false. The display color is controlled by the alarm class assigned to the boolean alarm variable. To use the
alarm variable on a CIMPLICITY* screen, it must be assigned to an EGD page. If the Enable Process Alarms property for the
OPC DA server is set to True, an alarm variable's attributes (for example, G1.MyAlarm.AlarmActive) can be used on a
CIMPLICITY screen even if the alarm variable is not assigned to an EGD page.
➢ To assign an alarm to an EGD page
2.1.9.2 Configure an Analog Variable Alarm
Note The information in this section represents a simplified example of the fundamental steps necessary to create and
configure an analog variable alarm. The instructions are designed to guide a qualified user, not as a training guide for new
personnel.
The following procedures create an alarm that displays on the WorkstationST Alarm Viewer as an H (Hi) alarm when the
output of a function generator is greater than 70. The alarm is in the Normal condition when the value is between 70 and 30
and an L (Lo) alarm displays when the value is less than 30.
Note With the release of ControlST V04.06 the rate of change alarm for analog alarms is only allowed if the alarm variable
data type is Real (single precision floating point) or LReal (double precision floating point). It is recommended that this
limitation also be followed in earlier versions. Refer to the ControlST Software Suite Upgrade Instruction Guide
(GEI-100694), the section Known Issues for additional information.

➢ To configure an alarm for an analog variable

Note A description of each property is displayed when selected.

The FUNGEN Library Block
displays in the worksheet.
Right-click inside the block and

select Edit Block Pins .
.
The Edit Block Pins dialog
box displays.
Note This enables an analog signal that is a triangle waveform that ramps up from 0 to 100 in 10 seconds, then ramps down
from 100 to 0 in 10 seconds.
Right-click OUTPUT , and

select OUTPUT Pin and
Edit Pin Connection.
The Connect Pin dialog

box displays.

The analog alarm displays on the WorkstationST Alarm Viewer as the current highest active alarm level, and as an inactive
alarm when no alarm levels are active. The display color for each analog level alarm is controlled by the alarm class assigned
to that level. To use the analog alarm variable, or any of the level boolean variables on a CIMPLICITY screen, the variables
must be assigned to an EGD page.
The L and H limits for the variable can now be assigned. This can be done from either the Property Editor or the Summary
View.
➢ To assign the L and H limits to a variable

From the Summary
View , select the
TestAnalog.L_SP
variable and set the
Initial Value to 30 .
Select the
TestAnalog.H_SP
variable and set the
Initial Value to 70 .
Analog Alarm Variables
Alarm Type Variable Extension Description Enter Initial Value?

Bad quality .BQ Signal bad quality No - Boolean
Deviation High .DH Deviation alarm No - Boolean

.DH_C Deviation alarm compare Yes
.DH_SP value
.DH_T Deviation alarm set point Yes
.DH_Y Deviation alarm delay time Yes
Deviation alarm hysteresis Yes
High .H High level alarm No - Boolean

.H_SP High level alarm set point Yes
.H_T High level alarm delay time Yes
High High .HH High High level alarm No - Boolean

.HH_SP High High level alarm set Yes
.HH_T point
High High level alarm delay Yes
time
High High High .HHH High High High level alarm No - Boolean
.HHH_SP High High High level alarm Yes
.HHH_T set point
High High High level alarm Yes
delay time
Low .L Low level alarm No - Boolean

.L_SP Low level alarm set point Yes
.L_T Low level alarm delay time Yes
Low Low .LL Low Low level alarm No - Boolean

.LL_SP Low Low level alarm set Yes
.LL_T point
Low Low level alarm delay Yes
time
Low Low Low .LLL Low Low Low level alarm No - Boolean
.LLL_SP Low Low Low level alarm set Yes
.LLLL_T point
Low Low Low level alarm Yes
delay time

Analog Alarm Variables (continued)
Alarm Type Variable Extension Description Enter Initial Value?

Level Alarm Hysteresis .HYST Level alarm hysteresis value Yes
Rate of Change High .RH Rate of Change alarm No - Boolean

..RH_SP Rate of Change alarm Yes
.RH_T setpoint
.RH_Y Rate of Change alarm time Yes
delay
Rate of Change alarm Yes
hysteresis
Note Do not set the hysteresis to a negative (-) value.
Note Use the same steps to configure alarms for any analog variable.
Deviation High Alarm (DH):

The Compare value (DH_C) is a base value at which we want to track the analog variable value. The Setpoint (DH_SP) is the
amount of deviation allowed.
Example: Assuming we want to track the variable value between 50±10 (40 to 60 range) we would set DH_C = 50 and DH_
SP = 10. The alarm will be active if the variable value is greater than or equal to 60 or less than or equal to 40.
Rate of Change High Alarm (RH):
If the rate of change of the analog variable is greater than or equal to the Setpoint value (RH_SP), an alarm will be active. The
rate at which the variable increases or decreases is in units/second.

The following figure shows an example of Level Alarm States with Hysteresis (.HYST) and Time Delay (.*_T).


2.1.9.3 Enable Alarm Shelving and Out-of-service
➢ To enable the alarm shelving and alarm out-of-service
For alarm shelving, there are two properties for each variable that must also be configured in the Component Editor:
Alarm Shelving must be set to Enabled before shelving will be allowed on that variable.
Alarm Shelving Max Duration is the maximum time in minutes that the alarm can be shelved.
Note Refer to the section, How to Shelve and Place Alarms Out-of-service for additional information.

2.1.9.4 Enable Alarm Parent Child
Note For detailed information, refer to the section How to Configure Alarm Parent Child in this manual.
➢ To enable the alarm parent child feature: open the System Editor , from the Tree View, select the system item,
and in the Property Editor, set the Alarm Parent Child property to True.

2.2 How to Configure Time Synchronization in the
ToolboxST* Application
assume that the HMI nor the operator will close a safety critical control loop.
Warning
To keep the information obtained from the devices within a system coordinated, it is critical that the devices are synchronized
in time. The time synchronization function can be provided by a computer configured with the WorkstationST* application
(WorkstationST computer) or a network time server configured to act as the primary time source. Network time servers
acquire time from the Global Positioning System (GPS). A WorkstationST computer configured as the designated primary
time source can be configured to get its time from its internal clock, the GPS system (using a time card), or from an external
time reference that exists at the customer site for the system. When using a site time reference, a designated WorkstationST
computer synchronizes its time with the time source and then synchronizes all other components in need of synchronization
with the WorkstationST time.
Basic Network Time Protocol (NTP) System Topology
2.2.1 Synchronize Time Using a WorkstationST Computer as a Server
Using a WorkstationST Computer as Primary/Secondary Time Source

➢ To synchronize time using a WorkstationST computer as a server
1. From the Windows Start menu, select All Programs, GE ControlST*, ToolboxST, and ToolboxST to display the
System Editor.
From the Tree View, select

the system item (Aim_24 in
this example ).
Select Time Synchronization

to display the properties in the
Property Editor.
2. From the Property Editor Time Synchronization section, configure the properties as follows:
Configured System Time Reference Acquisition Method has two options when using a WorkstationST computer as a
time source (without using a site time reference):
• Native Time Reference is selected when the WorkstationST computer does not have a time card. The computer will
use its internal clock.
• Native Time Reference, PC Time Card Option is selected when the WorkstationST computer has a time card. This
option also requires that you configure the time card in the designated WorkstationST computer. Failure to configure the
time card will prevent the time server from running on the WorkstationST computer.
• Site Broadcast Time Reference is selected when the system time is supplied by a customer maintained Timeserver
broadcasting time to designated local Workstations.
• Site Unicast Time Reference is selected when the system time is supplied by a customer maintained Timeserver
unicasting time to designated local Workstations.
Designated Primary Time Source is used to select the Timeserver or WorkstationST computer that will be the primary
time source. The Timeserver or workstation selected as the Primary Time Source supplies time to all of the remaining devices
in the system. This time source must be connected to both the PDH and UDH networks.

Designated Primary Time Source Preferred Network is used when there are multiple plant scope networks in a
system configuration. This is an optional network name used as a preferred network when finding the address of the Primary
Time Source. This setting is used by WorkstationST components to determine the address to use in the ntp.ini file to reach the
Primary Time Source. The setting can be used to select one network when multiple networks are available.
Designated Secondary Time Source (Optional) is used to select the Timeserver or WorkstationST computer that will
become the time source if the primary time source fails. Specifying a secondary time source is optional, but recommended.
This time source must be connected to both the PDH and UDH networks.
Designated Secondary Time Source Preferred Network is used when there are multiple plant scope networks in a
system configuration. This is an optional network name used as a preferred network when finding the address of the
Secondary Time Source. This setting is used by WorkstationST components to determine the address to use in the ntp.ini file
to reach the Secondary Time Source. The setting can be used to select one network when multiple networks are available.
Disable Time Source NTP Broadcasts disables NTP broadcasts from the WorkstationST computer(s) designated as the
Primary (and Secondary) time source(s). Unicast mode is recommended for all native devices, however, some external
devices do not implement Unicast mode and require periodic NTP broadcasts from the time sources to synchronize their time.
NTP Client Mode is the method by which the clients (components that need to synchronize time) receive the time messages.
There are three options:
• Unicast has the client request the time from the time source. This is recommended since it guarantees that the client is
getting the time from the correct time source.
• Broadcast is when the client listens for time messages on the network. If there is more than one time source
broadcasting the time messages on the network, the client could be getting time from different time sources, and be
susceptible to invalid time.
• Disabled is when the clients do not request or listen for time messages. The clients are not being time synchronized.
Note When a system is first created, the NTP Client Mode default mode is disabled. After the WorkstationST computer or
time servers have been created and configured to be the time source, change this mode to the appropriate setting (Unicast is
recommended).
The configuration at the system level controls the NTP settings for all the components in the system. Changing a system level
NTP setting causes all system components to update, build, and download.
Site Time Source #1 is used to enter the IP address or hostname of a computer or Network Time Server available on the
network that is not part of the system. This setting is used to synchronize the system to a time source at the customer site.
Site Time Source #2 (Optional) is used to enter the IP address or hostname of a computer or Network Time Server
available on the network that is not part of the system. This optional setting can be used to synchronize the system to a time
source at the customer site.

2.2.1.1 Configure a Time Card in a WorkstationST Computer
If the Native Time Reference, PC Time Card Option is selected as the Configured System Time Reference Acquisition
Method, you must configure the time card for the WorkstationST computer.
➢ To configure a time card in a WorkstationST computer

2.2.2 Synchronize Time Using a Network Time Server
A network time server is a time source outside the system configuration that is used to synchronize time throughout the
system, and typically throughout the site. The time server uses a standardized time source such as GPS or atomic clock for
accurate time reference. A network time server can be used to synchronize time. The network time server is used in place of a
WorkstationST computer as the Designated Primary Time Source.
Using a Network Time Server as Primary/Secondary Time Source

➢ To synchronize time using a network time server
From the System Editor ,

select the system item
(Aim_24 in this example ).
From the Property

Editor, expand Time
Synchronization, select
the Configured System
Time Reference
Acquisition Method
property, and select
Native Time Reference
from the drop-down menu .
Select the Designated

Primary Time Source
property and select
TimeServer1 from the
drop-down menu.
Note The Designated Secondary Time Source can be either a WorkstationST computer or another Time Server.
Refer to the procedure To synchronize time using a WorkstationST computer as a server for information on configuring the
remaining Time Synchronization properties.

2.2.3 Synchronize Time Using a Site Time Reference
Some customers require the entire facility to be time synched from a central source (site time reference). The site time
reference can either broadcast the time over the network (broadcast) or accept requests from clients for the time (unicast).
When using a site time reference rather than a WorkstationST time source, the WorkstationST computer synchronizes its time
with the site time reference rather than using its own internal clock. The WorkstationST computer still acts as the time source
for the clients in the control system and can be configured for unicast or broadcast mode.
Note Broadcast mode is not recommended for the NTP Client Mode because the clients will listen to any time source
broadcasting time on the network. The clients are therefore susceptible to invalid time references from misconfigured or
misoperating time sources on the network.
Using a Site Time Source

2.2.4 Synchronize Time Using a Site Broadcast Time Reference
➢ To synchronize time using a site broadcast time reference
From the System Editor , select

the system item (Aim_24 in this
example ).
From the Property Editor ,

select the Configured System
Time Reference Acquisition
Method property and select Site
Broadcast Time Reference
from the drop-down menu .
Select the Designated Primary

Time Source property and
select the WorkstationST
component (such as EWS1)
from the drop-down menu to use
as the Primary Time Source .
Note Refer to the procedure To synchronize time using a WorkstationST computer for information on configuring the
remaining Time Synchronization properties.
Tip � When using a Site Broadcast Time Reference, configure the NTP Client Mode as unicast. This prevents client
components from receiving broadcast time references over the network from a time source other than the Designated Primary
and Secondary Time Sources.

2.2.5 Synchronize Time Using a Site Unicast Time Reference
A site unicast time reference is when the system time is supplied by a site maintained Timeserver unicasting time to
designated local workstations as they request it. When configuring a site unicast time reference, two additional Time
Synchronization properties display in the Property Editor. Site Time Source #1 and #2 provide a primary and secondary
location for the WorkstationST computer to request time.
➢ To synchronize time using a site unicast time reference
From the System Editor , select

the system item (Aim_24 in this
example ).
From the Property Editor ,

select the Configured System
Time Reference Acquisition
Method property and select Site
Unicast Time Reference from
the drop-down menu .
Select Site Time Source # 1

and enter the IP address or
hostname of the component to
be used as the primary time
source .
Select Site Time Source # 2

and enter the IP address or
hostname of the component to
be used as the secondary time
source .
The two new Time Synchronization properties are configured as follows:

Site Time Source #1 is the host name or IP address of the primary site time reference. This time source must be accessible
to the Designated Primary and Secondary Time Source WorkstationST computer.
Site Time Source #2 is the host name or IP address of the secondary site time reference. This time source must be
accessible to the Designated Primary and Secondary Time Source WorkstationST computer.
Note Refer to the procedure To synchronize time using a WorkstationST computer as a server for information on configuring
the remaining Time Synchronization properties.

2.2.6 Override Time Synchronization Settings for a Component
When a component has a special time synchronization requirement, the time synchronization properties can be overridden.
This is done in the component's Property Editor.
➢ To override time synchronization settings for a component

2.2.7 Check a Component's Time Synchronization Status
When necessary, you can check the time synchronization of individual components. This can be done from the ToolboxST
Component InfoView or from the WorkstationST Monitor.
2.2.7.1 Check Time Synchronization Status in the ToolboxST Application

➢ To check a component's time synchronization in the ToolboxST application
♦ From the System Editor Summary View, click the Online button to take the system online.
The banner and

the task bar
display time
synchronization
information.
Note To display the NTP status of another component, close the NTP Status Viewer currently open and select another
component. Each data field has a tool tip that describes the field and gives an analysis of the current state.

2.2.7.2 Check Time Synchronization Status Using The WorkstationST Monitor
➢ To check a component's time synchronization using the WorkstationST Monitor
♦ Right-click the WorkstationST status icon in the taskbar notification area and select Open Detail View. The
WorkstationST Status of Features dialog box displays.
Right -click Tiime Synchronization System

and select View NTP (Time Sync) Detail .
The banner, tooltip , and the task bar display

time synchronization information.
The NTP status for another component can be displayed from this dialog box.

➢ To display the NTP status for another component
From the file menu, select

Specify Remote Hos t.
Enter the host name

or IP address and
click OK .

Tip � More than one NTP Status Viewer can be opened to display different components. To do this, double-click the
WorkstationST status icon in the taskbar notification area, double-click the Time Synchronization System item, and
select View NTPC (Time Sync) Detail to open additional windows which can be pointed to various remote hosts.

2.3 How to Use the Mark* VIe Tools in the Simulink™
Environment
Warning
The Simulink Translator (Translator) for Mark VIe blockware is a part of the MATLAB™ application, which is a set of
software tools for conducting simulations of physical systems. It is used to write ToolboxST* code. The code can also be used
as part of an overall simulation in the MATLAB application. After code has been verified to work satisfactorily, it is
converted for use in the ToolboxST application using the Translator.
The Simulink block library is used within the Translator to produce code that runs in a Mark VIe controller. The block library
is a set of Simulink S-Functions blocks (modified Mark VIe blocks) that use the actual code from the same blocks running in
the Mark VIe controller. A C-code wrapper is used to port the code to Simulink as a DLL. The Simulink block library is a sub
set of the blocks taken from the Mark VI standard, legacy, and turbine block libraries.
The Translator takes the Simulink model block code and produces blockware for the requested Mark VIe component in the
ToolboxST application. The Translator uses the ToolboxST automation in order to accomplish this. It also validates the
MATLAB configuration to make sure it can be translated with no errors.
Refer to the imulink® Translator Tool for Mark* VIe Blockware User Guide (GEH-6743) for detailed rules information.
This document is intended for Simulink and Mark VIe application code developers who write software in Simulink to be used
on a Mark VIe embedded controller. The following information is included:
• Installation of the Simulink block library and Translator

• Examples of the use of Mark VIe library blocks in Simulink models
• Definition of Simulink Programs and Tasks using Simulink sub-systems
• Declaration of Mark VIe global variables in a Simulink model
• Creating a Simulink user block
• Translation of Simulink models to Mark VIe applications using the Translator
• Instancing a Mark VIe Virtual Controller into a Simulink model
• Displaying the Virtual Mark VIe block parameters
• Using the I/O List Builder tool

2.3.1 Prerequisites
The following prerequisites apply:
• The MATLAB application must be installed on the computer in which the Simulink block library is installed.
• The user has previous knowledge of the Simulink program and does not need step-by-step instructions for routine
functions within the program.
• The Simulink block library and the Translator require the ControlST Software Suite Version 04.00 or higher.
2.3.2 Install the Simulink Block Library and Translator

Only one version of the Simulink block library can be installed at any one time on a computer. If a new version is installed, an
upgrade takes place. The installation of the Simulink block library is included as an option on the Setup - GE ControlST
dialog box.
The Translator is installed at the same time and in the same location as the ToolboxST application.
➢ To install the Simulink block library and Translator

1. Place the ControlST CD in the CD/DVD drive. The Read Me First message box displays.

2. From the Setup – GE ControlST dialog box, select the GE Installation Options to install.
3. Follow through the remainder of the installation screens.

4. Restart the computer.
Note Refer to the ToolboxST User Guide for Mark* Controls Platform(GEH-6700), the section, Installation for additional
information on the installation process.
A shortcut for the Translator is created when the ToolboxST application is installed. The last version to be installed is the one
that displays on the Start menu. When a version of the ToolboxST application is uninstalled, the Start menu shortcut for the
Translator reverts to the highest version installed (if there is one).
The version of the MATLAB application is checked by the setup program to make sure it is greater than or equal to the
minimum allowed and less than or equal to the maximum allowed. These Min and Max versions are not hardcoded into the
Setup.exe program, but are in a text file read by the setup program. If the installed version of the MATLAB application is not
within the appropriate range, an error message displays indicating this fact and the install of the Simulink block library is
stopped.

2.3.3 Create Simulink Models with Simulink Block Library
There are a defined set of rules used to create Simulink models. These rules must be followed for the Translator to
successfully translate the model into Mark VIe blockware. The following types of rules are defined:
• Program
• Task
• User block
• General
• StateFlow
➢ To create a Simulink model

1. From the Start menu, select Programs, MathWorks™, and MATLAB. The MATLAB screen displays.
2. From the File menu, select Name and enter a name for the model. (In this case example1 is used.)

A subsystem with the prefix PROG_ must be created. For example, if SpeedControl is the program name, create a subsystem
and name it PROG_SpeedControl.
Tip � A program (PROG_) subsystem can only contain the TASK_ subsystem. All other things that are within a program
subsystem are ignored.

➢ To create a Simulink program

Or

2.3.4 Task Subsystems
➢ To create Simulink task
1. Create a subsystem with the prefix TASK_ to its name.
2. Assign the frame rate and frame multiplier (offset) of the task in the prefix. For example, if the task name is
SpeedMonitor, create a subsystem and give it the name TASK_01_00_SpeedMonitor. The 01 assigns the frame rate of
the task and the 00 assigns the offset. If the task should run 4 times slower than the frame rate, define TASK_04_00_
SpeedMonitor.
Note Specify the frame rate and frame multiplier in the name only for the translator tool. It is the user’s responsibility to
write Simulink logic that runs the subsystem at the specified rate. Create a triggered subsystem that is triggered to run every
forth cycle for task names (TASK_04_00_xxxx).
Tip � A task subsystem can contain standard blocks and user blocks. All GOTO and FROM blocks that are defined inside a
TASK_ or a PROG_ are ignored.
The following is an example task subsystem using the TASK_04_01_EX name.

2.3.5 User Block Subsystems
➢ To create a Simulink User Block
1. Create a subsystem with the prefix USRB_ to its name.

Example:
Task
Subsystem with Assigned Ports and Logic

If the Input port allows the connection of an array of unknown size, the port name should start with the prefix "Array_". This
tells the Translator to set the array size to "-1" when building the user block in the library. Setting the Port dimension in the
Inport dialog box to "-1" is meaningful to Simulink, but does not get stored in the .mdl file when saved.
Subsystem with Input Array
The Translator is used to translate the subsystem into a user block and instance it into the task in which it was defined.

2.3.6 Use the Translator
➢ To open the Translator UI
From the Project

menu, select
Validate to display
the Simulink to
Mark VIe translator
screen.
When the Translator is first opened, no views display. From the File menu, select:
Create Project to create a new project.
Open Project to open an existing project.
Save Project to save a copy of the current project displayed in the UI.
Close Project to close the currently displayed project.
Recent Projects to display a list of the five most recently viewed projects.
Exit to exit the Translator.
➢ To display an existing project
From the File menu, select Open

Project or from the Recent Projects
drop-down list, select the project.

Object
Properties View
Program
Task View
Variables
View
Error and
Event
Log View
Program Task View displays the programs, tasks, user blocks, blocks, and variables in a hierarchical view.
Error and Event Log View displays status messages while parsing and/or building a project.
Object Properties View displays information about an item selected in the Tree View.
Variables View displays all global variables and parameters configured in a project when the Variables item is selected in
the tree view.
A Translator project must be created before translating a Simulink model.
Note Prior to creating a Translator project, ensure that at least one unused ToolboxST system .TCW file, with a Mark VIe
controller and an empty library container is available. This must be created manually in the ToolboxST application.
Refer to the ToolboxST User Guide for Mark* Controls Platform (GEH-6700), the section Opening and Creating Systems for
additional information.

➢ To create a project
1. From the Translator UI toolbar, click New.
Or
From the File menu select Create Project. The Create a new translator project dialog box displays.
Note Prior to creating a new project, verify that a new, unused .tcw file, containing a Mark VIe controller and an empty
library container, is available. This must be created manually in the ToolboxST application. Refer to the ToolboxST User
Guide for Mark* Controls Platform (GEH-6700), the section Opening and Creating Systems.
Click the + or the –

buttons to select or
remove source files.
Enter a project
name, path,
and the target
.tcw file.
Enter the
library
container
and the
library name
2. Click OK to create a project.

If you selected the Parse model files on startup check box, the Translator parses all the source files specified in the form
and creates all views. Any parse errors display in the Event and Error Log view.
3. After all views are created, from the Translator, click Save.
Or
From the File menu, select Save Project .

Tip � Click the Open Existing Project button to reopen the project.
➢ To configure or modify a project

1. From the Translator UI toolbar, click Configure.
Or
From the Project

menu, select
Configure to
display the Project
Configuration
dialog box.
The Project Configuration dialog box allows you to:
• Add source files to the project

• Delete source files from the project
• Change the .tcw target file
• Set build options
Source Files tab is used to change the target .tcw file (the file must already exist), add or remove source files, and specify
the order that source files are parsed. All files needed to run the simulation in the Translator must be listed here. Use the
arrow buttons to sort the files in the order to be parsed. At least one .mdl file must be listed. The file order list should identical
to what was loaded in the Translator to run the simulation. The sorted order file Main_Build.txt must be created after all
changes are made to the model. If it is out of date, an error displays.
Note Simulink models must follow a set of rules for the tool to recognize these files and successfully convert them.

Click the ellipsis Click the + or –
button to change buttons to select or
the .tcw file. remove a source file.

Build Information tab is used to configure the build options. All existing program tasks and variables are deleted, and
library contents are created.
Select Create
User Programs
and Tasks to
force creation of
programs, tasks,
and all variables.
If programs, task structure, and variables were created manually or are in place from the previous step, click to clear the
Create User Programs and Tasks check box. In this mode, the Translator only verifies that a program and/or task exists, and
then adds the logic to it. If the program and/or task structure does not exist, the Translator is stopped by an error. Variables are
only validated in this mode. The following items are validated:
• Variable existence
• Variable data type
• Variable Initial value
• Variables Display High, Display Low, and Entry High for control constants (Parameters in Simulink)
Select Create Library for each Program to automatically create a library with the same name as the program and then create
the user program inside the library. This feature is very useful when writing multiple tasks in the program and to selectively
invoke tasks using an instance script. Always keep this option checked, even when manually creating the library for each
program. This ensures the tool looks for the library and then opens a program for validation.
Tip � The only time you should uncheck this option is when you decide not to create a library for each program.

Select Enable logging progress messages to file to force the Translator to log all parsing and building messages to a text file.
Three levels of messages can be logged:
• At Level 1, all the basic messages and errors are logged.

• At Level 2, all the blocks and connections that have been ignored by the tool are logged. The reason for ignoring is
either the block is not supported or an EXCL_ was specified.
• At Level 3, all internal status and error messages are logged.
Selecting Level 2 or Level 3 slows down the parsing and building of the project. Use these levels only to debug if the
translation is not working correctly.
Select Add undefined variables to the first available program to force all variables that do not have an associated program
name, or variables whose programs don’t exist in the project, to be created in the first available program. Use this feature only
for testing. When the whole system is being built, always keep this option unchecked to ensure the tool reports all variable
related issues.
.TCW Library Information tab specifies the library container name for the blockware logic.
Note The container must be manually created in the target item before the translation is performed.
Enter a library
name for all
created user
blocks.

Select the
Parse model
on startup
check box to
parse specified
files each time
the Translator is
started.
2. After all configuration options have been selected, click Update to renew the configuration. Select Cancel to stop the
process at any time.
2.3.7 Build the Project

After all source files are added and the parsing is completed successfully, create a .tcw output.
➢ To create a .tcw output
From the toolbar, click Build .

Or
From the Project menu, select Build.
Note Because the tool has to load all dynamic link libraries and configure the .tcw output, the build process can take a few
seconds to a few minutes depending on the system configuration.
All build messages are output to the Event and Error Log view.
• Normal messages display in black.

• Warnings display in blue.
• Errors display in red.
The translation process may stop if a fatal error occurs, usually due to an internal exception. When this happens a message
displays the exception information. The most common causes of exceptions are invalid source input file format and/or failure
to follow all translation rules.

2.3.8 Use the Mark VIe Virtual Controller
The Mark VIe Virtual controller can be instanced into the Simulink model as a block. (It is assumed the user knows how to
set up the Virtual Mark VIe product.)
➢ To instance a Mark VIe Virtual controller into a Simulink model

1. From the Start menu, select Programs, MathWorksTM, and MATLAB. The MATLAB screen displays.

When the path is correct, the Virtual MarkVIe block can be instanced using the Simulink Library Browser.
2. From the Simulink program screen toolbar, click the Library Browser button. The Simulink Library Browser
dialog box displays.

➢ To display the Virtual Mark VIe block parameters

2.3.9 I/O List Builder Tool
The I/O List Builder tool is used to automatically generate the simulation I/O list. It accepts either a .M6B file (for Mark VI)
or a .TCW file (for Mark VIe) and can read the device signal list. It provides an option for the user to select the input and
output signals to be generated.
The Mark VIe S-function blocks expect the signal lists in a specific format. Refer to the Simulink Translator Tool for Mark
VIe Blockware User Guide (GEH-6743) for additional information. A .csv file with a list of signal names to be simulated is
used. The tool reads the .csv file and converts it into the required format.
Note Avoid manually creating or editing the .csv files generated by this tool. Users can only create a named list to feed to
the tool.
Tip � Every time the application is modified the I/O list should be rebuilt to update the signal addresses.

➢ To display the I/O List Builder
The first line of the .csv file is considered the file header. It contains a string that defines the type of file and number of signals
in the file.
Example:
<File Type>,<Signal Count>,0,0
File Type = Inputs or Outputs.
Signal Count is an integer.
The remaining two fields in the header are always 0, 0. (These are for future use.)
Each signal is defined in the .csv file as follows:
<Signal name>,<Signal Address>,<Initial Value>,1
Signal address is the Mark VI/Mark VIe token number of the variable.
Initial value is always 0.

2.4 How to Qualify a FOUNDATION Fieldbus Field Device
This document defines the test plan for qualification of FOUNDATION Fieldbus™ H1 field devices for use with the Mark VIe
control system. Although the Fieldbus Foundation certifies field devices with interoperability tests, anomalies have been
noted in the performance of some devices when used with host systems from different manufacturers. This test plan is
intended to serve as a tool to ensure field devices can be used with the Mark VIe control system without issues.
This document describes the minimal procedures that GE Energy exercises to qualify
a FOUNDATION Fieldbus device for use with the Mark VIe control. Device qualification
is the process by which GE Energy officially states that the device works with the host
system, and describes any issues. Non-GE persons are welcome and encouraged to use
these test procedures, report their findings to GE, discuss any issues, and request
devices to be qualified. However, only authorized GE personnel can officially qualify a
device. A device will not appear as qualified until the procedures are executed by GE
as part of device qualification efforts.
Attention
Refer to the FOUNDATION Fieldbus Device Qualification Support Central Community
for more information, including access to the list of qualified devices:
http://supportcentral.ge.com/products/sup_products.asp?prod_id=319535
This test plan covers the following functions:
• Autodetection of newly connected devices

• Commissioning of new devices
• Use of input and output function blocks in field devices with control in the controller
• Use of function blocks in field devices to allow control in the field.
This test plan does not cover the following functions:
• Testing Mark VIe hardware

• Testing Mark VIe software
• Testing field wiring devices such as segment protectors or power conditioners.
This test plan is intended to focus on operability of the field devices with the Mark VIe control, and not on the operating
characteristics or accuracy of the field device itself. It contains the following procedures:
• Add a New Device to a Segment

• Enable Each Block in the Field Device
• Test Each Block Input and Output to and from ToolboxST* Blocks
• Test Block Parameters for Read and Write Access
• Block Instantiation
• Test Alarms from a Field Device to the ToolboxST Alarm System
• Test Menus and Methods in a Field Device

2.4.1 Prerequisites
This document assumes the individual performing the tests is knowledgeable in the use of the ToolboxST application,
FOUNDATION Fieldbus concepts and use, and the field device to be tested. Refer to the Mark VIe Control FOUNDATION Fieldbus
Interface Application Guide (GEH-6761) and the ToolboxST User Guide for Mark Controls Platform (GEH-6700), the
chapter, Mark VIe Control FOUNDATION Fieldbus Interface for additional information.
Install the following software tools as a minimum:
• ControlST software suite version 04.03 or later

• WorkstationST application version 04.03 or later
Create a Mark VIe control system in the ToolboxST application that includes the following at a minimum:
• A special task of FOUNDATION Fieldbus type

• A linking device in the hardware tab
• A segment in the linking device
• A device placeholder of the type that matches the device to be tested (Refer to the ToolboxST User Guide for Mark
Controls Platform (GEH-6700), the chapter, Mark VIe Control FOUNDATION Fieldbus Interface , the section Device
Definition Files for importing DD files, if required.)
The Mark VIe control system should be set up as displayed in the following diagram. TMR or simplex controllers can be
substituted for the dual controllers diplayed. Simplex IONet, power conditioners, or linking devices can be substituted for the
dual redundant components displayed.

2.4.2 Field Device Testing
This test plan is intended to focus on operability of the field devices with the Mark VIe control system, and not on the
operating characteristics or accuracy of the field device itself. In general, all devices are independent. Record test results in
Appendix A Device Qualification Datasheet, using a separate data sheet for each field device. Repeat this entire section for
each device tested.
Testing for each device must be done in the order listed.
Attention
2.4.2.1 Add a New Device to a Segment

➢ To add a new device to a segment
1. From the ToolboxST System Editor Tree View, double-click the Mark VIe component (such as FF3).

2.4.2.2 Enable Each Block in the Field Device
Opening the field device in the Hardware tab displays the blocks supplied with the field device.

➢ To enable input blocks
1. From the Software tab, add input blocks to the task for each block supplied in the field device. With alignment the task
should look like the following example:

2. From the Software tab Summary View, right-click on each block (such as FF_AI_1) and select Assign from the
drop-down menu to connect each of the blocks to the blocks in the field device. When complete, the task should look like
the following figure:

Output Blocks

➢ To enable output blocks
1. From the Software tab, add output blocks to the task for each block supplied in the field device.
2. From the Software tab Summary View, right-click on each block (such as FF_AO_1) and select Assign from the
drop-down menu to connect each of the blocks to the blocks in the field device.

ToolboxST Blocks
➢ To enable ToolboxST blocks

1. From the Software tab Summary View, select the Library Blocks tab and Type Conversion.
2. Add a MOVE_STATUS block to the task for each input and output FF_ block added previously.
3. Connect the OUT pin of the input blocks to the SRC pin of the associated MOVE_STATUS blocks.
4. Connect the OUT pin of the MOVE_STATUS blocks to the CAS_IN pin of the associated output blocks. (Ensure the
data type of the MOVE_STATUS block is appropriate for the FF_ block it is connected to.)
5. From the Software tab Summary View, select the Library Blocks tab and System.
6. Add a STATUS_COMBINE block to the task for each MOVE_STATUS connected to an output FF_ block. The
application should look similar to the following diagram:
Build and Download

Build and download the ToolboxST configuration, the linking device, and the device under test. No download errors should
occur. Record the download results in the data sheet (Step 3.1.2.4) in Appendix A.

2.4.2.3 Test Each Block Input and Output to and from Blocks in the ToolboxST
Application
Input Blocks
➢ To test input blocks

1. From the Hardware tab, compare the live data for each input block with the output of the block in the Software tab.
2. Create a variance in the field device value if practicable. Data should be seen to transfer from the field device to the
Software tab.
3. Create a variance in the quality of the signal if practicable (refer to the field device vendor manual for possibilities on
creating status changes). Status information should be seen to transfer from the field device to the Software tab.
4. Record the results (Value and Status) in the data sheet (Step 3.1.3.1) in Appendix A.
Output Blocks
➢ To test output blocks

1. From the Hardware tab, compare the live data for each output block with the output of the MOVE_STATUS block
connected to the FF_ block in the Software tab.
2. Create a variance in the field device value if practicable. Data should be seen to transfer from the field device to the
Software tab.
3. Create a variance in the quality of the signal if practicable (refer to the field device vendor manual for possibilities on
creating status changes). Status information should be seen to transfer from the field device to the Software tab.
4. Record the results (Value and Status) in the data sheet (Step 3.1.3.2) in Appendix A.

2.4.2.4 Test Block Parameters for Read and Write Access
➢ To test block parameters for read and write access
1. From the ToolboxST Hardware tab, test the following parameters for write access. The user should be able to change
the online value for these parameters and see the change reflected in the online value. Record the results in the data sheet
(Step 3.1.4) in Appendix A.
• MODE_BLK.TARGET
2. From the ToolboxST Hardware tab, test the following parameters for write access during download. The user should be
able to set a new value in the ToolboxST value and download the value to the field device. Record the results in the data
sheet (Step 3.1.4) in Appendix A.
• MODE_BLK.PERMITTED
• XD_SCALE.EU_0
• XD_SCALE.EU_100
• XD_SCALE.UNITS_INDEX
• XD_SCALE.DECIMAL
• OUT_SCALE.EU_0
• OUT_SCALE.EU_100
• OUT_SCALE.UNITS_INDEX
• OUT_SCALE.DECIMAL
• IO_OPTS
• STATUS_OPTS
• CHANNEL (may be accomplished above)
• L_TYPE (may be accomplished above)
• LOW_CUT
• PV_FTIME (Input blocks)
• SP_RATE_DN (Output blocks)
• SP_RATE_UP (Output blocks)
• FSTATE_TIME (Output blocks)
• FSTATE_VAL (Output blocks)
• SHED_OPT (Output blocks)

2.4.2.5 Block Instantiation
Some field devices support block instantiation. Use the following procedure to instantiate a new block in the field device if it
is supported.
➢ To instantiate a new block in a field device

1. From the ToolboxST System Editor Tree View, double-click the Mark VIe component (such as FF3) to display the
Component Editor.

2. From the Software tab, create a block in the software task and assign it to the instantiated block.
3. Build and download the controller, the linking device, and the field device.
4. The device should download without error. Record the results in the data sheet (Step 3.1.5) in Appendix A.

2.4.2.6 Test Alarms from a Field Device to the Alarm System in the ToolboxST
Application
This section of the test plan tests the ability of a device-generated Fieldbus Alert to be transmitted into the ToolboxST alarm
system.
➢ To test alarms from a field device

1. Open a WorkstationST Alarm Viewer window for this section of the test.
2. From the ToolboxST Hardware tab, click the Go On/Offline button to go online with the controller to which the
device under test is connected.
3. Look at the Alarm Viewer window to verify that the device alert has been generated. The alarm should be similar to the
following:
4. Record the results in the data sheet in (Step 3.1.6) Appendix A.
2.4.2.7 Test Menus and Methods in a Field Device

This section of the test plan tests the ability of the ToolboxST application to interact with the menus and methods provided by
a device manufacturer.
➢ To test menus and methods from a field device

1. From the ToolboxST Hardware tab, click the Go On/Offline button to go online with the controller of the device being
test.
2. Right-click on the resource block of the device being test. Perform all methods displayed in the device menu. Follow all
menu paths to ensure that all of the menu selections are available.

3. Right-click on the transducer block(s) of the device being test. Execute all methods displayed in the device menu.
Explore all menu paths to ensure that all of the menu selections are available.
2.4.3 Appendix A Device Qualification Datasheet

Use a copy of this datasheet to record the test results for each device tested.

2.5 How to Test the TMR Capability of the Mark* VIe
Control Using the ToolboxST Application
Indicates a procedure, condition, or statement that, if not strictly observed, could

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

result in damage to or destruction of equipment.
Caution
The procedures in this document are used to test the triple modular redundant (TMR) capability of the Mark VIe turbine
control system using the ToolboxST application. The following procedures are included:
• Prepare for the TMR test

• Run the TMR test
• Run the protective module (PPRO) test
• Collect trip log and alarm and event files
• Determine the root cause of a trip event
2.5.1 Prerequisites
Before testing TMR capabilities, take necessary steps to secure the controlled
equipment to prevent equipment damage or personal injury.
Warning
Testing for TMR capability can cause a trip event since the testing purposely places
the control cabinet into a simplex mode while the controller restarts. Because the
probability of a unit trip is increased, it is recommended the test be performed in
phases where the first test is performed on turning gear, the second test at Full Speed
Caution No-Load (FSNL), and the final test with the unit online.

➢ To prepare for the TMR test
1. Review all standing and intermittent process alarms on the turbine control. Resolve all alarms related to TMR devices
and critical control functions.
2. Review all I/O module standing and intermittent diagnostic alarms on the turbine control. Resolve all alarms related to
TMR devices and critical control functions.
Note If any alarms remain un-cleared, print out the alarm queue to document them prior to conducting the TMR test.
3. Go online with each of the three controllers (R, S, and T) in turn to verify that each controller is running in the
controlling state with code that is equal to the .tcw file being used.
4. Verify that historical alarm data is being stored correctly. The WorkstationST Service in the HMI stores them as .bin files.
The typical location is E:\GEWorkstationST\HistoricalAlarmData.
5. Configure the trend for high resolution data according to the recommended list in Appendix A or Appendix B, depending
on turbine frame.
Note These appendices are for guidance only, and points can be added or subtracted as determined by the site team.
6. From the Trender for the ToolboxST application, start a trend that includes all of the following items:
• Speed pickups
• TMR analog transducers
• LVDT inputs
• Exhaust thermocouple values
• Gas valve position commands
• IBH valve position commands
• Liquid fuel bypass valve commands (if applicable)
• IGV position commands
• Non-voted servo current signals
• Non-voted ETR and PTR feedbacks

2.5.2 Tests
➢ To run the TMR test
1. From the ToolboxST application, open the .tcw file and double-click the controller (such as G1, G2 or S1) to display the
Component Editor.
Note In the Mark VIe control, the designated controller letter is displayed in the Component InfoView Status tab under the
Attribute Designated Controller.
2. From the Device menu, select Online.
3. Proceed in reverse order from the designated controller so the designated controller is tested last, for example:
a. If the designated controller is R (default), then the testing order is T, S, R.
b. If the designated controller is S, then the testing order is R, T, S.
4. If the unit is at Full Speed No-Load (FSNL) or low power, from the Trender, start a trend file on the designated
controller.
Note Run Trender on a controller that is not going to be shutdown. The Trender pulls data from the controller that was
selected when it was put online.

5. Power down the T controller (or the appropriate controller to test as explained in step three) by removing the power
supply. Make sure the unit continues to operate safely. Wait at least five minutes to ensure that the system is stable.
Note The MarkVIe control system uses different types of controllers and power supplies. Refer to the Mark VIe Control
System Hardware Guide (GEH-6721 Vol II) for more information.
If there are any problems during TMR testing, a unit shutdown or trip can occur.
Caution
6. Power up the controller that was just powered down.
7. From the Component Editor InfoView Status tab, wait for the Attribute Control State to be Controlling for the
controller that was just restarted.
Note The Control State moves through different states including Master_Initialization, DC_Determination, Data_
Initialization, Inputs_Enabled, Exch_Initialization, Exchanging, Sequencing, Standby, and finally Controlling after startup.
8. Wait for an additional five minutes after the controller has reached Controlling state to allow all processes to stabilize
before continuing.
A trip will occur if a second controller is restarted and the first controller has not
returned to the Controlling state. Give the controller sufficient time to return to the
Controlling state, which may take as long as eight minutes. If the controlling state is
not achieved, the test should be stopped.
Caution
9. Issue a Master Reset to clear the trip from the protective module.
10. Stop the trend file and save it. Record the file name and start a new trend file on the designated controller.
11. Repeat steps four through ten for the other two controllers in the order described in step three. It will be necessary to go
online with a different controller prior to powering off the designated controller.

➢ To run the PPRO I/O pack protective module test
1. Start a new trend file.
2. Power down the R-PPRO I/O pack by removing the 28 V power supply to the I/O pack. Make sure the unit continues to
operate safely.
3. Check that a communication failure diagnostic has been annunciated by the controller.
If there are any problems during TMR testing, a unit shutdown can occur
Caution
4. Power up the R-PPRO by plugging in the power supply.
5. Wait until the communication failure diagnostic has reset.
6. Stop the trend file and save it.
7. Issue a Master Reset and Diagnostic Reset.
8. Repeat steps one through seven for the S-PPRO and T-PPRO I/O packs.
2.5.3 Trip Event

If a trip event occurs, use the following procedure to collect the trip log, alarm and event files, and determine the root cause of
the trip.
➢ To collect the trip log and alarm and event files

1. Collect the .bin files from the HMI directory E:\GEWorkstationST\HistoricalAlarm. There will be separate .bin
files for process alarm, diagnostic alarm, events, and SOEs.
2. Collect trip logs from E:\GEWorkstationST\Recorder. Use the ToolboxST application to verify the files are from the
correct trip event.
➢ To determine the root cause of a trip event

1. From the ToolboxST application, review the trip log and alarm and event files to determine the root cause of a trip event.
2. If the site found any faulty TMR device, fix the issue and document the root cause and resolution as part of the trip
report.
3. If the trip is not due to a faulty TMR device, open a power answer center (PAC) case and attach the trip logs captured
during the test.
The following are examples of root causes:
• In a TMR system, two faults are usually required in combination to produce the root cause of a trip. For example, loss of
an LVDT on one controller can combine with the power down process of a second controller to result in what is reported
as a control valve out-of-position failure. The lurking or hidden fault was the LVDT failure, and it was revealed when the
controller power down process removed the redundant position feedback. The corrective action in this example would be
to repair the problem with the LVDT. Root cause and corrective action(s) should be included in the trip report.
• It is possible that I/O used in control code as critical inputs has been terminated in the control as simplex points. If this is
uncovered, a PAC case should be written and sent to the controls requisition engineer. Attachments for the PAC case
should include an archived copy of the .tcw file, trend files, trip log, event file, and the diagnostic alarm file. The PAC
case should describe the point in the TMR testing the trip occurred. It should also include a description of the specific
sequence of events leading up to the trip.

2.5.4 Appendix A Trend List for 9FB Gas Turbines
The list will vary by frame size and fuel system.
Signal Signal Description Signal Signal Description

G1\AA_PRS_ABS AA Manifold Pressure In PSIA G1\ctda2 Compressor Discharge
Thermocouple #2
G1\BB_MAX Maximum vibration G1\ctda3 Compressor Discharge
Thermocouple #3
G1\cagv IGV control servo current G1\ctif1 Compressor Inlet
Thermocouple 1
G1\CAGV_NVR Non Voted IGV Servo Current G1\ctif2 Compressor Inlet
Fdbk - R Thermocouple 2
G1\CAGV_NVS Non Voted IGV Servo Current G1\ctif3 Compressor Inlet
Fdbk - S Thermocouple 3
G1\CAGV_NVT Non Voted IGV Servo Current G1\DLN_MODE DLN Mode Enumerated State
Fdbk - T
G1\CONTROL_STATE_R <R> Controller State G1\dv Generator Volts
G1\CONTROL_STATE_S <S> Controller State G1\dvar Generator VARS
G1\CONTROL_STATE_T <T> Controller State G1\DWATT Generator Watts Max Selected
G1\CPD Compressor Discharge Press G1\FAG1 G1 Servo Current VSVO
Max Feedback
G1\cpd1a Compressor Discharge Press G1\FAG1_NVR Non Voted G1 Servo Current
Transd. 96CD-1 Fdbk - R
G1\cpd1b Compressor Discharge Press G1\FAG1_NVS Non Voted G1 Servo Current
Transd. 96CD-1B Fdbk - S
G1\cpd1c Compressor Discharge Press G1\FAG1_NVT Non Voted G1 Servo Current
Transd. 96CD-1C Fdbk - T
G1\CPRLIM COMPRESSOR PRESSURE G1\FAG1NSC G1 Null Bias Compensation
RATIO OPERATING LIMIT
G1\CPRLIMNC Comp Pressure Ratio Op Limit G1\FAG2 G2 Servo Current VSVO
- New and Clean Feedback
G1\csbhx Inlet Heating Control Valve G1\FAG2_NVR Non Voted G2 Servo Current
Position Fdbk - R
G1\csgv IGV FEEDBACK angle in deg G1\FAG2_NVS Non Voted G2 Servo Current
Fdbk - S
G1\csrgv IGV REFERENCE G1\FAG2_NVT Non Voted G2 Servo Current
Fdbk - T
G1\csrihout Inlet Heating Control Valve G1\FAG2NSC G2 Null Bias Compensation
Command
G1\ctda1 Compressor Discharge G1\FAG3 G3 Servo Current VSVO
Thermocouple #1 Feedback
G1\FAG3_NVR Non Voted G3 Servo Current G1\fpg2a Interstage fuel gas press xmitter
Fdbk - R 96FG-2A
G1\FAG3_NVS Non Voted G3 Servo Current G1\fpg2b Interstage fuel gas press xmitter
Fdbk - S 96FG-2B
G1\FAG3_NVT Non Voted G3 Servo Current G1\fpg2c Interstage fuel gas press xmitter
Fdbk - T 96FG-2C
G1\FAG3NSC G3 Null Bias Compensation G1\FPG3 Fuel gas flow orifice upstream
press xmitter
G1\FAG4 G4 Servo Current VSVO G1\FQG Gas Fuel Flow
Feedback

G1\FAG4_NVR Non Voted G4 Servo Current G1\FQR Liquid Fuel Flow Reference
Fdbk - R
G1\FAG4_NVS Non Voted G4 Servo Current G1\frcrout Fuel Gas Speed Ratio Servo
Fdbk - S Command
G1\FAG4_NVT Non Voted G4 Servo Current G1\FSG1 Diffussion (D5) GCV-1 Position
Fdbk - T Feedback
G1\FAG4NSC G4 Null Bias Compensation G1\FSG1 Gas ctrl valve #1 Pos Feedback
(hi val sel)
G1\fagr Cur Speed ratio valve servo G1\FSG2 Gas ctrl valve #2 Pos Feedback
current (hi val sel)
G1\FAGR_NVR SRV Non-Voted Servo Current G1\FSG2 PM1 GCV -2 Position Feedback
Feedback from <R>
G1\FAGR_NVS SRV Non-Voted Servo Current G1\FSG3 Gas ctrl valve #3 Pos Feedback
Feedback from <S> (hi val sel)
G1\FAGR_NVT SRV Non-Voted Servo Current G1\FSG3 PM4 GCV -3 Position Feedback
Feedback from <T>
G1\fal Liquid Fuel Bypass Valve G1\FSG4 Gas ctrl valve #4 Pos Feedback
Servo Current (hi val sel)
G1\FALNSC LCV Null Bias Compensation G1\fsgr Position fdbck srv (high value
selected)
G1\fd_intens_1 PRIMARY FLAME G1\FSR Fuel Stroke Reference
DETECTOR #1 FLAME
INTENSITY
G1\fd_intens_2 PRIMARY FLAME G1\fsrg1out G1 control valve servo output
DETECTOR #2 FLAME command
INTENSITY
G1\fd_intens_3 PRIMARY FLAME G1\fsrg1out PM1 Gas Control Valve Servo
DETECTOR #3 FLAME Command
INTENSITY
G1\fd_intens_4 PRIMARY FLAME G1\fsrg2out G2 control valve servo output
DETECTOR #4 FLAME command
INTENSITY
G1\FPG2 Interstage fuel gas press G1\fsrg3out G3 control valve servo output
command
G1\fsrg4out G4 control valve servo output G1\l33cb1o COMPRESSOR BLEED VALVE
command #1 OPEN
G1\FSRMIN FSR: Minimum G1\l33cb2o COMPRESSOR BLEED VALVE
#2 OPEN
G1\FTG Fuel gas temperature G1\l33cb3o COMPRESSOR BLEED VALVE
#3 OPEN
G1\h2gp Generator Gas Pressure G1\l33cb4o COMPRESSOR BLEED VALVE
Transmitter #4 OPEN
G1\L12H Turbine electrical overspeed G1\l33cb5c Compressor Bleed Valve #1
trip signal Closed
G1\L12H_ACC VPRO - Loss Of Protective G1\l33cb6c Compressor Bleed Valve #2
Speed Closed
G1\L12H_FLT Loss of Protective HP Speed G1\l33cb7c Compressor Bleed Valve #3
Inputs Closed
G1\L12H_P VPRO HP Overspeed Trip G1\l33cb8c Compressor Bleed Valve #4
Closed
G1\L12HF Loss Of Control Speed Signal G1\L3G1CVA_ALM G1 Not Following Reference

G1\L20FGX Gas Fuel Stop Valve G1\L3G1CVFLT G1 VALVE Fault
Command
G1\L20FLX Liquid Fuel Stop Valve Control G1\L3G1CVO G1 VALVE FAILED OPEN
Signal
G1\L28FDX Flame detection control G1\L3G1CVSC G1 Valve Current Inadequate
G1\L3 Turbine complete sequence G1\L3G2CVA_ALM G2 Not Following Reference
G1\L3_STAT_R <R> In Controlling State G1\L3G2CVFLT G2 VALVE Fault
G1\L3_STAT_S <S> In Controlling State G1\L3G2CVO G2 VALVE FAILED OPEN
G1\L3_STAT_T <T> In Controlling State G1\L3G2CVSC G2 Valve Current Inadequate
G1\L3_STATE_EX1 State Exchange 1 OK G1\L3G3CVA_ALM G3 Not Following Reference
G1\L3_STATE_EX2 State Exchange 2 OK G1\L3G3CVFLT G3 VALVE Fault
G1\L3_STATE_EX3 State Exchange 3 OK G1\L3G3CVO G3 VALVE FAILED OPEN
G1\L30FORCED_AL SIGNAL FORCING ENABLED G1\L3G3CVSC G3 Valve Current Inadequate
G1\L3G4CVA_ALM G4 Not Following Reference G1\L4PSTX2 Protective Status Trip Logic 2
G1\L3G4CVFLT G4 VALVE Fault G1\L4PSTX3 Protective Status Trip Logic 3
G1\L3G4CVO G4 VALVE FAILED OPEN G1\L4PSTX4 Protective Status Trip Logic 4
G1\L3G4CVSC G4 Valve Current Inadequate G1\L4T Master Protective Trip
G1\L3GFIVP GAS FUEL INTERVALVE G1\L4T_ST Voted Steam Turbine Trip
PRESSURE TROUBLE Signal
G1\L3GFLT Fuel Gas Control Fault G1\L52GX Generator Breaker Close/Open
Status Input
G1\L3GRVAX Stop/Speed Ratio valve G1\L5CMPST_TRP VPRO - Composite Trip(s)
position error alarm
G1\L3GRVFLT GAS RATIO VALVE G1\L5CMPST_TRP1 VPRO - Composite Trip
POSITION SERVO TROUBLE
G1\L3GRVGLT SRV Position Enable for Gas G1\L63ETH_ALM EXHAUST DUCT PRESSURE
Leak Test HIGH TRIP
G1\L3GRVPFLT STOP/SPEED RATIO VALVE G1\L63HGL REDUNDANT SENSORS GAS
NOT TRACKING TRIP FUEL HYD PRESS LOW TRIP
G1\L3GRVT Stop/Speed Ratio valve G1\l63qt2a Lube Oil Header Pressure
position error trip Switch A - Low Press Trip
G1\L3IGVFLT_ALM IGV POSITION SERVO G1\l63qt2b Lube Oil Header Pressure
FAULT Switch B - Low Press Trip
G1\L3LFLT Liquid Fuel Control Fault G1\L86FPG2HT_A POST-IGNITION P2 HIGH
TRIP
G1\l3SMT STARTING DEVICE TRIP G1\L86FPG2LT_A POST-IGNITION P2 LOW TRIP
G1\L4 Master Protective G1\L86GCV1 Gas Control Valve 1 Lockout
G1\L4IGVT INLET GUIDE VANE G1\L86GCV2 Gas Control Valve 2 Lockout
CONTROL TROUBLE TRIP
G1\L4POST Post-Ignition Trip G1\L86GCV3 Gas Control Valve 3 Lockout
G1\L4POSTX Post-Ignition Trip Auxiliary G1\L86GCV4 Gas Control Valve 4 Lockout
Signal
G1\L4PRET Pre-Ignition Trip G1\L86GVT IGV Not Following CSRGV Trip
G1\L4PSTX1 Protective Status Trip Logic 1 G1\L86TFB_ALM EXHAUST THERMOCOUPLES
OPEN TRIP
G1\l86tt GSU Transformer Lockout G1\TTXD1_23 Exhaust Thermocouple 23 -
Trip Compensated
G1\L86TXT Exhaust Overtemperature Trip G1\TTXD1_24 Exhaust Thermocouple 24 -
Compensated

G1\l86u Generator and GSU G1\TTXD1_25 Exhaust Thermocouple 25 -
Transformer Lockout Trip Compensated
G1\l89sso Static Starter Disconnect G1\TTXD1_26 Exhaust Thermocouple 26 -
Switch Open Compensated
G1\L94FIL FAILURE TO IGNITE ON OIL G1\TTXD1_27 Exhaust Thermocouple 27 -
Compensated
G1\TNH Turbine HP shaft speed in % G1\TTXD1_28 Exhaust Thermocouple 28 -
Compensated
G1\TTXD1_1 Exhaust Thermocouple 1 - G1\TTXD1_29 Exhaust Thermocouple 29 -
Compensated Compensated
G1\TTXD1_19 Exhaust Thermocouple 19 - G1\TTXM Exhaust Temp Median
Compensated Corrected By Average
G1\TTXD1_2 Exhaust Thermocouple 2 - G1\TTXSP1 Combustion Monitor Actual
Compensated Spread 1
G1\TTXD1_22 Exhaust Thermocouple 22 - G1\TTXSPL Combustion Monitor Allowable
Compensated Spread

2.5.5 Appendix B Trend List for A15 Steam Turbines
The list will vary for other steam turbines. Variables in these trend lists may or may not exist.

S1\ACV Admission Control Valve S1\l20bpt Bearing Oil Pump Test
Reference Solenoid
S1\acv1_out Admission control valve servo S1\l20ebpt Emergency Bearing Oil Pump
output Test Solenoid
S1\acv1_out_cur Admission Control Valve Servo S1\l20eqv1 Equalizer Valve #1 Solenoid
Current
S1\acv1_pos Admission control valve S1\l20eqv2 Equalizer Valve #2 Solenoid
position feedback
S1\ACV1_STROKE Linearized Flow Reference for S1\bb1x Vibration 1X - Bearing #1
ACV
S1\AFLR Admission Flow Setpoint S1\bb1y Vibration 1Y - Bearing #1
S1\AP Admission Pressure Feedback S1\bb2x Vibration 2X - Bearing #2
S1\ap1 Admission Steam Pressure #1 S1\bb2y Vibration 2Y - Bearing #2
S1\ap2 Admission Steam Pressure #2 S1\bb3x Vibration 3X - Bearing #3
S1\ap3 Admission Steam Pressure #3 S1\bb3y Vibration 3Y - Bearing #3
S1\APL Admission Pressure Limiter S1\bb4x Vibration 4X - Bearing #4
Reference
S1\APR Admission Pressure Setpoint S1\bb4y Vibration 4Y - Bearing #4
S1\APR_P Admission Pressure Setpoint S1\bb5x Vibration 5X - Bearing #5
S1\l20cv1_qc CV1 Quick Close Solenoid S1\bb5y Vibration 5Y - Bearing #5
(FASV)
S1\l20cv2_qc CV2 Quick Close Solenoid S1\bb6x Vibration 6X - Bearing #6
(FASV)
S1\l20iv1_qc IV1 Quick Close Solenoid S1\bb6y Vibration 6Y - Bearing #6
(FASV)
S1\l20iv2_qc IV2 Quick Close Solenoid S1\bb7x Vibration 7X - Bearing #7
(FASV)
S1\l20msv1dt Main Stop Valve FASV S1\bb7y Vibration 7Y - Bearing #7
S1\l20rsv1dt Reheat Stop Valve #1 Dump S1\bb8x Vibration 8X - Bearing #8
Test Solenoid
S1\l20rsv2dt Reheat Stop Valve #2 Dump S1\bb8y Vibration 8Y - Bearing #8
Test Solenoid
S1\axial1 Axial Position #1 S1\IV1_STROKE IV1 Characterized Flow
Reference
S1\axial2 Axial Position #2 S1\IV2_STROKE IV2 Characterized Flow
Reference
S1\axial3 Axial Position #3 S1\IVR1 IV Reference for Normal
Control
S1\l20msv1t Main Stop Valve #1 Test S1\IVR2 IV Reference Modified for
Solenoid Bypass
S1\l20msv2t Main Stop Valve #2 Test S1\IVR3 IV Reference Intermediate
Solenoid
S1\L20PTR1 TRPG Trip Card Relay Driver 1 S1\IVR Intercept Valve Reference
(PTR #1)
S1\L20PTR2 TRPG Trip Card Relay Driver 1 S1\IP Inlet Pressure
(PTR #2)

S1\L20PTR3 TRPG Trip Card Relay Driver 1 S1\ip1 Inlet Steam Pressure #1
(PTR #3)
S1\l20rsv1t Reheat Stop Valve #1 Test S1\ip2 Inlet Steam Pressure #2
Solenoid
S1\l20rsv2t Reheat Stop Valve #2 Test S1\ip3 Inlet Steam Pressure #3
Solenoid
S1\l63qt_l Lube Oil Pressure Low Trip - S1\L33ETD1RESET ETD #1 Reset - Open when
Open to Trip Reset
S1\l63qt_l2 Lube Oil Pressure Low Trip 2 - S1\L33ETD1TRIPD ETD #1 Tripped - Open when
Open to Trip Tripped
S1\l63qt_l3 Lube Oil Pressure Low Trip 3 - S1\L33ETD2RESET ETD #2 Reset - Open when
Open to Trip Reset
S1\L63QLT LUBE OIL PRESSURE LOW S1\L33ETD2TRIPD ETD #2 Tripped - Open when
TRIP Tripped
S1\iv1_pos Intercept Valve #1 Position S1\L5E MANUAL TRIP Circuit
Feedback Activated
S1\iv2_pos Intercept Valve #2 Position S1\L12H_ACC_DEC L12H_ACC_DEC HP
Feedback ACCEL/DECEL RATE TOO
HIGH, LOSS OF PROT SPD
SIG
S1\iv1_out Intercept Valve #1 Servo S1\L14TNH_DEV SPEED DEVIATION ABOVE
LIMIT - TRIP
S1\iv2_out Intercept Valve #2 Servo S1\L5E_DCS EMERGENCY TRIP FROM
BOP DCS
S1\iv1_out_cur Intercept Valve #1 Servo S1\L5E_GT_PB Emergency trip from Gas
Current turbine PB
S1\iv2_out_cur Intercept Valve #2 Servo S1\L14HR HP Speed - Zero Speed
Current
S1\L14HP HP Speed - Turbine Trip Level S1\EGD_WD_TRIP Watchdog Timer Trip Signal
S1\L14H_ZE VPRO HP Zero Speed S1\L12H Primary Overspeed Latch Trip
s1\L83WW_GT GT in Waterwash mode S1\L12H_P VPRO HP Overspeed Trip
S1\L1QLTRIP Lube Or Hydraulic Oil Trip S1\L4T Master Protective \ Turbine
Trip
S1\L63HQLT HYDRAULIC FLUID S1\L4 Turbine Reset
PRESSURE LOW TRIP
S1\L26HPEXT HP EXHAUST S1\L10PLU_R PLU Event Input - Ld Ref Rate
TEMPERATURE HIGH TRIP Select
S1\L26L1SLST L-1 STAGE STEAM S1\L63HQET EMERGENCY TRIP HEADER
TEMPERATURE TRIP TRIPPED
S1\L26EXHT HIGH EXHAUST S1\hrhp1 Hot Reheat Steam Pressure
TEMPERATURE TRIP #1
S1\L63EVT EXHAUST VACUUM TRIP S1\hrhp2 Hot Reheat Steam Pressure
#2
S1\L83ETDOF_TRP Off-Line ETD Test Trip S1\hrhp3 Hot Reheat Steam Pressure
#3
S1\L26HPTMPHT HP STEAM TEMPERATURE S1\l5e_stc EMERGENCY TRIP PB
HIGH TRIP FROM STC
S1\L26RHTMPHT REHEAT STEAM S1\l5e_fs EMERGENCY TRIP PB AT
TEMPERATURE HIGH TRIP FRONT STANDARD
S1\FLX_CLP_FAIL STM to Generator Flex S1\l5e_dcs_pb EMERGENCY TRIP FROM
Coupling Failure Trip REMOTE PB #2

S1\L39AT Axial Monitor Trip S1\L12H1 Selected Overspeed Setpoint
Exceeded
S1\L39DET Differential Expansion Trip S1\cv1_out CV1 Inlet Control Valve Servo
S1\L39VT Vibration Trip S1\cv1_out_cur CV1 Inlet Control Valve Servo
Current
S1\LBORT ROTOR BORE STRESS TRIP S1\cv1_pos Control Valve #1 Position
Feedback
S1\L3VALVES_C PRE-ROLL STEAM VALVE S1\CV1_STROKE CV1 Characterized Flow
POSITION PROBLEM Reference
S1\L39THRUST High Thrust Trip S1\cv2_out CV2 Inlet Control Valve Servo
S1\L4T_GT GT Trip to ST S1\cv2_out_cur CV2 Inlet Control Valve Servo
Current
S1\cv2_pos Control Valve #2 Position S1\L12HA PRIMARY OVERSPEED TRIP
Feedback
S1\CV2_STROKE CV2 Characterized Flow S1\DEXROC_HP HP Differential Expansion
Reference Rate of Change
S1\L12HA_P EMERGENCY OVERSPEED S1\DEXROC_RH RH Differential Expansion
TRIP Rate of Change
S1\ev_p1 Exhaust Vacuum #1 S1\IP_P Inlet Pressure Feedback
S1\ev_p2 Exhaust Vacuum #2 S1\IPC IPC Control Reference
S1\ev_p3 Exhaust Vacuum #3 S1\IPL_FL Inlet Pressure Fixed Level
Limit Reference
S1\L30COMM_IO IO PACK COMMUNICATIONS S1\IPL_RS IPL Rate Sensitive Control
FAULT Reference
S1\dv Generator Volts S1\IPL_L Inlet Pressure Limiter Low
Limit
S1\dvar Generator Vars S1\L39AXT Axial Position Trip
S1\dwatt Generator Watts S1\L39AXFT Two or More Axial Probes
Failed - TRIP
S1\C_MODE_CMD Control Mode Command S1\L39APFT Axial Probe Failure and Axial
Position Trip
S1\C_MODE_STAT Current Control mode state S1\L39DE1T Differential Expansion #1 Trip
S1\DIFF_EXP1 Diff Expansion #1 S1\L39DE2T Differential Expansion Probe
#2 High Trip
S1\DIFF_EXP2 Diff Expansion #2 S1\fsp First Stage Shell Pressure
S1\diff_exp1a Differential Expansion Probe #1 S1\L30WD1SU WATER DETECTED 1STG
BOWL UPPER
S1\diff_exp1b Differential Expansion Probe S1\L30WDHPEL WATER DETECTED HP
#1B EXHAUST LOWER
S1\hyd Hydraulic Fluid Pressure S1\L30WDHPEU WATER DETECTED HP
EXHAUST UPPER
S1\ECCET1 Eccentricity S1\L30WDIPLSL WATER DETECTED IP LAST
STAGE LOWER
S1\ECCET2 Eccentricity 2 S1\L30WDIPLSU WATER DETECTED IP LAST
STAGE UPPER
S1\ECCET3 Eccentricity 3 S1\L30WDRHBL WATER DETECTED RH
BOWL LOWER
S1\L30WDRHBU WATER DETECTED RH BOWL S1\L3SWC_RB_R Stator Coolant Water Runback
UPPER - Ld Ref Rate Select
S1\L30WDSSH WATER DETECTED STEAM S1\L26IS_L_OK Inlet Steam Temperature
SEAL HEADER Above Low Limit

S1\L30WDSSN2 WATER DETECTED STEAM S1\L26IS_H_OK Inlet Steam Temperature
SEAL SUPPLY N2 Below High Limit
S1\L30WDSSN3 WATER DETECTED STEAM S1\STAT_R <R> UCVx Controller
SEAL SUPPLY N3 State
S1\L30WDSSN4 WATER DETECTED STEAM S1\STAT_S <S> UCVx Controller
SEAL SUPPLY N4 State
S1\tt_exh1 Exhaust Steam Temperature #1 S1\STAT_T <T> UCVx Controller
State
S1\tt_exh2 Exhaust Steam Temperature #2 S1\L26GSEXHA GLAND SEAL EXHAUST
TEMPERATURE HIGH
S1\tt_exh3 Exhaust Steam Temperature #3 S1\L26TBFA TB MONITOR-NORM MAX
FRONT TEMP PRE-ALARM
S1\L26SS_H Stm Seal Temp is Above Allow S1\L26TBFDA TB MONITOR-FRONT DIFF
Limit TEMP PRE-ALARM
S1\L26SS_L Stm Seal Temp is Below Allow S1\L26TBFDHA TB MONITOR-FRONT DIFF
Limit TEMP ALARM
S1\crhp1 Cold Reheat Pressure #1 S1\L26TBFHA TB MONITOR-NORM MAX
FRONT TEMP ALARM
S1\crhp2 Cold Reheat Pressure #2 S1\L26TBRDA TB MONITOR-REAR DIFF
TEMP PRE-ALARM
S1\crhp3 Cold Reheat Pressure #3 S1\L26TBRDHA TB MONITOR-REAR DIFF
TEMP ALARM
S1\CRHP_P1 Cold Reheat Pressure (HP S1\L26TBRA TB MONITOR-NORM MAX
Turbine Exhaust) #1 in PSIG REAR TEMP PRE-ALARM
S1\CRHP_P2 Cold Reheat Pressure (HP S1\L26TBRHA TB MONITOR-NORM MAX
Turbine Exhaust) #2 in PSIG REAR TEMP ALARM
S1\CRHP_P3 Cold Reheat Pressure (HP S1\L26L1SLS_DIF L-1 STAGE STEAM
Turbine Exhaust) #3 in PSIG TEMPERATURE DIFF
S1\bhdr Bearing Header Pressure S1\L26L1SLSA L-1 STAGE STEAM
TEMPERATURE HIGH
S1\L27DZ 125VDC Undervoltage S1\L26CTH_ALM CONTROL PANEL
TEMPERATURE HIGH
S1\CVR_VPL Control Valve Reference - Valve S1\CVR_VPL_CTL VPL Control Correction CVR
Position Limit

2.6 How to Shelve and Place Alarms Out of Service
With the release of ControlST* V04.04, the feature, Alarm Out of Service was provided. In ControlST V04.06, Alarm
Shelving is provided and Alarm Out of Service was enhanced. These features are similar and only apply to process alarms.
The ControlST V04.06 release also includes Alarm Viewer dedicated Out of Service Alarm and Shelved Alarm displays to
reduce alarm information on the Live Alarm Data display.
This document contains the following procedures:
• Enable Alarm Shelving and Alarm Out of Service

• Assign user privileges
• Enable alarm shelving attribute
• Shelve alarms
• View shelved alarms
• Re-shelve alarms
• Unshelve alarms
• Place alarms out of service
• View out-of-service alarms
• Place alarms in service
2.6.1 Prerequisites
Prior to shelving or placing alarms out-of-service the following are required:
• ControlST V04.06 must be installed.

• Alarm Out of Service and Alarm Shelving properties must be enabled.
• User must be assigned a role with the appropriate privileges.
• Individual alarms must have the Alarm Shelving attribute enabled.
2.6.2 Documents
Refer to the following documents for additional information:

• ToolboxST User Guide for Mark* Controls Platform (GEH-6700), the section, Users and Roles

2.6.3 Enable Alarm Shelving and Out-of-service
➢ To enable Alarm Shelving and Alarm Out of Service
When the Alarm Viewer is running and the Live Alarm Data tab is selected, the toolbar displays icons that indicate enabled
features:
When an icon is clicked, it becomes highlighted to indicate that the selected display is active. Clicking it again toggles it
back , activating the Live Alarm Data display.
Note If no icons are selected, the Live Alarm Data display is active. If the Alarm Shelving or the Alarm Out of Service
feature is not enabled, the and the do not display.

2.6.4 Assign User Privileges
For Alarm Shelving, each user must have the Alarm Privilege and the Alarm Shelving Privilege enabled. For Alarm Out of
Service, each user must have the Alarm Privilege and the Alarm Service Privilege enabled.
➢ To assign user privileges: from the System Information Editor, assign each user Name (for example Smith) a
Role with the appropriate privileges enabled (for example operator

2.6.5 Alarm Shelving
Note The following procedure must be repeated for each alarm before it can be shelved.
➢ To enable the Alarm Shelving attribute
➢ To shelve alarms: from the Live Alarm Data display, select the alarm(s) to shelve (highlighted in blue).

➢ To view Shelved Alarms

➢ To re-shelve alarms

➢ To unshelve alarms
Note Shelved Alarms are automatically unshelved when the Shelved Time Remaining goes to zero.

2.6.6 Alarm Out of Service
Note Alarms placed out of service remain in that state until placed back in service by the operator or the controller is
restarted.
➢ To place alarms out of service

➢ To view Alarms Out of Service
➢ To place alarms in service

2.7 How to Configure Alarm Parent Child
Note To enable this feature refer to the section Enable Alarm Parent Child
With the release of ControlST V04.07, the Alarm Parent Child feature is available. This feature uses the parent child
configuration in the ToolboxST application for each variable that is defined as an alarm. The configuration in the ToolboxST
application creates an alarm hierarchy. The top most alarm is the parent alarm, which can be configured in application code as
an indicator that there are one or more alarms under the parent that need attention. The parent/child criteria can then be used
in an Alarm Viewer filter to selectively display only the parents or children in the live alarm data. This parent child
association is evaluated in the Alarm Viewer when alarms are to be displayed. The feature is enabled through a property in the
ToolboxST System Information Editor.
The symbol and the foreground and background color used to display the Parent and Child icons in the Alarm Viewer are
selected in ToolboxST System Editor. If the symbol selected is None, no Parent or Child icon displays. The following figure
shows the symbols configuration in the ToolboxST application.
Note When selecting colors, unnamed colors display the RGB code in place of the name in the data grid.
The symbol and color selected will display for parents and for children.
After enabling the Alarm Parent Child feature and configuring the symbol for the parent and child icons, the variables must be
configured in the controller to establish the parent child associations. The following procedure shows the ToolboxST
application configuration to define four Boolean variables that are enabled as process alarms with one parent and three
interconnected child alarms.
➢ To configure alarms in the controller configuration
From the Component Editor Software tab Tree View ,

select Variables .
From the Summary View , select a variable and configure

the Parent Alarms and Child Alarms as required.
This configuration can be visualized using the following diagram. In the application code defined in the ToolboxST
application, any combination of alarms available for display will be represented in the hierarchy as shown.

The diagram is read as follows:
A1 has children A2, A3, and A4.
A2 has children A3 and A4.
A3 has child A4.
2.7.1 Live Alarm Display

The Live Alarm display will show alarms based on the filter selected and the display mode selected. The parent and child
symbols will be shown for all alarms displayed on the filtered Live Alarm Data display. The Dynamic Priority display, the
Shelved Alarm display, and the Out of Service Alarm display will not show the parent child associations.
Parent or child alarms can be identified by the symbol or in front of the variable name of the alarms being
displayed. The symbol represents the position in the hierarchy, based on the set of alarms available at the time the alarms are
being displayed.
The following figure shows the all BoolA* alarms on screen. No hierarchy is displayed at this point but the alarms position in
the hierarchy is denoted by the or symbol.
The user can select the or symbol to see the alarms that are available in the specific alarms hierarchy for that
alarm. When the symbol is selected, the list of all available child alarms in the defined hierarchy is displayed in a dialog
box.
Note This list excludes any alarms that have been shelved or placed out of service.
The following figure shows the parent alarm selected, along with all child alarms that are available. Both displays can be used
to interact with the alarms.

When a child alarm is selected, the child name displays in the dialog box header, and all alarms up to the parent display in the
grid. In the following figure, the alarm A3 is selected. The dialog box displays all alarms available up the hierarchy (in this
example A2 and A1).
2.7.2 Filtering
The Parent Child filter option has been added to the filter definition. This option can be used to manage the alarms that are
displayed using the parent or child configuration information. The filtering selections are Parents Only, Children Only, and
Unused. Additionally, there is a check box selection Include Non-Parented Alarms. This allows alarms that are not parented to
also be displayed.

Note The Parent Child filter option is only used when displaying alarms on the Live Alarm Data tab. The filter has no effect
on any of the other alarm displays. This option is hidden if the Alarm Parent Child feature is not enabled.
When Parents Only is selected on the existing applied filter, the display will be as follows:
Changing to Children Only displays the following:
An Include Children option is available for Plant Area filtering.
In this example, when Include Children

and Plant.TG.GasSystem are selected,
then alarms with the plant area
Plant.TG.GasSystem .Dln ,
Plant.TG.GasSystem .Pump1 , and
Plant.TG.GasSystem .Valve1 will
display in the alarm viewer when this filter
is applied .

2.8 How to Configure Mark* VIe Controller Frame State
Timeouts
A frame is a unit of time in a running controller. It can be 10, 20, 40, 80, 160, or 320 ms. A frame state represents a
processing state inside a single frame. The four processing states are: Input, Application, Output, and Idle.
Note Contact your GE Energy product support representative for correct time-state values.
Each frame state has a timeout value. When that timeout is reached, the controller switches to the next state regardless of
whether it has finished processing the current state. It is possible to configure the values for input, application, and output
frame state timeouts. Before these values can be changed, the ShowEnableConfigFrameTimeouts parameter in the
GlobalValues.xml must be set to True.
➢ To set the ShowEnableConfigFrameTimeouts parameter

1. Close the ToolboxST application.
2. From the Windows® Explore Tools menu, select Folder Options.
3. From the View tab, select Show hidden files and folders and click Apply and OK.
4. Navigate to the location for document and settings folders, for example: C:\Documents and Settings\[logged-in user]
\Local Settings\Application Data\GE Energy\ToolboxST\GlobalValues.xml.
5. Open GlobalValues.xml with Notepad.
➢ To configure the frame state timeouts from the System Editor, double-click a Mark VIe component.

If the component has password protection enabled for design modification, the Enter Password – Modify Design dialog
box displays.

Note Frame state timeout values must be in multiples of the controller tick size (currently 1 ms).
Configuring frame state timeouts causes a major difference in the configuration. The
controller must be restarted.
Attention

2.9 How to Upgrade a BPPB-based I/O Module to a
BPPC-based I/O Module
This content has been moved to the Mark VIe and Mark VIeS Control Systems Volume I System Guide (GEH-6721_Vol_I), the
section Migrating to BPPC-based I/O Packs.

2.10 How to Configure Mark* VIe Control I/O Modules for
Expansion in an EX2100e Excitation Control
This document provides the procedure to configure a Mark* VIe control component
for a typical set of I/O modules that are used for I/O expansion in the EX2100e
excitation control. It is intended for ToolboxST* application users who know how to
configure exciters, but may not know how to configure the Mark VIe control. Also
included are instructions to map the I/O to EGD pages that are communicated
between the EX2100e control and the I/O modules on a Unit Data Highway (UDH)
network, and enter the correct barcode into the software configuration file.
Communications may also be configured on a Control Data Highway (CDH).

Refer to the ToolboxST User Guide for Mark* Controls Platform, the section, Networks
(GEH-6700).
When an EX2100e control includes Mark VIe control expansion, the I/O modules
typically included are listed in the following table.
Exciter I/O Modules

Part # Description
IS230TDBSH6A Simplex bi-directional discrete I/O, with PDIO
IS230STAOH2A Simplex analog outputs, with PAOC
IS230SRLYH2A Simplex relay outputs, with PDOA
Refer to the following related documentation:

ToolboxST for Mark* Controls Platform (GEH-6700)
Mark VIe Control, Volume I System Guide (GEH-6721)
2.10.1 Configure a Mark VIe Control Component

➢ To configure a Mark VIe control component
1. Open the ToolboxST application to display the System Editor .
2. From the File menu, select New System.
3. Enter a name and location and click OK. The new system and its default properties display in the Tree View and
Property Editor. A UDH is automatically added to the system.
4. From the Tree View, right-click the system and select Insert New, Controller, and Mark VIe Controller.
5. From the Mark VIe Creation Wizard, enter a name for the controller, include all libraries, and click Finish.
6. From the Tree View, double-click the new component to display the Component Editor.

7. Set the Platform and Redundancy properties as follows:
From the General tab

Property Editor, set
Platform to the correct
controller (such as
IS420UCSBH1A) and
Redundancy to
Simplex.
8. From the Tree View, select Network Adaptor 0. Verify that the Network property is UDH, and set the correct IP
Address in accordance with the following table.
Note For a single EX2100e control installed on the UDH, the IP address is typically set to 192.168.101.101.
EX2100e Control Component Default IP Addresses

Component IP Address
M1 Control 192.168.101.116
M2 Control 192.168.101.117
C Control 192.168.101.118
Touchscreen 192.168.101.119
VersaMax or I/O 192.168.101.101

From the Hardw are
tab Property Editor,
set Netw ork
Redundancy to
Sim plex.
9. From the Tree View, right-click Distributed I/O and select Add Module.
10. From the Add Module wizard, verify that the Redundancy is Simplex, select the PDIO I/O module, and click Next.
11. From the Add Module wizard, select Module Required, set the properties in accordance with the following table, and
click Next.
Required Boards and Modules
Terminal Board
Type TDBS
HW Form H6A
Bar Code Refer to the section, Enter a Barcode
I/O Module
HW Form H1A
ENET1 Port IONet1
12. Check the settings and click Finish.

13. Repeat steps 9 through 12 to add a simplex PAOC I/O module with terminal board STAO H2A, and a simplex PDOA I/O
module with terminal board SRLY H2A. When one of the three I/O modules in the Tree View is selected, the
Summary View displays a graphic view of the module.
Note To modify settings, double-click any I/O module to display the hardware configuration window.

2.10.2 Configure a Blockware Application
➢ To create a blockware application to drive the I/O modules
1. From the Software tab Tree View, right-click Programs and select Add Program. Enter a name for the program and
click OK.
2. From the Tree View, right-click the program and select Add Task. Enter a name for the task and click OK.
3. From the Tree View, right-click the Task and select Add Block. Select a block, such as Timer, and click OK.
4. From the Summary View, right-click the block and select Block Help to display block information.
5. From the Summary View, right-click the block and select Edit Block Pins to configure the pin connections and
values. Add blocks and variables, as necessary, to define the software configuration.
6. From the EGD tab, map the variables to be exchanged with the EX2100e control and complete mapping in the EX2100e
control configuration file.
Note Refer to the ToolboxST for Mark* Controls Platform (GEH-6700), the sections, Block Diagram Editor, and EX2100e
Component Editor.
7. Perform a Build command. The Component InfoView Log tab displays any errors.
Note If the UCSB controller IP address was changed or the controller has not been previously loaded, from the Device
menu, select Download and Controller Setup and follow the wizard instructions. A USB flash drive is required for a
UCSB controller.
8. Perform a Download command as follows:

a. From the Device menu, select Download and Download Wizard. The Download Mark VIe Controller window
displays all I/O modules that are defined in the configuration.
b. Proceed with the download. The first pass may be needed to configure just the UCSB controller; another pass may
be required to configure the I/O modules.
9. Open the Download wizard again to confirm the process. The Download wizard confirms that all software components
for all I/O modules that are present have been downloaded (indicated by symbols). I/O modules that are not present are
indicated by a symbol. The symbol indicates that software downloads may not have completed, and an additional
restart and Download command may be required.

In the following figures, the blockware sequences through each of the output relays on TDBS and SRLY, energizing each
for one second, one at a time. In addition, it drives sawtooth (ramp) patterns to the analog outputs on the STAO I/O
module.
Variables created to
drive I/O modules
Blockware pattern used

to drive I/O modules.

Timer configuration used as a 1-second
sequencing time base for the blockware.
Type conversion extracts low

word (UINT) from long integer.
Type conversion converts

integer to analog real number
Subtraction creates a down -sloping

sawtooth from the up-sawtooth .
Counter configuration makes a

12-step sequence to step the relays.

Type conversion makes an unsigned
integer from a long integer.
Decoder block makes a 12-line shift

register for the relay walking patern
Hardware settings
for the PDIO
discrete I/O pack
with TDBS
terminal board

Hardware settings
for the PAOC
analog output
pack with STAO
terminal board
Hardware settings
for the PDOA
discrete output
pack with SRLY
terminal board
Output configuration for

the PDIO/TDBS module

Output configuration for
the PAOC/STAO module
Output configuration for PDIO/SRLY

(the red X indicates the module is not present )
Input status for the

PDIO/TDBS module

2.10.3 Enter a Barcode
For the I/O expansion controller to communicate properly with the I/O modules and terminal boards, the correct barcode from
the circuit board (not the I/O module) must be entered into the software configuration file. If the hardware was shipped before
the software, or if the board has been replaced, the barcode must be properly set. The barcode may be entered either manually
(if you are able to get to and read the barcode) or from the controller itself, as described in the following procedure.
➢ To enter the barcode for I/O expansion

1. From the ToolboxST application, open the auxiliary I/O module and select the Hardware tab.
Three hardware I/O modules

should be displayed.
2. Double-click an I/O module (PAOC is used for this example) and modify the barcode as follows:
The Bar Code field will either

display 0 or an incorrect barcode .
Click inside the Bar Code field to

display a drop down button on the
right .
Click the Bar Code drop down

button to display a barcode that is
based on the installed hardware .
Click OK.

Select the line with the
correct barcode for the
I/O module and click OK.
Click OK .
Verify that the I/O

module barcode
details are displayed
and click OK .

Click OK .
3. Repeat steps 1 and 2 for all hardware modules.

4. Perform a Build and Download for all modified I/O modules as follows. The Download wizard displays the software
components for all I/O modules that have been downloaded (indicated by symbols). Modules that are not present and
should be downloaded are indicated by a symbol. The symbol indicates that software downloads are required.
Select all I/O modules

and components to
build and download
and click Next.
5. After the build and download is complete, shut down and restart the power to synchronize all I/O modules with the
controller.

Notes

3 WorkstationST Application
3.1 How to Interface to Third-party Clients Using the
WorkstationST* OPC® DA Server
Warning
The ToolboxST application provides a feature called an OLE for Process Control (OPC) DA Server. Third-party OPC DA
clients can connect to this server to obtain live variable values. The OPC DA Server is compliant with the OPC DA 3.0 and
the OPC DA 2.05 specifications. The server also has an optional client that can be configured to gather variable value data
from external OPC DA servers. The server is configured and monitored through the WorkstationST Component Editor of the
ToolboxST application.
OPC DA Server/Client Setup
3.1.1 Prerequisites
OPC is based on Microsoft® DCOM. When the OPC DA client resides on the same computer as the OPC DA Server, the
client must have default DCOM access. When the client runs as a service on the same computer as the WorkstationST
application, no DCOM configuration is needed to allow the client to talk to the OPC DA Server. When the client is running as
an interactive process, then INTERACTIVE should be configured with default access for the computer’s DCOM default
access setting. Refer to the WorkstationST OPC DA Server Instruction Guide (GEI-100621), the section Windows® XP
Workgroups Example for information on when the OPC DA client resides on a remote computer.
Firewall products such as Norton™ or other software firewalls can have adverse effects on DCOM client/server
communications. The WorkstationST application configures the Windows firewall to the DCOM TCP port 135.
WorkstationST Application GEH-6808N Instruction Guide 141

3.1.2 Configuring the WorkstationST OPC DA Server
Configuration of the OPC DA Server is described in the ToolboxST User Guide for Mark* Controls Platform (GEH-6700),
the section OPC DA Server Tab. Although default settings are typically used, the following can apply.
• Use the Maximum Client Rate setting to control how fast data can be requested by an OPC DA client. The default is
320 milliseconds.
• Use the Enable Client Writes setting to allow an OPC DA client to write, as well as read variable values. These can
include variables for all EGD consumed devices, as well as variables from other WorkstationST features (such as
Modbus) and other OPC DA Server data from the OPC DA client.
• All variables written to the OPC DA server or read from other servers can be placed onto one or more EGD
(redundant) pages. These pages can be defined in one WorkstationST computer as Primary pages, with a second
WorkstationST computer configured as a secondary producer. The primary producer produces the data if the source for
the variables is healthy. If the primary producer stops, the secondary producer takes over but stops production if the
primary resumes. Refer to the ToolboxST User Guide for Mark* Controls Platform (GEH-6700), the section
Redundant EGD Produced Pages. A sample setup is as follows.
Primary and Secondary EGD Redundant Produced Page

➢ To configure an EGD produced page
1. From the Start menu, select Programs, GE ControlST, ToolboxST, and ToolboxST to display the System
Editor.
2. From the Tree View, double-click a WorkstationST component.

3. Configure another WorkstationST component as a secondary producer.
• Add an EGD page in the second WorkstationST component, set its Redundancy to Secondary, and select the
primary page for it to reference.
• Add the same variables from the previous step to the Secondary WorkstationST component’s OPC DA Server tab
Client Driven Variables item.
➢ To configure a Mark VIe component to consume a variable

From the ToolboxST System Editor, double-click a Mark VIe component to display the Component Editor.

➢ To build and download the Mark VIe component
1. From the toolbar, click the Build button.
2. From the toolbar, click the Download button.
Monitor the values in the Mark VIe component. The above example has a 200 millisecond produced page with a health
timeout of 50. As long as a client writes to one of the variables, Wkstn1.PrimeRib0001 or Wksnt1.PrimeRib0002, within
five seconds, the producer remains healthy.

➢ To monitor values in the Mark VIe component
Verify that both the primary and secondary OPC DA Servers are working properly. Refer to the ToolboxST User Guide for
Mark* Controls Platform (GEH-6700), the section Test OPC DA Client, and perform the following:
• Configure a test client to connect to Wkstn1 and write a value to Wkstn1.PrimeRib0001. The value should display as
healthy (True) at the Mark VIe VAR_HEALTH_1 block.
• Configure a test client to connect to Wkstn2 and write a value to Wksnt2.PrimeRib0001. When the client connected to
Wkstn1 has not written for five seconds, and a value is written to Wkstn2, the Mark VIe value should display as healthy
(True) at the Mark VIe VAR_HEALTH_1 block.
• Stop the primary OPC DA Server and confirm that the values from the secondary OPC DA Server remain healthy as long
as the secondary client is periodically writing to at least one variable.

3.1.3 Connecting from an External OPC DA Client
When connecting to an OPC DA Server, clients allow a user to browse for the server’s name. The connection name for the
OPC DA Server is GeCssOpcServer. When connecting from an interactive client (a client running on the user’s desktop),
the interactive user must be included in the computer’s default DCOM Access Permission
➢ To confirm DCOM Access Permission
1. Right-click the Start button and select Command Prompt Here to display the Command Prompt window.
2. Enter dcomcnfg and pressEnterto display the Component Services window.

➢ To add a user to DCOM Access Permission
Note Restart your computer.
Interactive test clients most can now connect to the OPC DA Server . The ToolboxST application includes an interactive OPC
DA test client, accessed from the View menu of a WorkstationST Component Editor.

3.2 How to Configure and Troubleshoot a Trip Log in the
WorkstationST* Application
Warning
A trip log is a file created by the WorkstationST Recorder when a trip event occurs. The file consists of high-frequency data
from controller capture buffers and DDRs, and lower-frequency data collected by the Recorder over EGD. A resample of
lower-frequency data is performed during the creation of the trip.
In the controller, high-frequency data must be collected through capture buffer blocks and/or Dynamic Data Recorders
(DDR). A trip log can consist of multiple capture buffers and DDRs. The configuration of the capture buffers and DDRs that
are part of a trip log must be configured identically, except for the signals being collected.
Note The use of the Dynamic Data Recorders as part of a trip log is not supported in the Mark* VI controls. The UPL_
TYPE parameter is not available in all controllers.
Tip � One of the most common mistakes in creating a trip log is not using the same event for all the buffers in the trip log. If
a trip log is required for different events, then separate trip logs must be created for each event.
➢ To add a capture block and configure the controller

1. Open the ToolboxST application and from the File menu, select Open System, locate and select the appropriate
system. The System Editor displays.
2. From the System Editor Tree View, double-click the controller to display the Component Editor.

Pin Connection or Value options (all options are not available on all Pins)
• Browse Globals displays a Select a Variable dialog box to allow selection of global variables.
• Browse Local displays a Select a Variable dialog box to allow selection of local variables.
• True (Immediate) sets the Connection or Value to True.
• False (Immediate) sets the Connection or Variable to False.
• Disabled (Capture block disabled status, Enumeration Value)
• Waiting (Capture block is enabled and waiting for the trigger, Enumeration Value)
• Capturing (Capture block is capturing data, Enumeration Value)
• Complete (Capture block is done capturing and is ready for upload, Enumeration Value)
• LockedComplete (Capture block is done capturing and is ready for upload (0x8003), Enumeration Value)
Parameter Connection or Value options (all options are not available on all Parameters)
• Browse Globals displays a Select a Variable dialog box to allow selection of global variables.
• Browse Local displays a Select a Variable dialog box to allow selection of local variables.
• Normal (Collect data until buffer is full, Enumeration Value)
• Circular (Collect data until stopped, Enumeration Value)
• Only (Collect data only when trigger condition is TRUE, Enumeration Value)
• EQ (Trigger signal equals the trigger, Enumeration Value)
• GT (Trigger signal is greater than the trigger, Enumeration Value)
• GE (Trigger signal is greater than or equal to the trigger, Enumeration Value)
• LT (Trigger signal is less than the trigger, Enumeration Value)
• LE (Trigger signal is less than or equal to the trigger, Enumeration Value)
• NE (Trigger signal is not equal to the trigger, Enumeration Value)
• Edge (Trigger condition must be FALSE prior to becoming TRUE, Enumeration Value)
• Level (Trigger condition must be TRUE, Enumeration Value)
• Manual (Buffer is manually uploaded by a user, Enumeration Value)
• Automatic (Buffer is automatically uploaded by the data collection system, Enumeration Value)
• OnTrip (Buffer is automatically uploaded by the data collection system and is incorporated as part of the trip log,
Enumeration Value)

Additional trip logs can be configured through the Recorder feature in the WorkstationST component. If the capture
buffer/DDR is going to be part of a trip log configured through the Recorder, set the UPL_TYPE parameters to Manual as
shown below.
3.2.1 Configuring the WorkstationST Recorder

The automatic upload of trip logs from a controller and the recording of low-frequency data are handled by the
WorkstationST Recorder. The Recorder must be enabled and configured for these functions.
➢ To enable and upload trip logs from the Recorder

1. From the System Editor Tree View , double-click a WorkstationST item to display the Component Editor.

2. In this example, from the Component Editor Tree View, select the variables that are attached to the Status pin as
shown in the Edit Block Pin Connection dialog box of the capture buffer or the DDR status.
3. From the Component Editor toolbar, click Build , and then click Download .
Note No validation is performed on the signals in the capture buffers to verify they are on EGD. The trip log will still run,
but there will only be high-frequency data from the capture buffer for these signals. The Recorder runtime will mark the
collection as having at least one unhealthy variable.
3.2.2 Displaying Trip Log Data

➢ To display trip log data
Or
1. From the Windows® Start menu, select All Programs, GE ControlST, ToolboxST, and Trender to open the
Trender window.
2. From the Trender File menu, select Open and browse to locate and select the .dcaST file. Click Open to display the
Trender with all signals in the trend.

Troubleshooting a Trip Log Failure
Problem Possible Causes/Solutions
Trip Log is not generated Verify the Recorder displays the trip log and is running without error.
Verify the capture buffers and DDRs that make up the trip log are being
triggered by the same event.
Verify the capture buffers and DDRs that make up the trip log do have the
same configuration (such as pre-samples, post-samples, sample period
multiplier). If the capture buffers are in different tasks, check to see if the task
multipliers are the same. DDRs are not part of a task, so they do not have
task multipliers. In this case the task multipliers for the capture buffers would
need to be 1.
Recorder Status Errors Possible Causes/Solutions
Capture Buffer Upload failed. The Recorder was unable to connect and upload the capture buffer data
from the controller. Check the connectivity between the WorkstationST HMI
and the controller.
Failed to upload the variable information from The Recorder was unable to connect and upload the capture buffer variable
the device. Verify that the device is information from the controller. Check the connectivity between the
accessible. Retry will occur in one minute WorkstationST HMI and the controller.

3.3 How to Configure the Alarm Server in the
Warning
This document describes how to configure an Alarm Server in a system to provide alarms and events for display on the
WorkstationST Alarm Viewer.
• Configure the Alarm Server

• Display the Alarm Viewer
• Configure redundant Alarm Server operation
3.3.1 Documents

• The section, How To Configure Alarm Capability in the ToolboxST Application in this manual
3.3.2 System Topology

To configure an Alarm Server in the system, you first must understand the system configuration and the components that can
generate alarms and events. Some of the types of components in the system that can generate alarms and events include:
• Mark* VI and Mark VIe controllers and EX2100 exciters

• Workstation computers with the WorkstationST application configured to use the Alarm Scanner feature
The following example displays a simplified network and the components used in this document.
EWS1, EWS2, and GT1_Server are computers with the ToolboxST and WorkstationST applications installed.
H1 and G1 are configured Mark VIe controllers.

The network configuration must be complete. Ensure the device name has an IP address, host name, and network scope
assigned and configured as required for the system. Additionally, the IP address and host name should be entered in the
Windows® hosts file (for example C:\WINDOWS\system32\drivers\etc\hosts for Windows 7) to allow host names to be used
in the tools such as the WorkstationST Alarm Viewer.

3.3.3 Single Alarm Server Configuration
This section describes how to configure a single Alarm Server for handling all alarm and events in the system. The
WorkstationST EWS1 is used to display the configuration details.
➢ To configure the Alarm Server

1. From the Start menu, select All Programs, GE ControlST, ToolboxST, and ToolboxST .
From the Tree View ,

double-click the
EWS1 item.

From the General
tab Tree View ,
select Features.
From the Summary

View , select the
Alarm Server
Feature and in the
Enabled column,
select True from
the drop-down list .
The Alarm tab

displays.

Tree View , select the
Consumed Devices
item.
From the Summary

View , select a device
and in the
Referenced column,
select Yes from the
drop-down list .
The Alarm Server

can now connect to
the selected devices
and process alarms
and events.
Note Only alarms and events from referenced devices will be processed by the Alarm Server on this computer.
Tip � The properties displayed in the Summary View can be selected and rearranged by right-clicking in the header row
and selecting Organize Columns.

From the
Alarm tab
Tree View ,
select the
Alarm Server
item.
A list of options

for the Alarm
Server displays.
A description of
each item
displays when
an option is
selected.
2. From the toolbar, click Build .
3. From the toolbar, click Download .

After the download, the Alarm Server starts and all alarm/events from H1 and G1 can be displayed.
Note The Alarm Viewer requires the IP address or host name of the computer configured with the Alarm Server, if it is not
on the same computer as the Alarm Server. The host name used must connect to the computer that contains the Alarm Server.

➢ To display the Alarm Viewer
1. From the EWS1 Start menu, select All Programs, GE ControlST, WorkstationST Alarm Viewer,
WorkstationST Alarm Viewer. The WorkstationST Alarm Viewer window displays.
2. From the View menu, select Connect.
From the Remote Connection To WorkstationST Alarm Server

dialog box , select the correct Alarm Server and clickOK .
3. From the View menu, select Show Live Alarms. A connection is made to the specified Alarm Server running on the
workstation (such as EWS1). Live alarms from H1 and G1 display.

3.3.4 Redundant Alarm Server Configuration
➢ To configure the system for redundant Alarm Server operation
1. Follow the steps of the procedure To configure the Alarm Server for GT1_Server and EWS2 WorkstationST computers.
Ensure the following are configured the same on both computers:
• From the General tab Features item, set the Alarm Server feature to True.
• From the General tab Consumed Devices item, configure the Referenced item for all Devices from which
alarms are to be configured.
• From the Alarm tab Alarm Server item, configure all options the same for both WorkstationST computers.
2. Configure the redundant Alarm server as follows:
From the System Editor

Tree View , select the
System item.
From the Property Editor

Redundant Alarm Server
section, select Primary
Alarm Server and select
EWS2 from the drop-down
list.
Select Secondary Alarm

Server and select
GT1_Server from the drop-
down list.
3. From the EWS2 Component Editor, click Build .
4. From the EWS2 Component Editor, click Download .

5. Repeat steps 3 and 4 for GT1_Server.
Note You must connect to the defined primary Alarm Server (EWS2).
6. From the EWS2 Component Editor, select Viewand select WorkstationST Alarm Viewer. The Alarm Viewer
window displays.

Or
♦ If the Alarm Viewer is running on a computer other than EWS2, from the Alarm Viewer View menu, select Connect.

If the primary Alarm Server fails, or the connection fails, the Alarm Viewer automatically switches over to the secondary
Alarm Server (GT1_Server).

When the primary Alarm Server becomes available, the Alarm Viewer automatically switches back to the primary Alarm
Server.

3.4 How to Configure the Alarm Scanner Feature of the
WorkstationST* Alarm Server
Warning
This document outlines the steps necessary to configure and use the Alarm Scanner feature of the WorkstationST Alarm
Server. The Alarm Scanner periodically samples Ethernet Global Data (EGD) data published from external control devices,
creating alarms and events based on the values read. These alarms and events are then available for display using the
WorkstationST Alarm Viewer.
Note The Alarm Scanner should not be used to generate alarms and events from any device that can generate its own alarms
and events, such as a Mark VIe controller.
The following procedures are defined in this document:
• Create an external device

• Configure network settings
• Configure EGD produced data
• Check for OPC DA Server runtime errors
• Correct signature and timestamp errors
• Configure the Alarm Scanner
• Display the Alarm Viewer
3.4.1 Documents
Refer to the following documents for further information:
• GEI-100620, WorkstationST Alarm Viewer

• GEI-100626, WorkstationST Alarm Server
• The section, How To Configure Alarm Capability in the ToolboxST Application in this manual
• The section, How to Configure the Alarm Server in a WorkstationST Computer in this manual

3.4.2 Existing System Configuration
Before the Alarm Scanner can be used, the following conditions must be true (screen shots are provided as examples):
• The system topology must be defined and components created.
• The Network addresses and host names must be configured for each device on the network.

• At least one workstation computer must be configured with the WorkstationST application and the Alarm Server, OPC
DA Server, and EGD Configuration Server Features enabled and configured.
The simplified system diagram below displays a workstation (Ews1) and an external device (PLC70). The PLC70 is the new
device to be added to the system. Ews1 is the existing workstation configured with the WorkstationST application.

3.4.3 Create an External Device
➢ To create an external device
From the Tree

View , right-click
the System item,
select Insert
New and
External
Device .
Enter a Name ( such as

PLC70 ) for the
External Device and
click Finish .

From the Tree View , select the
new external device ( such as
PLC70 ) .
From the Property Editor , enter

the external editor App Path and
Doc Path , or leave these blank
and select Enable EGD Editor ,
and set to True to use the
ToolboxST Editor .
3.4.4 Configure Network Settings

➢ To configure the network settings for the PLC70 external device
From the General tab ,

select Network Adapter 0 .
From the Property Editor,

enter the appropriate
Network settings.

3.4.5 Configure EGD Produced Data
➢ To configure EGD produced data for the PLC70 external device
1. From the System Editor, double-click the PLC70 item to display it in the Component Editor.
From the EGD tab ,

right-click Produced
Pages and select
Add Page.
Enter a unique page

name (such as
PRODPAGE 501 ).
Click OK .
From the EGD tab, select the new page ( PROPAGE 501 ).
From the Summary View select the Configuration tab

to display the grid for entering variables.

2. Enter variables corresponding to the EGD page layout of the component.
3. Set the Alarm attributes for the variables to be used with the Alarm Scanner.
Note Only Boolean and Numeric variables can be used by the alarm scanner.
Tip � The properties displayed in the Summary View can be selected and rearranged by right-clicking in the header row
and selecting Organize Columns.
Select and display the alarm properties

columns.
Set the value for each of these columns to

enable the alarm /event behavior desired.
Examples of the variables and alarm

attributes are displayed.
Note At this point the Alarm, Event, and Alarm On Zero attributes must be set to True, as appropriate, for each variable
expected to create an alarm or event in the Alarm Scanner
Alarm and Event attributes:

Alarm is used to generate alarms for the selected variable.
Event is used to generate an event when the variable changes state.
Alarm On Zero is used to generate an alarm when the value of the variable is false.
Note Analog Alarms must have at least one Alarm Condition defined.

To create an Alarm Condition , from the
Configuration tab, select a variable.
From the Property Editor, select Alarm Conditions and

click the ellipsis to display the Alarm Conditions editor.
The possible Comparison Operators

are: <, <=, =, >, >=, !=
Enter up to six different Alarm Conditions

for any one variable.
If more than one Alarm Condition is configured for a single variable, and more than one condition is true at a given point in
time, only one actual alarm will be generated. The precedence in choosing which alarm will be generated, from highest
priority to lowest, is:
• Any = condition that is met.

• The largest > or >= condition that is met. (For example, there are both a > 100 and a >50 alarm condition. If the
current value is 125, then the > 100 alarm will be generated. If the current value is 75, then the >50 alarm will be
generated.)
• The smallest < or <= condition that is met. (For example, there are both a < 10 and a < 20 alarm condition. If the
current value is 5, then the <10 alarm will be generated. If the current value is 15, then the <20 alarm will be
generated.)
When a given alarm condition is met, the generated alarm uses the base description plus the description for the specific Alarm
Condition that occurred. When the alarm returns to the normal state (no alarm condition is met), the alarm displays the base
description from the variable.
For Analog alarms containing alarm conditions, Alarm Help can be viewed for each condition definition, as well as the
urgency condition for each. For Boolean alarms, there is only one Alarm Help file because there are only True/False
conditions.
Note The Alarm condition name for an Analog Alarm variable values displays in the Alarm State column in Alarm Viewer.
4. When editing is complete, from the toolbar, click Save to save changes.
Note An external device provides a means to let devices in the ToolboxST system know what variables an actual device will
be communicating over EGD, and whether or not the Alarm Scanner should generate alarms and events for them. Sometimes
that device is communicating using a fixed EGD exchange signature and configuration time. It is important that the external
device is configured with this same signature and configuration time. Since the ToolboxST application changes the signature
and configuration time based on how changes were entered within the tool, it is possible for the signature and configuration
time to not match. If this is the case, then you will see errors in the OPC DA Server at runtime. To check for these errors, use
the following procedure.

➢ To check for OPC DA Server runtime errors: from the taskbar notification area, double-click the Status Monitor
icon.
Right-click OPC DA Server

and select View Additional
Status Detail.
An error similar to this displays.
➢ To correct signature and timestamp errors
From the External Device Component Editor,

select the Configuration tab, right-click the
Signature heading and select Edit Exchange
Signatures and Configurations Time.

Edit the External Devices EGD Exchange
Signature to match the actual device.
Click OK .
Repeat these steps for the Configuration Time.
3.4.6 Configure the Alarm Scanner

➢ To configure the Alarm Scanner in WorkstationST EWS1
1. From the System Editor, double-click the EWS1 item to display the Component Editor.
For proper operation, the Alarm

Server ( Alarm tab ) and the OPC
DA Server must be enabled.
From the General

tab, select
Consumed
Devices .
From the Summary

View , select the
PLC70 External
Device and in the
Referenced
column, select Yes .
Note Only alarms and events from the devices enabled will be processed by the Alarm Server on this computer.

From the Alarm tab , right-
click Alarm Scanner and
select Add Variable .
From the Tree

View , select
Variables .
Select the
Variable(s)
to be used by
the Alarm
Scanner to
generate
alarms/events.
Click OK .
Note Variables added to the Alarm Scanner without Alarm or Event attributes enabled will not generate an alarm or event in
the Scanner.
From the Alarm tab, select PLC70 and the variables selected
in the previous step display in the Summary View .

4. From the taskbar notification area, double-click the WorkstationST icon to display the WorkstationST Status
of Features dialog box.
Confirm the Alarm Server and OPC DA

features are running.
➢ To display the Alarm Viewer
Note You must connect to the defined Alarm Server (EWS1).
♦ From the EWS1 Component Editor, select View, and select WorkstationST Alarm Viewer. The Alarm Viewer
window displays.
Or
♦ If the Alarm Viewer is running on a computer other than EWS1, from the Alarm Viewer View menu, select Connect.


The Variable Name displays using the format
<external device name>.<variable name>.
Alarms and events generated by the Alarm Scanner can be acknowledged and reset from the Alarm Viewer and are recorded
in the historical alarm files. Refer to the WorkstationST Alarm Viewer Instruction Guide (GEI-100620), the section Historical
Alarms for additional information on displaying historical alarms.

3.5 How to Analyze Historical Alarm Data Using the
WorkstationST* Alarm Viewer - Online Mode
Warning
The WorkstationST Alarm Viewer normally operates in the online mode. The Alarm Viewer requires the complete setup of
the control system, especially one or more workstations, with the Alarm Server feature enabled and configured on each
workstation. The Alarm Viewer connects to the workstation and Alarm Server by host name. The tool reads and uses that
workstation's configuration to display the alarm data. Refer to the following documents for further information:

• The section, How to Configure Alarm Capability in the ToolboxST Application in this manual
• The section, How to Configure the Alarm Server in the WorkstationST Computer in this manual

In this example, a portion of the actual system is displayed. The diagram shows the H1 controller sending live alarms and
events on the UDH network. The Alarm Server running on Ews1 is configured to consume alarms and events from H1 and
has the Historical Alarms Option enabled. The Alarm Server writes the alarms and events to the historical alarm archive
directory. The WorkstationST Alarm Viewer reads and displays these alarms and events.

3.5.2 WorkstationST Status Monitor
The WorkstationST Status Monitor can be displayed to confirm the operation of the workstation.
➢ To display the WorkstationST Status Monitor
From the Ews1 workstation, in

the lower right corner of the
taskbar, double -click the
WorkstationST icon to
display the WorkstationST
Status Monitor: Feature
Status dialog box .
Or
♦ From the Ews1 workstation Start menu, select All Programs, GE ControlST*, WorkstationST, and
WorkstationST Status Monitor to display the WorkstationST Status of Features dialog box.

3.5.3 Configuring the WorkstationST Alarm Viewer
➢ To configure the WorkstationST Alarm Viewer
♦ From the Ews1 workstation Start menu, select All Programs, GE ControlST, WorkstationST Alarm Viewer, and
WorkstationST Alarm Viewer. The WorkstationST Alarm Viewer displays.
From the View menu, select

Connect and Show Historical
Alarms.
From the Remote Connection To WorkstationST Alarm Server dialog box,

select the Alarm Server to display the alarms. If the correct Alarm Server is not listed,
click Add a Connection , enter an IP Address or Host name and click OK to add
the Alarm Server to the list.
Once the correct Alarm Server is displayed and selected, click OK .
From the Options

menu, select Settings .

From the Tree View , select Alarm Viewer Settings , expand Local Settings,
select Alarm Configuration Root Path and set the path to the correct location.
The default is C:\Documents and Settings\All users\ Application Data\ GE

Energy\WorkstationST AlarmViewerConfiguration.
Select Use Local Workstation Alarm Configuration

and set to True to use the host workstation configuration.
Click OK to display the Alarm Viewer screen.
The status bar connection pane displays the name or IP address of the host
used as the source of the alarms. The name of the host is the computer that
the WorkstationST Alarm Viewer is currently connected to.
The Alarm Viewer is ready to display the historical alarm data.

3.5.4 Displaying Alarm Data - Unfiltered
➢ To display unfiltered historical alarm data

The requested alarm data displays.

The unfiltered request displays the most recent set of alarm data (including Process Alarms, Events, SOEs Holds and
Diagnostics) found. In this example, records up to the limit of 50,000 are displayed. This data is called the result set. The data
can be processed in the following ways:
• Print the data by right-clicking over the data and selecting Print Alarms from the shortcut menu, or by selecting Print
Alarm Data from the File menu.
• Export the data to a CSV file by selecting Export Alarm Data from the File menu.
• Copy and paste the data into other applications.
• Display the data with the WorkstationST Alarm Viewer by selecting:
Displays the raw detail data (default display).
Displays a tabular summary of the data.
Displays a drop-down list of the following three types of Pareto charts:
Transitions Pareto displays the highest number of transitioning alarms and events as a percentage.
Transitions Frequency displays the highest number of transitioning alarms and events.
Priority displays alarms and events grouped by priority, the highest transition frequency.

➢ To display a tabular summary of the data
♦ Click the button and from the Tree View, select Device Summary to display a table for all components and alarm
types.
Note The default when Device Summary is selected is to display all of the data from the result set.

➢ To display a Transitions Frequency chart of the data
♦ Click the button.

➢ To display a Priority chart of the data
♦ Click the button.

3.6 How to Analyze Historical Alarm Data Using the
WorkstationST* Alarm Viewer - Offline Mode
Historical alarm data is analyzed offline when the data has been retrieved from a control system and placed into a directory on
your computer. All of the information required is contained in the files, so the alarm data can then be analyzed using the
WorkstationST Alarm Viewer. It is not dependant on the control system that generated the files.
3.6.1 Configuring the Alarm Viewer

➢ To configure the Alarm Viewer: From the Start menu, select All Programs, GE ControlST*, WorkstationST
Alarm Viewer, and WorkstationST Alarm Viewer. The WorkstationST Alarm Viewer displays.
From the Options


3.6.2 Displaying Alarm Data - Unfiltered
➢ To display unfiltered historical alarm data

• Click the Apply Filter button.
Or
Note The Alarm Viewer always uses the filter displayed in the available filters drop down window when processing alarm
data.


The unfiltered request always returns the most recent set of alarm data (includes Process Alarms, Events, SOEs Holds and
Diagnostics) found up to the record limit (50,000 in this case). This data is called the result set. The data can be processed in
the following ways:
• Print the data by right-clicking over the data and selecting Print Alarms from the shortcut menu, or by selecting Print
Alarm Data from the File menu.
• Export the data to a CSV file from by selecting Export Alarm Data from the File menu.
• Copy and paste the date into other applications.
• Display the data with the WorkstationST Alarm Viewer by selecting:
Displays the raw detail data (default display).
Displays a tabular summary of the data.
Displays a Pareto chart of the data. Select the type of chart from the drop-down list associated with this button.
Transitions Pareto displays the highest number of transitioning alarms and events as a percentage.
Transitions Frequency displays the highest number of transitioning alarms and events.
Priority displays alarms and events grouped by priority, the highest transition frequency.

➢ To display a tabular summary of the data
• Click the button and from the Tree View , select Device Summary to display a table for all components and alarm
types.
Note The default when Device Summary is selected is to display all of the data from the result set.

➢ To display a Transitions Frequency Pareto chart of the data
• Click the button.

3.7 How to Filter Live and Historical Alarms Using the
WorkstationST Alarm Viewer
Warning
Filtering controls what alarm and event information displays in the WorkstationST* Alarm Viewer. The Alarm Viewer can
open, edit, apply and save alarm filter collections. A filter collection contains one or more alarm filters that controls the alarm
information displayed. This document explains how to manage and use filters when displaying both live and historical alarm
information. Refer to the following documents for further information:

• The section, How to Configure the Alarm Capability in the ToolboxST Application in this manual
• The section, How to Configure the Alarm Server in a WorkstationST Computer in this manual
• The section, How to Analyze Historical Alarm Data Using the WorkstationST Alarm Viewer - Online Mode in this manual
This document describes the following procedures:
• Configuring the WorkstationST Alarm Viewer

• Displaying Live Alarm Data - Filtered
• Displaying Historical Alarm Data - Filtered
• Creating, Saving, and Opening Additional Filters

In this example, a portion of the actual system is displayed. The diagram shows the H1 controller sending live alarms and
events on the UDH network. The Alarm Server running on Ews1, was configured to consume alarms and events from H1 and
has the Historical Alarms option enabled. The Alarm Server writes the alarms and events to the Historical Alarm archive
directory. The Alarm Server also formats the live alarm/event data and sends the data to all of the clients connected. The
WorkstationST Alarm Viewer then displays live alarm data or historical data as required. Refer to the section, How to
Configure the Alarm Server in a WorkstationST Computer in this manual for additional information.

3.7.2 WorkstationST Status Monitor
The WorkstationST Status Monitor provides a means to check the status of the WorkstationST Features.
➢ To display the WorkstationST Status Monitor
From the Ews1 workstation, in

the lower right corner of the
taskbar, double -click the
WorkstationST icon to
display the WorkstationST
Status Monitor: Feature
Status dialog box .
Or
♦ From the Ews1 Start menu, select All Programs, GE ControlST*, WorkstationST, and WorkstationST Status
Monitor. The WorkstationST Status of Features dialog box displays.

3.7.3 Configuring the WorkstationST Alarm Viewer
➢ To configure the WorkstationST Alarm Viewer

From the View menu , select
Connect, Show Live Alarms ,
and Show Historical Alarms .

From the Options


From the Tree View , select Alarm Viewer Settings , expand Local Settings,
select Alarm Configuration Root Path and set the path to the correct location.
The default is C:\Documents and Settings\All users\ Application Data\ GE

Energy\WorkstationST AlarmViewerConfiguration.
Select Use Local Workstation Alarm Configuration

and set to True to use the host workstation configuration.
Click OK to display the Alarm Viewer screen.

➢ To create a new filter collection
➢ To create a filter that displays process alarms from the controller

Tip � Place the cursor over the name of the filter to display an equation that represents the current definition of the filter.

3.7.4 Displaying Live Alarm Data - Filtered
➢ To display live alarm data using the Alarm filter

Tip � The red icon(s) beside the column name(s) indicates that a filter has been applied and that data in these columns
is being used by the filter to control the display.
Tip � Place the cursor over the red icon next to a column name and the filter criteria for that column is displayed in a
tooltip. The tooltip for the Device column in this example is .
Tip � Click on the red icon next to a column name and a dialog box displays that allows the editing of the filter criteria for
that column. In this example clicking on the Device icon displays the filter editor for the device selection. Change any of
the choices, the filter is updated and the display automatically updates to display the new filtered content.

3.7.5 Displaying Historical Alarm Data - Filtered
➢ To display historical alarm data using the Alarm filter

Note The filtered request always returns the most recent set of alarm data based on the filter selected.
Tip � To eliminate the 50,000 record prompt, go to the Alarm filter definition and set the Maximum Rows To Return to a
number greater than 0. This restricts the returned data to the designated number of rows.
The data can be analyzed using the summary or charting display options. Refer to the section, How to Analyze Historical
Alarm Data Using the WorkstationST Alarm Viewer – Online Mode in this manual for further information.
3.7.6 Creating, Saving, and Opening Additional Filters

➢ To create additional filters

After custom filters are defined in a collection, the collection can be saved for reuse.
➢ To save a filter collection
Tip � Name the collection DefaultFilters.xml to make the filters available as part of new collections.
Note This collection file can then be copied to the default alarm configuration root path on other workstations for use.

➢ To open a save filter collection

3.8 How to Set Up Alarm and Diagnostics Help for use in
the WorkstationST* Alarm Viewer
Warning
This document describes the steps necessary to set up process and diagnostics alarm help in a GE ControlST system for
display in the WorkstationST Alarm Viewer. Refer to the following documents for further information:

• The section, How to Filter Live and Historical Alarms Using the WorkstationST Alarm Viewer in this manual

A master workstation must be defined prior to enabling alarm help for a ToolboxST system. The master workstation can be
any workstation in the system that has the WorkstationST package installed and configured. The master workstation stores
file-based information used for control system operations. The alarm help information is displayed in the alarm viewer.
The EGD Configuration Server must be enabled and operational. For the purposes of this document, the system is identified
as System_Test and EWS1 is used as the master workstation and the EGD Configuration Server.
3.8.2 Selecting the Master Workstation

➢ To select the master workstation
1. From the Start menu, select All Programs, GE ControlST, ToolboxST, and ToolboxST. The System Editor
displays.

2. From the toolbar, click the Save button.

3.8.3 Configuring the Master Workstation
➢ To configure the master workstation
3. When all errors have been corrected, from the toolbar, click the Download button.
Note After the download is complete, you need to stop and restart the WorkstationST Service on the Master Workstation so
the WorkstationST Service can publish all of the diagnostic alarm help to the appropriate diagnostic help subdirectory. This is
normally only required once in the system when the master workstation is first configured, or if the master workstation is
changed in the system.

➢ To stop the WorkstationST Service
➢ To start the WorkstationST Service

3.8.4 Displaying the Master Directory Contents
➢ To display the master directory contents
The file structure (G1\L86DFLO_A.en.txt) displayed above contains the following:
• G1 is the component name

• L86D FLO_A is the variable name
• en indicates the content is in English and will display if the Alarm Viewer is configured to display English alarm help
The Alarm Viewer uses this format to display process alarm help. Refer to the WorkstationST Alarm Viewer Instruction Guide
(GEI-100620) for additional information on alarm help.
Note The Diagnostics help directory contents are created automatically when the WorkstationST Server is started
Note The ProcessAlarm help directory is user defined and must be manually populated with the process alarm help for the
system in use.

3.8.5 Configuring the Alarm Viewer
➢ To configure the Alarm Viewer
From the Options

From the View menu , select

Connect, Show Live Alarms ,
and Show Historical Alarms .


3.8.6 Displaying Alarm Help
➢ To display Diagnostics Alarm help
Tip � To change the language, select the desired language from the menu bar. The Alarm Viewer displays the help in the
selected language.

➢ To display Process Alarm help

3.9 How to Configure OPC® AE Capability
Warning
The WorkstationST* application includes an OPC AE server that provides an interface to alarm and event data. Third-party
OPC AE clients can connect to this server to obtain live alarm and event notifications. The OPC AE server implementation is
compliant with the OPC AE 1.1 specification. The WorkstationST Alarm Server also provides internal OPC AE client
configuration capability that allows external alarm and event data to be received from external OPC AE servers. The OPC AE
server is a feature of the WorkstationST component, the OPC AE client is a capability of the Alarm Server feature. Both are
configured and monitored through the WorkstationST Component Editor.
WorkstationST External OPC AE Server Configuration
WorkstationST GeCssOpcAe Server Usage

This document contains the following procedures:
• To configure the OPC AE Server

• To add an external OPC AE server
• To add or delete alarms from an external OPC AE server
• To display live alarms in the Alarm Viewer
• To confirm DCOM access permission
• To set launch and activation permission
3.9.1 Documents

• WorkstationST OPC DA Server (GEI-100621)
• WorkstationST OPC AE Server (GEI-100624)
• The section, How to Configure Alarm Capability in the ToolboxST Application in this manual
3.9.2 Configure the OPC AE Server
Note The DCOM configuration must be completed for each server connection made. Refer to the section Configuring
DCOM.
➢ To configure the OPC AE Server

1. From the Start menu, select All Programs, GE ControlST, ToolboxST, and ToolboxST.
2. If the correct .tcw file does not display, from the File menu, click Open System, navigate to and select the correct .tcw
file, and click Open.
3. From the Component Editor Tree View, double-click the WorkstationST component.

Tree View , select
Features.
From the Summary

View , select the OPC AE
Server Feature and set
Enabled to True.
Note The Alarm Server feature must also be enabled.

From the General tab Tree View ,
select Consumed Devices .
From the Summary View , select a device (TMRM6E)

that the OPC AE server will receive Alarm / Events from
and set the Referenced column to Yes.
3.9.3 Configure OPC AE Clients to External Servers

The alarm server can be configured to receive alarm and event data from external OPC AE servers. The External OPC AE
Servers item displays in the WorkstationST Component Editor Alarm tab
Note The DCOM configuration must be completed for each server connection made. Refer to the section Configuring
DCOM.

➢ To add an external OPC AE server: From the Alarms tab Tree View, right-click the External OPC AE Servers
item and click Add Server Connection.
For a single connection to the OPC

AE Server, enter the Host name.
Select OPC AE Servers and

select the server name from the Workstation1
drop-down list .
Workstation1.SoftingOPCToolboxDemo_ServerAE
Click Refresh if the host name
has been changed .
Click OK .
Note If the local GeCssOPCAEServer is selected, duplicate alarm and event information displays in the Alarm Viewer.
If redundant operation is required, select

the Redundant Connection check box.
Enter the Host name and Secondary

Host name that will host the external OPC
AE Servers.
Workstation1
Select OPC AE Servers and select the
server name from the drop-down list. Workstation2
Workstation1.SoftingOPCToolboxDemo_ServerAE
Select a host and click Refresh to update
the list of servers available on that host.
Click OK .
Note The OPC AE server must be installed and configured identically on both hosts for redundancy operation to work
correctly. If the Host connection fails, the Secondary Host connection is used to provide alarm and event data from the server.
When the Host connection is restored, processing of alarm and event data is returned to the Host computer.
The server displays as an item in the Alarm tab Tree View and when selected, the alarm mapping screen displays. This
display is used to configure all alarms received from the external OPC AE server and make them available in the alarm
system.
➢ To add or delete alarms from an external OPC AE server: From the Alarm tab Tree View, right-click the OPC
AE server and select an option from the drop-down menu.

Right-click Menu Options
Menu Option Function

Add Variables from Client Connects to and allows browsing the external OPC AE server. All published alarms
Connection and their respective conditions display in the browser. Select all alarms to be
configured and click OK. The alarms will be added to the mapping configuration
screen.
The server must be configured and running on the host before alarms will be displayed
in the browser.
Not all vendors implement browsing in their server.
Add Variable Adds a variable to be manually added to the grid for configuration.
Delete Selected Variable Deletes the selected variable from the data grid.
Import Variables Imports the variable configuration from a correctly formatted csv file.
Export Variables Exports the current variable configuration to a csv file.
Delete Server Connection Deletes the selected server and all configured alarms.
3.9.3.1 Alarm Configuration

Alarm configuration requires obtaining all of the alarm conditions for every alarm to be consumed, and for each condition,
configure each of the ToolboxST alarm properties as necessary. The following example uses the Softing.OPCToolboxDemo_
ServerAE as the source external OPC AE server in a redundant system.
Example:
After selecting Add Variables from Client Connection, the following dialog box displays with the alarms from the Softing™
server.
Under Server Selection , select which host in the redundant

pair to use to connect to the server to browse.
The alarm details include the Variable Name and Condition/

Sub-condition that each alarm implements. The red icon
represents the conditions that must be included in the
configuration for proper alarm display.
Select the variables to add and click OK .
The Tree View displays the alarms in a hierarchical

format.
Select an item to display the alarm conditions for each

alarm that may be produced by the OPC AE server.

Note For redundant systems, both hosts must be configured exactly the same.
From the Alarm tab Tree View , select the

Softing. OPCToolboxDemo_ServerAE
item to display the variables added from the
Softing server .
Configure the alarms as required. The

following table provides configuration
information on the columns.
Column Definitions
Column Name Definition
Active Severity Offset The value to be added to the OPC AE received severity when the alarm is active to normalize the
values between servers. Assign 0 if the actual value is to be used.
Alarm Class The alarm class used when displaying the alarm on the WorkstationST Alarm Viewer. This defines
the color and priority of the alarm.
Alarm/Event State The alarm state to be displayed when this condition is received.
Alarm/Event Type† The alarm type assigned to this alarm when received.
Alarm Shelving† Enables shelving of the alarm. This should be the same for the alarm and all conditions defined.
Alarm Shelving Max The maximum time in minutes that the alarm can be shelved.
Duration†
Auto Reset† If true, will automatically acknowledge and reset the alarm when the alarm transitions to the normal
state. This should be the same for the alarm and all conditions defined. This will clear the alarm
from the alarm display when the alarm transitions to normal.
Condition / Sub The OPC AE condition that the alarm may transition to.
Condition Name
Normal Severity The value to be added to the OPC AE received severity when the alarm is inactive to normalize the
Offset values between servers. Assign 0 if the actual value is to be used.
Plant Area† The plant area associated with this alarm. Plant Areas are defined in the ToolboxST System
Component.
Variable Alias The alternate name assigned to this alarm for display. The name must be unique in the control
system.
Variable Name The fully qualified name of the variable from the OPC AE Server.
† All of these properties must be configured the same for all conditions and sub conditions of a variable. If they do not match,
a build error will be generated.
Note If the alarm states are not mapped, the client cannot process alarms or events. Additionally, the Alarm Class, Plant
Area, and OPC Severity (normal and active) are also defined. Refer to the section, How to Configure Alarm Capability in the
ToolboxST Application, the section Alarm State Definitions in this manual for additional information.

Note The Active Severity Offset and Normal Severity Offset columns represent values that are added to or subtracted from
the actual value received. This normalizes values received from other OPC AE servers to the severity assigned to control
system variables.

➢ To display live alarms in the Alarm Viewer
1. From the Start menu, select All Programs, GE ControlST, WorkstationST Alarm Viewer, and WorkstationST
Alarm Viewer.
2. From the View menu, select Local Mode and Show Live Alarms. Live alarms from TMRM6E and
GeCssOpcAEServer display..

3.9.4 Configuring DCOM
To connect to an external OPC AE server, the client must know the server name. Most clients allow a user to browse for the
server's name. The WorkstationST OPC AE server name is GeCssOpcAEServer. When connecting from an interactive client
(a client running on the user's desktop), the interactive user must be included in the computer's default DCOM access
permission. DCOM does not require configuration for a local OPC AE client.
➢ To confirm DCOM access permission
Enter dcomcnfg and press Enter.
From the Tree View , right-click My

Computer and select Properties.

From the COM Security
tab, under Access
Permissions , click Edit
Default .
Check Group or user

names for ANONYMOUS
LOGON and INTERACTIVE .
If either does not display, click
Add and enter the name.
Verify the Allow check boxes

for both Local Access and
Remote Access are
selected for ANONYMOUS
LOGON and INTERACTIVE .
Click OK .

tab, click Edit Limits .
Select INTERACTIVE
and verify the Allow
check boxes for both
Local Access and
Remote Access are
selected.
Repeat this step for

ANONYMOUS
LOGON .
Click OK .

➢ To set launch and activation permission

tab, under Launch and
Activation Permissions ,
click Edit Limits .
Verify the Allow check

boxes for all Permissions
are selected for each
Group or user name.
Click OK .

tab, under Launch and
Activation Permissions ,
click Edit Default .
Verify the Allow check

boxes for all
Permissions are
selected for each Group
or user name.
Click OK .

Note Restart your computer.
Interactive test clients can now connect to the OPC DA server. The ToolboxST application includes an interactive OPC DA
test client, accessed from the WorkstationST Component Editor View menu.
3.9.5 DCOM Considerations

OPC is based on Microsoft® DCOM. When the OPC DA client resides on the same computer as the OPC DA server, the
client must have default DCOM access. When the client runs as a service on the same computer as the WorkstationST
application, no DCOM configuration is needed to allow the client to talk to the OPC DA server. When the client is running as
an interactive process, INTERACTIVE should be configured with default access for the computer’s DCOM default access
setting. Refer to the WorkstationST OPC DA Server Instruction Guide (GEI-100621) for DCOM configuration information.
Tip � The , WorkstationST OPC DA Server Instruction Guide (GEI-100621), the section Windows Workgroups
Exampleprovides information for when the OPC DA client resides on a remote computer.
3.9.6 Firewall Considerations

Firewall products such as Norton™ or other software firewalls, can have adverse effects on DCOM client/server
communications. The WorkstationST application configures the Windows firewall to the DCOM TCP port 135, and the OPC
DA server application. Other ports are opened for other GE protocols. The Windows firewall exceptions opened by the
WorkstationST application can be viewed using the Windows firewall setup dialog box from the computer’s Control Panel.

3.10 How To Export Alarm Data for Rationalization
Alarm rationalization produces the detail design necessary for the management of an alarm lifecycle. During this process,
alarm definitions are systematically compared to criteria (conditions) set forth in the alarm philosophy document for the plant.
If an alarm meets this criteria, the alarm set point, consequence, and operator action are documented, and the alarm is
prioritized and classified according to the philosophy. The following figure displays the alarm management lifecycle as
outlined in the ISA 18.2 standard.
From the ControlST software suite, the ToolboxST application provides a platform to export the process alarms defined in the
supported devices to a .csv format accepted by the third-party Exida® SILAlarm rationalization tool.
Note The ToolboxST application provides neither alarm rationalization nor options to import the alarm rationalization
results back into the configuration. The rationalization results must be configured manually.

Alarms from the following ToolboxST components can be exported for rationalization:
• Mark VIe control

• Mark VIeS control
• EX2100e excitation control
• LS2100e static starter control
➢ To export alarms from a Mark VIe component

1. From the ToolboxST application, open a .tcw file.
2. From the System Editor, double-click a Mark VIe component.
From the View

menu, select
Export Alarms for
Rationalization.

From the drop-down lists, select the
rationalization application and the
measurement system to be used.
To return to default attributes and aliases in the

rationalization application, click Restore to Defaults,
then click OK when the warning message displays.
Note Refer to the SILAlarm Alarm Management/Advanced Alarm Rationalization Tool User Guide for detailed instructions
to perform rationalization.

4 Human-machine Interface
4.1 How to Enable Adobe® PDF Full Text Search for
ControlST* Documentation
ControlST Software Suite V04.07 and later includes the latest Adobe® Reader® to provide full text searches. Adobe Reader
XI and the Windows® indexing service perform fast, accurate searches from within specified folders containing multiple .pdf
files.
Perform the following procedures provided in this document to enable text search:
1. Install and Enable Windows Search Service on Windows Server 2012 (applicable only to Windows Server 2012 users)
2. Install Adobe Reader 11.0 or Later (perform one time only)
3. Specify the ControlST Installation Directory for Search Indexing
4. Rebuild the Windows 7 / Windows Server 2012 Search Index
5. Perform a Search
Note If you have already installed the ControlST Software Suite, rebuild the Windows 7 / Windows Server 2012 index. (PDF
Filter 64Setup must be installed first.)
4.1.1 Install and Enable Windows Search Service on Windows Server 2012
Beginning with ControlST V06.00, Windows server 2012 users need to install the
Windows Search Service before installing Adobe Reader.
This procedure only needs performed by Windows Server 2012 users. If you do not
use Windows 2012, skip this procedure and continue to the procedure to install Adobe
Attention Reader 11.0 or later.
➢ To install Windows Search Service on Windows Server 2012 and enable Indexing options
1. Install the Windows Search Service feature.
From the Server

Management Interface,
select Manage, then select
Add Roles and Features.
Human-machine Interface GEH-6808N Instruction Guide 241

Follow the Add Roles and
Features Wizard screen
prompts. From the list of
features to install, select
Windows Search Service.
Select the server on which
to install the Windows
Search Service and click
Install.
The Add Roles and Features Wizard will notify you when the installation is complete.
Installation Complete

4.1.2 Install Adobe Reader 11.0 or Later
➢ To install Adobe Reader
1. From the ControlST DVD, navigate to the AdobeReader folder.
2. Run the Adobe Reader installation .exe file.
3. For a 64-bit operating system, also run the PDFFilter 64Setup.msi file.
Example AdobeReader Folder Structure
4.1.3 Specify ControlST Installation Directory

➢ To specify the ControlST installation directory for search indexing
Note You must restart the computer after performing this procedure.
1. From the Start menu, select Control Panel.

2. Modify your computer’s Indexing options.
In the Search field, enter Search to filter the Control Panel items.
Select Indexing Optionsto

display the Indexing Options
dialog box.

Click Modify to display the
Indexed Locations dialog box.

3. Add the folders GE Energy and GE Control System Solutions to your Index locations.
Navigate to the folder in which the ControlST

Software Suite is installed, GE Energy.
The default locations for this folder are:
For 32-bit machines:
\\C:Windows7\Program Files\GE Energy
For 64-bit machines:
\\C:Windows7\Program Files (x86)\GE Energy
The folder GE Control System Solutions contains

Legacy tools documentation.
Select both folders, GE Energy and GE Control

System Solutions, and click OK to index these
locations.
Note Selecting GE Energy selects all applications you have installed from the ControlST release.
4. Restart your computer.

4.1.4 Rebuild Windows 7 / Windows Server 2012 Index
➢ To rebuild the Windows 7 / Windows Server 2012 index
1. From the Start menu, select Control Panel.
2. From the previous procedure, perform Step 2 to display the Indexing Options dialog box.
3. From the Indexing Options dialog box, click Advanced. If prompted by UAC, click Yes. The Advanced Options
Click
Rebuild
4. When the following message displays, click OK. The rebuild can take several hours.
5. Click Close. When the rebuild is complete, Index complete displays.

Search Documentation
➢ To perform a search: from the Start menu, enter a key word, such as Mark VIe control to display the search results of
all .pdf files that contain that term.

4.2 How to Display a Variable on an Human-machine
Interface Screen
assume that the Human-machine Interface (HMI) nor the operator will close a safety
Warning
Variables can be displayed on a CIMPLICITY® HMI screen in the following ways:
• Use the drag-and-drop feature from the ToolboxST* application

• From CimEdit, use the Drag Variables To Screen option.
When using the drag-and-drop feature from a variable grid or the Select a Variable dialog box in the ToolboxST
application, a simple text object is created in the CimEdit window with the text expression set to the value of the variable.
You can also drag a variable to a custom, user-defined, CIMPLICITY-linked screen object. If the file HMIBlockMappings.
xml exists in the ToolboxST application’s HMIScreens folder, the entry for $Variable defines the custom screen object on
the screen when you drag a variable to a CimEdit window. The value of the variable is assigned to the screen object’s
varname variable.
Example:
HMIBlockMappings.xml file:
<?xml version="1.0" encoding="utf-8" ?>
<root>
<Blocks>
<Block Name="$Variable" HmiScreenObj="variableDisplay" HMILinkSource="C:

\GEWorkstationST\HMIFiles\Library\ScreensObjects\General\
tp_WorkstationST_objects.cim" />
</Blocks>
</root>

In this example, the variableDisplay screen object is a group of three text objects containing the three expressions:
{varname}.Point_ID, {varname}, {varname}.Description.
The WorkstationST application’s integration with CIMPLICITY Advanced Viewer was enhanced by adding a Drag
Variables To Screen shortcut menu item to CimEdit. This allows you to easily browse for ToolboxST variables and add
them to the CimEdit window without opening the ToolboxST application. This feature is only available with CIMPLICITY
V7.5 Advanced Viewer. To enable this feature, the WorkstationST* HMI feature must be enabled, configured for HMI
Graphics without a project, and downloaded to the computer.

➢ To drag a variable to the CimEdit window: from CimEdit, right-click to display the shortcut menu.

Note Variables can be configured with an alias property (alias name) in the ToolboxST application. The HMI screens can
then use the alias name to refer to the variable.

The default drag-and-drop operation creates a simple text object in the CimEdit window with the text expression set to the
value of the variable. This default text object can be changed to a user-defined custom text object. The above example
displays a custom user-defined $Variable object.

➢ To verify object properties
1. From CimEdit, right-click on the object to display the shortcut menu.
2. Select Properties. The Properties – Object dialog box displays.

4.3 How to Configure a Second Language for ControlST*
HMI Applications
Warning
This document provides information on configuring a second language in the ToolboxST* and CIMPLICITY*applications,
and beginning with ControlST V04.03, for configuring the operating system language.
• Configure a primary and secondary language

• Enable the default language
• Enable the second language from CimView
• Create a new language mapper file
• Add language keys to the translation file
• Create primary and second language translations
• Include custom context menu items
• Use the global script InitializeCIMPLICITY
4.3.1 Documents
• ToolboxST User Guide for Mark* Controls Platform (GEH-6700)

• WorkstationST* Advanced Alarm Viewer Integration Instruction Guide (GEI-100697)
• Resource Translation Manager (RTM) User Guide (GEI-100793)

4.3.2 Configure Second Language Properties in the ToolboxST Application
The primary and second languages are configured in the ToolboxST System Editor. Configuring the names of the languages
allows HMI applications to provide translation support. CIMPLICITY CimView can be configured to use translation files,
which index translated text by language name.
➢ To configure a primary and second language
After the second language is entered, there are several locations within the ToolboxST configuration where primary and
second language descriptions are set:
• Variable Description and Second Language Description

• Variable Enumeration Definition
• Alarm state associated with a variable
• Alarm definitions associated with a variable configured as an analog alarm
The following are provided as examples of where the second language displays in the ToolboxST application, not as an
instruction guide:
Each variable in the ToolboxST system has a Description and a Second Language Description.

Variable Enumeration Definitions accessed from the variable’s enumerations property, or from the variable’s Initial Value
property editor, or from a format specification’s enumerations property.
Alarm states that are associated with a variable can have a second language description.
Note The Second Alarm State (second language names) must be entered and saved at this point for them to display in all
other locations when code is instanced.

Analog alarm definitions associated with a variable can have a second language defined for the alarm state and the alarm
message.
locations when code is instanced.
The Diagnostic Translations option allows you to display alarm diagnostic text in a second language.
Note Refer to the ToolboxST User Guide for Mark* Controls Platform (GEH-6700), the section Diagnostic Translations for

Each WorkstationST component can enable the second language to be used by HMI applications at startup.
Note If the WorkstationST component Use Second Language option is set to True, scripting must be invoked to initially set
the second language upon the first OnScreenOpen event. Refer to the procedure To use the global script
InitializeCIMPLICITY.
➢ To enable the default language

1. From the ToolboxST System Editor Tree View, double-click the WorkstationST component.
Or (when using ControlST V03.05 or later)

2. From the taskbar notification area, right-click the WorkstationST or ControlST icon to display the shortcut menu.

Note When the Use Second Language option is selected from Regional Settings, it becomes the permanent default setting,
regardless of what is configured in the General tab in the ToolboxST application.
4.3.3 Configure Second Language Properties for use with CIMPLICITY

CimView
The second language description can be set in the CIMPLICITY application. The following are provided as examples of
where the second language displays in the CIMPLICITY application, not as an instruction guide:
Key items configured with a language in the CIMPLICITY Language Mapper file display in the second language on the
CimView screen.
Note If the second language option is selected and there is no second language description defined for the variable, the
primary language description is displayed on the HMI screen, the CIMPLICITY Alarm Viewer, or the WorkstationST Alarm
Viewer.
The second language can be enabled from a CIMPLICITY CimView screen.
➢ To enable the second language from CimView: right-click on a CIMPLICITY CimView screen and select
Regional Settings and Use Second Language from the shortcut menu.
If the Use Second Language option is selected, the Enumeration text and variable description attributes display the configured
second language for the associated enumeration or description. In addition to displaying descriptions and enumeration text in
a second language, the CIMPLICITY CimView feature can be configured to use translation files. The files contain one or
more language translations of text. Using this CIMPLICITY feature allows static text on screens to be translated. This
requires creation of a new language mapper file and the addition of language keys to the translation file.
➢ To create a new language mapper file: from the CIMPLICITY screens folder, right-click inside the folder, select
New and CIMPLICITY Language Mapper UI from the shortcut menu, enter a Name (such as tp_translate.chm)
for the file and click OK.
Language keys must be added to the translation file for each language.
Note The names of the languages must match the names configured in the ToolboxST system for the primary and second
languages. (An earlier example used English and Norwegian.)

➢ To add language keys to the translation file
1. Double-click the translation file (tp_translate.clm) created earlier to open the file in the CIMPLICITY Language
Mapper.
2. From the Language Editor dialog box, click Add.
After the language keys are added, primary and second language translations must be created in the file.

➢ To create primary and second language translations: from a CimView screen, right-click on the screen.
The language mapper file created contains all the text strings and standard CIMPLICITY context menu items in the file for
translation. However, the custom context menu items configured by the WorkstationST application must be manually added to
the language mapper file to enable translations for those items.
Note Key strings entered in the language mapper file are case sensitive and must be an exact match (including special
characters) for translations to occur in CimView.

➢ To include the custom context menu items: follow the previous procedures to edit the language mapper file and
add the following keys and translation for each defined language:
• Regional Settings
• Use Second Language
• Go To Definition In &Logic
• Add to &Trend
• Go To Display &Screen
• Display Variable Attributes
• &Alarm Status History
• &Print Screen
• Ten Minute Filter
• One Hour Filter
• One Day Filter
• Enable Non-Translated Content
• Selective Active Measurement System (Native (Raw))
• Selective Active Measurement System (US)
• Selective Active Measurement System (METRIC)**
** Enter a string for each measurement system defined in the ToolboxST application.
The OnScreenOpen event can be used to run the installed WorkstationST global script InitializeCIMPLICITY. When the Use
Second Language option is set to True, the screen translation matches the configured second language when the following
procedure is completed.
➢ To use the global script InitializeCIMPLICITY: from the Screen Template screen (common to all screens),
right-click on the screen.

4.3.4 Configure the Operating System Language
Beginning with ControlST V04.03, the multi-language capability for operator HMI displays has been enhanced to include
translation of the WorkstationST Alarm Viewer, ToolboxST Trender, and WorkstationST Status Monitor applications when
accessed from an HMI. This functionality is enabled using a specific configuration on each HMI to automatically display the
translated applications based on the operating system language.
Note An optional Microsoft® language pack must be installed before a non-English display language can be selected in the
operating system. Refer to the Resource Translation Manager (RTM) User Guide (GEI-100793) for additional information.
Operating system display language — The Alarm Viewer, Trender, and Status Monitor read the current language setting
from the operating system at startup. If the operating system language abbreviation matches the application language folder
containing the resource.dll files, then the application opens with translated text displayed.
Translated resource .dll files — To enable translations for the applications, a set of resource.dll files must be created for
each alternate language to be used for each application. The Resource Translation Manager creates the initial list of text
strings for translation. After the translated strings are added to the file, the Resource Translation Manager imports the
translations, and creates a set of resource.dll files in a language folder for each application. The language folder must then be
copied to the associated application folder to make the translations available for use by that application.
Note Refer to the Resource Translation Manager (RTM) User Guide (GEI-100793) for additional information.
Resource Translation Manager for Trender to Display in French

Alarm Viewer Configured to Display in Spanish

4.4 How to Troubleshoot a CIMPLICITY* Project
Warning
Naming and configuration errors can cause errors and other problems when starting a project in the CIMPLICITY application.
These problems are most often associated with the CIMPLICITY or ToolboxST application.
CIMPLICITY Errors
There are a number of locations where naming or configuration errors could have been made that cause errors when creating
projects. Look at the CIMPLICITY status log to start.
Note The site and cimproj folders are located on the E: drive by convention. The actual file names and drives may vary by
site.
➢ To review the CIMPLICITY status log

Or,
1. From the Site folder, select cimproj, log, and double-click the CIMPLICITY Log folder to display the CIMPLICITY
logs. Review the CIMPLICITY logs for errors.
2. Double-click the cor_recstat.clg file to display the status log. Review the status log for errors.
Note Each CIMPLICITY process creates an error file (.err) and an output file (.out) when the project is started. Two copies
(_1.out, _2.out, _1.err, _2.err) are maintained in the log folder each time the project is stopped.
Another potential source of errors is the global script file location.
➢ To verify that the global script location is defined correctly
Note By clearing the Enable project broadcast checkbox, the amount of traffic sent over the network is reduced. The Enable
project broadcast check box must be selected if other computers are configured as viewers in the system in order for them to
connect to this project.

Note SNMP Devcom is only required for legacy network monitor configuration.
If for any reason some points are not imported, you might have to force re-import of CIMPLICITY project data.
➢ To force re-import of CIMPLICITY project data

1. From the Site folder, select cimproj, and double-click the project file (in this example HMISVR.gef). The
CIMPLICITY Workbench screen displays.
2. From the View menu, select Search to Activate Point. The Search dialog box displays.
3. Enter *Config* in the Point ID field.
4. Clear all other fields and click OK. Each device in the project will have two points:
• Device.config_version
• Device.config_version_alarms
5. Delete the two points associated with the device you want to re-import.
6. From the task bar, open the WorkstationST Status Monitor.
7. Right-click the HMI and select Start Subfeature. The Select Subfeatures to Start dialog box displays.
8. From the Select Subfeatures to Start dialog box, select Importer and click OK. The HMI Importer will run.
9. Check the WorkstationST Status Monitor, HMI feature for errors.

ToolboxST Errors
After the CIMPLICITY files have been checked for errors, there are several places within the ToolboxST application to
check. The first place is the CIMPLICITY project file.
➢ To verify that the CIMPLICITY project file path is defined correctly

4.5 How to Define a Measurement System for Use by
ControlST* HMI Applications
Warning
The ToolboxST* application and CIMPLICITY® CimView have a setting for a measurement system. The ToolboxST
application is used to configure the measurement system(s) used by the ControlST* HMI applications. After the configuration
is complete, measurement systems can be selected at individual HMIs. By default, CimView displays values in the native
units assigned to the variable.
4.5.1 Format Specifications
Format specifications control how variables are displayed by an HMI. Each variable in an application’s system can be
configured with a format specification. Format specifications are contained in a Format Specification Set. A Format
Specification Set can contain multiple format specifications, but each format specification in the set has a unique
measurement system assigned. Format Specification Sets establish a relationship between different measurement systems for
a particular type of data. For example, a Format Specification Set for temperature could contain two format specifications for
temperature: one for degrees Fahrenheit in the U.S. (English) measurement system and one for degrees Celsius in the
International System of Units (Metric) measurement system.
The Engineering minimum and maximum (Min and Max) values for both format specifications control the conversions that
take place when a measurement system is selected at an HMI. For example, if a temperature variable is assigned to the
Celsius format specification and the measurement system in use on the HMI is Metric, no conversion is performed on the
HMI displayed value. If the HMI’s measurement system is changed to English, the value of the variable is converted from
Celsius to Fahrenheit using a linear equation defined by the Engineering Min and Max of the Celsius and Fahrenheit format
specifications.
Note Within a Format Specification Set, all Engineering Min values must represent the same physical value in all
measurement systems and all Engineering Max values must represent the same physical value in all measurement systems.
For temperature, the Engineering Min value for Fahrenheit (32) and the Engineering Min value for Celsius (0) represent the
same temperature, the freezing point of water. The Engineering Max value for Fahrenheit (212) and the Engineering Max
value for Celsius (100) represent the same temperature, the boiling point of water. These are not limits on the range of the
measuring device or system; they are numbers of convenience (the freezing point and boiling point of water).
The ToolboxST System Information Editor allows editing of the format specifications. If access to a System Database (SDB)
is enabled, the contents of the System Information Editor can be stored in the SDB.

➢ To create a Format Specification Set
➢ To add format specifications to a Format Specification Set

The following properties are available in the Property Editor when a Format Specification Set is selected:
Engineering Max displays the maximum value of the range used for unit conversions.
Engineering Min displays the minimum value of the range used for unit conversions.
Enumerations allows the definition of acceptable alternate values for the Name, Value, Description, and Second Language
Description variables of a format specification. The enumerations are used unless overridden by enumerations defined locally
on the variable.
Precision displays the number of digits to display to the right of the decimal point (for example, a precision of two displays
the fraction 1/3 as .33).
Units display the text that identifies the format specification unit.
Format Spec Set displays the Format Specification Set that contains the selected format specification.
Measurement System displays the measurement system (for example, Metric or English) to which the unit belongs. (Refer
to the section, Measurement Systems).
Name displays a unique name for the format specification. If the system data is Put to an SDB (to be stored within an SDB),
a limit of 12 characters is enforced for the Name.

4.5.2 Measurement Systems
Each format specification is assigned a measurement system. Within a format specification set, which represents a particular
type of measurement (such as temperature), only one unit per measurement system can be created. (For example, you could
not add both Celsius and Kelvin within the Metric system as units of temperature.) You can select the two measurement
systems that are stored in the SDB in the System Information Editor.
➢ To select the measurement systems used by the SDB

Each WorkstationST* component can enable the default measurement system to be used by the HMI applications at startup.
➢ To enable the default measurement system

1. From the ToolboxST System Editor Tree View, double-click the WorkstationST component (such as EWS1) to
display the Component Editor.
Or (when using ControlST V03.05 or later)
2. Right-click the WorkstationST or ControlST icon in the taskbar notification area to display the shortcut
menu.

The measurement system can also be selected from a CIMPLICITY® CimView object.
➢ To select the measurement system from CimView

4.6 How to Link a ToolboxST* Block to an HMI Block
The ToolboxST application allows you to copy and paste, as well as drag and drop blocks. You can also create screen objects
on HMI screens created in Proficy HMI/SCADA CIMPLICITY* 7.5 and later (refer to the ToolboxST User Guide for Mark
Controls (GEH-6700), the section, Computer Recommendations for the table showing ControlST Windows* Compatibility). If
you drag a block from the ToolboxST Tree View onto the CimEdit screen editor, CimEdit uses data from the block’s attribute
list to create a screen graphic using a linked object.
Note A preconfigured .CIM file (such as tp_screen.cim) is required for the drag and drop smart object functionality to work.
The block’s attribute list must include HMILinkSource and HMILinkedObject. These specify the path to the link
source file and link source object needed to create the linked object. The path specified by the HMILinkSource must be
fully qualified, or must be relative to the screen being edited. CimEdit names the newly created link container based on the
block’s HMILinkContainer attribute, if present, or gives it a default name if the block’s HMILinkContainer attribute
is missing or empty.
CimEdit populates public variables of the linked object with the values from the block’s attributes. Each attribute is used to
populate the public variable of the same name, or is ignored if no public variable with that name exists. The exact value from
each attribute is used during this process, with the following exceptions:
• If an attribute’s values contain text in {braces}, that text is expanded based on the value of other block (or parent)
attributes. This expansion is identical to that done during block instancing.
• If there is no attribute named Caption, the ToolboxST application automatically creates one for CimEdit, and sets its
value to that of the Device attribute. By convention, the Device attribute contains the name of the field device, such as
the pump or motor, being controlled by the block.
• If there is no attribute named ctrlr, the ToolboxST application automatically creates one for CimEdit, and sets its value
to the name of the controller followed by a period. For example, if the block is being used by a controller named G1, the
ctrlr attribute is set to a value of “G1.” unless the block actually has a ctrlr attribute.
• The optional HMILinkBlockPinsToParameters block attribute enhances your ability to drag and drop, as well as
copy and paste objects. When this attribute is set to True, the ToolboxST application creates an attribute named after each
block pin with a connected global variable equal to the short name of the connected variable. If the
HMILinkBlockPinsToParameters block attribute is set to a value of FullNames, the full name of the attached
variable is used.
• It is possible to create multiple objects on the CimEdit screen editor when dragging a single block from the ToolboxST
application. This is done by using comma separated values (.csv) for the HMILinkedObject block attribute, which
splits that attribute value into multiple values. If this is done, the ToolboxST application also checks the
HMILinkSource, HMILinkContainer, Device, and Caption attributes for commas, and splits each of them if
appropriate.
Example:
A Software block is being dragged to CimEdit. The acv_horiz screen object found in tp_dcs_objects.cim is added to the target
CimEdit design surface when the 212FCV50219:PID_MA item is dragged to CimEdit. The parent task has a Device attribute
of value 212FCV50219.

➢ To link a ToolboxST block to an HMI block

4.7 How to Set Up the HMI Master Screens Copy
Functions
To maintain consistency a recommended directory structure has been developed for GE projects.
4.7.1 Setting Up the File Server
➢ To set up the file server

1. From the desktop double-click the My Computer icon.

Note <File Server> is the (PDH) name of the computer in the system containing the Master Folder (usually the engineering
workstation). Sharing must be enabled on the Master folder (with share name Master and correct permissions) before the
mapping shown above can be configured.
Note The M: drive should be used if possible to maintain consistency. If it is used for another purpose, select another drive
letter.
2. From the My Computer dialog box, double-click the M: drive icon to display the Master folder.
3. Right-click inside the Master folder and from the shortcut menu select New, and Folder. Enter Screens as the name
for the folder.
4. Copy a complete set of screens for the project to the M:\Master\Screens folder.
5. Go to the ICS Server, locate and select the Product_Information\HMI directory.
6. Copy the Screen_Copy folder (which contains the Screen_Copy .cmd files) to the M:\Master folder.

4.8 How to Create CIMPLICITY* Screens
Warning
This document is based on using CIMPLICITY 7.5 and presents the basic steps used to create CIMPLICITY screens. Screens
typically display two types of objects:
Static objects are used to represent process flow on the diagrams.
Dynamic objects are used to indicate the status of equipment in the process flow.
CIMPLICITY Screen

There are several options available when creating CIMPLICITY screens.
CimEdit Tools - CimEdit provides tools to graphically represent the facility (plant). CimEdit provides the capability to
import OLE and ActiveX™ objects (such as Trends, Quality Charts, and Alarm Viewer) into CIMPLICITY screens. Drawing
tools are provided.
As objects are placed on the screen, a set of alignment tools displays. Objects can be aligned automatically with a
configurable grid, or aligned as groups using the object alignment tools which include the ability to space objects evenly as
well as align them in relation to each other. After objects are created, they can be resized, rotated, or moved.
Linked Objects - Linked objects provide single source capability by allowing you to edit a single, linked source object. The
CIMPLICITY HMI updates all links in the project to the linked source object’s configuration whenever the original is
changed.
A linked container is the shell of a linked object. A linked object's container can have its own scripts or procedures. You can
configure properties for the container, such as movement and animation that, in addition to the linked properties, will affect
the linked object's runtime behavior. The configuration does not impact on the linked source object.
Standard Objects Template (tp_dcs_objects.cim) - The DCS domain tp_dcs_objects.cim screen contains source
objects of various types such as pumps, indicators, bar charts, and valves which are all smart objects and provide additional
configuration options when they are placed on a screen. Each object is designed in accordance with project requirements.
These objects can be configured in various screens as linked objects.
To create several objects with identical features (such as a title bar), create one object as the source object for several linked
identically configured objects. For objects with the same internal functionality (such as pumps), create a template that can be
used as the source for a linked object. The template can use public variables whose values can be specific to each screen.
Navigation Template - The navigation template is contained in the tp_screen.cim screen. This template is used to create
project-specific navigation using pre-configured layout and button colors and is inserted as a linked object in all screens.
The navigation template works in conjunction with an Excel®-based automation tool. This tool is used to define:
• System navigation levels

• Screen grouping
• Screen titles
• Button captions
Each time the tool is run, it modifies the navigation template in the tp_screen.cim screen depending upon the definition given
in the automation tool. As a linked object inserted in all screens, the screen navigation objects are modified in the entire
project.

4.8.1 Creating a Screen Template
A screen template provides a basis for screens that are created in the future.
➢ To create a screen template

1. From the computer desktop, double-click the My Computer icon, E: drive, and Site file.
2. Right-click inside the file to display the shortcut menu.
3. Select New and Folder. Enter the name as Screens. Click OK.
4. From the computer desktop, double-click the My Computer icon and the ICS Server network drive. Copy the tp_
dcs_objects.cim and tp_screen.cim files to the Screens folder.
5. From the Start menu, select Programs, Proficy HMI SCADA – CIMPLICITY 7.5, and CimEdit to display the
CimEdit1 - CimEdit screen.

6. From the File menu, select Save As and save the CimEdit1 screen as a template.
7. From the Screens folder, right-click on tp_screen.cim to display a shortcut menu. Select Edit to display the tp_
screen - CimEdit screen.

8. From the Screens folder, right-click on template.cim and select Edit to display the shortcut menu. Select Edit to
display the template - CimEdit screen.

9. From the toolbar, click the Save button.
10. From the File menu, select Close to close the template* - CimEdit screen.
The template - CimEdit screen is ready to use as a template.

4.8.2 Creating a User Screen
The toolbars and tools are available to create lines and objects as required. Use the Object Library to add static objects such as
tanks and heaters. Use the tp_dcs_objects.cim screen to add dynamic objects to the screens.
➢ To create a user screen
1. From the computer desktop, double-click the My Computer icon, E: drive, Site, and Screens.
2. Right-click template* - CimEdit and, from the shortcut menu Edit.
3. From the File menu, select Save As and enter a name for the screen (for example srv_water.cim).
4. Save the screen to the Screens folder.
5. Select and open the srv_water.cim screen.
Tip � Add all dynamic objects as linked objects (using Copy, Paste Special, and Paste Link procedure).
4.8.3 Configuring Objects/Smart Objects

In the tp_dcs_objects.cim file all objects are smart objects. Each smart object has numerous properties. All these properties
can be animated (such as scaling color animation procedures). For static objects, the properties that typically require
modifying are color, geometry, and width.
➢ To edit object properties

1. From the CIMPLICITY screen, right-click the object to display a shortcut menu.
2. Select Properties to display the Properties - Object dialog box.

In smart objects, certain properties are pre-animated. This helps in reducing object configuration time. The ICS smart objects
contain a configuration dialog to allow the user to customize the linked object after it is inserted into the screen, The smart
object dialog is displayed in CimEdit for any linked object by double clicking the object, or right clicking the object and
selecting Trigger Smart Object.
Note The Smart Object Configuration dialog box can display differently based upon the object selected.

4.9 How to Integrate CIMPLICITY* 6.1 HMI with the
Warning
This document provides information on working with the CIMPLICITY 6.1 Human-machine Interface (HMI) screens. It
includes procedures for configuring a CIMPLICITY HMI project, and setting up an HMI in the ToolboxST application, and
interfacing with the WorkstationST application.
4.9.1 Configuring the CIMPLICITY HMI

The CIMPLICITY project files are typically located on the E: drive. Individual sites may vary and the procedures must be
adjusted for the actual location.
➢ To configure the CIMPLICITY HMI

4.9.2 Configuring the ToolboxST Application
➢ To configure the ToolboxST application
1. From the Start menu, select Programs, GE ControlST*, ToolboxST, and ToolboxST. The ToolboxST application
displays.
2. From the File menu, select Open to display the Open dialog box.
3. Locate and select the <project name>.tcw file (for example SCEG.tcw). Click Open to display the SCEG –
ToolboxST window.
Note Normally, only one workstation in a system is configured to run the EGD Config Server.

4.9.3 Configuring the WorkstationST Application
➢ To configure the WorkstationST application

Importing Data
➢ To import data into the CIMPLICITY database
1. From the Windows® Taskbar Notification area, double-click the WorkstationST icon to display the
WorkstationST Status of Features dialog box.
2. Select the Importer box and click OK.

3. The HMI Status will indicate that HMI Importer is running while the project is being configured. The Import is complete
when the status line indicates OK and HMI Importer is Ready to Import. Last import completed at 5/7/2009
2:58:06 PM. The status will contain Error if import errors occurred.
➢ To verify the project has been updated

1. From the computer desktop, double-click the My Computer icon, E: drive, Site file, Cimproj file, and the <project
name>.gef file (for example CRM1SVR.gef), to display the CRM1SVR.gef – CIMPLICITY Workbench screen.
2. From the Tree View, expand Equipment and select Devices. Verify the devices are created and the signals are
populated.
3. From the Tree View, expand Security and select Resources. Verify the resources are created.
4. From the Tree View, expand Advanced and select Alarms. Verify the alarms are imported. Select Alarm Classes
and verify the alarm classes have been imported
5. From the Tree View, expand Advanced and double-click Measurement Units. Verify the format specifications from
the ToolboxST system information are imported.
To complete the CIMPLICITY HMI integration, copy the screens to the project screen folder (E:\site\cimproj\screens). The
WorkstationST HMI feature contains an option to enable automatic download of screen files.
Refer to the ToolboxST User Guide for Mark* Controls Platform (GEH-6700) for information on configuring this feature.
Refer to the WorkstationST HMI Configuration Instruction Guide(GEI-100629).
The CIMPLICITY HMI is integrated with the WorkstationST application. You can interact with the controller, through the
CIMPLICITY 6.1 HMI screens.

4.10 How to Change the IP Address for an Allied Telesis™
8516/8624 Network Switch
assume that the Human-machine Interface (HMI), nor the operator, will close a safety
Warning
Allied Telesis 8516 and 8624 Fast Ethernet switches support disk operating system (DOS) attack protection, are
cabinet-mountable, and offer full routing capabilities. If a switch needs to be configured or an IP address changed to match a
network, refer to the following procedures:
• Connecting to the 8516 or 8624 Network Switch

• Reconfiguring the 8516 Network Switch IP Address
• Reconfiguring the 8624 Network Switch IP Address
4.10.1 Prerequisites
When configuring the IP address for an 8516 or 8624 network switch, the following equipment is needed:
• Serial cable (supplied with the Allied Telesis switch)

• Computer with a serial (COM) port
• Switch console port
• Windows® operating system with HyperTerminal™

4.10.2 Connecting to the 8516 or 8624 Network Switch
➢ To connect to the 8516 or 8624 network switch using HyperTerminal
1. Connect the serial cable that was supplied with the Allied Telesis switch between the computer COM port and the switch
console port.
2. Navigate to the HyperTerminal.

➢ To reconfigure the IP address
• For the 8516 network switch, refer to the section, Reconfiguring the 8516 Network Switch IP Address.
• For the 8624 network switch, refer to the section, Reconfiguring the 8624 Network Switch IP Address.

4.10.3 Reconfiguring the 8516 Network Switch IP Address
➢ To reconfigure the 8516 network switch IP address
1. Make sure the serial cable (supplied with the Allied Telesis switch) is connected between the computer COM port and the
switch console port using HyperTerminal. Refer to the section, Connecting to the 8516 or 8624 Network Switch.
2. From the SW1 – HyperTerminal logon window, locate the logon prompt at the bottom of the window.

4.10.4 Reconfiguring the 8624 Network Switch IP Address
➢ To reconfigure the 8624 network switch IP address
1. Make sure the serial cable (supplied with the Allied Telesis switch) is connected between the computer COM port and the
switch console port using HyperTerminal. Refer to the section, Connecting to the 8516 or 8624 Network Switch.
2. From the SW1 – HyperTerminal logon window, locate the logon prompt at the bottom of the window.
Note Replace the xxx used in this example with the IP address that is needed.

Note YYYYY is the boot configuration file. For this example, the current configuration file is Current.cfg.
13. Log on to the network switch again using the username and password (refer to step 2).

14. Check the Bridge Priority.
16. Enter the logoff command to end the network switch session, completing the reconfiguration process.

4.11 How to Configure an Alias for ControlST* HMI
Applications
Warning
Specifying an alias provides you with the option to display a localized name for a variable on the HMI screens, and in the
ToolboxST Trender, Watch Window, and WorkstationST Alarm Viewer.
4.11.1 Creating Aliases

As an option, each variable in the ToolboxST application can have an Alias.
Aliases have the option to be prefixed with the component name. The component name, with prefix is then displayed and
accessed by other components. For example, and alias of localName for component G1 becomes G1.localName.
➢ To enable alias prefixing

1. Open the ToolboxST application.
2. From the Tree View, double-click a controller to display the Component Editor.

4.11.2 Exporting and Importing Aliases
Aliases can be exported and imported via the variable Alias Report.
➢ To export aliases

The report can be saved in either a .csv or .xml format. This file can then be edited and re-imported to populate the alias
values.
➢ To import aliases
♦ Locate and select the Variable Alias Report (either a .csv or .xml) to import and click Open.

4.11.3 Displaying Aliases
Aliases are displayed with the other variable properties in several applications. The following are examples:
Alarm Viewer
Watch Window
Trender

4.11.4 Using Aliases on HMI Screens
➢ To drag a variable to the CimEdit window
♦ From CimEdit, right-click the screen to display the shortcut menu.

➢ To place aliases in objects
1. From CimEdit, right-click an object to display the right-click menu.
2. Select Properties. The Properties – Group dialog box displays.

4.12 How to Install and Replace the Linksys™ SFE2000
Network Switch
The NetworkST 3.0 topology design uses the Linksys SFE2000 network switch in pairs and a stacked configuration. Switch
stacking allows the two switches to be connected together and operate as one switch with the port capacity of the combined
switches. The stacked switches are connected together through special stacking ports with one or more cables. Advantages of
switch stacking include:
• Built-in failover and recovery in case of a switch failover.

• An unconfigured switch can be used to replace a failed switch in the stack. It automatically uploads the running
configuration from the remaining switch in the stack.
Note The WorkstationST* Network Monitor checks connection status for devices, computers, and controllers connected to
the Linksys SFE2000 switches. The stacking software function operating on the Linksys SFE2000 can cause the Network
Monitor to display incorrect status, even when network communications are healthy. The installation and replacement
procedures in this document should be followed to ensure proper network operation and correct status indication by the
Network Monitor.
Linksys SFE 2000 Network Switch
4.12.1 Initial Startup

This procedure should be used during commissioning of the network. Use pre-configured switch pairs as ordered from GE
Energy. Switches are provided in matched pairs configured to work together in a stack. Switch pairs are numbered
sequentially as SW01, SW02, and SW03, SW04, and so on. Do not mix and match.
➢ To perform an initial startup of a stacked pair of switches

1. Connect the matched pair units to each other through the stacking ports using standard Ethernet cables. Do not connect
fiber-optic cables. Do not connect patch cables to the controllers, computers, or other connections external to the stack.
2. Turn on power to the lower (odd numbered) switch first. Then turn on power to the higher (even numbered) switch. After
a short interval the stack becomes operational, with one of the units selected as the Stack Master. The unit selected as
Stack Master is indicated by a lit green MST LED on its front panel. The Stack Master should be the lower (odd) switch
number.
3. Confirm the correct setup as described. Refer to the section, Switch Stack Identification for additional information.
4. Connect fiber-optic cables as shown on the network topology drawing.
5. Connect computers, printers, and other devices as shown on the network topology drawing. The switch stack is ready for
use.

Replace Stacked Pair of Switches
Use this procedure to replace a stacked pair of SFE2000 network switches with a new pair of SFE2000 network switches.
Replacement switches should be ordered as a stacked pair of pre-configured SFE2000 network switches from GE Energy.
Refer to the section, Replacement Parts Ordering for additional information.
➢ To replace a stacked pair of network switches

1. Follow steps 1-3 of the procedure To perform an initial startup of a stacked pair of switches.
2. Set the IP address of the stack to match that shown on the network topology drawing. Refer to the section, Change the
Switch Stack IP Address Using the Console for additional information
3. Replace labels on the switch with ones showing the correct IP address and switch numbers. Refer to the section, Switch
Stack Identification, the figure Switch Labeling for additional information.
use.

Replace Failed Backup Switch
Switch pairs are numbered sequentially as SW01, SW02, and SW03, SW04, and so on. The backup switch is the even
numbered switch – SW02, SW04, SW06 and so on in the stacked pair. Use the following procedure to replace a failed even
numbered switch.
➢ To replace a failed backup switch

1. Disconnect and remove the failed switch.
2. Check the Stack Master firmware version. Refer to the section, Check Switch Firmware Version on Operating Switches
for additional information.
3. Turn on power to the replacement switch without any stacking cables, fiber-optic, or network connections.
4. Check replacement switch firmware version. Refer to the section, Check Switch Firmware Version Using the Console for
5. Confirm that the firmware versions match. If they match, then move to step 6. If the firmware versions do NOT match,
both switches in the switch stacked pair must be replaced. Refer to the section, Replace Stacked Pair of Switches for
6. On the replacement switch, force the factory default switch configuration. Refer to the section, Force Factory Default
Switch Configuration for additional information.
7. Turn off power to the replacement switch. Connect the replacement switch to the Stack Master switch through the
stacking ports using standard Ethernet cables. Do not connect fiber-optic cables to the replacement switch. Do not
connect patch cables to the controllers, computers, or other connections external to the replacement switch.
8. Turn on power to the replacement switch and wait for a few minutes while it self-configures.
9. Confirm the correct setup as described in the section, Switch Stack Identification.
10. Apply labels to the replacement switch with the correct IP address and switch number. Refer to the section Switch Stack
Identification, the figure Switch Labeling for additional information.
use.
Switches come with a five year warranty. Contact Cisco™ support for assistance in replacing a failed switch under warranty.
Refer to the section, Cisco/Linksys Warranty Support for additional information. For switches not under warranty,
replacement switches can be ordered from GE Energy. Refer to the section, Replacement Parts Ordering for additional
information.

4.12.2 Replace Failed Stack Master Switch
Switch pairs are numbered sequentially as SW01, SW02, and SW03, SW04, and so on. The Stack Master switch is the odd
numbered switch – SW01, SW03, SW05 and so on in the stacked pair. Use this procedure to replace a failed odd numbered
switch. The Backup Stack Master becomes Stack Master after 10 minutes.
Switches come with a five year warranty. Contact Cisco support for assistance in replacing a failed switch under warranty.
Refer to the section, Cisco/Linksys Warranty Support for additional information. For switches not under warranty,
replacement switches can be ordered from GE Energy. Refer to the section, Replacement Parts Ordering for additional
information.
➢ To replace a failed Stack Master switch

1. Disconnect and remove the failed switch.
2. Check Stack Master firmware version (the remaining switch is now the Stack Master). Refer to the section, Check Switch
Firmware Version on Operating Switches for additional information.
3. Turn on power to the replacement switch without any stacking cables, fiber-optic, or network connections.
4. Check replacement switch firmware version. Refer to the section, Check Switch Firmware Version Using the Console for
5. Confirm that the firmware versions match. If they match, then move to step 6. If the firmware versions do NOT match,
both switches in the switch stacked pair must be replaced. Refer to the section, Replace Stacked Pair of Switches for
6. On the replacement switch, force the factory default switch configuration. Refer to the section, Force Factory Default
Switch Configuration for additional information.
7. Turn off power to the replacement switch. Connect the replacement switch to the stack master switch through the
stacking ports using standard Ethernet cables. Do not connect fiber-optic cables to the replacement switch. Do not
connect patch cables to the controllers, computers, or other connections external to the replacement switch.
8. Turn on power to the replacement switch and wait for a few minutes while it self-configures.
9. Apply labels to the replacement switch with the correct IP address and switch number. Refer to the section, Switch Stack
Identification, the figure Switch Labeling for additional information.
10. If needed, force the replacement switch (odd numbered) to become the stack master. Refer to the section, Configure a
Unit as the Stack Master and Configure the Unit ID for additional information.
11. Confirm the correct setup as described in the section, Switch Stack Identification.
use.

4.12.3 Force Factory Default Switch Configuration
To reset the switch to the factory default settings, insert a pin or paper clip into the RESET opening on the front panel. When
the reset switch is held for 10 seconds or longer, the switch resets to its default settings. When a switch is reset to its default
setting, it restarts in stackable mode using default stacking ports with auto-numbering enabled.
4.12.4 Switch Stack Identification

In an operational switch stack, the switch number, Unit ID, and Stack Master must be coordinated to ensure proper indication
of connections on the Network Monitor. The switches with the odd numbers, such as SW01, SW03, SW05, and so on should
have a Unit ID of one (1) and be the Stack Master. The switch with the even numbers, such as SW02, SW04, SW06, and so
on should have a Unit ID of two (2) and not be the stack master.
All indications display using LEDs on the front of the switch. They can also be viewed on the switch’s Web interface in the
System Information Menu.
Switch LEDs
LED Mode Color Description
Master Solid Green The switch is the Stack Master.
Off N/A The switch is not the Stack Master or the switch is not
stacked.
ID n Solid Green The switch is Unit ID n.
Off N/A The switch is not Unit ID n or the switch is not stacked.
All ports Solid Red The switch is powered on, but not operational.

After replacing a failed switch in the stack, verify these settings. If necessary, adjust the settings. Refer to the section,
Configure a Unit as the Stack Master and Configure the Unit ID for additional information. Also, ensure that the switches are
labeled correctly. The following is a typical SFE2000 switch showing the label locations:
Switch Labeling
4.12.5 SFE2000 Access Control

Access the network switch Web interface (GUI) at http://192.168.201xxx using the IP address on the switch front label. The
SFE2000 ships with both the username and password set to admin. If they have been changed, check with the local system
administrator for the new settings. Enter both the username and password to log on to the Web GUI.

4.12.5.1 Configure a Unit as the Stack Master and Configure the Unit ID
The lower switch number (odd number SW01, SW03, and so on) should have a Unit ID of one (1), and the higher switch
number (even number SW02, SW04, and so on) should have a Unit ID of one (2). If it becomes necessary to adjust the Unit
ID, log on to the network switch Web interface to make the change. Refer to the section, SFE2000 Access Control for
additional information. Use the Web interface to assign a static Unit ID to allow the unit to be renumbered.
➢ To configure a unit as the Stack Master

1. Log on to the network switch Web interface at http://192.168.201xxx using the IP address on the switch front label.
2. From the SFE 2000 Tree View, expand System, expand System Management, and select Stack Management.
3. From the Stack Management section, for the lower numbered switch, set the Unit No. After Reset text box to 1.
4. From the Stack Management section, for the higher numbered switch, set the Unit No. After Reset text box to 2.
5. From the Stack Management section, for the Master Election item, select Force Master, and for the Stacking
Ports After Reset item, select Copper Ports (or Combo/Fiber Ports if appropriate).
6. Click Apply to save the changes.
7. From the SFE 2000 Tree View, select Reset.

8. From the Reset section, in the Reset Unit No. text box, select Stack from the drop down menu.
9. Click Reset.

Resetting the Stack disrupts the network communications for computers, control
systems, and printers connected to the stacked switch pair. Network redundancy is
temporarily interrupted for the ring containing the stacked switch pair.
Attention
➢ To Configure the Unit ID
1. After the switches restart, log on to the network switch web interface at http://192.168.201xxx using the IP address on the
switch front label.
2. From the SFE 2000 Tree View, expand System, expand System Management, and select Stack Management.
3. From the Stack Management section, set the Unit No. After Reset for both switches to Auto.
4. From the Stack Management section, for the Master Election item, select Automatically.
5. Click Apply to save the changes.

6. From the SFE 2000 Tree View, select Reset.
7. From the Reset section, in the Reset Unit No. text box, select Stack from the drop down menu.
8. Click Reset.
Resetting the Stack disrupts the network communications for computers, control
systems, and printers connected to the stacked switch pair. Network redundancy is
temporarily interrupted for the ring containing the stacked switch pair.
Attention

4.12.5.2 Check Switch Firmware Version on Operating Switches
The switch firmware version is on a label on top of the switch. Refer to the section Switch Stack Identification, the figure
Switch Labeling for additional information.
➢ To check the switch firmware version

1. Log on to the network switch Web interface at http://192.168.201xxx using the IP address on the switch front label.
2. From the Tree View, expand System, expand System Management, and select System Information. The
software (firmware) versions display on this page.

4.12.6 Network Switch Console
Each Network Switch is supplied with a serial cable for basic, off line configuration adjustments. It is necessary to use this
interface for the following tasks when replacing a SFE2000 network switch:
• Check the switch’s software (firmware) version when preparing to replace a failed SFE2000 network switch in a stacked
pair.
• Check and set the IP Address of a stacked pair of switches to replace a failed pair of switches.
The switch can connect to a computer using the serial cable. The computer can access the switch’s console functions over the
serial interface.
4.12.6.1 Configuring the HyperTerminal™ Application

Before using the console interface, the HyperTerminal application must be configured on the computer.
➢ To configure the HyperTerminal application

1. Connect the supplied serial cable from the switch to the serial port on a computer.
2. From the computer Start menu, select Programs, Accessories, Communications, and HyperTerminal.
3. From the Connection Description dialog box, enter a Name for the connection (such as Linksys One).
4. Select an Icon for the application and click OK.
5. From the SFE2000 Properties dialog box, select the Connect To tab.
6. From the Connect Using text box, select a port from the drop down list (such as COM1). (Used to communicate with
the Ethernet switch.) Click Configure.

7. From the COM1 Properties dialog box, set the serial port settings as follows:
• Bits per second: 115200

• Data bits: 8
• Parity: None
• Stop bits: 1
• Flow control: None
8. Click OK
4.12.6.2 Console Access Control

Access the network switch console by connecting the switch to a computer with the serial cable supplied with the switch and
using its serial Web interface (GUI). The SFE2000 ships with both the username and password set to admin. If they have
been changed, check with the local system administrator for the new settings. Enter both the username and password when
logging on to the switch console.

Use the arrow keys and other keys as listed on the console screen to navigate.
4.12.6.3 Check the Switch Firmware Version Using the Console

➢ To check the switch firmware version using the console
1. Log on to the network switch console using its serial Web interface (GUI).
2. From the Switch Main Menu screen, select System Configuration Menu.
3. Select System Information and Versions.
4. The Versions screen displays the Boot, Software, and Hardware firmware versions of the Ethernet switch. (In
stacking mode, this information is displayed for the stack master.)
5. Select Quit and press Enter to exit the console.

4.12.6.4 Change the Switch Stack IP Address Using the Console
➢ To change the switch stack IP address using the console
3. Select IP Configuration and IPV4 Address Configuration.
4. From the IP Address Configuration screen, set the options as follows:
• Switch IP address: http://192.168.201xxx according to the site network topology diagram

• Subnet Mask: 255.255.255.0
5. Select Save and press Enter to save the settings.
6. Complete the procedure in the following section, Save the Switch Configuration Using the Console.
4.12.6.5 Save the Switch Configuration Using the Console

➢ To save the switch configuration using the console
3. Select File Management and Upgrade/Backup IPV4.

4. From the File Management screen, change the options to the following:
• Source File: running-config

• Destination File: startup-config
5. Select Execute and press Enter.
6. Select Quit and press Enter to exit the console.
4.12.7 Cisco/Linksys Warranty Support

Switches come with a five year warranty. Contact Cisco support for assistance in replacing a failed switch under warranty.
http://www.cisco.com/en/US/docs/general/warranty/5year_SmallBusiness.pdf
4.12.8 Replacement Parts Ordering

GE PartsEdge offers a comprehensive, easy-to-use tool to access parts information and recommendations, obtain quotes,
convert quotes to orders, and track orders in real-time from placement to delivery. Use the following:
• Call +1-704-947-3386 worldwide

• http://www.gepower.com/online_tools/parts_edge.htm

Notes

5 Renewable Energy
5.1 How to Set Up the Dynamic Data Recorder (DDR) and
Trender for Wind Farms
This document is designed to be used by GE Field Engineers and requires the
following:
• SSO (Single Sign On Account)
• Telnet Access
Attention • Site ToolboxST application access
• Wind CSN user account
This document uses the Fowler Ridge Wind Farm as an example to perform the following procedures:
• Setting up the Dynamic Data Recorder (DDR) for encoder in the ToolboxST* application.
• Setting up a live Trender with the signals defined in the DDR section.
Note Actual file locations, IP addresses, and Telnet numbers will vary by site.
5.1.1 Dynamic Data Recorder (DDR)

The DDR feature collects data when specified trigger events occur. Up to 12 DDRs can be configured for the controller.
➢ To set up the DDR

1. From the Start menu, select Run to display the Run dialog box.
Renewable Energy GEH-6808N Instruction Guide 335

2. From the Start menu, select Programs, Accessories, Communications, and Remote Desktop Connection to
display the Remote Desktop Connection dialog box.
3. From the Log On dialog box, select User Name, enter Engineering, (or appropriate User Name), select Password,
and enter the appropriate password.
4. After connection to the site is completed, from the desktop, double-click the ToolboxST icon or locate and select
the site .tcw file (such as D:\GEWindSite|GEWindSite.tcw). The system displays in the ToolboxST System
Editor.

After the
component has
finished loading,
click the button to
go online.
5. The Component Editor displays. From the Component Info View, select the Status tab (on the lower left corner)
and check that the Controller Equality is Equal.

6. If the state is unequal, from the Device menu, select Upload to do an upload.

7. From the Tree View, select AEPA-3B2. Repeat the above process to add connected variables, but change the variable
names to DeltaMarkerPulseA2, IncrEncoderCntsA2,and IncrMarkerCntsA2 respectively.
8. From the Tree View, select AEPA-3C3. Repeat the above process to add connected variables, but change the variable
names to DeltaMarkerPulseA3, IncrEncoderCntsA3, and IncrMarkerCntsA3 respectively.

10. When the process is complete, click Build again.

11. When the process is complete, click Download . The Download Mark VIe Controller wizard displays.
12. The progress bar shows 100% when the DDR has been set up successfully.

13. From the Component Editor toolbar, click Build .
14. From the Component InfoView, select the Log tab a check for errors. If any error messages display, stop and seek
assistance.
15. When the process is complete, click Build again.

16. When the process is complete, click Download . The Download WorkstationST wizard displays.
17. When the process is complete, don’t shut down the system and use the Log Off option to leave the site.

5.1.2 Trender Tool
The Trender is a tool used to capture and display trend graphs of variables in the system. It can collect and display values in
real time from controllers and other sources, and can display data collected by high-speed coherent data collection systems,
such as capture buffers and dynamic data recorders. The Trender also can display previously captured data from a saved data
file.
Note The following is an example on how to set up a live Trender with the signals defined earlier in the DDR section.
➢ To set up a live Trender

1. From the Start menu, select Run to display the Run dialog box.
2. From the Start menu, select Programs, Accessories, Communications, and Remote Desktop Connection to
display the Remote Desktop Connection dialog box.

3. From the Log On dialog box, select User Name, enter Engineering, (or appropriate User Name), select Password,
and enter the appropriate password.
4. After connection to the site is completed, from the desktop, locate and the site .tcw file (such as D:\GEWindSite|
GEWindSite.tcw). The system displays in the ToolboxST System Editor.
5. From the toolbar, click Go On/Offline to go online.

6. Name the collection turbine number_encoder (for example I123_encoder).

7. Add the following signals using the appropriate turbine prefix (such as I123):
I123.AI_In_BrakePWMVoltageA1 I123.DI_In_EncPositionNOKA1
I123.AI_in_HubAmbientTemp I123.DI_In_IncEncCorrectionA1
I123.AI_In_MotorCurrentA1 I123.DI_In_IncEncCorrectionA2
I123.AI_In_MotorCurrentA2 I123.DI_In_IncEncCorrectionA3
I123.AI_In_MotorCurrentA3 I123.DI_In_IncEncoderNOKA1
I123.AI_In_MotorTempA1 I123.DI_In_IncEncoderNOKA2
I123.AI_In_MotorTempA2 I123.DI_In_IncEncoderNOKA3
I123.AI_In_MotorTempA3 I123.DI_In_MainsOnA1
I123.AI_In_MotorVoltageA1 I123.DI_In_MainsOnA2
I123.AI_In_MotorVoltageA2 I123.DI_In_MainsOnA3
I123.AI_In_MotorVoltageA3 I123.DI_In_MarkerLossA1
I123.AI_In_MtrSpdRefA1 I123.DI_In_MarkerLossA2
I123.AI_In_MtrSpdRefA2 I123.DI_In_MarkerLossA3
I123.AI_In_MtrSpdRefA3 I123.DeltaMarkerPulseA1
I123.AI_In_PitchAngleCurrent1 I123.DeltaMarkerPulseA2
I123.AI_In_PitchAngleCurrent2 I123.DeltaMarkerPulseA3
I123.AI_In_PitchAngleCurrent3
I123.AI_In_TbWindSpeed_NRG
I123.AI_In_TorqueRefA1
Note The last three signals (deltaMarkerPulseA1, A2, and A3) need to be set up in DDR first to be added.

8. Add all of the variables and periodically from the toolbar, click Save .
9. After all variables are added, from the toolbar click Save .
11. After the build is complete, from the toolbar, click Download .
12. After the download is complete, click Go On/Offline to go offline.

13. Close the ToolboxST application and use the Log Off option to leave the site.

5.2 How to Configure a Wind Turbine ESS Doubly Fed
Induction Generator Control
The 1.6 MW wind power converter, combined with an Electrical Simplified System (ESS), provides excitation and torque
control for the doubly-fed induction generator (DFIG). The DFIG ESS (DFIGe) power converter is configured from the
ToolboxST* application System Editor.
Note It is necessary to first add both a Mark VIe controller and a Power Conversion controller, and configure each of them
to communicate with one another.
➢ To configure a DFIGe power converter

1. Open a *.tcw file.
2. From the System Editor Tree View, right-click the system and select Insert New, Controller, and Mark* VIe
Controller. The Mark VIe Creation Wizard displays.

3. From the System Editor Tree View, right-click the system and select Insert New, Controller, and Power
Conversion Control. The Power Conversion Creation Wizard displays.

5.3 How to Configure a Solar Power Inverter
A solar power inverter converts dc power from an array of photovoltaic devices into ac power at the grid frequency.
Note A Mark VIe controller and a Power Conversion controller must be added and configured to communicate with one
another.
➢ To configure a solar power inverter

1. Open a *tcw file.
2. From the System Editor Tree View, right-click the system and select Insert New, Controller, and Mark VIe
Controller. The Mark VIe Creation Wizard displays.

3. From the System Editor Tree View, right-click the system and select Insert New, Controller, and Power
Conversion Control. The Power Conversion Creation Wizard displays.

6 Legacy Support
6.1 How to Set Up and Download to Legacy Mark VIe and
Mark VIeS Controllers
6.1.1 Using Serial Cable (UCCA and UCCC)
To download an IP address to a legacy Mark VIe UCCA or UCCC controller, the following equipment is required.
For UCCC controllers:
Standard 4 pair UTP cable (Ethernet Cable) and Controller Connector (Part #: 342A4931ABP1)
For UCCA controllers:
Serial Cable (Part #: 336A3582P1) and Mini-Serial Cable Adapter (Part #: 336A4929G1)
Legacy Support GEH-6808N Instruction Guide 365

➢ To set the controller IP address using a serial cable
1. Connect the appropriate serial cables to the COM1 port of the R controller.
2. From the ToolboxST application, open the Mark VIe control *.tcw file.
3. From the Device menu, select Download and Controller Setup.

4. Select Configure Network Address and click Next.

5. Move the serial cable to the S controller.
6. Repeat steps 5 through 8 for the S controller.
7. Move the serial cable to the T controller.
8. Repeat steps 5 through 8 for the T controller.
Note Each controller is automatically restarted after the Controller Setup Wizard completes.

6.1.2 Downloading to the Controller
➢ To download to the controller
1. From the ToolboxST application, open the Mark VIe control .tcw file.
2. From the ToolboxST System Editor, open the Mark VIe component.
3. From the toolbar, click the Build button. Click the Component InfoView and verify there are no errors.
4. Click Download.

Note The base load and/or firmware might indicate Green Equal if they have already been downloaded earlier during FAT or
factory testing. GE Energy recommends that the respective check boxes be manually selected during a first-time download.

5. The controller restarts itself at each step after base load, firmware, and application code during the download.
6. When the download is complete, wait two minutes and go online with the controller to verify the equality for all three
controllers.

6.1.3 Downloading to the I/O Modules
➢ To download to the I/O modules
1. From the ToolboxST application, open the Mark VIe control .tcw file.
2. From the System Editor, open the Mark VIe component.
3. From the Hardware tab, right-click a pack and select Modify.
4. Enter the bar codes (found on terminal board stickers) in the I/O module configuration.
5. Cross-verify the bar codes with the Dallas ID read by the controller.
6. Click Online to go online with the controller.
7. Verify each bar code number for all I/O modules.

8. Build the software and verify that there are no errors.
9. Select Device, Download, Download Wizard and click Next.
10. Select the Scan I/O box and the Show All check boxes.
11. Click Scan.
Note When opening the Download Wizard, the configured hardware is automatically scanned for healthiness if the Scan was
previously enabled.

12. Verify that the Base load, Firmware and Parameters check boxes are selected for all packs.
Note Cycle power to the I/O modules or to the entire cabinet if some modules are not being read or located by the scan.
Re-scan the hardware more than once, if necessary.
Note The base load and/or firmware might indicate Green Equal status on some I/O modules if a previous download was
performed during FAT or factory testing. Manually select all respective check boxes during the first-time download.
13. Select the Download Backup File and click Next.
14. When download is complete, wait two minutes and go online to verify the status of the I/O modules.
15. To verify the download was successful, open the Download Wizard again and scan the hardware. Verify that all
controllers and modules display as Green Equal.

16. Check the controller diagnostic alarms and reset alarms.
17. Verify I/O module diagnostic alarms and reset alarms as follows:
a. From the Component InfoView, select the Status tab.
b. Double-click the I/O Diagnostic status and select All I/O modules from the drop-down list.

18. When the download is complete, select the Hardware tab and select all I/O modules.
19. Perform a build and download the application code to the controllers.

6.2 How to Download the IP Address for a Mark* VI
Controller Using the Control System Solutions (toolbox)
Application
This document is based upon a Mark VI controller in a system using the GE Control System Solutions (toolbox) application.
You will need the following cables to connect from your computer to the controller:
Serial Cable Mini-Serial Cable Adapter

Part #: 336A3582P1 Part #: 336A4929G1
➢ To download the IP address for a Mark VI controller

1. Connect a cable from your computer (typically port COM1) to the controller.
2. From the Start menu, select All Programs, GE Control System Solutions, Mark VI Controller (Version),
Serial Loader, and Serial Loader. The Serial Loader dialog box displays.
The Platform drop- The Source

down list allows you
Di re c tor y
to select a controller button is
type. enabled when
the Platform is
set to C ustom
or Mark V LM.
The Serial Port
Settings button The TCP\IP
allows you to select Settings button
the COM port and displays the TCP
communications IP SETTINGS
settings. Select the dialog box (see
highest Baud rate below).
supported by your
computer. D is play
Sum m ary
Info rm a tion
displays the
current TCPIP
settings in the
Log window

Click Load
Settings to
download the
settings entered
from a SSF file
Click Save
Settings to
store the
settings to a
.SSF file.
Note Obtain the Computer name, IP Address, Subnet Mask broadcast address, and Router IP address from the network
administrator. All IP addresses and masks are represented in a 192.168.1.1 format.
3. Complete all data fields and selection options in the Serial Loader and TCP/IP SETTINGS dialog boxes.
4. Click OK in each dialog box to save the settings and return to the Serial Loader dialog box.
5. From the Serial Loader dialog box, select Configure TCP/IP.
6. Click the Start Command(s) button. The IP address is downloaded to the Mark VI controller. Any messages will be
displayed in the Component InfoView Log tab.

6.3 How to Import Control System Solutions (toolbox)
Turbine Historian Configurations to the WorkstationST*
Historian Feature
The eTCSS product generation Control System Solution (toolbox) includes a Turbine Historian device for saving long term
historical data. The ControlST* product generation includes a WorkstationST Historian feature for the same purpose. This
procedure defines how to take the existing list of signals along with their attributes (such as the significant change band) and
import them into the ControlST software suite.
The document contains the following procedures:
• Export the Turbine Historian files from the CSS toolbox application.
• Import the M6B configurations.
• Enable the Historian feature on a WorkstationST component.
• Import the Turbine Historian files.
• Verify the information was imported correctly.
• Troubleshoot signals that do not display on the Historian or Recorder tabs.
6.3.1 Prerequisites
• The CSS (toolbox) application must be V11.01.01C or later to support the Export to NextGen feature.
• The ControlST software suite must be installed.
• A resulting system must be built in the ToolboxST application.

6.3.2 Export Data Historian Files
➢ To export the Turbine Historian files from the toolbox application:

1. From the GE Control System Toolbox File menu, select Open, then browse to locate and select the Turbine
Historian to be exported.
2. Click Open to display the component.
From the Tree

View, highlight
the turbine
Historian device
From the File

menu, select
Export and All
Note The Export – All action creates each *.tre and *.prj file for the respective Turbine Historian device. Store all files in a
single directory. (During export, these are typically stored in the directory of the original Turbine Historian *.thb device.)

Select the
desired directory,
then click Save
for each .prj and
.tre file
A copy of the Turbine Historian configuration is placed in the desired directory.

Before importing the Historian points, ensure the required M6b configurations are imported to the MarkVIe device in the
ToolboxST application.
➢ To import the M6B configurations

1. Import the required MarkVI libraries to the MarkVIe library container using the Tree File Importer .
2. Create a Mark VIe component in the ToolboxST application with the same name as that in the CSS toolbox application.
(The Tree File Importer looks for the exact same name.) For example, if the Mark VI component name is BOP, create a
Mark VIe component with the name BOP.
3. Refer the libraries imported in step 1 to the new BOP device created in step 2 using the Library Reference menu
option.
4. Import the MarkVI configuration into the MarkVIe component.
5. Compress all EGD pages (a major difference may be present).
6. From the Mark VIe Component Editor toolbar, click the Build icon and build the MarkVIe component.
7. From the Component InfoView, check for any Errors related to a signal being an array on an EGD page. Remove
these signals by deleting the value in the EGD page attribute.

6.3.3 Configure the WorkstationST Historian Feature
The WorkstationST component with the historical data storage subsystem must be configured to enable its Historian feature.
➢ To enable the Historian feature on a WorkstationST component

1. From the ToolboxST System Editor, select and double-click the WorkstationST component that includes the
Historical Storage subsystem.
From the General

tab, select Features,
then from the
Summary View, set
Historian to True
2. From the toolbar, click Save and close the ToolboxST application.
The WorkstationST component is now configured to import the Turbine Historian files.

6.3.4 Import Turbine Historian Files
The Tree File Importer is used to import files into the ToolboxST application.
➢ To import the Turbine Historian files : from the Start menu, select All Programs , GE ControlST , ToolboxST,
and Tree File Importer to display the Tree File Importer dialog box.
Click the ellipsis Click the ellipsis

button to locate and button to locate and
select a .tre or .prj file select a .tcw file
Select the WorkstationST

component and click Import
Note If an Error or Warning displays from the Tree File Importer, double-click the Error or Warning to display a Text File
Editor dialog box.
The Turbine Historian configuration files have been imported to the Historian feature of the selected WorkstationST
component.

➢ To verify the information was imported correctly
From the System Editor File

menu, select Open System .
Locate and select the system

.tcw file containing the
Historian file .
Click Open.
From the Tree

View, double-click
the WorkstationST
component to
display the
Component Editor
From the Historian tab, select Consumed

Device List and verify that the signals and
Historian Deadband have been added with
User Defined displayed in theSource column
Note To import the Historian points from the .tre file, verify that these points are present in the Referenced Device list in the
EGD tab Tree View of the selected WorkstationST component. They must be present on EGD for them to display in the
Historian.
➢ To troubleshoot signals that do not display on the Historian or Recorder tabs

1. From the WorkstationST conponentEGD tab, expand Referenced Devices and select the appropriate device (such as
BOP).
2. If it is not there, from the respective MarkVIe Component Editor (BOP) Software tab, search for the signal and add, if
necessary.
3. If present, verify that it has been placed on EGD.
4. From the toolbar, click the Build icon.
From the
WorkStationST EGD
tab, right-click the
appropriate
Referenced Device
(BOP ) and select
Refresh to display
newly added signal on
the variable list.
5. Repeat the procedure to Import the Turbine Historian files.

Data Historian Configurations to the WorkstationST*
Recorder Feature
The eTCSS software product includes a Data Historian for saving short term historical data. The ControlST* software product
includes a WorkstationST Recorder for saving short term historical data. This procedure defines how to take the existing list
of signals and their attributes (such as the significant change band) and import them into the ControlST environment.
This how-to guide consists of three procedures:
• Export the existing definitions using the toolbox application.

• Configure the WorkstationST Recorder using the ToolboxST* application.
• Use the ToolboxST Tree File Importer to read the exported information into the target workstation.
6.4.1 Prerequisites
When upgrading the Data Historian from the toolbox application to the ToolboxST application there are several prerequisites:
• The toolbox application must be version 11.01.01C or newer to support the Export to NextGen feature.
• The ControlST software must be installed.

6.4.2 Exporting Data Historian Files
➢ To export the Data Historian configuration from the toolbox application
The export function creates each *.tre and *.prj file for each Data Historian. Store all the files in a single directory. (Typically
it defaults to the directory of the original *.reb file.)
A copy of the Data Historian configuration is saved into the desired directory.

6.4.3 Configuring the WorkstationST Recorder Feature
The WorkstationST component that has the recorder subsystem must be configured to enable its Recorder feature.
➢ To enable the Recorder feature on a WorkstationST component

1. From the ToolboxST System Editor, select and double-click the WorkstationST component that is to be used for the
Recorder feature.
2. From the toolbar, click Save and then close the ToolboxST application.
The WorkstationST component is now configured to import the Data Historian files.

6.4.4 Importing Data Historian Files
The tree file importer is used to import files into the ToolboxST application.
➢ To import the Data Historian files

Note If an Error or Warning displays from the tree file importer, double-click the Error/Warning to display a Text File Editor
dialog box that provides the line in the .tre or .prj file that is the cause of the warning.

The Turbine Historian configuration files have been imported to the WorkstationST Recorder.
➢ To verify the information was imported correctly

1. Open the system (.tcw) file containing the WorkstationST component with the Recorder.
2. From the Tree View, double-click the WorkstationST component to display the Component Editor.
3. Select the Recorder tab and verify the items have been added.

6.5 How to Configure the ToolboxST* Application to
Receive Mark* VI Data from a Control System Solutions
(toolbox) Application
The toolbox application is used to configure and download the Mark VI controller. The change in the Mark VI controller
configuration often needs to be conveyed to ToolboxST based devices, such as WorkstationST*-based HMIs or
ToolboxST-based controllers, so that they can update how they exchange and interpret the Mark VI controller information. To
accomplish this configuration exchange the toolbox application puts the new Mark VI controller configuration information
into the System Database (SDB). The ToolboxST application retrieves the controller configuration from the SDB and uses it
to configure the WorkstationST-based HMIs and ToolboxST-based controllers that exchange information with the Mark VI
controller.
Note This document is based upon both toolbox and ToolboxST applications being active, and having a system created in
the ToolboxST application. Refer to the ToolboxST User Guide for Mark* Controls Platform (GEH-6700) for details on
ControlST software suite installation and creating a system in the ToolboxST application.
Setting Up an EGD Configuration Server

Several items must be configured in the ToolboxST and WorkstationST applications. If a WorkstationST component is used as
either an OPC DA Server, or as an Alarm Server, there must be an Ethernet Global Data (EGD) Configuration Server in the
system.
➢ To set up an EGD Configuration Server in the ToolboxST application
• From the System Editor Tree View, double-click the WorkstationST component (in this example GW3-SVR)
selected to run the EGD Configuration Server. The Component Editor displays.

Changing the ToolboxST Network Name
The toolbox and ToolboxST applications identify networks by the network name. The names assigned for the Unit Data
Highway (UDH) in both applications must match.
➢ To change the network name in the ToolboxST application

Adding Mark VI Data to the ToolboxST System
➢ To add Mark VI data to the ToolboxST system
Editor.
2. From the File menu, select Open System, then locate the system file to open. The System Editor displays.

Property Settings
Settings Description
App Path Location of the toolbox application executable file
Doc Path Location of the toolbox (.m6b) file
Enable EGD Editor False

Enable Get From SDB True (Required)
Leave Slashes True

Adding a Mark VI Component to the SDB
➢ To add the Mark VI component to the SDB
• From the ToolboxST System Editor, double-click the Mark VI External Device (such as G1) to display the
Control System Solutions Toolbox window.
The Mark VI component has been added to the SDB. The ToolboxST configuration and the Mark VI External Device can
now be updated.

Updating the ToolboxST Configuration from the SDB
➢ To update the ToolboxST configuration from the SDB
• From the Tree View, double-click the System item to display the System Information Editor.
Note You will need to create format specifications for the Mark VI scales. These are not imported from the SDB.

Updating the Mark VI External Device from the SDB
➢ To update the Mark VI External Device configuration
1. From the ToolboxST System Editor, double-click the Mark VI External Device (such as G1) to display the GE
Control System Toolbox window.
2. Edit the Mark VI component to make desired changes (such as adding additional signals, editing code, and so forth).
3. From the toolbar, click the Validate button.
4. From the toolbar, click Build to display the Build options dialog box.

6. When the download is complete, click Save.
7. From the ToolboxST System Editor Tree View, right-click the Mark VI External Device and select Get EGD
from SDB.
8. From the ToolboxST System Editor Tree View, double-click each component that uses a signal from the Mark VI
External Device and Build and Download each component.
The Mark VI External Device is now ready to receive and process signals from the Mark VI component.

6.6 How to Convert a Mark* V Component for Use in
ControlST* Applications
In ControlST V4.00, the ToolboxST application can configure Mark V controllers (in addition to the Mark VI and Mark VIe
controllers). Sites using Mark V can upgrade from the Control System Solutions product to the ControlST product
applications.
Note The Mark V Feature is an option in the WorkstationST Component Editor, similar to other options such as MODBUS®
or the OPC® DA Server. Enabling the Mark V Feature enables direct WorkstationST communication to the Mark V
controllers. The list of Mark V controllers that the WorkstationST component is to contact is defined in the Consumed
Devices list, and includes the Mark V components configured into the system using the ToolboxST application.
Basic procedures are:
• Copy the Mark V and HMI Configuration files from the existing site, modifying as needed
• Configure the Mark V Feature’s Control Panel
• Add the Mark V component to the ToolboxST system definition
• Modify the WorkstationST component to include the new Mark V component, then Build, Download, and restart
• Rebuild the Start menu Turbine Control Maintenance (ST) to include the new Mark V
• Update the Mark V component to launch the Mark V maintenance tools
• Import the Mark V configuration files into the ToolboxST System Definition
• Publish the Mark V component information to the EGD Configuration Server
• Add (optional) features for DCS communication (such as MODBUS or GSM interfaces)
• Add (optional) Alarm Help imported from the previous product
• Add EX2000 Fault Code Scanning (if required)

6.6.1 Copying the Mark V and HMI Configuration Files
The HMI servers running the WorkstationST Mark V Feature use a configuration directory with unit specific sub-directories,
the same as the existing or HMI computers. The standard location for this site directory is E:\Site_ST.
➢ To copy the Mark V and HMI configuration files
Tip � When copying from an HMI, shut down the TCI system service first to prevent errors due to attempting to copy files
that are open and active.
After copying the files from the existing system the modifications in the next five sections must be made. The following
modifications reference a set of template files distributed with the Mark V Feature. These template files are located where the
WorkstationST application is installed (typically in the C:\Program Files\GE Energy\WorkstationST Features\TCI\Data
directory).
6.6.1.1 Modifying the CONFIG.DAT File

As a reference, use the template for the site directory CONFIG.DAT file located in the template directory. The following list
provides guidelines and other information necessary for modifying the CONGIG.DAT file.
• The SITENAME section seldom needs to be changed.

• Remove all units that are not Mark V units from the UNIT_DATA section. The Mark V Feature only supports Mark V
components. The Mark VI components are supported in the native WorkstationST component, and the internal devices
are typically handled by defining a set of WorkstationST variables and using the WorkstationST subsystems to populate
them with real time values. The Mark V LM components are not supported by the Mark V Feature.
• When copying from an there is not a NETWORK_TYPE section. When copying from an HMI, the NETWORK_
TYPE section might specify the use of a different ARCNET® card than is supported by the Mark V Feature. Verify the
NETWORK_TYPE section defines one or two PCI™-based ARCNET cards using the CCSI20020DEVn driver. If
needed, copy the section from the template file and select the number of ARCNET cards to match the target
configuration.
• The NETWORK_DATA section retains the entries for the Mark V components. If any unit numbers are changed when
modifying the UNIT_DATA section, make sure the corresponding change is made in the NETWORK_DATA section.
• Most of the entries in the OPTIONS section can be removed. The Mark V Feature supports the HST_DIR entry to change
the historical data directory (where the Trip Logs are stored) and the MODBUS entry if the native MODBUS option is
required.
− Many existing HMI sites have the HST_DIR entry point to a subdirectory of the Historian_Data directory created for
the eTCSS Data Historian program. That program (and associated directory) is not present in the ControlST
environment, so it should be changed.
Tip � The original standard for an HMI was a directory called C:\HMIDATA. This is a good choice as that is where many
users will look first.
− Many sites will switch to use the MODBUS Slave from the WorkstationST application and not the MODBUS Slave
from the Mark V Feature. Do not include the MODBUS entry unless you are using the MODBUS Slave from the
Mark V Feature.

6.6.1.2 Modifying the IO_PORTS.DAT File
As a reference, use the template for the site directory IO_PORTS.DAT file located in the template directory. The only options
currently supported by the Mark V Feature are those for the MODBUS Slave subsystem. All other sections can be deleted to
reduce confusion. The MODBUS Slave sections that are supported include:
• [MODBUS_SLAVE_PORT] to define the Serial Port (COM1, COM2...) or Ethernet Port (Ethernet) used for MODBUS
communication.
• [MODBUS_ASSIGNMENT] to map the MODBUS slave addresses to the associated turbine controller and control the
format of the data (signed 16 bit, unsigned 16 bit, Native...).
• [MODBUS_SLAVE_TIMEOUT] to control the timeout period for the MODBUS Slave and the NAK code that is
returned upon that timeout.
6.6.1.3 Adding the HSTPOINT.SRC File for Historical Data Storage

In the previous product, the Historian used the HSTPOINT.SRC file in the Mark V Unit Configuration directory to indicate
the variables to collect for historical storage, and the significant change band used for each signal. This file was only used on
the Historian, not the HMIs. If there is a workstation with the Historian Feature enabled (to transfer data into historical data
storage) then copy the HSTPOINT.SRC file from the previous Historian and add it to the Mark V Unit Configuration
directory. The next time the Mark V Feature is restarted the list of desired variables with their significant change information
will be included in the Mark V configuration.
Note Since this information is typically used during configuration, after the restart use the commands Copy From TCI and
Publish to EGD Configuration Server to make the information available to all the configuration tools.
6.6.1.4 Modifying the Native Modbus Data File

The processor used a MODBUS.DAT file to map the signals in the Mark V product to the Modbus registers. It did not
include rescaling of the signals; the value in the Mark V product was what was sent over the MODBUS link. The HMI added
the ability to rescale the signals, and the sending of the raw data was called running in the Native mode. To allow concurrent
use of both Native and Rescaled modes in the HMI, the Native mode file was renamed from MODBUS.DAT to MODBUS_
N.DAT. When migrating from an to a HMI using Native mode, the file must be renamed from MODBUS.DAT to
MODBUS_N.DAT. After the file is renamed, open the file and remove any spaces in the Modbus register address (””HR
001”” becomes “”HR001””).
6.6.1.5 Modifying the Short Term Trending
The processor used a F:\ST_TREND.DAT file to indicate up to 64 signals to be collected in the background to backfill
real time trends. The workstation has a similar feature using the workstation Recorder Feature to backfill the Trender with
data. The HMI data is all defined using an ST_TREND.SRC file in each Mark V Unit Configuration directory, and follows
the HMI standard of having the Unit Configuration files not include unit names (so the files can be copied from unit to unit).

➢ To covert the format file to the HMI format files
1. Create an ST_TREND.SRC file in each Mark V Unit Configuration directory.
2. From the processor, copy the F:\ST_TREND.DAT file to act as the source of the data, and paste the contents of the
 ST_TREND.DAT file into the newly created file(s).
3. Copy the lines that contain variables from the target unit and remove the unit name to leave only the variable name and
the optional significant change value.
6.6.2 Configuring the Mark V Feature's All Programs, Turbine Control

Maintenance (ST), and Mark V Feature Settings
The Mark V Feature’s global settings are configured as follows:
➢ To configure the Mark V Feature settings

1. From the Start menu, select All Programs, Turbine Control Maintenance (ST), and Mark V Feature Settings.
The Turbine Control Interface dialog box displays.
2. Double-click the Turbine Interface icon to display the Turbine Control Interface dialog box.
Note You may have to open this as an administrator in order to edit the settings.
Note The Scale field must match the scale code set for the Mark V controller from its unit configuration directory (English,
Metric, Hardware, and Custom) and the Measurement Units field must match the name of the measurement units defined in
the system component’s format specifications. (In the WorkstationST component, the measurement units are selected using
the WorkstationST name. These are retrieved using the Mark V feature using the files defined in the Scale field.)

6.6.3 Adding a Mark V Component
➢ To add a Mark V component to the ToolboxST system
1. From the Start menu, select Start, Programs, GE ControlST, ToolboxST, and ToolboxST. The ToolboxST
System Editor displays.
2. If the system displayed is not the correct one, select File and Open to locate and select the correct system.

3. From the File menu, select Close to close Mark V component.
6.6.4 Including the Mark V Component in a WorkstationST Component

➢ To include the Mark V component in a WorkstationST component
1. Open the ToolboxST system.

Note Select Yes if this workstation is a server for the Mark V component, select ByProxy if this workstation is a Viewer.
When ByProxy is selected the Primary Proxy and optionally the Secondary Proxy are filled out with the names of workstation
components that are servers for the Mark V component.
From the Component

InfoView , select the
Log tab.
Check for and correct

any errors.
2. Correct the errors and repeat the Build process until there are no errors.

3. From the toolbar, click the Download button. The Download WorkstationST window displays and shows the
application code equality. Verify appropriate boxes are checked and click Next to download the WorkstationST
application code.
4. From the File menu, select Close to close the WorkstationST component.
5. From the File menu, select Exit to exit the ToolboxST application.
6.6.5 Determining the Mark V Start Directory

➢ To determine the Mark V start directory
1. Make sure the WorkstationST application is started and the Mark V Feature in the WorkstationST component is running
(this is required for the rebuild process to know what Mark V units are available and where their Unit Configuration
directories can be found).
2. From the Start menu, select Programs, Turbine Control Maintenance (ST), and Rebuild Start Menu. The
Rebuild Start Menu dialog box displays.
6.6.6 Configuring ToolboxST to Start the Mark V Maintenance Tools

➢ To configure ToolboxST to start the Mark V Maintenance Tools
1. From the desktop, double-click the My Computer icon, C: drive, Documents and Settings, All Users, Start
Menu, Programs, Turbine Control Maintenance, and Unit T1 file. The following dialog box displays.

2. Right-click any icon in the dialog box and select Properties from the shortcut menu. The Properties dialog box
displays.
3. From the Start menu, select Program, GE ControlST, ToolboxST, and ToolboxST. The System Editor displays.
4. From the Tree View, double-click the Mark V component to display the Component Editor.

➢ To test the configuration
6.6.7 Importing the Mark V Configuration into the ToolboxST System

The Mark V configuration information is imported into the ToolboxST system from the Mark V component so that the
configuration can be stored with the rest of the system components in the Configuration Management System (CMS). This
also allows the Mark V configuration information to be posted to the EGD Configuration Server.
➢ To import the Mark V configuration and publish it to the EGD

6.6.8 Configuring DCS Communication Links (optional)
Communication to a customer's DCS can be provided by the WorkstationST OPC DA server, the WorkstationST Modbus
server, or the WorkstationST GSM server. In the cases of MODBUS and GSM links, the customers often need the data to be
scaled the same way coming from the WorkstationST application as it was coming from a previous system ( or HMI). The
WorkstationST MODBUS and GSM servers support a rescale capability to provide that function. To accomplish this, the
following general steps are done:
• The knowledge of how the information has to be formatted is exported from the present Mark V configuration.
• The required feature (Modbus or GSM) is enabled in the WorkstationST component.
• The information is imported into the ToolboxST application to have the WorkstationST server provide the data in the
correct format.
Typically only one WorkstationST server (Modbus or GSM) needs to be enabled, but there is nothing preventing both from
being enabled at the same time.
➢ To enable and configure the WorkstationST Modbus Server

1. Export the Modbus configuration from the Mark V component.
a. From the Start menu, select Programs, Turbine Control Maintenance, Unit n, and Command Prompt to
open a command prompt window in the Unit Configuration directory.
b. Run the MODBUS_L (MODBUS Listing) program passing it the name of the unit and the Modbus Mode (Signed
16, Unsigned 16...) that is required. If unsure, the customer's previous F:\IO_PORTS.DAT file will indicate the mode
that the previous product was using. Use the same mode for the following MODBUS_L command.
c. Enter the command MODBUS_L /UNIT:<unit> <mode>where <unit> is the unit name and <mode> is the
customer's required mode. (Run MODBUS_L /? for a help screen that shows the available modes.)
d. Verify that the MODBUS.CSV file was created. This contains the formatting information used in the next steps.
2. From the ToolboxST System Editor, select the General tab, double-click the WorkstationST component to display
the Component Editor. Enable the Modbus Feature (if it is not already enabled).

➢ To enable and configure the WorkstationST GSM Server
1. Export the GSM configuration from the Mark V component.
a. From the Start menu, select Turbine Control Maintenance, Unit n, and Command Prompt to open a
command prompt window in the Unit Configuration directory.
b. Run the GSM_L (GSM Listing) program. No parameters are needed unless the default engineering units need to be
overridden.
c. Enter the command GSM_L (Run GSM_L /?) for a help screen that shows the available options.
d. Verify that the GSM.CSV file was created. This contains the formatting information used in the next steps.
2. From the ToolboxST System Editor Tree View double-click the WorkstationST component to display the
Component Editor.

6.6.9 Adding Alarm Help (optional)
The processor and HMI product supported an optional set of Alarm Help files that were used to provide additional help
for process alarms, diagnostic alarms, and Hold Lists. The WorkstationST Alarm Viewer supports the same type of alarm help
information, but uses a very different file structure to store the information. The Help2ST utility is used to create a set of
WorkstationST Alarm Help files from the previous generation alarm help files.
To determine if the previous product used these features look in the Unit Configuration Directory for the following files:
• HELP_QP.DAT or HELP_BP.DAT provides Process Alarm help.

• HELP_QD.DAT or HELP_BD.DAT provides Diagnostic Alarm help.
• HELP_HL.DAT provides Hold help.
The Help Conversion Utility (Help2ST) looks for these files and creates a subdirectory containing equivalent WorkstationST
Alarm Viewer format help files. These files are then moved to the Master workstation defined for the system so they can be
shared by all WorkstationST components.
➢ To convert the Help files

1. From the Start menu, select Programs, Turbine Control Maintenance (ST), Unit <unit>, and Command
Prompt to open a GeCssTci Command Prompt window in the Unit Configuration directory.
2. Run the conversion tool to produce the WorkstationST Alarm Viewer help files.
Tip � Normally no command line parameters are required for help file conversion, but if the site is using dual languages,
and the desired target language is not English, then the language identifier can be specified using the /LANGUAGE:xx
option. Run Help2ST /? for more information on the available command line options.
One of the attributes of the System Definition is the selection of which WorkstationST component is the Master workstation
and what directory on that workstation is the shared directory.
➢ To copy the files to the Master Workstation

1. From the System Definition in the Master Location section of the attributes, locate the Master WorkstationST
attribute (this defines which workstation is the Master Workstation.) The Path attribute shows the location on the Master
Workstation for the shared files.
2. Create a directory under the Master Workstation directory as shown below and copy the contents of the
ProcessAlarms directory there to include Process Alarm Help:
<MasterWorkstationPath>
Help
ProcessAlarms
T1 Where T1 is the WorkstationST name for the Mark V component
xxxxx Where xxxxx is the contents of ProcessAlarms
3. Create a directory under the Master Workstation directory as shown below and copy the contents of the Diagnostics
directory there to include Diagnostic Alarm Help:
Help
Diagnostics
MarkV
T1
xxxxx Where xxxxx is the contents of Diagnostics
4. Create the following directory under the Master Workstation directory and copy the contents of the ProcessAlarms
directory there to include Hold help:

Note This is the same location as the Process Alarms, the WorkstationST Alarm Viewer subsystem does not distinguish
between help for a process alarm created for a variable and help for a hold created from the same variable. If both exist and
are different text you may need to merge the contents of the two files into one file to meet the site requirements. (This is not
likely to happen, but it is possible.)
Help
ProcessAlarms
T1
xxxxx Where xxxxx is the contents of ProcessAlarms
Note Because the Process Alarm and Hold help is determined by the variable name, these help files are still valid after
conversion from a Mark V controller to a Mark Ve controller. The Diagnostic Alarm help files for a Mark V cotnroller are not
used after conversion to a Mark Ve controller.
6.6.10 Adding EX2000 Fault Code Scanning

The EX2000 controller supplies a fault code, an integer value that specifies fault conditions as they are detected. Previous
generations of software used a CIMPLICITY* script to decode this fault code and add an alarm to the CIMPLICITY alarm
queue indicating the fault. The WorkstationST Alarm Server includes a fault code scanner to produce local workstation alarms
based upon the EX2000 fault code, thereby acting as a replacement for the CIMPLICITY script in a CIMPLICITY Advanced
Viewer environment.
The WorkstationST Alarm Server's Fault Code Scanner can be used with any enumerated variable. It periodically scans the
variable for changes and creates an alarm when it detects a change, supplying the alarm text string from an enumeration that
is defined for the scanned signal. The enumeration (at least for the EX2000 scanning) is usually defined at the system level
because most EX2000 controllers share the same definition of the fault codes. For the EX2000 the fault code is typically
transmitted using a Status-S message to the turbine controller, which reads the value into an internal variable. That turbine
controller variable is read by the WorkstationST Alarm Server Fault Code Scanner from the WorkstationST OPC DA server.
➢ To support EX2000 Fault Code Scanning:

1. Create and populate the enumeration that maps the EX2000 fault codes to the desired alarm text strings.
2. Add one entry per EX2000 control to the WorkstationST Alarm Server Fault Code Scanner to scan the value and create
the alarms.
3. Use the Help Conversion utility to create a set of Fault Code help files that are then copied to the Master workstation.

➢ To create the EX2000 enumerations
1. Open the ToolboxST application and the appropriate system (*.tcw) file.
2. From the Tree View, double-click the system item to display the system Component Editor (system definition).
3. From the Tree View, right-click Format Specification Sets and select Add Format Specification Set. The Add
Format Specification Set dialog box displays.
4. Enter the Format Spec Set Description (such as EX2000Fault) and click OK. The new Format Specification
Set displays in the Tree View.
5. From the Tree View, select the new Format Specification Set (EX2000Fault)
6. From the Summary View, enter the appropriate values in the columns, such as:
Name is EX2000_Fault (This is slightly different than the Format Specification Name)
Description is Fault Codes for EX2000
Measurement System is English (or whatever is appropriate for the system definition)
Group, Units, EngMin, EngMax, and Precision can remain blank.
Enumerations enter the mapping of the EX2000 fault codes to the associated fault name and alarm text. This can typically
be obtained from the requisition standards, as there are very few different Fault Code definitions. Make sure the definitions
used match what was in use before the update (the site's existing EX2000.DAT file can be used to identify the correct
enumerations).
7. Save and exit the system definition.

➢ To scan EX2000 fault codes
1. Open the ToolboxST application and the appropriate system (*.tcw) file.
2. From the Tree View, double-click the WorkstationST component to be used for Fault Code Scanning.
3. From the Alarms tab, right-click Fault Code Scanner and select Add Variable. The Select a Variable dialog box
displays.
4. Locate and select the Mark V controller variable (EX_Fault) that contains the EX2000 Fault Code. The variable displays
in the Summary View.
5. From the Summary View, select the scanned variable and in the Format Spec column, enter the Format
Specification that includes the enumeration created in the previous procedure. (In this case EX2000_Fault.)
6. Enter values in the Alarm Class and Severity columns if required.
7. From the Property Editor, in the Fault Code Scanner Configuration section, select Enable and set it to True.
8. Select Scan Rate and enter an appropriate rate. (The rate does not need to be fast, the Mark V interface only updates
this value once per second.)
9. Use the build and download the commands to activate the Fault Code Scanner in the WorkstationST component.
WorkstationST Alarms Tab Screen

6.6.10.1 Converting EX2000 Fault Code Help Files
The previous HMI product used an EX2000.DAT file to match fault codes to alarm help text that could be displayed when
additional information (alarm help) was requested on one of the alarms. The WorkstationST Alarm Viewer supports the same
functionality, but the format of its input files is different. The Mark V Feature provides a help conversion utility that converts
the old format single ASCII file to a set of WorkstationST Alarm Help files. The files are then copied to the Master
workstation to make the information available to all WorkstationST Alarm Viewer clients.
Conversion of the EX2000 fault code help file is similar to conversion of the other types of alarm help (Process Alarm,
Diagnostic Alarm, and Hold Help) and uses the same Help Conversion Utility (Help2ST) to do the conversion. The main
differences for EX2000 fault code help are:
• The source of the data is the EX2000.DAT file

• The conversion utility needs to know the name of the signal that is scanned so that it can bind the resulting help files to
the scanned signal name.
➢ To convert EX2000 Fault Code Help Files

1. Copy the site's existing EX2000.DAT file to the unit configuration directory of the Mark V controller.
2. From the Start menu, select Programs, Turbine Control Maintenance (ST), Unit <unit>and Command Prompt
to open a GeCssTci Command Prompt window in the Unit Configuration directory.
3. Run the conversion tool (Help2ST) with the /EX2000 <variable> option, where <variable> is the name of the Fault Code
signal scanned. The variable name should have the unit name separated from the variable name using an underscore ( _ )
character. (For example, Help2ST /EX2000:T1_EX_FAULT) The set of alarm help files is created in the EX2000
subdirectory.
4. Copy the files to the Master Workstation in the ProcessAlarms section. The WorkstationST application makes a
distinction between help for a process alarm created from a variable and help for an EX2000 Fault Code scanned from
that same variable by adding the fault code as a suffix to the file that displays the help text.
5. Create a directory under the Master Workstation directory as shown below and copy the contents of the EX2000
directory there to include the EX2000 Fault Code help:
Help
ProcessAlarms
T1
xxxxx Where xxxxx is the contents of EX2000

Network Interface Configurations to a ToolboxST* External
Device
The eTCSS software product includes a Network Interface component for defining the EGD interface to a component. The
ControlST* software product includes an External Device for the same purpose. This procedure defines how to take the
existing EGD exchange and variable definitions and import them into the ControlST environment.
This how-to guide consists of three procedures:
• Export the existing definitions using the toolbox application.

• Create and define the target external device using the ToolboxST application.
• Use the ToolboxST Tree File Importer to read the exported information into the target device.
6.7.1 Prerequisites
When upgrading the Data Historian from the toolbox application to the ToolboxST application there are several prerequisites:
• The toolbox application must be version 11.01.01C or newer to support the Export to NextGen feature.
• The ControlST software must be installed.
6.7.2 Exporting Network Interface Files

➢ To export the Network Interface device files from the toolbox application
1. From the toolbox File menu, select Open, browse to locate and select the Network Interface device (Dev1.alb) to be
exported. Click Open to display the device.

Note The Export – All function creates each *.tre and *.prj file for each Network Interface device. Store all the files in a
single directory (typically it defaults to the directory of the original *.alb file).
2. When done, exit the toolbox application.

A copy of the Network Interface configuration is saved to the directory.

6.7.3 Creating the ToolboxST External Device
An External Device must be created in the ToolboxST system to act as the destination for the exported configuration
information.
➢ To create the External Device

1. From the Start menu, select Programs, GE ControlST, ToolboxST, and ToolboxST. The System Editor
displays.

2. Select the new External Device and in the Property Editor set the Enable EGD Editor field to True.
3. From the Tree View, double-click Dev1 to display the Component Editor.
4. From the External Device's toolbar, click the Save button and then close the External Device.
5. Exit the ToolboxST application saving the changes to the system.
The ToolboxST configuration now includes the External Device.

6.7.4 Importing Network Interface Files
The tree file importer is used to import files into the ToolboxST application.
➢ To import the Network Interface files

Note If an error or warning displays from the tree file importer, double-click the error or warning to display a Text File
Editor dialog box that provides the line in the .tre or .prj file that is the cause of the warning.

The Network Interface configuration files have been imported to the External Device (Dev1) component.

➢ To verify the information
1. Open the system (.tcw) file containing the External Device.
2. From the Tree View, double-click Dev1 to display the EGD Component Editor.
3. Select the EGD tab.
If changes are made to the EGD parameters, it may be necessary to manually set the EGD Signature to ensure it matches the
actual device.
➢ To manually set the EGD signature

6.8 How To Test the TMR Capability of the Mark* VI
Control using the Control System Toolbox
The following procedures are used to test the triple modular redundant (TMR) capability of the Mark VI turbine control
system using the Control System Toolbox. This document contains three procedures:
• To prepare for the TMR test

• To run the TMR test
• To run the XYZ protective module test
Testing for TMR capability can cause a trip event since the testing purposely places
the control cabinet into a simplex mode while the controller reboots.
Attention
➢ To prepare for the TMR test
1. Review all standing and intermittent process alarms on the turbine control. Resolve all alarms related to TMR devices
and critical control functions.
2. Review all I/O board standing and intermittent diagnostic alarms on the turbine control. Resolve all alarms related to
TMR devices and critical control functions.
Note If any alarms remain uncleared, print out the alarm queue to document them prior to conducting the TMR test.
3. Go online with each of the three controllers (R, S, and T) in turn to verify that each is running in the control state with
code that is equal to the .m6b file being used.
4. Verify that the historical alarm data is being stored correctly. Mark VI controls store them as .d03 files.
5. Configure the trend for high resolution data according to the recommended list in Appendix A or Appendix B, depending
on turbine type.
6. From the Trend Recorder, start a trend that includes all of the following items:
□ Speed pickups □ IBH valve position commands

□ TMR analog transducers □ Liquid fuel bypass valve commands (if applicable)
□ LVDT inputs □ IGV position commands
□ Exhaust thermocouple values □ Non-voted servo current signals
□ Gas valve position commands □ Non-voted ETR and PTR feedbacks

➢ To run the RST test
1. From the Control Systems Toolbox application (toolbox), select the Device menu and select Online. The Go Online
Note In the Mark VI control, the designated controller letter is displayed in the status bar with a green background. If
another controller is selected, its controller letter is displayed with a yellow background.
2. Proceed in reverse order from the designated controller so the designated controller is tested last, for example:
a. If the designated controller is R (default), then the testing order is T, S, R.
b. If the designated controller is S, then the testing order is R, T, S.
3. If the unit is at Full Speed No-Load (FSNL) or low power, from the Trend Recorder start a trend file on the designated
controller.
Note Run Trender on a controller that is not going to be shutdown. The Trend Recorder pulls data from the controller that
was selected when the Control Systems Toolbox application was put online.
4. Power down the T controller (or the appropriate controller to test as explained in step two) by using the toggle switch on
the rack-mounted power supply. Make sure the unit continues to operate safely. Wait at least 5 minutes to assure that the
system is stable.
If there are any problems during TMR testing, a unit shutdown or trip can occur.
Attention
5. Power on the processor that was just powered off, and use the Control Systems Toolbox application to monitor it until the
controlling state is returned. In the Mark VI control this can be done by checking the controller status box in the lower
right corner of the toolbox status bar.

6. Double-click the controller status box in the lower right corner of the toolbox, and watch the I/O State and the Control
State.
7. Continue to wait for 3 to 5 minutes.

8. After the state returns to Control (IO State = 0x6A, Control State = 0xCA), wait an additional 5 minutes to allow the
process to stabilize before continuing.
It is important to give the controller sufficient time to return to the Control State,
which may take as much as five minutes. If the control state is not achieved, the test
should be stopped. A trip will occur if a second controller is re-booted.
Attention
9. Issue a Master Reset to clear the trip from the protective module.
10. Stop the trend file and save it. Record the file name and then start a new trend file on the designated controller.
11. Repeat steps four though six for the other two controllers in the order described in step two. It will be necessary to go
online with a different controller prior to powering down the final rack (which had been designated).
➢ To run the XYZ protective module test

1. Start a new trend file.
2. Power off the X controller using the toggle switch on the PDM. Make sure the unit continues to operate safely.
If there are any problems during TMR testing, a unit shutdown can occur.
Attention
3. Power on the X controller.
4. Use the Status and Run LEDs on the front of the VPRO board to monitor the controller until it returns to the
controlling state.
5. Verify that, in addition to the normal status LEDs, the Run LED is flashing in unison with the other two controllers,
indicating that they are synchronized. Once this occurs, wait an additional 5 minutes before continuing.
6. Stop the trend file and save it.
7. Repeat steps one through six for the Y and Z controllers.

6.8.1 Trip Event
If a trip event occurs, use the following procedure to save the trip log and the alarm and event files.
➢ To save the trip log, alarm and event (.D03 or WSxxx.bin) files
1. From the desktop, double-click the Alarm And Event Logger to go to the turbine control interface (TCI ) home page.
2. From the TCI screen, select Alarm and Event Report.
3. Enter the appropriate request for all alarm and event information and save the file.
4. From the local HMI directory E:\Historian_Data\HMIDATA\Gn_TripLog Directory, double-click the trip log Gn_
TripLog_YYYYMMDD_HHMMSS.dca file.
5. From the Control Systems Toolbox application, open the trip files to verify the correct trip event. Gn_TripLog_LIVE
stores data at 1-second internals. It can also be used to verify the trip event.
Note Data Historian later than V05.01.17C automatically creates .dca files containing the capture block from the
non-designated processor (there will be no capture block from the controller that was powered off). If the system being tested
is using an older version of Data Historian, perform steps six and seven to extract the capture block from the non-designated
controller.
6. From the Trend Recorder, go online with the non-designated controller.

7. Upload the block collected data, then save it as a trend file.

➢ To determine the root cause of a trip event
1. From the toolbox, review the trip and events log to determine the root cause of a trip event.
2. If the site found any faulty TMR device, fix the issue and document the root cause and resolution as part of the trip
report.
3. If the trip is not due to a faulty TMR device, open a power answer center (PAC) case and attach the trip logs captured
during the test.
The following are examples of root causes:
• In a TMR system, two faults are usually required in combination to produce the root cause of a trip. For example,
loss of an LVDT on one controller can combine with power-off process of a second controller to result in what is
reported as a control valve out-of-position failure. The lurking or hidden fault was the LVDT failure, and it was
revealed when the controller power-off process removed the redundant position feedback. The corrective action in
this example would be to repair the problem with the LVDT. Root cause and corrective action(s) should be included
in the trip report.
• It is possible that I/O used in control code as critical inputs has been terminated in the control as simplex points. If
this is uncovered, a PAC case should be written and sent to the controls requisition engineer. Attachments for the
PAC case should include current Mark VI .m6b file (or an archive copy of the Mark VI file), trend files, trip log,
event file, and the diagnostic alarm file. The PAC case should describe at what point in the TMR testing the trip
occurred. It should include a description of the specific sequence of events leading up to the trip.
Note These tools are also available to GE employees on the Support Central Mark VI Turbine Controls Community (ID
number 2892) under Quick Tips/Tools/Mark VI Remote Diagnostics Distribution.
• When a controller fault has caused a trip as indicated by the Root Cause Analysis (RCA), capture the Mark VI diagnostic
alarms from each VCMI board and save them as files. The log files should be included in the PAC case. If an on-site
monitor (OSM) is accessible on the local web page, then the program WD_VIDA.EXE can be used to automate collecting
the diagnostic alarms from all the I/O boards. The program is run from command line: WD_
VIDA/NODE:192.168.101.111>REPORT.HTM, where the IP address is specific to the controller under test.
The OSM web diagnostic program can take 4 to 10 minutes to run. The user should be
familiar with how to run it before using it.
Attention

6.8.2 Appendix A Trend List for 7FA Gas Turbines
The list will vary by frame size and fuel system.
Trend List for 7FA Gas Turbines

Signal Name Description Signal Name Description
G1\TNH Turbine HP shaft speed in % G1\TTXD1_14 Exhaust Thermocouple 14 -
Compensated
G1\TTXD1_1 Exhaust Thermocouple 1- G1\TTXD1_15 Exhaust Thermocouple 15 -













Note Add or remove thermocouples based on frame size.

Trend List for 7FA Gas Turbines (continued)

G1\TTXM Exhaust Temp Median Corrected By G1\FALNSC LCV Null Bias Compensation
Average
G1\TTXSP1 Combustion Monitor Actual Spread 1 G1\L3LFLT Liquid Fuel Control Fault
G1\TTXSP2 Combustion Monitor Actual Spread 2
G1\TTXSP3 Combustion Monitor Actual Spread 3 G1\csrihout Inlet Heating Control Valve Command
G1\TTXSPL Combustion Monitor Allowable G1\csbhx Inlet Heating Control Valve Position
Spread
G1\FSR Fuel Stroke Reference G1\AA_PRS_ABS AA Manifold Pressure In PSIA
G1\csbhx Inlet Heating Control Valve Position
G1\fpg1 Fuel Gas Inlet Pressure Transducer G1\AFPEPX Exhaust Duct Pressure
G1\FQG Gas Fuel Flow G1\BB_MAX Maximum vibration
G1\FPG2 Interstage fuel gas press G1\CPD Compressor Discharge Press Max
Select
G1\fpg2a Interstage fuel gas press xmitter G1\cpd1a Compressor Discharge Press Transd.
96FG-2A 96CD-1
G1\fpg2b Interstage fuel gas press xmitter G1\cpd1b Compressor Discharge Press Transd.
96FG-2B 96CD-1B
G1\fpg2c Interstage fuel gas press xmitter G1\cpd1c Compressor Discharge Press Transd.
96FG-2C 96CD-1C
G1\CPRLIM COMPRESSOR PRESSURE RATIO
OPERATING LIMIT
G1\frcrout Fuel Gas Speed Ratio Servo G1\CPRLIMN Compressor Map - New
Command
G1\fsgr Position fdbck srv (high value G1\ctda1 Compressor Discharge Thermocouple
selected) #1
G1\fagr Cur Speed ratio valve servo current G1\ctda2 Compressor Discharge Thermocouple
#2
G1\FAGR_NVR SRV Non-Voted Servo Current G1\ctda3 Compressor Discharge Thermocouple
Feedback from <R> #3
G1\FAGR_NVS SRV Non-Voted Servo Current G1\ctif1a Compressor Inlet Thermocouple 1A
Feedback from <S>
G1\FAGR_NVT SRV Non-Voted Servo Current G1\ctif1b Compressor Inlet Thermocouple 1B
Feedback from <T>
G1\L3GFIVP GAS FUEL INTERVALVE G1\ctif2a Compressor Inlet Thermocouple 2A
PRESSURE TROUBLE
G1\L3GFLT Fuel Gas Control Fault G1\DESIGNATED Designated Controller Status


G1\L3GRVAX Stop/Speed Ratio valve position error G1\DLN_MODE DLN Mode Enumerated State
alarm
G1\L3GRVFLT GAS RATIO VALVE POSITION G1\dv Generator Volts - VTUR
SERVO TROUBLE
G1\L3GRVGLT SRV Position Enable for Gas Leak G1\dvar Generator VARS
Test
G1\L3GRVT Stop/Speed Ratio valve position error G1\DWATT Generator Watts Max Selected
trip G1\fd_intens_1 PRIMARY FLAME DETECTOR #1
FLAME INTENSITY
G1\fsrg1out PM1 Gas Control Valve Servo G1\fd_intens_2 PRIMARY FLAME DETECTOR #2
Command FLAME INTENSITY
G1\FSGPM1 PM1 GCV Position Feedback, same G1\fd_intens_3 PRIMARY FLAME DETECTOR #3
as fsg1 FLAME INTENSITY
G1\FAGPM1 PM1 GCV Current Feedback, same G1\fd_intens_4 PRIMARY FLAME DETECTOR #4
as fag1 FLAME INTENSITY
G1\FAG1_NVR PM1 GCV Non-Voted Servo Current G1\FSRMIN FSR: Minimum

Feedback from <R>
G1\FAG1_NVS PM1 GCV Non-Voted Servo Current G1\FTG Fuel gas temperature
Feedback from <S>
G1\FAG1_NVT PM1 GCV Non-Voted Servo Current G1\h2gp Generator Gas Pressure Transmitter
Feedback from<T>
G1\FAG1NSC GCV 1 Null Bias Compensation G1\L12H Turbine electrical overspeed trip signal
G1\L3GCV1A GCV1 Not Following Reference G1\L12H_ACC VPRO - Loss Of Protective Speed
Signal
G1\L3GCV1FB GCV1 Position Feedback Fault G1\L12H_FLT Loss of Protective HP Speed Inputs
G1\L3GCV1FLT GCV1 SERVO TROUBLE G1\L12H_P VPRO HP Overspeed Trip
G1\L3GCV1O GCV1 Open Trouble Alarm Logic G1\L12HF Loss Of Control Speed Signal
G1\L3GCV1SC GCV1 Servo Current Fault G1\L20FGX Gas Fuel Stop Valve Command, same
as l20fg1x
G1\L20FLX Liquid Fuel Stop Valve Control Signal,

same as l20fl1x
G1\fsrg2out PM2 Gas Control Valve Servo G1\L28FDX Flame detection control
Command


G1\FSGPM2 PM2 GCV Position Feedback, same G1\L3 Turbine complete sequence
as fsg2
G1\FAGPM2 PM2 GCV Current Feedback, same G1\L30FORCED_ SIGNAL FORCING ENABLED
as fag2 AL
G1\FAG2_NVR PM2 GCV Non-Voted Servo Current G1\l33cb1o COMPRESSOR BLEED VALVE #1
Feedback from <R> OPEN
G1\FAG2_NVS PM2 GCV Non-Voted Servo Current G1\l33cb2o COMPRESSOR BLEED VALVE #2
Feedback from <S> OPEN
G1\FAG2_NVT PM2 GCV Non-Voted Servo Current G1\l33cb3o COMPRESSOR BLEED VALVE #3
Feedback from <T> OPEN
G1\FAG2NSC GCV 2 Null Bias Compensation G1\l33cb4o COMPRESSOR BLEED VALVE #4
OPEN
G1\L3GCV2A GCV2 Not Following Reference G1\l33cb5c Compressor Bleed Valve #1 Closed
G1\L3GCV2FB GCV2 Position Feedback Fault G1\l33cb6c Compressor Bleed Valve #2 Closed
G1\L3GCV2O GCV2 Open Trouble Alarm Logic G1\l33cb7c Compressor Bleed Valve #3 closed
G1\L3GCV2SC GCV2 Servo Current Fault G1\l33cb8c Compressor Bleed Valve #4 Closed
G1\L3_STATE_EX1 State Exchange 1 OK
G1\fsrg3out PM3 Gas Control Valve Servo G1\L3_STATE_EX2 State Exchange 2 OK

Command
G1\FSGPM3 PM3 GCV Position Feedback, same G1\L3_STATE_EX3 State Exchange 3 OK
as fsg3
G1\FAGPM3 PM3 GCV Current Feedback, same G1\L3SFLT CONTROL SYSTEM FAULT TRIP
as fag3
G1\FAG3_NVR PM3 GCV Non-Voted Servo Current G1\L4 Master Protective

Feedback from <R>
G1\FAG3_NVS PM3 GCV Non-Voted Servo Current G1\L4T Master Protective Trip
Feedback from <S>
G1\FAG3_NVT PM3 GCV Non-Voted Servo Current G1\L4IGVT INLET GUIDE VANE CONTROL
Feedback from <T> TROUBLE TRIP
G1\FAG3NSC GCV 3 Null Bias Compensation G1\L4POST Post-Ignition Trip
G1\L3GCV3A GCV3 Not Following Reference G1\L4POSTX Post-Ignition Trip Auxiliary Signal
G1\L3GCV3FB GCV3 Position Feedback Fault G1\L4PRET Pre-Ignition Trip
G1\L3GCV3O GCV3 Open Trouble Alarm Logic G1\L4PSTX1 Protective Status Trip Logic 1


G1\L3GCV3SC GCV3 Servo Current Fault G1\L4PSTX2 Protective Status Trip Logic 2
G1\L4PSTX3 Protective Status Trip Logic 3
G1\fsrg4out Gas Quaternary Valve Servo G1\L4PSTX4 Protective Status Trip Logic 4
Command
G1\FSGQ PM4 GCV Position Feedback, same G1\L4T_LTH_ALM LUBE OIL HEADER TEMP HI TRIP
as fsg4
G1\FAGQ PM4 GCV Current Feedback, same G1\L52GX Generator Breaker Close/Open Status
as fag4 Input
G1\FAG4_NVR Quat GCV Non-Voted Servo Current G1\L5CMPST_TRP VPRO - Composite Trip(s)
Feedback from <R>
G1\FAG4_NVS Quat GCV Non-Voted Servo Current G1\L5CMPST_ VPRO - Composite Trip
Feedback from <S> TRP1
G1\FAG4_NVT Quat GCV Non-Voted Servo Current G1\L63ETH_ALM EXHAUST DUCT PRESSURE HIGH
Feedback from <T> TRIP
G1\FAG4NSC GCV 4 Null Bias Compensation G1\L63HGL REDUNDANT SENSORS GAS FUEL
HYD PRESS LOW TRIP
G1\l63qt2a Lube Oil Header Pressure Switch A -
Low Press Trip
G1\csrgv IGV REFERENCE G1\l63qt2b Lube Oil Header Pressure Switch B -

Low Press Trip
G1\csgv IGV angle in deg G1\L86FPG2HT_A POST-IGNITION P2 HIGH TRIP
G1\cagv IGV control servo current G1\L86FPG2LT_A POST-IGNITION P2 LOW TRIP
G1\CAGV_NVR IGV Non-Voted Servo Current G1\L86GCV1T GCV1 Not Following Reference Trip
Feedback from <R>
G1\CAGV_NVS IGV Non-Voted Servo Current G1\L86GCV2T GCV2 Not Following Reference Trip
Feedback from <S>
G1\CAGV_NVT IGV Non-Voted Servo Current G1\L86GCV3T GCV3 Not Following Reference Trip
Feedback from <T>
G1\L3GCVQA Quaternary Valve Not Following G1\L86GCVQT Quaternary Valve Not Following
Reference Reference Trip
G1\L3GCVQFB Quaternary Valve Position Feedback G1\L86GVT IGV Not Following CSRGV Trip
Fault
G1\L3GCVQO Quaternary Valve Open Trouble Alarm G1\L86TFB_ALM EXHAUST THERMOCOUPLES OPEN
Logic TRIP
G1\L3GCVQSC Quaternary Valve Servo Current Fault G1\l86tt GSU Transformer Lockout Trip


G1\L3IGVFLT_ IGV POSITION SERVO FAULT G1\L86TXT Exhaust Overtemperature Trip
ALM Generator and GSU Transformer
G1\l86u Lockout Trip
G1\FQR Liquid Fuel Flow Reference G1\l89sso Static Starter Disconnect Switch Open
G1\fal Liquid Fuel Bypass Valve Servo G1\L94FIL FAILURE TO IGNITE ON OIL -TRIP
Current
G1\FAL_NVR Liq Fuel Bypass Non-Voted Servo G1\STAT_R <R> UCVx Controller State
Current from <R>
G1\FAL_NVS Liq Fuel Bypass Non-Voted Servo G1\STAT_S <S> UCVx Controller State
Current from <S>
G1\FAL_NVT Liq Fuel Bypass Non-Voted Servo G1\STAT_T <T> UCVx Controller State
Current from <T>
6.8.3 Appendix B Trend List for D11 Steam Turbines

The list will vary for other steam turbines. Variables in these trend lists may or may not exist.
Trend List for D11 Steam Turbines, Admission Control Valve Variables
S1\ACV Admission Control Valve Reference S1\ap2 Admission Steam Pressure #2
S1\acv1_out Admission control valve servo output S1\ap3 Admission Steam Pressure #3
S1\ACV1_OUT_ S1\APC Admission Pressure Control Reference
S1\acv1_out_cur Admission Control Valve Servo S1\APC_COMP Admission Pressure Control Speed
Current Compensation
S1\acv1_pos Admission control valve position S1\APC_COMP1 Admission Pressure Control Speed
feedback #1 Compensation
S1\ACV1_ Linearized Flow Reference for ACV S1\APL Admission Pressure Limiter Reference
STROKE
S1\AFLR Admission Flow Setpoint S1\APR Admission Pressure Setpoint
S1\AP Admission Pressure Feedback S1\APR_P Admission Pressure Setpoint
S1\ap1 Admission Steam Pressure #1

Trend List for D11 Steam Turbines, Generator RTD Variables
S1\dtgac23 Generator Collector - Cold Air S1\dtgsa4 Generator Temp - Stator Collector End
Temperature
S1\dtgah17 Generator Collector - Hot Air S1\dtgsa5 Generator Temp - Stator Collector End
Temperature
S1\dtggc10 Generator Temp - Cold Gas Coupling S1\dtgsa6 Generator Temp - Stator Collector End
End
S1\dtggc11 Generator Temp - Cold Gas Collector S1\dtgsc7 Generator Temp - Stator Center
End
S1\dtggc12 Generator Temp - Cold Gas Collector S1\dtgsc8 Generator Temp - Stator Center
End #2
S1\dtggc13 Generator Temp - Cold Gas Turbine S1\dtgsc9 Generator Temp - Stator Center
End #2
S1\dtggh28 Generator Temp - Hot Gas S1\dtgsf1 Generator Temp - Stator Coupling End
S1\dtggh29 Generator Temp - Hot Gas S1\dtgsf2 Generator Temp - Stator Coupling End
S1\dtggk24 Generator Frame - Common Cold S1\dtgsf3 Generator Temp - Stator Coupling End
Gas
Trend List for D11 Steam Turbines

S1\l201srcv_c 1st Stage RH Cooling Valve Soln S1\L26GSCF STATOR CENTER RTD OUT OF LIMIT
(Energ to Close) FAILURE
S1\l20bpt Bearing Oil Pump Test Solenoid S1\L26GSEXHA GLAND SEAL EXHAUST
TEMPERATURE HIGH
S1\l20cv1_qc CV1 Quick Close Solenoid (FASV) S1\L26GSFF STATOR CPLG END RTD OUT OF
LIMIT FAILURE
S1\l20cv2_qc CV2 Quick Close Solenoid (FASV) S1\L26JBS1A JOURNAL BEARING #1 TEMP HIGH
PRE-ALARM
S1\l20ebpt Emergency Bearing Oil Pump Test S1\L26JBS1HA JOURNAL BEARING #1 TEMP HIGH
Solenoid ALARM
S1\l20eqv1 Equalizer Valve #1 Solenoid S1\L26JBS2A JOURNAL BEARING #2 TEMP HIGH
PRE-ALARM
S1\l20eqv2 Equalizer Valve #2 Solenoid S1\L26JBS2HA JOURNAL BEARING #2 TEMP HIGH
ALARM
S1\l20iv1_qc IV1 Quick Close Solenoid (FASV) S1\L26JBS3A JOURNAL BEARING #3 TEMP HIGH
PRE-ALARM
S1\l20iv2_qc IV2 Quick Close Solenoid (FASV) S1\L26JBS3HA JOURNAL BEARING #3 TEMP HIGH
ALARM
S1\l20msv1dt Main Stop Valve #1 Dump Test S1\L26JBS4A JOURNAL BEARING #4 TEMP HIGH
Solenoid PRE-ALARM

Trend List for D11 Steam Turbines (continued)

S1\l20msv2dt Main Stop Valve #2 Dump Test S1\L26JBS4HA JOURNAL BEARING #4 TEMP
Solenoid HIGH ALARM
S1\l20rsv1dt Reheat Stop Valve #1 Dump Test S1\L26JBS5A JOURNAL BEARING #5 TEMP
Solenoid HIGH PRE-ALARM
S1\l20rsv2dt Reheat Stop Valve #2 Dump Test S1\L26JBS5HA JOURNAL BEARING #5 TEMP
Solenoid HIGH ALARM
S1\L26G1DA BEARING #1 OIL DRAIN S1\L26JBS6A JOURNAL BEARING #6 TEMP
TEMPERATURE HIGH HIGH PRE-ALARM
S1\L26G2DA BEARING #2 OIL DRAIN S1\L26JBS6HA JOURNAL BEARING #6 TEMP
TEMPERATURE HIGH HIGH ALARM
S1\L26G3DA BEARING #3 OIL DRAIN S1\L26L1SLS_DIF L-1 STAGE STEAM
TEMPERATURE HIGH TEMPERATURE DIFF
S1\L26G4DA BEARING #4 OIL DRAIN S1\L26L1SLSA L-1 STAGE STEAM
TEMPERATURE HIGH TEMPERATURE HIGH
S1\L26G5DA BEARING #5 OIL DRAIN S1\L26L1SLST L-1 STAGE STEAM
TEMPERATURE HIGH TEMPERATURE TRIP
S1\L26G6DA BEARING #6 OIL DRAIN S1\L26TBFA TB MONITOR-NORM MAX FRONT
TEMPERATURE HIGH TEMP PRE-ALARM
S1\L26GAC23_ GENERATOR COLLECTOR INLET S1\L26TBFDA TB MONITOR-FRONT DIFF TEMP
ALM HIGH TEMP PRE-ALARM
S1\L26GAC23_HI RTD DT-GAC-23 Failed High S1\L26TBFDHA TB MONITOR-FRONT DIFF TEMP
ALARM
S1\L26GAC23_LO RTD DT-GAC-23 Failed Low S1\L26TBFHA TB MONITOR-NORM MAX FRONT
TEMP ALARM
S1\L26GAH17_ GENERATOR COLLECTOR S1\L26TBRA TB MONITOR-NORM MAX REAR
ALM OUTLET HIGH TEMP TEMP PRE-ALARM
S1\L26GAH17_HI RTD DT-GAH-17 Failed High S1\L26TBRDA TB MONITOR-REAR DIFF TEMP
PRE-ALARM
S1\L26GAH17_LO RTD DT-GAH-17 Failed Low S1\L26TBRDHA TB MONITOR-REAR DIFF TEMP
ALARM
S1\L26GGCA GENERATOR COLD GAS S1\L26TBRHA TB MONITOR-NORM MAX REAR
TEMPERATURE HIGH TEMP ALARM
S1\L26GGCF GEN COLD GAS RTD OUT OF S1\L30EQV1 LEFT EQUALIZER VALVE
LIMIT FAILURE TROUBLE
S1\L26GGCS GEN COLD GAS HIGH S1\L30EQV2 RIGHT EQUALIZER VALVE
TEMPERATURE SPREAD TROUBLE
S1\L26GGFA GENETATOR RTD FAILURE S1\L30WD1S_SPD WATER DETECT STG 01 TEMP
DETECTED SPREAD EXCEEDED
S1\L26GGFH_ALM GENERATOR RTD HIGH FAILURE S1\L30WDHPEX_ WATER DETECT HP EXHAUST
DETECTED SD TEMP SPREAD EXCEEDED
S1\L26GGFL_ALM GENERATOR RTD LOW FAILURE S1\L30WDRHB_ WATER DETECT RH BOWL TEMP
DETECTED SPD SPREAD EXCEEDED


S1\L26GGHA GENERATOR HOT GAS S1\bb1x Vibration 1X - Bearing #1
TEMPERATURE HIGH
S1\L26GGHF GEN HOT GAS RTD OUT OF LIMIT S1\bb1y Vibration 1Y - Bearing #1
FAILURE
S1\L26GGK24_HI RTD DT-GGK-24 Failed High S1\bb2x Vibration 2X - Bearing #2
S1\L26GGK24_LO RTD DT-GGK-24 Failed Low S1\bb2y Vibration 2Y - Bearing #2
S1\L26GGK_ALM GEN FRAME COMMON COLD GAS S1\bb3x Vibration 3X - Bearing #3

HIGH TEMP
S1\l26gms Generator Overheating Alarm (Core S1\bb3y Vibration 3Y - Bearing #3
Monitor)
S1\L26GSA1 STATOR TEMP TOO HIGH (1 Or More S1\bb4x Vibration 4X - Bearing #4

RTDs)
S1\L26GSA2 STATOR TEMP TOO HIGH (2 Or More S1\bb4y Vibration 4Y - Bearing #4

RTDs)
S1\L26GSAF STATOR COLL END RTD OUT OF S1\bb5x Vibration 5X - Bearing #5

LIMIT FAILURE
S1\L30WDS18 WATER DETECTION STAGE 18 TC S1\L12HA PRIMARY OVERSPEED TRIP
FAILURE
S1\L30WDS18_ WATER DETECT STG 18 TEMP S1\L12HA_P EMERGENCY OVERSPEED TRIP
SPD SPREAD EXCEEDED
S1\L31SB_TCF1 Water Detection 1st Stage Bowl TC S1\L14H_ZE VPRO HP Zero Speed
Failure 1
S1\L31SB_TCF2 Water Detection 1st Stage Bowl TC S1\l20msv1t Main Stop Valve #1 Test Solenoid
Failure 2
S1\l63hqt_l2 Hydraulic Fluid Pressure Low Trip 2 - S1\l20msv2t Main Stop Valve #2 Test Solenoid
Open to Trip
S1\l63hqt_l3 Hydraulic Fluid Pressure Low Trip 3 - S1\L20PTR1 TRPG Trip Card Relay Driver 1
Open to Trip (PTR #1)
S1\l71qt_l Lube Oil Level Low Trip - Open to Trip S1\L20PTR2 TRPG Trip Card Relay Driver 2
(PTR #2)
S1\l71qt_l2 Lube Oil Level Low Trip 2 - Open to S1\L20PTR3 TRPG Trip card Relay Driver 3 (PTR
Trip #3)
S1\l71qt_l3 Lube Oil Level Low Trip 3 - Open to S1\l20rsv1t Reheat Stop Valve #1 Test Solenoid
Trip
S1\axial1 Axial Position #1 S1\l20rsv2t Reheat Stop Valve #2 Test Solenoid
S1\axial2 Axial Position #2 S1\L25_BYPASS Synch Bypass
S1\axial3 Axial Position #3 S1\L25_ Breaker Close Command Issued -

COMMAND VTUR


S1\bb5y Vibration 5Y - Bearing #5 S1\L25P Synch Permissive Relay Driver
S1\bb6x Vibration 6X - Bearing #6 S1\L25PX Synch Permissive (25P)
S1\bb6y Vibration 6Y - Bearing #6 S1\L25X_PERM Synch Check Permissive (25X)
S1\bhdr Bearing Header Pressure S1\L26CTH_ALM CONTROL PANEL TEMPERATURE

HIGH
S1\C_GEN Generator Control Mode Feedback S1\L26EXHA HIGH EXHAUST TEMPERATURE
ALARM
S1\C_MODE Control Mode Feedback S1\L26EXHT HIGH EXHAUST TEMPERATURE
TRIP
S1\C_MW Megawatt Control Mode Feedback S1\L26G1MA BEARING #1 METAL TEMPERATURE
HIGH
S1\crhp1 Cold Reheat Pressure #1 S1\L26G1MT BEARING #1 METAL TEMPERATURE
HIGH HIGH
S1\CRHP1_P Cold Reheat Steam Pressure #1 (in S1\L26G2MA BEARING #2 METAL TEMPERATURE
psi) HIGH
S1\crhp2 Cold Reheat Pressure #2 S1\L26G2MT BEARING #2 METAL TEMPERATURE

HIGH HIGH
S1\CRHP2_P Cold Reheat Steam Pressure #2 (in S1\L26G3MA BEARING #3 METAL TEMPERATURE
psi) HIGH
S1\cv1_out CV1 Inlet Control Valve Servo S1\L26G3MT BEARING #3 METAL TEMPERATURE
HIGH HIGH
S1\cv1_out_cur CV1 Inlet Control Valve Servo Current S1\L26G4MA BEARING #4 METAL TEMPERATURE
HIGH
S1\cv1_pos Control Valve #1 Position Feedback S1\L26G4MT BEARING #4 METAL TEMPERATURE
HIGH HIGH
S1\CV1_ CV1 Characterized Flow Reference S1\L26G5MA BEARING #5 METAL TEMPERATURE
STROKE HIGH
S1\cv2_out CV2 Inlet Control Valve Servo S1\L26G5MT BEARING #5 METAL TEMPERATURE
HIGH HIGH
S1\cv2_out_cur CV2 Inlet Control Valve Servo Current S1\L26G6MA BEARING #6 METAL TEMPERATURE
HIGH
S1\cv2_pos Control Valve #2 Position Feedback S1\L26G6MT BEARING #6 METAL TEMPERATURE
HIGH HIGH
S1\CV2_ CV2 Characterized Flow Reference S1\L26HPEXA HP EXHAUST TEMPERATURE HIGH
STROKE


S1\CVR_VPL Control Valve Reference - Valve S1\L26HPEXT HP EXHAUST TEMPERATURE HIGH
Position Limit TRIP
S1\CVR_VPL_ VPL Control Correction CVR S1\L26HYDA HYDRAULIC OIL RESERVOIR TEMP
CTL HIGH
S1\DESIGNATED Designated Controller Status S1\L26IS_H_OK Inlet Steam Temperature Below High
Limit
S1\DEX_HP HP Differential Expansion in Percent S1\L26IS_L_OK Inlet Steam Temperature Above Low
Limit
S1\DEX_RH RH Differential Expansion in Percent S1\L26LOCOHA LUBE OIL OUTLET TEMPERATURE
HIGH
S1\DEXROC_HP HP Differential Expansion Rate of S1\L26LOCOHT LUBE OIL OUTLET TEMPERATURE
Change HIGH HIGH
S1\DEXROC_RH RH Differential Expansion Rate of S1\L26SS_HLA Stm Seal Temp Above Allow Limit (25%
Change < MW < 75% Rated)
S1\DIFF_EXP1 Diff Expansion #1 S1\L26SS_LLA Stm Seal Temp Below Allow Limit (25%
< MW <75% Rated)
S1\diff_exp1a Differential Expansion Probe #1 S1\L26SSHA Stm Seal Temp is Above Allow Limit
(MW < 25% Rated)
S1\DMWR Generator MW Control Reference S1\L26SSLA Stm Seal Temp is Below Allow Limit
(MW < 25% Rated)
S1\DPF Generator Power Factor (Calculated) S1\L26TADA ACTIVE THRUST BEARING OIL
TEMP HIGH
S1\DPFM Generator Power Factor Modified S1\L26TAMA THRUST BEARING ACTIVE METAL
TEMP HIGH
S1\DRPFM Generator Power Factor Control S1\L26TAMT THRUST BRG ACTIVE METAL TEMP
Reference Modified HIGH HIGH
S1\DRVAR Generator Var Control Reference S1\L26TIDA INACTIVE THRUST BEARING OIL
TEMP HIGH
S1\dv Generator Volts S1\L26TIMA THRUST BEARING INACTIVE METAL
TEMP HIGH
S1\DV_VPRO Generator Volts from VPRO S1\L26TIMT THRUST BRG INACTIVE METAL
TEMP HIGH HIGH
S1\dvar Generator Vars S1\L27AC_DC1A INCOMING AC #1 POWER LOST
S1\dwatt Generator Watts S1\L27AC_DC2A INCOMING AC #2 POWER LOST
S1\eccentricity Eccentricity S1\L27BATTA INCOMING BATTERY POWER LOST


S1\EHT_PCT Exhaust Temperature in Percent S1\L27DZ 125VDC Undervoltage
S1\ev_p1 Exhaust Vacuum #1 S1\L27DZA 125VDC UNDERVOLTAGE
S1\ev_p2 Exhaust Vacuum #2 S1\L2ETD12_2DO Sequence - Time to Drop Out Second

ETD (#2)
S1\ev_p3 Exhaust Vacuum #3 S1\L2ETD23_3DO Sequence - Time to Drop Out Second

ETD (#3)
S1\fsp First Stage Shell Pressure S1\L2ETD31_1DO Sequence - Time to Drop Out Second
ETD (#1)
S1\hrhp1 Hot Reheat Steam Pressure #1 S1\L2ETDT_TO ETD Test Time Out
S1\hrhp2 Hot Reheat Steam Pressure #2 S1\L2P1 Voltage Matching Pulsing Timer
S1\hrhp3 Hot Reheat Steam Pressure #3 S1\L2P2 Voltage Adjust Pulse Off TIme
S1\hyd Hydraulic Fluid Pressure S1\L2PTR1_RE Seq - ETD has Tripped for x Seconds
S1\IP Inlet Pressure S1\L2PTR1_REX Sequence - ETD #1 Resetting
S1\ip1 Inlet Steam Pressure #1 S1\L2PTR2_RE Seq - ETD has Tripped for x Seconds
S1\ip2 Inlet Steam Pressure #2 S1\L2PTR2_REX Sequence - ETD #2 Resetting
S1\ip3 Inlet Steam Pressure #3 S1\L2PTR3_RE Seq - ETD has Tripped for x Seconds
S1\IP_P Inlet Pressure Feedback S1\L2PTR3_REX Sequence - ETD #3 Resetting
S1\IPC IPC Control Reference S1\L2S Synch Check Relay (25X) Permissive
S1\IPL_FL Inlet Pressure Fixed Level Limit S1\L30AXA AXIAL POSITION HIGH - ACTIVE
Reference
S1\IPL_L Inlet Pressure Limiter Low Limit S1\L30AXAT AXIAL POSITION TRIP - ACTIVE
S1\IPL_RS IPL Rate Sensitive Control Reference S1\L30AXI AXIAL POSITION HIGH - INACTIVE
S1\iv1_out Intercept Valve #1 Servo S1\L30AXIT AXIAL POSITION TRIP - INACTIVE
S1\iv1_out_cur Intercept Valve #1 Servo Current S1\L30COMM_IO_ VCMI IO STATE EXCHANGE FOR <R>
R FAILED
S1\iv1_pos Intercept Valve #1 Position Feedback S1\L30COMM_IO_ VCMI IO STATE EXCHANGE FOR <S>
S FAILED
S1\IV1_ IV1 Characterized Flow Reference S1\L30COMM_IO_ VCMI IO STATE EXCHANGE FOR
STROKE T <T> FAILED


S1\iv2_out Intercept Valve #2 Servo S1\L30ETD12_FA UNEXPECTED TRIP - PROBLEM
W/ETD 1 OR 2
S1\iv2_out_cur Intercept Valve #2 Servo Current S1\L30ETD23_FA UNEXPECTED TRIP - PROBLEM
W/ETD 2 OR 3
S1\iv2_pos Intercept Valve #2 Position S1\L30ETD31_FA UNEXPECTED TRIP - PROBLEM
Feedback W/ETD 3 OR 1
S1\IV2_STROKE IV2 Characterized Flow Reference S1\L4 Turbine Reset
S1\IVR Intercept Valve Reference S1\l52g Generator Breaker Feedback (Direct)
S1\IVR1 IV Reference for Normal Control S1\L5E MANUAL TRIP Circuit Activated
S1\IVR2 IV Reference Modified for Bypass S1\l5e_stc EMERGENCY TRIP PB FROM STC
S1\IVR3 IV Reference Intermediate S1\L63EVT EXHAUST VACUUM TRIP

S1\L10PLU_R PLU Event Input - Ld Ref Rate S1\L63HQET EMERGENCY TRIP HEADER
Select TRIPPED
S1\L12H Primary Overspeed Latch Trip S1\L63HQLT HYDRAULIC FLUID PRESSURE LOW
TRIP
S1\L12H1 Selected Overspeed Setpoint S1\L63QLT LUBE OIL PRESSURE LOW TRIP
Exceeded
S1\L12H_ACC_ HP ACCEL/DECEL RATE TOO S1\l63qt_l2 Lube Oil Pressure Low Trip 2 - Open to
DEC HIGH Trip
S1\L12H_P VPRO HP Overspeed Trip S1\l63qt_l3 Lube Oil Pressure Low Trip 3 - Open to
Trip

7 Miscellaneous Procedures
7.1 How to Verify Software File Integrity
The goal of software integrity verification is to ensure that what you receive is exactly what was sent from the software
vendor and has not been modified. GE’s Automation & Controls has been continuously improving our software integrity
verification tools, first using .hash files, then product signing, and now expanding our signing capability and ease-of-use
using PowerShell scripting. This document provides a history of improvement tools and the procedures to verify software file
integrity using each tool.
7.1.1 History of Software File Integrity Verification Improvement Tools

Power Script Product Signing (Releases Dec 2015 and Later)
Beginning in December 2015, GE’s Automation & Controls added a layer of PowerShell scripting to our deliveries. This
provides a consistent interface to our integrity checking mechanisms and allows us to sign any file or a collection of files
(rather than just files that are typically signed, such as .exe and .msi files). This applies to all deliveries, from full ControlST*
release, to ControlST components, as well as collections of documentation and other products.
The basic procedure is as follows:
1. Verify the signature of the PowerShell script, Verify-Integrity.ps1, to confirm that the script itself has not been modified.
2. Run the script to verify all content and files associated with the script.
Refer to the section PowerShell Script Product Signing File Integrity Verification Procedures (Releases Dec 2015 and Later).
Product Signing (Releases Sept 2015 through Dec 2015)

Beginning in September 2015, ControlST release deployment files (Setup.exe, *.msi) have been signed by GE. This means
GE's Automation & Controls has created an SHA-256 hash of the contents, and encrypted that hash using a Private Key. If
you use GE's Automation & Controls’ Public Key (also obtained through the certificate shipped with the file), then you know
the file came from GE's Automation & Controls and has not been modified.
Refer to the section Product Signing File Integrity Verification Procedures (Releases Sept 2015 through Dec 2015).
Hash File Checking (Releases Prior to Sept 2015)

Previously, GE's Automation & Controls created an SHA-256 hash of the deployment files and made that available out of
band for checking against the file contents. There was no way to ensure that the hashes were as delivered by GE, other than
the fact that you downloaded the files from GE’s Automation & Controls’s website.
Refer to the section Hash File Integrity Verification Procedures (Releases Prior to Sept 2015).
7.1.2 Computer Requirements

Users are required to run Windows® 7 or later to use these instructions.
Note Windows operating systems prior to Windows 7 do not support the PowerShell feature.
Miscellaneous Procedures GEH-6808N Instruction Guide 447

7.1.3 PowerShell Script Product Signing File Integrity Verification
Procedures (Releases Dec 2015 and Later)
7.1.3.1 Normal Operation

During normal operation, perform the following verification procedures:
1. Verify that the Verify-Integrity.ps1 script is signed and trusted.
2. Open a Command prompt and enter the PowerShell console using the command PowerShell.
3. Set the execution policy using the command Set-ExecutionPolicy RemoteSigned –Scope CurrentUser.
Note GE Intelligent Platforms has been renamed as the Automation & Controls group within GE Energy Management;
However, product signing will display GE Intelligent Platforms until we renew our Symantec certificate. This does not affect
the integrity of the software.
Note Windows can run PowerShell scripts using the current Windows account. It verifies the product in its own directory
and the user does not need to have the default directory be that directory.
➢ To verify the signature on the script

1. From Windows Explorer, navigate to the folder containing the Verify-Integrity.psi file.
2. Right-click the file and select Properties.
3. View the Digital Signature information and verify the digital signature is OK.
From the Digital Signatures tab, select

the name of the signer (GE Automation &
Controls) and click Details.
Verify that This digital signature is OK

is displayed .

➢ To verify the integrity of the files from the Windows PowerShell console
2. Verify that all files match by running the Verify-Integrity.ps1 script.
PowerShell Console Command Prompt File Integrity Verification
➢ To verify the integrity of the files from the Windows (DOS) console
1. Open a Command prompt and enter the DOS console using the command CMD.
2. Verify that all files match the by running the Verify-Integrity.ps1 script.
DOS Console Command Prompt File Integrity Verification
7.1.3.2 Troubleshooting
If any the following warnings/failures are displayed during PowerShell script file integrity verification, do not trust the file
until the failure is resolved.
Verify-Integrity Script Integrity Check Failure Message
One or More Files Integrity Check Files Mismatch Message

One or More Files Integrity Check Missing File Message
7.1.3.3 Verbose Option

➢ To verify the integrity of the files using the Verbose option
1. Open a Command prompt and enter the PowerShell console using the command Verbose.
2. Verify that all files match the by running the Verify-Integrity.ps1 script.
Verbose Command File Integrity Verification
7.1.4 Product Signing File Integrity Verification Procedures (Releases Sept

2015 through Dec 2015)
If a software release was signed with GE's Automation & Controls’ external certificate, the certificate issuer is Symantec. If
the release was signed with GE's Automation & Controls’s internal certificate, then the certificate issuer is GE's Automation
& Controls’ internal domain (PDEV); you can only trust the file if you are a member of the PDEV domain or you have
configured your computer to trust GE’s Certificate Authority (CA) Server.
➢ To verify the signature of a file in the ControlST release
Note Only certain kinds of files can be signed, such as .exe and .msi files.
1. From Windows Explorer, navigate to the folder containing the file.

2. Right-click the file and select Properties.
3. View the Digital Signature information and verify the digital signature is OK.
GEH-6808N ControlST Software Suite How-To Guides

From the Digital Signatures tab, select the name of the
signer (GE Automation & Controls) and click Details.
Verify that This digital signature is OK is displayed .
Click OK to close the window .
This confirms the following:
• The hash of the file matches the hash value that was decrypted using GE's Automation & Controls’ Public Key.
• The issuer (signer) of GE's certificate was trusted, therefore GE's Automation & Controls’ certificate is trusted.
− For GE's Public certificate, this indicates you trusted Symantec, Symantec trusted GE's Automation & Controls,
therefore you trust GE's Automation & Controls.
− For GE's Internal certificate, this indicates you trusted the PDEV domain CA, the PDEV domain CA trusts GE's
Automation & Controls, therefore you trust GE's Automation & Controls.
As a convenience, GE's Automation & Controls has also added an additional level of integrity checking so the user does not
have to verify every file in a ControlST release. The file Setup.exe verifies the integrity of the files that it launches, and
requests user validation if it detects a file that is not trusted.
For self-extracting executable files: In addition to the previously discussed

verification in this document, you may wish to verify the integrity of a self-extracting
executable file that you downloaded from a GE website or file server. Within this
executable, all files have been signed as previously described; However, the executable
file itself may be too large to allow product signing. In these cases, a .hash file is used
Attention (available with the ControlST release). Follow the instructions provided in the section
Hash File Integrity Verification Procedures.

7.1.5 Hash File Integrity Verification Procedures (Releases Prior to Sept
2015)
Note This procedure also applies to self-extracting executable files that are too large to be signed.
7.1.5.1 Acquire PowerShell Script

➢ To acquire PowerShell script: download the Check-Filehash.ps1 PowerShell script from the following locations:
• Internal GE users: \\pdevnt.salem.ge.com\Releases\ControlST\Other\Hash Checker

• External GE users: contact customer support
7.1.5.2 Verify a Directory’s Contents

Perform the following procedures to verify a directory’s contents using a .hash file:
1. Acquire a previously generated .hash file.
2. Configure the PowerShell environment to grant Windows permission to run the PowerShell scripts defined by other
users.
3. Verify the directory’s contents using a single, previously generated .hash file.
➢ To acquire previously generated .hash file: Download the .hash file for the release.
Note External GE users must contact customer support to acquire the .hash file for the release.
GE Internal users can download the .hash file for the product or release for verification as follows:
• Internal GE Products (contains all full ControlST releases and component releases) are available on the ControlST
Releases File Server . The .hash file is located within the folder that hosts the software download.
• External GE Products (contains General Market ControlST releases) are available on GE's Automation & Controls
Support website.
➢ To configure the PowerShell environment

2. Set the execution policy using the command Set-ExecutionPolicy RemoteSigned –Scope CurrentUser.
Note Windows can run PowerShell scripts using the current Windows account.

➢ To verify a directory’s contents using a single, previously generated .hash file
2. Check the directory contents against the .hash file using the command: .\Check-Filehash.ps1 –Hashfile
HashfileName.hash –Path “Path of Directory to Hash”.
The following figure illustrates an example output for checking a directory with the path C:\Hash Kit\WEPA_V04.09.02C
against a previously generated file, WEPA_V04.09.02C.hash.
WEPA_V04.09.02C.hash File Integrity Verification Result (Passed)
7.1.6 Glossary of Terms

Key Pair: A cryptographic concept whereby two keys are generated such that if something is encrypted by one key it can
only be decrypted by the other, and vice versa.
Public Key: The Key in the Key Pair that is made public or published.
Private Key: The Key in the Key Pair that is kept private.
Certificate: A Public Key along with the identity of the person who owns it, typically signed by a 3rd party you trust to
vouch for the identity of the certificate holder (the person with the private key).
Hashing: The act of taking data of any size and running it through an algorithm to produce a single value of a fixed size. If
the original data is changed the output value produced (hash value) also changes. The algorithm is chosen to make it
extremely difficult to make changes in the original data while still having it generate the same output (hash) value.
Signing: The act of taking a hash of something (such as file, certificate, password) and encrypting the resulting hash with
your Private Key. A receiver can then decrypt this hash with your Public key and check it against the contents of what was
hashed. If they match, the recipient knows that it came from you (only you could sign it using your Private Key) and has not
been modified (the hash values [one you computed, one you decrypted using my Public Key] match).

7.1.7 Help Option on Verify-Integrity.ps1 Script
The help Verify-Integrity.ps1 command provides additional help and examples, such as follows:
PS V:\sign> help Verify-Integrity.ps1 -Detailed
NAME
Verify-Integrity.ps1
SYNOPSIS
Verify-Integrity.ps1 checks the integrity of the product located in the same directory as itself. Verify that the
Verify-Integrity.ps1 file is signed then execute the Verify-Integrity.ps1 script to verify the integrity of
the remaining files in the distribution.
SYNTAX
Verify-Integrity.ps1 [-Verbose] [CommonParameters]
DESCRIPTION
The Verify-Integrity.ps1 script is a signed script that will verify

(using file hashes) the contents of a distribution directory. The script
is signed to prove that it came from the manufacturer and has not been altered
– verify the signature on the script file before running the script file.
The signature can be verified by opening Windows Explorer, navigating to

the directory holding the distribution, right-clicking on the Verify-
Integrity.ps1 file, and selecting "Properties" - "Digital Signatures".
Select the line in the signature list and click on "Details". The
resulting dialog should show the phrase "This digital signature is OK."
After verifying the signature on the Verify-Integrity.ps1 file, run the

file to verify the integrity of the remaining files in the
distribution. The script will check the files in the same directory as
the Verify-Integrity.ps1 script, you do not need to set your current
default directory there first. The script can be run from a PowerShell
console, or from a Windows (DOS) console using the "PowerShell"
command. (See the examples for more details.)
—————————————— EXAMPLE 1 —————————————

PS C:\PS>:\Download\Verify-Integrity.ps1
The above command run from a PowerShell console verifies the distribution
located in the D:\Download directory. (Make sure you verify the script file
is signed before running it.)
—————————————— EXAMPLE 2 —————————————
C:\>PowerShell -File D:\Download\Verify-Integrity.ps1

The above command run from a Windows console verifies the distribution
located in the D:\Download directory. (Make sure to verify the script file
is signed before running it.)

7.2 How to Order ControlST* Software Media and License
Keys
Beginning with ControlST* V05.00.00, ControlST software is licensed using the same methods as other GE Digital and GE
Automation & Controls software, such as CIMPLICITY*, Proficy® Historian, Proficy Machine Edition (PME), and Proficy
Device Management. Although a license key is not required to install ControlST products, in order to use the ToolboxST* and
WorkstationST* applications a valid license key (hardware or software) must be purchased and installed or activated.
The following ordering processes and procedures are provided this document:
• Software media ordering process

• License key ordering process
7.2.1 Software Media (ControlST, OSI PI Historian, eTCSS, GECSS, and

OSM3) Ordering Process
➢ To order ControlST software media (CD/DVD): fill out and submit a Support Central Software Ordering Workflow.
Note ControlST license keys are ordered separately from ControlST software media.
7.2.2 License Key Ordering Process

The license key you order depends on the following criteria:
• ControlST version you need to license

• Whether you are ordering a new ControlST license or upgrading an existing license
• Type of license key (Legacy hardware key or Advantage software license) you are ordering
• License key user (GE customer or GE internal-use)
7.2.2.1 License Key Types

• Hardware Key: A computer with several software products installed must have license keys for all of those products on
a single hardware key.
• Software License: Project Advantage licensing uses a software activation key per product (ControlST, CIMPLICITY,
Proficy Historian) as needed. The activation codes can be applied directly to a computer or to the SSL Key (USB storage
device) by the user. The pre-programmed, non-configurable license is programmed by GE on a software license or the
M5 hardware key. An example of the user-configurable license is three license keys for ControlST, CIMPLICITY, and
Proficy Historian can be activated on one computer, or on three separate computers. Additional information and
troubleshooting for Advantage software license activation is available at GE Customer Care support website.
Note The Proficy License Client (or Manager or Viewer, depending on version) will only recognize one license key type at a
time.

7.2.2.2 License Key Ordering Procedure
Note For a license key ordering process flow diagram with detailed instructions, refer to ControlST Software Suite License
Key Ordering (GHT-200060).
➢ To order ControlST license keys

1. Determine which ControlST version you need to license. There are multiple license keys and you need to know which
version of the software product to license.
2. Determine if you need to order a new license or upgrade an existing license.
a. For an upgrade, determine if you can upgrade your existing key or if you need to order a new key (based on your
existing ControlST version). Refer to the following chart.
b. For a new license key, refer to the following chart.
Hardware and Software Keys
Note The Legacy ControlST license key (V04.07.xx and older) can be used with any other Proficy or Advantage license
keys.
However, you cannot use two of the same type of license keys on a single computer (applies to Legacy, Proficy, or Advantage
hardware keys). Proficy Common Licensing will only recognize one type of license. Hardware keys have the highest priority.
For example, the license software will only recognize a single hardware key, or an Advantage activation code; it will not
recognize both at the same time.
3. Determine which license key part number(s) you need to order. For assistance with determining your ControlST versions
and license key part numbers, quantity, and cost, refer to the following resources:
• Tables provided in the section ControlST Version Part Numbers and Cost
• ControlST Software Suite License Key Ordering (GHT-200060)
• Customer Care

4. For GE internal-use licenses, contact one of the following resources:
• Customer Care for Legacy licenses: CustomerCare.ip@ge.com
Note If you have a CSN or SAP from a previous software purchase, provide it to Customer Care. If you do not
have one, one will be created for you.
• Inside Sales for Solution Provider licenses: insidesales.ip@ge.com
5. Determine if there is an applicable blanket purchase order (PO) in place for your organization (Power, Power Services,
Wind USA, Wind Europe, and Control Solutions).
If you do not have an applicable blanket PO and need to create a PO, GE Automation & Controls may be listed in your
GSL as
GE Intelligent Platforms with one of the following addresses:
GE Automation & Controls Inc. GE Automation & Controls Inc. GE Automation & Controls Inc.
325 Foxborough Blvd PO Box 8106 RT 29N and RT 606 2500 Austin Dr
Foxboro, MA 02035 Charlottesville, VA 22906 Charlottesville, VA 22911–8319
6. To place an order, send an email to Customer Care with all of the following information:
• Part numbers
• Quantities
• Cost
• CSN or SAP number
• PO (or PO information)
• Ship To address and contact information
Note For an example email, refer to the section Example Order Request Emails.
To expedite your order, organize your license key request by computer. For example:
a. Computer 1, 3, and 4 need licenses for CIMPLICITY V08.02 and ControlST V07.00.
b. Computer 2 needs licenses for only ControlST V07.00.
c. Computer 5 needs licenses for Proficy Historian with 5,000 tags and WorkstationST for Historian.
This order would result in five license keys, one license key for each computer.
Note For assistance with license key activation, installation, use, and updates, refer to How to Install, Activate, Update, and
Troubleshoot ControlST Licenses (GHT-200049).

Example Order Request Emails
In the following examples, insert your specific information in place of the content within the brackets [ ].
For a New License Order Request:

Email Subject: ControlST License New Order Request for [project name/person]
Email Body:
Please find attached a PO to order the following:
[Qty 3 – ControlST Version 7.0 — ST70GE + KEY M5 AC (for hardware key)]
• Ship To Address: [Physical shipping address for hardware key; email address for software activation only]
• End User Info:

− End User Name: [End User Name]
− End User Address: [End User Address]
− End User Contact Name: [End User Contact Name]
− End User Contact Email address: [End User Email Address]
For an Upgrade License Order Request:

Email Subject: ControlST License Upgrade Order Request for [project name/person]
Email Body:
Please find attached a PO to upgrade the following [CIMPLICITY Serial Number license keys with ControlST
Version 7.0 — ST70GE]:
Note M4 hardware keys programmed by the Siebel system have been replaced with either software activation codes or the
M5 hardware key.
• [123456789]
• [123456790]
• [123456791]
• [123456792]
• Ship To Address (Internet): [Your.name@ge.com; email address for software activation only]
• End User Info:


For a New License Order Request with an Applicable Blanket PO:
Email Subject: ControlST License New Order Request for [project name/person]
Email Body:
Please order the following part numbers at No Charge, Reference [GE business name] blanket PO [Blanket PO
Number]:
[Qty 3 – ControlST Version 7.0 — ST70GE + KEY M5 AC (for hardware key)]
• Ship To Address: [Physical shipping address]
• End User Info:

For an Upgrade License Order Request with an Applicable Blanket PO:

Email Subject: ControlST License Upgrade Order Request for [project name/person]
Email Body:
Please upgrade the following [CIMPLICITY Serial Number license keys with ControlST Version 7.0 — ST70GE], at
No Charge, Reference [GE business name] blanket PO [blanket PO Number]:
Note M4 hardware keys programmed by the Siebel system will be replaced with either software activation codes or the M5
hardware key.
• [123456789]
• [123456790]
• [123456791]
• [123456792]
• Ship To Address (Internet): [Your.name@ge.com; email address for software activation only]
• End User Info:


7.2.2.3 Example ControlST Versions, Part Numbers, and Cost
ControlST V07.xx
Advantage M5 Hardware License Key
Note In the following table, xxx/yyy/zzz/aaa/bbb = 0–255 (qty).
Example ControlST V07.xx License Key Part Numbers and Cost

Siebel Part Number Salesforce.com
Item Qty No longer available as of Software Part Cost
April 7, 2017 Number†
Complete ControlST Software Suite
1 IC647CST-700 ST70GE $5,300 ea
V07.00.00C
ToolboxST
ToolboxST for Renewables (Wind, Solar,
1 IC647CSTRENEW-700 ST70GT $1,800 ea
Battery) - V07.00.xx (no Workstation features)
General Market 1 Not available Not available —
Safety Controller 1 Not Available ST70ES —
ControlST Options
Remote Desktop Connections (Terminal -Tbbb $1,800 ea
0–255 Not Available
Services) (Ex: ST70GE-T001) (Ex Cost: $7,100)
Control System Health (CSH) for 5 Clients -Haaa $1,000 ea
0–255 OC647CSTCSH05
Option for IC647CST-700 (Ex: ST70GE-H001) (Ex Cost: $6,300)
WorkstationST
WorkstationST 7.0.0 for Operator HMI with
Alarm Server, Alarm Viewer, HMI Interface,
1 IC647CSTHMI-700 ST70GO $2,700 ea
TrenderST, and View-only ToolboxST for go to
code
WorkstationST 7.0.0 for Historian with
Historian Interface, Alarm Server, Alarm
1 IC647CSTHIST-700 ST70GH $2,700 ea
Viewer, OPC-DA Client, Recorder and
TrenderST
WorkstationST 7.0.0 for Communication
Gateway with Alarm Server, GSM Link,
1 IC647CSTCGW-700 ST70GC $2,700 ea
Modbus Link, OPC-DA - Client, OPC-AE -
Server, OPC-AE – Client
WorkstationST 7.0.0 for Application Server
with Alarm Server, Alarm Viewer,
Configuration Management Server, Device 1 IC647CSTAS-700 ST70GA $2,700 ea
Manager Gateway, OPC-AE - Server,
Recorder, and TrenderST
†When ordering a hardware license key, you must add + Key M5 AC to the software license part number.
Part numbers can be combined on the same license key.

Example ControlST V07.xx License Key Part Numbers and Cost (continued)
Virtual Controllers for ControlST V07.00.00
Mark VI Virtual Controller
Mark VI Virtual Controller Only
-Mxxx $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVI01-700
(Ex: ST70GV-M001) (Ex Cost: $2,000)
WorkstationST)
Mark VIe Virtual Controller
Mark VIe Virtual Controller Only
-Eyyy $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVIE01-700
(Ex: ST70GV-E001)
WorkstationST)
Mark VIeS Virtual Controller
Mark VIeS Virtual Controller Only
-Szzz $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVIES01-700
(Ex: ST70GV-S001)
WorkstationST)
Examples
IC647CST
ControlST Engineering Workstation with -MxxxEyyySzzz $2,000 ea
IC647CSTVCMVI05-50
Mark VI, Mark VIe, Mark VIeS Virtual 5 (Ex: ST70GE- (Ex Cost: $11,300)
IC647CSTVCMVIE05-50
Controllers M001E001S001)
IC647CSTVCMVIES05-50
IC647CST
ControlST Engineering Workstation with
IC647CSTVCMVI05-50 -MxxxEyyySzzzHaaa $2,000 ea
Mark VI, Mark VIe, Mark VIeS Virtual
5 IC647CSTVCMVIE05-50 (Ex: ST70GE- (Ex Cost: $12,300)
Controllers and Control System Health
IC647CSTVCMVIES05-50 M001E001S001H001)
(CSH)
OC647CSTCSH-05
† When ordering a hardware license key, you must add + Key M5 AC to the software license part number.

ControlST V06.02.00
Example ControlST V06.02.00 License Key Part Numbers and Cost

1 IC647CST-620 ST62GE $5,300 ea
V06.02.00C
ToolboxST
Battery) - V06.02.00 (No Workstation features)
General Market 1 Not available Not available —
Safety Controller 1 Not Available ST62ES —
ControlST Options
WorkstationST
WorkstationST 6.2.0 for Operator HMI with
code
WorkstationST 6.2.0 for Historian with
TrenderST
WorkstationST 6.2.0 for Communication
WorkstationST 6.2.0 for Application Server
with with Alarm Server, Alarm Viewer,

Example ControlST V06.02.00 License Key Part Numbers and Cost (continued)
Mark VI Virtual Controller Only
-Mxxx $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVI01-620
(Ex: ST62GV-M001) (Ex Cost: $2,000)
WorkstationST)
Mark VIe Virtual Controller Only
-Eyyy $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVIE01-620
Ex: ST62GV-E001) (Ex Cost: $2,000)
WorkstationST)
Mark VIeS Virtual Controller Only
-Szzz $2,000 ea
(No ControlST, ToolboxST, or 1 IC647CSTVCMVIES01-620
(Ex: ST62GV-S001) (Ex Cost: $2,000)
WorkstationST)
Examples
IC647CST
ControlST Engineering Workstation with -MxxxEyyySzzz $2,000 ea
IC647CSTVCMVI05-62
Mark VI, Mark VIe, Mark VIeS Virtual 5 (Ex: ST62GE- (Ex Cost: $11,300)
IC647CSTVCMVIE05-62
Controllers M001E001S001)
IC647CSTVCMVIES05-62
IC647CST
ControlST Engineering Workstation with
IC647CSTVCMVI05-62 -MxxxEyyySzzzHaaa $2,000 ea
5 IC647CSTVCMVIE05-62 (Ex: ST62GE- (Ex Cost: $12,300)
Controllers and Control System Health
IC647CSTVCMVIES05-62 M001E001S001H001)
(CSH)
OC647CSTCSH-05
† When ordering a hardware license key, you must add + Key M5 AC to the software license part number.

CIMPLICITY, Proficy Historian, and Other GE Software Products
Example CIMPLICITY, Proficy Historian, and Other GE Software Products License Key Part Numbers and Cost
Siebel Part Number
Salesforce.com
Item No longer available as Cost
Part Number
of April 7, 2017
CIMPLICITY Advance Viewer V 8.2 IC647TAV000-82 — —
Standard/8.2/Viewer/Development/AdvancedViewer/English — CI82VDAEN —
Standard/8.2/Viewer/Development/AdvancedViewer/English/-
— CI82VDAEN-G005 —
with qty 5 Global View
CIMPLICITY Development Server V8.2 35k points IC647TDV935-82 — —
Standard/8.2/Server/Development/35000/English — CI82SSD35000EN —
CI82SS-
Standard/8.2/Server/Development/35000/English/GlobalView5 — —
D35000EN-G005
CIMPLICITY Development Server V8.2 Unlimited points IC647TDV000-82 — —
Standard/8.2/Server/Development/Unlimited/English — CI82SSDUNLIMEN —
Standard/9.0/Server/Development/Unlimited/English — CI90SSDUNLIMEN —
Modbus RTU IC646NMR000 — —
Modbus TCPIP IC646NMX000 — —
Pager IC646NPG000 — —
GlobalView IC647NGV000 — —
Proficy Historian Version 4.5 1000Tag IC647HSTSS1KM-45 — —
Standard/5.5/Standard/1000 points w/ 5 CALS included
— HS55S0000100000 —
includes Redundant Collector, OSI PI, OPC HDA Server
Standard/5.5/Standard/1000 points + additional 5 CALS (10
total) — HS55S0000100005 —
Historian v5.5 Standard 50000 Points + additional 5 CALS
— HS55S0005000005 —
OPC/HDA Server IC647HSTHDAM — —
Excel Add-On 27013110000C — —

ControlST V05.04.00
Example ControlST V05.04.00 License Key Part Numbers and Cost

Item Qty No longer available as Software Part Cost
of April 7, 2017 Number†
1 IC647CST-540 ST54GE $5,300 ea
V05.04.00C
ToolboxST
Battery) - V05.04.00 (no Workstation features)
ControlST Options
WorkstationST
WorkstationST 5.4.0 for: Operator HMI with
code
WorkstationST 5.4.0 for: Historian with
TrenderST
WorkstationST 5.4.0 for: Communication
WorkstationST 5.4.0 for: Application Server
with Alarm Server, Alarm Viewer,
Mark VI Virtual Controller Only -Mxxx $2,000 ea
1 IC647CSTVCMVI01-540
(No ControlST, ToolboxST, or WorkstationST) (Ex: ST54GV-M001) (Ex Cost: $2,000)

Example ControlST V05.04.00 License Key Part Numbers and Cost (continued)
Mark VIe Virtual Controller Only -Eyyy $2,000 ea
1 IC647CSTVCMVIE01-540
(No ControlST, ToolboxST, or WorkstationST) (Ex: ST54GV-E001) Ex Cost: $2,000
Mark VIeS Virtual Controller Only -Szzz $2,000 ea
1 IC647CSTVCMVIES01-540
(No ControlST, ToolboxST, or WorkstationST) (Ex: ST54GV-S001) Ex Cost: $2,000
Examples
IC647CSTVCMVI05-540 -MxxxEyyySzzz $2,000 ea
5 IC647CSTVCMVIE05-540 (Ex: ST54GV- Ex Cost: $6,000
Controller
IC647CSTVCMVIES05-540 M001E001S001)
ControlST Engineering Workstation with -MxxxEyyyySzzzHaaa $2,000 ea
Mark VI, Mark VIe, Mark VIeS Virtual 5 — (Ex: ST54GE- Ex Cost: $12,300
Controller and Control System Health (CSH) M001E001S001H001)

ControlST V04.07.xx or Older
Legacy Blue Dongle
Example ControlST V04.07.xx or Older License Key Part Numbers and Cost
Item Qty Part Number Cost
Complete ControlST Software Suite V04.07.xx —
1 IC647CST-47 $5,300 ea
DVD and blue dongle for V04.07.11C or older
ControlST Pre-V05.00 — Hardware key only 1 IC647CSTPRE50HWKEY $5,300 ea
Add Virtual Controllers (Available on Blue Dongle)
1 IC647CSTPRE50VCMVI01 $2,000 ea
Pre-V05.00 Mark VI Virtual Controller
1 IC647CSTPRE50VCMVIE01 $2,000 ea
Pre-V05.00 Mark VIe Virtual Controller
1 IC647CSTPRE50VCMVIES01 $2,000 ea
Pre-V05.00 Mark VIeS Virtual Controller

ControlST V03.06.09 or Older
Legacy Green Dongle
Example ControlST V03.06.09 or Older License Key Part Numbers and Cost
Item Qty Part Number Cost
ControlST Pre-V03.06.09C — Hardware key only (green dongle) 1 IC647CSTPRE369HWKEY $5,300 ea
Add Virtual Controllers (Available on Green Dongle)
Pre-V03.06.09 Mark VI Virtual Controller
Pre-V03.06.09 Mark VIe Virtual Controller
Pre-V03.06.09 Mark VIeS Virtual Controller

7.3 How to Set Up the Remote Services Gateway
The Remote Services Gateway (RSG) computer is installed on site to allow remote desktop access to the site. It provides
login to a site from a remote location to monitor the power plant. The RSG has additional layers of security, including a
lock-box, which is a metal box with a key that physically connects/disconnects the internet connection to the RSG, effectively
locking everyone out.
Note Refer to the OnSite Support* Remote Diagnostic Equipment Installation Guide (GEI-100760) for additional
information.
This document covers the following procedures:
• Bios Modification
• Windows Accounts Setup
• pcAnywhere™ Setup
• Installing VNC™
• Setting up Ethernet Adapters
• Turning off Windows® Firewall
• Configuring CIMPLICITY* computers
• Installing GE Software
• Adding new RSG in system configuration (.tcw file)
Note This document only applies to the ControlST* software suite V03.01 or later, and the CIMPLICITY application V5.5
or later.
The steps in these procedures should have been completed before the RSG was shipped to the site. It is a good practice to go
through the steps and make sure they have been completed.
7.3.1 Modifying the RSG Computer BIOS

➢ To modify the RSG computer BIOS
1. While the computer is starting up, press the F10 key to go into the BIOS.
2. After the BIOS displays, from the Advanced section, select Power-On Options, After Power Loss, and change
from OFF to ON. This is required so the RSG will restart automatically when power is restored after a power loss.
3. From the File menu select Save Changes and Exit.
4. The computer starts in Windows.

7.3.2 Setup of Windows Accounts
➢ To set up Windows accounts
1. When the computer displays the logon prompt, enter the following:
User name - administrator
Password - gepgc
2. From the desktop, double-click the My Computer icon, Control Panel, Administrative Tools, and Computer
Management to display the Computer Management screen.
3. From the right side of the screen, right-click anywhere in the display area (or from the Tree View, right-click on the
Users folder) and select Add User from the shortcut menu.
4. Add the following Windows accounts:
Username – onsite
Password – gesalem9
Group – Administrators
Username – viewer
Password – viewer
Group – Power Users
Note The only accounts required on the RSG are Administrator, onsite, and viewer. The maint and oper accounts are not
needed. The Administrator account should have the same password (gesalem9) as the onsite account.
Note These are default user names and passwords and will be updated and changed at each site for security reasons.

7.3.3 pcAnywhere Setup
➢ To set up the pcAnywhere application
1. Launch the application.

2. Click the New Item button to display Caller Properties dialog box.
3. From the Identification tab, select the User option button.
4. Select Domain and from the drop-down list, select [Local Machine].
5. Select Account and from the drop-down list, select viewer.
6. Click OK.
7. The Host Properties dialog box displays.

7.3.4 Installing VNC
UltraVNC is installed as a backup means to remotely connect to the RSGs in case the pcAnywhere application is not working.
Attached below are instructions for installing and configuring UltraVNC on the RSG.
➢ To install UltraVNC
1. Go to the following web site:
\\varoaa02psge\remote_services\Software\Freeware\UltraVNC
Note Do not put the RSG on the GE network. For transferring files to the RSG, use a USB flash drive.
2. Copy the UltraVNC-102-Setup.exe file to the USB drive.

3. Insert the USB drive in a USB port the RSG.
4. From My Computer, double-click on the USB drive to display the contents.
5. Double-click the UltraVNC-102-Setup.exe file to begin the installation process. The Select Setup Language

Note This password should be set to the same password as the onsite account. The onsite account is an administrator that is
used to administer the RSG, while the viewer account is a read-only account used for viewing control system data.
The UltraVNC installation is complete.

7.3.5 Setting up Ethernet Adapters
Configure the PDH and UDH Ethernet adapters with the correct IP addresses. For the PDH and UDH Ethernet adapters, the
subnet mask should be set to 255.255.255.0. The PDH adapter will also require a gateway address.
Note The UDH should have been created when the system was created. If not, consult site documentation for the network
configuration.
➢ To set up Ethernet adapters

Editor.
2. If the correct system is not displayed, from the File menu, select Open System, locate and select the correct .tcw file,
and click Open. The system displays in the System Editor.

Place the appropriate labeling on the Ethernet adapters: PDH and UDH. Also label the RSG as RSG1. If there are multiple
RSGs, label the second RSG as RSG2, the third RSG as RSG3, and so forth.
7.3.6 Turn Off Windows Firewall

➢ To turn off the Windows firewall
1. From the Start menu, select Settings, Control Panel, and double-click the Windows Firewall icon.
2. Set the Windows Firewall to OFF and click OK.

7.3.7 Configuring CIMPLICITY Computers
This procedure requires that CIMPLICITY 6.1 or earlier is installed.
➢ To configure CIMPLICITY computers

1. Locate and select the CIMPLICITY computer’s project .gef file to display the CIMPLICITY Workbench window.

2. Repeat the previous two steps to create another CIMPLICITY computer account called VIEWER, assign the role USER
to the account, and click OK.
7.3.8 Installing the GE Software

Based upon the customer’s site, install the appropriate versions of the GE ControlST CD, eTCSS application, PI Combo, and
other applications as required.

7.3.9 Adding a New RSG in the System Configuration (.tcw File)
➢ To add a new RSG in the system configuration (.tcw file)
Editor.
2. If the correct system is not displayed, from the File menu, select Open System, locate and select the correct .tcw file,
and click Open. The system displays in the System Editor.

3. The Download Welcome Wizard displays. Click Next.

7.4 How to Set Up the ExperTune® PlantTriage Control
Loop Monitoring System
The ExperTune® PlantTriage Control Loop Monitoring system can run on the same computer as the Human-machine
Interface (HMI) using the ControlST* software suite, and only needs access to an Object Linking and Embedding for Process
Control (OPC®) server to monitor plant performance. The OPC server provided by the WorkstationST* application is called
GeCssOpcServer. With access to the OPC server, the PlantTriage system can Read any variable that is accessible from the
local workstation. It also can Write to any variable defined as Read/Write.
Note The purpose of this document is for the user to become familiar with the PlantTriage system. For further loop
configuration options, refer to the PlantTriage system manual located at C:\xtune\PT\manual on the installed computer.
7.4.1 Installation
➢ To install the PlantTriage system
1. Complete the installation steps for configuring the CIMPLICITY* application on a standard HMI. This step is optional,
depending if the CIMPLICITY application screens are desired.
2. Complete the installation steps for configuring the ControlST application suite for a standard workstation.
3. Follow the steps provided with the ExperTune application to install all PlantTriage system applications.
a. Refer to the installation manual provided with the ExperTune application.
b. Install CD1, CD2, and CD3, followed by the OPC connectivity server.
Note For assistance with PlantTriage installation issues, contact tech.support@expertune.com.
4. Configure the ToolboxST* application with a workstation that has the HMI (if required) and OPC DA features installed.
Download to the WorkstationST application. Refer to the ToolboxST User Guide for Mark* Controls Platform
(GEH-6700).

7.4.2 Diagnostic Monitors
7.4.2.1 Connectivity Tester

➢ To run the Connectivity Tester
1. From your desktop, double-click the Connectivity Tester icon.

2. Select the type of test.

3. Close any open windows.
7.4.2.2 PlantTriage Monitor

1. From your desktop, double-click the PlantTriage Monitor icon.
2. Review the Installation checks.
Note If any items are marked with a red X, further troubleshooting is needed. Contact tech.support@expertune.com.

7.4.3 Loop Assessment
➢ To configure and run loop assessment
Note The PlantTriage system must be configured for each control loop. To configure individual loops, use the New Loop
Wizard. To add and configure multiple loops, use the ExperTune Import program.
1. From your desktop, double-click the PlantTriage Administration icon.

2. Select New Loop to display the New Loop Wizard.
Note This will not be a batch process.

3. Input a status bit to determine if the assessments of all the loops in the unit (HRSG1) are on or off. In most cases, a status
bit is not needed to turn the unit online or offline.
Note This feature allows specific loop assessments to be turned off based on a signal. This may be used for future
assessments. For example, HRSG out of service might turn off all Heat Recovery Steam Generator (HRSG) related signals.

4. Using the Proportional Integral Derivative (PID) block in the controller logic, enter the parameters to configure the
control loop.
Note Some default loop names are provided in the spreadsheet, GEFolderslink.xls. The spreadsheet also provides the
settings for each loop; however, the parameter names may vary depending on the loop. The spreadsheet may found at the
following location: http://libraries.ge.com/foldersIndex.do?entity_id=18854000101&sid=101&sf=1.

Note The minimum and maximum spans for the process variable and control output are the limits of the PID control and are
usually defined by the I/O. However, sometimes this may differ. Refer to the Scale factor connected to the PID block in the
logic. The full range of the CO should control the full range of the PV. If the CO is at its maximum level, then the PV should
also be at its maximum level, and vice versa.
Note The CO limit ranges from 0-100% but the control output high limit is not necessarily 100%. The high limit is put in for
protection but the CO range is still 0-100.

Note The following steps specify what the PID loop is controlling. If you are not sure about the loop, these steps can be
skipped and revisited once further knowledge about the loop is collected.
Cascading loops are two PID blocks connected in series. The CO of one loop goes to the setpoint (SP) of another loop,
allowing a valve or pump to be controlled by more than one process variable.
• None specifies a simple PID loop.

• Primary is the first PID loop in a cascading series (sometimes defined as an outer loop). The CO of this PID
connects to the SP of the secondary loop.
• Secondary is the second PID loop in a cascading series (sometimes defined as the inner loop). The CO of this PID
connects to the field device.
Loop Diagram

7.5 How to Set Up and Tune a Control Loop With
ExperTune® OPC® PID Tuner
The ExperTune® application accesses an OLE for Process Control (OPC®) server to read any variable that is accessible from a
local workstation. The WorkstationST* application provides the OPC server, GeCssOpcServer. The OPC server Proportional
Integral Derivative (PID) tuner is used to set up and tune a control loop. This how-to guide consists of the following
procedures:
• Set Up a control Loop

• Tune a Control Loop
7.5.1 Set Up a Control Loop

➢ To set up a control loop
1. From your computer, locate the OPC PID tuner file.

2. Set up a loop using one of the following three options:
• Use a previously configured configuration wizard and input specific attributes to populate all of the required
variables for the ExperTune application. This is the easiest way to set up a loop; however, a configuration wizard
needs to have been previously created.
• Create a configuration wizard to use for all subsequent loops.
Note For this document, we will set up a control loop using this option.
• Manually set up and configure each variable in the loop.

Note If you are using the WorkstationST application, the OPC server name will always be GeCssOPCServer.

3. From the ToolboxST* application, open the logic for the specified loop. Notice the name of the loop,
B1S.10LCA30AA551 [Controller].[Device].
The ExperTune setup will request specified variables for the loop. The following are the descriptions for each variable:
• Process Variable (PV) is the controlling variable of the PID loop. This may be a level, temperature, flow, or
pressure, which is the feedback of what is occurring in the field.
• Setpoint (SP) is the desired value of the PV. In Auto mode, the Command Output (CO) controls so that the PV
equals the SP. Usually, the PV is always equal to the SP; however, due to process, latencies, and poor tuning, the PV
can oscillate or lag behind a changing SP.

• Command Output (CO) is the command value sent to the controlling valve in the field. In Manual mode, this
value is controlled by the operator. In Auto mode, the logic and PID tuning parameters control the valve. The CO is
usually sent straight to the field for valve position, but this may not always be the case. There may be a lag between
the CO and the actual position of the valve. Additionally, the CO can control motor speed or another device that does
not receive 0-100%
Note This variable may also be referred to as Command Valve Output (CVO) or valve command.
• Proportional Gain (PG) defines how quickly the CO updates with changes in the PV. The greater the difference
between the PV and SP, the greater the effect the PG has on the variability of the CO.
• Interval Gain (IG) defines how quickly the CO updates with changes in the PV. The greater the difference between
the PV and SP over time, the greater the effect the IG has on the variability of the CO. This value is affected by the
overall error between the PV and SP.
• Derivative Gain (DG) defines how quickly the CO updates with changes in the PV. The greater the rate of change
of the PV with respect to the SP, the greater the effect the DG has on the variability of the CO. For most loops this is
set to 0 because noise in the PV causes the loop to become unstable.
• A controller can reside in the following modes:
− Manual mode: In this mode, the operator completely controls the command output. The operator can open the
valve and increase the CO, or close the valve and decrease the CO. Only output limitations, valve trips, and
valve forces can override the operator. This is almost always available for valve and speed control.
− Auto Local mode: In this mode, the CO is controlled by the PID tuning. With the software’s parameters, the
CO will increase or decrease to hold the PV equal to the SP. The operator has control over the SP only. The
operator’s SP control is limited by a SP change ramp rate and the SP high and low limits. Most loops are set up
in Auto mode.
− Auto Remote mode: This mode is similar to Auto Local mode, except that the logic also controls the loop SP.
The operator has no control over the action of the any loop. Ideally, all loops will be in Auto Remote mode
during plant operation so the operator has no loops to manually control.
− Tracking: This may occur in either Manual or Auto Local mode. Tracking indicates that the CO writes straight
back on itself, thus bypassing any PID efforts to change the CO. Tracking is always active in Manual mode. It is
only active in Auto Local mode when the CO reaches its high or low limit, thus being unable to further open or
close.
• Scale Factor (SF) is defined by the CO range divided by the PV range. This varies per loop.
Note The SF value is extremely important for tuning. It is standard to keep this value as (CO/PV). Tuners can change this
value, which will corrupt the proportional (P), integral (I), and derivative (D) values.
− PV range: This is usually the range of the transmitter. Sometimes, the previous tuner defines this as a different
value (the range of this value could be 0-xxx range).
− CO range: This should always be 0-100. The low and high limits can be within this range.
• Process Direction indicates the direction the CO needs to react if the PV strays from the SP. For example, a fill
valve for a tank would be reverse. As the tank fills up above the SP, then, when in Auto Local mode, the fill valve
would want to close. Thus, it would want to act in the reverse direction of the PV. ExperTune views this in a
different way. If an operator were to manually open the fill valve, PV would increase. If the loop is a reverse acting
controller,the indication would be up.

Note The values P Term, I Term, and D Term are the same as .PG, .IG, and .DG.

Note The .TK_OUT variable is a Boolean and will only have a value of 0 and 1. Due to how ExperTune interfaces with the
OPC server, it will only recognize the values 0 and -1.

Note MC is the abbreviation for Manual Command.

Note SC is the abbreviation for Setpoint Command. The operator can only write to this value if the valve is in Auto Local
mode.
Note MS is the abbreviation for Manual Set.

4. The PV engineering span varies per loop. The PV span is the range of the transmitter 90% of the time. For this specific
loop, the span would be 0-1500 mm (0-59.1 in).

5. All controller types in ToolboxST application version V03.3 or higher will be GE Mark* VIe controller, PID_MA
Parallel, or series.

6. The ExperTune application can collect tuning data as quickly as .02 sec. This is unnecessarily fast so the interval needs to
be slower.
7. The setup process for the configuration wizard is complete. Click Finished.

8. Confirm that all values displayed on the faceplate are correct.
9. Input the values for the CO.

10. Tune the loop (refer to the procedure, To tune a loop with OPC PID tuner).

7.5.2 Tune a Control Loop
➢ To tune a control loop with OPC PID tuner
This procedure can only be performed on an operating system. Take extreme

precautions and be aware of the disturbance that may be induced in an operating
plant.
Attention
1. From your computer, locate the OPC PID tuner file.
2. Open a loop faceplate that contains active data.

3. Allow the loop to stabilize at its current location.

Note There are multiple ways to tune a valve, although only one way is required to perform tuning analysis. All require the
manual change of the Command Output (CO) or Setpoint (SP) to induce a disturbance. Use steps 4-10 to tune a loop. Some
options may not be available depending on the loop.
Note If tuning a Mark VIe controller loop, the loop needs to be in Auto Local mode. Performing a Bump test in Auto Local
or Manual mode is known to produce the best tuning results.
4. Perform a Bump test in Auto Local mode.

a. Allow the response to remain stable for 1-2 minutes.
b. Make a rapid SP change either positive or negative. The SP change must be four times larger than the Process
Variable (PV) noise.
Note A greater change of SP relative to the noise is better, though four times the noise is the minimum.

c. Allow the loop to stabilize and remain stable for 1-2 minutes.
d. Stop archiving.
Note Performing a Bump test in Auto Local or Manual mode is known to produce the best tuning results.
5. Perform a Bump test in Manual mode.

a. Place the valve in Manual mode.
b. Allow the response to remain stable for 1-2 minutes.
c. Make a rapid CO change either positive or negative. The PV must change four times larger than the PV noise.
Note A greater change of PV relative to the noise is better, though four times the noise is the minimum.
d. Allow the loop to stabilize and remain stable for 1-2 minutes.
e. Stop archiving.

Note If tuning a Mark VIe controller loop, the loop needs to be in Auto Local mode.
6. Perform a Pulse test in Auto Local mode.

a. Allow the response to remain stable for 1-2 minutes.
b. Record the original value of CO, then make a rapid SP change either positive or negative. The SP change must be
four times greater than the PV noise.
c. Just as the PV responds to the movement in the valve, change the SP back to the original value as recorded in step b.
d. Allow the loop to stabilize and remain stable for 1-2 minutes.
e. Stop archiving.

7. Perform a Pulse test in Manual mode.
b. Allow the loop to stabilize and remain stable for 1-2 minutes.
c. Record the original value of CO, then make a rapid CO change either positive or negative. The PV must change four
times greater than the PV noise.
d. Just as the PV starts to respond to the valve movement, change the CO back to the original value recorded in step c.
e. Allow the loop to stabilize and remain stable for 1-2 minutes.
f. Stop archiving.

8. Perform a Double Pulse test in Auto Local mode.
Note If tuning a Mark VIe controller loop, the loop needs to be in Auto Local mode.
a. Allow the loop to remain stable for 1-2 minutes.

b. Record the original value of SP, then make a rapid SP change either positive or negative. The SP change must be
four times greater than the PV noise.
c. Just as the PV responds to the movement in the valve, change the SP to twice the value in the opposite direction.
This value should be on the other side of the original value.
d. Allow the loop to stabilize at it's current location, then change the SP back to the original value recorded in step b.
f. Stop archiving.

9. Perform a Double Pulse test in Manual mode.
b. Allow the loop to remain stable for 1-2 minutes.
c. Record the original value of CO, them make a rapid CO change either positive or negative. The PV must change four
times greater than the PV noise.
d. Just as the PV responds to the movement in the valve, change the CO to twice the value in the opposite direction.
This value should be on the other side of the original value.
e. Allow the loop to stabilize at it's current location, then change the CO back to the original value recorded in step c.
f. Allow the loop to stabilize and remain stable for 1-2 minutes.
g. Stop archiving.

10. Perform an Auto to Manual to Auto mode change.
a. Allow the loop to remain stable for 1-2 minutes.
b. Place the valve in Manual mode.
c. Make a rapid CO change either positive or negative. The PV must change four times greater than the PV noise.
d. Immediately place the valve in Auto Local mode.

f. Stop archiving.
11. Click Tune from archived data...
a. Select the file to tune.
b. Select the data range that has an ideal tuning condition.
c. Move the graph to one side of the screen, and click Analysis on the faceplate.

d. Several windows display, to allow further tune analysis.
The Control Loop Simulation window, displays the following graph showing the current and new (simulated)
response of the loop.
Four tabs in the top left corner of the graph can be selected, as follows:
• Setpoint plot displays the response if the SP is changed.

• Load upset plot displays the loop response if an external upset disrupts the steady state loop.
• Response to measurement noise displays the CO response to excess noise from the PV. This is important
because the CO should not respond very much to PV noise.
• Actual PV noise compared to simulated is used by ExperTune to convert the actual data to a function so
that it can run calculations. It is important to view this tab to verify that the simulated function matches the
actual PV response.
Additional features provided on the analysis windows include:
• Process frequency response displays both the actual and model frequency response for comparison. The
actual process data is usually noisy or jittery at higher frequencies. This plot can be useful to determine the best
model.
• PID recommended values indicates the PID recommended values with respect to the existing values. The
new values change as you modify different model settings. The tuner can use a filter or a Derivative Gain (DG).
Filters are not used for our current Mark VIe configuration. DG is rarely used because noisy transmitters may
cause problems with derivative.
• Process model is the model formula fit to the actual PV response.
• Performance summary displays the percent trade-off between performance and robustness. Valve travel and
reversals analysis is also included in the summary. Valve indices can be summarized based on setpoint, load, and
noise plots. Existing and new values are also included in the summary.
• Robustness plot displays the robustness of the current loop. The closer the red line gets to the lighter blue
region in the bottom left corner of the graph, the more unstable the loop. The further away the red line is from
instability, the slower the loop. The red line can be adjusted.

e. Adjust the PID settings if necessary. When a desirable PID setting is established, the new or proposed values will
already be in the appropriate cell. These values can be varied if further tuning is necessary.
f. After tuning is successful, click Download to download the new PID tuning and filter values to the controller.
Use caution when downloading new tuning settings. Actions should be taken to slowly
implement these changes.
Attention

7.6 How to Disable Network Services and Modify
Passwords in Mark* VI and Mark VIe Generation Controllers
While this procedure should not disrupt the normal operation of the controllers, it
should only be performed when the system is not actively controlling the plant. The
software used to perform this function is hosted on an HMI or workstation computer.
During the execution of commands, the tool automatically disables the computer’s
Attention firewall. The firewall will be left enabled after completion.
This document describes how to disable Telnet and File Transfer Protocol (FTP) network services and how to change the root
level password in Mark VI and Mark VIe generation controllers. Affected Mark VI generation includes Mark VI, EX2100,
and LS2100 controllers. Affected Mark VIe generation includes Mark VIe, Mark VIeS, Mark Ve, EX2100e, and LS2100e
controllers.
Simplified Control System Architecture View

Telnet and FTP are common software services that allow two operating systems to communicate with each other. Telnet
allows a user to log on and work on a remote computer. FTP is used to move files from one computer to another. Since the
Mark VI and Mark VIe controllers were developed using standard Ethernet communication software stacks, these services
exist in the controllers even though they are not necessary for normal operation.
To date, direct access to software services hosted on the controllers is administered through local password-protected user
accounts. When a controller is shipped, it contains a common, default password that should be modified by the end user to
improve resistance to unwarranted access.
Disabling Telnet and FTP and modifying the controller’s root password will increase the security posture of the control
system, but it can be more difficult to perform low level diagnostic and debugging operations. Once passwords have been
modified, only those authorized by the equipment owner will be able to log on. Similarly, once Telnet and FTP have been
disabled, this tool will be unable to modify the root password from the network.

7.6.1 Prerequisites
• The software tool used to perform this function is called svc_patch_1 and is intended to be installed and run on a GE
HMI or workstation computer, running either the Windows XP®, Windows 7, Windows Server 2003 R2, or Windows
Server 2008 R2 operating system with Microsoft® .Net Framework 3.5. (If .Net Framework 3.5 does not exist on the
computer, the tool will install it.)
• On some HMIs, svc_patch_1 can already be installed. If not, it can be ordered from GE using part number
DS224SVCPATCH01.
• The targeted controllers must be powered on and connected by Ethernet to the HMI.

7.6.2 Installation
➢ To install the software: Insert the CD into the computer and follow the prompts. If the prompts do not automatically
display, navigate to the CD and then the install directory and double-click the setup.exe file.
Select the install

option and select
Install. The Setup
wizard displays.
If the .Net
Framework 3.5
does not exist on
the computer, the
tool will install it
first.

On Windows 7 and
Windows Server 2008
R2 computers, the
installer will place the
tool in the directory C:
\Program Files(x86)
\ReqApps\ CTB\svc_
patch_1.
On Windows XP and
Windows Server 2003
R2 computers, the
installer will place the
tool in the directory C:
\Program Files
\ReqApps\CTB\svc_
patch_1.

7.6.3 Operation
➢ To start the tool:
From Windows 7 and Windows Server 2008 R2 computers, navigate to
Program files (x86)/ReqApps/CTB/svc_patch_1 and double-click svc_patch_1.exe.
Or
From Windows XP and Windows Server 2003 R2 computers, navigate to Program files/ReqApps/CTB/svc_patch_1
and double-click svc_patch_1.exe.
The tool will open and try to load a hosts file, if one exists in the directory C:\Windows\system32\drivers\etc. The hosts file
on a properly configured HMI contains all of the IP addressable components in the system, including the controllers. The tool
displays each component and its specified component name, if one is provided. If a desired controller is not in the list, add it
manually at the bottom by specifying the IP address and Device Name.
If a different hosts file is desired, use the File>Clear Click on the ellipses to navigate and select
command to delete the current entries. the desired hosts file.

The tool supports two main command buttons from the screen: Change Password, and Disable Services and Change
Password. The Enable Services button does not perform an action but directs the user to this How-to Guide. This is so
because when network services are disabled, the tool cannot communicate to the controllers; for additional information, refer
to the section in this document Re-enable Network Services. The Select All button allows the user to select all components in
the list to be targeted for the next command. The Unselect All button clears all checked boxes, preventing a command from
operating on any component in the list.
➢ To change the controller password

1. From the Select column, select the desired components by clicking the associated check boxes. Mass selections can be
made using the Select All and Unselect All buttons. Be sure to select only controller components that are currently
powered up. Commands to non-controller components or to powered-down controllers will fail.
2. Enter the controller Existing Password, New Password, and Confirm New Password. Press the Enter key to
accept the new passwords and activate the grayed command button.
Select Change Password to change the

password on the selected controllers.
When the command has completed, the status

will display in theLog window. The font colors
will display blue for success and red for failure.

If all controller passwords are currently identical, a single new password can be populated for all components.
Enter new password information on one Rescan verifies the Select the desired controller
device. Right-click the check box and controller’s status. check boxes and select
select Auto Update Passwords. Change Password.

➢ To disable Telnet and FTP, and change the controller password
1. From the Select column, select the desired controllers by clicking the associated check boxes. (Group selections and
auto populate can be used.)
2. Enter the controller Existing Password, New Password, and Confirm New Password. Press the Enter key to
accept the new passwords and activate the command buttons.
Select Disable Services and Change Password

to run the command on the selected controllers.

➢ To record the log contents to a file: Select Save and enter a filename.
The information is
saved as a text file.
The log window

contents may be
saved as a record of
the command
changes.

➢ To print the Log contents: Select the Print button and select a printer.

7.6.4 Re-enable Network Services
Once Telnet and FTP have been disabled in a controller, the tool cannot re-establish communication with the controller and
cannot re-enable network services or change the root password. Network services must first be restored on each controller
individually using a direct serial port connection. To connect the computer to a controller through a serial port, use the cables
and connectors listed in the following table.
Cables and Connectors for Controller Serial Port Connection

Controller Cables and Connectors
Cat5e (or better) Ethernet cable and controller serial connector (part # 121T6659P0001)
UCSC
Cat5e (or better) Ethernet cable and controller serial connector (part # 342A4944P1)
UCSA and UCSB
Cat5e (or better) Ethernet cable and controller serial connector (part # 342A4931ABP1)
UCCC
Serial cable (part # 336A3582P1) and mini serial cable adapter (part # 336A4929G1)
UCCA and UCVx
Alternately, the serial cable (part # 336A3582P1) can be replaced by a combination of a standard 4-pair
UTP cable and two connectors (part # 342A4931ABP1 and part # 342A4931ABP2).

➢ To re-enable Telnet and FTP Services
1. Configure a standard terminal emulator program with the following communication specifications:
a. UCSC, UCSB, and UCSA – 115,200 baud, 8–bit, no parity
b. UCCC, UCCA, and UCVx – 9600 baud, 8–bit, no parity
2. Connect the serial cable between the appropriate comport of the computer and COM1 of the controller.
3. Log on to the controller as the root account using the current password.
Note If this password has been changed from its default value, only those authorized by the equipment owner will be able to
log on.
4. Run the command cd /etc.

5. Run the command EnableTelnetFTP. This command is case-sensitive and must be entered as shown. You can now use
the tool to change root passwords, transfer files, or run shell commands again.

7.6.5 Troubleshooting
Issue Solution
Duplicate IP addresses The tool scans the host file for duplicate IP addresses. If any are found, they
must be corrected before those controllers can be targeted.
Difficulty connecting to a targeted controller Verify the controller is powered up and connected to the network. Verify the IP
address has been entered correctly.
Difficulty logging into a controller Verify the existing password for the target controller. Verify the existing
password has been entered correctly into the tool. Verify there are no active
Telnet sessions between the computer and the targeted controller.

7.7 How to Set Up a Remote ExperTune® PlantTriage
Tuning Server
The ExperTune® PlantTriage Control Loop Monitoring system tuning server may be configured using one of two options. The
first option consists of connecting the tuning server directly to the PDH and UDH network on a running plant. The tuning
server processes live plant data and performs control loop assessments based on configured algorithms. The second option
consists of placing the tuning server in a remote location to receive process data from the running plant.
In both cases, the tuning server performs control loop assessments using plant process data. However, the first configuration
option requires a tuning server and licensed software for every plant. Additionally, the existing site network must be modified
to accept the additional server on the network.
With the second option, a single tuning server is located at an engineering office to gather data from various plants.
Additionally, a remote server is located off site to collect Trender data and forwards it to the tuning server located at the
engineering office. The data is slightly compressed and the tuning server will have an offset of data. Depending on how often
the data is forwarded to the tuning server and played back, this could take as little as one day. This document provides the
necessary procedures to configure the remote tuning server located off site.
The remote tuning server obtains compressed Trender data, which is collected from Remote Service Gateways (RSG) or an
Onsite Monitoring System (OSM). The configured automation exports the Trender data to a .csv file, reformats it, and plays
the information back into the WorkstationST* application in real time. From there, the PlantTriage system connects to the
Object Linking and Embedding for Process Control (OPC®) server that is provided by the WorkstationST application,
GeCssOpcServer, and logs the control loop data. The following flowchart displays this process in detail.
Note The remote tuning server must have a server located on site to operate with the PlantTriage system.

Remote Tuning Server Data Process
Note Microsoft® Excel templates and other useful software may be obtained from the GE folders devoted to remote server
tuning.

7.7.1 Configure Recorder Collection
The Recorder collections on site need to be configured to continuously collect the multiple variables for each control loop.
Because some variables are not necessarily on the EGD, it may be difficult to obtain data for all of the variables. If possible,
variables should be added to the EGD so they may be recorded in a collection.
Note Sites with ControlST* software suite versions 3.3C and later use standardized PID_MA blocks, which have the
required variables already configured for the EGD. However, earlier versions do not have a standard. Each variable is
added to an EGD page manually. Also, the older versions of the ToolboxST* application do not have standardized naming.
For the purpose of this document, we will assume a version of 3.3C or later is being used.
➢ To configure Recorder collections

1. From the ToolboxST application, open the system (*.tcw) file.
2. From the Property Editor Features item, select Recorder.
3. Add all variables necessary for assessing each individual loop. It is strongly recommended to add deadbands. Otherwise,
the Recorder files will become extremely large.

The following table provides the needed variables per loop. These are the recommended deadbands for a simple loop (not
cascade); however, the deadbands may be adjusted if the data is insufficient or too large. Refer to the section, Software
Installation and .csv File Template Creation to create a template of variables that can be recorded on the RSG.
Recommended Deadbands for a Single Loop
Variable Description Deadband

{PidLoop}.PV Loop Process Variable Varies
{PidLoop}.SP Setpoint Same as .PV
{PidLoop}.CVO Command Output 0.02%
{PidLoop}.AUTO** Auto mode enabled Logged on Change
{PidLoop}.PG** Proportional Gain 0.00001
{PidLoop}.IG** Integral Gain 0.00001
{PidLoop}.DG** Derivative Gain 0.00001
{PidLoop}.H High Limit of Valve 0.02%
{PidLoop}.L Low Limit of Valve 0.02%
{PidLoop}.TK_OUT Valve is tracking Logged on Change
** The variable is preferred but not required. For ToolboxST version 3.3C or later, all of the above variables are automatically
configured on the EGD.
4. Perform the Build and Download the workstation device.
Note The RSG Recorder collection is configured to continuously collect data from the plant. If the Recorder collection stops
working properly, the remaining procedures in this document will not be able to operate properly.

7.7.2 Configure the Folder Structure
A folder structure needs to be configured for the remote tuning server.
➢ To configure the folder structure

1. From your desktop, locate the TrenderDataFromSite folder.
Note The Zip folder is the location to which the archived plant data will be copied to using the onsite auto copy script.

2. Contact the OSM to implement their automation copy scripting. This program compresses the .dcast files into a .zip file
and copies it to the remote computer.
Note Normally, the auto copy script is run daily, at night. However, different sites have different policies with lockbox
management. Some sites will only run the lockbox when requested. This script will not function properly unless the lockbox
is running. The remaining procedures in this document will be affected if continuous data is not received from the OSM.

7.7.3 Configure the Data
Configure the automation to create a compressed (.zip) file for the recorder collection .dcast files from the RSG. Software
tools copy the data from the onsite computer to the remote tuning server.
Note The RSG or OSM is accessed using the GE Energy Local Area Network (LAN). However, the remote tuning computer
also needs to be placed on the GE network so that data can be copied to it.
➢ To configure the OSM data from the RSG to the remote tuning server
1. On the remote tuning server, create the username as Data and assign a password.
2. Provide the username and password to the OSM.

3. Set up a similar folder structure on the remote tuning server.

7.7.4 Configure the Visual Basic Script for Automatic .csv File Creation
This section provides the procedure to create the folder structure for the Visual Basic Script (VBS). This script will massage
the Trender data into a .csv format, while replacing the site variable names with a standard name used for all loops on the
remote tuning server.
➢ To configure the VBS for automatic .csv file creation

1. Download the Recorder Data Sampling Tool (RDST) from the automation downloads webpage at the following location:
http://pgc.salem.ge.com/automation/Downloads.htm.
2. Install the RDST on the remote tuning server.
3. On the remote server, create a folder labeled Archive.

4. From the GE Library, locate the Remote_Tune_Sort_to_csv_rev1.vbs script.

5. Edit the .vbs file script to adjust for folder and name differences.
6. Go to the scheduled task for the .vbs file and configure the VBS.
Note The scripting will not run properly until the WorkstationST application is installed.
Note The VBS is run daily. Should the script crash continuously, the data will not be able to be used by the CSV to Live
import tool.

7.7.5 Software Installation and .csv File Template Creation
This section provides the procedure to install the necessary software and create the template .csv files that are used with the
import tool to initially configure the loops, baseline, and thresholds.
➢ To install software and create a template .csv file
Note This procedure needs to be performed only once per site setup or as additional loops are added.
1. Install the GE Energy ControlST software suite.

2. Install the PlantTriage system.
Note It is recommended that you also install Microsoft Office. Microsoft Excel is often used for .csv file management.
3. Modify the PlantTriage template .csv file.

a. From the GE Library, locate and open the Mk6ePTtemplate.xlsx spreadsheet.
b. Open the first sheet, PTLoops.
c. Follow the instructions provided in the red cell.
In the controller, the scale factor (SF) for each loop should follow the formula: . Normally, PVMax
and PVMin will be set to the transmitter ranges. However, that is not always the case. The PVMax and PVMin must be set so
that the calculated scale factor equals the online scale factor. From this example, you can assume the COMax-COMin =
100%. And, because the SF=0.04, you can calculate the PVMax-PVMin = 40,000.
d. Save the sheet as {Site}loops.csv (the file must be a .csv file).

e. Move the .csv file to the \TrenderDataFromSite\{Site} folder on the remote server.
4. Modify the cross reference template .csv file.
a. Open the Mk6ePTtemplate.xlsx spreadsheet.
b. Open the second sheet, Xref.
c. Follow the instructions provided in the red cells.
d. Save the sheet as {site}refInputs.csv.
e. Move the .csv file to the \TrenderDataFromSite\{Site} folder on the remote server.
5. Create the transfer file used for the CSV to Live import tool.
a. Open the \TrenderDataFromSite\{Site} folder on the remote server.
b. Create a new file called {Site}_TransferFile.csv.

7.7.6 Configure the Software
This section provides the procedure to configure the .tcw file and workstation, and create variables in the workstation to be
written from the CSV to Live import tool.
➢ To configure the .csv file
1. From the System Editor File menu, create a new .tcw file. A system network, UDH, is automatically added with the
system file.
2. Configure the REMTUN workstation.

3. From the OPC DA Server tab, double-click Client Driven Variables and select the {Site}refInputs.csv file.
Note Remove REMTUN from the name in Column B.
4. Perform the Build and Download the workstation.
Note A loopback adapter may need to be set up and configured with the UDH IP address 192.168.101.101.

7.7.7 Configure and Import Loops
This section provides the procedures to configure and import loops, units, baselines, and thresholds in the PlantTriage system.
7.7.7.1 Configure Loops and Units

Loop units must be configured before importing the PTLoops.csv file. Otherwise, the .csv import tool (CSV to Live) will not
create the loops with undefined units.
➢ To configure a loop and create units
Note The loop created in this example (NewLoop3) will be added only to create a new unit. As more loops are created with
this unit, NewLoop3 will be deleted but the new unit will remain.
1. From your desktop, double-click the PlantTriage Administration icon.

2. Repeat this procedure to create newly defined units (for example, M89X HRSG).
7.7.7.2 Delete Loops

This section provides the procedure to delete any unneeded loops that have be previously configured. The units created with
the loops will remain.
➢ To delete a loop: from your desktop, double-click the PlantTriage Administration icon.

7.7.7.3 Import Loops
Using previously created .csv file templates (refer to the section, Software Installation and .csv File Template Creation), the
ExperTune import tool allows easy .csv file import for configured loops.
➢ To import configured loops
1. From the Start menu, select All Programs.

Note This selection validates each variable and generates an alarm if the variable does not exist. The workstation device
must be downloaded and running to verify the variables.

2. Save the .csv file.

3. Multiple errors may occur and this takes time to troubleshoot. Repeat step 1 through 2 for multiple errors.
7.7.7.4 Import Baseline and Thresholds

The baseline and thresholds are parameters configured in relation to the performance assessments of the loop and help
diagnose the performance of a loop. A baseline is an indication of how a specific loop should ideally act. A threshold is an
indication of how much the loop deviates from the baseline.
Thresholds are configured for user indication of the loop performance with respect to a specific assessment. For example, a
specific loop will ideally have an assessment error of 0%, but the threshold for the loop allows for 5% error, that is, the
baseline is 0% and the threshold is 5%. This means as the loop’s error assessment approaches 5%, the loop will be deemed a
worse-performing loop. Conversely, as the assessment approaches 0%, it will be considered a better-performing loop. At 70%
difference between the baseline and threshold, the loop will be yellow. At 100% difference between the baseline and
threshold, the loop will be red. Therefore, if the loop has an error between 0% and 3.5% it will be green. If the error is
between 3.5% and 5% it will be yellow. If the error is beyond 5%, the loop will be red.
➢ To import configured baseline and thresholds
1. From the Start menu, select All Programs.

2. Click Next to import the file.

7.7.8 Playback Through CSV to Live
The Jar (CSVtoLivePlayer.jar) program file places the reformated (massaged) .csv files that were exported from the VBS into
the CSVtoLive folder. The .jar file copies the data one line at a time from the .csv file and pastes it in the TransferFile.csv file,
which is read by the WorkstationST application. How fast it copies each line depends on the configured Update Period. When
the .jar file copies the last line in the .csv file, it moves to the next .csv file in alphabetical order. This section provides the
procedure to set up the .jar file, view any errors found in the .csv file through the WorkstationST application, and log the data
into the PlantTriage system.
7.7.8.1 Configure the CSVtoLivePlayer.jar File

➢ Toconfigure the CSVtoLivePlayer.jar file
Note Refer to the section, Configure the Visual Basic Script for Automatic .csv File Creation, step 4, for the location of the
VBS strInterval value (blue circled area) used to configure the Update Period.

7.7.8.2 View Errors
➢ To view errors in the .csv file: from the Workstation application, open the WorkstationST Status window.

7.7.8.3 Log the Data
➢ To log the data into PlantTriage: from your desktop, double-click the PlantTriage Administration icon.

7.8 How To Use the ExperTune® PlantTriage Control Loop
Monitoring System
The PlantTriage Control Loop Monitoring System provides data analysis and control loop tuning through an Engineering or
Web interface. Both interfaces offer various features to view assessments, access archived trends, and tune individual loops.
The Engineering interface is mainly used for control loop setup and loop assessment configuration. The Web interface
provides simplified viewing. This document describes the most commonly used features provided in both interfaces.
Note For more information relating to the PlantTriage system, refer to the instruction manuals provided with the
ExperTune® application located at C:\xtune\PT\manual or C:\xtune\common.
7.8.1 User Account Access

To access the Engineering or Web interface, an administrator must set up user accounts and assign administrative or
maintenance access permission levels. Using the PlantTriage Administrator tool, the administrator can start and stop services,
configure the log directories, manage users, create user assessments, and such.
➢ To set up user accounts and access permissions: from your desktop, double-click the PlantTriage system
icon.

Note Individual users may have different permission levels.
7.8.2 Engineering Interface

The Engineering interface enables the administrator to configure and assess control loops. The Administration window
provides the following features for the user to perform these operations:
• New Loop
• Loop Properties
• Unit Operations Manager
• Display Group Manager
• New List
• Open List
• Process Data Trend
• Assessment Trend
• Open Saved Trend
• Set Baseline and Thresholds
• Process Model Active Model Capture Technology (AMCT)

Administration Window
New Loop displays the New Loop wizard, which provides the process to add a new control loop and loop units to the
PlantTriage system. New loops may be added individually or multiple loops may be added at one time. The most efficient
way to add multiple loops is through the .csv file import tool.
Note Refer to the PlantTriage Help file, Overview of ExperTune Import Program, for more information on bulk imports.

Loop Properties displays the current configuration for existing loops. Use the until and to dates to filter and search for
specific loops. The Structure, Process, Misc, and 6 Sigma tabs are not required for initial setup; however, these are beneficial
in overall loop assessment and for potential improvements.
Loop Properties
Unit Operations Manager is used for overall unit configuration. The Unit Operations Manager icon enables the user to
manage which units contain which loops.
Note A unit is not automatically created using the .csv file import tool. The user must manually add a new unit before using
the ExperTune import tool.
Unit Operations Manager

Display Group Manager displays loops divided into specific groups, which depends on the process a loop is trying to
control and the unit over which it presides. The Display Group Manager icon enables the user to configure the loop unit as a
Pressure, Temperature, Level, Flow or pH loop. More groups are available, however these are the most common. New groups
may be added with user-specific names. This feature, as well as other features discussed in this document, allows the user to
organize control loops.
Display Group Manager

New List offers the capability to organize loops by specific criticality. The New List icon enables the user to customize lists
for quick access to crucial loops. The following figure displays loops prioritized using the Harris assessment. The Harris
assessment is a good indicator of loops that need to be more efficiently tuned. Save the list view so that it can be accessed
later.
Prioritized Loop List

Open List displays a pre-configured loop list. Using the Browse button, locate the .ppl file to access a pre-configured loop
list on your computer.

Process Data Trend allows the user to select a loop for which to view archived Trender information. This viewer displays
a historical trend of the following:
• Process Variable (PV)-white

• Controller Output (CVO)-green
• Setpoint (SP)-yellow
Although the PlantTriage system automatically detects tuning opportunities, the process trend allows the user to search
archived data as a troubleshooting tool or to view locations for potential tuning. The process trend also allows the addition of
other variables; loop assessments or other loop properties can be added to this view. Save the trend view so that it can be
accessed later.
Process Data Trend View

Assessment Trend displays an archived trend of the specific loops similar to the Process Data Trend. However, the
assessment trend only displays historical assessment information. The Assessment Trend and Process Data Trend can be
important toosl for troubleshooting loop issues. Save the trend view so that it can be accessed later.
Assessment Trend View

Open Saved Trend displays a pre-configured trend view. Using the Browse button, locate the .tun file on your computer to
access a pre-configured trend view.

Set Baseline and Thresholds displays the configured baselines and thresholds for each control loop. The baseline and
thresholds parameters are configured in relation to the performance assessments of the loop and help diagnose performance
issues. A baseline is an indication of how a specific loop should ideally act. A threshold is an indication of how much the
loop deviates from the baseline. The baselines and thresholds notify the user when a loop is performing outside its thresholds.
Because each loop in a plant can be drastically different, the baselines may differ. Based on the type of loop (such as flow,
gas, and so forth), the PlantTriage system can easily place initial values for each loop. However, due to the specific operation
of the Heat Recovery Steam Generators (HRSG) and Balance of Plant (BOP) operation, many of the assessments are not
needed.
Note Refer to the provided Microsoft ® Excel spreadsheet, loop_assesments.xls, containing the recommended initial values
for specific loops. Depending on plant configuration, tuning, operation, and management requirements, these values may
change. These values do not affect loop operation; they are solely for indication to the user that the loop needs to monitored
due to a high threshold assessment.
Baselines and Thresholds

After troubleshooting valve assessment issues, a high threshold indication for a loop does not always require tuning to fix the
problem. An unhealthy indication for a loop may be resolved using the following options:
• Adjustment of baselines and thresholds if valve control is well within acceptable limits
• Finer tuning of valve to eliminate lag or oscillation (a high Harris assessment means the valve needs tuning)
• Lubricate or replace the hardware in the valve if the loop is not responding as desired
• Adjustment other valve parameters
Note The Process Interactions Map in the Web interface displays loop interaction. Refer to the section, Web Interface for
more information.
Process Model Active Model Capture Technology (AMCT) captures process models in normal operation. The
PlantTriage system automatically detects potential tuning models collected from the process data.As the loop operates (in
Manual or Automatic mode), the system recommends updated tuning constants that may increase the efficiency and speed of
the loop.
Process Model (AMCT)

The PlantTriage system only recommends new Proportional Integral Derivative (PID) tuning constants if it finds an adequate
model in the process. The model must meet certain requirements before the system performs any analysis.
Note Even if a model meets the requirements to be considered an adequate model, the PlantTriage system assesses the
quality of the model on a 1-7 scale. It is recommended to only use a model with 1 or 2 quality value for reliable tuning. If
tuning must be performed on a loop and there are no 1 or 2 quality models, then a setpoint (SP) change or manual valve
command (CVO) change must be induced to offer tuning recommendations.

Model Collected from the AMCT
7.8.3 Web Interface

The Web interface allows simplified assessment and archived trend viewing. Users that have been assigned access privileges
can log on to the Web interface located at the following link: http://localhost. Upon initial logon, the PlantTriage system
displays training material to assist the user with system use. Each activity has an attached video that takes approximately 5
minutes to upload. The videos are beneficial for understanding the PlantTriage system and are strongly recommended. A
reminder page displays every time the user logs on until the training has been completed.
Note The Web interface access link provided in this document will take the user to the log on page only if the user has the
PlantTriage software downloaded on their computer.

The Web interface offers numerous features to provide plant operation assessment and viewing. Features include:
• PlantTriage Overview
• Loop Health
• Key Assessments
• Dashboards
• Process Interaction Map
• Interaction Hot Spots
Note Refer to the PlantTriage Help and Index for further details. Both are accessible from the Web interface.
PlantTriage Overview displays a brief summary of overall plant health. It organizes control loop health into individual
units and displays the loops that deviate from their baseline and thresholds. Loop health is calculated using the key
assessments from the baseline and thresholds configured from the Engineering interface.
Note Refer to the PlantTriage Help file, the item, Key Assessments Measuring Loop Health, and the section, Engineering
Interface for further details.
PlantTriage Overview
The left side of window provides items for quick access to dashboards, various reports, loop diagnostics, notes, trends, and
advice. Although there are vast amounts of information, the individual loop dashboards offer the most valuable information
when reviewing a control loop.

PlantTriage Overview Screen Dashboard Templates
The dashboard Treemap units display the entire plant view and each individual loop’s health based on the baseline and
thresholds that have been configured.
Unit Operations Treemap (Loop Health)

Loop Health is based on key assessments that are selected for a control loop. A valve is considered a poor performer (bad
loop) due to a bad key assessments value. For example, the loop HRH_SH_ATTEMP_IN has a health rating of 92.81. The
plant view displays good and bad loops per the loop health, which is indicated by color (refer to the following figure). Loop
health colors are defined as follows:
• Green indicates that the loop is performing properly.

• Red indicates a poorly performing loop that should be further investigated.
• Grey indicates that no data has been collected for that loop.
Note
Plant View Displaying Loop Health

Key Assessments may be viewed for each configured control loop. Key assessments are selected during loop
configuration using the Engineering interface.
➢ To view key assessments for a loop

1. From the Plant View, click a loop.
Note For this procedure, we will use HRH_SH_ATTEMP_ as an example. The following figure displays the loop report
for the selected loop. The report indicates that the average absolute error is the leading cause for concern on this valve. Upon
examination, it can be deduced that either the valve is grossly out of tune, or the threshold for Avg abs error is inaccurate.
Loop Key Assessment Values

2. Click the Process Variable Trend to explore archived PV, SP, and CO trend data. The Web interface allows interaction to
change ranges, adjust times, and export to Excel.
Process Variables Trend for HRH_SH_ATTEMP_IN

The lower part of the trend indicates that the setpoint is 50° above the PV, while the CO is 0%. When the CO is at 0%, the
loop should be in a non-normal mode. During that time, Average Absolute Error (Avg abs error) should not be calculated.
However, the error was calculated because the proper modes were not configured correctly.
Loop Controller Mode Configuration

3. From the Engineering interface, configure the loop modes.
Dashboards display loop detail, including a complete analysis of a controller or plant area in a single window, and enable
the user to configure and filter individual loops. The individual loop dashboards display loop detail, which includes a
complete analysis of a controller or plant area in a single window. This enables to the user to quickly identify areas for
improvement. Dashboards may be customized per loop and are easily edited using the Dashboards tab.

➢ To view more information about dashboards: from the Web interface toolbar (located in the top left corner of the
screen), select Help.
Dashboard Loop Detail

Process Interaction Map summarizes the cross-correlation of the PV on a single control loop against the PVs of other
loops. The user selects the loop to analyze, as well as the set of loops to correlate it against. Process Interaction mapping can
assist with troubleshooting by locating the source of a problem with a control loop. The following figure displays a Process
Interaction Map chart. Each row in the chart represents one control loop. A band of color indications is displayed in each row.
The left-to-right scale displays the lead or lag relationship between the loops. If the loop name on the left leads the loop at top
of the graph, then the strongest colors are displayed on the right side of the chart. Conversely, a loop that lags behind the loop
at the top of the graph, then the stronger color blocks are displayed on the left side of the chart.
Process Interaction Map Chart

Interaction Hot Spots provide an overview of interactions across a number of loops to assist the user with troubleshooting
by locating the source of a problem with a control loop. In most process plants, there are interactions within unit operations,
as well as between unit operations. Interactions may be cyclical or non-cyclical. A list of all selected loops is displayed along
the left and top edges of the Interaction Hot Spots diagram (refer to the following figure). Interaction between loops is
indicated in blocks of colors, defined as follows:
• Red blocks indicate a strong interaction

• Yellow blocks indicate a weak interaction
• Green blocks indicate no interaction
When the user clicks in the interaction block, two windows open and display the process interaction of the two loops.
Note The Process Interaction Map represents the correlation between two control loops; this does not necessarily mean
cause and effect.
Interaction Hot Spots Diagram

7.9 How To Use Norton Ghost™ 9 to Backup and Restore
Hard Disk Drives
Norton GhostTM 9 is used to make backup images of the hard disk drive on some CCS-based HMIs and Historians running
Windows XP® and on some Dell® and HP® computers running Windows XP and Windows® 2000. These HMIs and
Historians use Roxio Easy CD Creator® to make backups of folders.
This document contains three procedures:
• Creating a backup image

• Restoring a hard disk drive from a backup image
• Deleting and renaming a drive letter
7.9.1 Prerequisites
The backup and restoration of a hard disk drive requires the following:
• Norton Ghost 9
• Roxio Easy CD Creator or other CD and DVD creation program
• Windows XP or Windows 2000

7.9.2 Creating a Backup Image
Tip � Be sure to label the disk with the disk number, date, and 3V number of the HMI or Historian.
Note The backup is created while Windows is running. Close all open programs before starting Norton Ghost 9.
Note When backing up to a CD or DVD, if a blank disk is not inserted into the CD/DVD drive, the Backup Wizard will
appear to be creating a backup image for several minutes before displaying a message asking for a disk to be inserted.
➢ To create a backup image

1. Insert a blank CD or DVD into the CD/DVD drive.
2. From the Windows XP Start menu, select Programs, Norton Ghost, and Norton Ghost. (From the Windows 2000
Start menu, select Programs, Norton Ghost, and Norton Ghost.) The Norton Ghost 9 window displays.
3. From the options displayed, select Backup Drives to display the Backup Wizard.
4. Click Next.
5. Select the drive (either C: or E:) to backup.
Note Do not backup more than one drive on a backup disk set.
6. Select Recordable CD or DVD drive.

7. Click Next.
8. Select Verify Backup Image after creation.
9. Enter a Description if desired.
10. Click Next and click Next again.
11. Click Close.
12. Remove the last CD or DVD from the CD/DVD drive and store the backup image CDs in a secure place.
7.9.3 Restoring a Hard Disk Drive from a Backup Image

When restoring a new or reformatted hard disk drive, restore the C: drive first and then restore the E: drive.
Before restoring a hard disk drive, note the drive partitions that have letters assigned and those that do not. If the original hard
disk drive cannot be accessed, get this information from another HMI or Historian of the same type and configuration as the
one being restored. If another HMI or Historian is not available, open a support case and include the 3V number of the HMI
or Historian in the case notes.
Windows sometimes assigns drive letters to drive partitions that did not originally have drive letters, and re-arranges the drive
letters of the drive partitions that did have drive letters assigned. After restoring a hard disk drive, verify that all drive
partitions have been assigned the correct letter (and any partition that does not need a drive letter has not been assigned one).
Refer to the procedure Deleting and Renaming a Drive Letter if any drive letters are incorrect.
If a backup image is corrupt or not available, the hard disk drive can be restored to a bootable state by using the distribution
disk(s). The Windows 2000 distribution disk requires a GE Universal Distribution Floppy Disk. Both disks are part of the
original HMI or Historian shipment. The Windows XP distribution disk is bootable and does not require the GE Universal
Distribution Floppy Disk. The distribution disk is a part of the original HMI or Historian shipment.

➢ To restore a hard disk drive from a backup image
1. Insert the Norton Ghost 9 Install CD into the CD/DVD drive and restart the computer.
Note It may be necessary to enter Setup and change the boot device order so that the CD/DVD drive is before the hard disk
drive.
2. When instructed, press a key to start from the CD. The Starting SymantecTM Recovery Disk window displays (this
might take several minutes to load).
3. The License Agreement window displays. Click Accept.
4. The Symantec Recovery Disk window displays. From the Do you want to start network services box, select
No.
5. Select Advanced Recovery Task.
6. Select System Restore.
7. Select Restore Drives.
8. Click Next.
9. Select Single Drive (refer to the paragraph at the beginning of this section for information regarding new or reformatted
hard disk drives).
10. Click Next.
11. To allow the loading of information into memory to complete, wait one minute and then remove the Norton Ghost 9
Install CD.
12. Insert the first disk of the backup set and wait one minute.
13. Click Browse. If this step fails, insert the Norton Ghost 9 Install CD and repeat this procedure starting at step six.
14. Locate and select the Backup Image File.
15. Click Open.
16. Insert the last disk of the backup set when requested.
17. Insert the first disk of the backup set when requested.
18. Click Next.
19. Click Next.
20. When restoring the C: drive, select all check boxes. When restoring the E: drive, select the Verify backup image
before restore and Check for file system errors before restore check boxes.
21. Click Next.
22. Click Finish.
23. Click Yes. The System Restore Wizard runs to restore the hard disk drive.
24. When the operation is complete, insert the Norton Ghost 9 Install CD.
25. If another hard disk drive is being restored, repeat this procedure starting with step six.
26. If another hard disk drive is not being restored, select Back, Exit, and click Yes.
27. Remove the Norton Ghost 9 Install CD.
28. Verify that all drive partitions have been assigned the correct letter (and that any partition that does not need a drive letter
has not been assigned one). Refer to the procedure Deleting and Renaming a Drive Letter if any drive letters are
incorrect.

7.9.4 Deleting and Renaming a Drive Letter
After restoring a hard disk drive, verify that all partitions have been assigned the correct letter (and that any partition that does
not need a drive letter has not been assigned one). If any drive letter is incorrect, delete or rename it as follows:
➢ To delete or rename a drive letter

1. From the Start menu, select Control Panel, Administrative Tools, and Computer Management to display the
Computer Management window.
2. Select Disk Management to display the disks and volumes.
3. Right-click the drive partition (such as D:) and select Change Drive Letter and Paths to display the Change Drive
Letter and Paths dialog box.
Note Delete drive letters from partitions that should not have them first.
4. Select Add, Change, or Remove (in Windows 2000, select Add, Edit, or Delete) as necessary. Reboot the computer
after each change.
5. Repeat steps one through four until the drive partitions have their original drive letters.

7.10 How to Use Norton Ghost™ 10 to Backup and
Restore Hard Disk Drives
Norton Ghost 10 is used to make backup images of the hard disk drive on some CCS-based HMIs and Historians running
Norton Ghost provides several methods for restoring files/folders or complete drives from a backup image. If the computer is
able to run Windows, you can recover either selected files/folders or the complete drive. If the computer is unable to start
Windows, or if the operating system prevents a restore operation, you can restore using the Symantec™ recovery
environment.
This document contains six procedures:
• Running the chkdsk program

• Testing/verifying the backup image
• Recovering selected files/folders from a backup image using Windows
• Recovering a complete backup drive using Windows
• Recovering a complete backup drive in the Symantec recovery environment
• Norton Ghost 10
7.10.2 Running the Chkdsk Program

Before backing up a hard disk drive, run the chkdsk program to identify and correct errors on the drive.
Note The NetworkX device and Crypkey License service are stopped during this procedure.

➢ To run the chkdsk program

2. From the Start menu, select Control Panel, Administrative Tools, and Services to display the Services window.
3. From the Windows XP Start menu, select All Programs and Command Prompt. (From the Windows 2000 Start
menu, select Programs and Command Prompt.)

4. Enter the command chkdsk /r and press the Enter key. Enter Y to select the restart option and restart the computer.
5. The chkdsk program runs during the computer restart. When complete, set the NetworkX device startup type to System
and the Crypkey License service to Automatic.
6. Restart the computer.
7.10.3 Creating a Backup Hard Disk Drive Image
Note Before creating a backup image, check that no disk defragmenting software or disk partitioning software such as
Norton PartitionMagic® is running.
Note Before creating a backup image, run the chkdsk program as described in the section, Running the Chkdsk Program.
Note After creating the backup image, verify/test the image as described in the section, Verifying/Testing the Backup Image.

1. From the Windows XP Start menu, select Programs, Norton Ghost, and Norton Ghost. (From the Windows 2000
Start menu, select Programs, Norton Ghost, and Norton Ghost.) The Norton Ghost window displays.

2. As each CD/DVD is filled during the backup process, Norton Ghost requests new (writable) media. Insert a new
CD/DVD and click OK.
3. Upon completion of the backup, a completion message displays below the progress bar in the Progress and
Performance window. Verify the backup was created successfully as described in the section, Testing/Verifying the
Backup Image.
4. Remove the last CD or DVD from the CD/DVD drive and store the backup image CDs in a secure place.

7.10.4 Testing/Verifying the Backup Image
The backup image can be verified by either of two methods:
• By browsing the contents of a recovery point to make sure desired files are present.
• By reviewing the event log for information about the backup, as well as other information and error messages.
➢ To browse the contents of a recovery point
♦ Open Norton Ghost

➢ To review the event log

7.10.5 Recovering Selected Files/Folders from a Backup Hard Drive Image
Using Windows
➢ To recover selected files and folders using Windows
♦ Open Norton Ghost

7.10.6 Recovering a Complete Backup Drive Using Windows
➢ To recover a complete backup drive using Windows
Note Close all other programs when performing a complete drive backup.
1. Open Norton Ghost.

Note Select Express to let Norton Ghost detect the restore drive destination automatically.

2. Check the drive to verify that all data is present.
Note When you recover a drive, all data on the drive being recovered is replaced by the data contained in the selected
recovery point. Any changes made to the drive after the selected recovery point was created (such as the creation of a new
file) are not recovered.
7.10.7 Recovering a Complete Backup Drive in the Symantec Recovery

Environment
When performing this procedure:
• The Norton Ghost 10 product (installation) CD is required.

• The computer must be configured to start from the CD drive.
• The computer must have a minimum of 256 MB of RAM.
• Only one partition (a C: drive, a D: drive, an E: drive) should be restored at a time.
➢ To recover a complete backup drive in the Symantec recovery environment

1. Insert the Norton Ghost 10 product CD into the computer’s media drive. Restart the computer from the CD to start in the
Symantec recovery environment. (Refer to the Norton Ghost 10.0 User’s Guide if you experience problems starting in the
Symantec recovery environment.)
Note This may take more than 15 minutes.
2. When the start to the Symantec recovery environment is complete, the following panels are displayed:
• Recover
• Analyze
• Scan

3. Click to select the Analyze panel for fixing any errors on the disk prior to starting the recovery.
4. From the Analyze panel, click Check Hard Disks for Errors. Select the drive you want to check (the drive being
recovered). Select the option Fix errors on disk and click OK.
5. Click to select the Recover panel and click Recover My Computer.
6. The recovery system starts looking for recovery points. Click Open another location and replace the Norton Ghost 10
product CD with the first backup CD/DVD of the respective drive. Browse and select the recovery point from the
CD/DVD.
7. Click Recover My Computer.
8. Select Express and proceed to step nine to allow the recovery system to automatically detect where the drive should be
restored. Select Custom and skip to step 10 if you want to modify where and how the drive is restored.
9. Check Reboot when finished to restart your computer when the recovery process is finished. Click OK > Yes to
begin the recovery process.
10. Click OK.
11. During the recovery process, insert the correct recovery CD/DVDs as requested.
12. After the recovery is complete, remove the last CD/DVD from the drive and let the system restart. Check that entire hard
drive has been recovered.

7.11 How to Use Norton Ghost™ 2003 to Backup and
Restore Hard Disk Drives
Norton Ghost 2003 is used to make backup images of the hard disk drive on some CCS-based HMIs and Historians running
This document contains four procedures:

• Testing the backup image
• Restoring a hard drive from a backup image
• Deleting and renaming a drive letter
• Norton Ghost 2003

7.11.2 Creating a Backup Image

Note The backup is created while Windows is running. Close all open programs before starting Norton Ghost 2003.
Note When backing up to a CD or DVD, if a blank disk is not inserted into the CD/DVD drive, the Backup Wizard will
appear to be creating a backup image for several minutes before displaying a message asking for a disk to be inserted.

2. From the Windows XP Start menu, select Programs, Norton Ghost 2003, and Norton Ghost. (From the Windows
2000 Start menu, select Programs, Norton Ghost 2003, and Norton Ghost.) The Norton Ghost 2003 window
displays.
3. From the options displayed, select Ghost Basic and then select Backup to display the Backup Wizard.
4. Click Next.
5. Select the drive (either C: or E:) to backup.
Note Do not backup more than one drive on a backup disk set.
6. Select Recordable CD or DVD drive.

7. Click Next.
8. If this is the first time Norton Ghost 2003 has been used on this computer, the Add Ghost Disk Identification dialog
box is displayed. Click OK. If Norton Ghost 2003 has previously been used on this computer, the dialog box is not
displayed.
9. Click Next, click Next, and click Next.
10. Read the Disaster Recovery dialog box and click Continue.
11. In the Backup Wizard window, select Run Now to create the backup image file. The computer is restarted in DOS
mode and the backup image file is created. Insert new CDs during this process as required. After the backup image file is
created, verify the integrity of the file as described in the following section, Testing the Backup Image.
7.11.3 Testing the Backup Image

➢ To test the backup image from DOS
1. Insert the first CD of the backup image into the CD drive and reboot the computer. Press any key to continue when
prompted. The computer starts in DOS mode and launches Ghost.exe. Press Enter to start the backup image integrity
check. The mouse is not active during the testing.
2. Use the arrow keys to select Check and press Enter. Use the arrow keys to select Image File and press Enter. The
Image File dialog box is displayed.
3. Use the Tab key to move to and highlight the Look In box. Use the arrow keys to select the CD drive and press Enter.
The backup image file is displayed and highlighted. Use the Tab key to move to the Open button and press Enter.
4. Use the Tab key to move to and highlight the Yes button. Press Enter to begin the integrity check.
5. Insert the backup image CDs as required and press Enter. When the integrity check is complete, use the arrow keys to
select Quit. Press Enter, and press Enter again.
6. Remove the last CD from the CD drive and store the backup image CDs in a secure place.
➢ To test the backup image from Windows

1. Insert the first CD of the backup image in the CD drive.
displays.
3. Select Ghost Advanced and then select Image Integrity Check to display the Image Integrity Check Wizard.
4. Click Next.

5. Click Browse, select the CD drive, and select the backup image file (*.gho).
6. Click Open, click Next, click Next, and click Next.
7. Review the task details and then click Run Now. The computer is restarted in DOS mode. Press any key when prompted
and then press Enter to begin the image integrity check. During the integrity check, insert the backup image CDs as
required. When the integrity check is complete, the computer restarts in Windows.
7.11.4 Restoring a Hard Disk Drive from a Backup Image

Before restoring a hard disk drive, note the drive partitions that have letters assigned and those that do not. If the original hard
disk drive cannot be accessed, get this information from another HMI or Historian of the same type and configuration as the
one being restored. If another HMI or Historian is not available, open a support case and include the 3V number of the HMI
or Historian in the case notes.
Windows sometimes assigns drive letters to drive partitions that did not originally have drive letters, and re-arranges the drive
letters of the drive partitions that did have drive letters assigned. After restoring a hard disk drive, verify that all partitions
have been assigned the correct letter (and that any partition that does not need a drive letter has not been assigned one). Refer
to the procedure Deleting and Renaming a Drive Letter if any drive letters are incorrect.
➢ To restore a hard disk drive from DOS

1. Insert the first CD of the backup image into the CD drive and restart the computer. Press any key to continue when
prompted. The computer starts in DOS mode and launches Ghost.exe. The mouse is not active during the restore.
drive.
2. Use the arrow keys to select Local and press Enter. Use the arrow keys to select Disk and press Enter. Use the arrow
keys to select From Image and press Enter.
3. Use the Tab key to move to the Look In box. Use the arrow keys to select the CD drive and press Enter. The backup
image file is highlighted. Use the Tab key to move to the Open button and press Enter.
4. Use the Tab key to move to the OK button and press Enter.
5. Use the Tab key to move to the OK button and press Enter.
6. Use the Tab key to move to the Yes button and press Enter to begin the restore.
7. Insert the backup image CDs as required and press Enter.
8. When the restore is complete, press Enter. The computer restarts in Windows.
10. Verify that all partitions have been assigned the correct letter (and that any partition that does not need a drive letter has
not been assigned one). Refer to the procedure Deleting and Renaming a Drive Letter if any drive letters are incorrect.
➢ To restore a hard disk drive from Windows

1. Insert the first CD of the backup image into the CD drive.
displays.
3. Select Ghost Basic. Click Restore and click Next to display the Restore Wizard.
4. Click Browse, select the CD drive, and select the backup image file (*.gho).

5. Click Open and click Next.
6. Select the destination partition and click Next.
7. Check Overwrite Windows and click Next, click Next, and click Next.
8. Review the Task Summary, click Run Now and click OK. The computer restarts in DOS mode.
9. Press any key when prompted.
10. Press 1 and press Enter. The computer restarts.
11. Press 1 and press Enter to begin the restore. During the integrity check, insert the backup image CDs as required. When
the integrity check is complete, the computer restarts in Windows.
12. Insert the backup image CDs as required and press Enter.
13. When the restore is complete, press Enter. The computer restarts in Windows.
15. Verify that all partitions have been assigned the correct letter (and that any partition that does not need a drive letter has
not been assigned one). Refer to the procedure Deleting and Renaming a Drive Letter if any drive letters are incorrect.
7.11.5 Deleting and Renaming a Drive Letter

After restoring a hard disk drive, verify that all partitions have been assigned the correct letter (and that any partition that does
not need a drive letter has not been assigned one). If any drive letter is incorrect, delete or rename it as follows:
➢ To delete or rename a drive letter

2. Select Disk Management to display the disks and volumes.
3. Right-click the drive partition (such as D:) and select Change Drive Letter and Paths to display the Change Drive
Letter and Paths dialog box.
Note Delete drive letters from partitions that should not have them first.
4. Select Add, Change, or Remove (in Windows 2000, select Add, Change, or Remove) as necessary. Restart the
computer after each change.
5. Repeat steps one through four until the drive partitions have their original drive letters.

7.12 How to Use Acronis® True Image Home to Backup
and Restore RAID1 and Non-RAID1 Hard Disk Drives
Acronis® True Image Home software is used to make backup images of the hard disk drive on some CCS-based HMIs and
Historians running Windows XP® and on some Dell® and HP® computers running Windows XP and Windows® 2000. These
HMIs and Historians use Roxio Easy CD Creator® to make backups of files and folders such as the F: drive and PI archives.
Note Acronis True Image Home software should not be used to backup files and folders.
This document contains four procedures:
• Creating a backup hard disk drive image

• Validating a backup hard disk drive image
• Creating a bootable rescue CD
• Restoring a hard disk drive from a backup hard disk drive image
• Acronis True Image Home

Note Backup hard disk drive images made with Acronis True Image Home software version 10 can be used to restore a
redundant array of independent disks (RAID1) hard disk drive. However, a bootable rescue CD made using Acronis version
11, build #8070 or newer must be used. A bootable rescue CD made with Acronis version 10 will not boot a RAID1 hard disk
drive. To verify the software version, select Help and About from the toolbar. If the software is older than version 11, build
#8070, open a Support Case to get a copy of the upgrade software, activation serial number, and instructions. Include the 3V
number of the HMIs. If this is a SupportCentral case, include the site information.

7.12.2 Creating a Backup Hard Disk Drive Image
➢ To create a backup hard disk drive image

2. From the Windows XP Start menu, select All Programs, Acronis, and Acronis True Image Home. (From the
Windows 2000 Start menu, select Programs, Acronis, and Acronis True Image Home.) The Acronis True
Image Home window displays.
3. From the Operations menu, select Backup to display the Create Backup Wizard.
4. Select My Computer.
5. Click Next.
6. Select Disk 1 to backup the complete hard disk drive or select drive C or E to backup a partition (it has been found that
the best practice is to backup one partition at a time). Click Next.
7. An information dialog box displays. Click OK.
8. Select the CD/DVD drive, H:.
9. Enter a filename (such as H:\CRM1_SVR_C_Drive_07-17-2007) and click Next.
10. Select Create a new full backup archive and click Next.
11. Select Use default options and click Next.
12. Enter comments, if desired, and click Next.
13. Click Proceed to begin the backup process. Insert new CDs or DVDs during this process as required.
14. After the backup image file is created, verify the integrity of the file as described in the following section, Validating the
Backup Hard Disk Drive Image.
7.12.3 Validating the Backup Hard Disk Drive Image

➢ To validate the backup hard disk drive image
1. From the Acronis Operations menu, select Validate backup archive to display the Backup Archive Validation
Wizard.
2. Click Next.
3. Select the backup file (such as H:\CRM1_SVR_C_Drive_07-17-2007).
4. Click Next.
5. Click Proceed to begin the validation process.
6. When the validation process is complete, remove the last CD or DVD from the CD/DVD drive and store the backup
image CDs or DVDs in a secure place.

7.12.4 Creating a Bootable Rescue CD
➢ To create a bootable rescue CD
1. From the Acronis Tools menu, select Create Bootable Rescue Media to display the Acronis Media Builder.
2. Select Acronis True Image Home and click Next.
3. Insert a blank CD into the CD/DVD drive.
4. Select the CD/DVD drive and click Next.
5. Click Proceed to create a bootable rescue CD.
6. When the operation is complete, remove the CD and label it. Store the CD with the hard disk drive backup image CDs in
a secure place and/or make a copy of the disc and store it off-site.
7.12.5 Restoring a Hard Disk Drive from a Backup Hard Disk Drive Image
When restoring a hard disk drive that does not have existing C and E partitions, use the disks labeled Windows XP
Distribution CD (Disk 1 of 3, Disk 2 of 3, and Disk 3 of 3) first, or the disk labeled GE HMI Windows XP Standard Image
(DVD), to create a base image on the hard disk drive. The disks are included with HMIs when shipped to site.
Note To restore a RAID1 hard disk drive, a bootable rescue CD made using Acronis version 11, build #8070 or newer must
be used. A bootable rescue CD made with Acronis version 10 will not boot a RAID1 hard disk drive. To verify the software
version, select Help and About from the toolbar. If the software is older than version 11, build #8070, open a Support Case
to get a copy of the upgrade software, activation serial number, and instructions. Include the 3V number of the HMIs. If this is
a SupportCentral case, include the site information.
➢ To restore a hard disk drive

1. Insert the bootable rescue CD into the CD/DVD drive (refer to the section Creating a Bootable Rescue CD) and start the
computer.
drive.
2. Select Acronis True Image (Full Version). This may take several minutes to load.
3. Select Recovery.
4. Select Next.
5. Remove the bootable rescue CD from the CD/DVD drive and insert the hard disk drive backup image.
Note If the backup image has more than one CD or DVD, insert the last disk of the backup image set. Change disks as
instructed.
6. Browse to the hard disk drive backup image location.

7. Select the hard disk drive backup image file.
8. Select Next.

9. Select Disk 1 to restore the complete hard disk drive.
a. Select Next.
b. Select No, I do not want to resize partitions.
c. Select Next.
d. Select Disk 1.
e. Select Next.
f. Select Yes, I want to delete all the partitions on the destination hard disk drive.
g. Select Next.
h. Select No, I do Not.
i. Select Next.
j. Do not check Validate Backup Archive Before Restoration.
k. Select Next.
l. Select Proceed.
m. Select OK when the operation is complete.
n. Select Operation and then Exit.
o. The computer restarts in Windows.

10. To restore drive C only
a. Select C.
b. Select Next.
c. Select No, I do not want to resize partitions.
d. Select Next.
e. Select C.
f. Select Next.
g. Select Active.
h. Select Next.
i. Select Next.
j. Select Yes, I want to restore another partition or hard disk drive
k. Select Next.
l. Select MBR and Track 0.
m. Select Next.
n. Select Disk 1.
o. Select Next.
p. Select No, I do not.
q. Select Next.
r. Do not check Validate Backup Archive Before Restoration.
s. Select Next.
t. Select Next.
u. Select Proceed.
v. Select OK when the operation is complete.
w. Select Operation and then Exit.
x. The computer will restart.

11. To restore drive E only
a. Select E.
b. Select Next.
c. Select No, I do not want to resize partitions.
d. Select Next.
e. Select D (partition E will be labeled D).
f. Select Next.
g. Select Primary.
h. Select Next.
i. Select Next.
j. Select No, I do not.
k. Select Next.
l. Do not check Validate Backup Archive Before Restoration.
m. Select Next.
n. Select Next.
o. Select Proceed.
p. Select OK when the operation is complete.
q. Select Operation and then Exit.
r. The computer will restart.

GEH-6808 ControlST Software Suite

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GEH-6808 ControlST Software Suite

Uploaded by

Copyright:

Available Formats

GEH-6808N

ControlST* Software Suite

Revised: June 2019

© 2013 - 2019 General Electric Company.

We would appreciate your feedback about our documentation.

Instruction Guide GEH-6808N 3

4 GEH-6808N ControlST Software Suite How-To Guides

Instruction Guide GEH-6808N 5

Indicates a procedure or condition that, if not strictly observed, could result in

Indicates a procedure or condition that should be strictly followed to improve these

To prevent personal injury or damage to equipment, follow all equipment safety

To minimize hazard of electrical shock or burn, approved grounding practices and

To prevent personal injury or equipment damage caused by equipment malfunction,

8 GEH-6808N ControlST Software Suite How-To Guides

GEH-6808N Instruction Guide 9

10 GEH-6808N ControlST Software Suite How-To Guides

Introduction GEH-6808N Instruction Guide 11

12 GEH-6808N ControlST Software Suite How-To Guides

• Open the System Information Editor

ToolboxST Application GEH-6808N Instruction Guide 13

• ToolboxST User Guide for Mark* Controls Platform (GEH-6700)

2.1.1 Alarm Block Templates

14 GEH-6808N ControlST Software Suite How-To Guides

➢ To configure automatic alias names for a template

ToolboxST Application GEH-6808N Instruction Guide 15

16 GEH-6808N ControlST Software Suite How-To Guides

ToolboxST Application GEH-6808N Instruction Guide 17

➢ To add an alarm definition

18 GEH-6808N ControlST Software Suite How-To Guides

ToolboxST Application GEH-6808N Instruction Guide 19

➢ To display the analog alarm default alarm definitions

20 GEH-6808N ControlST Software Suite How-To Guides

➢ To configure alarm inhibit groups

ToolboxST Application GEH-6808N Instruction Guide 21

When a sound is selected in the Data Grid, properties include:

22 GEH-6808N ControlST Software Suite How-To Guides

2.1.8 Alarm Symbols

➢ To edit alarm symbols: from the Tree View, select Symbols.

ToolboxST Application GEH-6808N Instruction Guide 23

• Priority 1 Active Unacknowledged

• Priority 1 Active Unacknowledged

2.1.9 Alarm Configuration

ToolboxST Application GEH-6808N Instruction Guide 25

26 GEH-6808N ControlST Software Suite How-To Guides

➢ To assign an alarm to an EGD page

2.1.9.2 Configure an Analog Variable Alarm

ToolboxST Application GEH-6808N Instruction Guide 27

28 GEH-6808N ControlST Software Suite How-To Guides

ToolboxST Application GEH-6808N Instruction Guide 29

Right-click inside the block and

Right-click OUTPUT , and

The Connect Pin dialog

ToolboxST Application GEH-6808N Instruction Guide 31

➢ To assign the L and H limits to a variable

32 GEH-6808N ControlST Software Suite How-To Guides

Analog Alarm Variables

Alarm Type Variable Extension Description Enter Initial Value?

Deviation High .DH Deviation alarm No - Boolean

High .H High level alarm No - Boolean

High High .HH High High level alarm No - Boolean

Low .L Low level alarm No - Boolean

Low Low .LL Low Low level alarm No - Boolean

ToolboxST Application GEH-6808N Instruction Guide 33

Alarm Type Variable Extension Description Enter Initial Value?