Geh 6757

GE Energy GEH-6757B
WorkstationST* GSM 3.0

User Guide
These instructions do not purport to cover all details or variations in equipment, nor to provide for every possible contingency
to be met during installation, operation, and maintenance. The information is supplied for informational purposes only, and
GE makes no warranty as to the accuracy of the information included herein. Changes, modifications, and/or improvements to
equipment and specifications are made periodically and these changes may or may not be reflected herein. It is understood
that GE may make changes, modifications, or improvements to the equipment referenced herein or to the document itself at
any time. This document is intended for trained personnel familiar with the GE products referenced herein.
GE may have patents or pending patent applications covering subject matter in this document. The furnishing of this document
does not provide any license whatsoever to any of these patents.
This document contains proprietary information of General Electric Company, USA and is furnished to its customer solely to
assist that customer in the installation, testing, operation, and/or maintenance of the equipment described. This document
shall not be reproduced in whole or in part nor shall its contents be disclosed to any third party without the written approval of
GE Energy.
GE provides the following document and the information included therein as is and without warranty of any kind, expressed or
implied, including but not limited to any implied statutory warranty of merchantability or fitness for particular purpose.
If further assistance or technical information is desired, contact the nearest GE Sales or Service Office, or an authorized
GE Sales Representative.
© 2009 – 2010 General Electric Company, USA. All rights reserved.

Revised: 100903
Issued: 091120
* Trademark of General Electric Company

OPC is a registered trademark of The OPC Foundation.
Windows is a registered trademark of Microsoft Corporation.
To:
Readers Comments GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA
Fax: 1–540–387–8651
(GE Internal DC *278–8651)
We welcome comments and suggestions to make this publication more useful.

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

Detach and fax or mail.
....................................................................Fold here and close with staple or tape....................................................................
Place
stamp
_______________________
here
_______________________
_______________________
GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
........................................................................................Fold here first........................................................................................

Safety Symbol Legend
Indicates a procedure, condition, or statement that, if not

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

if not strictly observed, could result in damage to or
destruction of equipment.
Caution
Indicates a procedure, condition, or statement that

should be strictly followed in order to optimize these
applications.
Attention
Note Indicates an essential or important procedure, condition, or statement.
Tip Ä Provides essential information that is not normally defined in regular use but
from an experienced user.
A margin note is used to

emphasize a specific statement
or provide a reference.
To prevent personal injury or damage to equipment
Follow all GE safety procedures, LOTO, and site safety
procedures as indicated by EHS.
Warning
This equipment contains a potential hazard of electric

shock, burn, or death. Only personnel who are
adequately trained and thoroughly familiar with the
equipment and the instructions should install, operate,
or maintain this equipment.
Warning
Isolation of test equipment from the equipment under

test presents potential electrical hazards. If the test
equipment cannot be grounded to the equipment under
test, the test equipment’s case must be shielded to prevent
contact by personnel.
To minimize hazard of electrical shock or burn, approved

Warning grounding practices and procedures must be strictly
followed.
To prevent personal injury or equipment damage caused

by equipment malfunction, only adequately trained
personnel should modify any programmable machine.
Warning
Always ensure that applicable standards and regulations

are followed and only properly certified equipment is
used as a critical component of a safety system. Never
assume that the HMI nor the operator will close a safety
critical control loop.
Warning
Contents
Chapter 1 Overview ................................................................................................................ 1-1
Chapter 2 Configuration ........................................................................................................ 2-1
Enabling the GSM Feature..............................................................................................................2-1
Configuring the GSM Feature .........................................................................................................2-4
Scaling.............................................................................................................................................. 2-9
Online Downloads ............................................................................................................................. 2-10
Import/Export of Translation Tables ....................................................................................................... 2-11
DCS Signals ..................................................................................................................................2-13
GSM Redundancy .........................................................................................................................2-13
Periodic Reads and Receiving Alarms, Events, and SOEs ......................................................................... 2-13
Periodic Writes ................................................................................................................................. 2-13
Command Requests .......................................................................................................................... 2-14
How Page Health is Determined ........................................................................................................... 2-14
Error and Warning Messages........................................................................................................2-15
Chapter 3 Runtime.................................................................................................................. 3-1
WorkstationST Status of Features ..................................................................................................3-1
WorkstationST Additional Status.....................................................................................................3-2
Detail Log ........................................................................................................................................3-7
GSM Spy .........................................................................................................................................3-9
Client Summary View .................................................................................................................... 3-11
Per Client Views ............................................................................................................................3-12
Status Tab ....................................................................................................................................... 3-13
Periodic Data List ............................................................................................................................. 3-16
Tracing ..........................................................................................................................................3-18
Chapter 4 GSM Test Client .................................................................................................... 4-1
Sending Messages..........................................................................................................................4-4
Messages Received ........................................................................................................................4-6
Glossary of Terms ..................................................................................................................... 1
GEH-6757B Contents 1
Notes
2 Contents WorkstationST* GSM 3.0

Chapter 1 Overview
GE Energy Standard Messaging (GSM) provides a consistent external interface regardless
of internal protocols and data representations. Used by a Distributed Control System
(DCS) to communicate with the GE Turbine Control System, the DCS can receive alarms,
event and periodic data from GE Turbine controllers (such as the Mark* V, Mark Ve, Mark
V LM, Mark VI, Mark VIe, and Mark VIeS) as well as support writing periodic data or
commands to the GE Turbine controllers. There have been slight modifications to the
GSM Protocol over time. Refer to the following documents:
Document Number Document Name

GEI-100516 GE Industrial System Messages (GSM) for HMI Applications
GEI-100658 GE Energy Standard Messaging (GSM) 2.0 for HMI Applications
GEH-6760 WorkstationST* GSM 3.0 Application Guide
GEH-6757B Chapter 1 Overview User Guide 1-1

Notes
1-2 WorkstationST* GSM 3.0

Chapter 2 Configuration
The ToolboxST* application allows you to enable the GSM feature that runs in the
WorkstationST component. As a minimum, the only configuration that’s required for
GSM is to enable this feature.
Enabling the GSM Feature

Ø To enable the GSM feature
1. From either the System Editor Tree View or the Summary View, double-click
the WorkstationST component. The WorkstationST Component Editor
displays.
Note The EGD Configuration Server and the Alarm Server must be set to True in one
of the configured WorkstationST components. (It does not have to be the WorkstationST
component with GSM enabled).
Note The GSM server must have access to an Alarm Server. If the Alarm Server
is enabled on the same computer as the GSM Server, then it will use the local
Alarm Server. However, if the GSM server is supposed to get Alarms from another
workstation, configure the one to use.
GEH-6757B Chapter 2 Configuration User Guide 2-1

2. From the System Editor, double-click the ws2 component to display the
Component Editor.
Note If there is only one network in the system, the Unit Data Highway (UDH),
then use the UDH.

Configuring the GSM Feature
Ø To configure the GSM feature
The following items are configured from the GSM tab.
Default Measurement System is the measurement system that is used for scaling all of
the data transferred to and from a GSM client unless it is changed using a Connection
Option Request message.
Port is the Port Number used by GSM and it defaults to 768. If necessary, this port can
be edited.
Use Second Language Alarm Descriptions as Default If set to true, when the GSM
server sends alarms, digital inputs, and SOEs, it sends the second language description
instead of the primary language description. If a second language description is not
provided, the primary language description is sent.

Control Hierarchy:
Control Hierarchy is an optional means to define different control locations and pass
control between these locations. Control locations are defined, and then different elements
in the system are configured to only send commands if the current control location allows
it. In the past, elements in the system determined the control location by reading the
value of the control level variable, which in turn determined if they were allowed to
send commands to the turbine controller.
Today, most elements in the system, for example the HMI, no longer follow control
hierarchy. However, because actions through GSM could be initiated from an offsite
location, it still supports a simplified form of control hierarchy.
This simplified version of control hierarchy works as follows: In the controller

