B151 0CG

GE
Energy
TASE.2 Server DPA

Configuration Guide
B151-0CG
Version 1.00 Revision 0
Associated Software Release: Version 1.00
General
TASE.2 Server DPA
Configuration Guide
GE Energy
COPYRIGHT NOTICE
© 2010, General Electric Company. All rights reserved.
The Software Product described in this documentation may only be used in accordance with the applicable License Agreement. The
Software Product and Associated Material are deemed to be “commercial computer software” and “commercial computer software
documentation,” respectively, pursuant to DFAR Section 227.7202 and FAR Section 12.212, as applicable, and are delivered with
Restricted Rights. Such restricted rights are those identified in the License Agreement, and as set forth in the “Restricted Rights
Notice” contained in paragraph (g) (3) (Alternate III) of FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
If applicable, any use, modification, reproduction release, performance, display or disclosure of the Software Product and Associated
Material by the U.S. Government shall be governed solely by the terms of the License Agreement and shall be prohibited except to
the extent expressly permitted by the terms of the License Agreement.
The information contained in this online publication is the exclusive property of General Electric Company, except as otherwise
indicated. You may view, copy and print documents and graphics incorporated in this online publication (the “Documents”) subject
to the following: (1) the Documents may be used solely for personal, informational, non-commercial purposes; (2) the Documents
may not be modified or altered in any way; and (3) General Electric Company withholds permission for making the Documents or
any portion thereof accessible via the internet. Except as expressly provided herein, you may not use, copy, print, display,
reproduce, publish, license, post, transmit or distribute the Documents in whole or in part without the prior written permission of
General Electric Company. If applicable, any use, modification, reproduction, release, performance, display, or disclosure of the
Software Product and Associated Material by the U.S. Government shall be governed solely by the terms of the License Agreement
and shall be prohibited except to the extent expressly permitted by the terms of the License Agreement.
The information contained in this online publication is subject to change without notice. The software described in this online
publication is supplied under license and may be used or copied only in accordance with the terms of such license.
TRADEMARK NOTICES
GE and are trademarks and service marks of General Electric Company.
* Trademarks of General Electric Company.

Other company or product names mentioned in this document may be trademarks or registered trademarks of their respective
companies.
2 B151-0CG-1.00-0 General
TASE.2 Server DPA
GE Energy Configuration Guide
Contents
About this Document .....................................................................................................................7

Purpose........................................................................................................................................ 7
Intended Audience ...................................................................................................................... 7
Additional Documentation.......................................................................................................... 7
Product Support.............................................................................................................................8
Search Technical Support ........................................................................................................... 8
Contact Customer Service .......................................................................................................... 8
1. Overview .....................................................................................................................................9
1.1 Overview of the TASE.2 Server DPA ................................................................................ 9
1.2 GE Energy Device Data Applications .............................................................................. 11
1.3 Table Naming Conventions .............................................................................................. 13
1.4 DPA Configuration Overview .......................................................................................... 13
1.5 Configuration Errors ......................................................................................................... 15
2. Set Up Procedure .....................................................................................................................16

2.1 Stage 1 – Build the Configuration .................................................................................... 16
2.2 Stage 2 – Generate Configuration..................................................................................... 17
2.3 Stage 3 – Connect to DPA ................................................................................................ 18
3. Configuration Tables ...............................................................................................................20

3.1 DPA LRU Configuration Table (B151LRU).................................................................... 20
3.2 Authentication Table (B151AUT) .................................................................................... 22
3.3 TASE.2 Configuration Table (B151T2) ........................................................................... 23
3.4 TASE.2 Data Sets Table (B151T2DS) ............................................................................. 23
3.5 TASE.2 DS Members Table (B151T2DM) ...................................................................... 24
3.6 TASE.2 Point Table (B151T2PT)..................................................................................... 24
3.7 Binary Input Mapping Table (B151MT01) ...................................................................... 27
3.8 Binary Output Mapping Table (B151MT02).................................................................... 27
3.9 Counter Input Mapping Table (B151MT03) .................................................................... 28
3.10 Analog Input Mapping Table (B151MT04) ..................................................................... 29
3.11 Analog Output Mapping Table (B151MT05)................................................................... 29
4. Configuring Other Applications.............................................................................................31

4.1 Configuring BridgeMAN.................................................................................................. 31
4.2 Configuring the TASE.2 Data Link .................................................................................. 32
A. Error Log Messages ................................................................................................................33

A.1 Fatal Error Messages......................................................................................................... 33
A.2 Error Messages.................................................................................................................. 36
General B151-0CG-1.00-0 3
TASE.2 Server DPA
Configuration Guide
GE Energy
A.3 Warning Messages ............................................................................................................ 38

A.4 Information Messages....................................................................................................... 49
A.5 Resolving Memory Problems ........................................................................................... 50
TASE.2 Server DPA
Figures
Figure 1 System Overview........................................................................................................... 10
Figure 2 Data Applications Within a GE Energy Device ........................................................... 12
Figure 3 DPA Table Relationships .............................................................................................. 14
Figure 4 Hardware Environment ................................................................................................. 19
TASE.2 Server DPA
Configuration Guide
GE Energy
Tables
Table 1 Common tables ............................................................................................................... 13
Table 2 TASE.2 Table Set tables................................................................................................. 14
Table 3 Mapping Tables .............................................................................................................. 14
Table 4 LRU (DPA Instance) Table (B151LRU) ........................................................................ 20
Table 5 Local / Remote Sub Table to B151LRU......................................................................... 22
Table 6 Authentication Table (B151AUT) .................................................................................. 23
Table 7 TASE.2 Configuration Table (B151T2) ......................................................................... 23
Table 8 Custom Data Sets Table (B151T2DS)........................................................................... 24
Table 9 TASE.2 DS Members Table (B151T2DM)................................................................... 24
Table 10 TASE.2 Point Table (B151T2PT) ............................................................................... 25
Table 11 Point Types and Auto-Generated Types....................................................................... 26
Table 12 Binary Input Mapping Table (B151MT01) .................................................................. 27
Table 13 Binary Output Mapping Table (B151MT02)................................................................ 27
Table 14 Counter Input Mapping Table (B151MT03) ............................................................... 28
Table 15 Analog Input Mapping Table (B151MT04) ................................................................ 29
Table 16 Analog Output Mapping Table (B151MT05).............................................................. 30
TASE.2 Server DPA
About this Document

This document contains detailed configuration specifications for the GE Energy implementation
of the TASE.2 Server DPA (data processing application). TASE is an acronym for Telecontrol
Application Service Element. The scope of this document includes descriptions of the
configuration tables that control the operation of a GE Energy device using the DPA. This
document does not attempt to describe operation of the ConfigPro* system, or any other
configuration software systems.
The TASE.2 Server DPA is part of the TASE.2 Software System (P279-0).
Purpose
This guide describes, in detail, how to configure the TASE.2 Server DPA. This document
describes the purpose and use of each of the configuration parameters of the DPA.
Note: Throughout this document the term DPA, by itself, refers to the TASE.2 Server DPA.
Note: Throughout this document the term Client, by itself, is used to refer to either a TASE.2
Master Station or any other TASE.2 Client software, such as a Browser or Test Client.
Intended Audience
This guide assumes the reader is familiar with the DPA as well as the basic functions of the GE
Energy devices on which it runs.
Additional Documentation
For further information about the TASE.2 Server DPA, refer to the following documents:
• iSCS LAN Users Guide (SWM0008)
• TASE.2 Services and Protocol (IEC 60870-6-503)
• TASE.2 Object Models (IEC 60870-6-802)
TASE.2 Server DPA
Configuration Guide
GE Energy
Product Support
If you need help with any aspect of your GE Energy product, you have a few options.
Search Technical Support

The GE Energy Web site provides fast access to technical information, such as manuals, release
notes and knowledge base topics. Visit us on the Web at:
http://www.gepower.com/prod_serv/products/substation_automation/en/index.htmwww.
ge.com/energy
Contact Customer Service

The GE Energy Customer Service Center is open 24 hours a day, seven days a week for you to
talk directly to a GE representative.
In the U.S. and Canada, call toll-free: 1.800.361.3652
International customers, please call: + 1 403.214.4600
Or e-mail to ge4service@ge.com
TASE.2 Server DPA
1. Overview
1.1 Overview of the TASE.2 Server DPA

The TASE.2 Server DPA software is installed in GE Energy equipment to provide an interface to
one or more hosts (clients) using the TASE.2 (Telecontrol Application Service Element - the “.2”
identifies it as the MMS based version) communications protocol. TASE.2 was originally named
(in North America) as ICCP (Inter-Control Center Communications Protocol). It has the ability
to function as several distinct TASE.2 Server DPA. Each such emulation is called a Logical
Remote Unit (LRU), and appears as a single physical TASE.2 Server DPA to any host
communicating with it.
1.1.1 Product Perspective

The TASE.2 Server DPA software is custom software installed in a GE Energy device, for the
purpose of transmitting information and executing commands using the TASE.2 communication
protocol. It is intended to be integrated in a modular software environment with one or more
Data Collection Applications (DCAs) to provide SCADA functionality.
Figure 1 represents a complete system overview of the interfaces between the DPA, the System
Point Database (WIN), and a TASE.2 Clients in a typical GE Energy device.
TASE.2 Server DPA
Configuration Guide
GE Energy
System Point Database (B008-1)
Commands Events
TAS.2 Server DPA

(B151-0)
TASE.2 Messages
BridgeMAN (B015-0)
TASE.2 Data Link

(B106-0)
Internet Protocol Software (B100-0)
iSCS Internet Software

(P112-0)
Network Driver Interface (B109-0)
Lance Ethernet Driver (B101-0)
Ethernet LAN
TSE.2 Client TASE.2 Client
Figure 1 System Overview
10 B151-0CG-1.00-0 General
TASE.2 Server DPA
1.1.2 Product Functions

