Foxboro Evo™

Process Automation System

GE GSM Driver for Mark V/VI
Using Windows-based
I/A Series Workstation

*DI700DA* *d*

DI700DA

Rev D
December 27, 2018
Schneider Electric, Foxboro, Invensys, Foxboro Evo, and I/A Series are trademarks of Schneider Electric SE, its
subsidiaries, and affiliates.
All other brand names may be trademarks of their respective owners.

Copyright 2014-2018 Schneider Electric.

All rights reserved

SOFTWARE LICENSE AND COPYRIGHT INFORMATION

Before using the Schneider Electric Systems USA, Inc. supplied software supported by this docu-
mentation, you should read and understand the following information concerning copyrighted
software.
1. The license provisions in the software license for your system govern your obligations
and usage rights to the software described in this documentation. If any portion of
those license provisions is violated, Schneider Electric Systems USA, Inc. will no lon-
ger provide you with support services and assumes no further responsibilities for your
system or its operation.
2. All software issued by Schneider Electric Systems USA, Inc. and copies of the software
that you are specifically permitted to make, are protected in accordance with Federal
copyright laws. It is illegal to make copies of any software media provided to you by
Schneider Electric Systems USA, Inc. for any purpose other than those purposes men-
tioned in the software license.
Contents
Figures................................................................................................................................... vii

Safety Information ................................................................................................................. ix

Preface.................................................................................................................................... xi
Who This Document Is For ..................................................................................................... xi
Revision Information ............................................................................................................... xi
Reference Documents .............................................................................................................. xi

1. General Description .......................................................................................................... 1

Overview ................................................................................................................................... 1
General Description .................................................................................................................. 1
Limitations ................................................................................................................................ 3
I/A Series System Isolation ................................................................................................... 3
Connection Display ............................................................................................................. 3
I/A Series Point Limits ......................................................................................................... 3
I/A Series Block Requirements ............................................................................................. 3
Alarming Limits ................................................................................................................... 4
GE Unit Name Limit ........................................................................................................... 4
GE Limits ............................................................................................................................ 4
SOE Reporting Package Limits ............................................................................................ 4
Ethernet Network Requirements .......................................................................................... 4
GE GSM Driver Features .......................................................................................................... 5
Data Transfer Connection Display ............................................................................................ 5
GSM Features ........................................................................................................................... 6

2. Reference Documents........................................................................................................ 9

3. GE GSM Driver Requirements ....................................................................................... 11

4. Installation ...................................................................................................................... 13
Step 1 Load the I/A Series Workstation Part of the Driver ................................................. 13
Step 2 (New Installations Only) Load the Status Control Part of the Driver ...................... 14
Step 3 (New Installations Only) Set up the Data Transfer Status Display ........................... 14
Step 4 (New Installations Only) Customize the Display(s) for This Site ............................. 14
Step 5 Install the Schneider Electric Foxboro GSM Configurator on Any PC .................... 15
Step 6 Install the Alarm Interface (if needed) ...................................................................... 15
Step 7 Set Up the TCP/IP “Logical” Connections .............................................................. 16
Step 8 Make the Physical Connections ............................................................................... 16

iii
DI700DA – Rev D Contents

Step 9 Configure the System .............................................................................................. 16

Step 10 Install the SOE Package as Directed (if needed) ..................................................... 16
Step 11 Start Up and Run the Package ............................................................................... 16

5. Configuring the GE GSM Interface ................................................................................ 17

Overview ................................................................................................................................. 17
FGC Home Screen .................................................................................................................. 18
ECB Configuration Screen ...................................................................................................... 20
Input Configuration ................................................................................................................ 23
Pushbutton Configuration ...................................................................................................... 25
Set Point Configuration .......................................................................................................... 27
Use of GE Tag Names for Alarms in CAD Display ................................................................. 28
GE Alarm Tag Configuration Steps .................................................................................... 29
Importing GE Tag Names to the Configurator .................................................................. 30
Generation of “CSV File” ................................................................................................... 31
Enabling the Use of GE Alarm tags .................................................................................... 31
Generation of Alarm map file ............................................................................................. 31
Alarm Handling Configuration ............................................................................................... 32
Map File Configuration ...................................................................................................... 32
Alarm Locking and Unlocking Configuration .................................................................... 33

6. Operation........................................................................................................................ 37
Move Files to Target Platform ................................................................................................. 37
Switch Block Creation ............................................................................................................ 37
Alarm Lock and Unlock .......................................................................................................... 37
GE GSM Operation ................................................................................................................ 37
GE GSM Monitor Operation ............................................................................................. 38
GE GSM Manager Operation ............................................................................................ 39
Configuring GE GSM ........................................................................................................ 40
Editing an Instance ............................................................................................................. 47
Shutting Down GE GSM ................................................................................................... 48
GE GSM Alarm Manager ................................................................................................... 49
Alarm Discard on Backup Machine ......................................................................................... 51
Use of GE GSM Configurator to Configure Alarm Discard from Backup Machine ........... 51
Data Transfer Display ............................................................................................................. 52
Local Time Adjustment ........................................................................................................... 52
Current Alarm Display Usage ................................................................................................. 52
Limitations of Alarm Synchronization After I/A Series Workstation Reboot ........................... 54
Limitation: Alarm Synchronization of Remote CADs After I/A Series Workstation Reboot 54
Limitation: Use of Common Alarm Group and WP CAD Backup .................................... 55
Forcing an Alarm Update ........................................................................................................ 55

iv
Contents DI700DA – Rev D

Alarm System Error Messages .................................................................................................. 55

Alarm Drop Number Restriction ............................................................................................ 56
SOE Interface ......................................................................................................................... 56
Load Testing ........................................................................................................................... 56
Alarm Tests ........................................................................................................................ 56
Troubleshooting ...................................................................................................................... 57
General Approach .............................................................................................................. 57
Analyzing Log File to Find Send/Receive Packets ............................................................... 58

7. I/A Series Block Control.................................................................................................. 59

Overview ................................................................................................................................. 59
Redundant Block Control ....................................................................................................... 59
Delay Switching Block ............................................................................................................ 60
SWCH Block .......................................................................................................................... 60
GE MARK V Data Transfer Display ....................................................................................... 62

8. Message Logging ............................................................................................................. 65

Communication Level ............................................................................................................. 65
Physical Level .......................................................................................................................... 65
DI70 Log File ......................................................................................................................... 65
TCP/IP Connection ........................................................................................................... 66
AIM*API Connections to I/A Series Blocks ........................................................................ 66
Non-Fatal Errors ........................................................................................................... 66
Fatal Errors .................................................................................................................... 66
Protocol Level Messages ..................................................................................................... 67
Supported Unit Request Message .................................................................................. 67
Supported Unit Response Message ................................................................................ 67
MARK VI with Workstation ST: ................................................................................... 67
Heartbeat Message ......................................................................................................... 68
Alarm Record Establish Message .................................................................................... 68
Alarm Record Establish ACK/NAK Message ................................................................. 68
Digital Input Record Establish Request Message ........................................................... 68
Digital Input Record Establish ACK/NAK Message ...................................................... 68
Digital Input Data Message ........................................................................................... 69
Software Event Record Establish Request Message ........................................................ 69
Software Event Record Establish ACK/NAK Message ................................................... 69
Software Event Data Message ........................................................................................ 70
Periodic Data Request Message ..................................................................................... 70
Periodic Data List Establish ACK/NAK Message ........................................................... 70
Periodic Data Message ................................................................................................... 71
Alarm Command Messages ........................................................................................... 72
Alarm Command ACK/NAK Message .......................................................................... 72
Alarm Data Message ...................................................................................................... 72
Alarm Dump Message ................................................................................................... 73

v
DI700DA – Rev D Contents

Process Control Command Message .............................................................................. 73

Process Control ACK/NAK Message ............................................................................. 73
Primary/Backup Control Message ................................................................................. 74
Alarming Log .......................................................................................................................... 74
AOS Error Logging ................................................................................................................. 74

9. Verifying AIM*API Version ............................................................................................ 75

10. Installing AOS............................................................................................................... 77

Quick Fix Installations ....................................................................................................... 77
Microsoft SQL Server Software .......................................................................................... 77
I/A Series Software with Security Enhancements ................................................................ 77
Uninstall AOS Software (Optional) .................................................................................... 78
AOS Software Installation .................................................................................................. 78
Modifying System Resources .............................................................................................. 79
Resizing the I/A Series System ................................................................................................. 79
Calculating the Correct Setting for OM_NUM_OBJS ...................................................... 79
Altering the Sizing Files ...................................................................................................... 80
Configuring the I/O Subsystem (AIM*API) ............................................................................ 81
Troubleshooting ...................................................................................................................... 82

11. I/A Series Alarm Displays.............................................................................................. 85

Appendix A. GE GSM Multi-Turbine Connection Scenario ............................................... 87

Appendix B. Migrating from Cimplicity to Workstation ST ............................................... 93

Appendix C. Migrating GE GSM........................................................................................ 95

Correcting Database Configuration File Manually .................................................................. 95
Correcting Alarm Map File Manually ..................................................................................... 95

vi
Figures DI700DA – Rev D

Figures
1-1. A Redundant Driver ...................................................................................................... 2
1-2. Data Transfer Status Display ......................................................................................... 6
5-1. FGC Home Screen ...................................................................................................... 20
5-2. ECB Configuration Screen .......................................................................................... 23
5-3. The Mark V Input File Screen .................................................................................... 25
5-4. The MARK VI Input File Screen ................................................................................ 25
5-5. Configuring Push Button Outputs for Mark V ........................................................... 26
5-6. Configuring Set Point Outputs for Mark V ................................................................ 27
5-7. Configuring Set Point Outputs for Mark VI ............................................................... 28
5-8. Main Screen of the Configurator ................................................................................. 29
5-9. Alarm Tag Configurator .............................................................................................. 30
5-10. GE Format for Specifying the Drop Number and the Corresponding GE Tag Name . 30
5-11. Alarms Home Screen ................................................................................................... 32
5-12. Alarms Backup Screen ................................................................................................. 33
5-13. Alarm Configurator ..................................................................................................... 34
6-1. GE GSM Manager Main GUI .................................................................................... 40
6-2. Starting AOS ............................................................................................................... 40
6-3. Starting Alarming ........................................................................................................ 42
6-4. Adding an Instance ..................................................................................................... 43
6-5. Adding an Instance - Cimplicity HMI ........................................................................ 43
6-6. Adding an Instance - Workstation ST HMI ................................................................ 44
6-7. GE GSM Manager with a Single Instance - Cimplicity HMI ...................................... 45
6-8. GE GSM Manager with a Single Instance - Workstation ST HMI ............................. 46
6-9. GE GSM Alarm Manager Dialog ................................................................................ 49
6-10. GE GSM Alarm Manager Dialog ................................................................................ 50
6-11. Alarm Report .............................................................................................................. 51
7-1. Communication Between Workstations and Blocks .................................................... 61
7-2. Logic for Delay CALC block, MARK V_SW .............................................................. 62
7-3. Data Transfer Status Display ....................................................................................... 63
7-4. Data Transfer Status Display ....................................................................................... 64
10-1. Microsoft SQL Server ................................................................................................. 78
A-1. Example of System with Two Controllers Each Interfacing with a Turbine ................ 87
A-2. Example of System with Turbine Controller Interfacing with Two Turbines .............. 88
A-3. Example of System with a Turbine Controller Interfacing
with a Turbine with a Different Name ........................................................................ 90
B-1. Driver ECB Configuration .......................................................................................... 93
B-2. Cimplicity Configuration ............................................................................................ 93
B-3. Workstation ST Configuration ................................................................................... 93

vii
DI700DA – Rev D Figures

viii
Safety Information
Important Information
Read these instructions carefully and look at the equipment to
become familiar with the device before trying to install, operate, ser-
vice, or maintain it. The following special messages may appear
throughout this manual or on the equipment to warn of potential
hazards or to call attention to information that clarifies or simplifies
a procedure.

The addition of either symbol to a "Danger" or

"Warning" safety label indicates that an electrical
hazard exists which will result in personal injury if
the instructions are not followed.

This is the safety alert symbol. It is used to alert you to

potential personal injury hazards. Obey all safety messages
that follow this symbol to avoid possible injury or death.

DANGER
DANGER indicates a hazardous situation which, if not avoided, will
result in death or serious injury.

WARNING
WARNING indicates a hazardous situation which, if not avoided, could
result in death or serious injury.

CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could
result in minor or moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury.
Please Note
Electrical equipment should be installed, operated, serviced, and main-
tained only by qualified personnel. No responsibility is assumed by
Schneider Electric for any consequences arising out of the use of this
material.

A qualified person is one who has skills and knowledge related to the con-
struction, installation, and operation of electrical equipment and has
received safety training to recognize and avoid the hazards involved.
Preface
This document describes the implementation of a single or redundant Ethernet interface between
an I/A Series system using Windows-based I/A Series workstations and one or more GE Unit
Controllers (controller or turbine controller, Mark V or Mark VI) using a GE HMI or gateway
(HMI or G Processor).

Who This Document Is For

This document is intended for the use of process control and/or application engineers.

Revision Information
For Revision D, these changes were made:
Chapter 1 “General Description”
♦ Updated “General Description” on page 1
♦ Updated “I/A Series System Isolation” on page 3
♦ Updated “Alarming Limits” on page 4
♦ Updated “GE GSM Driver Features” on page 5
Chapter 3 “GE GSM Driver Requirements”
♦ Replaced Windows 7 or Server2008 with Windows 7/Windows
10/Server2008/Server 2016
♦ Replaced 3.4.1 with QF1179987 with 3.5.0.28
Chapter 5 “Configuring the GE GSM Interface”
♦ Updated Figure 5-11, Figure 5-12, and Figure 5-13
Chapter 6 “Operation”
♦ Updated “GE GSM Operation” on page 37
♦ Updated “Alarm System Error Messages” on page 55
Chapter 10 “Installing AOS”
♦ Updated “I/A Series Software with Security Enhancements” on page 77
♦ Updated Figure 10-1
♦ Updated “Altering the Sizing Files” on page 80

Reference Documents
The following I/A Series documents are referenced in this document:
♦ AIM*AT Suite AIM*API User's Guide (B0193YN)
♦ Application Object Services User's Guide (B0400BZ)

xi
Preface DI700DA – Rev D

xii
1. General Description

Overview
This document describes the implementation of a single or redundant Ethernet interface between
an I/A Series system using Windows-based I/A Series workstations and one or more GE Unit
Controllers (controller or turbine controller, Mark V or Mark VI) via a GE HMI or gateway
(HMI or G Processor). The HMI/gateway can be either CIMPLICITY or Workstation ST. The
GE Drive Systems Standard Messages (GSM) protocol is used over the Ethernet TCP/IP link.
Data sent to or received from the GE HMI by the GE GSM driver is transferred to/from
I/A Series blocks using AIM*API (Version 5.5.0 or later) and the I/A Series Object Manager. The
GE GSM driver runs as an application program residing on one or two Windows-based I/A Series
workstations. The Interface Configurator runs on any Windows-based machine and produces
files, which are then installed on the I/A Series workstations.

General Description
The GE GSM Driver:
♦ Provides three interfaces, any or all of which can be used in a single installation:
♦ The data interface via I/A Series blocks
♦ The alarm interface via the Current Alarm Display (no blocks needed)
♦ The Sequence of Events (SOE) interface via the Schneider Electric Foxboro Power
Group SOE reporting package (no blocks needed).
♦ Uses standard 10/100 Ethernet connections to the GE turbine controller system, sin-
gle or redundant. One driver is used per I/A Series workstation (or I/A Series
workstation pair).
♦ Can have up to eight controllers connected to each I/A Series workstation; each con-
troller requires a separate instance of the driver. The number of controllers that can be
interfaced to an I/A Series workstation is also limited by the total number of alarms
that can be supported on each I/A Series workstation. Refer to “Resizing the I/A Series
System” on page 79 for the I/A Series workstation sizing information. An I/A Series
workstation can support up to 2200 input points, maximum per driver, total for
redundant systems, not including alarms or SOE points.
♦ May control multiple turbines on a single unit controller.
♦ Is not limited by the number of set points, pushbutton outputs, SOE points, or alarm
points.
♦ Has a limit of output operations (set points and pushbutton outputs, alarm com-
mands) to 10 per second by GE specification. A governor mechanism design prevents
this limit from being exceeded.
♦ For non-redundant installations, the driver part number is Q0302DE. The non-
redundant driver is installed on an I/A Series workstation with one fault-tolerant CP.
The heartbeat functionality is implemented through I/A Series blocks only.

1
DI700DA – Rev D 1. General Description

♦ For redundant installations, the driver part number is Q0302DF. The redundant
driver is installed on two I/A Series workstations and one or more fault tolerant CPs.
The I/A Series blocks are used for the heartbeat functionality and also for the data
interface run in the CP, as do the algorithms that control which data path is used for
each turbine controller connection.
♦ Needs SQL Server for the alarm interface and must be installed on the I/A Series
workstation, purchased separately if not already a part of the I/A Series workstation. It
is not needed if the alarm interface is not used. For more information on the SQL
server requirements, refer to the Application Object Services User's Guide (B0400BZ_C
or later).
♦ Needs Microsoft Office Professional for the Schneider Electric Foxboro GSM Config-
urator used with the GE GSM driver for Versions 4.0 and higher. It must be
purchased separately.
♦ Needs the Schneider Electric Foxboro Power Group SOE package for the Sequence of
Events (SOE) interface. To purchase the SOE software, contact your local sales repre-
sentative or call 1-866-746-6477 inside the U.S. or 1-508-549-2424 outside the U.S.
A special version must be purchased for redundant installations. The SOE package is
not needed if the SOE interface is not used.

Figure 1-1. A Redundant Driver

NOTE
I/A Series refers to I/A Series 8.8 and later.

2
1. General Description DI700DA – Rev D

Limitations
I/A Series System Isolation
The configuration diagrammed in Figure 1-1 above represents an I/A Series system with a
redundant GE GSM Driver, which resides in two I/A Series workstations and at least one CP (see
light gray box above). You can load up to eight instances of the GE GSM instance process on a
workstation, but the actual number of instances you can load is also limited by the number of I/O
points in each instance. For instance if you want to use 2200 I/O points on a workstation, the
maximum number of instances is four, with 550 I/O points used with each instance.The GE
GSM Driver consists of one instance of GE GSM Instance process for each turbine, one instance
of GE GSM Manager, one instance of GE GSM Monitor, one instance of the alarming process,
one instance of Application Object Services (aoAlm.exe) process for each controller,
AIM*API, and the input and output points in one or more CPs.
If more than one redundant GE GSM Driver must be installed on an I/A Series system, LAN
interfaces must be used to isolate each driver to one I/A Series system.