configuration, define a GSM Control Enable Boolean Variable and map it to an EGD
page. In the GSM configuration, enter a GSM Control Enable Boolean Variable for every
controller that is to be part of the Control Hierarchy. At runtime, GSM monitors the
Control Enable Variables. Before sending out any Alarm or Process Control commands
to a given controller, it checks to ensure the Control Enable Boolean Variable for that
controller is true. If a Control Enable Boolean Variable is not configured for a given
controller, whenever a command message is received from a DCS client it is always
sent to the controller.
Most of this simplified version of Control Hierarchy is a manual solution. The only parts
built into the product are:
• The ability in the ToolboxST application to configure the GSM Control Enable
Variable per controller
• GSM3 server monitoring the GSM Control Enable Variable (configured above) at
runtime and not sending any Alarm or Process Control Commands if a variable was
configured and yet its value isn’t true
Translation:
The translation tables allow a GSM client using GSM1 or GSM2 protocol to speak to the
GSM3 server. There are several differences between GSM1/GSM2 protocol and GSM3
protocol. For a complete list of differences, refer to GEH-6760, WorkstationST GSM 3.0
Application Guide. The following differences are relevant to the translation tables:
In GSM3 Controller Name, Point Name, and Alarm Descriptions in the ToolboxST
application can include any UTF-8 character, but GSM1 and GSM2 used ASCII encoding.
In GSM1 and GSM2, the alarm drop number was the key. In GSM3, the point name
is the key.
In GSM1 and GSM2, different sources of data supported different numerical data formats.
In GSM3, the GSM server returns the data in its native format as it is available from
the OPC DA server.
A translation table exists for each controller that requires one.

Ø To add a translation table

Tip Ä If this is a Mark V controller, set Points Must Be In Translation Table to True.
From Mark V controllers, every point must be scaled in order for the value to be in the
data type expected by older GSM clients. If necessary, change the Default Data Type. If
an older GSM client got its data from CIMPLICITY*, then it normally received the data
in a long Real format (an 8 byte IEEE floating point number). By setting the Default
Data Type, all variables returned to the GSM client are scaled to this data type without
requiring an individual entry in the translation table for each one.

Translation Table Column Headings
Column Name Description

Alarm Description The Alarm Description with any non-ASCII characters replaced with ASCII characters.
Alarm ID The Alarm ID (also known as Alarm Drop Number) that older systems used as a key instead
of the Variable Name.
ASCII Variable Name Short name (without controller prefix) for the variable, with any non-ASCII characters
replaced with ASCII characters.
GSM Client Data Type The DataType any GSM1/GSM2 protocol GSM clients expect for this variable.
GSM Minimum These are used to scale the data before it is sent out to the GSM client, or after it is read
from the GSM client.
GSM Maximum
Xopc – OPCmin Ygsm – GSMmin
OPC Minimum ———————– = ————————
OPCmax – OPCmin GSMmax – GSMmin

OPC Maximum
where Ygsm is the value to be sent to/from the GSM Client and Xopc is the value of the
variable in the OPC DA server. The scaling only takes place if either GSM Client Data Type
is set to True, or if Points Must Be In Translation Table is not set to True, but the Default
Data Type is set to True.
OPC Data Type The DataType of the variable in the OPC DA server. This is read only, for reference when
setting the scale factors.
Units The Units of the variable in the OPC DA server. This is read only, for reference when
setting the scale factors.
UTF8 Variable Name Short name (without controller prefix) for the variable, as used in the ToolboxST application.

Scaling
The relationship between Y (the value sent over GSM) and X (the OPC value) is linear.
This equation:
Xopc – OPCmin Ygsm – GSMmin

———————— = ————————
OPCmax – OPCmin GSMmax - GSMmin
can be converted into the slope intercept form:
y = mx + b
Where m = slope
b = offset
For the OPC value:
(OPCmax – OPCmin) OPCminGSMmax - OPCmaxGSMmin
Xopc = ————————– Yopc + ——————————————–

GSMmax – GSMmin GSMmax – GSMmin
For the value that is sent over GSM:
(GSMmax – GSMmin) OPCmaxGSMmin – OPCminGSMmax
Ygsm = ————————— Xopc + ——————————————–

OPCmax – OPCmin OPCmax - OPCmin
If all min and max values are zeros, a gain of 1 and an offset of zero are used.
Note The maximums and minimums are used as scale factors, not as limits to clamp
values. Instead, whatever the range of the given data type is, the value will be clamped
at that data types minimum and maximum. For instance, an unsigned 16 bit integer
will be clamped between 0 and 65535.

Scaling Example
OPCmax = 8.0 inches
OPCmin = 0 inches
The OPC variable is an IEEE float (in the ToolboxST application, referred to as REAL).
GSMmax = 65000
GSMmin = 0
OPC variable current value is 8.5.
The GSM data type is an unsigned 16-bit integer (in the ToolboxST application, referred
to as UINT).
65000 – 0 8 * 0 – 0 * 65000
GSMValue = ————– * 8.5 + ———————–

8 – 0 8 – 0
65000
GSMValue = ————– * 8.5 = 69062.5

8
GSM Value sent over GSM = 65535, clamped by the Maximum value of the GSM data
type.
Online Downloads
If the values in the GSM translation tables are changed and downloaded to a running
WorkstationST computer, then any new requests from the GSM client uses the new values.
However, if a Periodic Data Read or a Periodic Write Request was established before the
WorkstationST computer was re-downloaded, it will not use the new values unless the
GSM client re-sends the Periodic Data Read or Periodic Write Request message.

Import/Export of Translation Tables
The translation tables can be imported from, or exported to a .csv file. For a Mark V
controller, the.csv file contains all the points that are available from a Mark V controller.
Ø To import a translation table
Refer to GHT-200040, How to ♦ Locate and select the .csv file. For a Mark V controller, the one used by the GSM_L
Convert a Mark V Component utility. Click Open to import the file.
for Use in ControlST Systems
for additional information. Note The import adds rows to the translation table. Therefore, if the same .csv file
is imported twice, two rows display in the translation table for every line in the .csv
file. If the .csv file is the master file, delete all rows from the existing translation table
before importing to prevent duplication.
Tip Ä Use <ctrl><a> to select all the rows, and then delete.
Tip Ä The Undo button and Redo button work for the import.

Ø To export a translation table
♦ Locate and select the .csv file to export the translation too. Click Save.
Tip Ä Since the import and export functions are on a per controller basis, it facilitates
maintaining a common translation table amongst different controllers. When one
controller has all the desired values entered in the table, it can be exported and the
same file can be imported to another controller.

DCS Signals
The DCS needs to know the variables that are available over GSM and the scaling of those
variables. For Mark V controllers the GSM.CSV file (generated by the GSM_L utility)
provides the list of variables and their scaling. For a Mark VI controller, refer to the
Signal List report (Control System Solution toolbox) and for a Mark VIe controller refer
to a Variables report (ToolboxST) for the same information.
GSM Redundancy
There are three parts to GSM3 server redundancy:
• Periodic Reads and Receiving Alarms, Events, and SOEs

• Periodic Writes
• Command Requests
Periodic Reads and Receiving Alarms, Events, and

SOEs
For interchanges where the DCS reads information (data and alarms) from the GSM3
server, two or more WorkstationST computers can have the GSM feature enabled. A
DCS can have one or more clients connect into each of these GSM3 servers and request
alarms and data, and receive them.
Periodic Writes
Refer to GEI-100621, GE GSM3 also uses periodic writes from the DCS to points on the WorkstationST computer's
Energy WorkstationST* OPC EGD pages. In this case GSM3 redundancy piggy backs off of the WorkstationST
DA Server. Redundant EGD Produced Pages functionality. When redundancy is desired these Periodic
Write Points should be on the WorkstationST redundant EGD Pages.

When Periodic Writes are set up, they should always use WKS as the Controller Name, and
Point Names in the format WKS.PointName. Internally the GSM3 Server then translates
the WKS.PointName to ThisWorkstationSTsName.PointName before communicating with
the OPC DA server. This allows the DCS to use the same message content when talking
to two or more redundant GSM3 servers.
Refer to GEH-6706, ToolboxST The way the WorkstationST Redundant EGD Produced Pages functionality works, the
User Guide for WorkstationST. DCS can write to both GSM3 servers in a redundant pair. Only the WorkstationST
computer designated as having the primary produced page produces the page if the page is
healthy. (Refer to the section, How Page Health is Determined for additional information.)
A secondary produced page is produced by another WorkstationST computer if the primary
produce page is not heard for 3 periods. (Typically a consumer of the produced EGD page
will declare the page unhealthy after not receiving the page for 5 periods, so the consumer
never detects the page as unhealthy.) If the secondary again detects the production of the
primary page, it will stop data production. Like the primary, the secondary producer will
only produce the page if the page is healthy. Therefore, the WorkstationST EGD pages
should be architected such that points being written by the DCS system are on different
EGD pages than points being written by other components in the system. That way,
if connectivity is lost with the GSM3 server on the WorkstationST computer owning
the primary page, all writes to the page will stop, the page will go unhealthy, and the
WorkstationST computer owning the secondary page will begin producing the exchanges.
Command Requests
When the GSM3 server receives Command Requests from the DCS it always sends these
commands to the GE System (unless limited by Control Hierarchy). It is the responsibility
of the DCS to not send command requests to a primary and backup GSM3 server at the
same time.
How Page Health is Determined