The DPA supports the following functions and commands:
• Communication using the TASE.2 protocol.
• Communication with multiple master stations.
• Communication with a master station over more than one Ethernet LAN interface.
• TASE.2 version (edition 1, edition 2) selectable.
• The emulation of multiple DPAs per Ethernet LAN interface.
• Local/Remote Input functionality.
• Communication Failure Output functionality.
• Analog input and output scaling.
• Analog input deadband processing.
• TASE.2 defined security, using the Weak Authentication Mechanism.
• Support for the TASE.2 (ICCP) object models.
• Reporting of data in floating point format.
• Custom Data Sets.
• Remote (dynamic) creation of Data Sets.
• Storing statistics.
This version of the DPA does not support the following functions and commands:
• Information reporting for dynamically created Data Sets.
1.2 GE Energy Device Data Applications

All of the software within GE Energy devices communicate via the System Point Database. An
event driven real time database manager maintains a dynamically updated System Point
Database of all the input/output system points within the device.
The three types of applications within the GE Energy devices are:
1. Data Collection Applications (DCAs) - applications that are able to collect data from other
devices. The DCA writes input point values into the System Point Database and may process
control requests. An example of a DCA is the D.20 application (B003) that enables the D20
to communicate with the D20 peripheral boards.
2. Data Processing Applications (DPAs) - applications that allow a GE Energy device to
communicate with a master station. The DPA reads input point values from the System Point
Database and sends control requests to it. Two examples of a DPA are the GE Energy 6000
DPA application (A003) and the WESMAINT II application (B014).
3. Data Translation Applications (DTAs) - applications that can manipulate data within the
System Point Database. The DTA has the ability to examine the status of any input points
General B151-0CG-1.00-0 11
TASE.2 Server DPA
Configuration Guide
GE Energy
within the System Point Database and accept control requests from other DPAs or DTAs.
The DTA is able to process this data and then write an appropriate result back to the digital
inputs and analog inputs owned by the DTA or those output points belonging to any
application.
The following diagram illustrates a simplified relationship between the above mentioned
application types within GE Energy devices.
DCA Device(s)
Master
DPA
Station
System
Point
Database
DTA
GE Energy Services
Device
Figure 2 Data Applications Within a GE Energy Device
1.2.1 Configuration Basics

Applications within GE Energy devices are configured using GE Energy database tables. The GE
Energy ConfigPro system allows the user to edit each of these tables to provide a means by
which users can configure the application to meet their particular requirements.
The database tables consist of one or more records. Each record describes one object or item that
requires configuration. The records are subdivided into various fields that provide information
concerning the particular characteristics of each record.
If the user needs to select a range of records from another database table, this is done by
specifying:
• The first record as an offset into the other database table.
• The number of records to be selected from the other database table.
Note: The table offset numbers used in ConfigPro, for the DPA, are displayed as one based
numbers.
Note: Throughout the following text, the term “point(s)” is used to refer to TASE.2 Objects that
are primitive (e.g. integers or boolean values, as opposed to structures). Such points will often
map directly to System Database Points.
Note: TASE.2 refers to digital (two state) points as Binary Input and Binary Output. ConfigPro
refers to them as Digital Input (DI) and Digital Output (DO) points, specifically when discussing
System Database Points. In general, this document used the TASE.2 terminology.
12 B151-0CG-1.00-0 General
TASE.2 Server DPA
1.3 Table Naming Conventions

The following simple table naming conventions are used for GE Energy device applications.
Table names are up to eight characters long.
The first four characters of the table name consist of the application number. This alphanumeric
number is an arbitrary identification code chosen by GE Energy to indicate the application with
which the table is associated. For example, the application code for the TASE.2 Server DPA is
B151-0.
The last four characters of the name describe the general function of the table. For example:
− LRU contains general DPA instance specific configuration,
− T2 contains information on the names and members for TASE.2 Domain and
Objects.
− T2PT contains information on the names, number and types of points on the
DPA,
− MTxx contains information for system points, where xx indicates the System
Database Point type (Mapping Table, e.g., MT01 is binary input, MT05 is
analog output).
1.4 DPA Configuration Overview

The DPA is designed to provide multiple LRUs (Logical Remote Units), each of which shall be
configured as the TASE.2 functional model configuration creates a TASE.2 Server, which may
contain any combination of the standard object (point) types defined by the TASE.2
specification.
The following is a summary of all the configuration tables that can be configured for the TASE.2
Server DPA:
Table 1 Common tables
These tables are used by one or more LRU Table Set configurations. They define the operational
characteristics, Security, and TASE.2 Freeze for each DPA instance. Tables marked with an asterisk are
mandatory. All other tables are optional and may be omitted.
B151LRU * The LRU table. This table defines the operational characteristics of each DPA instance (LRU).
Each LRU must have a separate record in this table. In addition to defining parameters for the
LRU operation, this table contains the offset pointers to TASE.2 Configuration Table (B151T2).
Offset pointers to TASE.2 Data Set definition table (B151T2DS) are present. It also contains the
offset pointer to the Authentication table (B151AUT).
B151AUT * The Authentication table. This table contains information needed to provide TASE.2 security for
the DPA, such as passwords and access levels.
General B151-0CG-1.00-0 13
TASE.2 Server DPA
Configuration Guide
GE Energy
Table 2 TASE.2 Table Set tables
These tables define the TASE.2 Server configuration, Data Sets and Points for each TASE.2 Table Set
DPA instance. Tables marked with an asterisk are mandatory. All other tables are optional and may
be omitted.
B151T2 * The TASE.2 Configuration table. This table defines the TASE.2 domains and objects to be
included in a TASE.2 device model. Each record contains range and offset pointers which
define the TASE.2 objects
B151T2DS The TASE.2 Data Set definitions table. This table defines the parameters for a TASE.2 Data
Set. It contains offset pointers to the TASE.2 Data Set Members table (B151T2DM).
B151T2DM The TASE.2 Data Set Members table. This table contains a range of members that
constitute a TASE.2 Data Set. It contains offset pointers to the TASE.2 Point table
(B151T2PT).
B151T2PT * The TASE.2 Point table. This table defines the TASE.2 Point names and types, as well as
the offsets to the System Point Mapping tables (B151MTxx) - which define the TASE.2
Points in terms of System Database Points.
Table 3 Mapping Tables
These tables define the System Points, which are mapped back onto TASE.2 Points through the
TASE.2 Point Table (B151T2PT).
B151MT01 The Binary Input Mapping Table.
B151MT02 The Binary Output Mapping Table.
B151MT03 The Counter Mapping Table.
B151MT04 The Analog Input Mapping Table.
B151MT05 The Analog Output Mapping Table.
Note: While not all mapping tables are mandatory, some mapping tables must be present to
implement a “useful” DPA.
1.4.1 Configuration Table Relationships

Figure 3 illustrates the relationships between the tables used by the DPA
A u th e n tica tio n
T a ble
(B 1 5 1A U T )
L R U T a b le
(B 1 5 1L R U )
T A S E .2 D a ta
ξ D a ta S e ts S e ts T ab le
ξ A u th (B 1 5 1 T 2D S )
ξ M od e l R a n g e
P o in t M a p
T A S E .2 D a ta S e t T a ble s
M e m b e rs T ab le (B 1 5 1M T xx )
(B 1 5 1T 2 D M )
T A S E .2 C o nfig T A S E .2 P o in ts
T a b le T a b le
(B 1 5 1 T 2) (B 1 51T 2 P T )
Figure 3 DPA Table Relationships
14 B151-0CG-1.00-0 General
TASE.2 Server DPA
1.5 Configuration Errors

During initialization, the DPA performs a configuration check to ensure all mandatory
configuration tables are available and the configuration parameters, in all configured tables,
contain valid entries. If any of the mandatory tables are not available, the DPA suspends
execution and posts the appropriate error message to the WESMAINT Error Log (refer to A. for
details).
General B151-0CG-1.00-0 15
TASE.2 Server DPA
Configuration Guide
GE Energy
2. Set Up Procedure
This chapter outlines the sequence of steps needed to configure the TASE.2 Server DPA using
the GE Energy ConfigPro configuration software.
2.1 Stage 1 – Build the Configuration

The TASE.2 Server DPA uses a set of linked configuration tables to define the TASE.2 Server
functional model to be presented.
The TASE.2 Server Model defines an LRU for use in inter-control center communications, with
the LRU acting as a SCADA/EMS host. (TASE.2 is also known as ICCP – Inter-Control Center
Communications Protocol.)
The following steps describe the process needed to configure the DPA.
Note: A working knowledge and understanding of the TASE.2 specifications is necessary to
configure the DPA.
2.1.1 TASE.2 Server Model

The TASE.2 Server Model Table Set defines a TASE.2 Virtual Control Center (VCC) server.
2.1.1.1 Step 1: Configure the DCAs and DTAs

System Database Points (belonging to DCA or DTA applications present on the device), which
will be used by the DPA, must be defined. Configure the System Point Database with the correct
number of input and output points belonging to each of the applications. The System Point
Database is also used to specify the textual descriptions (descriptors) for each point.
You will need to consult the configuration guides for each of these applications.
Refer to 4. Configuring Other Applications for information on configuring the TASE.2 Data
Links and BridgeMAN.
2.1.1.2 Step 2: Set Up the Mapping Tables

All input and output System Database Points are selected using the mapping tables. The mapping
tables translate the device’s system points into the database used by the DPA.
Using mapping tables, it is possible for system points to be reported to the master station more
than once (i.e. multiple mapped points). Similarly, it is possible for system points not to be
reported to the master station (i.e. unmapped points).
It is not necessary to map the system points in any particular order.
For each record in this table, define the required system point number and any required
translation parameters (e.g. scaling factors, threshold values, etc).
16 B151-0CG-1.00-0 General
TASE.2 Server DPA
2.1.1.3 Step 3: Determine the VCC Domains