Connection Display
While the maximum number of turbine controllers that can be connected is eight, the package is
only delivered with connection displays for up to four turbine controllers. You must modify a
separate copy of the display if needed for turbine controllers 5 through 8. Mark V and Mark VI
turbine controllers are supported and can be mixed in any order.

I/A Series Point Limits

The Schneider Electric Foxboro GE GSM driver has a limit of 300 input data points per input
data list, but the GE Mark V controller has its own restrictions for list size (96) and number of
lists (16). The Mark VI does not have these restrictions. GE’s gateway, known as the “G”
processor can only handle a total of 32 lists for all turbines. Check with GE to see if these
restrictions apply.

I/A Series Block Requirements

Two CALC blocks are needed for each turbine and one block is needed for each input or output
point that passes through this interface. These points are located in a CP, so points must be
counted to determine if more than one CP is needed. Again, Alarms and SOEs do not use blocks
and should not be counted in the total. SWCH blocks are used for each input point; however, you
configure the scaling and offsets calculations in the interface so AIN blocks are not needed.

3
DI700DA – Rev D 1. General Description

Alarming Limits
The interface has been tested for up to 2200 alarms (550 per turbine for 4 turbines) total and is
believed to be able to handle more. It is important to have sufficient memory in the I/A Series
workstation for large alarm handling. The memory is allocated on startup of the alarming
software (specifically AOS) and fails at that time if sufficient memory has not been allocated.
♦ Maximum of 2000 alarm points can be configured per turbine controller.
♦ Alarm points that alarm and then return from alarm in less than 2 seconds are
reported 2 seconds apart. Multiple alarm state changes within 2 seconds result in one
alarm transition (into alarm or return from alarm) being reported.
See “Alarm Handling Configuration” on page 32 and “Limitations of Alarm Synchronization
After I/A Series Workstation Reboot” on page 54 for a discussion of remote alarming capabilities
and limits.

GE Unit Name Limit

The DI software limits the GE Unit Name (Turbine Name) from two to six characters. This limit
applies to the Controller Name field of the GE GSM Configurator ECB Header file
configuration and affects all communication to the GE HMI (or G processor).

GE Limits
General Electric has a limit on the number of inputs points (outputs from I/A Series) per second
per turbine. That limit should be respected when configuring control loops. Check with GE to
determine this limit. General Electric also has limits on the number of points that can be
configured in a input data list, the number of input data lists that can be configured, and the
number of alarms that can remain unacknowledged at any time without risking loss of alarm
reports. These limitations are different for turbine controller types (Mark V or Mark VI), and
different HMI/HMI or G Processor software. Check with GE on these limitations.

SOE Reporting Package Limits

Check with the Power Group at Schneider Electric Foxboro for SOE reporting package
limitations.

Ethernet Network Requirements

The GE GSM driver is designed to integrate a system of GE Mark V and/or Mark VI turbine
controllers to I/A Series software via a single or redundant Ethernet cable. The TCP/IP GE GSM
driver can be installed on single or redundant Windows-based I/A Series workstations. They
provide the features described in the next section.

4
1. General Description DI700DA – Rev D

GE GSM Driver Features

All versions of the Schneider Electric Foxboro GE GSM driver support the Data interface and the
SOE interface. Versions older than 4.0 support Windows NT/XP, versions 4.0 or later support
Windows 7/Windows 10/Server2008/Server 2016 installations (different part numbers), and all
versions support single and redundant connections to the GE gateways. For versions older than
4.0, refer to GE GSM Driver for Mark V/VI Using an AW51 or AW70 (DI700AI_L) for the GE
GSM driver features supported by each version. For versions 4.0 and later, these features are
supported:
♦ An Alarm Interface provides the capability to display and acknowledge GE alarms
with GE time stamps on any I/A Series Current Alarm Display (CAD) in the system.
Acknowledging an alarm from either the I/A Series CAD or the GE HMI causes that
alarm to display as acknowledged on both systems. The alarm interface is redundant,
and each alarm shows an identical status on the GE HMI and the primary, backup,
and remote I/A Series CADs. To use the Alarm Interface, SQL Server must be
installed on the I/A Series workstation.
♦ Simplified configuration. An easy-to-use GSM Configurator is provided with the GE
GSM driver to reduce startup costs. The Configurator provides a simple method to
input GE databases to the I/A Series system using Excel spread sheets. Download
capability (install a new database) is provided. Upload (read an existing database)
capability is not.
♦ Increased Application Flexibility. The GE GSM driver can now connect any mix of
Mark V and Mark VI turbine controllers on the same system using any combination
of GE gateways (HMI or “G” processor). There are also no restrictions on how the
turbines are divided between the GE gateways. You do not need to know the GE con-
figuration when ordering the driver; simply configure it to suit your needs at
installation.
♦ Supports multiple turbines connected to a single unit controller. Refer to
Appendix A “GE GSM Multi-Turbine Connection Scenario” for more details. Also,
starting with Version 3.4, GE controller names may be two to six characters. Addi-
tionally, to prevent duplicate C:B.P names on a large I/A Series network, GE
controller names may be assigned a two to six character “alias” name.
♦ The driver supports both CIMPLICITY and Workstation ST HMIs.
♦ The Configurator is updated to specify Workstation ST.

Data Transfer Connection Display

The Data Transfer Status Display supplied with this interface is shown in Figure 1-2. You can
configure the number of turbines it displays during installation, up to four. Two copies of the
display must be used if more than four turbines are to be connected. The connection can be single
or redundant. Redundant connections are made by using two General Electric HMI’s or G
Processors and two Schneider Electric Foxboro processors as shown in Figure 1-1. In a redundant

5
DI700DA – Rev D 1. General Description

configuration, connection is maintained through any single device failure. You control primary
and backup data routing using the Data Transfer Status display, shown in Figure 1-2.

Figure 1-2. Data Transfer Status Display

The status of each gas turbine is shown relative to each workstation. Selecting the pick box
bordering “ONLINE/OFFLINE”, enables a pop-up, allowing selection of whether the turbine
data transfer to the CP270 is ONLINE or OFFLINE. Selecting either of the other pick boxes
enables a pop-up allowing selection of Primary and Backup paths (which I/A Series workstation is
primary). The text field below the Primary vs. Backup pick box indicates if the heartbeat is
“Failed”, “Not Failed”, or “OOS” (Out Of Service). The bottom text field indicates if the
Workstation is “ACTIVE” (that is, this workstation is transferring the data), or “NOT ACTIVE”
(that is, this workstation is not transferring the data). A non-redundant display is also
configurable. See Chapter 7 “I/A Series Block Control”.

GSM Features
On the Ethernet link, the HMI or G Processor is the server and the GE GSM process in the
Windows-based I/A Series workstation is the client. The server makes itself ready for a connection
at initialization and waits for a connection request from the GE GSM. When the connection is
established, the GE GSM sends a Supported Unit request (see Chapter 5 “Configuring the GE
GSM Interface”) to start the session, and follows with Establish (Alarm, Digital Inputs, Software
Event) requests, an Alarm Command requesting an Alarm Dump, and the Periodic Data requests.

6
1. General Description DI700DA – Rev D

The session is maintained until either the GE GSM process is killed, or the server fails to receive a
Heartbeat command from the GE GSM at which time the GE server cancels any data lists
defined for the GE GSM Driver.
The GE GSM process runs on a Windows-based I/A Series workstation, which must have an
available Ethernet physical connection. The GE GSM Driver sends and receives data to and from
GE via a configurable database. Values can be sent and received to and from I/A Series blocks
(Compound:Block.Parameter). For a data point to/from the GE, a SWCH or a CALC block is
used to determine the communication path that is currently active. The CALC block determines
the path based on the ACTIVE path. Data passes between the ‘active’ GE GSM Driver to each
I/A Series data block (that is, AIN, CIN, AOUT, COUT). Since the GE GSM Driver process is
being used to move data between blocks in a CP and Mark V/VI Turbine Controllers, it is
necessary to configure both the blocks in the CP and the GE GSM Driver to connect those blocks
with specific data points in the Turbines. The GE GSM Driver configuration is based on a set of
GE GSM Driver block options as described in “Redundant Block Control” on page 59 of this
document. Chapter 7 “I/A Series Block Control” describes a possible CP configuration.
AIM*API facilities are used for reading and writing of block parameters. Refer to AIM*API
documentation for AIM*API options and operation.
The GE GSM Driver process, acting as the client, controls what information flows between the
server (HMI or G Processor) and itself. The GE GSM Driver process may send output (process
data and alarm) commands to the HMI or G Processor on a change driven basis. (GE restriction
is 10 per second per controller. The application engineer must be aware of this when designing
the databases.). The GE GSM Driver may request the HMI or G Processor to send analog data
periodically, and to send alarm changes, digital input events, and software events as they occur. In
addition, the GE GSM Driver must send a Heartbeat message to the HMI or G Processor at least
every 20 seconds, which lets the GE HMI or G Processor determine the health of the GE GSM
Driver process. These messages are exchanged between the GE HMI or G Processor and the GE
GSM Driver. Each message is for a specific turbine controller. If there is more than one controller
connected, each of these messages would occur for each controller.
The GE GSM Driver will also send a Supported Unit request to the HMI or G Processor
periodically, which allows the DI to determine the health of the connection between the GE
GSM Driver process, the GE HMI or G Processor and the Mark V controllers (units), and for a
Mark VI, between the GE GSM Driver process and the HMI Cimplicity application. For the
Mark VI interface the GE GSM Driver process determines absence of a connection to a controller
when it fails to receive any Periodic Data messages in the time it would take to receive 5
Supported Unit Responses (that is, PERIOD of Supported Unit Command multiplied by 5).
Whenever the GE GSM Driver process is “healthy”, it passes the health indication to the
“Selector” CALC block in the CP.
There are many message types in the GE GSM protocol. A quick list of the major message types
and some description follows:
♦ The Alarm Data Message is sent from the GE controller when an alarm changes state.
This message type contains one or more Alarm Data packets. The packets used for the
CAD are:
♦ Time Tag
♦ Alarm State
♦ Description
♦ Alarm ACK State.

7
DI700DA – Rev D 1. General Description

At startup, after a reconnect of the data link or after certain error conditions the
Schneider Electric Foxboro GSM Driver requests an Alarm Dump Message from each
controller to see if any alarms occurred during the disconnect. The Alarm Dump
Message consists of one or more messages containing Alarm Data packets for all unit
alarms. It is very much like the Alarm Data message and is used to update the CAD.
♦ Digital Input Data Message from the GE
This message type contains packets for one or more changed state inputs, which are
stored as an event in the Sequence of Events package along with the GE turbine
controller time tag.
♦ Software Event Data Message from the GE
This message type contains packets for one or more logic points which have changed
state and are stored as an event in the Sequence of Events package along with the GE
turbine controller time tag.
♦ Periodic Data Message from the GE
This message type is sent periodically at the rate, and for the Point Names defined in
the Periodic Data request. This message may contain data for up to 96 variables for
the Mark V and 300 variables for the Mark VI. The data received in this message from
the Mark V are 2-byte analog values or 1-byte logic variable. The data received from
the Mark VI may be 1 byte contact, 2 or 4-byte integer (signed and unsigned), or 8-
byte floating point. The message contains a time tag which is not used in this
application, only the data. These are the messages that supply the data for the data
blocks in the CP database.
♦ Process Control Command Message from GE GSM Driver
This message type is sent on a change driven basis. There are two categories of this
message:
♦ Setpoint Target
♦ Push Button.
These messages send I/A Series data block output data to the turbine.

8
2. Reference Documents
Refer to the following documents for additional information:
♦ GE Drive Systems document GEI-100165, issue date: November 1993. This docu-
ment describes the GSM protocol for Mark V turbine controllers connected through a
GE “G” processor.
♦ GSM Protocol Standard – Mark VI GEH-xxxx “Preliminary-Draft Copy”.
♦ Schneider Electric Foxboro I/A Series system documentation.

9
DI700DA – Rev D 2. Reference Documents

10
3. GE GSM Driver Requirements
The GE GSM driver requires:
♦ Windows-based I/A Series workstation (two for redundant installations).
♦ Installed TCP/IP networking software and a physical connection.
♦ For Windows 7/Windows 10/Server2008/Server 2016 workstations running
I/A Series V8.8 or later, AIM*API version 5.5.0 (along with AIM*AT 3.5.0.28) is
required1.
♦ For Windows 10 and Server 2016 workstations running Control Core Services V9.4
or later, AOS version 5.01.04 is required.
♦ GE “G” processor, GE HMI running Cimplicity, or Workstation ST. Some HMI
installations were not supported using the software and configuration methods used
with pre-3.0 GE GSM drivers.
♦ Installed Schneider Electric Foxboro Power Group SOE Recording Package (if the
SOE interface is to be used). To order the SOE package, enter an order on Power
Engineering, Department 983, with a line item “VAS-ES-SOE”. The ordering infor-
mation should include the type of system on which the driver is used: Windows
7/Windows 10/Server2008/Server 2016 operating system.2
♦ Microsoft Office Professional 97, Professional 2000, or higher to run the GSM Con-
figurator version 4.2 and later, needed for GSM Driver versions 4.0 and higher.
Microsoft Office must be loaded to the C drive.
♦ The GSM driver must be installed on the I/A Series workstations and CPs as defined
in Chapter 4 “Installation”.
♦ The GSM driver must be configured as defined in Chapter 5 “Configuring the GE
GSM Interface” (installations after January 2002 using version 3.0 or higher of the
GE GSM driver) or as defined in GE GSM Manual Configuration. Contact Schneider
Electric I/A Series Device Integration at iasdi@invensys.com.

NOTE
If you are migrating a GE GSM driver from an older version to a new version, refer
to Appendix C “Migrating GE GSM”.

1. Forthese items, contact the Global Customer Support by calling 1-866-746-6477.

2.
For these items, contact your local sales representative or call 1-866-746-6477.

11
DI700DA – Rev D 3. GE GSM Driver Requirements

12
4. Installation
The GE GSM Driver package is supplied on one CD. The complete GE GSM driver consists of
the di70 and alarming executables for the GSM protocol (GEGSMInstance.exe, GEGSMMan-
ager.exe, GEGSMMonitor.exe, Di70DllMKS8.dll, GEGSMAlarm.exe, and
Exec_Ksh_Script.bat), supporting functions, and the I/A Series compounds for the HEART-
BEAT compound. The HEARTBEAT compound drives the Data Transfer Status Display shown
in Figure 1-2 and in the case of a redundant installation, contains the data routing logic.
The files GEGSMInstance.exe, GEGSMManager.exe, GEGSMMonitor.exe, Di70DllMKS8.dll,
GEGSMAlarm.exe, and Exec_Ksh_Script.bat get installed at d:\opt\diw\di70\gegsm\bin.
Before installing the GE GSM software you need to make the following decisions:
1. Determine if you are installing a redundant or non-redundant GE GSM Driver. The
non-redundant driver is installed on a single workstation and a CP. The redundant
driver is installed on two workstations and a CP.
2. Determine if this is an upgrade installation or a new installation. The upgrade installa-
tion process installs the new driver but preserves edits you may have made to the
startup scripts and to the “Data Transfer Status Display”, shown in Figure 1-2.
3. Determine the number of turbine controllers used at this site and if the site is using
Mark V or Mark VI turbine controllers. Some sites use a mix of turbine controller
types.
4. Determine the GE names of each controller and its turbine(s). The names are of the
form “T1”, “T2” and so forth, but newer GE systems allow more characters in the
controller names. GE programs these names into the turbine controllers. Since the
turbine name is written into messages from the turbine controller, it is important that
each turbine have a unique name as delivered to the customer.
5. Determine if you need to install the SOE interface.
6. Determine if you need to install the Alarm interface.
Once these decisions have been made follow the steps listed in “Step 1 Load the I/A Series Work-
station Part of the Driver” on page 13.

Step 1 Load the I/A Series Workstation Part of the Driver

To install the GE GSM driver:
1. Uninstall any previously installed versions of the GE GSM driver on the I/A Series
workstation or I/A Series workstations that will act as integrators for this driver. Use
the Add/Remove Programs feature on the Control Panel of the I/A Series work-
stations and remove GeGSM.
2. Insert the CD labeled: GE GSM in the CD drive of the I/A Series workstation to load
the driver.
3. In Windows Explorer, expand the CD drive folder.
4. Double-click the “setup” icon and follow the installation instructions.

13
DI700DA – Rev D 4. Installation

5. The install shield project copies all the files to D:\opt\diw\di70\gegsm folder and also
registers the GEGSMMonitor.exe in FoxNTAppService to start the application auto-
matically in session 0 at system reboot.
6. Reboot the workstation after the installation completes.

Step 2 (New Installations Only) Load the Status Control Part of

the Driver
The installation CD also contains the status control part of the driver in ICC Save all format. The
status control part of the driver is a compound that provides the logic behind the “Data Transfer
Status Display” shown in Figure 1-2. The compound on the CD is MARKV, and referred to in
this document as the “HEARTBEAT” compound. The HEARTBEAT compound is loaded using
a Control Configurator (ICC). The HEARTBEAT compound is loaded into the CP that is to
accept the GE turbine database.
♦ Insert the CD in the I/A Series workstation hosting the processor. Use the ICC Con-
figurator to move the compound on the CD into the CP (“LoadAll”).
♦ The MARKV compound is shipped with a block named T1 to handle “Turbine 1”.
The compound name may be changed to MARKVI (if this compound is changed and
the MARKV_SW compound is used, its name must also be changed), or any other
desired name (in this case the display connections must also be changed). If the first
controller is “G1”, the block must be named G1. If connections are for more than one
controller, a block must be added for each controller.

Step 3 (New Installations Only) Set up the Data Transfer Status

Display
The Connection display file, GEDataXfr.fdf has now been loaded to d:\opt\diw\di70\gegsm\dis-
plays, and the overlay files for the display are loaded to d:\opt\diw\di70\gegsm\overlays.
♦ The GEDataXfr.fdf file must be moved to the proper place in d:\opt\menus. The
overlay files must be moved to d:\usr\ovly.
♦ To use the GEDataXfr connection display, edit the appropriate .mbr file in
\opt\fox\env. For example, duplicate a line such as: button –l Disp
\opt\menus and change to: button –l &GEDisp
/opt/menus/GEDataXfr.fdf.
♦ Optional: A display can show the status of up to four controllers. If there are more
than four controllers at this site a copy of the first display can be created and changes
made as required for controllers 5 - 8. Make sure to add the menu name of the second
display.

Step 4 (New Installations Only) Customize the Display(s) for

This Site
To customize the displays:
♦ Edit the text part of the display as needed.
♦ As installed the connection display expects the compound associated with the display
to be named MARKV, and the first four controllers to be named T1, T2, T3 and T4.

14
4. Installation DI700DA – Rev D