EGD produced exchanges are healthy as long as any one of the exchange variables has
been written by a client within the time specified by the Health Timeout Multiplier
multiplied by the Period. (If the Health Timeout Multiplier default of 0 is left then the
exchange will begin life as healthy and will remain healthy.) If Address Zero Health is
true, only the variable at offset 0 will affect the health of the produced exchange.

Error and Warning Messages
When the build command is selected, errors or warnings in the GSM configuration display
in the WorkstationST Component InfoView Log tab. Double-click an error/warning to
display the location the error or warning occurs.
Description The OPC DA server feature must be enabled for GSM to work.
Possible Cause OPC DA server not enabled
Solution Enable the OPC DA server.
Description Device Name {0} is duplicated. Duplicate Device Names aren't allowed in
the GSM Control Hierarchy Table.
Possible Cause The same Device Name was entered more than once.
Solution Determine if one of the device entries is supposed to be a different device. If

not, determine which Control Hierarchy Enable signal is desired, and delete the other entry.
Description The Device Name in the GSM Control Hierarchy Table cannot be blank.
Possible Cause A Control Hierarchy Enable Signal was entered, but no device name
was selected.
Solution Either determine which device was intended for this signal and select it, or
delete this row from the Control Hierarchy table.
Description The variable {0} in the GSM Control Hierarchy is not reachable from this
WorkstationST. Do you need to make the device that owns this variable a referenced
device under the EGD tab?
Possible Cause The variable that was entered into the Control Hierarchy Enable
Variable field is not defined in the system, or is not accessible from this workstation.
Solution Determine if the variable has been defined somewhere. If the variable comes
from another component, make sure that:
• Variable was defined in that component.

• Variable was mapped to EGD page in that component.
• The component was built on a computer that is working online with the EGD Config
server so that their EGD page maps are available.
• This component is set up to consume pages from that component.
• This computer is working online with the EGD Config server to get the latest EGD
Map.
Description The variable {0} in the GSM Control Hierarchy needs to be a Boolean.
Possible Cause Data type is not a Boolean.
Solution Determine if the wrong variable was selected, or if the data type of the variable
needs to be changed.

Description The device {0} in the GSM Control Hierarchy is not defined in this system.
Possible Cause When selecting devices, a list of available devices in the system is
provided. After this device was selected, the device was renamed or removed from the
system, or the name was typed in instead of being selected from the list.
Solution Determine which device to use, or if this entry is no longer needed.
Description The Alarm Server to Use (under the WorkstationST General properties)
is blank.
Possible Cause If the GSM feature is enabled, it must have access to the alarms
in the system.
Solution Determine if the Alarm feature should be enabled on this workstation, or if

another workstation that already has the Alarm feature enabled should be used.
Description WK1 was selected for the Alarm Server to Use (under the WorkstationST
General properties) but this device needs to be a Workstation.
Possible Cause The Alarm Server To Use field provides a list of all workstations in
the system. It is possible the device type associated with this name was changed after
this value was selected.
Solution Determine which workstation should provide alarms to GSM.
Description The workstation WK1 is selected for the Alarm Server to Use (under
the WorkstationST General properties) but its: Alarm feature is NOT enabled; (where
the workstation Name is yours)
the system, not just workstations that have the Alarm feature enabled.
Solution Determine if the Alarm Feature should be enabled on the selected workstation,
or if a different workstation should be selected. To enable the Alarm Feature on another
workstation, open that workstation’s configuration, enable the Alarm Feature, and save its
configuration.
Description The workstation WK1 is selected for the Alarm Server to Use (under
the WorkstationST General properties) but its: Not on the Plant Network; (where the
workstation Name is yours)
Possible Cause If GSM is running on a different computer than the Alarm Server,
then both the computer hosting GSM and the computer hosting the Alarm Server must
be on the plant network.
Solution Open the configuration for the other workstation, add a Network Adapter that
resides on the plant network, make sure the Network Adapter is enabled and save the
configuration.

Description The workstation WK1 is selected for the Alarm Server to Use (under the
WorkstationST General properties) but its: On the Plant Network but the Plant Network
Adapter isn't enabled; (where the workstation Name is yours)
then both the computer hosting GSM and the computer hosting the Alarm Server must be
on the plant network. The Network Adapter must be enabled.
Solution Open the configuration for the other workstation, select the Network Adapter
that resides on the plant network, make sure the Network Adapter is Enabled and save the
configuration.
Description Cannot find file WK1\Device.xml to open and validate Alarm Server To
Use.
Possible Cause The other workstation’s device configuration file is not found on
this computer.
Solution Make sure the configuration files for the other workstation are on this
computer. If using the Configuration Management System this may require doing a Get
on that device.
Description The workstation WK1 is selected for the Alarm Server to Use (under the
WorkstationST General properties) but this device is not found in the system.
the system. It is possible that the device was removed from the system after this value
was selected.
Solution Determine which workstation should provide alarms to GSM.
Description This Workstation needs to be on the plant network since an Alarm Server
on a different workstation was selected to be used (under the WorkstationST General
properties).
then both the computer hosting GSM and the computer hosting the Alarm Server must
be on the plant network.
Solution Open the configuration for the workstation, add a Network Adapter that
resides on the plant network, make sure the Network Adapter is enabled and save the
configuration.
Description This workstation needs its plant network enabled since an Alarm Server
on a different workstation was selected to be used (under the WorkstationST General
properties).
then both the computer hosting GSM and the computer hosting the Alarm Server must be
on the plant network. The Network Adapter must be enabled.
Solution Select the Network Adapter that resides on the plant network, make sure the
Network Adapter is enabled and save the configuration.

Description The GSM Default Measurement System {0} is not defined in this system.
Possible Cause A measurement system was selected which was later deleted from
the system, or a measurement system was never selected, and the default value is not a
valid value in this system.
Solution Determine the correct measurement system for the default and select it from
the drop-down list.
Description UTF8 controller {0} is duplicated. Duplicate UTF8 controller names are
not allowed in GSM Translator.
Possible Cause The same UTF8 controller name was entered for more than one
device under the Translation branch.
Solution Determine if one of the duplicates should be renamed, or if one of the device
entries should be deleted.
Description The UTF8 controller name in the GSM Translator cannot be blank.
Possible Cause The UTF8 controller name was not entered after a new Device
Translation was added.
Solution Enter the UTF8 controller name.
Description ASCII controller {0} is duplicated. Duplicate ASCII controller names are
not allowed in GSM Translator.
Possible Cause The same ASCII controller name was entered for more than one
device under the Translation branch.
Solution Determine if one of the duplicates should be renamed, or if one of the device
entries should be deleted.
Description The ASCII controller name in the GSM Translator cannot be blank. If
there are no non-ASCII characters in the UTF8 controller name then just use that value.
Possible Cause The UTF8 controller name was not entered after a new Device
Translation was added.
Solution Enter in the ASCII controller name. This is the name the GSM client using
GSM1/GSM2 protocol uses when referring to this device.
Description The device {0} in the GSM Device Translator is not defined in this system.
Possible Cause When selecting devices, a list of available devices in the system
is provided. After this device was selected it was either renamed or removed from the
system, or the name was typed instead of being selected from the list.
Solution Determine the correct device, or if this entry is no longer needed.

Description The ASCII controller name {0} in the GSM Device Translator contains
a non-ASCII character.
Possible Cause There is a non-ASCII character in the controller name.
Solution Edit the field to replace the non-ASCII characters with ASCII characters.
Description Alarm ID {0} is duplicated. Non-default (default is 65535) duplicate

Alarm IDs are not allowed in any given GSM Device Translation Table.
Possible Cause There is a duplicate Alarm ID in the Translation Table.
Solution Determine the correct Alarm ID for this point. If this entry in the Translation
Table is to translate a UTF8 variable name to an ASCII variable name, or to provide
scaling information, then set the Alarm ID to the default value of 65535.
Description The variable {0} in the GSM Translation Table is not reachable from
this WorkstationST computer. Do you need to make the device that owns this variable
a referenced device under the EGD tab?
Possible Cause The variable in the UTF8 variable field is not defined in the system
or is not accessible from this workstation.
Solution Determine if the variable has been defined. If the variable comes from another
component, make sure that:
• Variable was defined in that component.