Determine if the TASE.2 server is to represent a single, domain-less (or single domain) VCC or a
VCC with a collection of domains. For a single VCC only one record is configured in the main
TASE.2 table. For severs with multiple domains, each domain uses a separate record.
2.1.1.4 Step 4: Set Up the TASE.2 Points and Types

Determine which TASE.2 points (objects) you wish to include in the configuration for each
domain, as well as their types (defined by the TASE.2 specification).
Configure the TASE.2 point table with a record for each name desired. Select the offsets into the
point mapping tables, for each record, to point to the desired system database point.
2.1.1.5 Step 5: Set Up any TASE.2 Data Sets

Using the TASE.2 Data Set and TASE.2 DS Members tables, configure any desired TASE.2
Data Sets. The members of each Data Set are select using offsets into the TASE.2 Points table.
Note that TASE.2 Transfer Sets are not pre-configured, other than to allocate space for them in
the main TASE.2 Configuration table.
2.1.2 Summary
When the above steps have been completed:
• The LRU Table (B151LRU) lists the range of TASE.2 table entries contained within each
Logical Remote Unit. The TASE.2 Protocol Compliance is selected. The timestamp class is
selected if the protocol compliance is selected as TASE.2 edition 2. Operational parameters
for each LRU are selected.
• The Authentication Table (B151AUT) lists the security options selected.
• The TASE.2 Table (B151T2) lists the range of TASE.2 points and Transfer Sets.
• The TASE.2 Points Table (B151T2PT) lists the range of Mapping Table Entries applicable to
each TASE.2 Point.
• The TASE.2 Data Sets Table (B151T2DS) lists the TASE.2 Data Sets. The TASE.2 Data Set
Members Table (B151T2DM) list the TASE.2 Points which are members of each Data Set.
• Each entry of the various Mapping Tables (B151MTxx) refers to a valid System Point(s).
2.2 Stage 2 – Generate Configuration
2.2.1 Step 1: Generate Downloadable File

Generate a downloadable file. Note that the first time this is done, it will probably contain
ConfigPro error and warning messages. If there are no errors, go to step 3.
General B151-0CG-1.00-0 17
TASE.2 Server DPA
Configuration Guide
GE Energy
2.2.2 Step 2: Find And Fix Errors

If, after generating the configuration, ConfigPro may report errors or warnings. Examine the
errors to determine their cause, and correct them. If necessary, repeat step 1.
Note: If a downloadable file was generated without errors or warnings, it does NOT mean that
the configuration is 100% correct. While the GE Energy configuration software can detect many
errors, it cannot detect all configuration errors.
2.2.3 Step 3: Download Configuration File

Use the Connect | Configuration Download option in ConfigPro to download the configuration
file. If your target device does not have iSCS LAN communications configured, go online with
the device (using a serial connection) and use Communication | Download to download the
configuration file. Refer to the ConfigPro documentation, or help system, for details on
configuration file downloading.
2.2.4 Step 4: Determine if the TASE.2 Server DPA is Working

