Documente Academic
Documente Profesional
Documente Cultură
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.
Your Job Function / How You Use This Publication Publication No. Address
Publication Issue/Revision
Date
General Rating
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?)
Place
stamp
_______________________
here
_______________________
_______________________
GE Energy
Documentation Design, Rm. 297
1501 Roanoke Blvd.
Salem, VA 24153–6492 USA
Warning
Tip Ä Provides essential information that is not normally defined in regular use but
from an experienced user.
GEH-6757B Contents 1
Notes
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.
Note If there is only one network in the system, the Unit Data Highway (UDH),
then use the UDH.
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 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.
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.
GSM Maximum
Xopc – OPCmin Ygsm – GSMmin
OPC Minimum ———————– = ————————
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.
y = mx + b
Where m = slope
b = offset
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.
OPCmin = 0 inches
The OPC variable is an IEEE float (in the ToolboxST application, referred to as REAL).
GSMmax = 65000
GSMmin = 0
The GSM data type is an unsigned 16-bit integer (in the ToolboxST application, referred
to as UINT).
65000 – 0 8 * 0 – 0 * 65000
65000
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.
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.
♦ 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.
GSM Redundancy
There are three parts to GSM3 server redundancy:
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.
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.
Description The OPC DA server feature must be enabled for GSM to work.
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.
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:
Description The variable {0} in the GSM Control Hierarchy needs to be a Boolean.
Solution Determine if the wrong variable was selected, or if the data type of the variable
needs to be changed.
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.
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.
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.
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)
Possible Cause The Alarm Server To Use field provides a list of all workstations in
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.
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. 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.
Possible Cause The Alarm Server To Use field provides a list of all workstations in
the system. It is possible that the device was removed from the system after this value
was selected.
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).
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 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).
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. 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.
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.
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 Edit the field to replace the non-ASCII characters with ASCII characters.
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:
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.
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.
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}
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}
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.
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.
Possible Cause The full variable name was entered in the field instead of the portion
of the variable name after the controller prefix.
Description The ASCII Alarm Description for the Variable {0} in the GSM Device
Translator 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.
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.
Or
button. From the Component InfoView, select the Status tab of the
WorkstationST component running the configured GSM feature.
Errors
Warnings
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.
♦ 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.
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?
♦ 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.
• Error
• Warning
• Info
• Verbose
• 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.
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.
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.
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.
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.
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.
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.
• Connection
• Message Sent
• Reviewing Messages Received
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.
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.
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.
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.