• Variable was mapped to the EGD page in that component.
• The component was built on a computer that is working online with the EGD Config
server so that their EGD page maps are available.
• This component is set up to consume pages from that component.
• This computer is working online with the EGD Config server to get the latest EGD
map.
Description GSM Min Value and GSM Max Value cannot be equal. Variable: {0}
Possible Cause Both the GSM Minimum Value and the GSM Maximum Value
contain non-zero values, but they are equal.
Solution Determine the correct scale factor.
Description OPC Min Value and OPC Max Value cannot be equal. Variable: {0}
Possible Cause Both the OPC Minimum Value and the OPC Maximum Value contain
non-zero values, but they are equal.
Solution Determine the correct scale factor.

Description GSM Scale Values must be set because OPC Scale Values are set.
Variable: {0}
Possible Cause OPC Minimum and/or OPC Maximum values are entered, but no
corresponding GSM Minimum and/or GSM Maximum values are entered.
Solution Enter the corresponding GSM Minimum and/or GSM Maximum Values or
change the OPC Minimum and OPC Maximum values to zero.
Description OPC Scale Values must be set because GSM Scale Values are set.
Variable: {0}
Possible Cause GSM Minimum and/or GSM Maximum values are entered, but no
corresponding OPC Minimum and/or OPC Maximum values are entered.
Solution Enter the corresponding OPC Minimum and/or OPC Maximum Values or
change the GSM Minimum and GSM Maximum values to zero.
Description Because Points Must Be in Translation Table is true, the GSM Min Value,
GSM Max Value, OPC Min Value and OPC Max Value cannot all be zero. Variable: {0}
Possible Cause An incorrect scaling value is entered or the Points Must Be in

Translation Table option is set incorrectly.
Solution Determine if the Points Must Be In Translation Table setting is correct. For a
Mark V it should be set to true. Otherwise, it should be set to false If true, determine and
enter the correct scaling.
Description Because Points Must Be in Translation Table is true, the GSM Data Type
cannot be undefined. Variable: {0}
Possible Cause The GSM Data Type is entered incorrectly.
Solution Determine if the Points Must Be In Translation Table setting is correct. For a
Mark V it should be set to true. Otherwise, it should be set to false. If true, determine and
enter the correct data type for the GSM client.
Description The ASCII Variable {0} in the GSM Device Translator contains a
non-ASCII character.
Possible Cause The variable contains a non-ASCII character.
Solution Edit the field to replace the non-ASCII characters with ASCII characters.
Description The ASCII Variable {0} in the GSM Device Translator contains a "." and
it should not. It is supposed to be the variable name without the controller prefix.
Possible Cause The full variable name was entered in the field instead of the portion
of the variable name after the controller prefix.
Solution Remove the controller prefix.

Description The UTF8 variable {0} in the GSM Device Translator contains a "." and it
should not. It is supposed to be the variable name without the controller prefix.
Possible Cause The full variable name was entered in the field instead of the portion
of the variable name after the controller prefix.
Solution Remove the controller prefix.
Description The ASCII Alarm Description for the Variable {0} in the GSM Device
Translator contains a non-ASCII character.
Possible Cause The Alarm Description contains a non-ASCII character.
Solution Edit the field to replace the non-ASCII characters with ASCII characters. (If
this is not done, the GSM server replaces any non-ASCII characters with a “?”.)
Description Warning: The device {0} is a Mark V, and the "Points Must Be In
Translation Table" is set to false. It is recommended that you require points to be in the
Translation Table so that GSM Clients receive data scaled as they would expect it
Possible Cause The UTF8 controller name device is a Mark V, but the Point Must
Be In Translation Table is not set to true.
Solution This is a warning. The GSM clients using GSM1 or GSM2 protocol in the past
received data from a Mark V as 16 bit integers, they may still expect the data in that form,
instead of the data type defined for the variable in the OPC server.

Notes

Chapter 3 Runtime
For details on the GSM 3.0 version protocol refer to GEH-6760, WorkstationSTGSM 3.0
Application Guide.
Note If a client is to use the new GSM 3.0 protocol, a Connection Options Request
message requesting to use GSM3 must be sent. Otherwise, the GSM server defaults to
supporting GSM1/GSM2 protocol for backwards compatibility.
There are four ways to monitor the status of a running GSM server.
• WorkstationST Status of Features window

• WorkstationST Additional Status window
• Detail Log
• GSM Spy program
WorkstationST Status of Features

Ø To open the WorkstationST Status of Features screen
♦ From the Start menu, select Programs, GE ControlST, WorkstationST, and

WorkstationST Status Monitor.
Or
♦ From ToolboxST, open a WorkstationST component and click the Go On/Offline
button. From the Component InfoView, select the Status tab of the
WorkstationST component running the configured GSM feature.
GEH-6757B Chapter 3 Runtime User Guide 3-1

The logic that drives the Error/Warning/OK status for the GSM feature is as follows:
Errors
• No connection with the OPC server

• No connection with the Alarm Server
• Problem trying to set up a Port to listen for connections
Warnings
• Any Application errors while reading, processing, or sending a message

• Any NAKs returned to the GSM client
• Any connections shut down due to an Error
Note After a Warning condition has occurred, the Warning state remains set until the
Additional Status Details view is displayed and the Zero Counters button is clicked.
After a steady-state condition has been reached, it is recommended that the counters be
set to zero to more easily identify any subsequent conditions that occur.
WorkstationST Additional Status

Ø To view additional status information
♦ From the Component InfoView, select the Status tab. From the Features
column, right-click the GSM item and select View Additional Status Detail. The
WorkstationST additional status window displays.

The following information displays in the WorkstationST additional status window and
can be monitored at runtime.
GSM Additional Status Details
Message Description
GSM Initially started at The time that the program was last started. If WorkstationST Service is configured to start
7/1/2008 2:06:24 PM. automatically when the computer restarts, and the GSM feature is enabled, that service starts
the program. Otherwise, the WorkstationST Status Monitor can be used to stop and start the
GSM feature.
GSM last Downloaded When a new WorkstationST configuration is downloaded from the ToolboxST application, the
at 7/1/2008 3:02:13 PM. GSM program processes that download and the time is recorded. GSM tries to stay online as
much as possible. For example, if a new port is downloaded, GSM will stop listening on the old
port and start listening on the new port. However, it does not break any current client connections
that it has. Likewise, if it is told to use a different Alarm Server, there may be a break in alarms
being sent to clients, followed by an alarm dump to catch them up, but the client does not need to
send another Alarm Record Establish Request.
GSM last zeroed Once a steady-state condition is reached, it is recommended that the counters be set to zero.
counters at 7/2/2008 If a NAK is sent out for any message type then that Message line will show Warning. Likewise, the
3:51:53 PM. summary status for GSM displays a Warning. If the NAK count is greater than zero you know the
NAKs were generated after the time shown on this Message line.
The Zero Counters button also zeroes the counters for the number of messages sent and received.
OPC Server This message displays the measurement systems that GSM sees as defined, whether they were
Connections per defined in the system component, or on a per device basis in a device's Symbol table. GSM
Measurement System: maintains one connection to the OPC server for each different measurement system. If one GSM
Native - Connected; client is using English, and another client is using Metric, then the GSM server uses different
English - Connected; connections to the OPC server to support these two different clients. This provides a place to
Metric - Connected; confirm that the different connections to the OPC server are actually connected.
GSM is using Alarm This message shows which Alarm Server the GSM is currently getting its alarms from. If
Server on 3.29.16.214. Redundant Alarm Servers are set up in the System Configuration, then the IP Addresses for
Redundant pair: both of them are shown here.
3.29.17.16 and
3.29.16.214.
Alarm Server Sources: The message shows all the components this Alarm Server might get alarms from and whether or
Gateway1 – Connected; not the Alarm Server currently has a connection to those components. A GSM client should not
TMRM6E – Connected; expect to get alarms from any component that is not shown in this list.
C1 – Not Connected;
Client2 – Connected;
GSM is not connected to If GSM is not connected to the Alarm Server this message displays instead of the above two.
the Alarm Server! Trying Make sure the Alarm Server is running on the indicated workstations, and that those workstations
to connect to Alarm can be pinged from this workstation.
Server on: 3.29.17.16
or 3.29.16.214
GSM not connected to One of the downloaded configuration parameters had an unexpected value, that could not be
Alarm Server because it resolved to an IP Address. Make sure that the Alarm Server To Use field was configured correctly
got a blank IP Address in the WorkstationST component, General tab, General Properties. If this points to another
from Workstation workstation, make sure that the EGD Config Server is running and that the other workstation has
Config Reader. Was been built and downloaded.
an Alarm Server To Use
configured? Is Egd Cfg
Server running?