When the device has rebooted, the DPA will attempt to run. The application will first check that
it has a valid configuration. If it does not have a valid configuration, it will send a message to the
WESMAINT Error Log (viewable using the WESMAINT). If there are error messages, the
configuration needs to be changed and downloaded again (i.e. repeat stage 2).
Note: If you are familiar with the WESMAINT Monitor, another useful way of determining
whether the DPA is running correctly is to use the query process command (refer to the Monitor
User's Guide) to determine what (if any) processes are suspended.
Refer to A. for a comprehensive list of all the error messages the DPA can send to the
WESMAINT Error Log, and possible solutions.
2.3 Stage 3 – Connect to DPA

To ensure that the configuration of the DPA is correct, a protocol test set should be used to
validate the new device configuration. Figure 4 illustrates a typical configuration environment.
Note: Since it is possible to re-order and remove database points in the device configuration, it
is highly recommended that the device be fully "point to point" tested after any significant
changes are made to the system point mapping tables.
18 B151-0CG-1.00-0 General
TASE.2 Server DPA
PC with Config PC with UCA

Pro System Client
Figure 4 Hardware Environment
General B151-0CG-1.00-0 19
TASE.2 Server DPA
Configuration Guide
GE Energy
3. Configuration Tables
This chapter describes the purpose, possible values, and the recommended and default values for
each of the fields within the TASE.2 Server DPA configuration tables. The maximum number of
records permitted for each configuration table is dependent on the system resources.
In the following tables default values denoted as “(blank)” indicate that the default is an empty
text string.
3.1 DPA LRU Configuration Table (B151LRU)

Configure a record in this table for each Logical Remote Unit (LRU) to be contained within this
physical device. Each LRU defines a separate DPA instance. You may configure multiple LRUs
to give different TASE.2 clients a different view of the System Point Database, to enforce
security, or to ensure that multiple clients receive separate copies of change events.
3.1.1 LRU Main Tables

Table 4 LRU (DPA Instance) Table (B151LRU)
Field Name Description Allowed Values Default Value

DPA AppID Application address for LRU. Must correspond 1 to 65,535 1
with the appropriate BridgeMAN tables. Refer
to 4. Configuring Other Applications.
Security Determines if a client must have an entry in Clients must be in RAT Clients must
BridgeMAN’s Remote Application Table to be in RAT
connect to the LRU. If set to ‘Clients must be or
in RAT’, the DPA does not respond to any Accept any Client
client that is not configured in the RAT.
Choose this option when security is important.
Choosing ‘Accept any Client’ disables this
security check.
Protocol Selects Edition 1 or 2 of TASE.2 protocol. Edition 1 or Edition 2 Edition 2
Compliance
First Auth Entry Table offset to first of a selection of records in Any available table 1
the Authentication Table (B151AUT). There record.
must be at least 1 record.
Not permitted to be
Undefined.
Num Auth Entries The number of Authentication Table entries. 1 to 65,535 1
Configure a new Authentication Table entry for
each class of client that requires a different The value is
password or a different level of access. There determined by the
must be at least one Authentication Table number of First Auth
entry, although it may specify no Entry records selected.
authentication is necessary.
First Main Table Table offset to the first of a selection of Any available table 1
Entry records in the TASE.2 Configuration Table record.
(B151T2). There must be at least 1 record.
Not permitted to be
Undefined.
20 B151-0CG-1.00-0 General
TASE.2 Server DPA

Num Main Table The number of B151T2 table entries used by 1 to 65,535 1
Entries this LRU.
The value is
determined by the
number of First LRU
Model Entry records
selected.
First Data Set Table offset to the first of a selection of Any available Data Set Not Used
records in the Data Set table (B151T2DS). table record. The table
Each selected record defines a custom Data is determined by the
Set, which the DPA will create. Table Set field.
May be set to Not
Used.
Num Data Sets The number of custom Data Sets table entries 0 to 65,535 0
used by this LRU.
The value is
determined by the
number of First Cust
Data Set records
selected.
Comm Fail Output Determines the binary output point to operate Any valid binary output Undefined
Point when no connections are active for this LRU. System Database Point
Undefined (-1) means this feature is disabled.
This point need not be mapped to any LRU. or
Undefined (-1)
Event Cache Determines the minimum number of buffers 10 to 65,535 50
Buffers available to buffer data change events. The
maximum number of buffers is roughly 3.5
times this number and would be realized if all
the events were binary input change events.
The minimum number would apply if all the
events were counter change or freeze events.
Event Cache Determine if the data change events stored In NVRAM (Persistent) In RAM
Persistence are preserved over reboots. (Volatile)
or
In RAM (Volatile)
Dynamic DS Specifies how much system memory, in 0 to 32,767 (kilobytes) 10
Memory (KB) Kilobytes, to reserve for the creation of
TASE.2 Data Sets by a remote TASE.2 client
(master station).
Dynamic DS Determine if the dynamic TASE.2 Data Sets In NVRAM (Persistent) In NVRAM
Persistence (those created by a TASE.2 client) are (Persistent)
preserved over reboots. or
In RAM (Volatile)
Max Client Determines the maximum number of 1 to 100 4
Connections simultaneous connections the LRU will allow.
Note: in other protocols, it is customary that
there is only ever one connection per LRU. In
TASE.2, it is possible for a single Server to
provide data to multiple Clients. However, only
one Client at a time may receive spontaneous
or periodic reports of a given Data Set from a
given Server.
Max PDU Size Determines the maximum size of an MMS 512 to 16,384 octets 8,192
(TASE.2) message the LRU will accept.
General B151-0CG-1.00-0 21
TASE.2 Server DPA
Configuration Guide
GE Energy

Local / Remote See Local / Remote sub-table, Section 3.1.2 .
Clear Stats Determines whether the LRU’s statistics table True True
(B151STAn, where n = LRU number) is
cleared on system start-up. or
False
Dictionary This parameter determines if the Dictionary is Yes (Persistent) Yes
Persistence preserved over reboots. The Dictionary is a (Persistent)
large run-time database structure, which or
requires significant CPU resources to create. If No (Volatile)
the Dictionary is configured to be persistent,
the TASE.2 DPA’s startup time can be
significantly reduced.
Set to Persistent (yes) if there is enough
NVRAM for the dictionary and the NVRAM
requirements of other co-resident applications
such as DFR. Otherwise, set to Volatile (no).
Note that the first time the TASE.2 DPA starts
up after a new configuration is downloaded, its
startup time will be slower because it has to
create the dictionary in NVRAM.
3.1.2 Local / Remote Sub Table of B151LRU

There is one instance of this sub-table for each configured Logical Remote Unit provided by the
DPA. The configuration of this sub-table can prevent a TASE.2 client from performing any
binary output operations, for safety reasons.
Table 5 Local / Remote Sub Table to B151LRU

Local / Remote Identifies the binary input System Point that Any valid binary input Undefined
Input controls whether the LRU rejects output system point or Undefined
requests. (-1)
Local Mode Identifies the state of the Local/Remote Input ON or OFF ON
State point that causes the LRU to reject output
requests. This state is intended to indicate
that there is an operator present at the site
who could be harmed if the LRU performs an
output, or some other condition that should
prevent an output from operating.
3.2 Authentication Table (B151AUT)

Configure an entry in this table for each TASE.2 Client for which you wish to have a different
password or different level of access to the TASE.2 Server DPA. If it is more convenient and
security is not an issue, several clients may share the same password. There must be at least one
record in this table. If no authentication is desired, that one entry should have an Auth Type of
None.
22 B151-0CG-1.00-0 General
TASE.2 Server DPA
Table 6 Authentication Table (B151AUT)

Auth Type Determines the type of security authentication the None or Weak None
LRU will perform when a master station attempts to (option Strong is
connect to it. This determines the Authentication unsupported)
Mechanism. This field is ignored if Auth Type is set
to None. The existence of any record with Auth
Type set to None essentially disables authentication
completely. Note: The current version does not
support Strong authentication.
Auth Determines the password that will be used to 0 to 32 character (blank)
Password enforce the Weak Authentication mechanism. string
3.3 TASE.2 Configuration Table (B151T2)

The records in this table define the TASE.2 Bricks that will be present within an LRU configured
to use the TASE.2 (Telecontrol Application Service Element) Table Set. Configure a record in
this table for each TASE.2 Virtual Control Center (VCC) Domain to be configured.
The Domain name field determine the TASE.2 Domain within the VCC. A VCC may contain no
Domains, in which only a single record is configured with this field left blank.
Table 7 TASE.2 Configuration Table (B151T2)

Domain Name Specifies the name of the Domain for this 0 to 32 characters (blank)
TASE.2 definition. If no Domain is used,
leave blank.
Number of Determines how many TASE.2 Transfer 1 to 65,535 10
Transfer Sets Sets will be allocated. During operation,
Transfer Sets are allocated from, and de-
allocated back to, this pool.
First TASE.2 Table offset to the first of a selection of Any available table record. 1
Point records in the TASE.2 Point Table
(B151T2PT). There must be at least 1 Not permitted to be
record. Undefined.
Num TASE.2 The number of TASE.2 Objects (Points) 1 to 65,535 1

Points which are part of this definition.
The value is determined by
the number of First TASE.2
Point records selected.
Bilateral Table Specifies the Bilateral Table ID, which is 0 to 32 characters (blank)
ID the version number of the Bilateral Table.
3.4 TASE.2 Data Sets Table (B151T2DS)

Configure one record in this table for each TASE.2 Data Set to be created by the DPA. The Data
Set members are configured using a table offset into the TASE.2 DS Members table
(B151T2DM).
General B151-0CG-1.00-0 23
TASE.2 Server DPA
Configuration Guide
GE Energy
Table 8 Custom Data Sets Table (B151T2DS)
Field Name Description Allowed Values Default

Value
Data Set Specifies the name of this TASE.2 Data 0 to 65 character string (blank)
Name Set, including Domain name. If Domain
name is present, use a “/” delimiter
between it and the remainder of the Data
Set name.
First Data Set Table offset to the first of a selection of Any available table record. 1
Member records in the TASE.2 DS Members table
(B151T2DM), for this Data Set member Not permitted to be Undefined.
list. There must be at least 1 record.
Number of The number of TASE.2 objects which are 1 to 65,535 1
Members part of this Data Set definition.
The value is determined by the
number of First Data Set Member
records selected.
3.5 TASE.2 DS Members Table (B151T2DM)

Configure one record in this table for each member of a given Data Set listed in the TASE.2 Data
Sets Table. This table exists so the members of a Data Set can be non-contiguous in the TASE.2
Point Table.
Table 9 TASE.2 DS Members Table (B151T2DM)
Data Set Table offset to an entry in the TASE.2 Any available table record. 1
Member Point Table (B151T2PT), which specifies
this Data Set member. There must be at Not permitted to be
least 1 record. Undefined.
3.6 TASE.2 Point Table (B151T2PT)

Configure one record in this table for each TASE.2 Point (object) to be defined for the
configured VCC (see the TASE.2 Configuration Table description, above).
The Point Name field may contain any valid TASE.2 name. Valid names must consist only of the
characters: A-Z, a-z, 0-9, _ and $. No spaces are allowed in the names.
The Point Type is selected from a pull-down list of the TASE.2 defined basic object types. The
points are mapped to system database points using the mapping table determined by the Point
Type.
Quality, Time Tag and Change Of Value (COV) associated points may be automatically created
by the DPA by specifying the appropriate “Include” option, as shown in the following table.
The names of the generated points are constructed concatenating the Point Name with a suffix
representing the Include type. For:
• Quality, the suffix is $Flags
• Time Tag, the suffix is $TimeStamp
• COV, the suffix is $COV
24 B151-0CG-1.00-0 General
TASE.2 Server DPA
For DataState Point Types the Point Name always has a $Flags suffix attached, regardless of the
setting of Include Quality. This is because the binary input state is contained in the Flags
component, along with the quality bits.
Note that the Include options are not exclusive. Selecting Include Time Tag causes the DPA to
create a Quality (Flags) point as well as a Time Tag (TimeStamp) point. Similarly, selecting
Include COV causes the DPA to also create Time Tag and Quality points. This is in accordance
with the Tase.2 specification.
A special Point Type, AqCtrl, is selected to cause the DPA to generate an Aquire Controls
pseudo point. Selecting this type and entering a Point Name of “AqCtrln”, permits a Client to
acquire ownership of a particular DCA Control group, where n is the group number. No system
point is required for this type. A Client writing this point causes the DPA to attempt to acquire
ownership of the Control Group.
The Point Type Special is selected to enter Tase.2 identifiers used to manage Data Set Transfer
Set Reporting. Adding any of these Point Names result in the generated Information Reports
containing the data specified for the Special name. Refer to the Tase.2 specification for more
information about these identifiers. The permissible Special Point Names are:
• Transfer_Set_Name – Include the name of the variable, which contains the Transfer Set
object that triggered the report.
• DSConditions_Detected – Include the name of the variable, which contains the
DSConditions Detected object that triggered the report.
• Event_Code_Detected - Include the name of the variable, which contains the Event Code
Detected object that triggered the report.
• Transfer_Set_Time_Stamp - Include the name of the variable, which contains the
Transfer_Set_Time_Stamp object that contains the time of the report.
Table 10 TASE.2 Point Table (B151T2PT)

Point Name Specifies the name of the TASE.2 Point 1 to 32 characters (blank)
(object).
Point Type Selects the TASE.2 defined type of the point. List of TASE.2 types. Refer DataReal
to Table 11
Include Quality Specifies whether the DPA will automatically Yes, No Yes (e.g., makes
generate a TASE.2 Quality point associated DataRealQ for
with the defined point. DataReal)
Include Time Specifies whether the DPA will automatically Yes, No Yes
Tag generate a TASE.2 Time Tag point
associated with the defined point.
Include COV Specifies whether the DPA will automatically Yes, No Yes
generate a TASE.2 Change Of Value point
associated with the defined point.
First System Table offset to first of a set of records in a Any valid system point 1
Point system point mapping table (determined by entry in the mapping table
the Point Type) for the range of mapped for the type.
points.
Num System The number of system points mapped to this 0 to 2,147,483,647 1
Points TASE.2 Point entry.
General B151-0CG-1.00-0 25
TASE.2 Server DPA
Configuration Guide
GE Energy

Time Stamp Selects TimeStamp or TimeStampExtended TimeStamp or TimeStamp
Class of time stamp class, but TASE.2 Edition 1 TimestampExtended
only supports TimeStamp class.
Note:
The TimeStamp class provides a time stamp
with a minimum resolution of one second.
The TimestampExtended class provides a
time stamp with a minimum resolution of one
millisecond.
Table 11 Point Types and Auto-Generated Types
Point Type TASE.2 Type Generated Generated Time Tag1 Generated COV2
Quality
name + $Flags name + $TimeStamp / name + $COV

name$TimeStamp$GMT
BasedS and
name$TimeStamp$Milli
seconds
DataReal DataReal DataRealQ DataRealQTimeTag / DataRealExtended

DataRealQTimeTagExten
ded
4
DataState DataState DataStateQ DataStateQTimeTag / DataStateExtended
DataStateQTimeTagExte
nded
DataDiscrete DataDiscrete DataDiscreteQ DataDiscreteQTimeTag / DataDiscreteExtend

DataDiscreteQTimeTagE ed
xtended
DataDiscreteAccum DataDiscrete DataDiscreteQ DataDiscreteQTimeTag / DataDiscreteExtend

DataDiscreteQTimeTagE ed
xtended
CommandNonSBO ControlCommand n/a n/a n/a

SetpointDiscreteNonS ControlSetpointDiscre n/a n/a n/a
BO te
SetpointRealNonSBO ControlSetpointReal n/a n/a n/a

3
CommandSBO ControlCommand n/a n/a n/a
3
SetpointDiscreteSBO ControlSetpointDiscre n/a n/a n/a
te
3
SetpointRealSBO ControlSetpointReal n/a n/a n/a
5
AqCtrl n/a n/a n/a n/a
5
Special n/a n/a n/a n/a
Note 1: Also causes Quality point generation. The QTimeTagExtended shall be generated only when the Protocol
Compliance is selected to Edition 2 and the TimeStamp Class is selected to TimeStamp Extended.
Note 2: Also causes Time Tag and Quality point generation.
Note 3: Also causes creation of an additional point with “_SBO” suffix, for Select Before Operate Control and
Setpoint outputs.
Note 4: Note that DataState (Status) points are always generated with “$flags”, regardless of the setting of Include
Quality.
Note 5: Special point types. Refer to the table description, above.
26 B151-0CG-1.00-0 General
TASE.2 Server DPA
3.7 Binary Input Mapping Table (B151MT01)

Configure a record in this table for each binary input System Database Point the TASE.2 Server
DPA can present to a TASE.2 Client. You must refer to each record in this table from an
appropriate record in the TASE.2 Points table (B151T2PT) before the DPA can transmit the
point data to, or receive point data from, a Client.
Table 12 Binary Input Mapping Table (B151MT01)
Field Name Description Allowed Values Default

Value
Binary Input The binary input system point number. Any valid binary input Undefined
Point system point or
If the point number is specified as Undefined, the Undefined (-1)
point value, when read by a Client, will be 0
(unless Invert Status is True). Any associated
TASE.2 Quality and Timestamp values will be
Invalid (Offline) and the DPA Startup Date-Time,
respectively.
Invert Status If Enabled, causes the DPA to invert the current Disabled or Enabled Disabled
state of the point before transmitting it. If
Disabled, the DPA transmits the state in the
System Database.
TT Events Determines whether the DPA monitors Time Process TT Events or Process TT
Tagged or Non Time Tagged events from Data Events
Collection Applications (DCAs). With either option Process Non-TT
you may configure a timestamp TASE.2 Point ($t) Events
for this binary input (or configure the DPA to
auto-create one). If you select Process Non-TT
Events, the DPA will generate the timestamp
when it receives notification of the change. If you
select Process TT Events, the DPA will use the
timestamp provided by the DCA, which will be
more accurate.
3.8 Binary Output Mapping Table (B151MT02)

Configure a record in this table for each binary output System Database Point the TASE.2 Server
Table 13 Binary Output Mapping Table (B151MT02)
Binary Output The binary output system point number. Any valid binary Undefined
Point output system
If the point number is specified as Undefined, the point or
point state, when read by a Client, will be 0 (Open). Undefined (-1)
Any associated TASE.2 Quality and Timestamp
values will be Invalid (Offline) and the DPA Startup
Date-Time, respectively.
Paired Point Specifies a Binary Output system point which is Any valid binary Undefined
unconditionally reset when a master station sends a output system
Control Operate request to the point selected by the point or
Binary Output Point field. Undefined (-1)
General B151-0CG-1.00-0 27
TASE.2 Server DPA
Configuration Guide
GE Energy

Control Type Determines the type of the binary output (Control). Trip / Close, Trip / Close
Note: The Control Type you choose must match the Raise / Lower or
hardware configuration of the device and (if Latched
applicable) the configuration of the DCA. For
instance, if you select Trip/Close, the hardware of a
D20 or D25 must be correctly wired and jumpered to
provide Trip/Close functions.
Initial On Dur Determines the initial time to hold a two state Control 0 to 1,000
(ms) in its Closed or Raised state, when pulsed. 4,294,967,295
Initial Off Dur Determines the initial time to hold a two state Control 0 to 1,000
(ms) in its Tripped or Lowered state, when pulsed. 4,294,967,295
Initial Num Determines the initial number of state changes to 0 to 65,535 1
Pulses cause the Control to execute when operated.
SBO Select Determines the maximum allowed interval between 0 to 30,000
Timeout the selection of this point and issuance or an output 4,294,967,295
operation (for this point only). This value is ignored if
SBO Enable is False.
Note: SBO values configured in this table are only used if the overall configuration includes SBO points, either
automatically generated or created as custom, which map to the entry in this table. Setting any of the SBO
parameters in this table does not cause the TASE.2 points to be generated.
3.9 Counter Input Mapping Table (B151MT03)

Configure a record in this table for each Counter (accumulator) System Database Point the
TASE.2 Server DPA can present to a TASE.2 Client. You must refer to each record in this table
from an appropriate record in the TASE.2 Points table (B151T2PT) before the DPA can transmit
the point data to, or receive point data from, a Client.
Table 14 Counter Input Mapping Table (B151MT03)
Counter Input The counter (accumulator) system point number. Any valid counter Undefined
Point input system point
If the point number is specified as Undefined, the running or Undefined (-1)
point value, when read by a Client, will be 0. Any
associated TASE.2 Quality and Timestamp values will be
Invalid (Offline) and the DPA Startup Date-Time,
respectively.
Counter Type Determines the type of the counter. If Pulse, the DPA will Pulse or Transition
divide the System Database value of the point by two Transition
before transmitting it. If Transition, the DPA will transmit
the System Database value.
TT Events Determines whether the DPA monitors Time Tagged or Process TT Process TT
Non Time Tagged events from Data Collection Events Or Events
Applications (DCAs). With either option you may configure Process Non-TT
a timestamp TASE.2 Point ($t) for this binary input (or Events
configure the DPA to auto-create one). If you select
Process Non-TT Events, the DPA will generate the
timestamp when it receives notification of the change. If
you select Process TT Events, the DPA will use the
timestamp provided by the DCA, which will be more
accurate.
28 B151-0CG-1.00-0 General
TASE.2 Server DPA
3.10 Analog Input Mapping Table (B151MT04)

Configure a record in this table for each analog input System Database Point the TASE.2 Server
Table 15 Analog Input Mapping Table (B151MT04)
Field Name Description Allowed Recc’d /

Values Default
Value
Analog Input The analog input system point number. Any valid Undefined
Point If the point number is specified as Undefined, the point value, when analog input
read by a Client, will be 0 (Open). Any associated TASE.2 Quality system point
and Timestamp values will be Invalid (Offline) and the DPA Startup or Undefined
Date-Time, respectively. (-1)
Event Determines the net value change (from the previously reported -1 to 32767 -1
Deadband value) required to generate Information Reports (-1 disables
evaluation).
TT Events Determines whether the DPA monitors Time Tagged or Non Time Process TT Process TT
Tagged events from Data Collection Applications (DCAs). With Events or Events
either option you may configure a timestamp TASE.2 Point ($t) for Process Non-
this binary input (or configure the DPA to auto-create one). If you TT Events
select Process Non-TT Events, the DPA will generate the
timestamp when it receives notification of the change. If you select
Process TT Events, the DPA will use the timestamp provided by the
DCA, which will be more accurate.
Scale Factor Scaling factor to be applied to raw system value to produce an -1.0e17 to 1.0
engineering value in floating point representation. See equation +1.0e17
below.
Offset Offset to be applied to raw system value to produce an engineering -1.0e17 to 0
value in floating point representation. See equation below. +1.0e17
The analog input offset and scaling actions are performed according to the following formula:
TASE.2ServerFloatValue = SystemValue × ScaleFactor + Offset
This formula is only applied for floating point TASE.2 server values. Integer TASE.2 server
values are equivalent to the system value.
3.11 Analog Output Mapping Table (B151MT05)

Configure a record in this table for each analog output System Database Point the TASE.2 Server
General B151-0CG-1.00-0 29
TASE.2 Server DPA
Configuration Guide
GE Energy
Table 16 Analog Output Mapping Table (B151MT05)
Field Name Description Allowed Recc’d. /

Values Default Value
Analog The analog output system point number. If the point number is Any valid Undefined
Output Point specified as Undefined, the point value, when read by a Client, analog output
will be 0 (Open). Any associated TASE.2 Quality and system point
Timestamp values will be Invalid (Offline) and the DPA Startup or Undefined
Date-Time, respectively. (-1)
Scale Factor Scaling factor applied to TASE.2 floating point value to derive a -1.7e38 to 1.0
raw system value. See equation below. +1.7e38
Offset Offset applied to TASE.2 floating point value to derive a raw -1.7e38 to 0
system value. See equation below. +1.7e38
SBO Select Determines the maximum allowed interval between the selection 0 to 30,000
Timeout of this point and issuance or an output operation (for this point 4,294,967,29
only). This value is ignored if SBO Enable is False. 5
Note: SBO values configured in this table are only used if the overall configuration includes SBO points, either
automatically generated or created as custom, which map to the entry in this table. Setting any of the SBO
parameters in this table does not cause the TASE.2 points to be generated.
The analog output offset and scaling actions are as follows:
TASE 2ServerFloatValue − Offset

SystemValue =
ScaleFactor
This formula is only applied for floating point TASE.2 server values. Integer TASE.2 server
values are equivalent to the system value.
30 B151-0CG-1.00-0 General
TASE.2 Server DPA
4. Configuring Other Applications

This section provides an overview of other GE Energy TASE.2 applications, which must be
configured for use with the TASE.2 Server DPA. Due to the complex nature of TASE.2
addressing, the user should refer to the configuration guides mentioned below. It is beyond the
scope of this document to provide sufficient information for configuring the TASE.2 Data Links
and BridgeMAN.
4.1 Configuring BridgeMAN

This section provides a brief overview of how the Bridge Manager (B015-0) is configured and
used in a UCA environment. Refer to the BridgeMAN Configuration Guide (B015-0CG.DOC)
for detailed information on configuring this software.
The GE Energy Bridge Manager (BridgeMAN) is an application that allows any user application
to communicate with other peer applications.
BridgeMAN supports communication over protocols defined by the TASE.2. These protocols
include Seven Layer (Connection and Connectionless mode) and Three Layer (ADLC)
Specifications, as well as the RFC 1006 Seven Layer option ( ISO transport services on top of
the TCP).
The configuration file for BridgeMAN defines four tables, described below:
B015_CFG This table contains general configuration parameters. Only one record is
required, and it must always be present.
B015_LAT This table contains at least one entry for each local application using
BridgeMAN. Each BridgeMAN channel a local application uses to send and
receive messages requires a separate entry.
B015_RAT This table contains at least one entry for each remote application which
BridgeMAN will send messages to or receive messages from. Each
BridgeMAN channel BridgeMAN may use to communicate with the remote
application requires a separate entry.
You can configure BridgeMAN to dynamically add a remote application to this
table if the remote application initiates communication with a local application.
B015_DBT The data link bridging table allows BridgeMAN to be used as an intermediate
"hop" to bridge messages between remote applications on different data links.
The table requires an entry for each remote application connected to the bridge.
This table is not used in the UCA environment. The Ethernet LAN provides
routing.
The BridgeMAN tables, which are referenced by the TASE.2 Data Links are:
B015_DIR This table defines the OSI Network and Transport layer addressing. It is used by
the TASE.2 (B106-0) Data Links to retrieve the OSI and IP addressing
information.
General B151-0CG-1.00-0 31
TASE.2 Server DPA
Configuration Guide
GE Energy
B015_OSI This table defines the OSI Network and Transport configuration parameters for
accepting, initiating and maintaining an OSI connection. It is used by the OSI
TP4 and CLNP (B108-0) Data Link, is not used by the TASE.2 (B106-0) Data
Link.
BridgeMAN must be configured with entries in the B015_LAT table for the local TASE.2 Server
DPA LRUs, and in the B015_RAT table for remote TASE.2 Clients. The Application ID (the
DPA AppID in the B151LRU table) is used by the TASE.2 Data Links as an OSI Transport
Selector (TSEL). For remote Clients, the Application ID (TSEL) may be required to be present
in the B015_RAT table, depending on the Security setting in the B151LRU table.
4.2 Configuring the TASE.2 Data Link

This section provides a brief overview of how the TASE.2 Data Link (B106-0) is configured and
used in a TASE.2 environment. Refer to the TASE.2 Data Link Configuration Guide (B106-
0CG.DOC) for detailed information on configuring this Data Link.
The TASE.2 Data Link software is installed in a GE Energy device to provide a means for
applications to send and receive messages using the RFC 1006 Transport layer interface running
over TCP/IP on Ethernet LANs. RFC 1006 refers to the Request For Comments specification.
The Data Link conforms to the UCA Version 2.0 7-Layer profile.
The configuration for the TASE.2 Data Link uses one table, described as follows:
B106_CHN This table contains information for a particular Data Link Channel. This table
contains at least one record and each record is used to define, in conjunction with
the BridgeMAN tables, the local addressing and characteristics of data
communications for a particular TASE.2 RFC 1006 LAN connection.
The BridgeMAN (B015-0) tables, which are referenced by the Data Link are B015_DIR,
B015_OSI, B015_LAT and B015_RAT.
The Internet Protocol Stack (B100-0) table, which is referenced by the Data Link is B100HOST.
This tables provides the IP address of the local device.
The TASE.2 Data Link uses the Local Address SAP field in the B106_CHN table to identify
(though and offset into the B100HOST table) the IP (Network Layer) address the TASE.2 Server
DPA will respond to in a TCP/IP LAN environment. Only ONE IP Address is allowed per
device. Each LRU within the DPA is addressed by its Application ID (TSEL), using
BridgeMAN’s tables.
In the configuration guide for the TASE.2 Data Link, pay particular attention to the discussion of
TASE.2 addressing.
32 B151-0CG-1.00-0 General
TASE.2 Server DPA
A. Error Log Messages

During startup, the DPA checks its configuration tables and prints messages to the WESMAINT
Error Log describing any errors or discrepancies it found.
These error messages are often generated when an invalid configuration is used. When an error
occurs, determine if a valid configuration is being used by generating and downloading the
configuration.
Expressions in angular brackets, such as "<xx>", are filled with the appropriate values by the
DPA.
Messages logged to the WESMAINT Error Log by the DPA will contain the process name. This
name will be either:
B151:
or
B151-S-xx: where xx is the process number
B151-E-xx: where xx is the process number
B151-R-xx: where xx is the process number
A.1 Fatal Error Messages

Fatal error messages indicate the application is suspending due to either an invalid critical
configuration parameter, or a critical process initialization sequence failed.
F1: Spawner failure attaching to WIN, code <n>. Suspending.
F3: Spawner failure detaching from WIN, code <n>. Suspending.
F21: Bad status <n> attaching to WIN. Suspending.
F22: Report Enable for WIN event <n> failed. Suspending.
F23: WIN_DPA_READY_CMD failed. Suspending.
Cause:
• The DPA was unable communicate with the System Point Database (WIN).
Remedy:
• Examine the state of the WIN process (B008-1). This is a system problem. Contact GE
Energy for assistance.
General B151-0CG-1.00-0 33
TASE.2 Server DPA
Configuration Guide
GE Energy
F2: Failure getting CCU status, code <n>. Suspending.

Cause:
• The DPA was unable communicate with the System Point Database manager (WIN) to
determine the operating mode of the CCU.
Remedy:
• Examine the state of the WIN process (B008-1). This is a system problem. Contact GE
Energy for assistance.
F4: Fatal Configuration Fault for LRU <n>. Suspending.

F16: LRU <n> Failed to initialize. Suspending.
Cause:
• A fatal error occurred during configuration checking or initialization for LRU #n.
Remedy:
• Examine the WESMAINT log for E or W level errors entries preceding this error.
F5: Not enough mem for B151 DPA Context. Suspending.

F6: Not enough mem for MMS Context. Suspending.
F7: Not enough mem for LRU <n> Conn info. Suspending.
F8: Not enough mem for LRU <n> MMS Conn rec. Suspending.
F9: Not enough mem for DPA Data. Suspending.
F17: Not enough memory for BM receive buffer. Suspending.
F18: Not enough memory for BM transmit buffer. Suspending.
Cause:
• Not enough memory is available on the device.
Remedy:
• See Section A.5 Resolving Memory Problems.
F10: Could not spawn LRU <n> Service process. Suspending.

F11: Could not activate LRU <n> Service proc. Suspending.
F12: Could not spawn LRU <n> Receive process. Suspending.
F13: Could not activate LRU <n> Receive proc. Suspending.
F14: Could not spawn LRU <n> Event process. Suspending.
F15: Could not activate LRU <n> Event proc. Suspending.
34 B151-0CG-1.00-0 General
TASE.2 Server DPA
Cause:
• The DPA was unable to create or activate processes required to run LRU #n.
Remedy:
• Operating system resources are not sufficient. May require the removal of some resident
applications. If this is not feasible, add the “PSOS” application to your configuration and
increase the number of process control blocks available to the system.
F19: Unable to attach to BridgeMAN with AppID <n>. Suspending.

Cause:
• The DPA was not able to communicate with BridgeMAN (B015-0) to establish a connection
for Application ID n.
Remedy:
• Verify that the application IDs, for the LRUs configured, match those in BridgeMAN’s LAT
table. If the error persists, examine the WESMAINT log for error messages from
BridgeMAN and the TASE.2 Data Link (B106-0) configured for the DPA’s use. Refer to the
documentation for the DTA giving errors.
F20: LRU <n> Null pw with Authentication set. Suspending.

Cause:
• Authentication was enforced for LRU n, but no password was defined in configuration.
Remedy:
• Examine the B151AUT configuration table and ensure a valid Authentication password is
defined for the configured for LRU n. If the problem is persistent or cannot be resolved,
contact GE Energy for assistance.
F24: Failed finding Time Zone process <n>. Suspending.

Cause:
• The Time Zone and DST Settings DTA process was not spawned. The error code is n.
Remedy:
• Examine whether the B148 application was configured within ConfigPro. Also examine
whether it was spawned by using the qp B148 command in 68k monitor. If the problem is
persistent or cannot be resolved, contact GE Energy for assistance.
F25: Failed requesting Time Zone data <n>. Suspending.

Cause:
• A fatal error occurred at startup while requesting Time Zone and DST Settings data from
Time Zone and DST Settings DTA.
General B151-0CG-1.00-0 35
TASE.2 Server DPA
Configuration Guide
GE Energy
Remedy:
• Examine the WESMAINT log for E or W level errors that may be related to the operation of
B148. Verify the B148 application is running by using the qp B148 command in 68k
monitor. If the problem is persistent or cannot be resolved, contact GE Energy for assistance.
F26: Failed to create semaphore for LRU <n>. Suspending.

Cause:
• The DPA was unable to create an operating system semaphore (software interlock) for LRU
#n.
Remedy:
• The device has, probably, run out of operating system resources. This may require removing
some resident application(s) or reducing the number of LRUs.
F27: Error in RTG processing for LRU <n>. Suspending.

Cause:
• A serious error was encountered while creating the TASE.2 Point dictionary for LRU #n.
Remedy:
• Examine the WESMAINT log for E or W level error entries preceding this error.
A.2 Error Messages

E1: Error creating TASE.2 point for LRU <n>. Skipping LRU.
Cause:
• The DPA encountered a serious error while creating the TASE.2 Point dictionary for LRU
#n.
Remedy:
• Examine the WESMAINT log for W or E level messages preceding this error.
E2: Configuration Fault for LRU <n>. Skipping LRU.

Cause:
• The DPA encountered a serious configuration error during startup for LRU #n.
Remedy:
• Examine the WESMAINT log for W or E level errors preceding this error.
36 B151-0CG-1.00-0 General
TASE.2 Server DPA
E3: Cannot create LRU <n> Receive exchange. Skipping LRU.

E4: Cannot create LRU <n> Event Handler exch. Skipping LRU.
Cause:
• The DPA was unable to create a required system message exchange for LRU #n.
Remedy:
• The device has, probably, run out of operating system resources. This may require removing
some resident application(s) or reducing the number of LRUs. If this is not feasible, add the
“PSOS” application to your configuration and increase the number of exchanges available to
the system.
E5: Comm fail binary output pnt is offline

Cause:
• The configured comm fail output point was offline during DPA initialization.
Remedy:
• The DPA will continue to try to use the comm fail points. If it is still offline, this message is
repeated. Determine why the point was offline and, if possible, correct the problem.
E6: Comm Fail output request failed. Status <n>

Cause:
• The DPA attempted to operate the comm fail output point and received an error from the
System Point Database – code n.
Remedy:
• The DPA will continue to try to use the comm fail points. If the System Point Database error
persists, this message is repeated. Examine the WESMAINT log for error messages from the
System Point Database application (B008 – WIN) referring to this point.
E7: Not enough memory for comm fail bin out block
Cause:
• Not enough memory is available on the device. The configured comm fail output point will
not be active.
Remedy:
General B151-0CG-1.00-0 37
TASE.2 Server DPA
Configuration Guide
GE Energy
E8: Not enough memory for RTG tables

E9: Not enough memory for RTG name tables
E10: Not enough mem for LRU <n> Dyn DS allocation
E12: Not enough memory for Data Set storage
E13: Not enough mem: Data Set mbr <member name>
E14: Not enough memory for reporting triggers
E15: Not enough memory for reporting maps
Cause:
• Not enough memory is available on the device.
Remedy:
E16: Cannot find B151MT01 configuration table

Cause:
• The specified mapping table was not present in NVRAM at DPA startup.
Remedy:
• Correct the configuration and download it, then restart the device.
A.3 Warning Messages

Warning messages are printed to the WESMAINT Error Log if a system function call fails. The
application will attempt to handle these errors without suspending or jeopardizing the integrity of
the system. If a warning message occurs repeatedly, contact the Customer Service Department to
report the error. The following is the list of warning messages printed by the TASE.2 Server
DPA
W1: B151T2 rec <recno> Invalid domain name, Ignoring rec

Cause:
• The TASE.2 Configuration Table record whose record number is recno contains an invalid
Domain Name field. Valid names must consist only of the characters: A-Z, a-z, 0-9,_ and $.
No spaces are allowed in the names.
38 B151-0CG-1.00-0 General
TASE.2 Server DPA
Remedy:
• Remove spaces and illegal characters from the Domain Name field.
W2: B151T2PT rec <recno> Invalid point name, Ignoring rec

Cause:
• The TASE.2 Point Table record whose record number is recno contains an invalid Point
Name field. Valid names must consist only of the characters: A-Z, a-z, 0-9,_ and $. No
spaces are allowed in the names.
Remedy:
• Remove spaces and illegal characters from the Point Name field.
W3: TASE.2 point <point name> out of count range, Ignoring

Cause:
• The DPA detected a TASE.2 point table entry that referenced a non-existent mapping table
entry. Since ConfigPro checks for such errors, the likely cause is a mismatch between
configuration and firmware version.
Remedy:
• Ensure configuration and firmware versions match.
W4: B151T2PT rec <recno> AqCtrl bad group num, Ignoring rec
Cause:
• The TASE.2 Point Table record whose record number is <recno> is using the special name
“AqCtrln”, where n is the group number, but the group number is either not a number or not
in the range 1 to 255.
Remedy:
• Change the group number in the Point Name to a three-digit number in the range 1 to 255.
W5: TASE.2 bad special object <point name>, Ignoring

Cause:
• The indicated point name is not a valid name for the “Special” Point Type. The valid special
names are:
− Transfer_Set_Name
− DSConditions_Detected
− Event_Code_Detected
− Transfer_Set_Time_Stamp
General B151-0CG-1.00-0 39
TASE.2 Server DPA
Configuration Guide
GE Energy
Remedy:
• Ensure the indicated TASE.2 Point table record contains a valid Point Name field according
to the list above.
W6: B151T2PT pnt <%s> bad type, Ignoring rec

Cause:
• The TASE.2 Point Table record whose record number is <recno> has an invalid Point Type
field. This was likely caused by a mismatch between the configuration and firmware
versions.
Remedy:
• Ensure the configuration and firmware versions match.
W7: B151T2PT record <n> Binary In number or offset wrong

Cause:
• The T2PT table contains an invalid system point offset or count in record #n. Note: An Error
message will follow these warning messages and the LRU instance will be suspended.
Remedy:
• Edit the T2PT table and correct the error.
W8: System Pnt <n> in B151MT01 (rec <nn>) out of range

Cause:
• The specified mapping table contains an invalid system point number, n, in record #nn.
Remedy:
• Edit the mapping table and correct the error. Note: An Error message will follow these
warning messages and the LRU instance will be suspended.
W9: B151MT01 record <n>. Illegal TT Event Enable field

Cause:
• The binary input mapping table contains an invalid entry in the TT Events field in record #n.
Remedy:
• Edit the mapping table and correct the error.
40 B151-0CG-1.00-0 General
TASE.2 Server DPA
W10: B151MT01 record <n>. Illegal Invert Enable field

Cause:
• The binary input mapping table contains an invalid entry in the Invert Enable field in record
#n.
Remedy:
W11: B151T2PT record <n> Binary Out number or offset wrong

• Refer to W7.

W13: Paired Pnt <n> in B151MT02 (rec <nn>) out of range
• Refer to W8.
W14: Paired Pnt equals System Pnt in B151MT02 (rec <n>)

Cause:
• Attributes Binary Output Point and Paired Point in record #n of B151MT02 reference the
same WIN point, which is not permitted.
Remedy:
W15: B151MT05 rec <n>. 32Bit pnt count not 2

Cause:
• Analog output mapping table record #n contains an Analog Size of 32, but the associated
TASE.2 Points table entry does not have Num System Points set to 2. Since Analog Size is
fixed at 16, the likely cause of this error is a mismatch in configuration and firmware version.
Remedy:
• Ensure that the appldef versions in the configuration match the application versions in the
firmware.
W16: B151T2PT record <n> Counter number or offset wrong

• Refer to W7.

• Refer to W8.
General B151-0CG-1.00-0 41
TASE.2 Server DPA
Configuration Guide
GE Energy
W18: B151MT03 record <n>. Illegal counter type field

W19: B151MT03 record <n>. Illegal counter size field
Cause:
• The counter mapping table contains an invalid type (not P or T), or size (16 or 32) in record
#n.
Remedy:
W20: B151LRU rec <n> Application ID is zero!

Cause:
• The application ID for the LRU, defined in record #n, is 0.
Remedy:
• Edit the LRU table and correct the error.
W21: B151LRU rec <n> Num Authents too big - setting to max
Cause:
• The number of authentication records for this LRU (in rec #n) exceed the DPA’s maximum
(currently 3).
Remedy:
• No action – the default number will be used.
W22: B151LRU rec <n> Authentication number or offset wrong

Cause:
• The specified table offset or number for the LRU, defined in record #n, is invalid.
Remedy:
• Edit the LRU table and correct the error.
W23: B151T2PT rec <n> Analog Out number or offset wrong

• Refer to W7.

• Refer to W8.
42 B151-0CG-1.00-0 General
TASE.2 Server DPA
W25: Table overflow adding <name> - discarded

Cause:
• The DPA has discarded the point name “name”. The reason for rejection is due to an internal
software error.
Remedy:
• Contact GE Energy for assistance.
W26: B151T2PT rec <n> Analog In number or offset wrong

• Refer to W7.

• Refer to W8.
W28: B151MT04 rec <n>. Illegal analog in size field

Cause:
• The analog input mapping table contains an invalid size (16 or 32) in record #n.
Remedy:
W29: B151MT04 rec <n>. Invalid time tag

Cause:
• The analog input mapping table contains an invalid TT Events field in record #n, which was
likely caused by a mismatch between firmware version and configuration version.
Remedy:
• Ensure the firmware version matches the configuration version.
W30: Discard: [<name>] - <reason>

Cause:
• The DPA has discarded the point name “name” (constructed from the B151T2PT table
entries). The reason for rejection is “reason”. Note: RTG refers to the Run-Time GOMSFE
processing module, which reads the configured names and types and creates the TASE.2
Model (dictionary) the server will present.
General B151-0CG-1.00-0 43
TASE.2 Server DPA
Configuration Guide
GE Energy
Remedy:
• Examine the entries in the T2PT table and, based on the reason or code, correct the entries.
The LRU will continue to initialize – however, the named point will not be created. Refer to
the following table for the possible reasons, and what they mean.
Reason Description
"References GOMSFE primitive as The Functional Component or Data Objects portion of the Component / Custom
a structure" Name (proceeding the final $) is a name reserved for a Common Component
Class (primitive) component - e.g. V$PhasAi.
"References GOMSFE structure as The Common Component Class portion of the Component / Custom Name
a primitive" (following the final $) is a name reserved for a higher level component - e.g.
MX$V$Ang.
"Dictionary too large for memory Not enough system memory available. See Section A.5 Resolving Memory
allocation" Problems.
"Dictionary construction requires The DPA’s internal name processing stack is too small. This is likely due to a
larger stack" Brick with greater than 200 members. Check the Brick Instance table for bricks
with greater than 200 members. Reduce the size of these bricks by moving the
excess points into new bricks.
"Internal error constructing The DPA encountered an internal error. This is a system problem. Notify GE
dictionary" Energy for assistance.
"Premature end of dictionary table The DPA encountered an internal error. This is a system problem. Notify GE
data" Energy for assistance.
"Insufficient memory for Not enough system memory available. See Section A.5 Resolving Memory
constructing dictionary" Problems.
"Type of object must be specified" The TASE.2 Point Type was not specified.
"Max number of directory entries The DPA’s internal dictionary max size is too small. This is a system problem.
exceeded" Notify GE Energy for assistance.
W31: Duplicate Name: <name> - discarding

Cause:
• The DPA has rejected the point name “name” (constructed from the B151T2PT table entries)
because it is a duplicate.
Remedy:
• Examine the entries in the T2PT tables and correct the entries, using only one instance of the
point name. The LRU will continue to initialize.
W32: Name: <name> - wrong sys pnt type

Cause:
• The System Point Type specified for point “name” does not match the TASE.2 Point Type
class.
Remedy:
• Edit the B151T2PT table entry for this point to correct the problem.
44 B151-0CG-1.00-0 General
TASE.2 Server DPA
W33: Not enough memory for GOMSFE processing

Cause:
• Not enough memory is available on the device. Note: An Error message will follow these
warning messages and the LRU instance will be suspended.
Remedy:
W34: Invalid name: <name>, Ignoring rec

Cause:
• The DPA encountered a name string that didn’t begin with a letter (i.e. a-z or A-Z) and
discarded it. The invalid name string was located in an internal data structure created based
on the configuration tables.
Remedy:
• Check for a previous error that indicates the specific configuration table that the invalid name
is coming from.
W35: RTG dict err: <reason>

• Refer to W30.
W39: Unable to create stats table (code <0xn>).

Cause:
• The DPA failed to create the statistics table (B151STAn, where n is the LRU instance
number) in NVRAM, with error code 0xn.
Remedy:
W40: Unable to set recs for stats table (code <0xn>).

Cause:
• The DPA failed to set the number of records for the statistics table (B151STAn, where n is
the LRU instance number), with error code 0xn.
Remedy:
• Contact GE Energy Customer Service and report this error.
General B151-0CG-1.00-0 45
TASE.2 Server DPA
Configuration Guide
GE Energy
W41: Mem Re-alloc failed for ack, code <error code>

W42: Mem De-alloc failed for ack, code <error code>
Cause:
• The DPA failed to free a data buffer that was required for processing a control request.
Remedy:
• Contact GE Energy, and report this error.
W43: Out of memory for define Data Set, Rejecting

Cause:
• The DPA was unable to allocate enough memory.
Remedy:
W44: BM receive error <n>

Cause:
• The DPA received an error (code n) from BridgeMAN (B015-0) while receiving a data
message.
Remedy:
• Examine the WESMAINT log for preceding errors from BridgeMAN. Refer to the
BridgeMAN documentation for correct the problem.
W45: Failed to find point descriptor tbl, type <n>

W46: Point descriptor tbl, type <n>, no records
W47: Point descriptor tbl, type <n>, no such point <nn>
W48: Point desc tbl, type <n>, point <nn>, read fail
Cause:
• The DPA encountered an error accessing the descriptor table for points of type n (specific
point #nn). Types are system point type (1=binary input, 2=binary output, 3=counter,
4=analog input, 5=analog output)
Remedy:
• Examine the DCA configuration for this point type or number. Correct the DCA
configuration, if possible. The DPA will report a null (blank) description for these points.
Note: An Error message will follow these warning messages and the LRU instance will be
suspended.
46 B151-0CG-1.00-0 General
TASE.2 Server DPA
W49: Null sys point table for pnt <n>, type <n>
• Refer to W45.
W50: TASE.2 Data Set <data set name>, no valid members

Cause:
• The DPA was unable to allocate system memory for the data set indicated in the error
message.
Remedy:
W51: TASE.2 Data Set <data set name>, not enough memory
Cause:
• The DPA was unable to allocate enough memory to create the indicated data set.
Remedy:
W52: TASE.2 Data Set <data set name>, not found or bad domain
Cause:
• The DPA failed to add the data set members for the data set identified in the error message
because the data set wasn’t present in the Dictionary.
Remedy:
• Refer to a previous message that explains why the data set was not added to the Dictionary.
W53: Table overflowed. <TASE.2 point name> Data Set mbr not added
Cause:
• The DPA did not allocate enough space to store Dictionary and Data Set references.
Remedy:
W54: B151T2PT rec <recno> point name not found

Cause:
• The DPA failed to add the data set member corresponding to record #<recno> in the TASE.2
Data Sets Member Table. The reason for failure is that the Named Variable (identified by
point name) wasn’t present in the Dictionary.
General B151-0CG-1.00-0 47
TASE.2 Server DPA
Configuration Guide
GE Energy
Remedy:
• Refer to a previous message that explains why the Named Variable represented by point
name was not added to the Dictionary.
W55: Mapping DataSets failed, Ignoring

Cause:
• The DPA failed to initialize one or more data sets.
Remedy:
• Refer to the previous warning messages, which are more specific in the cause of the failure.
W56: Out of memory for DB context, Ignoring

Cause:
Remedy:
W57: Out of memory for DB points, Ignoring

Cause:
Remedy:
W58: Select point failed to add timer, Ignoring

Cause:
• The system ran out of timer resources. The impact is that the control point will not be
selected.
Remedy:
• Reduce the number of applications running on the affected node.
W59: Bad system event queue format in Log buffer

W60: Bad system event point type in Log buffer
W61: Bad system event queue value in Log buffer
Cause:
• The DPA detected a corruption in the log buffer.
48 B151-0CG-1.00-0 General
TASE.2 Server DPA
Remedy:
W62: Bad Data Set <data set name>, Ignoring

Cause:
• The DPA detected that a data set was referring to its members using an array reference,
which indicates a corruption.
Remedy:
W63: Trigger count mismatch: Data Set <%s>

Cause:
• The DPA detected a corruption while generating an information report.
Remedy:
A.4 Information Messages

Information messages indicate the application is taking some special action based on certain
configuration or initialization criteria.
I1: Cannot find table B151LRU . Deleting process.
Cause:
• The DPA was unable to locate its main configuration table. It is assuming that it should not
run and it will be deleted from the list of applications.
Remedy:
• Ensure the B151LRU table exists and contains at least one record. Ensure that this LRU was
not supposed to be disabled.
I2: Successfully created dictionary in NVRAM for LRU <LRU Index>

Cause:
• The DPA instance indicated by LRU Index successfully created its dictionary in NVRAM.
The DPA will create its dictionary in NVRAM if the Dictionary Persistence parameter is set
to Yes and this is the first time that the DPA has started since a new configuration or
firmware was installed. On subsequent restarts, the DPA will not generate this message
because it will use the dictionary in NVRAM.
General B151-0CG-1.00-0 49
TASE.2 Server DPA
Configuration Guide
GE Energy
A.5 Resolving Memory Problems

A number of the warning messages above are caused by insufficient memory in the RTU. When
you see one of these messages, type “qr /v” and “qr /n” to determine the amount of free memory
available. On the D200, you should also type “qr /gv” and “qr /gn”.
The commands “qr /v” and “qr /gv” tell you the RAM usage. If either command indicates free
RAM below 10KB, your system is running out of RAM. The commands “qr /n” and “qr /gn” tell
you the NVRAM usage. If either command indicates free NVRAM below 10KB, your system is
running out of NVRAM.
If your system is running out of RAM:
• Disable any applications that you are not using.
• Reduce RAM usage through configuration parameters of the DPA and other resident
applications. For example, reduce the number of points or number of buffers used.
If your system is running out of NVRAM:
• Disable any applications that you are not using.
• Reduce NVRAM usage through configuration parameters of the DPA and other resident
applications. For example, reduce the number of points.
• If on the D25 or D200, consider allocating more NVRAM and correspondingly reducing the
available RAM. On the D25, the available NVRAM is 2 MB less the Base System and
Global Variable Area (typically, 128 KB). On the D200, the available NVRAM is the entire
global memory space less the Base System Area of 1 MB.
You need to make sure that you leave enough RAM for application use. You can
approximate the RAM use based on the output of the “qr /v” and “qr /gv” commands. You
will want to allocate more than this amount to account for RAM that was allocated and then
freed during initialization.
If there is no NVRAM available, you may have to disable Dictionary Persistence on one or more
LRU instances.
50 B151-0CG-1.00-0 General
TASE.2 Server DPA
MODIFICATION RECORD
VERSION REV. DATE AUTHOR CHANGE DESCRIPTION
1.00 0 24 AUG 2010 J. Chen Created.
General B151-0CG-1.00-0 51

B151 0CG

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B151 0CG

Uploaded by

Copyright:

Available Formats

GE

TASE.2 Server DPA

GE and are trademarks and service marks of General Electric Company.

* Trademarks of General Electric Company.

About this Document .....................................................................................................................7

2. Set Up Procedure .....................................................................................................................16

3. Configuration Tables ...............................................................................................................20

4. Configuring Other Applications.............................................................................................31

A. Error Log Messages ................................................................................................................33

A.3 Warning Messages ............................................................................................................ 38

About this Document

Search Technical Support

Contact Customer Service

1.1 Overview of the TASE.2 Server DPA

1.1.1 Product Perspective

System Point Database (B008-1)

TAS.2 Server DPA

TASE.2 Data Link

Internet Protocol Software (B100-0)

iSCS Internet Software

Network Driver Interface (B109-0)

Lance Ethernet Driver (B101-0)

TSE.2 Client TASE.2 Client

Figure 1 System Overview

1.1.2 Product Functions

1.2 GE Energy Device Data Applications

Figure 2 Data Applications Within a GE Energy Device

1.2.1 Configuration Basics

1.3 Table Naming Conventions

1.4 DPA Configuration Overview

Table 1 Common tables

Table 2 TASE.2 Table Set tables

Table 3 Mapping Tables

1.4.1 Configuration Table Relationships

Figure 3 DPA Table Relationships

1.5 Configuration Errors

2.1 Stage 1 – Build the Configuration

2.1.1 TASE.2 Server Model

2.1.1.1 Step 1: Configure the DCAs and DTAs

2.1.1.2 Step 2: Set Up the Mapping Tables

2.1.1.3 Step 3: Determine the VCC Domains

2.1.1.4 Step 4: Set Up the TASE.2 Points and Types

2.1.1.5 Step 5: Set Up any TASE.2 Data Sets

2.2 Stage 2 – Generate Configuration

2.2.1 Step 1: Generate Downloadable File

2.2.2 Step 2: Find And Fix Errors

2.2.3 Step 3: Download Configuration File

2.2.4 Step 4: Determine if the TASE.2 Server DPA is Working

2.3 Stage 3 – Connect to DPA

PC with Config PC with UCA

Figure 4 Hardware Environment

3.1 DPA LRU Configuration Table (B151LRU)

3.1.1 LRU Main Tables

Field Name Description Allowed Values Default Value

Field Name Description Allowed Values Default Value

Field Name Description Allowed Values Default Value

3.1.2 Local / Remote Sub Table of B151LRU

Table 5 Local / Remote Sub Table to B151LRU

Field Name Description Allowed Values Default Value

3.2 Authentication Table (B151AUT)

Table 6 Authentication Table (B151AUT)

Field Name Description Allowed Values Default Value

3.3 TASE.2 Configuration Table (B151T2)