If different names are required, edit the Data Transfer Status Display to reflect the
block names (and compounds if applicable) used.
♦ If more than four controllers are required, and a second display was created for con-
trollers 5 through 8, edit this display as required.
♦ Configure the Data Transfer Status Display(s) to show the correct number of turbines
and to show a redundant or non-redundant system as shown in Figure 7-3 and
Figure 7-4. To do that bring up the display and click the Turbine Select button.
Then follow the directions on the display. Configuring the Data Transfer Status Dis-
play can only be done once. If you make a mistake repeat steps 3 and 4.

Step 5 Install the Schneider Electric Foxboro GSM Configurator

on Any PC
The Schneider Electric Foxboro GE GSM Configurator (FGC) is supplied on a CD. The FGC
can be installed on the C drive of any Windows workstation that has Microsoft Office installed.
♦ Insert the CD GE GSM Configurator in the PC running Microsoft Office Profes-
sional (97 or higher). Run the Install Shield setup.exe file which loads the
Configurator software to the folder gegsm_config on the C: drive.
Helpful hints:
♦ Microsoft Office must be loaded on the ‘C’ drive.
♦ If you use Excel 2000, perform the following steps:
a. Rename “config.xls” to “config.xls.2002”.
b. Rename “config.xls.2000” to “config.xls”.

NOTE
The latest version of the GE GSM Configurator has not been completely tested with
Excel 97.

Step 6 Install the Alarm Interface (if needed)

The alarming interface sends turbine controller alarm messages to the Current Alarm Display
(CAD) and returns acknowledgments from the CAD to the GE HMI. The AOS CD-ROM is
only needed for the Alarm Interface. If the Alarm Interface will not be used, skip this step. Other-
wise, if needed, install the AOS package and SQL Server on the I/A Series workstation that will
serve as the path for the alarm interface. Windows-based I/A Series workstations are not shipped
with SQL Server installed. You must order the SQL Server software using the ordering informa-
tion given in Chapter 3 “GE GSM Driver Requirements”. You must install SQL Server and the
files from the AOS CDs on the I/A Series workstations running the GE GSM Driver package.
The Alarm Interface can be configured to send turbine controller alarms to multiple alarm desti-
nations (CAD, printers, etc.). See Chapter 10 “Installing AOS” for detailed instructions on load-
ing AOS and SQL Server.
On large I/A Series networks with multiple GE networks, it may be necessary to assign a Turbine
Name Alias for alarms (see the ECB spreadsheet).

15
DI700DA – Rev D 4. Installation

Step 7 Set Up the TCP/IP “Logical” Connections

The TCP/IP addresses, the GE machine address and the address of the I/A Series workstation’s
Ethernet card, are site dependent and defined by GE. Normally dedicated links are used to con-
nect each I/A Series workstation to each G processor or HMI on the GE system. In Figure 1-1
two HMIs or G processors connected to a set of turbine controllers redundantly. In non-redun-
dant systems only one HMI or G processor is needed to connect all turbine controllers, but in
many non-redundant systems more than one G or HMI is used, each connecting a subset of the
total turbine controllers. Redundant systems can also use more than two turbine controllers, but
to be redundant, the I/A Series system must have access to each turbine controller through each of
its I/A Series workstations.
The I/A Series workstation connection to the HMI or G processor is always an Ethernet connec-
tion using one of the I/A Series workstation’s ports.
On a Windows-based I/A Series workstation the Control Panel, Network, Protocols pick allows
the entry of the TCP/IP address, Adapters, and Bindings. The IP Address is of the form
192.1.1.3x for a Mark V, and is of the form 192.168.201.xxx for a Mark VI. Also, the Subnet
Mask must be 255.255.254.0 for the Mark V, and the Subnet Mask must be 255.255.255.0 for
the Mark VI, and in both cases the Default Gateway field must be left blank. Under the Adapters
pick, under the Protocols pick, the Transceiver type should be checked for correctness. The Bind-
ings must then be selected. The I/A Series workstation must be rebooted to effect the changes.
The GSM Server address is defined in the GE GSM database file, ECB Configure. For the Mark
V the GSM Server (machine) IP Address is of the form 192.1.1.x. For the Mark VI the GSM
Server (machine) IP Address is of the form 192.168.201.xxx.

Step 8 Make the Physical Connections

Cable the physical connection that provides the paths for the logical connections configured in
Step 7. Ping the HMI or G processors to insure the connections are made.

Step 9 Configure the System

See Chapter 5 “Configuring the GE GSM Interface”.

Step 10 Install the SOE Package as Directed (if needed)

If the SOE package is to be used, see the SOE product installation instructions.

Step 11 Start Up and Run the Package

See Chapter 6 “Operation” for directions to start up and run the package.

16
5. Configuring the GE GSM
Interface

Overview
The Schneider Electric Foxboro GSM Configurator (FGC) is a separate application that runs in
Excel on a Windows based PC. It produces files that are then installed in the I/A Series
workstation or in the case of a redundant installation, in both I/A Series workstations and the CP
or CPs. Once a database has been created with the FGC, the I/A Series workstation files can be
back-loaded into the FGC and modified as needed (this feature will be added in a future release).
♦ For diagnostic purposes, and to provide backwards compatibility with earlier versions
of the GE GSM Driver, GE GSM Manual Configuration provides a detailed
explanation of all the fields in the resulting I/A Series workstation files. (Contact the
Schneider Electric I/A Series Device Integration group[iasdi@invensys.com] for this
document.) However, it is recommended that all configuration be done using the
FGC since you will need to be able to back-load the I/A Series workstation files
should you have a problem and need factory support. In redundant applications the
database is distributed between the two I/A Series workstations and one or more CPs
such that it is almost impractical to keep track of changes if the FGC is not used.
The Design approach in the 3.x version has important differences from earlier versions of the GE
GSM driver, some of which are only practical with the introduction of the FGC. For example, the
FGC eliminates the need for signal conditioning blocks, minimizes hand typing and minimizes
the details the engineer needs to deal with when a decision to make a database change is made.
More specifically the ease-of use features in the 3.x version of the GSM driver include:
♦ Since the FGC is spreadsheet-based, the I/O list provided by the turbine vendor
(Access database, Excel spreadsheet, etc.) can be imported into the FGC without
retyping it. The FGC accepts various words for data types. For example it recognizes
“INT”, “SIGN16” or “SGN16” as the same thing, an analog integer number.
Configuration is primarily a process of cutting and pasting columns of data from the
supplied I/O list into the FGC.
♦ Most AIN blocks can be eliminated from the database because the FGC provides the
application engineer an easy way to scale and offset inputs by providing a range
parameter column in the input spreadsheet.
♦ The primary reason to use CIN blocks in the database of earlier versions was to allow
the point to be alarmed. Version 3.x provides an Alarm Interface that couples the
I/A Series CAD directly to the GE HMI alarm display. The only time CIN blocks are
needed is when the customer did not specify a point as an alarm to the turbine vendor.
This method provides the CAD with accurate time stamps, printed in the turbine

17
DI700DA – Rev D 5. Configuring the GE GSM Interface

controller when the alarm occurred as opposed to when the I/A Series block
recognized the occurrence.
♦ The FGC provides an ICC DRVR file of SWCH blocks for all input points that need
to be displayed which can be uploaded to ICC.
The FGC creates:
♦ The compounds for the control processor
♦ The text files for the data interface, the alarm interface (optional) and the SOE
interface (optional) for the I/A Series workstation
♦ In the case of a redundant installation, the files for both I/A Series workstations
♦ Certain other files which the GSM Driver needs to operate
♦ Excel spreadsheets (.xls) files used to update the above project files.

FGC Home Screen

To start the FGC, using Excel, bring up the file called c:\gegsm_config\config.xls on your PC.
Enable Macros. The FGC will come up with the screen in Figure 5-1, except that the file names
in some of the cells are examples, not necessarily the file names used on all systems. This is the
top-level or “home” screen in the FGC, the screen you will return to after each configuration step.
Instructions on the home screen outline the basic steps needed to build the configuration files for
the Schneider Electric Foxboro GSM driver. It is not necessary to complete the configuration in
one session. It is only necessary to know the project name and enter it as part of Step 1 of the
configuration if you are switching between projects. Unless the project name is changed, the last
configured project will come up automatically when the FGC is started.
The first time the configurator is started:
1. Click Tools > Options > General.
2. Change the Default file location to c:\gegsm_config.
3. Click Tools > Macros > Security.
4. Excel 2002 only: in the Trusted Sources tab, check Trust access to Visual
Basic Project.
5. In the Security Level tab, select the Medium option.
6. If a copy of personal.xls is found in XLStart, remove it.
User help is built into the FGC. By placing the cursor over any cell with a red triangle in its upper
right corner, additional text is displayed.
The basic configuration steps outlined on the home screen of the FGC as seen in Figure 5-1 are:
7. Configure the port ECB. The port ECB contains the general project parameters such
as how many turbine controllers are to be connected and their specifics, if the inter-
face is to be redundant or not and which interfaces are to be used, etc.
♦ To configure the ECB, click on the Driver ECB Configuration, fill in the
fields and click on Save Entries and Exit to return to the FGC home screen.
♦ When alternating between projects, to display the ECB of a previous project, after
enabling config.xls (the FGC), open the saved ECB “project name_ecb.xls”
from the File menu. Clicking the Driver ECB Configuration button would
not work in this situation because it would open the most recent ECB.

18
5. Configuring the GE GSM Interface DI700DA – Rev D

8. Configure the alarm interface if it was enabled, in the ECB configuration. The alarm
interface is optional. It can only be used if AOS is installed on the I/A Series worksta-
tion that will use the Alarm Interface. There is very little configuration required for
this interface. If the Alarm Interface is not going to be used, skip this step.
♦ To configure Alarm Handling, click on the Alarm Handling Configuration
button, fill in the fields and click on Done to return to the FGC home screen.
♦ To display alarms from the turbine controllers on the CAD (Current Alarm Dis-
play) using “GE Tag names” instead of drop numbers, click on the Alarm Tag
Configuration button. (Refer to section “Use of GE Tag Names for Alarms in
CAD Display” on page 28)
9. Configure the data interface if it was enabled in the ECB configuration. The data
interface connects I/A Series blocks to specific turbine points. Configure a separate
data interface for each turbine controller to be connected. Each data interface has
three parts, inputs, set points and pushbuttons. It is a package requirement that at
least one Input File (with at least one point) be created.
♦ To configure the data interface, click on the Open Input File button, the Open
Setpoint File button, the Open Push Button file button, each in turn. Fill in
the fields and click on Save or Cancel buttons to return to the FGC home
screen.
10. Generate the Schneider Electric Foxboro GSM Driver files for each turbine controller
separately by clicking on the Generate Controller x Database button for that
controller (where x indicates Turbine 1-8). Wait for completion. Upon completion, a
dialog box appears stating that the .db file has been created. Click OK. Next, another
dialog box appears with the question Do you want to create the switch block
text file? If only switch blocks are to be created, click YES, otherwise click NO.
Repeat for each controller to be connected. This process generates the files that will be
used by the GSM Driver for that controller including information entered for the
ECB, the Data, Alarm, and SOE (in ECB) interfaces. The database files created are of
the form projectname_controllername(turbinename).db. If a redundant
database is created the file name is of the form
projectname_r_controllername(turbinename).db. If a switch block file is
created the name is of the form projectname_controllername(turbine-
name)_switch.txt.

NOTE
The turbine name is included in the database file name if Workstation ST is config-
ured.

11. When exiting the FGC a dialog box asks:

Do you want to save the changes you made to ‘config.xls’?
If you want the config.xls file to display the current contents the next time config.xls is
loaded, click YES. It may be desirable to have the config.xls be blank the next time it is
used. If so, click No. NO is the preferable response in most cases.

19
DI700DA – Rev D 5. Configuring the GE GSM Interface

12. Once completed load the files on the target machines as described in Chapter 6
“Operation”.

Figure 5-1. FGC Home Screen

NOTE
Screen allows the configuration of up to eight controllers.

ECB Configuration Screen

The Project Name parameter seen in Figure 5-2 is used in all the files created by the Configurator.
Use a unique Project Name for each project.
The WorkstationST parameter is to enable the WorkStation ST. Enter 1 for configuring
WorkstationST; otherwise leave it blank. If WorkstationST is configured, enter the turbine name
for the respective controller.

NOTE
The Turbine name will be considered only if WorkstationST is configured.