Message Description
GSM is not connected The message line shows if GSM is not currently connected to the OPC server. Start the OPC
to the OPC server! server, if it is not running. If the OPC server is running, use the OPC server’s trace log file to
identify errors.
GSM listening on There is one of these message lines for each IP Address on which GSM is listening for client
3.29.16.214, Port 768 connections. It identifies if there are any problems setting up the listening on this port. If there
with No TCP Listening are any errors, then consult the Detail log to get further information. Any information related to
Errors: connections to this address, including status information about currently collected clients, is
indented / grouped under this message line.
2 Connections, 0 This displays the total number of connections that have been made on this IP Address since
shutdown due to counters were last zeroed. The following are the ways that a connection can be shut down, sorted
Errors, since last Zeroed by which conditions are considered Errors versus Normal.
Counters. Error Conditions:
Network Stream is null when beginning a read, finishing a read or sending a message.
An Async Result is null when finishing a read.
A bad GSM Read State object is gotten out of the Async Result
The message size at the beginning of a received message is greater than the Maximum Message
Size, so assumed it was in the middle of a message frame and broke the connection
There was a connection related exception.
Normal Conditions:
Did not get a heartbeat message within 1 minute.
The other party closes the connection.
Use the detail log for more information about what caused a shutdown.
Currently 1 Active GSM This shows how many clients and how many spies are currently connected using the IP Address
Clients, 1 Active GSM under which this message is grouped / indented.
Spies. If counters were zeroed after the last connection was made, then it is possible the number of
connections shown in this message line is actually more than the total number of connections
shown in the message line above this. This happens because the numbers for this message line
are calculated when requested to be displayed, not just kept in a counter that could be zeroed out.
GSM Client on TCP There is one of these message lines for each GSM client that is currently connected on the IP
Remote End Point Address under which this is grouped / indented. In turn, there is a set of detailed messages
3.29.17.191:1451 providing more information about this client connection that is grouped / indented under this
connected at 7/3/2008 message line.
8:13:02 AM: Note The End Point shown in this message line is comprised of the IP Address and port of the
GSM client, not the GSM server it is connected to.
Current Connection This shows the Current Connection Options for this connection. If this is for a GSM2 client, then
Options: Measurement the measurement system shows what is configured in the ToolboxST application for the default,
System – Native; and the Maximum Message Size is 4096 because there is no way for a GSM2 client to change
Maximum Message it. However, a GSM3 client can change these values using the Connection Options Request
Size – 4096; Protocol – message. The Maximum Message Size shows how large a message can be before it must be
GSM 3; split into multiple messages.
74 Received, 30 Sent This is the total number of messages that have been received and sent since the counters were
Messages Total. last set to zero.
1 Messages Received This can be used to make sure that the GSM server is not being inundated with messages.
in the last Second, 0.2
Average messages per
second over the last five
seconds, 1 message
per second highwater
mark.