The Trace Level parameter controls the driver diagnostics as explained in the help. Keep this OFF
(0) for normal operation. This is the one parameter that should be turned on or off in the
resultant file on the target I/A Series workstation. It can be turned ON (at various levels) or OFF
separately for each turbine to show diagnostic information. Turning it on produces a running file
of what is happening while the GSM Driver is running (For more information, refer to GE GSM

20
5. Configuring the GE GSM Interface DI700DA – Rev D

Manual Configuration. Contact the Schneider Electric I/A Series Device Integration Group
[iasdi@invensys.com] for this document.

! WARNING
It is critical that this feature is turned off on systems with large numbers of input
points. On such an installation, only have this on for one turbine controller at a
time during initial checkout.

The “Establish Request Selection” parameter is what enables the various interfaces, Data, Alarm
and SOE.
Data entered while configuring the port ECB is not only used in the configuration files for the
Driver. The data is also used to determine what parameters will be solicited in the other FGC
screens. Although a single project can be used to configure up to eight turbine controllers, a
project is limited to one of the four possible turbine-GE Gateway types:
♦ Mark V turbines connected through GE “G” processors
♦ Mark V turbines connected through GE “HMI” processors running Cimplicity or
Workstation ST
♦ Mark VI turbines connected through GE “HMI” processors running Cimplicity or
Workstation ST
♦ Mark VIe turbines connected through GE “HMI” processors running Cimplicity or
Workstation ST
It is possible for the GE GSM Driver to support any or all of these types of turbines - GE
Gateways at the same time, but to do that the FGC must be used to create multiple projects with
different project names, one for each system type. The total number of turbines in the multiple
projects must not exceed eight, and the resultant files from each of the projects must be loaded
onto the target processors.
The GE Controller Name field is limited from 2- to 6-character unit names.
The Heartbeat CALC Block Name is used with the “Data Transfer Status Display” and defaults to
MARKV or MARKVI. These and other fields are explained by “comment” boxes on the
spreadsheet.
When the ECB configuration is complete, hit Save Entries and Exit. The following message
appears:
Header files successfully created!
If an error is detected in the ECB configuration, a dialog box suggesting appropriate action
appears.
Note: When using .xls files created with an older version of Excel such as Microsoft Excel 97 or
Office 2000, the following message box may appear after the Save or Exit button is clicked:
“A document with the name ‘personal.xls’ is already open. You cannot
open two documents with the same name, even if the documents are in
different folders.
To open the second document, either close the document that is cur-
rently open, or rename one of the documents.”

21
DI700DA – Rev D 5. Configuring the GE GSM Interface

If this message box is displayed, you must do the following:

1. Click OK.
2. Right-click on the problem button.
3. Click Assign Macro.
The Macro Name field may have:
'C:\Program Files\Microsoft Office\Office10\XLStart\personal.xls'!get_header
In this example get_header is a macro name. In other cases it is possible that the
macro name will differ.

NOTE
The above path may be replaced by C:\Documents and Settings\ etc.

4. Change the entry to:

personal.xls!get_header

NOTE
Both apostrophes (') must be removed, and the path name must be deleted.

5. Click OK.
6. Click Save.
This process may need to be done for ecb.xls, input.xls, setpoint.xls, and pushbutton.xls files.
After executing this procedure, the proper settings will not be saved if the Exit button is used.
Clicking the Save button will save the proper settings.

NOTE
The Mark V input.xls files have 16 sheets and the Mark VI input.xls files have 35
sheets. It is not necessary to alter the buttons on each sheet. Only alter the buttons
on the first sheet and, after entering information for the other sheets, return to
Sheet 1, and click the SAVE button.

When alternating between projects, to display the ECB of a previous project, after enabling
config.xls (the FGC), open the saved ECB project name_ecb.xls from the File menu.
Clicking the Driver ECB Configuration button would not work in this situation because it
would open the most recent ECB.

22
5. Configuring the GE GSM Interface DI700DA – Rev D

Figure 5-2. ECB Configuration Screen

Input Configuration
The Input Configuration spreadsheets are used to connect turbine data points that are to be
displayed on I/A Series process screens. There are 15 spreadsheets per controller for Mark V
systems and 35 spreadsheets per controller for Mark VI. If a controller has multiple turbines, only
points from a single turbine may be on a given spreadsheet. A separate set of spreadsheets is used
for each controller.
The column called “GE Signal Name” as well as the “GE Data Type” column and the “Data High
Scale” and “Data Low Scale” column of the Input File Screen are normally populated by cutting
and pasting from the spreadsheet or ASCII document the turbine vendor supplies. The names in
the “GE Signal Name” column become the I/A Series block names that will receive the data to be
displayed.

NOTE
The redundant GE GSM interface uses SWITCH blocks for input points, so con-
figure “IA data value type” column value as 3 and “IA Parameter” column value as
INP1.

GE turbines require that the DCS ask for data by data lists. A data list is a grouping of GE points
by turbine name and update frequency. The grouping is otherwise arbitrary. The points are in lists
for data transfer efficiency. Mark V turbines can handle up to 16 lists of data. Mark VI turbines

23
DI700DA – Rev D 5. Configuring the GE GSM Interface

can handle more data lists, but problems have been reported when large lists are specified. A single
GE “G” processor can handle up to 32 lists which must be divided between the turbines it
connects. A GE HMI can handle many more lists. GE also places limits in how many input data
points that can be put in a single list (96 for Mark Vs, many more for Mark VIs). The GE limits
must be respected. The GE GSM driver for a Mark VI allows up to 35 lists for each turbine, using
the Input File Screen, using the “list” spreadsheet tabs at the bottom of the screen and up to 300
input data points (rows) per list.

NOTE
Even though GE documents that 300-point lists are allowed, trial and error has
shown that a practical limit based on the point name length exists. A database with
an average point size of 8 bytes could not exceed 212 points. The database designer
should err on the low side since extra periodic data lists can be added at a minimal
additional load. Creating shorter lists is a good idea because the error caused by a
list that is too long only appears in the GE log file during startup of the application.

The “IA compound” column allows the engineer to specify the compound in which each block is
to be located. The “IA Parameter” column is almost always left as INP1 and is required to be
INP1 for redundant installations. Setting any row in this column to another value will require the
engineer to respond NO to the question Do you want to create the switch block text
file which will occur later in the configuration process. The yellow field in row one of each
input sheet allows the user to alter the default frequency for the list of points to something other
than the default frequency – 2 seconds. Comments are provided in row 1 of the spreadsheet for
the user’s help.
In the "Separator" column, the Engineer can specify the point separator as either "." or "\" for
each point in all the lists. The user can specify the point separator in the first sheet and click SAVE;
it applies to all the points in all the sheets. This is an optional field.
For the Mark V input configuration the Configurator’s software calculates the scaling value when
the “Data High Scale” field is entered. However, the calculated scaling value may be overridden by
entering the scaling value directly into the “Scaling” column. If the “scaling” value is entered, and
an offset value is needed, it must be entered in the “Offset” column.
For the Mark VI input configuration a scaling value of 1 is defaulted. The scaling and offset may
be entered if needed, however.
The “Engineering Units” and “Description” columns are only used for the creation of SWCH
blocks.
When completed with all the lists, click Save to return to the FGC Home Page.
The input configuration spreadsheet is saved to a file of the form
projectname_controllername_input.xls.
At this point, a message box appears asking: Do you want to create the switch block
text file? If only switch blocks are to be created, the user would indicate YES. If YES, the
configuration will create an ICCDRVR compatible file named addswch.txt. This will provide a
set of blocks in the named compound whose names are the same as the names in column H.

24
5. Configuring the GE GSM Interface DI700DA – Rev D

Figure 5-3. The Mark V Input File Screen

Figure 5-4. The MARK VI Input File Screen

Pushbutton Configuration
Pushbuttons are a defined class of output data from I/A Series to the turbines, normally
implemented as a display pushbutton on an I/A Series process screen. The GSM pushbutton
command cannot be used with the Mark IV controller. To send a pushbutton command, use the
GSM Setpoint Target command with the name of the pushbutton and a value of one. A separate

25
DI700DA – Rev D 5. Configuring the GE GSM Interface

Push Button screen is provided for each controller in the project. A separate spreadsheet screen is
used for each turbine controller.
Put the Turbine name and the GE Signal Name in the appropriate columns and repeat the point
name after the desired compound in the “IA Point Name” column.
In the "Separator" column, the Engineer can specify the point separator as either "." or "\" for
each point in all the lists. The user can specify the point separator in first sheet and click SAVE and
it applies to all the points in all the sheets. This is an optional field.
If a controller supports multiple turbines, pushbutton commands for each turbine are defined in
this single spreadsheet. Comments are provided in row 1 of the spreadsheet for the user’s help.
When completed, click Save to return to the FGC Home Page.
The pushbutton configuration spreadsheet is saved to a file of the form
projectname_controllername_pushbutton.xls.

Figure 5-5. Configuring Push Button Outputs for Mark V

26
5. Configuring the GE GSM Interface DI700DA – Rev D

Set Point Configuration

Set Points are a defined class of output data from I/A Series to the turbines. A separate Set Points
screen is provided for each controller in the project. A separate spreadsheet screen is used for each
turbine controller.
Put the Turbine name and the GE Signal Name in the appropriate columns and repeat the point
name after the desired compound in the “IA Point Name” column.
In the "Separator" column, the Engineer can specify the point separator as either "." or "\" for
each point in all the lists. The user can specify the point separator in first sheet and click SAVE and
it applies to all the points in all the sheets. This is an optional field.
If a controller supports multiple turbines, set point commands for each turbine are defined on this
single spreadsheet. Comments are provided in row 1 of the spreadsheet for the user’s help.
When completed, click Save to return to the FGC Home Page.
The set point configuration spreadsheet is saved to a file of the form
projectname_controllername_setpoint.xls.

Figure 5-6. Configuring Set Point Outputs for Mark V

27
DI700DA – Rev D 5. Configuring the GE GSM Interface

Figure 5-7. Configuring Set Point Outputs for Mark VI

Use of GE Tag Names for Alarms in CAD Display

When this feature is used, alarm drops are displayed on the CAD with GE Alarm Tag names
rather than, as drop numbers. This helps users identify the alarm easily. To enable this, specify the
"GE Tag name" of each drop in the GE GSM configurator. For the drop numbers for which ‘GE
Tag Name’ is not provided, the driver uses the default names. Enter "GE Alarm tags" in Alarm
Configuration tab and choose the option to generate a file that maps alarm drops to GE Alarm
tags. This map file is then passed as a parameter to the alarming program. The alarming
application uses this file to map alarm drops coming from the GE turbine controller to CAD.
The details of the configuration process are described below.

28
5. Configuring the GE GSM Interface DI700DA – Rev D

GE Alarm Tag Configuration Steps

The figure below is the main GSM Configurator screen. Configure the ECB as required. This is
the first step, because alarm tag configurator requires the controller’s name.
To display the screen to configure GE Tag Names for alarms (Figure 5-8), click on the “Alarm Tag
Configuration” button.

Figure 5-8. Main Screen of the Configurator

29
DI700DA – Rev D 5. Configuring the GE GSM Interface

Figure 5-9 shows the Alarm Tag Configurator for the GE controllers T1 and T2 entered on the
ECB configuration screen.

Figure 5-9. Alarm Tag Configurator

The drop number and the “GE Tag name” can either be entered manually or imported into the
configurator.

Importing GE Tag Names to the Configurator

Figure 5-10 shows the format of the GE HMI file used to specify the drop number corresponding
to the signal name (i.e. GE tag name).

Figure 5-10. GE Format for Specifying the Drop Number and the Corresponding GE Tag Name

A separate file with this format is required for each of the controllers to be configured.

30
5. Configuring the GE GSM Interface DI700DA – Rev D

In Figure 5-9, two controllers are configured (T1 and T2).

To import the first two columns, “Drop No” and the “Signal Name”, of this file into the Alarm
Tag Configurator, do the following:
♦ In the configurator, specify the delimiter, column number to skip from import and
the number of the starting row in the file from which the data is to be imported.
♦ By default, the delimiter is ‘|’ (pipe symbol), column to skip is 3 and the starting row
is 3 (for the file format shown in Figure 5-10).
♦ Select the first cell of the "Drop No" column of the corresponding turbine in the
configurator, where the first row has to be copied. For example: in Figure 5-9 for
importing data to T1 select cell B3 and for T2 select cell D3.
♦ Click the Import button. The Select File dialog box opens. Select the path and the
filename and click OK.
The Drop number and the Signal Name columns of the file are copied to the corresponding
columns in the configurator as shown in Figure 5-9.

NOTE
The configured GE Tag Name can have a maximum of 12 characters. The tag name
cannot have any special characters other than '/' (forward slash) and '_' (under-
score). After the data is entered, click the Sort button to sort data in the ‘Drop No’
field in ascending order.

Generation of “CSV File”

Click the Generate CSV File button to generate the ‘.csv’ file. The name of the generated CSV
file is in the format: <projectname>_alarm_tags.csv and it is saved at "C:\gegsm_config".
For redundant configuration, a file with the name <projectname>_ alarm_tag_r.csv is also
generated for the backup machine in the above location.

Enabling the Use of GE Alarm tags

In the Alarm Configurator (see “Alarm Handling Configuration” on page 32), click Yes for the
column ‘Enable GE Alarm Tags’ (Figure 5-11) to enable the driver to consider “GE Tag Names”
configured for the corresponding controller. If the option No is selected then the driver uses the
default Tag Names for that controller.

Generation of Alarm map file

Generate map file as specified in section “Alarm Handling Configuration” on page 32.

31
DI700DA – Rev D 5. Configuring the GE GSM Interface

Alarm Handling Configuration

This section explains how to configure the Alarm Handling options available with the GE GSM
Interface.

Map File Configuration

There are only a few Alarm Interface parameters that must be configured for each controller.
The “Number of Alarms” must be set to allow for all the possible GE Alarms (default=600). Up to
2000 alarms can be configured using this feature.
The Enable Reset field should be set either YES or NO for all controllers, since this is normally a
site decision that would apply to all controllers. On the I/A Series CAD an alarm is removed from
the display once it is acknowledged and is out of alarm. On the GE alarm display, the alarm
remains on the display even after it has been acknowledged and is out of alarm. To remove it from
the display the operator must also RESET it. If the “Enable Reset” parameter is set YES, the I/A
Series system will automatically send a RESET command to the GE display for each alarm once it
has been removed from the CAD. If NO, the operator must walk over to the GE display and
RESET each alarm. It is important that either the parameter is set YES or the operator is
consistent about manually resetting the alarms on the GE display. If alarms are allowed to
accumulate on the GE display, the GE FIFO will overflow and no more alarms will be sent to
either display.
For details on discarding the alarms on the backup machines, refer to section “Alarm Discard on
Backup Machine” on page 51.
The resulting spreadsheet has a name of the form projectname_alarm.xls The resulting file for
the primary I/A Series workstation is of the form projectname_controllername.map and
projectname_controllernameB.map for the backup I/A Series workstation. When moved
to the target I/A Series workstation, the file(s) must be renamed controllername.map for the
primary I/A Series workstation and controllernameB.map for the backup I/A Series
workstation.

Figure 5-11. Alarms Home Screen

32
5. Configuring the GE GSM Interface DI700DA – Rev D

Figure 5-12. Alarms Backup Screen

The Alarm Configurator causes alarms to be sent to only one Device Group. Each alarm point is
configured with the same priority. If multiple alarm groups or priorities are required, the .map file
may be edited by the engineer to achieve the desired result.
The I/A Series Alarm Destination of the workstation of an Alarm Display must be the I/A Series
workstation’s WP logical name as defined in SysDef and is found in /etc/msgln. The logical name
is also used in SOE compound configuration if SOE is required. Also available on this sheet are
columns for “IA ALARM BACKUP DEST. FOR DEVICE (1-8)”, which are used for the
redundant I/A Series workstation.
Hit Done to return to the FGC Home Screen. The resulting spreadsheet has a name of the form
projectname_alarm.xls.

Alarm Locking and Unlocking Configuration

NOTE
For details on operating the Alarm Lock and Unlock features, refer to section
“Alarm Lock and Unlock” on page 37.

Clicking on the “Alarm Handling Configuration” button in the main GSM Configurator screen
(Figure 5-1) opens the Alarm Configurator (Figure 5-13).

33
DI700DA – Rev D 5. Configuring the GE GSM Interface

In the column "Alarm Drops to be Locked", specify the drop numbers for which the Alarm
condition should not be notified by the Turbine controller to the driver.

Figure 5-13. Alarm Configurator

The drop numbers should be entered as individual drop numbers with each drop number
separated by commas.
For example: 100, 200, 300, etc.
The configurator does not allow any other special characters in this column except ‘,’ (comma).
Empty spaces are ignored.
For example:10, 2 0, ,30.
In the above example, observe that one empty space is present after first “,”, two empty spaces are
present within the number 20 and one empty space between the commas following 20. These
empty spaces are ignored and the configurator reads that cell value as “10,20,30”.
The drop numbers for a controller should be a valid alarm drop number and it should be less than
the maximum number of alarms allowed for that controller. The maximum number of alarms
that is supported by the number is given in the column “Number of Alarms”.
For instance, in Figure 5-13, each of the drop numbers entered for turbine T1 in column “Alarm
Drops to be Locked” has to be less than the maximum number of alarms specified in column
“Number of Alarms” for the T1 controller.
The drop numbers start from zero. A valid drop number with a maximum of 600 drops is any
number from 0 to 599.
The configurator accepts only 50 drop numbers per controller. If there are more than 50 drop
numbers to be locked, the GE GSM Alarm Manager GUI is used.

34
5. Configuring the GE GSM Interface DI700DA – Rev D

Click the Done button to execute these steps in the configurator:

♦ Verify the validity of drop numbers configured in column “Alarm Drops to be
Locked”. If the drop numbers are valid the following series of steps are executed:
♦ The map files for each controller are generated.
♦ The database (.db) files for each controller with their corresponding drop number
list is generated.

NOTE
If the .db file already exists, then it is regenerated with the Alarms information. The
map files and the database files that are generated are provided as inputs to the GE
GSM Driver at startup time.

NOTE
This method of specifying the drop numbers using the Configurator is used to spec-
ify the drops to lock before starting the driver. To lock alarm drop numbers on the
fly refer to “Alarm Lock and Unlock” on page 37.

35
DI700DA – Rev D 5. Configuring the GE GSM Interface

36
6. Operation

Move Files to Target Platform

After configuration with the Configurator is completed, the resulting database file, extension .db;
the switch block creation file, extension .txt; the alarm handling map file, extension .map; and the
alarm tag configuration file, extension .csv must be moved to the target I/A Series workstation.
♦ The files must be copied to the directory d:\opt\diw\di70\gegsm\data.
♦ The .map file must be renamed controllername.map (for example, T1.map)
for the primary I/A Series workstation and controllernameB.map (for exam-
ple, T1B.map) for the redundant I/A Series workstation.
♦ The switch block creation file, projectname_controllername_swch.txt,
must be renamed to addswch.txt.

Switch Block Creation

In the Command Prompt window, run iccdrvr.tsk.exe with input as the switch block file
which is a .txt file. Type the following commands at the command prompt to add the switch
blocks:
d:
cd \opt\fox\ciocfg\api
iccdrvr.tsk.exe -i
d:\opt\diw\di70\gegsm\data\projectname_controllername_swch.txt

Alarm Lock and Unlock

Alarm lock and unlock feature allows the user to stop the selected alarm points from generating
alarms. The drop numbers to be locked can be specified during alarm configuration using the
option provided in the GSM Configurator. The drop numbers can also be locked or unlocked,
even when the driver is running, using the GE GSM Alarm Manager GUI.
The GE GSM Manager application is provided to invoke the Alarm Manager GUI for the
selected controller.
The Alarm Manager is used to view the alarms’ lock state, toggle the alarms to lock/unlock state,
and generate and save reports for the alarms lock status.
For details on how to configure this functionality, refer to “Alarm Locking and Unlocking
Configuration” on page 33.

GE GSM Operation
The GE GSM driver version 4.0 runs on Windows 7/Windows 10/Server2008/Server 2016 based
I/A Series workstations. This version of driver is divided into 3 applications GEGSMInstance.exe,
GEGSMManager.exe, and GEGSMMonitor.exe due to the need for Session 0 isolation in
Windows 7/Windows 10/Server2008/Server 2016.

37
DI700DA – Rev D 6. Operation

In Windows XP/Server 2003, all services run in the same session as the first user who logs on to
the console. This session is called Session 0. In Windows 7/Windows 10/Server2008/Server 2016,
Session 0 is made non-interactive. Services remain in Session 0, but the first user logs on to
Session 1. Thus, services never run in the same session as user's applications.
♦ GEGSMMonitor.exe is a console application and is registered in FoxNTAPPService
by the install shield project to start the application in Session 0. The GEGSMMoni-
tor.exe starts automatically in Session 0 after rebooting the I/A Series workstation.
♦ GEGSMManager.exe is a GUI application for the end user to configure and monitor
the driver.
♦ GEGSMInstance.exe is a console application and is started by the GEGSMMoni-
tor.exe in Session 0. One instance of GEGSMInstance.exe application is required for
each turbine.

GE GSM Monitor Operation

The GEGSMMonitor.exe performs the following tasks:
a. Starts the GEGSMInstance.exe in Session 0 on receiving Go-Online request from
GE GSM Manager.
b. Stops GEGSMInstance.exe on receiving Go-Offline request from GE GSM
Manager.
c. Starts the GEGSMAlarm.exe in Session 0 on receiving Start Alarm request from
GE GSM Manager.
d. Stops GEGSMAlarm.exe on receiving Stop Alarm request from GE GSM Man-
ager.
e. Executes the AOS Start and Stop Script files on receiving AOS Start and Stop
request from GE GSM Manager.
f. Continuously monitors the GEGSMInstance.exe(s) and GEGSMAlarm.exe. If
GEGSMInstance.exe or GEGSMAlarm.exe closes unexpectedly for any reason,
the instance is restarted by the GEGSMMonitor.exe.
g. Saves the current driver configuration in a file on receiving checkpoint request
from GE GSM Manager. On I/A Series workstation reboot, loads all the data
from the checkpoint file and restores the GE GSM driver to the previous state
without user intervention.
On checkpoint, the GE GSM Monitor saves the last AOS Start Script file. For
testing purpose, the user can run individual AOS Script files for each map file.
Before performing checkpoint, merge all AOS Script files into one Script having
all AOS instances map files and execute “Start AOS” before calling checkpoint.
h. Forwards the log messages received from GE GSM Instance to the GE GSM
Manager and also saves the log messages in
C:\Programdata\Invensys\GEGSM\Logs\GEGSMMonitor folder.
i. Forwards the changed controller status (good or fail) to GE GSM Manager.

38
6. Operation DI700DA – Rev D

GE GSM Manager Operation

The GE GSM Manager is a GUI application for configuring and monitoring the GE GSM driver.
The install shield project creates three short cuts for this application— on the desktop, at Start-
>All Programs->Invensys->GEGSM, and on the Config menu in FoxView. The user can start
this application by clicking the short cut or by clicking GEGSMManager.exe located at
D:\opt\diw\di70\gegsm\bin. Only one instance of GE GSM Manager is allowed. If the user
opens another instance of GEGSMManager.exe, the previous instance will be brought to the
foreground.

NOTE
In a Secure I/A environment, the GE GSM Manager application can be configured
only in an Engineer account and not in an Operator account.
In an Operator account, the operator can monitor the instance status and log mes-
sages. The operator can stop and start alarm and AOS. The operator can delete the
Instance from the list of controllers list box but cannot add it.

39
DI700DA – Rev D 6. Operation

Figure 6-1. GE GSM Manager Main GUI

Configuring GE GSM
The user must configure one instance of the driver (GEGSMInstance.exe) for each turbine.
Following is the procedure to configure an instance of the driver:
1. Start AOS, if alarms are to be configured. Click the Browse icon to select the AOS
Start Script file. The install shield project copies the sample AOS Start Script file
'runaostx' to the D:\opt\diw\di70\gegsm\unedited_scripts folder.

Figure 6-2. Starting AOS

40
6. Operation DI700DA – Rev D

2. Click Start AOS. The GE GSM Manager displays the status of each command in the
script file in a command window.
You can run multiple AOS Start Script files. To do this, select each script file and click
Start AOS. It is recommended to run only one script file that contains all the .map
files of the turbines. On checkpoint, the GE GSM Monitor saves the last executed
AOS Start Script file and starts this file when the workstation reboots.

NOTE
The AOS Start Script file takes time to complete. The log messages at GE GSM
Manager logs a message when AOS script execution is complete. Then, AoAlm.exe
is displayed in the task manager.
If there are any errors during the execution of the AOS Script file, refer to the log
files at D:\opt\aos\logs.

The following is a sample script for Controller T1:

echo "******************* Starting T1 Configuration *******************"
/opt/aos/exe/aoCrt T1 -skipCSA
/opt/aos/exe/aoDel T1
# The AOSBUILDDB needs to be done only once per .map file.
# Therefore, once it has been done successfully, the AOSBUILDDB command line
# can be commented out because the AOSBUILDDB takes time
# for a large database - why do it again when it isn't necessary?
echo "************************************************************"
echo "* Building alarm database in SQL Server from T1.map file. *"
echo "************************************************************"
/opt/aos/scripts/AOSBUILDDB /opt/diw/di70/gegsm/data T1 T1.map
sleep 10
echo "************************************************************"
echo "* Creating the alarm objects for T1 in shared memory. *"
echo "************************************************************"
/opt/aos/scripts/AOSCREATE T1 forceCSA
sleep 10
echo "************************************************************"
echo "* Starting alarm object mapping and alarming for T1 *"
echo "************************************************************"
mkdir -p /opt/diw/di70/gegsm/logs/T1
/opt/aos/exe/aoSet -i 4 T1.pstat
sleep 10
NTSTART="/usr/fox/system32/startp /b"
echo "starting aoAlm "
$NTSTART d:/opt/aos/exe/aoAlm T1 -m /opt/diw/di70/gegsm/data
-l /opt/diw/di70 /gegsm /logs/T1
echo "******************* Completed T1 Configuration *******************"

To create a script file for a new controller, do the following:

a. Copy and paste the above sample script for Controller T1 in Notepad.
b. Search for T1 (controller name) and replace it with the name of the new controller
or alias name (specified for alarms in ECB Configuration).
c. Save the file.
d. Repeat steps a through c for all the controllers.

41
DI700DA – Rev D 6. Operation

e. Combine all the script files of the controllers and create a single AOS Start Script
file.
f. Refer to the installed AOS Start Script file ‘runaostx’ for controllers in T1 and T3,
in the D:\opt\diw\di70\gegsm\unedited_scripts folder.
g. Include sleep 120 at the beginning of the script file. This will add sleep time of
two minutes for I/A Series System to start at the time of reboot. Modify the sleep
time, if required.
h. Include exit 0 at the end of the script file.
i. Save the file.
3. In the GEGSM Manager window, browse and select the Alarm Tag Config File
and then click Start Alarming to start GEGSMAlarm.exe.

Figure 6-3. Starting Alarming

The Alarm Process ID is displayed, the Start Alarming button is disabled, and
the Stop Alarming button is enabled. The Alarm Process ID is added as a suffix
to the filename of the logs that are created by the Alarming application. The log files
are located at C:\ProgramData\Invensys\GEGSM\Logs\GEGSMAlarm.
The .csv file is optional; use this file only if GE tag names are used for Alarm points.
The GE GSM Alarm application forwards the alarms from the controller to the
CAD. Only one instance of GEGSMAlarm.exe is required for eight instances of the
driver.
If the Alarming application is started without selecting a .csv file, the GE GSM
Manager displays a confirmation dialog box. Click Yes to continue without a .csv
file or click No to cancel. If the user wants to deselect a .csv file, click the browse
icon and then click Cancel in the File Open dialog box without selecting a file.
The .csv filename in the Alarm Tag Config File field is deleted.

42
6. Operation DI700DA – Rev D

Figure 6-4. Adding an Instance

4. On the Controller menu, click New. The Add New Instance dialog box is dis-
played.

Figure 6-5. Adding an Instance - Cimplicity HMI

43
DI700DA – Rev D 6. Operation

Figure 6-6. Adding an Instance - Workstation ST HMI

5. In the Database File (.db) field, browse and select the file.
The GE GSM Manager populates the values for the Trace Level, Controller
Name and Turbine Name (if configured) fields from the selected .db file.
6. In the Trace Level list, select the required level.
7. Click ADD to add the new instance. The newly added instance is displayed under List
of Controllers in the left pane. The status of the instance will be UNRESOLVED
and it appears in cyan color.

44
6. Operation DI700DA – Rev D

The naming convention for an instance is Controller Name(Turbine Name)

and the name must be unique. Turbine Name is optional depending on whether or
not it is configured in the .db file.

Figure 6-7. GE GSM Manager with a Single Instance - Cimplicity HMI

45
DI700DA – Rev D 6. Operation

Figure 6-8. GE GSM Manager with a Single Instance - Workstation ST HMI

8. Under List of Controllers, select the instance.

9. On the Controller menu, click Go Online to start the instance. The details of the
selected controller are displayed in the right pane.
The Controller Status field displays:
♦ UNRESOLVED to indicate that no operation is performed on the instance
♦ GOOD to indicate that the instance is connected to the device after you click
Go Online
♦ FAIL to indicate that the instance is not connected to the device or is discon-
nected from the device
♦ OFFLINE when you click Go Offline.

46
6. Operation DI700DA – Rev D

NOTE
Refer to the Data Transfer Display on FoxView for the actual controller status based
on heartbeat point update.

The Instance Process ID field displays the process ID of GEGSMInstance.exe.

This ID is added as a suffix to the filename of the logs created by the driver. The log
files are located at C:\ProgramData\Invensys\GEGSM\Logs\GEGSMInstance.
10. Perform steps 1 through 9 (except step 3, to start the GEGSMAlarm.exe) to config-
ure a new instance for another turbine.
11. After configuring the instances for all the turbines, click the Check Point on File
menu to save the configuration in GE GSM Monitor. This enables a restore of the
configuration to the original state on I/A Series workstation reboot.
After completing the configuration, ensure that you click Checkpoint on the File menu. The
GE GSM Monitor saves the last executed AOS Start Script file, the Alarm application status with
.csv file, and the status of all the configured instances in the check point file. You can create the
check point file multiple times; the previous version is overwritten by the new version. The GE
GSM Manager displays “Check point success” message after completing the check point
operation.

NOTE
Ensure that the AOS Start Script file contains the script commands for all the
required instances and is started once before performing the check point operation.

Refer to “Troubleshooting” on page 57 for details about how to clear a check point.
The log messages displayed in the GE GSM Manager window contain the time stamp in local
time format and the source of the log message. In the log, error messages appear in red and
warnings appear in green. The log window displays only the last 100 log messages. To clear the
log, do one of the following:
♦ On the File menu, click Log and then click Clear Display or
♦ Under LOG, click Clear Display.
The log messages are also saved in C:\ProgramData\Invensys\GEGSM\Logs\GEGSMMonitor
folder. This log file contains the time in UTC format. To create a new log file, do one of the
following:
♦ On the File menu, click Log and then click New File or
♦ Under LOG, click Create New Log File.

Editing an Instance
♦ To lock and unlock alarms for a selected instance, click Open Alarm Manager on the
Controller menu. For more information, refer to “GE GSM Alarm Manager” on
page 49.
♦ To change the status of an instance to OFFLINE, click Go Offline on the Control-
ler menu. The menu item will switch between Go Online and Go Offline
depending on the status of an instance.

47
DI700DA – Rev D 6. Operation

The GE GSM Instance takes some time to execute a Go Offline request from the GE
GSM Manager. Proceed further only after the completion message "Completed Go
Offline Command for the Instance" is displayed in the GE GSM Manager log win-
dow.
♦ To delete an instance, select the instance from the List of Controllers, click
Delete on the Controller menu.

NOTE
You can delete an instance only if its status is UNRESOLVED or OFFLINE.

The configuration information of the GE GSM Manager is stored in GE GSM Monitor.

Whenever you close and open the GE GSM Manager, either from the same user account or from
a different user account, this information is retrieved to display the GE GSM Manager in the
original state.

Shutting Down GE GSM

To shutdown the GE GSM operation, do the following:
1. Under List of Controllers, delete all instances:
a. Select the instance. On the Controller menu, click Go Offline to change the
status to OFFLINE.
b. On the Controller menu, click Delete to delete the selected instance.
2. Click Stop Alarming to stop GEGSMAlarm.exe.
3. Click Stop AOS to stop AOS.
To stop AOS, the user need not specify a script file. The driver locates the *.map files
in D:\opt\diw\di70\gegsm\data folder and stops AOS for all the files. If a particular
AOS need not be stopped, delete the corresponding map file from the folder. After
AOS is stopped, the log window displays the “AOS stop execution complete” message.
4. Close the GE GSM Manager.

48
6. Operation DI700DA – Rev D

GE GSM Alarm Manager

Figure 6-9 shows the GE GSM alarm manager, a user interface that allows the user to view the
alarm lock state of each drop, toggle its lock state, and generate reports while the driver is
running. To toggle alarm lock state of a drop, the user can select a drop from the list or type the
drop number in the edit box (labeled 5 in Figure 6-9).

Figure 6-9. GE GSM Alarm Manager Dialog

The numbered labels are described as below:

1. ‘Alarm List for T1’ (labeled as 1 in Figure 6-9) initially shows up as “Alarm List” and
later when the driver gets connected to the GE HMI, as “Alarm List for <controller
name>”.

49
DI700DA – Rev D 6. Operation

2. Check box “Show locked alarms only” (labeled as 2 in Figure 6-9) when checked, dis-
plays only the locked alarms in the list box as in Figure 6-10, else it displays all the
alarms as shown in Figure 6-9.

Figure 6-10. GE GSM Alarm Manager Dialog

3. Alarm list (labeled as 3 in Figure 6-9) provides an option to select multiple drops at
once to toggle between lock states. The user can select only locked alarms or unlocked
alarms at a time. If there are no alarms displayed in the list box, all controls will be dis-
abled. Initially, this list shows all alarm drops and their status as reported by the HMI
server.
4. Check box “Alarm Drop” (labeled as 4 in Figure 6-9) provides an option to pick a
drop for status toggling either from the edit box below or from the list. When the
check box is selected, the drop number entered in the edit box is selected. When you
select any drop in alarm list, the check box gets unchecked automatically and the edit
box gets disabled.
5. Edit box for drop number (labeled as 5 in Figure 6-9) provides a field to type a drop
number. If the drop number exists in the list automatic scrolling of the list to display
the drop number in the GUI will occur. You cannot lock or unlock any drop, which
does not exist in the alarm list.
6. Lock/Unlock button (labeled as 6 in Figure 6-9) toggles the lock status of the selected
drop number. The drop number can be selected from the list or entered in the edit
box (labeled 5 in Figure 6-9). Once an alarm drop toggle lock status request is sent,
GUI controls get disabled until the driver receives a positive acknowledgement from
the GEHMI or a time out occurs. The time out is the number of drops selected for
toggle status multiplied by 2 seconds plus 10 seconds. You cannot request more than
25 alarm drops for toggle status at a time.

50
6. Operation DI700DA – Rev D

7. Report button (labeled as 7 in Figure 6-9) generates a report on lock status of all alarm
drops and saves it to a file. The file name used for the report has the format
"ar_<Instance name>.log” (for example: ar_T1.log). It overwrites an existing file with
the same name. Figure 6-11 displays the alarm report. The report files are saved in the
C:\ProgramData\Invensys\GEGSM\Logs\GEGSMManager folder.

Figure 6-11. Alarm Report

8. Close button or cross button or minimize button (labeled as 8 in Figure 6-9) makes
the Alarm GUI invisible. This interface can be made visible again on the screen by
clicking Open Alarm Manager on the Controller menu in the GE GSM Manager.
9. This interface can be made visible again on the screen using the Fox View menu
“Config->GEGSMSelect” as shown in Figure 6-9.

NOTE
Locking of Alarm drops from the Alarm Manager GUI will not clear any prior
Alarm massages for those drops on the CAD. The Alarm Messages still need to be
acknowledged manually from CAD to clear them from CAD display.

Alarm Discard on Backup Machine

This feature is applicable only in case of a redundant setup. Using this feature the user can choose
not to display the alarms received by the backup machine. Only the alarms received on the active
I/A Series workstation are displayed on the CAD. This avoids duplication of alarms on the CAD
display.

Use of GE GSM Configurator to Configure Alarm Discard from

Backup Machine
In the Alarm Configurator, a new column called “Enable alarm discard on backup” (refer
Figure 5-13) is used to specify if the alarms from Backup I/A Series workstation need to be
displayed or not. Selection can be made for each controller from the combo box in this column.
‘No’ implies that the alarms will be displayed on the backup machine. ‘Yes’ implies the alarms will

51
DI700DA – Rev D 6. Operation

be discarded on the backup machine. If none of the options is selected, then it is considered as a
‘No’.
The user can continue to use the databases configured with the older versions of the GSM
Configurator with the new versions of the driver, since by default this value will be taken as ‘No’
by the driver.
After configuring this value, the map file and db file have to be generated.

Data Transfer Display

Use the “Mark V/VI Data Transfer Display” to monitor that connection to the GE is completed
and OK. Completion of the connection might take several minutes depending on the number of
I/A Series Object Manager connections. To use the display, first choose the system type, Not
Redundant or Redundant, and second the turbine(s) (controllers) must be put on line by
selecting the Offline button for the turbine(s) (controllers).

Local Time Adjustment

Software is provided for the adjustment from Greenwich Mean Time to Local Time for Time
Stamping for the Alarming and Sequence-of-Events functions in the package. This function is
controlled by one entry on the ECB Configurator screen of the FGC, “Hours Diff From
Greenwich Mean Time”. This parameter may need to be changed if:
♦ It were set improperly during initial configuration.
♦ Daylight Savings Time adjustments need to be made.
To make the changes:
♦ Stop the driver processes.
♦ Make changes to the di70 .db file.
♦ Make changes to the .map file for each turbine controller.
♦ Restart the processes.
For the .db file the parameter is 5HDGMT.
For the .map file the parameter is GMTDEL.
For example, Boston uses U.S. Eastern Time. GMT is 5 hours greater than U.S. Eastern Standard
Time so the parameter would be set to -5. For Boston’s Daylight Savings Time adjustment, the
parameter is set to -6.

Current Alarm Display Usage

Turbine alarms from the GE turbines appear as I/A Series Alarm Displays when the GE GSM
driver is configured to support alarm handling. The GE alarms can be propagated to multiple
displays.

52
6. Operation DI700DA – Rev D

In the Current Alarm Display there are two lines of information for each turbine alarm. The first
line of the alarm display is:
C:B.P, Description, STATE, alarm/returned-to-normal,
acknowledged/unacknowledged
♦ For example, C:B.P may be T1:ALM_0050.STATE, where T1 designates the tur-
bine and 50 is the GE “drop number”. If the turbine name is T1, the compound
name is T1 on the primary I/A Series workstation and T1B on the backup I/A Series
workstation. P is always STATE.
♦ The Description field contains the description received from GE in the alarm
record (this is referred to as the “long name” in the GE documentation). The descrip-
tion may be up to 40 characters which results in the description being continued on
the second line of the display.
The second line of the alarm display is of the format:
Date Time, msecs, Pnt 1
♦ Date Time is
displayed as provided by the GE turbine.
♦ The milliseconds portion of the time stamp are provided after msecs. The millisec-
onds are represented by 6 digits, which are interpreted, as xxxxxx.
The turbine alarm can be acknowledged as can any alarm. The turbine alarm can be
acknowledged from any of the Alarm Displays. The following operational notes are of high
importance:

NOTE
The operator action to Clear Page and Clear Alarm must only be allowed if the Cur-
rent Alarm Display is customized to set the clear option to mark the alarm as
returned to normal and to acknowledge the alarm.

This is accomplished for each workstation by editing the file init.user, located in
d:/usr/fox/wp/data. The “clear option” (CLR_OPT) must be set to 2. Failure to make this Alarm
Display customization could result in GE alarms overflowing the queue in the GE machine. If the
GE queue overflows, new GE alarms are not transmitted to I/A Series software and are not
displayed on the GE HMI.

NOTE
If the primary or backup I/A Series workstation is disconnected from the GE (reboot
or cable disconnect) and the alarms associated with that GE connection are dis-
played at a separate workstation, any GE alarms on the CAD should be cleared from
the display before the I/A Series workstation is reconnected. This ensures that only
current GE alarm information is displayed on the Current Alarm Display (CAD).

53
DI700DA – Rev D 6. Operation

NOTE
For redundant operation, configure two CADs, one on each of two I/A Series work-
stations. Connect the primary CAD, the one that is configured to display all related
I/A Series alarms, with turbine alarms from the GSM driver in the primary
I/A Series workstation. Put the backup CAD on a separate I/A Series workstation.
The backup turbine alarm CAD should only display turbine alarms, no I/A Series
alarms. To avoid problems inherent in having multiple alarm databases being
updated simultaneously, and also to avoid operator confusion, keep the backup
CAD display turned off. Bring up the backup CAD display only if the I/A Series
workstation with the primary CAD has failed. From version 3.5.4 onwards, a new
feature is available to discard alarms on the backup machine. See section “Alarm
Discard on Backup Machine” on page 51 for more details.

NOTE
An Alarm Dump may be forced by plant personnel. See “Forcing an Alarm Update”
on page 55.

Limitations of Alarm Synchronization After I/A Series

Workstation Reboot
Limitation: Alarm Synchronization of Remote CADs After
I/A Series Workstation Reboot
When It Applies
This limitation applies if GE GSM alarms are sent to CAD displays other than the one on the
I/A Series workstation hosting the GE GSM software.
Issue
The Alarm Manager database in a I/A Series workstation/WP is totally independent of the actual
alarm state of the controllers. If a controller reboots while the WP is displaying an alarm - for
example, a high flow - and as alarmed condition returns to normal before the controller reboots,
e.g., the flow goes within range, then the WP will not be notified of the return to normal of the
alarm since the CP will not know that the alarm existed before the reboot.
Similarly, if the I/A Series workstation used to generate alarms reboots and alarms clear in the GE
device, the alarm state of “remote” CADs do not reflect the cleared alarms in the GE device
because the I/A Series workstation does not know that they were in alarm prior to the reboot.
Workaround
If “remote” CADs are being used, the following procedure can be used to bring the “remote”
CADs in to synchronization with the actual alarm state:
1. On each “remote” CAD, use the CLEAR button to remove the alarms from the GE
GSM system.

54
6. Operation DI700DA – Rev D

2. Once all of the “remote” CADs are cleared, trigger an alarm update from the GE
GSM gateway software. This will cause the software to reissue all active alarm
messages.

Limitation: Use of Common Alarm Group and WP CAD Backup

When It Applies
This issue applies if the user tries to configure the GE GSM interface software host in a Common
Alarm Group.
Issue
The I/A Series workstation used to host the GE GSM software must not be configured to have a
WP backup for its CAD display. If it is so configured, it will recover a probably incorrect alarm
state from the WP used as its backup.
Workaround
Do not specify a WP backup for the I/A Series workstation used to host the GE GSM interface
software. If it is included in the CAG, the Workaround described under "ALARM
SYNCHRONIZATION AFTER I/A SERIES WORKSTATION REBOOT" should be used to
bring the representation of the GE GSM alarms into synchronization on all members of the CAG
including the I/A Series workstation hosting the GE GSM interface software.

Forcing an Alarm Update

When alarms are configured in the database the potential to force an alarm update is included.
The database contains a pseudo block for ALARM DUMP COMMAND. The Alarm Update is
forced by changing the value of the .OUT parameter of the controllernameALARMDUMP
block in the HEARTBEAT compound.
No pushbutton display to exercise this feature is provided.

Alarm System Error Messages

Heavy alarm activity for a turbine controller (i.e., GE alarming points going into/out of alarm
rapidly – “chattering”) may cause unwanted system side effects such as heavy CPU usage and
system memory queue build-up. During periods of such activity, when the alarm memory queue
for a turbine controller reaches 500 entries, a warning message is sent to the CAD:
ALM_0601 ALARM SYSTEM OVERLOAD WARNING
If the cause of the problem is not fixed and the memory queue reaches its limit (600 entries), this
failure message is sent to the CAD:
ALM_0600 ALARM SYSTEM FAILURE
No more GE alarms are sent to the CAD until the cause of the problem is fixed and the operator
forces an alarm dump. (See “Forcing an Alarm Update” on page 55.)
The ALM numbers used are the last two alarm points configured. If 600 alarm points are
configured with FGC, 602 alarm points are actually created, and last two are used for this feature.

55
DI700DA – Rev D 6. Operation

Alarm Drop Number Restriction

Alarm drop numbers must begin with zero.
For example, if the GE HMI has alarm drop numbers beginning with “600”, the alarms must be
“repacked” by GE to start at zero (0).

SOE Interface
The Schneider Electric Foxboro Power Group SOE package is required to use the GE GSM driver
SOE interface. It is not needed for the Data Interface or the Alarm Interface. The SOE package
can be installed on any I/A Series workstation that is on the same I/A Series network as the GE
GSM driver.
To use the SOE interface you must purchase the SOE package and install it on your I/A Series
system.1
The Schneider Electric Foxboro GE GSM Driver passes all event messages to the SOE package if
so configured, but you should note that there may be differences between the Mark V and the
Mark VI as to what events can be configured in the Turbine controller and there are differences in
the “G” processor and the GE HMI processor running Cimplicity, as to what kinds of events can
be passed through the GSM interface. Consult GE documentation to determine what events the
turbine, turbine controller and GE gateway support for display in an SOE package.
Both the GE GSM Driver and the Schneider Electric Foxboro Power Group SOE package can
support redundant connections to the turbine controllers for SOE events. The GE GSM Driver
only sends SOE messages to a single instance of the SOE package, for example SOE01. When the
GE GSM Driver is redundant, each I/A Series workstation sends the same SOE message to the
same SOE destination and the SOE package throws away duplicates.

Load Testing
Alarm Tests
Testing was done with a simulation of two turbine controllers, alarm messages being received in
two alarm packets at a rate of 10 messages per second on controller1 and 4 messages per second
on controller2.
Results:
Windows: less than 10% load
Conclusions: Normal alarm handling is no problem. However, “chattering” alarms cause system
loading problems and must be eliminated.

1.
For this item, contact your local sales representative or call 1-866-746-6477.

56
6. Operation DI700DA – Rev D

Troubleshooting
General Approach
♦ Make sure correct parameters are set for “Trace Level” and “Print Error Message” on
ECB Configurator in order to get the log files. The correct configuration for verbose
logging is, 1 for “Trace Level” and 3 for “Print Error Message”.
♦ Verify that communication has been established between driver and the controller.
This can be verified by looking into the di<PID>.log file where send and receive pack-
ets (in hexadecimal format) can be seen (see section “Analyzing Log File to Find
Send/Receive Packets” on page 58).
♦ If no packets are seen in the log file first run a ping command on the station where
driver is installed as following:
♦ Open a command prompt and run following
♦ Ping <IP Address of controller>
If above ping command fails then check your network connection and cables. Also
verify the IP address of controller is correct.
If ping command is successful but communication could not be established then ver-
ify that port number configured in "5PORT" field of the .db file and at GE side are
same.
♦ Communication still could not be established make sure firewall is turned off on the
station where driver is installed.
♦ If alarm data are not seen on the CAD then check if the log file has message logged
“ALARM DUMP message received for Controller”. This message is logged in the log
file when driver is started and initially it receives current status of alarms. If this mes-
sage is not logged make sure parameter “Establish Request Selection” has been
correctly configured on ECB Configurator.
♦ If using alias name for alarms then make sure the script file you are using to start the
AOS is also having alias name entries not turbine name.
♦ If the log window displays the error message 'Can't Open Pipe....' then restart the
Alarming application (Click Stop Alarming and then click Start Alarming in the
GE GSM Manager window).
♦ Restart the AIM API Services if the heartbeat point is not incrementing or if the log
window displays the error message 'Open set returns error -1'.
♦ To clear a checkpoint (undo check point), delete the 'CheckPointInfo.txt' file from
the C:\Programdata\Invensys\GEGSM folder.
♦ If SOE is configured in the .db file and if there is a delay in displaying the Alarms in
the CAD, then check if the configured SOE destination in the .db file is available in
the network and the soe.exe is running in the configured workstation. If soe.exe is not
running, then start the soe.exe and verify if the issue is resolved.

57
DI700DA – Rev D 6. Operation

Analyzing Log File to Find Send/Receive Packets

Following is a snippet of di<PID>.log file. The line starts with SND is the packet send by the
driver and the line starts with RCV is the packet received by the driver.
SND (2) Fri Jan 16 15:44:29 2009 size=6 pid=4444
0000 04 00 00 01 dd 03 ................
END binary dump Fri Jan 16 15:44:29 2009 di_send_msg pid = 4444

RCV (2) Fri Jan 20 15:44:29 2009 size=92, pid=4444

0000 5a 00 01 01 dd 03 00 80 9a 00 80 4f 00 00 81 12 Z..........O....
0010 00 00 10 02 00 47 32 10 10 02 00 01 00 20 10 02 .....G2...... ..
0020 00 01 00 00 81 1a 00 00 10 0a 00 43 49 4d 50 4c ...........CIMPL
0030 49 43 49 54 59 10 10 02 00 01 00 20 10 02 00 02 ICITY...... ....
0040 00 00 81 13 00 00 10 03 00 45 47 44 10 10 02 00 .........EGD....
0050 01 00 20 10 02 00 03 00 00 00 00 00 .. .............
END binary dump Fri Jan 16 15:44:29 2009 di_rcv_msg pid = 4444
SUPPORTED UNIT Response message received Fri Jan 16 15:44:29 2009 gsm_prot pid = 4444
RCV (2) Fri Jan 16 15:44:30 2009 size=155, pid=4444

58
7. I/A Series Block Control

Overview
Pre-3.0 versions of the GSM Driver required that the user configure each GSM message in an
ASCII file to be located in the I/A Series workstation. For redundant implementations, two files
were needed, one for each I/A Series workstation but different from each other in that they
addressed different points in each switch block in the CP. Redundant versions also required the
user to configure a CP database to fit the I/A Series workstation databases.
Starting at version 3.0, the user configures a spreadsheet list of the points to be connected to tur-
bines, using the GSM Configurator. The GSM Configurator is an application included with the
product, which creates the needed operational files that are detailed in Chapter 5 “Configuring
the GE GSM Interface”.
A user can upgrade to version 4.0 without using the GSM Configurator but that process is not
described in this User’s Guide. See Chapter 1 “General Description” for other differences between
version 4.0 and earlier versions of the GSM driver.
The files that the GSM driver uses in operation have two parts.
1. Blocks which must be in a CP.
2. A text file in the I/A Series workstation that tells the GE GSM Driver process in the
Windows-based I/A Series workstation how to connect the blocks to the turbine con-
trollers.
Figure 7-1 shows an overview of how the communications between the workstations and blocks
are carried out. In Figure 7-1 dotted lines indicate control; solid lines indicate data.
The GE GSM Driver database is a file created using the DI70 Configuration Tool (FGC) as
described in Chapter 5 “Configuring the GE GSM Interface”.

Redundant Block Control

A set of CALC blocks and SWCH blocks are programmed to control the high availability redun-
dant connection capability of the interface. These are connected as shown in Figure 7-1.
The following are descriptions of the redundant calculations provided for the DI-70 Software for
one to four units. There may be one or more fault tolerant control processors.
MARKV:DISPFUNC
This CALC block is for all four units. The block functions are for the redundant dis-
play. In addition to the calculation in the block for the display, the inputs for the
block are used for the display. Notes below show some of the inputs display function.
INPUT BI08:
If this input is set to a one (1) the redundant display displays information for selecting
redundant operations.

59
DI700DA – Rev D 7. I/A Series Block Control

NOTE
You may find it helpful to refer to Figure 7-1 as you read the following sections.

MARKV:T1 (HEARTBEAT CALC Block)

The block name T1 may be changed to reflect the controller naming convention of
the installation, but if this is done the Display Configurator (FoxDraw) must then be
used to change the block connections for the “Data Transfer Display” correspond-
ingly. The blocks may be created in one or more compounds. The functions of this
block are as follows:
1. To select which of the two I/A Series workstations is “in the Primary Mode” and
which is “in the Secondary Mode”. If the block’s input BI02 is equal to zero (0) then
AW01 is selected as Primary. If the blocks input BI02 is equal to one (1) then AW02 is
selected as Primary. This input is set by the overlay display.
2. To determine whether or not the Primary and Secondary I/A Series workstation’s
heartbeat has failed. If the output BO01 is equal to zero (0) the Primary I/A Series
workstation’s heartbeat has failed. If the output BO01 is equal to one (1) the Primary
I/A Series workstation’s heartbeat has not failed. If the output BO02 is equal to zero
(0) the Secondary I/A Series workstation’s heartbeat has failed. If the output BO02 is
equal to one (1) the Secondary I/A Series workstation’s heartbeat has not failed.
3. To select if the Turbine Controller is Online or Offline. IF the blocks input BI01 is
equal to zero (0) then the controller is selected Off Line. IF the blocks input BI01 is
equal to one (1) then the controller is selected On Line. This input is set by the over-
lay display.
4. To determine if the Primary and Secondary I/A Series workstations are In Service: If
the output RO01 is equal to zero (0) the Primary I/A Series workstation is In Service.
If the output RO01 is equal to one (1) the Primary I/A Series workstation is Out Of
Service. If the output RO02 is equal to zero (0) the Secondary I/A Series workstation
is In Service. If the output RO02 is equal to one (1) the Secondary I/A Series worksta-
tion is Out Of Service.

Delay Switching Block

Figure 7-2 illustrates the Delay Switching Signal block used to delay primary/backup switchover
to allow the driver to receive current GE input data on the newly active I/A Series workstation.

SWCH Block
This block determines from which Workstation the GE input data will be processed. The inputs
to this SWCH block include Real, Integer, Long Integer, and Boolean values from AW-01 and
AW-02. INP1 is the input from AW-01 and INP2 is the same exact input but from AW-02. The
SWCH block is toggled based on the value of RO01 from the connected CALC block.

60
7. I/A Series Block Control DI700DA – Rev D

Figure 7-1. Communication Between Workstations and Blocks

61
DI700DA – Rev D 7. I/A Series Block Control

PULSE OUT
TD ON
SET OUT (RO01)
Input edge

IN (RI01)

PULSE OUT
RESET
TD OFF Input edge

Figure 7-2. Logic for Delay CALC block, MARK V_SW

Function: Delay switching signal to SW blocks. There is one of these for each turbine controller.

GE MARK V Data Transfer Display

The GE MARK V Data Transfer display allows the option of viewing a “Redundant” or “Not
Redundant” type process for transferring GE MARK V GAS TURBINE data. The first step to
using this display is to choose the process of interest, “Redundant or Not Redundant” from the
buttons at the bottom of the screen.

62
7. I/A Series Block Control DI700DA – Rev D

Figure 7-3. Data Transfer Status Display

The pick box bordering “OFFLINE” calls a pop-up enabling selection of whether the turbine
controller data transfer to the Control Processor is “ONLINE or OFFLINE”. The Turbine
Select button at the lower left portion of the display allows a selected view of up to four gas tur-
bine controllers. You must be in the proper environment to make the type of selections previously
mentioned from this display. If “Redundant” is picked as the process of interest and TURBINE 1
(Controller 1) is put ONLINE, the display looks similar to that of Figure 7-4, assuming that a
heartbeat is available from both workstations.

NOTE
The heading of the display may be changed using Display Builder/FoxDraw soft-
ware to reflect MARK VI if necessary. References to “Turbine” should instead be
“Controller.”

63
DI700DA – Rev D 7. I/A Series Block Control

Figure 7-4. Data Transfer Status Display

The status of each gas turbine controller is shown relative to each workstation. There are three
pick boxes per turbine controller. The “OFF/ON LINE” pick was mentioned above and the other
two pick boxes call the same pop-up enabling selection to swap the data communications from
one workstation to the other, Primary vs. Backup. The text field below the Primary vs. Backup
pick box indicates if the heartbeat is “Failed”, “Not Failed”, or “OOS” (Out Of Service). The bot-
tom text field indicates if the Workstation is “ACTIVE” meaning this is the Workstation transfer-
ring the data, or “NOT ACTIVE” meaning this is the Workstation that is not transferring the
data.

NOTE
The heading of the display may be changed using Display Builder/FoxDraw soft-
ware to reflect MARK VI if necessary. References to “Turbine” should instead be
“Controller.”

64
8. Message Logging

Communication Level
The GE GSM Driver checks received messages for receive errors. If an error is detected, the mes-
sage is discarded. It also checks that an output message is successfully transmitted. If retries are
configured Alarm Command and Process Command request messages are retried. If communica-
tion is successful but the data indicates that the GE device is unable to communicate with a spe-
cific unit, that unit’s status (as observed on the Transfer Status Display) is set to FAILED.
The ‘number of retries’ are configured by the ECRECT parameter of the ECB70 GE GSM Driver
block.
Success of a Process Control command is best determined by monitoring feedback from the GE
Processor as Periodic Data since the GE processor only signals an acknowledgement of a received
command, not completion of the command.

Physical Level
Failure to receive the Supported Unit request informs the GE GSM Driver, by use of the
HEARTBEAT CALC block, of the bad communication status based on the period of the CALC
block and the CALC block logic.
Upon detection of failure of the Ethernet connection (which takes 1 minute) all I/A Series points
named in the DI70 database are set Out_Of_Service. Upon reconnection of the Ethernet (which
takes about 4 seconds) the I/A Series points are set In_Service.
The status of the Ethernet connection is available to a shared variable or compound:block.param-
eter connection. Refer to the ECSTAT parameter for the ECB70 GE GSM Driver block. The sta-
tus is set to 1 for a good connection or 0 for a loss of connection. Should the Ethernet cable
connection be lost, the GE GSM Driver application is notified that an output message was unde-
liverable and the connection status is set to ‘0’. This could take 1 minute to be recognized. On
reconnection of the Ethernet cable, the connection is re-established.
TCP/IP error messages are reported in the dipid.log file and described in a later part of this
chapter.

DI70 Log File

NOTE
Using this logging mechanism adds significant CP overhead and should not be used
after start-up testing. It particularly causes problems when logging is done for more
than one turbine controller process. The logging can be disabled by setting the di70
database file (.db) parameters 5TRCLV and 5PERR to zero (0). After using the files
they should be removed because of file space concerns.

Protocol type error messages (Message received with bad message length and so forth)
are reported in the GE GSM Driver’s log files which are named using the value of the ECB70

65
DI700DA – Rev D 8. Message Logging

5TRPRE parameter and the process id with the .log file extension. An example of the two log file
names might be di789.log and didb789.log if 5TRPRE=di and the process id is 789. The files are
designed to be circular files with a size configured in the ECB70 block, 5MXLOG. The amount
of information stored in the dipid.log file is also definable in the ECB70 block. Setting the ecb70
parameter 5PERR=3 gives the most verbose .log file entries and the descriptions below reflect this
setting. All transmitted messages are sent to the dipid.log file. The log files should be reviewed to
determine that 1. AIM*API has found the I/A Series C:B.P points defined in the di70 database,
and 2 to check that the GE is responding as desired. Since this log file is circular, events, which
occur at start up of the process, may be overwritten. The second log file is also created which is
named similarly using the process id but with the letters “db” following the 5TRPRE value (for
example, Didb789.log). This log file contains the database OM connection information logged at
start up and other information that occurs infrequently. This log file was added because the first
file may rapidly overwrite the startup database information. These log files are found in C:\Pro-
gramdata\Invensys\GEGSM\Logs\GEGSMInstance.

TCP/IP Connection
The dipid.log file should be checked a short time after starting the interface, perhaps 20 minutes.
If AIM*API finds no errors associated with I/A Series points, and the software successfully con-
nects to the TCP/IP server (GE Gateway, “G” Processor or HMI device), the first message in the
log file is RECONNECT message received …. If the software has problems connecting to the GE,
the error messages are obvious.

AIM*API Connections to I/A Series Blocks

Non-Fatal Errors
If AIM*API returns error codes for the I/A Series points, the code for each point in the DI data-
base will be reported in didbpid.log along with its error code. If no fatal error is found, the
RECONNECT message follows the last AIM*API error code message. If V finds an error, the mes-
sages have the format: block NAME entry = nnn name = IAPOINTNAME error=xxx, ….,
where nnn is the AIM*API “list” entry number, and error is the Object Manager status. The
value is displayed in the log file as an integer, and must be translated to hex for analysis. Positive
value codes appear for non-fatal statuses. An example of a non-fatal status is 547, which translates
to 223 hex. This bit pattern is 0000 0010 0010 0011 (where bit zero is at the least significant
position). Bits 0 and 1 indicate a float value, bit 5 indicates the point is being scanned, and bit 9
indicates the point is secured (member of a write list; an input value from GE). Notice that this
status is perfectly proper and thus should be ignored. An example of a non-fatal code that requires
the engineer’s attention is 2597, which translates to A25 hex. This bit pattern is 0000 1010 0010
0101. Bits 0 to 2 indicate a 1-byte boolean value, bit 5 indicates the point is being scanned, bit 9
means the point is secured, but bit 11 indicates the point is out-of-service.

Fatal Errors
An error value of 0 or -1 associated with an individual point results in a fatal error and the GE
GSM Instance exits before attempting connection to the GE.
Fatal errors also occur if AIM*API is unable to open a data set. This error type produces one of
the following diagnostic errors in the didbpid.log file:
FATAL: Write Data set did not open because one or more duplicate
points exist in the database file, reterr = 26

66
8. Message Logging DI700DA – Rev D

FATAL: Write Data set did not open, reterr = x

FATAL: Read Data set did not open, reterr = x
where x indicates the AIM*API error code.

Protocol Level Messages

The bytes sent/received are recorded in the dipid.log file. A description entry appears for each
message. The description entry precedes each message sent to the GE, and follows each message
received from the GE.

Supported Unit Request Message

These messages are sent to the GE every two seconds and request the current link status.
These messages are preceded by the message:
SUPPORTED UNIT Command message sent

Supported Unit Response Message

These messages are received from the GE and are the response to the Supported Unit Request.
The GE status is reported in this message.
These messages are followed by the message:
SUPPORTED UNIT Response message received
If the connection is working fine, there is no need to inspect the response message.
MARK V with ‘G’ Processor:
To determine if the paths to all the turbine controllers are connected correctly, scan the bytes in
the message for the hex string: 00 10 02 00 xx xx where xx xx is the unit name, for example 54 31
(T1). Following this, but not necessarily immediately following, is the hex string: 10 10 02 00 xx
00 where xx is the number of active paths for the controller. On the Mark V the number of paths
is one. If the number of paths is 0, either the physical connectors are not installed correctly (for
example, are they terminated properly?) or the GE is experiencing a problem on its network. In
this case the Heartbeat CALC block is not updated and the following message is entered in the log
file:
Heartbeat CALC block for Turbine xx not updated because no active
links found
MARK VI with CIMPLICITY:
Within the message the Cimplicity record is begun by the Unit Name item: 00 10 0a 00 43 49 4d
50 4c 49 43 49 54 59. Following this is the item indicating if the Cimplicity program is running:
10 10 02 00 xx 00 where 01 indicates it is running. If the Cimplicity program is not running the
Heartbeat CALC blocks will not be updated and the following message is entered in the log file:
Heartbeat CALC block for Turbine xx not updated because Cimplicity
off or Periodic Data messages not being received

MARK VI with Workstation ST:

Within the message, the configured controller name must be included. If the controller name is
not included, the Heartbeat CALC blocks will not be updated.

67
DI700DA – Rev D 8. Message Logging

Heartbeat Message
GE requires these messages to be sent at least every 20 seconds. Failure results in a soft disconnect
from GE, which requires restarting the GE GSM Driver.
These messages are preceded by the message:
HEARTBEAT Command message sent for Controller x

Alarm Record Establish Message

These messages are sent for each turbine to request alarm information. If this message is not sent
for a turbine, the GE does not send alarms for the turbine. This feature is selected in the FGC
ECB configuration by entering the appropriate “Establish Request Selection”.
This message is preceded by the message:
ALARM RECORD ESTABLISH Command message sent for Controller xx

Alarm Record Establish ACK/NAK Message

This message is followed by the messages:
ALARM RECORD ESTABLISH ACK/NAK for Controller xx
ACK / NAK Status = ack/nak code
The ack/nak codes are:
0- Success.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.
-2 - Function not supported by process controller.
Resolution: Send the dipid.log to CSC.
-3 - Gateway distribution list table is full.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-4 - Malformed request.
Resolution: Send the dipid.log and didbpid.log files to CSC.

Digital Input Record Establish Request Message

These messages are sent for each turbine to request Digital Input Event information. If the mes-
sage is not sent for a turbine, the GE does not send Digital Input Event information for the tur-
bine. This feature is selected in the FGC ECB configuration by entering the appropriate
“Establish Request Selection”.
This message is preceded by the message:
DIGIN RECORD ESTABLISH Command message sent for Controller xx

Digital Input Record Establish ACK/NAK Message

This message is followed by the messages:
DIGITAL INPUT RECORD ESTABLISH ACK/NAK for Controller xx
ACK / NAK Status = ack/nak code

68
8. Message Logging DI700DA – Rev D

The ack/nak codes are:

0- Success.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.
-2 - Function not supported by process controller.
Resolution: Send the dipid.log to CSC.
-3 - Gateway distribution list table is full.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-4 - Malformed request.
Resolution: Send the dipid.log and didbpid.log files to CSC.

Digital Input Data Message

These messages contain information about a Digital Input Event. This information is passed to
the SOE package. Information includes time stamp, point name, point description, and state.
These messages are followed by the message:
DIGIN Data message received for Controller xx
If the GE GSM Driver is operating in the Redundant mode, Digital Input Data messages received
at the BACKUP I/A Series workstation are discarded as indicated in the log file by the following
message:
Digital Input Event message discarded for Controller xx

Software Event Record Establish Request Message

These messages are sent for each turbine to request Software Event information. If the message is
not sent for a turbine, the GE does not send Software Event information for the turbine. This fea-
ture is selected in the FGC ECB configuration by entering the appropriate “Establish Request
Selection”.
This message is preceded by the message:
S/W EVENT RECORD ESTABLISH Command message sent for Controller xx

Software Event Record Establish ACK/NAK Message

This message is followed by the messages:
SOFTWARE EVENT RECORD ESTABLISH ACK/NAK for Controller xx
ACK / NAK Status = ack/nak code
The ack/nak codes are:
0- Success.
+1 - Request received by GE gateway, but communications with process controller is not
currently possible.
Resolution: The GE GSM Driver will re-issue the Alarm Command message. If
problem persists, contact GE.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.

69
DI700DA – Rev D 8. Message Logging

-2 - Function not supported by process controller.

Resolution: Send the dipid.log to CSC.
-3 - Gateway distribution list table is full.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-4 - Malformed request.
Resolution: Send the dipid.log and didbpid.log files to CSC.

Software Event Data Message

These messages contain information about a Software Event. This information is passed to the
SOE package. Information includes time stamp, point name, point description, and state.
These messages are followed by the message:
S/W EVENT Data message received for Controller xx
If the GE GSM Driver is operating in the Redundant mode, Software Event Data messages
received at the BACKUP I/A Series workstation are discarded as indicated in the log file by the
following message:
Software Event message discarded for Controller xx

Periodic Data Request Message

These messages contain the GE points for which the data will be sent periodically by GE. A set of
these messages is sent for each turbine. Each message contains a list of points. The contents of the
lists are defined in the FGC using the Input File spreadsheets, and each sheet represents a list of
points. The transmit frequency (defaulted to 2 seconds) may also be defined on the spreadsheets.
These messages are preceded by the message:
PERIODIC DATA Command message sent for Controller xx
This message is not processed by the di70 software if no matching Periodic Data Response mes-
sage is found, and a diagnostic message is entered in the log file:
Periodic Data Request message for Controller xx, List yy has no cor-
responding Periodic Data message

Periodic Data List Establish ACK/NAK Message

This message is followed by the messages:
PERIODIC DATA LIST ESTABLISH ACK/NAK for Controller xx, List yy
ACK / NAK Status = ack/nak code
The ack/nak codes are:
0- Success.
+1 - Request received by GE gateway, but communications with process controller is not
currently possible.
Resolution: The GE GSM Driver will re-issue the Alarm Command message. If
problem persists, contact GE.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.
-2 - Function not supported by process controller.
Resolution: Send the dipid.log to CSC.

70
8. Message Logging DI700DA – Rev D

-3 - Gateway distribution list table is full.

Resolution: Send the dipid.log and didbpid.log files to CSC.
-4 - Malformed request.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-5 - Internal GE gateway error.
Resolution: Contact GE.
-6 - All points requested are undefined.
Resolution: Correct the configuration.
-7 - Too many data points defined in request.
Resolution: Correct the configuration.

Periodic Data Message

These messages, received periodically, contain the GE point value.
These messages are followed by the message:
PERIODIC Data message received for Controller xx, List yy
When connected to GE MARK VI, if no Periodic Data messages are received from a turbine for 5
consecutive periods, each I/A Series point associated with the controller is marked OOS.
The following information is found in the dipid.log file.
Each point value is presented in the following format:
60 10 xx 00 value
where:
xx indicates the number of bytes in the value field.
Exception: A point that GE is unable to report has a value length of 0 and no value bytes
are present.
When the GE is unable to report a value, the GE GSM Driver software creates a diagnostic mes-
sage for each point with no value and enters it in the log file:
GE sent no data for point 'n' (base 0) because it can't be found in GE
database or is Out-Of-Service
The corresponding I/A Series point is marked OOS.
It is the responsibility of the database Engineer to correct the invalid GE point name in the associ-
ated Periodic Data Response record in the di70 database.
If the GE GSM Driver is operating in the Redundant mode, Periodic Data messages received at
the BACKUP I/A Series workstation are discarded as indicated in the log file by the following
message:
Periodic data message discarded for Controller xx, List yy
For a Mark VI if the Cimplicity software is functional but the GE does not send Periodic Data
messages, indicating failure of the link to the controller or the turbine itself, the di70 software cre-
ates a diagnostic message in the log file:
Heartbeat CALC block for Controller xx not updated because Cimplicity
off or Periodic Data messages not being received

71
DI700DA – Rev D 8. Message Logging

Redundant configurations receive Periodic Data on both I/A Series workstations but this data is
passed to I/A Series blocks only on the ACTIVE connection. The Periodic Data message on the
NOT ACTIVE connection is discarded and a diagnostic message is put in the log file:
Periodic data message discarded Controller xx, List yy

Alarm Command Messages

These messages are sent to the GE as required to facilitate the alarm information flow. These mes-
sages request alarm dumps, acknowledge alarms, and reset alarms. These commands are typically
handled internally, but an Alarm Dump may be requested manually as described in “Forcing an
Alarm Update” on page 55.
These messages are preceded by the message:
ALARM Command message sent Controller xx

Alarm Command ACK/NAK Message

These messages are followed by the messages:
ALARM COMMAND ACK/NAK Controller xx
ACK / NAK Status = ack/nak code
The ack/nak codes are:
0- Success.
+1 - Request received by GE gateway, but communications with process controller is not
currently possible.
Resolution: The GE GSM Driver will re-issue the Alarm Command message. If
problem persists, contact GE.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.
-2 - Function not supported by process controller.
Resolution: Send the dipid.log to CSC.
-3 - Gateway distribution list table is full.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-4 - Malformed request.
Resolution: Send the dipid.log and didbpid.log files to CSC.
-5 - Internal GE gateway error.
Resolution: Contact GE.

Alarm Data Message

These messages contain information about current alarms. A message may hold information
about one or more alarm events. The GE GSM Driver uses the information to update the
I/A Series Alarm Display system.
This message is followed by the following message:
ALARM Data message received for Controller xx

72
8. Message Logging DI700DA – Rev D

Alarm Dump Message

These messages contain information about all the alarms currently in the GE alarm queue. One of
these messages may contain information about 40 alarms. It may take up to four of these messages
to report all the GE alarms. The GE GSM Driver uses the information to update the I/A Series
Alarm Display system.
This message is followed by the following message:
ALARM Dump message received for Controller xx

Process Control Command Message

These messages are sent to the GE to request set point or pushbutton control changes. Requests to
send these messages are created from the FGC by selecting Open Setpoint File #x or Open
Push Button file #x (“x” represents the controller number 1 through 8). These outputs are
change driven and are set when the output value of a connected I/A Series block changes.
These messages are preceded by the message:
PROCESS CONTROL Command message sent for Controller xx
Redundant configurations send out to the GE only on the ACTIVE connection. The Process
Control message on the NOT ACTIVE connection is discarded and a diagnostic message is put
in the log file:
PROCESS CONTROL message discarded for Controller xx

Process Control ACK/NAK Message

These messages are followed by the messages:
PROCESS CONTROL ACK/NAK Controller xx
ACK / NAK Status = ack/nak code
The ack/nak codes are:
0- Success.
+1 - Request received by GE gateway, but communications with process controller is not
currently possible.
Resolution: I/A Series application design must monitor feedback from GE and re-
issue the Process Control Command message.
-1 - Unknown Controller Name.
Resolution: Contact GE to determine the correct Controller Name (turbine name)
and the correct database configuration.
-2 - Function not supported by process controller.
Resolution: Send the dipid.log to CSC.
-3 - Invalid command.
Resolution: Send the dipid.log to CSC.
-4 - Invalid parameter (i.e. Value for “Push Button” or no value for a set point target.)
Resolution: Send database file and dipid.log file to CSC.

73
DI700DA – Rev D 8. Message Logging

-5 - Internal GE gateway error.

Resolution: Contact GE.
-6 - Control hierarchy
Resolution: This error occurs on GAS Turbines only; there is a GE point named
I_C_CTRL_1 that is set to a value that does not allow the desired GE point to be
changed by the DCS through the Ethernet connection. The value of I_C_CTRL_1
is site specific and must be changed by a GE engineer.

Primary/Backup Control Message

When this internal message is processed by the di70 software indicating a change in state of the
MARK?:T?.RO01 point (for the primary I/A Series workstation) or MARK?:T?.RO02 point (for
the backup I/A Series workstation), the following message is put into the log file:
PRIMARY/BACKUP message processed for Controller xx: discard = {0,1}
where the value “discard” is the state of the point: 0 = process data messages, 1 = discard input
data messages and don’t resend output commands.
When a DI70 enters the “discard messages” state for a controller, each associated I/A Series point
is set OOS, and each associated point is set good when the “process data messages state” is
entered.

Alarming Log
The alarming program creates a file of the form Pxalarmpid.log, where x is the message pipe, 1-
8, and is directly associated with the controller defined as 1-8. This log file does not create a sig-
nificant load on the processor because only a few alarms occur at any time. This file has start-up
information and information about every alarm state change. The files main use is diagnostics.
These log files are found in C:\Programdata\Invensys\GEGSM\Logs\GEGSMAlarm. Send these
files to CSC if alarming problems exist.

AOS Error Logging

When AOS is started, it creates various log files. Send these log files to CSC if alarming problems
exist:
d:\opt\aos\logs : aos_create and aos_builddb
More AOS Troubleshooting suggestions may be found in “Troubleshooting” on page 82 in
Chapter 10 “Installing AOS”.

74
9. Verifying AIM*API Version
The GSM driver uses AIM*API to connect to I/A Series blocks for the data interface and for the
Alarm Interface. AIM*API must be version 5.5.0 or later. It can be updated from the Global Cus-
tomer Support Center, if needed. To determine the installed version of AIM*API, use a command
window:
1. Enter:
cd /opt/aim/bin (or cd \opt\aim\bin)
2. Enter:
apitst
3. Enter:
1229
Observe the monitor output: AIM*API_version must be 5.5.0 or later.
4. Enter:
-1
to exit the tester.

75
DI700DA – Rev D 9. Verifying AIM*API Version

76
10. Installing AOS
The AOS for Windows software ships on a CD-ROM. Installation consists of these steps:
1. Install any relevant Foxboro I/A Series Quick Fixes as per Quick Fix Installation
instructions. The AIM*API software has frequent upgrades, so check with the
Customer Satisfaction Center for the latest version.
2. Install and configure the SQL Server software package and enable this software to start
on reboot.
3. Install the Application Object Services software.
4. Configure I/A Series software to support the required number of Application Objects.

NOTE
The operating system is modified to allow larger numbers of Object Manager
Objects to be created. Refer to “Resizing the I/A Series System” on page 79. This
modification requires a system reboot to take effect.

Quick Fix Installations

Install any relevant Schneider Electric I/A Series Quick Fixes as per Quick Fix Installation instruc-
tions.

Microsoft SQL Server Software

Microsoft SQL Server® software must be installed before the installation of the AOS software.
For version details and installation instructions of SQL Server, refer to the Installation Chapter of
Application Object Services User's Guide (B0400BZ).

I/A Series Software with Security Enhancements

If Microsoft SQL Server Express edition software is installed on an I/A Series workstation or
server that has I/A Series software with security enhancements installed on it, do the following
modifications:
1. Click , then click Microsoft SQL Server Tools 17 and click Microsoft
SQL Server Management Studio 17.

77
DI700DA – Rev D 10. Installing AOS

2. In the Connect to Server window, select Connect. The Microsoft SQL Server
Management Studio window is displayed.

Figure 10-1. Microsoft SQL Server

3. In the Object Explorer pane, click the Security folder and then click the Logins
folder.
4. In the Logins folder, double-click BUILTIN\Users.
The Login Properties - BUILTIN\Users window is displayed.
5. In the left pane, click Server Roles. In the right pane, under Server roles, select
the public check box and the sysadmin check box.
6. Click OK and close the Microsoft SQL Server Management Studio window.

Uninstall AOS Software (Optional)

In the event that a prior version of the AOS software is already installed, use
Add/Remove/Programs to uninstall the previous version.

AOS Software Installation

For information about installation of AOS Software, refer to the Installation Chapter of Applica-
tion Object Services User's Guide (B0400BZ).

78
10. Installing AOS DI700DA – Rev D

Modifying System Resources

To configure I/A Series software to support the required number of Application Objects, do the
following:
1. Resize virtual memory per the I/A Series software installation guide.
2. Modify the Object Manager parameters per the instructions found in “Calculating the
Correct Setting for OM_NUM_OBJS” on page 79.
3. Modify the AIM*API programs configuration files per the instructions found in
“Configuring the I/O Subsystem (AIM*API)” on page 81.

Resizing the I/A Series System

The I/A Series system ships with the ability to create 1250 Shared Variables. Because Application
Objects use the same resources as Shared Variables and because some user applications require sev-
eral hundred Application Objects each with a hundred or so attributes, one must raise this limit.
The 1250 limit can be raised to 4000. The 4000 limit can be increased to an arbitrary amount by
following the procedures found in the Application Object Services User's Guide (B0400BZ).

! CAUTION
The performance of the I/A Series station can be impaired if it does not have
enough RAM to handle this and other demands placed on it.

It is the responsibility of the user to provide enough RAM for the required applications. The AOS
package includes a tool to help size its RAM requirements.

Calculating the Correct Setting for OM_NUM_OBJS

Application Object Attributes occupy space in the Object Managers Shared Memory parti-
tion.The size of this Shared Memory setting is controlled by the value of OM_NUM_OBJS.
OM_NUM_OBJS is typically used to specify the number of OM Shared Variables permitted in a
station, but it can be used to size the Shared Memory segment for use by AOS. This setting can be
found in the file /etc/fox/opsys_usr.cfg.
Experience shows that the ratio of AOAs to OM Shared Variables (the value of
OM_NUM_OBJS) is approximately 2.5:1 for most applications.
Although resource requirements can be estimated with the above ratio, the better technique is to
use the AOS tool calcAppSize. CalcAppSize indicates the OM_NUM_OBJS setting required to
accommodate the Application Object Attributes defined by one or more map files. CalcApp-
Size.exe is in d:/opt/aos/exe and requires just one parameter the .map file name (for example,
T1.map).
If you do not yet have a map file, wait until you do.
One should be aware that calcAppSize program calculates only the space required to hold the
Application Object Attributes. Additional space is required by applications that use OM lists.
Almost all of the common I/A Series programs use such lists. These programs include DM/FV, all
historians, and all Multivariable Controllers.

79
DI700DA – Rev D 10. Installing AOS

Each OM list requires 64 bytes for a header and 64 bytes for each variable being monitored. Using
this information plus the fact that each OM_NUM_OBJS increment makes 350 bytes available,
one can estimate the additional increase required to support these lists.
For example, if one has 20 Display Managers each of which will be looking at 75 AOAs, the
increase in the setting of OM_NUM_OBJS is approximately.
20 × ( 64 × ( 1 + 75 ) )
----------------------------------------------------- = 278
350

Generally, it is easier to simply round the output of calcAppSize up a few thousand. For exam-
ple, if the result is 5425, set OM_NUM_OBJS to 10000. Since each .map file created by the
configuration is the same size, set OM_NUM_OBJS to (number of controllers)*1000.

Altering the Sizing Files

The procedure to increase the number of OM objects in an I/A Series workstation is:
1. Click Start > Run, enter:
d:\usr\local\show_params
and record the results.
2. In Wordpad or Notepad, edit the file d:\usr\fox\exten\config\user_rules.cfg to
change the bottom numbers (maximums):
♦ OM_NUM_OBJECTS variable to 10000 x number of controllers. (This value needs
to be set to a minimum value of 20,000.)
♦ OM_NUM_IMPORT_VARS to 10000.
3. In Wordpad or Notepad, edit the file d:\etc\fox\opsys_usr.cfg to change the top
range:
♦ OM_NUM_OBJECTS variable to 10000 x number of controllers
♦ OM_NUM_IMPORT_VARS to 10000.
4. Cause the parameters to change on the next reboot by initiating a command prompt
window and entering the following:
d:
cd \usr\local
sh
./reconfig_IA prep_reboot
5. Reboot the PC.
6. Click Start > Run.
d:\usr\local\show_params
and compare the results to those recorded in Step 1.

80
10. Installing AOS DI700DA – Rev D

NOTE
After the entire setup and during the alarm tests, if alarms are not being displayed in
the Current Alarm Display, repeat the setup procedure in this section and increase
the OM_NUM_OBJECTS value in multiples of 16 (for example, 16,000, 32,000,
and so forth). Note that whenever the OM_NUM_OBJECTS variable is changed
in one place, the same value is applied to the OM_NUM_OBJECTS variable in all
the files where it is used.

Configuring the I/O Subsystem (AIM*API)

The I/A Series system has offered two APIs to obtain process data:
♦ The Object Manager (OM) API
♦ The AIM*API Software
The Object Manager API is complex and difficult to program.
AIM*API simplifies the OM API and extends it over a variety of networks to various client com-
puters and Operating Systems. In addition, it minimizes the consumption of various resources
used by the OM.
The Application Object Services package uses AIM*API and, therefore, AIM*API may need con-
figuration for a particular project. Configuration of AIM*API is accomplished by changing the
file /opt/aim/bin/aimapi.cfg and restarting the package.
The first change is to raise the maximum number of objects that AIM*API may address (maxobj)
from the default of 5000 to a number that matches the OM_NUM_OBJECTS.
maxobj = 10000 x number of controllers (for example, for 4 controllers,
enter 40000)
If large numbers of points are being opened in a short period of time, ensure that ctdlay is set to
200 (2 seconds).
ctdlay = 200
To conserve resources, you should request updates as infrequently as possible. The update rate is
set by the fastest_rsr parameter. It is adjusted in increments of 0.5 seconds. A fastest_rsr setting of
4 is 2 seconds.
fastest_rsr = 4
Here is an example aimapi.cfg file with the non-default values in Italics:
maxobj = 40000
maxqo = 1
maxch = 1
maxds = 300
crnpak = 0
cwnpak = 1
maxlog = 1000
ctdlay = 200
ddctly = 0

81
DI700DA – Rev D 10. Installing AOS

logtrm = 0
docmsg = 0
wfilt = 0
trcast = 0
trccts = 0
trcef = 0
trcfil = 0
trclok = 0
trcx25 = 0
trcbrw = 0
open_wait = y
uread_direct = 0
nocsaonread = 1
fastest_rsr = 4
use_omopen = 1
rmtid = 1AW70A 1AW70A /R/W 20-Series
rmtid = 1AW70B 1AW70B / R/W 20-Series
rmtid = 1AW70C 1AW70C / R/W20-Series
rmtid = 1AW70E 1AW70E / R/W 20-Series

NOTE
The value of maxobj should be set to the same value as that of
OM_NUM_OBJECTS. Whenever the OM_NUM_OBJECTS variable is changed,
change the maxobj variable to the same value.

Troubleshooting
General Approach
The general approach to debugging any AOS based application is as follows:
1. Delete all of the log files in /opt/aos/logs and any related log directories.
2. Repeat the AOS operation that failed.
3. Examine the log files.

Common Problems
Strange AOA Behavior
Application Object Attributes exist in a Shared Memory segment owned by the OM. This mem-
ory segment needs to be properly sized. If it is too small, you get various strange behaviors, for
example, some A:O.As existing and others not and failure to open some OM lists while others
succeed.

82
10. Installing AOS DI700DA – Rev D

Be sure to follow the instructions in “Resizing the I/A Series System” on page 79 to ensure that
the segment is properly sized. Refer to the notes in “Resizing the I/A Series System” on page 79
and “Configuring the I/O Subsystem (AIM*API)” on page 81 for additional information.

AOS Startup Problems

Observe the startup script results on the console. If a problem is noted in AOS BUILDDB or
CREATE, change directory to /opt/aos/logs and observe the files: AOS_BUILDDB and
AOS_CREATE. One or more of these file may indicate an error occurred.
One example of a reported problem would be seen in AOS_CREATE if the
OM_NUM_OBJECTS were set at too small of a value - there will be a diagnostic message
suggesting the OM_NUM_OBJECTS be set larger. In this case, implement the suggested
change. On occasion a cryptic error code might appear such as -52. In this case, contact Global
Customer Support by calling 1-866-746-6477 inside the U.S. or 1-508-549-2424 outside the
U.S.

83
DI700DA – Rev D 10. Installing AOS

84
11. I/A Series Alarm Displays
Turbine alarms from the GE turbines appear as I/A Series Alarm Displays when the GE GSM
driver is configured to support alarm handling. The GE alarms can be propagated to multiple
displays.
In the Current Alarm Display there are two lines of information for each turbine alarm. The first
line of the alarm display is:
C:B.P, Description, STATE, alarm/returned-to-normal, acknowl-
edged/unacknowledged
♦ For example, C:B.P may be T1:ALM_0050.STATE, where T1 designates the tur-
bine and 50 is the GE “drop number”. If the turbine name is T1, the compound
name is T1 on the primary I/A Series workstation and T1B on the backup I/A Series
workstation. P is always STATE.
♦ The Description field contains the description received from GE in the alarm
record (this is referred to as the “long name” in the GE documentation). The descrip-
tion may be up to 40 characters which results in the description being continued on
the second line of the display.
The second line of the alarm display is of the format:
Date Time, msecs, Pnt 1
♦ Date Time is displayed as provided by the GE turbine.
♦ The milliseconds portion of the time stamp are provided after msecs. The millisec-
onds are represented by 6 digits, which are interpreted, as xxx . xxx
The turbine alarm can be acknowledged as can any alarm. The turbine alarm can be acknowl-
edged from any of the Alarm Displays. The following operational notes are of high importance:

NOTE
The operator action to Clear Page and Clear Alarm must only be allowed if the Cur-
rent Alarm Display is customized to set the clear option to mark the alarm as
returned to normal and to acknowledge the alarm.

This is accomplished for each workstation by editing the file init.user, located in
d:/usr/fox/wp/data. The “clear option” (CLR_OPT) must be set to 2. Failure to make this Alarm
Display customization could result in GE alarms overflowing the queue in the GE machine. If the
GE queue overflows, new GE alarms are not transmitted to I/A Series software and are not dis-
played on the GE HMI.

NOTE
If the primary or backup I/A Series workstation is disconnected from the GE (reboot
or cable disconnect) and the alarms associated with that GE connection are dis-
played at a separate workstation, any GE alarms on the CAD should be cleared from
the display before the I/A Series workstation is reconnected. This ensures that only
current GE alarm information is displayed on the Current Alarm Display (CAD).

85
DI700DA – Rev D 11. I/A Series Alarm Displays

NOTE
For redundant operation, configure two CADs, one on each of two I/A Series work-
stations. Connect the primary CAD, the one that is configured to display all related
I/A Series alarms, with turbine alarms from the GSM driver in the primary
I/A Series workstation. Put the backup CAD on a separate I/A Series workstation.
The backup turbine alarm CAD should only display turbine alarms, no I/A Series
alarms. To avoid problems inherent in having multiple alarm databases being
updated simultaneously, and also to avoid operator confusion, keep the backup
CAD display turned off. Bring up the backup CAD display only if the I/A Series
workstation with the primary CAD has failed.

NOTE
An Alarm Dump may be forced by plant personnel. See “Forcing an Alarm Update”
on page 55.

86
Appendix A. GE GSM Multi-Turbine
Connection Scenario
This appendix describes the configuration guidelines for systems with turbine controllers interfac-
ing to multiple turbines.
The following diagrams are examples of some typical systems. All the configurations are applica-
ble to both GE Mark V and Mark VI controllers using Cimplicity or Workstation ST Server.

Figure A-1. Example of System with Two Controllers Each Interfacing with a Turbine

Figure A-1 shows a system with two turbine controllers each interfacing to a turbine with the
same name as that of the controller. The configuration for this scenario using Cimplicity Server
and Workstation ST Server is described below.
Using CIMPLICITY Server
1. On the ECB Configuration Screen for GE controller name entries, enter two control-
lers F1 and F2.
2. Generate the controller database to create two .db files.
3. Use two instances of the driver with the two database files.

87
DI700DA – Rev D Appendix A. GE GSM Multi-Turbine Connection Scenario

4. Follow the Alarm Configuration process for each of the controllers and generate two
map files for the two turbine controllers. (See “Alarm Handling Configuration” on
page 32)
5. Customize the data transfer display for monitoring the status of turbines F1 and F2.
Using Workstation ST Server
1. On the ECB Configuration Screen:
a. for Workstation ST, enter 1
b. for GE Controller names, enter two controllers F1 and F2
c. for Turbine names, enter two turbines F1 and F2.
2. Generate the controller database to create two .db files.
3. Use two instances of the driver with the two database files.
4. Follow the Alarm Configuration process for each of the controllers and generate two
map files for the two turbine controllers. (See “Alarm Handling Configuration” on
page 32)
5. Customize the data transfer display for monitoring the status of turbines F1 and F2.

Figure A-2. Example of System with Turbine Controller Interfacing with Two Turbines

Figure A-2 shows a system with Turbine controller F3 interfacing to turbines named F3 and F4.
The configuration for this scenario using Cimplicity Server and Workstation ST Server is
described below.

88
Appendix A. GE GSM Multi-Turbine Connection Scenario DI700DA – Rev D

Using CIMPLICITY Server

1. On the ECB Configuration Screen for GE controller name entries, enter two control-
lers F3 and F4 (refer to “ECB Configuration Screen” on page 20).
2. Turbine F4 needs to be entered as a controller to get periodic data from F4. Enter
periodic data lists for turbines F3 and F4.
3. Generate two .db files and use them with two instances of the driver.
4. The alarms from both the turbines are obtained by the I/A Series workstation from
the Turbine controller F3, and hence, configure alarms with turbine controller F3
only. Generate a single Map File. If you use the Alarm lock/unlock feature the Alarm
Manager GUI is functional with controller F3 only. See “Alarm Handling Configura-
tion” on page 32.
5. Customize the data transfer display for monitoring the status of turbines F4 and F3.
Using Workstation ST Server
1. On the ECB Configuration Screen:
a. for Workstation ST, enter 1
b. for GE Controller names, enter F3 for both the controllers (refer to “ECB Config-
uration Screen” on page 20)
c. for GE turbine names, enter two turbines F3 and F4 (refer to “ECB Configura-
tion Screen” on page 20).
2. Enter periodic data lists for turbines F3 and F4.
3. Generate two .db files and use them with two instances of the driver.
4. The alarms from both the turbines are obtained by the I/A Series workstation from
the Turbine controller F3, and hence, configure alarms with turbine controller F3
only. Generate a single Map File. If you use the Alarm lock/unlock feature the Alarm
Manager GUI is functional with controller F3 only. See “Alarm Handling Configura-
tion” on page 32.
5. Customize the data transfer display for monitoring the status of turbines F4 and F3.

89
DI700DA – Rev D Appendix A. GE GSM Multi-Turbine Connection Scenario

Figure A-3. Example of System with a Turbine Controller Interfacing

with a Turbine with a Different Name

Figure A-3 shows a system with Turbine controller F5 interfacing to a turbine named F6. The
configuration for this scenario using Cimplicity Server and Workstation ST Server is described
below.
Using CIMPLICITY Server
1. On the ECB Configuration screen for GE controller name entries, enter two control-
lers F5 and F6. (Refer to “ECB Configuration Screen” on page 20)
2. Turbine F6 needs to be entered as a controller to get periodic data from F6 into the
driver. The selections you make in Establish Request Selection option on ECB header
file configuration apply to all the controllers. You would include periodic data to get
that from turbine F6. However, you enter the periodic inputs, set points, and push-
buttons for F6 only.
3. Generate two databases for F5 and F6. Only the database for F6 will have configura-
tion related to periodic inputs, set points, and push buttons. The database for F5 will
have configuration information to establish connection to the controller F5 for access
of alarm data.
4. Use two instances of the driver with F5 and F6.
5. The alarms for the turbine F6 are obtained by the I/A Series workstation from the
Turbine controller F5. Hence, configure the alarms for only the turbine controller F5,
and generate a single Map File. If you use the Alarm lock/unlock feature, the Alarm
Manager GUI is functional with controller F5 only. See “Alarm Handling Configura-
tion” on page 32.
6. Customize the data transfer display for monitoring the status of turbine F6 only.

90
Appendix A. GE GSM Multi-Turbine Connection Scenario DI700DA – Rev D

Using Workstation ST Server

1. On the ECB Configuration Screen:
a. for Workstation ST, enter 1
b. for GE Controller names, enter F5 for both the controllers (refer to “ECB Config-
uration Screen” on page 20)
c. for GE turbine names, enter two turbines F5 and F6 (refer to “ECB Configura-
tion Screen” on page 20).
2. Enter the periodic inputs, set points, and pushbuttons for F6 only.
3. Generate two databases for F5 and F6. Only the database for F6 will have configura-
tion related to periodic inputs, set points, and pushbuttons. The database for F5 will
have configuration information to establish connection to the controller F5 for access
of alarm data.
4. Use two instances of the driver with F5 and F6.
5. The alarms for the turbine F6 are obtained by the I/A Series workstation from the
Turbine controller F5. Hence, configure the alarms for only the turbine controller F5,
and generate a single Map File. If you use the Alarm lock/unlock feature, the Alarm
Manager GUI is functional with controller F5 only. See “Alarm Handling Configura-
tion” on page 32.
6. Customize the data transfer display for monitoring the status of turbine F6 only.

91
DI700DA – Rev D Appendix A. GE GSM Multi-Turbine Connection Scenario

92
Appendix B. Migrating from
Cimplicity to Workstation ST
To migrate Cimplicity to Workstation ST, do the following:
1. To configure Driver ECB:
a. In a new Microsoft Excel worksheet, open the existing *_ecb.xls file.
b. Start GEGSM Configurator 4.2.
c. Enable Macros and click Driver ECB Configuration.

Figure B-1. Driver ECB Configuration

d. In the Driver ECB Configuration window, refer to the older version of the
configuration file and enter the values.
e. In the Workstation ST field, enter 1.
f. In the GE Controller Names column, enter the name of controller only.
g. In the Turbine Names column, enter the turbine names.
For example:
The following is a snapshot for one Controller T1 with two Turbines, T1 and T2, using
Cimplicity HMI.

Figure B-2. Cimplicity Configuration

The following is a snapshot of the modifications in the configuration for migrating to

Workstation ST. As indicated in Figure B-3, enter only T1in the GE Controller Names
column and enter T1 and T2 in the Turbine Names column.

Figure B-3. Workstation ST Configuration

93
DI700DA – Rev D Appendix B. Migrating from Cimplicity to Workstation ST

h. Click Save Entries and Exit.

2. To configure the Input File:
a. In a new Microsoft Excel worksheet for Controller 1, open the existing
*_input.xls file.
b. In the GEGSM Configurator window, click Open Input File # 1.
c. Copy the cell contents from list1 of the older worksheet and paste the contents in
list1 of the new GE GSM Configurator.
d. In the Separator field, enter a ‘.’ (dot) or a ‘\’ (slash). This is an optional field.
e. Perform step c for all the lists and click Save.
3. To configure the SetPoint File:
a. In a new Microsoft Excel worksheet for Controller 1, open the existing
*_setpoint.xls file.
b. In the GEGSM Configurator window, click Open Setpoint File # 1.
c. Copy the cell contents from config_output sheet of the older worksheet and paste
the contents in config_output sheet of the new GE GSM Configurator.
d. In the Separator field, enter a ‘.’ (dot) or a ‘\’ (slash). This is an optional field.
e. Click Save.
4. To configure the Push Button File:
a. In a new Microsoft Excel worksheet for Controller 1, open the existing
*_output_pb.xls file.
b. In the GEGSM Configurator window, click Open Push Button File # 1.
c. Copy the cell contents from config_output sheet of the older worksheet and paste
the contents in config_output sheet of the new GE GSM Configurator.
d. In the Separator field, enter a ‘.’ (dot) or a ‘\’ (slash). This is an optional field.
e. Click Save.
5. Click Generate Controller 1 Database.
The Configurator creates the database file with the naming convention of Control-
ler name(Turbine name).db. For example: T1(T1).db.
6. Perform steps 2 through 5 for all the Controllers to generate the respective database
files.

94
Appendix C. Migrating GE GSM
If you are migrating the GE GSM Window driver from an older version to a new version, you can
check and use the previous database configuration file (*.db). Refer “Correcting Database Config-
uration File Manually” on page 95. The GE GSM script files (*.ksh) created and used with ver-
sions older than GE GSM version 4.0 needs to be recreated. Refer to “Configuring GE GSM” on
page 40.
If the GE GSM Window driver is used with an AOS version older than 5.0, the MKALARM
parameter of the alarm map file (*.map) may require correction. To identify the version of AOS
installed on the old machine, browse the D:\opt\aos (AOS install location) folder and open the
VERSION file in Notepad.
To correct the alarm map file manually, refer to “Correcting Alarm Map File Manually” on
page 95. The alarm map file can also be regenerated using the GE GSM Configurator 4.2 or later.
To create a map file, refer to “Generation of Alarm map file” on page 31.

Correcting Database Configuration File Manually

The database configuration file in GE GSM Driver version 4.0 and later use the AOCNM1
parameter for identifying the controller name. To check whether the file contains the AOCNM1
parameter, open the file in Notepad and search for the parameter. If the file does not contain this
parameter, add AOCNM1 = T1 (where T1 is turbine name) after the AOALM parameter. Save
and close the file. The database configuration file is now ready to use.

Correcting Alarm Map File Manually

To correct the MKALAR parameter in the alarm map file, open the alarm map file in Notepad.
Search and replace all the occurrences of MKALARM with MKALAR, save, and close the file.
The alarm map file is now ready to use.

95
Schneider Electric Systems USA, Inc.
38 Neponset Avenue
Foxborough, MA 02035-2037
United States of America
www.schneider-electric.com

Global Customer Support

https://pasupport.schneider-electric.com