Message Description
0 Application Errors. If an Application Exception occurs, the connection waits the Restart Cycle Time (configuration
(An Unexpected parameter, default 5 seconds) and then tries to read the next message. (The Restart Cycle
Exception that doesn't Time prevents the restart from being caught in an infinite loop.) Consult the Detail Log for more
appear to be related to information.
a connection problem.)
Supported Controller How many of this message type have been received from this client since counters were last
Request: 1 Received zeroed.
Connection Options How many of this message type have been received from this client and how many of those
Request: 1 Received, 0 were responded to with a NAK since counters were last zeroed. Consult the Detail Log for more
Nak’d information about any NAKs.
Alarm Command How many of this message type have been received from this client and how many of those
Request: 2 Received, 1 were responded to with a NAK since counters were last zeroed. Consult the Detail Log for more
Nak’d information about any NAKs.
Process Control How many of this message type have been received from this client and how many of those
Command Request: were responded to with a NAK since counters were last zeroed. Consult the Detail Log for more
3 Received, 0 Nak’d information about any NAKs.
Alarm Establish How many of this message type have been received from this client and how many of those were
Request: 3 Received, 2 responded to with a NAK since counters were last zeroed. The Active value is calculated when
Active, 0 Nak’d – Active requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
Devices: C1, TMRM6E request, the received count could be zero even though the active count is not. If any establish
requests are currently active the names of those active devices are listed. Consult the Detail Log
for more information about any NAKs.
Digital Input Establish How many of this message type have been received from this client and how many of those were
Request: 3 Received, 2 responded to with a NAK since counters were last zeroed. The Active value is calculated when
Active, 0 Nak’d – Active requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
Devices: C1, TMRM6E request, the received count could be zero even though the active count is not. If any establish
requests are currently active then the names of those active devices are listed. Consult the
Detail Log for more information about any NAKs.
Software Event How many of this message type have been received from this client and how many of those were
Establish Request: responded to with a NAK since counters were last zeroed. The Active value is calculated when
3 Received, 2 Active, 0 requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
Nak’d – Active Devices: request, the received count could be zero even though the active count is not. If any establish
C1, TMRM6E requests are currently active the names of those active devices are listed. Consult the Detail Log
for more information about any NAKs.
Periodic Read Establish How many of this message type have been received from this client and how many of those were
Request: 1 Received, responded to with a NAK since counters were last zeroed. The Active value is calculated when
1 Active, 0 Nak’d – requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
Cntrlr Name List Name; request, the received count could be zero even though the active count is not. The controller
#Points; #Unbound; name, list name, number of points in that list, number of unbound points in that list, number of
#Unhealthy; #No Scale; unhealthy points in that list, number of points where a scale factor was required but none was
#Rebinds: wks L1; 6; 0; found in the translation table, and the number of times that list was rebound are shown for all
0; 0; 0 currently active lists. Consult the Detail Log for more information about any NAKs.
When GSM is asked to send periodic data to its clients it sets up lists to communicate with the
OPC DA server and also keeps track of which components in the system are producing that data.
If any of those components is downloaded, the lists are stopped and restarted. This is what the
rebind count refers to. The rebind allows GSM to get the latest information about available points
and any changes in address or data types. There may be a one-time slightly longer than normal
gap in periodic data being sent to the client when this occurs. Any changes in data types or
availability of points will be reflected in the new Periodic Data Messages.

Message Description
High Speed Periodic How many of this message type have been received from this client and how many of those were
Read Establish responded to with a NAK since counters were last zeroed. The Active value is calculated when
Request: 1 Received, requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
1 Active, 0 Nak’d – request, the received count could be zero even though the active count is not. The controller
Cntrlr Name List Name; name, list name, number of points in that list, number of unbound points in that list, number of
#Points; #Unbound; unhealthy points in that list, number of points where a scale factor was required but none was
#Unhealthy; #No Scale; found in the translation table, and the number of times that list was rebound are shown for all
#Rebinds: wks L1; 6; 0; currently active lists. Consult the Detail Log for more information about any NAKs.
0; 0; 0 When GSM is asked to send periodic data to its clients it sets up lists to communicate with the
OPC DA server and also keeps track of which components in the system are producing that data.
If any of those components is downloaded, the lists are stopped and restarted. This is what the
rebind count refers to. The rebind allows GSM to get the latest information about available points
and any changes in address or data types. There may be a one-time slightly longer than normal
gap in periodic data being sent to the client when this occurs. Any changes in data types or
availability of points will be reflected in the new Periodic Data Messages.
Periodic Write Establish How many of this message type have been received from this client and how many of those were
Request: 1 Received, responded to with a NAK since counters were last zeroed. The Active value is calculated when
1 Active, 0 Nak’d – requested to be displayed, so it is not zeroed out. If counters were zeroed after an establish
Cntrlr Name List Name; request, the received count could be zero even though the active count is not. The controller
#Points; #Unbound; name, list name, number of points in that list, number of unbound points in that list, number of read
#Read Only; #No Scale; only points in that list, number of points where a scale factor was required but none was found in
#Mismatched Data the translation table, and the number of points where the length sent to us in the last Periodic
Lengths: wks L1; 3; 0; Write message did not match the length we expected based on the point's current data type are
0; 0; 0 shown for all currently active lists. Consult the Detail Log for more information about any NAKs.
Periodic Write Message: How many of this message type have been received from this client and how many of those were
2232 Received, 0 Nak’d responded to with a NAK since counters were last zeroed.
Note These are total counters. That is, if there were two different Periodic Write Lists established,
and one list received 2200 writes, and the second list received 32 messages, then the total of
2232 messages received is shown. Consult the Detail Log for more information about any NAKs.
GSM Spy on TCP There is one of these message lines for each GSM Spy that is currently connected on the IP
Remote End Point Address under which this is grouped / indented. In turn, there is a set of detailed messages
3.29.17.191:1824 providing more information about this spy connection that is grouped / indented under this
connected at 7/2/2008 message line.
3:52:20 PM: Note The End Point that is shown in this message line is comprised of the IP Address and port of
the GSM Spy, not the GSM server to which it connected.

Detail Log
GSM writes messages to a trace log file to help identify problems.
Ø To display the GSM trace log
♦ From the WorkstationST Status of Features dialog box, right-click the GSM
feature, select Advanced and View Detail Log to display the contents of the
trace log file.
There are four message levels in the trace log file:
• Error
• Warning
• Info
• Verbose

Ø To change the message level
1. From Windows® Explorer, select C:, then Program Files, GE Energy, and
WorkstationST Features.
2. From the WorkstationST Features folder, use Notepad to open the
GeCssGSM.exe.config file.
The ApplicationDefaultSwitch values are:
• Error messages = 1
• Errors and warnings = 2
• Errors, warnings, and information = 3
• Errors, warnings, information, and verbose = 4
Note The default value is 3. To view the contents of each message received, change
the value to 4 to include verbose. This value quickly fills the trace log file, so return the
value to 3 as soon as possible.
An example of an Error is when GSM receives a Periodic Write message from a client
for a list number that it does not recognize. An example of a Warning is when GSM
receives a Periodic Write message but the data length for some of the variables in the
message does not match the data length of the variables in GSM. An example of an Info
message is when a Rebind is done on a Periodic Data Read list, when a referenced
component is downloaded.
If the message level is changed to 4 (verbose) then the raw data bytes for every message
sent and received are logged. The preferred way to view this information is to use the
GSM Spy instead of the trace log.

GSM Spy
The GSM Spy is a separate program that can be used to monitor message traffic between a
GSM server and its clients.
Ø To start the GSM Spy
♦ From the Start menu, select Programs, GE ControlST, WorkstationST, and

GSM Spy. The GSM Spy dialog box displays.

For additional information about tracing, refer to the section Tracing.

Client Summary View
Ø To display the Client Summary View
Client Summary View Column Headings
Column Description
Alarm Commands The first number displayed is the number of successful alarm commands. The second number
displayed is the total number of alarm commands received from this client.
Note Both of these counters are zeroed when counters are zeroed using the WorkstationST monitor.
Alarm Lists All the devices this client currently receives alarms from.
Client End Point The End Point (IP Address and local port) on the client side.
Connection Time The time this client connected to the server.
Digital Input Lists All the devices this client currently receives digital inputs from.
Event Lists All the devices this client currently receives events from.
GSM Server IP The IP Address of the GSM server that this client connected to. A GSM server listens on all network
Address adapters, so it is possible for the spy to connect using one IP Address, and the client to have
connected to that same server process using a different IP Address.
High-Speed For each high-speed periodic data read list that is established, this displays the list # / # of points in
Periodic Data Lists the list / # of Rebinds that have taken place on that list.
I’m A Spy True or False. Even though there are only nodes in the Tree View for every client connected, this
table actually displays both spies and clients that are currently connected to the server. Besides an
entry for yourself, any other spies currently connected to the server are displayed here.
Periodic Data Lists For each periodic data read list that is established, this displays the list # / # of points in the list / #
of Rebinds that have taken place on that list.
Periodic Write Lists For each periodic write list that is established, this displays the list # / # of points in the list.
Process Control The first number displayed is the number of successful process control commands. The second
Commands number displayed is the total number of process control commands received from this client.
Note Both of these counters are zeroed when counters are zeroed using the WorkstationST monitor.

Per Client Views

Status Tab
The Status Tab displays the following information for the selected client:
Status Tab Information
Row Description
This Data Last Updated: The Client Summary and Per Client information is only updated when a connection is
first made to the server and when the Refresh pushbutton on the Spy user interface is
clicked. This time indicates the last time this information was refreshed from the server.
GSM Server IP Address: The IP Address of the GSM server that this client connected to. A GSM server listens on
all network adapters, so it is possible for the spy to connect using one IP Address, and a
client to connect to that same server process using a different IP Address.
GSM Client Connection Time: This is the time the GSM client that is being monitored first connected to the GSM server.
Total Application Errors: If an Application Exception occurs, the connection waits the ReStart Cycle Time
(configuration parameter, default of 5 seconds) and then tries to read the next message.
(The ReStart Cycle Time prevents the restart from being caught in an infinite loop.)
Consult the Detail Log for more information.
Maximum Message Size: The Maximum Message Size before a message must be split into multiple messages.
The default for this is 4096, but each GSM client can change this for their connection
with a Connection Options Request message.
Measurement System: The Measurement System that this client is currently configured to use. It starts out as
the GSM Measurement System Default set in the ToolboxST configuration. However,
any client can change the Measurement System it uses by sending a Connection Option
Request.
Note Any periodic data reads or periodic writes that were established prior to
a Connection Option Request changing the Measurement System still use the
Measurement System that was selected when they were established. Only new establish
requests use the new Measurement System.
Total Messages Received: The total number of messages the server has received from this client since the counters
were last set to zero.
Total Messages Sent: The total number of messages the server has sent to this client since the counters
were last set to zero.
Time Last Zeroed Counters: After a steady-state condition is reached, it is recommended that the counters be set to
zero.
If a NAK is sent for any message type, that Message line shows Warning. Likewise, the
summary status for GSM will show Warning. If the NAK count is greater than zero, the
NAKs were generated after the time shown on this Message line.
The Zero Counters button also zeroes the counters for the number of messages sent
and received.
Messages Received in Last The number of Messages the server received from this client in the last second. This
Second: can be used to make sure the GSM server is not being inundated with messages.
Average Messages per Second: The average number of messages per second the server received from this client. This
can be used to make sure the GSM server is not being inundated with messages.
Most Messages Received per The most messages the server has ever received from this client in any given second.
Second: This can be used to make sure the GSM server isn’t being inundated with messages.
Supported Controller Request: How many of this message type have been received from this client since counters
1 Received were last zeroed.

Row Description
Connection Options Request: How many of this message type have been received from this client and how many of
1 Received, 0 Nak’d those were responded to with a NAK since counters were last zeroed. Consult the Detail
Log for more information about any NAKs.
Alarm Command Request: 2 How many of this message type have been received from this client and how many of
Received, 1 Nak’d those were responded to with a NAK since counters were last zeroed. Consult the Detail
Process Control Command How many of this message type have been received from this client and how many of
Request: 3 Received, 0 Nak’d those were responded to with a NAK since counters were last zeroed. Consult the Detail
Alarm Establish Request: 3 How many of this message type have been received from this client and how many of
Received, 2 Active, 0 Nak’d – those were responded to with a NAK since counters were last zeroed. The Active value
Active Devices: C1, TMRM6E is calculated when requested to be displayed, so it is not zeroed out. If counters were
zeroed after an establish request, the received count could be zero even though the
active count is not. If any establish requests are currently active, the names of those
active devices are listed. Consult the Detail Log for more information about any NAKs.
Digital Input Establish Request: How many of this message type have been received from this client and how many of
3 Received, 2 Active, 0 Nak’d – those were responded to with a NAK since counters were last zeroed. The Active value
Active Devices: C1, TMRM6E is calculated when requested to be displayed, so it is not zeroed out. If counters were
zeroed after an establish request, the received count could be zero even though the
Software Event Establish How many of this message type have been received from this client and how many of
Request: 3 Received, 2 Active, those were responded to with a NAK since counters were last zeroed. The Active value
0 Nak’d – Active Devices: C1, is calculated when requested to be displayed, so it is not zeroed out. If counters were
TMRM6E zeroed after an establish request, the received count could be zero even though the
Periodic Read Establish How many of this message type have been received from this client and how many of
0 Nak’d – Cntrlr Name List is calculated when requested to be displayed, so it is not zeroed out. If counters were
Name; #Points; #Unbound; zeroed after an establish request, the received count could be zero even though the
#Unhealthy; #No Scale; active count is not. The controller name, list name, number of points in that list, number
#Rebinds: wks L1; 6; 0; 0; 0; 0 of unbound points in that list, number of unhealthy points in that list, number of points
where a scale factor was required but none was found in the translation table, and the
number of times that list was rebound are shown for all currently active lists. Consult the
When GSM is asked to send periodic data to its clients it sets up lists to communicate
with the OPC DA server and also keeps track of which components in the system are
producing that data. If any of those components is downloaded, the lists are stopped
and restarted. This is what the rebind count refers to. The rebind allows GSM to get
the latest information about available points and any changes in address or data types.
There can be a one-time slightly longer than normal gap in periodic data being sent to
the client when this occurs. Any changes in data types or availability of points will be
reflected in the new Periodic Data Messages.

Row Description
High Speed Periodic Read How many of this message type have been received from this client and how many of
Establish Request: 1 Received, those were responded to with a NAK since counters were last zeroed. The Active value
1 Active, 0 Nak’d – Cntrlr is calculated when requested to be displayed, so it is not zeroed out. If counters were
Name List Name; #Points; zeroed after an establish request, the received count could be zero even though the
#Unbound; #Unhealthy; #No active count is not. The controller name, list name, number of points in that list, number
Scale; #Rebinds: wks L1; 6; 0; of unbound points in that list, number of unhealthy points in that list, number of points
0; 0; 0 where a scale factor was required but none was found in the translation table, and the
number of times that list was rebound are shown for all currently active lists. Consult the
When GSM is asked to send periodic data to its clients it sets up lists to communicate
with the OPC DA server and also keeps track of which components in the system are
producing that data. If any of those components is downloaded, the lists are stopped
and restarted. This is what the rebind count refers to. The rebind allows GSM to get
the latest information about available points and any changes in address or data types.
There can be a one-time slightly longer than normal gap in periodic data being sent to
the client when this occurs. Any changes in data types or availability of points will be
Periodic Write Establish How many of this message type have been received from this client and how many of
0 Nak’d – Cntrlr Name List is calculated when requested to be displayed, so it is not zeroed out. If counters were
Name; #Points; #Unbound; zeroed after an establish request, the received count could be zero even though the
#Read Only; #No Scale; active count is not. The controller name, list name, number of points in that list, number
#MisMatched Data Lengths: of unbound points in that list, number of read only points in that list, number of points
wks L1; 3; 0; 0; 0; 0 where a scale factor was required but none was found in the translation table, and the
number of points where the length sent in the last Periodic Write message did not match
the length expected based on the point's current data type, is shown for all currently
active lists. Consult the Detail Log for more information about any NAKs.
Periodic Write Message: 2232 How many of this message type have been received from this client and how many of
Received, 0 Nak’d those were responded to with a NAK since counters were last zeroed.
Note These are total counters. If there were two different Periodic Write Lists
established, and one list received 2200 writes, and the second list received 32
messages, the total of 2232 messages received is shown. Consult the Detail Log for
more information about any NAKs.

Periodic Data List
If any Periodic Data Read, High Speed Periodic Data Read, or Periodic Write lists are
currently active, there is a tab for each list, with the tab name being the type of list,
controller name, and the list name (for example, Periodic Data List WKS L1). When the
tab is selected, overall information is displayed along with a grid containing an entry for
each point in the list. For Periodic Data Read lists, the overall information includes the
Time a Periodic Data Message was last sent to the client and the rate for which this list
was set up. The rate is in milliseconds. For Periodic Write lists, the overall information
includes the time data was last successfully written into the EGD page owned by the
GSM Server.

The following table describes the information displayed in the grid.
Periodic List Tab Column Names
Column Description:
Point The point name that the GSM server is using for this item in this list. For Periodic Data Lists, this is what was
Name sent by the GSM client. For Periodic Write lists, the controller portion of the name (the part before the first “.”)
is WKS coming from the DCS, but is replaced with the GSM server’s Device name. (Refer to the section GSM
Redundancy for additional information.)
Point Value The value of the variable when the Refresh button was last clicked and this updated information was sent to
the spy. If this connection is using GSM1/GSM2 protocol, and the GSM translation table contains scaling
information and/or a different data type for this point, the value shown is the value that the GSM client
receives (periodic data reads) or has written (periodic data writes). (Not the value of the point in the OPC
DA server.) The correct data type is written to the GSM client, but the value shown here is always in floating
point format to reduce the amount of CPU memory used to support the spy interface. If the Points Must Be
In Translation Table flag is set, the variable must be in the translation table with non-zero scale factors,
and the GSM client Data Type defined. Otherwise, it will display as Can Not Be Calculated, with the Data
Type set to No Required Translation Table Entry.
Data Type The data type the GE system thought the variable was the last time the value was either read (Periodic data
reads) or written (Periodic Writes), unless this connection is using GSM1/GSM2 protocol, and the GSM
translation table contains a different data type for this point. In this case the data type is the one that the GSM
client receives (periodic data reads) or has written (periodic data writes).
Units Each point can have a format specification associated with it. For example, the format spec Celsius, which
would be associated with the Metric measurement system and might have its units set to C. The units shown
here would reflect which measurement system is currently being used by this Periodic List. Remember that if
the client starts a Periodic List and then changes the measurement system, the Periodic List used the older
measurement system unless the client resends the Periodic List Establish message. It is possible that a point
can have units assigned directly to it instead of, or in addition to, a format spec. It is not recommended to have
units on a variable override the units in the format spec, because the point will be scaled based on the format
spec. If units were assigned directly to a point, then those units are shown here.
For example, GSMClient_3-29-16-214Port2874_PeriodicDataList_WKS L1.csv would contain:
PeriodicRate 5000, TimeLastSent 7/8/2009 11:50:31 AM

PointName,DataType,PointValue,Units
C1.AliasForGSMPrivateDint0,DINT,12,C
C1.AliasForGSMPrivateInt0,INT,40,C
C1.AliasForGSMPrivateLReal0,LREAL,10,C
C1.AliasForGSMPrivateReal0,REAL,6,EU
C1.AliasForGSMPrivateUDint0,UDINT,140,EU
C1.AliasForGSMPrivateUint0,UINT,27,C

Tracing
When tracing is turned on for a given GSM client, the GSM server forwards to the GSM
Spy every message the server either receives from, or sends to, that client. Each of these
messages is then available in the Spy to be inspected.
There are a few different ways that tracing can be turned on/off. The first way is through
the checkboxes in the Tree View. If the check box beside the top node GSM Clients is
checked, tracing is turned on for all GSM clients. This is reflected by the checkbox next to
each client also being checked. If tracing is only desired for one client, then only check
the box next to that client. If tracing is turned on for all clients by clicking the checkbox
for GSM Clients, it can be selectively turned off for any given client by clicking to clear
the checkbox next to that client.
The above methods of turning tracing on only apply to clients that are already connected
to the server. There is another way tracing can be turned on.

In the Tree View, when a given client is expanded, then all the traced messages for that
client are displayed below it. The order of these messages defaults to being sorted by time.
Behind the scenes the latest messages are collected. However, the messages displayed in
the Tree view are only updated when the user clicks the Refresh button. This allows you
to examine multiple messages, change the sort, and change the way the displayed data is
presented without changing the core list of messages being examined.
When an individual traced message is selected in the Tree View, the Client Summary
View displays the details of that message. Each portion of the message is broken out
and displayed.
For messages where a variable’s value is displayed, if the Spy thinks it knows the data
type of the variable, the raw bytes of value are converted to that data type. However, if
it does not know what the data type is, it converts the raw bytes based on the defaults
selected in the Trace Messages Information section of the screen.
Note If the GSM client is using GSM1/GSM2 protocol, and there is scaling
information associated with this point, the value displayed is what the GSM client
receives (periodic data reads) or what the GSM client sends (periodic writes), not the
variable’s value in the OPC DA server.

When a GSM client connects to a GSM server, for backwards compatibility the GSM
server defaults to using GSM1/GSM2 protocol. The GSM client can issue a Connections
Options Request to switch to using the GSM3 protocol. The GSM Spy defaults to
decoding the trace messages using GSM1/GSM2 protocol. If there are any non-ASCII
characters in the Controller Name, Variable Names, or Alarm Descriptions, these are
replaced by question marks (?). To correct this, select Use GSM3 in the
Connection Information section of the screen and click the Refresh button. This causes
the trace messages to be decoded using GSM 3 protocol, which supports UTF8. The
GSM server can have more than one GSM client connected at a time, and each client can
choose whether or not to use GSM1/GSM2 protocol or GSM3 protocol. This can require
changing the Use GSM3 selection when spying on different clients.
The GSM Spy can be used to determine a GSM server’s turnaround time to respond to
a request. When the GSM server receives a request message, as soon as it has read the
last byte for that message, it saves the time. This is the time that is displayed for that
request message when viewed in the GSM Spy. Likewise, immediately after a response
message is sent from the GSM server to a GSM client, the time is saved. This is the time
that is displayed for the response message when viewed in the GSM Spy. Using these
two times, the GSM Spy can be used to see the turnaround time from the receipt of a
request to the return of a response.

Chapter 4 GSM Test Client
The GSM Test Client is a separate program that can be used to send messages to a GSM
server and display the responses sent from the server. The GSM Test Client can be found
where the WorkstationST feature was installed. For example, C:\Program Files\GE
Energy\WorkstationST Features\GeCssGsmTestClient.exe.
The screen is divided into the following three sections:
• Connection
• Message Sent
• Reviewing Messages Received
Ø To connect the GSM Test Client
♦ From Windows Explorer select C:, Program Files, GE Energy, Workstation

Features, and GeCssGsmTestClient.exe to display the GSM Test Client
dialog box.
GEH-6757B Chapter 4 GSM Test Client User Guide 4-1

When a GSM client connects to a GSM server, for backwards compatibility the GSM
server defaults to using GSM1/GSM2 protocol.

Ø To test GSM3 protocol
Refer to the section Sending If the Connection Options Response indicates a Success, select Use GSM 3 Protocol
Messages.
in the Connection section. Refer to the section Messages Received
for additional information.
To change back to using GSM1/GSM2 protocol, send another Connection Options

Request with Use GSM3 deselected. When first connecting to a GSM server, it defaults
to using GSM1 /GSM2 protocol.

Sending Messages
Ø To send a message to the GSM server
Note The controller name for a Periodic Data Request and a Periodic Write Definition
should be WKS.
• After all required fields are completed, click the Send button.
There is a status line updated every second that shows how many NonHeartbeat versus
Heartbeat messages have been sent to the GSM server.
The Sent Msgs field is a drop-down list containing all the non-periodic messages that
were sent to a GSM server.

The list contains all messages the user defined and sent using the Send button. It does
not contain heartbeat messages or periodic write messages. It does contain periodic
Write Definitions. The first number in the field is the Sequence Number (19525) on the
sent message, followed by the Message Code (0x0600). The list can be used for the
following purposes:
• To review what was sent out.

• It can facilitate stopping a list or alarms by selecting the establishing message from
the list. The message fields all update to match the values that are used with that
establishing message. Change the Establish Function field to Stop Sending and click
the Send button.
• The list can be used to dynamically change the values sent in Periodic Write
Messages. Pick the desired establishing Periodic Write Definition Message from
the Sent Msgs list. The Chg button is enabled. (It is only enabled when a periodic
Write Definition message is being displayed.) Click the Chg button to display a
separate window with a grid showing the Point Names, Point Values, and Data Types
corresponding to the Periodic Write Definition.
From this window the Point Values can be changed. When the Point Value is changed and
the cursor is moved off that Point Value field, the Periodic Write Messages starts using the
new value. Even when this window is closed, the new values are remembered.

Messages Received
There is a Status Line in the Messages Received section of the screen that displays the
total number of Messages this Test Client has received from the GSM server, the current
number of messages per second, and the most number of messages ever received from
the server in any given second.
When the Refresh button is pressed, the Tree View displays. Expanding the Tree View
displays a Messages in Order Received item. Under that item, each messages received
from the Server is listed. Selecting the Messages in Order Received item updates the right
pane with a grid containing columns corresponding to fields in a message, and a row for
every message. Selecting an individual message in the Tree View updates the right pane
with a breakdown of the contents of that message.
When Periodic Data Messages are displayed, the point values are formatted based on
the selected ways to view 2 byte, 4 byte, and 8 byte data. Behind the scenes the latest
messages are collected. However, the messages displayed are only updated when the user
clicks the Refresh button. The number of messages to keep in the queue is defaulted to
100, but can be changed using the # to keep in Queue field.

Glossary of Terms
Data Structure is a method of storing data in a computer so that it can be used
efficiently.
DCS Distributed Control System is a digital process control system used for plant
process control applications, including power plant control.
Feature is an element of the WorkstationST runtime system, which can be optionally
enabled through the ToolboxST application. Examples include OPC DA server, Recorder,
OPC AE server, and Alarm System.
GSM GE Energy Standard Messages, used for communication with the DCS.
Heartbeat is a message from the DCS to GSM indicating that the DCS is functioning.
OPC OLE for Process Control (OLE is Microsoft's Object Linking and Embedding) is
a standard for data exchange in an industrial environment. The OPC foundation provides
specifications for various OPC standards such as OPC DA (Data Access) and OPC AE
(Alarm and Event).
OPC DA Server a core part of the WorkstationST product that conforms to the
OPC Data Access Specification.
Rebind is when GSM is asked to send periodic data to its clients and it sets up lists to
communicate with the OPC DA server and also keeps track of which components in the
system are producing that data. If any of those components are downloaded, the lists are
stopped and restarted. This is what rebind means in the GSM context. The rebind allows
GSM to get the latest information about available points and any changes in address or
data types. There can be a one-time slightly longer than normal gap in periodic data being
sent to the client when this occurs. Any changes in data types or availability of points are
GEH-6757B Glossary of Terms 1

Notes
2 WorkstationST* GSM 3.0

GE Energy
1501 Roanoke Blvd.
1 540 387 7000

www.geenergy.com

Geh 6757

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Geh 6757

Enviado por

Direitos autorais:

Formatos disponíveis

GE Energy GEH-6757B

WorkstationST* GSM 3.0

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

* Trademark of General Electric Company

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

Excellent Good Fair Poor Additional Comments

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

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

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

Indicates a procedure, condition, or statement that,

Indicates a procedure, condition, or statement that

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

A margin note is used to

This equipment contains a potential hazard of electric

Isolation of test equipment from the equipment under

To minimize hazard of electrical shock or burn, approved

To prevent personal injury or equipment damage caused

Always ensure that applicable standards and regulations

2 Contents WorkstationST* GSM 3.0

Document Number Document Name

GEH-6757B Chapter 1 Overview User Guide 1-1

1-2 WorkstationST* GSM 3.0

Enabling the GSM Feature

GEH-6757B Chapter 2 Configuration User Guide 2-1

2-2 WorkstationST* GSM 3.0

The following items are configured from the GSM tab.

2-4 WorkstationST* GSM 3.0

This simplified version of control hierarchy works as follows: In the controller

A translation table exists for each controller that requires one.

GEH-6757B Chapter 2 Configuration User Guide 2-5

2-6 WorkstationST* GSM 3.0

GEH-6757B Chapter 2 Configuration User Guide 2-7

Column Name Description

OPCmax – OPCmin GSMmax – GSMmin

2-8 WorkstationST* GSM 3.0

Xopc – OPCmin Ygsm – GSMmin

can be converted into the slope intercept form:

For the OPC value:

(OPCmax – OPCmin) OPCminGSMmax - OPCmaxGSMmin

Xopc = ————————– Yopc + ——————————————–

For the value that is sent over GSM:

(GSMmax – GSMmin) OPCmaxGSMmin – OPCminGSMmax

Ygsm = ————————— Xopc + ——————————————–

GEH-6757B Chapter 2 Configuration User Guide 2-9

OPC variable current value is 8.5.

GSMValue = ————– * 8.5 + ———————–

GSMValue = ————– * 8.5 = 69062.5

2-10 WorkstationST* GSM 3.0

Ø To import a translation table

GEH-6757B Chapter 2 Configuration User Guide 2-11

2-12 WorkstationST* GSM 3.0

• Periodic Reads and Receiving Alarms, Events, and SOEs

Periodic Reads and Receiving Alarms, Events, and

GEH-6757B Chapter 2 Configuration User Guide 2-13

How Page Health is Determined

2-14 WorkstationST* GSM 3.0

Possible Cause OPC DA server not enabled

Solution Enable the OPC DA server.

Solution Determine if one of the device entries is supposed to be a different device. If

• Variable was defined in that component.

Possible Cause Data type is not a Boolean.

GEH-6757B Chapter 2 Configuration User Guide 2-15

Solution Determine which device to use, or if this entry is no longer needed.